NETWORKING COOPERATION METHOD AND MACHINE USING SUCH METHOD

Abstract

A networking cooperation method and a machine using the method are provided. The networking cooperation method includes the following steps. Firstly, plural unified matters are combined together into a projectable space instance for modeling a relational synchronization workspace according to an operational demand. Then, the relational synchronization workspace is projected to multiple cooperators. The projected relational synchronization workspace equips the plural unified matters according to the projectable space instance. When the projected relational synchronization workspace is accessed by at least one cooperator, the at least one cooperator and at least one other cooperator will cooperatively implement a task. Any information, any tool or any service can be arbitrarily combined together into the cooperative working environment by any cooperator according to the practical requirements. Moreover, any cooperator can operate any content of the cooperative working environment.

Description

TECHNICAL FIELD

The present invention relates to a networking cooperation method, and more particularly to a networking cooperation method for cooperatively implementing a task through a relational synchronization workspace and a machine using the method.

BACKGROUND

In today's convenience daily life, people are accustomed to use an electronic device with computational capability to achieve various kinds of applications. For example, these applications include working, file processing, entertainment, social communication, and so on. With development of science and technology, information can be propagated more quickly. Accordingly, various web platforms, operating systems and software tools have been have been developed for people to use, and brought more efficient lives to the users. Especially in the post-PC era, the conventional desktop computers, tablet computers, mobile phones or other mobile devices still make people to implement tasks whenever and wherever they are, and people over the world communicate with each other to transmit and share information through Internet.

Generally, the existing technologies (regardless of hardware or software) are developed in view of personal devices (e.g., computers). That is, a large number of data stations with obvious barriers in the networks become obstruction for many people to cooperatively implement a task. Under this circumstance, the purpose of having no international limitation in network cannot be successfully achieved. In particular, the cooperation method in the real life should comply with the following three conditions: people participation, communication channels, and synchronization of the displayed content. However, if many cooperators are ready to use personal devices (e.g., computers) at different places to cooperatively implement a task through network connection, it is difficult to comply with the above three conditions simultaneously. Especially, it is a challenge to comply with the third condition because of the network security and privacy. If the personal devices (e.g., computers) of all cooperators are connected with the personal device (e.g., a computer) of a specified cooperator to view and operate a specified object (e.g., TeamViewer® remote control software), the network security and privacy are possibly lost.

For solving the above drawbacks, many researches pay much attention to the development of a working environment for cooperatively implementing the task through network connection. For example, Skype® internet instant messaging software provides a medium for communication and discussion because of the following features. Firstly, as long as the Skype® internet instant messaging software is installed in a personal device (e.g., a computer) of a user, the user can be invited as a member of a cooperator list in order to cooperatively implement a task with other cooperators. Secondly, the cooperators can communicate and discuss with each other via messages, audio means or video means. Thirdly, the cooperators can share their own screen images to show the content of the task.

Although the Skype® internet instant messaging software appears to meet the above three conditions of cooperatively implementing the task, there are still some drawbacks in practical applications. Firstly, it is necessary to install the Skype® internet instant messaging software in the personal devices (e.g., computers) of all cooperators in order to cooperatively implement the task. Secondly, any cooperator cannot configure a desired tool (e.g., a video recorder) on the Skype® internet instant messaging software according to the practical requirements. Thirdly, the way of sharing the own screen image to show the working content has some limitations. For example, the working content shared by the sharer can be operated by the sharer only, and the other user can only view the shared working content and make a speech and discuss about the shard working content. In other words, even if the cooperative working content is synchronously shown, only one person has the right to operate the working content. Fourthly, since the display screens of the personal devices (e.g., computers) of all cooperators are not always identical, the screen image shared by the sharer is not sure to be completely shown on the display screens of the receivers. For example, if the display screen of the sharer is much smaller than the display screen of the receiver, the screen image viewed by the receiver is blurred. Fifthly, the approach of sharing the own screen image to show the working content may occupy a lot of the network bandwidth. Under this circumstance, the network performance is deteriorated (e.g., audio delay or video delay).

From the above discussions, the cooperative working environment to cooperatively implement the task should have the following benefits. Firstly, any identity can be invited to join the cooperative working environment to cooperatively implement the task. Secondly, any information, any tool or any service can be arbitrarily combined together into the cooperative working environment by any cooperator according to the practical requirements. Thirdly, any cooperator can access any content of the cooperative working environment, and any cooperator can simultaneously view the change of the cooperative working environment in response to an operation of other cooperator.

SUMMARY

For solving the drawbacks of the conventional technologies, the present invention provides a networking cooperation method and a machine using the method. By the networking cooperation method, any identity can be invited to join the cooperative working environment to cooperatively implement a task. Moreover, any information, any tool or any service can be arbitrarily combined together into the cooperative working environment by any cooperator according to the practical requirements. Moreover, any cooperator can access any content of the cooperative working environment, and any cooperator can simultaneously view the change of the cooperative working environment in response to an operation of other cooperator.

In accordance with an aspect of the present invention, there is provided a networking cooperation method. The networking cooperation method includes the following steps. Firstly, a plurality of unified matters are combined together into a projectable space instance for modeling a relational synchronization workspace according to an operational demand from at least one promoter. Then, the relational synchronization workspace is projected to at least one participant. The projected relational synchronization workspace equips the plurality of unified matters according to the projectable space instance. The at least one participant accesses the projected relational synchronization workspace and cooperatively implement a task with the at least one promoter and/or at least one other participant.

In an embodiment, at least two of the at least one promoter, the at least one participant and the at least one other participant are related with each other according to the operational demand.

