A management method, system and storage medium

Abstract

The application discloses a management method, a system and a storage medium. The method comprises the following steps: registering a target service to an SOA layer through an SDK layer; acquiring target service information corresponding to the target service through the SOA layer, wherein the target service information comprises device information of a service providing device, and the service providing device is any physical device in a heterogeneous physical local area network; and synchronizing the target service information to other physical devices in the heterogeneous physical local area network except the service providing device based on a network topology through a connection layer. Through the technical scheme, the service information of the physical devices in the heterogeneous physical local area network is synchronized under the condition of compatibility of different physical connection modes.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of computer, and particularly relate to a control method and system and storage medium. BACKGROUND

[0002] At present, there are various problems in the interaction between physical devices, which leads to great difficulty in cross-end and cross-domain collaborative interaction development.

[0003] Due to the diversity of physical devices, the connection modes and operating systems of various physical devices are different, which leads to the fact that there is no unified solution to cross-physical device interaction under the condition of compatible different physical connection modes. SUMMARY

[0004] Embodiments of the present application provide a management method and system and storage medium to realize the synchronization of service information of physical devices in a heterogeneous physical local area network under the condition of compatible different physical connection modes.

[0005] According to an aspect of the present application, a management method is provided, comprising:

[0006] registering a target service to an SOA layer through an SDK layer;

[0007] obtaining target service information corresponding to the target service through the SOA layer, wherein the target service information comprises device information of a service providing device, and the service providing device is any physical device in a heterogeneous physical local area network;

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

[0009] According to another aspect of the present application, a management system is provided, comprising an SDK layer, an SOA layer and a connection layer.

[0010] The SDK layer is configured to register a target service to an SOA layer;

[0011] The SOA layer is configured to obtain target service information corresponding to the target service, wherein the target service information comprises device information of a service providing device, and the service providing device is any physical device in a heterogeneous physical local area network;

[0012] The connection layer is configured to synchronize the target service information to other physical devices in the heterogeneous physical local area network except the service providing device based on a network topology structure.

[0013] According to another aspect of the present application, an electronic device is provided, comprising:

[0014] at least one processor; and

[0015] a memory communicatively connected with the at least one processor; wherein,

[0016] the memory stores a computer program executable by the at least one processor, and the computer program is executed 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 application.

[0017] According to another aspect of the present application, a computer readable storage medium is provided, which stores computer instructions for enabling a processor to implement the management method according to any one of the embodiments of the present application when executed.

[0018] The embodiments of the present application register the target service to the SOA layer through the SDK layer; acquire the target service information corresponding to the target service through the SOA layer, wherein the target service information comprises device information of a service providing device, and the service providing device is any physical device in a heterogeneous physical local area network; and synchronize the target service information to other physical devices in the heterogeneous physical local area network except the service providing device based on the network topology through the connection layer, thereby realizing the service information synchronization based on the physical devices in the heterogeneous physical local area network in the case of compatible different physical connection modes.

[0019] It should be understood that the content described in this part is not intended to identify key or important features of the embodiments of the present application, nor to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some of the embodiments of the present application, and therefore should not be regarded as limiting the scope. For those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings.

[0021] Figure 1 is a flow chart of a management method in the embodiments of the present application;

[0022] Figure 2 is a service registration process schematic diagram in the embodiments of the present application;

[0023] Figure 3 is a heterogeneous network physical connection schematic diagram in the embodiments of the present application;

[0024] Figure 4Figure 1 is a data structure schematic diagram of the description information of the physical device in the embodiment of the present application;

[0025] Figure 5 Figure 2 is a data structure schematic diagram of the connection information of the physical device in the embodiment of the present application;

[0026] Figure 6 Figure 3 is a data structure schematic diagram of each device when not connected in the embodiment of the present application;

[0027] Figure 7 Figure 4 is a data structure schematic diagram of the device A and the device B after being connected in the embodiment of the present application;

[0028] Figure 8 Figure 5 is a data structure schematic diagram of the device B and the device C after being connected in the embodiment of the present application;

[0029] Figure 9 Figure 6 is a data structure schematic diagram of the target service in the embodiment of the present application;

