HOME SYSTEM ESTABLISHING METHOD

TECHNICAL FIELD

The present invention relates to a home system establishing method, and more particularly to a home system establishing method for establishing a home system in a different server.

BACKGROUND

Recently, with the rapid growth of many social networking sites such as Twitter® and Facebook®, the social networking sites have become the new trend of using Internet. For example, people can share various types of information contents with each other. However, the current social networking sites still have some limitations. Firstly, for sharing and managing the information contents through the current service provider architecture, the user has to register an account and login to the social networking site. In addition, the users of different social networking sites cannot share the information contents through different service providers. Moreover, if the information contents acquired by the user are distributed in the servers that are provided by different social groups of service providers, the information contents cannot be easily managed.

For solving the above drawbacks, a workspace and a method for building the workspace have been disclosed in U.S. patent application Ser. Nos. 14/324,069 and 14/325,466, and a method for projecting a workspace has been disclosed in U.S. patent application Ser. No. 14/577,772. According to the disclosures of these patents, the information contents and tools to be shared are firstly configured in the workspace by a user, and then a uniform resource identifier corresponding to the workspace is transmitted to another user. Consequently, another user can connect with the corresponding workspace to achieve the purpose of sharing information contents and tools. Under this circumstance, users can share information contents without the need to register an account and login to the social networking site, and the users of different social networking sites can share the information contents through different service providers.

However, after the user acquires the uniform resource identifier of the workspace, it is necessary to establish a home system for managing the workspace in order to avoid inconvenience of recording and managing the uniform resource identifier. After the home system is accessed, the workspace corresponding to the received uniform resource identifier can be directly opened in the home system.

For example, a method of establishing a home system is disclosed in China Patent Application No. 201510003852.0. In this patent, the workspace and the home system are stored in the same server. If the workspace corresponding to the user is stored in a server of a specified domain, the user is possibly impermissible to establish the home system in the server with the workspace. For example, if the user is a customer of Company A, but the received workspace is stored in the server of Company B, the user has no access right to establish the home system for managing the workspace in the server of Company B. In case that the workspace is stored in the server of a company, a school, a specified national region or a specified domain, the above problems possibly occur.

Consequently, after the workspace is received, it is an important issue to guide the user to an appropriate server so as to establish a home system for managing the workspace.

SUMMARY

For solving the drawbacks of the conventional technologies, the present invention provides a home system establishing method for guiding a user to establish a home system in an appropriate server, wherein the home system belongs to the user, and a workspace is hosted and managed by the home system.

In accordance with an aspect of the present invention, there is provided a home system establishing method. The home system establishing method includes the following steps. Firstly, a workspace is provided in a first server. Then, a user connects with the workspace. Then, the user is guided to establish a home system in a second server. The home system belongs to the user, and the workspace is hosted and managed by the home system.

In an embodiment, the home system establishing method further includes providing an administrative server and guiding the user to establish the home system in the second server by the administrative server.

In an embodiment, the administrative server at least contains a service scope data of the second server.

In an embodiment, the service scope data contains at least one of an e-mail address range, an IP address range and/or a geographical location range.

In an embodiment, the administrative server guides the user to establish the home system in the second server according to the match of at least one of an e-mail address, an IP address and/or a geographical location of the user and the service scope data.

In an embodiment, the user has a first identification information corresponding to the projected workspace, and the user has a second identification information corresponding to the home system.

In an embodiment, while the user establishes the home system in the second server, a connecting relationship between the user and at least one of the first server, the second server, the workspace and the home system is stored in the second server and/or the administrative server.

In an embodiment, the connecting relationship includes at least one of a domain name of the first server, a recognition information of the workspace, a first identification information of the user corresponding to the workspace, a domain name of the second server, a recognition information of the home system and a second identification information of the user corresponding to the home system.

In an embodiment, the administrative server is the first server, the second server or an independent server.

In an embodiment, the home system establishing method further includes steps of acquiring a projectable space instance through a uniform resource identifier, and using a projector to parse the projectable space instance to generate a projected workspace corresponding to the workspace, so that the user connects with the workspace.

In an embodiment, the projectable space instance is stored in the first server. In accordance with another aspect of the present invention, there is provided a server for establishing a home system that hosts and manages a workspace. The workspace is provided by an additional server. After a user connects to the workspace, the user is guided to establish the home system belonging to the user in the server.

