WO2014101786A1

WO2014101786A1 - Method, apparatus, and system for accessing device

Info

Publication number: WO2014101786A1
Application number: PCT/CN2013/090523
Authority: WO
Inventors: 刘孟红; 展华益; 张恩阳
Original assignee: 四川长虹电器股份有限公司
Priority date: 2012-12-29
Filing date: 2013-12-26
Publication date: 2014-07-03
Also published as: CN103078855B; CN103078855A

Abstract

Provided are a method, an apparatus, and a system for accessing a device. The present invention relates to network technologies. The present invention solves the existing problems of complication of device access right management work, low efficiency and poor user experience due to the large number of smart devices. The technical solutions of the present invention can be summarized as follows: device access rights are managed by adding user information in a device access request and introducing a relationship between a user and another user and a relationship between a user and a device. The present invention has the benefits: the present invention brings convenient to a user and improves the user experience, and is suitable for access between devices.

Description

Method, device and system for realizing device access

The present invention relates to network technologies, and more particularly to device access technologies.

Background technique

With the rapid development of chip technology and Internet technology, more and more terminals are more intelligent and networked, such as tablets, smart phones, smart appliances (such as TVs, washing machines, air conditioners, refrigerators, printers, rice cookers, water heaters). Can connect with the Internet. The explosive growth of the number and category of intelligent terminal devices (more than 50 billion connected devices are expected in 2020), making connection and collaboration between devices, remote access of devices, and sharing of devices become real and urgent needs of users.

A device-to-user sharing refers to a device that can be accessed by that user. Device access includes at least control of the device, acquisition of services provided by the device, and other interactions with the device (such as pushing content to the device). Utilizing UPnP (universal plug and play), IGRS and other device interconnection protocols, it can interconnect and share devices between home and small enterprises. It can also be set for each device in the remote access server. Access user lists for remote access to devices.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art:

The existing device interconnection technology and device access rights management are all device-centric. With a large number of intelligent terminal devices accessing the Internet, if the user accesses the user list for each device, the device access rights management is performed. Device access rights management is complicated, low in efficiency, and poor user experience. Summary of the invention

The method, device and system for implementing device access provided by the present invention aim to overcome the shortcomings of complicated access management, low efficiency and poor user experience caused by the large number of intelligent terminals.

An embodiment of the present invention provides a method for implementing device access, including:

Receiving a device access request sent by the requesting user, where the device access request includes identification information of the requesting user and the accessed device;

Judging whether the requesting user can access the accessed device according to the relationship between the requesting user and the owner of the accessed device and/or requesting the relationship between the user and the accessed device and the access authority of the accessed device, or by interacting with the accessed device The owner performs information interaction to determine whether the user can access the accessed device;

When the requesting user can access the accessed device, the gateway is aggregated to the device of the accessed device or the accessed device or is The proxy device accessing the device forwards the device access request; otherwise, the device access request failure message is sent to the requesting user. A method of implementing device access is also provided, including:

Judging whether the user can access the accessed device according to the relationship between the requesting user and the owner of the accessed device and/or requesting the relationship between the user and the accessed device and the access authority of the accessed device, or through the device and the user The information management platform or the owner of the accessed device performs information interaction judgment to request the user to access the accessed device;

When the requesting user can access the accessed device, the device access request is forwarded to the accessed device or the proxy device of the accessed device; otherwise, the device access request failure message is sent to the requesting user.

A method of implementing device access is also provided, including:

Judging whether the user can access the accessed device according to the relationship between the requesting user and the owner of the accessed device and/or requesting the relationship between the user and the accessed device and the access authority of the accessed device, or through the device and the user The information management platform or the device aggregation gateway or the owner of the accessed device performs information interaction judgment to request the user to access the accessed device;

When the requesting user can access the accessed device, the device access request or the operation instruction involved in the device access request is forwarded to the accessed device; otherwise, the device access request failure message is sent to the requesting user.

And provides a device and user information management platform device, including:

a first information receiving unit, configured to receive a device access request sent by the requesting user, where the device access request includes identifier information of the requesting user and the accessed device;

a first information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or request a relationship between the user and the accessed device, and an access permission of the accessed device, whether the requested user can access the accessed device The device, or by performing information interaction with the owner of the accessed device, determining whether the user is requested to access the accessed device;

a first information execution unit, configured to: when the requesting user can access the accessed device, forward the device access request to the device aggregation gateway of the accessed device or the accessed device or the proxy device of the accessed device; otherwise, send the device access request to the requesting user. Failure message.

A device aggregation gateway device is also provided, including:

a second information receiving unit, configured to receive a device access request sent by the requesting user, where the device access request packet Identification information including the requesting user and the accessed device;

a second information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or requesting the relationship between the user and the accessed device and the access authority of the accessed device, whether the requested user can access the accessed device The device, or by interacting with the device and the user information management platform or the owner of the accessed device to determine whether the user is requested to access the accessed device;

And a second information execution unit, configured to: when the requesting user can access the accessed device, forward the device access request to the accessed device or the proxy device of the accessed device; otherwise, send the device access request failure message to the requesting user.

A device device is also provided, including:

a third information receiving unit, configured to receive a device access request sent by the requesting user, where the device access request includes identifier information of the requesting user and the accessed device;

a third information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or requesting the relationship between the user and the accessed device, and the access authority of the accessed device, whether the requested user can access the accessed device The device, or through information interaction with the device and the user information management platform or the device aggregation gateway or the owner of the accessed device, determines whether the user can access the accessed device;

And a third information execution unit, configured to: when the requesting user can access the accessed device, execute an operation instruction related to the device access request; otherwise, send a device access request failure message to the requesting user.

A proxy device device is also provided, including:

a fourth information receiving unit, configured to receive a device access request sent by the requesting user, where the device access request includes identifier information of the requesting user and the accessed device;

a fourth information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or requesting the relationship between the user and the accessed device, and the access authority of the accessed device, whether the requested user can access the accessed device The device, or through information interaction with the device and the user information management platform or the device aggregation gateway or the owner of the accessed device, determines whether the user can access the accessed device;

And a fourth information execution unit, configured to: when the requesting user can access the accessed device, forward the device access request to the accessed device; otherwise, send the device access request failure message to the requesting user.

A system for implementing device access is provided, including a requesting user and an accessed device or an owner including the requesting user, the accessed device, and the accessed device, and the device and user information management platform device as described above.

The method, device, and system for implementing device access provided by the embodiments of the present invention have the beneficial effects of: adding user information in a device access request, and introducing a relationship between the user and the user and between the user and the device to implement device access. Rights management, in the case of a large number of intelligent terminals, improves the efficiency of device access rights management and improves the user experience. DRAWINGS

The drawings are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawings: FIG. 1 is a flowchart of a method for implementing device access according to Embodiment 1 of the present invention;

2 is a flowchart of a method for implementing device access according to Embodiment 2 of the present invention;

FIG. 3 is a flowchart of a method for implementing device access according to Embodiment 3 of the present invention;

4 is a flowchart of a method for implementing device access according to Embodiment 4 of the present invention;

FIG. 5 is a flowchart of a method for implementing device access according to Embodiment 5 of the present invention;

