CN116405505A

CN116405505A - Management method, system and storage medium

Info

Publication number: CN116405505A
Application number: CN202310350289.9A
Authority: CN
Inventors: 苗顺才
Original assignee: Ecarx Hubei Tech Co Ltd
Current assignee: Ecarx Hubei Tech Co Ltd
Priority date: 2023-03-30
Filing date: 2023-03-30
Publication date: 2023-07-07

Abstract

The invention discloses a management method, a management system and a storage medium. The method comprises the following steps: registering the target service to the SOA layer through the SDK layer; target service information corresponding to target service is obtained through the SOA layer, wherein the target service information comprises: the method comprises the steps that equipment information of service providing equipment is provided, wherein the service providing equipment is any physical equipment in a heterogeneous physical local area network; the target service information is synchronized to other physical devices except the service providing device in the heterogeneous physical local area network based on the network topology structure through the connection layer, and the service information synchronization of the physical devices in the heterogeneous physical local area network is realized under the condition of being compatible with different physical connection modes through the technical scheme of the invention.

Description

Management method, system and storage medium

Technical Field

The embodiment of the invention relates to the technical field of computers, in particular to a control method, a control system and a storage medium.

Background

The interaction between the physical devices at the present stage has various problems, so that the difficulty of cross-end and cross-domain collaborative interaction development is very high.

Because of the diversity of physical devices, the connection modes of various physical devices are different and the operating systems are different, so that no unified scheme can interact across the physical devices under the condition of being compatible with different physical connection modes at present.

Disclosure of Invention

The embodiment of the invention provides a management method, a management system and a storage medium, which are used for realizing service information synchronization of physical equipment in a heterogeneous physical local area network under the condition of being compatible with different physical connection modes.

According to an aspect of the present invention, there is provided a management method including:

registering the target service to the SOA layer through the SDK layer;

target service information corresponding to target service is obtained through the SOA layer, wherein the target service information comprises: the method comprises the steps that equipment information of service providing equipment is provided, wherein the service providing equipment is any physical equipment in a heterogeneous physical local area network;

and synchronizing the target service information to other physical devices except the service providing device in the heterogeneous physical local area network based on the network topology structure through a connection layer.

According to another aspect of the present invention, there is provided a management system including: an SDK layer, an SOA layer and a connection layer.

The SDK layer is used for registering the target service to the SOA layer;

the SOA layer is used for acquiring target service information corresponding to target service, wherein the target service information comprises: the method comprises the steps that equipment information of service providing equipment is provided, wherein the service providing equipment is any physical equipment in a heterogeneous physical local area network;

and the connection layer is used for synchronizing the target service information to other physical devices except the service providing device in the heterogeneous physical local area network based on a network topology structure.

According to another aspect of the present invention, there is provided an electronic apparatus including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the management method according to any one of the embodiments of the present invention.

According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to execute the management method according to any one of the embodiments of the present invention.

According to the embodiment of the invention, the target service is registered to the SOA layer through the SDK layer; target service information corresponding to target service is obtained through the SOA layer, wherein the target service information comprises: the method comprises the steps that equipment information of service providing equipment is provided, wherein the service providing equipment is any physical equipment in a heterogeneous physical local area network; and synchronizing the target service information to other physical devices except the service providing device in the heterogeneous physical local area network based on the network topology structure through the connection layer, so that the service information synchronization based on the physical devices in the heterogeneous physical local area network is realized under the condition of being compatible with different physical connection modes.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a method of management in an embodiment of the invention;

FIG. 2 is a schematic diagram of a service registration procedure in an embodiment of the present invention;

FIG. 3 is a schematic diagram of a heterogeneous network physical connection in an embodiment of the present invention;

FIG. 4 is a schematic diagram of a data structure of description information of a physical device in an embodiment of the present invention;

FIG. 5 is a schematic diagram of a data structure of connection information of a physical device in an embodiment of the present invention;

FIG. 6 is a schematic diagram of a data structure when devices are not connected in an embodiment of the present invention;

FIG. 7 is a schematic diagram of a data structure of a device A and a device B after connection in an embodiment of the present invention;

FIG. 8 is a schematic diagram of a data structure of a device B and a device C after connection in an embodiment of the present invention;

FIG. 9 is a schematic diagram of a data structure of a target service in an embodiment of the invention;

FIG. 10 is a schematic diagram of a management system according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of a hierarchical architecture of a management system in an embodiment of the invention;

fig. 12 is a schematic structural diagram of an electronic device in an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It will be appreciated that prior to using the technical solutions disclosed in the embodiments of the present disclosure, the user should be informed and authorized of the type, usage range, usage scenario, etc. of the personal information related to the present disclosure in an appropriate manner according to the relevant legal regulations.

