Computer Services

Abstract

Computer service technologies are disclosed, some of which relate to the use of code in code-aware services. Furthermore, hierarchical and substructures usable for providing computer services in computer systems are disclosed, relating to service-related functions such as iterative processing of context-dependent user interface processes. In addition, the use of integration in hierarchical structures and related computer systems, particularly service delivery using integration, is disclosed. Advantageous user interface functions are also disclosed. Other computer service-related functions are also disclosed.

Description

Technical Field

[0001] Technical field This disclosure relates to computer services and user interface functions.

Background Art

[0002] Background technology Computers are useful for performing various processes. By networking multiple computers so that they can execute mutually related processes, the usefulness of computers has been further expanded. With these computer systems, many advantages are obtained, such as the accumulation of vast amounts of information and the realization of various processes. On the other hand, along with the development of computers, new problems specific to computers have emerged.

Summary of the Invention

[0003] overview Conventional computer implementation tools and technologies have not recognized the computer implementation tools and technologies described and claimed in this specification, and the advantages brought by them.

[0004] In one embodiment, a computer system may include user accounts and service data structures linked to said user accounts. The service data structure may include a plurality of categories having a hierarchical structure, and these categories may include a first category located at a first level and a second category at a second level contained within the first category. Furthermore, the service data structure may include records within the second category. A record may include information about at least one scannable code linked to a user account in the computer system and information about one or more computer implementation services executed through the computer system in response to user input using the at least one scannable code. For example, these one or more computer implementation services may be executed or managed by one or more corresponding service managers.

[0005] In yet another embodiment, a display showing at least a portion of the service data structure is presented, and the display shows the current position in the hierarchy. Upon receiving user input, navigation between different levels in the hierarchy can be performed, and the display content can be updated accordingly. The display may include the user interface display described above, or other different interface displays.

[0006] In yet another embodiment, a request can be received to move a record to a new hierarchical location based on user input. When this request is received, the record and / or the category structure index corresponding to the record can be moved to a new hierarchical location within the computer system. The category structure index is information indicating the hierarchical category structure containing the record, and this category structure may include a first category and a second category. The record can retain the structure indicated by the category structure index even after being moved.

[0007] In yet another embodiment, a method is provided for managing a service data structure associated with a user account in a computer system. The service data structure includes a record which includes information indicating at least one scannable code and one or more computer-implemented services to be performed through the computer system in response to user input using the code. The method may include the step of performing the one or more computer-implemented services in response to user input using the scannable code. The management of the service data structure may include the step of performing a first set of actions in response to input from at least one human-facing user interface device, or the step of performing a second set of actions in response to input from at least one artificial intelligence bot operating on the computer system.

[0008] In yet another embodiment, a technique is provided for managing a service data structure associated with a user account. The service data structure includes a record which may include information about at least one scannable code linked to a user account in a computer system. The record may also include configuration information (e.g., configuration items) for one or more computer-implemented services that are executed by the computer system in response to user input using the scannable code. The technique further includes the step of receiving user input, including an input code, in a computer system, and using the input code and the service data structure to identify the processing requested by the user. The computer system can perform a security check based on the received input code. If the security check determines that there is a security problem, one or more precautionary measures can be taken against the input code. On the other hand, if the security check is completed successfully (i.e., there is no security problem), the execution of the precautionary measures can be omitted.

[0009] In yet another embodiment, a technique is provided for managing a service data structure associated with a user account. The service data structure includes a record containing information about at least one scannable code linked to a user account in a computer system, and information about one or more computer-implemented services performed by the computer system in response to user input using the code. The technique further includes the step of performing the one or more services when it receives user input using the scannable code. Furthermore, when it receives a request to create another user account, the computer system generates a second user account in response to the request. At the time of generation, a tracking code may be associated with the second user account, and this tracking code indicates the referrer of the account. The referrer may be either a product provider user account related to the new account creation request, or a referring user account. Furthermore, the technique may include the step of crediting the referrer record for the creation of the second user account.

[0010] In yet another embodiment, a technique is provided for managing a service data structure associated with a user account in a computer system. The service data structure includes a record containing information about at least one scannable code and one or more computer-implemented services that are executed in response to user input using the code. The technique further includes the step of receiving user input using the scannable code in the computer system. Upon receipt, a quick link linked to the scannable code can be generated and presented to a user output device. If the user selects the quick link, one or more computer-implemented services linked to the scannable code are executed. Furthermore, the quick link is reused and made available again in response to subsequent user input. Such reuse includes the step of temporarily unlinking the quick link from the scannable code. The reused quick link may be used in subsequent similar operations for other scannable codes linked to the same but different services, or for scannable codes linked to different user accounts.

[0011] In yet another embodiment, a technique is provided for presenting a user interface display representing the current node when navigating between nodes in a hierarchical data structure. The hierarchical data structure includes multiple service integrations, and the user interface display includes a context-sensitive user interface control displayed on two or more nodes located at multiple levels within the hierarchical data structure. These two or more nodes include contact nodes in a contact integration, which includes contact nodes linked to profiles of accounts other than the active user account, and portfolio nodes located in a portfolio integration separate from the contact integration. The portfolio nodes are of a type other than contact nodes, and the portfolio integration includes a portfolio integration node integrated into the hierarchical data structure to provide services to the active user account. The portfolio integration may include structures other than account profiles. Furthermore, the technique includes a step of iterating through the state of the context-sensitive user interface control as the user interface display navigates between nodes. Through this iteration, the control is configured to invoke context-sensitive integrations and execute triggered processes as selected. These processes are individually tailored depending on the node currently displayed in the user interface display, and different processes are executed across multiple nodes.

[0012] In yet another embodiment, a technique is provided for presenting a user interface display that includes an outline. The technique also includes a step of partially collapsing subject items within the outline being displayed, in response to a system determination relating to the outline. The partial collapsing process includes a step of composing and presenting the outline with one or more items that are subordinate to the subject item hidden and one or more items displayed.

[0013] In yet another embodiment, a profile sharing system provides a technique for sharing multiple profiles linked to a shared account with another account. The technique also includes the step of integrating profile data from the multiple shared profiles to generate a blended profile. Furthermore, the technique includes the step of displaying profile data from the blended profile when a user input from another account requests the display of profile information of the shared account.

[0014] In yet another embodiment, a technique is provided for presenting a user interface display representing the current node when navigating between nodes in a hierarchical data structure. The user interface display can present a user interface area representing a category node located below the current node in the hierarchical data structure. The user interface area for the category node may include a drill-down user interface control that can be selected to drill down the user interface display to the category node and to display one or more subcategories below the category node, and an access point user interface control that can be selected to display an access display for accessing one or more records linked to the category node. The technique also includes the step of moving the user interface display to a new display depending on the selection of the drill-down user interface control and / or the access point user interface control.

[0015] In yet another embodiment, a technique is provided for maintaining data indicating that multiple information data items included in the structure of an active user account are being used at multiple different locations within a hierarchical data structure system. The technique also includes the step of presenting a profile monitoring user interface display of the active user account. The profile monitoring user interface display represents multiple information data items and includes one or more display elements corresponding to each data item, the display elements indicating one or more different locations where the corresponding data item is being used.

[0016] In yet another embodiment, a technology is provided for maintaining a code record linked to a user account. The code record defines a predefined code, which includes a predefined pattern in one or more of the following: a video pattern, an audio pattern, a biometric pattern, or a frequency pattern. The code also defines a service to be performed using integrated processing when the code is scanned by a computer system and the predefined pattern is identified. The technology further includes receiving a scan input, which includes one or more of the following: a video input, an audio input, a biometric input, or a frequency input; identifying the predefined code; and, depending on the identification result, performing a service using integrated processing within the computer system.

[0017] In yet another embodiment, a technique is provided for receiving access point requests from a user account for access points to a service integration that is not fully configured. This technique includes the steps of determining to use the user account's access point profile in configuring the access point, identifying a specific profile to be used by the service integration, and configuring that specific profile as the access point profile as part of the access point configuration. The specific profile may be an existing profile identified or entered by user input, or a system-generated profile (for example, the system may select a public profile as the default profile or automatically generate the necessary profiles for the access point).

[0018] In yet another embodiment, the technology is implemented by a computer system comprising a mobile user device and a desktop user device (a device having a larger screen than a typical mobile device, such as a desktop computer, notebook computer, or tablet computer). The technology includes the steps of presenting a mobile display on the mobile user device and presenting a desktop display on the desktop user device. The desktop display includes a mobile area having a layout and user interface controls that mimic the mobile display, and a content area separate from the mobile area. The content area is displayable simultaneously with the mobile area and displays content related to the instructions displayed in the mobile area. The technology also includes the steps of expanding the content area to include at least a portion of the mobile area and hiding at least a portion of the mobile area. Furthermore, the expansion step includes receiving user input directed to user interface controls on the desktop display and, in response to the input, expanding the content area to include at least a portion of the mobile area and hiding at least a portion of the mobile area.

[0019] This abstract is provided to introduce some concepts in a simplified form. These concepts will be further explained in the detailed description below. This abstract is not intended to identify the main or essential features of the claimed subject matter, nor is it intended to limit the scope of the claims. Similarly, the present invention is not limited to the specific technologies, techniques, environments, disadvantages, or advantages discussed in the background art, detailed description, or accompanying drawings.

Brief Description of the Drawings

[0020] Brief explanation of the drawing [Figure 1] FIG. 1 is a schematic diagram of a computer service system.

[0021] [Figure 2] FIG. 2 is a schematic diagram of a service data structure.

[0022] [Figure 3] FIG. 3 is a block diagram of a computing environment suitable for implementing one or more aspects described herein.

[0023] [Figure 4] FIG. 4 is an illustrative diagram of a user computing device for presenting a display.

[0024] [Figure 5] FIG. 5 is an illustrative diagram of a user computing device for presenting another display.

[0025] [Figure 6] FIG. 6 is an illustrative diagram of a user computing device for presenting yet another display.

[0026] [Figure 7] FIG. 7 is an illustrative diagram of a user computing device for presenting yet another display.

[0027] [Figure 8] Figure 8 is an example of a user computing device that displays yet another type of information.

[0028] [Figure 9] Figure 9 is an example of a user computing device that displays yet another information.

[0029] [Figure 10] Figure 10 is an example of a user computing device that displays yet another information.

[0030] [Figure 11] Figure 11 is an example of a user computing device that displays yet another information.

[0031] [Figure 12] Figure 12 is an example of a user computing device that displays yet another information.

[0032] [Figure 13] Figure 13 is an example of a user computing device that displays yet another information.

[0033] [Figure 14] Figure 14 is an example of a user computing device that displays yet another information.

[0034] [Figure 15] Figure 15 is an example of a user computing device that displays yet another information.

[0035] [Figure 16] Figure 16 is an example of a user computing device that displays yet another information.

[0036] [Figure 17] Figure 17 is an example of a user computing device that displays yet another information.

[0037] [Figure 18] Figure 18 is an example of a user computing device that displays yet another information.

[0038] [Figure 19] Figure 19 is an example of a user computing device that displays yet another information.

[0039] [Figure 20] Figure 20 is an example of a user computing device that displays yet another information.

[0040] [Figure 21] Figure 21 is an example of a user computing device that displays yet another information.

[0041] [Figure 22] Figure 22 is an example of a user computing device that displays yet another information.

[0042] [Figure 23] Figure 23 is an example of a user computing device that displays yet another information.

[0043] [Figure 24] Figure 24 is an example of a user computing device that displays yet another information.

[0044] [Figure 25] Figure 25 is an example of a user computing device that displays yet another information.

[0045] [Figure 26] Figure 26 is an example of a user computing device that displays yet another information.

[0046] [Figure 27] Figure 27 is an example of a user computing device that displays yet another information.

[0047] [Figure 28] Figure 28 is an example of a user computing device that displays yet another information.

[0048] [Figure 29] Figure 29 is an example of a user computing device that displays yet another information.

[0049] [Figure 30] Figure 30 is an example of a user computing device that displays yet another information.

[0050] [Figure 31] Figure 31 is an example of a user computing device that displays yet another information.

[0051] [Figure 32] Figure 32 is an example of a user computing device that displays yet another information.

[0052] [Figure 33] Figure 33 is an example of a user computing device that displays yet another information.

[0053] [Figure 34] Figure 34 shows an example of an encoded material.

[0054] [Figure 35] Figure 35 shows an example of another encoded object.

[0055] [Figure 36] Figure 36 is a schematic diagram showing an example of a service integration type and service manager.

[0056] [Figure 37] Figure 37 is a schematic diagram showing an example of a service integration type.

[0057] [Figure 38] Figure 38 is an example diagram of a user computing device that displays information.

[0058] [Figure 39] Figure 39 is an example of a user computing device that displays an alternative information.

[0059] [Figure 40] Figure 40 is an example of a user computing device that displays yet another information.

[0060] [Figure 41] Figure 41 is an example of a user computing device that displays yet another information.

[0061] [Figure 42] Figure 42 is an example of a user computing device that displays yet another information.

[0062] [Figure 43] Figure 43 is an example of a user computing device that displays yet another information.

[0063] [Figure 44] Figure 44 is an example of a user computing device that displays yet another information.

[0064] [Figure 45] Figure 45 is an example of a user computing device that displays yet another information.

[0065] [Figure 46] Figure 46 is an example of a user computing device that displays yet another information.

[0066] [Figure 47] Figure 47 is an example of a user computing device that displays yet another information.

[0067] [Figure 48] Figure 48 is an example of a user computing device that displays yet another information.

[0068] [Figure 49] Figure 49 is an example of a user computing device that displays yet another information.

[0069] [Figure 50] Figure 50 is an example of a user computing device that displays yet another information.

[0070] [Figure 51] Figure 51 is an example of a user computing device that displays yet another information.

[0071] [Figure 52] Figure 52 is an example of a user computing device that displays yet another information.

[0072] [Figure 53] Figure 53 is an example of a user computing device that displays yet another information.

[0073] [Figure 54] Figure 54 is an example of a user computing device that displays yet another information.

[0074] [Figure 55] Figure 55 is a schematic diagram of a system including a mobile user device, a desktop user device, and a service subsystem.

[0075] [Figure 56] Figure 56 is a schematic diagram of the blend profile.

[0076] [Figure 57] Figure 57 is an example of a user computing device that displays yet another information.

[0077] [Figure 58] Figure 58 is an example of a user computing device that displays yet another information.

[0078] [Figure 59] Figure 59 is an example of a user computing device that displays yet another information.

[0079] [Figure 60] Figure 60 is a schematic diagram including a display layout for the user's computing device.

[0080] [Figure 61] Figure 61 is a flowchart showing at least some aspects of computer service technology.

[0081] [Figure 62] Figure 62 is a flowchart showing at least some of the other computer service technologies.

[0082] [Figure 63] Figure 63 is a flowchart illustrating at least some of another computer service technology.

[0083] [Figure 64] Figure 64 is a flowchart illustrating at least some of another computer service technology.

[0084] [Figure 65] Figure 65 is a flowchart illustrating at least some of yet another computer service technology.

[0085] [Figure 66] Figure 66 is a flowchart illustrating at least some of yet another computer service technology.

[0086] [Figure 67] Figure 67 is a flowchart illustrating at least some of another computer service technology.

[0087] [Figure 68] Figure 68 is a flowchart illustrating at least some of another computer service technology.

[0088] [Figure 69] Figure 69 is a flowchart illustrating at least some of another computer service technology.

[0089] [Figure 70] Figure 70 is a flowchart illustrating at least some of another computer service technology.

[0090] [Figure 71] Figure 71 is a flowchart illustrating at least some of another computer service technology.

[0091] [Figure 72] Figure 72 is a flowchart illustrating at least some of another computer service technology.

[0092] [Figure 73] Figure 73 is a flowchart illustrating at least some of another computer service technology.

[0093] [Figure 74] Figure 74 is a flowchart illustrating at least some of another computer service technology. [Modes for carrying out the invention]

[0094] Detailed explanation The embodiments described herein are directed toward methods and tools relating to computer services. Improvements may arise from using various methods and tools individually or in combination. With the explosive growth of data in computer systems (including the acceleration of this growth due to content generated by artificial intelligence), computer systems that provide computer services in a systematic and useful manner can support the efficiency of the computer system, as well as user experience and effectiveness. At least some of the tools and methods described herein can provide advanced structured management of encoded and / or standardized data.

[0095] The tools and techniques described herein may include tools and techniques for computer service systems. A computer service system may manage records for user accounts. A record may be a service code record that includes, or does not include, a representation of scannable code linked to a user account in the computer system. For example, this record is linked to a user account and scannable code. Another record, such as a service code record, may include a set of one or more computer-implemented services performed through the computer system in response to user input using scannable code (the services may be performed with artificial intelligence and / or human assistance). A computer service system may manage service data structures for each of several user accounts, each service data structure being linked to the corresponding user account in the computer system. Multiple service data structures may be linked to different user accounts and maintained within a larger data structure. Different service data structures may be integrated with each other in various ways within that larger data structure. Multiple service data structures may also be linked to a single user account. For example, each of such service data structures may be linked to a different organization indicator for the user account, allowing the user account to switch management between different service data structures for different organizations. Where used herein, an organization indicator or designation may be an indicator or designation that enables the organization of user accounts into separate record structures. This record structure is a category containing records.For example, user accounts may be separated by display or designation for different occupations held by human users, different businesses managed by human users, different subordinate business organizations to the business organization using the account (e.g., different departments, divisions, or subsidiaries of a company), different hobbies or interests held by human users, different third-party providers of coded materials and / or services, and / or other ways in which the data structure for categories and / or records linked to user accounts may be divided or separated. Organizations may be set up and / or modified in response to input from one or more sources, such as user input from active user accounts linked to organizations in the data structure and / or input from service subsystems and / or developers / administrators of service subsystems. Furthermore, the tools and techniques applicable to categories described herein may also be applicable to organizations, which may be considered and treated as higher-level categories (such as when categories and records are contained within an organization or within a subordinate group of an organization) and include the categories described herein, as necessary.

[0096] In one example, a service code database may include a database unit for each service data structure (such as one database table, multiple database tables, or a set of database records within a database table). In other embodiments, each service data structure may be separated from other service data structures, or service data structures may be integrated with each other in different ways, insofar as the structure provides links between elements within each service data structure, such as to indicate the categories to which other categories and records belong, as described herein. Such linking may be implemented in various ways, such as locating data within computer storage and / or including references between different data units (e.g., references between different data units in one or more databases or other types of data structures).

[0097] Computer service systems can facilitate the management of records (such as their activation, creation, configuration, modification, and use). Use of a record may include providing computer implementation services indicated within that record in response to a computer device scanning a code indicated within the record or entering such code in any other way (e.g., as a text identifier) ​​to indicate a desired record. Use of a record may include providing computer implementation services indicated within that record in response to a computer device scanning a code indicated within that record or entering such code in any other way (e.g., as a text identifier) ​​to indicate a desired record.

[0098] The services described herein may be any services provided in connection with the use of a computer system. Services may involve the operation of artificial intelligence bots, and may also involve non-computerized operations, such as when a human user provides user input as part of the service provision. As used herein, system services may include record services and / or shared services. Record services are services provided through the system to user accounts relating to records for which the user account has administrator privileges and / or obligations. For this purpose, record services may provide extended system services to records and / or categories of such user accounts. In contrast, shared services are services provided in response to the scanning of shared scannable code.

[0099] In one example of a records service, the system may provide a service that prompts a user account to perform bulk data uploads and / or downloads to the system (which may include uploading and / or downloading records, categories, links, user account data, organization data, and / or other data linked to the user account within the computer system). These bulk uploads and / or downloads may be performed via the account service or using an extended records service.