[0030] Figure 10 Figure 7 is a structure schematic diagram of a management system in the embodiment of the present application;

[0031] Figure 11 Figure 8 is a hierarchical architecture schematic diagram of a management system in the embodiment of the present application;

[0032] Figure 12 Figure 9 is a structure schematic diagram of an electronic device in the embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the personnel in the art better understand the present application scheme, the technical scheme in the embodiment of the present application will be described clearly and completely in the following with reference to the drawings in the embodiment of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all the other embodiments obtained by the person of ordinary skill in the art without making creative labor should belong to the protection scope of the present application.

[0034] It should be noted that the terms "first", "second", and the like in the description and claims of the application and the above drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the application described herein can be implemented in other than the order illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a list of steps or units does not necessarily limit those steps or units to the clearly listed ones, but can include other steps or units not clearly listed or inherent to such processes, methods, products or devices.

[0035] It can be understood that, before using the technical solutions disclosed in the embodiments of the present disclosure, the type, use range, use scenario, etc. of the personal information involved in the present disclosure should be informed to the user and the authorization of the user should be obtained according to relevant laws and regulations.

[0036] Embodiment one

[0037] Figure 1 A flowchart of a management method provided for the embodiments of the present application, the present embodiment can be applicable to the management of service information between physical devices in a heterogeneous physical local area network. The method can be executed by the management system in the embodiments of the present application, which can be realized in the form of software and / or hardware. As shown in the figure, the method specifically includes the following steps: Figure 1

[0038] S110, register the target service to the SOA layer through the SDK layer.

[0039] The SDK layer is used by the service providing and using layer. The main capability is to expose the capability of the SOA layer to the service provider and the service user. For example, for the service provider, the SDK layer provides the "service registration capability" in the SOA layer to the service provider; for the service user, the SDK layer provides the "service query" and "service call" capabilities in the SOA layer to the service user.

[0040] The SOA layer builds a cross-platform, service-oriented service development and management framework. The SOA layer provides service definition, service management, and synchronization of service information to other physical devices in the heterogeneous local area network by using the logical connection layer. The physical devices in the heterogeneous local area network can use remote services as if they are using local services.

[0041] ​Specifically, the target service can be registered to the SOA layer through the SDK layer in the following manner: service information of the target service is acquired through the service providing and using layer in advance, and the target service is registered to the SOA layer based on the service information of the target service through the SDK layer.

[0042] In S120, target service information corresponding to the target service is acquired through the SOA layer, wherein the target service information comprises device information of a service providing device, and the service providing device is any physical device in the heterogeneous physical local area network.

[0043] The target service information comprises service information of the target service and device information of the service providing device.

[0044] 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.

[0045] Specifically, the target service information corresponding to the target service can be acquired through the SOA layer in the following manner: the SOA layer is queried to obtain device information of the service providing device in the connection layer, the device information of the service providing device is added to the service information of the target service through the SOA layer, and the target service information is obtained. The target service information corresponding to the target service can also be acquired through the SOA layer in the following manner: the SOA layer receives broadcast information of other physical devices, and the target service information is determined according to the received broadcast information through the SOA layer.

[0046] In S130, the target service information is synchronized to other physical devices in the heterogeneous physical local area network except the service providing device through the connection layer based on the network topology structure.

[0047] It should be noted that the network topology structure can be generated in the following manner: description information and connection information of the physical devices in the heterogeneous physical local area network are acquired through the logical connection layer, and the network topology structure is generated according to the description information and the connection information of the physical devices.

[0048] Specifically, the target service information can be synchronized to other physical devices in the heterogeneous physical local area network except the service providing device through the connection layer based on the network topology structure in the following manner: a target physical device connection mode and an address of the target physical device are determined based on the network topology structure through the logical connection layer, wherein the target physical device is other physical device in the heterogeneous physical local area network except the service providing device; and the target service information is broadcasted according to the target physical device connection mode and the address of the target physical device through the physical connection layer.

[0049] Optionally, the connection layer comprises a logical connection layer and a physical connection layer.

[0050] synchronizing the target service information to other physical devices in the heterogeneous physical local area network except the service providing device based on the network topology structure through the logical connection layer, including:

[0051] determining the connection mode of the target physical device and the address of the target physical device based on the network topology structure through the logical connection layer, wherein the target physical device is other physical device in the heterogeneous physical local area network except the service providing device;

[0052] broadcasting the target service information according to the connection mode of the target physical device and the address of the target physical device through the physical connection layer.

[0053] The connection mode of the target physical device can include at least one of WIFI, Bluetooth, USB, CAN bus and NFC.

[0054] The network topology structure includes description information of the current service device and connection information of the current service device.

[0055] Specifically, the way of determining the connection mode of the target physical device and the address of the target physical device based on the network topology structure through the logical connection layer can be determining the connection information of the current service device based on the network topology structure through the logical connection layer, and determining the connection mode of the target physical device and the address of the target physical device according to the connection information of the current service device.

[0056] Optionally, broadcasting the target service information according to the connection mode of the target physical device and the address of the target physical device through the physical connection layer includes:

[0057] encapsulating the target service information based on the connection mode of the target physical device through the logical connection layer to obtain a target data packet;

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

[0059] Specifically, the way of encapsulating the target service information based on the connection mode of the target physical device through the logical connection layer to obtain a target data packet can be determining a target protocol based on the connection mode of the target physical device through the logical connection layer, and encapsulating the target service information based on the target protocol through the logical connection layer.

[0060] Specifically, the way of broadcasting the target data packet according to the connection mode of the target physical device and the address of the target physical device through the physical connection layer can be broadcasting the target service information according to the connection mode of the target physical device, the address of the target physical device and the target protocol through the physical connection layer.

[0061] In one specific example, as Figure 2As shown, Figure 2 A device and a B device are connected through WiFi, and the B device and a C device are connected through Bluetooth. A target service is registered on the A device, and the target service on the A device is synchronized to the B device (the B device receives a WiFi broadcast packet of the A device). The B device parses the WiFi broadcast packet and then packs the WiFi broadcast packet into a Bluetooth data packet, and then broadcasts the Bluetooth data packet to the C device through a Bluetooth channel. Thus, the DemoServ service is registered on the A, B and C devices, and the device (i.e., a service providing device) where the target service is located is identified through a deviceId field. Finally, the information of the service is on all devices in the heterogeneous network. Therefore, a remote device can use the service as using a local service.

[0062] Optionally, the method further comprises:

[0063] The SDK layer sends the service request to the SOA layer;

[0064] The SOA layer obtains the identification information of the service providing device carried by the service request;

[0065] If it is determined according to the identification information of the service providing device that the current service device is not the service providing device, the connection layer sends the service request to the service providing device.

[0066] Specifically, the way of determining whether the current service device is the service providing device according to the identification information of the service providing device can be: judging according to the deviceId of the current service device and the deviceId of the service providing device, for example, if the deviceId of the current service device is the same as the deviceId of the service providing device, it is determined that the current service device is the service providing device, and if the deviceId of the current service device is different from the deviceId of the service providing device, it is determined that the current service device is not the service providing device.

[0067] Optionally, the connection layer comprises a logical connection layer and a physical connection layer.

[0068] The connection layer sends the service request to the service providing device, comprising:

[0069] The logical connection layer generates a target request based on the service request and the identification information of the current service device, and queries a network topology structure according to the identification information of the service providing device to determine an address of the service providing device and a connection mode of the service providing device.

[0070] The physical connection layer sends the target request to the service providing device according to the address of the service providing device and the connection mode of the service providing device.

[0071] The connection mode of the service providing device includes at least one of WIFI connection, Bluetooth connection, USB connection, CAN bus connection and NFC connection.

[0072] The target request includes a calling service request and identification information of the current service device.

[0073] Optionally, the method further comprises:

[0074] The target service device determines the address and the connection mode of the current service device according to the identification information of the current service device carried by the target request through the logical connection layer;

[0075] The target service device sends the feedback information to the current service device according to the address and the connection mode of the current service device through the physical connection layer.

[0076] The feedback information is feedback information generated by the service providing device according to the calling service request.

