CN113794582A - Heaven and earth integrated network communication management protocol and method - Google Patents

Heaven and earth integrated network communication management protocol and method Download PDF

Info

Publication number
CN113794582A
CN113794582A CN202110914138.2A CN202110914138A CN113794582A CN 113794582 A CN113794582 A CN 113794582A CN 202110914138 A CN202110914138 A CN 202110914138A CN 113794582 A CN113794582 A CN 113794582A
Authority
CN
China
Prior art keywords
message
control agent
management
target
pdu
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
Application number
CN202110914138.2A
Other languages
Chinese (zh)
Inventor
赵伟程
田建召
刘言
赵立东
王颖
杨杨
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Academy of Electronic and Information Technology of CETC
Original Assignee
China Academy of Electronic and Information Technology of CETC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Academy of Electronic and Information Technology of CETC filed Critical China Academy of Electronic and Information Technology of CETC
Priority to CN202110914138.2A priority Critical patent/CN113794582A/en
Publication of CN113794582A publication Critical patent/CN113794582A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/28—Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
    • 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
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/255—Maintenance or indexing of mapping tables
    • 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/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • 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/22—Parsing or analysis of headers

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a communication management protocol and a method for a heaven-earth integrated network, which comprises the following steps: sending a first message to a target management and control agent, wherein the first message is determined by corresponding configuration according to user requirements and by using a protocol header in a preset format; and receiving a simple response message corresponding to the user requirement sent by the target management and control agent, and/or receiving a detailed response message corresponding to the user requirement sent by the target management and control agent. The method disclosed by the invention utilizes the protocol header with the preset format according to the user requirement through the first message to carry out corresponding configuration determination, and the corresponding response message is received and can also be realized according to the protocol with the preset format, so that the adoption of a unified architecture, a unified system and a unified standard between the space-based management and control and the foundation management and control is realized, and the seamless coverage of the wide-area networking is realized.

Description