[0100] As described herein, an integration structure, referred to as an integration (corresponding to the categories in the service data structures described below), can provide many different types of services, such as services that may include shared services and / or record services. For example, a system service may include shared services and / or record services, and a system service may be one of many services, such as any service selected from the following group of services (or combinations thereof), which may be provided by integrations (including optional and non-optional integrations) as appropriate: anthropological services; (advertising) copy services; 3D printing services; accounting services; activity services; actuarial services; advertising services; management services; adult services; advertising services; aerospace services; agent services; agricultural services; farming services; alternative medicine services; animal services; animal welfare services; animal health services; anti-counterfeiting services; appointment services; archaeological services; architectural services; artist services; assistant services; astrophysical / astronomy services; audio services; automatic Car services; Autonomous device services; Autonomous equipment services; Automated vehicle services; Banking services; Biochemical services; Biology / Biomedical services; Biological services; Biostatistics / Bioinformatics services; Booking services; Broadcasting services; Brokerage services; Management services; Business services; Taxi services; Calendar services; Schedule management services; Charitable services; Chemical services; Chemical services; Administrative services; Confidential services; Coaching services; Cognitive science services; Communication services; Community services; Computer services; Connector services; Maintenance services; Construction services; Construction / Mining services; Consulting services; Contact services; Contact data sharing services; Contact management services; Content creation services; Content services; Contractor services; Controller services; Counseling / Theory services; Course services; Creative writing services; Creator services;Credit services; Criminology / criminal justice services; Cryptography-related services; Cultural studies services; Customer service; Dating services; Data science services; Dealer services; Detention services; Device services; Digital services; Distribution services; Document services; Economics services; Editorial services; Education / Teaching services; Educational services; Email services; Text messaging services; Facsimile services; Emergency management services; Employment services; Energy services; Energy / Utility services; Engineering services; Engineering services; Entertainment services; Broadcast entertainment services; Environmental science services; Epidemiology services; Equipment services; Equipment services; Ethnomusicology / Musicology services; Event services; Event services; Financing services; Fisheries services; Fitness / Health services; Food services; Forestry services; Fulfillment services; Funding services; Fundraising services; Genetics services; Geography services; Government services; Healthcare services; Heavy equipment services; Historical services; Homeland security services; Hospitality Talent services; human services; personnel services; human welfare services; import / export services; industrial services; influencer services; information technology services; insurance services; intellectual property services; intelligence services; interactive / multimedia services; international relations services; interview services; inventory management services; investment services; IoT (Internet of Things) services; IT services; journalism / news services; judicial services; kinematics services; landscaping services; law enforcement services; legal services; library services; linguistic services; literature services; loan services; logistics services; made-to-order services; postal services; maintenance services; management services; manufacturing services; production / manufacturing services; marketing services; mathematical services; media services; medical services; mental services; merchant services; metaverse services; military services; mixed media services; film services; moving services; music services; networking services; non-profit services; notification services; online store services; operations services; order management services; organizational services;Packaging services; park / recreation services; services for people; personal care services; personal services; pharmaceutical / biodegradation services; charitable services; planning services; podcast services; political services; print-on-demand services; product services; production services; professional services; professional services services; profile management services; program services; programming services; project management services; property management services; protection services; provider services; public administration services; public relations services; publishing services; quality assurance services; real estate services; restaurant services; referral services; reputation management services; research services; research / development services; retail services; safety services; sales services; science / research services; security services; delivery services; signage services; skilled worker services; social media services; social services services; SOP services; specification services; sports services; store services; support services; talent services; Tax services; technical services; technical services; telecommunications services; training services; training / development services; translation services; transportation services; transport services; travel services; vehicle services; video services; virtual travel services; virtual reality services; volunteer services; website sharing services; Web1 services; Web2 services; Web3 services; web services; welfare services; wellness services; writing services; short-term rental services; hotel services; rideshare / taxi services; personal services; organizational services; gaming services; augmented reality services; text / SMS / MMS services; marketplace / sales / purchase services; automated response services; device / smartphone file / data exchange services; media buyer services; media posting related services; AI (artificial intelligence) integration services; machine learning services; computer / networking / system / AI / human interface services; computing-enabled services; networked computing-enabled services; AI integrated computing system services;Parking / transportation services; concert services; professional services; human-integrated computing system services; hobby services; registration services; identification services; cataloging services; organization services; lost and found services; physical product services; digital product services; vehicle maintenance services; television broadcasting services; digital broadcasting services; holographic services; projection media services; film (pornography) industry services; service provider services; IT management services; online account management services; customer account management services; automated messaging services; 3D rendering / imaging services; CAD services; design services; art / craft services; file sharing services; data sharing services; information sharing services; writing / editing services; data calculation / derivation services; file enhancement services; video enhancement services; image enhancement services; retail product services; wholesale product services; affiliate product services; dropshipping product services; white-label product services; manufactured product services; original product services; prototype product services; service services Services; Teacher services; Trainer services; Physical trainer services; Business trainer services; SME (Specialized Enterprise) services; Encoded literature services; Virtual broadcasting services; Virtual advertising services; Virtual object generation services; Virtual object encoding services; Virtual encoding services; Services to convert physical objects to virtual objects; Services to convert digital objects to virtual objects; Services to convert specifications to digital objects; Services to physically create objects from specifications; Virtual video advertising services; Services to create physical objects from virtual objects; Services to create digital objects from virtual objects; Services to convert virtual objects to specifications; Services to convert digital objects to specifications; Services to convert physical objects to specifications; Encoded literature services; Encoded product services; Encoded service services; Encoded book services; Encoded item services; Encoded object services; Encoded digital posting services; Encoded advertising services; Encoded billboard services; Encoded digital display services; Encoded article services;Encoded specification services; Encoded SOP (Standard Operating Procedure) services; Encoded toy services; Encoded label / tag services; Encoded medical alert item services; Encoded clothing / apparel services; Encoded personal accessory services; Encoded ID tag services; Specific organizational department services; Specific organizational unit services; Specific organization / entity services; Specific group services; Specific service category services; Specific people / person services; Specific affiliate services; Specific service center services; Specific business type services; Specific business services; Specific organizational function area services; Specific project services; Specific program services; Specific campaign services; Specific location services; Specific object services; Specific location services; Specific animal services; Specific object services; Specific item services; Specific physical object services; Specific virtual object services; Specific digital object services; Encoded electronic equipment services; Encoded vehicle services; Encodeable object services; Data synchronization services; Digital / electronic file related services Period services; payment processing services; fiat currency payment processing services; cryptocurrency payment processing services; digital currency processing services; fiat currency payment services; crypto payment services; digital course training services; NFT (non-fungible token) services; cryptocurrency services; digital currency services; crypto services; sharing services for goods; trading services for goods; lending services for goods; display services for goods; advertising services for goods; use services for goods; NFT goods services; electronic equipment services; vehicle services; literature services; product services; service services; book services; item services; object services; digital posting services; advertising services; encoded signage services; encoded digital display services; article services; specification services; SOP (standard operating procedure) services; toy services; label / tag services; medical alert item services; clothing / apparel services; personal accessories services; consumer goods services; customer goods services; automated response services; call attendant services; chatbot services; mapping services; imaging services;Product organization services; product ordering services; product management services; product manufacturing services; inventory management services; fulfillment services; production services; construction / manufacturing / construction services; teaching services; knowledge sharing services; product editing services; profile services; profile creation services; profile sharing services; Profile management services; Website / webpage services; Website / webpage creation services; Website / webpage sharing services; Website / webpage management services; (Web) funnel services; (Web) funnel creation services; (Web) funnel sharing services; (Web) funnel management services; Research area services; Organization services; Organizational product services; Product line services; Brand services; Recruitment services; On-job services; Vocational training services; Job role and responsibility support services; Job role and responsibility services; Job resource services; (Online) Forms / Documents / Literature services; Organization (Online) Forms / Documents / Literature services; Job (Online) Forms / Documents / Literature services; Business (Online) Forms / Documents / Literature services; Training (Online) Forms / Documents / Literature services; Professor (Online) Forms / Documents / Literature services; Coaching (Online) Forms / Documents / Literature services; API (Application Programming Interface) Services; automation services (such as Zapier®, Airtable®, etc.); API (Application Programming Interface) integration services; automation integration services (such as Zapier®, Airtable®, etc.); integration services; integrated application services; integrated system services; dental services; industry product services; industry service services; industry tool services; industry (online) forms / documents / literature services; medical services; emergency relief services; emergency product services; emergency service services; emergency tool services; emergency (online) forms / documents / literature services; disaster relief services; disaster relief product services; disaster relief service services; disaster relief tool services; disaster relief (online) forms / documents / literature services; weapons services; weapons product services; weapons relief service services; weapons relief tool services; weapons (online) forms / documents / literature services; charitable services; charitable product services; charitable service services; charitable relief tool services;Charity (online) forms / document / literature services; programming services; device programming services; smartphone programming services; computing device programming services; command services; device command services; smartphone command services; computing device command services; URL services; contact element (group) services; dynamic URL services; auto-generated URL services; encoded URL services; encoded dynamic URL services; encoded auto-generated URL services; coded data transfer services; shared media page services; shared media posting services; shared (integrated) calendar site services; shared (integrated) communication site services; shared contact data services; shared contact profile (data) services; exchange contact information services; shared location services; shared event services; shared content services; physical object display services; virtual object display services; digital object display services; physical product purchase services; digital product purchase services; virtual product purchase services; website Services; Media page services; Information page services; Shared information page services; Profile page services; Contact profile page services; Business profile page services; Organization profile page services; Social media posting services; Social media posting services; Calendar services; Communication posting services; Notification delivery services; Alert delivery services; Message delivery services; Email / text / mail / information delivery services; Contact data / information processing services; Profile processing / delivery services; Data / information / file delivery services; Event delivery services; Text outgoing services; Call outgoing services; Email outgoing services; Physical goods services; Digital goods services; Virtual goods services; Autonomous services; TaaS (Transportation as a Service) services; HaaS (Housing as a Service) services; Menu services; Services of provided services; Service provider product services; Store services; Online store services; Record services; Menu management services; Service management services; Store management services;Online store management services; record management services; browser (extension) services; computing device application services; computing device OS services; real-time services; partner services; human resources services; owner services; management team services; founder team services; organizational team / group services; scanning services; code scanning services; data sharing services; data exchange services; mobile phone services; computing device services; system application services; application services; cloud services; IaaS (Infrastructure as a Service) services; PaaS (Platform as a Service) services; SaaS (Software as a Service) services; NaaS (Network as a Service) services; data / file / information transmission services; data / file / information placement services; data / file / information availability services; decryption services; encoding services; encryption services; image decryption services; video (clip) decryption services; visual / text pattern decryption Services; Voice pattern decoding services; Transmission frequency decoding services; Image coding services; Video (clip) coding services; Visual / text pattern coding services; Voice pattern coding services; Transmission frequency coding services; Image encryption services; Video (clip) encryption services; Visual / text pattern encryption services; Voice pattern encryption services; Transmission frequency encryption services; Code services; Visual code services; Voice code services; Frequency code services; Optical spectrum code services; NFC services; RFID services; Barcode services; QR code services; Referral tracking services; Product tracking services; Shipment tracking services; Postal tracking services; Tracking services; Progress tracking services; Service parts services; Manufacturing services; Research and development services; Development services; Product fulfillment services; Warehousing services; Storage services; Defect inspection services; Inspection services; Environmental, hygiene, and safety services; Audit services; CPA (Certified Public Accountant) services; Specific business area services; Specific personnel function / role / responsibility services;Job roles / responsibilities services; physical reality services; digital reality services; physical location services; digital location services; virtual location services; mentoring services; group services; statistical services; analytics services; presentation development services; custom design services; AI design services; direct-to-consumer distribution services; direct-to-end-user distribution services; direct distribution center services; e-commerce provider direct sales services; (physical store) store direct sales services; video broadcasting services; frequency broadcasting services; audio broadcasting services; physical product services; digital product services; virtual product services; system-driven product services; application-driven product services; account-driven product services; device-driven product services; AI-driven product services; human-driven product services; physical product services; digital product services; virtual product services; system-driven product services; application-driven product services; account-driven product services; device-driven product services; AI-driven product services; human-driven product services Services; Shopping via account; Shopping via store; Shopping via online store; POS (Point of Sale) direct sales shopping service; Shopping via direct advertising code scan; Financial services; Investment services; Business development services; Curriculum services; Optimization services; Business methodology services; Specification services; Standard services; Procedure (development) services; Program development services; SOW (Scope of Work) services; SOW development services; Literature development services; Project development services; Product development services; Program development services; Organizational development services; Organizational management services; Organizational resource services; Invitation services; Reminder services; Meeting services; Task (management) services; Scheduling services; Virtual assistant services; Anniversary services; Holiday services; Preset / automated services; Guided setup (instruction) services; Lookup services; Command response services; Automated (social media) posting services; Survey services; Quiz services; Testimonial services; Review services; Customer review services;Return services; product return services; screening services; PR (personal public relations) services; talent management services; reputation management services; photo display services; photo gallery services; interactive video services; interactive avatar (chat) services; comparative product / service price inquiry services; product comparison inquiry services; comparative product / service inquiry services; research services for any item; research services for content / products / services / organizations / people; verification services for content / products / services / organizations / people; verification services for any item; verification services; research services; labor services; contract services; advisory services; protection services; document presentation services for signatures; document preparation services for signatures; document services for signatures; signature services; authentication services; virtual object customization services Services; virtual object creation services; services for integrating virtual objects into virtual worlds; virtual object sharing services; virtual object services; digital object services; physical object services; missing persons services; missing animal services; collaborative gaming services; online gaming services; metaverse gaming services; virtual reality gaming services; and, where applicable, any services, and / or related services, and / or any virtual / digital equivalent services, and / or any similar services, and / or any variations of the services; and / or any number of services, and / or combinations thereof; in addition to the above, where applicable, anything related to the services may be an encoded object if the term “encoded” or “encodeable” used in describing a service refers to an encoded object as described herein. The following are additional examples of services: Shared services (rides, housing, files, etc.); scanned (QR) code entry (physical, digital, virtual…access) services; third-party services (products, systems, networks, applications, content, etc.); physical (security) access services (doors, elevators, events, rooms, areas, places, buildings, facilities, gates, vending machines, vehicles, equipment, home appliances, public utility systems, physical systems, etc.);Digital (security) access services (systems, system services, data, information, applications, networks, Wi-Fi networks, frequency networks, transmission networks); AI generation services (data, information, content, media, profiles, manufacturing, websites, apps, construction, business, computing, games, currency, paid services, literature, contracts, agreements, financial automation, automated trading, and any applicable AI generation services); ;Games and game services (products, paid but profitable, Web 2.0, Web 3.0, cryptography, real-world integration, gambling, standards, current, still under development, etc.);Financial services (banking, credit, loans, trading, automated trading, currency transfers, planning, management, investment, commodities, real estate, stocks, cryptography, fiat currency, currency exchange, etc.);Insurance services (automobile, housing, business, life, etc.);Activity services (dating, events, games, sports, hobbies, enthusiasts, etc.);Information services (files, content, code, images, photos, videos);Gift services Services (lead generation, contact recommendation, shopping, idea generation (for personal / others), list creation, automated purchasing, automated fulfillment, etc.); (online) store services (AI management, creation, inventory management, product manufacturing, product fulfillment, etc.); business (resource) services (personnel, materials, equipment, services, HR, management, recruitment, benefits, legal, contracting, etc.); real estate services (commercial, residential, short-term, long-term, lease, rental, purchase, services, agreement, contract, storage, management, marketing, advertising, tenants, tenant matching, investment, etc.) Productivity services (individual, business, etc.); Productivity (software / SaaS) app services (business, individual, marketing, advertising, sales, project management, resource management, product management, booking calendar, email, shared mail inbox, communications, CRM, support, accounting, forms, documents, storage, customer engagement, signatures, mapping, processes, systems, affiliate, phone / voice, social media, email / SMS campaigns, marketing campaigns, surveys, websites, analytics, event management, webinars, e-commerce, marketing automation, business / web funnel, inventory, payment processing, meetings, clients, customers, files, data, specifications, procedures, fulfillment, communities, groups, employees, contractors, recruitment, scheduling, support tickets, coaching, training, bug tracking, developers, business networking, message boards, etc.); Telephony services (telephone, IVR, call attendant, messaging, automated response, call center, etc.);Service center services (reservations, virtual business addresses, on-demand use, mail processing / scanning, events, facilities, education, entertainment, training, etc.); GPS (live location) services; reservation services (reservations, events, travel, hotels, accommodations, services, concert tickets, etc.); (network, cross-promotion) services (paid, free, white label, barter, referral, affiliate, joint venture, etc.); event ticketing services; (data) organization services; URL services (tracking, management, organization, data mining of related sites, data processing of related sites, saving / sharing favorites, etc.); (mobile) (device) data services (backup, archiving, synchronization, processing, sharing, saving, transfer, protection, deletion, organization, etc.); data scraping (networked data, web pages, browser web pages, accounts, storage, accessed device files, etc.); celebrity / animal meetup experience services (paid, free, video / audio) Remote, local live, event-focused, athletes, business icons, celebrities, influencers, changemakers, etc.; Alumni services (networking, events, connections, subscriptions, related member search, automated association, benefits, reconnection, etc.); Environmental services (sustainability, food, animal welfare, waste management, charity, conservation, etc.); Charity services; (residential / commercial / provider) public utility services (gas, electricity, solar, water, waste, recycling, regeneration, donations, etc.); Alarm / monitoring services (emergencies, elderly, children, disabled, weather, civil unrest, opportunities, jobs / recruitment, events, projects, etc.); Creative services (art, artists, musicians, performers, actors, producers, showcases, galleries, receptions, etc.); Interactive (social / live) services (voice / video chat rooms, posts, news, topics, etc.); Communication messaging services (peer-to-peer, peer-to-AI / bot, live, latency, voice, audio, images, video, etc.)(AI or Artificial Intelligence) Avatar (related) services (user appearance, user representation, greeting-based, virtual attendant / assistant, virtual greeter, co-pilot); (AI) Machine Learning services (accessing internal / external "user" information to provide user services, including those listed herein); System applications / services (software, software as a service, transportation as a service, infrastructure as a service, platform as a service, serverless computing, mobile applications, desktop applications, browser (extension) applications, etc.) (including similar to those available online (including app stores)); Data computation / processing services (research, analysis, computation, solution, modeling, prediction, transformation, action decision, etc.); (AI) Automated building services (business, organization, integration (referral, affiliate, joint venture, partnership, etc.), services performed by integration (as disclosed herein), print-on-demand On-demand, made-on-demand, construction-on-demand, project-on-demand, solutions, etc.); Fraud detection services (personal / business information, impersonation, system / service / app access, verification, deepfakes (voice, voice, video, appearance, etc.)); (ADA) Accessibility services (hearing, visual, learning, mobility, etc.); Process modeling services (diagrams, charts, visual representations, etc.); Digital (summary) dashboards; Coaching / training services (life, wellness, counseling, etc.); Physician (private practice) services (medical, alternative, preventive, etc.); (personal) monitoring (reporting) services (implantable devices, wearable devices, user input, location tracking, vital signs, exercise, exercise programs, inventory tracking, maintenance schedules, security, systems, etc.); (AI / automation) file / folder organization services (structured, internal / external, photo, related event-based, etc.); (money, billing, collection, etc.) management services (recurring payments, summaries, savings opportunities, comparison offers, unsubscriptions; accounting, money management, optimization, etc.); Secure (encrypted) communication services;Physical mail services (processing, routing, tracking, address changes / updates, etc.); rental services (autonomous vehicles, vehicles, storage, charging, event spaces, venues, facilities, etc.); AI robotics integration; automated (personal / business) network construction services; fulfillment services (procurement, construction, shipping, storage, supply, distribution, etc.). While the above services are illustrative, one or more terms used in one or more descriptions of one or more of the above services may be combined with one or more other terms in one or more descriptions of one or more other services and / or other services described herein to describe one or more different illustrative services, insofar as they are applicable to the tools and techniques described herein. Furthermore, references to services or types of services herein include references to the above services insofar as they are applicable in the context of references to one or more of the services herein.

[0101] Multiple different tools and techniques for computer service systems, as described herein, can produce technical advantages that enable the creation of improved computer systems that provide services through computer systems and manage the code linked to them in a more efficient and useful way than previous systems.

[0102] User accounts managed by a computer service system may be a mixture of accounts for human users (for example, each account may be for a single user, a group of users, or an organization such as a company, a group of companies, or a part of a company) and accounts for artificial intelligence bots. An artificial intelligence bot may be configured to analyze output from a system, which is typically provided to human users, and to analyze such output and return responsive user input to the system. Of course, the bot itself may operate within the system, resulting in such user input being provided from one part of the system in which the bot operates to another. Thus, providing input from an artificial intelligence bot designed to provide input similar to that from a human user is considered user input in this specification. The use and interaction of artificial intelligence bots in a system can provide additional efficiency by reducing the time and effort required for human users to interact with the system. Furthermore, artificial intelligence bots can provide more repeatable and reliable analysis and input in certain situations, particularly when tasks related to similar services and code are repeatedly performed within the system.

[0103] Where used herein, a user account is a dataset representing entities such as human users, artificial intelligence bot users, groups of human users, and computing resources. Where a user account is referred to performing an action (such as sending or receiving), that action is considered to be performed by that user account if it is performed by a computer component in the environment in which the user account is active (for example, if the user account is logged into an environment and that environment controls the execution of the action). In many cases, such actions by or for a user account are also performed by or for the human user or artificial intelligence bot user corresponding to that user account. For example, this may be the case if a user account is logged into and active in a computer application and / or computing device that is performing an action for that user account on behalf of the corresponding human user or artificial intelligence bot user. To give some specific examples, the usage of this user account terminology applies to references to user accounts that provide user input, receive responses, or interact with computer components as described herein.

[0104] The subject matter defined in the attached claims is not necessarily limited to the advantages described herein. Specific embodiments of the invention may provide all, some, or none of the advantages described herein. While the processes for various methods are described herein sequentially in a specific order for ease of explanation, it should be understood that the embodiments described herein are inclusive of any reordering of the processing order, unless a specific order is required. For example, processes described sequentially may, in some cases, be reordered or performed simultaneously. Also, for simplification, flowcharts may not show the various ways in which a particular method may be used in conjunction with other methods. Furthermore, it should be understood that singular and plural references throughout this application are non-limiting and should be understood as encompassing both singular and plural (e.g., one or more of those referred to in the singular or plural form). Also, the concepts of user interfaces described herein may be replicated for use by users via avatars in immersive virtual reality or augmented reality environments. Furthermore, it should be understood that certain areas of this disclosure can stand alone without depending on other areas of this disclosure, and as a result, problems or defects in such areas of this disclosure do not necessarily cause similar problems or defects in other areas of this disclosure.

[0105] Structured services with associated service records may be drilled down to specialize in niches, and / or to the organization or any part of that organization, to the extent feasible and desired, thereby making available any number / types / variations of system services and integrated system services, to the extent feasible and desired. Structured services can range from broad (public) to niche (account) and / or specific (private).

[0106] The techniques described herein may be used in conjunction with one or more of the systems described herein, and / or with one or more other systems. For example, the various procedures described herein may be implemented by hardware, software, or a combination of both. For example, the processor, memory, storage, output device, input device, and / or communication connection described below with reference to Figure 3 may each be at least part of one or more hardware components. One or more of the techniques described herein may be implemented by configuring dedicated hardware logic components. For example, but not limited to, such hardware logic components may include field-programmable gate arrays (FPGAs), integrated circuits for specific programs (ASICs), standard products for specific programs (ASSPs), system-on-a-chip (SoC) systems, complex programmable logic devices (CPLDs), and the like. Applications, which may include various forms of devices and systems, may broadly include a wide range of electronic and computer systems. The techniques may be implemented using two or more interconnected specific hardware modules or devices, together with relevant control signals and data signals that can communicate between and through the modules, or as part of an integrated circuit for a specific application. Furthermore, the techniques described herein can be implemented by software programs executable by a computer system. Examples may include distributed processing, component / object distributed processing, and parallel processing. Additionally, virtual computer system processing may be configured to implement one or more of the techniques or functions described herein.

[0107] I. Computer Service Systems and Environment The communications between the various devices and components described herein may be transmitted using hardware within a single computing device, hardware within multiple computing devices, and / or computer system hardware such as computer network hardware. A communication or data item can be considered transmitted to a destination by a component if the component passes the communication or data item to the system in a manner that instructs the system to route the communication or data item to the destination, for example, by including an appropriate identifier or address associated with the destination. Furthermore, data items may be transmitted in multiple ways, for example, by directly transmitting the item or by transmitting a notice containing an address or pointer used by the receiver to access the data item. In addition, multiple requests may be transmitted by transmitting a single request requesting the execution of multiple tasks.

[0108] The components of the computer service system 100 are described here with reference to Figure 1. System 100 may be a live information management, service, sharing, and collaboration platform, including linked interactive contacts, calendars, profiles, groups, and services. Each component may include hardware and software. For example, the components in Figure 1 may be implemented entirely by computer hardware, such as in a system-on-chip configuration. Alternatively, the components may be configured according to computer software and implemented by computer hardware running that computer software. The components may be distributed across computing machines or combined into a single computing machine in various ways. For example, a single component may be distributed across multiple different computing machines (e.g., some of the component's processing may run on one or more client computing devices, while other processing of the component runs on one or more server machines).

[0109] The computer service system 100 may include an encoded object 110. The encoded object 110 may include a contact element. This contact element may be a trigger code that triggers the system execution of a system service, and may be a scannable code such as a code 112 containing a visual pattern and / or a transmittable code 114 stored in a device. For example, the code 112 containing a visual pattern may be a one-dimensional barcode, a two-dimensional barcode such as a QR code, or another visual pattern such as a pattern encoding a trigger uniform resource locator. The device storing the transmittable code 114 may be a device capable of providing the code in a transmittable form, such as a code transmittable by a radio signal such as a frequency signal and / or a digital signal. For example, the device storing the transmittable code 114 may be an RFID tag or a near-field communication device. In one embodiment, the contact element may be a text identifier that can be manually entered into the computing device, such as a uniform resource locator (e.g., a website address). The encoded object 110 may be any physical object that can contain a scannable code, such as an item that can display a visual code or contain a transmittable code. For example, the encoded object 110 could be a sign (as shown in Figure 1), a card, a wearable item such as a wristband (e.g., a bracelet or watch), a keychain, a neckband (e.g., a necklace or lanyard), clothing, or other types of items useful for other purposes (e.g., a mug, product packaging, paper, adhesive items, labels, a case for housing other items such as a computing device). Alternatively, the encoded object 110 could be a computing device such as a user device 120. For example, such a user device 120 may have a visual code printed on the device housing. The user device 120 may also display the visual code on a device display screen. In addition, the user device 120 may include a transmittable code.User device 120 can transmit this transmittable code via a wired or wireless connection, such as by transmitting the code to other user devices 120 using a protocol such as a short-range wireless communication protocol. Encoded objects 110 may be mass-produced or custom-produced. Encoded objects are provided to the end user along with the code already contained in the encoded object 110. In addition, the code for multiple encoded objects 110 can be serialized, and such serialized code can be used to track the provider of the encoded object 110, for example, to award credit to such provider through their user account. Encoded objects may also be digital objects such as digital files, encoded virtual goods available in virtual reality and / or augmented reality computing environments, and these may be combinations of different physical and / or digital objects. Encoded objects are described here, but the computer service system 100 can manage both encoded and unencoded objects by including references to encoded and / or unencoded objects in linked records, for example, as described herein.

[0110] The user device 120 may include any of the various computing devices that the user can handle, such as a mobile device 122 (e.g., a smartphone or tablet computer). The mobile device 122 may run a dedicated software application (app), such as a service app 124, which may be a dedicated app designed to work with a subsystem for providing computer services. The mobile device 122 may also run a third-party app 126, which is an app that primarily provides services other than computer services of a dedicated service subsystem, such as a service code subsystem, but the third-party app 126 may also provide and receive data from the dedicated service subsystem. As an example, the third-party app 126 may be a camera app, a near-field communication app, or other apps such as a shopping app that includes a program for scanning codes.

[0111] Furthermore, the user device 120 may include a desktop computer 130, which may be a desktop terminal. The desktop computer 130 may run software applications such as a general-purpose web browser 134, which may be used to browse web pages. The desktop computer 130 may also run specific dedicated applications, such as service applications, and other third-party applications. One or more such applications may be used in computer services and other computer services linked to code as described herein. A human user 132 may use the user device 120 (providing user input to the user device 120 and / or receiving presentation output from the user device 120), but the human user is not considered part of the computer service system 100. In fact, the human user 132 may be scanned in a biometric scanning process, but the human user is still not considered part of the computer service system 100. Instead, the computer service system 100 may operate for or against the human user 132.

[0112] User device 120 can communicate with other computer devices within the computer service system 100 via a network. This network may be a wired network and / or a wireless network. In fact, such a network may involve two computing devices communicating directly with each other (as in a peer-to-peer connection) using, for example, protocols, short-range wireless communication, wired communication, or other types of communication. Alternatively, devices may communicate with each other via network 140 in a client-server configuration.

[0113] The service subsystem 150 may be a computer subsystem capable of communicating with the user device 120 via the network 140. For example, the service subsystem 150 can operate as a cloud-based server system. This cloud-based server system can interact with the user device 120, for example, via a service application 124 such as a code service application, a third-party application 126, and / or a browser 134.

[0114] The service subsystem 150 may include an account manager 160, which can manage an account store 162. This account store 162 may be a data store capable of storing user accounts 164. This user account 164 may include a profile 165 for the user account 164. The account manager 160 may interact with other subsystems in addition to the service subsystem 150, and may interact with other management components.

[0115] Furthermore, the service subsystem 150 may include a service code data manager 170, which can manage a service code data store 172. This service code data store 172 can store service data structures 174 that can be linked to user accounts 164. For example, a user account 164 may enumerate identifiers for each of the one or more service data structures 174 linked to that user account 164, and / or, a service data structure 174 may enumerate one or more identifiers for each of the one or more user accounts 164 linked to that service data structure 174.

[0116] The service subsystem 150 may also include a user interface manager that can interface with other components that interface with the user. Each user interface manager may interact with the account manager 160 and / or the service code data manager 170, and each may interact with the user or with other components that interact with the user. For example, a service application manager 180, such as a code service application manager, may interact with the user device 120 using a dedicated service application 124 that runs on the user device. For example, one or both of the service application manager 180 and the service application 124 may store data and computer-readable instructions relating to the presentation and functionality of the user interface for the computer services described herein.

[0117] Furthermore, the user interface manager may include a service web manager 182, which can interact with a user device 120 running a browser 134. For example, the service web manager 182 can store and provide user interface data (such as web pages and web page templates) and backend functions for web pages for computer services described herein.

[0118] Furthermore, the user interface manager may include one or more additional app / web managers 184, which may or may not be managers dedicated to computer services.

[0119] The user interface manager may also include an artificial intelligence bot manager 186. The artificial intelligence bot manager 186 runs in conjunction with the artificial intelligence bot 190 and can further / or interact with the artificial intelligence bot 190. The artificial intelligence bot 190 can operate for the computer service system 100 to perform actions that would otherwise be performed by human users and user devices 120. The bot 190 can run on a bot platform 192, which can provide functionality for the bots but allows for the customization of individual bots 190 according to their individual usage scenarios.

[0120] An example of a hierarchical service data structure 174 will be explained with reference to the schematic diagram of the service data structure 174 in Figure 2. The service data structure 174 may include multiple levels in which records and record categories (for example, portfolios for organizing typically non-profile or non-contact records and categories, and contact groups for organizing profiles or contacts, as described later) can be included in the data structure. For example, the top-level level 1 210 may include top category 1A 212. All other categories and records may be subordinate to top-level category 1A 212. However, the data structure may include more than one top-level category, and the top level may include records in addition to categories. Each category may include a category description title that applies to the child categories and records within that category. This title may be displayed on the user display when the user input device is displaying the navigation and record wallet display screens for the service data structure 174.

[0121] Furthermore, the example service data structure 174 may include a level 2 220 below level 1 210. Level 2 220 may include one or more service code categories and / or one or more records. In this example, level 2 220 includes multiple categories, category 2A 222, category 2B 224, ... category 2N 226 (where "N" represents the number of categories in level 2 220), all belonging to category 1A 212. For the purposes of this explanation, category 1A 212 can be considered the "parent" category of the categories in level 2 220, and the categories in level 2 220 can be considered the "child" categories of category 1A 212. Similarly, the children of children within a category (and children of children of children, etc.) can also be considered to belong to that category and are descendants of that category. The parent of a parent of a category or record (and parents of parents of parents, etc.) can be considered the ancestor of that category or record.

[0122] Level 3 230 is subordinate to Level 2 220 and can include additional categories, subcategories within Category 2A 222 such as Category 3A 232 and Category 3B 234, Category 3C 236 within Category 2B 224, ... Category 3N 238 within Category 2N 226. Level 4 240 is subordinate to Level 3 230 and can include additional categories and records, Category 4A 242 within Category 3A 232, Category 4B 244 within Category 3B 234, Available Record 4A 246 within Category 3C 236, ... Category 4N 248 within Category 3N 238.

[0123] An available record, such as available record 4A 246, may be a record that can be linked to a user account to which the current service data structure 174 is linked. For example, an available record may be selected by user input from a linked account to be added to a linked record in the account. This may or may not require the transfer of some value (e.g., a monetary payment) as consideration for linking the record. A linked record may be a record that is already linked to a user account so that the functionality of that record (e.g., setting up the record in response to the receipt of a code indicated in the record and providing a service) is available to that user account.

[0124] Referring further to Figure 2, Level 5 250 is a subcategory of Level 4 240 and can include linked record 5A 252, linked record 5B 254, and available record 5A 256 within Category 4A 242. Level 5 250 can also include Category 5A 258 as a subcategory within Category 4B, ... linked service record 5N 264 and available service record 5N 266 within Category 4N 248. The service data structure 174 may continue with additional records and categories in additional levels below Level 5 250.

[0125] The service data structure 174 may include links between categories and categories and records within those categories. Such links can be implemented in various ways. For example, each category may include references to identifiers for all of its direct child categories and parent categories, and references to all of its direct child categories. Each record may include a reference to its direct parent category. In one embodiment, each category and each record may include references to all of its direct and indirect ancestor categories, and references to all of its direct and indirect descendant categories and records.

[0126] Categories (including record-level categories, the lowest level categories that include records but may not include subcategories) may be defined more specifically or broadly as needed and as desired. For example, a record-level category may be a “For Sale” category, or a record-level category may simply be a “Sign.” Access to a specified service category, record, and / or record service may be free or require payment. For example, access to one service category may be free, while access to another service category may be restricted to user accounts designated as having access to such categories (e.g., where an indicator in the system indicates that such user account has access to that category). If a user account makes a new payment for access to a service category, record, and / or record service, referral credits may be applied to the user account that provided the encoding that triggered the payment for such access, the user account that shared the item that led to the payment for such access, and / or the user account that sent the record that led to the payment for such access.

[0127] As described herein, the following are examples of operations that may be performed by a computer service system: managing payment transactions; generating trigger uniform resource locators encoded into scannable code; generating scannable code; generating web pages and websites; generating records and categories and including them in a data structure; setting default services for records within categories; linking records to user accounts; sending encoding specifications to manufacturers or printers for production; and processing orders for encodings. Users may also perform actions such as receiving and using authenticated and activated encodings; providing user input to instruct the system when managing records via their user accounts; and providing user input to instruct the system when managing service pages (such as web pages) via their user accounts.

[0128] Reusable quick links may be used for target uniform resource locators linked to scannable codes. These quick links may be made available and usable when a scannable code is presented. If a scannable code is no longer used in the system, the quick link may be included in storage so that it can be accessed and used later along with other scannable codes. This provides a short web address that the user can quickly type into a browser, rather than relying on the automatic use of the uniform resource locator from the scanning operation. With respect to such quick links, the short-lived and dynamic nature of the quick links may be used to avoid advertising or posting of the quick links. To reduce the number of unique codes, such as QR codes, used, reusable codes for on-the-fly sharing may be generated by the computer system. Such reusable codes may be presented when dynamically linked scanned code data changes in the background. This reusable code may be linked to a quick link.

[0129] II. Exemplary Computing Environments Figure 3 shows a generalized example of a preferred computing environment 300 in which one or more of the embodiments described may be implemented. For example, one or more such computing environments may be used as a device in a service subsystem, a third-party subsystem, a user device, or other device in a computer service system. Generally, a variety of different computing system configurations can be used. Generally, they vary considerably. Examples of well-known computing system configurations that may be suitable for use with the tools and techniques described herein include, but are not limited to, server farms and server clusters, personal computers, server computers, smartphones, laptop devices, slate devices, game consoles, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices.

[0130] Since the present invention can be implemented in a variety of computing environments, computing environment 300 is not intended to imply any limitation on the scope of use or functionality of the present invention.

[0131] Referring to Figure 3, various hardware-based computer components illustrated are described. As described below, these hardware components can store and / or execute software. The computing environment 300 includes at least one processing unit or processor 310 and memory 320. In Figure 3, this most basic configuration 330 is enclosed within the dashed lines. The processing unit 310 executes computer-executable instructions and may be a real processor or a virtual processor. In a multiprocessing system, multiple processing units execute computer-executable instructions to increase processing power. The memory 320 may be volatile memory (e.g., registers, cache, RAM), non-volatile memory (e.g., ROM, EEPROM, flash memory), or a combination of the two. The memory 320 stores software 380 that implements computer services. The implementation of computer services may include, in place of or in addition to the software 380, the implementation of all or part of the operation of the processor 310 and memory 320 in hardware logic.

[0132] Although the various blocks in Figure 3 are shown with lines for clarity, in reality, drawing lines between the various components is not so clear, and figuratively speaking, the lines in Figure 3 and other figures described herein would be more precisely gray and blurred. For example, a presentation component such as a display device (for example, if the display screen includes a touchscreen) can be considered an I / O component. Also, a processor has memory. The inventors recognize that such things are the nature of the art and reiterate that the diagram in Figure 3 is merely to illustrate an exemplary computing device that may be used in relation to one or more aspects of the art described herein. There is no distinction between categories such as “workstation,” “server,” “laptop,” and “portable device,” and these are all considered to be within the scope of Figure 3 and the references to “computer,” “computing environment,” or “computing device.”

[0133] The computing environment 300 may have additional functions. In Figure 3, the computing environment 300 includes storage 340, one or more input devices 350, one or more output devices 360, and one or more communication connections 370. An interconnection mechanism (not shown), such as a bus, controller, or network, connects the components of the computing environment 300 to each other. Typically, operating system software (not shown) provides an operating environment for other software running within the computing environment 300 and coordinates the operation of the components of the computing environment 300.

[0134] The memory 320 may include storage 340 (which is depicted separately in Figure 3 for convenience), which may be removable or non-removable and may include computer-readable storage media such as flash drives, magnetic disks, magnetic tapes or cassettes, CD-ROMs, CD-RWs, or DVDs. These storage media are available for storing information and are accessible within the computing environment 300. The storage 340 stores instructions for the software 380.

[0135] The input device 350 may be one or more of a variety of different input devices. For example, the input device 350 may include user devices such as a mouse, keyboard, trackball, or augmented reality interface device. The input device 350 may implement one or more natural user interface techniques such as speech recognition, touch and stylus recognition, gesture recognition when adjacent to the input device 350 while in contact with the input device 350, air gesture recognition, head and eye tracking, voice and speech recognition, detection of the user's brain activity (e.g., using EEG and related methods), and machine intelligence (e.g., using machine intelligence to understand the user's intentions and goals). As another example, the input device 350 may include a scanning device, network adapter, CD / DVD reader, thumb drive or other type of removable storage or memory, or other devices that provide input to the computing environment 300. The output device 360 ​​may be a display, printer, 3D printer, speaker, CD / DVD writer, network adapter, computer-controlled machinery, home appliance, door or other barrier, vehicle, augmentation or virtual reality output device such as goggles, or other device that provides output from the computing environment 300. Examples of output from the output device 360 ​​include physical action triggers, warnings, commands (e.g., mail / delivery fulfillment instructions, drone drop-off instructions, ride-hailing service pickup / drop-off instructions), and / or physical tasks initiated by a computer. The input device 350 and the output device 360 ​​may be integrated into a single system or device such as a touchscreen or virtual reality system.