6 is a structural block diagram of a device and a user information management platform device according to Embodiment 6 of the present invention;

7 is a structural block diagram of a device aggregation gateway device according to Embodiment 7 of the present invention;

8 is a structural block diagram of a device to be accessed in Embodiment 8 of the present invention;

9 is a structural block diagram of a proxy device device according to Embodiment 9 of the present invention;

FIG. 10 is a structural block diagram of a system for implementing device access according to Embodiment 10 of the present invention. detailed description

The technical solution of the present invention will be described in detail below with reference to the embodiments. It is apparent that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

A method for implementing device access according to the embodiment of the present invention first receives a device access request sent by a requesting user, where the device access request includes identification information of the requesting user and the accessed device, and then according to the requesting user and the accessed device. The relationship between the owner and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device determine whether the requesting user can access the accessed device, or by interacting with the owner of the accessed device Requesting the user to access the accessed device, and finally, when the requesting user can access the accessed device, forwarding the device access request to the device aggregation gateway of the accessed device or the accessed device or the proxy device of the accessed device; otherwise, sending the device to the requesting user Access request failure message. A method for implementing device access in another embodiment of the present invention is: first receiving a device access request sent by a requesting user, where the device access request includes identification information of the requesting user and the accessed device, and then according to the requesting user and being accessed. The relationship between the owner of the device and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device determine whether the requesting user can access the accessed device, or through access to the device and user information management platform or The owner of the device performs information interaction to determine whether the user can access the accessed device, and finally when the requesting user can access the accessed device. At the time of the device, the device access request is forwarded to the accessed device or the proxy device of the accessed device; otherwise, the device access request failure message is sent to the requesting user. In another embodiment of the present invention, a method for implementing device access is: first receiving a device access request sent by a requesting user, where the device access request includes identification information of the requesting user and the accessed device, and then according to the requesting user and the accessed device. Relationship between the owner and/or requesting the relationship between the user and the accessed device and the access rights of the accessed device to determine whether the requesting user can access the accessed device, or by aggregating the gateway with the device and the user information management platform or device Or the owner of the accessed device performs information interaction to determine whether the user can access the accessed device, and finally, when the requesting user can access the accessed device, forward the device access request or perform the operation involved in the device access request to the accessed device. Instruction; otherwise, the device access request failure message is sent to the requesting user. A device and user information management platform device in the embodiment of the present invention includes: a first information receiving unit, configured to receive a device access request sent by a requesting user, where the device access request includes identifier information of the requesting user and the accessed device a first information processing unit, configured to determine, according to a relationship between the requesting user and an owner of the accessed device, and/or request a relationship between the user and the accessed device, and an access authority of the accessed device, whether the requested user can access the Accessing the device, or determining whether the user can access the accessed device by performing information interaction with the owner of the accessed device; the first information execution unit is configured to access the accessed device or be accessed when the requesting user can access the accessed device The device aggregation gateway of the device or the proxy device of the accessed device forwards the device access request; otherwise, the device access request failure message is sent to the requesting user. A device aggregation gateway device in the embodiment of the present invention includes: a second information receiving unit, configured to receive a device access request sent by a requesting user, where the device access request includes identifier information of the requesting user and the accessed device; An information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or requesting the relationship between the user and the accessed device and the access authority of the accessed device, whether the requesting user can access the accessed device, Or determining whether the requesting user can access the accessed device by performing information interaction with the device and the user information management platform or the owner of the accessed device; and the second information executing unit is configured to be accessed when the requesting user can access the accessed device The device or the proxy device of the accessed device forwards the device access request; otherwise, the device user is requested to send a device access request failure message. An access device device in the embodiment of the present invention includes: a third information receiving unit, configured to receive a device access request sent by a requesting user, where the device access request includes identifier information of the requesting user and the accessed device; An information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or requesting the relationship between the user and the accessed device and the access authority of the accessed device, whether the requesting user can access the accessed device, Or determining whether the requesting user can access the accessed device by performing information interaction with the device and the user information management platform or the device aggregation gateway or the owner of the accessed device; the third information execution unit is configured to: when the requesting user can access the accessed device Executing an operation instruction involved in the device access request; otherwise, sending a device access request failure message to the requesting user. A proxy device device in an embodiment of the present invention includes: a fourth information receiving unit, configured to receive a device access request sent by the requesting user, where the device access request includes identification information of the requesting user and the accessed device; and a fourth information processing unit, configured to: according to the requesting user and the owner of the accessed device The relationship between the relationship and/or the requesting user and the accessed device and the access rights of the accessed device determine whether the requesting user can access the accessed device, or through the gateway or device with the device and user information management platform or device. The device owner performs information interaction to determine whether the user can access the accessed device. The fourth information execution unit is configured to forward the device access request to the accessed device when the requesting user can access the accessed device; otherwise, send the device to the requesting user. Access request failure message. A system for implementing device access in the embodiment of the present invention includes a requesting user and an accessed device or an owner including the requesting user, the accessed device, and the accessed device, and further includes the device and the user information management platform device as described above. Example 1

A flowchart of a method for implementing device access in this example is shown in FIG. Its specific includes:

Step 101: The device and the user information management platform receive a device access request sent by the requesting user. The device access request includes any operation command or operation instruction for the accessed device, such as acquiring a device/service description, a function call, an event subscription, and a content. (pictures, audio/video, apps) Push, etc.

In order for the device and the user information management platform to determine the access authority, the device access request must include the identification information of the requesting user and the accessed device. In a specific implementation, the device access request sent by the requesting user may be a set of multiple messages, for example, the requesting user first sends a message containing only an operation command to the accessed device, and then sends a message containing the requested user identification information, and the message is sent. It should be understood as a device access request, or as a whole, as a device access request.

The identification information here may be the requesting user identifier and the accessed device identifier. The requesting user identity may be any logically identifiable information of the requesting user, such as an IP address and/or port number, a username and/or a user password, a user number, fingerprint information, voiceprint information, eye information, facial information, etc. . Similarly, the accessed device identifier can be any logically identifiable information about the accessed device, such as an IP address and/or port number, a device name or device group name, a device number, or a device group number.

The identification information may also be an association identifier. The association identifier is predefined between the requesting user, the accessed device, the device, and the user information management platform, and the device and user information management platform can directly determine the requesting user and the accessed device involved in the device access request according to the association identifier. The association identifier can be any information that logically identifies the requesting user and the accessed device, such as a numeric number, a name, and the like.

In addition, the requesting user sends a device access request through a specific device, such as a mobile phone, a tablet, a PC, and the like. The requesting user and the device and the user information management platform can exchange information through the Internet, the mobile network, and the like. The information transmitted by the user (including the requesting user and the device owner) can also be understood as information sent by the user's specific device. Therefore, the user (including the requesting user and the device owner) can be understood as a person, and can also be understood as a specific device, and the person and the specific device as a whole can be understood as a user.

Step 102: The device and the user information management platform determine, according to the relationship between the requesting user and the owner of the accessed device, and/or the relationship between the requesting user and the accessed device, and the access authority of the accessed device, whether the requesting user can access the Accessing the device, or determining whether the user can access the accessed device by performing information interaction with the owner of the accessed device;

