CN117424928B - Network equipment and resource sharing method - Google Patents

Abstract

The present invention provides a method for sharing network equipment and resources, including: device discovery: the local device starts P2P connection service and prepares its own device information, and simultaneously deploys multicast DNS and discovery services to publish its own device information and Detect other network devices; resource sharing: The local device obtains information from other network devices, establishes a P2P connection with the corresponding device based on the information, and shares resource information through P2P connection communication. This invention does not require the user to specify the device IP address, with zero-configuration access. The device and resource status can be updated synchronously in real time. It can run on all operating system platforms and devices that support standard IP protocol stacks. Different operating systems can also directly share resource information. .

Description

Methods for sharing network equipment and resources

Technical field

The present invention relates to the field of resource interaction, and in particular to a network device and a resource sharing method.

Background technique

Network equipment and resource sharing means that users can access other equipment and resource information on the network on any computer, including files, audio and video media streams, pictures and other digital content. Users need to specify the device IP address and port before accessing network devices. They cannot directly obtain the devices and resources on the current network. There are some network neighbor protocols that can automatically discover other network devices (for example, Simple Service Discovery Protocol-SSDP, Server Blocking -SMB, Network Service Dynamic Discovery Protocol WS-D), but they are only suitable for sharing specific types of resources (such as files, printers), cannot run across subnets, and there is no P2P long connection between devices, resulting in the inability to sense devices and resources online in real time status, and different operating system platforms may not be able to communicate with each other.

Contents of the invention

In view of the problems existing in the existing technology, a method for sharing network equipment and resources is provided, using a combination of multicast DNS (domain name system) and a discovery server, so that network equipment can automatically discover each other and run across subnets. After the devices discover each other, they can then exchange resource information with each other through P2P connection networking, which can ensure that device and resource status are updated online in real time. After the connection is established, any form of data can be transmitted, and the resources shared between devices are no longer limited to specific types.

The technical solution adopted by the present invention is as follows: a method for sharing network equipment and resources, including:

Device discovery: The local device starts the P2P connection service and prepares its own device information. At the same time, it deploys multicast DNS and discovery services to publish its own device information and detect other network devices throughout the network;

Resource sharing: The local device obtains information from other network devices, establishes a P2P connection with the corresponding device based on the information, and shares resource information through P2P connection communication.

Further, the prepared own device information includes:

① Use TCP or other reliable IP transmission protocols to bind a local port;

②Record the protocol name used;

③Generate a random device number;

④Collect the network IP information of the local device.

Further, the specific working process of the multicast DNS includes:

Step A1. After the local device goes online, it automatically joins an IP multicast and constructs a DNS response message. After the response message is constructed, it is immediately sent to the multicast address. Other network devices in the network receive the response message and parse it out. After entering the device information, try to connect to the local device;

Step A2: Query other devices in the network, construct a DNS query message, and send the query message to the target multicast address. After receiving the query message, other network devices parse the query type and domain name, and construct a response message after the domain name matches. Sent to query device;

Step A3: Wait for DNS response messages from other network devices in the network. After receiving the messages, parse out the P2P service connection information of the device, and try to connect to the device for resource sharing based on the parsed information;

Step A4: Continuously monitor the online DNS messages or offline DNS messages of other devices in the network, verify the message content and parse to obtain the corresponding device information, and use device numbers to distinguish different devices; when the local device goes offline, send offline DNS message to the multicast address.

Further, in step A2, the domain name matching rules are:

Compare the service name and protocol name. If they are the same as the local server name and protocol name, the match is successful;

Names are matched according to string rules and are not case-sensitive.

Further, the working process of discovery service includes:

Step B1. Use the WebSocket protocol to bind the server address and port, listen for connection requests and respond;

Step B2. Deploy a local DNS server in the device or use the DNS server in the current network, and add the discovery service record to the DNS server, including the domain name and IP address of the discovery server;

Step B3: Other devices in the network discover the service address through DNS query and resolution;

Step B4: The local device connects to the discovery server and registers the local device information;

Step B5: The discovery server distributes the registered device information, compiles the registered device information into a device information table, and sends the device information table to each connected device;

Step B6: After receiving the device information table, the local device parses the P2P connection information of other devices and attempts to initiate a connection.

Further, in step B3, if step B2 cannot be performed, directly configure the local device DNS cache record to add the IP address of the discovery server.

Further, in step B5, when the device information changes, a connection is established or a connection is disconnected, the specific data management method is as follows:

When the device establishes a connection or the information changes, use the device number as the primary key to update the current device information list. At the same time, the device number is bound to the current connection mapping, and then the device information table is sent to other connected devices;

When the device is disconnected, the corresponding data in the device information table is deleted through its device number, and then the device information table is sent to other connected devices.

Further, the specific process of establishing a P2P connection with the corresponding device based on the information includes:

Step C1: Integrate the connection information of the device through the device number to generate an address information table, and treat information with the same number as information of the same device;

Step C2: Traverse the information table and start connecting from the first address information;

Step C3. If the connection fails, try to connect to the next address. If the information table is updated during the process, re-enter step C2;

Step C4. If the connection is successful, stop traversing and keep the connection;

Step C5: If the connection is disconnected, check whether the information table is updated. If there is an update, proceed to step C2. If there is no update, stop the connection process and the other device goes offline.

Further, the specific process of sharing resource information through P2P connection communication includes:

After the connection is established, the devices on both sides immediately send the resource information shared by the other device to the other device; the resource information of each device is indexed by the corresponding resource number and stored in the resource information table;

When devices in the entire network establish connections with each other and exchange resource information, when the resource information and status of a certain device change, the corresponding changes need to be synchronized to other devices in the network.

Further, the synchronization process is:

Step D1. When adding resource information, generate a new local unique resource number, bind the resource number to the resource information, and update it to the resource information table;

Step D2: Resource information changes or is deleted, and the resource information is updated by indexing the resource number;

Step D3: Send the updated resource information table to all other currently connected devices through the P2P connection;

Step D4: After other devices receive it, they index to the corresponding resource information table through the device number and update the data.

Compared with the existing technology, the beneficial effects of adopting the above technical solution are: the present invention does not require users to specify device IP addresses, has zero-configuration access, device and resource status can be updated synchronously in real time, and can run on all operations that support standard IP protocol stacks On system platforms and devices, different operating systems can also directly share resource information.

Description of the drawings

Figure 1 is a flow chart of a method for sharing network equipment and resources proposed by the present invention.

Figure 2 is a schematic diagram of an application system for device discovery in an embodiment of the present invention.

Figure 3 is a schematic diagram of the process of establishing a connection in an embodiment of the present invention.

Detailed ways

The embodiments of the present application are described in detail below. Examples of the embodiments are shown in the drawings, where the same or similar reference numerals throughout represent the same or similar modules or modules with the same or similar functions. The embodiments described below with reference to the drawings are exemplary and are only used to explain the present application and cannot be understood as limiting the present application. On the contrary, the embodiments of the present application include all changes, modifications and equivalents falling within the spirit and scope of the appended claims.

The embodiment of the present invention proposes a method in which network devices can freely share different types of resource information. At the same time, there is no need for users to specify device IP addresses, zero-configuration access, device and resource status can be updated synchronously in real time, and it can run on all devices that support standard IP On the operating system platform and device of the protocol stack, different operating systems can also directly share resource information. specific:

Please refer to Figure 1. The network device and resource sharing method includes two parts: device discovery and resource sharing. in,

(1) The device discovery part includes: after the local device is started, the P2P connection service is first started for subsequent P2P connection establishment. After the service is started, its own device information is prepared and used in subsequent device information exchanges. Then the device connection information discovery process begins. Multicast DNS and discovery services work simultaneously to publish their own device information and detect other devices throughout the network. The specific system is shown in Figure 2.

In one embodiment, the own device information includes bound local port information, P2P protocol type, device number, and network IP information. Its acquisition methods include:

a) Use TCP or other reliable IP transmission protocols to bind a local port;

b) Record the protocol name used, such as "tcp";

c) Generate a random device number (id) with a length of 32 bits;

d) Collect the network IP information of the local device.

The following is a further explanation of multicast DNS and discovery services in device discovery work.

The working process of multicast DNS includes:

Step A1. After the local device goes online, it automatically joins an IP multicast and constructs a DNS response message. After the response message is constructed, it is immediately sent to the multicast address. Other network devices in the network receive the response message and parse it out. After receiving the device information, you can start trying to connect to the local device.

It should be noted that the DNS response message must contain the following records:

a) For an A-type or AAAA-type record data, the domain name field must comply with the rules described in RFC8533, including the protocol name and service name. The service name uses "_nvi" by default;

b) A piece of SRV type data, including the local device name and the port bound to the local P2P connection service;

