CN111478791B - A data management method and device - Google Patents

Abstract

A data management method and device provided by the embodiments of the present invention, through the mapping relationship between the sub-node identifier corresponding to the data existing in the target device and the target identifier input by the user, so that the user can define the target according to the user. The identifier manages the data set corresponding to the parent node identifier in the target device, which improves the readability of the child node identifier corresponding to the data and facilitates user identification.

Description

A data management method and device

technical field

The present invention relates to the field of information technology, and in particular, to a data management method and device.

Background technique

SNMP (Simple Network Management Protocol, Simple Network Management Protocol) is a common network device management protocol, through which the OID (Object IDentifier, object identifier) corresponding to the contained information data can be obtained from the network device, so that it can be used based on SNMP. The OID manages the information data in the network device.

However, since the OID contains both numeric and alphanumeric forms, and the numeric value is a positive integer greater than 0 and less than 16000 000, the alphanumeric value is a variable length of not less than 1 character and not more than 100 characters string. It can be seen that this naming rule is relatively complicated, which makes the OID less readable, which makes it difficult for users to identify the OID corresponding to the information data they need when using the OID to manage the information data of the network device.

SUMMARY OF THE INVENTION

In view of the above problems, embodiments of the present invention are proposed to provide a data management method and apparatus that overcome the above problems or at least partially solve the above problems.

In order to solve the above problems, a first aspect of the embodiments of the present invention discloses a data management method, and the method includes:

Obtain the child node identifier corresponding to the data stored in the target device;

Identify the parent node identifier corresponding to the child node identifier;

Replace the parent node identifier in the preset first mapping relationship with the corresponding child node identifier to obtain a second mapping relationship, where the preset first mapping relationship is the parent node identifier and the preset Mapping relationship between identifiers;

receiving a target identifier input for the preset identifier;

Replace the preset identification in the second mapping relationship with the target identification, and obtain a third mapping relationship between the target identification and the child node identification, so as to manage the target according to the third mapping relationship The data set corresponding to the parent node identifier stored in the device.

Optionally, after the step of replacing the preset identifier in the second mapping relationship with the target identifier to obtain a third mapping relationship between the target identifier and the child node identifier, further comprising: :

receiving a first input, where the first input at least includes: an acquisition instruction and a target identifier;

Determine at least one child node identifier corresponding to the target identifier according to the third mapping relationship;

Acquire data corresponding to the at least one child node identifier from the target device according to the acquisition instruction.

Optionally, after the step of replacing the preset identifier in the second mapping relationship with the target identifier to obtain a third mapping relationship between the target identifier and the child node identifier, further comprising: :

receiving a second input, where the second input at least includes: a modification instruction, a target identifier, and a child node index value;

Determine at least one child node identifier corresponding to the target identifier according to the third mapping relationship;

Identifying the parent node identifier corresponding to the at least one child node identifier;

Generate a target child node identifier according to the parent node identifier and the child node index value;

The target device is controlled to modify the data corresponding to the target child node identifier according to the modification instruction.

Optionally, the step of obtaining the identifier of the child node corresponding to the data stored in the target device includes:

Use the query method class in the private simple network management protocol to obtain the parent node identifier corresponding to the data set stored in the target device, and the child node index value corresponding to the parent node identifier;

The parent node identifier and the child node index value are combined to obtain the child node identifier corresponding to each data in the data set.

Optionally, the preset first mapping relationship is obtained through the following steps:

Obtain the parent node identifier corresponding to the data set in the target device;

Generate a preset identifier corresponding to the parent node identifier according to a preset rule;

A mapping relationship between the parent node identifier and the preset identifier is established to obtain a preset first mapping relationship.

Optionally, the device management system adopts the Internet of View protocol, the target device adopts the Internet protocol, the device management system and the target device are communicated and connected through a protocol conversion server, and the obtained data stored in the target device corresponds to The steps for identifying child nodes of , including:

The child node identifier corresponding to the data stored in the target device is acquired through the transparent transmission module in the protocol conversion server.

A second aspect of the embodiments of the present invention discloses a data management apparatus, the apparatus is applied to a device management system, and the apparatus includes:

The first acquisition module is used to acquire the child node identifier corresponding to the data stored in the target device;

a first identification module for identifying the parent node identification corresponding to the child node identification;

The first replacement module is configured to replace the identifier of the parent node in the preset first mapping relationship with the corresponding identifier of the child node to obtain a second mapping relationship, and the preset first mapping relationship is the Describe the mapping relationship between the parent node identifier and the preset identifier;

a first receiving module, configured to receive a target identifier input for the preset identifier;

A second replacement module, configured to replace the preset identifier in the second mapping relationship with the target identifier, and obtain a third mapping relationship between the target identifier and the child node identifier, so as to The three-mapping relationship manages the data set corresponding to the parent node identifier stored in the target device.

Optionally, the device further includes:

A second receiving module, configured to receive a first input, where the first input at least includes: an acquisition instruction and a target identifier;

a first determining module, configured to determine at least one sub-node identifier corresponding to the target identifier according to the third mapping relationship;

A second acquiring module, configured to acquire data corresponding to the identifier of the at least one child node from the target device according to the acquiring instruction.

Optionally, the device further includes:

A third receiving module, configured to receive a second input, where the second input at least includes: a modification instruction, a target identifier, and a child node index value;

