CN107209674B

CN107209674B - Method for managing assets and asset management system and machine using the same

Info

Publication number: CN107209674B
Application number: CN201680005618.4A
Authority: CN
Inventors: 张伟东; 林俊孝; 张皓翔
Original assignee: Abel Global International Ltd
Current assignee: Abel Global International Ltd
Priority date: 2015-01-12
Filing date: 2016-01-12
Publication date: 2020-12-29
Anticipated expiration: 2036-01-12
Also published as: TWI564731B; TW201631494A; CN107209674A; WO2016112844A1

Abstract

The present invention provides a method of managing assets. Firstly, a projectable space entity is provided and used for establishing a total management system. When a user obtains the projectable space entity, a projection means interprets the projectable space entity. After the projectable spatial entity is interpreted, a projected mains system corresponding to the mains system is established for the user to access at least one asset (P1). In addition, the invention also provides an asset management system and a machine applying the method for managing the assets.

Description

Method for managing assets and asset management system and machine using the same

Technical Field

The present invention relates to a method for managing assets and an asset management system and a machine using the same, and more particularly, to a method for managing assets over the internet and an asset management system and a machine using the same,

background

In modern times where life is convenient, people are accustomed to using electronic devices with computing capabilities for various applications such as work, word processing, entertainment, social communications, and the like. With the progressive development of science and technology, information is spread more rapidly, and various web platforms, operating systems and software tools are developed for people to use, so that more efficient life is brought to people. Particularly, in the post-computer age, besides the traditional desktop computers, tablet computers, mobile phones and other mobile devices, people can operate anytime and anywhere, and meanwhile, the mobile devices can be connected with people all over the world in series through the internet to transmit and share information. However, there are still many troubles that make the users feel inconvenient in using the internet.

First, a large amount of information and tools are distributed in different formats (formats) or different formats in different information sources, which makes it increasingly impossible to integrate and use information and tools of different formats obtained in a single workspace (workplace), and after all, the information and tools of different formats often have incompatibility problems.

Second, since different users have different habits and usages in operating electronic devices, an operating environment and/or a working space suitable for the users are mostly created only on electronic devices commonly used by individuals (e.g., a desktop computer for home use). Once the user leaves the place where the personal commonly used electronic device is located, the user can only access the information placed on the commonly used electronic device through the network on another electronic device, and since the other electronic device is not the working environment and/or working space used by the user, and the personal commonly used software tools or specific functions are not configured in the other electronic device, the user cannot work unless the required software tools or specific functions are reloaded in the other electronic device.

Third, the Linglan-full-purpose web platform, operating system and software are mostly developed by different developers, and are often independent and incompatible with each other, so that people cannot operate specific functions belonging to different web platforms, operating systems and software on a single user interface when executing tasks.

Fourth, existing hardware or software is mostly a product developed from the perspective of "personal device", which causes a barrier to the cooperative work of human and human networking, like there are numerous and well-defined data stations on the internet.

Currently, there is no working space for multiple cooperative workers to freely combine any information, any tool, or any service into it for cooperative work according to actual work requirements, and there is no suitable operating environment for each user to manage the working space and personal property created by different work initiators.

Therefore, the application of the existing internet has room for improvement.

Disclosure of Invention

The invention provides a method for managing assets, an asset management system and a machine using the method, so as to improve the application mode of the existing Internet.

In one aspect, the present invention provides a method of managing assets. First, a projectable space entity (projectable space entity) is provided, and the projectable space entity is used to build a (model) total system (home system). When a machine obtains the projectable space entity, a projector interprets the projectable space entity. After the projectable spatial entity is interpreted, a projected businessystem corresponding to the businessystem is established for a user to access (access) at least one asset (property).

In a preferred embodiment, the machine obtains the projectable spatial entity via a path link message (URI) and/or a login procedure of the user.

In a preferred embodiment, the projectable spatial entity has a plurality of unified elements built therein for building the total pipe system.

In a preferred embodiment, at least some of the plurality of unified elements constitute a cloud desktop (cloud desktop), a workspace creator, a service manager, and/or a relationship manager.

In a preferred embodiment, the user accesses the at least one asset through the cloud desktop.

In a preferred embodiment, the workspace creator provides the user with a deliverable workspace (workspace).

In a preferred embodiment, the service management unit comprises at least one unified tool (unified converter), wherein at least one unified tool (unified tool) and/or at least one unified information unit (unified information unit) is inputted into the host system and/or the at least one asset via the at least one unified converter.

In a preferred embodiment, the at least one original tool corresponding to the at least one unified tool comprises a utility (utility), an interface tool set (widget), a proxy (agent), an application, a service (service), or any executable accessible on a related machine or server; and/or, the at least one original message corresponding to the at least one unified message unit includes a file (file), a web page (web page), a database (database row), a policy, a rule, an operation specification (policy), or any message accessible to a related machine or a server.

In a preferred embodiment, the relationship management unit is used for the user to manage (manage), aggregate (aggregate) or access (access) a relationship (relationship).

In a preferred embodiment, the at least one asset comprises a transportable workspace (scalable workspace) created by another projectable space entity, and the another projectable space entity is used for adding or removing at least one unified element.

In a preferred embodiment, the at least one normalization element is formed by normalizing (unification) at least one primitive element obtained from at least one information source (information source).

In a preferred embodiment, the projection engine is loaded into an engine (engine) and the engine is configured to provide a compatible environment for executing the projection engine.

