JP2018502384A - How to delay ID binding to an account - Google Patents

Abstract

The present invention provides a method for delaying the binding of an ID to an account. The method includes the following steps. First, an instance of a projectable space used to build a workspace is provided to the system, and an information input device, information and / or tools are arranged in the projectable space instance. The workspace is then projected to the machine and a user account is provided, the user is allowed to access the projected workspace, and the user is authorized to log in to the projected workspace. The user account is automatically generated by the system under conditions that do not provide an ID. When the user accesses the projected workspace to drive the information input device, the information, and / or the tool, the user provides an authorized ID and the authorized ID for the user account The steps that are required to be bound. Subsequently, the user is permitted to log in to the projected workspace by the authorized ID bound to the user account. [Selection] Figure 7

Description

  The present invention relates to a method for delaying the binding of an ID to an account.

  In today's digital life, it is important to use various network service platforms. This is because network service platforms allow people to build new contact information and share information over the Internet. Due to the fact that it is designed to do. Many network service platforms that provide services and application programs are currently well developed, but many such as online shopping platforms (eg, eBay) and social networking sites (eg, Facebook, Twitter, Plurk, Google+) The network service platform requires that the user complete the account registration process first, and the user can acquire and use the services and functions provided by the network service platform after completing the account registration. It becomes possible.

  Many conventional network service platforms (for example, Google, Opera, Facebook, etc.) are accessible after the user registers a user account. Conversely, if the user has not registered or authorized the user account, the user cannot view the content or use the provided service. Some network service platforms cannot use a specific program or read a specific sentence unless the user first evaluates it like it or provides personal information. In some cases, users may not understand or trust these network service platforms. For example, if the user wants to share a psychological test game with a friend using Facebook, and the user's friend is also interested in the psychological test game, first press “Like” on the psychological test game on Facebook, It must be allowed to provide personal information to the psychological test game program. Also, it is currently possible for a user of a conventional network service platform (for example, Facebook) to enable a specific function (for example, a specific function of Facebook) to be used by friends of a different network service platform (for example, Twitter). Unauthorized.

  Therefore, there is a need for a network service platform that allows users to access services and functions without first performing account registration work. In addition, services (for example, contents) and functions provided by the network service platform are required to be shared by users of other network service platforms.

  In order to solve the conventional problems as described above, the present invention provides a method for delaying the binding of an ID to an account. If a current general user uses various conventional network service platforms, all of the network service platforms require the user to register a user account. Accounts are automatically provided and users can access services and functions provided by the network service platform without user account registration. Furthermore, the service (for example, contents) and functions provided by the network service platform can be shared by users of other network service platforms.

  The method for delaying the binding of an ID to an account of the present invention includes the following steps. First, a projectable space instance used to build a workspace is provided to the system, and an information input device, information and / or tools are arranged in the projectable space instance. Next, the workspace is projected onto the machine and a user account is provided, the user is allowed to access the projected workspace, and the user is allowed to log in to the projected workspace. The user account is automatically generated by the system under the condition that no ID is provided. When the user accesses the projected workspace to drive the information input device, the information, and / or the tool, the user provides an authorized ID and the authorized ID for the user account And the access authority to the information input device, the information and / or the tool is validated. The authorized ID bound to the user account is then allowed the user to log into the projected workspace from the machine or another machine.

  In a specific embodiment, the system includes a server, and an instance of the projectable space is provided to the server, and the user does not provide an authorized ID for logging into the projected workspace. Under conditions, the user account is automatically generated by the server.

  In a specific embodiment, the information input device is used to provide the information and / or the tool to the projected workspace.

  In a specific embodiment, the information is a unified information unit formed after the original information obtained from the information source is unified, and / or the tool is unified with the original tool obtained from the information source. It is a unified tool that was formed after

  In a specific embodiment, the original information is modeled as the unified information unit based on a unified data model and / or the original tool is modeled as the unified tool based on another unified data model. The

  In a specific embodiment, the information source is a network service platform.

  In a specific embodiment, the method of delaying ID binding to an account further comprises the machine locking the user account by binding the user account to the machine code of the machine.

  In a specific embodiment, the machine code is a code used to identify the machine.

  In a specific embodiment, the method of delaying ID binding to an account further includes the step of recording the user's usage history in the projected workspace.

  In a specific embodiment, the usage history is recorded on a storage medium accessible to the projected workspace.

  In a specific embodiment, the storage medium is a browser cookie, browser cache or file.

  In a specific embodiment, the usage history includes browsing history, operation execution logs and / or information records used for rational analysis of the user's preferences.

  In a specific embodiment, the projected workspace tracks the usage history of the user based on the user account.

  In a specific embodiment, the projected workspace tracks and analyzes the usage history of the user and provides services and / or content to the user.

  In a specific embodiment, a method for delaying the binding of an ID to an account is used to indicate the user account that is automatically generated and provided with a label under certain conditions, Creating a name and character as desired by the user and providing access to the projected workspace by the machine using the name and character without providing the authorized ID; Including.

  In a specific embodiment, the content of the label includes a real name or a pseudonym provided by the user and is used to indicate the user account.

  In a specific embodiment, the user is permitted to provide a plurality of authorized IDs that are bound to the user account and are authenticated for binding, and any of the authorized IDs One of these is a service object that can be identified by the projected workspace.

  In a specific embodiment, when the user logs in to the projected workspace from the other machine with the authorized ID bound to the user account, the projected workspace tracks the user account. Is done.

  In a specific embodiment, the user account is automatically generated by the system when the user first accesses the projected workspace.

  In a specific embodiment, a method for delaying the binding of an ID to an account allows the system to automatically generate other user accounts and provide them to other users, and for the other user's The existing ID is bound to the other user account and the binding is authenticated, and the other user account shares the projected workspace to the other user by the user who has accessed the projected workspace. Or generating when the other user is invited to the projected workspace.

  In a specific embodiment, the projectable space instance is an instance created with an object, an extensible markup language or a structured language or structured protocol.

  The present invention further provides a computer program product used to delay binding of an ID to an account. The computer program product includes program code. The program code performs the following steps when the computer program product is executed by a computer. First, a projectable space instance used to build a workspace is provided to the system, and an information input device, information and / or tools are arranged in the projectable space instance. Next, the workspace is projected onto the machine and a user account is provided, the user is allowed to access the projected workspace, and the user is allowed to log in to the projected workspace. The user account is automatically generated by the system under the condition that no ID is provided. When the user accesses the projected workspace to drive the information input device, the information, and / or the tool, the user provides an authorized ID and the authorized ID for the user account And the access authority to the information input device, the information and / or the tool is validated. Then, the authorized ID bound to the user account allows the user to log in to the projected workspace from the machine or other machine.

  The above objects and advantages of the present invention can be understood more clearly by those skilled in the art with reference to the following detailed description and drawings.