In an embodiment, when at least one of the at least one promoter, the at least one participant and the other participant performs at least one operation on the corresponding projected relational synchronization workspace to result in a change of the corresponding projected relational synchronization workspace, the projected relational synchronization workspace corresponding to at least another of the at least one promoter, the at least one participant and the other participant is synchronously changed according to a corresponding synchronization setting.

In an embodiment, when the at least one of the at least one promoter, the at least one participant and the other participant performs the at least one operation on the corresponding projected relational synchronization workspace, a synchronization command is generated; and/or the synchronization command is transmitted to the corresponding projected relational synchronization workspace of the at least another of the at least one promoter, the at least one participant and the other participant through a client-server architecture or a peer-to-peer architecture, so that the projected relational synchronization workspaces of the at least one promoter, the at least one participant and the other participant are synchronously changed.

In an embodiment, the at least one participant includes a machine, and/or the at least one other participant includes another machine.

In an embodiment, an operating mode of the projected relational synchronization workspace includes a one user to one user mode, a one user to multiple user mode or a multiple user to multiple user mode.

In an embodiment, the plurality of unified matters added to the projectable space instance include at least one matterizer, at least one unified tool and/or at least one unified information unit, wherein the at least one unified tool and/or the at least one unified information unit is imported into the corresponding projected relational synchronization workspace through the at least one matterizer.

In an embodiment, each of the unified matters is produced after an original matter from at least one information source is unified by the at least one matterizer, wherein each of the unified matters is added to the projectable space instance.

In an embodiment, at least one original tool corresponding to the at least one unified tool includes a utility, a widget, an agent, an application, a service or any executable element accessible from a corresponding machine or a server, and/or at least one original information corresponding to the at least one unified information unit includes a file, a web page, a database row, a policy, a rule, a policy of the relational synchronization workspace or any information accessible from a corresponding machine or a server.

In an embodiment, the projecting step includes the sub-steps of acquiring the projectable space instance through a uniform resource identifier, and using a projector to parse the projectable space instance to build a working environment, so that the projected relational synchronization workspace is executed in the working environment.

In an embodiment, the projector is loaded into an engine that provides a compatible environment to execute the projector.

In an embodiment, the engine includes at least one of a Javascript engine, a Windows application or a Linux application.

In an embodiment, the projectable space instance is an object, an extensible markup language document, or an instance which is instantiated with a structured language or a structured protocol.

In accordance with another aspect of the present invention, there is provided a networking cooperation method. The networking cooperation method includes the following steps. Firstly, a plurality of unified matters are combined together into a projectable space instance for modeling a relational synchronization workspace according to an operational demand. Then, the relational synchronization workspace is projected to multiple cooperators. The projected relational synchronization workspace equips with the plurality of unified matters according to the projectable space instance. At least one cooperator of the multiple cooperators accesses the projected relational synchronization workspace and cooperatively implement a task with at least one other cooperator of the multiple cooperators.

In an embodiment, at least two of the multiple cooperators are related with each other according to the operational demand.

In an embodiment, when the at least one cooperator of the multiple cooperators performs at least one operation on the corresponding projected relational synchronization workspace to result in a change of the corresponding projected relational synchronization workspace, the projected relational synchronization workspace corresponding to the at least one other cooperator of the multiple cooperators is synchronously changed according to a corresponding synchronization setting.

In an embodiment, when the at least one cooperator of the multiple cooperators performs the at least one operation on the corresponding projected relational synchronization workspace, a synchronization command is generated; and/or the synchronization command is transmitted to the corresponding projected relational synchronization workspace of the at least one other cooperator of the multiple cooperators through a client-server architecture or a peer-to-peer architecture, so that the projected relational synchronization workspaces of the multiple cooperators are synchronously changed.

In an embodiment, each of the multiple cooperators includes a machine.

In an embodiment, an operating mode of the projected relational synchronization workspace includes a one cooperator to one cooperator mode, a one cooperator to multiple cooperator mode or a multiple cooperator to multiple cooperator mode.

In an embodiment, the plurality of unified matters added to the projectable space instance include at least one matterizer, at least one unified tool and/or at least one unified information unit, wherein the at least one unified tool and/or the at least one unified information unit is imported into the corresponding projected relational synchronization workspace through the at least one matterizer.

In an embodiment, each of the unified matters is produced after an original matter from at least one information source is unified by the at least one matterizer, wherein each of the unified matters is added to the projectable space instance.

In an embodiment, the projecting step includes sub-steps of acquiring the projectable space instance through a uniform resource identifier, and using a projector to parse the projectable space instance to build a working environment, so that the projected relational synchronization workspace is executed in the working environment.

In accordance with a further aspect of the present invention, there is provided a machine. The machine includes a projector. After the machine receives a projectable space instance, the projector parses the projectable space instance to build a projected relational synchronization workspace corresponding to the projectable space instance. After the projected relational synchronization workspace equips a plurality of unified matters that are combined in the projectable space instance, the machine and at least one cooperator cooperatively implement a task, or at least one cooperator of multiple cooperators accesses the projected relational synchronization workspace and cooperate with at least one other cooperator of the multiple cooperators to cooperatively implement the task. The plurality of unified matters are combined together into the projectable space instance according to an operational demand.

In an embodiment, each of the multiple cooperators comprises an other machine.

In an embodiment, when the at least one cooperator of the multiple cooperators performs at least one operation on the corresponding projected relational synchronization workspace to result in a change of the corresponding projected relational synchronization workspace, the projected relational synchronization workspace corresponding to the at least one other cooperator of the multiple cooperators is synchronously changed according to a corresponding synchronization setting.

In an embodiment, the projected relational synchronization workspace corresponding to the at least one other cooperator of the multiple cooperators is built in at least one other machine.

In an embodiment, at least two of the multiple cooperators are related with each other according to the operational demand.

