WO2024183048A1 - Connection establishment method and apparatus - Google Patents

Abstract

Provided are a connection establishment method and apparatus. The method comprises: a client device establishing a connection with a server device on the basis of public network address information, the public network address information comprising public network address information of the client device and/or public network address information of the server device.

Description

Connection establishment method and device Technical Field

The present application relates to the field of communication technology, and more specifically, to a method and device for establishing a connection.

Background Art

In the field of IoT communication, client devices and server devices can communicate based on the established connection. However, currently the connection between client devices and server devices needs to go through the cloud platform, resulting in high complexity of the connection.

Summary of the invention

The present application provides a method and device for establishing a connection. The following introduces various aspects of the present application.

In a first aspect, a method for establishing a connection is provided, comprising: a client device establishing a connection with a server device based on public network address information, wherein the public network address information includes the public network address information of the client device and/or the public network address information of the server device.

In a second aspect, a method for establishing a connection is provided, comprising: configuring a device to send public network address information of a server device to a client device, wherein the public network address information of the server device is used to establish a connection between the client device and the server device.

In a third aspect, a method for establishing a connection is provided, comprising: a public network server device sends public network address information of a server device, and the public network address information of the server device is used to establish a connection between the client device and the server device.

In a fourth aspect, a method for establishing a connection is provided, comprising: a server device establishes a connection with a client device based on public network address information, wherein the public network address information includes the public network address information of the client device and/or the public network address information of the server device.

In a fifth aspect, a client device is provided, comprising a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory to execute the method described in the first aspect.

In a sixth aspect, a configuration device is provided, comprising a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory to execute the method described in the second aspect.

In a seventh aspect, a public network server device is provided, comprising a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory to execute the method described in the third aspect.

In an eighth aspect, a server device is provided, comprising a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory to execute the method described in the fourth aspect.

In a ninth aspect, a device is provided, comprising a processor, configured to call a program from a memory to execute the method described in any one of the first to fourth aspects.

In a tenth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in any one of the first to fourth aspects.

In an eleventh aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in any one of the first to fourth aspects.

In a twelfth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in any one of the first to fourth aspects.

In a thirteenth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in any one of the first to fourth aspects.

The present application establishes a connection between a client device and a server device through the public network address information of the client device and/or the public network address information of the server device, so that the client device and the server device can be directly connected, thereby reducing the complexity of the connection.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a wireless communication system 100 to which an embodiment of the present application is applied.

FIG. 2 is a schematic diagram of a process of performing network configuration for a server-side device.

FIG3 is a model structure of an Internet of Things device to which an embodiment of the present application can be applied.

FIG4 is a schematic diagram of a process for performing key exchange based on the sigma protocol according to an embodiment of the present application.

FIG5 is a schematic flowchart of a method for establishing a connection provided in an embodiment of the present application.

FIG6 is a schematic flowchart of another method for establishing a connection provided in an embodiment of the present application.

FIG. 7 is a schematic flowchart of another method for establishing a connection provided in an embodiment of the present application.

FIG8 is a schematic diagram of a process for configuring a device to obtain a public network IP address of a public network server device provided in an embodiment of the present application.

FIG9 is a schematic diagram of a process for a client device to obtain a public network IP address of a public network server device from a configuration device according to an embodiment of the present application.

FIG10 is a process of allocating a public network IP address to a server-side device by a public network server device provided in an embodiment of the present application.

FIG. 11 is a schematic diagram of a process of establishing a connection between a client device and a server device provided in an embodiment of the present application.

FIG. 12 is a flow chart showing another configuration device provided in an embodiment of the present application for obtaining a public IP address of a server device from a public network server device.

FIG. 13 is a schematic diagram of a process of establishing a connection between another client device and a server device provided in an embodiment of the present application.

FIG. 14 is a schematic block diagram of a client device provided in an embodiment of the present application.

FIG. 15 is a schematic block diagram of a configuration device provided in an embodiment of the present application.

FIG16 is a schematic block diagram of a public network server device provided in an embodiment of the present application.

FIG. 17 is a schematic block diagram of a server device provided in an embodiment of the present application.

FIG. 18 is a schematic diagram of the structure of the device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solution in the present application will be described below in conjunction with the accompanying drawings. For ease of understanding, the following first introduces the system architecture applicable to the embodiment of the present application in conjunction with FIG. 1 .

FIG1 is a schematic diagram of a system architecture applicable to an embodiment of the present application. The system 100 shown in FIG1 may include a client device 110 , a configuration device (mediator) 120 , a cloud platform 130 and a server device 140 .

The client device 110 may be a device having a function of communicating with the cloud platform 130. In some implementations, the client device 110 may be provided with a client, which may be used to communicate with the cloud platform 130 and communicate with the server device 140 through the cloud platform 130. For example, a user may access the cloud platform 130 through a client, and access the server device 140 through the cloud platform 130. For another example, a user may access the cloud platform 130 through a client, and control the server device 140 through the cloud platform 130. In some embodiments, the client device 110 may also be referred to as a client.

In some embodiments, the above-mentioned client may be an application (APP) or a mini-program, etc.

The server device 140 may be a device that has a function of communicating with the cloud platform 130. In some implementations, the server device 140 may provide service functions for users, and therefore, the server device 140 may also be referred to as a server or a service device.

The configuration device 120 is used to configure the client device 110 and/or the server device 140. For example, the configuration device 120 can configure the client device 110 and/or the server device 140 to communicate with the cloud platform 130. For another example, the configuration device 120 can configure the client in the client device 110 so that the client can communicate with the cloud platform 130.

In some implementations, the configuration device 120 may be an application (APP) or a small program, etc. In other implementations, the configuration device 120 may be installed on a terminal device, wherein the terminal device may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), etc. The embodiments of the present application do not limit this.

The cloud platform 130, also known as a cloud computing platform or "cloud", can be understood as a service providing network communication capabilities based on hardware resources and software resources. Therefore, in the embodiment of the present application, the client in the client device 110 can access or control the server device 140 through the cloud platform 130.

In some implementations, the cloud platform 130 may be built based on one or more cloud servers to provide network functions.

It should be noted that the cloud platform 130 may also be other systems or devices that can provide network functions, such as a cluster system that can provide network functions, etc. This embodiment of the application does not limit this.

In addition, the configuration device 120 may be an APP or a small program that matches the client, and of course, the configuration device 230 may be an APP or a small program that is different from the client. This embodiment of the application does not limit this.

In some scenarios, the system 100 may be, for example, an Internet of Things (IoT) system. The IoT, or "Internet of Things connected to everything", can be understood as a network extended and expanded on the basis of the Internet. Any object can be connected to the Internet through various information sensing devices (such as radio frequency identification, global positioning system, etc.) to form a huge network for information exchange and communication, so as to realize the interconnection between all things.

In some embodiments, the client device 110 and/or the server device 140 may be an Internet of Things (IoT) device. The client device 110 and/or the server device 140 may refer to an IoT device that supports any IoT protocol, such as an IoT device that supports the Matter standard protocol. Exemplarily, IoT devices may include vehicle devices, vehicle-mounted terminals, smart home devices, smart monitoring devices, and the like. Smart home devices may include, for example, smart air conditioners, smart refrigerators, washing machines, rice cookers, sweeping robots, and the like. Smart monitoring devices may include, for example, surveillance cameras, temperature sensors, sound sensors, and the like.

In other embodiments, the cloud platform may be an IoT cloud platform, referred to as “IoT cloud”, which is used to provide communication service functions for IoT devices in an IoT system.

For ease of understanding, the system 100 is introduced by taking an IoT device as an example. Assume that the client device 110 is a vehicle-mounted terminal, the server device 140 is a smart home device, and the configuration device 120 can be a terminal device. Continuing to refer to Figure 1, the terminal device 120 can configure the client in the vehicle-mounted terminal 110 so that the client can communicate with the cloud platform 130. After the client is successfully configured, the user can access and/or control the smart home devices on the cloud platform (or the smart home devices connected to the cloud platform) through the client. The client that can access and/or control the smart home devices can also be called a "smart home client".

For example, assuming that the server device is a smart air conditioner, and the smart air conditioner is located on the cloud platform, the client can control the smart air conditioner on and off through the cloud platform and set the air conditioner temperature, wind speed, etc. When the server device is a sweeping robot, the client can control the sweeping robot to start or stop working, control the sweeping robot's working mode, etc. through the cloud platform.

The following is an introduction to the process of configuring the network for the server device in conjunction with FIG. 2 .