It is the schematic of the implementation concept of the unification method in embodiment. FIG. 2 is a schematic diagram of a preferred concept that uses a unified script as an intermediate language for realizing a personal workspace. FIG. 3 is a schematic diagram of a preferred arrangement of the personal workspace shown in FIG. It is the schematic of the initial state of the projection method of the workspace in preferable embodiment. It is the schematic of the operation | use concept of the projection method of the workspace shown in FIG. It is the schematic of the operation | use concept of the projection method of the workspace shown in FIG. FIG. 5 is a schematic diagram of the relative relationship between the projectable space instance shown in FIG. 4 and the projected workspace shown in FIG. 5B. 6 is a flowchart of a preferred method for delaying ID binding to an account according to the present invention. FIG. 8 is a schematic diagram of a concept applying the mechanism of the method shown in FIG. 7 in a preferred embodiment. FIG. 9 is a schematic diagram of a preferred concept in which the user first accesses the projected workspace in the method shown in FIG. 7 and the mechanism shown in FIG. FIG. 9 is a schematic diagram of a preferred concept in which the user accesses the projected workspace again in the method shown in FIG. 7 and the mechanism shown in FIG. FIG. 2 is a schematic diagram of a preferred concept for providing and displaying labels for automatically generated user accounts. FIG. 9 is a schematic diagram of a preferred concept of a method for performing mutual authentication by binding a user account to another network service platform by applying the method shown in FIG. 7 and the mechanism shown in FIG. 8. FIG. 6 is a schematic diagram of a preferred concept for performing authentication by binding a user account corresponding to a projected workspace to Facebook. 4 is a flowchart of a preferred method for automatically generating a user account of a content recipient by sharing content according to the present invention. FIG. 8 is a block schematic diagram of a computer program product applying the method shown in FIG. 7 in a preferred embodiment.

  The present invention facilitates a more complete understanding with the following description, including examples of the following terms and conclusions. For the sake of brevity, in this specification, publications containing the published content of the invention are cited in the text for reference.

  In the following, embodiments of the present invention are not limited and only show various aspects and features of the present invention. Regarding the technical significance that is most restricted, the “information source” described in the text refers to an order of codes that are translated into useful information, and the useful information is used for organizing and labeling information. Information sources include websites (eg, Internet services), intranets, social networks, software, e-books, databases, and other information media (eg, recording media used for non-transitory computers, recording media for mobile devices) ). The “original information” described in the text includes files, web pages, databases, policies, rules, or any information that can be accessed by related machines and servers. The “original tool” described in the main text is a utility program. , Widgets, intelligent agent tools, application programs, service tools, or any executable element accessible to the associated machine and server. However, the information source, the original information, and the original tool are not limited to those described above.

  Note that both “original information” and “original tool” are embodiments of the “original element” described in the text, and in the practice of the present invention, a plurality of “original sources” from the same or different “information sources” are used. The “elements” are all modeled into a plurality of “unified elements” through a unified method, and a plurality of “unified elements” are all compatible with each other in the same work environment, and can perform a specific task in cooperation. Both the “unified tool” and the “unified information unit” are embodiments of the “unified element”. In addition, the “materializer” described in the text is a member, device, or program code that unifies the “original element”.

  In one embodiment, the above-described unification method is configured such that original information acquired from at least one information source of a plurality of information sources is reorganized based on a unified data model, so that the original information is modeled into a unified information unit. The original tool is modeled into a unified tool by reorganizing the original tool obtained from at least one information source of the plurality of information sources based on other unified data models. The unified data model and the other unified data model are the same or different, and the above unified method is completed by a materializer.

  FIG. 1 is a schematic diagram of an implementation concept of the above-described unified method in the embodiment. In FIG. 1, the materializer 992 reorganizes the attributes and related links of the original element 991 based on the unified data model 993, the original element 991 is modeled as the unified element 994, and the basic attributes of the unified element 994 are the original elements. It includes a link that displays the type and location of the original element.

  In this embodiment, the original element 991 includes at least original information (not shown) or original tool (not shown), but is not limited thereto. Next, in the above-described unified method, when the attribute acquired from the original information corresponds to the attribute unified in the unified information unit, the unified information unit is directly generated by the materializer 992. If the attributes obtained from the original information do not correspond to the attributes unified in the unified information unit, the original information is redefined by first performing a logical reorganization on the attributes and related links of the original information. The original information is converted into new original information whose attributes correspond to the attributes unified in the unified information unit, and the unified information unit is indirectly generated.

  When the original tool is compatible with the work environment of the workspace, the unified tool is directly generated by the materializer 992. If the original tool is not compatible with the work environment of the workspace, the original tool is driven by the adapter and / or the original tool software development kit (SDK) to indirectly generate the unified tool. The adapter also provides an interface implementation that is compatible with the workspace.

  “Specific implementation method of unified method”, “specific acquisition method of unified element”, and “specific operation method of materializer” according to the present embodiment are described in “A” of US patent application No. 14/324669. “METHOD OF UNIFYING INFORMATION AND TOOL FROM A PLURALITY OF INFORMATION SOURCES” and Chinese Patent Application No. 201410768564. Reference is made here to the X issue of “Methods and Methods for Unifying Information and Tools from Multiple Information Sources, and Computer Program Products and Apparatus Applying the Methods”, and will not be reiterated here.

  Incidentally, the above-described unification method is only an embodiment of the unification method adopted by the present application, and the method of unifying a plurality of original elements of different information sources is not limited to the above. Anyone skilled in the art can make any design change that has the same effect according to actual demand.

  Below, two unification methods different from the above-mentioned explanation are illustrated. The first unifying method is a data unifying method applied to Garmin's satellite navigation, and the point of interest (POI) function of Garmin's satellite navigation is input therein by the unifying data method. Corresponding unified spot information (unified information unit) is acquired by executing a unified process on the original spot information (original information). The second method is a tool unification method applied to an Android (Android) system. The Android system is an open source mobile operating system based on Linux (registered trademark), however, many of the application programs (original tools) in the Android system are programmed with Java (registered trademark). All application programs (original tools) programmed with the registered trademark are modeled into a unified application program (unified tool) that is compatible with the Android system by the tool unifying method, and can be executed on the Android system.

  Further, as used herein, “workspace” refers to a workspace for performing a specific task by interactively operating at least one materializer and / or at least one tool and / or at least one information, and At least one information and / or at least one tool is input into the workspace by at least one materializer, however, the method of inputting information and / or tools into the workspace is not limited thereto. Next, the following information input devices (information input devices 9881, 9882, and 9883 in FIG. 2, Dropbox (registered trademark) information input device 9761 ′ in FIG. 6 and information input device 760 in FIG. 13) are all materializers. This is an embodiment. The “unified script” described in the text refers to an intermediate language for realizing a workspace, and at least one materializer and / or at least one information and / or at least one by the “unified script”. Tools are provided in the workspace (eg built-ins and plug-ins).

  In one embodiment, the at least one information is at least one unified information unit formed after at least one original information obtained from at least one information source is unified, and the at least one information The tool is at least one unified tool formed after at least one original tool obtained from at least one information source is unified. Based on the different tasks, the user adds the necessary unified information units and / or unified tools from the corresponding information source (eg, built-in or plug-in) into the personal workspace. Therefore, the “workspace” is a user-oriented “personal workspace”.

  More specifically, refer to FIG. 2 and FIG. 3, which is a schematic diagram of a preferred concept of using a unified script as an intermediate language for realizing a personal workspace, and FIG. 3 is a personal work shown in FIG. FIG. 6 is a schematic view of a preferred arrangement of spaces. 2 and FIG. 3 show a unified information unit 985 ′ corresponding to the original information 985 in the Dropbox 982, a first corresponding to the compatible original tool 986 in the cloud storage 983 according to the user's task needs. The combination of a unified tool 986 ′ and a second unified tool 987 ′ corresponding to the incompatible original tool 987 in the server 984 is illustrated in the personal workspace 981. More specifically, the user first edits the unified script 980 as an intermediate language for realizing the personal workspace 981, and the unified script 980 uses the information input device 9881 of the Dropbox 982, the information input device 9882 of the cloud storage 983, and The information input unit 9883 of the server 984 is set. The original information 985 in the Dropbox 982 is unified into the unified information unit 985 ′ by the information input device 9881 and inputted to the personal workspace 981.

  2 and 3 are original tools 986 in which the original tool stored in the cloud storage 983 is compatible (ie, the compatible original tool 986 is unified in the personal workspace 981). A first unified tool 986 'corresponding to the original tool 986 compatible with the unified script 980 (in which the information input device 9882 is utilized) Shown provided in workspace 981.

  2 and 3 are the original tool 987 in which the original tool stored in the server 984 is incompatible (ie, the incompatible original tool 987 is a unified tool in the personal workspace 981). And a second unified corresponding to the original tool 987 that is incompatible with the unified script 980 (in which the compatible adapter 989 and the information input unit 9883 are used). It illustrates that a tool 987 ′ needs to be provided in the personal workspace 981.

  In FIG. 3, the user arranges 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 actual application needs. To do. Finally, the user accesses or corresponds to the corresponding unified information unit using the unified tool according to the operational relationship between the unified tool and the unified information unit (for example, click operation or drag operation between the two). The necessary tasks are executed by controlling.

  In this embodiment, “a specific implementation method in which a unified script is used as an intermediate language for realizing a personal workspace”, “a unified information unit and / or a necessary information required by a user according to actual application needs” “A specific implementation method for performing tasks by freely combining unified tools into a personal workspace based on corresponding information sources” is “METHOD FOR PERFORMING TASK ON UNIFIED INFORMATION” in US patent application Ser. No. 14/325466. “UNITS IN A PERSONAL WORKSPACE” and Chinese Patent Application No. 20141079658.4, “A Method for Combining Unified Elements in a Personal Workspace, and Computer Program Product and System Applying the Method” In order to refer to the document “Stem”, the detailed description is omitted here.

  Incidentally, the above-described personal workspace is only an embodiment of the workspace, and the workspace applied to the present invention is not limited to the above. For example, a unified script as an intermediate language for realizing a workspace is edited in advance, and the workspace becomes a workspace in which a default materializer and / or default information and / or a default tool is built-in. Such a workspace is not limited to use by a single user, but can be accessed by multiple users simultaneously or separately depending on the demands of the actual application.

  In addition, the “workspace” described in the text includes any electronic device (for example, a mobile phone, a tablet, a notebook computer, a desktop computer, etc.) that has a calculation ability according to the “workspace projection method”, but is not limited thereto. Not) and any user can access the “projected workspace” on any electronic device that has computing power.

  In one embodiment, the workspace projection method first obtains an instance of a projectable space in which a unified script is generated by a unified resource identifier (URI). A unified script is defined such that a workspace constructed by at least one of a materializer, information, and tools is located (eg, as described above), and an instance of a projectable space corresponds to a workspace Used to build a projected workspace and includes providing an interface that can perform tasks by accessing at least one of a materializer, information, and tools. A projector is then utilized to analyze the projectable space instance, and a work environment is constructed in which at least one of the materializer, information, and tools is located in the projectable space instance, and the projection is performed. The executed workspace is executed, whereby at least one user and the projected workspace are interactively operated.

  The projector is obtained from a remote data station, an instance of a projectable space or a preloaded application program and loaded into an engine for running the projector providing a compatible environment. Examples of the engine include a Java (registered trademark) script engine, a Windows (registered trademark) application program, or a Linux (registered trademark) application program, but are not limited to those described above. In addition, the unified script is formed by being declared in a document type definition (DTD), an extensible markup language schema (XML schema), a structured language, a structured protocol, or the like, but is not limited to the above. An instance of a projectable space is an instance generated by an object, an extensible markup language (XML) file, or a structured language or a structured protocol, but is not limited to the above.

  4 is a schematic diagram of an initial state of the above-described workspace projection method in the preferred embodiment, FIGS. 5A and 5B are schematic diagrams of an operation concept of the workspace projection method shown in FIG. 4, and FIG. FIG. 5 is a schematic diagram of the relative relationship between the projectable space instance shown in FIG. 4 and the projected workspace shown 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 communicate with each other (eg, through a network connection), and the first electronic device 971 has an instance 973 of a projectable space. The projector 974 is built in the second electronic device 972.

  The unified script 9731 is formed by being declared in a document type definition (DTD), and at least one information input device (matterizer embodiment) and / or at least one unified information unit and / or at least one unified. It is defined that the workspace constructed by the tool is arranged. The projectable space instance 973 is an instance generated in the extensible markup language (XML). As shown in FIG. 6, the projectable space instance 973 is used to construct a projected workspace 976 corresponding to the workspace, and the information input unit and / or the unified information unit and / or unified tool Added to or removed from.

  The projector 974 of the second electronic device 972 creates a work environment 975 used for the operation of the workspace 976 projected onto the second electronic device 972, and a microkernel 977 (see FIG. 6) provides the work environment 975. In doing so, it is equipped with at least one information input and / or at least one unified information unit and / or at least one unified tool added into the projected workspace 976. When the second electronic device 972 acquires the projectable space instance 973 in the first electronic device 971 with the unified resource identifier, the projector 974 of the second electronic device 972 starts analyzing the projectable space instance 973. Is shown in FIG. 5A. Further, after the projectable space instance 973 is analyzed by the projector 974, the projected work space 976 is constructed on the work environment 975 based on the content analyzed by the projectable space instance 973. Shown in FIG. 5B. This allows the user of the second electronic device 972 to interact with the workspace 976 projected via the second electronic device 972 and perform related tasks.

  In the following, the relationship between the above-described unified script 9731, the projectable space instance 973, and the projected workspace 976 will be described by taking the usage situation further illustrated in FIG. 6 as an example. In the usage situation shown in FIG. 6, a projected workspace for allowing the user to observe the jpg format image file and the gif format image file stored in the designated Internet space is constructed. In this usage situation, the unified script 9731 is declared in the document type definition (DTD), and the projectable space instance 973 is generated in the extensible markup language (XML).

  Also, an information input device and a unified tool are added to the projectable space instance 973, and the information input device inputs at least one unified information unit corresponding to at least one original information to the projected workspace 976. Used to do. In this usage situation, the information input device is a Dropbox input device (ie, illustrated as a dashed box 9761) and the original information is the jpg format image files 9791, 9792 and the gif format image file 9793 in the Dropbox 979 information source, The unified information units are unified jpg format image files 9791 'and 9792' and unified gif format image file 9793 'which will be described later, the unified tool is an image viewer (ie, illustrated as a broken line frame 9762), and the projected workspace. 976 is used to read the image file input.

  Further, the projected workspace 976 is constructed after the projectable space instance 973 is analyzed by the projector 974 of the second electronic device 972, and a Dropbox input 9761 ′ (broken line shown) is projected on the projected workspace 976. And an image viewer 9762 ′ (corresponding to the broken-line frame 9762 shown in the figure) are arranged. It is input to the unified and projected workspace 976, and is input to the jpg format image file 9791, 9792 and the gif format image file 9793 respectively. Corresponding to unify jpg format image file 9791 ', 9792' and unified gif format image file 9793 'is displayed on the work space 976, which is projected. Next, when the user of the second electronic device 972 performs an operation on one of the unified jpg format image files 9791 ′ and 9792 ′ and the unified gif format image file 9793 ′ by a specific operation method (for example, unified jpg Click any one of the format image files 9791 ′, 9792 ′ and the unified gif format image file 9793 ′, or any of the unified jpg format image files 9791 ′, 9792 ′ and the unified gif format image file 9793 ′. Drag one of them to the image viewer 9762 '), and the image viewer 9762' can use the unified jpg format image files 9791 ', 9792' and the unified gif format. Any one of the contents of the image file 9793 'is displayed read, so users can be observed. In addition, the above-described Dropbox input unit 9661 ′ and image viewer 9762 ′ are equipped with a microkernel 977.

  Incidentally, the unified resource identifier of the projectable space instance 973 is a hypertext transfer protocol (HTTP) unified resource identifier or a file transfer protocol (FTP) unified resource identifier. When the first electronic device 971 and the second electronic device 972 are integrated devices, the unified resource identifier of the instance 973 of the projectable space is also the local file unified resource identifier. However, the form of the unified resource identifier is not limited to the above.

  The “specific acquisition method of the projecting method of the workspace” described in the present embodiment is “METHOD OF PROJECTING A WORKSPACE AND SYSTEM USING THE SAME” of US Patent Application No. 14/577772 and Chinese Patent Application No. 201410814138.5. The detailed description here will be omitted, since it is referred to the document “Projection Method of Workspace and System Applying the Projection Method of Workspace”.

  Incidentally, the above-described workspace projection method is only one of the projection methods in which the workspace of the present application is projected onto any electronic device having computational capability, and the projection in which the workspace is projected onto any electronic device having computational capability. The method is not limited to that described above. Those skilled in the art can make any design change that achieves the same effect according to the actual application demand.

  In addition, any workspace can be projected to any electronic device having a calculation capability, and thus any workspace can be regarded as a workspace that can be transmitted to any electronic device having a calculation capability. Hereinafter, a method for delaying the binding of an ID to an account according to the present invention will be described in more detail.

  FIG. 7 is a flowchart of a preferred method for delaying ID binding to an account according to the present invention. The method for delaying ID binding to an account includes the following steps. First, an instance of a projectable space used to construct a workspace is provided to the system, and an information input device, information, and / or tools are arranged in the projectable space instance (S110). The workspace is then projected to the machine and a user account is provided, the user is allowed to access the projected workspace, and the user is authorized to log in to the projected workspace. The user account is automatically generated by the system under the condition that no ID is provided (S120). When the user accesses the projected workspace to drive the information input device, the information, and / or the tool, the user provides an authorized ID and the authorized ID for the user account The access authority to the information input device, the information and / or the tool is validated (S130). Subsequently, the authorized ID bound to the user account permits the user to log in to the projected workspace from the machine or another machine (S140).

  FIG. 8 is a schematic diagram of a preferred concept of a mechanism applying the method shown in FIG. 7 in a specific embodiment. The system 1 is a network service platform of any type, although not limited thereto, and has functions such as Internet connection, Internet transit, domain name registration and hosting, dial-up connection, leased line connection and arrangement. Network service platform providers are various types of providers, such as commercial service providers, community owned service providers, non-profit service providers, etc., for example, workspace providers. In a preferred embodiment, the system 1 includes a server 210, which is provided with a projectable space instance 212 used to build a workspace, and the server 210 is executed or driven locally or remotely.

  The machine 220 is a desktop personal computer, a notebook personal computer, a personal tablet terminal, a smartphone, a mobile terminal, or a wearable terminal, but is not limited to the above. The machine 220 obtains the projectable space instance 212 by the uniform resource identifier (URI) of the projectable space instance 212, and the workspace 211 projected by the web browser 221 and the projector 222 loaded thereon is the machine 220. Built on top. When the user first accesses the projected workspace 211 using the web browser 221 of the machine 220, the server 210 automatically creates or generates a user account 230.

  The browser cookie 240 is a storage medium. Each time the user accesses the projected workspace 211 using the web browser 221 of the machine 220, the browser cookie 240 stores the usage history 241 of the projected workspace 211 on the machine 220 by the user account 230. Record inside. Usage history includes browsing history, operation execution logs, or any information records used for rational analysis of user preferences. As a result, the projected workspace 211 tracks the usage history 241 of the user based on the user account 230, and further provides services and / or contents that are better or better for the user. However, recording the usage history 241 of the user account 230 using the above-described browser cookie 240 is only one embodiment, and is not limited thereto. The usage history 241 of the user account 230 may be recorded in another storage medium (for example, a browser cache or a file) that can access the projected workspace 211.

  9 is a schematic diagram of a preferred concept in which the user first accesses the projected workspace in the method shown in FIG. 7 and the mechanism shown in FIG. 8, and FIG. 10 is in the method shown in FIG. 7 and the mechanism shown in FIG. FIG. 2 is a schematic diagram of a preferred concept for a user to re-access a projected workspace. When the user 200 first accesses the projected workspace 211 using the web browser 221 of the machine 220, the user account 230 is automatically generated by the server 210, and the usage history 241 of the user account 230 is stored in the browser cookie 240. Every operation performed in the workspace 211 onto which the user account 230 is projected is recorded. Therefore, when the user 200 accesses the projected workspace 211 again using the user account 230 using the web browser 221 of the machine 220 next time, the past usage history of the user account 230 is saved. Yes.

  Optionally, the method shown in FIG. 7 further includes the step of machine 220 locking user account 230 by binding user account 230 to the machine code of machine 220. The machine code is a code used to identify the machine 220. In a preferred embodiment, the machine code is an IP code (IP code) such as 210.32.54.123. When the user 200 logs in to the projected workspace 211 using the web browser 221 of the machine 220 and is not the first time (second or more), the projected workspace 211 has the user account 230 as an IP code. Since it is bound, it is stored in the browser cookie 240 and the history record corresponding to the user account 230 is read, that is, any operation performed on the workspace 211 onto which the user account 230 is projected, and then the user account Operations performed in the workspace 211 on which 230 is projected are continuously recorded in the browser cookie 240.

  In the following, the present invention is applied to a machine installed in a public place or a public machine that is open to the public (for example, a computer apparatus installed in a public place or a public computer apparatus that is open to the public). The usage situation will be further described. In general, a machine installed in a public place or a public machine that is open to the public may not be able to identify the user who uses the machine because many different users use the same machine at different times. is there. In order to solve the above situation, the user is identified and the user account is determined. The method shown in FIG. 7 further includes the step of providing a label and indicating an automatically generated user account. Therefore, the user can access the projected workspace using the machine given the name and character (role) under the condition that the authorized ID is not provided.

  FIG. 11 is a schematic diagram of a preferred concept for providing an indication of a user account that is automatically provided with a label provided. When the user 500 accesses the projected workspace 511 using the web browser 521 of the machine 520, as described above, the user account 530 is automatically generated for the user 500 by the server 210, and at the same time, the user account 530. Is bound to a machine code of the machine 520, for example, the IP code 210.32.54.123, and a label is automatically generated for the IP code 210.32.54.123 to indicate the user account 530. Done. Therefore, when the user 500 accesses the projected workspace 511 using the web browser 521 of the machine 520 next time, the server 210 authenticates by inputting the label used for the indication of the user account 530. Is performed, the user 500 is identified, and the user 500 can access the projected workspace 511 again to be usable.

  Further, when another user 501 accesses the projected workspace 511 or other projected workspace using the web browser 521 of the machine 520, the server 210 similarly uses the IP code 2100.32 of the machine 520. Another label is automatically generated for .54.123 (similar IP code). As described above, when the other user 501 subsequently inputs the other label that is also used to indicate the user account, the projected workspace 511 or another projected workspace is again input. It becomes accessible. As can be seen from the above description, the method of the present application can identify different users connecting to the same server using the same machine.

  In a preferred specific embodiment, the server provides the user with a new label in either case, regardless of whether or not the user has accessed the projected workspace using the machine's web browser for the first time. To do. Of course, such a label providing function can be arbitrarily disabled by the user, thereby saving the user from having to remember a new label each time. Also, without limitation, the content of the label includes any letter, number, or any combination of both, which can be provided by the server as a random number or can be determined by the user. For example, the real name or pseudonym provided by the user is included as the content of the label. The method of marking the user account with such a label and causing the server to identify and authenticate the user has other advantages. The same user can have a plurality of character IDs using the above-described method, and the character IDs respectively correspond to different projected workspaces. Note that when the user accesses the projected workspace by the machine using the name and character without creating a name and character and obtaining an authorized ID, the user account is given by the above-mentioned label. Authentication is performed and the user is identified by the server.

  FIG. 12 is a schematic diagram of a preferred concept for performing mutual authentication by binding a user account to another network service platform by applying the method shown in FIG. 7 and the mechanism shown in FIG. As illustrated in FIG. 12, a user 600 accesses a projected workspace 611 using the web browser 621 of the machine 620 and uses various services and functions, some of which are in other networks. Provided by a service platform (hereinafter referred to as an additional network service platform). Also, if the user 600 uses additional network service platform services or functions, an additional authorized ID is required. If the user account 630 is bound to an authorized ID of an additional network service platform, the authorized ID can be used to use that service or function. If the user account 630 is not bound to an authorized ID of the additional network service platform, the authorized ID of the additional network service platform is first bound to the user account 630, and the services and functions of the additional network service platform You need to gain access to.

  However, regardless of whether the user 600 has an authorized ID for an additional network service platform or whether the user 600 has created an authorized ID for the network service platform for the first time, the user 600 may all have one or more The authorized ID is specified and bound to the user account 630 to authenticate the binding. Specifically, the user 600 uses the machine 610 to perform authentication by binding the user account 630 to one or more other network service platforms that require an authorized ID. That is, one or more authorized IDs of other network service platforms are bound to the user account 630 so that the user 600 can subsequently access the projected workspace 611 using the user account 630 and others. When the services and functions provided by the network service platform are operated, the services and functions can be directly used without re-authentication. That is, the user account 630 is automatically authenticated by the network service platform.

  FIG. 13 is a schematic diagram of a preferred concept for binding a user account corresponding to a projected workspace to Facebook. As shown in FIG. 13, the projected workspace 711 includes a Facebook tool (which is an embodiment of a unified tool, and in the preferred embodiment, displayed as a Facebook icon 770) and the Facebook server 750 information. An information input device 760 for inputting to 711 is arranged. When the user clicks on the Facebook icon 770, the projected workspace 711 displays a window 780 that redirects to the Facebook web page, and the user enters an authorized ID, that is, the personal Facebook account and password. Thus, services and functions provided by Facebook can be acquired. At this time, the projected workspace 711 displays a question as to whether or not to authenticate the binding by binding the user account to the ID permitted by Facebook, and if the user agrees to the authentication of the binding, When accessing the projected workspace 711 using a user account and using the Facebook tool, it is possible to directly acquire services and functions provided by Facebook without entering a personal Facebook account and password.

  Since the user account is bound to the authorized ID of Facebook, the user can log in to the workspace 711 projected from any machine with the authorized ID of Facebook. Of course, the user can log in to the projected workspace 711 from any machine with any authorized ID bound to the user account. The above is only one implementation method in which a user accesses a projected workspace using a user account.

  In addition, when a user accesses a projected workspace using a user account and shares the projected workspace with another user, or invites another user to the projected workspace, First providing the other user's existing ID to the projected workspace, then the server automatically creates another user account for the other user and binds to the other user's existing ID. Binding authentication is performed, and a notification message is notified to an existing ID of another user in a wireless or wired manner. The other user's existing ID is an account or ID authenticated by any network service platform, for example, an account or authorized ID that another user has applied for on a social networking site, an email that another user has applied for Account. The notification message also includes a uniform resource identifier of the projectable space instance of the projected workspace. For this reason, when another user clicks or opens a notification message using an existing ID (for example, another user receives a notification message on Facebook using a Facebook account and is in it) You can access the projected workspace (by clicking on the uniform resource identifier). This achieves the purpose of sharing the projected workspace with other users.

  FIG. 14 is a flowchart of a preferred method for automatically generating a user account of a content recipient through content sharing according to the present invention. As shown in FIG. 14, in the process of accessing the projected workspace using a user account and browsing each network information in the projected workspace, the content is shared with other users. Sharing includes the following steps. First, when a user shares content with another user, it is checked whether the other user has a user account (hereinafter referred to as a second user account) on the server (S210). If so, the content can be shared with the second user account (S240). If not, the process proceeds to the next step (S220). In step S220, it is further determined whether an existing ID of another user is provided. If it is determined that the content is not provided, the process ends and content cannot be shared. If it is determined that it is provided, the process proceeds to the next step (S230). In step S230, the server automatically creates a second user account for another user, binds to the existing ID of the other user, and authenticates the binding.

  When the user knows an existing ID in another user's network resource, the second user account created in step S230 described above is the other user's existing ID in the existing network resource. Shared via link. Thus, when another user opens the link with the existing network resource, the projected workspace can be directly accessed using the second user account, and the content shared by the user can be viewed. Also, other users can change the information of existing IDs or permitted IDs that are bound to the second user account (for example, account names and passwords). In addition, the existing network resource described above may be a social networking site (for example, Facebook or Twitter) or any other network service (for example, e-mail).

  FIG. 15 is a block schematic diagram of a computer program product applying the method shown in FIG. 7 in the preferred embodiment. A computer program product 7 (eg, a software package) is used to delay the binding of an ID to an account and includes program code 71. The program code 71 executes the steps shown in FIG. 7 when the computer program product 7 is executed by the computer 6. Since the specific implementation method of these steps is the same as that described above, it will not be described again here.

  As described above, the present application further has the following advantages as compared with the prior art. First, there is no need to perform user account registration work before the user logs in or connects to the network service platform, and a user account is automatically created directly for the user by the network service platform. The user account is automatically generated by the network service platform even if the user logs into the network service platform for the first time and is not authenticated by the network service platform. Second, the network service platform can use user accounts to track and analyze user usage history and analyze user preferences. Third, the user is provided with an authorized ID that is bound to the user account and can use different machines to access the projected workspace using that user account. Fourth, the user can access the projected workspace using an anonymous ID, and can arbitrarily install various information and tools in the projected workspace. Fifth, if the user knows the existing IDs of other users of different network service platforms, the user can share and invite content to other users.

  As mentioned above, although embodiment of this invention was explained in full detail with reference to drawings, the concrete structure is not restricted to this embodiment, The design change etc. of the range which does not deviate from the summary of this invention are included.