In an embodiment, the plurality of unified matters added to the projectable space instance include at least one matterizer, at least one unified tool and/or at least one unified information unit, wherein the at least one unified tool and/or the at least one unified information unit is imported into the corresponding projected relational synchronization workspace through the at least one matterizer.

In an embodiment, each of the unified matters is produced after an original matter from at least one information source is unified by the at least one matterizer, wherein each of the unified matters is added to the projectable space instance.

In an embodiment, at least one original tool corresponding to the at least one unified tool includes a utility, a widget, an agent, an application, a service or any executable element accessible from a corresponding machine or a server, and/or at least one original information corresponding to the at least one unified information unit includes a file, a web page, a database row, a policy, a rule, a policy of the projected relational synchronization workspace, or any information accessible from a corresponding machine or a server.

From the above descriptions, the networking cooperation method of the present invention has the following benefits. Since the participants for participating in the networking cooperation method can receive the URI through the corresponding platforms and/or channels and build the cooperative working environments (i.e., the projected relational synchronization workspaces), any identity (including any person or any machine) can be invited to cooperatively implement the task without the need of additionally installing an application software or an application program in the personal device (e.g., a computer). Secondly, since the working environment for allowing these cooperators to cooperatively implement the task can be unified into a unified environment by the unifying process, any information, any tool or any service can be arbitrarily combined together and compatible with each other according to the operational demand of any cooperator. Thirdly, any information, any tool or any service in the cooperative working environment (i.e., the projected relational synchronization workspace) can be operated by any cooperator. Moreover, since the cooperative working environments (i.e., the projected relational synchronization workspaces) for allowing these cooperators to cooperatively implement the task are projected to and executed in the personal devices (e.g., computers) of all cooperators, any cooperate can synchronously view the change of the cooperative working environment in response to an operation of other cooperator. Fourthly, in comparison with the conventional cooperation method of sharing the screen image, the networking cooperation method of the present invention allows the synchronization command to be transferred between the projected relational synchronization workspaces in order to achieve the synchronizing efficacy. Since the networking cooperation method of the present invention only transmits the synchronization command instead of transmitting the data of the whole screen, the bandwidth usage is largely reduced and the network performance is effectively enhanced.

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 networking cooperation method according to an embodiment of the present invention;

FIG. 8 is a schematic diagram illustrating a usage situation of the networking cooperation method according to an embodiment of the present invention;

FIG. 9 is a schematic diagram illustrating a process of inviting a first participant and a second participant by a promoter;

FIG. 10 is a schematic diagram illustrating the operating concepts of the networking cooperation method applied to the usage situation of FIG. 8;

FIG. 11 is a schematic diagram illustrating the relationship between a projectable space instance and a projected relational synchronization workspace according to an embodiment of the present invention;

FIG. 12A is a schematic diagram illustrating the interaction between the first participant and the projected relational synchronization workspace of the first machine of FIG. 10 in an initial state of the networking cooperation method;

FIG. 12B is a schematic diagram illustrating the interaction between the second participant and the projected relational synchronization workspace of the second machine of FIG. 10 in an initial state of the networking cooperation method;

FIG. 12C is a schematic diagram illustrating the interaction between the promoter and the projected relational synchronization workspace of the third machine of FIG. 10 in an initial state of the networking cooperation method;

FIG. 13A is a schematic diagram illustrating the interaction between the first participant and the projected relational synchronization workspace of the first machine of FIG. 10 after a first presentation material is added to a blank presentation and edited;

FIG. 13B is a schematic diagram illustrating the interaction between the second participant and the projected relational synchronization workspace of the second machine of FIG. 10 after the first presentation material is added to the blank presentation and edited by the first participant;

FIG. 13C is a schematic diagram illustrating the interaction between the promoter and the projected relational synchronization workspace of the third machine of FIG. 10 after the first presentation material is added to the blank presentation and edited by the first participant;

FIG. 14A is a schematic diagram illustrating the interaction between the first participant and the projected relational synchronization workspace of the first machine of FIG. 10 after a second presentation material is added to the presentation with the first unified presentation material and edited by the second participant;

FIG. 14B is a schematic diagram illustrating the interaction between the second participant and the projected relational synchronization workspace of the second machine of FIG. 10 after the second presentation material is added to the presentation with the first unified presentation material and edited by the second participant;

FIG. 14C is a schematic diagram illustrating the interaction between the promoter and the projected relational synchronization workspace of the third machine of FIG. 10 after the second presentation material is added to the presentation with the first unified presentation material and edited by the second participant;

FIG. 15 is a schematic diagram illustrating the use of the client-server architecture to synchronize the projected relational synchronization workspaces in different machines;

FIG. 16 is a schematic diagram illustrating the use of the peer-to-peer architecture to synchronize the projected relational synchronization workspaces in different machines; and

FIG. 17 is a schematic diagram illustrating a usage situation of a networking cooperation method according to another 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, the Dropbox importer 9761′ of FIG. 6 and the information importers 52 of FIGS. 11, 12A˜12C, FIGS. 13A˜13C and FIGS. 14A˜14C 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 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. 201410768564.X, 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 has 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. An example of the electronic device includes but is not limited to a mobile phone, a tablet computer, a notebook computer or a desktop computer. 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 includes 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. Consequently, the workspace is also a working platform for allowing multiple cooperators to cooperatively implement the task. That is, the workspace is a “relational synchronization workspace”. The present invention provides a networking cooperation method on network and a machine using the networking cooperation method, which will be illustrated in more details as follows.

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

Step P1: Combine a plurality of unified matters together into a projectable space instance for modeling a relational synchronization workspace according to an operational demand from at least one promoter; and