In an embodiment, the user is guided to establish the home system in the server by an administrative server.

In an embodiment, the administrative server at least contains a service scope data of the server.

In an embodiment, the service scope data contains at least one of an e-mail address range, an IP address range and/or a geographical location range.

In an embodiment, the administrative server guides the user to establish the home system in the server according to the match of at least one of an e-mail address, an IP address and/or a geographical location of the user and the service scope data.

In an embodiment, the user has a first identification information corresponding to the projected workspace, and the user has a second identification information corresponding to the home system.

In an embodiment, while the user establishes the home system in the server, a connecting relationship between the user and at least one of the server, the additional server, the workspace and the home system is stored in the server and/or the administrative server.

In an embodiment, the connecting relationship includes at least one of a domain name of the server, a recognition information of the workspace, a first identification information of the user corresponding to the workspace, a domain name of the additional server, a recognition information of the home system and a second identification information of the user corresponding to the home system.

In an embodiment, the administrative server is the server, the additional server or an independent server.

In an embodiment, a projectable space instance corresponding to the workspace is acquired through a uniform resource identifier, wherein a projector is used to parse the projectable space instance to generate a projected workspace corresponding to the workspace, so that the user connects with the workspace.

In an embodiment, the projectable space instance is stored in the additional server.

The above objects and advantages of the present invention will become more readily apparent to those ordinarily skilled in the art after reviewing the following detailed description and accompanying drawings, in which:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating an implementation concept of a unifying method according to an embodiment;

FIG. 2 is a schematic diagram illustrating an implementation concept of using the unified script as an intermediate language for implementing the personal workspace;

FIG. 3 is a schematic diagram illustrating a preferred configuration of a personal workspace;

FIG. 4 is a schematic diagram illustrating an initial state of the method of projecting the workspace according to an embodiment of the present invention;

FIGS. 5A and 5B are schematic diagrams illustrating operating concepts of the method of projecting the workspace as shown in FIG. 4;

FIG. 6 is a schematic diagram illustrating the relationship between a projectable space instance as shown in FIG. 4 and a projected workspace as shown in FIG. 5B;

FIG. 7 is a flowchart illustrating a home system establishing method according to an embodiment of the present invention;

FIG. 8 is a schematic diagram illustrating a usage situation applied to a home system establishing method according to an embodiment of the present invention;

FIG. 9 is a schematic diagram illustrating a process of connecting the user and the workspace according to an embodiment of the present invention;

FIG. 10 is a schematic diagram illustrating the concept of connecting the user to the workspace according to an embodiment of the present invention; and

FIG. 11 is a schematic diagram illustrating a process of establishing the home system according to an embodiment of the present invention.

DETAILED DESCRIPTION

The present invention is more fully appreciated by reference to the following description, including the following glossary of terms and the concluding examples. For the sake of brevity, the disclosures of the publications, including patents, cited in this specification are herein incorporated by reference.

The examples below are non-limiting and are merely representative of various aspects and features of the present invention. The term “information source” used herein is defined as a sequence of symbols that can be interpreted as a message in the most limited technical meaning. And the message is used for organizing and labeling information. For example, the information source includes website (such as internet service), intranet, social network, software, electronic book, database and other media of information (such as storage media of non-transitory computer or storage media of mobile device). The term “original information” used herein is a file, a web page, a database row, a policy, a rule or any data accessible in corresponding machines and servers, but is not limited thereto. The term “original tool” used herein is a utility, a widget, an intelligent agent, an application, a service or any executable component accessible in corresponding machines and servers, but is not limited thereto. It is noted that the information sources, the original information and the original tool are not restricted to the above examples.

Moreover, “original information” and “original tool” are implementation examples of “original matters” used herein. In accordance with the present invention, a plurality of “original matters” from identical or different “information sources” are modeled to a plurality of “unified matters” by a unifying method. Consequently, the “unified matters” in the same execution environment are compatible with each other and cooperate to perform a specified task. The “unified tool” and the “unified information unit” are implementation examples of the “unified matters”. Moreover, the term “Matterizer” used herein is a means, a device or a program code to perform the unifying process.