a second determining module, configured to determine at least one sub-node identifier corresponding to the target identifier according to the third mapping relationship;

The second identification module is used to identify the parent node identification corresponding to the at least one child node identification;

a generating module, configured to generate a target child node identifier according to the parent node identifier and the child node index value;

A modification module, configured to control the target device to modify the data corresponding to the target child node identifier according to the modification instruction.

Optionally, the obtaining module includes:

The first obtaining submodule is used to obtain the parent node identifier corresponding to the data set stored in the target device, and the child node index value corresponding to the parent node identifier by using the query method class in the private simple network management protocol;

The assembly submodule is used for combining the parent node identifier and the child node index value to obtain the child node identifier corresponding to each data in the data set.

Optionally, the preset first mapping relationship is obtained by the following preprocessing module, and the preprocessing module is used for:

Obtain the parent node identifier corresponding to the data set in the target device;

Generate a preset identifier corresponding to the parent node identifier according to a preset rule;

A mapping relationship between the parent node identifier and the preset identifier is established to obtain a preset first mapping relationship.

Optionally, the device management system adopts the Internet of View protocol, the target device adopts the Internet protocol, the device management system and the target device are communicated and connected through a protocol conversion server, and the first acquisition module includes:

The second obtaining sub-module is configured to obtain the child node identifier corresponding to the data stored in the target device through the transparent transmission module in the protocol conversion server.

The embodiments of the present invention include the following advantages:

A data management method and apparatus provided by the embodiments of the present invention, through the mapping relationship between the sub-node identifier corresponding to the data existing in the target device and the target identifier input by the user, so that the user can define the target according to the user. The identifier manages the data set corresponding to the parent node identifier in the target device, which improves the readability of the child node identifier corresponding to the data and facilitates user identification.

Description of drawings

Fig. 1 is the step flow chart of a kind of data management method of the present invention;

Fig. 2 is a kind of schematic flow chart of generating the third mapping relationship according to the present invention;

Fig. 3 is the step flow chart of another kind of data management method of the present invention;

Fig. 4 is the step flow chart of a kind of data acquisition method of the present invention;

Fig. 5 is the step flow chart of a kind of data modification method of the present invention;

Fig. 6 is a kind of step flow chart of generating the first mapping relationship of the present invention;

Fig. 7 is a structural block diagram of a data management device of the present invention;

FIG. 8 is a schematic diagram of networking of a video network according to the present invention;

9 is a schematic diagram of the hardware structure of a node server of the present invention;

10 is a schematic diagram of the hardware structure of an access switch of the present invention;

FIG. 11 is a schematic diagram of the hardware structure of an Ethernet protocol conversion gateway of the present invention.

Detailed ways

In order to make the above objects, features and advantages of the present invention more clearly understood, the present invention will be described in further detail below with reference to the accompanying drawings and specific embodiments.

Referring to FIG. 1, a data management method of the present invention is shown, and the method includes:

Step 101: Obtain the child node identifier corresponding to the data stored in the target device.

In this embodiment of the present invention, the target device refers to an electronic device with a data storage function in a network environment. The child node identifiers refer to OIDs (Object IDentifiers, object identifiers) corresponding to the data stored in the network device, and are used to locate and manage the data stored in the network device. SNMP is a standard protocol specially designed to manage network devices (servers, workstations, routers, switches and HUBS, etc.), usually network devices will generate MIB (Management Information Base, Management Information Base) locally for storage control and Status information and other data, and MIB is a tree database based on the SNMP protocol. The object data managed by the MIB is the node of the tree, and each node has a corresponding child node identifier.

Usually, the user can obtain through the device management system and store the sub-node identifier corresponding to the network device, so as to perform operations such as adding, deleting, and modifying the data in the network device. However, because the naming rules of the sub-node identification are complex and the readability is poor, it is difficult for the user to determine the sub-node identification corresponding to the information required by the user through identification. Therefore, the sub-node identifier needs to be reassembled to facilitate user identification.

Before reassembly, the child node identifier corresponding to each data contained in the MIB in the target device can be obtained through the private SNMP protocol. The private SNMP protocol will obtain the index value contained in the data set contained in the target device corresponding to each parent node identification, so as to assemble the parent node identification and the corresponding index value, and obtain the child corresponding to each data in the data set corresponding to the node identification. Node ID.

Step 102: Identify the parent node identifier corresponding to the child node identifier.

In the embodiment of the present invention, since the child node identifiers are generated in a tree structure, the parent node identifier corresponding to each child node identifier can be obtained by deleting the last object in the child node identifier.

Step 103: Replace the parent node identifier in the preset first mapping relationship with the corresponding child node identifier to obtain a second mapping relationship, where the preset first mapping relationship is the parent node identifier Mapping relationship with preset identifiers.

In this embodiment of the present invention, the preset first mapping relationship is generated when the device management system establishes a communication connection with the target device. By replacing the parent node identifier in the first mapping relationship with its corresponding child node identifier, a mapping relationship between the preset identifier and the child node identifier is established, and the parent node identifier can be determined through the preset identifier All child node identifiers in .

Step 104: Receive a target identifier input for the preset identifier.

In the embodiment of the present invention, in the design and development process, the user usually needs to set the identification name for each data according to his own actual requirements, so as to adapt to different development and design requirements. Therefore, the user can input the target identification of each preset identification according to his own needs by identifying the preset identification.