In a preferred embodiment, the projectable spatial entity is an object (object), an extensible markup language (XML) file, or an entity (instance) generated in a structured language (structured language) or a structured protocol (structured protocol).

In another aspect, the present invention provides an asset management system that provides a projectable space entity (projectable space instance) for building (model) a total management system (home system) to a machine. When the machine obtains the projectable space entity, a projection means interprets the projectable space entity. After the projectable spatial entity is interpreted, a projected businessystem corresponding to the businessystem is established for a user to access (access) at least one asset (property).

In a preferred embodiment, the user accesses the at least one asset through the cloud desktop. Alternatively, the workspace creator provides the user with a transferable workspace (deliverable workspace). Alternatively, the service management unit comprises at least one unified tool (unified tool) and/or at least one unified information unit (unified information unit) input to the host system and/or the at least one asset via the at least one element translator. Alternatively, the relationship management unit is used for the user to manage (manage), aggregate (aggregate) or access (access) a relationship (relationship).

In yet another aspect, the present invention also provides a method of managing assets. First, a projectable space entity (projectable space entity) for building a total system (home system) is obtained. Next, a projection means (projector) is used to interpret the projectable spatial entity. After the projectable spatial entity is interpreted, a projected businesset corresponding to the businese is established to access (access) at least one asset (property).

In a preferred embodiment, the projectable space instance is obtained by the machine via a path link information (URI) and/or a user login procedure; and/or the projectable spatial entity is an object (object), an extensible markup language (XML) file, or an entity (instance) generated by a structured language (structured language) or a structured protocol (structured protocol); and/or the projection means is loaded into an engine (engine) and the engine provides a compatible environment to execute the projection means.

In a preferred embodiment, a user accesses the at least one asset through the cloud desktop.

In a preferred embodiment, the workspace creator is adapted for a user to create a deliverable workspace (deliverable workspace).

In a preferred embodiment, the relationship management unit is used for a user to manage (manage), aggregate (aggregate) or access (access) a relationship (relationship).

In a preferred embodiment, the at least one normalization element is formed by normalizing at least one primitive element obtained from at least one information source (information source) by the at least one element transformer.

In another aspect, the present invention also provides a machine, into which a projector is loaded, for obtaining a projectable space entity (projectable space entity) for building a host system (model). The projection means interprets the projectable space entity after the machine obtains the projectable space entity, so that a projected host system corresponding to the host system is established on the machine for a user to access at least one property.

In a preferred embodiment, the machine obtains the projectable space entity via a path link message (URI) and/or a login procedure of the user; and/or the projectable spatial entity is an object (object), an extensible markup language (XML) file, or an entity (instance) generated by a structured language (structured language) or a structured protocol (structured protocol); and/or the projection means is loaded into an engine (engine) and the engine provides a compatible environment to execute the projection means.

The above objects and advantages of the present invention will become more apparent to those of ordinary skill in the art after considering the following detailed description and accompanying drawings, in which:

drawings

Fig. 1 is a conceptual diagram of an embodiment of a unification method.

FIG. 2 is a conceptual diagram of an implementation of unified scripts as an intermediate language for implementing a personal workspace.

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

FIG. 4 is a diagram illustrating an initial state of a method for projecting a workspace according to a preferred embodiment of the invention.

Fig. 5A and 5B are conceptual diagrams illustrating the operation of the method for projecting the workspace shown in fig. 4.

Fig. 6 is a diagram illustrating a relative relationship between the projectable spatial entity shown in fig. 4 and the projected workspace shown in fig. 5B.

FIG. 7 is a flow chart of a preferred embodiment of a method of managing assets in accordance with the present invention.

FIG. 8 is a schematic diagram of an asset management system and machine to which the method of managing assets of FIG. 7 is applied.

Fig. 9A and 9B are schematic diagrams illustrating the relationship between the projectable spatial entity shown in fig. 8 and the projected mains system.

Fig. 10 is a conceptual diagram of the operation of the cloud desktop shown in fig. 9B.

FIG. 11 is a schematic diagram of an asset management system of the present invention as a device carrying a network service platform.

Detailed Description

The invention will be more fully understood from the following description, including the following glossary of terms and conclusive examples. For the sake of brevity, publications, including patent disclosures, cited in this specification are incorporated herein by reference.

The following examples of the invention are non-limiting and merely represent various aspects and features of the invention. In the most limiting technical sense, an "information source" as described herein refers to a sequence of symbols that can be interpreted as useful messages, and that are used to organize and tag data; wherein, the information source can include: websites (e.g., internet services), intranets, network communities, software, electronic books, databases, and other media of information (e.g., non-transitory computer-usable storage media, mobile device storage media). Also, the "raw information" described herein may include files, web pages, databases, policies, rules, or any data accessible to the associated machine and server, while the "raw tools" described herein may include utilities, interface toolsets, intelligent agent tools, applications, service tools, or any executable elements accessible to the associated machine and server. However, the source, source and tool are not limited to the above.

In addition, the "original information" and the "original tool" are implementation aspects of the "original element" described herein, and in implementing the present invention, a plurality of "original elements" from the same or different "information sources" can be respectively modeled as a plurality of "unified elements" through a unified approach, so that the plurality of "unified elements" in the same operating environment can be compatible with each other to cooperatively perform a specific task; the "unification tool" and the "unification information unit" are implementation modes of the "unification element". Also, an "element transformer (matchizer)" described herein is a component, device, or program code to unify "original elements".

