WO2016000634A1

WO2016000634A1 - Matter sharing method

Info

Publication number: WO2016000634A1
Application number: PCT/CN2015/083172
Authority: WO
Inventors: Waitung CHEUNG; Chunhsiao LIN; Shihcheng LAN; Hocheung CHEUNG
Original assignee: U3D Ltd
Current assignee: U3D Ltd
Priority date: 2014-07-03
Filing date: 2015-07-02
Publication date: 2016-01-07
Anticipated expiration: 2017-01-03
Also published as: TWI566110B; TW201626259A

Abstract

A matter sharing method includes the following steps. Firstly, a first user transmits a matter to a second user through a first URI. The first URI contains an information to acquire a projectable space instance and a first descriptive table corresponding to the matter. When the second user receives and launches the first URI to execute a projected workspace, the first descriptive table is updated. Then, the second user transmits the matter through a second URI to a third user. The second URI contains an information to acquire the projectable space instance and a second descriptive table corresponding to the matter. When the third user receives and launches the second URI to execute the projected workspace, the second descriptive table is updated. Then, a propagation-related parameter of the matter is obtained according to the first descriptive table and the second descriptive table.

Description

MATTER SHARING METHOD

TECHNICAL FIELD

The present invention relates to a matter sharing method, and more particularly to a matter sharing method for calculating a propagation-related parameter of a shared matter.

BACKGROUND

Recently, with the rapid growth of many social networking sites such as

and

the social networking sites have become the new trend of using Internet. Generally, the social networking sites are related to the services and tools that facilitate the users to maintain and expand their social circles and thus widen the existing relationships. Since many users spend a lot of time in social networking sites through Internet, the social networking sites have become the main entrances of online activities. Moreover, social networking sites are also the centers for sharing network links, multimedia files, music and other information.

When people create fan pages or share information in the social networking sites on the basis of commercial operations, market research, popularity enhancement or brand image enhancement, they hope that the fan pages or the shared information can attract more attention in order to bring a variety of derivative values for individual persons or organizations. Generally, the levels of the derivative values are dependent on many indexes. For example, the request frequency in the same platform or different platforms, the request frequency within a specified time period or a specified location, the propagation path, the key propagator and any other appropriate propagation-related parameter are some of the important indexes. In case that the fan page or the shared information is clicked and re-shared more frequently, the propagated area is wider and the propagated duration is longer, indicating that the covered topics, contents and services are closer to the users’ preferences and the derivatives value are higher.

Of course, the creators of the fan pages or the sharers of the shared information desire to acquire various propagation-related parameters in order to increase the propagation rate. However, the creators of the fan pages of the current social networking sites can only know the number of people tracking their own fan pages and the change of the tracker number within a specified time period. In addition, the information sharers can only know the number of times the information provided to a specified platform is re-shared in the specified platform. The user cannot acquire various propagation-related parameters from the existing information. Consequently, the user cannot realize the propagation trend and the key propagator, not to mention the market heat and direction.

Consequently, it is an important issue to calculate the propagation-related parameters in the market. For example, US Patent No. 8190711 discloses a method of calculating a propagation-related parameter. The method of calculating the propagation-related parameter will be illustrated as follows. Firstly, when a user provides information through the Internet, a uniform resource identifier for acquiring the information is generated. Then, when the user decides to share the information, the uniform resource identifier is provided to a receiver. After the receiver launches the uniform resource identifier to acquire the information, the uniform resource identifier is modified. When the receiver re-shares the information, the modified uniform resource identifier is provided to other receivers. As the consequence, the propagation condition of the information can be tracked and calculated according to the modified uniform resource identifier.

However, the above method is only able to realize the total request frequency of the information and the request frequencies corresponding to different sharers, but the above method is unable to gather statistic about other propagation-related parameters. Moreover, if the information is shared to different platforms, for example shared from

to

and then shared in

the

server cannot realize whether the information is re-shared by the

user and cannot modify the uniform resource identifier. Consequently, the method cannot continuously track and realize the propagation condition of the information.

Moreover, FIG. 1C of US Patent Application No. 20140149888 discloses a statistical graph for visualizing the number of people who view, share or click the information shared by the user within a specified time period. However, this patent does not disclose the method of gathering statistics about various propagation-related parameters. In addition, this method is only related to the statistics about the number of people viewing, sharing or clicking the information in the same social networking site (e.g.,

) .