In an embodiment, the above unifying method comprises steps of: modeling at least one original information obtained from at least one information source of multiple information sources into a unified information unit with one unified data model via re-organizing the original information, and/or modeling at least one original tool obtained from at least one information source of multiple information sources into a unified tool with another unified data model via re-organizing the original tool. The one unified data model and another unified data model could be identical or different, and the unifying method described above could be completed through a matterizer.

Please refer to FIG. 1. FIG. 1 is a schematic diagram illustrating an implementation concept of a unifying method according to an embodiment. As shown in FIG. 1, the matterizer 992 re-organizes an attribute and a link of an original matter 991 with a unified data model 993, and thus models the original matter 991 into a unified matter 994. Consequently, the basic attribute of the unified matter 994 include a type of the original matter 994 and a link indicating where the original matter 994 is located.

In this embodiment, the original matter 991 at least includes an original information (not shown) or an original tool (not shown), but is not limited thereto. In the above unifying method, if the attribute accessible from the original information corresponds to the attribute to be unified in the unified information unit, the unified information unit is directly produced through the matterizer 992. If the attribute accessible from the original information does not correspond to the attribute to be unified in the unified information unit, the original information is firstly re-defined by logically re-organizing the attributes and the link of the original information, and then the original information is converted into a new original information with the attributes which correspond to attributes to be unified in the unified information unit. Consequently, the unified information unit is indirectly produced.

Moreover, if the original tool is compatible with the working environment of the workspace, the unified tool is directly produced by the matterizer 992. On the other hand, if the original tool is incompatible with the working environment of the workspace, the unified tool is indirectly produced via an adapter and/or a software development kit (SDK) of the original tool to drive the original tool. The adapter provides an interface implementation compatible with the working environment.

Herein, “the descriptions of the unifying method”, “the methods of obtaining the unified matters” and “the descriptions of the matterizer” may be referred to the U.S. patent application Ser. No. 14/324,069, entitled “A method of unifying information and tool from a plurality of information sources”, and also referred to the China Patent Application No. 201410768564.X, which claims the benefit of priority to the U.S. patent application Ser. No. 14/324,069 and is entitled “A method of unifying information and tool from a plurality of information sources and computer product and device using the method”. The detailed descriptions thereof are omitted.

The above unifying method is presented herein for purpose of illustration and description only. The method of unifying a plurality of original matters from different information sources is not restricted. However, those skilled in the art will readily observe that numerous modifications and alterations may be made while retaining the teachings of the invention.

Hereinafter, two other unifying methods will be illustrated. The first unifying method is applied to a method of unifying the information of Garmin satellite navigation. Through a point-of-interest (POI) function of the Garmin satellite navigation, the method of unifying the information is employed to unify the imported original point information (i.e., an original information) into the corresponding unified point information (i.e., a unified information unit). The second unifying method is applied to a method of unifying the tool of an Android system. The Android system is a Linux-based open source mobile operating system. However, most application programs (i.e., original tools) are written in the Java programming language. Consequently, the application program (i.e., the original tool) written in the Java programming language can be modelled into a unified application program (i.e., the unified tool) compatible with the Android system so as to be executed in the Android system.

The term “workspace” used herein is a working environment for providing interactions between the at least one matterizer, the at least one tool and/or the at least one information so as to implement a specified task. Moreover, the at least one tool and/or at least one information can be imported into the workspace through the at least one matterizer. However, the way of importing the information and/or tool into the workspace is not restricted. Hereinafter, information importers such as the information importers 9881, 9882 and 9883 of FIG. 2 are some examples of the matterizer. The term “unified script” used herein is an intermediate language to implement the workspace. Moreover, via the “unified script”, the at least one matterizer, the at least one tool and/or the at least one information can be provided to the workspace (e.g., built in or plugged in the workspace).

In an embodiment, the above at least one information is a unified information unit which is produced after at least one original information obtained from at least one information source is unified, and the above at least one tool is a unified tool which is produced after at least one original tool obtained from at least one information source is unified. Moreover, according to different tasks, the required unified information unit and/or the required unified tool from the corresponding information source can be added to the personal workspace (e.g., built in or plugged in the personal workspace). In other words, the “workspace” is a user-orientated “personal workspace”.

