CN112217873B

CN112217873B - Device sharing method, related device and storage medium

Info

Publication number: CN112217873B
Application number: CN202010976223.7A
Authority: CN
Inventors: 刘备; 赵欢; 郑炎平; 包丰田; 郭振东
Original assignee: Beijing Agilestar Technology Co ltd
Current assignee: Beijing Agilestar Technology Co ltd
Priority date: 2020-09-16
Filing date: 2020-09-16
Publication date: 2024-02-02
Anticipated expiration: 2040-09-16
Also published as: CN112217873A

Abstract

The embodiment of the application provides a device sharing method, related devices and a storage medium, wherein a terminal device acquires an accessible proxy host list from a service platform, and the terminal device initiates a call to a sharing device through a proxy host in the proxy host list and receives acquired data returned by the sharing device and returned by the proxy host in the proxy host list so as to realize device sharing. Therefore, the proxy host is adopted to replace the terminal equipment to initiate the call to the sharing equipment, so that one sharing equipment can be called by a plurality of terminal equipment, and the equipment utilization rate is improved. In addition, external equipment for collecting different information is not required to be configured for each terminal equipment, so that equipment purchasing cost and maintenance cost are reduced.

Description

Device sharing method, related device and storage medium

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a device sharing method, a related device, and a storage medium.

Background

At present, in order to realize automatic business handling, a terminal device for handling business often needs an external device to collect various data information. The external equipment is POS (Point Of Sale) machine, certificate information acquisition equipment, handwriting screen equipment, scanner equipment, high-speed camera equipment, camera equipment and the like. When the number of terminal devices handling the service increases, the number of corresponding external devices also increases. However, each external device can only be used by the terminal device to which the external device belongs, and the device utilization rate of the external device is low.

Disclosure of Invention

Aspects of the present application provide a device sharing method, related device, and storage medium for improving device usage.

The embodiment of the application provides a device sharing method, which comprises the following steps:

the terminal equipment acquires an accessible proxy host list from a service platform, wherein the proxy host accessible to the terminal equipment is stored in the proxy host list, and the proxy host is connected with sharing equipment of equipment types required by the terminal equipment;

the terminal equipment initiates the call to the sharing equipment through the proxy host in the proxy host list;

and the terminal equipment receives the collected data returned by the sharing equipment and returned by the proxy host in the proxy host list so as to realize equipment sharing.

The embodiment of the application also provides a device sharing method, which comprises the following steps:

the target proxy host responds to a device calling request sent by the terminal device, wherein the device calling request comprises a device type required by the terminal device;

the target proxy host identifies the state of the shared device under the device type to which it is connected;

if the sharing device is in an available state, the target proxy host judges whether the target proxy host has permission to call the sharing device as an intermediate device of the terminal device;

If yes, the target proxy host acquires the acquired data of the sharing device and returns the acquired data to the terminal device.

the method comprises the steps that a service platform receives a list acquisition request sent by terminal equipment, wherein the list acquisition request comprises equipment types required by the terminal equipment;

according to the list acquisition request, acquiring a proxy host connected with the sharing equipment belonging to the equipment type and generating a proxy host list;

the service platform returns the proxy host list to the terminal equipment so that the terminal equipment initiates the call to the sharing equipment through a target proxy host in the proxy host list, wherein the target proxy host is a proxy host in the proxy list;

the service platform receives a device authentication request sent by a target proxy host and calls the sharing device to authenticate whether the target proxy host has authority as an intermediate device of the terminal device;

and the service platform returns an authentication passing message to the target proxy host, so that the target proxy host is used as an intermediate device of the terminal device to acquire the acquired data of the sharing device and returns the acquired data to the terminal device.

The embodiment of the application also provides a terminal device, which comprises: a memory, a processor, and a communication component;

the memory is used for storing a computer program;

the processor, coupled to the memory, is configured to execute the computer program for:

acquiring a proxy host list accessible to the terminal equipment from a service platform, wherein a proxy host accessible to the terminal equipment is stored in the proxy host list, and the proxy host is connected with sharing equipment of equipment types required by the terminal equipment;

initiating a call to the shared device through a proxy in the proxy list;

and receiving the collected data returned by the sharing equipment and returned by the proxy host in the proxy host list through the communication component so as to realize equipment sharing.

The embodiment of the application also provides a proxy host, which can be realized as a target proxy host, and comprises: a memory, a processor, and a communication component;

the memory is used for storing a computer program;

responding to a device call request sent by a terminal device through a communication component, wherein the device call request comprises a device type required by the terminal device;

Identifying a status of the shared device under the device type to which it is connected;

The embodiment of the application also provides a service platform, which comprises: a memory, a processor, and a communication component;

the memory is used for storing a computer program;

receiving a list acquisition request sent by a terminal device through a communication component, wherein the list acquisition request comprises the device type required by the terminal device;

returning the proxy host list to the terminal equipment so that the terminal equipment initiates the call to the sharing equipment through a target proxy host in the proxy host list, wherein the target proxy host is a proxy host in the proxy list;

Receiving a device authentication request sent by a target proxy through a communication component, and calling the sharing device to authenticate whether the target proxy has authority as an intermediate device of the terminal device;

and returning an authentication passing message to the target proxy host, so that the target proxy host can be used as an intermediate device of the terminal device to acquire the acquired data of the sharing device and return the acquired data to the terminal device.

Embodiments of the present application also provide a computer-readable storage medium storing a computer program, which when executed by a processor causes the processor to implement the steps in the above-described device sharing method.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

fig. 1 is a schematic structural diagram of a device sharing system according to an exemplary embodiment of the present application;

fig. 2 is a flow chart of a device sharing method according to an exemplary embodiment of the present application;

FIG. 3 is a flow chart of yet another method for sharing devices according to an exemplary embodiment of the present application;

FIG. 4 is a flow chart of yet another method for sharing devices according to an exemplary embodiment of the present application;

fig. 5 is a schematic structural diagram of a terminal device according to an exemplary embodiment of the present application;

FIG. 6 is a schematic structural diagram of a proxy according to an exemplary embodiment of the present application;

fig. 7 is a schematic structural diagram of a service platform according to an exemplary embodiment of the present application.

Detailed Description

For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Aiming at the technical problem that the equipment utilization rate of the existing external equipment is not high, in some embodiments of the application, the terminal equipment acquires an accessible proxy host list from the service platform, and the terminal equipment initiates the call to the sharing equipment through a proxy host in the proxy host list and receives the acquired data returned by the sharing equipment and returned by the proxy host in the proxy host list so as to realize equipment sharing. Therefore, the proxy host is adopted to replace the terminal equipment to initiate the call to the sharing equipment, so that one sharing equipment can be called by a plurality of terminal equipment, and the equipment utilization rate is improved. In addition, external equipment for collecting different information is not required to be configured for each terminal equipment, so that equipment purchasing cost and maintenance cost are reduced.