The configuration device shown in Figure 2 can have its own ecological network (fabric). The ecological network can also be called ecology. The ecological network can be a network domain in which all devices or nodes can communicate securely. For example, Company A developed an APP and built Company A's ecology based on the APP, so that all devices connected in the ecology can communicate securely.

2 , in step S210 , the configuration device may establish a connection with a public network server device. In some implementations, the public network server device may allocate an IP address to the configuration device.

In step S220, the configuration device may configure the server device into its own ecological network and configure the server device to access the network. In some implementations, the configuration device may send authentication information that can connect to the public network server device to the server device.

In step S230, the server device establishes a connection with the public network server device. For example, the server device may establish a connection with the public network server device based on the authentication information sent by the configuration device. In some embodiments, the public network server device may allocate an IP address to the server device.

In step S240, the configuration device establishes a connection with the server device based on the IP address. In some implementations, the configuration device may also establish a local secure session channel with the server device.

The above-mentioned public network server device may also be referred to as a public network server, an access point or an access point device. The public network server device may be, for example, a gateway, a router, an access point, etc.

At present, different manufacturers may use different communication protocols (also called ecological chain protocols) to achieve interconnection between IoT devices that support the communication protocols. This may lead to the inability of IoT devices produced by different manufacturers to communicate with each other, and the true interconnection of all things cannot be achieved.

Based on this, the Connectivity Standards Alliance (CSA) launched an IoT application layer technology standard - Matter standard protocol, which can provide an interoperable application layer solution for smart home devices based on the Internet Protocol (IP). In some embodiments, the Matter standard can also be called the connected home over IP (CHIP) standard. In some embodiments, the Matter standard can support three underlying communication protocols: Ethernet, Wi-Fi, and Thread, and can allow IoT devices with different protocols to communicate with each other.

Accordingly, if the client described above supports the Matter protocol, it can be called a "Matter client". If the server device described above supports the Matter protocol, it can be called a "Matter server". Client devices and/or server devices that support the Matter protocol can also be called "Matter devices".

The following uses the Matter protocol as an example to introduce the terms involved in the embodiments of the present application and the solutions of the embodiments of the present application. Of course, the solutions of the embodiments of the present application can also be applied to other Internet of Things protocols.

Model of the Matter device

3 is a data model structure of a Matter device applicable to an embodiment of the present application. The data model structure 200 of the Matter device includes a node 310 , an endpoint 320 , and a function cluster 330 .

Node 310 encapsulates an addressable, unique resource on the network, has a set of functions and capabilities, and can be clearly viewed by the user as a functional whole. Generally, node 310 can be the highest or outermost first-order element in the data model. In other words, node 310 is the only addressable element at the outermost level of the data model. Therefore, a node can represent a device node and belongs to a logical device.

It should be noted that a physical entity (e.g., a Matter device) can support multiple nodes 310. In addition, a node can have multiple node IDs, and the scope of each node ID is a specific network (fabric). For example, when the node ID is used as the target address of an interaction, the network that specifies the scope of the node ID is the access network for the interaction. A node can include one or more endpoints 320. An endpoint 320 is an instance, which can be a service instance or a virtual device, indicated by the device type. Each endpoint 320 conforms to one or more device type definitions, which define the clusters supported on the endpoint. A cluster is an object class instantiated on an endpoint.

It should be noted that in this architecture model, the device type can be the highest semantic element. The device type defines the consistency of a set of endpoints 320. The device type defines a set of requirements for a node 310 or an endpoint 320.

In some embodiments, endpoints can be divided into two categories: endpoint 0 and business endpoints. Endpoint 0 can be understood as the first endpoint in a node, and the device type of endpoint 0 is the "root node" device type. In some embodiments, endpoint 0 can also be called a root node endpoint. Endpoint 0 must be included under each node. A business endpoint can be understood as any endpoint in a node except endpoint 0. A business endpoint can support the main operations of a node. For example, a business endpoint can include one or more application function clusters.

Each endpoint 320 may be a collection of a type of functions, which may include one or more function clusters 330 .

Function cluster 330 is a functional building block element of the data model, or in other words, function cluster 330 belongs to an element for building a function set. In some embodiments, function cluster may also be referred to as function set, function set, cluster, cluster, etc., which is not limited by the embodiments of the present application. Function cluster specification defines a client and a server that correspond to each other through interaction. In other words, function cluster 330 may include two roles, namely, client and server, wherein the client belongs to the control end and the server belongs to the controlled end. Function cluster 330 may be regarded as an interface, service or object class, which is the lowest independent functional element in the data model.

Generally, the above functional clusters can be divided into two categories: utility functional clusters (utility cluster) and application functional clusters (application cluster).

Utility function clusters are not part of the primary application operation of the endpoint. Utility function clusters can be used for configuration, discovery, addressing, diagnostics, monitoring device health, software updates, etc. A utility function cluster may have a temporary relationship with its function cluster counterpart. Utility function clusters may include, for example, descriptor function clusters, binding function clusters, etc.

The application function cluster supports the main operations of the endpoint. In some embodiments, the application function cluster can also be called a business function cluster. The application function cluster can support the interaction of one or more persistent applications between the client and the server. For example, the switch function cluster (On/Off cluster) in the smart light, the client can send a control command to the server (i.e., the switch function cluster) to control the switch of the smart light.

In some embodiments, the service function cluster may refer to a function cluster on other endpoints except endpoint 0 in the node, that is, a function cluster on a service endpoint.

Typically, each functional cluster 330 may be defined by a functional cluster specification, which defines the elements of the functional cluster 330, including attributes, events, commands, and behaviors related to the interactions of these elements. In some embodiments, attributes, commands, and events may also be referred to as interface units of the functional cluster 330, and corresponding functions may be provided through these three interface units.

In some embodiments, the properties, events, commands, and behaviors in a functional cluster 330 are mandatory or optional, depending on the definition of the functional cluster 330 .

The following is a brief introduction to the main elements of the function cluster, such as commands, properties, and events.

Attributes can be used to describe functional units in a functional cluster. A functional cluster can contain 0 or more attributes. Attributes are functional cluster data. Currently, the protocol stipulates that each attribute can be listed in a table. The data quality columns of the attribute defined in the table may include: ID, name, (data) type, constraint, other quality, access, default (value) and consistency. In some implementations, attributes can also define their related semantics and behaviors. Attributes can reflect the queryable/settable status, configuration, and capabilities of the device. In some cases, if privileges are not explicitly defined for an attribute, the default access privilege takes effect.

Functional cluster commands (also called "commands") can be used to describe the control of functional clusters. A functional cluster can contain 0 or more commands. A command is a set of data fields, each data type is passed between client and server functional cluster instances to invoke the behavior of the command recipient. Currently, it is agreed in the protocol that each command can be listed in a table, which can contain data quality columns for the command: identification (ID), name (name), direction (direction), response (response), access (access), and consistency (conformance). Accordingly, a command can indicate zero or more fields defined in a table. Each command field is defined as a row in the table.

Events can be used to describe a record of specific behaviors that have occurred in the past for a functional cluster, or events define a record of what happened in the past. In this regard, an event record can be thought of as a log entry that provides a chronological view of events on a node through an event record stream. A functional cluster can contain 0 or more events. Unlike attributes, which do not provide any edge-preserving functionality (that is, there is no guarantee that every attribute change will be delivered to the observer), events allow each individual edge or change to be captured and reliably delivered to the observer. This is critical for safety and security applications that rely on correct behavior guarantees. Currently, the protocol stipulates that each functional cluster event can be listed in a table, and the data quality columns of the event defined in the table may include: ID, priority, access, and consistency.

For ease of understanding, the following describes the meanings of several common data qualities contained in commands, attributes, and events. It should be noted that the commands, attributes, and events in the embodiments of the present application may also include other data qualities, or include parts of the above data qualities. The embodiments of the present application do not limit this.

Identifier, which indicates the unique field ID of a field, or the unique identifier of a command (or attribute, event).

Name, which indicates the unique name of the field, or the name of the command (or attribute).

Type indicates the data type of the field, or the data type of the command parameter (or attribute parameter).

Direction, usually present in the command list, is used to define the transmission direction of the command, for example, it can be defined as from the client to the server. For another example, it can be defined as from the server to the client.

Access permissions, which define how an element can be accessed (e.g., read or write) and what permissions are required to access the data. In some implementations, access permissions may include V, which indicates that view privileges are required for read access or call access. Access permissions may also include O, which indicates that "read access", "write access", or "call access" requires operation permissions. Access permissions may also include R, which indicates read access. Access permissions may also include W, which indicates write access.