Please refer to FIG. 2 and FIG. 3. FIG. 2 is a schematic diagram illustrating an implementation concept of using the unified script as an intermediate language for implementing the personal workspace. FIG. 3 is a schematic diagram illustrating a preferred configuration of a personal workspace. As shown in FIG. 2 and FIG. 3, a unified information unit 985′ corresponding to an original information 985 in Dropbox 982, a first unified tool 986′ corresponding to a compatible original tool 986 in a cloud storage 983 and a second unified tool 987′ corresponding to an incompatible original tool 987 in a server 984 are combined together into a personal workspace 981 according to the required tasks. In particular, a unified script 980 which is regarded as an intermediate language for implementing the personal workspace 981 is firstly compiled, and then an information importer 9881 of the Dropbox 982, an information importer 9882 of the cloud storage 983 and an information importer 9883 of the server 984 are configured through the unified script 980. Moreover, after the original information 985 in the Dropbox 982 is unified into the unified information unit 985′ by the information importer 9881, the unified information unit 985′ is imported into the personal workspace 981.

As shown in FIG. 2 and FIG. 3, the original tool stored in the cloud storage 983 is the compatible original tool 986, which is compatible with the component architecture of the unified tool in the personal workspace 981. Moreover, the first unified tool 986′ corresponding to the compatible original tool 986 is directly provided to the personal workspace 981 through the information importer 9882 of the unified script 980.

As shown in FIG. 2 and FIG. 3, the original tool stored in the server 984 is the incompatible original tool 987, which is incompatible with the component architecture of the unified tool in the personal workspace 981. Moreover, the second unified tool 987′ corresponding to the incompatible original tool 987 is provided to the personal workspace 981 through the compatible adapter 989 and the information importer 9883 of the unified script 980.

As shown in FIG. 3, the user can configure and arrange (e.g., group or place) the unified information unit 985′, the first unified tool 986′ and the second unified tool 987′ in a specific area of the personal workspace 981 according to the practical requirements. Moreover, according to the operational relationship between the unified tool and the unified information unit (e.g., the clicking or dragging actions between the two), the user can perform specified tasks by using the unified tool to access or control the corresponding unified information unit.

Herein, “the descriptions of using the unified script as the intermediate language for implementing the personal workspace” and “the descriptions of allowing the required unified information unit and/or the required unified tool from the corresponding information sources to be arbitrarily combined together into the personal workspace according to the practical requirements” may be referred to the U.S. patent application Ser. No. 14/325,466, entitled “Method for performing task on unified information units in a personal workspace”, and also referred to the China Patent Application No. 201410796528.4, which claims the benefit of priority to the U.S. patent application Ser. Nos. 14/324,069 and 14/325,466 and is entitled “A method of combining unified matters in a personal workspace and computer product and device using the method”. The detailed descriptions thereof are omitted.

The above personal workspace is presented herein for purpose of illustration and description only. It is noted that the workspace used in the present invention is not restricted. For example, the unified script as the intermediate language for implementing the workspace can be previously edited. Consequently, the workspace equips the default matterizer, the default information and/or the default tool. This workspace is not limited to be operated by a single user. According to the practical requirements, this workspace can be operated by multiple users at the same time or at different times.

Moreover, the “workspace” used herein is obtained by “a method of projecting a workspace” to any electronic device with computational capability. Consequently, the “projected workspace” can be operated by any user through any electronic device with computational capability.

In an embodiment, the method of projecting the workspace comprises the following steps. Firstly, a projectable space instance instantiated by the unified script is obtained through a uniform resource identifier (URI). As mentioned above, the unified script is defined to configure at least one of the matterizer, the information and the tool to model the workspace. Moreover, the projectable space instance is used to build the projected workspace corresponding to the workspace, and thus provide an interface for operating at least one of the matterizer, the information and the tool to implement a task. Then, a projector parses the projectable space instance and build a working environment to configure at least one of the matterizer, the information and the tool so as to execute the projected workspace for providing interactions between at least one user and the projected workspace.

The projector is acquired from a remote data station, the projectable space instance or a preloaded application program, and loaded into an engine for providing a compatible environment to execute the projector. An example of the engine includes but is not limited to a Javascript engine, a Windows application or a Linux application. Preferably but not exclusively, the united script can be declared by a document type definition (DTD), an extensible markup language (XML) schema, a structured language or a structured protocol. Preferably but not exclusively, the projectable space instance is an object, an extensible markup language (XML) document, or an instance instantiated with a structured language or a structured protocol.