[0136] The communication connection 370 enables communication to other computing entities via a communication medium. In addition, the functionality of the components of the computing environment 300 may be implemented on a single computing machine or on multiple computing machines that can communicate via the communication connection. Therefore, the computing environment 300 may operate in a network environment using logical connections to one or more remote computing devices, such as handheld computing devices, personal computers, servers, routers, network PCs, peer devices, or other common network nodes. The communication medium transmits information, such as data or computer-executable instructions or requests, in a modulated data signal. A modulated data signal is a signal in which one or more of its properties are set or modified to encode information within the signal. For example, the communication medium includes, but is not limited to, wired and / or wireless methods implemented by electricity, light, RF, infrared, acoustics, or other carrier waves.

[0137] This tool and method can be described in the general context of computer-readable media, which may be storage media or communication media. Computer-readable storage media are any available storage media accessible within a computing environment, but the term computer-readable storage media does not mean the propagating signal itself. For example, in computing environment 300, computer-readable storage media include, but are not limited to, memory 320, storage 340, and any combination thereof.

[0138] This tool and technique can be described in the general context of computer-executable instructions, such as those contained in a program module and executed on a target real or virtual processor in a computing environment. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or realize a specific abstract data type. The functionality of program modules can be combined or separated among program modules as desired in various ways. Computer-executable instructions for program modules can be executed in a local or distributed computing environment. In a distributed computing environment, program modules can reside on both local and remote computer storage media.

[0139] For illustrative purposes, this detailed description uses terms such as “decision,” “selection,” “adjustment,” and “action” to describe computer processes in a computing environment. These terms, and other similar terms, describe processes performed by a computer at a high level and should not be confused with human actions unless explicitly stated that a human (such as a “user”) is performing the action. The actual computer processes corresponding to these terms will vary depending on the implementation.

[0140] III. Examples of technically advantageous features The following describes some examples of advantageous computer service features that create technical advantages not present in conventional systems. These advantages can overcome problems specific to computer systems, such as the use of code in computer systems and / or the provision of services using computer systems, for example, inefficiencies in providing computer services and / or inefficiencies in using scannable code. These features can be used individually or in different combinations and / or in combination with other features described herein. Such combinations can also create technical advantages not present in conventional systems.

[0141] A. Structured Category Hierarchy for Records Records such as available records and linked records as described herein may be included in a service data structure for an account. The service data structure may include categories and subcategories of records and a hierarchy of records within those categories. This structure can be used to provide structured, hierarchical navigation of categories and records, such as code records, using the user interface of a user device. This hierarchical structure of service record categories and records can provide an efficient foundation for the system to provide user interface navigation through organized categories and records. Furthermore, such efficient and organized navigation features can reduce the computing resources (memory, network bandwidth, etc.) used when locating desired records and categories in a computer service system.

[0142] B. Paired hierarchical record wallets and navigation pages A pair of interconnected display screens can be used to navigate and manage different levels of the record and category hierarchy. These screens may include a record wallet display and a navigation display, and both displays can be adjusted when user input is given to move the user interface display between different positions or nodes (categories or records) in the hierarchy. The record wallet display may include user interface controls that represent the record at the current node in the hierarchy. The record wallet display may also include selectable user interface controls to switch from the record wallet display to the navigation display while remaining at the same current node in the hierarchy. The navigation display may include user interface controls for navigating to the record wallet display for the current node and for navigating to each node of each ancestor category of the current node. The navigation display may also include other user controls such as a status control for the status of records linked to a user account, a selectable action item control to indicate action items awaiting user input, and a selectable retrieved data control to indicate code linkage service data retrieved by the system for the user account. Both the Record Wallet view and the Navigation view may include one or more user interface controls, such as a selectable Live User Interface control for displaying a display for scanning a code and / or a display for sharing the app with other devices. As described herein, a record may include a service code, a service record, or a combination thereof. The Live User Interface may also work in conjunction with the device's Global Positioning System to find nearby services, activities, products, geofenced users and / or items, other app users, and / or other nearby items.The characteristics and associated data and services of nearby items may be integrated with third-party systems and / or provided directly to and / or from the system via owner accounts made available by the system. A live user interface can provide live feed services, such as services delivered in real time.

[0143] Paired hierarchical record wallets and navigation pages can provide more efficient navigation to desired user interface controls and displays regarding service code categories and records within a hierarchy linked to user accounts. Specifically, they enable navigation with fewer user input requests and fewer additional screen displays, thus reducing the time and effort of human users or the time and resources of the computer system used to manage service code categories and records within the hierarchy. User interfaces can continue to be placed in familiar locations for navigation features and functions, which helps to facilitate ease of use by users with different technical abilities, improves the computer system, and brings easy access to the tools and techniques described herein to a wider population.

[0144] C. Transfer of records and / or codes User input may be provided requesting the transfer of records to different locations linked to the same user account (e.g., to different organization designations and possibly different service data structures for the same user account), or to different user accounts. This would ensure that the transferred records are transferred along with a representation of their ancestor categories, and after the transfer, the records can be included in the new service data structure along with those same ancestor categories. The transfer may be carried out in different ways in different embodiments, for example, by changing links such as references, and / or by moving data from one storage location to another.

[0145] Scannable codes can be transferred between records. For example, a code linked to a first record may be unlinked from the first record and linked to a different second record. Such transfers of scannable codes between records may occur in response to user input from an account linked as the owner of the source record to which the scannable code is being transferred. All or part of the data that has been retrieved and linked to the sending record (the source record to which the code is being transferred) may also be transferred to the receiving record (the destination record to which the code is being transferred). This may include linking the retrieved data to the receiving record. For example, a new code may be retrieved for the sending record by generating a new code and / or transferring a code from another third record. In some cases, user input may instruct the sending record to be deleted after the transferred code has been successfully transferred to the receiving record. Sending and receiving records may belong to the same or different categories or organizations. Also, sending and receiving records may be linked to the same user account owner or to different user account owners. The transferability of records associated with physical encoded objects enables the exchange of management of these encoded objects between accounts, allowing the user or group currently managing an encoded object to transfer it to a different user. For encoded objects that appear in various locations (both local and remote), the user or group currently managing the encoded object only needs to seamlessly transfer some or all of the records corresponding to the other user or group when a new object manager exists (for example, when management rights of the entity managing the record and encoded object are transferred).

[0146] D. Customizing records and categories using current conditions Records and categories can be customized using current conditions. As used herein, current conditions are conditions that may change over time so that different tools and methods become appropriate as the conditions change. For example, such changes may include making different records available, making different services available for specific records, and making different service code categories available. Examples of such conditions may include data within an account such as the preferences, age, and / or gender of a representative human user; the current date and time; the location of the user device; the current or forecast weather at the current location; events occurring at or near the current location; the current speed of the user device requesting the service; and preferences indicated in the system for the user account requesting the service. Conditions for structured categories and associated records may also take into account user account rankings. Such rankings may be based on one or more factors such as the activity level of a user account and / or the amount paid by or on behalf of the user account. Such conditions and other conditions may be entered individually or in combination with other conditions, resulting in rule-based real-time adaptations based on such conditions. A computer service system may store rules that specify what conditions are and when / how they affect the system's operation, for example, which services, service records, and / or categories are offered, and perhaps how specific services are offered. Conditions for categories and associated services (e.g., various apps, games, stores, software services, customer service, etc.) may be set by applicable administrators (e.g., system administrators, account managers, account agents, etc.) at any applicable level of the service data structure. For example, administrators may be people and / or bots.In addition, conditions based on account status and available information may also be used as conditions, such as verified or unverified account status; the number and type of things or assets and / or their association with other accounts or account types; the type of categories, records, and services (e.g., games, productivity apps, and other apps); businesses, services, products, content, posts, articles, events, subscriptions, networks, charities, groups, and / or other affiliations; public / private information / records (such as arrests, awards, associations, health, wellness, demographics, abilities, physical characteristics, assets, clubs, positions, roles, business roles / affiliations); political / religious preferences; travel / residency history; contact connections; service providers; causes of interest, charities, events, literature, television, movies, hobbies, etc.; and / or other available (lawfully / by agreement) owner-related information / associations.

[0147] Condition-based customization can provide a more efficient, useful, and even safer computer service system. For example, customization may avoid providing services that are unsafe or undesirable in certain circumstances. For instance, if a computerized source of weather information indicates current severe weather at the user's current location, some services that could be dangerous during severe weather may not be provided. Another example is a service that is illegal in a particular location, which may not be provided if the user device is determined to be currently in that location. Yet another example is a service that is unlikely to be considered useful for the current conditions, which may not be provided. For example, with regard to a real estate search service, if the requesting user account indicates that the requesting user's family does not have school-age children, information about local schools, along with other information, may not be provided. In such situations, the computer system can avoid wasting the time and effort of the user and / or the computer system's resources. Furthermore, this and other efficiencies described herein may also lead to a reduction in the response time for the computer system to provide other services that are deemed appropriate for the current conditions. The conditions may relate to one or more augmented reality and / or virtual reality environments.

[0148] E. Referral credits and tracking A user account may be credited for referring a new user account to the computer service system. For example, such a referral may take the form of a user account providing a referral code to refer another user to the computer service system. In one example of such a referral, the referring user account may include a referral code, such as a QR code, for that user account. When another user device scans that QR code, the scanning user's device can decode a uniform resource locator that can trigger the device to initiate the process of joining the scanning user by setting up a new account. Alternatively, the scanning user's device may receive a referral code or identifier linked to the referring user account within the computer service system, or such a referral code or identifier may be provided to the service subsystem and linked to the scanning user's new account. In one scenario, the referral code or identifier for the referring user account may be provided directly at the time of scanning, or it may be stored on the scanning user's device (e.g., as a cookie) until the scanning user takes action (such as setting up a new account or ordering a paid service from the computer service system). In either case, the service subsystem 150 may store the suggestion of credit for referrals within the service subsystem, for example, in the referring user's account or in a location linked to the referring user's account. The credit may be credit that enables the referring user to benefit, such as the computer service system providing additional services or functions, or sending money digitally or physically to the user represented by the referring user account. Alternatively, scanning the referral code may prompt the system to apply the credit to the user account to which the code was shared after initiating a system sharing service that starts setting up a new user account on the scanned device.This may be done as part of a service such as an information sharing service (e.g., exchanging contact information, event invitations, transferring ebooks, etc.) or as part of another service. Referral tracking may be based on augmented reality and / or virtual reality referrals. Conventional sending, sharing, and / or delivery of referral links may also be tracked. For example, the link may be shared via one or more sharing options available on a mobile device, such as email, SMS, or other messaging services. Alternatively, a code associated with the referral link (e.g., a QR code) may be embedded in the transmitted encoding for scanning by the recipient. The system's response to the referral code may set a predetermined (e.g., pre-built) category in the scanning and / or receiving app. This may be applied immediately (perhaps with an installation confirmation notification requesting permission) if the app is already on the recipient's mobile device, if necessary. If the app is not installed, the option to accept the category template may be incorporated during the setup of a new account (perhaps with a confirmation notification) or via a pending notification for that purpose. The receiving app may also receive user input from the recipient indicating that the receiving user account will complete the setup of a new account at a later date. This could prompt the system to remind the user about the pending account settings in some way (for example, by sending one or more reminder messages using the contact information provided by the recipient user).

[0149] Related record services (or service-related products) accessible by other account users (e.g., via public, group, network, organization, or other shared category record services) that result in a transfer, referral, subscription, or introduction to a new category record service (and related category) may be credited to related immediate and / or future transactions. Integrations (including related service records) may be pre-built by account owners, account administrators, system administrators, and / or app administrators and may be offered for transfer free of charge (possibly with related service fees) or purchased for transfer (possibly with related service fees). Pre-built categories (also referred to herein as integrations) may be made available in various ways, e.g., through private accounts, groups (organizations, networks, etc.), and / or public portfolios and / or portfolio-related marketplaces. Integrations may also be automatically made available for optional installation based on the terms of an account (e.g., user), and / or generally. Integrations may be shared via scans, as described below. In this scenario, the user is notified of the integration's arrival via a notification, allowing them to review it, gain more information, and then decide whether to accept it. The integration may be built in response to user input via a user account, or it may be generated by the system. The integration may be shared with other user accounts as needed, in connection with the send action and / or the sharing notification.

[0150] Similar credit may be granted to providers of coded materials used to set up a new account or to request a specific type of service (e.g., a paid service) from a computer service system. For example, coded materials may be sold or distributed free of charge to customers by a retailer, who receives the coded materials from a distributor, who receives the coded materials from a manufacturer. Codes on coded materials (e.g., visual pattern codes 112 or transmittable codes 114 in a device) may initially be recorded in a database and linked to the provider of the corresponding coded material (manufacturer, distributor, retailer, etc.). For example, these codes may be serialized, and codes belonging to a particular series may originate from a particular group of providers. Thus, if one of the codes on coded materials provided by a group of providers is scanned and used to set up a new user account or request a specific type of service from a service system linked to the code, the computer service system can perform a verification to determine which provider provided the corresponding coded material (by comparing the code from the new account or service request with the code linked to the provider in the system). If one or more matches are found, the computer service system may store a credit indication linked to the user account for the provider in a manner similar to the crediting of referring users as described above. As described herein, the methods for tracking referrals and credits may include crediting at different levels within categories of service data structures.

[0151] These products and referral tracking and crediting methods can improve efficiency and accuracy in providing computer-readable value credits to referrer and product provider accounts that generate computer service system operations (e.g., setting up new accounts or requesting specific types of services through the system) that are deemed beneficial within the system to the operator of the computer service system. For example, the tracking system can avoid manual phone calls, manual maintenance of credit records, manual user input for entering and sending messages about such credits, and manual inspection of products to grant appropriate credits. Furthermore, even manual methods for providing such credits may not have been known prior to this disclosure. Thus, these referral crediting and tracking features can offer significant technical advantages.

[0152] F. Code Safety Check When a user device within the system scans code (for example, to scan the code to request the execution of one or more services linked to the code in a record, or to scan the code to set or edit a record corresponding to the code), safety checks may be performed. For example, safety checks may include forgery checks and / or malicious code checks. If a code fails a safety check, the computer system may take one or more precautionary measures. For example, for forgery checks, the system may check whether the code is included in a list of codes that have been listed as genuine for use in the system. If the code is not found in the list of genuine codes, the system may deny permission to use the code (for example, by not allowing the creation of a record for the code). If the code is found, the system may perform an action to activate the code, thereby allowing the creation of a record for the code (or, if a record has already been created, by allowing the use of the record to revise the record, or by allowing the use of the record to provide the service indicated in the record).

[0153] For example, when a company provides an encoded object to a user, the code may be registered in a canonical code list by a transmission from the company. For instance, an online or physical store provider of a physical item may operate a third-party subsystem 196, which may work in conjunction with one or more third-party applications 126. The third-party subsystem 196 and / or the corresponding third-party application 126 may transmit information about the corresponding code to the service subsystem 150 when providing an encoded object to a user. The service subsystem 150 may receive this code information and store it in a data structure that records a list of canonical codes. For example, such a company can authenticate a code by scanning the code using an application running on a device and transmitting the identifier of the code to be authenticated to the service subsystem 150 via that application. Also, if an encoded item 110 is ordered through the service subsystem 150, the service subsystem 150 may store the code information of the item provided by the system in the same canonical code data structure (which may be held within the service subsystem 150).

[0154] As another example, security checks may include inspection for malicious computer code. For example, this malicious code inspection may include verifying the actions performed when the code is scanned, and inspecting uniform resource locators linked to the code within the computer system. This inspection may also include verifying the data returned when the uniform resource locator is used (e.g., websites, files, commands, etc.). For example, if the code is linked to a website's uniform resource locator, the website may be inspected to check for the presence of known types of malicious computer code, to compare against a list of known malicious websites, to verify valid certificates and / or signatures, and to verify the effective use of security protocols such as TLS. If the code is determined to be malicious, the system may present a warning to the user about the code. The warning may include information indicating the nature of the detected maliciousness (e.g., an invalid certificate, the target website being on a list of malicious sites). The warning may also include user interface controls to instruct the user whether to continue using the code despite the malicious code warning.

[0155] IV. Examples of User Interfaces The following describes examples of visual user interface representations, including user interface displays for computer services.

[0156] Referring to Figure 4, the mobile device 400 (which is a computing device) may have a display screen 410. The mobile device 400 may run an application, such as a camera application, that can scan the code 412 on the encoded object 420. In this example, the code 412 may be a visual pattern placed on the encoded object 420, i.e., a QR code, and the encoded object 420 may be a sales sign or, more generally, an order sign for ordering goods with or without payment (similarly, wherever “sale” is referred to herein, it applies whether the goods are accompanied by payment or not). The sales sign may include instructions such as “Scan the QR code for information and other options.” If such instructions are included, the instructions and the QR code together are considered a contact element group, and the instructions and the code may each be a contact element. The code may be of other types, and the encoded object may also be of other types, provided that the code is scannable and the encoded object can contain the code (e.g., an item with an RFID tag containing the code, or a device containing a transmittable code). The encoded object may contain multiple contact element groups.

[0157] After code 412 is scanned, the mobile device 400 decodes the QR code and obtains information such as a uniform resource locator. The mobile device 400 can use this information to request computer resources such as a web page or an application page of an app. An example of such a product setup introductory display 500 is shown in Figure 5. The introductory display 500 includes instructions for starting the setup process for a new product and may begin by instructing the user to log in to a valid user account (where the text in the introductory display 500 says "app name", the name of the service app may be included). Furthermore, the introductory display 500 may include an existing user control 510 that can be selected by existing users who already have an account in the computer service system, and a new user control 520 that can be selected by new users who do not yet have an account.

[0158] The user selection in the existing user control 510 or the new user control 520 may instruct the mobile device 400 to launch the service app, or to launch the service app after downloading it. When the service app is launched, the service app will prompt for user input, asking the user to log in to an existing user account or to enter information for the system to create a new user account, and after the user enters the information, they can be logged into the new user account.

[0159] After the service application is launched and the user logs into their account, the Live Scan display 600 shown in Figure 6 may be presented. The Live Scan display 600 may include a scan tab indicating that the current display is the scan screen. The Live Scan display 600 may also include a live video window 610 that displays a video feed from the camera of the mobile device 400. The Live Scan display 600 may also include a transmittable code scan status message 620 indicating that a transmittable code scan function, such as Near Field Communication (NFC), is enabled and scannable. Furthermore, the Live Scan display 600 may include a scan start user interface control 630 that can be selected to initiate a scan (however, the scan may be performed automatically after the mobile device 400 recognizes a scannable visual code or transmittable code). The Live Scan display 600 may also include a close user interface control 640 that can be selected to close the Live Scan display 600. The Live Scan display 600 may also include an app sharing user interface control 650 that can be selected to switch to the Live App Sharing display described later.

[0160] After the code has been scanned, the system can perform security checks on the scanned code, as described above. This may include authentication checks and / or malicious code checks. After the security checks, the mobile application may present a security check display 700, as shown in Figure 7. The security check display 700 may include one or more messages regarding the code scan results in the header 705 and one or more messages regarding the security check results in the message window 710. The security check display 700 may include a user interface control 720 that the user can select to continue processing. Depending on the result of the security check, the security check display may also include a cancel user interface control (not shown) that allows the user to cancel processing to avoid using the scanned code. The security check display 700 may also include a live user interface control 750 that can be selected for the live scan display 600 described above or the live app sharing display described later.

[0161] If the scan operation is performed to incorporate or integrate one or more integration features, such as records and / or related services, into the user account of the scanning device, a message or a series of prompts may ask the user to confirm the operation and request user input (e.g., the content and location of the integration feature to be added, payment requests related to the integration feature to be added, and other incidental operations related to the scan operation). The scan operation may also be performed to transfer (e.g., add, share, etc.) one or more records of service records and related information (e.g., data, settings, permissions, etc.). This transfer can be performed with or without related information indicating which portfolio of the user account the transferred integration feature will be added to, and the user account may provide input specifying where in its portfolio the integration feature should be added. The shared integration feature may include a program that preloads the recipient data within a shared code (e.g., a QR code or related uniform resource locator) and automatically verifies the recipient (e.g., a verified account) before transfer to match the preloaded information. For example, a physician can have a patient scan a code (or share it in a conventional way) and share a physician integration feature preloaded with patient data (including current medication status, health status, or suggested wellness programs). This process may be assisted by artificial intelligence tools such as AI bots. Alternatively, patient information within the integration feature can be integrated into an application, such as a third-party app downloaded to the user's mobile device, which can then integrate the patient information. In this scenario, the user can manually or automatically provide informational feedback to the physician through the app, which can then be used for continuous monitoring and health management. This method can be similarly applied to other types of service providers. In fact, service providers like physicians may create user accounts and shareable user profiles corresponding to their patients, and include patient information in those profiles.When a user account views its profile, that profile may be a blended profile and may include data from the physician's user profile as needed. Furthermore, while the current user account may be able to view the profile or its information, editing may be restricted to the physician or other service providers only. Additionally, the service data structure may include a service provider portfolio, which may be an integrated feature providing this functionality.

[0162] If the security check determines that the code is not legitimate, the system may not permit its use. However, if the security check determines that the code is legitimate and not yet linked to a user account within the system, the scan action may prompt the system to activate the code and link it to the current user account (the account logged into the app). The user interface control 720 can display a settings screen on the mobile device 400 to configure a record corresponding to the scanned code and prompt the user for input indicating the services to be provided when the code is scanned by another device.

[0163] Figure 8 shows the Live App Sharing Display 800. The Live App Sharing Display 800 may include a display of a visual share code 810 in a service app on a mobile device 400 that can be linked to a currently logged-in user account on the computer service system. The visual share code 810 is scanned by another device to which the app is shared, allowing that other device to install the same app and use the computer service system. Similarly, the Live App Sharing Display 800 includes a transmittable code status message 820. This indicates the status of the tool for sharing the share code (which can also be linked to a currently logged-in user account on the mobile device 400) via transmission (e.g., near-field communication). As mentioned above, if another device scans the visible share code 810 (or transmittable code) and creates a new user account on the computer service system, the system can award value credits to that account associated with the share code. Similarly, the Live App Sharing Display 800 may include a copy link user interface control 830 for copying the link. Selecting this control copies the shareable link to other devices, allowing the app to be shared with those devices. This may result in credits being awarded to currently logged-in user accounts on the 400 mobile devices sharing the app. Application sharing can be part of a contact information exchange service, which enables users to exchange contact information. During the contact exchange setup and information exchange process, if one of the users is a new user of the system, referral credits are also awarded to the existing user account. Combining the provision of interactive services involving existing user accounts with credit awarding and new user account setup may encourage engagement with the system and create additional user accounts to use it. For example, human users who are not registered with the system may want services that involve interaction with existing user accounts within the system (such as contact information exchange and other interactive services).Furthermore, by integrating service provision, new user account setup, and credit granting to existing user accounts, user account setup, service provision, and credit granting to existing accounts can be achieved more efficiently. These processes can be integrated into a single interactive service process that involves existing user accounts and newly added accounts within the system.