Here, the device and the user information management platform determine, according to the relationship between the requesting user and the owner of the accessed device, and/or the relationship between the requesting user and the accessed device, and the access authority of the accessed device, whether the requested user can access the accessed device. The method of the device is described in detail as follows:

The device and user information management platform stores and maintains information about users and devices. The device and user information management platform also stores and maintains relationships between users and/or user-to-device relationships and/or device access rights. Therefore, the device and user information management platform supports: user and device registration; user information, device information, user relationship, user-to-device relationship, device access rights establishment or update or deletion.

The relationship between users is at least one of friends, strangers and blacklists (or other combinations and extensions, such as the relationship between users only contains friends and non-friends); the relationship between users and devices is at least the owner and non-owner One (or other combination and extension); access to the device is at least only owner access, all friends accessible, some friends accessible, non-blacklisted users accessible, and anyone accessible (or other combinations and extensions) If the access rights of the device need to be maintained and the list of buddy users can be accessed, the access rights of the device can be defined in a composite manner or in combination. The method or rule for determining whether the requesting user has the device access right needs to be performed according to the definition of the relationship and the access authority, and may be optimized in the logical judgment, at least: if the relationship between the requesting user and the accessed device is the owner, or If the relationship between the requesting user and the accessed device is non-owner, and the relationship between the requesting user and the owner of the accessed device is a friend, and the access right of the accessed device is accessible to all friends or accessible to anyone Or the non-blacklisted user can access or some of the friends can access and request the user to belong to the accessible friend user, or if the relationship between the requesting user and the accessed device is non-owner, and the requesting user and the owner of the accessed device The relationship is a stranger, and the access rights of the accessed device are accessible to any user or non-blacklisted user, or if the relationship between the requesting user and the accessed device is non-owner, and the requesting user and the accessed device are The relationship between the owners is blacklisted and the access rights of the accessed device are anyone Accessible, the requesting user can access the accessed device; otherwise, the requesting user cannot access the accessed device.