Step 105, replace the preset identification in the second mapping relationship with the target identification, and obtain a third mapping relationship between the target identification and the child node identification, to manage according to the third mapping relationship The data set corresponding to the parent node identifier stored in the target device.

In this embodiment of the present invention, the preset identifier in the previously generated second mapping relationship is replaced with the target identifier input by the user, so as to establish a third relationship between the target identifier and all child node identifiers corresponding to the parent node identifier. Mapping relations. In this way, the user can obtain the parent node identifier corresponding to the data set where the data he needs is located through the target identifier set by himself. Since the target identifier is set by the user and is easier to be identified by the user than the child node identifier, the target identifier can be directly used to input control instructions for the data in the target device to manage the data in the target device.

Specifically, referring to FIG. 2, a schematic flowchart of generating a third mapping relationship is shown, where Oid represents the parent node identifier, index is the child node index value, and Oid+index is the child node identifier. Specifically, first obtain the child node identifier in the form of Oid+index=index from the target device, for example, 1.3.6.1.4.1.54120.1.3.1.7.1.1=1; then the Oid in the first mapping relationship stored locally Replace with the corresponding Oid+index, so as to obtain the second mapping relationship between Oid+index and the preset identifier, for example: 1.3.6.1.4.1.54120.1.3.1.7.1.1=preset identifier; then use the received The obtained target identifier for the preset identifier replaces the preset identifier in the second mapping relationship to obtain a third mapping relationship between the target identifier and the preset identifier, for example: 1.3.6.1.4.1.54120.1.3.1.7.1.1 = target ID.

Optionally, the device management system adopts the Internet of View protocol, the target device adopts the Internet protocol, and the device management system and the target device are communicated and connected through a protocol conversion server, and the step 101 may include: through the The transparent transmission module in the protocol conversion server obtains the identifier of the child node corresponding to the data stored in the target device.

In the embodiment of the present invention, when the device management system is deployed in the Internet of View environment, due to the limitation of the network protocol, it cannot directly communicate with the target device deployed in the Internet, and therefore cannot directly obtain the information in the target device. Child node ID. Therefore, in the embodiment of the present invention, a protocol conversion server for performing protocol conversion between the Internet of View protocol and the Internet protocol is provided between the device management system and the target device. The protocol conversion server is provided with an Internet interface and a video networking interface. The target device sends the child node identification to the Internet interface of the protocol conversion server through the transparent transmission module. The protocol is converted, and then the sub-node identifier after the protocol conversion is sent to the device management system from the video networking interface through the transparent transmission module. Thus, the communication connection between the device management system in the Internet of View environment and the electronic device in the Internet environment is realized.

In a data management method provided by an embodiment of the present invention, through the mapping relationship between the sub-node identifier corresponding to the data existing in the target device and the target identifier input by the user, so that the user can define the target identifier according to the user. The data set corresponding to the parent node identification in the target device is managed, which improves the readability of the child node identification corresponding to the data and facilitates user identification.

Referring to FIG. 3, another data management method of the present invention is shown, and the method includes:

Step 201 , use the query method class in the private simple network management protocol to obtain the parent node identifier corresponding to the data set stored in the target device, and the child node index value corresponding to the parent node identifier.

In the embodiment of the present invention, the private simple network management protocol refers to a private SNMP protocol, through which the parent node identifier of the data set stored in the target device and the included index value are acquired. For example, the parent node is identified as 1.3.6.1.4.1.54120.1.3.1.7.1.3, and the index values it contains are 1, 2, 3, and so on.

Step 202: Combine the parent node identifier and the child node index value to obtain the child node identifier corresponding to each data in the data set.

In the embodiment of the present invention, the child node identifier is obtained by adding the child node index value as an object to the corresponding parent node identifier, and a mapping relationship between the child node identifier and the child node index value is established. That is, in the form of oid+index=inedx, oid refers to the parent node ID, and index is the child node index value. For example, the parent node ID 1.3.6.1.4.1.54120.1.3.1.7.1.3 is assembled with its corresponding child node index value 1, gives 1.3.6.1.4.1.54120.1.3.1.7.1.3.1=1.

Step 203: Identify the parent node identifier corresponding to the child node identifier.

For this step, reference may be made to the detailed description of step 102, which will not be repeated here.

Step 204: Replace the parent node identifier in the preset first mapping relationship with the corresponding child node identifier to obtain a second mapping relationship, where the preset first mapping relationship is the parent node identifier Mapping relationship with preset identifiers.

For this step, reference may be made to the detailed description of step 103, which will not be repeated here.

Step 205: Receive a target identifier input for the preset identifier.

For this step, reference may be made to the detailed description of step 104, which will not be repeated here.

Step 206, replace the preset identification in the second mapping relationship with the target identification, and obtain a third mapping relationship between the target identification and the child node identification, to manage according to the third mapping relationship The data set corresponding to the parent node identifier stored in the target device.

For this step, reference may be made to the detailed description of step 105, which will not be repeated here.

Optionally, referring to FIG. 4, based on another data management method shown in FIG. 3, after step 206, the following steps 207 to 209 are further included:

Step 207: Receive a first input, where the first input at least includes: an acquisition instruction and a target identifier.