Response, usually exists in the command list, and is used to define the response message of the command.

Quality, used to define additional data qualities not covered in other columns.

Default, used to define the default value. It should be noted that the default value is not the value used when the server returns the factory refresh settings. The default value can indicate that the consistency specified for the data field can be optional or can change over time. When the actual data field value does not exist, a default value can be defined to complete the dependency.

Conformance, defines the optionality and dependencies of any data model element or set of elements. Typically, this column is valid for attributes, commands, events, enumerations, and fields of commands, events, or structures. In some implementations, "M" indicates that the corresponding command is part of the basic mandatory feature set, and "O" indicates that the corresponding command is part of the optional feature set.

For commands, client-to-server command conformance means that the server should recognize and support client-to-server commands and generate responses as defined. Server-to-client command conformance means that the server should send commands as defined by the functional cluster behavior, i.e., respond to client-to-server commands. Command conformance depends on supported server features. Clients should not be required to support optional commands or commands that depend on optional features.

Constraints include all and desc. All is defined in a numeric data type to allow all values. desc indicates that the constraint is defined in the description part.

Range, which indicates the value range of a field. Range can support two forms: explicit constraint and width constraint. Among them, the explicit constraint can give the minimum and maximum values corresponding to the value of the field, for example, the value range of a field is (0,128). The width constraint can limit the value of a field to a specific number of bytes, for example, the value of a field is limited to 8 bytes. In some embodiments, the value of the range can include "N/A" to indicate not applicable. Of course, "N/A" can also appear in other parts (other data quality), such as defaults, constraints, etc.

Priority: Each event record has an associated priority. This priority can be used to describe the usage semantics of the event.

The Matter protocol is introduced above, and the sigma protocol involved in this application is introduced below.

Sigma Protocol

On the one hand, the sigma protocol can be understood as an efficient interactive zero-knowledge proof protocol that allows the prover to prove to the verifier that he knows the secret without showing the secret to the verifier.

On the other hand, the sigma protocol can be understood as a key exchange protocol that can further ensure the security of key exchange by using digital signatures for authentication.

In some embodiments, the participants of the sigma protocol may include the configuration end (initiator) of the initiation process and the receiving end (responder) of the response process. The initiator and the responder may exchange keys through one or more rounds of sigma messages. FIG4 is a schematic diagram of a process of performing key exchange based on the sigma protocol provided in an embodiment of the present application. In conjunction with FIG4, the key exchange between the initiator and the responder based on the sigma protocol is exemplarily described below.

As shown in FIG. 4 , in step S410 , the initiator constructs a sigma1 message and sends the sigma1 message to the responder.

The sigma1 message may be used to request the responder to perform key exchange or key negotiation. In some embodiments, the sigma1 message may be a plaintext message. In some embodiments, the sigma1 message may be a ciphertext message.

In step S420, the responder generates a shared key according to the sigma1 message sent by the initiator, and sends the constructed sigma2 message to the initiator.

In some embodiments, before generating a shared key, the responder may verify the sigma1 message sent by the initiator, and execute step S420 after the verification passes.

In step S430, the initiator generates a shared key according to the sigma2 message sent by the responder, and sends the constructed sigma3 message to the responder.

In some embodiments, before generating a shared key, the initiator may verify the sigma2 message sent by the responder, and execute step S430 after the verification passes.

In step S440, the responder verifies the sigma3 message, and returns a sigma verification completion message to the initiator after the verification passes.

In real life, the following scenarios may exist. Scenario 1: The user may have different houses A and B, and the user wants to use the devices in house B to access the devices in house A. Scenario 2: The user has a car, and after the user drives away from home, he wants to access the devices at home through the car. In the above scenario 1, the devices in house A can be understood as client devices, and the devices in house B can be understood as server devices. In the above scenario 2, the car can be understood as a client device, and the devices in the user's home can be understood as server devices. At present, the access of client devices to server devices needs to be implemented through the cloud platform. The following is an explanation in conjunction with Figure 1.

Continuing to refer to FIG. 1 , when the client device 110 accesses the server device 140, it needs to access the server device 140 through the cloud platform 130. For example, the client device 110 needs to first send the instruction to the cloud platform 130, and then the cloud platform sends the instruction to the server device 140. This method has the problem of high connection complexity. Especially for the case where the client device and the server device belong to different manufacturers, the complexity of the connection will be further increased. For example, if the client device and the server device belong to different manufacturers, it is necessary to adopt a cloud-to-cloud interconnection solution to enable the client device to access the server device. For example, assuming that the client device belongs to manufacturer A, the cloud platform corresponding to manufacturer A is called cloud platform A, and the server device belongs to manufacturer B, and the cloud platform corresponding to manufacturer B is called cloud platform B, when the client device accesses the server device, it needs to go through cloud platform A and cloud platform B to access the server device.

Based on this, the embodiments of the present application provide a method and device for establishing a connection, which can realize the establishment of a connection between a client device and a server device through public network address information, so that the client device and the server device can be directly connected, thereby reducing the complexity of connection and access, making connection and access simple and convenient.

The solution of the embodiment of the present application is described in detail below in conjunction with FIG. 5 .

Referring to FIG. 5 , in step S510 , the client device establishes a connection with the server device based on public network address information.

In some embodiments, the client device and/or the server device may be an IoT device. The client device and/or the server device may refer to an IoT device that supports any IoT protocol, such as an IoT device that supports the Matter standard protocol. Exemplarily, IoT devices may include vehicle devices, vehicle-mounted terminals, smart home devices, smart monitoring devices, and the like. Smart home devices may include, for example, smart air conditioners, smart refrigerators, washing machines, rice cookers, sweeping robots, and other devices. Smart monitoring devices may include, for example, surveillance cameras, temperature sensors, sound sensors, and other devices.

The client device and the server device may be devices from the same manufacturer or devices from different manufacturers, and this embodiment of the present application does not specifically limit this.

In some embodiments, the client device may be referred to as an away-from-home device, and the server device may be referred to as a home device.

In some embodiments, the client device may be a vehicle device, or the client device may be a central control device located in a different area from the server device.

The public network address information is unique, and can enable a device to uniquely address another device through the public network address information of another device. The public network address information may include public network IP address information and/or port number. The public network IP address can be an IPv4 address (or a public network IPv4 address) or an IPv6 address (or a public network IPv6 address). Since the number of IP addresses in the IPv6 protocol is greater than the number of IP addresses in the IPv4 protocol, the use of IPv6 addresses can provide more possibilities for establishing a connection between a client device and a server device.

In some embodiments, the public network address information may include the public network address information of the server device and/or the public network address information of the client device. For example, the client device may establish a connection with the server device based on the public network address information of the server device. For another example, the client device may establish a connection with the server device based on the public network address information of the client device. For another example, the client device may establish a connection with the server device based on the public network address information of the client device and the public network address information of the server device. For another example, the server device may establish a connection with the client device based on the public network address information of the server device. For another example, the server device may establish a connection with the client device based on the public network address information of the client device. For another example, the server device may establish a connection with the client device based on the public network address information of the client device. For another example, the server device may establish a connection with the client device based on the public network address information of the client device and the public network address information of the server device.

The types of the public network address information of the client device and the public network address information of the server device may be the same or different. For example, the public network address information of the client device may be an IPv4 address, and the public network address information of the server device may be an IPv6 address. For another example, the public network address information of the client device may be an IPv6 address, and the public network address information of the server device may be an IPv4 address. For another example, the public network address information of the client device and the public network address information of the server device are both IPv4 addresses. For another example, the public network address information of the client device and the public network address information of the server device are both IPv6 addresses.

In some embodiments, the public network address information of the client device may be configured by an operator, or may also be configured by a public network server device.

In some embodiments, the public network address information of the server device may be configured by an operator, or may also be configured by a public network server device.

The public network server device may be a device with the ability to allocate public network addresses. In some embodiments, the operator may configure an address range for the public network server device, and the public network server device may configure public network addresses for other devices within the address range. In some embodiments, the public network server may configure public network addresses for devices connected thereto.

In some embodiments, the public network address configured by the public network server device for the device may be a static address or a dynamic address. Taking the dynamic address as an example, the public network server device may update the public network address configured for the device at regular intervals.