In an embodiment, the unification method includes the following steps: re-modeling (modeling) at least one raw information obtained from at least one of the plurality of sources into a unified information unit according to a unified data structure, and/or re-modeling at least one raw tool obtained from at least one of the plurality of sources into a unified tool according to another unified data structure; wherein the unified data structure and the another unified data structure can be the same or different, and the above-mentioned unified method can be accomplished by an element transformer (Matterizer).

Please refer to fig. 1, which is a conceptual diagram of an embodiment of a unification method. Fig. 1 illustrates that the element transformer 992 reforms an attribute and an associated nexus (link) of the primary element 991 according to the unified data structure 993 to model the primary element 991 as a unified element 994, such that the basic attributes of the unified element 994 include the type (type) of the primary element 994 and the nexus (link) indicating where the primary element 994 is located.

In the embodiment, the primitive element 991 at least includes a primitive message (not shown) or a primitive tool (not shown), but not limited thereto. Secondly, in the above unification method, when the attribute obtainable from the original information corresponds to the attribute to be unified in the unified information unit, the unified information unit can be directly generated through the element converter 992; when the attribute that can be obtained from the original information and the attribute that is to be unified in the unified information unit cannot correspond to each other, the original information needs to be redefined by logically reforming the attribute and the related link of the original information, so that the original information is converted into new original information having the attribute corresponding to the attribute that is to be unified in the unified information unit, thereby indirectly generating the unified information unit.

The type of the unified tool is used to define an element type, and the element type of the unified tool and the connection where the element type is located are used to obtain a physical element necessary for the external application, management or execution of the unified tool. When the original tool is compatible with the working environment of the workspace (workspace), the unified tool can be directly generated via the element transformer 992; when the original tool is not compatible with the working environment of the working space, the unified tool is generated indirectly by driving the original tool through a converter (adapter) and/or a Software Development Kit (SDK) of the original tool; wherein, the translator (adapter) is used to provide interface implementation (interface implementation) compatible with working space.

The "detailed implementation OF the normalization METHOD", "detailed obtaining manner OF the normalization element", AND "detailed operation manner OF the element converter" described in this embodiment can refer to the U.S. patent application with application number 14/324,069 AND name "a metal OF unity INFORMATION AND TOOL OF touch FROM a program OF public OF INFORMATION SOURCES", AND the chinese patent application with application number 201410768564.X AND name "METHOD for normalizing INFORMATION AND TOOLs FROM multiple INFORMATION SOURCES AND computer program product AND apparatus applying the METHOD", AND thus, the detailed description thereof is omitted here.

It is to be noted that the above-mentioned unification method is only one embodiment of the unification method adopted in the present invention. The method for unifying multiple original elements from different information sources is not limited to the above, and those skilled in the art can make any equivalent design changes according to the actual application requirements.

Two further unification methods different from the above description are exemplified below. The first unification method is an information unification method applied to Garmin satellite navigation, where a Point of Interest (POI) function of the Garmin satellite navigation is to perform a unification procedure on original landmark information (original information) input thereto through the information unification method to obtain corresponding unification landmark information (unification information unit); the second method is a tool unification method applied to an Android system, which is an open source code mobile device operating system based on Linux, but most of the applications (source tools) in the Android system are written in Java, so that all the applications (source tools) written in Java can be modeled into unified applications (unified tools) compatible with the Android system by the tool unification method, and further can be executed in the Android system.

The "workspace" refers to a workspace for at least one element converter and/or at least one tool and/or at least one information to interact with to perform a specific task, and at least one information and/or at least one tool can be input into the workspace through at least one element converter, but the manner of inputting information and/or tools into the workspace is not limited thereto; next, information input devices (information input devices) described below, such as the

information input devices

9881, 9882, and 9883 in fig. 2, the Dropbox input device 9761' in fig. 6, the YouTube input device 731, the Flicker input device 732, the face book input device 733, and the Dropbox input device 734 in fig. 10, are all embodiments of the element converter. Furthermore, the unified script is an intermediate language that can be used to implement the workspace, and the unified script can enable at least one element converter and/or at least one message and/or at least one tool to be provided (e.g., built-in or plug-in) to the workspace.

In one embodiment, the at least one message is at least one unified message unit formed by unifying at least one original message obtained from at least one message source, and the at least one tool is at least one unified tool formed by unifying at least one original tool obtained from at least one message source; the user can add (such as built-in or plug-in) the needed unified information unit and/or unified tool from the corresponding information source to the personal workspace according to different tasks, so the "workspace" can be a user-oriented "personal workspace".

Further, referring to fig. 2 and fig. 3, fig. 2 is a conceptual diagram of an implementation of an intermediate language for implementing a personal workspace by using a unified script, and fig. 3 is a schematic diagram of a preferred configuration of the personal workspace. Fig. 2 and 3 illustrate that the user combines the unified information unit 985 ' corresponding to the original information 985 in the Dropbox982, the first unified tool 986 ' corresponding to the compatible original tool 986 in the cloud hard disk 983, and the second unified tool 987 ' corresponding to the incompatible original tool 987 in the server 984 into the personal workspace 981 according to the task requirements; specifically, the user may first edit a unified script 980 as an intermediate language for implementing the personal workspace 981, and set (configure) the information input device 9881 of the Dropbox982, the information input device 9882 of the cloud hard disk 983, and the information input device 9883 of the server 984 by the unified script 980; the information input device 9881 can unify the original information 985 in the Dropbox982 into a unified information unit 985' and input the unified information unit to the personal workspace 981.