Step P2: Project the relational synchronization workspace to at least one participant, wherein the projected relational synchronization workspace equips the plurality of unified matters according to the projectable space instance, wherein the at least one participant accesses the projected relational synchronization workspace to cooperatively implement a task with the at least one promoter and/or at least one other participant.

Please refer to FIGS. 8˜11. FIG. 8 is a schematic diagram illustrating a usage situation of the networking cooperation method according to an embodiment of the present invention. FIG. 9 is a schematic diagram illustrating a process of inviting a first participant and a second participant by a promoter. FIG. 10 is a schematic diagram illustrating the operating concepts of the networking cooperation method applied to the usage situation of FIG. 8. FIG. 11 is a schematic diagram illustrating the relationship between a projectable space instance and a projected relational synchronization workspace according to an embodiment of the present invention.

This embodiment is related to the following usage situation. That is, a promotor 23 intends to invite a first participant 21 and a second participant 22 to cooperatively make a topical presentation. Hereinafter, the promotor 23, the first participant 21 and the second participant 22 are collaboratively referred as cooperators 2. According to an operational demand of “making a topical presentation”, these cooperators 2 are related with each other. Before the networking cooperation method starts, the promotor 23 installs a projectable space instance 3 in a fourth machine 14. The projectable space instance 3 is used for modeling a relational synchronization workspace. According to the operational demand of making the topical presentation and a required communication means for cooperation, the required unified matters 5 are combined together into the projectable space instance 3 by the promotor 23. In this embodiment, the unified tools 51 added to the projectable space instance 3 include a presentation reader 511, a presentation editor 512, a video caller 513 and a recorder 514.

In this embodiment, as shown in FIG. 11, the projectable space instance 3 is an instance instantiated with the extensible markup language (XML). FIG. 11 also shows the compiled contents of the projectable space instance 3 and the relationships between the compiled contents of the projectable space instance 3 and the unified matters 5 of a projected relational synchronization workspace 6. In FIG. 11, the both ends of each dotted line denote the compiled contents of the projectable space instance 3 and the corresponding unified matters 5 in the relationship.

Moreover, in the usage situation of FIG. 8, a first machine 11, a second machine 12 and a third machine 13 are operated by the first participant 21, the second participant 22 and the promotor 23, respectively. Moreover, each of the first machine 11, the second machine 12 and the third machine 13 has a projector 4. Preferably but not exclusively, the projector 4 is at least acquired from a remote station (not shown), the projectable space instance 3 in the fourth machine 14 or a preloaded application program (not shown) in the first machine 11, the second machine 12 and the third machine 13.

In this embodiment, the first machine 11, the second machine 12 and the third machine 13 are connected with the fourth machine 14 directly or indirectly (e.g., through network connection as indicated by dotted lines as shown in FIG. 10). Consequently, the projectable space instance 3 can be transmitted from the fourth machine 14 to the first machine 11, the second machine 12 and the third machine 13. In addition, any original matter (e.g., the first presentation material or tool in the first machine 11, the second presentation material or tool in the second machine 12, the third presentation material or tool in the third machine 13 and the data or executable element accessible from a corresponding machine or a server) can be provided to the fourth machine 14 after being unified.

Please refer to the step P2 of FIG. 7 and FIG. 9. The projectable space instance 3 has the corresponding uniform resource identifier (URI). When the promotor 23 intends to invite multiple participants to cooperatively make a topical presentation 5, the promoter 23 issues the URI of the projectable space instance 3 to the first participant 21 and the second participant 22 through a platform and/or a channel. Consequently, the first participant 21 and the second participant 22 can load the projectable space instance 3 into the first machine 11 and the second machine 12 through the URI. Similarly, through the URI, the promoter 23 can load the projectable space instance 3 into the third machine 13 which is operated by the promoter 23. For example, 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.

Please refer to the step P2 of FIG. 7 and FIG. 10. The projectors 4 in the first machine 11, the second machine 12 and the third machine 13 build the working environments 41 in the first machine 11, the second machine 12 and the third machine 13. Consequently, the projected relational synchronization workspaces 6A, 6B and 6C are executed in the working environments 41. In addition, the projectors 4 provide microkernels 61 corresponding to the projected relational synchronization workspaces 6A, 6B and 6C (see FIGS. 12A˜12C, FIGS. 13A˜13C and FIGS. 14A˜14C) in order for equipping unified matters 5 that are compiled in the projectable space instance 3. For example, the unified matters 5 include unified tools 51 and information importers 52. After the first machine 11, the second machine 12 and the third machine 13 acquire the projectable space instance 3 from the fourth machine 14 through the URI, the projectors 4 start to parse the projectable space instance 3. After the projectable space instance 3 is parsed by the projectors 4, the projected relational synchronization workspaces 6A, 6B and 6C are built in the working environment according to parsed contents of the projectable space instance 3. Consequently, the first participant 21 of the first machine 11, the second participant 22 of the second machine 12 and the promotor of the third machine 13 can interact with the projected relational synchronization workspaces 6A, 6B and 6C through the first machine 11, the second machine 12 and the third machine 13, respectively. That is, these cooperators 2 can operate the corresponding projected relational synchronization workspaces 6A, 6B and 6C so as to cooperatively implement a specified task.

Hereinafter, a process of cooperatively implementing a task by these cooperators 2 according to the networking cooperation method of the present invention will be illustrated with reference to FIGS. 12A˜12C, FIGS. 13A˜13C and FIGS. 14A˜14C.