Moreover, FIG. 4 of US Patent Application No. 20140129558 discloses a statistical graph about the propagation status of timeline-based data visualization of the same event. Moreover, FIG. 1J of US Patent No. 8676937 discloses a graphical user interface capable of showing the hot event at a specified geographic location. However, these patents do not disclose the methods of gathering statistics about various propagation-related parameters. Moreover, the methods disclosed in these patents are only applied to integration and analysis of the events of a single or specified server.

From the above discussions, the current social networking sites can neither acquire various propagation-related parameters nor calculate the propagation-related parameters in cross-platforms. Therefore, there is a need of providing a method of calculating propagation-related parameters in cross-platforms.

SUMMARY

For solving the drawbacks of the conventional technologies, the present invention provides a matter sharing method for calculating a propagation-related parameter of a shared matter according to the statistics about the generated descriptive tables.

In accordance with an aspect of the present invention, there is provided a matter sharing method. The matter sharing method includes the following steps. Firstly, a matter is received through a source information. The source information contains an information to acquire a first descriptive table corresponding to the matter. Then, the matter is transmitted through a destination information. The destination information contains an information to acquire a second descriptive table corresponding to the matter. Then, a propagation-related parameter of the matter is calculated according to at least one of the first descriptive table and the second descriptive table.

In an embodiment, the source information is a first URI (uniform resource identifier) , and the destination information is a second URI.

In an embodiment, each of the first URI and the second URI includes a HTTP (hypertext transfer protocol) URI, a FTP (file transfer protocol) URI, or a local file URI.

In an embodiment, the source information contains an information to acquire a projectable space instance and the first descriptive table, and the destination information contains an information to acquire the projectable space instance and the second descriptive table, wherein a projected workspace is built according to the projectable space instance.

In an embodiment, the matter sharing method further includes a step of using a projector to parse the projectable space instance so as to execute the projected workspace.

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 an embodiment, the first descriptive table contains a first identification code corresponding to the first descriptive table, an identification code of an associated descriptive table corresponding to the first descriptive table and a first view count corresponding to the matter. In addition, the second descriptive table contains a second identification code corresponding to the second descriptive table, an identification code of an associated descriptive table corresponding to the second descriptive table and a second view count corresponding to the matter.

In an embodiment, the first view count is updated when the source information is launched, and the second view count is updated when the destination information is launched.

In an embodiment, the first descriptive table further contains a first sharing time corresponding to the source information, and the second descriptive table further contains a second sharing time corresponding to the destination information.

In an embodiment, the matter sharing method further includes a step of calculating a request frequency of the matter within a specified time period according to at least one of the first sharing time, the first view count, the second sharing time and the second view count.

In an embodiment, the first descriptive table further contains a first location information corresponding to the source information, and the second descriptive table further contains a second location information corresponding to the destination information.

In an embodiment, the matter sharing method further includes a step of calculating a request frequency of the matter at a specified location or a propagation path of the matter within a specified time period according to at least one of the first sharing time, the first view count, the first location information, the second sharing time, the second view count and the second location information.

In an embodiment, the first descriptive table further contains a first sharer data corresponding to a first user who transmits the source information, and the second descriptive table further contains a second sharer data corresponding to a second user who transmits the destination information.

In an embodiment, the first descriptive table further contains a first channel data corresponding to the second user, and the second descriptive table further contains a second channel data corresponding to a third user.

In an embodiment, the matter is a unified information unit or a unified tool provided to the projected workspace.

In an embodiment, the unified information unit is produced after an original information from at least one information source is unified, and/or the unified tool is produced after an original tool from at least one information source is unified.

In an embodiment, the unified information unit includes a file, a web page, a database row, a policy, a rule, or any information accessible from a corresponding machine or a server, and/or the 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.

In an embodiment, the matter is the projected workspace.