Fig. 2 and 3 also illustrate that the original tool stored in the cloud hard disk 983 is a compatible original tool 986, i.e., the compatible original tool 986 is compatible with the component architecture for the unified tool in the personal workspace 981, and the first unified tool 986' corresponding to the compatible original tool 986 can be provided directly to the personal workspace 981 through the information input device 9882 of the unified script 980.

Fig. 2 and 3 also illustrate that the original tool stored in the server 984 is an incompatible original tool 987, i.e., the incompatible original tool 987 is incompatible with the component architecture for the unified tool in the personal workspace 981, and a second unified tool 987' corresponding to the incompatible original tool 987 is provided to the personal workspace 981 through the compatible translator 989 and the information input device 9883 of the unified script 980.

Fig. 3 also illustrates that the user configures (e.g., groups or places) the unified information element 985 ', the first unifying tool 986 ', and the second unifying tool 987 ' in a specific area of the personal workspace 981 according to the actual application requirement; finally, the user can access or control the corresponding unified information unit by using the unified tool to execute the required task according to the operation relationship between the unified tool and the unified information unit (such as the click action or the drag action between the unified tool and the unified information unit).

The "specific implementation of the UNIFIED script as the intermediate language FOR realizing the PERSONAL WORKSPACE" and the "specific implementation of the user combining the required UNIFIED INFORMATION unit and/or the required UNIFIED tool from the corresponding INFORMATION into the PERSONAL WORKSPACE to execute the TASK according to the actual application requirements" IN the present embodiment can refer to the us patent application with application number 14/325,466 and named "METHOD FOR combining UNIFIED elements IN the PERSONAL WORKSPACE and the chinese patent application with application number 201410796528.4 and named" computer program product and system applying the METHOD ", and thus will not be described again here.

It should be noted that the personal workspace is only one embodiment of the workspace, and the workspace applicable to the present invention is not limited to the above. For example, a unified script as an intermediate language for implementing a workspace can be edited in advance to make the workspace become a workspace with a preset element converter and/or preset information and/or preset tools built therein, and such a workspace is not limited to a single user operation, and can be provided for multiple users to perform operations simultaneously or separately according to actual application requirements.

Furthermore, the workspace can be projected to any electronic device with computing capability, such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, etc. through a method of projecting a workspace, but not limited to the above, so that any user can operate the projected workspace on any electronic device with computing capability.

In one embodiment, a method of projecting a workspace comprises the following steps. First, a projectable space instance (projectable space instance) generated by the unified script is obtained via a Uniform Resource Identifier (URI). As previously described, a unified script is defined to configure at least one of the element transformer, the information, and the tool to build a workspace, and the projectable space entity is used to build a projected workspace corresponding to the workspace to provide an interface for operating at least one of the element transformer, the information, and the tool to perform a task; then, a projection means (projector) is used to interpret the projectable space entity and establish an operating environment for at least one of the element converter, the information and the tool to be configured in the projectable space entity, so as to further execute the projected workspace, thereby providing at least one user to interact with the projected workspace.

The projection means can be obtained from the remote data station, the projectable space entity or the preloaded application program, and loaded into an engine (engine) for providing a compatible environment to execute the projection means, and the engine can include, but is not limited to, Javascript engine, windows application program or Linux application program; furthermore, the unified script may be declared by a Document Type Definition (DTD), an extensible markup language schema (XML schema), a structured language (structured language) or a structured protocol (structured protocol), but not limited thereto; the projectable space entity may be an object (object), an extensible markup language (XML) file, or an entity (instance) generated by a structured language (structured language) or a structured protocol (structured protocol), but is not limited thereto.

Referring to fig. 4, fig. 5A, fig. 5B and fig. 6, fig. 4 is a schematic diagram illustrating an initial state of the method for projecting a workspace in accordance with a preferred embodiment, fig. 5A and fig. 5B are schematic diagrams illustrating an operation concept of the method for projecting a workspace in fig. 4, and fig. 6 is a schematic diagram illustrating a relative relationship between a projectable space entity in fig. 4 and a projected workspace in fig. 5B.

In the initial state shown in fig. 4, there are a first electronic device 971 and a second electronic device 972 that can be connected to each other (e.g., connected via a network), the first electronic device 971 stores a projectable space entity 973, and the second electronic device 972 has a built-in projection means 974.

In the present embodiment, the unified script 9731 is declared by a Document Type Definition (DTD) and is defined to configure at least one information input device (which is an implementation of an element transformer) and/or at least one unified information unit and/or at least one unified tool to build (model) a workspace, and the projectable space entity 973 is an extensible markup language (XML) generated entity, which is used to build (build) a projected workspace 976 corresponding to the workspace and is allowed to be added to or removed from the information input device and/or the unified information unit and/or the unified tool, as shown in fig. 6.

The projection means 974 of the second electronic device 972 establishes an operating environment 975 for the projected workspace 976 to operate on the second electronic device 972, and provides a micro kernel 977 (see fig. 6) for the operating environment 975 to load (e.g., query) at least one information input device and/or at least one unified information unit and/or at least one unified tool to be added to the projected workspace 976. When the second electronic device 972 obtains the projectable space entity 973 in the first electronic device 971 through a path connection message, the projection means 974 in the second electronic device 972 starts to interpret the projectable space entity 973 (as shown in fig. 5A). When the projectable space entity 973 is interpreted by the projection means 974, the projected workspace 976 is built on the job environment 975 according to the content interpreted by the projectable space entity 973 (as shown in fig. 5B). Thus, a user at the end of the second electronic device 972 can interact with the projected workspace 976 through the second electronic device 972 to perform related tasks.