FIG. 12A is a schematic diagram illustrating the interaction between the first participant and the projected relational synchronization workspace of the first machine of FIG. 10 in an initial state of the networking cooperation method. FIG. 12B is a schematic diagram illustrating the interaction between the second participant and the projected relational synchronization workspace of the second machine of FIG. 10 in an initial state of the networking cooperation method. FIG. 12C is a schematic diagram illustrating the interaction between the promoter and the projected relational synchronization workspace of the third machine of FIG. 10 in an initial state of the networking cooperation method. FIG. 13A is a schematic diagram illustrating the interaction between the first participant and the projected relational synchronization workspace of the first machine of FIG. 10 after a first presentation material is added to a blank presentation and edited. FIG. 13B is a schematic diagram illustrating the interaction between the second participant and the projected relational synchronization workspace of the second machine of FIG. 10 after the first presentation material is added to the blank presentation and edited by the first participant. FIG. 13C is a schematic diagram illustrating the interaction between the promoter and the projected relational synchronization workspace of the third machine of FIG. 10 after the first presentation material is added to the blank presentation and edited by the first participant. FIG. 14A is a schematic diagram illustrating the interaction between the first participant and the projected relational synchronization workspace of the first machine of FIG. 10 after a second presentation material is added to the presentation with the first unified presentation material and edited by the second participant. FIG. 14B is a schematic diagram illustrating the interaction between the second participant and the projected relational synchronization workspace of the second machine of FIG. 10 after the second presentation material is added to the presentation with the first unified presentation material and edited by the second participant. FIG. 14C is a schematic diagram illustrating the interaction between the promoter and the projected relational synchronization workspace of the third machine of FIG. 10 after the second presentation material is added to the presentation with the first unified presentation material and edited by the second participant.

Please refer to FIGS. 12A˜12C. In the initial state of the usage situation, the projected relational synchronization workspaces 6A, 6B and 6C are built in the first machine 11, the second machine 12 and the third machine 13, respectively. A blank presentation 53 is firstly unified, and then imported into the projected relational synchronization workspaces 6A, 6B and 6C through the information importers 52. Moreover, the blank presentation 53 is shown to be viewed by the first participant 21, the second participant 22 and the promotor 23 through the presentation readers 511. FIG. 12A shows the projected relational synchronization workspace 6A built in the first machine 11 in the initial state. FIG. 12A also shows the presentation reader 511, the presentation editor 512 and the video caller 513 in addition to the blank presentation 53. The photo images of the second participant 22 and the promoter 23 are shown on the video caller 513 for facilitating the first participant 21 to communicate and discuss with the second participant 22 and the promoter 23. By operating the presentation editor 512, the first participant 21 can edit the presentation 53 shown on the projected relational synchronization workspace 6A. By operating the recorder 514, the first participant 21 can record the cooperating process of these cooperators 2. The recorded contents include image information, sound information, and so on. Moreover, the recorded contents can be stored in a specified storage area. Moreover, as shown in FIG. 12A, the first participant 21 is ready to add a first presentation material 54 to the blank presentation 53 and edit the blank presentation 53 through the presentation editor 512 while these cooperators 2 communicate and discuss with each other.

Similarly, FIG. 12B shows the projected relational synchronization workspace 6B built in the second machine 12 in the initial state. FIG. 12B also shows the presentation reader 511, the presentation editor 512 and the video caller 513 in addition to the blank presentation 53. The photo images of the first participant 21 and the promoter 23 are shown on the video caller 513 for facilitating the second participant 22 to communicate and discuss with the first participant 21 and the promoter 23. By operating the presentation editor 512, the second participant 22 can edit the presentation 53 shown on the projected relational synchronization workspace 6B. By operating the recorder 514, the second participant 22 can record the cooperating process of these cooperators 2. The recorded contents include image information, sound information, and so on. Moreover, the recorded contents can be stored in a specified storage area.

Similarly, FIG. 12C shows the projected relational synchronization workspace 6C built in the third machine 13 in the initial state. FIG. 12C also shows the presentation reader 511, the presentation editor 512 and the video caller 513 in addition to the blank presentation 53. The photo images of the first participant 21 and the second participant 22 are shown on the video caller 513 for facilitating the promoter 23 to communicate and discuss with the first participant 21 and the second participant 22. By operating the presentation editor 512, the promoter 23 can edit the presentation 53 shown on the projected relational synchronization workspace 6C. By operating the recorder 514, the promoter 23 can record the cooperating process of these cooperators 2. The recorded contents include image information, sound information, and so on. Moreover, the recorded contents can be stored in a specified storage area.

After the first participant 21 adds the first presentation material 54 to the blank presentation 53 and edit the blank presentation 53, the contents of the projected relational synchronization workspaces 6A, 6B and 6C are shown in FIGS. 13A˜13C. When the first participant 21 adds the first presentation material 54 to the blank presentation 53 (e.g., by dragging the first presentation material 54 to the blank presentation 53), the first presentation material 54 is unified into a first unified presentation material 54′ through the information importer 52. From the drawings, it is found that the presentations 53 in the projected relational synchronization workspaces 6B and 6C are synchronously changed when the presentation 53 in the projected relational synchronization workspace 6A is changed in response to the operation of the first participant 21. In other words, the presentation 53 in each of the projected relational synchronization workspaces 6A, 6B and 6C contains the first unified presentation material 54′ and the edited result of the first participant 21.

As shown in FIG. 13B, while these cooperators 2 communicate and discuss with each other, the second participant 22 is ready to add a second presentation material 55 to the presentation 53, which contains the first unified presentation material 54′ and has been edited by the first participant 21. Moreover, through the presentation editor 512 of the projected relational synchronization workspace 6B, the presentation 53 with the first unified presentation material 54′ can be edited by the second participant 22.