Please refer to FIG. 4, FIG. 5A, FIG. 5B and FIG. 6. FIG. 4 is a schematic diagram illustrating an initial state of the method of projecting the workspace according to an embodiment of the present invention. FIGS. 5A and 5B are schematic diagrams illustrating operating concepts of the method of projecting the workspace as shown in FIG. 4. FIG. 6 is a schematic diagram illustrating the relationship between a projectable space instance as shown in FIG. 4 and a projected workspace as shown in FIG. 5B.

In the initial state of FIG. 4, a first electronic device 971 and a second electronic device 972 are in communication with each other (e.g., through network connection). Moreover, the first electronic device 971 stores a projectable space instance 973, and the second electronic device 972 has a built-in projector 974.

In this embodiment, the united script 9731 is declared by a document type definition (DTD) and defined to configure at least one information importer (i.e., an example of the matterizer), at least one unified information unit and/or at least one unified tool to model a workspace, and the projectable space instance 973 is an instance instantiated with the extensible markup language (XML). As shown in FIG. 6, the projectable space instance 973 is used for building a projected workspace 976 corresponding to the workspace. Moreover, the information importer, the unified information and/or the unified tool is allowed to be added to or removed from the projectable space instance 973.

The projector 974 of the second electronic device 972 will build a working environment 975 in the second electronic device 972 for executing the projected workspace 976. In addition, the projector 974 provides a microkernel 977 (see FIG. 6) to the working environment 975 for equipping at least one information importer, at least one unified information and/or at least one unified tool that will be added to the projected workspace 976. When the second electronic device 972 acquires the projectable space instance 973 from the first electronic device 971 through a URI, the projector 974 of the second electronic device 972 starts to parse the projectable space instance 973 (see FIG. 5A). After the projectable space instance 973 is parsed by the projector 974, the projected workspace 976 is built in the working environment 975 according to parsed contents of the projectable space instance 973 (see FIG. 5B). Accordingly, a user of the second electronic device 972 can interact with the projected workspace 976 through the second electronic device 972 so as to perform related tasks.

The relationships between the unified script 9731, the projectable space instance 973 and the projected workspace 976 will be illustrated in more detailed through a usage situation as shown in FIG. 6. The usage situation as shown in FIG. 6 is related to a process of building a projected workspace that is capable of accessing jpg format image files and gif format image files from a specified internet space and allowing the image files to be viewed by a user. In this usage situation, the unified script 9731 is declared by the Document Type Definition (DTD), and the projectable space instance 973 is instantiated with XML.

Moreover, an information importer and a unified tool are added into the projectable space instance 973, and at least one unified information unit corresponding to the original information is imported into the projected workspace 976 through the information importer. In this usage situation, the information importer is a Dropbox importer. The information of the Dropbox importer is disclosed in the dashed line frame 9761 of FIG. 6. The original information includes a jpg format image file 9791, a jpg format image file 9792 and a gif format image file 9793 in Dropbox 979 (i.e., an information source). The unified information units include a unified jpg format image file 9791′, a unified jpg format image file 9792′ and a unified gif format image file 9793′, which will be described later. The unified tool is an image viewer for accessing image files which are imported into the projected workspace 976. The information of the image viewer is disclosed in the dashed line frame 9762 of FIG. 6.

As mentioned above, the projected workspace 976 is built after the projectable space instance 973 is parsed by the projector 974 of the second electronic device 972. In this embodiment, the Dropbox importer 9761′ corresponding to the dashed line frame 9761 and the image viewer 9762′ corresponding to the dashed line frame 9762 are configured in the projected workspace 976. Moreover, the jpg format image file 9791, the jpg format image file 9792 and the gif format image file 9793 in Dropbox 979 are unified and imported into the projected workspace 976 by the Dropbox importer 9761′. Consequently, the unified jpg format image file 9791′ corresponding to the jpg format image file 9791, the unified jpg format image file 9792′ corresponding to the jpg format image file 9792 and the unified gif format image file 9793′ corresponding to the gif format image file 9793 are displayed on the projected workspace 976. When the user of the second electronic device 972 manipulates any of the unified image files 9791′, 9792′ and 9793′ by any specified operating means (such as an action of clicking any of the unified images files 9791′, 9792′ and 9793′ or an action of dragging and dropping any of the image files 9791′, 9792′ and 9793′ to the image viewer 9762′), the image viewer 9762′ will access the contents of the corresponding unified image files 9791′, 9792′ or 9793′ to allow the unified image files 9791′, 9792′ or 9793′ to be viewed by the user. Moreover, the Dropbox importer 9761′ and the image viewer 9762′ mentioned above are equipped by the microkernel 977.