The interrelationship of the unified script 9731, the projectable space entity 973, and the projected workspace 976 is further described below in the context of use shown in fig. 6. The use scenario illustrated in FIG. 6 is: a workspace is created that can be projected and read jpg picture files and gif picture files stored in a designated network space for a user to view, and in this use scenario, the unified script 9731 is declared as a Document Type Definition (DTD), and the projectable space entity 973 is generated in extensible markup language (XML).

Moreover, an information input device and a unification tool are added to the projectable space entity 973, and the information input device is used to input at least one unification information unit corresponding to the original information into the projected workspace 976; in the present use scenario, the information input device is a Dropbox input device, i.e. shown in the dashed box 9761 in fig. 6, and the original information includes a jpg picture file 9791, a jpg picture file 9792 and a gif picture file 9793 in a Dropbox 979 (information source), the unified information unit includes a unified jpg picture file 9791 ', a unified jpg picture file 9792 ' and a unified gif picture file 9793 ' described later, and the unified tool is a picture reader, i.e. shown in the dashed box 9762 in fig. 6, for reading the picture file input into the projected workspace 976.

As described above, the projected workspace 976 is established after the projectable space entity 973 is interpreted by the projection means 974 in the second electronic device 972. In the embodiment, a Dropbox input device 9761 '(corresponding to the illustrated dashed box 9761) and a picture reader 9762' (corresponding to the illustrated dashed box 9762) are disposed on the projected workspace 976, and the Dropbox input device 9761 'further unifies and inputs the jpg picture file 9791, the jpg picture file 9792 and the gif picture file 9793 in the Dropbox 979 into the projected workspace 6, so that the unified jpg picture file 9791', the unified jpg picture file 9792 'and the unified gif picture file 9793' corresponding to the jpg picture file 9791, the jpg picture file 9792 and the gif picture file 9793, respectively, are presented on the projected workspace 976. Then, when the user of the second electronic device 972 operates any one of the unified picture files 9791 ', 9792' and 9793 'through a specific operation manner (e.g., clicks on any one of the unified picture files 9791', 9792 'and 9793', or drags any one of the unified picture files 9791 ', 9792' and 9793 'to the picture reader 9762'), the picture reader 9762 'reads the content of the corresponding one of the unified picture files 9791', 9792 'and 9793' to be displayed for the user to view. The Dropbox input 9761 'and the picture viewer 9762' are loaded by the micro core 977 (equip).

Specifically, the path link information of the projectable space entity 973 may be Hyper Text Transfer Protocol (HTTP) path link information or File Transfer Protocol (FTP) path link information, and if the first electronic device 971 and the second electronic device 972 are a common device, the path link information of the projectable space entity 973 may also be local file path link information, but the type of the path link information is not limited thereto.

THE specific obtaining manner OF THE METHOD for PROJECTING THE working space described in this embodiment can refer to THE united states patent application with application number 14/577,772 and entitled "METHOD OF PROJECTING a working space AND SYSTEM USING THE SAME" and THE chinese patent application with application number 201410814138.5 and entitled "METHOD for PROJECTING THE working space and system USING THE METHOD for PROJECTING THE working space", and therefore will not be described herein again.

It should be noted that the method for projecting the workspace is only one projection method for projecting the workspace to any electronic device with computing capability, but the projection method for projecting the workspace to any electronic device with computing capability is not limited to the above, and those skilled in the art can make any equivalent design changes according to the actual application requirements. Moreover, since any workspace can be projected onto any electronic device with computing capability, any workspace can be regarded as a workspace that can be transmitted (delivery) to any electronic device with computing capability, and thus the workspace can also be a working platform for multiple workers to work in cooperation.

Regarding the specific implementation of cooperative work through a workspace, refer to the chinese patent application with application number 201510003717.6 entitled "NETWORKING cooperative work METHOD and machine applying the METHOD", and refer to the PCT international patent application with application number PCT/CN2015/083179 and name "network coordination METHOD AND MACHINE USING sun METHOD", which require priority of the chinese patent application with application number 201510003717.6, and are not described herein again.

In view of the continuous expansion of the internet, the applications and products of the internet are increasing, for example, the work spaces created by the user or the work spaces created by other people and projected onto the user's machine through the path link information will be more and more, so that the user also needs to pay attention to the maintenance and management, for example, the path link information of the projectable space entity belonging to each work space must be remembered or stored to be operated again afterwards, which obviously causes inconvenience again. Accordingly, the present invention provides a method for asset management to overcome the above-mentioned drawbacks.

For convenience of describing the method for managing assets according to the present invention, the aforementioned "workspace" and its corresponding "projected workspace" are both referred to as a "transportable workspace (deliverable workspace)" in the following description.

Please refer to fig. 7, which is a flowchart illustrating a method for managing assets according to a preferred embodiment of the present invention. The method for managing assets comprises: a projectable space entity is provided and used to build (model) a total management system (home system). When a user obtains the projectable space entity, the projectable space entity is interpreted by a projection means, so that a projected header system corresponding to the header system is established for the user to access (access) at least one property. The method described in fig. 7 is further explained below with reference to fig. 8 to 10.

Referring to fig. 8 and fig. 9A and 9B, fig. 8 is a schematic diagram of an asset management system and a machine applying the method for managing assets of fig. 7, and fig. 9A and 9B are schematic diagrams of a relative relationship between the projectable space entity and the projected total management system shown in fig. 8. It is noted that the central management system can also be regarded as an implementation of "workspace" for the user 21 to access the assets after being projected to the machine 31 of the user 21, and the projectable space entity 41 for building the central management system has a plurality of unified elements 6 built therein and is installed in the asset management system 1.