In this embodiment of the present invention, when the user determines the required data set through the input target identifier, the user inputs an acquisition instruction for the target identifier.

Step 208: Determine at least one child node identifier corresponding to the target identifier according to the third mapping relationship.

In this embodiment of the present invention, the device management system will acquire all the child node identifiers corresponding to the target device from the third mapping relationship according to the target identifier.

Step 209: Acquire data corresponding to the at least one child node identifier from the target device according to the acquisition instruction.

In the embodiment of the present invention, the target device is sent to the target device through the SNMP protocol, including the child node identifier corresponding to the target identifier, so that the target device returns data corresponding to the child node identifier, that is, the parent node corresponding to the child node identifier. All data in the identified data collection. Therefore, the user can obtain the data in the target device through a more easily identifiable target identifier.

Optionally, referring to FIG. 5, based on another data management method shown in FIG. 3, after step 205, the following steps 210 to 214 are further included:

Step 210: Receive a second input, where the second input at least includes: a modification instruction, a target identifier, and a child node index value.

In this embodiment of the present invention, when a user needs to perform operations such as adding, deleting, or modifying certain data in a target device, the user can set the RowStatus (row status of the data object) corresponding to the target identifier through the SNMP protocol and input a modification instruction, as well as the target identifier and The index value of the child node corresponding to the data to be modified.

Step 211: Determine at least one child node identifier corresponding to the target identifier according to the third mapping relationship.

In this embodiment of the present invention, all child node identifiers corresponding to the target identifier are determined from the third mapping relationship.

Step 212: Identify the parent node identifier corresponding to the at least one child node identifier.

In the embodiment of the present invention, the parent node identifier corresponding to the child node identifier is obtained by removing the last object in the child node identifier from the tree structure of the child node identifier.

Step 213: Generate a target child node identifier according to the parent node identifier and the child node index value.

In the embodiment of the present invention, by assembling the parent node identifier and the child node index value input by the user, the target child node identifier corresponding to the data to be modified by the modification instruction can be obtained.

Step 214: Control the target device to modify the data corresponding to the target child node identifier according to the modification instruction.

In the embodiment of the present invention, a modification instruction carrying the identifier of the child node is sent to the target device, so that the target device modifies the data corresponding to the identifier of the target child node stored in the target device. Thus, the user can modify the data in the target device through the identifiable target identifier.

Optionally, referring to FIG. 6 , the preset first mapping relationship is obtained through the following steps A1 to A3:

Step A1: Obtain the parent node identifier corresponding to the data set in the target device.

Step A2: Generate a preset identifier corresponding to the parent node identifier according to a preset rule.

Step A3: Establish a mapping relationship between the parent node identifier and the preset identifier to obtain a preset first mapping relationship.

In the embodiment of the present invention, the target device sends the parent node identifier corresponding to the data stored by itself to the data management system, and then the device management system generates a preset identifier corresponding to each parent node identifier according to a naming rule identifiable by the user. Set identification. The user-identifiable naming rule may be generated according to the content of the data set corresponding to the parent node identification, so that the user can directly identify the content of the data combination corresponding to the parent node identification through the preset identification. This enables the user to recognize the content of the data corresponding to each parent node when inputting a recognizable target identifier.

In another data management method provided by the embodiment of the present invention, through the mapping relationship between the sub-node identifier corresponding to the data existing in the target device and the target identifier input by the user, the user can define the target identifier according to the user. Acquiring the data set corresponding to the parent node identification in the target device and modifying each data, it is convenient for the user to determine the required child node identification by identifying the target identification, so as to manage the data in the target device and improve the data corresponding to the child node identification. Readability of node IDs.

Referring to FIG. 7 , a data management apparatus of the present invention is shown. The apparatus is applied to a device management system, and the apparatus includes:

The first obtaining module 301 is configured to obtain the child node identifier corresponding to the data stored in the target device.

The first identification module 302 is configured to identify the parent node identification corresponding to the child node identification.

The first replacement module 303 is configured to replace the identifier of the parent node in the preset first mapping relationship with the corresponding identifier of the child node to obtain a second mapping relationship, where the preset first mapping relationship is: The mapping relationship between the parent node identifier and the preset identifier.

The first receiving module 304 is configured to receive the target identifier input for the preset identifier.

The second replacement module 305 is configured to replace the preset identifier in the second mapping relationship with the target identifier, and obtain a third mapping relationship between the target identifier and the child node identifier, so as to The third mapping relationship manages the data set corresponding to the parent node identifier stored in the target device.

Optionally, the device further includes:

The second receiving module 306 is configured to receive a first input, where the first input at least includes: an acquisition instruction and a target identifier.

The first determining module 307 is configured to determine at least one sub-node identifier corresponding to the target identifier according to the third mapping relationship.

The second obtaining module 308 is configured to obtain data corresponding to the at least one child node identifier from the target device according to the obtaining instruction.

Optionally, the device further includes:

The third receiving module 309 is configured to receive a second input, where the second input at least includes: a modification instruction, a target identifier, and a child node index value.

The second determining module 310 is configured to determine at least one child node identifier corresponding to the target identifier according to the third mapping relationship.

The second identification module 311 is configured to identify the parent node identification corresponding to the at least one child node identification.

The generating module 312 is configured to generate a target child node identifier according to the parent node identifier and the child node index value.