[0077] Specifically, the SOA layer broadcasts the local service to the heterogeneous network after adding necessary device information to the local service, and each device saves the registered service to the local after receiving the broadcast of the service registration. Each device continues to broadcast the service registration on other devices connected by the device. If the service involves cross-heterogeneous network transmission, there will be a process of unpacking and repacking transmission on the cross-heterogeneous network node. Finally, all devices in the heterogeneous network have information of the service. Therefore, the remote device can use the service like using the local service. When using the service, the calling request is routed to the corresponding device according to the device information of the service, and the service on the corresponding device returns the processing result to the remote device via the original route after processing the request.

[0078] In one specific example, the service request is sent to the SOA layer through the SDK layer; the identification information of the service providing device carried by the service request is obtained through the SOA layer; if it is determined according to the identification information of the service providing device that the current service device is not the service providing device, that is, the current service device is the service using device, the service using device generates a target request based on the service request and the identification information of the current service device through the logical connection layer, and determines the address of the service providing device and the connection mode of the service providing device according to the network topology structure according to the identification information of the service providing device; the service using device sends the target request to the service providing device through the physical connection layer according to the address of the service providing device and the connection mode of the service providing device, and the service providing device generates feedback information according to the target request after receiving the target request, determines the address and connection mode of the service using device according to the identification information of the service using device carried by the target request, and sends the feedback information to the service using device according to the address and connection mode of the service using device.

[0079] In another specific example, as shown in Figure 2 Assuming that DemoServ is called on the C device, the logical connection layer routes the use request of the target service to the A device according to the deviceId field (the device information of the service providing device in the target service information) and the network topology structure.

[0080] Optionally, before determining the connection mode and the address of the target physical device based on the network topology structure through the logical connection layer, the method further comprises:

[0081] The heterogeneous physical local area network between the at least two physical devices is established through the physical connection layer, wherein the physical devices include a terminal device and / or a vehicle-mounted device.

[0082] The description information and the connection information of the physical devices in the heterogeneous physical local area network are obtained through the logical connection layer, and the network topology structure is generated according to the description information and the connection information of the physical devices.

[0083] The vehicle-mounted device can be each domain of a vehicle body.

[0084] Optionally, the heterogeneous physical local area network between the at least two physical devices is established through the physical connection layer, comprising:

[0085] The physical connection type between the at least two physical devices is obtained through the physical connection layer, wherein the physical connection type includes at least one of WIFI, Bluetooth, USB, CAN bus and NFC.

[0086] The heterogeneous physical local area network between the at least two physical devices is established according to a physical connection type between the at least two physical devices through a physical connection layer.

[0087] The physical device includes a terminal device and / or a vehicle-mounted device.

[0088] It should be noted that various intelligent terminals and vehicle body domains need to be physically connected to each other. The physical connection method can be various, and the heterogeneous network physical connection relationship is as shown in Figure 3 The connection between the intelligent terminal and each vehicle body domain is not limited to using only one or several physical connection methods. For example, an Android mobile phone and an IOS mobile phone can be connected to a car machine through any one of WiFi, Bluetooth, and USB connection, and the connection between the car machine and other vehicle body domains can be shared memory, vehicle-mounted Ethernet, and the like.

[0089] Specifically, if the physical device includes a terminal device and a vehicle-mounted device, a heterogeneous physical local area network between the terminal device and each vehicle body domain is established.

[0090] Optionally, description information and connection information of the physical device in the heterogeneous physical local area network are acquired through a logical connection layer, and a network topology structure is generated according to the description information and the connection information of the physical device, including:

[0091] The description information of the physical device in the heterogeneous physical local area network is acquired through the logical connection layer, and the description information includes an identifier of the physical device, a name of the physical device, and an IP address of the physical device.

[0092] When the physical connection between the physical devices is established, the connection information corresponding to each physical device is generated through the logical connection layer.

[0093] The network topology structure is generated based on the description information of each physical device in the heterogeneous physical local area network and the connection information corresponding to the physical device through the logical connection layer.

[0094] Optionally, the description information of the physical device includes an identifier of the physical device, a name of the physical device, and an IP address of the physical device, and the connection information of the physical device includes an identifier of a connected device, a name of the connected device, an IP address of the connected device, and a connection type.