In particular, when the user 21 wants to access his/her assets, it can proceed by activating the master management system. For example, the user 21 may first load the projectable space entity 41 provided in the asset management system 1 into his/her own machine 31. At this time, the projection means 5 in the machine 31 establishes a working environment 51 for the projected mains system 42 to operate on the machine 31, and provides a micro core 52 corresponding to the projected mains system 42 to load (acquiring) the uniform elements 6 configured in the projectable spatial entity 41. After the machine 31 loads the projectable space entity 41, the projection means 5 starts to interpret the projectable space entity 41. After the projectable space entity 41 is interpreted by the projection means 5, the projected manifold system 42 is built on the working environment 51 of the machine 31 according to the content interpreted by the projectable space entity 41. At this point, the action of starting the main pipe system is completed. In addition, the machine 31 of the user 21 includes, but is not limited to, a computer (e.g., a desktop computer, a notebook computer, or a tablet computer), a portable electronic device (e.g., a smart phone, a personal digital assistant, a wearable device), or any internet-enabled device.

The user 21 may load the projectable space entity 41 into the machine 31 by opening the browser (browser)211 of the machine 31 and inputting the path connection information of the projectable space entity 41, or may obtain the projectable space entity 41 or the path connection information thereof by opening the browser (browser)211 of the machine 31 and logging in the asset management system 1; however, the manner of loading the projectable spatial entity 41 into the machine 31 is not limited to the above, and those skilled in the art can make any equivalent design changes according to the actual application requirements.

In the preferred embodiment, the projectable space entity 41 is an entity instantiated by an extensible markup language (XML). The compiled content of the projectable space entity 41 and its correspondence with the projected mains system 42 are shown in fig. 9A and 9B. In fig. 9A and 9B, both ends of either dashed line illustrate the compiled content of the associated projectable spatial entity 41 and the corresponding unification element 6. For example, a first part 61 of the unified elements 6 constitutes a cloud desktop (cloud desktop)71, a second part 62 of the unified elements 6 constitutes a workspace creator (workspace creator)72, a third part 63 of the unified elements 6 constitutes a service management unit (service manager)73, and a fourth part 64 of the unified elements 6 constitutes a relationship management unit (relationship manager)74, and the related cloud desktop 71, workspace creator 72, service management unit 73, and relationship management unit 74 will be illustrated later in fig. 10. However, the unified element 6 disposed in the projectable space entity 41 is not limited to the above, and one skilled in the art can dispose the required unified element 6 in the projectable space entity 41 according to the actual application requirement.

Furthermore, in the preferred embodiment, either the transferable workspaces created by the user 21 themselves, or the transferable workspaces created by other users received by the user 21 via the corresponding path link information, are considered "assets" of the user 21, so that the user 21 can manage these transferable workspaces via the projected mainframe system 42 established on their machine 31. However, the assets accessible by activating the master management system are not limited to the working space available for transmission, and those skilled in the art can make any equivalent design changes according to the actual application requirements.

Please refer to fig. 10, which is a conceptual diagram illustrating an operation of the cloud desktop shown in fig. 9B. After the projected central management system 42 is built on the machine 31, the projected central management system 42 is presented on the browser 211 in the form of a cloud desktop 71 to serve as an operation interface of the user 21, and the cloud desktop 71 displays the cloud desktop 71, the workspace creator 72, the service management unit 73 and the relationship management unit 74 for the user 21 to operate. The workspace creator 72 is used for the user 21 to create (create) a transferable workspace 81, the service management unit 73 is used for the user 21 to unify tools and/or information from different information sources into unified tools and/or unified information, and then add the unified tools and/or unified information into the cloud desktop 71 or transferable workspaces 81 and 82 managed by the host management system, and the relationship management unit 74 is used for the user 21 to manage, aggregate (aggregate) or access personal relationships (relationship).

In the present embodiment, either the transferable workspace 81 created by the user 21 itself or the transferable workspace 82 created by another user, which is received by the user 21 via the corresponding path link message, can be stored in the cloud desktop 71. Moreover, the transferable workspaces 81 and 82 stored in the cloud desktop 71 are displayed by the

icons

711 and 712, so that the user 21 can enter the transferable workspaces 81 and 82 and operate the transferable workspaces by operating the

icons

711 and 712 in a specific manner (e.g., clicking). That is, after the transferable workspace 82 is stored in the cloud desktop 71, the user 21 can enter the transferable workspace 82 and perform operations without searching for path connection information corresponding to the transferable workspace 82.

In the preferred embodiment, the service management unit 73 displayed on the cloud desktop 71 includes a YouTube input device 731, a Flicker input device 732, a Facebook (Facebook) input device 733, and a Dropbox input device 734, so that the user 21 can add the audio/video data in the YouTube web service platform to the cloud desktop 71 or any transferable working space 81, 82 through the YouTube input device 731 according to the actual operation requirement, the image data in the Flicker web service platform can be added to the cloud desktop 71 or any transferable working space 81, 82 through the Flicker input device 732, the information in the facebook service platform can also be added to the cloud desktop 71 or any transferable working space 81, 82 through the facebook input device 733, the data stored in the Dropbox web services platform can also be added to the cloud desktop 71 or any transferable workspaces 81, 82 via the Dropbox input 734. However, the element transformer that the service management unit 73 can include is not limited to the above, and one skilled in the art can configure the required element transformer in the projectable space entity 41 according to the actual application requirement.