User relationships, user-to-device relationships, and device access rights are logically defined to determine whether a user can access a device. There are many other ways to define or implement it: use {0,1,2} Indicates the relationship between users; For example, if a relationship between users can be added to a super friend, the device access permission between the default super friends is completely open; for example, one-dimensional can be added in the definition of access rights of the device, and different settings can be set for each accessible user or user group. Access rights (such as the access device provides different services to different users, can also be understood as restrictions on the device access request category). Whether the user has the device access authority is judged logically according to these definitions, so the logic judgment method also has many implementation ways: the order of the logic judgment may be different; for example, the definition of the access authority of the device is increased for each When an accessible user or user group sets different access rights (such as when the accessed device provides different services to different users, and can also be understood as a restriction on the device access request category), it should also increase the judgment of the device access request. Confirms whether the accessed device accepts the device access request of the requesting user. To facilitate judgment and optimization, the following list may be generated for the accessed device according to the defined relationship between users, the relationship between the user and the device, and the access rights of the device: {accessible user or accessible user group list} or { (accessible user 1 or Accessible User Group 1, Access Rights Category), (Accessible User 2 or Accessible User Group 2, Access Rights Category), ···}, where the access rights category indicates the accessible permission categories (the specific permission categories can be based on Determined by the function or service provided by the accessed device, can be defined as any privilege (ie, all privilege) or a combination of partial privilege. When the requesting user and/or device access request category is in the list, the user has access rights. And allows the execution of the operation instructions involved in the device access request. Therefore, any other logical definition method and logical judgment method regarding the relationship between users, the relationship between the user and the device, and the access authority of the device using the inventive concept are still within the protection scope of the patent.

The device and the user information management platform determine whether the requesting user can access the accessed device by performing information interaction with the owner of the accessed device as follows:

When the device and the user information management platform do not have the user access authority judgment function or other conditions that cannot determine the user access authority, the information may be exchanged with the owner of the accessed device, and the owner of the accessed device performs the user access authority judgment. And feedback the judgment result to the device and the user information management platform, at least including the following process:

The device and the user information management platform send an access permission judgment request to the owner of the accessed device, where the access authority determination request includes the identification information of the requesting user and the accessed device, and is used for the access judgment authority of the owner of the accessed device. . The identification information is detailed in the description of step 101;

The device and user information management platform receives an access authority determination response sent by the owner of the accessed device, the access authority determination response including an indication of whether the user is allowed to access the accessed device.

The device and user information management platform and the owner of the accessed device can exchange information through the Internet or mobile network. In particular, the owner of the accessed device can interact with the device and the user information management platform information by the accessed device, that is, the owner of the accessed device logs in to the device and the user information management platform through the accessed device.

Step 103, if the requesting user can access the accessed device, the device and the user information management platform to the accessed device Or the device aggregation gateway of the accessed device or the proxy device of the accessed device forwards the device access request; otherwise, the device and the user information management platform send a device access request failure message to the requesting user.

The device access request failure message here may contain the reason why the access request failed.

Note that the device and the user information management platform can modify the device access request sent by the requesting user before forwarding (for example: in order to be compatible with the communication protocol; and the device device access request is reduced and then forwarded, if the identification information of the requesting user is not required to be forwarded. Or only extracting useful operational instructions; or other purposes), or directly forwarding without modification, therefore, "forwarding" in the present invention is broad.

After the accessed device receives the device access request, the operation instruction involved in the device access request is executed. The interaction between the device and the information management platform and the information between the accessed devices can be through the Internet, mobile networks, and the like.

A more specific example for the embodiment 1 is given: the user A logs in to the device and the user information management platform through the mobile phone, and initiates a request for accessing the user B's television (such as changing channels) to the device and the user information management platform, in the request The identification information of the television including the user A and the user B, assuming that the user A and the user B are in a friend relationship and the access rights of the user B's television are accessible to all the friends, the device and the user information management platform are based on the relationship between the user A and the user B. And when the access right of the TV of the user B determines that the user A can access the TV of the user B, the request is sent to the television of the user B.

Embodiment 1 of the present invention implements device access authority management by adding user information in a device access request, and introducing a relationship between the user and the user and between the user and the device, thereby solving the device access authority management caused by the large number of intelligent terminals. The problem of complicated work, low efficiency, and poor user experience. Example 2

A flowchart of a method for implementing device access in this example is shown in FIG. 2. Its specific includes:

Step 201: The device and the user information management platform receive the device access request sent by the user. For details and related operations, refer to the description in step 101 in Embodiment 1.

Step 202: The device and the user information management platform determine, according to the relationship between the requesting user and the owner of the accessed device, and/or the relationship between the requesting user and the accessed device, and the access authority of the accessed device, whether the requesting user can access the Accessing the device, or determining whether the user can access the accessed device by performing information interaction with the device and the user information management platform or the owner of the accessed device;

For details and related operations, refer to the description of step 102 in Embodiment 1.

Step 203: When the requesting user can access the accessed device, the device and the user information management platform forward the device access request to the device aggregation gateway of the accessed device or the proxy device of the accessed device; otherwise, the device and the user information tube The platform sends a device access request failure message to the requesting user.

The improvement of the embodiment is based on the addition of a device aggregation gateway between the device and the user information management platform and the accessed device. The device aggregation gateway is used for different devices (the device types are different and the supported communication protocols are different). Centralized management can be used to proxy a large number of low-end devices online. For example, in a home environment, a large number of low-end appliances (such as lights, water heaters, rice cookers, etc.) can access the Internet through the device aggregation gateway. At the same time, the single communication protocol between the device aggregation gateway and the device and user information management platform can also reduce the load on the device and user information management platform. Of course, the accessed device may also have a specific proxy device, and the proxy device of the accessed device may directly interact with the device and the user information management platform information, or may interact with the device and the user information management platform through the device aggregation gateway.

Note that the device and the user information management platform can modify the device access request sent by the requesting user before forwarding (for example: in order to be compatible with the communication protocol; and the device device access request is reduced and then forwarded, if the identification information of the requesting user is not required to be forwarded. Or only extract useful operational instructions; or other purposes), or forward directly without modification.

The information exchange between the device and user information management platform and the device aggregation gateway or proxy device can be through the Internet, mobile network, and the like.

It should be particularly noted that the device aggregation gateway or proxy device involved in the present invention may be a single physical entity or a functional module (which may be embedded in one or some devices or other physical entities).

Step 204: The device aggregation gateway or the proxy device forwards the device access request to the accessed device.

Note that the device aggregation gateway or proxy device can modify the device access request sent by the device and the user information management platform before forwarding (for example: in order to be compatible with the communication protocol; the device device access request is streamlined and then forwarded, if no forwarding request is required The user's identification information or only useful operational instructions; or other purposes) may also be forwarded directly without modification. If the proxy device of the accessed device interacts with the device and the user information management platform through the device aggregation gateway, the device aggregation gateway first forwards the device access request to the proxy device, and the proxy device forwards the device access request to the accessed device.

After the accessed device receives the device access request, the operation instruction related to the device access request is executed. Embodiment 2 of the present invention implements device access authority management by adding user information in a device access request, and introducing a relationship between the user and the user and between the user and the device, thereby solving the device access authority management caused by the large number of intelligent terminals. The problem of complicated work, low efficiency, and poor user experience, and the introduction of a device aggregation gateway, can support centralized network management of different devices (different device types and different supported communication protocols), and reduce the load on the device and user information management platform. Example 3

Step 301: The device aggregation gateway receives a device access request sent by the requesting user.

When the requesting user is within the communication range of the device aggregation gateway, the device access request may be directly sent to the device aggregation gateway. For details of the device access request and related operations, refer to the description in step 101 in Embodiment 1.

Step 302: The device aggregation gateway determines, according to the relationship between the requesting user and the owner of the accessed device, and/or the relationship between the user and the accessed device, and the access permission of the accessed device, whether the user can access the accessed device. Or determining whether the requesting user can access the accessed device by performing information interaction with the device and the user information management platform or the owner of the accessed device;

For the definition of the relationship between users, the relationship between users and devices, and the access rights of devices, refer to the description of step 102 in Embodiment 1.

The device aggregation gateway can locally set up and maintain inter-user relationships and/or user-to-device relationships and/or device access rights associated with the devices it manages. The device aggregation gateway can also acquire and store user-related relationships and/or user-to-device relationships and/or device access rights associated with the devices it manages by interacting with the device and user information management platform information.

The specific process of determining whether the user can access the accessed device according to the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access authority of the accessed device is the same as Embodiment 1 Step 102 is basically the same.

The process of requesting the user to access the accessed device by using the device and the user information management platform or the owner of the accessed device to determine whether the user can access the accessed device is substantially the same as that in the first step of Embodiment 1, and the detailed description is as follows:

When the device aggregation gateway does not have the user access permission judgment function or other conditions that cannot determine the user access rights, the device and the user information management platform or the owner of the accessed device may exchange information, and the device and the user information management platform may be The owner of the access device judges the user access authority and feeds back the judgment result to the device aggregation gateway. At least the following process is included:

A2. The device aggregation gateway sends an access permission determination request to the device and the user information management platform or the owner of the accessed device, where the access permission determination request includes identification information of the requesting user and the accessed device, and is used for the device and the user information management platform. Or the owner of the accessed device makes access judgment authority. For a detailed description of the identification information, refer to the description of step 101 in Embodiment 1. It should be noted that when the device and the user information management platform do not have the user access authority judgment function or other conditions that cannot determine the user access authority, all of the devices that are accessed may be The information is exchanged, and the owner of the accessed device performs the user access authority judgment, and the judgment result is fed back to the device and the user information management platform. For the specific process, refer to the description of step 102 in Embodiment 1;

B2. The device aggregation gateway receives the device and the user information management platform or the access authority judgment response sent by the owner of the accessed device, and the access permission judgment response includes an instruction to request the user to access the accessed device.

Step 303: If the requesting user can access the accessed device, the device aggregation gateway forwards the device access request to the accessed device or the proxy device of the accessed device; otherwise, the device aggregation gateway sends a device access request failure message to the requesting user.

If the accessed device interacts with the device aggregation gateway information through the proxy device, the device aggregation gateway first forwards the device access request to the proxy device, and the proxy device forwards the device access request to the accessed device.

Note that the device aggregation gateway can modify the device access request sent by the requesting user before forwarding (for example: in order to be compatible with the communication protocol; the device device access request is reduced and then forwarded, if the identification information of the requesting user is not required to be forwarded or only extracted Useful operational instructions; or other purposes), can also be forwarded directly without modification.

After the accessed device receives the device access request, it executes the operation instruction involved in the device access request.

On the basis of the beneficial effects of the second embodiment, the third embodiment of the present invention also supports requesting the user to directly access the device through the device aggregation gateway, thereby increasing the user experience (for example, the user cannot temporarily communicate with the device and the user information management platform through the Internet or the mobile network). ), reducing the load on the device and user information management platform. Example 4

Step 401: The accessed device receives a device access request sent by the requesting user.

When the requesting user is within the communication range of the accessed device, the device access request may be directly sent to the accessed device. For the specific content and related operations of the device access request, refer to the description in step 101 in Embodiment 1.

Step 402: The accessed device determines, according to the relationship between the requesting user and the owner of the accessed device, and/or the relationship between the requesting user and the accessed device, and the access permission of the accessed device, whether the user can access the accessed device. Or determining whether the requesting user can access the accessed device by performing information interaction with the device and the user information management platform or the device aggregation gateway or the owner of the accessed device;

The accessed device can locally set and maintain the inter-user relationship and/or user-to-device relationship and/or device access rights associated with itself. The accessed device can also be connected to the device and user information management platform or device. The information exchange acquires and stores the inter-user relationship and/or user-to-device relationship and/or device access rights associated with itself.

The specific process of the device being accessed by the device and the user information management platform or the device aggregation gateway or the owner of the accessed device to determine whether the user can access the accessed device is substantially the same as the step 102 in the first embodiment. :

When the accessed device does not have the user access permission judgment function or other conditions that cannot determine the user access right, the device and the user information management platform or the device aggregation gateway or the owner of the accessed device may perform information interaction, the device and the user information. The management platform or the device aggregation gateway or the owner of the accessed device performs the user access authority judgment, and feeds the judgment result to the accessed device, and at least includes the following process:

A3. The accessed device sends an access permission determination request to the device and the user information management platform or the device aggregation gateway or the owner of the accessed device, where the access permission determination request includes the identification information of the requesting user and the accessed device, and is used for the device and The user information management platform or the device aggregation gateway or the owner of the accessed device performs access judgment authority. For the identification information, refer to the description of step 101 in Embodiment 1. It should be noted that when the device aggregation gateway does not have the user access permission judgment function or other conditions that cannot determine the user access authority, the device and the user information management platform or the owner information of the accessed device may interact with the device and the user information. The management platform or the owner of the accessed device performs the user access authority judgment, and the judgment result is fed back to the device aggregation gateway. For the specific procedure, refer to step 302 of Embodiment 3. When the device and the user information management platform do not have the user access authority judgment function or other conditions that cannot determine the user access authority, the information may be exchanged with the owner of the accessed device, and the owner of the accessed device performs the user access authority judgment. And the result of the judgment is fed back to the device and the user information management platform. For the specific process, refer to step 102 in Embodiment 1;

B3. The accessed device receiving device and the user information management platform or the device aggregation gateway or the owner of the accessed device sends an access permission judgment response, and the access permission judgment response includes an instruction to request the user to access the accessed device.

Step 403: If the requesting user can access the accessed device, the accessed device performs an operation instruction involved in the device access request; otherwise, the accessed device sends a device access request failure message to the requesting user.

On the basis of the beneficial effects of the first, second, and third embodiments, the fourth embodiment of the present invention also supports requesting the user to directly access the accessed device, thereby increasing the user experience (for example, the user cannot temporarily access the Internet or the mobile network and the device). And the user information management platform or the device aggregation gateway communication) reduces the load on the device and the user information management platform and the device aggregation gateway. Example 5