[0095] 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 can be as shown in Figure 4As shown, the meanings of the fields are as follows: deviceId: the unique identifier of the device in the logical connection layer, which is assigned by the logical connection layer when the physical device accesses the heterogeneous network; deviceName: the device name, which is the unique identifier of the physical device in the physical connection layer, and the physical connection layer will report the deviceName to the logical connection layer after the device accesses the physical connection layer. The deviceName and the deviceId complete the device mapping between the physical connection layer and the logical connection layer. deviceIp: the IP address of the device.

[0096] The connection information of the physical device can be an array ConnectInfo[] of data structures representing the connection information. The specific definition of ConnectInfo is as follows: Figure 5 As shown, the meanings of the fields of ConnectInfo are as follows:

[0097] connectedDeviceId: the device Id of the connected device;

[0098] connectedDeviceName: the device name of the connected device;

[0099] connectedDeviceIp: the IP address of the connected device;

[0100] connectedType: the connection type with the device, such as Bluetooth, WiFi, etc.

[0101] In a specific example, assume that there are three physical devices A, B, and C, and the logical connection layer heterogeneous network topology architecture establishment process is as follows when the physical connections between them are established:

[0102] As shown in Figure 6 When the three devices are independent and not connected, the logical connection layer only has the DeviceInfo information of each device, and the ConnectionInfos information is empty.

[0103] As shown in Figure 7 When the device A and the device B establish a physical connection through WiFi, the two devices will exchange information based on the physical connection and maintain in their respective ConnectionInfos.

[0104] As shown in Figure 8 When the device B and the device C establish a physical connection through Bluetooth, the two devices will exchange information based on the physical connection and maintain in their respective ConnectionInfos.

[0105] As shown in the above flow, as different heterogeneous network devices are continuously added to the network, a logical network topology is gradually formed at the logical connection layer.

[0106] Optionally, the management system further comprises a service providing and using layer.

[0107] The target service is registered to the SOA layer through the SDK layer, including:

[0108] The service information of the target service is acquired through the service providing and using layer.

[0109] The target service is registered to the SOA layer based on the service information of the target service through the SDK layer.

[0110] The SOA layer defines a basic data structure for each service, and the definition of the data structure is shown in the following table: Figure 9 The meanings of the fields of the DistributeService are as follows:

[0111] serviceName: the service name of the current service

[0112] functionName: the function name provided by the current service, which can be multiple.

[0113] The technical scheme of the embodiment registers the target service to the SOA layer through the SDK layer; acquires the target service information corresponding to the target service through the SOA layer, wherein the target service information includes the device information of a service providing device, and the service providing device is any physical device in the heterogeneous physical local area network; and synchronizes the target service information to other physical devices in the heterogeneous physical local area network except the service providing device based on the network topology through the connection layer, thereby realizing the synchronization of the service information of the physical devices in the heterogeneous physical local area network under the condition of compatibility of different physical connection modes.

[0114] Embodiment Two

[0115] Figure 10 A structure diagram of a management system provided by the embodiment of the application is shown in the following table: Figure 10 The management system specifically comprises an SDK layer 210, an SOA layer 220, and a connection layer 230.

[0116] The SDK layer is configured to register a target service to the SOA layer.

[0117] The SOA layer is configured to acquire target service information corresponding to a target service, wherein the target service information comprises device information of a service providing device, and the service providing device is any physical device in a heterogeneous physical local area network.

[0118] The connection layer is configured to synchronize the target service information to other physical devices in the heterogeneous physical local area network except the service providing device based on a network topology.

[0119] The SDK layer is configured to be used by a service providing and using layer. Main capabilities are to expose capabilities of the SOA layer to a service providing party and a service using party. For example, for the service providing party, the SDK layer provides a service registration capability in the SOA layer to the service providing party; for the service using party, the SDK layer provides a service query capability and a service calling capability in the SOA layer to the service using party.

[0120] The SOA layer builds a cross-platform service development and management framework. The SOA layer provides service definition, service management, and synchronization of service information to other physical devices in a heterogeneous local area network by using a logical connection layer. Physical devices in the heterogeneous local area network can use remote services as if they use local services.