The modification module 313 is configured to control the target device to modify the data corresponding to the target child node identifier according to the modification instruction.

Optionally, the obtaining module 301 includes:

The first obtaining sub-module 3011 is used to obtain the parent node identifier corresponding to the data set stored in the target device, and the child node index value corresponding to the parent node identifier by using the query method class in the private simple network management protocol .

The assembly sub-module 3012 is configured to combine the identifier of the parent node and the index value of the child node to obtain the identifier of the child node corresponding to each data in the data set.

Optionally, the preset first mapping relationship is obtained by the following preprocessing module 314, and the preprocessing module 314 is used for:

Obtain the parent node identifier corresponding to the data set in the target device;

Generate a preset identifier corresponding to the parent node identifier according to a preset rule;

A mapping relationship between the parent node identifier and the preset identifier is established to obtain a preset first mapping relationship.

Optionally, the device management system adopts the Internet of View protocol, the target device adopts the Internet protocol, and the device management system and the target device are communicated and connected through a protocol conversion server, and the first acquisition module 301 includes:

The second obtaining sub-module 3013 is configured to obtain the identifier of the child node corresponding to the data stored in the target device through the transparent transmission module in the protocol conversion server.

A data management apparatus provided by an embodiment of the present invention uses the mapping relationship between the sub-node identifier corresponding to the data existing in the target device and the target identifier input by the user, so that the user can define the target identifier according to the user. The data set corresponding to the parent node identification in the target device is managed, which improves the readability of the child node identification corresponding to the data and facilitates user identification.

As for the apparatus embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and reference may be made to the partial description of the method embodiment for related parts.

In order to better illustrate the solution of the present invention, video networking is described in detail below:

Video networking is an important milestone in network development. It is a real-time network that can realize real-time transmission of high-definition video, and push many Internet applications to high-definition video, high-definition face-to-face.

Video networking adopts real-time high-definition video switching technology, which can provide required services on a network platform, such as high-definition video conferencing, video surveillance, intelligent monitoring and analysis, emergency command, digital broadcast TV, delayed TV, online teaching, live broadcast , VOD on demand, TV mail, personal recording (PVR), intranet (self-organized) channels, intelligent video broadcast control, information release and other dozens of video, voice, picture, text, communication, data and other services are all integrated into one The system platform can realize high-definition video playback through TV or computer.

In order to make those skilled in the art better understand the embodiments of the present invention, video networking is introduced as follows:

Some of the technologies used in the Internet of Things are as follows:

Network Technology

The network technology innovation of the video network improves the traditional Ethernet (Ethernet) to face the potentially huge video traffic on the network. Different from pure network packet switching (Packet Switching) or network circuit switching (Circuit Switching), the Internet of View technology adopts Packet Switching to meet the requirements of Streaming. The Internet of Things technology has the flexibility, simplicity and low price of packet switching, and at the same time has the quality and security assurance of circuit switching, and realizes the entire network of switched virtual circuits and seamless connection of data formats.

Switching Technology

The Internet of Things adopts the asynchronous and packet switching advantages of Ethernet, and eliminates the defects of Ethernet under the premise of full compatibility. User data does not need any format conversion in the whole network. Video networking is a more advanced form of Ethernet. It is a real-time switching platform that can realize the real-time transmission of large-scale high-definition video across the entire network that cannot be achieved by the Internet, and push many network video applications to high-definition and unified.

Server Technology

The server technology on the video networking and unified video platform is different from the server in the traditional sense. Its streaming media transmission is based on connection-oriented, and its data processing capability has nothing to do with traffic and communication time. A single network layer can contain information. command and data transmission. For voice and video services, the complexity of video networking and unified video platform streaming media processing is much simpler than data processing, and the efficiency is greatly improved by more than 100 times compared to traditional servers.

Storage Technology

The ultra-high-speed storage technology of the unified video platform adopts the most advanced real-time operating system in order to adapt to the media content of large capacity and large flow, and maps the program information in the server instruction to the specific hard disk space, and the media content no longer passes through the server. It is directly delivered to the user terminal in an instant, and the general waiting time of the user is less than 0.2 seconds. The optimized sector distribution greatly reduces the mechanical movement of the hard disk head seeking, and the resource consumption only accounts for 20% of the same level of IP Internet, but it generates 3 times more concurrent traffic than traditional hard disk arrays, and the overall efficiency is increased by more than 10 times.

Network Security Technology

The structural design of the Internet of Things completely eliminates the network security problems that plague the Internet through separate licensing for each service and complete isolation of equipment and user data. Generally, anti-virus programs and firewalls are not required, and hackers and viruses are prevented from attacking. , to provide users with a structured worry-free safety network.

Service Innovation Technology

The unified video platform integrates services and transmission. Whether it is a single user, a private network user, or the aggregate of a network, it is just an automatic connection. User terminals, set-top boxes or PCs are directly connected to the unified video platform to obtain a variety of multimedia video services in various forms. The unified video platform adopts the "recipe-style" table matching mode to replace the traditional complex application programming. It can realize complex applications with very little code, and realize "unlimited" new business innovation.

The networking of the Internet of Things is as follows:

The Internet of Things is a centralized control network structure. The network can be a tree network, a star network, a ring network, etc., but on this basis, a centralized control node is required in the network to control the entire network.