In the preferred embodiment, the relationship management unit 74 displayed on the cloud desktop 71 includes a friend list 741. The user 21 can invite another person to become a friend on the friend list 741, and can add any member of any transferable workspace 81 and 82 to the friend list 741, so that the user 21 can manage, gather or access his/her personal relationships. Preferably, but not limited to, the projected master management system 42 further provides the user 21 with a friend on the friend list 741 for text communication, voice communication or video communication. However, the implementation of the relationship management unit 74 is not limited to the above, and those skilled in the art can make any equivalent design changes according to the actual application requirements.

It should be noted that the asset management system of the present invention may be a personal device for personal use, or may be a device for carrying a network service platform to provide network services, for example, it may be a commercial device, a cell-owned device or a non-profit device. Please refer to fig. 11, which is a schematic diagram of an asset management system as a device for carrying a network service platform according to the present invention. FIG. 11 illustrates a web services platform 11 carried by an asset management system 1' that

users

21a, 21b may access using

browsers

211a, 211b of their

machines

31a, 31b, respectively. After the

users

21a, 21b register or apply for the account of the network service platform 11, they can create their own host systems 43a, 43b to manage their assets.

Projectable space entities

41a, 41b for building the main management systems 43a, 43b, respectively, are provided in the asset management system 1'. In addition, the account data registered or applied by the

users

21a, 21b are also recorded in the asset management system 1'. However, the descriptions of how the

users

21a, 21b access their assets after creating their host systems 43a, 43b are the same as the previous descriptions, and are not repeated herein.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the claims, therefore, all equivalent changes and modifications without departing from the spirit of the present invention should be included in the scope of the present invention.

Claims

1. A method of managing assets, comprising the steps of:

providing a projectable space entity, wherein the projectable space entity is used for configuring a plurality of uniform elements therein, each uniform element is formed by unifying an original element acquired from at least one information source through at least one element converter, at least part of the uniform elements is used for forming a cloud desktop, a working space creator, a service management unit and/or a relationship management unit, at least one uniform element comprises at least one uniform tool, and the at least one uniform tool is modeled from at least one original tool of at least one information source; and

when a machine obtains the projectable space entity, the projectable space entity is interpreted by a projection means so that a projected main system corresponding to the main system is established, and the projected main system is loaded with the plurality of unified elements for a user to access at least one asset.

2. The method of claim 1, wherein the machine obtains the projectable space entity via a path link message and/or a login procedure of the user.

3. The method as claimed in claim 1, wherein the projectable spatial entity has a plurality of unified elements built therein for building the overall system.

4. The method of claim 3, wherein the at least one primitive tool is modeled as a unified tool by at least one primitive translator that reforms attributes and associated links of the primitive tool according to a unified data structure.

5. The method of claim 4, wherein the user accesses the at least one asset via the cloud desktop.

6. The method for managing assets of claim 4 wherein the workspace creator provides the user with a transferable workspace.

7. The method as claimed in claim 4, wherein the service management unit comprises at least one element converter, and the at least one element converter is used to input at least one normalization tool and/or at least one normalization information unit into the header system and/or the at least one asset.

8. The method of claim 7, wherein the at least one original tool corresponding to the at least one unification tool comprises a utility, an interface tool set, an agent, an application, a service tool, or any executable accessible on a related machine or a server; and/or, the at least one original message corresponding to the at least one unified message unit comprises a document, a web page, a database, a policy, a rule, an operation specification, or any message accessible to a related machine or a server.

9. The method as claimed in claim 4, wherein the relationship management unit is used for the user to manage, aggregate or access an interpersonal relationship.

10. The method of claim 1, wherein the at least one asset comprises a transportable workspace created by another projectable spatial entity, and the another projectable spatial entity has at least one unified element added to or removed from it.

11. The method for managing assets of claim 10 wherein the unifying tool is generated directly via the element translator when an original tool is compatible with an operating environment of a workspace; when the original tool is not compatible with the working environment of the working space, the unified tool is indirectly generated by driving the original tool through a converter and/or a software development kit of the original tool.

12. The method of claim 1, wherein the casting agent is loaded into an engine, and the engine is configured to provide a compatible environment for executing the casting agent.

13. The method of claim 1, wherein the projectable spatial entity is an object, an extensible markup language file, or an entity generated in a structured language or a structured protocol.

14. An asset management system, providing a projectable spatial entity for configuring a total management system to a machine, wherein the projectable spatial entity is configured for a plurality of unified elements to be configured therein, each of the unified elements is formed by unifying an original element obtained from at least one information source through at least one element converter, at least part of the unified elements is used for forming a cloud desktop, a workspace creator, a service management unit and/or a relationship management unit, at least one unified element comprises at least one unified tool, and the at least one unified tool is modeled from at least one original tool of at least one information source; when the machine obtains the projectable space entity, the projectable space entity is interpreted by a projection means so as to establish a projected main management system corresponding to the main management system, and the projected main management system is used for loading the plurality of unified elements for a user to access at least one asset.

15. The asset management system of claim 14, wherein said machine obtains said projectable space entity via a path link message and/or a log-in procedure of said user.

16. The asset management system of claim 14, wherein said projectable spatial entity has a plurality of unified elements built therein for building said master management system.

17. The asset management system of claim 16, wherein said at least one primitive tool is modeled as a unified tool by at least one primitive translator that reforms attributes and associated links of said primitive tool according to a unified data structure.