1 System 6 Computer 7 Computer Program Product 71 Program Code 200 User 210 Server 211 Projected Workspace 212 Projectable Space Instance 220 Machine 221 Web Browser 222 Projector 230 User Account 240 Browser Cookie 241 Usage History 500 User 501 User 511 Projection Projected Workspace 520 Machine 521 Web Browser 530 User Account 600 User 611 Projected Workspace 620 Machine 621 Web Browser 630 User Account 711 Projected Workspace 750 Facebook Server 760 Information Input 770 Facebook Icon 780 Window 971 First Electronic device 972 Second Electronic Device 973 Projectable Space Instance 974 Projector 975 Work Environment 976 Projected Workspace 977 Microkernel 979 Dropbox
980 Unified Script 981 Personal Workspace 982 Dropbox
983 Cloud storage 984 Server 985 Original information 985 'Unified information unit 986 Original tool 986' First unified tool 987 Original tool 987 'Second unified tool 991 Original element 992 Materizer 993 Unified data model 994 Unified element 9731 Unified script 9761 Broken line frame 9761 'Dropbox input device 9762 Broken line frame 9762' Image viewer 9791 jpg format image file 9791 'Unified jpg format image file 9792 jpg format image file 9792' Unified jpg format image file 9793 gif format image file 9793 'Unified gif format image File 9881 Information input unit 9882 Information input unit 9883 Information input unit S110 Step S120 step S130 step S140 step S210 step S220 step S230 step S240 step