[0164] Furthermore, the live app sharing display 800 may include a selectable preview user interface control 840 for previewing the application sharing display. The live app sharing display 800 may also include a selectable close user interface control 850 for closing the app sharing display 800, and a selectable scan user interface control 860 for opening the aforementioned live scan display 600.

[0165] When a new user logs into the Service Code app for the first time, a new user account is created. The Service Code app then displays the welcome screen 900 shown in Figure 9. This screen may include a welcome message 910 and a "Continue" user interface control 920 that the user can choose to continue setting up their user account. For example, the user can continue setting up by providing user input about their account (name, contact information, settings, etc.).

[0166] After a user account is set up, the mobile device 400 can display the Record Wallet Display 1000 shown in Figure 10. The Record Wallet Display 1000 may also be displayed when logging in with a user account set up in a previous session. The Record Wallet Display 1000 may include a Content List 1010. The Content List 1010 can list entries for the content of the current node (such as categories and records within the current category that are direct children of the current category). Instead of the list shown in Figure 10 and other figures, entries for items such as categories can be presented in different ways, such as images, video tiles, or cards. Images and / or videos may have embedded links that provide information and / or functionality, such as categories, record details, or demos. In this example, the current category is the top-level "Wallet" category, indicated by the position indicator 1020 (to the right of the Live User Interface Control 750) in the header of the Record Wallet Display 1000. The Content List 1010 may include one or more entries 1025. Each entry may include an item selection user interface control 1030. This control can display a record number indicator 1035. This indicator shows the number of records in the category linked to the current user account in the user account's current organization designation. (The record number indicator may be omitted if the entry refers to the record itself). It also includes a title 1040, which is the title of the entry. In Figure 10, the letter "n" is used alone and refers to the record number indicator 1035. In Figure 10 and other figures herein, where the letter "n" is used alone or in similar usages such as "-n", "n" means any applicable number, variation, type, etc., depending on the context in which it is used (here in Figure 10, any number applicable from the context). Selecting the item selection user interface control 1030 transitions the record wallet display 1000 to the listed category or record.Each entry 1025 in the content list 1010 may also include an information user interface control 1045, which, when selected, displays information about the category or record represented by that entry. Category entries may be omitted from the display if the system determines that no record for that category exists in the current service data structure, and / or if the system determines that no record for that category exists associated with the current user account or the account's current organization.

[0167] In the example in Figure 10, the categories may include a "My Apps" category. The service data structure allows for the addition of applications via user input, navigating different types of app categories under the "My Apps" category in the hierarchical structure, and reaching the app record level. At the record level, the displayed user interface controls can be selected, and user input can be accepted requesting actions related to a specified app (or multiple apps), such as specifying settings, accessing the app, or sharing the app. Such apps are the third-party apps 126 mentioned earlier with reference to Figure 10, and may include apps provided by the same entity providing the service app 124, or by one or more different entities. Common system service options in this case include allowing users to scan and share apps (providing scannable code for app sharing) or transfer apps to another organization or another user account. If an app is transferred, a process may be provided to receive data to set up a new user account for the transferred app. For example, this could involve prompting user input or requesting data from other computer components.

[0168] Apps, including games, operate in single-user or multi-user configurations (such as gameplay or use of other apps). Sharing, forwarding, and initiating invitation scans (or related shared link invitations) can invite other user accounts and associated users to participate in multi-user apps and games, either as paid or free referrals. The user account sharing the app may be designated as an administrator and may have the authority to assign roles and perform other administrative tasks for user accounts invited by that sharing user account. The original app creator may be permitted to set forwarding and sharing restrictions based on the user conditions and app policy rules of the receiving account.