In some embodiments, the public network address information of the server device can be generated based on the public network address of the public network server device. For example, the public network address of the server can be generated based on the IP address of the public network server device, and the public network server device can add port number information to its own IP address to generate the public network address of the server.

In some embodiments, the public network server device may include one or more of the following: a gateway, a router, an access point, etc. In some embodiments, the public network server device may also be referred to as an access point or an access point device.

In some embodiments, the public network server device may have a network address translation (NAT) function, so that a private IP address can be converted into a public IP address. In some embodiments, the public network server device may have a network address port translation (NAPT) function, so that an IP address and a port number can be converted into a public IP address. In some embodiments, the public network server device may have a network address translation protocol translation (NAT-PT) function, so that an IPv4 address can be converted into an IPv6 address.

The connection established between the client device and the server device can be a remote connection. As described in the above scenario 1 and scenario 2, the server device and the client device can be located in different local area networks. Through the solution of the embodiment of the present application, the client device can achieve remote control of the server device.

The following uses the example of the public network address information of the server-side device being configured by the public network server device to illustrate the solution of the embodiment of the present application.

In some embodiments, the public network server device can configure a public network address for the server device. After configuring the public network address for the server device, the public network server device can send the public network address information of the server device. As shown in FIG6, in step S610, the public network server device can send the public network address information of the server device. For example, the public network server device can send the public network address information of the server device to the client device. For another example, the public network server device can send the public network address information of the server device to the configuration device.

In some embodiments, before establishing a connection with a server device, the client device may first obtain the public network address information of the server device.

In some embodiments, there are multiple ways for a client device to obtain the public network address information of a server device. For example, the client device can obtain the public network address information of the server device from a public network server device. For another example, the client device can obtain the public network address information of the server device from a configuration device. If the client device obtains the public network address information of the server device from the configuration device, the configuration device can first obtain the public network address information of the server device from the public network server device. The following will introduce these two situations respectively.

Next, the relevant solutions for the client device to obtain the public network address information of the server device from the public network server device are introduced.

In some embodiments, before the client device obtains the public network address information of the server device from the public network server device, the client device may establish a connection with the public network server device. For example, the client device may establish a connection with the public network server device based on the public network address information of the public network server device.

There are many ways for a client device to obtain the public network address information of a public network server device. For example, the client device can obtain the public network address information of the public network server device from a configuration device. For another example, the client device can obtain the public network address information of the public network server device from a cloud platform.

In some embodiments, if the client device obtains the public network address information of the public network server device from the configuration device, the configuration device may first establish a connection with the client device and then send the public network address information of the public network server device to the client device.

In some embodiments, the configuration device may have its own ecological network. In order to improve the security of communication, the configuration device may configure the client device into its own ecological network, that is, the client device is in the ecological network of the configuration device. The configuration device can communicate securely with the client device through the ecological network. For example, the configuration device can send the public network address information of the public network server device to the client device through the ecological network.

In some embodiments, the public network address information of the server device obtained by the client device from the public network server device can be static address information or dynamic address information. When allocating public network address information to the server device, the public network server device can allocate static address information or dynamic address information.

In some embodiments, the configuration device can configure the public network server device to its own ecological network, that is, the public network server device is in the ecological network of the configuration device, and the configuration device can communicate securely with the public network server device through the ecological network. For example, the configuration device can obtain the public network address information of the public network server device from the public network server device through the ecological network.

In some embodiments, the client device and the public network server device may both be in the ecological network of the configuration device, and the client device and the public network server device may communicate securely in the ecological network. For example, the public network server device may send the public network address information of the server device to the client device through the ecological network. In some implementations, the configuration device may have multiple ecological networks, and the client device and the public network server device may be in the same ecological network of the configuration device.

In some embodiments, the public network server device may store public network address information of one or more server devices. When the public network server device sends the public network address information of the server device to the client device, it may send the public network address information of some of the server devices stored on the public network server device, or it may send the public network address information of all the server devices stored on the public network server device.

In some embodiments, the public network server device can actively send the public network address information of the server device to the client device, or the client device can first send a request message to the public network server device, and after receiving the request message, the public network server device sends the public network address information of the server device to the configuration device. When the client device sends a request message to the public network server device, it can also indicate to the public network server device which server devices' public network address information to request, such as the client device can indicate to the public network server device to request the public network address information of the first device, and the public network server device can send the public network address information of the first device to the client device according to the request of the client device.

The following introduces the relevant solutions for the client device to obtain the public network address information of the server device from the configuration device.

Referring to FIG. 7 , in step S710 , the configuration device sends the public network address information of the server device to the client device.

In some embodiments, the configuration device may first obtain the public network address information of the server device from the public network server device, and then send the public network address information of the server device to the client device. In some embodiments, the configuration device may also obtain the public network address information of the server device from other devices (such as operators).

In some embodiments, the configuration device may first configure the public network server device to establish a connection with the public network server device. After establishing a connection with the public network server device, the configuration device may obtain the public network address information of the server device from the public network server device. In some embodiments, the public network server device may actively send the public network address information of the server device to the configuration device, or the configuration device may first send a request message to the public network server device, and after receiving the request message, the public network server device sends the public network address information of the server device to the configuration device.

In order to ensure the security of communication, the configuration device can configure the public network server device into its own ecological network and communicate with the public network server device through the ecological network. For example, the public network server device can send the public network address information of the server device to the configuration device through the ecological network.

Similarly, to ensure the security of communication, the configuration device can configure the client device into its own ecological network and communicate with the client device through the ecological network. For example, the configuration device can send the public network address information of the server device to the client device through the ecological network.

In some embodiments, the public network server device may store public network address information of one or more server devices. When the configuration device obtains the public network address information of the server device from the public network server device, it may obtain the public network address information of some server devices stored on the public network server device, or it may obtain the public network address information of all server devices stored on the public network server device.

In some embodiments, the configuration device may send the public network address information of one or more server devices to the client device. For example, the configuration device may send the acquired public network address information of some server devices to the client device. For another example, the configuration device may send the acquired public network address information of all server devices to the client device.

In some embodiments, in order to ensure the security of communication, a secure connection can be established between two devices communicating with each other in the present application. The two devices communicating with each other can be a client device and a server device, or a client device and a public network server device, or a server device and a public network server device.

In some embodiments, the secure connection may include a secure connection established based on a sigma protocol. Two devices communicating with each other may perform key exchange and shared key negotiation based on the sigma protocol to establish a secure connection. For example, two devices communicating with each other may negotiate a shared key based on the sigma protocol, and based on the shared key, establish an operation channel (or interoperation channel) and perform secure communication through the operation channel.

In some embodiments, it can be known from the above description that the sigma protocol is a key exchange and shared key negotiation based on the operation certificate. The two devices in this application can perform key exchange and shared key negotiation based on the operation certificate.

The operation certificate may be sent by the configuration device to other devices. For example, the configuration device may send the operation certificate corresponding to the client device to the client device. For another example, the configuration device may send the operation certificate corresponding to the server device to the server device. For another example, the configuration device may send the operation certificate corresponding to the public network server device to the public network server device.

To ensure the security of communication, the configuration device can configure other devices into its own ecological network and send operation certificates to other devices through the ecological network. The operation certificates corresponding to different devices may be different.

In some embodiments, two devices communicating with each other can verify the identity of the operation certificate based on the ecological network identifier and/or node identifier. If the operation certificate is verified, a secure connection can be established between the two devices. The ecological network identifier is used to identify which ecological network the device is connected to, and the node identifier is the unique identity information assigned by the configuration device to the device to identify the device's access to the network. The ecological network identifier and node identifier can be assigned to the device when the configuration device establishes a connection with the device.

In some embodiments, the client device is in the ecological network of the configuration device, and the configuration device can send the first information for the client device to the client device through the ecological network, thereby ensuring the security of the first information. The first information can be used by the client device to establish a secure connection with other devices. For example, the first information can be used to establish a secure connection between the client device and a public network server device, or the first information can be used to establish a secure connection between the client device and a server device.

The first information may include one or more of the following: an operation certificate, an ecological network identifier, and a node identifier.

The eco-network identifier can be used to identify the eco-network in which the device is located. If the eco-network identifiers of two devices are the same, the two devices can communicate securely in the eco-network. If the eco-network identifiers of two devices are different, the two devices may not be able to communicate securely through the eco-network.

The node identifier can be used as the target address for interaction. Client devices can communicate securely with other devices through the node identifier.