The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

Fig. 1 is a schematic structural diagram of a device sharing system according to an exemplary embodiment of the present application. As shown in fig. 1, the system includes: the service platform 6, the at least one terminal device 5, the at least one proxy 4 and each proxy are connected with at least one sharing device, wherein each terminal device and each proxy can be in communication connection with the service platform, each terminal device can be in communication connection with each proxy, and each proxy can be in communication connection with the device connected with the terminal device. Note that, in fig. 1, only the sharing devices such as the handwriting screen device 1, the camera device 2, the POS device 3, and the like are shown, but the sharing devices are not limited to those shown in fig. 1.

In this embodiment, the service platform is responsible for managing and maintaining a proxy list accessible to each terminal device, and authenticating whether the proxy has authority as an intermediate device of the terminal device to invoke the sharing device, and of course, the function of the service platform is not limited thereto. Wherein the proxy in the proxy list is accessible by the terminal device. In different access procedures, the terminal device may need to access different types of sharing devices, so the proxy in the proxy list corresponding to the terminal device may be different.

In this embodiment, each terminal device is a device capable of providing a certain service to a user. The device modality corresponding to different services may vary. For example, the terminal device may be a banking terminal capable of providing banking services to the user, such as a self-service number machine, a self-service cash dispenser, or the like. As another example, the terminal device may be a terminal device capable of providing lobby telecommunications services to a user, such as a self-service lobby terminal. For another example, the terminal device may be a terminal device capable of providing a user with a water, electricity and coal payment service, such as a self-service payment machine, but is not limited thereto.

In this embodiment, the proxy host can initiate a call to the sharing device as an intermediary device of the terminal device instead of the terminal device. Each proxy is connected to a shared device, which is a device that can be used by a plurality of terminal devices, in addition to the terminal devices. The device types of these shared devices include, but are not limited to: POS machine, document information collection device, handwriting screen device, scanner device, high-speed camera device, printer, facsimile machine, etc., but is not limited thereto. In different application scenarios, the sharing device connected with the proxy host and the device type and form of the terminal device are different. For example, in a banking scenario, the terminal device is an automated teller machine, and the sharing device is a printer, camera device, respectively. For another example, in a corporate office scenario, the terminal device is a notebook computer, a desktop computer, or the like used by a corporate employee, and the sharing device is a printer, a facsimile machine of the corporation; for another example, in a business hall scenario, the terminal device is a self-service business hall terminal, and the shared device is a certificate information acquisition device, a handwriting screen device, a scanner device, a high-speed camera device, or a camera device of the business hall. For another example, in the scenario of paying for water, electricity and coal, the terminal device is a self-service payment machine, and correspondingly, the sharing device is: POS machine, printer, camera, handwriting screen equipment, card reading equipment.

It should be noted that the sharing device may be a network connection device connected to the proxy host through a network, and the network connection device may be, for example, a POS device, a certificate information collecting device, a handwriting screen device, a scanner device, a high-speed camera device, a printer, and a facsimile machine. The sharing device may also be a USB device connected to the proxy, for example, a handwriting screen device or a card reading device.

In this embodiment, the server platform maintains a binding relationship between each proxy and the sharing device connected thereto, and host information of each proxy and device information of the sharing device connected thereto. Based on this, when a certain terminal device needs to call a sharing device of a certain device type, the terminal device may obtain a list of accessible proxy hosts from the service platform, and the service platform may provide the terminal device with the list of accessible proxy hosts. Then, the terminal equipment initiates the call to the sharing equipment through the proxy host in the proxy host list; the proxy host in the proxy host list can determine the sharing device under the device type required by the terminal device, acquire the acquired data of the sharing device and return the acquired data to the terminal device, so that the terminal device can execute corresponding service operation by utilizing the acquired data of the sharing device, and sharing of the sharing device is realized. When the proxy host calls the sharing equipment, the proxy host performs data interaction with the service platform, and identifies whether the proxy host has permission to replace the terminal equipment to initiate the call to the sharing equipment, if so, the proxy host acquires the acquired data of the sharing equipment and returns the acquired data to the terminal equipment.

Taking a business hall scenario as an example, there are multiple self-service business hall terminals in the business hall. Some self-service business hall terminals are connected with certificate information acquisition equipment, handwriting screen equipment, scanner equipment, high-speed image shooting equipment and camera equipment, and some self-service business hall terminals are connected with high-speed image shooting equipment, camera equipment and other equipment. Each self-service business hall terminal can be used as a proxy host of other self-service business hall terminals. When a certain self-service business hall terminal is not connected with the certificate information acquisition equipment and the camera equipment, and the certificate information acquisition equipment or the camera equipment is required to acquire data in the business handling process, an equipment calling request can be sent to the self-service business hall terminal connected with the certificate information acquisition equipment or the camera equipment, and corresponding acquired data can be acquired through the certificate information acquisition equipment or the camera equipment connected with other self-service business hall terminals. Obviously, through setting up the proxy host computer, can realize the sharing of equipment, the self-service business hall terminal that does not connect certain shared equipment can obtain the collection data of certain shared equipment through the self-service business hall terminal that is connected with certain shared equipment, has improved the equipment utilization ratio of shared equipment, has also reduced equipment purchase cost and maintenance cost.

It can be understood that in this embodiment, a proxy host is added between the sharing device and the terminal device, and the proxy host initiates the call to the sharing device instead of the terminal device, so that one sharing device can be called by multiple terminal devices, and the device utilization rate is improved. In addition, external equipment for collecting different information is not required to be configured for each terminal equipment, so that equipment purchasing cost and maintenance cost are reduced.

With regard to the working principle of the system, reference is made to the detailed description of the method embodiments described below.

Fig. 2 is a flow chart of a device sharing method according to an exemplary embodiment of the present application. The execution main body of the method is a terminal device, as shown in fig. 2, and the device sharing method comprises the following steps:

201. the terminal equipment acquires an accessible proxy host list from the service platform, the proxy host list stores the proxy hosts accessible to the terminal equipment, and the proxy hosts are connected with sharing equipment of equipment types required by the terminal equipment.

202. The terminal device initiates a call to the shared device through the proxy in the proxy list.

203. And the terminal equipment receives the collected data returned by the sharing equipment and returned by the proxy in the proxy list so as to realize equipment sharing.