[0169] In the example in Figure 10, the categories can include a "My Managed Records" category, which can include displaying categories and / or records for which the current user account is not the owner but has been granted administrative privileges within the system. The service data structure can allow user input for user accounts and prompt the system to move to other account records where the current user account is set as an administrator. Setting someone as an administrator grants administrator privileges to user accounts other than the user account designated as the owner of an item in the system (i.e., the item's primary administrator account). This includes organizations (including categories and records within an organization), categories (including categories and records within a category), or records. Permissions set in an organization or category apply to items within that organization or category. However, if an exception is set for default permissions in a subcategory or record, that exception takes precedence over the default permissions. Administrator privileges include, for example, "Read Only" (allowed user accounts to only view records), "Editor" (allowed user accounts to edit records), and "Author" (allowed user accounts to edit, add, transfer, reassign, and delete records). Furthermore, administrators can invite members (such as users with access rights in roles like non-administrator or viewer) and grant them access-enabled viewing permissions to services. This allows members to invoke the service manager and run one or more services made available by records or categories associated with their member role. Such members may also have access to and permission to modify their non-administrator settings for related services. Depending on the permissions granted, administrators can add, delete, and adjust the activities of members and other administrators with different administrator roles, and they can also invoke the service manager to run permitted services made available by related records or categories.

[0170] In the example in Figure 10, the categories can include an "Organization" category, which can include a display of the organization associated with the current user account. The service data structure can allow user input for the user account and prompt the system to set up one or more organizations and one or more organizational displays (showing departments, divisions, etc.), under which applicable service categories and related records can be set. Based on organizational descriptors (type, industry, product, service, etc.), it is possible to set up pre-configured and / or pre-determined service categories, records, and / or services.

[0171] In the example in Figure 10, the category includes a physically encoded category, which in turn includes a representation of a physically encoded object. This includes scannable codes linked to records in the physically encoded category (including its subcategories). By scanning the scannable code (trigger code) on the physically encoded object, the services indicated in the linked record can be made available. A physically encoded object is physically composed of scannable visual codes and / or transmission system link codes.

[0172] Physically encoded record types may include standard encodeds that make the encoded specification available within existing records, such as service records. Some standard encodeds are configurable during initial setup, allowing users to further configure (customize, etc.) the encoded using features such as additional graphics, setting of configured code locations, and / or optional addition of system integration contact elements (such as system integration phone numbers (call routing ID is optional), messaging service addresses, URLs (uniform resource locators), and / or email addresses). Physical encoded record types also include custom encodeds, which allow for the provision of encoded settings. This enables user input for managing related resources such as images, files, services, apps, and specifications (including custom record code setting options and instructions).

[0173] In the example in Figure 10, the categories may include a digital encoding category, which can provide a code scannable on one or more computer devices. It may also include a display of the digital encoding (e.g., when the code is transmittable by a computer device or when the code is displayed on the screen of a computer device). In such a scenario, the computer device can become the physical encoding itself, digitally configured according to the encoding. Thus, the digital encoding can be digitally constructed using system-interlocked codes. These codes are configured to be scanned in various ways, including visual scanning, auditory scanning, and / or code transmission via signals such as electromagnetic waves (e.g., frequency-based transmission). These digital encodings are similar to physical encodings and can take standard or customized forms, and may be designed for computer output, such as screen display, projection onto a surface, or integration with holographic images.

[0174] In the example in Figure 10, the categories may include a virtual code category, which includes suggestions of virtual code that can provide scannable code on one or more computer devices (e.g., when code is transmittable by a computer device or when code is displayed on the screen of a computer device). These code may be digitally configured with system link code, such as system link code transmitted visually and / or audibly, but may also make available system services that are virtually tapped or selected and linked. In such situations, the computer device itself becomes a digitally configured code depending on the code. These virtual code, like physical and digital code, can be standard or customized and may be intended for deployment in augmented reality (AR), the metaverse, and / or virtual or simulated worlds and / or locations. Scan-sharing services for these code can make available service settings related to the code's virtual reality. Other scan-sharing options are similar to those described later with reference to Figure 23.

[0175] In the example in Figure 10, the categories may include a “Encoded Templates” category, which may contain instructions for encoded templates that can provide scannable code on one or more computer devices (for example, when the code is transmittable by a computer device or when the code is displayed on the screen of a computer device). These encoded materials can be digitally configured using system link codes that are visually and / or audibly transmitted to the computer template, such as video conferencing (background) templates for video conferencing services, image templates, video templates, document templates, social media post templates, advertising templates, television or video broadcast templates, and / or other types of applicable digital media elements incorporating templates. Templates can be configured, downloaded, and applied manually, or they can be applied automatically via APIs, service synchronization, or other similar configuration and application processes and tools.

[0176] In the example in Figure 10, the categories could include a “Posted Encodes” category, which could include displays of posted codes that provide scannable codes on one or more computer devices (for example, when the code is transmittable by a computer device or when the code is displayed on a computer device's screen). These codes are digitally constructed using visual and / or transmission system-linked codes embedded in digital images and videos intended for posting to online media services such as social media services. Posts can be configured, downloaded, and manually posted, as well as configured and / or integrated for automated creation and / or automated scheduling via one or more available (third-party) posting services, such as social media services, websites, blogs, forums, and customer relationship management (CRM) services. Posts can also be automatically transmitted via APIs, service synchronization, and / or other similar configuration and application processes and tools.

[0177] In the example in Figure 10, the categories may include the “Advertised Encodes” category, which may include displays of advertised codes that can provide a scannable code on one or more computer devices (for example, when the code is transmittable by a computer device or when the code is displayed on the screen of a computer device). These codes are digitally constructed using visual and / or transmission system-linked codes embedded in digital images or videos intended to be advertised online. Advertisements can be configured, downloaded, and manually placed, as well as configured and / or integrated for automated creation and / or scheduled placement through one of the many available online advertising services, including third-party online advertising services. Advertisements can be automatically applied or placed through APIs, service synchronization, and / or other similar configuration and application processes and tools.

[0178] The record wallet display 1000 may also include the user interface control 1050 and the navigation user interface control 1060. Selecting the user interface control 1050 will display the order display described below.

[0179] Selecting the navigation user interface control 1060 opens the navigation display 1100 corresponding to the current location of the record wallet display 1000 (in this example, the top-level "Wallet" category). The navigation display 1100 corresponding to the current location of the record wallet display 1000 (in this example, the top-level "Wallet" category) is shown in Figure 11. The navigation display 1100 may include a location indicator 1120 in its header that shows the current location (in this example, the top-level "Wallet" category). The navigation display 1100 may also include an item indicator control 1112 or a rollup indicator control, as shown in Figure 23. However, in certain situations, such as the wallet page, the item indicator control may be omitted from the navigation display 1100. The item indicator control 1112 may include a service status user interface control 1125. This can indicate whether the system has detected a problem with a service associated with the current user account, through items such as categories and records within the category where the user is currently located under the currently active organization designation (a single user account may have multiple organization designations, each with its own set of associated records, and the user can switch between organization designations for that user account via user input). Selecting the Service Status User Interface Control 1125 displays information about the service problem. The Item Indicator Control 1112 may also include the Action Item User Interface Control 1130, which lists multiple action items awaiting user input ("n" can be replaced with a number, as does the list item in the Record Wallet Display 1000). Selecting the Action Item User Interface Control 1130 displays a list of action items that require user input to proceed. The Item Indicator Control 1112 may also include the Captured Data User Interface Control 1135.Selecting this option displays captured data, such as data captured when providing services to the code associated with the current user account and organization designation. The item indicator control 1112 may also include a messaging user interface control 1136, which shows the number of unprocessed messages (which may include messages marked as unread) associated with items such as categories and records within the current category, and is selectable to display the messages. The item indicator control 1112 may also include an analytics data user interface control 1137, which is selectable to display analytics data associated with items such as categories and records within the current category (e.g., the number of code scans and associated device identifiers for a specific record and / or all records within a specific category). The item indicator control 1112 may further include an administrator user interface control 1138, which is selectable to display information about administrators (i.e., user accounts granted administrator privileges) for items such as categories and records within the current category, and optionally allows user input to edit administrator privileges for specified items such as categories and records, or to add or remove administrators. The Item Indicator Control 1112 can also include a Summary / Report User Interface Control 1139, which can be selected to display one or more reports or summaries about items such as categories and records within the current category. In all data that can be displayed depending on the selection of the Item Indicator Control 1112, the data is rolled up to the current category, so the data includes the specified type of data for the current category (including its descendants such as subcategories and records). The Item Indicator Control 1112 and its associated action options may be limited or not included at all in some scenarios, such as on mobile devices.

[0180] The navigation display control 1100 may also include an account user interface control 1140, which displays data for an active account and allows editing of that data. The navigation display 1100 may also include one or more navigation user interface controls 1150, which may include user interface controls for the current location (again the top-level "Wallet" category in this example) and the ancestor category of the current location (i.e., the category containing the current category). When a user interface control within the navigation user interface control 1150 is selected, a record wallet display 1000 corresponding to the location indicated by that control (such as the "Wallet" category in the case of the "My Wallet" user interface control in Figure 10) may be displayed.

[0181] Referring to Figure 12, the record wallet display 1000 corresponding to the "Encoded Items" category shown in content list 1010 of Figure 10 is shown. In addition to the types of user interface controls in Figure 10, the record wallet display 1000 in Figure 12 has an additional search user interface control 1260. When this is selected, the user is prompted to enter text to search for records that match the entered search text (i.e., descendant records of the current category in the record wallet display 1000). When the navigation user interface control 1060 is selected in the record wallet display 1000 shown in Figure 12, the mobile device 400 displays the navigation display 1100 at the current location ("Encoded Items" category), as shown in Figure 13.

[0182] The navigation display 1100 in Figure 13 may be the same as the navigation display 1100 in Figure 11. However, the navigation display 1100 in Figure 13 may omit the item indicator control 1112 in Figure 11. Furthermore, the navigation user interface control 1150 of the navigation display 1100 in Figure 13 may further include an encoded user interface control in addition to the wallet ("My Wallet") user interface control. Selecting the encoded user interface control displays the record wallet display 1000 in Figure 12, and selecting the wallet user interface control displays the record wallet display 1000 in Figure 10. Alternative and / or additional functions for retrieving and presenting encodeds may be used as described herein.

[0183] When the user selects the "Offer Sign" item in the record wallet display 1000 in Figure 12, the mobile device 400 is prompted to display the record wallet display at the destination sign location. When the user selects the additional user interface control on that record wallet display, the mobile device 400 is prompted to display the record wallet display 1000 in Figure 14. This may be a record wallet display for selecting additional service records (i.e., orders, which may include requesting that the selected available records be linked as linked records to the current user account). Therefore, additional user interface controls like those in Figure 12 may not be included in the record wallet display 1000 in Figure 14, because the display is already in add mode. However, the record wallet display 1000 in Figure 14 may include a user interface control (not shown) that switches to a record wallet display to show already linked records for the user account, as in Figure 12. Furthermore, the selection of the navigation user interface control 1060 in the record wallet display 1000 in Figure 14 can prompt the mobile device 400 to display the navigation display 1100 for the "Offer Sign" category location, as shown in Figure 15. This display is similar to the display in Figure 13, but the navigation user interface control 1150 includes user interface controls for displaying the record wallet display 1000 for each category ("Offer Sign," "Encoded Items," "Wallet") (for the current location and the respective locations of its ancestor categories).

[0184] When the user interface control 1030 for selecting the "Sales Sign" category in the record wallet display 1000 in Figure 14 is selected, the mobile device 400 displays the record wallet display 1000 in Figure 16 corresponding to the location of the "Sales Sign" category. Furthermore, selecting the navigation user interface control 1060 in the record wallet display 1000 in Figure 16 can prompt the mobile device 400 to display the navigation display 1100 for the location of the "Sales Sign" category, as shown in Figure 17. This is similar to the display in Figure 15, but the navigation user interface control 1150 includes user interface controls for displaying the record wallet display 1000 corresponding to the categories of Sales Sign, Offer Sign, Encoded Items, and Wallet (the current location and the location of each of its parent categories).

[0185] Selecting the item selection user interface control 1030 for the English signature category in the record wallet display 1000 in Figure 16 can prompt the mobile device 400 to display the record wallet display 1000 in Figure 18 at the English signature category location. Furthermore, selecting the navigation user interface control 1060 in the record wallet display 1000 in Figure 18 can prompt the mobile device 400 to display the navigation display 1100 at the English signature category location, as shown in Figure 19. This is similar to the display in Figure 17, but the navigation user interface control 1150 includes user interface controls for displaying the record wallet display 1000 for each category (current location and the location of its parent category) of English signature, sale signature, offer signature, coded, and wallet.

[0186] In the record wallet display 1000 in Figure 18, entry 1025 in the content list 1010 for the English signature category may be an item in the on-demand printed signature and ready-made signature categories. In this situation, when the item selection user interface control 1030 corresponding to the on-demand printed signature entry is selected in add mode, the order display 2000 shown in Figure 20 is displayed.

[0187] The order display 2000 in Figure 20 includes a descriptive message 2010 that describes the ordered item. For example, it includes the title of the corresponding on-demand printable signature availability record and its higher-level category. The order display 2000 also includes additional information about the availability record. The order display 2000 may also include an order user interface control 2020. This is optional to trigger a user interface display or a series of displays for ordering the coded items described by the descriptive message 2010. This may include the system processing of payment information if payment is to be made for the ordered coded items, and delivery information and other information for obtaining the ordered coded items. Order processing also includes applicable system actions related to the order. Examples include: adding the code of the ordered coded item to the authenticated code list, activating the code and linking it to the current user account, sending a message to a third party for order approval, providing an estimate of the coding item's production time by checking the production queue, requesting and receiving user input indicating accessory options, requesting and receiving user input indicating customization specifications, requesting and receiving user input indicating customization warranty options, and third-party compatibility checks.

[0188] The order display 2000 may also include an optional navigation user interface control unit 2030 to prompt the mobile device 400 to display a navigation display 1100 corresponding to the location of the on-demand printed sign category, as shown in Figure 21. In the navigation display 1100 of Figure 21, the navigation user interface control 1150 may include a user interface control for displaying a record wallet display 1000 corresponding to the categories of on-demand printed sign, English sign, sign for sale, sign for purchase, coded items, and wallet (for the current location and the location of each of its ancestor categories).

[0189] Figure 22 shows a record wallet display 1000 for a category that has direct children, which are records linked to the current user account in the current organization designation, and can take the form of a record list. In this case, the record wallet display 1000 can include a content list 1010 containing entries, where entries may include entries 1025 for records linked to the current user account in the current organization designation. Each list item can include an item selection user interface control 1030 and display a title 1040. The record wallet display in Figure 22 can also include a navigation user interface control 1060 and an add user interface control 1050, both of which are selectable for operations on similar user interface controls as described above. Furthermore, the record wallet display 1000 in Figure 22 can include a transfer user interface control 2220, which is selectable to initiate the process of transferring one or more selected service control records and instructions for the ancestor category of each selected record (e.g., including link references between the service control records to be transferred and the organization designation). (Example: Transferring a service to a different organizational destination for the same user, or transferring to a different user account. This involves changes to association references, including association references between the service control record being transferred and the organizational destination / user account, and / or inter-category references within the service control data structure.)

[0190] The selection of the item selection user interface control 1030 for the service control record in Figure 22 can prompt the mobile device 400 to display the record management display 2300 in Figure 23. The record management display 2300 may have similar functionality to the navigation display 1100. This includes the live user interface control 750, the location indicator 1120, and the item indicator control 1112. The record management display 2300 may further include a scan-sharing service user interface control 2330. This is selectable for performing scan-sharing of a service, such as displaying a scannable visual link code and / or launching a tool to transmit a transmittable link code (scanning the transmittable code), prompting the system to make the linked service available to the scan device or scan user account. The record management display 2300 may further include a scan-sharing record user interface control 2332, selectable for performing scan-sharing of a record. This performs scan-sharing of a record, such as displaying a scannable visual link code and / or launching a tool to send a transmittable link code. Scanning this link code prompts the system to share the current record with another organization or user account, making the record available to that other organization or user account. For example, another user account might provide the relevant code in the scan-sharing service process and provide a service linked to the scan device and / or user account. The record management display 2300 may further include a shared service configuration user interface control 2334. When selected, this displays a shared service configuration display and allows the user to configure (initialize and / or modify) the shared service linked to the current record. The record management display 2300 may further include a record service configuration user interface control 2336. When selected, this displays one or more displays to the system to receive user input and prompt the user to configure the record service linked to the current record.The Record Management Display 2300 may further include a Shared Pages Settings user interface control 2338. Selecting this displays the Shared Pages Settings display, which allows the system to display one or more displays to accept user input and configure pages to be shared as part of the services provided when the current record is shared for service. The Record Management Display 2300 may further include a Record Fields user interface control 2340. This is selectable to list the encoded fields indicated for the current record (for example, a sales display list field marked with a visual code linked to the current record). Other encoded fields can also be ordered here to include the same code. The Record Management Display 2300 may further include a Transfer Records user interface control 2350, which is selectable to initiate the process of transferring a record to another organization designation (which may be another category) or user account. Delete Records user interface control 2355: Selectable to delete (or delete, archive, disable) a record. Return to Record List user interface control 2360: Selectable to return to the Record Wallet Display 1000 in Figure 22. Furthermore, referring to Figure 22, by selecting the illustrated code icon 1042 based on user input, the system can display a visual code linked to the related record. In addition, other similar record setting controls can be added as immediate access icons to the item selection user interface control 1030 as needed, and by selecting each, the specified information from the linked record can be displayed. The interfaces associated with the record management display 2300 are not limited in number and / or related functions or types.

[0191] By selecting the Scan Share Service User Interface Control 2310 in Figure 23, the mobile device 400 is prompted to display the Scan Share Display 2400 shown in Figure 24. The Scan Share Display 2400 is similar to the Live App Share Display 800 described above, but instead of sharing a share code, the Scan Share Display 2400 can operate in a way that shares a record and a code linked to the service indicated in the record. Thus, a device scanning a code from the Scan Share page can receive the code and use it to request the service indicated in the linked record.

[0192] The scan-share display 2400 may include a location display 2405 indicating the current record from which the code is being shared. The scan-share display 2400 may also include a display of a visual trigger code 2410 that can be linked to the current record. This trigger code may be different from the codes used for application sharing and user account application sharing credit tracking mentioned above. The visual trigger code 2410 can be scanned by another device from which the app is shared, allowing that device to invoke the service indicated in the current record. This begins with the scanning device sending a request to the service subsystem, which may contain data derived from the scanned code. Similarly, the scan-share display 2400 may include a transmittable code status message 2420. This indicates the status of a tool that is sharing the trigger code (also linkable to the current record) over a transmission such as near-field communication. Similarly, the scan-share display 2400 may include a copy link user interface control 2430. This is optional for copying a trigger link (e.g., a URL) and sharing it with another device, prompting that device to trigger the service indicated in the current record. This also includes the receiving device (or the mobile device 400 itself) sending a request to the service subsystem along with the data derived from the copied link. If a service app (e.g., service app 124 as described in Figure 1) manages the scanning of shared trigger codes, instead of providing a service page or executing a command to provide the requested shared service, or in addition to that, the system may instead prompt for confirmation to add or start one or more processes to place / set up / create the data in the appropriate location within the data structure associated with the receiving user account (the user account active in the service app at the time the trigger code was scanned) and / or execute an account command directly.

[0193] Furthermore, the scan sharing display 2400 may include a selectable preview user interface control 2440 for previewing the application sharing display. The scan sharing display 2400 may also include a selectable close user interface control 2450 for closing the scan sharing display 2400.

[0194] As can be seen in Figure 23, selecting the shared page settings user interface control 2338 prompts the mobile device 400 to display one or more displays for configuring the functionality of services provided in relation to a record. For example, such displays may include one or more illustrations from Figures 25, 26, 27, 28, and 29, and / or other service functionality settings displays. Figure 25 shows a service settings page display 2500. The service settings page display 2500 may include a service list 2510 containing multiple service entries 2520 representing the services available for the current record. The services available for a record may be inherited from the settings of the category containing that record. Categories can also inherit the settings of services available from their parent categories, and these parent categories can inherit the settings of services available from their parent categories, and so on, hierarchically. For example, the services available for a record in a category may include a subset of the records available in the parent category of that category. Each service entry 2520 may include a status indicator 2530 indicating whether the service is enabled or disabled (on or off) for the current record. Some of the available services are free, while others are paid. Each service entry 2520 may also include a service title 2535 and an editable user interface control 2540 that can be selected to edit the service's functionality. For example, a mobile device 400 may, in response to a user input selection in the editable user interface control 2540, display one or more displays containing user interface controls for editing the functionality of the service when used in the current record, and the resulting input is saved in the record as the settings for that service when used in that record. For example, this may occur when the service is provided in response to a trigger containing a code linked to that record.

[0195] The page setup service display 2500 may also include a save / continue user interface control 2560 that allows the user to save changes and proceed to another display screen for setting or editing records.

[0196] Returning to Figure 23, the selection of the shared page user interface control 2338 may display the "Product Page Format Display 2600" in Figure 26. This may look identical to the actual service display provided as part of the service offering in response to the scanning of the relevant trigger code. However, the actual service page may include images corresponding to features such as a main image, interactive map, photo gallery, and interactive video (therefore, such a service page is shown in Figure 26 as a reference to service page 2660, and there is no separate figure for the service page). The Product Page Format Display 2600 is formatted as a template for a service page that can be displayed in response to the scanning of the code associated with the current record. It may offer options to select from multiple templates or to reformat the template (such as resizing the page area). The Product Page Format Display 2600 may include user interface controls 2610 that can be selected to provide content for various page features displayed on the corresponding service page. These controls are positioned in the same location as they appear on the Product Page Format Display 2600. Each user interface control 2610 can be selected to provide data related to the page in question. For example, selecting the product title ("Product Name") will display a text box for entering the product title. Selecting the main image ("Product Image") will allow you to select an image from available images (for example, photos saved on your mobile device). Selecting the interactive map ("Interactive Map") will allow you to provide the address of the location to be displayed on the interactive map within the service page. Selecting the image gallery ("Photo Gallery") will allow you to provide multiple images to include in the image gallery feature of the service page. Selecting the interactive video control ("Interactive Video") will allow you to provide one or more interactive video files for the interactive video feature to be included on the service page.Selecting the Message System control ("Message System") provides the information necessary for sending messages to the messaging profile associated with the record. The Sales Page Format Display 2600 may also include one or more other user interface controls, such as a Save / Continue user interface control and / or a Close user interface control (not shown in the diagram).

[0197] Depending on the selection of the Save / Continue user interface control on the service settings screen, or the selection of the Shared Page Settings user interface control 2338, the Shared Website Settings screen 2700 shown in Figure 27 may be displayed. The Shared Website Settings display 2700 may include a Title user interface control 2710 that accepts user input for setting the title of the website to be shared, and a URL control 2720 that accepts user input for setting the URL (Uniform Resource Locator) of the website. The URL control is used to provide a service that launches the web page referenced by the URL control. The Shared Website display 2700 may also include a Cancel user interface control 2730 that can be selected to cancel the data entered in the Shared Website display 2700, and a Save / Continue user interface control 2740 that can be selected to save the data entered in the Shared Website display 2700 and proceed to another display. Instead of such a shared website, in the case of a social media site, the system may prompt for the social media username instead of the URL. The URL referred to here can be entered by the user, but the actual website URL used to provide the service is a system-configured URL encoded in scannable code linked to the record, which may redirect to the URL shown in Figure 27.

[0198] The Shared Contact Data Settings screen 2800 shown in Figure 28 may be displayed by selecting the Save / Continue user interface control on the Service Settings screen, or by selecting the Shared Settings page user interface control 2338. The Shared Contact Data Display 2800 may include a Contact Data user interface control 2810 that can be used to enter contact data to be shared (such as record title, first name, last name, organization identifier, mobile phone number, work phone number, email address, website address (URL), shared notes, etc.). The service associated with the current record can share such data with the scanning device in response to scanning the code associated with the record. The Shared Contact Data Display 2800 may also include a Cancel user interface control 2830 that can be selected to cancel the data entered in the Shared Contact Data Display 2800, and a Save / Continue user interface control 2840 that can be selected to save the data entered in the Shared Contact Data Display 2800 and proceed to another display.

[0199] In the configuration of Shared Contact Data Display 2800 and related Shared Contact functions, this also serves as an example of an encoded command for invoking a trigger URL command. This command opens a new contact form on the scanned device, automatically populates the form with the entered information, and prepares the resulting contact profile for saving to the scanned device. A similar process can be used to trigger any device-aware action, including queuing a device map to share pre-configured location information, queuing a device calendar to set pre-configured events / appointments, queuing a device text message to send pre-configured text, queuing a device mail client to send pre-configured emails, queuing a device phone function to make calls to pre-configured phone numbers, queuing a device Wi-Fi setting to share pre-configured Wi-Fi data, and / or operations via system integration / API integration applications, or operations from apps with OS control / permissions.

[0200] One implementation example is to optionally set a service page link in the website address. This service page can be updated at any time by user input, as account users can add the service page link as contact data in the device contact data form. This expands the options for shared data. For example, when a scanning device user selects contact information associated with a record and then selects a website link, the service page expands in real time to display the latest information.

[0201] Selecting the Save / Continue user interface control on the service settings screen, or selecting the Shared Page Settings user interface control 2338, may display the Settings Trigger Message Contact Exchange Display 2900 shown in Figure 29. The Settings Trigger Message Contact Exchange Display 2900 may include a Data User Interface Control 2910 that can be used to input data for trigger messages sent in response to scanning a linked code. For example, the Data User Interface Control 2910 may include a user interface control where a phone number can be entered. The entered phone number is provided to the scanning device as a response to scanning the linked trigger code, and the scanning device sends its own phone number to the entered phone number, allowing it to receive a reply message containing a link to a form (including any number of other possible service page links). This enables the exchange of contact information. The Data User Interface Control 2910 may also include controls for entering the message to be sent, requesting other scanning devices to reply with its own phone number, and allowing it to receive a link to a form. The data user interface control 2910 may also include a country input user interface control for selecting a country (e.g., select from a dropdown menu) and a digital contact card user interface control for selecting and loading a digital contact card to share using a form provided in the message. The setup trigger message contact exchange display 2900 may also include a cancel user interface control 2930 that can be selected to cancel data entered into the setup trigger message contact exchange display 2900, and a save / continue user interface control 2940 that can be selected to save data entered into the setup trigger message contact exchange display 2900 and proceed to another display.This process is applicable to various scenarios in which, upon scanning a code, computer-readable information is sent to the scanning device, and this information includes data that requests a response computer communication by sending an initial computer communication containing a link (such as a user-selectable link). This link can be used to trigger further system actions. This process is applicable to all types of system communication (not limited to text messages), such as email, various messaging systems, and calendar invitations. Furthermore, the relevant service configuration page can be configured to suit any scenario, including prompting the user for appropriate data depending on the scenario (including appropriate communication contact information depending on the type of communication used).

[0202] Figures 30-32 show examples of how custom records that can be added by a user of a computer service system can be displayed. As mentioned earlier, the system comes preloaded with standard structured categories and records. However, it is also possible to provide user accounts that add and modify custom records to include in custom categories through user input. Custom categories are created and modified according to user input. For example, a user may want to print codes into their own custom codings and categorize them themselves. Referring to Figure 30, the record wallet display 1000 may be titled "Custom Codings" and contain one or more entries 1025 for custom codings. When user input is provided to the field selection user interface control 1030 for custom coded items, the record wallet display shown in Figure 31 is displayed. This display includes record list fields for custom coded items similar to the record list fields for standard items in the record wallet display 1000 shown in Figure 22. However, the record wallet display 1000 for custom coded records in Figure 31 may include a reassignment user interface control 3120 for reassigning custom records to a different location. This could be a reassignment within the current organizational designation and user account hierarchy, or a reassignment by transferring a custom record to a different user account or a different organizational designation within the same user account, as described here for standard records. In fact, when transferring a custom record to a different user account or a different organizational designation within the same user account, as described here for standard records, the transferred record retains its hierarchical structure information (ancestors of the standard hierarchy and any custom hierarchy ancestors that may have been added based on user input). These hierarchical structures are used by the system to include the transferred custom record within the same hierarchical structure for the new organizational designation or user account data structure. As part of the reassignment process, a reassignment option is provided that allows user input to change the custom hierarchy category name and / or structure.Subsequently, custom records are reassigned using these new category names and / or structures.

[0203] When the navigation user interface control 1060 is selected on the display in Figure 31, the mobile device 400 is prompted to display the record management display 2300 shown in Figure 32. This is the same as the record management display 2300 in Figure 23 mentioned above. However, the record management display 2300 for custom records in Figure 32 may include a reassignment user interface control 3220 instead of the record transfer user interface control 2350. The reassignment user interface control 3220 may be the same as the reassignment user interface control 3120 mentioned above with respect to Figure 31.

[0204] Adding encoded items or records may involve more complex procedures. For example, wizard-guided steps may guide you through configuring service categories related to orders for services and items associated with service records, or the system may receive user input and configure standard or custom objects.

[0205] Figure 33 shows a record service settings display 3300 for configuring record services for records and / or records within categories. These record services are a type of system service and, like other record services, can be provided to user accounts to further extend record functionality. For example, record services may include: adding items to the marketplace service (including adding items to one or more marketplaces, e.g., posting one or more ads or product listing items to the marketplace, including scannable codes); setting up social media posts (including setting up and posting one or more social media posts); and / or placing ads (including setting up, publishing, and / or generating one or more ads, including scannable codes). Therefore, the record service settings display 3300 may include user interface controls that can be selected to configure the corresponding services, and / or additional displays that prompt user input for service configuration. In the example in Figure 33, these user interface controls on the record service settings display 3300 include the "Add Items to Marketplace" user interface control 3310, the "Set Up Social Media Posts" user interface control 3320, and the "Place Ads" user interface control 3330. The record service settings display 3300 may further include a save / continue user interface control 3350 that allows the user to select options for saving changes and continuing. The services referred to here may be any of the various services, including one or more of the service types described above.

[0206] While specific user interface designs and functions have been described above, different functions and designs can be used for individual display screens and the flow between screens for the records described herein. For example, differences may occur in web-based interfaces compared to dedicated application interfaces. Similarly, different structures and functions of the components within the system described herein can be used, and different combinations of functions can be used with each other or with other functions. It is also possible to employ different types of user interfaces, such as voice user interfaces using speech recognition tools or speech synthesis tools.

[0207] V. Example Scenario The following are some examples of scenarios using the tools and technologies described herein. However, many other scenarios can be implemented in this system.

[0208] A. Managing records and / or record structures that can be added to other user accounts. In this scenario, a user account may have the authority to modify (add, edit, reorganize, delete, etc.) service data structure items (including organizations, categories, and / or records) that can be added (added via links) to other user accounts, as detailed herein (not simply through transfer or sharing operations from one user account to another). A user account with such modification authority may be an account that has the authority to modify some or all of the available organizations, categories, and / or records. For example, this could be the user account of an employee who is a software developer or system administrator of an entity that manages the service subsystem and / or other parts of the computer service system. Service data structure items that are generally available to other user accounts may be available to all other user accounts, or they may be available to a defined subset of all other user accounts. For example, different user accounts may subscribe to access different subsets of service data structure items.

[0209] In other examples of this scenario, one or more user accounts with modification privileges may only have such privileges over a subset of common service data structure items that can be added to other user accounts. Thus, such a subset of available service data structure items may be subject to the privileges granted to one or more user accounts with modification privileges (data within the computer system granting the privileges; this data may be contained within the user account and / or elsewhere in the system). For example, this might be the case for a user account of an employee who is a software developer or system administrator of a third-party entity (an entity other than the entity managing the entire service subsystem and / or other parts of the computer service system discussed herein). Such a third-party entity may, for example, manage a third-party subsystem such as an online marketplace and / or be a provider of coded materials. For example, a third-party entity may operate an online marketplace where coded advertisements, including product offerings, can be posted from the service subsystem to the third-party online marketplace subsystem. Furthermore, the same third-party entity may also be a supplier of encoded sales notices that can be linked to product listing items on the online marketplace (services provided in response to scanning trigger codes and / or advertisements on encoded sales notices include displaying those product listing items on the online marketplace).

[0210] Furthermore, a user account with modification authority, which has the authority to modify service data structure items that are generally available to other user accounts (for example, all other user accounts, or a subset including one or more of all other user accounts), may also be a user account that makes certain records available for use in providing computer services, as described herein. Thus, a single user account may be used to modify service data structure items that are generally available to create linked records that are added to other linked user accounts, and may also be used to manage records and / or other service data structure items linked to that single user account. Thus, such a single user account may retain the authority to modify records and other related service data structure items that are generally available to other user accounts, as well as the authority to modify and use records and other related service data structure items linked to that single user account, as described herein.

[0211] The system may restrict changes made by user accounts that have permission to modify records and record structures available to other user accounts. For example, the system may prohibit at least some user accounts with administrative privileges from deleting records, organizations, and / or categories (or records and / or categories within them) after they have become available for addition by other user accounts, or after they have been added to at least one other user account. For example, the system may prohibit such deletions, or may only be permitted if certain conditions are met (e.g., permission is granted by one or more other user accounts in the system, such as a user account for an entity that generally manages a service subsystem). Such restrictions may be the same for all user accounts that have permission to modify records and record structures available to other user accounts, or they may differ for different groups of user accounts that have permission to modify records and record structures available to other user accounts (e.g., restrictions may differ between user accounts with different roles assigned in the system, and / or between user accounts linked in the system to different entities such as entities). Additionally, when a user account scans for receiving or sending integrations (including the transfer of integration records containing categorical structure instructions), the transfer process allows the wizard to incorporate the integration into an applicable location within the user account's service data structure. This location may be specified by the integration itself or other settings. The wizard then prompts the user account to authorize and / or facilitate necessary financial transfers (such as integration payment processing) and / or integration-related settings. Instead of managing the settings, the wizard may request the user account to accept the integration and provide a brief approval for its placement in a location referenced in the "Pending (Review) Integrations" location list item shown in Figure 48. This allows the integration to be configured later. Some integrations, such as those controlled by other user accounts, may be locked and unavailable for transfer from the current user account.

[0212] B. Ordering time representation as an encoded object The encoded object can be any of several different things, such as a point-of-sale display. For example, referring to Figure 34, a point-of-sale display 3400, or more generally, a point-of-sale display for ordering goods regardless of whether payment is made (the point-of-sale display 3400 may be a physical sign, a computer terminal with a screen display, or other type of point-of-sale display), may include an instruction message 3410 and a scannable code 3420. In the example in Figure 34, scanning the code can prompt the system to perform a service. This service may include providing a tool for ordering goods such as encoded signs, which can be performed using a record linked to the scannable code 3420. The sign provider's user account can be linked to that record for setting up and managing the record linked to the scannable code 3420. Of course, the encoded sign being ordered may itself be an encoded object containing a different scannable code than the scannable code 3420 on the point-of-sale display 3400. Therefore, the service for ordering encoded signatures includes a service for registering a user account within the system, or a service for logging into an existing user account (a separate user account for the human user ordering the signature, and not for the provider of the point-of-sale information display), and also includes associating the code of the ordered encoded signature with that user account and any existing records linked to that user account. This allows the system to perform one or more configurable services indicated in the records linked to the user account by scanning the ordered scannable object.

[0213] A point-of-sale display may contain scannable code linked to a record that directs one or more other types of services to be performed in addition to, or instead of, the coding order process. For example, scanning a code on a point-of-sale display may prompt the system to access a record indicating other service types and to provide at least one of those other service types in addition to, or instead of, the coding order process. For example, such services could be paid subscription services, paid event services such as concert ticket purchases, or other types of services (which may or may not be related to the coding ordered simultaneously using the point-of-sale display).

[0214] Referring to Figure 35, another example of this scenario is that the point-of-sale (POS) display 3500 (which may be a physical sign, a computer terminal with a screen display, or other type of PSO) may include an instruction message 3510 and a scannable code 3520. The PSO 3500 may have a similar structure and function to the PSO 3400 described above. However, the scannable code 3520 may be scanned to order an encoded item that is a pet tag rather than an encoded sign. As mentioned above, scanning an encoded item can trigger a process to order another encoded item, and the different codes of these two encoded items may be linked to different corresponding records in the system, and to different user accounts in the system for managing those records.

[0215] If an encoded item is scanned first and an item such as an encoded item is ordered second, the referral credit described herein may be provided within the system to one or more of the providers of the first encoded item (including manufacturers, distributors, and retail stores displaying the encoded point-of-sale indication).

[0216] VI. Examples of additional features and user interfaces This section describes additional user interface displays and related functions. These user interface displays and related functions can be used in conjunction with those described in other sections of this specification. In fact, the user interface displays described below may have many similarities to those described above. Several concepts related to user interface displays are explained in the following sections.

[0217] A. Concepts and functions related to integration In discussions of these user interface displays and concepts, we refer to integrations. An integration is a structure that is incorporated into a hierarchical service data structure, such as the service data structure 174 described above. An integration can be a category within a service data structure. An integration can be used to provide one or more services, such as the service types described above. For example, a service may be provided using an integration via a service manager. The service manager can also manage the creation and / or modification of service records included in the integration. An integration can implement the service types listed above as appropriate. An integration can contain subcategories, including hierarchical categories and records. For example, an integration can contain one or more service records that can be used to provide a service, such as a record service and / or a code service (e.g., via a service manager). Integrations can include rollup integrations, which aggregate lower-level data and records for use at higher levels. Integrations can also include fixed integrations, where the data in question is aggregated at a higher level within the integration, but each record is considered to belong to a specific level and is not aggregated at a higher level. Furthermore, in fixed or rollup integrations, operations performed on a category node at a higher level (such as applying settings) may apply to descendant nodes at lower levels of that category node (such as category nodes or record nodes). Integrations may include temporary integrations that are enabled or disabled within a structure. The system may also include temporary links to structures that can be enabled or disabled. Additionally, options associated with structures may change. These temporary structures and states related to integrations may change based on internal and / or external conditions.

[0218] An example of a rollup integration described below is a contact integration in which the profiles of contact groups within a contact structure are rolled up to a higher level of the contact structure. Another example of a rollup integration is a document integration for document management, in which documents can become records that can be rolled up to a higher level. However, the types of integrations described as rollup integrations in this specification may be used as fixed integrations in other implementations, and the types of integrations described as fixed integrations in this specification may be used as rollup integrations in other implementations.

[0219] Examples of fixed integrations discussed herein include portfolio integrations, configuration integrations, and measurement integrations. For example, a portfolio integration is an integration that provides a structured hierarchy of categories (referred to here as portfolios), and other portfolios, records, and other integrations can be integrated into the structure of the portfolio integration. Thus, a portfolio is another name for a structured category located below the aforementioned "wallet" category. Each portfolio within a portfolio integration can remain at a specific level without being aggregated to a higher level (although portfolios within an integration may be moved to other locations within the portfolio structure). A configuration integration refers to an integration that manages the configurations of other integrations (e.g., portfolio configurations within a portfolio integration, and / or configurations of other integrations). Configurations are applicable at a specific level, but data related to configurations is aggregated at a higher level, and configurations are applied to a specified node, and by default may also be applied to the descendants of that node. A measurement integration refers to an integration that provides measurement services. For example, a measurement integration may provide a service that tracks how a measured value changes over time. Measurement itself may be provided on a node-by-node basis, but measurement operations may be performed on data aggregated from nodes below that node.

[0220] Referring to Figure 36, integration types can be classified in other ways. For example, all integrations discussed herein may be of service integration type 3600. These can also provide services as enumerated elsewhere in this application. These service integration types may also include option type 3610. Because these are context-dependent as discussed herein, the processes they perform may vary depending on the context in which they are invoked for service execution (e.g., which node the user interface display is showing when the option integration is invoked for service execution). Referring to Figure 36, service integration type 3600 also includes non-option type 3620. Option type 3610 and non-option type 3620 of integrations can perform services such as the service types described above. Integrations can work together to perform services, including option type services 3630 provided by option type 3610 of integration and non-option type services 3660 provided by non-option type 3620 of integration. The manager 3665 for the optional service 3630 can manage the service records of the optional service 3630 (e.g., creation and editing of service records) and manage the provision of the service. Similarly, the management device 3670 for the non-optional service 3600 can manage the service records of the non-optional service 3600 and the provision of the non-optional service 3660. In fact, optional types 3610 and non-optional types 3620 can provide services to each other (as shown in Figure 36 by the arrows between the "Service" box and other types). Specifically, an integrated optional type 3610 can provide an optional service 3630 to an integrated non-optional type 3620. Similarly, an integrated non-optional type 3620 can provide a non-optional service 3660 to an integrated optional type 3610.

[0221] Referring to Figure 37, a more detailed example of integration subtypes is shown, but option type 3610 includes global types and types 3720 below the current hierarchy level. These may include optional integration types that can apply services below the current level in the hierarchy, but may also provide global services that are not specific to the current node or level when invoked. Option type 3610 also includes “below current level type” 3725, which includes optional integration types that can apply services below the current level in the hierarchy. These typically do not provide global services. Global and below current level types 3720 include action notification type 3730 and live type 3735, which will be discussed later. Global and current-level-down type 3725 may include other context-dependent option types 3740 (such as communication integration, interactive calendar integration, marketplace integration, support integration, data integration, metering integration, assignment integration, searchable access integration, related contact integration, experience option integration, shared profile integration, related structure integration, record access integration, and service access (record management) integration). While option integrations are described as context-dependent in this specification, other types of integrations (e.g., record integration and portfolio integration) may also be context-dependent. Furthermore, integration types classified here as global and current-level-down type 3720 may be current-level-down type 3725 in some implementations, and vice versa.

[0222] Non-optional type 3620 may include portfolio type 3755, which can be integrated into the portfolio structure of the entire service data structure. Non-optional type 3620 may also include calendar type 3760, which can include an integration function that provides one or more calendar services for user accounts. Non-optional type 3620 may also include contact type 3770, which can include an integration function that provides one or more services to contacts between user accounts. Non-optional type 3620 may also include profile type 3780, which can include an integration function that provides one or more services to profiles linked to user accounts.

[0223] Referring to Figures 36 and 1, the service subsystem 150 can be configured to facilitate the construction and integration of additional integrations into the service data structure 174. Such integrations may be built by bots and / or humans developing for entities managing the service subsystem 150 and / or other bots and humans (e.g., third parties that may build integrations that are incorporated and provided in a digital integration marketplace running on the service subsystem 150). These bots and / or humans may provide information to administrators 3665 and / or 3670 in building and / or editing such integrations. Furthermore, integrations within subsystem 150 may interact with computer resources in other subsystems, such as third-party subsystem 196.

[0224] The following are examples of integration functions that can be integrated into the systems discussed herein: AI-assisted information organization service integration (filtering, sorting, presets, default settings, predictive data input, etc.); AI-assisted matching service integration (combinations, people, organizations, events, content, services, activities, courses, curricula, literature, music, videos, podcasts, art, products, entertainment, etc.); service provider integration; administrator integration; integration to control other integrations; AI-assisted program / project / product management service integration (structured blueprints, schedules, plans, budgets, costs, resource allocations, etc., including some or all of the related (paid) services, built (flexibly), including progress monitoring; or planning and development of physical stores; or planning and development of e-commerce stores with automated advertising, marketing, budget management, scaling, etc.); AI-assisted showcase service integration (enabling users, organizations, etc., to showcase products, content, services, events, etc., to diverse target audiences or during visitor interactions during account integration); A AI-assisted browsing monitoring service integration (creating, presenting, and delivering user-specific experiences based on available user data, browsing history, device information, etc.); AI-assisted interactive library service integration (creation, storage, organization, and intelligent delivery functions for library-applicable content such as SOPs, albums, photos, images, art, processes, specifications, content, literature, digital books, videos, courses, training, files, and physical / digital / virtual assets); AI-assisted file management service integration (management, storage, backup, archiving, album creation / assignment, access rights setting, etc. for related files such as photos, documents, images, videos, files, and archives); AI-assisted content management service integration (identification, creation, modification, reuse, placement, advertising, marketing, etc. for related digital assets / content / files such as advertisements, posts, photos, albums, videos, media, literature, profiles, careers, and resumes) to an integrated social media, advertising, publishing, posting, and other applicable (service) platform;Potential integration of AI-assisted research / construction services (including opportunities for joint ventures, performance-based advertising, and other brands, including needs identification, risk assessment, risk mitigation, configuration and / or maintenance, creation, research, definition, development, implementation, construction; printing, manufacturing, delivery, production, processing, manufacturing, performance, supply, logistics management, etc.; sales, marketing, advertising, social media, business support, etc.; construction, identification, integration (system / existing / new) potentially including marketplaces, virtual stores, service centers, sales channels, etc.; physical, online and / or virtual stores and / or service centers) Provision of services that enable the creation, provision, optimization, management, and maintenance of centers; provision of all related incidental and system (startup, maintenance) actions, etc.); integration of AI-assisted asset management services (including tracking, monitoring, measurement, usage, status, maintenance, and activity management of related location information); integration of AI-assisted asset transformation services (conversion of physical objects to digital / virtual representations; conversion of digital / virtual objects to physical objects using technologies such as 3D printing, etc.); integration of AI-assisted audience introduction services (services (processes and systems) that present general / specific objects to general / specific audiences).

[0225] The following are additional integration examples that can be integrated into the systems discussed herein. The first example is an organizational development portfolio integration that may involve AI assistance. This includes integration with third-party systems aimed at completing service (real, digital, virtual, etc.) tasks and / or actions. For example, an organizational development service integration involving the establishment of multiple entities in multiple states, countries, or regions would include all aspects of establishment procedures, association registration, agent registration, filing with the IRS / state tax authorities (or similar agencies), payment of related expenses, and organization of digital contacts and documents. The second example is an AI-assisted real-world gameplay portfolio integration. This includes encoded game software (physical, digital, virtual, etc.), connections from peer-to-peer user accounts of game participants to interactive game services, and the integration of encoded game software into interactive game services in addition to standard game software to provide diverse (online integrated and / or real-world) game experiences. The third example is a QR code fortune cookie (live) integration. Scanning in the usual way displays your basic fortune, but using the live scan described herein will grant you one or more significantly enhanced fortune rewards. The basic fortune will inform the holder of these rewards and offer an instant download of an app with referral tracking linked to the supplier.

[0226] The system can offer restricted integrations. In the case of restricted integrations, the system can impose restrictions on the operations that a user account can perform on the integration. For example, restrictions may prevent a particular user account from performing the following operations: - Scanning to receive a specified restricted integration - Purchasing a restricted integration - Accepting a restricted integration. These restrictions can be applied at different levels, such as the device level, the user account level, and the node level within the service data structure. Additional features and concepts related to integrations are described elsewhere in this application.

[0227] B. Iterating over context-dependent user interface controls As mentioned above, some user interface controls (e.g., some option types 3610) can be context-dependent. This allows for iterative processing to perform different operations as the user interface display moves between nodes in data structures such as hierarchical service data structures. In fact, multiple such controls may be provided within a single display screen. Furthermore, the same control or group of controls can perform different appropriate operations in different structure types (including different integration types), enabling iterative behavior in response to user control selection input. For example, one or more user interface controls can perform iterative behavior such as providing one operation when a contact node is selected in a contact structure within a hierarchical service data structure, and another operation when selected in a portfolio data structure. Additionally, context-dependent operations provided in response to user interface control selections can utilize aggregated data, including aggregated records. This concept is explained in relation to specific examples of context-dependent user interface controls described later.

[0228] C. Cooperative code hosting between service subsystems and third-party subsystems Some users who utilize codes such as QR codes may be using codes reserved by online code service providers, and these service providers may manage information associated with those codes. For example, an online service provider may offer a service that maintains URLs (uniform resource locators) associated with codes included in a coded object 110 (or more coded objects) owned by the user. However, the user may want to use a different service for the maintenance of those codes. For example, even if the code is managed by a third-party subsystem 196, the user may have a user account 164 in a service subsystem 150 and may want to use the service subsystem 150 to provide services linked to that code and associated coded object 110. To achieve this, the service subsystem 150 and the third-party subsystem 196 can be synchronized with each other using application programming interface (API) calls or other communication technologies. Therefore, if user 132 updates the code data in the third-party subsystem 196, the third-party subsystem 196 can propagate that change to the service subsystem 150, and the service subsystem 150 can update the associated data of the code linked to user account 164 within that subsystem. Similarly, if user 132 updates the code data in the service subsystem 150, the service subsystem 150 will communicate the changes to the third-party subsystem 196, which can then update the associated code data linked to the user account within its own system.

[0229] Furthermore, if user 132 requests code transfer between subsystems, the subsystem can respond to the user input and coordinate the transfer of code management records. For example, user 132 can provide user input to service subsystem 150 requesting that its code record be transferred to third-party subsystem 196. In response, service subsystem 150 identifies the relevant record and sends it to third-party subsystem 196 in one or more communications. Third-party subsystem 196 incorporates the received record into itself and provides code-aware services associated with that code. In addition, if there is a standard system for entities that oversee the hosting of a particular code, service subsystem 150 and / or third-party subsystem 196 communicate with that standard system to notify it that the hosting of the code is being migrated from service subsystem 150 to third-party subsystem 196, or has already been migrated.

[0230] As described above, transferring or sharing a host of code between subsystems involves scanning the code and inputting it into the new system, as well as providing user input requesting the transfer or sharing of the host of code between hosts, thereby enabling the storage and use of code in code management and / or usage integration within the new subsystem.

[0231] D. Automatic collapse function for width-constrained code outline display This section describes the automatic collapsing function for width-constrained code outline displays. Referring to Figure 38, a mobile device 3800 may have a display 3810 that displays an outline 3820 containing entries representing nodes in a hierarchical data structure, such as a hierarchical service data structure. As shown in Figure 38, the outline contains entries representing nodes at different levels of the hierarchy. Each entry has a user interface control on its left side that indicates whether the entry is collapsed or expanded. In an expanded entry (where the "-" user interface control indicator is displayed on the left), the entry is expanded. When the user selects the "-" user interface control, the next lower level of that entry is hidden, and the entry is considered partially collapsed. Alternatively, in some implementations, when the user selects the "-" user interface control, all of the lower nodes of that entry are hidden, and the entry is considered fully collapsed. When a user selects the "+" user interface control, the next lower level of the corresponding entry is displayed, and the entry is considered to be at least partially expanded (partially expanded and partially collapsed if the lower entries of that entry in the hierarchy are a mix of hidden and visible entries). Alternatively, in some implementations, when a user selects the "+" user interface control, all nodes below that entry are displayed, and the entry is considered to be fully expanded.

[0232] If user input requests the expansion of an entry that would cause the outline to extend beyond the available width of the display, the system can respond by expanding the entry as requested while simultaneously collapsing one or more other entries to keep the outline within the available width of the display. This includes collapsing entries above the entry that was requested to be expanded. For example, referring to Figure 38, outline 3820 contains the topmost entry, the top-level node entry (representing the top-level node, such as the root node in a hierarchical data structure, or a node below the current node corresponding to the display). Below the top-level node entry are the node 1 level 1 entry and the node 2 level 2 entry. The node 2 level 1 entry is fully collapsed, the node 1 level 1 entry is partially expanded, and the node 1 level 2 entry is displayed below the node 1 level 1 entry, and below the node 1 level 2 entry is the node 1 level 3 entry. This outline also contains the node 1 level 4 entry and the node 2 level 4 entry below the node 1 level 3 entry. Node 2 level 4 entries display a "+" user interface control indicating that the entry is collapsed.

[0233] Therefore, it is possible to expand a node 2 level 4 entry based on user input. In response to such user input, the system can expand the node 2 level 4 entry and display its sub-entries, as shown in Figure 39. The system can also analyze the screen when preparing to redisplay after the expansion operation and determine if the requested expansion will cause the outline to exceed the effective width of the screen. In response to this, the system can fold another entry. In the example in Figure 39, the system partially folds the node 1 level 1 entry by hiding the node 1 level 2 entry and moving its sub-entries horizontally (to the left in the example). This makes space for the newly displayed node 1 level 5 entry to be placed below the node 2 level 4 entry. In this example, the entry whose folding has been adjusted is a higher ancestor of the entry being expanded. However, in situations where a partially expanded entry exists in the outline, it is also possible to responsively fold entries that are lower descendants of the entry being expanded. For example, if user input requests the expansion of a node 1 level 1 entry, the system may expand that entry and then re-fold the node 2 level 4 entry.

[0234] The system may collapse some outline nodes if it determines that there are no additional records represented by entries belonging to other branches of the outline below those entries, other than those that are displayed. For example, referring to Figures 38 and 39, if the only records in a node represented by Node 1 Level 3 (i.e., its descendants) are the records in a node represented by Node 1 Level 5, the system may collapse the outline between Node 1 Level 3 and Node 1 Level 5. This could place Node 1 Level 5 directly below Node 1 Level 3. This operation may occur even if it is not necessary to fit the outline within the width of the display area. However, the outline may include a display indicating the labels of nodes that have been hidden by auto-collapse (such as a display after selecting a user interface control).

[0235] This technique, which automatically collapses width-constrained outlines as needed, is applicable to various types of outlines displayed on computer screens where entry expansion and collapse are provided in response to user input, and where the screen width allocated to outline display is limited. However, it is particularly useful for outlines representing nodes within the service data structures described herein. In fact, this technique can overcome the computer-specific problem where expandable and collapsible display outlines tend to exceed the width of the outline display area on the computer display. The solution lies in technological advancements. Specifically, it can improve the user experience by leveraging computer capabilities and reduce the waste of resources associated with scrolling (horizontally and vertically if the entered text wraps). Specifically, the computer system automatically adapts and collapses some of the currently expanded entries, thereby avoiding or mitigating the need for such scrolling. Furthermore, the computer system can perform this automatically adaptive collapsing process without requiring any additional user input other than the user input requesting the expansion of entries that would result in the outline exceeding the display width. Furthermore, the automatically adapting collapsing feature can be used in combination with other space-saving functions such as text wrapping and text truncation for input fields.

[0236] E. Monitoring of profile data usage based on location information As described herein, an account can hold one or more profiles and other account data. This data can also be used in various different locations within the system, such as in different parts of the service data structure. Providing an indication of which data is being used within the system is beneficial. However, to incorporate further control over the account user's own data, an indication can be provided showing where a data unit or group of data units of account data is being used within the system. Such indications can be provided for multiple different types of data. Referring to Figure 40, a mobile device 4000 includes an information display 4010 that displays information data items from a user account, and an indication 4020 that shows where the corresponding information data items are being used within the system. For example, in Figure 40, the indication 4020 shows that the "Date of Birth" data item in the user account is being used in a system verification location and in a "High School Friends Group" (which may be a contact group), and is also being used by another user account named "John Doe". The indication may also include a delete user interface control 4030 that can be selected to delete usage from the corresponding indicated location. For example, selecting the Delete User Interface Control 4030 to the right of the John Doe List item in Figure 40 disables the John Doe user account's permission to access the Active User account's birthday data item. Clearly, requesting the discontinuation of a data item may result in the system ceasing to use that data, and the user account may lose access to certain resources associated with that use. For example, contact group consolidation may require access to birth date information to verify the age of the corresponding user who is a member of that contact group. Therefore, requesting the discontinuation of the group's birth date information may result in the user account losing access to that contact group.

[0237] In today's interconnected computer systems, user account data is used at multiple locations within the system, while users are unaware of where the data is being used. Furthermore, users are not given the option to request the suspension of data use at specific locations within the system and are forced to request a suspension of use across the entire system simultaneously. This location-based profile data usage monitoring provides a means to better control data usage for users by leveraging computer technology, enabling a more efficient and secure computer system.

[0238] F. Real-Time Auditory and Visual Code Scanning This system may include integrated functions to facilitate the processing of auditory and / or dynamic visual input for code identification. This auditory and / or visual processing can be performed in a similar manner to voice commands and / or visual commands (e.g., visual user gestures) in existing bot surveillance. The system can perform video, audio, biometric input, and / or frequency processing to identify patterns within video, frequency biometric input, and / or audio input and determine whether they match predefined audio and / or visual data (identified as commands). Data regarding patterns to be matched in audio, frequency, biometric input, and / or video scans is stored in a code record within the service subsystem 150. For example, processing may determine whether an input matches a specific audio frequency, the frequency of another signal, or a specific word or phrase structured in a predetermined manner. Such inputs are identified as codes and used in the same way as other codes scanned, as described herein. Pre-identified visual patterns identified as codes may also include visual patterns in video sequences, real-time cameras or still images, or analysis of videos playing on a video display on a device other than the scanning device, captured by the scanning device's camera. In some cases, the system may process video, frequency, biometric input, and / or voice input to scan codes only in live mode, only when the service app 124 is running on the user device 120, or only at other times (depending on the settings) when the user device 120 is operational. This setting can be changed by user input according to the user's privacy settings. In fact, in all operations described herein, it is beneficial to consider and respect the user's privacy and security needs regarding themselves and the data relating to them. This can be achieved in a variety of different ways.

[0239] In addition to the code scanning used in this specification, the bots described in this specification are integrated into or operate in conjunction with the integration to identify voice commands, frequency commands, biometric inputs, and / or visual gestures and other visual inputs, and can identify commands for executing bot functions such as the functions executed by the chatbot.

[0240] The visual, frequency, biometric input, and / or voice scans described in this specification can be executed by a dedicated user device 120 and / or as one or more software and / or hardware components integrated into other devices. It is possible to execute as one or more software and / or hardware components integrated into other devices.

[0241] As an example, the system constantly monitors auditory, frequency, biometric input, and / or video codes, issues immediate warnings about data related to auditory, frequency, biometric input, and / or video codes (such as labeled dates that may include uniform resource locators), and / or can organize / store them for quick access at a later date. As another example, video, audio, and frequency-based distributions that include constantly integrated codes such as QR codes are dynamically updated instant by instant (e.g., frame by frame) to provide instantaneous information / actions in response to visual / auditory scans of the distribution. For example, in a product placement advertising scene within a movie, a related information site is opened by scanning the recognized code. Embedded codes can be any visual or transmission code, including instantaneous video frames, transmission frequency durations, etc. Such codes also include images, photos, real-world / virtual-world live shooting scenes, and scenes incorporating identifiable landmarks. In real-world scenes, it is possible for the user terminal to combine inputs from the location information system and visual inputs to identify / verify landmarks used as codes during scanning.

[0242] Just as a biometric scanner can scan for codes in sounds, images, or scenes, a biometric scanner can perform biometric authentication scans. Here, the user's biometric characteristics can be the codes that the device scans. For example, a device can perform facial recognition or iris scanning, and a fingerprint scanner can perform fingerprint scanning. If the scan result matches a code pattern stored in the system, the system will execute the service associated with that code, similar to other codes described herein.

[0243] G. Examples of additional user interfaces Examples of additional user interfaces and their corresponding functions for use in computer service systems are described below. Referring to Figure 41, the mobile device 4100 is equipped with a root node display 4110, which may be a node display similar to the record wallet display described above.

[0244] The root node display 4110 may include a location indicator 4120 in its header that indicates the current location. This current location refers to a node called "My ObDEX" in the example, as it is a reference to the root node, i.e., the top-level node, in the hierarchical service data structure of the active user account. However, account nodes and other nodes may be located above this "My ObDEX" node. Furthermore, the root node display 4110 may include context-dependent optional user interface controls 4125. That is, by selecting an optional user interface control 4125, the system can invoke an optional integration and perform processing that is adaptable to different node locations corresponding to user interface displays shown for user input selections. Different sets of optional user interface controls 4125 may be displayed for different displays corresponding to different nodes, and / or different displays of nodes in the hierarchical service data structure. Optional user interface controls 4125 may include user interface controls within the header 4127 (which may include optional user interface controls 4125 and the location indicator 4120). Header 4127 is included in all displays, either as a multi-level header in Figure 41 or as a single-level header as shown in other figures, such as the single-level header in Figure 41. In either case, header 4127 may contain one or more optional user interface controls 4125.

[0245] The optional user interface control 4125 may include the live user interface control 4130. Depending on the selection of the live user interface control, the system can invoke live integration and display live displays, etc., as described below. Furthermore, the optional user interface control 4125 may include the action user interface control 4135. This can be selected to invoke action integration and display action displays (such as the examples described below). Furthermore, the optional user interface control 4125 may include the optional integration user interface control 4140. When this is selected, it invokes optional integration and displays optional displays, etc. The optional user interface control 4125 may include the communication integration user interface control 4145. When this is selected, it invokes communication integration and displays communication displays, etc. Communication displays can show communications (for example, communications between the current user account and other user accounts). Communications include communications associated with the current node (the root node in the example of the root node display 4110). For example, communication may be communication that has a link to the current node or a subordinate node of the current node (in an example where the root node is the current node, this could be all communication). For example, communication may be communication with user accounts that have roles that grant permissions to the current node, such as viewers, members, and administrators (host, editor, moderator, etc.). Each of these roles (and other roles) can have a set of permissions that can be configured and modified in the settings.

[0246] Referring to Figure 41, the optional user interface control 4125 may include an interactive calendar user interface control 4150 that can be selected to call the interactive calendar integration and display an interactive calendar display. The interactive calendar display can show calendar information for interactive use of the calendar. This includes, for example, interactive calendar use of events, tasks, or other calendar items involving multiple user accounts (such as calendar entries between user accounts with roles linked to the current node and / or its subnodes where the interactive calendar user interface control 4150 with the interactive calendar display selected is located).

[0247] The optional user interface control 4125 may also include the Marketplace Integration User Interface Control 4155. This can be selected to invoke integrations for managing the Marketplace Integrations for the current user account and to display integration management displays such as the Marketplace Integrations display described later.

[0248] The optional user interface control 4125 may also include a selectable search user interface control 4160 for calling the search integration function and displaying the search results. For example, the search user interface control may be a text box where the user can enter search terms to perform a search and display the search results, or a selectable button to move the user interface display to the search results. The search results can display search results, which may be limited to results from data linked to the current node and nodes below the current node. List items within the search results may be selectable to display additional data about the list items, for example by moving the user interface display to the node represented by the search list item.

[0249] The optional user interface control 4125 may also include a configuration user interface control 4165. This is selectable and invokes configuration integration to display the configuration display. The configuration display can show the configuration of the current node. Depending on the permissions allowed by the role of the current user account on the current node, the configuration may include a user interface control for configuration, which allows user input from the current user account to prompt configuration integration and change the configuration of the current node. Configurations changed for the current node are applied to the current node and, by default, may also be applied to the subordinate nodes of the current node. However, in certain scenarios, configurations applied to the subordinate nodes of the current node may override the default configurations on the node to which they apply (and possibly its subordinate nodes). However, some implementations may use other methods to apply configurations, such as applying the configuration only to the current node and not to subordinate nodes.

[0250] Referring to Figure 41, the optional user interface control unit 4125 may also include a marketplace button 4170. Selecting this button invokes the marketplace integration and displays the marketplace integration addition screen. This allows the current user account to view and register marketplace integrations applicable at the current level. This will be discussed later.

[0251] Referring to Figure 41, the optional user interface control 4125 may also include a navigation button 4172. Selecting this button displays the navigation information described later.

[0252] Referring to Figure 41, the optional user interface control unit 4125 may also include a structure user interface control unit 4174. By selecting this structure user interface control unit 4174, it becomes possible to switch between a node display, such as the root node display 4110, and a structure display, which will be described later. The structure user interface control 4174 can change its state to indicate whether the current display is a structure display or not. For example, in Figure 41, the structure user interface control 4174 is displayed in a dark color, indicating that the current display is not a structure display. However, in other figures such as Figure 53, the structure user interface control 4174 may be filled with a bright color, indicating that the current display is a structure display.

[0253] The root node display 4110 can also display node list items 4176 of nodes located directly below the current node. Each list item includes a structure user interface control section 4178, and selecting it displays the structure (details below). Each structure user interface control can be displayed as a different icon for each structure type in the specified node and its subordinate nodes. Icons without borders or fills may indicate a fixed structure, in which the current user account does not have permission to add new integrations or modify the structure. Filled icons (black in the drawing) may indicate a flex-open structure, in which the current user account has permission to add new integrations or modify the structure. Icons without fills or borders indicate a flex-closed structure. In this structure, the current user account can make certain selections and changes within the structure, but there are restrictions on adding new integrations or modifying the structure (e.g., a specified new integration can be added, but the structure itself cannot be changed). Furthermore, icons that display a multi-level hierarchical structure indicate that not everything is aggregated at the current level (e.g., some data is aggregated at the current level, but records are not). In contrast, when a structure icon contains only a single level (indicated by three squares arranged horizontally without another square at the top, as shown in the structure icon described later in Figure 48), this may indicate a roll-up structure (such as a structure where data and records can be rolled up to corresponding nodes indicated by list items). These types of icons and their representations can be applied to the structure user interface control 4174 for the current level and the structure user interface control within the node list item 4176. They can also be applied to similar list items in other representations described herein.

[0254] Each list item in node list item 4176 may also include a number indicated by "[n]" within each list item. This number may include a number indicating the number of records in a given node, such as a number representing the number of records in a given node. Each list item may also include a title 4180, which is a user input The user interface controls may also be part of a selectable user interface control to navigate the interface display to the node display of a specified node (similar to the display in Figure 41, but for the specified node, not the root node in Figure 41). At least some list items may include an access user interface control 4182, which, when selected, allows access to records such as the consolidation of the listed node (records located directly below the listed node in the hierarchy). If the node represented by the list item has only one record, selecting the access user interface control 4182 moves the user interface display directly to that record. If the node represented by the list item has multiple records, selecting the access user interface control 4182 moves to a list of user interface controls for accessing those records. If no records exist for the listed node, or if access points to those records are not configured for the current user account, the access configuration user interface control 4184 may be displayed instead of the access user interface control 4182.

[0255] When configuring an access point, a profile may be automatically configured for that access point. Alternatively, a profile may be selected and / or entered by the user as part of the access point configuration for a user account at a specific access point. For example, this process may involve receiving an access point request from a user account when the access point for the service integration is not fully configured (i.e., the access point is not fully configured). This process may also include a step of deciding to use the user account's profile for the access point configuration. Furthermore, it may include a step of acknowledging the decision to use the user account's profile for the access point configuration, identifying the profile to be used for the service integration, and configuring the identified profile for the access point as part of the access point configuration. Identifying the profile may involve determining that neither a fixed profile nor a custom profile has been specified for the access point, and setting the default profile as the specific profile for the access point. The default profile may be a public or private profile. Therefore, for example, the identified profile could be an existing profile identified or entered by user input, and / or a system-generated profile (for example, when the system selects and responds with a default profile such as a public profile, or when the system generates and responds with a profile required by the access point (for example, when generating a specific required profile by identifying and using corresponding data from other profiles of the same user account)).

[0256] In the example in Figure 41, node list item 4176 can include a "My Profile" list item, and selecting it invokes profile integration and displays the portfolio view of the current user account (details below). Node list item 4176 can also include a "My Contacts" list item, and selecting it invokes contact integration and displays the contact's contact page (details below). Node list item 4176 may also include a "My Calendar" list item, and selecting it activates calendar integration and displays the calendar view of the current user account. Node list item 4176 may also include a "My Portfolio" list item, and selecting it activates portfolio integration and displays the portfolio view of the current user account. Since the My Portfolio structure may be a structure created and generated by the current user account, the current user account may have the authority to modify the structure, including the category structure within My Portfolio, and to add and remove integration functions within that structure. Node list item 4176 can also include the "My Shared Portfolios" list item. Selecting this item invokes portfolio integration, displaying a portfolio view of a portion of the current user account's portfolio shared with other user accounts (including user account groups such as contact groups). The current user account may also have the authority to modify or build structures within the My Shared Portfolios structure. At this highest functional level, there is a provider portfolio, which includes integration features available to the current user account and providers (such as the doctor example mentioned earlier). For example, a doctor might be able to share patient information with a user account through an integration feature. Such integration features and other provider integration features can be integrated into the provider portfolio for the user account. Additionally, there can be a "My Shared Marketplace Portfolio," which is functionally tailored for user accounts providing shopping services or specifically for built integrations, intended for the user account to view and / or purchase from.

[0257] In particular, user accounts can share entire portfolios or parts of portfolios (such as integrations within a portfolio, or services included in those integrations) with other user accounts within the system. User accounts can also migrate portfolios to other user accounts within the system. When such sharing or migration occurs, the structure of the shared or migrated portfolio (or any part thereof) is maintained and migrated or shared along with the portfolio.

[0258] Node list item 4176 may also include the My Network Portfolio list item. Selecting this invokes portfolio integration, displaying a portfolio view that the system automatically constructs based on the current user account's network (for example, based on the current user account's links to other user accounts, such as an organization's network making integrations available to user accounts in that organization). For example, a university may have student integrations, alumni integrations, and faculty integrations. If the current user account is an alumnus of that university, the "My Network Portfolio" for that account will automatically include the alumni integration, and the user will be able to access and use the services of that integration. Integrations such as alumni integrations may have administrators who manage the portfolio, such as university staff or simply alumni. Examples of network connections that may encourage inclusion in a network include universities, past or current workplaces, clubs, and professional organizations. User accounts belonging to these networks may have conditionally verified or unverified access to integrations that provide services to user accounts in those networks.

[0259] The node list item 4176 may also include the "Portfolio as Member" list item. Selecting this will call the portfolio integration and display the portfolio view. This view includes portfolios that contain portfolio integrations, and there may be cases where the current user account is assigned the role of a member with permissions for those portfolio members. Similarly, the node list item 4176 can also include the "Portfolio as Administrator" list item. Selecting this will call the portfolio integration and display the portfolio view. This view may include portfolios that contain portfolio integrations. There, a certain type of administrator role is assigned to the current user account, with permissions related to that type of administrator, such as host, editor, moderator, and other administrator roles.

[0260] Therefore, for one or more of the node list items 4176 that represent the subordinate nodes of the current node in the hierarchical structure, selecting the title 4180 of the node represented by the list item provides user input for drilling down to the node represented by that list item. To access the record of the node represented by the list item, select the access user interface control 4182 (or, by selecting the access settings user interface control 4184, set an access point that will generate the access user interface control 4182 for that list item in the future). Alternatively, by selecting the structure user interface control 4178 corresponding to the list item, display the structure of the node represented by the list item (including the structure of the nodes below that list item).

[0261] Referring to Figure 42, user input selection via the navigation button 4172 can cause the system to display the navigation display 4120 shown in Figure 42. Similar to the root node display 4110, the navigation display 4210 for the root node may include a location indicator 4220, which indicates the currently displayed node and that the current display is a navigation display. The navigation display 4210 includes optional user interface controls 4125, but may also include different sets of optional user interface controls 4125. In fact, different sets of optional user interface controls 4125 may be displayed as the user interface moves between different nodes or between different display types of nodes (node / wallet display, navigation display, structure display, etc.). Also, as mentioned above, since the controls themselves are context-dependent, it is possible to select controls to perform different operations on different nodes. In the exemplary navigation display 4210 in Figure 42, the optional user interface controls 4125 may include live user interface controls 4130 and action user interface controls 4135.

[0262] In this example, the navigation display 4210 may also include a shortcut user interface control 4230, which is selected by user input and prompts the system to display the shortcut display. This display can show a list of shortcuts to different locations, such as different displays or different nodes. Such shortcuts can be configured by selecting the user interface control to which the shortcut is set, as described in the example below. Other useful navigation-based features similar to the shortcut function can be added or enabled through account settings. For example, another navigation feature could be a "Most Accessed" list and an associated user control to access that list. This would provide a list of the most frequently accessed locations for the current user account. Also, the shortcut list and My Information list described here can include data aggregated up to the current level. This would include data from the current node and its descendants.

[0263] The navigation display 4210 may include an information user interface control unit 4235. By selecting this control unit, an information display like the information display 4010 in Figure 40 can be displayed, thereby displaying data from the current user account.

[0264] The navigation display 4210 may also include node list items 4240 for the current node and ancestor nodes higher than the current node (in this example, since the current node is the root node, nodes higher than the current node are not listed). Each node list item 4240 can be the same as the node list item 4176 mentioned above, refer to Figure 41. In this example, the node list item for the root node (My ObDEX) may not include records at the root node level, so an access user interface control like the access user interface control 4182 mentioned above may not exist. Also, there may be no configurable access points, in which case the access configuration user interface control may also be omitted from the list items.

[0265] The navigation display 4210 may also include an selectable account user interface control 4245 to instruct the system to invoke the account management integration function and display the account management display. The account management display can display data from the current account. Account management may be configured to include multiple nodes and displays corresponding to different functions within the account. The account management integration may also modify the current account in response to user input on the modifiable parts of the account. And, as with any other integration, the account management integration may have related integrations, such as optional integrations that serve the account management integration to enhance its functionality.

[0266] The navigation display 4210 may also include a public profile user interface control unit 4250. By selecting this control unit, the public profile of the current user account can be previewed and / or modified. A public profile refers to a profile that is viewable by all user accounts in the system. As described herein, a user account may also hold one or more other profiles that are shared in different locations within the hierarchical service data structure.

[0267] When the Marketplace button 4170 is selected from a display such as the Root Node display 4110, the system invokes the Marketplace Integration, and the Marketplace Integration Additional Display 4310 is displayed as shown in Figure 43. The Marketplace Integration Additional Display 4310 may include a location indicator 4320 that indicates that the display is the Marketplace Integration Additional Display. The location indicator may also indicate the corresponding current node. This is because Marketplace Integration (integrations for adding or registering other integrations for the current user account) can be context-dependent. For example, the Marketplace Integration Additional Display 4310 may list only the available integrations that are applicable to the current corresponding node from which the Marketplace Integration was invoked (such as a Portfolio node or Contacts node, and possibly also applicable to subnodes of the current node).

[0268] The additional display 4310 for marketplace integrations may include an optional user interface control 4125. Furthermore, the additional display 4310 for marketplace integrations may include an available integration list item 4330. The available integration list item 4330 may each include a registration user interface control 4335 and a later registration user interface control 4340. The registration user interface control 4335, selected by user input, initiates the process of registering the corresponding integration and adding it to the structure of the current user account. This registration process may include gathering information from user input and / or existing information associated with the user account. For example, a user account profile may be selected or created and used for the new integration. It is also possible to define the integration settings. As part of the registration process, an access point for the new integration can also be configured. This integrates the new integration into the user account hierarchy and makes it available as a means of providing services to the user account via a service manager, etc.

[0269] The additional display 4310 for marketplace integrations may also include an exit user interface control 4345 that can be selected to exit the marketplace integration and return the user interface display to the original display that entered the marketplace integration. The additional display 4310 for marketplace integrations may also include a save user interface control 4350 that can be selected to save changes made during the marketplace integration. For example, this may include saving the selection of integrations to add (such as selecting the register user interface control 4335 or the register later user interface control 4340 to register the listed integrations now or later). It may also include saving selections and entries made during registration of one or more new integrations to be added to the current user account. The additional display 4310 for marketplace integrations may also include a continue user interface control 4355, which can be selected to continue an operation, such as starting a selected registration process or continuing a current registration process that has already started.

[0270] Referring to Figure 44, the option display 4410 is described. This option display is displayed in response to user input selecting the option integration user interface control unit 4140 in another display, and option integration can be invoked. Option integration manages the option display. Option display 4411 can contain many user interface controls similar to those described above. The corresponding types of user interface controls will not be described again here. However, option display 4410 can also contain types of user interface controls not described above. For example, option display 4410 can include an experience selection user interface control 4430. This allows selection from a selection of different experience types for viewing and managing the data and services provided by the options listed in option display 4410. The experience selection user interface control 4430 and similar selection user interface controls described herein are selectable to invoke option type integrations that may be context-dependent (i.e., option type integrations can be used to manage the experience selection user interface control 4430). Furthermore, such integrations may provide features such as sorting, searching, and filtering of selections offered by the selection user interface control. For example, experience types may include experiencing as the current user account (as shown in Figure 44, "My User Experience") or experiencing as a role with specific permissions (e.g., as a viewer, member, host, moderator, etc.).

[0271] The options display 4410 may also include a back button 4440 that can be selected to return to the previous display. Furthermore, the options display 4410 may include a settings shortcut button 4445 that is displayed when selected, and pressing this prompts the system to add the current display as a shortcut in the "My Shortcuts" list.

[0272] The option display 4410 may include option list items 4450 for the corresponding option integration (also referred to herein as “options”). These can be list items similar to the node list items 4176 described above. However, in this example, each item in the option list items 4450 may contain either a structure user interface control 4178 or an access user interface control 4182 suitable for a particular list item and the corresponding particular option integration (the access user interface control 4182 provides direct access to the record, while the structure user interface control 4178 provides a structure display for the corresponding option integration).

[0273] The following describes some of the options listed in option list item 4450. Selecting a communication list item invokes the communication display as described above in the communication integrated user interface control 4145 in Figure 41. Communication list items may include a highlighted star icon indicating that the corresponding user interface control is included in the option user interface control 4125 at the top of the display (and may also indicate that the corresponding user interface control is included in the same position on other displays). List items with a star that are not highlighted (without a circle in Figure 44) indicate that the corresponding user interface control is not listed in the option user interface control 4125 at the top of the screen (and may also indicate that the corresponding user interface control may not be included in the same position on other screens). In some embodiments, the option user interface control 4125 at the top of the display is set automatically by the system. However, in other embodiments, user input may be provided to select the controls to display in the option user interface control 4125 at the top of the display. For example, user input can be provided by selecting a non-highlighted star icon to highlight it and including the corresponding user interface control in the optional user interface control 4125 at the top of the display, or by selecting a highlighted star icon to de-highlight it and removing the corresponding user interface control from the optional user interface control 4125 at the top of the display.

[0274] Referring to Figure 44, the option list item 4450 may also include an interactive calendar list item corresponding to the interactive calendar user interface control 4150 described in Figure 41. Furthermore, the option list item 4450 may also include a marketplace integration list item corresponding to the marketplace integration user interface control 4155 described in Figure 41.

[0275] Option list item 4450 can also include a support list item. Selecting this item invokes support integration, facilitating support input requests from users. Support requests can be tailored to the originating node. For example, if option display 4410 is invoked from a display corresponding to node "N", the support integration function facilitates communication with user accounts assigned to provide support for node "N". Specifically, this would be user accounts assigned as hosts or other administrator roles for node N. The support communications provided may include messages, voice calls, video calls, and live chats.

[0276] The optional user interface control 4125 can also include a data list item. Selecting this item invokes data integration to provide data services (such as displaying the data itself or data analysis). Such data services can be provided for data in the current node and its subordinate nodes (i.e., data can be rolled up to the current node for use in data integration).

[0277] The optional user interface control 4125 can also include a measurement list item. Selecting this item invokes measurement integration, which provides measurement services. Specifically, this includes displaying measurement calculation results, other measured values, and related data. Measurement will be explained in more detail later, referring to the measurement display section.

[0278] The optional user interface control 4125 may also include an assignment integration list item, which, when selected, invokes assignment integration, facilitating integration assignment. For example, this includes assignments such as transferring, sending, and sharing integrations. Specifically, it includes operations to transfer or send an integration and its structure from one user account to another, and operations to share integrations across multiple user accounts.

[0279] Referring to Figure 45, another option display 4510 is shown. This option display 4510 can be the same as the option display 4411 described in Figure 44. However, option display 4510 can also contain a different set of option list items 4550. For example, option display 4510 may be the screen that appears after scrolling down option display 4410 and changing the experience selection user interface control 4430 to "As experienced by the member".

[0280] The option list item 4550 in Figure 45 can include a searchable access list item. Selecting this item invokes the searchable access integration function, enabling searchable access to contact links, including access to the current node and its subnodes. The searchable access integration function allows you to drill down into the substructure of the current node to narrow down the contacts displayed by the searchable access integration function. These contacts and associated user profiles (available in the current user account) are listed in a structured format on the contact display screen described later.

[0281] Different option list item 4550 may also include related contacts list item, and selecting this item invokes the related contacts integration function. The related contacts integration function lists and provides access to the profile data of contacts associated with the current user account through the current node or its subnodes. For example, this may apply if the related contact's user account has been assigned roles such as administrator roles for the current node and / or its subnodes. The related contacts integration function may allow drilling down into the substructure of the current node to refine the contacts listed by the integration function.

[0282] Among the different option list items 4550, there may also be an "Experience Options" list item that can be selected to invoke the Experience Options Integration. The Experience Options Integration allows users to select permission roles (such as Reader, Member, Administrator (e.g., Host, Moderator, Editor)) through user input. This allows the current user account to experience the current node and its subnodes as a user with a different permission level than their actual permission level. For example, even if the current user account is the owner of the current node, the user may choose to experience it as a member. In that case, the Experience Options Integration modifies the user account's experience when using the current node and its subnodes as if they were a member rather than the owner of the current node. This process may occur, for example, when a setting is changed.

[0283] Among the different option list items 4550 is the “Shared Profiles” list item, which can be selected to invoke shared profile integration. The system can allow a user account to create multiple custom profiles and / or form profiles and share them with different parts of the hierarchical structure. Shared profile integration allows the current user account to access the shared profiles. This is done through the user account’s links to nodes in the system, including the current node and its subnodes. This allows users to dig down the integration hierarchy and see profiles shared at different levels of the hierarchy in the current node and its subhierarchies. Furthermore, user interface controls and related functions may be provided during this digging operation or at other times to configure profiles that are relevant only to the current level.

[0284] Referring to Figure 45, option list item 4550 may also include related structure list item, which can be selected to invoke related structure integration. Invoking related structure integration displays representations of portfolio structures, record structures, and services (which may include structures) that are related to or linked to the current node and its subordinate nodes.

[0285] The set of 4550 option list items can also include selectable record access list items to invoke record access integration. Record access integration provides direct access to records. This includes navigating directly to records or providing a list of records (such as service records) and allowing direct access to records by selecting the list item.

[0286] The set of 4550 option list items can also include service access list items that can be selected to invoke service access integration. Service access integration is similar to record access integration, but service access integration can provide access to the record manager for service records corresponding to a service.

[0287] Referring to Figure 46, a structural display 4610 of the "My Portfolio" node with a position indicator 4620 is shown. For example, this page may be displayed depending on whether the user has entered and selected the structural user interface control 4176 corresponding to the "My Portfolio" list item in the node list item 4176 in Figure 41. The structural display 4610 may include a structural representation of the hierarchical structure of the current node and its subordinate nodes, such as in the form of the outline 4630 shown in Figure 46. These nodes may include portfolio integration nodes, which may include organization type nodes and service nodes.

[0288] Outline 4630 may include list entries for the current node and each node below it. Outline 4630 may also indicate which nodes contain one or more records that are directly accessible through an access point at that level, and may include an access user interface control 4635 for selection to access the corresponding records. This typically corresponds to the lowest-level node (a node that does not have any subordinate nodes in the hierarchical structure of Outline 4630), but such nodes may also contain hierarchical structures within them.

[0289] In addition to the responsive collapsible functionality described above, the outline 4630 may include a collapsible / unfoldable user interface control 4640 for collapsing and unfolding in response to specific user input requests. The structure display 4610 may also include several optional user interface controls 4125 and an exit structure user interface control 4650 that can be selected to exit the structure and return to the previous display (such as the "My Portfolio" node display, similar to the root node display 4110).

[0290] In the outline 4630 of Figure 46, if the access user interface control 4635 for the ACME CORP list item is selected, the system initiates the process of accessing the requested record. If the access point is configured, direct access to the ACME CORP node record or the list of accessible records becomes possible. If the access point is not fully configured, an access configuration screen like the access configuration screen 4710 shown in Figure 47 is displayed.

[0291] The access settings display 4710 may include a location indicator 4720 and optional user interface controls 4125. These may include user interface controls as shown in Figure 41. The access settings display may also include an exit user interface control 4345, a save user interface control 4350, and a continue user interface control 4355. However, in Figure 47 and other figures herein, the areas labeled “node-dependent options” or “context options” indicate the presence of optional user interface controls 4125, but do not specify which optional user interface controls are included. This is because different user interface controls may be included depending on other factors such as location within the system and user settings. However, it is possible to include controls for invoking option integrations as enumerated in Figures 44 and 45.

[0292] The access settings screen 4710 may include an input information area 4730, which may contain display information related to access (such as information about the integration being accessed). The input information area 4730 may also include user interface controls for entering information to configure the access point. For example, such input information may include providing existing or newly created profiles for user accounts used in integrations accessed through the access point. Other examples include providing validation and configuration priorities for information used in integrations accessed through the access point. After the access point is configured, the user account is provided with access to the requested resource (such as the requested record, which may be an integration).

[0293] Referring to Figure 48, the Marketplace Integration Display 4810 is described. For example, the Marketplace Integration Display 4810 may be displayed in response to user input selecting the Marketplace Integration User Interface Control 4155 in Figure 41. The Marketplace Integration Display 4810 may include a location indicator 4820, which indicates that the current display location is on a node in the system for the current user's Marketplace Integration (an Integration from or to the System Marketplace that is connected to the current user account). The Marketplace Integration Display 4810 may also include user interface controls as described above (including the optional user interface control 4125, back button 4440, navigation button 4172, Marketplace button 4170, and shortcut setting button 4445).

[0294] The Marketplace Integration Display 4810 also includes a My Marketplace Integration List item 4850 for the current user account. Each list item may include a Structural User Interface Control 4178 and a record count indicator (indicated by "[n]"). In addition, each Marketplace Integration List item 4850 may include a Title 4180. All Structural User Interface Controls 4178 indicate that the listed node is a record-level node (see the difference in icons in Figures 48 and other figures such as Figure 41). In this case, selecting the Structural User Interface Control 4178 prompts the system to display the node view of the specified node. Similarly, selecting the Title 4180 prompts the system to display the node view of the specified node, allowing you to list its subordinate nodes.

[0295] Specifically, the Marketplace Integrations list item 4850 can include the "ObDEX" Integrations list item, which, when selected, provides access to a list of integrations available from the Marketplace and the integrations themselves. The Marketplace Integrations list item 4850 also includes the "My ObDEX Integrations" list item, which, when selected, provides access to a list of Marketplace integrations registered to the current user account and the integrations themselves. Selecting "My Integrations Workshop" provides access to a list of integrations the current user account is working on (such as integrations under construction) and the integrations themselves. Integrations built and completed by the current user account (listed in My Integrations Workshop) become available to that account and / or other accounts. For example, by adding a completed integration to the managed integration structure shown in the "My Managed Integrations" list item within the Marketplace Integrations list item 4850, the current user account can control the integration.

[0296] Additionally, user accounts can add integrations they create to the marketplace, making them available for registration and use by all other user accounts. Alternatively, a current user account can allow only specific user subsets to register for an integration they have created. For example, only user accounts that the current user account directly shares the integration with, or user accounts in a contact group specified by the current user account. When a user account manages an integration, that account can share administrative privileges with one or more other user accounts and grant those accounts permission roles for the integration, such as administrator roles (e.g., co-host or co-owner roles for the integration). Integrations where management is shared between the current user account and one or more other user accounts can be accessed by selecting the "Shared Management Integrations" list item within the marketplace integration list item 4850. The marketplace integration list item 4850 may also include the "Integrations Pending (Review)" list item. Selecting this item allows the current user account to review and continue the registration process for integrations that have been initiated but not yet completed, or integrations that the current user account has indicated they will register later but have not yet completed.

[0297] In the category specified in marketplace integration list item 4850, integrations can be rolled up to the level of the specified node. This allows integrations from the specified node and its descendants to be displayed at the level of the specified node.

[0298] Figure 49 illustrates the ObDEX integration display 4910. For example, the ObDEX integration display 4910 may appear in response to user input selecting an ObDEX integration list item title from the Marketplace integration display 4810 in Figure 48. The ObDEX integration display 4910 may include a location indicator 4920, which indicates that the current display location is on a node in the system within the current user's Marketplace integration (an integration connected to the current user account, either from or to the System Marketplace). The ObDEX integration display 4910 also includes user interface controls as described above. These include the options user interface control 4125, the back button 4440, the navigation button 4172, the Marketplace button 4170, and the shortcut settings button 4445. The structure user interface control 4174 in Figure 49 may contain three squares instead of the usual multi-layered structure icon, indicating that the structure user interface control 4174 is not selectable in this display.

[0299] The ObDEX integration display 4910 may also include an ObDEX integration list item 4950 corresponding to the current ObDEX integration node. As mentioned above, an ObDEX integration node contains a list of integrations that a user account can register for. Therefore, by selecting each ObDEX integration list item 4950, the registration process for that integration can be initiated. As another example, if the display includes a list of integrations that the current user account has already registered for, selecting the list item may invoke the integration and provide one or more services suitable for the integration via the service manager. Alternatively, if the user account is building an integration, selecting the list item may transition the user to a development environment for building the integration, which may be provided by the service manager. In the example in Figure 49, the ObDEX integration list item 4950 contains list items for different available integrations. In the example in Figure 49, each list item is represented by a tile, and each tile may have different characteristics depending on the functionality provided for the integration represented by the tile. For example, a “(Structural) Integration-1” list item includes an information area about the list item, an image included in the list item, a description of the integration represented, and / or other indications related to the integration represented by the list item (see the area labeled “{information, image, description, etc. area}”). In other examples, list items may be simpler; for example, a “(Structural) Integration-2” list item simply includes the title within the list item. The indicated integration may provide any of the above services as appropriate.

[0300] Furthermore, list items can include other functions. For example, the (Structure) Integration-n list item can include a Structure User Interface Control 4178, similar to the Structure User Interface Control described above for other list items. Therefore, selecting the Structure User Interface Control 4178 prompts the system to move to a display screen where the structure of the expressed feature (in this case, the integration labeled (Structure) Integration-n) can be seen at a glance. Also, selecting the (Structure) Integration-n list item makes available the node location where the structure is located (i.e., the ancestor node of the structure of the expressed feature). The (Structure) Integration-n list item can also include a Code Sharing User Interface Control 4970. Selecting the Code Sharing User Interface Control 4970 displays a Code Sharing display to the system, allowing other user accounts to share codes that can be scanned on other user devices. This prompts the system to guide other users to a display representing the referenced integration. This also includes prompting the code receiving device to log in with the user account via the service app 124 if the app is not already active on the receiving device. Furthermore, if a user account does not exist, the receiving user device may prompt the receiving device to install service app 124 and create a user account. The user account is then guided to the integration represented by the shared code. In addition, the integration and the list items of the integration can be shared in other ways, such as by sending communications between user accounts in the system via service subsystem 150.

[0301] Referring to Figure 50, the Integration Manager display 5010 is described. As discussed herein, an Integration Manager is a service manager that can provide services for managing an Integration. This includes providing development tools for building and / or modifying the Integration, including services provided by the Integration. The Manager also provides tools for running and providing Integration services, which may be provided through the Integration Manager or a Service Manager. The Integration Manager display 5010 represents a display provided by such a Manager.

[0302] The Integration Manager display 5010 may include a location indicator 5020. The location indicator 5020 can indicate that the current display location is the Integration Manager for the current integration. The Integration Manager display 5010 may also include user interface controls as described above, namely the optional user interface control 4125, the exit control 4345, the save control 4350, and the continue control 4355. The Integration Manager display 5010 may also include a manager window 5050. This is a display area that includes information and user interface controls that receive output from the manager and provide input to the manager. The manager can perform services within the manager window, such as displaying the service pages described above. For example, a user account and the manager can use the manager window to play a game, interact with a chat board, or use other services. Also, as described above, the manager can also provide tools for building and / or modifying the integration, including services provided within the integration, such as modifying service records and service pages used for service delivery. The current user account may require appropriate permission roles to access the manager or utilize certain manager functions. For example, there may be cases where a user account needs to be a member of the integration, or where a specific level of administrator privileges (such as host or moderator) are required. In such cases, user interface controls may be provided to allow the user account to request such access or privileges (e.g., access to record management for the integration). As with other integration registrations in the system, the registration process may automatically configure the access profile, such as by selecting a default profile, or the registration process may require user input to create or select an access profile. This generates an access profile, which may use a unique profile, or it may use a public profile or a default profile that can be used by other access points in the system.For example, creating a profile for an access point may involve incorporating a link between that access point and an existing profile (such as a default profile, which may be a public profile). Therefore, the profile assigned to an access point may be an existing profile specified or entered by user input, and / or a system-generated profile (e.g., the system selects and responds with a default profile such as a public profile, or the system generates and responds with the profile required for the access point (e.g., generating a specific required profile by specifying and using corresponding data from other profiles of the same user account)).

[0303] Figure 51 shows the measurement display 5110. The measurement display 5110 is displayed according to the selection of measurement options as described above. The measurement display 5110 may include a position indicator 5120. The position indicator 5120 can indicate the current position, i.e., the measurement display at the currently displayed node or level ("CL" in the example in Figure 51). The measurement display also includes user interface controls common to other display screens, such as the options user interface control 4125, the back button 4440, the navigation button 4172, the marketplace button 4170, and the shortcut setting button 4445.

[0304] Furthermore, the measurement display 5110 may include measurement list items 5110. These can enumerate measurement values ​​and other related values ​​that indicate the parameters being measured. The measurement (billing) integration represented by the live display 5110 can manage and / or track the processing of in-system and third-party systems, as well as account-related incoming and outgoing measurement resources, on the system. The data is aggregated in the current node and used for analysis and calculations to generate parameter values ​​displayed in the measurement list items 5150. The aggregation option allows the measurement integration to access payments and measurement billing for third-party integrated application programming interface services. Examples of payment options include links to cryptocurrency wallets, bank accounts, credit cards, payment processing providers, and other payment implementation options, as well as withdrawal options. Notifications accessible from the measurement display 5110 through the action user interface control 4135 include notifications related to the measurement billing status.

[0305] Billing integration simplifies the setup of billing options for shared billing. Each user account can pay for its own usage-related and billable fees. Each user account may also be required to provide payment information with prior consent. If billable fees are not paid, billing integration may temporarily suspend access to the portfolio. Alternative options include temporarily freezing access to billable services and / or temporarily restricting access to affected paid services.

[0306] Third-party money transfer / payment services may be integrated into the billing system in connection with both money transfer and payment, and with products / services / content (sales, bartering, purchases, etc.). Billed resources may include managing the effort of work performed by or on behalf of the user. Working hours and rates may be based on and / or related to work experience, job title, location, organization, hours, date, working hours, holiday work, vacation, benefits, bonuses, etc. Profiles, features, and / or services related to app-integrated job services may include resumes, work history, qualifications, education, organization, third-party cross-app job service integration data, and / or the user's job requirements. More generally, information used for services may be obtained through other integrated third-party services and / or systems.

[0307] The integration of the system and measurement functions has no limitations on the traceable parameters, including Web 2.0, Web 3.0, crypto assets (coins, tokens, NFTs, services, etc.), working hours, service and / or product-related credits, referral credits, transactions and / or balances of third-party accounts, and their variations, alternatives, and combinations. Measurement items may include threshold limits that enable or disable measurement functions when the functional thresholds of the account system are met.

[0308] The service measurement option integration can include a measurement service that can be run via the manager located at the bottom of the service measurement option integration. This measurement service retrieves and analyzes underlying parameter values ​​such as usage and utilization within the configuration and generates measurement parameters and other measurement parameters as shown in Figure 51.

[0309] Referring to Figure 51, specific examples of measurement parameters in the measurement display 5110 may include the following for an exemplary user account: usage code (e.g., QR code), estimated (next) payment amount, balance, automatic replenishment limit: automatic replenishment amount, daily withdrawal rate, code rate (charge rate per code, such as QR code), code scan rate (charge rate per code scan), SMS rate (charge rate per SMS message sent), storage rate (rate per megabyte of system storage used, etc.), system utilization rate (rate for system resource usage (e.g., per data unit or per processing usage unit)), and / or other parameters suitable for measurement.

[0310] Referring to Figure 52, the live display 5210 is described. For example, the live display 5210 is displayed in response to a user input selecting the live user interface control 4130. The functionality of the live display 5210 is context-dependent and changes depending on the location within the system in which the live display 5210 is invoked. The functionality may change depending on conditions within the subsystem (e.g., profile data of the current user account, including settings, age, and current city of residence) or conditions outside the subsystem (e.g., current events outside the system, current weather, etc.). Such conditions are described elsewhere in this specification. For example, context-dependent functions that depend on the current location within the subsystem include code scanning, sharing, and sensing functions. However, there are also global functions that do not depend on the location within the system in which the live display 5210 is invoked (e.g., some latest information functions). However, these functions may depend on other conditions, such as external or internal conditions.

[0311] The live display 5210 may include a location indicator 5220, which can indicate the current location, i.e., the live display at a specified current node or level (indicated as "CL" in the example in "Figure 52"). The live display also includes user interface controls common to other display screens. These include an option selection interface control 4125, a back button 4440, a navigation button 4172, a marketplace button 4170, and a shortcut setting button 4445. Furthermore, the live display 5210 may include a live list item 5250, which lists additional integrations available within the live integration. The live list item 5250 may include controls similar to those described above in other list items in other displays. For example, the list item of the live list item 5250 may include a structured user interface control 4178, a title 4180, and / or an access user interface control 4182.

[0312] Livelist item 5250 can include an ObDEX smart scanner list item. This can be selected to invoke scan integrations that scan codes and respond appropriately, as described above. In fact, as described above, this scan can include scanning various types of codes. For example, visual codes on objects, codes in videos, codes in audio, codes in frequencies, codes from bioscans, etc. For example, a scanner can perform a bioscan that can uniquely identify an individual using the biometric information or physical characteristics of a user or non-user. This process allows current user accounts and associated users to use the system to bioscan other users or potential users. If another active user is scanned, it becomes possible to send / exchange service integration-related information, and in the case of a non-user, it is possible to register that non-user as a referring user and provide the option to register a new user account at that time or later. Bioscans may also include users and associated user accounts setting up their own bioscan-related integrations that are specific to what is presented when scanned by other users (usually depending on the user relationship). Code scanning may be restricted depending on the circumstances. For example, if a scan is initiated from a specific node within the hierarchy, at least some scan types will be unavailable. Specifically, certain code scanning capabilities will only be available when accessing the scanner from an authorized node location.

[0313] Livelist item 5250 can also include an ObDEX QuickShare list item. When this list item is selected, the system invokes an integration function. When this integration function is selected, a user terminal presentation code can be displayed for scanning by the user terminal to exchange relevant referral information. Information regarding such sharing is as described above.

[0314] The Live List item 5250 can also include an ObDEX Smart Sensing List item. Selecting this list item activates smart sensing. Specifically, it detects video, frequency, biometric input, and / or voice data, and performs biometric identification such as facial recognition (similar to chatbot identification for voice commands) when the system identifies such data. As an example of monitoring biometric input, a bioscan can be used to identify heart rate, other movements, or vital signs. This type of scan can be effectively used to monitor vital signs of vulnerable individuals such as infants and the elderly. If vital signs cease for a specified period, an alert can be sent to one or more user accounts, such as family, friends, and / or emergency response personnel. The ObDEX Smart Sensing List item can also include an Activation User Interface Control 5280. Selecting this control allows you to toggle smart sensing on and off.

[0315] Live list item 5250 can also include a Quick Share Services List item. As mentioned earlier, selecting a Quick Share Services List item prompts the system to quickly share useful services. This includes sharing useful services such as exchanging contact information or sharing upcoming events. This is achieved by the system responding to user input selections and presenting service-related codes to scan for relevant service information exchanges.

[0316] Live list item 5250 may also include a list of things happening now, and by selecting an item, the user can access information and / or services that are local or of interest to them, based on data in the corresponding user account and conditions such as the time, date, and geographical location of the user's device. For example, this local or of interest information may include restaurants, other businesses, events, retail sales, or other currently available items. This information may also be related to one of the services described herein, as appropriate.

[0317] Livelist item 5250 may also include a "Current Level Latest Information" list item that can be selected to access services related to the current node and its descendants. This may include node services that are currently running or are scheduled to run in the near future.

[0318] Furthermore, livelist items can include live-related integrations with services that are typically considered convenient for users corresponding to their user accounts, providing quick access. As an additional example, livelist items could refer to integrations with digital wallets, such as digital wallets available on mobile operating systems. Digital wallets are capable of context-dependent operation and can be integrated at any applicable level or node of the service data structure.

[0319] Available user integrations allow user accounts to build and / or incorporate live integrations. In addition, system administrators and third-party integration system administrators retain the option to incorporate live integrations. In fact, as described herein, integrations can be built and integrated at various locations within the system as appropriate, and integration into subsystems also includes integration into various node list items. Therefore, it is possible to add, modify, and / or delete integrations at various locations within the system and at available integration locations, thereby updating and improving the system. The scalability of this system offers technical advantages in terms of flexible, efficient, and feature-rich subsystems. Furthermore, as described herein, current subsystem integrations can be configured to interact and function with other subsystems.

[0320] Referring to Figure 53, the action display 5310 may include a location indicator 5320, which indicates the action display at the current location, i.e., the current node or level indicated (indicated as "CL" in the example in Figure 53). The action display 5310 may also include user interface controls common to other displays, such as the optional user interface control 4125, the back button 4440, the navigation button 4172, the marketplace button 4170, and the shortcut setting button 4445.

[0321] Here, an action refers to a record that can request a user account to take some action (such as checking a message, replying to a message, or performing a task within a subsystem). Action integration at the top category and subcategory may include services that enable the identification, sorting, and filtering of action representations at any integration node level, including node levels such as options, contacts, and calendars. Actions can also be assigned priorities and levels from other users, such as the sender of the action. Actions have delivery configuration options that allow you to determine the sending schedule (whether or not to send, when, and how often) for associated action notifications. The action in question can be routed or assigned permanently or temporarily to other user accounts or groups of user accounts (e.g., contact groups).

[0322] The action selection list can be structured into the following higher categories, for example: Action integration includes new (unconfirmed), confirmed (read / unread), pause (for an appropriate period, etc.), check later (to be checked later), save (for later reference, important, etc.), archive (for records), delete (clear), transfer (one-to-many), assignment of different specifications, applicable service integration-related actions, and applicable combinations, variations, and similar actions. Transfer (one-to-many), assignment of different specifications, applicable service integration-related actions, and / or applicable combinations, variations, and similar actions.

[0323] The action selection list may consist of the following higher categories: Subcategory action integration types include user notifications and user action requests, which include information (new / updated content), communications (chat, voice, video, posts / message boards, etc., including message types and live call notifications), approvals (project-related, etc.), acceptance / confirmation of shared and / or forwarded integrations, physical or email receipts, requests for information and actions, invitations (contact links, events, groups, clubs, subscriptions, organizations, etc.); calendar items (tasks, events, content, reminders, appointments, etc.); and / or service integrations related to applicable subcategory actions, and / or applicable actions.

[0324] The structure user interface control 4174 is lightly colored in Figure 53 (compared to the structure user interface control 4174 in Figure 41, which is darkly colored). As mentioned above, this indicates that the current display is the structure display. Therefore, the action display 5310 includes a selection list structured in the form of an outline 5330, which can outline the structure of action representations and groupings of actions nested within categories. Each list item in the outline 5330 has an associated access point for the current user account to access one or more actions and may include an access user interface control 4182 that can be selected to access the associated actions. That is, the access user interface control 4182 allows the user to proceed with the user interface display to an associated action type integrated related service record that can be selected by the user, where the selected action type manager is displayed, and the service action can be reviewed, resolved, transferred, saved, delayed, archived, shared, (integrated) deployed, etc.

[0325] Furthermore, outline 5330 may include a collapse / expand user interface control 4640 that allows the user to collapse or expand the nodes of outline 5330 by selection. The responsive collapse / expand functionality of outline nodes described above is also applicable to outline 5330 and other display outlines described and illustrated herein.

[0326] The action list display type user interface control 5340 within the action display 5310 can indicate the display type of the representation of actions and action groups in the action display 5310. The action list display type user interface control 5340 currently indicates that the display type is "New (All Actions)". The action grouping includes a top-level node "New (All Actions)", which can list new (not yet reviewed or addressed) actions. Furthermore, the "New (All Actions)" node in the outline 5330 may include child nodes according to the priority level of the actions. The outline 5330 also includes a top-level node of previously reviewed actions, with child nodes categorizing when the actions were reviewed or received. It may also include a top-level node of "Pending Actions", which can also include groupings of child nodes. The action functionality described herein can create technical advantages in addressing the problem of overload with numerous actions that need to be executed in computer-driven processing, and the problem that these actions are often disorganized. For example, the action functionality described herein enables efficient optimization so that users can view, control, manage, and respond to action requests from potentially numerous integration sources under a centrally organized integration.

[0327] Referring to Figure 54, another action display is shown. Specifically, Figure 54 shows the action type display 5410, which can be displayed by selecting "Action Type (All)" from the action list display type user interface control 5340. The action type display 5410 may include a position indicator 5420, which can show the action type display at the current position, i.e., the currently indicated node or level (indicated as "CL" in the example in Figure 54). The action type display 5410 also includes user interface controls common to other display screens, such as the options user interface control 4125, the back button 4440, the navigation button 4172, the marketplace button 4170, and the shortcut settings button 4445.

[0328] However, in Figure 54, instead of outline 5330, an outline 5430 can be included, which allows actions to be grouped by action type. For example, in the example shown in the figure, the types include: - Information node (child node: New Training, with UI control 4182 for accessing related actions) - Request node (child node: Information, with UI control 4182) - Invite node (child node: Event, child node: Contact link, each with UI control 4182) - Communication node (with collapsible / expandable user interface control 4640; the collapsed state indicates that child nodes are hidden), and a node labeled "(Type / sub-n) Action-n" (indicating the possibility of including other types, the node shown in the figure is just an example). Thus, action type integrations related to applicable service integrations as described herein can be included in the display shown in Figure 54.

[0329] Referring to Figure 55, synchronized mobile and desktop displays are shown. Specifically, both the mobile device 5510 and the desktop device 5520 can be user devices that interact with the service subsystem 150 and run a service application 124 that enables the functions described herein. For example, the mobile device 5510 and the desktop device 5520 are each connected to the service subsystem 150 individually and / or to each other via local or remote connections. For example, the mobile device 5510 may be connected to the service subsystem 150 and the desktop device 5520 at the same time, and the desktop device 5520 may be connected to the service subsystem 150 indirectly via the mobile device 5510. For example, the mobile device 5510 may be linked to the desktop device 5520 in the form of a desktop computer or smart display in order to play online games. The mobile device 5510 can display a mobile display 5530 with a layout via the service application 124. Desktop device 5520 can also display desktop display 5540 via service app 124, which may differ from service app 124 for mobile device 5510 (for example, service app 124 for desktop device 5520 may be a general web browser or a dedicated desktop application rather than a mobile app, or a single app may adapt to both desktop and mobile devices, such as changing its behavior based on the device screen size). Also, mobile display 5530 and / or desktop display 5540 may reside on a single display screen, span multiple screens (including extended display functionality or foldable smartphones), be a virtual display, or be a projected display. However, desktop display 5540 may include a mobile area 5550 that can mimic the layout of mobile display 5530. Desktop display 5540 may also include a content area 5555 separate from the mobile area 5550.When in use, if the administrator is running and / or managing the integrated services of this system on the desktop device 5520, the mobile area behaves similarly to the mobile display 5530 when performing the same operations. However, the content area 5555 can be used by the manager to provide additional screen space for content, such as the type of content that is normally displayed in the central display area of ​​a display (between the upper and lower user interface control areas) as shown in the other figures described herein. This allows for a large display area in the content area 5555 while maintaining a consistent appearance and operability between the mobile device 5510 and the desktop device 5520. This enables efficient use of screen space and improves the overall efficiency and effectiveness of the system. Furthermore, the user can select "Hide User Interface Controls" 5560 via user input, thereby hiding part or all of the mobile area 5550 and expanding the content area 5555 to include part or all of the area previously occupied by the mobile area 5550. This is useful when more screen space is desired for the functions displayed in the content area 5555. Therefore, this operation involves shrinking or contracting the entire mobile area, and in some cases, it may not be displayed at all.

[0330] Blended profiles are described below. In a computer service system, a single user account may have access to multiple user profiles through different connections and links within the system. For example, referring to the schematic diagram in Figure 56, Alice's user account may contain multiple profiles 5610, and Joe's user account may contain multiple profiles 5620. Both user accounts are members of a high school friends contact group 5630 within the system, which may include a service that allows members to access other members' profiles (including names, high school graduation years, and a list of extracurricular activities participated in during high school). Alice and Joe's user accounts also have access to a game integration feature 5640 that provides a service enabling online gameplay between them. This game integration feature allows members to access other members' profiles (including names, high scores in specific games, and a list of digital resources available within specific games). Additionally, Joe's and Alice's user accounts may share an email address directly through the system, which is considered a separate profile at the contact sharing location 5650. If Joe's user account requests to view Alice's user account profile (for example, by selecting a user interface control containing the name "Alice" within the game integration feature 5640), the system can respond by creating an integration profile 5660 for Alice. This profile may include information from Alice's user account that is accessible to Joe's user account through the game integration 5640 and the high school friends contact group 5630 (as well as other connection channels such as information directly shared between Alice and Joe's user accounts in the contact sharing location 5650 (email addresses)). Creating an integration profile involves merging the profile used for game integration with the profile used ...

