WO2016000638A1 - Networking cooperation method and machine using such method - Google Patents

Networking cooperation method and machine using such method Download PDF

Info

Publication number
WO2016000638A1
WO2016000638A1 PCT/CN2015/083179 CN2015083179W WO2016000638A1 WO 2016000638 A1 WO2016000638 A1 WO 2016000638A1 CN 2015083179 W CN2015083179 W CN 2015083179W WO 2016000638 A1 WO2016000638 A1 WO 2016000638A1
Authority
WO
WIPO (PCT)
Prior art keywords
unified
workspace
participant
machine
relational synchronization
Prior art date
Application number
PCT/CN2015/083179
Other languages
English (en)
French (fr)
Inventor
Waitung CHEUNG
Chunhsiao LIN
Shihcheng LAN
Hocheung CHEUNG
Original Assignee
U3D Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/324,069 external-priority patent/US9134963B1/en
Priority claimed from US14/325,466 external-priority patent/US9727391B2/en
Priority claimed from US14/577,772 external-priority patent/US9626157B2/en
Application filed by U3D Limited filed Critical U3D Limited
Priority to SG11201610927XA priority Critical patent/SG11201610927XA/en
Priority to EP15815771.9A priority patent/EP3164818A4/en
Priority to JP2017519776A priority patent/JP2017531879A/ja
Priority to US15/319,195 priority patent/US20170149578A1/en
Priority to KR1020177002951A priority patent/KR102428231B1/ko
Priority to CN201580036469.3A priority patent/CN106663118B/zh
Priority to KR1020227026315A priority patent/KR20220111738A/ko
Publication of WO2016000638A1 publication Critical patent/WO2016000638A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/182—Distributed file systems
    • G06F16/1834—Distributed file systems implemented based on peer-to-peer networks, e.g. gnutella
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/275—Synchronous replication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/101—Collaborative creation, e.g. joint development of products or services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • 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.
  • the existing technologies 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.
  • the cooperation method in the real life should comply with the following three conditions: people participation, communication channels, and synchronization of the displayed content.
  • 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.
  • the personal devices e.g., computers
  • the personal device e.g., a computer
  • a specified object e.g., Team remote control software
  • internet instant messaging software provides a medium for communication and discussion because of the following features. Firstly, as long as the 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.
  • a personal device e.g., a computer
  • 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.
  • the 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 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 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.
  • a desired tool e.g., a video recorder
  • 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.
  • 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) .
  • 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.
  • the present invention provides a networking cooperation method and a machine using the method.
  • the networking cooperation method any identity can be invited to join the cooperative working environment to 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.
  • 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.
  • a 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.
  • 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.
  • the at least one participant and the other participant 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.
  • 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.
  • the at least one participant includes a machine, and/or the at least one other participant includes another machine.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • the projector is loaded into an engine that provides a compatible environment to execute the projector.
  • the engine includes at least one of a Javascript engine, a Windows application or a Linux application.
  • 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.
  • a 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.
  • At least two of the multiple cooperators are related with each other according to the operational demand.
  • 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.
  • 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.
  • each of the multiple cooperators includes a machine.
  • 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.
  • 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.
  • 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.
  • 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.
  • a machine 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.
  • each of the multiple cooperators comprises an other machine.
  • 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.
  • 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.
  • At least two of the multiple cooperators are related with each other according to the operational demand.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • the cooperative working environments i.e., the projected relational synchronization workspaces
  • any information, any tool or any service in the cooperative working environment can be operated by any cooperator.
  • the cooperative working environments i.e., the projected relational synchronization workspaces
  • any cooperate can synchronously view the change of the cooperative working environment in response to an operation of other cooperator.
  • 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.
  • 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.
  • FIG. 17 is a schematic diagram illustrating a usage situation of a networking cooperation method according to another embodiment 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.
  • 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) .
  • 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.
  • 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.
  • original information and “original tool” are implementation examples of “original matters” used herein.
  • 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” .
  • the term “Matterizer” used herein is a means, a device or a program code to perform the unifying process.
  • 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.
  • FIG. 1 is a schematic diagram illustrating an implementation concept of a unifying method according to an embodiment.
  • 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.
  • the original matter 991 at least includes an original information (not shown) or an original tool (not shown) , but is not limited thereto.
  • 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.
  • the unified tool is directly produced by the matterizer 992.
  • 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.
  • SDK software development kit
  • the descriptions of the unifying method” may be referred to the US Patent Application 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 US Patent Application 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 first unifying method is applied to a method of unifying the information of Garmin satellite navigation.
  • 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.
  • most application programs i.e., original tools
  • 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.
  • the at least one tool and/or at least one information can be imported into the workspace through the at least one matterizer.
  • the way of importing the information and/or tool into the workspace is not restricted.
  • 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.
  • 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) .
  • 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
  • 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.
  • 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) .
  • the “workspace” is a user-orientated “personal workspace” .
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the user can perform specified tasks by using the unified tool to access or control the corresponding unified information unit.
  • 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.
  • 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.
  • 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.
  • 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) .
  • URI uniform resource identifier
  • the unified script is defined to configure at least one of the matterizer, the information and the tool to model the workspace.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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) .
  • the projectable space instance 973 is used for building a projected workspace 976 corresponding to the workspace.
  • 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.
  • 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.
  • 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) .
  • 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.
  • the unified script 9731 is declared by the Document Type Definition (DTD)
  • the projectable space instance 973 is instantiated with XML.
  • 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.
  • 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.
  • the projected workspace 976 is built after the projectable space instance 973 is parsed by the projector 974 of the second electronic device 972.
  • 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.
  • 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’ .
  • 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.
  • 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.
  • the Dropbox importer 9761’ and the image viewer 9762’ mentioned above are equipped by the microkernel 977.
  • the URI of the projectable space instance 973 may be a HTTP (hypertext transfer protocol) URI or a FTP (file transfer protocol) URI.
  • the URI of the projectable space instance 973 can also be a local file URI.
  • the types of the URI of the projectable space instance 973 are not restricted.
  • 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;
  • 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.
  • 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.
  • a promotor 23 intends to invite a first participant 21 and a second participant 22 to cooperatively make a topical presentation.
  • the promotor 23, the first participant 21 and the second participant 22 are collaboratively referred as cooperators 2.
  • these cooperators 2 are related with each other.
  • 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.
  • the required unified matters 5 are combined together into the projectable space instance 3 by the promotor 23.
  • 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.
  • 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.
  • 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.
  • 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.
  • each of the first machine 11, the second machine 12 and the third machine 13 has a projector 4.
  • 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.
  • 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.
  • 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
  • the fourth machine 14 after being unified.
  • the projectable space instance 3 has the corresponding uniform resource identifier (URI) .
  • URI uniform resource identifier
  • 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.
  • the promoter 23 can load the projectable space instance 3 into the third machine 13 which is operated by the promoter 23.
  • the platform for transmitting the URI is an operating system or a browser
  • 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.
  • 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.
  • 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.
  • the unified matters 5 include unified tools 51 and information importers 52.
  • the projectors 4 start to parse the projectable space instance 3.
  • 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 23 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.
  • FIGS. 12A ⁇ 12C, FIGS. 13A ⁇ 13C and FIGS. 14A ⁇ 14C 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. 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 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.
  • 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.
  • the first participant 21 can edit the presentation 53 shown on the projected relational synchronization workspace 6A.
  • the recorder 514 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.
  • the recorded contents can be stored in a specified storage area.
  • 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.
  • 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.
  • the presentation editor 512 the second participant 22 can edit the presentation 53 shown on the projected relational synchronization workspace 6B.
  • 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.
  • the recorded contents can be stored in a specified storage area.
  • 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.
  • the presentation editor 512 the promoter 23 can edit the presentation 53 shown on the projected relational synchronization workspace 6C.
  • 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.
  • the recorded contents can be stored in a specified storage area.
  • the contents of the projected relational synchronization workspaces 6A, 6B and 6C are shown in FIGS. 13A ⁇ 13C.
  • the first presentation material 54 is unified into a first unified presentation material 54’ through the information importer 52.
  • 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.
  • 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.
  • 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.
  • the contents of the projected relational synchronization workspaces 6A, 6B and 6C are shown in FIGS. 14A ⁇ 14C.
  • 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.
  • 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.
  • 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.
  • the present invention further provides the following synchronization process.
  • a corresponding synchronization command is generated.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • any of these cooperators 2 may invite other participants to cooperatively implement the task.
  • the second participant 22 may invite another participant (e.g., a third participant, not shown) to ask for help.
  • 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.
  • the third participant can cooperatively implement the task with the promoter 23, the first participant 21 and the second participant 22.
  • 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.
  • another unified matter 5 e.g., a photo edit tool, not shown
  • 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.
  • these cooperators are machines.
  • 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’ .
  • the projectors 4’ receive the projectable space instance 3’ through the URI, the projectors 4’ a utomatically parse the projectable space instance 3’ .
  • 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.
  • 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.
  • the projected relational synchronization workspaces 6A’ , 6B’ and 6C’ a re 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.
  • 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.
  • 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.
  • the cooperative working environments i.e., the projected relational synchronization workspaces
  • any information, any tool or any service in the cooperative working environment can be operated by any cooperator.
  • the cooperative working environments i.e., the projected relational synchronization workspaces
  • any cooperate can synchronously view the change of the cooperative working environment in response to an operation of other cooperator.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Strategic Management (AREA)
  • Software Systems (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computing Systems (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Digital Computer Display Output (AREA)
PCT/CN2015/083179 2014-07-03 2015-07-02 Networking cooperation method and machine using such method WO2016000638A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
SG11201610927XA SG11201610927XA (en) 2014-07-03 2015-07-02 Networking cooperation method and machine using such method
EP15815771.9A EP3164818A4 (en) 2014-07-03 2015-07-02 Networking cooperation method and machine using such method
JP2017519776A JP2017531879A (ja) 2014-07-03 2015-07-02 ネットワーク協調方法及び前記方法を応用する機械
US15/319,195 US20170149578A1 (en) 2014-07-03 2015-07-02 Networking cooperation method and machine using such method
KR1020177002951A KR102428231B1 (ko) 2014-07-03 2015-07-02 네트워킹 협력 작업의 방법 및 상기 방법을 응용하는 기계
CN201580036469.3A CN106663118B (zh) 2014-07-03 2015-07-02 连网协同工作的方法以及应用该方法的机器
KR1020227026315A KR20220111738A (ko) 2014-07-03 2015-07-02 네트워킹 협력 작업의 방법 및 상기 방법을 응용하는 기계

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US14/324,069 US9134963B1 (en) 2014-07-03 2014-07-03 Method of unifying information and tool from a plurality of information sources
US14/324,069 2014-07-03
US14/325,466 2014-07-08
US14/325,466 US9727391B2 (en) 2014-07-08 2014-07-08 Method for performing task on unified information units in a personal workspace
US14/577,772 US9626157B2 (en) 2014-07-03 2014-12-19 Method of projecting a workspace and system using the same
US14/577,772 2014-12-19
CN201510003717.6 2015-01-04
CN201510003717 2015-01-04

Publications (1)

Publication Number Publication Date
WO2016000638A1 true WO2016000638A1 (en) 2016-01-07

Family

ID=55018472

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/083179 WO2016000638A1 (en) 2014-07-03 2015-07-02 Networking cooperation method and machine using such method

Country Status (7)

Country Link
EP (1) EP3164818A4 (ko)
JP (1) JP2017531879A (ko)
KR (2) KR102428231B1 (ko)
CN (1) CN106663118B (ko)
SG (1) SG11201610927XA (ko)
TW (1) TWI563404B (ko)
WO (1) WO2016000638A1 (ko)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016119744A1 (en) * 2015-01-29 2016-08-04 U3D Limited Interactive operation method, and transmitter machine, receiver machine and interactive operation system using the same

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111327510B (zh) * 2018-12-13 2022-02-08 国家电投集团科学技术研究院有限公司 核电计算分析业务的通讯系统
CN109814791B (zh) * 2018-12-20 2020-11-13 东软集团股份有限公司 处理流程节点的方法、装置、存储介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010090286A1 (ja) * 2009-02-09 2010-08-12 コニカミノルタホールディングス株式会社 情報処理システム、情報処理装置および情報処理方法
US20130246901A1 (en) * 2012-03-19 2013-09-19 Litera Technologies, LLC. System and method for synchronizing bi-directional document management
CN103765403A (zh) * 2011-09-12 2014-04-30 英特尔公司 应用和web服务之间元数据驱动的合作
US20140172799A1 (en) * 2012-12-19 2014-06-19 Box, Inc. Method and apparatus for synchronization of items with read-only permissions in a cloud-based environment

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040001095A1 (en) * 2002-07-01 2004-01-01 Todd Marques Method and apparatus for universal device management
US20040016073A1 (en) * 2002-07-25 2004-01-29 Knutson James D. Disposable toothbrush system
US20050080909A1 (en) * 2003-10-10 2005-04-14 Anatoliy Panasyuk Methods and apparatus for scalable secure remote desktop access
US7730223B1 (en) * 2004-07-30 2010-06-01 Apple Inc. Wireless home and office appliance management and integration
US20070016650A1 (en) * 2005-04-01 2007-01-18 Gilbert Gary J System and methods for collaborative development of content over an electronic network
US8156500B2 (en) * 2005-07-01 2012-04-10 Microsoft Corporation Real-time self tuning of planned actions in a distributed environment
EP1941360A2 (en) * 2005-09-27 2008-07-09 Morgan Stanley Host build and rebuild system and method
CN101216846B (zh) * 2008-01-04 2010-06-02 清华大学 一种仿真数据的可视化与协同共享方法
US20100138007A1 (en) * 2008-11-21 2010-06-03 Qwebl, Inc. Apparatus and method for integration and setup of home automation
US8301270B2 (en) * 2009-01-27 2012-10-30 Eldon Technology Ltd. Systems and methods for facilitating home automation
US9245047B2 (en) * 2010-12-10 2016-01-26 Wyse Technology L.L.C. Methods and systems for facilitating a remote desktop session utilizing a remote desktop client common interface
CN102332039B (zh) * 2011-04-29 2013-07-03 华南理工大学 网络协同设计的异源cad模型数据集成装置及集成方法
EP2847962B1 (en) * 2012-05-10 2019-11-20 Telefonaktiebolaget LM Ericsson (publ) System, method and computer program product for protocol adaptation
CN103092980A (zh) * 2013-01-31 2013-05-08 中国科学院自动化研究所 一种数据自动转换与存储的方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010090286A1 (ja) * 2009-02-09 2010-08-12 コニカミノルタホールディングス株式会社 情報処理システム、情報処理装置および情報処理方法
CN103765403A (zh) * 2011-09-12 2014-04-30 英特尔公司 应用和web服务之间元数据驱动的合作
US20130246901A1 (en) * 2012-03-19 2013-09-19 Litera Technologies, LLC. System and method for synchronizing bi-directional document management
US20140172799A1 (en) * 2012-12-19 2014-06-19 Box, Inc. Method and apparatus for synchronization of items with read-only permissions in a cloud-based environment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3164818A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016119744A1 (en) * 2015-01-29 2016-08-04 U3D Limited Interactive operation method, and transmitter machine, receiver machine and interactive operation system using the same

Also Published As

Publication number Publication date
KR102428231B1 (ko) 2022-08-01
EP3164818A1 (en) 2017-05-10
CN106663118B (zh) 2021-05-07
CN106663118A (zh) 2017-05-10
TW201626257A (zh) 2016-07-16
TWI563404B (en) 2016-12-21
SG11201610927XA (en) 2017-02-27
EP3164818A4 (en) 2017-06-14
KR20170040225A (ko) 2017-04-12
KR20220111738A (ko) 2022-08-09
JP2017531879A (ja) 2017-10-26

Similar Documents

Publication Publication Date Title
US11687324B2 (en) Property management method and property management system and machine using the same
AU2019216773B2 (en) Live-rendered and forkable graphic edit trails
Ardito et al. Creation and use of service-based distributed interactive workspaces
WO2016000638A1 (en) Networking cooperation method and machine using such method
US20170149578A1 (en) Networking cooperation method and machine using such method
KR101621496B1 (ko) 터치이벤트정보를 이용한 발표자료 재현 시스템 및 방법
Shurtz Application Sharing from Mobile Devices with a Collaborative Shared Display
WO2017165253A1 (en) Modular communications
WO2016000657A1 (en) Networking conference method, workspace interaction method and machine using the same
US11456983B2 (en) Interactive operation method, and transmitter machine, receiver machine and interactive operation system using the same
EP3166017A1 (en) Method for projecting workspace and system using same
WO2016112844A1 (en) Property management method and property management system and machine using the same
CN106326015A (zh) 连网协同工作的方法以及应用该方法的机器
EP3232384A1 (en) Network service providing method and network service station using method
Preti et al. Transitions: a crossmedia interaction relevant aspect
WO2016000640A1 (en) Cooperative work method on webpage
EP3164804A1 (en) Method and system of dynamically configuring functions of machine

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15815771

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15319195

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2017519776

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015815771

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015815771

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20177002951

Country of ref document: KR

Kind code of ref document: A