In accordance with an aspect of the present invention, there is provided a matter sharing method. The matter sharing method includes the following steps. Firstly, a matter is transmitted through a first URI (uniform resource identifier) . The first URI contains an information to acquire a projectable space instance and a first descriptive table corresponding to the matter. A projected workspace is built according to the projectable space instance. Then, the first URI is received and launched to execute the projected workspace. When the first URI is launched to execute the projected workspace, the first descriptive table is updated. Then, the matter is transmitted through a second URI. The second URI contains an information to acquire the projectable space instance and a second descriptive table corresponding to the matter. Then, the second URI is received and launched to execute the projected workspace. When the second URI is launched to execute the projected workspace, the second descriptive table is updated. Then, a propagation-related parameter of the matter is calculated according to the first descriptive table and the second descriptive table.

In an embodiment, the first view count is updated when the first URI is launched, and the second view count is updated when the second URI is launched.

In an embodiment, the first descriptive table further contains a first sharing time corresponding to the first URI, and the second descriptive table further contains a second sharing time corresponding to the second URI.

In an embodiment, the first descriptive table further contains a first location information corresponding to the first URI, and the second descriptive table further contains a second location information corresponding to the second URI.

In an embodiment, the first descriptive table further contains a first sharer data corresponding to a first user who transmits the first URI, and the second descriptive table further contains a second sharer data corresponding to a second user who transmits the second URI.

In an embodiment, the matter is the projected workspace.

From the above descriptions, the present invention provides a matter sharing method. Whenever a matter is shared, a descriptive table containing a view count, a sharing time, a location information and other information is generated. By integrating all descriptive tables corresponding to the same matter, various propagation-related parameters associated with the matter are obtained. As a consequence, the drawbacks of the conventional technology can be overcome.

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 schematic diagram illustrating the architecture of a system for performing a matter sharing method according to an embodiment of the present invention；

FIG. 8 is a schematic diagram illustrating a process of generating a descriptive table according to an embodiment of the present invention；

FIG. 9 schematically illustrates the contents of a first descriptive table；

FIG. 10 schematically illustrates the contents of a statistical table according to an embodiment of the present invention；

FIG. 11 is a cumulative diagram showing the request frequency； and

FIG. 12 is a propagation map showing the propagation path of the matter.

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 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 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 and the Dropbox importer 9761’ of FIG. 6 are some examples of the matterizer. The term “unified script” used herein is an intermediate language to implement the workspace. Moreover, via the “unified script” , the at least one matterizer, the at least one tool and/or the at least one information can be provided to the workspace (e.g., built in or plugged in the workspace) .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Herein, “the descriptions of the method of projecting the workspace” may be referred to the US Patent Application 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 US Patent Application 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.

The present invention provides a matter sharing method, which will be illustrated in more details as follows. Please refer to FIGS. 7～9. FIG. 7 is a schematic diagram illustrating the architecture of a system for performing a matter sharing method according to an embodiment of the present invention. FIG. 8 is a schematic diagram illustrating a process of generating a descriptive table according to an embodiment of the present invention. FIG. 9 schematically illustrates the contents of a first descriptive table.

Firstly, a first user 10 acquires a projectable space instance 12 from a first machine 11. Then, a projector 13 is used to parse the projectable space instance 12. Consequently, a projected workspace 15 is executed in a second machine 14. Then, the first user 10 may arbitrarily combine one or more matterizers, one or more unified tools and/or one or more unified information unit together into the projected workspace 15. In this embodiment, the projectable space instance 12 is built in the first machine 11. Alternatively, in another embodiment, the projectable space instance 12 may be built in the second machine 14.

For sharing the unified tool, the unified information unit or the projected workspace 15 (i.e., the matter) , the first user 10 may tap a share button 15a in the projected workspace 15 (see FIG. 8) . Consequently, a first descriptive table 16 and a source information 17 are generated.

For example, the source information 17 is a uniform resource identifier (URI) , e.g. http: //abc. com/#！ /space_id？ propagation_id＝” …” . After the source information 17 is acquired, the projectable space instance 12 and the first descriptive table 16 are obtained according to a recognition information (space_id) of the projected workspace 15 and a first identification code (propagation_id) of the first descriptive table 16. In the embodiment as shown in FIG. 7, the first descriptive table 16 is stored in the first machine. It is noted that the first descriptive table 16 can be stored in any storage medium with a network connection function.