Claims

1. The service system includes the following: Computer systems including the following: User accounts; and A service data structure linked to a user account in a computer system, the service data structure includes the following: Multiple structured categories having a hierarchical structure, having multiple levels, and a structured category includes a first category at the first level and a second category within the first category, with the second category located at the second level below the first level in the hierarchy; and The record belongs to Category 2 and includes the following: Display of at least one scannable code linked to a user account within a computer system; and This refers to a set of one or more computer-implemented services that are executed via a computer system in response to user input using at least one scannable code.

2. A service system according to claim 1, wherein the user account is a linked user account, the service data structure includes at least one record category and at least one generally available record within the record category, and the computer system further includes instructions indicating that at least one authorized change user account has at least one indicated authority to change at least one portion of the generally available data structure items in the computer system.

3. The service system according to claim 2, wherein at least a portion of the set of generally available data structure items is a predefined subset smaller than the entire set of generally available data structure items, thereby restricting the computer system to at least one indicated permission to the predefined subset.

4. The service system according to claim 2, wherein at least one user account with modification authority includes linked user accounts.

5. The service system according to claim 2, wherein the computer system further includes: at least one processor; and A memory that stores the user account and service data structure, the memory further stores instructions that, when executed by at least one processor, cause at least one processor to perform the following actions: To receive a change request for at least one of the publicly available data structure items from at least one user account with modification privileges; Upon receiving the request, verify that the user account with modification privileges has the authority to make the changes, and this verification includes accessing information indicating that the user account with modification privileges has at least one specified privilege. After verifying that the user account with modification permissions has the authority to make changes, the process of making the requested changes is executed.