Example 1

Fig. 1 is a flowchart of a management method provided in an embodiment of the present invention, where the embodiment is applicable to a case of managing service information between physical devices in a heterogeneous physical local area network, the method may be performed by a management system in the embodiment of the present invention, and the system may be implemented in a software and/or hardware manner, as shown in fig. 1, where the method specifically includes the following steps:

s110, registering the target service to the SOA layer through the SDK layer.

Wherein the SDK layer is used by a service providing and using layer. The primary capability is the ability to expose the SOA layer to both the provider of the service and the consumer of the service. For example, for a service provider, the SDK layer provides "registration capability of service" in the SOA layer to the service provider; for a service user, the SDK layer provides the service user with "query for service" and "call for service" capabilities in the SOA layer.

The SOA layer builds a cross-platform service-oriented service development and management framework. The SOA layer provides definition of services, management of services, and synchronization of service information to other physical devices of the heterogeneous local area network using the logical connection layer. So that physical devices within the heterogeneous local area network may use remote services as well as local services.

Specifically, the manner of registering the target service to the SOA layer through the SDK layer may be: service information of the target service is obtained in advance through a service providing and using layer, and then the target service is registered to an SOA layer through an SDK layer based on the service information of the target service.

S120, obtaining target service information corresponding to target service through an SOA layer, wherein the target service information comprises: device information of a service providing device, wherein the service providing device is any physical device in a heterogeneous physical local area network.

Wherein the target service information includes: service information of the target service and device information of the service providing device.

The heterogeneous physical local area network is a heterogeneous physical local area network between at least two physical devices established through a physical connection layer.

Specifically, the method for obtaining the target service information corresponding to the target service through the SOA layer may be: and inquiring the connection layer through the SOA layer to obtain the equipment information of the service providing equipment in the connection layer, and adding the equipment information of the service providing equipment to the service information of the target service through the SOA layer to obtain the target service information. The method for obtaining the target service information corresponding to the target service through the SOA layer may also be: and receiving broadcast information of other physical devices through the SOA layer, and determining target service information according to the received broadcast information through the SOA layer.

And S130, synchronizing the target service information to other physical devices except the service providing device in the heterogeneous physical local area network based on the network topology structure through a connection layer.

It should be noted that, the generation manner of the network topology structure may be: and acquiring the description information and the connection information of the physical equipment in the heterogeneous physical local area network through the logic connection layer, and generating a network topology structure according to the description information and the connection information of the physical equipment.

Specifically, the method for synchronizing the target service information to other physical devices except the service providing device in the heterogeneous physical local area network through the connection layer based on the network topology may be: determining a target physical device connection mode and an address of target physical devices based on a network topology structure through a logic connection layer, wherein the target physical devices are other physical devices except service providing devices in a heterogeneous physical local area network; and broadcasting the target service information through a physical connection layer according to the connection mode of the target physical equipment and the address of the target physical equipment.

Optionally, the connection layer includes: a logical connection layer and a physical connection layer;

synchronizing, by a connection layer, the target service information to other physical devices in the heterogeneous physical local area network, excluding the service providing device, based on a network topology, including:

determining a target physical device connection mode and an address of target physical devices based on a network topology structure through a logic connection layer, wherein the target physical devices are other physical devices except service providing devices in a heterogeneous physical local area network;

and broadcasting the target service information through a physical connection layer according to the connection mode of the target physical equipment and the address of the target physical equipment.

The target physical device connection manner may include: at least one of WIFI, bluetooth, USB, CAN bus, and NFC.

Wherein the network topology comprises: description information of the current service device and connection information of the current service device.

Specifically, the method of determining, by the logical connection layer, the connection mode of the target physical device and the address of the target physical device based on the network topology may be that the connection information of the current service device is determined by the logical connection layer based on the network topology, and the connection mode of the target physical device and the address of the target physical device are determined according to the connection information of the current service device.

Optionally, broadcasting, by the physical connection layer, the target service information according to the connection mode of the target physical device and the address of the target physical device includes:

encapsulating the target service information based on a target physical equipment connection mode through a logic connection layer to obtain a target data packet;

and broadcasting the target data packet through a physical connection layer according to the connection mode of the target physical device and the address of the target physical device.

Specifically, the method for encapsulating the target service information based on the target physical device connection mode by the logic connection layer may be that: and determining a target protocol based on a target physical equipment connection mode through the logic connection layer, and packaging the target service information based on the target protocol through the logic connection layer.