18. The asset management system of claim 17, wherein said user accesses said at least one asset via said cloud desktop; or the workspace creator provides the user with a transferable workspace; or the service management unit comprises at least one element converter, and the at least one element converter is used for inputting at least one unification tool and/or at least one unification information unit into the main management system and/or the at least one asset through the at least one element converter; or the relationship management unit is used for the user to manage, gather or access an interpersonal relationship.

19. The asset management system of claim 14, wherein said at least one asset comprises a transportable workspace created by another projectable spatial entity, and said another projectable spatial entity has at least one unified element added to or removed from it.

20. The asset management system of claim 19, wherein said unifying tool is generated directly via said element translator when an original tool is compatible with the operating environment of the workspace; when the original tool is not compatible with the working environment of the working space, the unified tool is indirectly generated by driving the original tool through a converter and/or a software development kit of the original tool.

21. The asset management system of claim 14, wherein said projectable spatial entity is an object, an extensible markup language file, or an entity generated in a structured language or a structured protocol.

22. A method of managing assets, comprising the steps of: obtaining a projectable spatial entity for constructing a total management system, wherein the projectable spatial entity is configured with a plurality of uniform elements, each uniform element is formed by unifying an original element acquired from at least one information source through at least one element converter, at least part of the uniform elements are used for forming a cloud desktop, a workspace creator, a service management unit and/or a relationship management unit, the at least one uniform element comprises at least one uniform tool, and the at least one uniform tool is modeled from at least one original tool of at least one information source; and

the projectable space entity is interpreted by a projection means, so that a projected main system corresponding to the main system is established, and the projected main system loads the plurality of uniform elements to access at least one asset.

23. The method of claim 22, wherein the projectable spatial entity is obtained by a machine via a path link message and/or a user login procedure; and/or the projectable space entity is an object, an extensible markup language file, or an entity generated by a structured language or a structured protocol; and/or the projection means is loaded into an engine, and the engine is used for providing a compatible environment to execute the projection means.

24. The method as claimed in claim 22, wherein said projectable spatial entity has a plurality of unified elements built therein for building said overall system.

25. The method of claim 24, wherein the at least one primitive tool is modeled as a unified tool by at least one primitive translator that reforms attributes and associated links of the primitive tool according to a unified data structure.

26. The method of claim 25, wherein a user accesses the at least one asset via the cloud desktop.

27. The method for managing assets of claim 25 wherein the workspace creator provides a user with the creation of a transferable workspace.

28. The method as claimed in claim 25, wherein the service management unit includes at least one element translator, and the at least one element translator is configured to input at least one unification tool and/or at least one unification information unit into the head pipe system and/or the at least one asset.

29. The method of claim 28, wherein the at least one original tool corresponding to the at least one unification tool comprises at least one of a utility, an interface tool set, an agent, an application, a service tool, or any executable element accessible to a related machine and a server; and/or, the at least one original message corresponding to the at least one unified message unit includes at least one of a document, a web page, a database, a policy, a rule, an operation specification, and any data accessible to a related machine or a server.

30. The method for managing assets of claim 25 wherein the relationship management unit provides a user with management, aggregation or access to an interpersonal relationship.

31. The method of claim 22, wherein the at least one asset comprises a transportable workspace created by another projectable spatial entity, and the another projectable spatial entity has at least one unified element added to or removed from it.

32. The method for managing assets of claim 31 wherein the unifying tool is generated directly via the element translator when an original tool is compatible with an operating environment of a workspace; when the original tool is not compatible with the working environment of the working space, the unified tool is indirectly generated by driving the original tool through a converter and/or a software development kit of the original tool.

33. A machine, it is for a projection means to load into it, and is used for obtaining a projectable space entity used for setting up a total management system, wherein, the projectable space entity is for a plurality of unification elements to dispose among them, and each one of the unification elements is that an original element got from at least one information source is formed after being unified by at least one element converter, at least some in a plurality of unification elements are used for making up a cloud end desktop, a workspace creator, a service management unit and/or a relation management unit; wherein, the projection means obtains the projectable space entity at the machine and the projectable space entity is interpreted to enable a projected main system corresponding to the main system to be established on the machine, and the projected main system loads the plurality of uniform elements for a user to access at least one asset.

34. The machine of claim 33, wherein the machine obtains the projectable spatial entity via a path link message and/or a login procedure of the user; and/or the projectable space entity is an object, an extensible markup language file, or an entity generated by a structured language or a structured protocol; and/or the projection means is loaded into an engine, and the engine provides a compatible environment to execute the projection means.

35. The machine of claim 33, wherein the projectable spatial entity has a plurality of unified elements built therein for building the header system.

36. The machine of claim 35, wherein the at least one primitive tool is modeled as a unified tool by at least one primitive translator that reforms attributes and associated links of the primitive tool according to the unified data structure.

37. The machine of claim 36, wherein the user accesses the at least one asset via the cloud desktop; or the workspace creator provides the user with a transferable workspace; or the service management unit comprises at least one element converter, wherein at least one unification tool and/or at least one unification information unit are input into the main pipe system and/or the at least one asset through the at least one element converter; or the relationship management unit is used for the user to manage, gather or access an interpersonal relationship.

38. The machine of claim 33, wherein the at least one asset comprises a transportable workspace created by another projectable spatial entity, and the another projectable spatial entity has at least one unified element added to or removed from it.

39. The machine of claim 38, wherein the unified tool is generated directly via the element converter when an original tool is compatible with a working environment of a workspace; when the original tool is not compatible with the working environment of the working space, the unified tool is indirectly generated by driving the original tool through a converter and/or a software development kit of the original tool.