The operation certificate stores the key information of the device. The sender and the receiver can perform key exchange and shared key negotiation based on the operation certificate. For example, the client device can use the sigma key negotiation algorithm to perform key exchange and shared key negotiation with other devices. In some embodiments, the client device can establish a secure connection with other devices based on the operation certificate.

In some embodiments, the ecological network identifier and/or the node identifier may be used to verify the operation certificate. If the operation certificate is verified, the client device may use the operation certificate to establish a secure connection with other devices.

In some embodiments, the public network server device is in the ecological network of the configuration device, and the configuration device can send the second information for the public network server device to the public network server device through the ecological network, thereby ensuring the security of the second information. The second information can be used by the public network server device to establish a secure connection with other devices. For example, the second information can be used to establish a secure connection between the public network server device and the client device.

The second information may include one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The relevant contents of the operation certificate, the ecological network identifier, and the node identifier can be found in the above description, and will not be repeated here for the sake of brevity.

In some embodiments, the ecological network identifier and/or the node identifier may be used to verify the operation certificate. If the operation certificate is verified, the public network server device may use the operation certificate to establish a secure connection with other devices.

In some embodiments, the server device is in the ecological network of the configuration device, and the configuration device can send the third information for the public network server device to the public network server device through the ecological network, thereby ensuring the security of the third information. The third information can be used by the public network server device to establish a secure connection with other devices. For example, the third information can be used to establish a secure connection between the public network server device and the client device, or the third information can be used to establish a secure connection between the public network server device and the server device.

The third information may include one or more of the following: operation certificate, ecological network identifier and node identifier. The relevant contents of the operation certificate, ecological network identifier and node identifier can be found in the above description, and will not be repeated here for the sake of brevity.

In some embodiments, the ecological network identifier and/or the node identifier may be used to verify the operation certificate. If the operation certificate is verified, the public network server device may use the operation certificate to establish a secure connection with other devices.

In some embodiments, the public network server device may include a first functional cluster. The first functional cluster may be a new functional cluster. The first functional cluster may include the public network address information of the server device. In some embodiments, the first functional cluster may include one or more of the following: the public network address information of the server device, the ecological network identifier of the server device, and the node identifier of the server device. For example, the first functional cluster includes the public network address information of the server device. For another example, the first functional cluster includes the public network address information of the server device and the ecological network identifier of the server device. For another example, the first functional cluster includes the public network address information of the server device and the node identifier of the server device. For another example, the first functional cluster includes the public network address information of the server device, the ecological network identifier of the server device, and the node identifier of the server device.

In some embodiments, the first functional cluster may include device list information (or node list information). The device list information may include one or more of the following information: public network address information of one or more server devices, ecological network identification of one or more server devices, and node identification of one or more server devices.

In some embodiments, the first functional cluster may also include one or more of the following information: public network address information of the public network server device, an ecological network identifier of the public network server device, and a node identifier of the public network server device.

By setting the first functional cluster, other devices can safely obtain information in the first functional cluster, ensuring the security of information in the first functional cluster. For example, the configuration device can obtain one or more of the following information from the first functional cluster: the public network address information of the server device, the ecological network identifier of the server device, and the node identifier of the server device. For another example, the configuration device can obtain one or more of the following information from the first functional cluster: the public network address information of the public network server device, the ecological network identifier of the public network server device, and the node identifier of the public network server device.

In some embodiments, when the configuration device obtains information from the first functional cluster, it may obtain all the information in the first functional cluster, or may only obtain part of the information in the first functional cluster. For example, the configuration device may only obtain the public network address information of the device. For another example, the configuration device may obtain relevant information of some server-side devices in the first functional cluster.

In some embodiments, the client device may obtain the public network address information of the server device from the first functional cluster. The client device may obtain the public network address information of all server devices in the first functional cluster, or may obtain the public network address information of some server devices in the first functional cluster.

Table 1 shows an example of the first functional cluster.

Table 1

The node list may include relevant information of one or more server devices. NodeStruct may include one or more of the following information: node ID, fabric ID, and IP address string. The node ID is the node ID of the server device, the fabric ID is the fabric ID of the server device, and the IP address string may include the public network address and/or port number assigned by the public network server device to the server device.

In some embodiments, the first functional cluster may further include first indication information, where the first indication information is used to indicate the type of the public network address information. The type of the public network address information includes static public network address information and dynamic public network address information. That is, the first indication information may be used to indicate whether the public network address information in the first functional cluster is static public network address information or dynamic public network address information.

In some embodiments, the first indication information may be used to indicate the type of public network address information of the public network server device, or may also be used to indicate the type of public network address information of the server device.

Table 2 shows another example of the first functional cluster. The difference between Table 2 and Table 1 is that the first indication information, namely Static IP, is added.

Table 2

If Static IP is true, it means that the public IP address (such as the public IP address of the server device) is a static address; if Static IP is false, it means that the public IP address (such as the public IP address of the server device) is a dynamic address.

In some embodiments, the manner in which the client device obtains the public network address information of the server device can be adjusted according to the type of the public network server indicated by the first indication information. For example, if the first indication information indicates that the public network address information of the server device is static address information, the client device can obtain the public network address information of the server device from the configuration device or the public network server device. For another example, if the first indication information indicates that the public network address information of the server device is dynamic address information, the client device can obtain the public network address information of the server device from the public network server device.

As described above, the solution of the embodiment of the present application can not only realize the direct connection between the client device and the server device, but also ensure the security of the communication process. In addition, in the process of realizing secure communication, the existing protocol specifications can be reused, which can reduce the complexity of implementation.

For ease of understanding, the following two examples are combined to introduce the scheme of the embodiment of the present application in detail. It should be noted that the following two examples are only for ease of understanding, and the description of the embodiment of the present application should not limit the embodiment of the present application.

Example 1 describes a solution in which a client device obtains the public network address information of a server device from a public network server device, and Example 2 describes a solution in which a client device obtains the public network address information of a server device from a configuration device.

Example 1

FIG. 8 shows a process of configuring a device to obtain a public network IP address of a public network server device.

8, in step S810, the operator allocates a public IP address to the public network server device. After unpacking, the public network server device can be connected to the operator network, and the operator network can allocate a public IP address to the public network server device.

In step S820, the configuration device configures the public network server device into its ecosystem, issues an operation certificate to the public network server device, and establishes a local secure connection with the public network server device.

In step S830, the public network server device may define a new functional cluster. The functional cluster may be used to store the public network IP address information of the public network server device. For example, the public network server device may define a cluster named PublicIP, whose attribute is the public network IPv6 address. The functional cluster may be the functional cluster shown in Table 1, or the functional cluster shown in Table 2.

In step S840, after the configuration device establishes a secure connection with the public network server device, it may send a request message to the public network server device, where the request message is used to request the public network IP address of the public network server device.

In step S850, after receiving the request message sent by the configuration device, the public network server device may send the public network IP address of the public network server device to the configuration device.

In step S860, the configuration device stores the correspondence between the public IP address of the public network server device and the Fabric ID and Node ID of the public network server device.

FIG. 9 shows a process of a client device acquiring a public network IP address of a public network server device from a configuration device.

9, in step S910, the configuration device configures the client device into its own ecosystem, issues an operation certificate to the client device, and establishes a local secure connection with the client device. When configuring the client, the configuration device may use a local connection method.

In step S920, the configuration device stores the correspondence between the public IP address of the public network server device and the Fabric ID and Node ID of the public network server device.

In step S930, the client device sends a request message to the configuration device, and the request message is used to request relevant information of the public network server device. For example, the request message can be used to request to obtain one or more of the following information: the public network IP address of the public network server device, the Fabric ID of the public network server device, and the Node ID of the public network server device.

In step S940, the configuration device sends a response message to the client device. The response message may include one or more of the following information: the public network IP address of the public network server device, the Fabric ID of the public network server device, and the Node ID of the public network server device.

In step S950, the client device establishes a connection with the public network server device according to the response message.

Figure 10 shows a process of allocating a public IP address to a server device by a public network server device. The difference between Figure 10 and Figure 2 is that Figure 10 adds a step of allocating a public IP address to a server device by a public network server device. For contents not described in detail in Figure 10, please refer to the description of Figure 2.

Referring to FIG. 10 , in step S1010 , the configuration device may establish a connection with a public network server device, and the public network server device may allocate an IP address to the configuration device.

In step S1020, the configuration device may configure the server device into its own ecological network, issue an operation certificate to the server device through the ecological network, and configure the server device to access the network.

In step S1030, the server device establishes a connection with the public network server device. In some embodiments, the public network server device can allocate an IP address to the server device.