In this embodiment, the terminal device needs to obtain a list of proxy hosts that it can access before invoking the sharing device through one proxy host. The proxy stored in the proxy list is a proxy accessible to the terminal equipment, the accessible proxy is connected with the sharing equipment of the equipment type required by the terminal equipment, and the terminal equipment can call the sharing equipment through the accessible proxy to acquire the acquired data of the sharing equipment.

In this embodiment, the manner in which the terminal device obtains the list of proxy hosts that it can access from the service platform is not limited. For example, the service platform may periodically issue a list of up-to-date agents accessible to the terminal device. For another example, the terminal device actively requests the service platform to acquire the proxy list. Specifically, the terminal device sends a list acquisition request to the service platform, wherein the list acquisition request comprises device types required by the terminal device, so that the service platform acquires proxy hosts connected with sharing devices belonging to the device types and generates a proxy host list; and receiving a proxy host list returned by the service platform. For example, if the terminal device needs the image data shot by the camera device, each proxy in the proxy list returned by the service platform is connected with the camera device. If the terminal equipment needs the certificate information acquired by the certificate information acquisition equipment, each proxy host in the proxy host list returned by the service platform is connected with the certificate information acquisition equipment. If the terminal equipment needs scanning information scanned by the scanner equipment, all the proxy hosts in the proxy host list returned by the service platform are connected with the scanner equipment.

After the proxy host list is obtained, the terminal equipment can send an equipment call request to the proxy host in the proxy host list, so that acquisition information of the sharing equipment is obtained through the proxy host.

In this embodiment, the terminal device may sequentially initiate a device call request to the proxy in the proxy list, or may select one proxy from the proxy list to initiate a device call request, and of course, the manner in which the terminal device initiates a call to the shared device through the proxy in the proxy list is not limited to this.

In an alternative embodiment, in order to find out the proxy host that can successfully call the shared device as quickly as possible, the service platform may set a priority for the proxy host in the proxy host list in the process of generating the proxy host list for the terminal device, so that the terminal device may initiate a device call request to the proxy host in the proxy host list according to the priority of the proxy host, so that the proxy host initiates a call to the shared device. The priority of the proxy may be determined by the service platform according to the relevant influencing factors, and the relevant content for determining the priority of the proxy may be referred to the description in the embodiment shown in fig. 4, which is not described in detail herein. In this embodiment, the higher the priority of the proxy, the greater the likelihood that the terminal device successfully invokes the sharing device through the proxy; conversely, the lower the priority of the proxy, the less likely that the terminal device will successfully invoke the shared device through the proxy.

In the present embodiment, when the proxy hosts in the proxy host list are arranged in order of priority from high to low, the terminal device may call the sharing device in the following manner, which is, of course, not limited to the following manner.

As an example, the terminal device sequentially sends device call requests to the proxy hosts in the proxy host list in order of priority from high to low, so that the proxy hosts call the shared devices under the connected device types until the target proxy hosts of the shared devices are successfully called. The target proxy is one of the proxies in the proxy list.

For example, 10 proxies A1-a10 in the proxy list, the 10 proxies are arranged in order of priority from high to low. The terminal equipment firstly sends an equipment calling request to the proxy host ordered at the first position, and if the acquired data of the sharing equipment is successfully called, the proxy host ordered at the first position is a target proxy host. And if the acquired data of the shared equipment is not called, sequentially sending equipment calling requests to the proxy host ordered at the later position until the acquired data of the shared equipment is successfully called. When the proxy A8 successfully invokes the collected data to the shared device, at this time, A8 is the target proxy.

As another example, the terminal device selects a target proxy from the proxy list according to the priority between the proxies; and sending a device call request to the target proxy host so that the target proxy host can call the sharing device under the connected device type.

Along the above example, 10 agents in the agent list are arranged in order of priority from high to low. The terminal device can select one proxy host with higher priority as a target proxy host to call the sharing device, and if the acquired data of the sharing device is not called, the terminal device can continue to select other proxy hosts with higher priority as the target proxy hosts to call the sharing device until the acquired data of the sharing device is successfully called. Specifically, when a proxy with a higher priority is selected, the proxy with the highest priority may be selected as the target proxy from among the proxies that have not been selected yet. One of the top N hosts may be selected as the target host from among the top N hosts that have not been selected, where N is a natural number greater than or equal to 2.

In this embodiment, after the proxy host in the proxy host list successfully invokes the sharing device of the device type required by the terminal device, the acquired data of the sharing device is returned to the terminal device, so that the terminal device acquires the acquired data of the sharing device through the proxy host.

In practical applications, the collected data of the sharing device may relate to privacy information of a user, for example, face data captured by a camera device, user certificate information collected by a certificate information collecting device, and so on.

In an alternative embodiment, in order to ensure the security and availability of data transmission, the collected data of the sharing device may be transmitted between the proxy host and the terminal device by adopting a data encryption transmission method.

As an example, if the collected data is a data ciphertext encrypted by the target proxy, after the terminal device receives the collected data, the method further includes: sending a key acquisition request to a service platform, wherein the key acquisition request comprises identification information of a target proxy host; receiving a decryption key corresponding to the encryption key used by the target proxy host in an encrypting way returned by the service platform; and decrypting the data ciphertext by using the decryption key to obtain a data plaintext.

Specifically, after successfully invoking the collected data to the sharing device, the target proxy may request an encryption key from the service platform, and the service platform may generate a decryption key corresponding to the encryption key for the target proxy. After the target proxy host acquires the encryption key generated by the service platform for the target proxy host, the encryption key is adopted to encrypt the acquired data of the sharing equipment, and the encrypted data ciphertext is obtained. After receiving the data ciphertext sent by the target proxy, the terminal equipment sends a key acquisition request carrying identification information of the target proxy to the service platform; after receiving a key acquisition request initiated by the terminal equipment, the service platform acquires a decryption key corresponding to an encryption key used for encrypting the target proxy host according to the identification information of the target proxy host and returns the decryption key to the terminal equipment; and the terminal equipment receives the decryption key returned by the service platform, and decrypts the data ciphertext generated by the target proxy host by using the decryption key to obtain a data plaintext.

According to the equipment sharing method, the terminal equipment acquires the accessible proxy host list from the service platform, the terminal equipment initiates the call to the sharing equipment through the proxy host in the proxy host list, and receives the acquired data returned by the sharing equipment and returned by the proxy host in the proxy host list, so that equipment sharing is realized. Therefore, the proxy host is adopted to replace the terminal equipment to initiate the call to the sharing equipment, so that one sharing equipment can be called by a plurality of terminal equipment, and the equipment utilization rate is improved. In addition, external equipment for collecting different information is not required to be configured for each terminal equipment, so that equipment purchasing cost and maintenance cost are reduced.