As shown in Figure 8, the Internet of Things is divided into two parts: the access network and the metropolitan area network.

The equipment in the access network part can be mainly divided into three categories: node server, access switch, and terminal (including various set-top boxes, coding boards, memory, etc.). The node server is connected to the access switch, and the access switch can be connected to multiple terminals and can be connected to Ethernet.

The node server is a node in the access network that functions as a centralized control, and can control access switches and terminals. The node server can be directly connected to the access switch, or it can be directly connected to the terminal.

Similarly, the equipment in the metropolitan area network can also be divided into three categories: metropolitan area server, node switch, and node server. The metropolitan area server is connected with the node switch, and the node switch can be connected with multiple node servers.

The node server is the node server of the access network part, that is, the node server belongs to both the access network part and the metropolitan area network part.

The metropolitan area server is a node with centralized control function in the metropolitan area network, which can control the node switch and the node server. The metropolitan area server can be directly connected to the node switch or directly connected to the node server.

It can be seen that the entire VisionLink network is a network structure controlled by layers and centralized, and the network controlled by the node server and the metro server can be tree, star, ring and other structures.

Figuratively, the access network part can form a unified video platform (the part in the dashed circle), and multiple unified video platforms can form a video network; each unified video platform can be interconnected through the metro and wide-area video networks.

Classification of Internet-connected devices

1.1 The devices in the video networking according to the embodiment of the present invention can be mainly divided into three categories: servers, switches (including Ethernet gateways), and terminals (including various set-top boxes, coding boards, memories, etc.). As a whole, the Internet of Views can be divided into a metropolitan area network (or a national network, a global network, etc.) and an access network.

1.2 The equipment in the access network part can be mainly divided into three categories: node server, access switch (including Ethernet gateway), terminal (including various set-top boxes, coding boards, memory, etc.).

The specific hardware structure of each access network device is as follows:

Node server:

As shown in FIG. 9 , it mainly includes a network interface module 501, a switching engine module 502, a CPU module 503, and a disk array module 504;

Among them, the incoming packets from the network interface module 501, the CPU module 503, and the disk array module 504 all enter the switching engine module 502; the switching engine module 502 performs the operation of looking up the address table 505 for the incoming packets, thereby obtaining the orientation information of the packets; The steering information of the packet stores the packet in the queue of the corresponding packet buffer 506; if the queue of the packet buffer 506 is close to full, it is discarded; the switching engine module 502 polls all the packet buffer queues, and forwards if the following conditions are met: 1) The port sending buffer is not full; 2) The queue packet counter is greater than zero. The disk array module 504 mainly realizes the control of the hard disk, including the initialization, reading and writing of the hard disk, etc.; (including the downlink protocol packet address table, the uplink protocol packet address table, and the data packet address table) configuration, and the configuration of the disk array module 504.

Access switch:

As shown in FIG. 10 , it mainly includes a network interface module (downlink network interface module 601, uplink network interface module 602), a switching engine module 603 and a CPU module 604;

Wherein, the incoming packet (uplink data) from the downlink network interface module 601 enters the packet detection module 605; the packet detection module 605 detects whether the destination address (DA), source address (SA), data packet type and packet length of the packet meet the requirements. If it matches, assign the corresponding stream identifier (stream-id) and enter the switching engine module 603, otherwise discard it; the incoming packet (downlink data) from the upstream network interface module 602 enters the switching engine module 603; the incoming data packet from the CPU module 604 Enter the switching engine module 603; the switching engine module 603 performs the operation of looking up the address table 606 for the incoming packet, thereby obtaining the orientation information of the packet; if the packet entering the switching engine module 603 is from the downlink network interface to the uplink network interface, then combine The stream identifier (stream-id) stores the packet into the queue of the corresponding packet buffer 607; if the queue of the packet buffer 607 is close to full, it is discarded; if the packet entering the switching engine module 603 is not the downstream network interface, it goes upstream If the data packet goes to the network interface, the data packet is stored in the queue of the corresponding packet buffer 607 according to the direction information of the packet; if the queue of the packet buffer 607 is nearly full, it is discarded.

The switching engine module 603 polls all packet buffer queues, and in this embodiment of the present invention, there are two situations:

If the queue is from the downlink network interface to the uplink network interface, the following conditions are met for forwarding: 1) The port sending buffer is not full; 2) The queue packet counter is greater than zero; 3) The token generated by the rate control module is obtained ;

If the queue is not from the downlink network interface to the uplink network interface, the following conditions are met for forwarding: 1) the sending buffer of the port is not full; 2) the packet counter of the queue is greater than zero.

The rate control module 608 is configured by the CPU module 604, and generates tokens for the packet buffer queues going from all downlink network interfaces to uplink network interfaces within a programmable interval, so as to control the rate of uplink forwarding.

The CPU module 604 is mainly responsible for the protocol processing with the node server, the configuration of the address table 606 , and the configuration of the rate control module 608 .

Ethernet protocol conversion gateway :

As shown in FIG. 11, it mainly includes network interface modules (downlink network interface module 701, uplink network interface module 702), switching engine module 703, CPU module 704, packet detection module 705, address table 706, packet buffer 707, code rate Control module 708, MAC adding module 709, MAC deletion module 710.