Moreover, the first user 10 can transmit the source information 17 to one or more second users 18 through appropriate channels. Preferably but not exclusively, the channel includes a network channel (e.g.,

or

channel) , a telecom channel (e.g., a telecommunication channel or a fax channel) , or a physical channel (e.g., a paper note) . Please refer to FIG. 8. After the first user 10 taps the share button 15a, selects one of a

option 15b and a

option 15c and taps the confirmation button 15d sequentially, the source information 17 is shared to

and/or

and lunched in

and/or

After the second user 18 launches the source information 17 to acquire the projectable space instance 12, a projector 20 of the third machine 19 parses the projectable space instance 12. Consequently, a projected workspace 15’ is executed in the third machine 19. In FIG. 7, the source information 17 is transmitted to a single first user 18 only. It is noted that the number of the second user 18 is not restricted. In some other embodiments, the source information 17 can be transmitted from the first user 17 to multiple second users 18 through various channels simultaneously or sequentially.

Preferably but not exclusively, the URI may be a HTTP (hypertext transfer protocol) URI, a FTP (file transfer protocol) URI or a local file URI.

The detailed contents of the first descriptive table 16 will be illustrated as follows. An example of the first descriptive table 16 includes but is not limited to an object, an extensible markup language (XML) document, or an instance instantiated with a structured language or a structured protocol. In this embodiment as shown in FIG. 9, the information fields of the first descriptive table 16 contain propagation_id, propagator_id, propagated_time, propagated_channels, propagated_work, propagated_link, track, network_address, geo_info, viewed_matters and produced_view_count, which will be illustrated as follows.

The information field propagation_id is a first identification code of the first descriptive table 16. The information field propagator_id denotes the user who shares matters and thus generates the first descriptive table 16. In this embodiment, the information field propagator_id is a first sharer data of the first user 10.

The information field propagated_time is the time of generating the first descriptive table 16 and also referred as a first sharing time in this embodiment. The information field propagated_channels denotes a first channel data for transmitting the source information 17 (i.e., the first channel data for allowing the second user 18 to receive the source information 17) . For example, the first channel data includes

or

The information field propagated_work denotes the workspace corresponding to the first descriptive table 16 (e.g., the identification code of the projected workspace 15) .

The information field propagated_link denotes a first URI of the source information 17. If the source information 17 is shared to different channels, the first URI has different forms. Regardless of the forms of the first URI, the projectable space instance 12 and the first descriptive table 16 can be acquired through the first URI. Preferably but not exclusively, the information field propagated_link about the transmission channel for sharing the source information 17 to

is http: //abc. com/#！ /space_id？ propagation_id＝” …” &channel＝” Facebook” , and the information field propagated_link about the transmission channel for sharing the source information 17 to

is http: //abc. com/#！ /space_id？ propagation_id＝” …” &channel＝” Twitter” .

The information field track is used for recording the identification code (s) of the descriptive table (s) associated with the first descriptive table 16. For example, if the user “a” shares a matter to the user “b” and thus generates the descriptive table “a” and the URI “a” and the user “b” shares the same matter to the user “c” and thus generates the descriptive table “b” and the URI “b” , the information field track of the descriptive table “b” records the identification codes of the descriptive tables “a” and “b” in order to indicate that the sharing action of the user “a” brings about the re-sharing action of the user “b” . Similarly, if the user “c” shares the same matter to the user “d” and thus generates the descriptive table “c” and the URI “c” , the information field track of the descriptive table “c” records the identification codes of the descriptive tables “a” , “b” and “c” in order to indicate that the sharing action of the user “a” brings about the re-sharing actions of the user “b” and the user “c” . It is noted that numerous modifications and alterations may be made while retaining the teachings of the invention. For example, in another embodiment, the information field track of the descriptive table “c” only records the identification codes of the descriptive tables “b” and “c” . Consequently, after the descriptive table “c” is acquired, it is realized that the matter is shared by the sharer “a” because the descriptive table “a” can be acquired through the descriptive table “b” . In this embodiment, the first user 10 is the first sharer. Consequently, the information field track of the first descriptive table 16 only records the identification code of the first descriptive table 16.