Heaven and earth integrated network communication management protocol and method
Technical Field
The invention relates to the technical field of communication, in particular to a heaven and earth integrated network communication management protocol and a method.
Background
In recent years, with the continuous maturity of computer network technology, network communication has attracted extensive attention and gradually permeates people's life, study and work, so that it has important research value and application prospect. Computer networks, particularly transmission Control Protocol/Internet Protocol (TCP/IP) networks, are the basis of global information communication protocols, and various organizations build their own ethernet networks to implement information communication.
Currently, an IP-based local area network is built inside an international space station, where ground internet access is available to astronauts. The heaven and earth integrated network is a fusion network of a space satellite network and a ground network, and essentially realizes the fusion of various space satellite networks and heaven and earth networks by utilizing an internet protocol. However, the existing inter-domain protocol design lacks consideration of uniqueness of the space network, and if the inter-domain protocol design is directly deployed to the heaven-earth integrated information network, the inter-domain protocol design is unreasonable and faces various problems.
For example, the existing communication system mainly includes the internet, a ground gateway station, a high-throughput satellite, a vehicle-mounted small gateway station and a user terminal; the ground gateway station is respectively communicated with the Internet and the high-flux satellite; and the vehicle-mounted small gateway station is respectively communicated with the high-flux satellite and the user terminal. By the method, the user in the high-speed rail or the airplane can be ensured to communicate by using the user terminal, and the communication-in-motion problem of the user in the high-speed rail or the airplane is solved. However, the user terminal mainly uses the vehicle-mounted small gateway station, and such a design is not only difficult to implement, but also consumes materials and has low universality.
On the basis of adopting a space-ground gateway, different data link layer protocols and different physical layer protocols are configured in the spacecraft network and the ground network, so that data communication in the spacecraft network and the ground network is respectively executed; above the network layer of the world link, data communication between the world link is performed in an internet protocol manner. The invention realizes the integrated design of the spacecraft and the ground computer IP network, can directly operate equipment on the spacecraft, in particular test equipment, on the ground through the computer network, and is convenient for test development. However, only a method for communicating a spacecraft with a ground gateway is provided, a more universal application is not pointed out, and no solution is provided for faults possibly existing in the method.
Most of the existing integrated world communication management protocols only propose communication methods for individual fields, which depend on established rules or defined use scenarios, and have the following problems that are not solved yet: service processing time is prolonged, protocol design is redundant, and the requirement of comprehensively covering the space-ground management and control functions cannot be met.
Disclosure of Invention
The embodiment of the invention provides a space-ground integrated network communication management protocol and a method, which realize that a unified architecture, a unified system and a unified standard are adopted between space-based management and control and foundation management and control, and realize seamless coverage of wide-area networking.
The embodiment of the invention provides a heaven and earth integrated network communication management protocol, which comprises the following steps:
sending a first message to a target management and control agent, wherein the first message is determined by corresponding configuration according to user requirements and by using a protocol header in a preset format;
and receiving a simple response message corresponding to the user requirement sent by the target management and control agent, and/or receiving a detailed response message corresponding to the user requirement sent by the target management and control agent.
In some embodiments, the protocol header of the preset format includes a plurality of units, each unit corresponds to a field, and the field includes: a first message type, version number, IP address, encryption parameter, time identifier, message sequence number, message length, authentication parameter, and Protocol Data Unit (PDU);
the first message is obtained by configuring the PDU according to the requirement of a user.
In some embodiments, in a case that the first message is a query packet message, a parameter configuration message, or a task configuration message, the PDU of the first message includes: a second message type, a proxy representation, and a message ID.
In some embodiments, in the case that the first message is a query message, the PDU of the first message and the corresponding detailed response message further comprises a key-value pair parameter item configured to indicate the queried parameter;
in the case that the first message is a task configuration message, the PDU of the first message and the corresponding detailed response message further includes a device parameter item configured to indicate a status of the configured task;
in the case that the first message is a parameter configuration message, the PDU of the first message and the corresponding detailed response message further includes a configuration information item configured to indicate the configured device status.
In some embodiments, the following network entry/network exit authentication procedures are also included:
acquiring a network access authentication message sent by a target management and control agent;
carrying out protocol adaptation based on the network access authentication message, and sending the adapted network access authentication message to a security management system;
and after receiving the network access authentication response message of the security management system, sending a network access authentication detailed response to the target management and control agent.
In some embodiments, the method further includes reconstructing the message flow as follows to update the software of the target device:
sending a reconstruction request message to a target management and control agent so that the target management and control agent sends a reconstruction request with target equipment based on the reconstruction request message;
after a reconfiguration simple response message sent by the target management and control agent is acquired, data communication is established with the target device, wherein the reconfiguration simple response message is determined by the reconfiguration response sent by the target management and control agent after the reconfiguration preparation of the target device is completed.
In some embodiments, the method further includes the following active reporting procedure:
acquiring an active report message sent by a target management and control agent, wherein the active report message is sent by the target management and control agent after receiving a device parameter or an alarm message sent by target equipment;
and sending an alarm simple response message to the target management and control agent.
In some embodiments, in a case that the active report message includes an alarm report message, a PDU of the alarm report message includes an alarm information item configured to indicate status information of an alarm.
The embodiment of the invention also provides a heaven and earth integrated network communication management protocol, which comprises the first message.
An embodiment of the present invention further provides a data acquisition and distribution system, including a processor configured to:
sending a first message to a target management and control agent, wherein the first message is determined by corresponding configuration according to user requirements and by using a protocol header in a preset format;
and receiving a simple response message corresponding to the user requirement sent by the target management and control agent, and/or receiving a detailed response message corresponding to the user requirement sent by the target management and control agent.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the heaven and earth integrated network communication management protocol according to the embodiments of the present disclosure are implemented.
According to the embodiment of the invention, the first message is used for carrying out corresponding configuration determination according to the requirement of a user by utilizing the protocol header in the preset format, and the corresponding response message is received and can also be realized according to the protocol in the preset format, so that the adoption of a unified architecture, a unified system and a unified standard between space-based management and control and foundation management and control is realized, and the seamless coverage of wide-area networking is realized.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a basic flow diagram of an embodiment of the present disclosure;
fig. 2 is a schematic flow chart of a sky-based management and control agent for querying a message according to the embodiment of the present disclosure;
fig. 3 is a schematic flow chart of a query message-ground management control agent according to an embodiment of the present disclosure;
FIG. 4 is a flow chart illustrating a parameter configuration message according to an embodiment of the present disclosure;
FIG. 5 is a schematic diagram illustrating a task configuration message flow according to an embodiment of the disclosure;
fig. 6 is a schematic diagram illustrating a network entry/exit authentication process according to an embodiment of the disclosure;
FIG. 7 is a schematic reconstruction flow chart according to an embodiment of the disclosure;
fig. 8 is a schematic diagram of an alarm reporting process according to an embodiment of the disclosure.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The embodiment of the invention provides a communication management protocol of a world-wide integrated network, as shown in fig. 1, the communication management protocol disclosed by the invention is applied to a communication method of the world-wide integrated network, and comprises the following steps:
step S101, sending a first message to a target management and control agent, where the target management and control agent may be a space-based management and control agent or a ground-based management and control agent, and the first message is determined by using a protocol header in a preset format according to a user requirement. For example, the preset format may include a uniform message type, a version number, and other protocol formats, and a designated position of the preset format may set at least one field for distinguishing different message types, so that each message as a whole adopts a uniform protocol header, and the message type may be specifically defined by the at least one field, thereby implementing a uniform architecture, a uniform system, and a uniform standard, and implementing seamless coverage of wide area networking.
Step S102, receiving a simple response message corresponding to the user requirement sent by the target management and control agent, and/or receiving a detailed response message corresponding to the user requirement sent by the target management and control agent. The specific response adopted by the target management and control agent may be determined according to an actual definition, which is not limited herein. In this example, the target management and control agent may be a space-based management and control agent or a ground-based management and control agent, which is not limited specifically. The corresponding response message, whether it is a simple response message or a detailed response message, may be implemented by using the aforementioned uniform protocol header with a preset format.
The method disclosed by the invention utilizes the protocol header with the preset format according to the user requirement through the first message to carry out corresponding configuration determination, and the corresponding response message is received and can also be realized according to the protocol with the preset format, so that the adoption of a unified architecture, a unified system and a unified standard between the space-based management and control and the foundation management and control is realized, and the seamless coverage of the wide-area networking is realized.
In some embodiments, the protocol header of the preset format includes a plurality of units, each unit corresponds to a field, and the field includes: a first message type, version number, IP address, encryption parameter, time identifier, message sequence number, message length, authentication parameter, and Protocol Data Unit (PDU); the first message is obtained by configuring the PDU according to the requirement of a user.
A protocol header format may be defined in this example, comprising several fields, e.g. the protocol header format may be:
Figure BDA0003204805260000061
the specific definition of each field of the header may be:
a first message type: 1 byte, in the message parsing formula, the type of message transmitted is indicated by this byte.
Version number: 1 byte, when there is a protocol version change, different versions are indicated by this field. For example, a first version is represented by 0X01, a second version is represented by 0X02, and so on.
IP address: indicating the destination IP address.
Encryption parameters: 16 bytes, when the encryption parameters are all 0, the encryption is not carried out; otherwise, filling in encryption parameters, and encrypting the message load field through a DES-CBC algorithm. After receiving the message, the receiver decrypts the encrypted field through the local decryption key;
time identification: 8 bytes (to the nearest millisecond), when the command message is sent, a timestamp is generated in the message sequence indicating the time when the entity sent the command message.
Message sequence number: and 2 bytes, sequentially adding 1 to the message serial number of the initiator, filling the message serial number during receiving when the receiver returns a response message to indicate which message is responded to, and sequentially adding 1 to the serial number if a plurality of responses exist.
Message length: 2 bytes, which represents the size of the message byte sent by the message sender.
Authentication parameters: 16 bytes, when the authentication parameters are all 0, the authentication is not performed; otherwise, a 16-byte authentication key is obtained through the MD5 hash function. When sending the message, a message authentication code is generated using the authentication key and filled in the authentication parameter field.
PDU: the protocol data unit is specifically designed according to the type of the message, such as carrying various parameters and the like.
In some embodiments, in a case that the first message is a query packet message, a parameter configuration message, or a task configuration message, the PDU of the first message includes: a second message type, a proxy representation, and a message ID.
In some embodiments, in the case that the first message is a query message, the PDU of the first message and the corresponding detailed response message further comprises a key-value pair parameter item configured to indicate the queried parameter.
The PDU format of the query message in this example may include the following fields:
Figure BDA0003204805260000071
the description of each field of PDU of inquiry message is as follows:
the second message type: 1 byte;
agent identification: representing a unique identification of the message transmission destination.
And the message ID represents the number of the query message, and the query ID number of the returned query response message is the same as the number and represents the response to the message.
A flag bit: when the flag bit is 0, the key list query of subsequent OID is represented, and when the flag bit is 1, the parameters of all OID under the target IP address are queried;
key List: an OID list of parameters is obtained.
The acquire-simplex query-simple response PDU format may include:
Figure BDA0003204805260000081
the description of each field of the Inquire-SimpleRely query-simple response message PDU is as follows:
the second message type: 1 byte;
agent identification: representing a unique identification of the message transmission destination.
Message ID: the number of the query message is indicated, and the query ID number of the returned query response message should be the same as the number, indicating that the query response message is a response to the query message.
An acknowledgement bit: bit 1, default to 1, namely acknowledgement reply.
The acquire-DetailReply query-detail response PDU format may include:
Figure BDA0003204805260000082
the description of each field of the Inquire-detailRely query-detailed response message PDU is as follows:
the second message type: 1 byte;
agent identification: representing a unique identification of the message transmission destination.
Message ID: the number of the query message is indicated, and the query ID number of the returned query response message should be the same as the number, indicating that the query response message is a response to the query message.
A flag bit: when the flag bit is 0, the parameter represents that part of the OID is returned, and when the flag bit is 1, the parameter represents that all the OIDs under the destination IP address are returned.
Key-value pair parameters: and returning the queried device parameter key value pair, and filling false for the query failure value, and filling true for the query success value.
As shown in fig. 2 and 3, the present example further provides a communication method for querying message information, where the query message (the first message) is used for querying parameter information of a housekeeping computer cached on a skyscraper management and control agent by the data acquisition and distribution system, or for querying parameter information on a station controller, a network controller, and other devices by the acquisition and distribution system.
Firstly, a data acquisition and distribution system provides an information acquisition request to a management and control agent system. The message sent at this time is an inquiry message PDU.
And then the management and control agent carries out simple response to the data acquisition and distribution system after obtaining the request, and informs the data acquisition and distribution system that the management and control agent has received the information acquisition request and is preparing data. The message sent at this time is Inquire-SimpleRely query-simple response PDU.
And after the management and control agent obtains the corresponding data, sending a detailed corresponding message to the data acquisition and distribution system. The message sent at this time is an Inquire-detailReply query-detailed response PDU.
In the case that the first message is a parameter configuration message, the PDU of the first message and the corresponding detailed response message further includes a configuration information item configured to indicate the configured device status.
In this example, the format of the ParaConf parameter configuration PDU may include:
Figure BDA0003204805260000091
the description of each field of the ParaConf parameter configuration message PDU is as follows:
the second message type: 1 byte;
agent identification: representing the unique identification of the message transmission destination;
message ID: representing the number of the message in transmission, and filling the same number when the message returns to represent the response to the self-numbering message;
list of device parameters: and carrying out the configured device parameter key value pair.
The ParaConf-DetailReply parameter configuration-detailed response PDU format may include:
Figure BDA0003204805260000092
ParaConf-detailRely parameter configuration- -the detailed response message PDU fields are described as follows:
the second message type: 1 byte;
agent identification: representing a unique identification of the message transmission destination.
Message ID: represents the number of the message in transmission, and the same number is filled in when the message returns, which represents the response to the self-numbering message.
Error key-value pair parameter: the first key value pair is filled with 0 to indicate no exception, otherwise the key indicates the wrong device parameter OID, the value indicates the reason for the error occurrence, 0x1 indicates that the parameter is undefined, 0x2 indicates that the operation read-only variable is reserved, and other bits.
In this example, the parameter configuration message is used to perform configuration operations on parameters of the managed device, including modifying an attribute value or setting an attribute default value, and the response mode is a detailed response. The following steps can be performed, as shown in fig. 4:
firstly, a data acquisition and distribution system sends a parameter configuration message to a management and control agent, and the sent message is a ParaConf parameter configuration PDU.
After receiving the request, the management and control agent adapts to the protocol according to the parameters provided by the data acquisition and distribution system, and then sends the private protocol to the house computer or the station control (network control).
The housekeeping computer or the station control (network control) configures the parameters of the data acquisition and distribution system, and the control agent sends a detailed configuration response message to the data acquisition and distribution system after the configuration is finished. The message sent at this time is a ParaConf-detailRely parameter configuration-detailed response PDU.
In the case that the first message is a task configuration message, the PDU of the first message and the corresponding detailed response message further includes a device parameter item configured to indicate a status of the configured task.
The format of the MissionConf task configuration message PDU may include:
Figure BDA0003204805260000101
the descriptions of each field of the configuration message PDU of the MissionConf task are as follows:
the second message type: 1 byte;
agent identification: representing the unique identification of the message transmission destination;
message ID: representing the number of the message in transmission, and filling the same number when the message returns to represent the response to the self-numbering message;
configuring the effective time: represents the specific validation time of this configuration setting;
reporting period: the periodic frequency of information reporting comprises three different uploading periods of slow speed, medium speed and fast speed;
a flag bit: when the flag bit is 0, the parameter represents the parameters of the configured part OID, and when the flag bit is 1, the parameter represents the parameters of all OIDs under the configured destination IP address;
device key list: a key list of the configured OID device is required.
The MissionConf-DetailReply task configuration-detail response PDU format may include:
Figure BDA0003204805260000111
the descriptions of the fields of the messionconf-DetailReply task configuration-detailed response message PDU are as follows:
the second message type: 1 byte;
agent identification: representing the unique identification of the message transmission destination;
message ID: representing the number of the message in transmission, and filling the same number when the message returns to represent the response to the self-numbering message;
error key-value pair parameter: the first key value pair is filled with 0 to indicate no exception, otherwise the key indicates the wrong device parameter OID, the value indicates the error occurrence reason, 0x1 indicates that an operation is attempted on a non-existent variable, 0x2 indicates that an invalid value or invalid syntax is set and operated, 0x3 indicates that the management process attempts to modify a read-only variable, and others remain.
The task configuration message is used for the data acquisition and distribution subsystem to configure and modify parameters of the acquisition and reporting tasks of the management and control agent (such as changing the uploading frequency), and the response mode may be a detailed response. The specific process is shown in fig. 5, and includes:
firstly, a data acquisition and distribution system may send a task configuration message to a management and control agent, where the sent message is a MissionConf task configuration message PDU.
And after receiving the task configuration request, the management and control agent configures according to the task configuration parameters. And after the task is completed, sending an agent task configuration detailed response message to the data acquisition and distribution system. The message sent at this time is a MissionConf-detailRely task configuration-detailed response PDU.
In some embodiments, the following network entry/network exit authentication procedures are also included:
acquiring a network access authentication message sent by a target management and control agent;
carrying out protocol adaptation based on the network access authentication message, and sending the adapted network access authentication message to a security management system;
and after receiving the network access authentication response message of the security management system, sending a network access authentication detailed response to the target management and control agent.
In this embodiment, a network entry/network exit authentication procedure is further introduced, which also includes PDUs in a unified format, for example: the authentication network entry/exit authentication PDU format may include:
Figure BDA0003204805260000121
the description of each field of the authentication PDU for network entry/network exit is as follows:
message type: 1 byte;
agent identification: a unique identification representing the agent.
Network entry/exit identification: the flag bit is 0 to indicate a logout request, and when it is 1, it indicates a network entry request.
The network access identification code is as follows: 16 bytes, and the unique identification code for managing the proxy to enter/exit the network.
The authentication-detach reply inbound authentication response PDU format may include:
Figure BDA0003204805260000122
the fields of the authentication-DetailReply enter/exit network authentication-detailed response PDU are described as follows:
the second message type: 1 byte;
agent identification: representing the unique identification of the reporting message agent;
permission bit: 1 bit, 0 indicates rejection, 1 indicates passing of network entry/exit authentication;
the reason for the error is as follows: if the permission bit is set to 0, the error reason field is set to 0x1 to indicate that the network access identification code is expired, 0x2 to indicate that the network access identification code is wrong, and other bits are reserved.
The authentication network access/network withdrawal authentication message is used for network access/network withdrawal authentication of the management and control agent, and the interactive flow is shown in fig. 6, and includes:
firstly, the management and control agent sends a network access authentication message to the data acquisition and distribution subsystem, and the message sent at this time is an authentication PDU (protocol data Unit) for network access/network withdrawal.
After receiving the message, the data acquisition and distribution subsystem carries out protocol adaptation on the message and then sends the message to the safety management system.
The security management system carries out network access authentication on the security management system, and then sends a network access authentication response message to the data acquisition and distribution subsystem.
And after receiving the network access authentication response message, the data acquisition and distribution subsystem carries out protocol adaptation on the network access authentication response message and then sends the network access authentication detailed response message to the management and control agent. At this time, the message sent is the authentication-detail reply network access authentication response PDU.
In some embodiments, the method further includes reconstructing the message flow as follows to update the software of the target device:
sending a reconstruction request message to a target management and control agent so that the target management and control agent sends a reconstruction request with target equipment based on the reconstruction request message;
after a reconfiguration simple response message sent by the target management and control agent is acquired, data communication is established with the target device, wherein the reconfiguration simple response message is determined by the reconfiguration response sent by the target management and control agent after the reconfiguration preparation of the target device is completed.
In this example, the following reconstructed packet flow is further included, and the Reconstruct reconstructed packet PDU format may include:
Figure BDA0003204805260000131
the descriptions of each field of Reconstruct reconstruction message PDU are as follows:
the second message type: 1 byte;
agent identification: a unique representation representing the agent;
software OID: for identifying which software is updated;
program version: 4 bits, the version of the program currently to be updated;
the transmission mode is as follows: and 4 bits for indicating which application layer data block transmission protocol is adopted for program updating.
The Reconstruct-simpleprly reconstruction-simple response message PDU format may include:
Figure BDA0003204805260000132
the fields of Reconstruct-SimpleRely reconstruction-simple response message PDU are described as follows:
the second message type: 1 byte;
agent identification: a unique identification representing the agent;
an acknowledgement bit: 1 bit, where 1 represents ready to receive; 0 means not ready to receive. As shown in fig. 7, the message reconfiguration process may include:
firstly, a data acquisition and distribution system sends a reconstruction request message to a management and control agent, and the sent message is a Reconstruct reconstruction message PDU.
After receiving the message, the management and control agent performs protocol adaptation on the message, and then sends a private reconfiguration request to a housekeeping computer or a station controller (network control).
After receiving the private reconstruction request, the housekeeping computer or the station control (network control) performs reconstruction preparation, and then sends a private protocol reconstruction response to the control agent.
And after receiving the private protocol reconfiguration response, the management and control agent performs protocol adaptation on the private protocol reconfiguration response and then sends a reconfiguration-simple response message to the data acquisition and distribution system. The message sent at this time is a Reconstruct-SimpleRefly reconstruction-simple response message PDU.
In some embodiments, the method further includes the following active reporting procedure:
acquiring an active report message sent by a target management and control agent, wherein the active report message is sent by the target management and control agent after receiving a device parameter or an alarm message sent by target equipment;
and sending an alarm simple response message to the target management and control agent.
In some embodiments, in a case that the active report message includes an alarm report message, a PDU of the alarm report message includes an alarm information item configured to indicate status information of an alarm.
Further explaining the reporting process in this example, the format of the alarmnform alarm report PDU may include:
Figure BDA0003204805260000141
the description of each field of the AlarmInform alarm report message PDU is as follows:
the second message type: 1 byte;
source agent ID: a unique identifier representing an alarm agent;
alarm generation time: 16 bytes, time of alarm generated from equipment;
and (4) alarm level: 2 bits, three-level identification is adopted, 0x0 represents grade III (general), 0x1 represents grade II (serious), 0x3 represents grade I (especially serious), and other bits are reserved;
alarm type: 1 bit, 0 represents a performance alarm, and 1 represents a fault alarm;
the reason of the alarm is as follows: lengthening, namely, representing an alarm;
an alarm source: lengthening and alarming the source OID.
The alarmlnform-simpleprly alarm reporting-simple response message PDU format may include:
Figure BDA0003204805260000151
the description of each field of the report message PDU of the AlarmInform-SimpleRely alarm simple response is as follows:
the second message type: 1 byte;
source agent ID: representing a unique identification of the alert agent.
An acknowledgement bit: bit 1, fill 1 by default, acknowledge reply.
The active report message is used for the management and control agent to locally cache the device information and the alarm information reported by the devices such as the satellite computer, the station controller, the network controller and the like, and report the information according to a preset report period. As shown in fig. 8, may include:
firstly, a housekeeping computer or a station controller (network controller) sends device parameters or alarm messages to a control agent. At this time, the sent message is a ParaInform equipment parameter reporting message PDU or an AlarmInform alarm reporting message PDU.
After receiving the message, the management and control agent system performs protocol adaptation and caching on the message, and then informs the data acquisition and distribution system of the message actively reported.
And after receiving the report message, the data acquisition and distribution system sends an active report simple response message to the management and control agent. The message sent at this time is ParaInform-SimpleRely parameter reporting-simple response message PDU or AlarmInform-SimpleRely alarm reporting-simple response message PDU.
The embodiment of the disclosure also provides an implementation case of a heaven-earth integrated network communication management protocol:
inquiring an interactive flow example:
s11, the data acquisition and distribution system sends a query message Inquire { MessageType ═ 1, agentID ═ 1, infoID ═ 1, sign ═ 1, variable bindings ═ 1.1.0.1:0:1.1.0.2: 1' } to the management and control agent center, and in order to ensure the reliability and safety in data message transmission, the message is encrypted, and the encrypted data is as follows: [ -40,109, -31,52, -23,8,36, -69,36,36, -65,53,57, -33, -93, -94, -110,44,97,109, -54,92,114,25.66, -1, -39, -82, -9, -49,71, -100, -37,124].
S12, the management and control agent center continuously monitors whether a message is received, and after receiving the message, it first decodes and integrity checks the message, and after confirming that the data is not lost, obtains a query message Inquire { MessageType ═ 1, agentID ═ 1, info ═ 1, sign ═ 1, variable bindings ═ 1.1.0.1:0:1.1.0.2: 1' }; and (3) knowing that the query is required to be carried out according to the MessageType which is 1, starting the query according to the requirement of the query message, sending a simple response message to the data acquisition and distribution center, informing the data acquisition and distribution center of receiving the query message, and starting the query. The sending of the encrypted message data is: [ -98,14, -12, -54, -26, -23,47, -5, -29, -95, -33,22,11,34,48.-103,80,8, -38, -25, -29,77, -58, -74].
S13, monitoring data by the data acquisition and distribution system: [ -98,14, -12, -54, -26, -23,47, -5, -29, -95, -33,22,11,34,48, -103,80,8, -38, -25, -29,77, -58, -74], which is decoded and integrity checked to obtain a message: inquire simpleprly [ message id 1, message type 2, confirm 1 ].
S14, the management and control agent inquires data and sends a detailed response message to the data acquisition and distribution system: the query data message PDU is serialized according to Inquire { MessageType ═ 3, agentID ═ 1, infoID ═ 1, sign ═ 1, variable bindings ═ 1.1.3.1.0:5.1.1.3.2.0:2.1.1.3.3.0:0.1.1.3.4.0:0.1.1.3.5.0:0.1.1.3.6.0:0.1.1.3.7.0:0,1.1.3.8.0:0,1.1.3.9.0:0, 1.1.3' }, and the serialized data is as follows: [8,3,16,1,24,1,32,1,42, -122,1,49,46,49,46,51,46,49,46,48,58,53,44,49,46,49,46,51,46,50,46,48,58,50,44,49,46,49], encrypting the protocol data packet PDU portion to ensure reliable transmission, the encrypted data being: [ -98,14, -12, -54, -26, -23,47, -5,69,97, -32, -67,11,104, -70,108, -25, -25,17,44,73,103, -40,6, -40, -79,116, -24, -5, -57,87, -3, -37].
S15, the management and control agent monitors the message: [ -98,14, -12, -54, -26, -23,47, -5,69,97, -32, -67,11,104, -70,108, -25, -25,17,44,73,103, -40,6, -40, -79,116, -24, -5, -57,87, -3, -37] which are decoded and integrity checked, and after determining that there are no errors, a query detail response message is obtained: inquire { MessageType ═ 3, agentID ═ 1, infoID ═ 1, sign ═ 1, variable bindings ═ 1.1.3.1.0:5.1.1.3.2.0:2.1.1.3.3.0:0.1.1.3.4.0:0.1.1.3.5.0:0.1.1.3.6.0:0.1.1.3.7.0:0,1.1.3.8.0:0,1.1.3.9.0:0, 1.1.3' }. And finishing the data query interaction.
Parameter configuration interaction flow example:
s21, the data acquisition and distribution system sends a parameter configuration message to the management and control agent: ParaConf { MessageType ═ 4, agentd ═ 1, messageID ═ 1, variable bindings { "originalSpeed": 0, "moveSpeed": 1, "paraList": 2 }. For reliable transmission of the message, the data after encrypting the protocol data message PDU part is: [28, -50, -62,92, -2,118, -88,83, -103, -86,115,102, -120, -29, -67, -108,35,97, -19, -48,88].
S22, the management and control agent continuously monitors the message, and receives the packaged message data: [28, -50, -62,92, -2,118, -88,83, -103, -86,115,102, -120, -29, -67, -108,35,97, -19, -48,88], decoding and integrity checking the message, and obtaining the parameter configuration message after confirming the message is error-free: ParaConf { MessageType ═ 4, agentd ═ 1, messageID ═ 1, variable bindings { "originalSpeed": 0, "moveSpeed": 1, "paraList": 2 }.
S23, the management and control agent starts parameter configuration according to the message requirement, and the configuration is completed to return the message to the data acquisition and distribution system: paraconf detailreply { messageId ═ 1, messageType ═ 5, errory variablebindings ═ 1.1.3.1.0:5,1.1.3.2.0:2,1.1.3.3.0:0,1.1.3.4.0:0, 1.1.3.5' }. Serializing the parameter configuration detailed response data message PDU, wherein the serialized data is as follows: [8,1,16,5,26, -122,1,49,46,49,46,51,46,49,46,48,58,53,44,49,46]. The data after encrypting the protocol data message PDU part for reliable transmission is: [ -127, -36,60, -99, -67, -107,89, -100, -62,6, -56,50, -103,107,91,45, -72,60,4, -23, -79, -86, -76,67, -20,23,100].
S24, the data acquisition and distribution system receives the encrypted message [ -127, -36,60, -99, -67, -107,89, -100, -62,6, -56,50, -103,107,91,45, -72,60,4, -23, -79, -86, -76,67, -20,23,100 ]. Decoding and integrity checking are carried out on the message, and if the message is confirmed to be correct, a parameter configuration detailed response message sent by the management and control agent is received: paraconf detailreply { messageId ═ 1, messageType ═ 5, errory variablebindings ═ 1.1.3.1.0:5,1.1.3.2.0:2,1.1.3.3.0:0,1.1.3.4.0:0, 1.1.3.5' }. And completing parameter configuration interaction.
Task configuration interaction flow example:
s31, the data acquisition and distribution system sends a task configuration message to the management and control agent, and the packaged message is as follows: MissionConf { messageType ═ 6, agentID ═ 1, messageId ═ 1, startTime ═ 1570673582487, informacmycecle ═ 1, sign ═ 1, variable bindings ═ 1.1.3.1.0:5,1.1.3.2.0:2,1.1.3.3.0:0,1.1.3.4.0:0, 1.1.3.5'. The data after encrypting the PDU part of the protocol data message is as follows: [ -29,81, -107, -42, -121, -63, -91, -115,119, -58,2, -78, -117, -54,74,12, -53,74,12, -53,24,102, -94,108].
S32, the management and control agent receives the task configuration message, decodes the task configuration message, and confirms the received message after integrity check:
MissionConf { messageType ═ 6, agentID ═ 1, messageId ═ 1, startTime ═ 1570673582487, informacmycecle ═ 1, sign ═ 1, variable bindings ═ 1.1.3.1.0:5,1.1.3.2.0:2,1.1.3.3.0:0,1.1.3.4.0:0, 1.1.3.5'. And configuring according to command requirements.
S33, after the management and control agent is configured, sending a detailed response data message to the data acquisition and distribution system: misson conf detail reply { messageId ═ 1, messageType ═ 7, errorVariableBindings ═ 1.1.3.1.0:5,1.1.3.2.0:2,1.1.3.3.0:0,1.1.3.4.0:0, 1.1.3.5' }. Serializing the detailed task configuration response data message PDU, wherein the serialized data is as follows: [8,1,16,7,26, -122,1,49,46,49,46,51,46,49,46,48,58,53,44,49,44]. The data after partially encrypting the protocol data message PDU is as follows: [117,46,0,71, -90,95, -91,63,42,2,34, -15, -89, -27,26, -76, -25, -77, -76, -30, -101, -51,95, -98, -103,51,43,41].
S34, the data acquisition and distribution system receives a task configuration response message sent by the management and control agent: [117,46,0,71, -90,95, -91,63,42,2,34, -15, -89, -27,26, -76, -25, -77, -76, -30, -101, -51,95, -98, -103,51,43,41]. Decoding and integrity checking are carried out on the task configuration message, no error is confirmed, and a task configuration detailed response message is received: misson conf detail reply { messageId ═ 1, messageType ═ 7, errorVariableBindings ═ 1.1.3.1.0:5,1.1.3.2.0:2,1.1.3.3.0:0,1.1.3.4.0:0, 1.1.3.5' }. And completing the task configuration interactive process.
An example of an interactive process of an alarm report message:
s41, the management and control agent actively reports alarms to the data acquisition and distribution system at regular intervals, and the sending messages are as follows: alarmlnform { messageType ═ 8, agentId ═ 1, alarmTime ═ 11, alarmlgrade ═ 1, alarmType ═ 0, alarmReason ═ 3, alarmSource ═ alarm }. The data after encrypting the PDU part of the protocol data message is as follows: [25, -12, -51,22,7,31, -98, -114, -122,77, -5, -80,105,113,73,14,56,118, -18, -97, -99, -35,96, -36, -107, -46,75,78, -27,93,86, -27, -41, -115,43,4,53,45, -81,78].
S42, the data acquisition and distribution system monitors the message: [25, -12, -51,22,7,31, -98, -114, -122,77, -5, -80,105,113,73,14,56,118, -18, -97, -99, -35,96, -36, -107, -46,75,78, -27,93,86, -27, -41, -115,43,4,53,45, -81,78]. And decoding the message. And after integrity verification, data is confirmed to be correct, and an alarm report message sent by the management and control agent is received. And finishing the alarm reporting interactive process.
Reporting an interactive process example by the equipment parameters:
and S51, the management and control agent actively reports the equipment parameter information to the data acquisition and distribution system at regular intervals, namely low-speed, medium-speed and high-speed equipment parameter reporting. The low speed is taken as an example for description, and the original data is as follows: {1.1.2.4.1.1 ═ 1,1.1.2.4.3.1 ═ 2,1.1.2.4.2.1 ═ Node1, speed ═ 0 }. Serializing the device parameter reporting message PDU, wherein the serialized data is as follows: [8,10,16,1,26,58,123,49,46,49,46,50,46,52,46,49,46,49,61,49,44,32,49,46,49,46,50,46,52,46,51,46,49,61,50,44,32,49,46,49,46,50,46,52,46,50,46,49,61,78,111,100,101,49,44,32,115,112,101,101,100,61,48,125]. The data after encrypting the PDU part of the protocol data message is as follows: [ -123,89,85,100,78,0,105, -114, -39, -106,25, -127,29, -60, -98, -46,47, -52,56,44, -127, -30,68,125, -123,93, -90, -101, -13, -97, -96, -28, -115,33,19,120,97, -19,19, -49, -70,114, -21, -78,70, -93, -10,60,113,96, -110, -78, -66, -87, -71, -37,50, -19,38,12, -84,105, -51,126, -28,9,112, -103,46,89, -48, -74,88,17, -52,85, -92, -38,62, -71].
S52, the data acquisition and distribution center receives the device parameter report message: [ -123,89,85,100,78,0,105, -114, -39, -106,25, -127,29, -60, -98, -46,47, -52,56,44, -127, -30,68,125, -123,93, -90, -101, -13, -97, -96, -28, -115,33,19,120,97, -19,19, -49, -70,114, -21, -78,70, -93, -10,60,113,96, -110, -78, -66, -87, -71, -37,50, -19,38,12, -84,105, -51,126, -28,9,112, -103,46,89, -48, -74,88,17, -52,85, -92, -38,62, -71], decoding and integrity checking are carried out, data are confirmed not to be lost, and the interactive process is completed when the equipment parameters report.
The heaven-earth integrated communication protocol with the preset format is simplified based on the SNMP, and efficient and accurate communication between the heaven base and the foundation is realized through the improved design of each message. The protocol header of the system mainly comprises space-based management and control and foundation management and control, ground network communication is used as a support, space-based network communication is used as an expansion, a unified framework, a unified system and a unified standard are adopted between the space-based management and control and the foundation management and control, seamless coverage of wide-area networking is achieved, and the system has new-generation network communication with safety guarantee. The invention aims to realize the expected aims of high heaven-earth integrated communication expansibility, quick response delay, safety and credibility.
An embodiment of the present invention further provides a data acquisition and distribution system, including a processor configured to:
sending a first message to a target management and control agent, wherein the first message is determined by corresponding configuration according to user requirements and by using a protocol header in a preset format;
and receiving a simple response message corresponding to the user requirement sent by the target management and control agent, and/or receiving a detailed response message corresponding to the user requirement sent by the target management and control agent.
The embodiment of the invention also provides a heaven and earth integrated network communication management protocol, which comprises the first message.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the heaven and earth integrated network communication management protocol according to the embodiments of the present disclosure are implemented.
According to the embodiment of the invention, the first message is used for carrying out corresponding configuration determination according to the requirement of a user by utilizing the protocol header in the preset format, and the corresponding response message is received and can also be realized according to the protocol in the preset format, so that the adoption of a unified architecture, a unified system and a unified standard between space-based management and control and foundation management and control is realized, and the seamless coverage of wide-area networking is realized.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims (10)

1. A heaven and earth integrated network communication management method is characterized by comprising the following steps:
sending a first message to a target management and control agent, wherein the first message is determined by corresponding configuration according to user requirements and by using a protocol header in a preset format;
and receiving a simple response message corresponding to the user requirement sent by the target management and control agent, and/or receiving a detailed response message corresponding to the user requirement sent by the target management and control agent.
2. The method for integrated network communication management of heaven and earth of claim 1, wherein the protocol header of the preset format comprises a plurality of units, each unit corresponds to a field, and the field comprises: a first message type, version number, IP address, encryption parameter, time identifier, message sequence number, message length, authentication parameter, and Protocol Data Unit (PDU);
the first message is obtained by configuring the PDU according to the requirement of a user.
3. The heaven-earth integrated network communication management method according to claim 2, wherein in case that the first message is an inquiry message, a parameter configuration message or a task configuration message, the PDU of the first message comprises: a second message type, a proxy representation, and a message ID.
4. The heaven-earth-integrated network communication management method according to claim 3, wherein in case the first message is a query message, the first message and the corresponding PDU of the detailed response message further include a key-value-pair parameter item configured to indicate the queried parameter;
in the case that the first message is a task configuration message, the PDU of the first message and the corresponding detailed response message further includes a device parameter item configured to indicate a status of the configured task;
in the case that the first message is a parameter configuration message, the PDU of the first message and the corresponding detailed response message further includes a configuration information item configured to indicate the configured device status.
5. The integrated network communication management method of claim 2, further comprising the following authentication procedures of network entry/network exit:
acquiring a network access authentication message sent by a target management and control agent;
carrying out protocol adaptation based on the network access authentication message, and sending the adapted network access authentication message to a security management system;
and after receiving the network access authentication response message of the security management system, sending a network access authentication detailed response to the target management and control agent.
6. The integrated network communication management method of claim 2, further comprising the following message reconfiguration process to update the software of the target device:
sending a reconstruction request message to a target management and control agent so that the target management and control agent sends a reconstruction request with target equipment based on the reconstruction request message;
after a reconfiguration simple response message sent by the target management and control agent is acquired, data communication is established with the target device, wherein the reconfiguration simple response message is determined by the reconfiguration response sent by the target management and control agent after the reconfiguration preparation of the target device is completed.
7. The integrated network communication management method of claim 2, further comprising the following active reporting procedure:
acquiring an active report message sent by a target management and control agent, wherein the active report message is sent by the target management and control agent after receiving a device parameter or an alarm message sent by target equipment;
sending an alarm simple response message to the target management and control agent;
and under the condition that the active report message comprises an alarm report message, the PDU of the alarm report message comprises an alarm information item, and the alarm information item is configured to indicate alarm state information.
8. A heaven-earth integrated network communication management protocol comprising the first message of any one of claims 1 to 7.
9. A data collection and distribution system, comprising a processor configured to:
sending a first message to a target management and control agent, wherein the first message is determined by corresponding configuration according to user requirements and by using a protocol header in a preset format;
and receiving a simple response message corresponding to the user requirement sent by the target management and control agent, and/or receiving a detailed response message corresponding to the user requirement sent by the target management and control agent.
10. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, carries out the steps of the heaven-earth-integrated network communication management method according to any one of claims 1 to 7.
CN202110914138.2A 2021-08-10 2021-08-10 Heaven and earth integrated network communication management protocol and method Pending CN113794582A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110914138.2A CN113794582A (en) 2021-08-10 2021-08-10 Heaven and earth integrated network communication management protocol and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110914138.2A CN113794582A (en) 2021-08-10 2021-08-10 Heaven and earth integrated network communication management protocol and method

Publications (1)

Publication Number Publication Date
CN113794582A true CN113794582A (en) 2021-12-14

Family

ID=78875819

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110914138.2A Pending CN113794582A (en) 2021-08-10 2021-08-10 Heaven and earth integrated network communication management protocol and method

Country Status (1)

Country Link
CN (1) CN113794582A (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114785843A (en) * 2022-03-22 2022-07-22 成都爱瑞无线科技有限公司 Data communication method, device, communication system and storage medium
CN115913809A (en) * 2022-09-26 2023-04-04 重庆长安汽车股份有限公司 Data distribution communication method, system, computer device and storage medium
CN117811644A (en) * 2024-02-29 2024-04-02 中国电子科技集团公司第五十四研究所 Satellite integrated electronic device with definable protocol reconfigurable function
WO2024098948A1 (en) * 2022-11-09 2024-05-16 华为技术有限公司 Communication methods, storage medium and program product
CN114785843B (en) * 2022-03-22 2024-05-31 成都爱瑞无线科技有限公司 Data communication method, device, communication system and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110380970A (en) * 2019-07-22 2019-10-25 北京邮电大学 A kind of self-adapting data message forwarding method and device suitable for heterogeneous network
CN111770155A (en) * 2020-01-03 2020-10-13 中国人民解放军63920部队 Data processing method, device, storage medium and processor
CN112532712A (en) * 2020-11-24 2021-03-19 青岛海尔科技有限公司 Protocol transmission method and device, storage medium, and electronic device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110380970A (en) * 2019-07-22 2019-10-25 北京邮电大学 A kind of self-adapting data message forwarding method and device suitable for heterogeneous network
CN111770155A (en) * 2020-01-03 2020-10-13 中国人民解放军63920部队 Data processing method, device, storage medium and processor
CN112532712A (en) * 2020-11-24 2021-03-19 青岛海尔科技有限公司 Protocol transmission method and device, storage medium, and electronic device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
闻铭;张军;朱衍波;: "地空通信应用层报文传输协议的设计与实现", no. 15 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114785843A (en) * 2022-03-22 2022-07-22 成都爱瑞无线科技有限公司 Data communication method, device, communication system and storage medium
CN114785843B (en) * 2022-03-22 2024-05-31 成都爱瑞无线科技有限公司 Data communication method, device, communication system and storage medium
CN115913809A (en) * 2022-09-26 2023-04-04 重庆长安汽车股份有限公司 Data distribution communication method, system, computer device and storage medium
CN115913809B (en) * 2022-09-26 2024-05-03 重庆长安汽车股份有限公司 Data distribution communication method, system, computer device and storage medium
WO2024098948A1 (en) * 2022-11-09 2024-05-16 华为技术有限公司 Communication methods, storage medium and program product
CN117811644A (en) * 2024-02-29 2024-04-02 中国电子科技集团公司第五十四研究所 Satellite integrated electronic device with definable protocol reconfigurable function
CN117811644B (en) * 2024-02-29 2024-05-03 中国电子科技集团公司第五十四研究所 Satellite integrated electronic device with definable protocol reconfigurable function

Similar Documents

Publication Publication Date Title
CN113794582A (en) Heaven and earth integrated network communication management protocol and method
JP4759382B2 (en) COMMUNICATION DEVICE, COMMUNICATION METHOD, COMMUNICATION PROGRAM, AND RECORDING MEDIUM
US8180876B2 (en) Device manager and device management program
WO2019023620A1 (en) Secure short message service over non-access stratum
US10554755B2 (en) Aircraft data interface function implementation using aircraft condition monitoring function and data gathering application architecture
EP2590382B1 (en) Method and apparatus for tracking device management data changes
CN108848145B (en) Method and system for accessing near-end network management of equipment through WEB agent and far-end network management
US20110004654A1 (en) Device management session trigger
CN110912977A (en) Configuration file updating method, device, equipment and storage medium
US20130346610A1 (en) Device Management Method and Apparatus
CN101106806B (en) Method, system and mobile terminal for wireless network to capture mobile IP style of mobile terminal
WO2021057802A1 (en) Das system management method and device, electronic device, and storage medium
CN113746716A (en) Multi-connection access point
US9456340B2 (en) Unsolicited broadcast packet transmission through close-by communication protocol
EP2930962B1 (en) Encryption/decryption method, system and device
WO2012139463A1 (en) Terminal device initialization method and device
KR101380535B1 (en) Management of a communication device via a telecommunications network
CN109150661A (en) A kind of method for discovering equipment and device
JP2019061650A (en) Device management system, device management apparatus, relay management apparatus, device management method, device management program, and relay management program
WO2020092484A1 (en) Performance measurements related to pdu session and n4 session management
CN109417558B (en) Method, device and system for managing network slices
Dietz et al. Definitions of managed objects for IP flow information export
KR20090046054A (en) Apparatus and method for transferring protocol
Lindholm-Ventola et al. Coap-snmp interworking iot scenarios
CN113169965B (en) Resource allocation method, 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