Among them, the data packets coming from the downlink network interface module 701 enter the packet detection module 705; the packet detection module 705 detects the Ethernet MAC DA, Ethernet MAC SA, Ethernet length or frame type, video network destination address DA, video network Check whether the source address SA, network data packet type and packet length meet the requirements, and if so, assign the corresponding stream identifier (stream-id); then, the MAC deletion module 710 subtracts the MAC DA, MAC SA, length or frame type (2byte), and enter the corresponding receive buffer, otherwise discard;

The downlink network interface module 701 detects the sending buffer of the port, and if there is a packet, learns the Ethernet MAC DA of the corresponding terminal according to the network destination address DA of the packet, and adds the Ethernet MAC DA of the terminal, the MACSA of the Ethernet protocol conversion gateway, Ethernet length or frame type, and send.

The functions of other modules in the Ethernet protocol conversion gateway are similar to that of the access switch.

terminal:

Mainly include network interface module, service processing module and CPU module; for example, set-top box mainly includes network interface module, video and audio codec engine module, CPU module; encoding board mainly includes network interface module, video and audio encoding engine module, CPU module; memory It mainly includes network interface module, CPU module and disk array module.

1.3 The equipment in the metropolitan area network can be mainly divided into two categories: node server, node switch, and metropolitan area server. Among them, the node switch mainly includes a network interface module, a switching engine module and a CPU module; the metropolitan area server mainly includes a network interface module, a switching engine module and a CPU module.

2. Definition of Internet Data Packets

2.1 Definition of Access Network Data Packets

The data packet of the access network mainly includes the following parts: destination address (DA), source address (SA), reserved bytes, payload (PDU), and CRC.

As shown in the table below, the data packets of the access network mainly include the following parts:

DA SA Reserved Payload CRC

in:

The destination address (DA) consists of 8 bytes (byte), the first byte indicates the type of the data packet (such as various protocol packets, multicast data packets, unicast data packets, etc.), there are up to 256 possibilities, The second to sixth bytes are the metropolitan area network address, and the seventh and eighth bytes are the access network address;

The source address (SA) is also composed of 8 bytes (byte), and the definition is the same as the destination address (DA);

Reserved bytes consist of 2 bytes;

The payload part has different lengths according to different types of datagrams. If it is a variety of protocol packets, it is 64 bytes. If it is a single multicast data packet, it is 32+1024=1056 bytes. Of course, it is not limited to Above 2 kinds;

The CRC consists of 4 bytes, and its calculation method follows the standard Ethernet CRC algorithm.

2.2 MAN Data Packet Definition

The topology of the metropolitan area network is a graph. There may be two or even more than two connections between two devices, that is, there may be more than two connections between node switches and node servers, between node switches and node switches, and between node switches and node servers. kind of connection. However, the metropolitan area network address of the metropolitan area network equipment is unique. In order to accurately describe the connection relationship between the metropolitan area network equipment, a parameter: label is introduced in the embodiment of the present invention to uniquely describe a metropolitan area network equipment.

The definition of labels in this specification is similar to the definition of MPLS (Multi-Protocol Label Switch, Multi-Protocol Label Switch) labels. Assuming that there are two connections between device A and device B, the data packets from device A to device B have 2 labels, packets from device B to device A also have 2 labels. Labels are divided into incoming labels and outgoing labels. Assuming that the label (incoming label) of the data packet entering device A is 0x0000, the label (outgoing label) of the data packet when it leaves device A may become 0x0001. The network access process of the metropolitan area network is a network access process under centralized control, which means that the address allocation and label allocation of the metropolitan area network are dominated by the metropolitan area server, and the node switches and node servers are all passively executed. Different from MPLS label assignment, MPLS label assignment is the result of mutual negotiation between switches and servers.

As shown in the table below, the data packets of the metropolitan area network mainly include the following parts:

DA SA Reserved Label Payload CRC

Namely destination address (DA), source address (SA), reserved bytes (Reserved), label, payload (PDU), CRC. Among them, the format of the label can refer to the following definition: the label is 32 bits, of which the upper 16 bits are reserved, and only the lower 16 bits are used, and its position is between the reserved bytes of the data packet and the payload.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments may be referred to each other.

It should be understood by those skilled in the art that the embodiments of the embodiments of the present invention may be provided as a method, an apparatus, or a computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media having computer-usable program code embodied therein, including but not limited to disk storage, CD-ROM, optical storage, and the like.

Embodiments of the present invention are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present invention. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal equipment to produce a machine that causes the instructions to be executed by the processor of the computer or other programmable data processing terminal equipment Means are created for implementing the functions specified in the flow or flows of the flowcharts and/or the blocks or blocks of the block diagrams.

These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing terminal equipment to operate in a particular manner, such that the instructions stored in the computer readable memory result in an article of manufacture comprising instruction means, the The instruction means implement the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing terminal equipment, so that a series of operational steps are performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby executing on the computer or other programmable terminal equipment The instructions executed on the above provide steps for implementing the functions specified in the flowchart or blocks and/or the block or blocks of the block diagrams.

Although preferred embodiments of the embodiments of the present invention have been described, additional changes and modifications to these embodiments may be made by those skilled in the art once the basic inventive concepts are known. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications that fall within the scope of the embodiments of the present invention.