In step S1040, the public network server device can allocate a public network IP address to the server device, and store the public network IP address of the server device, the Fabric ID of the server device, and the Node ID of the server device in the relevant functional cluster.

In step S1050, the configuration device establishes a connection with the server device based on the IP address. In some implementations, the configuration device may also establish a local secure session channel with the server device.

FIG. 11 shows a process of establishing a connection between a client device and a server device.

Referring to FIG. 11 , in step S1110 , the client device may establish a connection with the public network server device based on the public network IP address of the public network server device according to the user's intention.

In step S1120, the client device and the public network server device establish a secure connection based on the operation certificate. Since both the client device and the public network server device are issued by the same ecosystem (the ecosystem of the configuration device) with operation certificates, and are assigned Fabric ID and Node ID, the client device and the public network server device can verify the identity of the operation certificate through Fabric ID and Node ID. In addition, the client device and the public network server device can perform key exchange and shared key negotiation based on the sigma protocol to establish a secure connection.

In step S1130, the client device may send a request message to the public network server device based on the secure connection. The request message is used to request to obtain the public network IP address information of the server device. For example, the client device may obtain the nodelist attribute information in the functional cluster corresponding to the public network server device, thereby obtaining the public network IP address information of the device connected to the public network server device.

In step S1140, the public network server device sends a response message to the client device based on the request message sent by the client device. The response message includes the public network IP address of the server device.

In step S1150, the client device establishes a connection with the server device based on the public IP address of the server device.

Since both the client device and the server device have operation certificates issued by the same ecosystem (the ecosystem of the configuration device) and are assigned Fabric ID and Node ID, the client device and the server device can verify the identity of the operation certificate through Fabric ID and Node ID. In addition, the client device and the server device can perform key exchange and shared key negotiation based on the sigma protocol to establish a secure connection.

In step S1160, after the client device establishes a connection with the server device, the client device can access the server device, for example, the client device can control the server device.

Example 2

FIG. 12 shows a process of configuring a device to obtain a public IP address of a server device from a public network server device.

In step S1210, the operator allocates a public IP address to the public network server device. After unpacking, the public network server device can be connected to the operator network, and the operator network can allocate a public IP address to the public network server device.

In step S1220, the configuration device configures the public network server device into its ecosystem, issues an operation certificate to the public network server device, and establishes a local secure connection with the public network server device.

In step S1230, the configuration device sends a request message to the public network server device, where the request message is used to request to obtain public network IP address list information of the server-side devices on the functional cluster.

In step S1240, the public network server device sends a response message to the configuration device, and the response message includes public network IP address information of one or more server devices. The server device may be a device connected to the public network server device.

In step S1250, configure the correspondence between the public IP address of the device storage service client device, the Fabric ID of the server device, and the Node ID of the server device.

After the configuration device obtains the public IP address of the server device, it can send the public IP address of the server device to the client device.

FIG. 13 shows a process of establishing a connection between a client device and a server device.

Referring to FIG. 13 , in step S1310 , the client device establishes a connection with the server device.

Since both the client device and the server device have operation certificates issued by the same ecosystem (the ecosystem of the configuration device) and are assigned Fabric ID and Node ID, the client device and the server device can verify the identity of the operation certificate through Fabric ID and Node ID. In addition, the client device and the server device can perform key exchange and shared key negotiation based on the sigma protocol to establish a secure connection.

In step S1320, after the client device establishes a connection with the server device, the client device can access the server device, for example, the client device can control the server device.

The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 13, and the device embodiment of the present application is described in detail below in conjunction with Figures 14 to 18. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the part not described in detail can refer to the previous method embodiment.

Fig. 14 is a schematic block diagram of a client device provided in an embodiment of the present application. The client device 1400 shown in Fig. 14 can be any of the client devices described above. The client device 1400 can include an establishing unit 1410.

The establishing unit 1410 is used to establish a connection with the server device based on the public network address information, where the public network address information includes the public network address information of the client device and/or the public network address information of the server device.

In some embodiments, the public network address information of the server device is configured by a public network server device.

In some embodiments, the public network address information of the server device is generated based on the public network address of the public network server device.

In some embodiments, the client device further includes: an acquisition unit, configured to acquire the public network address information of the server device from the public network server device.

In some embodiments, before the client device obtains the public network address information of the server device from the public network server device, the acquisition unit is also used to: obtain the public network address information of the public network server device from the configuration device; the establishment unit is also used to: establish a connection with the public network server device based on the public network address information of the public network server device.

In some embodiments, the client device further includes: an acquisition unit, configured to acquire the public network address information of the server device from a configuration device.

In some embodiments, the public network address information of the server device is obtained by the configuration device from the public network server device.

In some embodiments, the client device is in an ecological network of a configuration device, and the client device further includes: a receiving unit, for receiving first information for the client device sent by the configuration device through the ecological network, the first information being used to establish a secure connection between the client device and the public network server device, or the first information being used to establish a secure connection between the client device and the server device; wherein the first information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier.

In some embodiments, the public network address information of the server device is included in a first functional cluster of public network server devices.

In some embodiments, the first functional cluster further includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device.

In some embodiments, the first functional cluster includes device list information, and the device list information includes one or more of the following information: public network address information of one or more server devices, ecological network identifiers of one or more server devices, and node identifiers of one or more server devices.

In some embodiments, the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information of the server device, and the type of the public network address information includes static public network address information and dynamic public network address information.

In some embodiments, the first functional cluster also includes one or more of the following information: public network address information of the public network server device, an ecological network identifier of the public network server device, and a node identifier of the public network server device.

FIG15 is a schematic block diagram of a configuration device provided in an embodiment of the present application. The configuration device 1500 shown in FIG15 may be any of the configuration devices described above. The configuration device 1500 may include a sending unit 1510 .

The sending unit 1510 is used to send the public network address information of the server device to the client device, and the public network address information of the server device is used to establish a connection between the client device and the server device.

In some embodiments, the public network address information of the server device is configured by a public network server device.

In some embodiments, the configuration device further includes: an acquisition unit, configured to acquire the public network address information of the server device from the public network server device.

In some embodiments, the public network address information of the server device is generated based on the public network address of the public network server device.

In some embodiments, the client device is in the ecological network of the configuration device, and the configuration device also includes: a sending unit, used to send first information for the client device to the client device through the ecological network, the first information is used to establish a secure connection between the client device and the server device, or the first information is used to establish a secure connection between the client device and a public network server device; wherein the first information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier.

In some embodiments, the public network server device is in the ecological network of the configuration device, and the configuration device also includes: a sending unit, used to send second information for the public network server device to the public network server device through the ecological network, and the second information is used to establish a secure connection between the public network server device and the client device; wherein the second information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier.

In some embodiments, the server device is in the ecological network of the configuration device, and the configuration device also includes: a sending unit, used to send third information for the server device to the server device through the ecological network, and the third information is used to establish a secure connection between the server device and the client device; wherein the third information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier.

In some embodiments, the configuration device further includes: a sending unit, configured to send public network address information of a public network server device to the client device, wherein the public network address information of the public network server device is used to establish a connection between the public network server device and the client device.

In some embodiments, the public network address information of the server device is included in a first functional cluster of public network server devices.

In some embodiments, the first functional cluster further includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device.

In some embodiments, the first functional cluster includes device list information, and the device list information includes one or more of the following information: public network address information of one or more server devices, ecological network identifiers of one or more server devices, and node identifiers of one or more server devices.

In some embodiments, the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server device, and the type of public network address information includes static public network address information and dynamic public network address information.

In some embodiments, the first functional cluster also includes one or more of the following information: public network address information of the public network server device, an ecological network identifier of the public network server device, and a node identifier of the public network server device.

FIG16 is a schematic block diagram of a public network server device provided in an embodiment of the present application. The public network server device 1600 shown in FIG16 can be any of the public network server devices described above. The public network server device 1600 can include a sending unit 1610.

The sending unit 1610 is used to send the public network address information of the server device, and the public network address information of the server device is used to establish a connection between the client device and the server device.

In some embodiments, the public network address information of the server device is configured by the public network server device.

In some embodiments, the public network address information of the server device is generated based on the public network address of the public network server device.

In some embodiments, the sending unit is used to: send the public network address information of the server device to the client device.

In some embodiments, the sending unit is further used to: send public network address information of the public network server device to the configuration device, and the public network address information of the public network server device is used to establish a connection between the public network server device and the client device.