Specifically, the manner of broadcasting the target data packet according to the connection manner of the target physical device and the address of the target physical device through the physical connection layer may be: and broadcasting the target service information through a physical connection layer according to the connection mode of the target physical equipment, the address of the target physical equipment and the target protocol.

In a specific example, as shown in fig. 2, the a device is connected to the B device through WiFi, and the B device is connected to the C device through bluetooth. The device A registers a target service, synchronizes the target service on the device A to the device B (the device B receives the WiFi broadcast packet of the device A), analyzes the WiFi broadcast packet on the device B, packages the WiFi broadcast packet into a Bluetooth data packet, and broadcasts the Bluetooth data packet to the device C through a Bluetooth channel. Up to now A, B, C, three device nodes have registered services: demoServ, and identifies the device (i.e., service providing device) where the target service is located through the deviceId field. Eventually, all devices of the heterogeneous network will have information about the service. Thus, the remote device may use the service as if it were a local service.

Optionally, the method further comprises:

sending a call service request to the SOA layer through the SDK layer;

acquiring identification information of service providing equipment carried by a call service request through an SOA layer;

and if the non-service providing device of the current service device is determined according to the identification information of the service providing device, sending a call service request to the service providing device through the connection layer.

Specifically, the manner of determining whether the current service device is the service providing device according to the identification information of the service providing device may be: the determining according to the deviceId of the current service device and the deviceId of the service providing device may be, for example, determining that the current service device is the service providing device if the deviceId of the current service device is the same as the deviceId of the service providing device, and determining that the current service device is not the service providing device if the deviceId of the current service device is different from the deviceId of the service providing device.

sending the call service request to the service providing device through the connection layer, comprising:

generating a target request based on the calling service request and the identification information of the current service equipment through a logic connection layer, and inquiring a network topology structure according to the identification information of the service providing equipment to determine the address of the service providing equipment and the connection mode of the service providing equipment;

and sending the target request to the service providing equipment through the physical connection layer according to the address of the service providing equipment and the connection mode of the service providing equipment.

The connection mode of the service providing device comprises the following steps: at least one of a WIFI connection, a bluetooth connection, a USB connection, a CAN bus connection, and an NFC connection.

Wherein the target request includes: invoking a service request and identification information of a current service device.

Optionally, the method further comprises:

the target service equipment inquires a network topology structure through a logic connection layer according to the identification information of the current service equipment carried by the target request to determine the address and the connection mode of the current service equipment;

and the target service equipment sends the feedback information to the current service equipment through the physical connection layer according to the address and the connection mode of the current service equipment.

The feedback information is generated by the service providing equipment according to the service calling request.

Specifically, after adding necessary device information to the local service, the SOA layer broadcasts the local service to the heterogeneous network, and each device stores the registered service to the local after receiving the broadcast of the service registration. Each device will continue to broadcast the service registration broadcast on the other devices to which it is connected. Services if transmissions across heterogeneous networks are involved, there may be a process of unpacking and repackaging transmissions at nodes across heterogeneous networks. Eventually, all devices of the heterogeneous network will have information about the service. Thus, the remote device may use the service as if it were a local service. When the service is used, the calling request route is sent to the corresponding equipment according to the equipment information of the service, and after the service on the corresponding equipment processes the request, the processing result is returned to the remote equipment in an original route.

In a specific example, the call service request is sent to the SOA layer through the SDK layer; acquiring identification information of service providing equipment carried by a call service request through an SOA layer; if the non-service providing equipment of the current service equipment is determined according to the identification information of the service providing equipment, namely the current service equipment is service using equipment, the service using equipment generates a target request based on the calling service request and the identification information of the current service equipment through a logic connection layer, and inquires a network topological structure according to the identification information of the service providing equipment to determine the address of the service providing equipment and the connection mode of the service providing equipment; the service using device sends a target request to the service providing device through a physical connection layer according to the address of the service providing device and the connection mode of the service providing device, the service providing device generates feedback information according to the target request after receiving the target request, the service providing device determines the address and the connection mode of the service using device according to the identification information of the service using device carried by the target request, and the service providing device sends the feedback information to the service using device according to the address and the connection mode of the service using device.

In another specific example, as shown in fig. 2, assuming that DemoServ is invoked on the C device, the logical connection layer will route the usage request of the target service to the a device according to the deviceId field (device information of the service providing device in the target service information) and the network topology.

Optionally, before determining, by the logical connection layer, the connection mode of the target physical device and the address of the target physical device based on the network topology, the method further includes:

and establishing a heterogeneous physical local area network between at least two physical devices through a physical connection layer, wherein the physical devices comprise: terminal equipment and/or vehicle-mounted equipment;