The information field network_address is associated with the internet protocol address (IP address) of the user who shares the matter and thus generates the first descriptive table 16 (i.e., the first user 10) . The information field geo_info is associated with a first location information of the user who shares the matter and thus generates the first descriptive table 16 (i.e., the first user 10) . The information field viewed_matters is associated with the recognition information of the unified tool or the unified information unit in the projected workspace 15 that has been launched by first user 10 before this sharing action. The information field produced_view_count denotes a first view count generated by this sharing action. When the second user 18 launches the source information 17 to acquire the projectable space instance 12 and the first descriptive table 16, the first view count is increased and updated.

Moreover, the information field propagated_link and the information field produced_view_count of the first descriptive table 16 may respectively record the first URI and the first view count according to different channels.

Similarly, the process of sharing the unified tool, the unified information unit or the projected workspace 15 (i.e., the matter) by the first user 10 can also be performed by the second user 18. That is, the second user 18 may select the identical channel or a different channel through the projected workspace 15’ to share the same unified tool, the same unified information unit or the same projected workspace 15’ (i.e., the matter) to one or more third users 21. Similarly, when the second user 18 taps the share button (not shown) to share the matter, a second descriptive table 22 and a destination information 23 are generated. For example, the destination information 23 is a second URI. According to the second URI, the projectable space instance 12 and the second descriptive table 22 are obtained.

After the third user 18 acquires the projectable space instance 12 according to the destination information 23, a projector 25 of the fourth machine 24 parses the projectable space instance 12. Consequently, a projected workspace 15” is executed in the fourth machine 24. In FIG. 7, the destination information 23 is transmitted to a single third user 21 only. It is noted that the number of the third user 21 is not restricted. In some other embodiments, the destination information 23 can be transmitted from the second user 18 to multiple third users 21 through various channels simultaneously or sequentially. The projected

workspaces

15, 15’ and 15” are built after the same projectable space instance 12 is parsed. Consequently, the projected

workspaces

15, 15’ and 15” are completely identical.

Similarly, the information fields of the second descriptive table 22 contain propagation_id, propagator_id, propagated_time, propagated_channels, propagated_work, propagated_link, track, network_address, geo_info, viewed_matters and produced_view_count. For brevity, these information fields are not shown in another drawing.

The information field propagation_id is a second identification code of the second descriptive table 22. The information field propagator_id denotes the user who shares matters and generates the second descriptive table 22. In this embodiment, the information field propagator_id is a second sharer data of the second user 18.

The information field propagated_time is the time of generating the second descriptive table 22 and also referred as a second sharing time in this embodiment. Moreover, information field propagated_channels denotes a second channel data for transmitting the destination information 23 (i.e., the second channel data for allowing the third user 21 to receive the destination information 23) . For example, the second channel data includes

or

The information field propagated_work denotes the workspace corresponding to the second descriptive table 22 (e.g., the identification code of the projected workspace 15’ ) .

The information field propagated_link denotes the second URI of the destination information 23. If the destination information 23 is shared to different channels, the second URI has different forms. Regardless of the forms of the second URI, the projectable space instance 12 and the second descriptive table 22 can be acquired through the second URI.

As mentioned above, the information field track is used for recording the identification code (s) of the descriptive table (s) associated with the second descriptive table 22. Since the second descriptive table 22 is generated after the second user 18 receives the source information 17 from the first user 10 and the matter is re-shared, the information field track of the second descriptive table 22 records the first identification code of the first descriptive table 16 corresponding to the sharing action of the first user 10 and the second identification code of the second descriptive table 22 corresponding to the re-sharing action of the second user 18 in order to indicate that the sharing action of the fist user 10 brings about the re-sharing action of the second user 18.

The information field network_address is associated with the internet protocol address (IP address) of the user who shares the matter and thus generates the second descriptive table 22 (i.e., the second user 18) . The information field geo_info is associated with a second location information of the user who shares the matter and thus generates the second descriptive table 22 (i.e., the second user 18) . The information field viewed_matters is associated with the recognition information of the unified tool or the unified information unit in the projected workspace 15’ that has been launched by second user 18 before this sharing action. The information field produced_view_count denotes a second view count generated by this sharing action. When the third user 21 launches the destination information 23 to acquire the projectable space instance 12 and the second descriptive table 22, the second view count is increased and updated.

Since the projected

workspaces

15, 15’ and 15” correspond to the same projectable space instance 12, the projected

workspaces