Step 501: The proxy device of the accessed device receives a device access request sent by the requesting user.

A proxy device is a special device that can be interconnected with a accessed device through a protocol (such as UPnP, IGRS), and various operations on the accessed device can be implemented on the proxy device. To give a concrete example: TV is a proxy device, and air conditioners are accessed devices. On the TV, various operations can be performed on the air conditioner, such as displaying and controlling the temperature of the air conditioner.

When the requesting user is within the communication range of the proxy device of the accessed device, the device access request may be directly sent to the proxy device of the accessed device. For details of the device access request and related operations, refer to the description in step 101 in Embodiment 1.

Step 502: The proxy device determines, according to the relationship between the requesting user and the owner of the accessed device, and/or the relationship between the user and the accessed device, and the access authority of the accessed device, whether the user can access the accessed device, or Determine whether the requesting user can access the accessed device by performing information interaction with the device and the user information management platform or the device aggregation gateway or the owner of the accessed device;

The proxy device can locally set and maintain inter-user relationships and/or user-to-device relationships and/or device access rights associated with the accessed device. The proxy device can also acquire and store the inter-user relationship and/or user-to-device relationship and/or device access rights associated with the accessed device by interacting with the device and the user information management platform or the device aggregation gateway information.

The specific process of the proxy device to determine whether the user can access the accessed device by using the information exchange between the device and the user information management platform or the device aggregation gateway or the owner of the accessed device is substantially the same as the step 402 in the fourth embodiment.

When the proxy device does not have the user access permission judgment function or other conditions that cannot determine the user access right, the information exchange may be performed with the device and the user information management platform or the device aggregation gateway or the owner of the accessed device. The device and the user information management platform or the device aggregation gateway or the owner of the accessed device judges the user access authority, and feeds the judgment result to the proxy device, and at least includes the following process:

A3. The proxy device sends an access permission determination request to the device and the user information management platform or the device aggregation gateway or the owner of the accessed device, where the access permission determination request includes the identification information of the requesting user and the accessed device, and is used for the device and the user. The information management platform or the device aggregation gateway or the owner of the accessed device performs access judgment authority. For the identification information, refer to the description of step 101 in Embodiment 1. It should be noted that when the device aggregation gateway does not have the user access permission judgment function or other conditions that cannot determine the user access authority, the device and the user information management platform or the owner information of the accessed device may interact with the device and the user information. The management platform or the owner of the accessed device performs the user access authority judgment, and the judgment result is fed back to the device aggregation gateway. For the specific process, refer to the description of step 302 in Embodiment 3. When the device and the user information management platform do not have the user access authority judgment function or other conditions that cannot determine the user access authority, the information may be exchanged with the owner of the accessed device, and the owner of the accessed device performs the user access authority judgment. And the result of the judgment is fed back to the device and the user information management platform. For the specific process, refer to step 102 in Embodiment 1;

B3. The proxy device receives the access judgment response sent by the device and the user information management platform or the device aggregation gateway or the owner of the accessed device, and the access permission judgment response includes an indication of whether the user can access the accessed device.

Step 503: If the requesting user can access the accessed device, the proxy device forwards the device access request to the accessed device; otherwise, the proxy device sends a device access request failure message to the requesting user.

Note that the proxy device can modify the device access request sent by the requesting user before forwarding (for example: in order to be compatible with the communication protocol; the device device access request is reduced and then forwarded, if the identification information of the requesting user is not required to be forwarded or only useful The operation instructions; or other purposes), can also be forwarded directly without modification.

On the basis of the beneficial effects of the first, second, and third embodiments, the fifth embodiment of the present invention further supports requesting the user to directly access the proxy device of the accessed device, thereby increasing the user experience (for example, the user cannot temporarily use the Internet or the mobile network) The device and the user information management platform or the device aggregation gateway communication) reduce the load on the device and the user information management platform and the device aggregation gateway. Example 6

A block diagram of a device for implementing device access and a user information management platform device in this example is shown in FIG. 6 , and specifically includes: The first information receiving unit is configured to receive a device access request sent by the requesting user, where the device access request includes the identification information of the requesting user and the accessed device. The identifier information may be the requesting user identifier and the accessed device identifier, and the identifier information may also be an association identifier. For specific definition, refer to step 101 in Embodiment 1 or the related description in step 301 in Embodiment 3;

a first information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or request a relationship between the user and the accessed device, and an access permission of the accessed device, whether the requested user can access the accessed device The device, or the information exchange with the owner of the accessed device, determines whether the user can access the accessed device. For details, refer to the related description in step 102 in Embodiment 1;

a first information execution unit, configured to: when the requesting user can access the accessed device, forward the device access request to the device aggregation gateway of the accessed device or the accessed device or the proxy device of the accessed device; otherwise, send the device access request to the requesting user. For details, refer to step 103 in Embodiment 1 and related description in step 203 in Embodiment 2.

The device and user information management platform device in this example may further include:

The first registration unit is used for registration of users and devices. The first registration unit stores and maintains information about users and devices.

The first relationship and device authority maintenance unit is configured to save the relationship between users, the relationship between the user and the device, and the access authority of the device. The first relationship and device rights maintenance unit can also support the relationship between users, the relationship between users and devices, and the establishment or update or deletion of device access rights.