It is noted that the URI of the projectable space instance 973 may be a HTTP (hypertext transfer protocol) URI or a FTP (file transfer protocol) URI. In case that the first electronic device 971 and the second electronic device 972 are integrated into one device, the URI of the projectable space instance 973 can also be a local file URI. However, the types of the URI of the projectable space instance 973 are not restricted.

Herein, “the descriptions of the method of projecting the workspace” may be referred to the U.S. patent application Ser. No. 14/577,772, entitled “Method of projecting a workspace and system using the same”, and also referred to the China Patent Application No. 201410814138.5, which claims the benefit of priority to the U.S. patent application Ser. Nos. 14/324,069, 14/325,466 and 14/577,772 and is entitled “Method of projecting a workspace and system using the same”. The detailed descriptions thereof are omitted.

The above method of projecting the workspace to any electronic device with computational capability is presented herein for purpose of illustration and description only. The method of projecting the workspace to any electronic device with computational capability is not restricted. However, those skilled in the art will readily observe that numerous modifications and alterations may be made while retaining the teachings of the invention. Moreover, any workspace can be projected to any electronic device with computational capability. That is, any workspace can be delivered to any electronic device with computational capability.

In the following paragraphs, the “home system” is used to manage the workspace, but is not limited thereto. Moreover, the home system may be set to expansively manage other subsystem, Matterizer, tool or information. Moreover, the home system can be activated in an appropriated platform such as a browser, a Windows platform or an embedded system activated in a physical hardware component.

FIG. 7 is a flowchart illustrating a home system establishing method according to an embodiment of the present invention. The home system establishing method includes the following steps:

Step P1: Provide a workspace in a first server;

Step P2: Connect a user with the workspace;

Step P3: Judge which server complies with the user when the workspace is closed;

Step P4: Establish a home system belonging to the user in a second server that complies with the user; and

Step P5: Connect the user with the home system.

The home system establishing method as depicted in FIG. 7 will be illustrated in more details as follows. Please refer to FIGS. 8-11. FIG. 8 is a schematic diagram illustrating a usage situation applied to a home system establishing method according to an embodiment of the present invention. FIG. 9 is a schematic diagram illustrating a process of connecting the user and the workspace according to an embodiment of the present invention. FIG. 10 is a schematic diagram illustrating the concept of connecting the user to the workspace according to an embodiment of the present invention. FIG. 11 is a schematic diagram illustrating the process of establishing the home system according to an embodiment of the present invention.

Firstly, as shown in FIG. 8 and Step P1, this embodiment is related to the following usage situation. That is, a first user 1 operates a first machine 3, and a second user 2 operates a second machine 4. In addition, a projectable space instance 5 for modelling a workspace is built in a first server 6. Moreover, each of the first machine 3 and the second machine 4 has a projector 7. Preferably but not exclusively, the projector 7 is acquired from a remote data station (not shown), the projectable space instance 5 or a preloaded application program (not shown) in the first machine 3 and the second machine 4.

As mentioned above, the workspace of the present invention can be projected to any electronic device with computational capability. Consequently, the projected workspace corresponding to the workspace can be accessed by any user through any electronic device with computational capability. A method of projecting the workspace will be illustrated as follows.

As shown in FIG. 10, the projectable space instance 5 has the corresponding uniform resource identifier (URI). The first user 1 can load the projectable space instance 5 into the first machine 3 through the URI. After the first machine 3 acquires the projectable space instance 5, the projector 7 starts to parse the projectable space instance 5. After the projectable space instance 5 is parsed by the projector 7, the projected workspace 8 is built in the first machine 3 according to parsed contents of the projectable space instance 5. Consequently, the first user 1 can configure information or tools in the projected workspace 8 according to the practical requirements.