6. The service system according to claim 1 further includes an encoded object comprising at least one scannable code in a scannable form.

7. A service system according to claim 6, wherein the encoded object is an order time representation, and one or more computer-implemented services include an order for an object of the type indicated in the order representation.

8. A service system according to claim 7, wherein the record is a first record, and the ordered goods are an encoded object comprising a scannable code configured to link to a second record in a different computer system from the first record.

9. The service system according to claim 8, wherein the ordered item is a manufactured physical object.

10. The service system according to claim 8, wherein the ordered item is an encoded signature.

11. A service system according to claim 1, wherein the computer system further includes a limited access indicator indicating whether a particular user account has access rights to a particular structured category, a particular record, a particular record service, or a particular combination thereof.

12. The service system according to claim 1, wherein the computer system further includes: at least one processor; and A memory that stores the user account and service data structure, the memory further stores instructions that, when executed by at least one processor, cause at least one processor to perform the following actions: It provides a visual representation of the current subcategory contained within another category in the service data structure, and this visual representation includes selectable user interface controls to display one or more indicators of one or more specified items linked to one or more items of one or more specified types within the current subcategory, where the items within the current subcategory include one or more items in one or more descendant subcategories contained within the current subcategory.

13. The service system according to claim 12, wherein the items in the current subcategory include one or more subcategories.

