A network intercommunication method, device and computer cluster based on private network
By realizing network service deployment licenses and interoperability between public and private network devices, the problem of one-way connectivity of private networks is solved, and the interoperability between private networks and other networks is achieved, saving bandwidth costs and improving Resource utilization rate.
Patent Information
- Application Number
- CN202011003839.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-09-22
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-09-22
AI Technical Summary
Existing private networks can only achieve one-way communication and the Internet, and cannot effectively utilize bandwidth resources, resulting in an increase in bandwidth costs and limiting the development of the Internet.
By enabling network service deployment licenses and IPv6 addresses between public and private devices, public network devices are allowed to obtain the IPv6 address of private network devices and update them when necessary to achieve intercommunication between private networks and other networks. .
It realizes two-way interoperability between private networks and other networks, saves bandwidth costs, improves resource utilization, and reduces the bandwidth requirements for Internet access.
Smart Images

Figure CN114301873B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a network intercommunication method, device and computer cluster based on a private network. Background Art
[0002] With the popularization of the Internet and the rapid development of big data and cloud computing technologies, the scale of Internet users is growing. The surge in the scale of Internet users has increased the bandwidth required by Internet users to access the Internet, resulting in a sharp increase in bandwidth costs, which, to a certain extent, has restricted the development of the Internet.
[0003] Currently, there are many unused bandwidth resources in private networks. If the Internet can borrow these bandwidth resources, it can save a lot of bandwidth costs.
[0004] However, private networks can only achieve one-way communication with the Internet at present, that is, network devices in private networks can only access the Internet in one direction, while devices in the Internet cannot access the private network. This one-way communication method has become an urgent problem that needs to be solved in the solution of borrowing bandwidth resources in private networks by the Internet. Summary of the invention
[0005] The present application provides a network intercommunication method, device and computer cluster based on a private network, so as to realize the interconnection and intercommunication between the private network and other networks.
[0006] In the first aspect, the embodiment of the present application provides a network intercommunication method based on a private network, which can be executed by a device deployed in a public network (hereinafter referred to as a public network device), and the method includes: the public network device can first obtain a network service deployment license from the private network device, and after obtaining the network service deployment license, it can instruct the private network device to deploy the network service, and record the IPv6 address of the private network device that deploys the network service, such as recording the correspondence between the identifier of the network service and the IPv6 address of the private network device. Afterwards, when receiving a service query request from a client for requesting the IPv6 address of the private network device that deploys the network service, the public network device can provide the client with the IPv6 address of the private network device that provides the network service.
[0007] Through the above method, when the client needs a private network device to provide network services, it can first obtain the IPv6 address of the private network device from the public network device, and then realize the interconnection between the private network and other networks (such as the public network or other private networks), which provides the possibility for the Internet to borrow the resources of the private network.
[0008] In one possible implementation, the network service deployment license obtained by the public network device from the private network device may be requested by the public network device to the private network device. For example, the public network device may send a service deployment request to the private network device, and the service deployment request is used to request the deployment of the network service. Afterwards, the public network device may receive a service deployment response from the private network device, and the service deployment response is used to agree to deploy the network service.
[0009] Through the above method, the public network device can request the network service deployment permission from the private network device so that the network service can be deployed subsequently.
[0010] In one possible implementation, the service deployment request may also indicate a first preferential policy, which is fee discount information provided to private network devices for private network devices. The number of first preferential policies is not limited here, and may be one or more, so that the private network device can choose from multiple first preferential policies.
[0011] Through the above method, in order to deploy network services in private network devices, public network devices can provide some preferential policies so that private network devices can provide network service deployment permissions.
[0012] In one possible implementation, the network service deployment permission obtained by the public network device from the private network device may also be actively provided by the private network device. For example, the public network device may receive a resource occupation permission from the private network device, and the resource occupation permission is used to indicate that it is allowed to occupy the resources of the private network device to deploy network services.
[0013] Through the above method, the private network device can actively request the deployment of network services, thereby improving the initiative of the private network device and being applicable to other scenarios.
[0014] In a possible implementation, the resource occupation permission also includes a second preferential policy, which is a fee preferential information proposed by the private network device for the private network device. The number of second preferential policies is not limited here, and can be one or more, so that the public network device can choose from multiple second preferential policies.
[0015] Through the above method, private network devices can actively request the deployment of network services and can also put forward their own demands for fee discounts.
[0016] In a possible implementation, when a network service is updated, or a network service needs to be deleted or migrated, the public network device may also instruct the private network device to update the network service.
[0017] Through the above method, the public network device can update the network service in time to ensure the effectiveness of the network service deployed in the private network device.
[0018] In a possible implementation, the public network device may also receive an updated IPv6 address of the private network device from the private network device, and update the locally stored IPv6 address of the private network device.
[0019] Through the above method, the public network device can obtain the updated IPv6 address to ensure that the latest and most accurate IPv6 address of the private network device can always be saved locally, ensuring the validity of the IPv6 address provided to the client.
[0020] On the second aspect, an embodiment of the present application provides a network intercommunication method based on a private network, which can be executed by a private network device in a private network. In this method, the private network device can provide a network service deployment license to a device in a public network; thereafter, under the instruction of the device in the public network, the network service is deployed, and the IPv6 address of the private network device can also be sent to the device in the public network; after the network service is deployed, the private network device can provide network services to the client, that is, the private network device can receive service requests from the client, and the service requests are used to request network services; thereafter, a service response is fed back according to the service request.
[0021] Through the above method, network services can be deployed in private network devices. By providing the IPv6 address of the private network device to the public network device, the client can access the private network device to obtain network services, thereby realizing interconnection between the private network device and devices in other networks.
[0022] In a possible implementation, when a private network device provides a network service deployment license to a device in a public network, it may be provided at the request of the public network device. For example, the private network device may receive a service deployment request from a device in a public network, the service deployment request being used to request the deployment of a network service; and then send a service deployment response to the device in the public network, the service deployment response being used to agree to deploy the network service.
[0023] Through the above method, the private network device provides the network service deployment permission at the request of the public network device, so that the network service can be deployed subsequently.
[0024] In a possible implementation, the service deployment request is also used to indicate a first preferential policy, which is fee preferential information provided to the private network device and targeted at the private network device. The number of first preferential policies is not limited here, and can be one or more. When there are multiple first preferential policies, the private network device selects from the multiple first preferential policies and carries the selected first preferential policy in the service deployment response.
[0025] Through the above method, the private network device can obtain corresponding preferential policies when agreeing to deploy network services, making the solution of deploying network services in the private network device more feasible.
[0026] In one possible implementation, the network service deployment permission provided by the private network device to the device in the public network may also be actively proposed by the private network device. For example, the private network device may send a resource occupation permission to the device in the public network. The resource occupation permission is used to indicate that the resources of the private network device are allowed to be occupied to deploy network services.
[0027] Through the above method, the private network device can actively request the deployment of network services, thereby improving the initiative of the private network device and being applicable to other scenarios.
[0028] In a possible implementation, the resource occupation permission also includes a second preferential policy, which is a fee preferential information proposed by the private network device for the private network device. The number of second preferential policies is not limited here, and can be one or more, so that the public network device can choose from multiple second preferential policies.
[0029] Through the above method, private network devices can actively request the deployment of network services and can also actively express their demands for fee discounts to obtain corresponding compensation.
[0030] In a possible implementation, the private network device may also update the network service under the instruction of the device in the public network.
[0031] Through the above method, the timely update of network services can ensure the effectiveness of network services deployed in private network devices.
[0032] In a possible implementation, when the private network device's IPv6 address is updated, the private network device may send the updated IPv6 address to the device in the public network.
[0033] Through the above method, the private network device can provide the updated IPv6 address in time, ensuring that the public network device can obtain the latest and most accurate IPv6 address of the private network device.
[0034] In the third aspect, the embodiment of the present application provides a network intercommunication method based on a private network, which can be executed by a device deployed in a public network (hereinafter referred to as a public network device), and the method includes: the public network device can first obtain an IPv6 address exposure license from the private network device, and after obtaining the IPv6 address exposure license, the IPv6 address of the private network device and the identifier of the private network device can be obtained from the private network device deployed with the network service. Afterwards, when an address query request for the IPv6 address of the private network device deployed with the network service is received from the client, the private network device can provide the IPv6 address of the private network device of the network service to the client according to the identifier of the private network device, wherein the address query request includes the identifier of the private network device.
[0035] Through the above method, when the client needs to access a private network device, it can first obtain the IPv6 address of the private network device from the public network device, and then communicate with the private network device based on the IPv6 address of the private network device, thereby realizing the interconnection between the private network and other networks (such as the public network or other private networks).
[0036] In one possible implementation, the IPv6 address exposure permission obtained by the public network device from the private network device may be requested by the public network device to the private network device. For example, the public network device may send an address acquisition request to the private network device, and the address acquisition request is used to request the IPv6 address of the private network device. Afterwards, the public network device may receive an address acquisition response from the private network device, and the address acquisition response is used to agree to expose the IPv6 address, and the address acquisition response includes the IPv6 address and the identifier of the private network device.
[0037] Through the above method, the public network device can request an IPv6 address from the private network device, so that the IPv6 address can be provided to the client that needs to access the private network device later.
[0038] In a possible implementation, the address acquisition request may also indicate a first preferential policy, which is fee discount information provided to private network devices for private network devices. The number of first preferential policies is not limited here, and may be one or more, so that the private network device can choose from multiple first preferential policies.
[0039] Through the above method, in order to deploy network services in a private network device and expose the IPv6 address of the private network device, the public network device can provide some preferential policies so that the private network device can provide IPv6 address exposure permission.
[0040] In one possible implementation, the IPv6 address exposure permission obtained by the public network device from the private network device may also be actively provided by the private network device. The public network device may receive the IPv6 address and the identifier of the private network device from the private network device. That is, the private network device provides the IPv6 address exposure permission by actively sending the IPv6 address and the identifier of the private network device.
[0041] Through the above method, the public network device actively provides IPv6 address exposure permission, which improves the initiative of the private network device and is applicable to other scenarios.
[0042] In a possible implementation, the public device can also send a second preferential policy after actively providing the IPv6 address exposure permission. The second preferential policy is the fee preferential information proposed by the private network device for the private network device. The number of second preferential policies is not limited here, and can be one or more, so that the public network device can choose from multiple second preferential policies.
[0043] Through the above method, private network devices can actively request the deployment of network services and expose IPv6 addresses, and can also express their own demands for fee discounts.
[0044] In a possible implementation, the public network device may also receive an updated IPv6 address or identifier of the private network device from the private network device, and update the locally stored IPv6 address or identifier of the private network device.
[0045] Through the above method, the public network device can obtain the updated IPv6 address or identifier to ensure that the latest and most accurate IPv6 address or identifier of the private network device can always be stored locally, so that a real and valid IPv6 address can be provided to the client.
[0046] In a fourth aspect, an embodiment of the present application provides a network intercommunication method based on a private network, which can be executed by a private network device in a private network. In this method, the private network device can provide an IPv6 address exposure permission to a device in a public network; then, the IPv6 address of the private network device and the identifier of the private network device are sent to the device in the public network. After that, the private network device can interact with the client for data, for example, it can receive a data message from the client, and the destination address of the data message is the IPv6 address of the private network device.
[0047] Through the above method, the private network device provides the IPv6 address of the private network device to the public network device, so that the client can access the private network device to interact with data, thereby realizing the interconnection between the private network device and devices in other networks.
[0048] In one possible implementation, the network service deployment license provided by the private network device to the device in the public network may be provided at the request of the public network device. For example, the private network device may receive an address acquisition request from the device in the public network, where the address acquisition request is used to request the IPv6 address of the private network device. The address acquisition request is also used to indicate the conditions that need to be faced after the IPv6 address is exposed. After the user confirms the conditions that need to be faced after the IPv6 address is exposed, the private network device sends an address acquisition response from the device in the public network. The address acquisition response is used to agree to expose the IPv6 address, and the address acquisition response includes the IPv6 address and the identifier of the private network device.
[0049] Through the above method, the private network device provides a Pv6 address at the request of the public network device, so that the public network device can subsequently provide the Pv6 address to the client.
[0050] In one possible implementation, the network service deployment license provided by the private network device to the device in the public network may also be actively provided by the private network device. For example, the private network device may send the IPv6 address and the identifier of the private network device to the device in the public network under the instruction of the user.
[0051] Through the above method, private network devices can actively request to expose Pv6 addresses, thereby improving the initiative of private network devices and being applicable to other scenarios.
[0052] In a possible implementation, when the private network device's own IPv6 address or identifier is updated, the private network device may send the updated IPv6 address or identifier to the device in the public network.
[0053] Through the above method, the private network device can provide the updated IPv6 address or identifier in a timely manner, ensuring that the public network device obtains the latest and most accurate IPv6 address or identifier of the private network device in a timely manner.
[0054] In the fifth aspect, the embodiment of the present application further provides a public network device, and the beneficial effects can be found in the description of the first aspect and will not be repeated here. The device has the function of implementing the behavior in the method example of the first aspect above. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the structure of the device includes a node management module, a service management module, and an address resolution module, and these modules can execute the corresponding functions in the method example of the first aspect above. Please refer to the detailed description in the method example for details, which will not be repeated here.
[0055] In the sixth aspect, the embodiment of the present application further provides a private network device, and the beneficial effects can be found in the description of the second aspect and will not be repeated here. The device has the function of implementing the behavior in the method example of the second aspect above. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the structure of the device includes a node agent module and a service agent module, and these modules can execute the corresponding functions in the method example of the second aspect above. Please refer to the detailed description in the method example for details, which will not be repeated here.
[0056] In the seventh aspect, the embodiment of the present application further provides a public network device. The beneficial effects can be found in the description of the third aspect and will not be repeated here. The device has the function of implementing the behavior in the method example of the third aspect above. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the structure of the device includes a node management module and an address resolution module, which can execute the corresponding functions in the method example of the third aspect above. Please refer to the detailed description in the method example for details, which will not be repeated here.
[0057] In the eighth aspect, the embodiment of the present application further provides a private network device, and the beneficial effects can be found in the description of the fourth aspect and will not be repeated here. The device has the function of implementing the behavior in the method example of the fourth aspect above. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the device includes node agent modules, which can execute the corresponding functions in the method example of the fourth aspect above. Please refer to the detailed description in the method example for details, which will not be repeated here.
[0058] In the ninth aspect, an embodiment of the present application further provides a computing device, which includes a processor and a memory, and may also include a communication interface. The processor executes the program instructions in the memory to execute the method provided by the first aspect or any possible implementation of the first aspect. The memory is coupled to the processor, which stores necessary program instructions and data. The communication interface is used to communicate with other devices, such as receiving the IPv6 address of a private network device, a service query request, sending a service query response, etc.
[0059] In the tenth aspect, an embodiment of the present application further provides a computing device, which includes a processor and a memory, and may also include a communication interface. Optionally, a display screen is also included. The processor executes the program instructions in the memory to execute the method provided by the second aspect or any possible implementation of the second aspect. The memory is coupled to the processor and contains necessary program instructions and data. The communication interface is used to communicate with other devices, such as sending an IPv6 address, receiving a service request, and feeding back a service response. The display screen is used to display information to a user when triggered by the processor.
[0060] In the eleventh aspect, an embodiment of the present application further provides a computing device, which includes a processor and a memory, and may also include a communication interface. The processor executes the program instructions in the memory to execute the method provided by the third aspect or any possible implementation of the third aspect. The memory is coupled to the processor, which stores necessary program instructions and data. The communication interface is used to communicate with other devices, such as receiving the IPv6 address or identifier of a private network device, an address query request, sending an address query response, etc.
[0061] In the twelfth aspect, the embodiment of the present application further provides a computing device, which includes a processor and a memory, and may also include a communication interface. Optionally, a display screen is also included. The processor executes the program instructions in the memory to execute the method provided by the fourth aspect or any possible implementation of the fourth aspect. The memory is coupled to the processor, and contains necessary program instructions and data. The communication interface is used to communicate with other devices, such as sending an IPv6 address or identifier, receiving a data message, etc. The display screen is used to display information to a user when triggered by the processor.
[0062] In a thirteenth aspect, the present application provides a computing device cluster, which includes at least one computing device. Each computing device includes a memory and a processor. The processor of at least one computing device is used to access the code in the memory to execute the method provided by any of the aforementioned aspects or any possible implementation of any of the aspects.
[0063] In a fourteenth aspect, the present application provides a non-transient readable storage medium, and when the non-transient readable storage medium is executed by a computing device, the computing device executes the method provided in the aforementioned first aspect or any possible implementation of the first aspect. The storage medium stores a program. The storage medium includes but is not limited to a volatile memory, such as a random access memory, a non-volatile memory, such as a flash memory, a hard disk drive (HDD), and a solid state drive (SSD).
[0064] In a fifteenth aspect, the present application provides a computer program product, the computer program product including computer instructions, when executed by a computing device, the computing device performs the method provided in the aforementioned first aspect or any possible implementation of the first aspect. The computer program product may be a software installation package, and when it is necessary to use the method provided in any of the aforementioned aspects or any possible implementation of any of the aspects, the computer program product may be downloaded and executed on a computing device.
[0065] In the sixteenth aspect, the present application also provides a computer chip, which is connected to a memory, and the chip is used to read and execute a software program stored in the memory, and execute the method provided in any of the preceding aspects or any possible implementation of any of the aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0066] Figure 1 A schematic diagram of the architecture of a system provided for this application;
[0067] Figure 2 A schematic diagram of a network intercommunication method based on a private network provided in this application;
[0068] Figures 3A to 3C A schematic diagram of a display interface provided by the present application and presented to a user;
[0069] Figures 4A to 4C A schematic diagram of a display interface provided by the present application and presented to a user;
[0070] Figure 5 A schematic diagram of a network intercommunication method based on a private network provided in this application;
[0071] Figure 6 A schematic diagram of the structure of a computer cluster provided for this application;
[0072] Figure 7 A schematic diagram of the structure of a computer cluster provided for this application. DETAILED DESCRIPTION
[0073] Before describing a network intercommunication method, device, and computer cluster based on a private network provided in an embodiment of the present application, some concepts involved in the embodiment of the present application are described first:
[0074] 1. Private Network
[0075] A private network refers to a network that enables intercommunication between devices within a specific scope. A private network is not a public network. It is a component of an individual or an organization and is used within a specific scope. The resources in the private network (such as storage resources, bandwidth resources, etc.) and the devices in the private network are owned by the individual or organization.
[0076] There are many types of network devices in private networks, including but not limited to: communication equipment, entertainment equipment, household appliances, lighting equipment, monitoring equipment, water, electricity, gas and heat meter equipment, home alarm devices, etc. Network devices in private networks (referred to as private network devices) are configured with network addresses, which can be regularly allocated to private network devices by operators. Based on the network address, private network devices can access devices in the public network.
[0077] 2. Public network
[0078] The public network, also known as the wide area network, allows devices in the wide area network to access devices on the Internet without restrictions.
[0079] The following is a description of a system architecture applicable to a network intercommunication method based on a private network provided in an embodiment of the present application. Figure 1 As shown, it is a schematic diagram of a system architecture provided in an embodiment of the present application. The system architecture may include network devices deployed in a private network 100 (the network devices may be referred to as private network devices) and devices deployed in a public network 200 (the devices in the public network 200 may also be referred to as public network devices). The embodiment of the present application does not limit the number of private networks 100 and the number of home network devices in the private network 100. Figure 1 Only three private networks 100 are illustrated for example. To distinguish different private networks 100 , the three private networks 100 are named private network 100A, private network 100B, and private network 100C, respectively.
[0080] The private network 100 may include one or more private network devices. The embodiment of the present application does not limit the type of private network devices. Private network devices include but are not limited to: modems, routers, notebooks, computers, etc.
[0081] In the embodiment of the present application, a private network device in the private network 100 can realize the connection with the public network and the function of providing network services to the outside. In actual applications, the function of connecting to the public network and the function of providing network services to the outside can be deployed in multiple private network devices in the private network 100 and completed by the cooperation of multiple private network devices.
[0082] Figure 1 In the example, the private network device in the private network 100A is identified as the private network device 110 , the private network device in the private network 100B is identified as the private network device 120 , and the private network device in the private network 100C is identified as the private network device 130 .
[0083] The following takes the private network device 110 as an example to describe the modules included in the private network device:
[0084] The private network device 110 includes a node agent module 111 and a service agent module 112 .
[0085] The node agent module 111 is used to connect the private network device 110 to the public network 200. For example, it can actively provide the Internet Protocol version 6 (IPv6) address of the private network device 110 to the public network device 210 in the public network 200, or provide the IPv6 address of the private network device 110 at the request of the public network device 210. It can also receive access requests from network devices in other networks (such as private network devices or other public network devices in other private networks 100), and feedback access responses, etc.
[0086] The service proxy module 112 can deploy network services in the private network device 110 at the request of the public network device 210 and when the user agrees to the request of the public network device 210. The service proxy module 112 can also manage the network services deployed on the private network device 110, including but not limited to: the operation and update of the network services, and is also used to provide network services to the service objects of the network services. The service objects of the network services (i.e., the objects receiving the network services) can be other private network devices deployed in the private network 110A, private network devices deployed in other private networks 100, or public network devices.
[0087] The public network may include one or more public network devices 210. The embodiment of the present application does not limit the device form of the public network device 210. For example, the public network device 210 may be a server, a virtual machine in a server, or a software device deployed on a server or a virtual machine.
[0088] In the embodiment of the present application, a public network device 210 in the public network is used as an example for explanation. The public network device 210 can connect to the private network device in the private network 100 and manage the private network device 110 connected thereto. For example, after obtaining the network service deployment license of the private network device, the public network device 210 can deploy the network service on the private network device; and query the IPv6 address of the private network device where the network service is located on the client, and provide the IPv6 address of the private network device to the client. After obtaining the IPv6 address exposure license of the private network device, the IPv6 address of the private network device is obtained, and when the client needs to query the IPv6 address of the private network device, the IPv6 address of the private network device is fed back.
[0089] In actual applications, the functions of the above-mentioned public network device 210 can also be deployed in multiple public network devices 210 in the public network and implemented by the cooperation of multiple public network devices 210.
[0090] The following takes the public network device 210 as an example to describe the modules included in the public network device 210:
[0091] The public network device 210 includes a node management module 211 , an address resolution module 212 , and a service management module 213 .
[0092] The node management module 211 is used to manage the private network device 110 connected to the public network device 210, including but not limited to: obtaining the IPv6 address exposure permission of the private network device, the identification and IPv6 address of the private network device 110, saving the correspondence between the identification and IPv6 address of the private network device 110, and updating the correspondence between the identification and IPv6 address of the private network device 110.
[0093] The address resolution module 212 is used to receive an address query request from other devices (such as other public network devices and private network devices in the private network 100), the address query request is used to request the IPv6 address of the private network device, and the address query request includes the identifier of the private network device. The address resolution module 212 can determine the IPv6 address of the private network device according to the identifier of the private network device based on the correspondence between the identifier of the private network device and the IPv6 address, and feed back an address query response to other devices, the address query response including the IPv6 address of the private network device.
[0094] The service management module 213 is used to receive the network service program, and after obtaining the network service deployment license from the private network device, deploy the network service program on one or more private network devices connected to the public network device 210, and record the IPv6 address of the private device that deploys the network service. The server management module 123 can also manage the network service program deployed on the one or more private network devices. For example, update the network service program on the one or more private network devices.
[0095] The address resolution module 212 is also used to receive service query requests from other devices (such as other public network devices and private network devices in the private network 100), and the service query request is used to request the IPv6 address of the private network device that provides the network service. The address resolution module 122 can determine the IPv6 address of the private network device that deploys the network service, and feedback the service query response to other devices, and the service query response includes the IPv6 address of the private network device.
[0096] Combine the following Figure 2 Taking the interaction between the private network device 110 and the public network device 210 as an example, a network intercommunication method based on the private network 100 provided in the embodiment of the present application is described. Figure 2 The method includes two parts. One is a method for the private network device 110 to interact with other devices outside the private network 100, see steps 201 to 206, and the other is a method for the private network 100 to deploy network services and provide network services, see steps 206 to 213:
[0097] Step 201: The node agent module 111 sends a registration request to the node management module 211, the registration request includes the identifier of the private network device 110 and the IPv6 address of the private network device 110, and the registration request is used to request registration with the public network device 210. Here, the node agent module 111 only sends the identifier of the private network device 110 and the IPv6 address of the private network device 110 by sending a registration request. In actual applications, the node agent module 111 can also send the identifier of the network device 110 and the IPv6 address of the private network device 110 in other message carriers. Any method that can send the identifier of the private network device 110 and the IPv6 address of the private network device 110 is applicable to the embodiments of the present application.
[0098] The identifier of the private network device 110 is information that can uniquely identify the private network device 110. The embodiment of the present application does not limit the type of the identifier of the private network device 110. For example, the identifier of the private network device 110 can be a number pre-configured for the private network device 110 in the private network 100 or the public network 200, or a device number of the private network device 110, or an identifier assigned to the private network device 110 by the public network 200 (such as a device in the public network) or an operator according to a preset constraint rule and generation method. Any information that can uniquely identify the private network device 110 can be used as the identifier of the private network device 110.
[0099] The embodiment of the present application does not limit the timing of the node agent module 111 executing step 201. For example, when the private network 100A is successfully networked, the node agent module 111 can directly execute step 201. For another example, the node agent module 111 can also execute step 201 after determining that it is necessary to communicate with the public network device 210 or other private network devices in the private network 100. For another example, the node agent module 111 can also execute step 201 under the instruction of the public network 200 (such as the instruction issued by the public network device 210), such as the need to register. For another example, the node agent module 111 can also execute step 201 under the trigger of the user, such as the user triggers the process of starting the registration with the public network device 210.
[0100] In one possible implementation, before the node agent module 111 provides the public network device 210 with the identifier of the private network device 110 and the IPv6 address of the private network device 110, the node agent module 110 may first provide an IPv6 address exposure permission, that is, the node agent module 110 needs to first allow its own IPv6 address to be exposed, and the IPv6 address exposure permission may be actively provided by the node agent module 111, or may be provided at the request of the public network device 210.
[0101] The following describes these two possible situations respectively:
[0102] (1) The node agent module 111 actively provides IPv6 address exposure permission.
[0103] The node agent module 111 determines the need to communicate with other private networks or public networks outside the private network 110A under the user's instruction. For example, the private network device 110 can provide the user with the option of communicating with other private networks or public networks outside the private network 110A, such as the private network device 110 can communicate with other private networks or public networks outside the private network 110A through Figure 3A The display interface shown asks the user whether it is necessary to communicate with other private networks or public networks outside the private network 110A. After the user clicks "Yes", it is determined that it is necessary to communicate with other private networks or public networks outside the private network 110A. The node agent device 111 can also communicate with other private networks or public networks outside the private network 110A. Figure 3B The displayed interface reminds the user whether to confirm that the IPv6 address of the private network device 110 needs to be exposed, and the situation faced by exposing the IPv6 address of the private network device 110, such as the possibility of being attacked will increase, resources may be occupied or consumed, etc. After the user clicks "Confirm", it is determined that it is necessary to communicate with other private networks or public networks outside the private network 110A, and the IPv6 address of the private network device 110 can be exposed.
[0104] The premise of communication is that the other end of the communication needs to know the IPv6 address of the private network device 110. After determining that it needs to communicate with other private networks or public networks outside the private network 110A, the node agent module 110 can send a registration request or the identifier of the private network device 110 and the IPv6 address of the private network device 110 to the public network device 210.
[0105] The IPv6 address exposure permission may be explicit information, such as indication information 1, which indicates consent to expose the IPv6 address of the private network device 110. For example, the node agent module 111 may send the indication information 1 to the public network device 210 under the instruction of the user, and send the identification of the private network device 110 and the IPv6 address of the private network device 110 at the same time or after sending the indication information 1. The indication information 1 may also be carried in the registration request. The IPv6 address exposure permission may be implicit information, such as as long as the public network device 210 receives the registration request, or receives the identification of the private network device 110 and the IPv6 address of the private network device 110, it indicates that the private network device 210 agrees to expose the IPv6 address exposure permission. That is, the identification of the private network device 110 and the IPv6 address of the private network device 110 may implicitly indicate the IPv6 address exposure permission.
[0106] When the node agent module 111 actively provides IPv6 address exposure permission, it can also provide preferential policies, which are fee preferential information for the private network device, such as fee discounts or fee reductions, etc. The node agent module 111 can display selectable preferential policies to the user. After detecting the user's selection, the node agent module 111 can send the user's selected preferential policy to the public network device 210.
[0107] (2) The node agent module 111 provides IPv6 address exposure permission at the request of the public network device 210.
[0108] The public network device 210 may send an address acquisition request to the node agent module 111 to request the IPv6 address of the private network device. The address acquisition request may also indicate the situation to be faced after the IPv6 address is exposed.
[0109] After receiving the address acquisition request, the node agent module 111 can display the following information to the user: Figure 3C The display interface shown in the figure informs the public network device of the IPv6 address for requesting the private network device and the situation to be faced after the IPv6 address is exposed. After the user clicks confirm, the node agent module 111 determines that the user agrees to provide the IPv6 address of the private network device, and sends a registration request to the public network device 210 or an address acquisition response carrying the identification of the private network device 110 and the IPv6 address of the private network device 110.
[0110] The address acquisition request may also indicate a preferential policy for agreeing to expose the IPv6 address. The node agent module 111 may display the preferential policy to the user through a display interface. If there are multiple preferential policies, the user may also select a preferential policy. The preferential policy selected by the user may be carried in the address acquisition response.
[0111] For instructions on IPv6 address exposure permission, please refer to the above content and will not be repeated here.
[0112] It should be noted that the embodiments of the present application do not limit the manner in which the public network device 210 sends an address acquisition request. For example, the address acquisition request may be a request that the public network device 210 sends alone to the node agent module 111, or it may be address acquisition information that the public network device 210 pushes to the node agent module 111 periodically or irregularly. The address acquisition information may be displayed on a private network device, and a user may view and confirm the information to provide permission for IPv6 address exposure.
[0113] Step 202 : After receiving the registration request, the node management module 211 may save the identifier of the private network device 110 and the IPv6 address of the private network device 110 , and establish and save the correspondence between the identifier of the private network device 110 and the IPv6 address of the private network device 110 .
[0114] The node management module 211 can receive a registration request sent by any private network device connected to the public network device 210, save the identification of each private network device and the IPv6 address of the private network device, and establish and save the correspondence between the identification of each private network device and the IPv6 address of the private network device.
[0115] In addition to sending the registration request to the node management module 211, the node agent module 111 can also send the update request to the node management module 211 when the identifier of the private network device 110 or the IPv6 address of the private network device 110 is updated. The update request can carry the updated identifier of the private network device 110 or the IPv6 address of the private network device 110.
[0116] After receiving the update request, the node management module 211 can use the updated identifier of the private network device 110 or the IPv6 address of the private network device 110 carried in the update request to update the saved identifier of the private network device 110 or the IPv6 address of the private network device 110, and update the correspondence between the identifier of the private network device 110 and the IPv6 address of the private network device 110.
[0117] After executing step 201 and step 202, the private network device 110 is registered in the public network device 210, and the public network device 210 stores the corresponding relationship between the identifier of the private network device 110 and the IPv6 address of the private network device 110. The following takes the device accessing the private network device 110 as the first client as an example to explain the method of accessing the private network device 110, see steps 203 to 206. The first client can be the public network device 210, or a private network device in another private network 100.
[0118] Step 203: The first client sends an address query request to the address resolution module 212. The address query request is used to request to query the IPv6 address of the private network device 110. The address query request includes the identifier of the home private address.
[0119] When the first client needs to access the private network device 110, such as when the first client needs to request data from the private network device 110, or when the first client needs to send data to the private network device 110, the first client needs to first obtain the IPv6 address of the private network device 110. Since the IPv6 address of the private network device 110 may change, the first client may first query the IPv6 address of the private network device 110, that is, initiate an address query request to the address resolution module 212, so as to be able to correctly access the private network device 110 later.
[0120] The embodiment of the present application does not limit the manner in which the first client obtains the identifier of the private network device 110 . For example, the identifier of the private network device is obtained by the first client through a query service, or the first client pre-stores the identifier of the private network device 110 locally.
[0121] Step 204 : after receiving the address query request, the address resolution module 212 determines the IPv6 address of the private network device 110 based on the correspondence between the identifier of the private network device stored in the node management module 211 and the IPv6 address of the private network device.
[0122] The address resolution module 212 receives the address query request and can directly determine the IPv6 address of the private network device 110 based on the correspondence between the identifier of the private network device and the IPv6 address of the private network device stored in the node management module 211; the address resolution module 212 can also first verify the first client, such as verifying the identity of the first client and verifying whether the first client has the authority to query the private network device 110. After the verification is passed, the IPv6 address of the private network device 110 is determined based on the correspondence between the identifier of the private network device and the IPv6 address of the private network device stored in the node management module 211.
[0123] The method in which the address resolution module 212 verifies the first client is not limited here, and one of them is listed below:
[0124] The address query request may carry the identity information of the first client, which may be part or all of the following information: the identifier of the first client, and information about the network to which the first client belongs (such as the private network 100 or the public network).
[0125] The address resolution module 212 verifies the first client based on the identity information of the first client. For example, the address resolution module 212 can determine whether the identifier of the first client belongs to an identifier set, which is an identifier set of devices that are allowed to access the private network device 110. If the identifier of the first client belongs to the identifier set, the verification succeeds, otherwise the verification fails. For another example, the address resolution module 212 can determine whether the network to which the first client belongs is a network that is allowed to access the private network device 110. If the network to which the first client belongs is a network that is allowed to access the private network device 110, the verification succeeds, otherwise the verification fails.
[0126] If the address resolution module 212 fails to authenticate the first client, the address resolution module 212 may reject the address query request, such as by feeding back a query rejection response.
[0127] If the address resolution module 212 successfully authenticates the first client, the address resolution module 212 may execute step 205 after querying the IPv6 address of the private network device 110 .
[0128] Step 205 : the address resolution module 212 sends an address query response to the first client, where the address query response includes the IPv6 address of the private network device 110 .
[0129] Step 206 : The first client accesses the private network device 110 based on the IPv6 address of the private network device 110 .
[0130] When the first client needs to request data from the private network device 110 , the first client may send a data request to the private network device 110 . The data request is used to request data from the private network device 110 . The destination address of the data request is the IPv6 address of the private network device 110 .
[0131] When the first client needs to send data to the private network device 110 , the first client can send a data transmission message to the private network device 110 . The data transmission message is used to transmit data to the private network device 110 . The destination address of the data transmission message is the IPv6 address of the private network device 110 .
[0132] Through steps 201 to 206, devices outside the private network 100A can interact with the private network device 110 in the private network 100A. In order to further utilize the network resources in the private network 100A, such as bandwidth, etc., the private network 100 can also deploy network services to provide network services to the public network device 210 or other private networks 100 (such as private network devices in other private networks 100), see steps 207 to 213 for details. In steps 207 to 213, the second client is used as an example to publish network services to the public network device 210, and the third client is used as an example to request network services. The second client and the third client can be the public network device 210 or private network devices in other private networks 100. The first client, the second client, and the third client can be the same client or different clients.
[0133] Step 207: the second client sends a service deployment request to the service management module 213. The service deployment request is used to request the deployment of the network service. The service deployment request includes the program of the network service.
[0134] The number of network service programs included in the service deployment request is not limited here, and may be one network service program or multiple network service programs.
[0135] Step 208: After receiving the first service deployment request, the service management module 213 determines a private network device that can deploy the network service. The embodiment of the present application does not limit the number of the private network devices, which can be one or more. Here, the determined private network device is private network device 110 for example.
[0136] When determining the private network device 110 that can deploy the network service, the service management module 213 can determine the private network device that needs to deploy the network service based on the idle resources of each private network device connected to the public network device 210, such as the idle bandwidth of the private network device, idle virtual machines, etc. For example, the service management module 213 can preferentially select the private network device 110 with the most idle resources as the private network device that can deploy the network service.
[0137] When determining the private network device 110 that can deploy the network service, the service management module 213 can also determine the performance of the private network device based on the performance of each private network device 110 connected to the public network device 210. For example, the service management module 213 can determine the performance of the private network device based on the bandwidth (uplink bandwidth and downlink bandwidth), central processing unit, memory, disk and other indicators of the private network device and the current status of the bandwidth (uplink bandwidth and downlink bandwidth), central processing unit, memory, and disk, wherein the bandwidth (uplink bandwidth and downlink bandwidth), central processing unit, memory, disk and other indicators of the private network device and the current status of the bandwidth (uplink bandwidth and downlink bandwidth), central processing unit, memory, and disk can be reported to the service management module by the private network device 110. For example, the service management module 213 can preferentially select the private network device 110 with the best performance as the private network device that can deploy the network service.
[0138] It should be noted that, for one network service, the service management module 213 may also determine multiple private network devices, that is, the same network service is deployed in the multiple private network devices.
[0139] When the first service deployment request received by the service management module 213 includes programs for multiple network services, the above-mentioned method can be used to separately determine the private network devices for deploying each network service. The private network device determined by the service management module 213 can be one or more, that is, the home private device can deploy some or all of the multiple network services.
[0140] Optionally, the service management module 213 may also decompose the network service into multiple network sub-services, that is, the service management module 213 may decompose the program of the network service into multiple network sub-services.
[0141] For example, if the network service is a speech recognition service, the speech recognition service can be divided into three network sub-services: speech noise reduction, background sound removal, and speech-to-text conversion. For another example, if the network service is an image-based object recognition service, the image-based object recognition service can be divided into three network sub-services: extracting feature images, selecting candidate objects based on feature images, and identifying objects from candidate objects.
[0142] When determining the private network device that can deploy the network service, the service management module 213 can determine the private network device that can deploy each network sub-service. The private network device determined by the service management module 213 can be one or more, that is, the home private device can deploy some or all of the multiple network sub-services.
[0143] After determining the private network device 110 that can deploy the network service, the service management module 213 can establish and save the correspondence between the identifier of the network service and the identifier of the private network device 110. If the network service is deployed in multiple private network devices (such as the network service is disassembled into multiple network sub-services, and the multiple network sub-services are deployed in multiple private network devices), the service management module 213 can save the correspondence between the identifier of the network service and the identifiers of the multiple private network devices 110.
[0144] Among them, the embodiments of the present application do not limit the specific type of the identifier of the network service. For example, the identifier of the network service can be an identifier of an application interface that connects to the network service, or it can be the name of the network service. Any information that can identify the network service is applicable to the embodiments of the present application.
[0145] If the service management module 213 has further disassembly operations on the network service, after determining the private network devices that can deploy each network sub-service, the service management module 213 can also establish and save the corresponding relationship between the identifier of the network sub-service and the identifier of the private network device. The identifier of the network sub-service can be configured by the service management module 213 itself, such as being configured based on the identifier of the network service.
[0146] For example, the identifier of the network service is AAA, and the network service is decomposed into three network sub-services. The service management module 213 can configure the identifiers of the network sub-services to be AAA-1, AAA-2, and AAA-3 respectively.
[0147] It is worth noting that the public network device 210 can store the following correspondences:
[0148] The correspondence between the identifier of the private network device and the IPv6 address of the private network device, the correspondence between the identifier of the network service and the identifier of the private network device, and the correspondence between the identifier of the network sub-service and the identifier of the private network device.
[0149] These correspondences are further processed, and the service management module 213 can also generate a correspondence between the identifier of the network service and the IPv6 address of the private network device. If there is a further disassembly operation on the network service, the service management module 213 can also generate a correspondence between the identifier of the network sub-service and the IPv6 address of the private network device. In this case, the public network device 210 can save the following correspondences: the correspondence between the identifier of the private network device and the IPv6 address of the private network device, the correspondence between the identifier of the network service and the IPv6 address of the private network device. If there is a further disassembly operation on the network service, the public network device 210 can also save the correspondence between the identifier of the network sub-service and the IPv6 address of the private network device, or only save the correspondence between the identifier of the private network device and the IPv6 address of the private network device and the correspondence between the identifier of the network sub-service and the IPv6 address of the private network device.
[0150] Step 209: the service management module 213 sends a service deployment instruction to the private network device 110, wherein the service deployment instruction includes the program of the network service.
[0151] It should be noted that, before executing step 209, the service management module 213 may also pre-acquire the network service deployment license of the private network device 110. Several methods for acquiring the network service deployment license are listed below:
[0152] Method 1: The private network device 110 can sign an agreement in advance, which agrees to deploy network services in the private network device 110, and the information of the agreement signed by the private network device 110 can be pre-stored in the public network device 210. The service management module 210 can determine through the agreement that the private network device 110 agrees to deploy network services, that is, obtains the network service deployment license of the private network device 110.
[0153] Method 2: The private network device 110 (service agent module 212) actively provides the network service deployment permission.
[0154] The service agent module 212 determines that the user can allow the private network device 110 to occupy resources to deploy network services under the user's instruction. For example, the private network device 110 can provide the user with options for deploying network services, such as the private network device 110 can be configured as follows: Figure 4A The display interface shown asks the user whether to deploy the network service, and agrees to deploy the network service to allow the requested preferential policy. The preferential policy can be a fee preferential information for private equipment, such as rental cost reduction, rental discount, service fee discount, etc.
[0155] After the user clicks "Yes" and selects the preferential policy, it is determined that the network service can be deployed on the private network device 110, and the preferential policy selected by the user. Figure 4B The displayed interface reminds the user whether to confirm the deployment of the network service, and the situation faced after the deployment of the network service, such as the possible occupation or consumption of resources. After the user clicks "Confirm", the resource occupation permission is sent to the public network device, and the preferential policy selected by the user can also be sent. The resource occupation permission indicates that the resources of the private network device are allowed to be occupied to deploy the network service. The resource occupation permission can be understood as another form of network service deployment permission.
[0156] Resource occupation permission and network service deployment permission may be explicit information, such as indication information 2, which indicates consent to deploy network services, such as the service agent module 212 can send the indication information 1 to the public network device 210 under the instruction of the user. IPv6 address exposure permission may be implicit information, such as when executing step 209, after the service management module 213 sends a service deployment instruction to the private network device 110, the service agent module 212 sends a service deployment success response, indicating that the network service is deployed successfully, indicating that the private network device 110 agrees to deploy the network service or allows the private network device 110's resources to be occupied.
[0157] Method three: the service management module 213 may request the private network device 110 (service proxy module 212) for permission to deploy the network service.
[0158] The service management module 21 may send a second service deployment request to the service proxy module 212 to request the deployment of the network service. The second service deployment request may also indicate the situation faced after the deployment of the network service, such as resources that may be occupied or consumed. The second service deployment request may also carry one or more preferential policies, which may be fee preferential information for private devices, such as rental cost reduction, rental discount, service fee discount, etc.
[0159] After receiving the second service deployment request, the service agent module 212 may display the following information to the user: Figure 4C The display interface shown is used to inform the user that the public network device requests to deploy a network service on the private network device, and can also inform the user of the situation faced after the network service is deployed and that the service deployment request can also carry one or more preferential policies.
[0160] After the user clicks "Confirm" and selects a preferential policy (when there are multiple preferential policies for the user to choose from), the service proxy module 212 determines that the user agrees to deploy the network service on the private network device, and sends a service deployment response to the public network device 210. The service deployment response is used to agree to deploy the network service, and the service deployment response can be understood as a form of network service deployment permission. If the user selects a preferential policy, the service deployment response can also carry the preferential policy selected by the user.
[0161] It should be noted that the embodiment of the present application does not limit the manner in which the public network device 210 sends the second service deployment request. For example, the second service deployment request can be a request that the public network device 210 sends alone to the node agent module 111, or it can be service deployment information that the public network device 210 pushes to the node agent module 111 regularly or irregularly. The information can prompt the user whether to agree to deploy the network service. The information can also include the multiple preferential policies. The service deployment information can be displayed on the private network device, and the user can view the information and confirm the information to provide network service deployment permission.
[0162] Step 210: After receiving the service deployment instruction, the service agent module 212 in the private network device 110 obtains the program of the network service from the service deployment instruction and runs the network service, that is, installs the program of the network service.
[0163] It should be noted that in step 209 and step 210, the program carried by the service deployment instruction is the program of the network service. In actual applications, if the service management module 213 has further disassembly operations on the network service, and determines that one or more network sub-services need to be deployed in the group's private network device 110, then the service deployment instruction carries the program of the one or more network sub-services.
[0164] It should be noted that when a network service is broken down into multiple network sub-services and the multiple network sub-services are deployed in multiple private network devices, for any private network device among the multiple private network devices, the private network device can save the IPv6 addresses of the private network devices other than itself among the multiple private network devices. For example, the IPv6 address of the private network device saved by the private network device can be the IPv6 address of the private network device where the network sub-service that performs the next step of processing the data generated by the network sub-service when running the private network device is located.
[0165] In addition to determining the private network devices 110 that can deploy the network service or the network sub-service, the service management module 213 can also update the network services deployed in the private network devices 110 .
[0166] There are many scenarios for updating the network services deployed in the private network device 110, and several of them are listed below:
[0167] Scenario 1: Modify the program of network service.
[0168] When determining that the program of the network service needs to be modified, the service management module 213 may send a first service update instruction to the private network device 110 that deploys the network service. The first service update instruction carries the modified program of the network service.
[0169] After receiving the first service update instruction, the service agent module 212 in the private network device 110 obtains the modified program of the network service from the first service update instruction and installs the modified program of the network service.
[0170] There are many situations in which the service management module 213 determines that the program of the network service needs to be modified. For example, the second client can send a service update request, and the service update request carries the identifier of the network service and the modified program of the network service. After receiving the service update request, the service management module 213 determines that the program of the network service needs to be modified. For another example, a user can operate on the public network device 210 to trigger the program modification process of the network service. For example, the public network device 210 can provide a specific user with the authority to view and modify the program of the network service. After the specific user views the program of the network service through the public network device 210, the specific user can modify the program of the network service. After detecting the user's modification operation on the program of the network service, the service management module 213 can determine that the program of the network service needs to be modified.
[0171] Scenario 2: Deleting the network service deployed in the private network device 110.
[0172] When determining that the network service does not need to be deployed on the private network device 110 , the service management module 213 may send a second service update instruction to the private network device 110 that deploys the network service, where the second service update instruction instructs uninstallation of the network service.
[0173] After receiving the second service update instruction, the service agent module 212 in the private network device 110 deletes the locally installed program of the network service.
[0174] There are many situations in which the service management module 213 determines that the network service does not need to be deployed on the private network device 110. For example, the second client can send a service termination request, which carries the identifier of the network service. The service termination request indicates to terminate the network service. After receiving the service termination request, the service management module 213 determines that the network service does not need to be deployed on the private network device 110. For another example, when the service management module 213 learns that some components of the private network device 110 currently deploying the network service have failed or there are potential safety hazards, it can determine that the network service does not need to be deployed on the private network device 110; for another example, the user can operate on the public network device 210 to trigger the program deletion process of the network service. For example, the public network device 210 can provide a specific user with the authority to view and delete the program of the network service. After the specific user views the program of the network service through the public network device 210, the specific user can delete the program of the network service. After detecting the user's deletion operation on the program of the network service, the service management module 213 can determine that the network service does not need to be deployed.
[0175] The service management module 213 may also delete the correspondence between the identifier of the network service and the identifier (or IPv6 address) of the private network device 110 .
[0176] Scenario 3: Migrate the network services deployed in the private network device 110.
[0177] When determining the network service deployed in the migrated private network device 110, the service management module 213 determines the target private network device on which the network service needs to be deployed. The private network device 110 currently deployed with the network service is the source private network device. The service management module 213 can send a second service update instruction to the source private network device and a third service update instruction to the target private network device. The third service update instruction carries the program of the network service.
[0178] The operation of the source private network device receiving the second service update instruction is similar to the operation of the private network device 110 receiving the second service update instruction in scenario 3, and the details can be referred to the above description, which will not be repeated here. The operation of the target private network device receiving the third service update instruction is similar to the operation performed after the private network device 110 receives the service deployment instruction in step 210, and the details can be referred to the above description, which will not be repeated here.
[0179] There are many situations in which the service management module 213 determines to migrate the network service deployed in the private network device 110. For example, when the service management module 213 learns that some components in the private network device 110 currently deploying the network service have failed or there are security risks, it can determine that the network service needs to be migrated. For example, the user can operate on the public network device 210 to trigger the migration process of the network service. For example, the public network device 210 can provide a specific user with the permission to view and modify the deployment location of the network service. After the specific user views the program of the network service through the public network device 210, the deployment location of the network service can be modified. After detecting the user's modification operation on the deployment location of the network service, the service management module 213 can determine that the network service needs to be migrated.
[0180] The service management module 213 may also update the correspondence between the identifier of the network service and the identifier (or IPv6 address) of the private network device 110, and update the identifier or IPv6 address of the private network device 110 to the identifier or IPv6 address of the target private network device.
[0181] Step 211: the third client sends a service query request to the address resolution module 212. The service query request is used to request the IPv6 address of the private network device 110 providing the network service. The address query request includes the identifier of the network service.
[0182] When the third client obtains a network service, the third client needs to first obtain the IPv6 address of the private network device 110 on which the network service is deployed. Since the IPv6 address of the private network device 110 may change, the third client may first query the IPv6 address of the private network device 110, that is, initiate a service query request to the address resolution module 212, so that the private network device 110 can be correctly accessed later and the network service provided by the private network device 110 can be obtained.
[0183] Step 212 : after receiving the service query request, the address resolution module 212 may send a service query response to the third client according to the service query request, where the service query response includes the IPv6 address of the private network device 110 .
[0184] When the address resolution module 212 receives the service query request, it can determine the IPv6 address of the private network device 110 where the network service is deployed based on the locally stored correspondence and the identifier of the network service, carry the IPv6 address in the service query response, and send it to the third client.
[0185] It should be noted that if the network service is deployed on multiple private network devices at the same time, the address resolution module 212 can select a private network device and send a service query response to the third client, and the service query response can carry the IPv6 address of the selected private network device. The service query response carrying the IPv6 addresses of multiple private network devices can also be sent to the third client, so that the third client can select which private network device or devices provide the network service.
[0186] If the network service is decomposed into multiple network sub-services and deployed on multiple private network devices, the address resolution module 212 sends a service query response to the third client, and the service query response may carry the IPv6 address of the private network device where the network sub-service running first among the multiple private network devices is located, and the service query response may also instruct the multiple private network devices to cooperate in providing the network service. The service query response may also carry the IPv6 addresses of the multiple private network devices, and the service query response may also instruct the multiple private network devices to cooperate in providing the network service.
[0187] Step 213: The third client requests the private network device 110 to provide network services based on the IPv6 address of the private network device 110.
[0188] The third client requests the voice recognition service. The third client may initiate a service request to the private network device 110 with the destination address being the IPv6 address of the private network device 110 and the source address being the IPv6 address of the third client. The service request includes the voice data to be recognized.
[0189] After receiving the service request, the private network device 110 may perform voice recognition on the voice data to be recognized, and feed back text information after voice recognition to the third client.
[0190] It should be noted that if the network service is decomposed into multiple network sub-services, and the multiple network sub-services are deployed on multiple private network devices, if the service query response carries the IPv6 address of the private network device where the first network sub-service running in the multiple private network devices is located, the third client obtains the IPv6 address of the private network device 110 of the first network sub-service running, and the third client can initiate a service request to the private network device 110, and the service request can indicate a request for a voice recognition service. When the private network device 110 receives the service request, it runs the network sub-service based on the voice data to be recognized, and then transmits the data generated by the network sub-service and the IPv6 address of the third client to the private network device where the network sub-service for the next step of processing is located, until it is transmitted to the private network device where the last network sub-service running in the network service is located. When the private network device where the last network sub-service running is located ends, the text information after voice recognition can be fed back to the third client based on the IPv6 address of the third client.
[0191] If the service query response carries the IPv6 addresses of the multiple private network devices, after the third client obtains the IPv6 addresses of the multiple private network devices, the third client can initiate service requests to each private network device in turn to request the network sub-services deployed in the multiple private network devices respectively.
[0192] In such Figure 2 In the illustrated embodiment, the private network device 110 first provides an IPv6 address and an identifier of the private network device 110, and then deploys the network service under the instruction of the public network device 210. In actual applications, the private network device 110 may also directly deploy the network service under the instruction of the public network device 210, so that the private network device may only provide the IPv6 address of the private network device 110, and the public network device 210 may save the correspondence between the identifier of the network service and the IPv6 address of the private network device 110.
[0193] like Figure 5 As shown, a network intercommunication method based on a private network is provided in an embodiment of the present application, and the method includes:
[0194] Step 501: The second client sends a service deployment request to the service management module 213. The service deployment request is used to request the deployment of a network service. The service deployment request includes a program of the network service. The same as step 207. For details, please refer to the relevant description of step 207. No further description is given here.
[0195] Step 502: After receiving the first service deployment request, the service management module 213 determines a private network device that can deploy the network service.
[0196] Step 503 : the service management module 213 obtains the network service deployment permission from the service proxy module 112 in the private network device 110 .
[0197] The manner in which the service management module 213 obtains the network service deployment license can be found in the relevant description in step 209 and will not be repeated here.
[0198] Step 504 : the node management module 211 obtains the IPv6 address of the private network device 110 from the node agent module 111 .
[0199] It should be noted that the IPv6 address of the private network device 110 can be actively provided by the node agent module 111 to the node management module 211 when the service agent module 112 sends a network service deployment license to the service management module 213, or after the service agent module 112 sends a network service deployment license to the service management module 213, or it can be provided by the node agent module 111 at the request of the node management module 211. For example, the node management module 211 sends an address acquisition request to the node agent module 111 to request the IPv6 address of the private network device 110, and then the node agent module 111 sends a node acquisition response to the node management module 212, which carries the IPv6 address of the private network device 110.
[0200] The service management module 213 may also record the correspondence between the identifier of the network service and the IPv6 address of the private network device.
[0201] Step 505: The service management module 213 instructs the service agent module 112 in the private network device 110 to deploy the network service. For example, the service management module 213 may send a service deployment instruction to the service agent module 112, and the service deployment instruction includes the program of the network service. For details, please refer to the relevant description of step 209, which will not be repeated here.
[0202] Step 506: After receiving the service deployment instruction, the service agent module 212 in the private network device 110 obtains the program of the network service from the service deployment instruction and runs the network service, that is, installs the program of the network service. For details, please refer to the relevant description of step 210, which will not be repeated here.
[0203] The manner and scenario in which the service management module 213 updates the network services deployed in the private network device 110 can be found in the above description and will not be repeated here.
[0204] Step 507: The third client sends a service query request to the address resolution module 212. The service query request is used to query the IPv6 address of the private network device 110 providing the network service. The address query request includes the identifier of the network service. For details, please refer to the relevant description of step 211, which will not be repeated here.
[0205] Step 508: After receiving the service query request, the address resolution module 212 may send a service query response to the third client according to the service query request, and the service query response includes the IPv6 address of the private network device 110. For details, please refer to the relevant description of step 212, which will not be repeated here.
[0206] Step 509: The third client requests the private network device 110 to provide network services based on the IPv6 address of the private network device 110. For details, please refer to the relevant description of step 213, which will not be repeated here.
[0207] The following is a description of the system architecture to which the embodiments of the present application are applicable. Figure 6 As shown, a computer cluster provided in an embodiment of the present application includes at least one computing device 300, and a communication path is established between each computing device 300 through a communication network.
[0208] Each computing device 300 includes a bus 301 , a processor 302 , a communication interface 303 , and a memory 304 . The processor 302 , the memory 304 , and the communication interface 303 communicate with each other via the bus 301 .
[0209] The processor 302 may be composed of one or more general-purpose processors, such as a central processing unit (CPU), or a combination of a CPU and a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.
[0210] The memory 304 may include a volatile memory, such as a random access memory (RAM). The memory 304 may also include a non-volatile memory (NVM), such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid-state drive (SSD). The memory 304 may also include a combination of the above.
[0211] The memory 304 stores executable codes. The processor 302 can read the executable codes in the memory 304 to implement functions, and can also communicate with other computing devices through the communication interface 303 .
[0212] In an embodiment of the present application, the processor 302 can implement the functions of one or more modules of the public network device 210 (such as the node management module 211, the address resolution module 212, and one or more modules of the service management module 213). In this case, the memory 304 stores one or more modules of the public network device 210 (such as the node management module 211, the address resolution module 212, and one or more modules of the service management module 213).
[0213] In an embodiment of the present application, the processors 301 in multiple computing devices 300 can work in coordination to execute the method executed by the public network device in the network intercommunication method based on a private network provided in an embodiment of the present application.
[0214] The following is a description of the system architecture to which the embodiments of the present application are applicable. Figure 7 As shown, a computer cluster provided in an embodiment of the present application includes at least one computing device 400, and a communication path is established between each computing device 400 through a communication network.
[0215] Each computing device 400 includes a bus 401, a processor 402, a communication interface 403, and a memory 404. Optionally, the computing device 40 may further include a display screen 405. The processor 402, the memory 404, and the communication interface 403 communicate with each other via the bus 401.
[0216] The description of the processor 402 and the memory 404 refers to the description of the processor 302 and the memory 304 , which will not be repeated here.
[0217] The memory 404 stores executable code, and the processor 402 can read the executable code in the memory 404 to implement functions, and can also communicate with other computing devices through the communication interface 403. The processor 402 can also trigger the display screen 405 to display information to the user, such as in the embodiment of the present application. Figures 3A to 3C As well as Figures 4A to 4C The information included in the interface shown.
[0218] In an embodiment of the present application, the processor 402 can implement the functions of one or more modules of the private network device 110 (such as one or more modules in the node agent module 111 and the service agent module 112). In this case, the memory 404 stores one or more modules of the change device 400 (such as one or more modules in the node agent module 111 and the service agent module 112).
[0219] In an embodiment of the present application, the processors 401 in multiple computing devices 400 can work in coordination to execute the method executed by the private network device in the network intercommunication method based on a private network provided in an embodiment of the present application.
[0220] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0221] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0222] The above is only a specific embodiment of the present invention. Those skilled in the art may conceive of changes or substitutions based on the specific embodiments provided by the present invention, which should all be included in the protection scope of the present invention.
Claims
1. A network intercommunication method based on a private network, characterized in that: The method is applied to a device deployed in a public network, and the method includes: receiving a service deployment response or a resource occupation permission from a private network device, wherein the service deployment response is used to agree to deploy a network service, and the resource occupation permission is used to indicate that resources of the private network device are allowed to be occupied to deploy the network service; Instructing the private network device to deploy the network service, and recording the Internet Protocol version 6 IPv6 address of the private network device that deploys the network service; Receiving a service query request from a client, wherein the service query request is used to request an IPv6 address of the private network device deploying the network service; The IPv6 address of the private network device that provides the network service to the client.
2. The method according to claim 1, characterized in that Before receiving the service deployment response from the private network device, the method further includes: A service deployment request is sent to the private network device, where the service deployment request is used to request deployment of a network service.
3. The method according to claim 2, characterized in that The service deployment request is further used to indicate a first preferential policy, where the first preferential policy is fee preferential information provided to the private network device and targeted at the private network device.
4. The method according to claim 1, characterized in that The resource occupation permission further includes a second preferential policy, where the second preferential policy is fee preferential information proposed by the private network device and targeted at the private network device.
5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Instruct the private network device to update the network service.
6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Receive the updated IPv6 address of the private network device from the private network device, and update the locally stored IPv6 address of the private network device.
7. A network intercommunication method based on a private network, characterized in that: The method is applied to a private network device in a private network, and the method comprises: Sending a service deployment response or a resource occupation permission to a device in the public network, wherein the service deployment response is used to agree to deploy the network service, and the resource occupation permission is used to indicate that the resources of the private network device are allowed to be occupied to deploy the network service; Under the instruction of the device in the public network, deploy the network service and send the IPv6 address of the private network device to the device in the public network; receiving a service request from a client, wherein the service request is used to request the network service; According to the service request, a service response is fed back.
8. The method according to claim 7, characterized in that Before sending the service deployment response to the device in the public network, the method further includes: A service deployment request is received from a device in the public network, where the service deployment request is used to request deployment of a network service.
9. The method according to claim 8, characterized in that The service deployment request is further used to indicate a first preferential policy, where the first preferential policy is fee preferential information provided to the private network device and targeted at the private network device.
10. The method according to claim 7, characterized in that The resource occupation permission further includes a second preferential policy, where the second preferential policy is fee preferential information proposed by the private network device and targeted at the private network device.
11. The method according to any one of claims 7 to 10, characterized in that: The method further comprises: The network service is updated under the instruction of the device in the public network.
12. The method according to any one of claims 7 to 10, characterized in that: The method further comprises: Send the updated IPv6 address to the device in the public network.
13. A network intercommunication method based on a private network, characterized in that: The method is applied to a device deployed in a public network, and the method includes: After obtaining the IPv6 address exposure permission from the private network device, obtaining the IPv6 address of the private network device where the network service is deployed and the identifier of the private network device from the private network device; receiving an address query request from a client, the address query request being used to request an IPv6 address of the private network device where the network service is deployed, the address query request including an identifier of the private network device; The IPv6 address of the private network device is provided to the client, wherein the client is used to request the network service based on the IPv6 address of the private network device.
14. The method according to claim 13, characterized in that The obtaining of the IPv6 address exposure permission from the private network device includes: Sending an address acquisition request to the private network device, where the address acquisition request is used to request the IPv6 address of the private network device; An address acquisition response is received from the private network device, where the address acquisition response is used to agree to expose the IPv6 address, and the address acquisition response includes the IPv6 address and an identifier of the private network device.
15. The method according to claim 14, characterized in that The obtaining of the IPv6 address exposure permission from the private network device includes: Receive the IPv6 address of the private network device and the identifier of the private network device.
16. The method according to any one of claims 13 to 15, characterized in that: The method further comprises: Receive the updated IPv6 address or identifier of the private network device from the private network device, and update the locally stored IPv6 address or identifier of the private network device.
17. A network intercommunication method based on a private network, characterized in that: The method is applied to a private network device in a private network, and the method comprises: Provide IPv6 address exposure permission to devices on the public network; Sending the IPv6 address of the private network device and the identifier of the private network device to the device in the public network; A service request is received from a client, wherein the destination address of the service request is the IPv6 address of the private network device, and the service request is used to request a network service deployed by the private network device.
18. The method according to claim 17, characterized in that Providing a network service deployment license to a device in a public network includes: receiving an address acquisition request from a device in the public network, the address acquisition request being used to request an IPv6 address of the private network device, and the address acquisition request being used to indicate a condition to be faced after the IPv6 address is exposed; After the user confirms the situation that will be faced after the IPv6 address is exposed, an address acquisition response is sent from the device in the public network. The address acquisition response is used to agree to expose the IPv6 address. The address acquisition response includes the IPv6 address and the identifier of the private network device.
19. The method according to claim 18, characterized in that Providing a network service deployment license to a device in a public network includes: Under the instruction of the user, the IPv6 address and the identifier of the private network device are sent to the device in the public network.
20. The method according to any one of claims 17 to 19, characterized in that: The method further comprises: Send the updated IPv6 address or identifier to the device in the public network.
21. A public network device, characterized in that: The public network device is deployed in the public network, and includes: Node management module, used to obtain the IPv6 address of private network devices; A service management module, configured to receive a service deployment response or a resource occupation permission from the private network device, wherein the service deployment response is used to agree to deploy the network service, and the resource occupation permission is used to indicate permission to occupy the resources of the private network device to deploy the network service, and instruct the private network device to deploy the network service; and record the IPv6 address of the private network device that deploys the network service; The address resolution module is used to receive a service query request from a client, wherein the service query request is used to request the IPv6 address of the private network device that deploys the network service; and provide the IPv6 address of the private network device that provides the network service to the client.
22. A private network device, characterized in that: The private network device is deployed in a private network, and includes: The service proxy module is used to send a service deployment response or a resource occupation permission to a device in the public network, wherein the service deployment response is used to agree to deploy the network service, and the resource occupation permission is used to indicate that the resources of the private network device are allowed to be occupied to deploy the network service; and deploy the network service under the instruction of the device in the public network; A node agent module, used for sending the IPv6 address of the private network device to the device in the public network; The service proxy module is further used to receive a service request from a client, wherein the service request is used to request the network service; and to feed back a service response according to the service request.
23. A public network device, characterized in that: The public network device is deployed in the public network, and includes: A node management module, configured to obtain, after obtaining an IPv6 address exposure permission from a private network device, an IPv6 address of the private network device where a network service is deployed and an identifier of the private network device from the private network device; An address resolution module is used to receive an address query request from a client, wherein the address query request is used to request the IPv6 address of the private network device of the network service, and the address query request includes an identifier of the private network device; and provide the IPv6 address of the private network device of the network service to the client, wherein the client is used to request the network service based on the IPv6 address of the private network device.
24. A private network device, characterized in that: The private network device is deployed in a private network, and includes: A node agent module is used to provide an IPv6 address exposure permission to a device in a public network; and to send the IPv6 address of the private network device and an identifier of the private network device to the device in the public network; The node agent module is also used to receive a service request from a client, the destination address of the service request is the IPv6 address of the private network device, and the service request is used to request a network service deployed by the private network device.
25. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each computing device includes a processor and a memory; the memory in the at least one computing device is used to store computer program instructions; The processor in the at least one computing device calls the computer program instructions stored in the memory to execute the method according to any one of claims 1 to 6.
26. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each computing device includes a processor and a memory; the memory in the at least one computing device is used to store computer program instructions; The processor in the at least one computing device calls the computer program instructions stored in the memory to execute the method according to any one of claims 7 to 12.
27. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each computing device includes a processor and a memory; the memory in the at least one computing device is used to store computer program instructions; The processor in the at least one computing device calls the computer program instructions stored in the memory to execute the method according to any one of claims 13 to 16.
28. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each computing device includes a processor and a memory; the memory in the at least one computing device is used to store computer program instructions; The processor in the at least one computing device calls the computer program instructions stored in the memory to execute the method according to any one of claims 17 to 20.
Citation Information
Patent Citations
Method, device and system for interacting with private network
CN102447747A