It should be noted that the device and the user information management platform device in Embodiment 6 of the present invention may be a physical entity; or may be in a logical sense, that is, the first information receiving unit, the first information processing unit, and the first information execution. The unit, the first registration unit, and the first relationship and device rights maintenance unit may be located in the same physical entity or in different physical entities. Meanwhile, each unit of the device and the user information management platform device in the sixth embodiment of the present invention is also in a logical sense. In specific implementation, multiple units may be combined into one unit or module, and one unit may be split into multiple units or Module.

The device and the user information management platform device in the sixth embodiment of the present invention solve the problem by adding user information in the device access request, and introducing the relationship between the user and the user and between the user and the device to implement device access authority management. Due to the large number of intelligent terminals, the device access management management is complicated, inefficient, and the user experience is poor. At the same time, the device aggregation gateway is introduced, which can support centralized network management of different devices (different device types and different supported communication protocols). And reduce the load on the device and user information management platform. Example 7 A block diagram of a device aggregation gateway device that implements device access in this example is shown in FIG. 7, which specifically includes: a second information receiving unit, configured to receive a device access request sent by a requesting user, where the device access request includes a request Identification information of the user and the accessed device. The identifier information may be the requesting user identifier and the accessed device identifier, or may be an associated identifier. For the specific definition, refer to the related description of step 101 in Embodiment 1;

a second information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or requesting the relationship between the user and the accessed device and the access authority of the accessed device, whether the requested user can access the accessed device The device, or the information exchange with the device and the user information management platform or the owner of the accessed device, determines whether the user can access the accessed device. For details, refer to the description in step 302 in Embodiment 3;

a second information execution unit, configured to: when the requesting user can access the accessed device, forward the device access request to the accessed device or the proxy device of the accessed device; otherwise, send the device access request failure message to the requesting user, and the specific content is as follows. A detailed description of step 303 in 3.

A device aggregation gateway device of this example may further include:

The second relationship and device authority maintenance unit is configured to save the inter-user relationship and/or the user-to-device relationship and/or the device access authority associated with the device it manages, and may interact with the device and the user information management platform information. Mode acquisition or local establishment and maintenance (eg, establishment or update or deletion of inter-user relationships and/or user-to-device relationships and/or device access rights by the owner of the accessed device at the device aggregation gateway).

Specifically, the second information receiving unit is further configured to determine whether the received device access request is a device access request directly sent by the requesting user, and if not, directly transmitting the device access request to the second information executing unit, by the second The information execution unit forwards the device access request directly to the accessed device or the proxy device of the accessed device, and if so, transmits the device access request to the second information processing unit.

It should be noted that the device aggregation gateway device in Embodiment 7 of the present invention may be a physical entity; or may be in a logical sense, that is, the second information receiving unit, the second information processing unit, the second information executing unit, and the first The relationship and device authority maintenance unit can be located in the same physical entity or in different physical entities. In the meantime, the units of the device aggregation gateway device in the seventh embodiment of the present invention are also logically implemented. In specific implementation, multiple units may be combined into one unit or module, and one unit may be split into multiple units or modules.

The device aggregation gateway device in the seventh embodiment of the present invention solves the problem of the number of intelligent terminals by adding user information in the device access request, and introducing the relationship between the user and the user and between the user and the device to implement device access authority management. The huge device access management management problem is complicated, low in efficiency, and poor user experience. At the same time, the device aggregation gateway is introduced to support centralized network management of different devices (different device types and different supported communication protocols), and to reduce equipment and The load of the user information management platform. It also supports requesting users to access devices directly through the device aggregation gateway, which increases the user experience (such as users temporarily unable to use the Internet or mobile networks and devices). And user information management platform communication), reducing the load on the device and user information management platform. Example 8

A block diagram of a device for accessing a device for accessing a device in this example is as shown in FIG. 8 , which specifically includes: a third information receiving unit, configured to receive a device access request sent by a requesting user, where the device access request includes a request Identification information of the user and the accessed device. The identifier information may be the requesting user identifier and the accessed device identifier, or may be an associated identifier. For the specific definition, refer to the related description in step 101 in Embodiment 1;

a third information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or requesting the relationship between the user and the accessed device, and the access authority of the accessed device, whether the requested user can access the accessed device The device, or the information exchange with the device and the user information management platform or the device aggregation gateway or the owner of the accessed device to determine whether the user can access the accessed device. For details, refer to the description in step 402 in Embodiment 4.

And a third information execution unit, configured to: when the requesting user can access the accessed device, perform an operation instruction related to the device access request; otherwise, send a device access request failure message to the requesting user. For details, refer to the related description in step 403 in Embodiment 4. .

An access device device of this example may further include:

The third relationship and device authority maintenance unit is configured to save the inter-user relationship and/or the user-to-device relationship and/or the device access right related to the accessed device itself, and may aggregate the gateway through the device and the user information management platform or device. The manner in which the information is exchanged is acquired or maintained locally (eg, by the owner of the accessed device at the accessed device, the inter-user relationship and/or the user-to-device relationship and/or device access rights are established or updated or deleted).

Specifically, the third information receiving unit is further configured to determine whether the received device access request is a device access request directly sent by the requesting user, and if not, directly transmitting the device access request to the third information executing unit, by the third The information execution unit executes an operation instruction related to the device access request, and if so, transmits the device access request to the third information processing unit.

It should be noted that the accessed device device in Embodiment 8 of the present invention may be a physical entity; or may be in a logical sense, that is, a third information receiving unit, a third information processing unit, a third information executing unit, and a third The three relationship and device rights maintenance unit can be located in the same physical entity or in different physical entities. In the meantime, the units of the device to be accessed in the eighth embodiment of the present invention are also logically. In the specific implementation, multiple units may be combined into one unit or module, and one unit may be split into multiple units or modules.

By using the accessed device device in Embodiment 8 of the present invention, by adding user information in the device access request, The relationship between the user and the user and between the user and the device is introduced to implement the device access authority management, thereby solving the problem that the device access authority management work is complicated, the efficiency is low, and the user experience is poor due to the large number of intelligent terminals. At the same time, the device aggregation gateway is introduced, which can support centralized network management of different devices (different device types and different supported communication protocols), and reduce the load on the device and user information management platform. It also supports requesting users to directly access devices on the accessed device, which increases the user experience (for example, the user cannot temporarily communicate with the device and the user information management platform or the device aggregation gateway through the Internet or the mobile network), thereby reducing the device and user information management platform and The load of the device aggregation gateway. Example 9

A block diagram of a proxy device device for implementing device access in this example is as shown in FIG. 9, which specifically includes: a fourth information receiving unit, configured to receive a device access request sent by a requesting user, where the device access request includes a requesting user And identification information of the accessed device. The identifier information may be the requesting user identifier and the accessed device identifier, or may be an associated identifier. For the specific definition, refer to the related description in step 101 in Embodiment 1;

a fourth information processing unit, configured to determine, according to a relationship between the requesting user and the owner of the accessed device, and/or requesting the relationship between the user and the accessed device, and the access authority of the accessed device, whether the requested user can access the accessed device The device, or the information exchange with the device and the user information management platform or the device aggregation gateway or the owner of the accessed device to determine whether the user can access the accessed device. For details, refer to the description in step 502 in Embodiment 5;

