CN114666313A - Parameter acquisition method, server, terminal and readable storage medium - Google Patents
Parameter acquisition method, server, terminal and readable storage medium Download PDFInfo
- Publication number
- CN114666313A CN114666313A CN202011410554.0A CN202011410554A CN114666313A CN 114666313 A CN114666313 A CN 114666313A CN 202011410554 A CN202011410554 A CN 202011410554A CN 114666313 A CN114666313 A CN 114666313A
- Authority
- CN
- China
- Prior art keywords
- parameter acquisition
- parameters
- equipment
- service node
- parameter
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 230000008569 process Effects 0.000 claims abstract description 33
- 238000004891 communication Methods 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 20
- 230000035515 penetration Effects 0.000 claims description 7
- 230000003993 interaction Effects 0.000 abstract description 15
- 238000004904 shortening Methods 0.000 abstract 1
- 230000001413 cellular effect Effects 0.000 description 15
- 230000002452 interceptive effect Effects 0.000 description 3
- 230000005641 tunneling Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 235000014510 cooky Nutrition 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 239000000344 soap Substances 0.000 description 1
- 238000010561 standard procedure Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
Images
Classifications
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention provides a parameter acquisition method, a server, a terminal and a readable storage medium, wherein in the process of chaining back with client equipment, an equipment parameter acquisition instruction is issued to the client equipment, and the equipment parameter acquisition instruction comprises indication information for indicating the client equipment to acquire equipment parameters and service node parameters; and receiving a collection result sent by the client equipment according to the equipment parameter collection instruction. The method of the invention can obtain the service node parameters only by one message interaction process, thereby greatly shortening the completion time of the parameter acquisition task and reducing the flow occupation.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to but not limited to a parameter acquisition method, a server, a terminal and a readable storage medium.
Background
The basic idea of the TR-069 protocol is to utilize the simple object access protocol SOAP based remote procedure call RPC method, which is widely used in Web services.
In the existing TR069 protocol, a collection of client parameters requires multiple message interactions in the process of obtaining required service node parameters by using a GetParameterValue and GetParameterValue response standard method, which results in a long time for task completion, reduces user experience, and increases unnecessary traffic consumption due to multiple messages.
Disclosure of Invention
The parameter acquisition method, the server, the terminal and the readable storage medium provided by the embodiment of the invention can directly finish the acquisition of the service node parameters in the process of chaining back, thereby reducing the process of message interaction, reducing the completion time of the parameter acquisition task and reducing the flow consumption.
In order to solve the above technical problem, an embodiment of the present invention provides a parameter collecting method, applied to a server side, including: in the process of chaining back with client equipment, issuing an equipment parameter acquisition instruction to the client equipment, wherein the equipment parameter acquisition instruction comprises indication information for indicating the client equipment to acquire equipment parameters and service node parameters; and receiving an acquisition result sent by the client equipment according to the equipment parameter acquisition instruction so as to acquire the equipment parameters and the service node parameters.
The embodiment of the invention also provides a parameter acquisition method, which is applied to client equipment and comprises the following steps: in the process of chaining back with a server, receiving an equipment parameter acquisition instruction issued by the server, wherein the equipment parameter acquisition instruction comprises indication information for indicating the client equipment to acquire equipment parameters and service node parameters; identifying service node parameters needing to be acquired in the equipment parameter acquisition instruction; acquiring parameters according to the service node parameters to obtain an acquisition result; and sending the acquisition result to the server.
The embodiment of the invention also provides a server, which comprises a first processor, a first memory and a first communication bus; the first communication bus is used for realizing connection communication between the first processor and the first memory; the first processor is configured to execute one or more first computer programs stored in the first memory to implement the steps of the aforementioned parameter acquisition method.
The embodiment of the invention also provides a terminal, which comprises a second processor, a second memory and a second communication bus; the second communication bus is used for realizing connection communication between the second processor and the second memory; the second processor is configured to execute one or more computer programs stored in the second memory to implement the steps of the aforementioned parameter acquisition method.
The embodiment of the present invention further provides a computer-readable storage medium, where one or more first computer programs and one or more second computer programs are stored, where the one or more first computer programs are executable by one or more processors to implement the steps of the foregoing parameter acquisition method; alternatively, the one or more second computer programs may be executable by one or more processors to implement the steps of the aforementioned parameter acquisition method.
According to the parameter acquisition method, the server, the terminal and the readable storage medium provided by the embodiment of the invention, the indication information indicating the acquisition equipment parameters and the service node parameters of the client equipment is integrated in one equipment parameter acquisition instruction, so that the acquisition of the service node parameters can be completed in one instruction in certain implementation processes, the message interaction process is reduced, and the completion time of a parameter acquisition task is effectively shortened.
Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
FIG. 1 is a basic structure diagram of a first embodiment of the present invention;
FIG. 2 is a basic flowchart of a first embodiment of the present invention;
FIG. 3 is a diagram of an interactive architecture according to a first embodiment of the present invention;
fig. 4 is a basic flowchart of a second embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The first embodiment is as follows:
in order to solve the problem that in the prior art, a message needs to be interacted for multiple times in the process of obtaining required service node parameters, so that the time for completing a task is long, and the user experience is poor, please refer to fig. 1, in this embodiment, a server establishes a communication connection with a client device.
S201, in the process of chaining back with client equipment, issuing an equipment parameter acquisition instruction to the client equipment, wherein the equipment parameter acquisition instruction comprises indication information for indicating the client equipment to acquire equipment parameters and service node parameters;
specifically, in the process of chaining back with the client device, the server may issue an device parameter acquisition instruction to the client device, where the device parameter acquisition instruction is provided with indication information, and the indication information is used to indicate the client device to acquire the device parameter and the service node parameter. The process of chaining back to the client device is to establish a communication connection with the client for the first time, for example, the server completes network construction through a TCP protocol and an IP protocol. According to the rule, the connection of the deeper layer protocol can be performed only after the lower layer protocol is established, so that a TCP connection is established first, after the TCP connection is established, the client sends a request command, such as GET/sample/hello.jspshttp/1.1, to the server, and then the server sends a response, such as HTTP/1.1200OK, thereby completing the back link process to establish communication. After receiving an equipment parameter acquisition instruction, the client equipment identifies service node parameters in the equipment parameter acquisition instruction; and acquiring parameters according to the service node parameters to obtain an acquisition result. In this embodiment, the client device may be a CPE, an RSU, a set-top box, a router, or the like.
S202, receiving a collection result sent by the client device according to the device parameter collection instruction.
Specifically, the client device may perform corresponding parameter acquisition upon receiving the device parameter acquisition instruction. The acquisition result is then packaged and sent to the server, whereby the device parameters and the service node parameters may be included in one acquisition result. Therefore, in the embodiment, the service node parameters can be obtained only by one message interaction process, the completion time of the parameter acquisition task is greatly shortened, and the traffic occupation is reduced.
In an embodiment, the indication information includes a reverse address or a reverse penetration address of the client device, and an extension field corresponding to the indication to acquire the service node parameter.
Specifically, in this embodiment, for the communication between different servers and client devices, for example, when the server and the client device can communicate directly, the server links back the client device through a reverse address reported by the client device, where for example, the reverse address of the client device that can communicate directly includes a corresponding ip address and a device identifier, for example, http:// x0.x7.x1.15: xx002id ═ 00012$ $ subType ═ 00259E. In the case where the server and the client device cannot communicate directly, for example, the client device is in an intranet, the server is linked back to the client device through a STUN reverse address, and in some cases, the client is in the intranet, that is, in the intranet like 192.168.x.x, the server and the client need to establish a connection, including a reverse address of the client, including a corresponding ip, port, and pass-through field, for example, http://10.x.x.x:8080ts ═ 1120673700& id ═ 1234& un ═ CPE57689& cn ═ xtgrpc 6D3IPXS3& sig ═ 3545F7B5820D76 A3a509DA8D 38F 13512. And adding extension fields corresponding to the acquisition instruction of the service node parameters in the reverse address or the reverse penetration address in the process of back-linking the client equipment. In this embodiment, different service node parameters have different extension fields, so that the client device can conveniently acquire corresponding service parameters after receiving the indication information.
In one embodiment, the extension field includes a node address of a service node to be collected.
In one embodiment, the extension field is disposed after the reverse address or reverse tunneling address; or, the extension field is set in a request body of a request packet corresponding to the device parameter acquisition instruction;
when two or more node addresses are included, the node addresses are separated by a preset character.
Specifically, on the basis of the foregoing embodiment, in this embodiment, for example, in a case that the server and the client device can directly communicate with each other, the server links back the client device through the reverse address reported by the client device, and carries the node address of the corresponding service node in the process of the link back. Corresponding to the case of HTTP protocol get, the extension field is set after the reverse address or reverse tunneling address, and the client reverse address is exemplarily: http:// x0.x7.x1.15: xx002id ═ 00012$ subType ═ 00259E, if the server needs to collect service node parameters, the node parameters can be directly added in the reverse address, and different node addresses are separated by preset characters, for example, the server requires the client device to report two parameter values, i.e., device.cellular. interface.1.rssi and device.cellular. interface.1.status, and the device parameter collection instruction may be: http:// x0.x7.x1.15: xx002id ═ 00012$ subType ═ 00259E & node ═ device.cellular. interface.1.rssi | device.cellular. interface.1. status. Of course, if the address is a reverse penetration address, the corresponding service parameter acquisition can be achieved by using http://10. x.x.x.x: 8080ts ═ 1120673700& id ═ 1234& un ═ CPE57689& cn ═ XTGRWIPC6D3IPXS3& sig ═ 3545F7B5820D76A3DF45 a509DA8D8C38F13512& node ═ device.
And setting a situation extension field corresponding to the HTTP post in a request body of a request packet corresponding to the device parameter acquisition instruction. The http request contains a request line/state line, a request header, and a request body. The request header can store some cookies and token information; the request body may store the parameters and parameter data of the post, and in an embodiment, the extended field may be set in the request body of the request packet corresponding to the device parameter acquisition instruction.
In this embodiment, the device parameter acquisition instruction further supports a wildcard, for example, if the server requires the client to report all the following parameters and node values:
http://x0.x7.x1.15:xx 002id＝00012$$subType＝00259E&node＝Device.Cellular.Interface.1.*
certainly, the wildcard may further include a #, which is used to indicate a fuzzy matching node, for example, D #. C #. I #.1.RSSI indicates that the client device reports device.
Therefore, according to the method of the embodiment, the acquisition indication information of the service node parameters is issued through the node, a plurality of parameters are separated through the '|' symbol, and in order to reduce the length of the node parameters, the indication information supports wildcards. The separation symbol between the plurality of parameters is not limited to the characters in the above example.
In an embodiment, the receiving the device parameters and the service parameters returned by the client device according to the acquisition instruction includes: and receiving a data packet sent by the client device, wherein the data packet comprises device parameters and service node parameters acquired by the client device according to the device parameter acquisition instruction.
In one embodiment, the client device may send all device parameters and service node parameters in one data packet. Of course, the device parameter and the service node parameter may also be sent by a plurality of data packets, and in the case of sending the device parameter and the service node parameter by a plurality of data packets, the server combines the plurality of data packets after receiving all the data packets, thereby obtaining the device parameter and the service node parameter of the client device. In an embodiment, the client device may perform corresponding service node parameter acquisition upon receiving one service node parameter indication information, then package the acquired service node parameters into data packets and send the data packets to the server, and may complete acquisition of all service node parameters upon completing receiving all service node parameter indication information and send the data packets. This also makes it possible to achieve a greater saving in interaction time than the solutions of the prior art with multiple interactions. Of course, in an embodiment, all the device parameters and the service node parameters are sent in one data packet, so that the server can obtain the corresponding acquisition result only by receiving one data packet. For example, after the aforementioned server requires the client device to report two parameter values, i.e., device.cellular.interface.1.rssi and device.cellular.interface.1.status, the device parameter data packet reported by the client device may adopt the following format:
corresponding to the TR069 standard, in this embodiment, a second extension field corresponding to the indication information may be set in the Inform packet reported by the client device, and the collected service node parameters may be extended by the second extension field, so as to implement extended reporting of the corresponding service node parameters in the device parameter data. Therefore, the message interaction process of the server and the client equipment is simplified.
As shown in fig. 3, after receiving the device parameter data packet corresponding to the acquisition result reported by the client device, the server sends a reception reply to the client device. And then the client device sends an ending empty packet to the server, and finally the server can also send the ending empty packet to the client device, so that the client device and the server end the current parameter acquisition process through an interactive empty packet. Therefore, in the embodiment, the acquisition of the equipment parameters and the required service node parameters can be completed only through one instruction, and the message interaction efficiency is improved.
In other embodiments, the server may continue to issue the acquisition instruction to the client device after receiving the device parameter data packet corresponding to the acquisition result reported by the client device, and acquire the required service node parameter through the acquisition instruction. That is, after receiving the device parameter data packet corresponding to the acquisition result reported by the client device and receiving the completion null packet reported by the client device, the current parameter acquisition flow is not completed, and the acquisition instruction is continuously issued to the client device. Certainly, in this case, the parameter acquisition can be realized by GetParameterValue, or by issuing the device parameter acquisition instruction twice. And after the acquisition is finished, the server and the client equipment finish the current acquisition process through an interactive empty packet message.
In summary, in the method of the present invention, the server carries the service parameter node through the indication information in the process of chaining the client device back, thereby realizing that the client device directly reports the required service node parameter value in the sent first packet Inform packet, and thus the server can directly obtain the corresponding service node parameter value. The method greatly simplifies the interaction times of the server and the client device in the parameter acquisition process and improves the parameter acquisition efficiency.
Example two:
in order to solve the problem that in the prior art, a message needs to be interacted for multiple times in the process of obtaining a required service node parameter, which results in a long time for task completion and poor user experience, please refer to fig. 4, a first embodiment of the present invention provides a parameter acquisition method, which is applied to a client device, and includes:
s401, in the process of chaining back with a server, receiving an equipment parameter acquisition instruction issued by the server, wherein the equipment parameter acquisition instruction comprises indication information for indicating the client equipment to acquire equipment parameters and service node parameters;
specifically, in the process of chaining back with the server, the client device may receive an equipment parameter acquisition instruction issued by the server, where the equipment parameter acquisition instruction is provided with indication information, and the indication information is used to indicate the client device to acquire an equipment parameter and a service node parameter. The client device may perform corresponding parameter acquisition upon receiving the device parameter acquisition instruction. In this embodiment, the client device may be a CPE, an RSU, a set-top box, a router, or the like.
S402, identifying service node parameters needing to be collected in the equipment parameter collection instruction;
s403, acquiring parameters according to the service node parameters to obtain an acquisition result;
s404, sending the acquisition result to a server.
Specifically, the client device receives a device parameter acquisition instruction, extracts the device parameter acquisition instruction to identify a service node parameter to be acquired in the device parameter acquisition instruction, and then executes corresponding parameter acquisition according to the service node parameter. And finally, packaging the acquisition result and sending the acquisition result to a server, so that one acquisition result can comprise the equipment parameters and the service node parameters. In the embodiment, the service node parameters can be obtained only by one message interaction process, so that the completion time of the parameter acquisition task is greatly shortened, and the traffic occupation is reduced.
In an embodiment, the indication information includes a reverse address or a reverse penetration address of the client device, and an extension field corresponding to the indication to acquire the service node parameter.
Specifically, in this embodiment, for the communication between different client devices and the server, for example, in the case that the client device and the server can directly communicate, the server may link back the client device through the reverse address reported by the client. In the event that the server and client device cannot communicate directly, e.g., the client device is in an intranet, the server chains back the client device through the STUN reverse address. And adding extension fields corresponding to the parameters for indicating acquisition of the service nodes in the reverse address or the reverse penetration address in the process of back-linking the client equipment. In this embodiment, different service node parameters have different extension fields, so that the client device can conveniently acquire corresponding service parameters after receiving the indication information.
In an embodiment, the extension field includes a node address of the service node.
In one embodiment, the extension field is disposed after the reverse address or the reverse tunneling address, and different node addresses are separated by a predetermined character.
Specifically, on the basis of the foregoing embodiment, in this embodiment, for example, in a case that the server and the client device can directly communicate with each other, the server links back the client device through the reverse address reported by the client device, and carries the node address of the corresponding service node in the process of the link back. Illustratively, the client reverse address is: http:// x0.x7.x1.15:xx002id ═ 00012$ subType ═ 00259E if the server needs to collect service node parameters, the node parameters can be directly added in the reverse address, and different node addresses are separated by preset characters, for example, the server requires the client device to report two parameter values, i.e., device.cellular interface.1.rssi and device.cellular interface.1.status, so the device parameter collection instruction may be: http:// x0.x7.x1.15: xx002id ═ 00012$ subType ═ 00259E & node ═ device.cellular. interface.1.rssi | device.cellular. interface.1. status.
In this embodiment, the device parameter acquisition instruction further supports a wildcard, for example, if the server requires the client to report all the following parameters and node values:
http://x0.x7.x1.15:xx 002id＝00012$$subType＝00259E&node＝Device.Cellular.Interface.1.*
certainly, the wildcard may further include a #, which may be used to represent fuzzy matching nodes, for example, D #. C #. I #.1.RSSI represents that the client device reports device.
Therefore, the acquisition indication information of the service node parameters is issued through the node by the method of the embodiment, a plurality of parameters are separated by the "|" symbol, and the indication information supports wildcards in order to reduce the length of the node parameters.
In an embodiment, the receiving the device parameters and the service parameters returned by the client device according to the acquisition instruction includes: and receiving a data packet sent by the client device, wherein the data packet comprises device parameters and service node parameters acquired by the client device according to the device parameter acquisition instruction.
In one embodiment, the client device may send all device parameters and service node parameters in one data packet. Of course, the device parameter and the service node parameter may also be sent by a plurality of data packets, and in the case of sending the device parameter and the service node parameter by a plurality of data packets, the server combines the plurality of data packets after receiving all the data packets, thereby obtaining the device parameter and the service node parameter of the client device. In an embodiment, the client device may perform corresponding service node parameter acquisition upon receiving one service node parameter indication information, then package the acquired service node parameters into data packets and send the data packets to the server, and may complete acquisition of all service node parameters upon completing receiving all service node parameter indication information and send the data packets. This also makes it possible to achieve a greater saving in interaction time than the solutions of the prior art with multiple interactions. Of course, in an embodiment, all the device parameters and the service node parameters are sent in one data packet, so that the server can obtain the corresponding acquisition result only by receiving one data packet. For example, after the server requests the client device to report two parameter values, i.e., device.cellular.interface.1.rssi and device.cellular.interface.1.status, the device parameter data packet corresponding to the acquisition result sent by the client device may adopt the following format:
in an embodiment, as an example of the TR069 standard, in this embodiment, a second extension field corresponding to the indication information may be set in an Inform packet reported by the client device, and the collected service node parameters are extended by the second extension field, so that the corresponding service node parameters are extended and reported in the device parameter data. Therefore, the message interaction process between the server and the client device is simplified.
In an embodiment, the sending the acquisition result to the server according to the device parameter acquisition instruction further includes:
and if the current client equipment does not contain the service node parameters, adding a preset indication field in the returned equipment parameters.
In some embodiments, if the service node acquired by the indication client device in the indication information sent by the server does not exist or the client device fails to be matched with the corresponding service node, the service node is selected. The client device returns the device parameter and indicates the service node mismatch through the preset indication field in the returned device parameter. For example, if the server issues http:// x0.x7.x1.15: xx002id ═ 00012$ $ subType ═ 00259E & node ═ device.cellular. interface.1.home, after the client device receives the device parameter acquisition instruction, it determines that the corresponding service node does NOT exist, then 404NOT FOUND may be returned, for example:
in summary, in the method of the present invention, the client device carries the service parameter node through the indication information in the process of chaining back with the server, so that the client device can directly report the required service node parameter value in the sent first Inform packet, and the server can directly obtain the corresponding service node parameter value according to the Inform packet. The method greatly simplifies the interaction times of the server and the client device in the parameter acquisition process and improves the parameter acquisition efficiency.
The embodiment of the invention also discloses a server, which comprises a first processor, a first memory and a first communication bus;
the first communication bus is used for realizing connection communication between the first processor and the first memory;
the first processor is configured to execute one or more first computer programs stored in the first memory to implement the steps of the parameter acquisition method of the first embodiment.
The embodiment of the invention also discloses a terminal, which comprises a second processor, a second memory and a second communication bus;
the second communication bus is used for realizing connection communication between the second processor and the second memory;
the second processor is configured to execute one or more computer programs stored in the second memory to implement the steps of the parameter acquisition method of the second embodiment.
The embodiment of the present invention also provides a computer-readable storage medium, where one or more first computer programs and one or more second computer programs are stored, where the one or more first computer programs are executable by one or more processors to implement the steps of the parameter acquisition method according to the first embodiment;
the one or more second computer programs are executable by the one or more processors to implement the steps of the parameter acquisition method of the second embodiment.
It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing device), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
In addition, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Thus, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (10)
1. A parameter acquisition method is applied to a server side and comprises the following steps:
in the process of chaining back with client equipment, issuing an equipment parameter acquisition instruction to the client equipment, wherein the equipment parameter acquisition instruction comprises indication information for indicating the client equipment to acquire equipment parameters and service node parameters;
and receiving a collection result sent by the client device according to the device parameter collection instruction so as to obtain the device parameters and the service node parameters.
2. The parameter acquisition method according to claim 1, wherein the indication information includes a reverse address or a reverse penetration address of the client device, and an extension field corresponding to the indication of acquisition of the service node parameter.
3. The parameter acquisition method of claim 2, wherein the extension field includes a node address of a service node to be acquired.
4. The parameter acquisition method according to claim 3, wherein the extension field is provided after the reverse address or reverse penetration address; or, the extension field is set in a request body of a request packet corresponding to the device parameter acquisition instruction;
when two or more node addresses are included, the node addresses are separated by a preset character.
5. The parameter collection method according to any one of claims 1 to 3, wherein the receiving the device parameters and the service parameters returned by the client device according to the collection instruction comprises: and receiving a data packet sent by the client device, wherein the data packet comprises device parameters and service node parameters acquired by the client device according to the device parameter acquisition instruction.
6. A parameter acquisition method is applied to client equipment and comprises the following steps:
in the process of chaining back with a server, receiving an equipment parameter acquisition instruction issued by the server, wherein the equipment parameter acquisition instruction comprises indication information for indicating the client equipment to acquire equipment parameters and service node parameters;
identifying service node parameters needing to be acquired in the equipment parameter acquisition instruction;
acquiring parameters according to the service node parameters to obtain an acquisition result;
and sending the acquisition result to the server.
7. The parameter acquisition method of claim 6, wherein sending the acquisition result to the server according to the device parameter acquisition instruction further comprises:
and if the current client equipment does not contain the service node parameters, adding a preset indication field in the returned equipment parameters.
8. A server, comprising a first processor, a first memory, and a first communication bus;
the first communication bus is used for realizing connection communication between the first processor and the first memory;
the first processor is configured to execute one or more first computer programs stored in the first memory to implement the steps of the parameter acquisition method according to any one of claims 1 to 3.
9. A terminal comprising a second processor, a second memory, and a second communication bus;
the second communication bus is used for realizing connection communication between the second processor and the second memory;
the second processor is configured to execute one or more computer programs stored in the second memory to implement the steps of the parameter acquisition method according to any one of claims 4 to 7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores one or more first computer programs and one or more second computer programs, the one or more first computer programs being executable by one or more processors to implement the steps of the parameter acquisition method according to any one of claims 1 to 5; or the like, or, alternatively,
the one or more second computer programs are executable by one or more processors to implement the steps of the parameter acquisition method as claimed in claim 6 or 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011410554.0A CN114666313A (en) | 2020-12-04 | 2020-12-04 | Parameter acquisition method, server, terminal and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011410554.0A CN114666313A (en) | 2020-12-04 | 2020-12-04 | Parameter acquisition method, server, terminal and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114666313A true CN114666313A (en) | 2022-06-24 |
Family
ID=82025596
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011410554.0A Pending CN114666313A (en) | 2020-12-04 | 2020-12-04 | Parameter acquisition method, server, terminal and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114666313A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101227348A (en) * | 2008-02-02 | 2008-07-23 | 杭州华三通信技术有限公司 | Server and method for collecting performance statistics data of network equipment |
| US20090064268A1 (en) * | 2005-04-15 | 2009-03-05 | Thomson Licensing | Remote Management Method of a Distant Device, and Corresponding Video Device |
| US20100132000A1 (en) * | 2007-04-20 | 2010-05-27 | Gilles Straub | Management methods of a video device and corresponding video device |
| CN108900359A (en) * | 2018-08-08 | 2018-11-27 | 四川长虹网络科技有限责任公司 | Network equipment parameter batch capture system and method |
| CN109246235A (en) * | 2018-09-30 | 2019-01-18 | 广州圣亚科技有限公司 | Method of reseptance, device and the data monitoring system of monitoring data |
| WO2020233330A1 (en) * | 2019-05-20 | 2020-11-26 | 深圳壹账通智能科技有限公司 | Batch testing method, apparatus, and computer-readable storage medium |
-
2020
- 2020-12-04 CN CN202011410554.0A patent/CN114666313A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090064268A1 (en) * | 2005-04-15 | 2009-03-05 | Thomson Licensing | Remote Management Method of a Distant Device, and Corresponding Video Device |
| US20100132000A1 (en) * | 2007-04-20 | 2010-05-27 | Gilles Straub | Management methods of a video device and corresponding video device |
| CN101227348A (en) * | 2008-02-02 | 2008-07-23 | 杭州华三通信技术有限公司 | Server and method for collecting performance statistics data of network equipment |
| CN108900359A (en) * | 2018-08-08 | 2018-11-27 | 四川长虹网络科技有限责任公司 | Network equipment parameter batch capture system and method |
| CN109246235A (en) * | 2018-09-30 | 2019-01-18 | 广州圣亚科技有限公司 | Method of reseptance, device and the data monitoring system of monitoring data |
| WO2020233330A1 (en) * | 2019-05-20 | 2020-11-26 | 深圳壹账通智能科技有限公司 | Batch testing method, apparatus, and computer-readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 张一哲;姚辉军;李蓓佳;庄?;刘晨;: "基于TR-069协议的终端管理系统设计与应用", 广播电视网络, no. 02, 15 February 2020 (2020-02-15) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11411897B2 (en) | Communication method and communication apparatus for message queue telemetry transport | |
| CN102469124B (en) | Based on the implementation method of the mobile Internet business of AOG, gateway, agency and system | |
| CN101848107B (en) | SNMP (Simple Network Management Protocol) network element and communication method of SNMP network element and proprietary protocol network element | |
| CN106789606B (en) | Network communication system, management method and communication method thereof | |
| CN103795689A (en) | Resource subscription method and device | |
| CN113810438A (en) | Scheduling and requesting methods of service computing resources, node equipment and terminal | |
| CN106453683A (en) | Method for centralized access management of cameras | |
| CN113746928B (en) | Cross-cloud service calling method, device and system | |
| CN103997539A (en) | Radar operation state collecting and distributing system and method based on web service | |
| CN106970843B (en) | Remote calling method and device | |
| CN112055078A (en) | Data transmission method and device, computer equipment and storage medium | |
| CN105635083A (en) | Service processing method and service processing system based on server and client architecture | |
| CN114338063A (en) | Message queue system, service processing method, and computer-readable storage medium | |
| US7218714B2 (en) | Method of calling service among devices in home network | |
| US20140201376A1 (en) | Method and system for the handling of redundant long poll | |
| CN111064729B (en) | Message processing method and device, storage medium and electronic device | |
| CN114666313A (en) | Parameter acquisition method, server, terminal and readable storage medium | |
| CN101729530B (en) | Data synchronization method and data synchronization system | |
| CN103533001A (en) | Communication method and communication system based on HTTP multi-proxy, and intermediate proxy server | |
| CN113992740B (en) | Middleware based on autonomous control and data transmission method | |
| CN113596105B (en) | Content acquisition method, edge node and computer readable storage medium | |
| CN114844847A (en) | High-reliability real-time message distribution method and device | |
| CN111294358B (en) | Message processing method and device | |
| EP1780942A1 (en) | Method for automatically discovering a bus system in a multipoint transport network, multipoint transport network and network node | |
| CN113037803A (en) | Geological disaster monitoring method and system, electronic equipment and storage medium |
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 |