and acquiring the description information and the connection information of the physical equipment in the heterogeneous physical local area network through the logic connection layer, and generating a network topology structure according to the description information and the connection information of the physical equipment.

The vehicle-mounted device can be each domain of the vehicle body.

Optionally, establishing a heterogeneous physical local area network between at least two physical devices through a physical connection layer includes:

obtaining a physical connection type between at least two physical devices through a physical connection layer, wherein the physical connection type comprises: at least one of WIFI, bluetooth, USB, CAN bus, and NFC;

and establishing a heterogeneous physical local area network between the at least two physical devices according to the physical connection type between the at least two physical devices through the physical connection layer.

Wherein the physical device comprises: terminal device and/or vehicle-mounted device.

The various intelligent terminals and the respective domains of the vehicle body need to be physically connected to each other. The physical connection method can be various, the physical connection relation of the heterogeneous network is shown in fig. 3, and the connection between the intelligent terminal and each vehicle body domain is not limited to only one or a plurality of physical connection modes. For example, the Android mobile phone and the IOS mobile phone can be connected with the car machine through any one of WiFi, bluetooth and USB connection, and the connection between the car machine and other car body domains can be shared memory, car ethernet and the like.

Specifically, if the physical device includes: and the terminal equipment and the vehicle-mounted equipment establish heterogeneous physical local area networks between the terminal equipment and each domain of the vehicle body.

Optionally, the method for obtaining the description information and the connection information of the physical devices in the heterogeneous physical local area network through the logic connection layer, and generating the network topology structure according to the description information and the connection information of the physical devices includes:

the method comprises the steps of obtaining description information of physical equipment in a heterogeneous physical local area network through a logic connection layer, wherein the description information comprises the following steps: identification of the physical device, name of the physical device, and IP address of the physical device;

when physical connection is established between the physical devices, generating connection information corresponding to each physical device through a logic connection layer;

and generating a network topology structure based on the description information of each physical device and the corresponding connection information of the physical devices in the heterogeneous physical local area network through the logic connection layer.

Optionally, the description information of the physical device includes: the identification of the physical device, the name of the physical device and the IP address of the physical device, and the connection information of the physical device includes: the identity of the connection device, the name of the connection device, the IP address of the connection device, and the connection type.

The description information of the physical device is a general and abstract data structure identifier of the physical device in the logical connection layer, for example, the data structure of the description information of the physical device is shown in fig. 4, and the meanings of the fields are described as follows: unique identifier of the device at the logic connection layer, when the physical device is accessed to the heterogeneous network, the unique identifier is distributed by the logic connection layer; the deviceName is the unique identifier of the physical device on the physical connection layer, and after the device is accessed to the physical connection layer, the physical connection layer reports the deviceName to the logical connection layer. The two fields deviceName and deviceId complete the device mapping between the physical connection layer and the logical connection layer. deviceIp: IP address of device.

The connection information of the physical device may be a data structure array ConnectInfo [ ] representing the connection information. The concrete definition of ConnectInfo is shown in FIG. 5: the meaning of the fields of ConnectInfo is illustrated as follows:

connectieddeviceid: device Id of the connected device;

connectieddevicename, device name of the connected device;

connectieddeviceip, the IP address of the connected device;

connectiedtype-type of connection with the device, such as bluetooth, wiFi, etc.

In a specific example, three physical devices A, B, C are assumed, and with the establishment of physical connection, the heterogeneous network topology architecture establishment flow of the logical connection layer is as follows:

as shown in fig. 6, when three devices are not connected independently of each other, the logical connection layer has only DeviceInfo information of each device, and connectioninfo information is null.

As shown in fig. 7, when the device a and the device B establish a physical connection through WiFi, the two devices exchange information with each other based on the physical connection, and maintain the information in respective ConnectionInfos.

As shown in fig. 8, when the device B and the device C establish a physical connection through bluetooth, the two devices exchange information with each other based on the physical connection and maintain the information in respective ConnectionInfos.

As shown in the above flow, as different heterogeneous network devices continuously join the network, a logical network topology structure is gradually formed at the logical connection layer.

Optionally, the management system further includes: a service providing and using layer;

registering the target service to the SOA layer through the SDK layer comprises the following steps:

acquiring service information of a target service through a service providing and using layer;

registering the target service to the SOA layer based on the service information of the target service through the SDK layer.

The SOA layer agrees with a basic data structure for each service, and a definition of the data structure is shown in fig. 9, where the meaning of each field of the DistributeService is described as follows:

serviceName: service name of current service

functionName: there may be multiple function names provided by the current service.