c) A piece of TXT type extended data, the data content uses the "k=v" dictionary format and includes the device number ("id=123");

d) The survival time field must be greater than 0.

In one embodiment, IP multicast is used to receive messages from other devices, and the default address and port specified in RFC6762 can be used.

Step A2: Query other devices in the network, construct a DNS query message, and send the constructed query message to the target multicast address. The router will forward the multicast message to other network devices, and other network devices receive the query. After the message is parsed, the query type and domain name are parsed. After the domain name is matched, a response message is constructed and sent to the query device.

In this embodiment, the DNS query message must contain the following records:

a) A piece of query data of type A, type AAAA, type SRV, or type PTR;

b) The domain name field queried needs to comply with the rules described in RFC8533, including the protocol name and service name. The service name uses "_nvi" by default.

In one embodiment, the domain name matching rules are:

a) Compare the service name and protocol name. If they are the same as the service name and protocol of the local machine, the match is considered successful;

b) Names are matched according to string rules and are not case-sensitive.

Step A3: Wait for DNS response messages from other network devices in the network. After receiving the messages, parse out the device's P2P service connection information, and try to connect to the device for resource sharing based on the parsed information.

In this embodiment, the DNS response message must contain the following records:

a) An A type or AAAA type record with a correct IP address;

b) A piece of SRV type data, including the device name and the port bound to the P2P connection service;

c) A piece of TXT type extended data. The data content uses the "k=v" dictionary format and includes the device number (for example, "id=123").

Step A4: Continuously monitor the DNS messages of other devices in the network that go online or offline, verify the received messages according to the message content requirements described in step A3, parse and obtain the IP address, port, and device number data, and use the device number to distinguish between different devices.

Step A5: The local device goes offline and sends an offline DNS message to the multicast address added in step A1. The message must contain:

a) A piece of TXT type extended data, the data content uses the "k=v" dictionary format and includes the device number (for example, "id=123");

b) The time-to-live field must be set to 0.

The exchange of device information is completed through multicast DNS. The entire process does not require user configuration intervention and is completely completed automatically by the system.

Multicast DNS cannot discover other devices across multiple subnets or when multicast packet routing is disabled. Network administrators deploy discovery services to help share information between devices. The discovery service can communicate using the WebSocket protocol and only uses unicast messages to ensure normal routing. At the same time, local DNS can be configured to resolve the discovery server IP address, and the device can be accessed through DNS zero configuration. specific:

The working process of discovery service includes:

Step B1. Deploy the discovery service, use the WebSocket protocol to bind the server address and port, listen for connection requests and respond.

Step B2: Add a record of the discovery service to the DNS server, including the domain name and the IP address of the discovery server. The domain name can be "sd.nvi" and the recorded IP address is configured as the IP address of the discovery server. The DNS server can be a local DNS server deployed or use a DNS server in the current network.

Step B3: Other devices in the network discover the service address through DNS query and resolution. If step B2 cannot be performed, the discovery service address cannot be resolved through DNS query. In this case, you can directly configure the local DNS cache record to add the IP address of the discovery server. For example, in Windows systems, you can add a line of record "10.1.1.2 sd.nvi" in the "C:\Windows\System32\drivers\etc\hosts" file.

Step B4: The local device connects to the discovery server and registers the local device information.

In this embodiment, the registration information must include the data shown in Table 1:

Table 1 Registration information table

Step B5: The discovery server distributes the registered device information, compiles the registered device information into a device information table, and sends the device information table to each connected device; each row of data in the device information table contains a complete Device registration information.

In one embodiment, when the device information changes, the connection is established and the connection is disconnected, the specific data management method is as follows:

a) When a device is established or the information changes, use the device number as the primary key to update the current device information list. At the same time, the device number is bound to the current connection mapping, and then the device information table is sent to other connected devices.

b) When a device disconnects, delete the data in the information table through the device number, and then send the device information table to other connected devices.

Step B6: After receiving the device information table, the local device parses the P2P connection information of other devices and attempts to initiate a connection.

Through multicast DNS and discovery services, devices can be shared across the entire network and established connections with other devices throughout the network.

(2) The resource sharing part includes: obtaining the IP addresses, P2P connection protocol types and port information of other network devices through device discovery. Using this information, you can start to try to establish P2P connections with devices on the network, and then use P2P Connect and communicate to share resource information.