14. The service system according to claim 12, wherein the items in the current subcategory include one or more records.

15. A service system according to claim 12, wherein the indicated item includes one or more messages.

16. The service system according to claim 12, wherein the displayed items include one or more action items that require user input.

17. The service system according to claim 1, wherein the computer system further includes: at least one processor; and A memory that stores the user account and service data structure, the memory further includes instructions stored in such a memory that, when executed by at least one processor, cause at least one processor to perform the following actions: A representation is presented that represents at least a portion of the service data structure, and the representation indicates the current position in the hierarchical structure of the service data structure; In response to receiving user input for the expression, move between levels within the service data structure; and Modify the representation to reflect the movement between levels.

18. A service system according to claim 17, wherein the representation includes a record wallet display and a navigation display, the record wallet display includes a category content display including user interface controls representing items in the current category, and the navigation display includes user interface controls representing the current category and categories higher than the current category in the hierarchy, wherein: The Record Wallet display includes selectable user interface controls to switch to a navigation display configured for the current category represented in the Record Wallet display; and The user interface controls in the navigation display (representing the current category and higher-level categories in the hierarchy) can each be selected to switch to the record wallet display for the category represented by the selected user interface control in the navigation display.

19. The service system according to claim 18, wherein the record wallet display and the navigation display each include one or more identical user interface controls located in the same position in both the record wallet display and the navigation display.

20. A service system according to claim 18, wherein the presentation of the representation includes presenting a customized subset of categories from a service data structure, the customized subset of categories being customized by the computer system based on current conditions identified by the computer system.

21. The service system according to claim 18, wherein the presentation of the representation includes presenting a representation of a customized subset of a set of computer-implemented services that are performed via a computer system in response to user input using at least one readable code, the customized subset of services being customized by the computer system based on current conditions identified by the computer system.

22. A service system according to claim 18, characterized in that navigating between hierarchies within a service data structure includes traversing the hierarchy of the service data structure to reach the record.

23. A service system according to claim 18, wherein the change in representation includes indicating a set of one or more computer-implemented services.

24. A service system according to claim 1, wherein the record described herein is a first record, and the service data structure further includes a second record of a second category.

25. A service system according to claim 1, wherein the record described herein is a first record, and the service data structure further includes a second record in a third category, the third category being at a second level.

26. A service system according to claim 1, wherein a first category includes an indication of a set of services available for records of the first category, a second category includes an indication of a set of services available for records of the second category, and the set of services available for records of the second category includes a subset of the set of services available for records of the first category.

27. The service system according to claim 26, wherein one or more computer-implemented services performed via a computer system in response to user input using at least one scannable code include a subset of services available for records of a second category.

28. A service system according to claim 11, wherein the computer system further includes: at least one processor; and Memory for storing user accounts and service data structures, and memory for storing instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: The system receives a user input request, and the user input request records the data in the computer system. Request to transfer to a new hierarchical location within; and In response to receiving a user input request, the record and the record's category structure indicator are transferred to a new hierarchical location in the computer system. The category structure indicator shows the category structure, which includes the categories in the hierarchy containing the record. The categories in the hierarchy containing the record include the first category and the second category. The record maintains the category structure shown by the category structure indicator at the new hierarchical location in the computer system.

29. A service system according to claim 28, wherein the user account is a first user account, the service data structure is a first service data structure, and the transfer of a record includes transferring the record to a second service data structure associated with a second user account instead of associating it with a first user account.

30. A service system according to claim 28, wherein the service data structure is a first service data structure, and the transfer of a record includes transferring the record to a second service data structure associated with a user account, the first service data structure being associated with a first organization designation of the user account, and the second service data structure being associated with a second organization designation of the user account instead of a first organization designation of the user account.

31. The service system includes the following: A computer system equipped with the following: at least one processor; and The memory stores user accounts and service data structures, and also stores instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: This manages the service data structure associated with user accounts within a computer system. The service data structure includes records containing the following items: Display of at least one scannable code linked to a user account within a computer system; and A representation of one or more computer-implemented services that are executed via a computer system in response to user input using at least one scannable code; and Performing one or more computer implementation services in response to user input to a computer system using at least one scannable code; The management of the service data structure includes performing a first set of one or more actions in response to user input from at least one computerized human user interface device, and performing a second set of one or more actions in response to user input from at least one artificial intelligence bot operating on a computer system.

32. A service system according to claim 31, further comprising an encoded object that includes at least one scannable code in a scannable form.

33. The service system includes the following: A computer system equipped with the following: at least one processor; and The memory stores user accounts and service data structures, and also stores instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: This manages the service data structure associated with user accounts within a computer system. The service data structure includes records containing the following items: Display of at least one scannable code linked to a user account within a computer system; and A representation of one or more computer-implemented services that are executed via a computer system in response to user input using at least one scannable code; and The computer system receives user input, including input codes, and this user input uses the input codes and service data structures to request the desired action; To perform security checks on input codes in response to receiving user input to a computer system that uses input codes; and If the security check of the input code detects a security issue, take one or more available precautions against the input code; or If the security check for the input code does not result in a security failure, then either one or more available precautions for that input code are not taken.

34. A service system according to claim 33, further comprising an encoded object that includes at least one scannable code in a scannable form.

35. A service system according to claim 33, The security check involves searching a database of authentic codes containing at least one scannable code, and determining whether the input code matches any of the authentic codes in the database. If the input code does not match any of the authentic codes in the database, the security check fails; if the input code matches any of the authentic codes in the database, the security check succeeds. Taking one or more of the available precautions against an input code includes refusing to perform the requested action; Failure to take one or more available precautions against an input code includes failing to take the requested action.

36. A service system according to claim 35, wherein an input code matches at least one scannable code, and the requested action includes performing a management action for managing a record that includes instructions for at least one scannable code.

37. A service system according to claim 33, A security check includes determining whether an input code is invalid, and determining whether an input code is invalid includes analyzing the requested action. If the requested action is determined to be invalid, the security check fails; if the requested action is determined not to be invalid, the security check succeeds. Implementing one or more available precautions against input codes includes displaying user output warnings; and Failure to implement one or more available precautions for an input code includes not displaying a user output warning.

38. The service system according to claim 37, wherein the step of determining whether an input code is invalid includes analyzing whether a URL (uniform resource locator) linked to the input code is invalid in a computer system.

39. The service system according to claim 37, wherein the input code matches at least one scannable code, and the determination of whether the input code is invalid includes parsing a record that includes an instruction for at least one scannable code.

40. The service system includes the following: A computer system equipped with the following: at least one processor; and Memory for storing user accounts and service data structures, and memory for storing instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: This manages the service data structure associated with user accounts within a computer system. The service data structure includes records containing the following items: This manages the service data structure associated with user accounts within a computer system. The service data structure includes records containing the following items: Display of at least one scannable code associated with a user account within a computer system; and A set of one or more computer-implemented services that are executed via a computer system in response to user input using at least one scannable code; Receiving user input, including input codes, into a computer system; the user input requests an action using the input code; In response to receiving user input to a computer system that uses input codes, search a database of authentic codes containing at least one scannable code and determine whether the input code matches any of the authentic codes in the database; and If the input code is determined not to match any of the authenticated codes in the database, the requested action will not be performed; or If the input code is determined to match one of the authenticated codes in the database, then perform one of the requested actions.

41. A service system according to claim 40, further comprising an encoded object that includes at least one scannable code in a scannable form.

42. The service system includes the following: A computer system equipped with the following: at least one processor; and The memory includes a first user account and a service data structure, and further includes instructions that, when executed by at least one processor, are configured to cause at least one processor to perform the following actions: Manages the service data structure associated with user accounts within the computer system. The service data structure includes records containing the following items: Display of at least one scannable code associated with a user account within a computer system; and Display of one or more computer-implemented services executed via a computer system in response to user input using at least one scannable code; Performing one or more computer implementation services in response to user input to a computer system using at least one scannable code; Receiving a request to create a second user account; To create a second user account in response to a request to create a second user account; A second user account is linked to a tracking code, which indicates the referrer of the second user account. The referrer is either the product provider user account of the product provider linked to the second user account creation request, or a referring user account linked to the second user account creation request. For the creation of a second user account, add credit to the referrer's record.

43. A service system according to claim 42, further comprising an encoded object that includes at least one scannable code in a scannable form.

44. The service system according to claim 42, wherein the referrer is the product provider user account of the product provider associated with the request to create a second user account.

45. The service system according to claim 42, wherein the referrer is a referral user account linked to a request to create a second user account.

46. The service system includes the following: A computer system equipped with the following: at least one processor; and It includes memory for storing user accounts and service data structures, and further includes memory for storing instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: The service data structure is managed using a service code computer subsystem and associated with user accounts within the computer system. This involves managing the service data structure using at least one user device computer application used exclusively for the service code computer subsystem and at least one user device computer application designed for use in service-specific computer subsystems other than the service code computer subsystem. The service data structure includes records that include: Display of at least one scannable code linked to a user account within a computer system; and Display of one or more computer-implemented services performed via a computer system in response to user input using at least one scannable code; and Performing one or more computer implementation services in response to user input to a computer system using at least one scannable code.

47. A service system according to claim 46, further comprising an encoded object which includes at least one scannable code in a scannable form.

48. The service system includes the following: A computer system equipped with the following: at least one processor; and The system includes memory, which stores user accounts and service data structures, and further includes stored instructions that, when executed by at least one processor, cause at least eleven processors to perform the following actions: It manages a service data structure linked to user accounts within a computer system, and this service data structure includes records that include the following: Display of at least one scannable code linked to a user account within a computer system; and Display of one or more computer-implemented services executed via a computer system in response to user input using at least one scannable code; Receive user input to a computer system using at least one scannable code; In response to receiving user input to a computer system that utilizes at least one scannable code, associate a quick link with at least one scannable code and display the quick link on a user output device; In response to receiving a quick link as user input, perform one or more computer implementation services linked to at least one scannable code; and Quick links are reused to make them available in subsequent computer system responses to subsequent user input received by a computer system using scannable codes, and this reuse includes unlinking the quick links from at least one scannable code.

49. A service system according to claim 48, further comprising an encoded object that includes at least one scannable code in a scannable form.

50. A system that includes the following: A computer system equipped with the following: at least one processor; and It includes memory, which stores instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: A user interface display is presented that represents the current node in a hierarchical data structure, and as the user interface display moves between nodes in the hierarchical data structure, the hierarchical data structure includes multiple service integrations, the user interface display includes context-dependent user interface controls displayed at multiple nodes in the user interface display, the multiple nodes are located at multiple levels of the hierarchical data structure, and include the following elements: Contact nodes within contact integration that include contact nodes linked to the profile of an account other than the active user account; and Portfolio nodes within a portfolio integration (belonging to a separate portfolio integration from the contact integration and being a node type other than a contact node), the portfolio integration includes nodes linked to portfolio integrations integrated into a hierarchical data structure to serve active user accounts, and the portfolio integration includes structures other than account profiles; and As the user interface display moves between nodes, iterates through the state of context-dependent user interface controls. This iteration is configured to respond by calling context-dependent integration and executing triggered processes when a context-dependent user interface control is selected. These triggered processes are adjusted to match the current node displayed as the user interface display moves between multiple nodes, and the process differs for each node.

51. In the system according to claim 50, the action further includes performing an operation on the integration of a hierarchical data structure and modifying the functionality of the integration based on predetermined conditions.

52. In the system according to claim 50, a management integration of contacts or portfolios is managed by one or more computer implementation managers, the operation of which includes the managers managing the management integration, and the management of which includes performing processes for building, modifying and operating the management integration.

53. The system according to claim 50 further includes using contact integration to generate a blended profile derived from a plurality of profiles connected to different nodes in a hierarchical data structure.

54. The system according to claim 50 further includes the following operations: While the user interface display is showing a contact node, upon receiving user input to select a context-dependent user interface control, trigger processing tailored to the contact node is executed; and While the user interface display is showing a portfolio node, upon receiving user input to select a context-sensitive user interface control, trigger processing is executed that is tailored to the portfolio node.

55. In the system according to claim 50, the triggered process includes rolling up the current node data up to the level of the current node so that the current node data includes the data of the current node and one or more of its descendants.

56. In the system according to claim 54, the context-dependent user interface control is a search control, the trigger processing includes searching for a data item, and the data item is limited to items associated with the current node and one or more of its descendants.

57. In the system according to claim 50, the context-dependent user interface control is an action control, and the triggered process includes displaying an action display that shows one or more specific controls representing an available set of actions including one or more digital actions, wherein the one or more digital actions are limited to actions associated with the current node and one or more of its descendants.

58. In the system according to claim 50, the context-dependent user interface control is a marketplace control, and the triggered process includes displaying a digital marketplace that is operable to accept user input for registering a set of available structures, which includes one or more structures configured to be integrated into a hierarchical data structure, the selection of structures within the set of available structures being adjusted to the current node.

59. In the system according to claim 50, the context-dependent user interface control is an instrumentation control, and the triggered process includes displaying instrumentation data for the current node, the displayed instrumentation data includes node-limited data which is limited to instrumentation data for the current node and one or more descendants of the current node.

60. In the system according to claim 50, the context-dependent user interface control is a data analysis control, and the triggered process includes displaying a data analysis for the current node, the displayed data analysis includes node-limited data analysis which is limited to the data analysis for the current node and one or more of its descendants.

61. In the system according to claim 50, the context-dependent user interface control is a data control, and the triggered process includes displaying data for the current node, the displayed data including node-limited data which is limited to the data of the current node and one or more of its descendants.

62. In the system according to claim 50, the context-dependent user interface control is a communication control, and the triggered process includes displaying one or more specific controls for the current node, the one or more specific controls including one or more node-limited specific communication controls that are limited to communications associated with the current node and one or more of its descendants.

63. In the system according to claim 50, the context-dependent user interface control is a configuration control, and the triggered process includes displaying specific controls for displaying and editing configurations that apply to the current node and one or more of its descendants.

64. In the system according to claim 50, the context-dependent user interface control is an information control, and the triggered process includes displaying information about the current node, the displayed information including node-limited information which is limited to information about the current node and one or more of its descendants.

65. In the system according to claim 50, the context-dependent user interface control is a support control, and the triggered process includes displaying a support request control for the current node, the support request control being selectable to send a support request to a user profile linked to the current node as a support provider.

66. In the system according to claim 50, the context-dependent user interface control is a live control, and the triggered process includes displaying live information about the current node, the live information displayed includes node-specific live information, the node-specific live information refers to information about current events associated with the current node and one or more of the current node's descendants.

67. In the system according to claim 50, the context-dependent user interface control is an option control, and the triggered process includes displaying options for the current node and its descendant nodes, the options including at least two control displays, the displays consisting of controls of the following types: information control, configuration control, marketplace control, communication control, data control, data analysis control, support control, measurement control, action control, and live control.

68. A system that includes the following: A computer system equipped with the following: at least one processor; and The memory, when executed by at least one processor, includes instructions configured to cause at least one processor to perform the following actions: Present a user interface display including an outline; and In response to a system determination regarding the outline, the system includes partially collapsing the subject entries of the displayed outline, wherein the partial collapsing includes structuring and presenting the outline to include one or more hidden entries and one or more visible entries from the outline hierarchy that are lower in the subject entry.

69. In the system according to claim 68, the outline represents a plurality of nodes in a computerized hierarchical data structure, one or more entries of the outline are collapsed in the user interface display, one or more entries below the collapsed entries are hidden, the outline fits within the available width of the user interface display, and the partial collapse process includes: Receive user input indicating that the outline should be expanded, thereby displaying one or more expanded entries of the outline below the collapsed entries of the outline; and In response to user input, perform the following: Expand the outline to reveal one or more of the displayed entries; and Collapse and hide one or more newly hidden entries in the outline other than those already displayed, so that the outline fits within the available width of the user interface display.

70. In the system according to claim 69, at least one of the one or more newly hidden entries is located above the entries disclosed in the outline hierarchy.

71. In the system according to claim 69, one or more newly hidden entries are located directly above the displayed entries in the outline hierarchy.

72. In the system according to claim 68, partial collapsing includes collapsing some outline entries in response to the system determining that there are no additional records in other branches of the outline below those entries other than those that are displayed.

73. A system that includes the following: A computer system equipped with the following: at least one processor; and The memory, when executed by at least one processor, contains instructions stored to cause at least one processor to perform the following actions: In a profile sharing system, sharing multiple profiles linked to a shared account with another account; Integrate profile data from multiple shared profiles to create a blended profile; and In response to user input from different accounts, if a user requests to view profile information for a shared account, the system displays profile data from the blended profile.

74. In the system according to claim 73, the integration of profile data includes identifying duplicate data in multiple profiles linked to a shared account and deduplication of the duplicate data in the integrated profile.

75. In the system according to claim 73, the integration of profile data includes filtering and removing data that has been excluded from one or more of the multiple profiles, wherein the excluded data is excluded from the display of data from the blended profile.

76. In the system according to claim 75, the excluded data includes all data within the filtered profile.

77. A system that includes the following: A computer system equipped with the following: at least one processor; and It includes memory, which stores instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: The system presents a user interface display representing the current node in a computerized hierarchical data structure, and as the user interface display moves between nodes in the hierarchical data structure, it presents a category node user interface area representing the category nodes below the current node in the computerized hierarchical data structure, the category node user interface area includes: A drill-down user interface control that allows selection and drills down the user interface display to a category node, displaying representations of one or more subcategory nodes below the category node; and An access point user interface control that is selectable and displays an access indicator for accessing one or more records linked to a category node.

78. In the system according to claim 77, the category node user interface area further includes a selectable structure user interface control for displaying a structure display of the category node, the structure display showing the structure of the category node and its descendant nodes in a single display.

79. In the system according to claim 77, the access display displays data from one or more records associated with the category node.

80. In the system according to claim 77, the access display displays one or more selectable user interface controls to initiate adding a representation of one or more records to the access display, the one or more records being linked to a category node.

81. In the system described in claim 80, the access display currently does not display a representation of the record integration linked to the category node.

82. In the system described in claim 77, the category node is a portfolio node.

83. In the system described in claim 77, the category node is a contact group node.

84. A system that includes the following: A computer system equipped with the following: at least one processor; and It includes memory, which stores instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: In a hierarchical data structure system, maintaining data indicating multiple different locations for a user account that uses multiple information data items obtained from the active user account structure; and A profile monitoring user interface display is provided for active user accounts, the profile monitoring user interface display representing multiple information data items, the profile monitoring user interface display including one or more displays for each data item of the multiple information data items, and the one or more displays indicate one or more of several different locations where the corresponding data item is used.

85. The system according to claim 84 includes an operation to discontinue the use of one of the information data items at a location indicated on the user interface display, in response to a request from the user to discontinue the use of one of the information data items at that location.

86. The system according to claim 84 includes revoking permission to use the computer resource associated with the location indicated by the user account in response to a user input on the user interface display and a request to cease using any of the information data items at the location indicated on the user interface display.

87. In the system according to claim 84, a profile structure is included at a plurality of different locations.

88. In the system according to claim 84, the multiple different locations include a contact group structure.

89. In the system according to claim 84, the user account is a first user account, and multiple different locations include second user accounts other than the first user account.

90. A computer system equipped with the following: at least one processor; and It includes memory, which stores instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: Maintain a code record associated with a user account, which defines a predetermined code containing one or more predefined patterns in video patterns, frequency patterns, biometric patterns, and voice patterns; and further define a service to be performed using an integrated function in response to a computer system scanning the code in accordance with the identification of the predefined pattern. Scanning of inputs including one or more of the following for a given code: video input, frequency input, biometric input, and voice input; Identification of a predetermined code; and In response to the identification of a predetermined code, the service is performed using integration within the computer system.

91. In the system according to claim 90, the predefined pattern includes a video pattern.

92. In the system according to claim 90, the predefined pattern includes an audio pattern.

93. In the system according to claim 90, the predefined pattern includes a frequency pattern.

94. In the system according to claim 90, the predefined pattern includes a biometric authentication pattern.

95. In the system according to claim 90, the input scan includes the broadcast scan in the electronic output device.

96. In the system according to claim 90, the input scanning includes scanning a real scene using a camera on a user device within the computer system.

97. A computer system equipped with the following: at least one processor; and It includes memory, which stores instructions configured to cause at least one processor to perform the following actions when executed by at least one processor: The user account receives a user-input access point request for an access point to a service integration that is not fully configured; It is decided to use the user account's access point profile for configuring the access point; and Having decided to use the user account's access point profile for access point configuration, identify the specific profile to be used for service integration and configure that specific profile as the access point profile for that access point as part of the access point configuration.

98. In the computer system according to claim 95, the step of identifying a specified profile includes determining that neither a fixed profile nor a custom profile has been designated as a target for setting for the access point, setting a default profile as the specified profile for the access point, or generating a new profile for the access point based on one or more existing profiles for user accounts.

99. In the computer system according to claim 96, the step of identifying a specified profile includes setting the default profile as the specified profile for the access point.

100. In the computer system described in claim 98, the default profile is a public profile.

101. In the computer system according to claim 96, the step of identifying a specified profile includes generating a new profile for an access point based on one or more existing profiles for user accounts.

102. A computer system equipped with the following: Mobile user devices; Desktop user devices; at least one processor; and When executed by at least one processor, the memory contains instructions that cause at least one processor to perform the following actions: Presenting a mobile display on a mobile user device; Presenting a desktop view on a desktop user device, where the desktop view includes: Mobile area: An area with a layout and user interface controls that mimic mobile display; and Content area: An area separate from the mobile area, which can be displayed simultaneously with the mobile area, and which displays content related to the content displayed in the mobile area; and Expand the content area to include at least a portion of the mobile area, while hiding at least a portion of the mobile area.

103. In the computer system according to claim 98, the step of expanding the content area to include at least a portion of the mobile area while concealing at least a portion of the mobile area includes receiving user input to a user interface control on the desktop display, and in response to the user input, expanding the content area to include at least a portion of the mobile area while concealing at least a portion of the mobile area.

Images