According to the technical scheme, the target service is registered to the SOA layer through the SDK layer; target service information corresponding to target service is obtained through the SOA layer, wherein the target service information comprises: the method comprises the steps that equipment information of service providing equipment is provided, wherein the service providing equipment is any physical equipment in a heterogeneous physical local area network; and synchronizing the target service information to other physical devices except the service providing device in the heterogeneous physical local area network based on the network topology structure through the connection layer, so that the service information synchronization of the physical devices in the heterogeneous physical local area network is realized under the condition of being compatible with different physical connection modes.

Example two

Fig. 10 is a schematic structural diagram of a management system according to an embodiment of the present invention. The present embodiment may be applied to the case of managing service information between physical devices in a heterogeneous physical local area network, where the system may be implemented in software and/or hardware, as shown in fig. 10, and the management system specifically includes: an SDK layer 210, an SOA layer 220, and a connection layer 230.

The SDK layer is used for registering the target service to the SOA layer;

Optionally, the connection layer 230 includes: logical connection layer and physical connection layer.

The physical connection layer is used for establishing a physical local area network between physical devices, and because of various intelligent terminals and various domains of a vehicle body, mutual physical connection is needed. The physical connection method can be various, for example, the Android mobile phone and the IOS mobile phone can be connected with the vehicle machine through any one of WiFi, bluetooth and USB connection, and the connection between the vehicle machine and other vehicle body domains can be shared memory, vehicle-mounted Ethernet and the like. Therefore, it is necessary to establish a physical local area network between physical devices according to the type of physical connection between the physical devices.

Optionally, the management system further includes: a cross-device OS layer and a provision and use layer of services, the cross-device OS layer representing that embodiments of the present invention may run on any physical device, including but not limited to: android, linux, IOS, windows and other embedded devices and non-embedded devices of different operating systems, embodiments of the present invention may also operate on various domains of the vehicle body, such as IVI, cluster, and the like. The developer develops own service based on the SDK, exposes the developed service to other intelligent devices or vehicle body domains in the local area network through the SDK layer, and allows the other intelligent devices or vehicle body domains to use remote service like using local service, obtain service information through the service providing and using layer, and further register target service to the SOA layer through the SDK layer according to the service information.

In a specific example, as shown in fig. 11, the management system includes: the cross-device cross-OS layer, the physical connection layer, the logical connection layer, the SOA layer, the SDK layer and the service providing and using layer. And the cross-equipment and cross-OS layer supports Android equipment, linux equipment, IOS equipment, vehicle IVI and various domains of a vehicle body, the physical connection layer supports USB connection, WIFI connection, bluetooth connection, NFC connection and vehicle-mounted Ethernet, and the logical connection layer supports equipment discovery, equipment logical connection, data transmission and cross-network section protocol conversion. The SOA layer supports service discovery, service information cross-terminal synchronization, service scheduling, and service lifecycle management. The SDK layer supports service development frameworks, service registration, service queries, and service invocation. The provision and use layer of services supports service provider APP and service consumer APP.

The product can execute the method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Example III

Fig. 12 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 12, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the respective methods and processes described above, such as the management method.

In some embodiments, the management method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the management method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the management method in any other suitable way (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. A method of management, performed by a management system, the management system comprising: the management method comprises the following steps of:

registering the target service to the SOA layer through the SDK layer;

2. The method of claim 1, wherein the connection layer comprises: a logical connection layer and a physical connection layer;

3. The method of claim 2, wherein broadcasting the target service information through the physical connection layer according to the target physical device connection manner and the address of the target physical device comprises:

4. The method as recited in claim 1, further comprising:

sending a call service request to the SOA layer through the SDK layer;

5. The method of claim 4, wherein the connection layer comprises: a logical connection layer and a physical connection layer;

6. The method of claim 2, further comprising, prior to determining, by the logical connection layer, the target physical device connection and the address of the target physical device based on the network topology:

7. The method of claim 6, wherein the description information of the physical device includes: the identification of the physical device, the name of the physical device and the IP address of the physical device, and the connection information of the physical device includes: the identity of the connection device, the name of the connection device, the IP address of the connection device, and the connection type.

8. The method of claim 1, wherein the management system further comprises: a service providing and using layer;

9. A management system, characterized in that it performs the management method according to any one of the preceding claims 1-7, said management system comprising: an SDK layer, an SOA layer and a connection layer;

the SDK layer is used for registering the target service to the SOA layer;

10. A computer readable storage medium, characterized in that the computer readable storage medium stores computer instructions for causing a processor to implement the management method of any one of claims 1-8 when executed.