A network device may be in multiple networks, and accordingly it will have multiple IP addresses. It needs to find an address that can communicate with each other to establish a connection. Please refer to Figure 3. The specific process of establishing a connection includes:

Step C1: Integrate the connection information of the device through the device number to generate an address information table, and treat information with the same number as information of the same device.

Step C2: Traverse the information table and start connecting from the first address information.

Step C3: If the connection fails, try to connect to the next address. If the information table is updated during the process, re-enter step C2.

Step C4: If the connection is successful, stop traversing and keep the connection.

Step C5: If the connection is disconnected, check whether the information table is updated. If there is an update, proceed to step C2. If there is no update, stop the connection process and the other device goes offline.

It should be noted that the connection is maintained after it is established and keep-alive packets are sent periodically. The device automatically disconnects when it goes offline.

After the connection is established, the devices on both sides immediately send the resource information shared by the machine to the other device, so that both parties can obtain the resource information of the other party. Among them, the resource information of each device is indexed through the corresponding resource number and stored in the resource information table. The data fields of resource information in each device include but are not limited to the content shown in Table 2:

Table 2 Resource information table

When devices in the entire network establish connections with each other and exchange resource information, users can obtain resource information shared by other devices on any device. It should be noted that once the resource information and status of a certain device change, the corresponding changes need to be synchronized to other devices in the network. The specific synchronization process is:

Step D1. When adding resource information, generate a new local unique resource number, bind the resource number to the resource information, and update it to the resource information table;

Step D2: Resource information changes or is deleted, and the resource information is updated by indexing the resource number;

Step D3: Send the updated resource information table to all other currently connected devices through the P2P connection;

Step D4: After other devices receive it, they index to the corresponding resource information table through the device number and update the data.

The present invention combines a multicast DNS (domain name system) and a discovery server to allow network devices to automatically discover each other and run across subnets at the same time. After the devices discover each other, they can then exchange resource information with each other through P2P connection networking, which can ensure that device and resource status are updated online in real time. After the connection is established, any form of data can be transmitted, and the resources shared between devices are no longer limited to specific types.

It should be noted that the specific steps involved in this description are not completely dependent on each other, and may also be parallel.

The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of the present application. Each block in the flow chart or block diagram may represent a module, program segment, or part of the code. The above-mentioned module, program segment, or part of the code includes one or more executable components for implementing the specified logical function. instruction. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown one after another may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. It will also be noted that each block in the block diagram or flowchart illustration, and combinations of blocks in the block diagram or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or may be implemented by special purpose hardware-based systems that perform the specified functions or operations. Achieved by a combination of specialized hardware and computer instructions.

The units involved in the embodiments of this application can be implemented in software or hardware, and the described units can also be provided in a processor. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances.

As another aspect, the present application also provides a computer program product or computer program, which computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the network device and resource sharing method described in the above embodiments.

As another aspect, this application also provides a computer-readable medium. The computer-readable medium may be included in the electronic device described in the above embodiments; it may also exist independently without being assembled into the electronic device. middle. The computer-readable medium carries one or more programs. When the one or more programs are executed by an electronic device, the electronic device implements the network device and resource sharing method described in the above embodiments.

It should be noted that although several modules or units of equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above may be further divided into being embodied by multiple modules or units.