Fig. 3 is a flowchart of a device sharing method according to an exemplary embodiment of the present application. The execution subject of the method is a target proxy. In this embodiment, only the target proxy is taken as an example for explanation, and the working principle of other proxy in the proxy list accessible to the terminal device is the same as that of the target proxy, which is not described herein.

As shown in fig. 3, the device sharing method includes the steps of:

301. the target proxy host responds to a device call request sent by the terminal device, wherein the device call request comprises the device type required by the terminal device.

302. The target proxy identifies the status of the shared device under the device type to which it is connected.

303. If the sharing device is in the available state, the target proxy host determines whether there is authority to call the sharing device as an intermediate device of the terminal device, and if yes, step 304 is executed.

304. The target proxy host acquires the acquired data of the sharing device and returns the acquired data to the terminal device.

In this embodiment, the target proxy is any proxy in the proxy list accessible to the terminal device from the service platform. When the terminal device needs to call the sharing device of a certain device type, the terminal device sends a device call request including the device type required by the terminal device to the target proxy host, and then the target proxy host responds to the device call request sent by the terminal device.

In practical application, various abnormal situations such as connection failure, power failure and the like of the sharing device may occur, and at this time, the sharing device is in an unavailable state, and the proxy device cannot acquire the acquired data from the sharing device in the unavailable state. Therefore, in order to enable the target proxy host to successfully call the shared device under the device type required by the terminal device, before the target proxy host calls the shared device, the state of the shared device under the device type required by the target proxy host to identify the connected terminal device is identified, and only when the shared device is in an available state, the target proxy host initiates a call operation on the shared device; otherwise, if the shared device is in an unavailable state, the target proxy host gives up the calling operation of the shared device.

It should be noted that if there are multiple sharing devices of the same device type connected to the current target proxy, one sharing device in the available state may be selected from the multiple sharing devices, and the target proxy invokes the selected sharing device in the available state. If none of the sharing devices connected to the current target proxy is in an available state, the terminal device may then reselect a new target proxy from the host list and send a device call request to the new target proxy.

In practical applications, some of the shared devices connected to the proxy are supported by the terminal device, and some of the shared devices are not supported by the terminal device. For example, the service platform determines the proxy host accessible to the terminal device according to the device type required by the terminal device, but the shared device connected to the proxy host is not registered in the service platform (the shared device registered in the service platform allows the terminal device to be invoked through the proxy host), and at this time, the proxy host has no authority to invoke the shared device as an intermediate device of the terminal device.

Therefore, in order to ensure the success rate of the call of the sharing device, the pressure brought to the system by frequent call is avoided as much as possible, and the target proxy host needs to identify whether the target proxy host has permission to replace the terminal device to call the sharing device before the call of the sharing device.

In this embodiment, after the target proxy host successfully invokes the sharing device, the collected data of the sharing device is returned to the terminal device, so that the terminal device obtains the collected data of the sharing device through the target proxy host.

According to the equipment sharing method, the terminal equipment acquires the accessible proxy host list from the service platform, the terminal equipment initiates the call to the sharing equipment through the proxy host in the proxy host list, and receives the acquired data returned by the sharing equipment and returned by the proxy host in the proxy host list, so that equipment sharing is realized. Thus, the proxy host is adopted to replace the terminal equipment to initiate the call to the sharing equipment, so that one sharing equipment can be called by a plurality of terminal equipment, and the equipment utilization rate is provided. In addition, external equipment for collecting different information is not required to be configured for each terminal equipment, so that equipment purchasing cost and maintenance cost are reduced.

In practical applications, the collected data of the sharing device may relate to privacy information of a user, for example, face data captured by a camera device, user certificate information collected by a certificate information collecting device, and so on. Therefore, in order to ensure the safety and usability of data transmission, the collected data of the sharing device can be transmitted between the target proxy host and the terminal device by adopting a data encryption transmission method.

As an example, before the target proxy returns the acquired data for acquiring the shared device to the terminal device, a key acquisition request including identification information of the target proxy may also be sent to the service platform, so that the service platform generates an encryption key corresponding to the target proxy; receiving an encryption key returned by the service platform; and encrypting the acquired data by using the encryption key to obtain a data ciphertext.

In an alternative embodiment, the service platform may generate a generic encryption key and a decryption key that matches the encryption key. It will be appreciated that the generic encryption key and the decryption key matching the encryption key are applicable to all proxy hosts, i.e. each proxy host uses the same encryption key and the corresponding decryption key.

In another alternative embodiment, to further increase the security of data transmission, the service platform may also generate, for each proxy, its dedicated encryption key and its matching decryption key, i.e. each proxy uses a different encryption key and a corresponding decryption key. It should be noted that the encryption key and its decryption key may be generated using various encryption and decryption algorithms available.

In practical application, the target proxy host can authenticate whether the target proxy host has authority to replace the terminal equipment to call the sharing equipment in various modes. In an alternative embodiment, the authentication may be performed by the service platform. As an example, the target proxy obtains a first UDID (Unicode Device ID, device identification code) of the shared device, where the first UDID includes device information of the shared device; the target proxy host sends a device authentication request comprising a first UDID to the service platform, so that the service server authenticates the target proxy host according to the device information included in the first UDID and the pre-stored device information of the sharing device bound with the target proxy host; if the target proxy host receives the authentication passing message returned by the service platform, determining that the intermediate equipment with authority as the terminal equipment calls the sharing equipment.

For ease of understanding and distinction, the UDID of the shared device uploaded by the target proxy during the device authentication phase is referred to as a first UDID, and the UDID of the shared device uploaded by the target proxy during the device registration phase is referred to as a second UDID.

In order to ensure that the service platform can perform authentication, before the target proxy host sends a device authentication request comprising a first UDID to the service platform, device information of shared devices connected with the target proxy host can be acquired; generating a second UDID according to the equipment information of the sharing equipment; and reporting the second UDID and the host information of the target proxy host to the service platform for binding and storing the host information and the device information of the sharing device included in the second UDID.

It will be appreciated that the target proxy registers in advance the device supporting its proxy terminal device invocation into the service platform. For data security, the target proxy host does not directly upload the acquired device information of the shared device to the service platform, but generates a second UDID according to the device information of the shared device, and reports the second UDID and host information of the target proxy host to the service platform. The subsequent service platform can analyze the second UDID to obtain the device information of the second UDID, bind and store the host information of the target proxy host and the device information of the sharing device.