Claims (22)

Providing the system with an instance of a projectable space used to build the workspace, and placing an information input device, information and / or tools in the projectable space instance;
The workspace is projected onto the machine and a user account is provided, the user is allowed to access the projected workspace, and the user is allowed to log in to the projected workspace. The user account is automatically generated by the system under non-providing conditions;
When the user accesses the projected workspace to drive the information input device, the information, and / or the tool, the user provides an authorized ID and the authorized ID for the user account Requesting to bind to and enabling access rights to the information input device, the information and / or the tool;
Including the step of allowing the user to log into the projected workspace from the machine or other machine by the authorized ID bound to the user account. A method of delaying ID binding.   The system includes a server, and the user account under the condition that an instance of the projectable space is provided to the server and the user does not provide an authorized ID to log into the projected workspace The method of delaying ID binding to an account according to claim 1, characterized in that is automatically generated by the server.   The method of delaying binding of an ID to an account according to claim 1, wherein the information input device is used to provide the information and / or the tool to the projected workspace.   The information is a unified information unit formed after the original information obtained from the information source is unified, and / or the tool is formed after the original tool obtained from the information source is unified. The method of delaying binding of an ID to an account according to claim 1, wherein the method is a tool.   The original information is modeled as the unified information unit based on a unified data model, and / or the original tool is modeled as the unified tool based on another unified data model, 5. A method for delaying binding of an ID to an account according to claim 4.   5. The method for delaying ID binding to an account according to claim 4, wherein the information source is a network service platform.   The method of claim 1, further comprising the step of locking the user account by the machine by binding the user account to the machine code of the machine. Method.   8. The method for delaying ID binding to an account according to claim 7, wherein the machine code is a code used to identify the machine.   The method of delaying ID binding to an account according to claim 1, further comprising the step of recording the usage history of the user in the projected workspace.   10. The method for delaying ID binding to an account according to claim 9, wherein the usage history is recorded on a storage medium accessible to the projected workspace.   The method of delaying ID binding to an account according to claim 10, wherein the storage medium is a browser cookie, a browser cache, or a file.   10. The ID binding to an account according to claim 9, wherein the usage history includes browsing history, operation execution log and / or information records used for rational analysis of user preferences. Method.   The method for delaying ID binding to an account according to claim 9, wherein the projected workspace tracks the usage history of the user based on the user account.   14. The account according to claim 13, wherein the projected workspace tracks and analyzes the user's usage history and provides services and / or content to the user. A method of delaying ID binding.   A label is provided under certain conditions and is used to indicate the automatically generated user account, which creates the name and role desired by the user and provides the authorized ID. The binding of an ID to an account as recited in claim 1, further comprising the step of: accessing the projected workspace by the machine using the name and role. How to delay.   16. The method of delaying binding of an ID to an account according to claim 15, wherein the content of the label includes a real name or pseudonym provided by the user and is used to indicate the user account.   The user is allowed to provide a plurality of authorized IDs that are bound to the user account and are authenticated for binding, and any one of the plurality of authorized IDs is projected. 2. The method for delaying binding of an ID to an account according to claim 1, wherein the service target is identifiable by a workspace.   The user account is tracked by the projected workspace when the user logs into the projected workspace from the other machine with the authorized ID bound to the user account. The method of delaying binding of an ID to an account according to claim 17.   The method of delaying ID binding to an account according to claim 1, wherein the user account is automatically generated by the system when the user first accesses the projected workspace. .   The system is allowed to automatically generate and provide other user accounts to other users, and the other user's existing ID is bound to the other user account and the binding is authenticated, Another user account allows the user who has accessed the projected workspace to share the projected workspace with the other user, or the other user has been invited to the projected workspace The method of delaying binding of an ID to an account according to claim 1, further comprising the step of generating at the time.   The delayed ID binding to an account according to claim 1, wherein the projectable space instance is an object, an instance generated by an extensible markup language, a structured language or a structured protocol. How to make. A computer program product used to delay the binding of an ID to an account, comprising program code, the program code when the computer executes the computer program product
Providing the system with an instance of a projectable space used to build the workspace, and placing an information input device, information and / or tools in the projectable space instance;
The workspace is projected onto the machine and a user account is provided, the user is allowed to access the projected workspace, and the user is allowed to log in to the projected workspace. The user account is automatically generated by the system under the condition of not providing an ID;
When the user accesses the projected workspace to drive the information input device, the information, and / or the tool, the user provides an authorized ID and the authorized ID for the user account Requesting to bind to and enabling access rights to the information input device, the information and / or the tool;
Executing the step of allowing the user to log in to the projected workspace from the machine or another machine by the authorized ID bound to the user account. Product.