After the second participant 22 adds the second presentation material 55 to the presentation 53 and edit the blank presentation 53, the contents of the projected relational synchronization workspaces 6A, 6B and 6C are shown in FIGS. 14A˜14C. When the second participant 22 adds the second presentation material 55 to the blank presentation 53 (e.g., by dragging the second presentation material 55 to the blank presentation 53), the second presentation material 55 is unified into a second unified presentation material 55′ through the information importer 52. From the drawings, it is found that the presentations 53 in the projected relational synchronization workspaces 6A and 6C are synchronously changed when the presentation 53 in the projected relational synchronization workspace 6B is changed in response to the operation of the second participant 22. In other words, the presentation 53 in each of the projected relational synchronization workspaces 6A, 6B and 6C contains the first unified presentation material 54′, the second unified presentation material 55′ and the edited results of the first participant 21 and the second participant 22.

As mentioned above, when any cooperator operates the corresponding projected relational synchronization workspace and results in a change of the corresponding projected relational synchronization workspace, the projected relational synchronization workspaces corresponding to the other cooperators are synchronously changed. For achieving the above purpose, the present invention further provides the following synchronization process. When the projected relational synchronization workspace in any machine is accessed, a corresponding synchronization command is generated. In addition, the synchronization command is transmitted to the projected relational synchronization workspaces of the other machines. According to the synchronization command, these projected relational synchronization workspaces are synchronously changed. The synchronization process may be implemented with client-server architecture, peer-to-peer architecture or the like.

FIG. 15 is a schematic diagram illustrating the use of the client-server architecture to synchronize the projected relational synchronization workspaces in different machines. In the client-server architecture, all of the first machine 11, the second machine 12 and the third machine 13 are connected with a server 8. The synchronization command from any of the first machine 11, the second machine 12 and the third machine 13 can be transmitted to the other two of the first machine 11, the second machine 12 and the third machine 13 through the server 8.

As shown in FIG. 15, the projected relational synchronization workspace 6A in the first machine 11 issues a synchronization command D1 in response to an operation of the first participant 21. After the synchronization command D1 is received by the server 8, the synchronization command D1 is transmitted to the projected relational synchronization workspace 6B in the second machine 12 and the projected relational synchronization workspace 6C in the third machine 13. Consequently, the contents of the projected relational synchronization workspaces 6A, 6B and 6C are synchronized in response to the operation of the first participant 21. Similarly, when the second participant 22 of the second machine 12 accesses the corresponding projected relational synchronization workspace 6B or when the promoter 23 of the third machine 13 accesses the corresponding projected relational synchronization workspace 6C, the synchronization process is also implemented.

FIG. 16 is a schematic diagram illustrating the use of the peer-to-peer architecture to synchronize the projected relational synchronization workspaces in different machines. In the peer-to-peer architecture, all of the first machine 11, the second machine 12 and the third machine 13 can realize the network locations of other machines through the fourth machine 14. Consequently, the first machine 11, the second machine 12 and the third machine 13 are in communication with each other through network connection. Meanwhile, the synchronization command from any of the first machine 11, the second machine 12 and the third machine 13 can be transmitted to the other two of the first machine 11, the second machine 12 and the third machine 13 directly.

As shown in FIG. 16, the projected relational synchronization workspace 6B in the second machine 12 issues a synchronization command D2 in response to an operation of the second participant 22. Consequently, the synchronization command D2 is directly transmitted to the projected relational synchronization workspace 6A in the first machine 11 and the projected relational synchronization workspace 6C in the third machine 13. Consequently, the contents of the projected relational synchronization workspaces 6A, 6B and 6C are synchronized in response to the operation of the second participant 22. Similarly, when the first participant 21 of the first machine 11 accesses the corresponding projected relational synchronization workspace 6A or when the promoter 23 of the third machine 13 accesses the corresponding projected relational synchronization workspace 6C, the synchronization process is also implemented.

The synchronization process and the architecture for implementing the synchronization process are presented herein for purpose of illustration and description only. However, those skilled in the art will readily observe that numerous modifications and alterations may be made while retaining the teachings of the invention.

Preferably but not exclusively, a synchronization setting about the change of the corresponding projected relational synchronization workspace in response to any operation may be determined by any cooperator 2 according to the practical requirements. For example, during the cooperating process, the first participant 21 may remark relevant attentive items (not shown) or make notes (not shown) on the projected relational synchronization workspace 6A. If the first participant 21 sets that the attentive items or notes are not synchronized, the attentive items or notes will not be displayed on the projected relational synchronization workspace 6B of the second participant 22 and the projected relational synchronization workspace 6C of the promoter 23. For example, during the cooperating process, the promoter 23 may configure a toolbar (not shown) containing a plurality of unified tools (not shown) in the projected relational synchronization workspace 6C so as to facilitate operation. If the promoter 23 intends to share the toolbar with the second participant 22 only, the promoter 23 may set the synchronization of the toolbar. Consequently, the toolbar is only synchronously shown on the projected relational synchronization workspace 6B of the second participant 22.

Moreover, while these cooperators 2 communicate and discuss with each other, any of these cooperators 2 may invite other participants to cooperatively implement the task. For example, if the second participant 22 meets with obstruction while making a topical presentation, the second participant 22 may invite another participant (e.g., a third participant, not shown) to ask for help. Under this circumstance, the URI of the projectable space instance 3 can be transmitted to the third participant through the platform and/or channel which is frequently used by the third participant. Consequently, the third participant can load the projectable space instance 3 into the own machine through the URI. After the projected relational synchronization workspace is built, the third participant can cooperatively implement the task with the promoter 23, the first participant 21 and the second participant 22. Moreover, while these cooperators 2 communicate and discuss with each other, any of these cooperators 2 can provide another unified matter 5 (e.g., a photo edit tool, not shown) to the projected relational synchronization workspaces 6A, 6B and 6C at any time according to the practical requirements.