It should be noted that the device information of the sharing device may include a device type of the sharing device, a product identification code PID, and a vendor identification code VID, and of course, the device information of the sharing device is not limited to the above examples. The host information may include at least one of identification information of the host, host IP, host MAC (Media Access Control Address ) address, although the host information is not limited to the above examples.

It should be noted that the second UDID may be generated by processing information such as a device type, a Product ID (PID), a Vendor ID (VID), and the like in the device information of the shared device using an existing UDID generation algorithm.

Therefore, in the device authentication stage, the target proxy host firstly acquires the device information of the shared device needing authentication, and adopts the UDID generation algorithm to process the device information of the shared device needing authentication, so as to generate a corresponding first UDID. And then, the target proxy host sends a device authentication request to the service platform, the service platform judges whether the device information of the shared device in the first UDID is one of the device information of the shared device bound with the target proxy host stored in the device registration stage, if so, the service platform returns an authentication passing message to the target proxy host, and if not, the service platform returns an authentication failure message to the target proxy host.

It can be understood that the service platform returns an authentication passing message to the target proxy, which indicates that the target proxy has authority to call the sharing device as an intermediate device of the terminal device. And when the service platform returns an authentication failure message to the target proxy host, the target proxy host has no authority to call the sharing device as the intermediate device of the terminal device.

In a practical situation, the target proxy may be connected to a new device, but the terminal device cannot call the new device through the target proxy because the registration operation is not authorized. Therefore, on the basis of the above embodiment, if the target proxy host does not have permission to call the shared device as the intermediate device of the terminal device, the prompt message may also be output, so that the manager may determine whether to execute the authorized registration operation of the shared device on the target proxy host.

Specifically, when the manager determines to execute the authorized registration operation of the shared device to the target proxy, the target proxy acquires the device information of the shared device that needs to perform the authorized registration operation, and processes the device information of the shared device according to the UDID generation algorithm to generate the UDID of the shared device. And reporting the UDID of the shared device and the host information of the target proxy host, which are required to be subjected to authorization registration operation, to a service platform by the target proxy host so as to bind and store the host information and the device information of the shared device included in the UDID.

Fig. 4 is a flowchart of yet another device sharing method according to an exemplary embodiment of the present application. The execution subject of the method is a service platform, as shown in fig. 4, and the device sharing method comprises the following steps:

401. the service platform receives a list acquisition request sent by the terminal equipment, wherein the list acquisition request comprises equipment types required by the terminal equipment.

402. And acquiring the proxy hosts connected with the sharing equipment belonging to the equipment type according to the list acquisition request and generating a proxy host list.

403. And the service platform returns the proxy host list to the terminal equipment so that the terminal equipment initiates the call to the sharing equipment through a target proxy host in the proxy host list, wherein the target proxy host is a proxy host in the proxy list.

404. The service platform receives a device authentication request sent by a target proxy host and calls the sharing device to authenticate whether the target proxy host has authority as an intermediate device of the terminal device;

405. and the service platform returns an authentication passing message to the target proxy host, so that the target proxy host is used as an intermediate device of the terminal device to acquire the acquired data of the sharing device and returns the acquired data to the terminal device.

In this embodiment, the service platform provides the terminal device with a list of proxy hosts that it can access. After receiving a list acquisition request sent by a terminal device, the terminal platform finds out an agent host connected with a sharing device of a device type required by the terminal device, and adds the found agent host meeting the requirements of the terminal device into an agent host list.

In an alternative embodiment, the host information of the configured proxy may be configured into the service platform during the registration phase of the shared device. The service platform may report the host state of the configured proxy in real time, or the configured proxy periodically reports its host state to the service platform. In addition, the configured proxy host can also periodically report the device information of the sharing device connected with the configured proxy host to the service platform. The host state is divided into an abnormal state and a normal state.

Therefore, the service platform finds out the configured proxy in the normal state by analyzing the host state of the configured proxy. If the device type of the shared device connected with the configured proxy in the normal state is the device type required by the terminal device, determining the configured proxy in the normal state as a target proxy, and adding the target proxy into a proxy list.

After the service platform generates the proxy list accessible to the terminal device, the service platform returns the proxy list to the terminal device, so that the terminal device initiates a call to the sharing device through the target proxy in the proxy list. And then, the target proxy host of the equipment call request sent by the terminal equipment is received, and the target proxy host sends an equipment authentication request to the service platform before calling the acquired data of the sharing equipment. And then, the service platform calls the sharing device to authenticate whether the target proxy host has authority as an intermediate device of the terminal device.

In an alternative embodiment, in order to ensure that the service platform is able to perform device authentication operations, a binding relationship between host information of the target proxy host and device information of the shared device needs to be generated at the service platform.

Specifically, before the service platform receives the device authentication request sent by the target proxy, the method may further include: the service platform receives an authorized registration request sent by the target proxy host, wherein the authorized registration request comprises host information of the target proxy host and a second UDID of sharing equipment connected with the target proxy host; the service platform analyzes the second UDID to acquire equipment information of the sharing equipment; the service platform generates a binding relationship between host information of the target proxy host and device information of the sharing device.

Therefore, in an alternative embodiment, the service platform invokes the shared device to authenticate whether the target proxy host has authority as an intermediate device of the terminal device, specifically: the service platform acquires a first UDID from a device authentication request, wherein the first UDID comprises device information of a sharing device connected with the target proxy host; comparing the equipment information of the shared equipment connected with the target proxy host included in the first UDID with the equipment information of the shared equipment corresponding to the host information of the target proxy host in a binding relation maintained in advance; and if the two are the same, the service platform returns an authentication passing message to the target proxy host.

It may be understood that the device information of the shared device connected to the target proxy host included in the first UDID is compared with the device information of the shared device corresponding to the host information of the target proxy host in the binding relationship maintained in advance, and if the device information is different from the device information of the shared device corresponding to the host information of the target proxy host, the service platform may return an authentication failure message to the target proxy host.

On the basis of the above embodiment, in order to find out the proxy host that can successfully call the shared device as quickly as possible, the service platform may set a priority for the proxy host in the proxy host list in the process of generating the proxy host list for the terminal device, so that the terminal device may initiate a device call request to the proxy host in the proxy host list according to the priority of the proxy host, so that the proxy host initiates a call to the shared device.

In an optional embodiment, the service platform generates the proxy list, specifically: the service platform determines a proxy host connected with the sharing equipment belonging to the equipment type according to the host state of the configured proxy host and the type of the sharing equipment connected with the configured proxy host, and adds the proxy host to a proxy host list; the service platform calculates the priority among the proxy hosts in the proxy host list, and sorts the proxy hosts in the proxy host list according to the order of the priority from high to low.