[0121] Optionally, the connection layer 230 comprises a logical connection layer and a physical connection layer.

[0122] The physical connection layer is configured to establish a physical local area network between physical devices. Various intelligent terminals and vehicle body domains need to be physically connected to each other. The physical connection method can be various, such as any one of WiFi, Bluetooth, and USB connection between an Android mobile phone and an IOS mobile phone to connect a car machine, and the connection between the car machine and other vehicle body domains can be shared memory, vehicle Ethernet, etc. Therefore, the physical local area network between the physical devices needs to be established according to the type of physical connection between the physical devices.

[0123] Optionally, the management system further comprises: a cross-device OS layer and a service providing and using layer, the cross-device OS layer representing that the embodiment of the application can run on any physical device, including but not limited to: embedded devices and non-embedded devices of different operating systems such as Android, Linux, IOS, Windows, etc., and can also run on various domains of a vehicle body, such as IVI, Cluster, etc. Developers develop their own services based on the SDK, expose the developed services to other smart devices in the local area network or vehicle body domains through the SDK layer, so that other smart devices or vehicle body domains can use remote services like using local services, obtain service information through the service providing and using layer, and then register the target service to the SOA layer according to the service information through the SDK layer.

[0124] In one specific example, as shown in Figure 11 The management system comprises: a cross-device cross-OS layer, a physical connection layer, a logical connection layer, an SOA layer, an SDK layer, and a service providing and using layer. The cross-device cross-OS layer supports Android devices, Linux devices, IOS devices, IVI of a vehicle machine, and various domains of a vehicle body. The physical connection layer supports USB connection, WIFI connection, Bluetooth connection, NFC connection, and vehicle-mounted Ethernet. The logical connection layer supports device discovery, device logical connection, data transmission, and cross-network segment protocol conversion. The SOA layer supports service discovery, service information cross-end synchronization, service scheduling, and service life cycle management. The SDK layer supports a service development framework, service registration, service query, and service invocation. The service providing and using layer supports service provider APP and service user APP.

[0125] The above product can execute the method provided by any embodiment of the application, and has the corresponding functional modules and beneficial effects of executing the method.

[0126] Embodiment three

[0127] Figure 12 A structural schematic diagram of an electronic device 10 that can be used to implement embodiments of the application is shown. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, tablets, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smart phones, wearable devices (e.g., headsets, glasses, watches, etc.), and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the application described and / or claimed in this document.

[0128] As Figure 12As shown, 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., connected to the at least one processor 11 in communication. The memory stores a computer program executable by the at least one processor 11, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or 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 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0129] A plurality of 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, a speaker, etc., a storage unit 18, such as a magnetic disk, an optical disk, etc., and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunication networks.

[0130] The processor 11 can be various general and / or special-purpose processing components having processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 performs various methods and processes described above, such as the management method.

[0131] In some embodiments, the management method can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can 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 can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the management method by any other appropriate means, such as by means of firmware.

[0132] The various embodiments of the systems and techniques described above can be implemented in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a load programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0133] Computer programs used to implement the processes of the application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer program, when executed, can cause instructions defined in the flow charts and / or block diagrams to be implemented. The computer program can be executed entirely on a machine, partially on a machine, partially on a machine as a standalone software package and partially on a remote machine or entirely on a remote machine or server.

[0134] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store computer programs for use by or in connection with an instruction execution system, apparatus, or device. Computer-readable storage media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0135] 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 the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0136] The systems and techniques described here can be implemented in a computing system that includes a back end 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 back end, 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 a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0137] The computing system can include clients and servers. A client and server are generally 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. A server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.

[0138] It should be understood that the various forms of flow shown above can be re-ordered, added to, or deleted from without departing from the scope of the present disclosure. For example, the steps recited in the present disclosure can be executed in parallel, executed in sequence, or executed in a different order, as long as the desired results of the present disclosure are achieved, and the present disclosure is not limited herein.

[0139] The specific embodiments described above are not intended to be limiting, and persons skilled in the art will appreciate that various modifications, combinations, sub-combinations and alternatives can be made to the specific embodiments without departing from the spirit and principles of the disclosure. Accordingly, the disclosure is not limited to the specific embodiments described above, but only by the scope of the appended claims.