The operating mode of the networking cooperation method includes a one cooperator to one cooperator mode, a one cooperator to multiple cooperator mode (e.g., a broadcasting method), or a multiple cooperator to multiple cooperator mode. Alternatively, in some other embodiments, these cooperators are machines. Furthermore, another usage situation of the networking cooperation method will be illustrated as follows.

FIG. 17 is a schematic diagram illustrating a usage situation of a networking cooperation method according to another embodiment of the present invention. The embodiment is related to the following usage situation. That is, a cable TV setting staff 74 intends to set a first internet TV box 71, a second internet TV box 72 and a third internet TV box 73 at different families in order to cooperatively implement a network playing task. The first internet TV box 71, the second internet TV box 72 and the third internet TV box 73 have corresponding projectors 4′. After the projectors 4′ receive the projectable space instance 3′ through the URI, the projectors 4′ automatically parse the projectable space instance 3′. Consequently, a working environment 41′ is built to execute the projected relational synchronization workspaces 6A′, 6B′ and 6C′. In this embodiment, the cable TV setting staff 74 is a promoter, and the first internet TV box 71, the second internet TV box 72 and the third internet TV box 73 are participants. Moreover, the cable TV setting staff 74 is related with the first internet TV box 71, the second internet TV box 72 and the third internet TV box 73 according to an operational demand of cooperatively implementing a network playing task. Before the networking cooperation method starts, the cable TV setting staff 74 installs the projectable space instance 3′ in a fourth machine 14. The projectable space instance 3′ is used for modeling a relational synchronization workspace. Moreover, according to the operational demand of cooperatively implementing a network playing task, a video play tool (not shown) and a video playlist (not shown) are combined together into the projectable space instance 3′ by the cable TV setting staff 74. Meanwhile, the projected relational synchronization workspaces 6A′, 6B′ and 6C′ are configured in the working environments 41′ of the first internet TV box 71, the second internet TV box 72 and the third internet TV box 73. After the networking cooperation method starts, the first internet TV box 71, the second internet TV box 72 and the third internet TV box 73 can play the video programs according to a video playlist, which is set by the cable TV setting staff 74. Consequently, the purpose of cooperatively implementing the network playing task will be achieved.

From the above descriptions, the networking cooperation method of the present invention has the following benefits. Since the participants for participating in the networking cooperation method can receive the URI through the corresponding platforms and/or channels and build the cooperative working environments (i.e., the projected relational synchronization workspaces), any identity (including any person or any machine) can be invited to cooperatively implement the task without the need of additionally installing an application software or an application program in the personal device (e.g., a computer). Secondly, since the working environment for allowing these cooperators to cooperatively implement the task can be unified into a unified environment by the unifying process, any information, any tool or any service can be arbitrarily combined together and compatible with each other according to the operational demand of any cooperator. Thirdly, any information, any tool or any service in the cooperative working environment (i.e., the projected relational synchronization workspace) can be operated by any cooperator. Moreover, since the cooperative working environments (i.e., the projected relational synchronization workspaces) for allowing these cooperators to cooperatively implement the task are projected to and executed in the personal devices (e.g., computers) of all cooperators, any cooperate can synchronously view the change of the cooperative working environment in response to an operation of other cooperator. Fourthly, in comparison with the conventional cooperation method of sharing the screen image, the networking cooperation method of the present invention allows the synchronization command to be transferred between the projected relational synchronization workspaces in order to achieve the synchronizing efficacy. Since the networking cooperation method of the present invention only transmits the synchronization command instead of transmitting the data of the whole screen, the bandwidth usage is largely reduced and the network performance is effectively enhanced.

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.

Claims

1. A networking cooperation method, comprising steps of: combining a plurality of unified matters together into a projectable space instance for modeling a relational synchronization workspace according to an operational demand from at least one promoter; andprojecting the relational synchronization workspace to at least one participant, wherein the projected relational synchronization workspace equips the plurality of unified matters according to the projectable space instance, wherein the at least one participant accesses the projected relational synchronization workspace to cooperatively implement a task with the at least one promoter and/or at least one other participant.

2. The networking cooperation method according to claim 1, wherein at least two of the at least one promoter, the at least one participant and the at least one other participant are related with each other according to the operational demand.

3. The networking cooperation method according to claim 1, wherein when at least one of the at least one promoter, the at least one participant and the other participant performs at least one operation on the corresponding projected relational synchronization workspace to result in a change of the corresponding projected relational synchronization workspace, the projected relational synchronization workspace corresponding to at least another of the at least one promoter, the at least one participant and the other participant is synchronously changed according to a corresponding synchronization setting.

4. The networking cooperation method according to claim 3, wherein when the at least one of the at least one promoter, the at least one participant and the other participant performs the at least one operation on the corresponding projected relational synchronization workspace, a synchronization command is generated; and/or the synchronization command is transmitted to the corresponding projected relational synchronization workspace of the at least another of the at least one promoter, the at least one participant and the other participant through a client-server architecture or a peer-to-peer architecture, so that the projected relational synchronization workspaces of the at least one promoter, the at least one participant and the other participant are synchronously changed.

5. The networking cooperation method according to claim 1, wherein the at least one participant includes a machine, and/or the at least one other participant includes another machine.

6. The networking cooperation method according to claim 1, wherein an operating mode of the projected relational synchronization workspace includes a one user to one user mode, a one user to multiple user mode or a multiple user to multiple user mode.

7. The networking cooperation method according to claim 1, wherein the plurality of unified matters added to the projectable space instance include at least one matterizer, at least one unified tool and/or at least one unified information unit, wherein the at least one unified tool and/or the at least one unified information unit is imported into the corresponding projected relational synchronization workspace through the at least one matterizer.