In some embodiments, the public network server device is in the ecological network of the configuration device, and the public network server device also includes: a receiving unit, used to receive second information for the public network server device sent by the configuration device through the ecological network, and the second information is used to establish a secure connection between the public network server device and the client device; wherein the second information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier.

In some embodiments, the sending unit is used to: send the public network address information of the server device to the configuration device.

In some embodiments, the public network address information of the server device is included in the first functional cluster of the public network server device.

In some embodiments, the first functional cluster further includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device.

In some embodiments, the first functional cluster includes device list information, and the device list information includes one or more of the following information: public network address information of one or more server devices, ecological network identifiers of one or more server devices, and node identifiers of one or more server devices.

In some embodiments, the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server device, and the type of public network address information includes static public network address information and dynamic public network address information.

In some embodiments, the first functional cluster also includes one or more of the following information: public network address information of the public network server device, an ecological network identifier of the public network server device, and a node identifier of the public network server device.

FIG17 is a schematic block diagram of a server device provided in an embodiment of the present application. The server device 1700 shown in FIG17 can be any server device described above. The server device 1700 can include an establishing unit 1710.

The establishing unit 1710 is used to establish a connection with the client device based on the public network address information, where the public network address information includes the public network address information of the client device and/or the public network address information of the server device.

In some embodiments, the public network address information of the server device is configured by a public network server device.

In some embodiments, the public network address information of the server device is generated based on the public network address of the public network server device.

In some embodiments, the server device is in the ecological network of the configuration device, and the server device also includes: a receiving unit, used to receive third information for the server device sent by the configuration device through the ecological network, and the third information is used to establish a secure connection between the server device and the client device; wherein the third information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier.

In some embodiments, the public network address information of the server device is included in a first functional cluster of public network server devices.

In some embodiments, the first functional cluster further includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device.

In some embodiments, the first functional cluster includes device list information, and the device list information includes one or more of the following information: public network address information of one or more server devices, ecological network identifiers of one or more server devices, and node identifiers of one or more server devices.

In some embodiments, the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server device, and the type of public network address information includes static public network address information and dynamic public network address information.

In some embodiments, the first functional cluster also includes one or more of the following information: public network address information of the public network server device, an ecological network identifier of the public network server device, and a node identifier of the public network server device.

FIG18 is a schematic structural diagram of a communication device according to an embodiment of the present application. The dotted lines in FIG18 indicate that the unit or module is optional. The device 1800 may be used to implement the method described in the above method embodiment. The device 1800 may be a chip, a client device, a server device, a configuration device, or a public network server device.

The device 1800 may include one or more processors 1810. The processor 1810 may support the device 1800 to implement the method described in the above method embodiment. The processor 1810 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

The apparatus 1800 may further include one or more memories 1820. The memory 1820 stores a program, which can be executed by the processor 1810, so that the processor 1810 executes the method described in the above method embodiment. The memory 1820 may be independent of the processor 1810 or integrated in the processor 1810.

The apparatus 1800 may further include a transceiver 1830. The processor 1810 may communicate with other devices or chips through the transceiver 1830. For example, the processor 1810 may transmit and receive data with other devices or chips through the transceiver 1830.

The embodiment of the present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the device provided in the embodiment of the present application, and the program enables a computer to execute the method executed by the device in each embodiment of the present application.

The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the device provided in the embodiment of the present application, and the program enables the computer to execute the method executed by the device in each embodiment of the present application.

The embodiments of the present application also provide a computer program. The computer program can be applied to the device provided in the embodiments of the present application, and the computer program enables a computer to execute the method executed by the device in each embodiment of the present application.

It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions.

In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, B can be obtained through C; it can also mean that there is an association relationship between A and B.

In the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and/or other information.

In the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship of indication and being indicated, configuration and being configured, etc.

In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including client devices, configuration devices, server devices and public network server devices), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

In the embodiments of the present application, the term "and/or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this article generally indicates that the associated objects before and after are in an "or" relationship.

In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

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.

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.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (87)