15, 15’ and 15” are completely identical. In other words, the information field propagated_work of the first descriptive table 16 and the information field propagated_work of the second descriptive table 22 are identical.

From the above descriptions, the descriptive table as shown in FIG. 9 is generated whenever the user shares the unified tool, the unified information unit or the projected workspace (i.e., the matter) . By integrating the descriptive tables corresponding to the same workspace (i.e., the descriptive tables with the same identification code in the information field propagated_work) , various propagation-related parameters are obtained. The contents of the propagation-related parameters will be described as follows.

Firstly, the first machine 11 or a remote server generates a statistical table according to all descriptive tables corresponding to the same workspace. In particular, the statistical table is generated by integrating the descriptive tables corresponding to the same workspace within a time period. FIG. 10 schematically illustrates the contents of a statistical table according to an embodiment of the present invention.

As shown in FIG. 10, the information fields of the statistical table 26 contain record_id, propagated_work, record_start_date, record_end_date and day_view_count.

The information field record_id denotes a recognition information of the statistical table 26. The information field propagated_work denotes the corresponding workspace of the statistical table 26. In this embodiment, the information field propagated_work of the statistical table 26 denotes the recognition information of the workspace which is built after the projectable space instance 12 is parsed. Consequently, the recognition information recorded in the information field propagated_work of the statistical table 26 is identical to that of the first descriptive table 16 and the second descriptive table 22.

The information field record_start_date and the information field record_end_date denote the start record date and the end record date of the statistical table 26, respectively. That is, the information field propagated_time of any descriptive table corresponding to the projectable space instance 12 and recorded in the statistical table 26 is in the range between the start record date and the end record date.

The information field day_view_count records the cumulative count of the values of the information field viewed_matters in all descriptive tables corresponding to the projectable space instance 12 and at the same date in the information field propagated_time (i.e., the information field matter_view_count in the statistical table 26) and the cumulative count of the values of the information field produced_view_count in all descriptive tables corresponding to the projectable space instance 12 and generated till the date (i.e., the information field work_view_count in the statistical table 26) .

As shown in FIG. 10, the information field record_start_date and the information field record_end_date in the statistical table 26 are 2014-06-01 and 2014-06-30, respectively. The information field work_view_count in the statistical table 26 records the cumulative count of the values of the information field produced_view_count in all descriptive tables corresponding to the projectable space instance 12 till each date (e.g., till 2014-06-30) . Moreover, the information field matter_view_count in the statistical table 26 records the cumulative count of the values of the information field viewed_matters in all descriptive tables corresponding to the projectable space instance 12 and at each date (e.g., the date 2014-06-30) .

Consequently, if the user intends to know the request frequency of the workspace corresponding to the projectable space instance 12 within any day, several days or the whole month in the range between 2014-06-01 and 2014-06-30, the user can acquire the statistical table 26 as shown in FIG. 10 according to the recognition information of the workspace. According to the information field work_view_count of the statistical table 26, a cumulative diagram is depicted in FIG. 11 to show the request frequency corresponding to the time period of any day, several days or the whole month.

Moreover, if the user intends to know which unified tool or unified information unit in the workspace corresponding to the projectable space instance 12 is launched most frequently within any day, several days or the whole month in the range between 2014-06-01 and 2014-06-30, the user may acquire the required data by summing up and sorting the values of the information field matter_view_count in the statistical table 26.

In some embodiments, the statistical table is not generated by the first machine 11 or the remote server. According to the information field propagated_time and the information field geo_info of all descriptive tables, a propagation map as shown in FIG. 12 is obtained. A propagation path of the workspace corresponding to the projectable space instance 12 within a specified time period can be realized. Moreover, according to the information field produced_view_count and the information field geo_info of all descriptive tables, the request frequency of the workspace corresponding to the projectable space instance 12 at a specified location can be realized.

Please refer to FIG. 12. When the user selects any time point (e.g., the time point T) , a first locating point A, a second locating point B and a third locating point C are shown. The first locating point A denotes the location of the sharer who shares the unified tool, the unified information or the workspace at the time point T. The second locating point B denotes the location of the sharer who shares the unified tool, the unified information or the workspace at the previous day corresponding to the time point T. The third locating point C denotes the location of the sharer who shares the unified tool, the unified information or the workspace at the next day corresponding to the time point T. As a consequently, the user can realize the propagation path of the same unified tool, the same unified information or the same workspace within the specified time period.