8. The networking cooperation method according to claim 7, wherein each of the unified matters is produced after an original matter from at least one information source is unified by the at least one matterizer, wherein each of the unified matters is added to the projectable space instance.

9. The networking cooperation method according to claim 8, wherein at least one original tool corresponding to the at least one unified tool includes a utility, a widget, an agent, an application, a service or any executable element accessible from a corresponding machine or a server, and/or at least one original information corresponding to the at least one unified information unit includes a file, a web page, a database row, a policy, a rule, a policy of the relational synchronization workspace, or any information accessible from a corresponding machine or a server.

10. The networking cooperation method according to claim 1, wherein the projecting step comprises sub-steps of: acquiring the projectable space instance through a uniform resource identifier; andusing a projector to parse the projectable space instance to build a working environment, so that the projected relational synchronization workspace is executed in the working environment.

11. The networking cooperation method according to claim 10, wherein the projector is loaded into an engine that provides a compatible environment to execute the projector.

12. The networking cooperation method according to claim 10, wherein the engine includes at least one of a Javascript engine, a Windows application or a Linux application.

13. The networking cooperation method according to claim 1, wherein the projectable space instance is an object, an extensible markup language document, or an instance which is instantiated with a structured language or a structured protocol.

14. A networking cooperation method, comprising steps of: combining a plurality of unified matters together into a projectable space instance for modeling a relational synchronization workspace according to an operational demand; andprojecting the relational synchronization workspace to multiple cooperators, wherein the projected relational synchronization workspace equips with the plurality of unified matters according to the projectable space instance, wherein at least one cooperator of the multiple cooperators accesses the projected relational synchronization workspace to cooperatively implement a task with at least one other cooperator of the multiple cooperators.

15. The networking cooperation method according to claim 14, wherein at least two of the multiple cooperators are related with each other according to the operational demand.

16. The networking cooperation method according to claim 14, wherein when the at least one cooperator of the multiple cooperators performs at least one operation on the corresponding projected relational synchronization workspace to result in a change of the corresponding projected relational synchronization workspace, the projected relational synchronization workspace corresponding to the at least one other cooperator of the multiple cooperators is synchronously changed according to a corresponding synchronization setting.

17. The networking cooperation method according to claim 16, wherein when the at least one cooperator of the multiple cooperators performs the at least one operation on the corresponding projected relational synchronization workspace, a synchronization command is generated; and/or the synchronization command is transmitted to the corresponding projected relational synchronization workspace of the at least one other cooperator of the multiple cooperators through a client-server architecture or a peer-to-peer architecture, so that the projected relational synchronization workspaces of the multiple cooperators are synchronously changed.

18. The networking cooperation method according to claim 14, wherein each of the multiple cooperators includes a machine.

19. The networking cooperation method according to claim 14, wherein an operating mode of the projected relational synchronization workspace includes a one cooperator to one cooperator mode, a one cooperator to multiple cooperator mode or a multiple cooperator to multiple cooperator mode.

20. The networking cooperation method according to claim 14, wherein the plurality of unified matters added to the projectable space instance include at least one matterizer, at least one unified tool and/or at least one unified information unit, wherein the at least one unified tool and/or the at least one unified information unit is imported into the corresponding projected relational synchronization workspace through the at least one matterizer.

21. The networking cooperation method according to claim 20, wherein each of the unified matters is produced after an original matter from at least one information source is unified by the at least one matterizer, wherein each of the unified matters is added to the projectable space instance.

22. The networking cooperation method according to claim 14, wherein the projecting step comprises sub-steps of: acquiring the projectable space instance through a uniform resource identifier; andusing a projector to parse the projectable space instance to build a working environment, so that the projected relational synchronization workspace is executed in the working environment.

23. A machine comprising a projector, wherein after the machine receives a projectable space instance, the projector parses the projectable space instance to build a projected relational synchronization workspace corresponding to the projectable space instance, wherein after the projected relational synchronization workspace equips a plurality of unified matters that are combined in the projectable space instance, the machine and at least one cooperator cooperatively implement a task, or at least one cooperator of multiple cooperators accesses the projected relational synchronization workspace and cooperate with at least one other cooperator of the multiple cooperators to cooperatively implement the task, wherein the plurality of unified matters are combined together into the projectable space instance according to an operational demand.

24. The machine according to claim 23, wherein each of the multiple cooperators comprises an other machine.

25. The machine according to claim 23, wherein when the at least one cooperator of the multiple cooperators performs at least one operation on the corresponding projected relational synchronization workspace to result in a change of the corresponding projected relational synchronization workspace, the projected relational synchronization workspace corresponding to the at least one other cooperator of the multiple cooperators is synchronously changed according to a corresponding synchronization setting.

26. The machine according to claim 23, wherein the projected relational synchronization workspace corresponding to the at least one other cooperator of the multiple cooperators is built in at least one other machine.

27. The machine according to claim 23, wherein at least two of the multiple cooperators are related with each other according to the operational demand.

28. The machine according to claim 23, wherein the plurality of unified matters added to the projectable space instance include at least one matterizer, at least one unified tool and/or at least one unified information unit, wherein the at least one unified tool and/or the at least one unified information unit is imported into the corresponding projected relational synchronization workspace through the at least one matterizer.

29. The machine according to claim 28, wherein each of the unified matters is produced after an original matter from at least one information source is unified by the at least one matterizer, wherein each of the unified matters is added to the projectable space instance.

30. The machine according to claim 29, wherein at least one original tool corresponding to the at least one unified tool includes a utility, a widget, an agent, an application, a service or any executable element accessible from a corresponding machine or a server, and/or at least one original information corresponding to the at least one unified information unit includes a file, a web page, a database row, a policy, a rule, a policy of the projected relational synchronization workspace, or any information accessible from a corresponding machine or a server.