In practical application, the service platform determines the influencing factors of the priority of the proxy host according to the practical situation. In an alternative embodiment, in order to objectively and reasonably calculate the priority of each proxy in the proxy list, one or more influencing factors such as the host state of the proxy, the state of the sharing device connected by the proxy and belonging to the device type, the number of times the terminal device successfully accesses the sharing device through the proxy, and the distance information between the terminal device and the proxy may be considered. Wherein, after each successful access of the terminal device to the proxy, the service platform may increase the historical number of times the terminal device successfully accesses the sharing device through the proxy. It can be understood that the more historical proxy hosts, the greater the likelihood that the terminal device successfully obtains the acquired data of the sharing device through the proxy hosts.

The distance relation between the terminal equipment and the proxy host can be judged based on the distance information between the terminal equipment and the proxy host. It can be understood that the closer the proxy is to the terminal device, the faster the data transmission speed between the terminal device and the proxy is, and at the same time, the transmitted data is not easy to be lost.

The distance information between the terminal device and the proxy can be calculated based on the IP address of the terminal device and the IP address of the proxy, but the distance information between the terminal device and the proxy can be calculated based on the geographic position information of the terminal device and the geographic position information of the proxy, but the distance information is not limited thereto.

As an example, the service platform may calculate the priority of each proxy in the proxy list by weighting and summing at least one information of a host state of the proxy, a state of a shared device connected to the proxy and belonging to the device type, a history of the terminal device successfully accessing the shared device through the proxy, distance information between the terminal device and the proxy, and the like.

Specifically, for each proxy in the proxy list, the host state of the proxy is denoted as C, the device state of the device belonging to the device type connected to the proxy is denoted as S, the historical number of times that the terminal device successfully accesses the shared device through the proxy is denoted as num, and the distance information between the terminal device and the proxy is denoted as d, then the score score=w that the proxy can be accessed ₁ *C+w ₂ *S+w ₃ *num+w ₄ * d. It will be appreciated that the higher the score the greater the probability that it will be accessed.

Wherein w is ₁ 、w ₂ 、w ₃ 、w ₄ Weights, w, of the influencing factors ₁ +w ₂ +w ₃ +w ₄ =1. The weight of each influence factor may be set according to the actual situation when the weight is assigned.

The host state C is 0 or 1, when the host state C is 0, it indicates that the corresponding proxy is in an abnormal state, and when the host state C is 1, it indicates that the corresponding proxy is in a normal state. The value of the equipment state S is 0 or 1, when the equipment state S is 1, the corresponding equipment is available, and when the equipment state S is 0, the corresponding equipment is unavailable.

Thus, after determining the accessible score of each proxy in the proxy list, the priority of each proxy is set according to the accessible score of each proxy. It will be appreciated that the higher the score that a proxy can be accessed, the higher the priority of that proxy, and conversely, the lower the score that a proxy can be accessed, the lower the priority of that proxy. For example, a plurality of priorities are set, each priority corresponds to a score range, the score range where the score accessible to the proxy is located is judged, and the priority corresponding to the proxy is determined.

It should be noted that, the execution subjects of each step of the method provided in the above embodiment may be the same device, or the method may also be executed by different devices. For example, the execution subject of steps 201 to 203 may be device a; for another example, the execution subject of steps 201 and 202 may be device a, and the execution subject of step 203 may be device B; etc.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations appearing in a specific order are included, but it should be clearly understood that the operations may be performed out of the order in which they appear herein or performed in parallel, the sequence numbers of the operations such as 201, 202, etc. are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.

Fig. 5 is a schematic structural diagram of a terminal device according to an exemplary embodiment of the present application. As shown in fig. 5, the terminal device includes: comprising the following steps: memory 11, processor 12 and communication component 13.

The memory 11 is used for storing a computer program and may be configured to store other various data to support operations on the processor. Examples of such data include instructions for any application or method operating on a processor, contact data, phonebook data, messages, pictures, video, and the like.

The memory 11 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

A processor 12 coupled to the memory 11 for executing a computer program in the memory 11 for:

Initiating a call to the shared device through a proxy in the proxy list;

and receiving collected data returned by the sharing device and returned by the proxy in the proxy list through the communication component 13 so as to realize device sharing.

Further, the processor 12, when obtaining the list of the proxy hosts accessible to it, is specifically configured to:

a list acquisition request is sent to a service platform, wherein the list acquisition request comprises equipment types required by terminal equipment, so that the service platform acquires proxy hosts connected with sharing equipment belonging to the equipment types and generates a proxy host list; and receiving the proxy host list returned by the service platform.

Further, the proxy hosts in the proxy host list are arranged in order of priority from high to low, and the processor 12 is specifically configured to, when calling the sharing device: sending device calling requests to the proxy hosts in the proxy host list in sequence according to the order of the priority from high to low so that the proxy hosts call the sharing devices of the connected device types until the target proxy host is successfully called;

Or selecting a target proxy from the proxy list according to the priority among the proxy; and sending a device call request to the target proxy host so that the target proxy host can call the sharing device under the device type connected with the target proxy host.

The terminal device shown in fig. 5 may perform the method of the embodiment shown in fig. 2, and the terminal device may be a notebook computer, a tablet, a mobile phone, or the like, and for a part of this embodiment that is not described in detail, reference may be made to the description related to the embodiment shown in fig. 2. The implementation process and the technical effect of this technical solution are described in the embodiment shown in fig. 2, and are not described herein.

Further, as shown in fig. 5, the apparatus further includes: a display 14, a power supply component 15, an audio component 16, and the like. Only some of the components are schematically shown in fig. 5, which does not mean that the processor only comprises the components shown in fig. 5.

Accordingly, embodiments of the present application also provide a computer readable storage medium storing a computer program, where the computer program when executed is capable of implementing the steps of the method of the embodiment of the method described above, where the steps of the method of the embodiment shown in fig. 2 may be executed by a processor.

Fig. 6 is a schematic structural diagram of a proxy according to an exemplary embodiment of the present application. As shown in fig. 6, the proxy includes: comprising the following steps: memory 21, processor 22 and communication component 23.

The memory 21 is used for storing a computer program and may be configured to store other various data to support operations on the processor. Examples of such data include instructions for any application or method operating on a processor, contact data, phonebook data, messages, pictures, video, and the like.

The memory 21 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

A processor 22 coupled to the memory 21 for executing the computer program in the memory 21 for:

responding to a device call request sent by the terminal device through the communication component 23, wherein the device call request comprises a device type required by the terminal device;

Further, when determining whether there is authority to call the sharing device as the intermediate device of the terminal device, the processor 22 is specifically configured to:

acquiring a first device identification code (UDID) of the sharing device, wherein the first UDID comprises device information of the sharing device;

sending a device authentication request comprising the first UDID to a service platform, so that the service server authenticates the target proxy host according to device information included in the first UDID and pre-stored device information of a sharing device bound with the target proxy host;

and if the authentication passing message returned by the service platform is received, determining that the terminal equipment is authorized to be used as the intermediate equipment of the terminal equipment to call the sharing equipment.

Further, before sending the device authentication request including the first UDID to the service platform, the processor 22 is further configured to:

acquiring equipment information of shared equipment connected with the target proxy host;

generating a second UDID according to the equipment information of the sharing equipment;

And reporting the second UDID and the host information of the target proxy host to a service platform so as to bind and store the host information and the equipment information of the sharing equipment included in the second UDID.

Further, the device information of the sharing device includes a device type, a product identifier, and a vendor identifier of the sharing device, and the processor 22 is specifically configured to, when generating the second UDID:

and processing the equipment type, the product identification code and the provider identification code of the sharing equipment according to the UDID generation algorithm to generate the second UDID.

The proxy shown in fig. 6 may perform the method of the embodiment shown in fig. 3, and for a part of this embodiment that is not described in detail, reference is made to the description related to the embodiment shown in fig. 3. The implementation process and the technical effect of this technical solution are described in the embodiment shown in fig. 3, and are not described herein.

Further, as shown in fig. 6, the proxy further includes: a display 24, a power supply assembly 25, an audio assembly 26, and other components. Only some of the components are schematically shown in fig. 6, which does not mean that the processor only comprises the components shown in fig. 6. In addition, the components shown in the dashed boxes in fig. 6 are optional components, and not necessarily optional components, depending on the specific implementation form of the device sharing apparatus. If the proxy is implemented as a terminal device such as a notebook computer, a tablet, a mobile phone, etc., the proxy may include components shown by a dashed box in fig. 6; if the proxy is implemented as a server-side device such as a conventional server, cloud server, or server array, the components shown in the dashed box in fig. 6 are not included.

The proxy also includes: other components such as a display, a power supply component, an audio component, etc. The component assemblies are presented and are not meant to imply that the processor comprises only the illustrated assemblies. In addition, the components shown in the dashed boxes are optional components, not necessarily optional components, and are specific implementation forms of the visual device sharing apparatus.

Accordingly, embodiments of the present application also provide a computer readable storage medium storing a computer program, where the computer program when executed is capable of implementing the steps of the method of the embodiment of fig. 3 that may be executed by a processor in the above-described method embodiment.

Fig. 7 is a schematic structural diagram of a service platform according to an exemplary embodiment of the present application. As shown in fig. 7, the service platform includes: comprising the following steps: memory 31, processor 32, and communication component 33.

The memory 31 is used for storing a computer program and may be configured to store other various data to support operations on the processor. Examples of such data include instructions for any application or method operating on a processor, contact data, phonebook data, messages, pictures, video, and the like.

The memory 31 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

A processor 32 coupled to the memory 31 for executing the computer program in the memory 31 for:

receiving, by the communication component 33, a list acquisition request sent by the terminal device, where the list acquisition request includes a device type required by the terminal device;

receiving a device authentication request sent by a target proxy through a communication component 33, and calling the sharing device to authenticate whether the target proxy has authority as an intermediate device of the terminal device;

Further, the processor 32 is specifically configured to, when generating the proxy list: determining a proxy connected with a sharing device belonging to the device type according to the host state of the configured proxy and the type of the sharing device connected with the configured proxy, and adding the proxy to a proxy list; and calculating the priority among the proxy hosts in the proxy host list, and sequencing the proxy hosts in the proxy host list according to the order of the priority from high to low.

Further, the processor 32 is specifically configured to, when calculating the priority of the proxy in the proxy list: for each proxy in the proxy list, acquiring at least one of the host state of the proxy, the state of the shared device connected with the proxy and belonging to the device type, the historical times of successful access of the terminal device to the shared device through the proxy, and the distance information between the terminal device and the proxy; and calculating the priority between the proxy host and other proxy hosts in the proxy host list according to the at least one piece of information.

Further, the processor 32 is specifically configured to, when performing device authentication: acquiring a first UDID from a device authentication request, wherein the first UDID comprises device information of a sharing device connected with the target proxy host; comparing the equipment information of the shared equipment connected with the target proxy host included in the first UDID with the equipment information of the shared equipment corresponding to the host information of the target proxy host in a binding relation maintained in advance; and if the two are the same, returning an authentication passing message to the target proxy host.

Further, the processor 32 is further configured to, prior to performing the device authentication: receiving an authorized registration request sent by the target proxy host, wherein the authorized registration request comprises host information of the target proxy host and a second UDID of sharing equipment connected with the target proxy host; analyzing the second UDID to acquire equipment information of the sharing equipment; and generating a binding relationship between host information of the target proxy host and device information of the sharing device.

The service platform shown in fig. 7 may perform the method of the embodiment shown in fig. 4, where the service platform may be a conventional server, a cloud server, or a server array, and the portions of the embodiment that are not described in detail may be referred to in the related description of the embodiment shown in fig. 4. The implementation process and the technical effect of this technical solution are described in the embodiment shown in fig. 4, and are not described herein.

Further, as shown in fig. 7, the service platform further includes: power supply assembly 34, and the like. Only some of the components are schematically shown in fig. 7, which does not mean that the processor only comprises the components shown in fig. 7.

Accordingly, embodiments of the present application also provide a computer readable storage medium storing a computer program, where the computer program when executed is capable of implementing the steps of the method of the embodiment of fig. 4 that may be executed by a processor in the above-described method embodiment.

The communication assembly of fig. 5, 6 and 7 is configured to facilitate wired or wireless communication between the device in which the communication assembly is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as a mobile communication network of WiFi,2G, 3G, 4G/LTE, 5G, etc., or a combination thereof. In one exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component further comprises a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

The displays in fig. 5 and 6 described above include screens, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation.

The power supply assembly shown in fig. 5, 6 and 7 provides power for various components of the device where the power supply assembly is located. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices in which the power components are located.

The audio components of fig. 5 and 6 described above may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive external audio signals when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a speech recognition mode. The received audio signal may be further stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A method of device sharing, comprising:

the terminal equipment acquires an accessible proxy host list from a service platform, wherein the proxy host list stores proxy hosts accessible to the terminal equipment, and the proxy hosts are connected with sharing equipment of equipment types required by the terminal equipment, and the service platform maintains binding relations between all the proxy hosts and the sharing equipment connected with the proxy hosts, host information of all the proxy hosts and equipment information of the sharing equipment connected with the proxy hosts;

the terminal equipment receives the collected data returned by the sharing equipment and returned by the proxy host in the proxy host list so as to realize equipment sharing;

the terminal equipment acquires an accessible proxy host list from the service platform, and the method comprises the following steps:

the method comprises the steps that terminal equipment sends a list acquisition request to a service platform, wherein the list acquisition request comprises equipment types required by the terminal equipment, so that the service platform acquires proxy hosts connected with sharing equipment belonging to the equipment types and generates a proxy host list; and receiving the proxy host list returned by the service platform.

2. The method according to claim 1, wherein the proxy in the proxy list is arranged in order of priority from high to low, and the terminal device initiates the call to the sharing device through the proxy in the proxy list, comprising:

the terminal equipment sequentially sends equipment calling requests to the proxy hosts in the proxy host list according to the order of the priority from high to low so that the proxy hosts call the sharing equipment of the connected equipment type until the target proxy host is successfully called;

Or,

the terminal equipment selects a target proxy host from the proxy host list according to the priority among the proxy hosts;

and sending a device call request to the target proxy host so that the target proxy host can call the sharing device under the device type connected with the target proxy host.

3. A method of device sharing, comprising:

if yes, the target proxy host acquires the acquired data of the sharing equipment and returns the acquired data to the terminal equipment;

wherein the terminal device performs the method of claim 1 or 2.

4. A method according to claim 3, wherein the target proxy determining whether there is authority to invoke the sharing device as an intermediary device of the terminal device comprises:

The target proxy host acquires a first device identification code (UDID) of the sharing device, wherein the first UDID comprises device information of the sharing device;

the target proxy host sends a device authentication request comprising the first UDID to a service platform, so that the service platform authenticates the target proxy host according to device information included in the first UDID and device information of a shared device which is stored in advance and is bound with the target proxy host;

and if the target proxy host receives the authentication passing message returned by the service platform, determining that the target proxy host has permission as the intermediate equipment of the terminal equipment to call the sharing equipment.

5. The method of claim 4, further comprising, prior to the target proxy sending a device authentication request to a service platform that includes the first UDID:

6. The method of claim 5, wherein the device information of the shared device includes a device type, a product identification code, and a vendor identification code of the shared device, and wherein generating the second UDID based on the device information of the shared device comprises:

7. A method of device sharing, comprising:

the method comprises the steps that a service platform receives a list acquisition request sent by terminal equipment, wherein the list acquisition request comprises equipment types required by the terminal equipment, and the service platform maintains binding relations between proxy hosts and sharing equipment connected with the proxy hosts, host information of the proxy hosts and equipment information of the sharing equipment connected with the proxy hosts;

the service platform returns the proxy host list to the terminal equipment so that the terminal equipment initiates the call to the sharing equipment through a target proxy host in the proxy host list, wherein the target proxy host is a proxy host in the proxy host list;

8. The method of claim 7, wherein the service platform generating the proxy list comprises:

the service platform determines a proxy host connected with the sharing device belonging to the device type according to the host state of the configured proxy host and the type of the sharing device connected with the configured proxy host, and adds the proxy host to a proxy host list;

the service platform calculates the priority among the proxy hosts in the proxy host list, and sorts the proxy hosts in the proxy host list according to the order of the priority from high to low.

9. The method of claim 8, wherein the service platform calculating the priority of the proxy in the proxy list comprises:

For each proxy in the proxy list, the service platform obtains at least one of a host state of the proxy, a state of a shared device connected with the proxy and belonging to the device type, a history of successful access of the terminal device to the shared device by the proxy, and distance information between the terminal device and the proxy;

and calculating the priority between the proxy host and other proxy hosts in the proxy host list according to the at least one piece of information.

10. The method of claim 9, wherein authenticating whether the target proxy has permission to invoke the shared device as an intermediary device for the terminal device comprises:

the service platform acquires a first UDID from a device authentication request, wherein the first UDID comprises device information of a sharing device connected with the target proxy host; comparing the equipment information of the shared equipment connected with the target proxy host included in the first UDID with the equipment information of the shared equipment corresponding to the host information of the target proxy host in a binding relation maintained in advance;

And if the two are the same, the service platform returns an authentication passing message to the target proxy host.

11. The method of claim 10, further comprising, before the service platform receives the device authentication request sent by the target proxy:

the service platform receives an authorized registration request sent by the target proxy host, wherein the authorized registration request comprises host information of the target proxy host and/or a second UDID of sharing equipment connected with the target proxy host;

the service platform analyzes the second UDID to acquire equipment information of the sharing equipment;

the service platform generates a binding relationship between host information of the target proxy host and device information of the sharing device.

12. A terminal device, comprising: a memory, a processor, and a communication component;

the memory is used for storing a computer program;

acquiring a proxy host list accessible to the terminal equipment from a service platform, wherein the proxy host list stores proxy hosts accessible to the terminal equipment, and the proxy hosts are connected with sharing equipment of equipment types required by the terminal equipment, and the service platform maintains binding relations between all the proxy hosts and the sharing equipment connected with the proxy hosts, host information of all the proxy hosts and equipment information of the sharing equipment connected with the proxy hosts;

Initiating a call to the shared device through a proxy in the proxy list;

collecting data returned by the sharing equipment and returned by the proxy host in the proxy host list is received through the communication component so as to realize equipment sharing;

13. A proxy, implementable as a target proxy, comprising: a memory, a processor, and a communication component;

the memory is used for storing a computer program;

if yes, the target proxy host acquires acquired data of the sharing device and returns the acquired data to the terminal device, wherein the terminal device executes the method as claimed in claim 1 or 2.

14. A service platform, comprising: a memory, a processor, and a communication component;

the memory is used for storing a computer program;

receiving a list acquisition request sent by a terminal device through a communication component, wherein the list acquisition request comprises device types required by the terminal device, and a service platform maintains binding relations between all proxy hosts and sharing devices connected with the proxy hosts, host information of all proxy hosts and device information of the sharing devices connected with the proxy hosts;

Returning the proxy host list to the terminal equipment so that the terminal equipment initiates the call to the sharing equipment through a target proxy host in the proxy host list, wherein the target proxy host is a proxy host in the proxy host list;

15. A computer readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1-11.