Please refer to FIGS. 9 and 10. If the first user 1 intends to share or cooperatively operate information or tool in the projected workspace 8 with the second user 2, the first user 1 may issue the URI of the projectable space instance 5 to the second user 2 through a platform and/or a channel. Consequently, the second user 2 can load the projectable space instance 5 into the second machine 4 through the URI. Similarly, after the second machine 4 acquires the projectable space instance 5, the projector 7 starts to parse the projectable space instance 5. After the projectable space instance 5 is parsed by the projector 7, the projected workspace 8 is built in the second machine 4 according to parsed contents of the projectable space instance 5. Consequently, the second user 2 connects with the projected workspace 8. The above procedure is depicted in Step P2.

In an embodiment, the platform for transmitting the URI is an operating system or a browser, and the channel for transmitting the URI is an e-mail, an intranet, a social network, a blog, a web site or a chat communication channel. The type of the platform and the type of the channel are presented herein for purpose of illustration and description only. For example, the projected workspace 8 has a preset address book tool (not shown), and the address book tool records an e-mail address of the second user 2. When the first user 1 accesses the address book tool and selects the second user 2, the URI of the projectable space instance 5 is automatically issued to the second user 2. The way of propagating the URI is presented herein for purpose of illustration and description only.

The steps P3, P4 and P5 in the home system establishing method of the present invention will be illustrated with reference to FIG. 11. As mentioned above, even if the second user does not have the home system, the second user 2 can access the projected workspace 8 through the URI of the projectable space instance 5, which is transmitted from the first user 1.

In this embodiment, a workspace closing button B1 is shown on the interface of the projected workspace 8. After the second user 2 taps the workspace closing button B1, the commands associated with a process of automatically establishing a home system for the second user 2 will be executed and described as follows. Firstly, please refer to FIG. 11 and Step P3. After the second user 2 taps the workspace closing button B1, a confirmation command is transmitted from the second machine 4 to an administrative server 9. The administrative server 9 is in communication with the first server 6 and a second server 13 through network connection. Moreover, the administrative server 9 has a database 10. A first server's service scope data 11 and a second server's service scope data 12 are recorded in the database 10. For brevity, only a single second server 13 is shown in this embodiment. In another embodiment, the administrative server 9 is in communication with multiple second servers 13 with different service scope data 12 through network connection. In case that the administrative server 9 is in communication with multiple second servers 13, multiple service scope data 12 are recorded in the database 10 of the administrative server 9.

In this embodiment, the confirmation command contains at least one of the e-mail address, the internet protocol address (IP Address) and the geographical location of the second user 2. Each of the first server's service scope data 11 and the second server's service scope data 12 contains at least one of an e-mail address range (e.g., *@gmail.com), an IP address range (e.g., 131.4.5.*) and a geographical location range (e.g., CN). Consequently, after the administrative server 9 receives the confirmation command, the administrative server 9 judges whether the second user 2 has to establish the home system in the first server 6 or the second server 13. For example, if the confirmation command contains the e-mail address of the second user 2, the first server's service scope data 11 and the second server's service scope data 12 contain different e-mail address ranges. If the e-mail address of the second user 2 does not comply with the first server's service scope data 11 but complies with the second server's service scope data 12, the administrative server 9 judges that the second user 2 has to establish the home system in the second server 13. After the administrative server 9 judges that the second user 2 has to establish the home system in the second server 13, the following steps will be performed.

Please refer to FIG. 11 and Step P4. Then, the administrative server 9 creates a home system space instance 14 in the second server 13 so as to establish a home system 15 of the second user 2. Preferably but not exclusively, the home system space instance 14 is an object, an extensible markup language (XML) document, or an instance instantiated with a structured language or a structured protocol.

The connecting relationships between the second user 2 and at least one of the first server 6, the projected workspace 8, the second server 13 and the home system 15 are stored in the second server 13 or the administrative server 9, or stored in both of the second server 13 or the administrative server 9. For example, the connecting relationships include the domain name of the first server 6, the recognition information of the projected workspace 8, the domain name of the second server 13, the recognition information of the home system 15 and a first identification information of the second user 2 corresponding to the projected workspace 8. For example, after the second user 2 accesses the projected workspace 8, the first identification information of the second user 2 corresponding to the projected workspace 8 is recorded in the projectable space instance 5 or the first server 6. Preferably but not exclusively, the first identification information is a randomly-generated identification code.