Claims

1. A management method, characterized in that, The management system is executed by a management system comprising: a Software Development Kit (SDK) layer, a Service-Oriented Architecture (SOA) layer, and a connection layer; the management method includes: Register the target service to the SOA layer through the SDK layer; The target service information corresponding to the target service is obtained through the SOA layer. The target service information includes: device information of the service providing device, wherein the service providing device is any physical device in the heterogeneous physical local area network. The target service information is synchronized to other physical devices in the heterogeneous physical local area network, excluding the service provider device, through the connection layer based on the network topology; The connection layer includes: a logical connection layer and a physical connection layer; The target service information is synchronized to other physical devices in the heterogeneous physical local area network (excluding the service provider device) through the connection layer based on the network topology, including: The connection method and address of the target physical device are determined by the logical connection layer based on the network topology. The target physical device is a physical device other than the service provider in the heterogeneous physical local area network. The target service information is broadcast through the physical connection layer based on the connection method and address of the target physical device. It also includes: after adding device information to the local service through the SOA layer, broadcasting the local service to the heterogeneous physical local area network through the connection layer, so that each physical device in the heterogeneous physical local area network will save the registered service locally after receiving the service registration broadcast, and each physical device will continue to broadcast the service registration broadcast to other physical devices connected to it.

2. The method according to claim 1, characterized in that, The target service information, broadcast through the physical connection layer based on the target physical device's connection method and address, includes: The target service information is encapsulated by the logical connection layer based on the connection method of the target physical device to obtain the target data packet; The target data packet is broadcast through the physical connection layer according to the connection method and address of the target physical device.

3. The method according to claim 1, characterized in that, Also includes: The service request is sent to the SOA layer through the SDK layer; Obtain the identification information of the service provider device carried in the service call request through the SOA layer; If the identification information of the service provider determines that the current service device is not the service provider device, the service request will be sent to the service provider device through the connection layer.

4. The method according to claim 3, characterized in that, The connection layer includes: a logical connection layer and a physical connection layer; The service request is sent to the service provider device through the connection layer, including: The logical connection layer generates a target request based on the service call request and the identification information of the current service device, and determines the address and connection method of the service provider device by querying the network topology according to the identification information of the service provider device. The target request is sent to the service provider device through the physical connection layer based on the address of the service provider device and the connection method of the service provider device.

5. The method according to claim 1, characterized in that, The description information of the physical device includes: the identifier of the physical device, the name of the physical device, and the IP address of the physical device. The connection information of the physical device includes: the identifier of the connected device, the name of the connected device, the IP address of the connected device, and the connection type.

6. The method according to claim 1, characterized in that, The management system also includes: a service provision and usage layer; Registering the target service to the SOA layer through the SDK layer includes: Obtain service information of the target service through the service provision and usage layer; The target service is registered to the SOA layer through the SDK layer based on the service information of the target service.

7. A management system, characterized in that, The management system performs the management method according to any one of claims 1-6, and the management system includes: a software development kit (SDK) layer, a service-oriented architecture (SOA) layer, and a connection layer; The SDK layer is used to register the target service to the SOA layer; The SOA layer is used to obtain target service information corresponding to the target service, wherein the target service information includes: device information of the service providing device, and the service providing device is any physical device in a heterogeneous physical local area network; The connection layer is used to synchronize the target service information to other physical devices in the heterogeneous physical local area network, excluding the service provider device, based on the network topology. The connection layer includes: a logical connection layer and a physical connection layer; The connection layer is also used for: The connection method and address of the target physical device are determined by the logical connection layer based on the network topology. The target physical device is a physical device other than the service provider in the heterogeneous physical local area network. The target service information is broadcast through the physical connection layer based on the connection method and address of the target physical device. The SOA layer is also used to add device information to local services; The connection layer is also used to broadcast local services to heterogeneous physical local area networks, so that each physical device in the heterogeneous physical local area network will save the registered service locally after receiving the service registration broadcast, and each physical device will continue to broadcast the service registration broadcast to other physical devices connected to it.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to execute the management method according to any one of claims 1-6.

Images