A method for establishing a connection, characterized by comprising: The client device establishes a connection with the server device based on the public network address information, where the public network address information includes the public network address information of the client device and/or the public network address information of the server device. The method according to claim 1 is characterized in that the public network address information of the server device is configured by a public network server device. The method according to claim 1 is characterized in that the public network address information of the server-side device is generated based on the public network address of the public network server device. The method according to any one of claims 1 to 3, characterized in that the method further comprises: The client device obtains the public network address information of the server device from the public network server device. The method according to claim 4 is characterized in that before the client device obtains the public network address information of the server device from the public network server device, the method further comprises: The client device obtains the public network address information of the public network server device from the configuration device; The client device establishes a connection with the public network server device based on the public network address information of the public network server device. The method according to any one of claims 1 to 3, characterized in that the method further comprises: The client device obtains the public network address information of the server device from the configuration device. The method according to claim 6 is characterized in that the public network address information of the server device is obtained by the configuration device from the public network server device. The method according to any one of claims 1 to 7, wherein the client device is in an ecological network of a configuration device, and the method further comprises: The client device receives first information sent by the configuration device, where the first information is used to establish a secure connection between the client device and the public network server device, or the first information is used to establish a secure connection between the client device and the server device; The first information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The method according to any one of claims 1-8 is characterized in that the public network address information of the server-side device is included in the first functional cluster of the public network server device. The method according to claim 9 is characterized in that the first functional cluster also includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device. The method according to claim 9 or 10 is characterized in that the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information of the server device, and the type of public network address information includes static public network address information and dynamic public network address information. A method for establishing a connection, characterized by comprising: The configuration device sends the public network address information of the server device to the client device, and the public network address information of the server device is used to establish a connection between the client device and the server device. The method according to claim 12 is characterized in that the public network address information of the server device is configured by a public network server device. The method according to claim 13, characterized in that the method further comprises: The configuration device obtains the public network address information of the server device from the public network server device. The method according to claim 12 is characterized in that the public network address information of the server-side device is generated based on the public network address of the public network server device. The method according to any one of claims 12 to 15, wherein the client device is in an ecological network of the configuration device, and the method further comprises: The configuration device sends first information for the client device to the client device through the ecological network, where the first information is used to establish a secure connection between the client device and the server device, or the first information is used to establish a secure connection between the client device and a public network server device; The first information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The method according to any one of claims 12 to 16, characterized in that the public network server device is in the ecological network of the configuration device, and the method further comprises: The configuration device sends second information for the public network server device to the public network server device through the ecological network, where the second information is used to establish a secure connection between the public network server device and the client device; The second information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The method according to any one of claims 12 to 17, wherein the server device is in an ecological network of the configuration device, and the method further comprises: The configuration device sends third information for the server device to the server device through the ecological network, where the third information is used to establish a secure connection between the server device and the client device; The third information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The method according to any one of claims 12 to 18, characterized in that the method further comprises: The configuration device sends public network address information of a public network server device to the client device, and the public network address information of the public network server device is used to establish a connection between the public network server device and the client device. The method according to any one of claims 12-19 is characterized in that the public network address information of the server-side device is contained in a first functional cluster of the public network server device. The method according to claim 20 is characterized in that the first functional cluster also includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device. The method according to claim 20 or 21 is characterized in that the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server-side device, and the type of public network address information includes static public network address information and dynamic public network address information. A method for establishing a connection, characterized by comprising: The public network server device sends the public network address information of the server device, and the public network address information of the server device is used to establish a connection between the client device and the server device. The method according to claim 23 is characterized in that the public network address information of the server device is configured by the public network server device. The method according to claim 23 is characterized in that the public network address information of the server-side device is generated based on the public network address of the public network server device. The method according to any one of claims 23 to 25, characterized in that the public network server device sends the public network address information of the server device, including: The public network server device sends the public network address information of the server device to the client device. The method according to claim 26, characterized in that the method further comprises: The public network server device sends the public network address information of the public network server device to the configuration device, and the public network address information of the public network server device is used to establish a connection between the public network server device and the client device. The method according to claim 27, characterized in that the public network server device is in the ecological network of the configuration device, and the method further comprises: The public network server device receives second information for the public network server device sent by the configuration device through the ecological network, where the second information is used to establish a secure connection between the public network server device and the client device; The second information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The method according to claim 23, characterized in that the public network server device sends the public network address information of the server device, including: The public network server device sends the public network address information of the server device to the configuration device. The method according to any one of claims 23-29 is characterized in that the public network address information of the server-side device is included in the first functional cluster of the public network server device. The method according to claim 30 is characterized in that the first functional cluster also includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device. The method according to claim 30 or 31 is characterized in that the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server-side device, and the type of public network address information includes static public network address information and dynamic public network address information. A method for establishing a connection, characterized by comprising: The server device establishes a connection with the client device based on the public network address information, where the public network address information includes the public network address information of the client device and/or the public network address information of the server device. The method according to claim 33 is characterized in that the public network address information of the server device is configured by a public network server device. The method according to claim 33 is characterized in that the public network address information of the server-side device is generated based on the public network address of the public network server device. The method according to any one of claims 33 to 35, characterized in that the server device is in an ecological network of a configuration device, and the method further comprises: The server device receives third information for the server device sent by the configuration device through the ecological network, wherein the third information is used to establish a secure connection between the server device and the client device; The third information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The method according to any one of claims 33-36 is characterized in that the public network address information of the server-side device is contained in the first functional cluster of the public network server device. The method according to claim 37 is characterized in that the first functional cluster also includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device. The method according to claim 37 or 38 is characterized in that the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server-side device, and the type of public network address information includes static public network address information and dynamic public network address information. A client device, comprising: An establishing unit is used to establish a connection with a server device based on public network address information, wherein the public network address information includes the public network address information of the client device and/or the public network address information of the server device. The client device according to claim 40 is characterized in that the public network address information of the server device is configured by a public network server device. The client device according to claim 40 is characterized in that the public network address information of the server device is generated based on the public network address of the public network server device. The client device according to any one of claims 40 to 42, characterized in that the client device further comprises: The acquisition unit is used to acquire the public network address information of the server device from the public network server device. The client device according to claim 43, characterized in that before the client device obtains the public network address information of the server device from the public network server device, The acquisition unit is further used to: acquire the public network address information of the public network server device from the configuration device; The establishing unit is further configured to establish a connection with the public network server device based on the public network address information of the public network server device. The client device according to any one of claims 40 to 42, characterized in that the client device further comprises: The acquisition unit is used to acquire the public network address information of the server device from the configuration device. The client device according to claim 45 is characterized in that the public network address information of the server device is obtained by the configuration device from the public network server device. The client device according to any one of claims 40 to 46, wherein the client device is in an ecological network of a configuration device, and the client device further comprises: A receiving unit, configured to receive first information for the client device sent by the configuration device through the ecological network, wherein the first information is used to establish a secure connection between the client device and the public network server device, or the first information is used to establish a secure connection between the client device and the server device; The first information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The client device according to any one of claims 40-47 is characterized in that the public network address information of the server device is included in the first functional cluster of the public network server device. The client device according to claim 48 is characterized in that the first functional cluster also includes one or more of the following: the ecological network identifier of the server device and the node identifier of the server device. The client device according to claim 48 or 49 is characterized in that the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information of the server device, and the type of public network address information includes static public network address information and dynamic public network address information. A configuration device, comprising: The sending unit is used to send the public network address information of the server device to the client device, and the public network address information of the server device is used to establish a connection between the client device and the server device. The configuration device according to claim 51 is characterized in that the public network address information of the server device is configured by a public network server device. The configuration device according to claim 52, characterized in that the configuration device further comprises: The acquisition unit is used to acquire the public network address information of the server device from the public network server device. The configuration device according to claim 51 is characterized in that the public network address information of the server-side device is generated based on the public network address of the public network server device. The configuration device according to any one of claims 51 to 54, characterized in that the client device is in an ecological network of the configuration device, and the configuration device further comprises: A sending unit, configured to send first information for the client device to the client device through the ecological network, wherein the first information is used to establish a secure connection between the client device and the server device, or the first information is used to establish a secure connection between the client device and a public network server device; The first information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The configuration device according to any one of claims 51 to 55, characterized in that the public network server device is in the ecological network of the configuration device, and the configuration device further comprises: A sending unit, configured to send second information for the public network server device to the public network server device through the ecological network, wherein the second information is used to establish a secure connection between the public network server device and the client device; The second information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The configuration device according to any one of claims 51 to 56, characterized in that the server device is in an ecological network of the configuration device, and the configuration device further comprises: A sending unit, configured to send third information for the server device to the server device through the ecological network, wherein the third information is used to establish a secure connection between the server device and the client device; The third information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The configuration device according to any one of claims 51 to 57, characterized in that the configuration device further comprises: The sending unit is used to send the public network address information of the public network server device to the client device, and the public network address information of the public network server device is used to establish a connection between the public network server device and the client device. The configuration device according to any one of claims 51-58 is characterized in that the public network address information of the server-side device is included in the first functional cluster of the public network server device. The configuration device according to claim 59 is characterized in that the first functional cluster also includes one or more of the following: an ecological network identifier of the server-side device and a node identifier of the server-side device. The configuration device according to claim 59 or 60 is characterized in that the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server device, and the type of public network address information includes static public network address information and dynamic public network address information. A public network server device, characterized by comprising: The sending unit is used to send the public network address information of the server device, and the public network address information of the server device is used to establish a connection between the client device and the server device. The public network server device according to claim 62 is characterized in that the public network address information of the server device is configured by the public network server device. The public network server device according to claim 62 is characterized in that the public network address information of the server device is generated based on the public network address of the public network server device. The public network server device according to any one of claims 62 to 64, wherein the sending unit is used to: Send the public network address information of the server device to the client device. The public network server device according to claim 65, characterized in that the sending unit is also used to: The public network address information of the public network server device is sent to the configuration device, where the public network address information of the public network server device is used to establish a connection between the public network server device and the client device. The public network server device according to claim 66, characterized in that the public network server device is in the ecological network of the configuration device, and the public network server device further comprises: A receiving unit, configured to receive second information for the public network server device sent by the configuration device through the ecological network, wherein the second information is used to establish a secure connection between the public network server device and the client device; The second information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The public network server device according to claim 62, characterized in that the sending unit is used to: Send the public network address information of the server device to the configuration device. The public network server device according to any one of claims 62-68 is characterized in that the public network address information of the server-side device is included in the first functional cluster of the public network server device. The public network server device according to claim 69 is characterized in that the first functional cluster also includes one or more of the following: the ecological network identifier of the server-side device and the node identifier of the server-side device. The public network server device according to claim 69 or 70 is characterized in that the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server-side device, and the type of public network address information includes static public network address information and dynamic public network address information. A server device, comprising: The establishing unit is used to establish a connection with the client device based on the public network address information, wherein the public network address information includes the public network address information of the client device and/or the public network address information of the server device. The server device according to claim 72 is characterized in that the public network address information of the server device is configured by a public network server device. The server device according to claim 72 is characterized in that the public network address information of the server device is generated based on the public network address of the public network server device. The server device according to any one of claims 72 to 74, characterized in that the server device is in an ecological network of a configuration device, and the server device further comprises: A receiving unit, configured to receive third information for the server device sent by the configuration device through the ecological network, wherein the third information is used to establish a secure connection between the server device and the client device; The third information includes one or more of the following: an operation certificate, an ecological network identifier, and a node identifier. The server device according to any one of claims 72-75 is characterized in that the public network address information of the server device is contained in the first functional cluster of the public network server device. The server device according to claim 76 is characterized in that the first functional cluster also includes one or more of the following: an ecological network identifier of the server device and a node identifier of the server device. The server device according to claim 76 or 77 is characterized in that the first functional cluster also includes first indication information, and the first indication information is used to indicate the type of public network address information in the server device, and the type of public network address information includes static public network address information and dynamic public network address information. A client device, characterized in that it comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method as described in any one of claims 1-11. A configuration device, characterized in that it comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method as described in any one of claims 12-22. A public network server device, characterized in that it includes a memory and a processor, the memory is used to store programs, and the processor is used to call the program in the memory to execute the method as described in any one of claims 23-32. A server device, characterized in that it includes a memory and a processor, the memory is used to store programs, and the processor is used to call the program in the memory to execute the method as described in any one of claims 33-39. A device, characterized in that it includes a processor, which is used to call a program from a memory to execute the method as described in any one of claims 1-39. A chip, characterized in that it includes a processor for calling a program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1 to 39. A computer-readable storage medium, characterized in that a program is stored thereon, wherein the program enables a computer to execute the method as described in any one of claims 1-39. A computer program product, characterized in that it comprises a program, wherein the program enables a computer to execute the method according to any one of claims 1 to 39. A computer program, characterized in that the computer program enables a computer to execute the method according to any one of claims 1 to 39.