Through the above description of the embodiments, those skilled in the art can easily understand that the example embodiments described here can be implemented by software, or can be implemented by software combined with necessary hardware. Therefore, the technical solution according to the embodiment of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to cause a computing device (which can be a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiment of the present application.

For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood in specific situations; the drawings in the embodiments are used to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, all The described embodiments are some, but not all, of the embodiments of the present invention. The components of the embodiments of the invention generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations.

Although the embodiments of the present application have been shown and described above, it can be understood that the above-mentioned embodiments are illustrative and cannot be understood as limitations of the present application. Those of ordinary skill in the art can make modifications to the above-mentioned embodiments within the scope of the present application. The embodiments are subject to changes, modifications, substitutions and variations.

Claims (8)

1. The network equipment and the resource sharing method are characterized by comprising the following steps:

the device discovers: the local equipment starts P2P connection service, prepares self equipment information, deploys multicast DNS and discovery service to release self equipment information and detect other network equipment in the whole network;

and (3) resource sharing: the local equipment acquires information of other network equipment, establishes P2P connection with corresponding equipment according to the information, and shares resource information through P2P connection communication;

the specific working process of the multicast DNS comprises the following steps:

step A1, after local equipment is online, automatically adding an IP multicast, and constructing a DNS response message; immediately sending the response message to the multicast address after the construction is completed, and starting to attempt to connect the local equipment after other network equipment in the network receives the response message and analyzes the equipment information;

a2, inquiring other network equipment in the network, constructing a DNS inquiry message, sending the inquiry message to a target multicast address, analyzing the inquiry type and the domain name after the other network equipment receives the inquiry message, and constructing a response message after the domain name is matched and sending the response message to the inquiry equipment;

a3, waiting for DNS response messages of other network devices in the network, analyzing P2P service connection information of the devices after receiving the messages, and attempting to connect the devices for resource sharing according to the analyzed information;

step A4, continuously monitoring the online DNS messages or the offline DNS messages of other network devices in the network, verifying the content of the messages, analyzing and obtaining corresponding device information, and distinguishing different devices by using device numbers; when the local equipment is offline, an offline DNS message is sent to a multicast address;

the working process of the discovery service comprises the following steps:

step B1, binding a server address and a port by using a WebSocket protocol, monitoring a connection request and responding;

step B2, a local DNS server is deployed in the equipment or a DNS server in the current network is used, and a record of the discovery service, comprising a domain name and an IP address of the discovery server, is added in the DNS server;

step B3, other network equipment in the network analyzes and discovers the service address through DNS inquiry;

step B4, the local equipment is connected to a discovery server, and the local equipment information is registered;

step B5, the discovery server distributes registered equipment information, compiles the information of the registered equipment into an equipment information table, and sends the equipment information table to each connected equipment;

and B6, after receiving the device information table, the local device analyzes the P2P connection information of other network devices and tries to initiate connection.

2. The network device and the resource sharing method according to claim 1, wherein the prepared own device information includes:

(1) binding a native port using TCP or other reliable IP transport protocol;

(2) recording the name of the protocol used;

(3) generating a random device number;

(4) network IP information of the local device is collected.

3. The method for sharing resources and network equipment according to claim 1, wherein in the step A2, the domain name matching rule is:

comparing the service name and the protocol name, wherein the service name and the protocol name are the same as the server name and the protocol name of the local machine, namely the matching is successful;

names are matched according to the string rule, and case are not distinguished.

4. The method for sharing resources and network device according to claim 1, wherein in the step B3, if the step B2 cannot be executed, the local device DNS cache record is directly configured to add the IP address of the discovery server.

5. The method for sharing resources and network devices according to claim 1, wherein in step B5, after the device information is changed, connection is established or disconnected, a specific data management manner is as follows:

when the equipment establishes connection or information is changed, using the equipment number as a primary key to update the equipment information list, binding the equipment number with the current connection mapping, and then sending the equipment information list to other connected equipment;

and after the equipment is disconnected, deleting the corresponding data of the equipment information table through the equipment number, and then sending the equipment information table to other connected equipment.

6. The method for sharing resources by network devices according to claim 1, wherein the specific process of establishing a P2P connection with the corresponding device according to the information includes:

step C1, generating an address information table through the connection information of the equipment number integration equipment, and regarding the information with the same number as the information of the same equipment;

step C2, traversing the information table, and starting connection from the first address information;

step C3, if the connection fails, the next address is tried to be connected, and if the information table is updated in the process, the step C2 is restarted;

step C4, successfully connecting, stopping traversing, and maintaining connection;

and step C5, if the connection is disconnected, detecting whether the information table is updated, if so, entering a step C2, and if not, stopping the connection process, and if not, disconnecting the opposite equipment.

7. The method for sharing resources by network devices according to claim 1 or 6, wherein the specific process of sharing resource information through P2P connection communication includes:

after connection is established, the two devices immediately send the resource information shared by the two devices for one time to the other device; the resource information of each device constructs an index through the corresponding resource number and stores the index into a resource information table;

when the resource information and the state of a certain device are changed after the devices in the whole network establish the connection interaction resource information, the corresponding change needs to be synchronized to other network devices in the network.

8. The network device and resource sharing method of claim 7, wherein the synchronization process is:

step D1, when the resource information is newly added, generating a new unique resource number of the machine, binding the resource number with the resource information, and updating the resource number into a resource information table;

step D2, changing or deleting the resource information, and updating the resource information through the resource number index;

step D3, the updated resource information table is sent to all other network devices which are connected at present through P2P connection;

and D4, after receiving the data, other network equipment indexes the corresponding resource information table through the equipment number, and updates the data.