After the above steps are completed, the administrative server 9 issues a responding command to the second machine 4. Consequently, as shown in FIG. 11, a home system establishing confirmation button B4 is shown on the interface of the projected workspace 8. Moreover, registration dialog boxes B2 and B3 are further shown on the projected workspace 8. The registration dialog boxes B2 and B3 can provide multiple text options or provide interfaces for allowing the second user 2 to input characters. Preferably but not exclusively, the second user 2 may input an account number into the registration dialog box B2 and input a password into the registration dialog box B3 so as to create an account of the home system 15.

After the second user 2 directly taps the home system establishing confirmation button B4 or input the account number and password to access the home system 15, the home system space instance 14 is loaded into the second machine 4 through the URI of the home system space instance 14 (see FIG. 11). After the second machine 4 acquires the home system space instance 14, the projector 7 starts to parse the home system space instance 14. After the home system space instance 14 is parsed by the projector 7, the home system 15 is built in the second machine 4 according to parsed contents of the home system space instance 14. Consequently, the second user 2 connected with the home system 15 (i.e., Step P5). At the same time, a second identification information of the second user 2 corresponding to the home system 15 is recorded in at least one of the second server 13 and the administrative server 9. In an embodiment, the second identification information includes a randomly-generated identification code. Alternatively, the second identification information includes the account number and password that are set by the second user 2.

As mentioned above, the domain name of the first server 6, the recognition information of the projected workspace 8 and the first identification information of the second user 2 corresponding to the projected workspace 8 have been recorded in at least one of the second server 13 and the administrative server 9. As a consequence, a workspace opening button B5 is shown on the interface of the home system 15. After the second user 2 taps the workspace opening button B5, the URI for directly opening the workspace is obtained according to the calculation and combination about the domain name of the first server 6, the recognition information of the projected workspace 8 and the first identification information of the second user 2 corresponding to the projected workspace 8, which are recorded in at least one of the second server 13 and the administrative server 9. Consequently, an inline frame is generated upon the interface of the home system 15 and the projectable space instance 5 is loaded into the generated inline frame upon the home system 15 through the URI, and the projected workspace 8 is indirectly hosted by the home system 15. Moreover, according to the first identification information of the second user 2 corresponding to the projected workspace 8 indicated in the URI, the identity of the second user 2 to access the workspace is recognized by the projected workspace 8. For example, the domain name of the second server 13 is second.hservice.com, the recognition information of the projected workspace 8 is space0001, and the first identification information of the second user 2 corresponding to the projected workspace 8 is user0001. Consequently, after the calculation and combination are performed, the obtained URI is http://second.hservice.com/#!/space/space0001?user=user0001. In the obtained URI, http://second.hservice.com/#!/space/space0001 is directed to the address for loading the projectable space instance 5, and ?user=user0001 is directed to the identity of the second user 2 corresponding to the workspace.

In this embodiment, the administrative server 9 is an independent server. Alternatively, in another embodiment, the first server 6 or the second server 13 may have the function of acting as the administrative server. The operations are similar to those of the administrative server 9, and are not redundantly described herein.

From the above descriptions, the present invention provides a home system establishing method. An administrative server is used to implement automatic analysis and guide the user to establish a home system in an appropriate server. As previously described about the conventional technology, if the workspace corresponding to the user is stored in a server of a specified domain, the user is possibly impermissible to establish the home system managing the workspace in the server with the workspace. The home system establishing method of the present invention can effectively solve the drawbacks of the conventional technology. Moreover, by recording the connecting relationship between the user and at least one of the server, the workspace and the administrative server, the home system establishing method of the present invention can manage the workspace without the need of account registration. In other words, the present invention is industrially applicable.

While the invention has been described in terms of what is presently considered to be the most practical and preferred embodiments, it is to be understood that the invention needs not be limited to the disclosed embodiments. On the contrary, it is intended to cover various modifications and similar arrangements included within the spirit and scope of the appended claims which are to be accorded with the broadest interpretation so as to encompass all such modifications and similar structures.

	Number	Date	Country
Parent	14324069	Jul 2014	US
Child	15319439		US
Parent	14325466	Jul 2014	US
Child	14324069		US
Parent	14577772	Dec 2014	US
Child	14325466		US

HOME SYSTEM ESTABLISHING METHOD

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

PCT Information

Continuations (3)