In some embodiments, the statistical table is not generated by the first machine 11 or the remote server. According to the information field produced_view_count of all descriptive tables, the view count of the workspace corresponding to the projectable space instance 12 is calculated. Consequently, the channel corresponding to the highest view count is realized.

In some embodiments, the first machine 11 or the remote server can realize the key propagator according to the information field propagator_id, the information field track and the information field produced_view_count.

For example, by gathering statistics about the number of descriptive tables having the same workspace recognition information and having the recorded identification code of the descriptive table “a” in the information field track, the re-sharing count that is brought about through the descriptive table “a” can be realized. Moreover, according to the sharer data recorded in the information field propagator_id of the descriptive table “a” , the re-sharing count that is brought about by a specified user can be realized. Consequently, the key propagator can be found.

Otherwise, after a specified descriptive table with the highest value of the information field produced_view_count is searched from a plurality of descriptive tables with the same workspace recognition information, the re-sharing count that is brought about by a specified user can be realized according to the sharer data recorded in the information field propagator_id of the specified descriptive table. Similarly, the key propagator can be found accordingly.

From the above descriptions, the present invention provides a matter sharing method. Whenever a matter is shared, a descriptive table containing a view count, a sharing time, a location information and other information is generated. By integrating all descriptive tables corresponding to the same matter, various propagation-related parameters of the matter are obtained. As a consequence, the drawbacks of the conventional technology can be overcome.

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

A matter sharing method, comprising steps of:

receiving a matter through a source information, wherein the source information contains an information to acquire a first descriptive table corresponding to the matter；

transmitting the matter through a destination information, wherein the destination information contains an information to acquire a second descriptive table corresponding to the matter； and

calculating a propagation-related parameter of the matter according to at least one of the first descriptive table and the second descriptive table.
The matter sharing method according to claim 1, wherein the source information is a first URI (uniform resource identifier) , and the destination information is a second URI.
The matter sharing method according to claim 2, wherein each of the first URI and the second URI includes a HTTP (hypertext transfer protocol) URI, a FTP (file transfer protocol) URI, or a local file URI.
The matter sharing method according to claim 1, wherein the source information contains an information to acquire a projectable space instance and the first descriptive table, and the destination information contains an information to acquire the projectable space instance and the second descriptive table, wherein a projected workspace is built according to the projectable space instance.
The matter sharing method according to claim 4, further comprising a step of using a projector to parse the projectable space instance so as to execute the projected workspace.
The matter sharing method according to claim 4, 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.
The matter sharing method according to claim 1, wherein the first descriptive table contains a first identification code corresponding to the first descriptive table, an identification code of an associated descriptive table corresponding to the first descriptive table and a first view count corresponding to the matter, wherein the second descriptive table contains a second identification code corresponding to the second descriptive table, an identification code of an associated descriptive table corresponding to the second descriptive table and a second view count corresponding to the matter.
The matter sharing method according to claim 7, wherein the first view count is updated when the source information is launched, and the second view count is updated when the destination information is launched.
The matter sharing method according to claim 7, wherein the first descriptive table further contains a first sharing time corresponding to the source information, and the second descriptive table further contains a second sharing time corresponding to the destination information.
The matter sharing method according to claim 9, further comprising a step of calculating a request frequency of the matter within a specified time period according to at least one of the first sharing time, the first view count, the second sharing time and the second view count.
The matter sharing method according to claim 7, wherein the first descriptive table further contains a first location information corresponding to the source information, and the second descriptive table further contains a second location information corresponding to the destination information.
The matter sharing method according to claim 9, wherein the first descriptive table further contains a first location information corresponding to the source information, and the second descriptive table further contains a second location information corresponding to the destination information.
The matter sharing method according to claim 12, further comprising a step of calculating a request frequency of the matter at a specified location or a propagation path of the matter within a specified time period according to at least one of the first sharing time, the first view count, the first location information, the second sharing time, the second view count and the second location information.
The matter sharing method according to claim 1, wherein the first descriptive table further contains a first sharer data corresponding to a first user who transmits the source information, and the second descriptive table further contains a second sharer data corresponding to a second user who transmits the destination information.
The matter sharing method according to claim 14, wherein the first descriptive table further contains a first channel data corresponding to the second user, and the second descriptive table further contains a second channel data corresponding to a third user.
The matter sharing method according to claim 4, wherein the matter is a unified information unit or a unified tool provided to the projected workspace.
The matter sharing method according to claim 16, wherein the unified information unit is produced after an original information from at least one information source is unified, and/or the unified tool is produced after an original tool from at least one information source is unified.
The matter sharing method according to claim 16, wherein the unified information unit includes a file, a web page, a database row, a policy, a rule, or any information accessible from a corresponding machine or a server, and/or the 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.
The matter sharing method according to claim 4, wherein the matter is the projected workspace.
A matter sharing method, comprising steps of:

transmitting a matter through a first URI (uniform resource identifier) , wherein the first URI contains an information to acquire a projectable space instance and a first descriptive table corresponding to the matter, wherein a projected workspace is built according to the projectable space instance；

receiving and launching the first URI to execute the projected workspace, wherein when the first URI is launched to execute the projected workspace, the first descriptive table is updated；

transmitting the matter through a second URI, wherein the second URI contains an information to acquire the projectable space instance and a second descriptive table corresponding to the matter；

receiving and launching the second URI to execute the projected workspace, wherein when the second URI is launched to execute the projected workspace, the second descriptive table is updated； and

calculating a propagation-related parameter of the matter according to the first descriptive table and the second descriptive table.
The matter sharing method according to claim 20, wherein each of the first URI and the second URI includes a HTTP (hypertext transfer protocol) URI, a FTP (file transfer protocol) URI, or a local file URI.
The matter sharing method according to claim 20, further comprising a step of using a projector to parse the projectable space instance so as to execute the projected workspace.
The matter sharing method according to claim 20, 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.
The matter sharing method according to claim 20, wherein the first descriptive table contains a first identification code corresponding to the first descriptive table, an identification code of an associated descriptive table corresponding to the first descriptive table and a first view count corresponding to the matter, wherein the second descriptive table contains a second identification code corresponding to the second descriptive table, an identification code of an associated descriptive table corresponding to the second descriptive table and a second view count corresponding to the matter.
The matter sharing method according to claim 24, wherein the first view count is updated when the first URI is launched, and the second view count is updated when the second URI is launched.
The matter sharing method according to claim 24, wherein the first descriptive table further contains a first sharing time corresponding to the first URI, and the second descriptive table further contains a second sharing time corresponding to the second URI.
The matter sharing method according to claim 26, further comprising a step of calculating a request frequency of the matter within a specified time period according to at least one of the first sharing time, the first view count, the second sharing time and the second view count.
The matter sharing method according to claim 24, wherein the first descriptive table further contains a first location information corresponding to the first URI, and the second descriptive table further contains a second location information corresponding to the second URI.
The matter sharing method according to claim 26, wherein the first descriptive table further contains a first location information corresponding to the first URI, and the second descriptive table further contains a second location information corresponding to the second URI.
The matter sharing method according to claim 29, further comprising a step of calculating a request frequency of the matter at a specified location or a propagation path of the matter within a specified time period according to at least one of the first sharing time, the first view count, the first location information, the second sharing time, the second view count and the second location information.
The matter sharing method according to claim 20, wherein the first descriptive table further contains a first sharer data corresponding to a first user who transmits the first URI, and the second descriptive table further contains a second sharer data corresponding to a second user who transmits the second URI.
The matter sharing method according to claim 31, wherein the first descriptive table further contains a first channel data corresponding to the second user, and the second descriptive table further contains a second channel data corresponding to a third user.
The matter sharing method according to claim 20, wherein the matter is a unified information unit or a unified tool provided to the projected workspace.
The matter sharing method according to claim 33, wherein the unified information unit is produced after an original information from at least one information source is unified, and/or the unified tool is produced after an original tool from at least one information source is unified.
The matter sharing method according to claim 33, wherein the unified information unit includes a file, a web page, a database row, a policy, a rule, or any information accessible from a corresponding machine or a server, and/or the 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.
The matter sharing method according to claim 20, wherein the matter is the projected workspace.