The fourth information execution unit is configured to: when the requesting user can access the accessed device, forward the device access request to the accessed device; otherwise, send the device access request failure message to the requesting user. For details, refer to the related description in step 503 in Embodiment 5. .

The proxy device device of this example may further include:

The fourth relationship and device authority maintenance unit is configured to save the inter-user relationship and/or the user-to-device relationship and/or the device access right related to the accessed device, and may aggregate the gateway information by using the device and the user information management platform or device. Inter-acquisition acquisition or local establishment and maintenance (eg, establishment of an inter-user relationship and/or user-to-device relationship and/or device access rights establishment or update or deletion by the owner of the accessed device at the proxy device).

Specifically, the fourth information receiving unit is further configured to determine whether the received device access request is a device access request directly sent by the requesting user, and if not, directly transmitting the device access request to the fourth information executing unit, by the fourth The information execution unit forwards the device access request directly to the accessed device, and if so, transmits the device access request to the fourth information processing unit.

It should be noted that the proxy device in Embodiment 9 of the present invention may be a physical entity; The fourth information receiving unit, the fourth information processing unit, the fourth information executing unit, and the fourth relationship and the device rights maintaining unit may be located in the same physical entity or in different physical entities. In the meantime, the units of the proxy device in the embodiment 9 of the present invention are also in a logical sense. In specific implementation, multiple units may be combined into one unit or module, and one unit may be split into multiple units or modules.

The proxy device device in the embodiment 9 of the present invention solves the problem of the number of smart terminals by adding user information in the device access request, and introducing the relationship between the user and the user and between the user and the device to implement device access authority management. The huge device access management management problem is complicated, low efficiency, and poor user experience. At the same time, the device aggregation gateway is introduced, which can support centralized network management of different devices (different device types and different supported communication protocols), and reduce the load on the device and user information management platform. It also supports requesting users to access the accessed device through the proxy device, which increases the user experience (for example, the user cannot temporarily communicate with the device and the user information management platform or the device aggregation gateway through the Internet or the mobile network), thereby reducing device and user information management. The load of the platform and device aggregation gateway. Example 10

A structural block diagram of a system for implementing device access in this example is shown in FIG. 10, and includes a requesting user and an accessed device or an owner including the requesting user, the accessed device, and the accessed device, and further includes:

The device and user information management platform is the device and user information management platform device of the embodiment 6, and the related description of the embodiment 6 is described in detail.

The system for implementing device access may further include a device aggregation gateway. For the device of Embodiment 7, refer to the related description of Embodiment 7.

The accessed device in the system for implementing device access may also be the accessed device device of Embodiment 8, as described in detail in Embodiment 8.

The system for implementing device access may further include a proxy device, which is the proxy device device of Embodiment 9, as described in detail in Embodiment 8.

The double arrow connection in Fig. 10 exemplifies various information interaction modes involved in the above embodiment.

The system for implementing device access in Embodiment 10 of the present invention solves the problem of intelligence by adding user information in the device access request, and introducing the relationship between the user and the user and between the user and the device to implement device access authority management. The problem of complicated device access management caused by a large number of terminals is complicated, low efficiency, and poor user experience. At the same time, the device aggregation gateway is introduced, which can support centralized network management of different devices (different device types and different supported communication protocols), and reduce the load on the device and user information management platform. It also supports requesting users to access devices directly through the device aggregation gateway or proxy device or directly access the accessed devices, which increases the user experience. (If the user cannot temporarily communicate with the device and the user information management platform through the Internet or the mobile network), the load on the device and the user information management platform or the device aggregation gateway is alleviated.

It will be understood by those skilled in the art that all or part of the processes in the above embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, and the program is executed. At the time, the flow of the embodiment of each of the above methods may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

claims

1. A method for realizing device access, which is characterized by including:

Receive a device access request sent by the requesting user, where the device access request includes identification information of the requesting user and the accessed device;

Determine whether the requesting user can access the accessed device based on the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device, or by communicating with the accessed device The owner conducts information interaction to determine whether the requesting user can access the accessed device; when the requesting user can access the accessed device, forward the device access request to the accessed device or the device aggregation gateway of the accessed device or the proxy device of the accessed device; Otherwise, a device access request failure message is sent to the requesting user.

2. The method according to claim 1, characterized in that the identification information is a requesting user identification and an accessed device identification.

3. The method according to claim 1, characterized in that the identification information is an associated identification.

4. The method according to claim 1, wherein the relationship between the requesting user and the owner of the accessed device is at least one of a friend, a stranger, and a blacklist.

5. The method according to claim 4, characterized in that the access rights of the accessed device are at least owner-only, accessible to all friends, accessible to some friends, accessible to non-blacklisted users, and accessible to anyone. Visit one.

6. The method according to claim 5, characterized in that the relationship between the requesting user and the accessed device is at least one of owner and non-owner.

7. The method according to claim 6, characterized in that,

In the method for determining whether the requesting user can access the accessed device based on the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device, at least include:

If the relationship between the requesting user and the accessed device is owner, or if the relationship between the requesting user and the accessed device is non-owner, and the relationship between the requesting user and the owner of the accessed device is friend, and The access rights of the accessed device are accessible to all friends or accessible to anyone or accessible to non-blacklisted users or accessible to some friends and the requesting user is an accessible friend user, or if the relationship between the requesting user and the accessed device is is not the owner, and the relationship between the requesting user and the owner of the accessed device is a stranger, and access to the accessed device is accessible by anyone or by non-blacklisted users, or If the relationship between the requesting user and the accessed device is non-owner, the relationship between the requesting user and the owner of the accessed device is blacklist, and the access permission of the accessed device is accessible by anyone, then the request The user can access the accessed device; otherwise, the requesting user cannot access the accessed device.

8. The method according to claim 1, characterized in that,

The method for determining whether the requesting user can access the accessed device through information interaction with the owner of the accessed device at least includes:

Send an access permission determination request to the owner of the accessed device, where the access permission determination request includes the identification information of the requesting user and the accessed device;

Receive an access permission determination response sent by the owner of the accessed device, where the access permission determination response includes an indication of whether the requesting user can access the accessed device.

9. A method for realizing device access, characterized by including:

Determine whether the requesting user can access the accessed device based on the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device, or by communicating with the device and user The information management platform or the owner of the accessed device conducts information interaction to determine whether the requesting user can access the accessed device;

When the requesting user can access the accessed device, the device access request is forwarded to the accessed device or the accessed device's proxy device; otherwise, a device access request failure message is sent to the requesting user.

10. The method according to claim 9, characterized in that,

The method for determining whether the requesting user can access the accessed device through information interaction with the device and user information management platform or the owner of the accessed device at least includes:

Send an access permission determination request to the device and user information management platform or the owner of the accessed device, where the access permission determination request includes the identification information of the requesting user and the accessed device;

Receive an access permission determination response sent by the device and user information management platform or the owner of the accessed device, where the access permission determination response includes an indication of whether the requesting user can access the accessed device.

11. A method for achieving device access, characterized by including:

Receive a device access request sent by the requesting user, where the device access request includes identification information of the requesting user and the accessed device; Determine whether the requesting user can access the accessed device based on the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device, or by communicating with the device and user The information management platform or device aggregation gateway or the owner of the accessed device conducts information interaction to determine whether the requesting user can access the accessed device;