Finally, it should also be noted that in this document, relational terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply these entities or that there is any such actual relationship or sequence between operations. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or terminal device comprising a list of elements includes not only those elements, but also a non-exclusive list of elements. other elements, or also include elements inherent to such a process, method, article or terminal equipment. Without further limitation, an element defined by the phrase "comprises a..." does not preclude the presence of additional identical elements in the process, method, article or terminal device comprising said element.

A data management method and a data management device provided by the present invention have been introduced in detail above. The principles and implementations of the present invention are described with specific examples in this paper. The descriptions of the above embodiments are only used to help Understand the method of the present invention and its core idea; at the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific implementation and application scope. In summary, the content of this specification does not It should be understood as a limitation of the present invention.

Claims (10)

1. a data management method, is characterized in that, described method comprises: Obtain the child node identifier corresponding to the data stored in the target device; Identify the parent node identifier corresponding to the child node identifier; Replace the parent node identifier in the preset first mapping relationship with the corresponding child node identifier to obtain a second mapping relationship, where the preset first mapping relationship is the parent node identifier and the preset Mapping relationship between identifiers; receiving a target identifier input for the preset identifier; Replace the preset identification in the second mapping relationship with the target identification, and obtain a third mapping relationship between the target identification and the child node identification, so as to manage the target according to the third mapping relationship The data set corresponding to the parent node identifier stored in the device. 2. The method according to claim 1, characterized in that, in the replacement of the preset identifier in the second mapping relationship with the target identifier, obtaining a relationship between the target identifier and the child node identifier After the step of the third mapping relationship, it also includes: receiving a first input, where the first input at least includes: an acquisition instruction and a target identifier; Determine at least one child node identifier corresponding to the target identifier according to the third mapping relationship; Acquire data corresponding to the at least one child node identifier from the target device according to the acquisition instruction. 3. The method according to claim 1, characterized in that, replacing the preset identifier in the second mapping relationship with the target identifier, and obtaining between the target identifier and the child node identifier After the step of the third mapping relationship, it also includes: receiving a second input, where the second input at least includes: a modification instruction, a target identifier, and a child node index value; Determine at least one child node identifier corresponding to the target identifier according to the third mapping relationship; Identifying the parent node identifier corresponding to the at least one child node identifier; Generate a target child node identifier according to the parent node identifier and the child node index value; The target device is controlled to modify the data corresponding to the target child node identifier according to the modification instruction. 4. The method according to claim 1, wherein the step of obtaining the child node identifier corresponding to the data stored in the target device comprises: Use the query method class in the private simple network management protocol to obtain the parent node identifier corresponding to the data set stored in the target device, and the child node index value corresponding to the parent node identifier; The parent node identifier and the child node index value are combined to obtain the child node identifier corresponding to each data in the data set. 5. The method according to claim 1, wherein the preset first mapping relationship is obtained by the following steps: Obtain the parent node identifier corresponding to the data set in the target device; Generate a preset identifier corresponding to the parent node identifier according to a preset rule; A mapping relationship between the parent node identifier and the preset identifier is established to obtain a preset first mapping relationship. 6. The method according to claim 1, wherein the device management system adopts the Internet of View protocol, the target device adopts the Internet protocol, the device management system and the target device are communicated and connected through a protocol conversion server, and the The steps of obtaining the identifier of the child node corresponding to the data stored in the target device include: The child node identifier corresponding to the data stored in the target device is acquired through the transparent transmission module in the protocol conversion server. 7. A data management device, wherein the device comprises: The first acquisition module is used to acquire the child node identifier corresponding to the data stored in the target device; a first identification module for identifying the parent node identification corresponding to the child node identification; The first replacement module is used to replace the identifier of the parent node in the preset first mapping relationship with the corresponding identifier of the child node to obtain a second mapping relationship, and the preset first mapping relationship is the Describe the mapping relationship between the parent node identifier and the preset identifier; a first receiving module, configured to receive a target identifier input for the preset identifier; A second replacement module, configured to replace the preset identifier in the second mapping relationship with the target identifier, and obtain a third mapping relationship between the target identifier and the child node identifier, so as to The three-mapping relationship manages the data set corresponding to the parent node identifier stored in the target device. 8. The device according to claim 7, wherein the device further comprises: A second receiving module, configured to receive a first input, where the first input at least includes: an acquisition instruction and a target identifier; a first determining module, configured to determine at least one sub-node identifier corresponding to the target identifier according to the third mapping relationship; A second acquiring module, configured to acquire data corresponding to the identifier of the at least one child node from the target device according to the acquiring instruction. 9. The device according to claim 7, wherein the device further comprises: A third receiving module, configured to receive a second input, where the second input at least includes: a modification instruction, a target identifier, and a child node index value; a second determining module, configured to determine at least one sub-node identifier corresponding to the target identifier according to the third mapping relationship; The second identification module is used to identify the parent node identification corresponding to the at least one child node identification; a generating module, configured to generate a target child node identifier according to the parent node identifier and the child node index value; A modification module, configured to control the target device to modify the data corresponding to the target child node identifier according to the modification instruction. 10. The apparatus according to claim 7, wherein the acquisition module comprises: The first obtaining submodule is used to obtain the parent node identifier corresponding to the data set stored in the target device, and the child node index value corresponding to the parent node identifier by using the query method class in the private simple network management protocol; The assembly submodule is used for combining the parent node identifier and the child node index value to obtain the child node identifier corresponding to each data in the data set.

Images