When the requesting user can access the accessed device, forward the device access request to the accessed device or execute the operation instructions involved in the device access request; otherwise, send a device access request failure message to the requesting user.

12. The method according to claim 11, characterized in that,

The method for determining whether the requesting user can access the accessed device through information interaction with the device and user information management platform or device aggregation gateway or the owner of the accessed device at least includes:

Send an access permission determination request to the device and user information management platform or device aggregation gateway or the owner of the accessed device, where the access permission determination request includes the identification information of the requesting user and the accessed device;

Receive an access permission determination response sent by the device and user information management platform or device aggregation gateway or the owner of the accessed device, where the access permission determination response includes an indication of whether the requesting user can access the accessed device.

13. An equipment and user information management platform device, characterized by including:

The first information receiving unit is configured to receive a device access request sent by the requesting user, where the device access request includes identification information of the requesting user and the accessed device;

A first information processing unit configured to determine whether the requesting user can access the accessed device based on the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device. device, or determine whether the requesting user can access the accessed device through information interaction with the owner of the accessed device;

The first information execution unit is used to forward the device access request to the accessed device or the device aggregation gateway of the accessed device or the proxy device of the accessed device when the requesting user can access the accessed device; otherwise, send the device access request to the requesting user. Failure message.

14. The device according to claim 13, wherein the identification information is a requesting user identification and an accessed device identification.

15. The device according to claim 13, characterized in that the identification information is an associated identification.

16. The device according to claim 13, characterized in that: the requesting user and the accessed device The relationship between the device owners is at least one of friend, stranger, and blacklist.

17. The device according to claim 16, wherein the access rights of the accessed device are at least owner-only access, all friends can access, some friends can access, non-blacklisted users can access, and anyone can access Visit one.

18. The apparatus according to claim 17, wherein the relationship between the requesting user and the accessed device is at least one of owner and non-owner.

19. The apparatus according to claim 18, wherein: the access is based on the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access of the accessed device. The methods for determining whether the requesting user can access the accessed device include at least:

If the relationship between the requesting user and the accessed device is owner, or if the relationship between the requesting user and the accessed device is non-owner, and the relationship between the requesting user and the owner of the accessed device is friend, and The access rights of the accessed device are accessible to all friends or accessible to anyone or accessible to non-blacklisted users or accessible to some friends and the requesting user is an accessible friend user, or if the relationship between the requesting user and the accessed device is is not the owner, and the relationship between the requesting user and the owner of the accessed device is a stranger, and the access permissions of the accessed device are accessible by anyone or non-blacklisted users, or if the requesting user and the accessed device If the relationship between the requesting user and the owner of the accessed device is non-owner, and the relationship between the requesting user and the owner of the accessed device is blacklist, and the access permission of the accessed device is accessible to anyone, then the requesting user can access the accessed device; otherwise , the requesting user cannot access the accessed device.

20. The device according to claim 13, characterized in that,

The method for determining whether the requesting user can access the accessed device based on information interaction with the owner of the accessed device at least includes:

21. The device according to claim 13, further comprising:

The first registration unit is used for user and device registration.

22. The device according to claim 21, further comprising:

The first relationship and device permission maintenance unit is used to save the relationship between users, the relationship between users and devices, Device access rights.

23. A device aggregation gateway device, characterized by including:

The second information receiving unit is configured to receive a device access request sent by the requesting user, where the device access request includes identification information of the requesting user and the accessed device;

The second information processing unit is used to determine the relationship between the requesting user and the owner of the accessed device and

/or determine the relationship between the requesting user and the accessed device and the access rights of the accessed device to determine whether the requesting user can access the accessed device, or determine the request through information interaction with the device and user information management platform or the owner of the accessed device Whether the user can access the accessed device;

The second information execution unit is configured to forward the device access request to the accessed device or the proxy device of the accessed device when the requesting user can access the accessed device; otherwise, send a device access request failure message to the requesting user.

24. The device according to claim 23, further comprising:

The second relationship and device permission maintenance unit is used to save the relationship between users and/or the relationship between users and devices and/or device access permissions related to the devices it manages.

25. The device according to claim 23 or 24, characterized in that the second information receiving unit is also used to determine whether the received device access request is a device access request directly sent by the requesting user; if not, directly Send the device access request to the second information execution unit, and the second information execution unit directly forwards the device access request to the accessed device or the proxy device of the accessed device. If so, the device access request is sent to the second information processing unit. .

26. An accessed equipment device, characterized in that it includes:

The third information receiving unit is configured to receive a device access request sent by the requesting user, where the device access request includes identification information of the requesting user and the accessed device;

The third information processing unit is used to determine whether the requesting user can access the accessed device based on the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device. device, or determine whether the requesting user can access the accessed device through information interaction with the device and user information management platform or device aggregation gateway or the owner of the accessed device;

The third information execution unit is used to execute the operation instructions involved in the device access request when the requesting user can access the accessed device; otherwise, a device access request failure message is sent to the requesting user.

27. The device according to claim 26, further comprising: The third relationship and device permission maintenance unit is used to save the relationship between users and/or the relationship between users and devices and/or the device access permissions related to the accessed device itself.

28. The device according to claim 26 or 27, wherein the third information receiving unit is further configured to determine whether the received device access request is a device access request directly sent by the requesting user; if not, directly The device access request is sent to the third information execution unit, and the third information execution unit executes the operation instructions involved in the device access request. If so, the device access request is sent to the third information processing unit.

29. An agent device, characterized in that it includes:

The fourth information receiving unit is configured to receive a device access request sent by the requesting user, where the device access request includes identification information of the requesting user and the accessed device;

The fourth information processing unit is used to determine whether the requesting user can access the accessed device based on the relationship between the requesting user and the owner of the accessed device and/or the relationship between the requesting user and the accessed device and the access rights of the accessed device. device, or determine whether the requesting user can access the accessed device through information interaction with the device and user information management platform or device aggregation gateway or the owner of the accessed device;

The fourth information execution unit is used to forward the device access request to the accessed device when the requesting user can access the accessed device; otherwise, send a device access request failure message to the requesting user.

30. The device according to claim 29, further comprising:

The fourth relationship and device permission maintenance unit is used to save the relationship between users and/or the relationship between users and devices and/or the device access permissions related to the accessed device.

31. The device according to claim 29 or 30, characterized in that the fourth information receiving unit is also used to determine whether the received device access request is a device access request directly sent by the requesting user; if not, directly The device access request is sent to the fourth information execution unit, and the fourth information execution unit directly forwards the device access request to the accessed device. If so, the device access request is sent to the fourth information processing unit.

32. A system for realizing device access, including a requesting user and an accessed device or a requesting user, an accessed device and an owner of the accessed device, characterized in that it also includes as described in any one of claims 13 to 22 equipment and user information management platform devices.

33. The system according to claim 32, further comprising a device aggregation gateway device according to any one of claims 23 to 25.

34. The system according to claim 32 or 33, characterized in that the accessed device is the accessed device device according to any one of claims 26 to 28.

35. The system according to claim 32 or 33, further comprising a proxy device device according to any one of claims 29 to 31.