EP4681407A2 - Services informatiques - Google Patents

Services informatiques

Info

Publication number
EP4681407A2
EP4681407A2 EP24771693.9A EP24771693A EP4681407A2 EP 4681407 A2 EP4681407 A2 EP 4681407A2 EP 24771693 A EP24771693 A EP 24771693A EP 4681407 A2 EP4681407 A2 EP 4681407A2
Authority
EP
European Patent Office
Prior art keywords
service
user
display
services
user interface
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP24771693.9A
Other languages
German (de)
English (en)
Inventor
Jackson L. Crisp
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Publication of EP4681407A2 publication Critical patent/EP4681407A2/fr
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/40—Business processes related to social networking or social networking services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/01—Customer relationship services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/018—Certifying business or products
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00—Business processing using cryptography

Definitions

  • the disclosure relates to computer services and user interface features.
  • a computer system can include a user account and a service data structure linked to the user account in the computer system.
  • the service data structure can include a plurality of structured categories arranged in a hierarchy having multiple levels, the structured categories including a first category at a first level and a second category in the first category, the second category being at a second level that is below the first level in the hierarchy.
  • the service data structure can also include a record in the second category.
  • the record can include an indication of at least one scannable code that is linked to the user account in the computer system, and an indication of a set of one or more computer- implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the set of one or more computer- implemented services may be performed and possibly otherwise managed via one or more corresponding service managers.
  • a technique can include presenting a representation of at least a portion of the service data structure, with the representation indicating a current location in the hierarchy of the service data structure.
  • the technique can also include, in response to receiving user input directed at the representation, navigating between levels in the service data structure. Additionally, the technique can include changing the representation to reflect the navigation between levels.
  • the representation may include displays, such as ones like the user interface displays discussed above or different user interface displays.
  • a technique can include receiving a user input request that requests a transfer of the record to a new hierarchical location in the computer system.
  • the technique can also include, in response to receiving the user input request, transferring the record and/or a category structure indicator for the record to a new hierarchical location in the computer system.
  • the category structure indicator can indicate a category structure including categories of the hierarchy that include the record.
  • the categories of the hierarchy that include the record can include the first category and the second category, and the record can retain a category structure indicated in the category structure indicator in the new hierarchical location in the computer system.
  • a technique can include managing a service data structure linked to a user account in the computer system.
  • the service data structure can include a record.
  • the record can include an indication of at least one scannable code that is linked to the user account in the computer system, and an indication of a set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can also include performing the one or more computer-implemented services in response to a user input into the computer system that uses the at least one scannable code.
  • the managing of the service data structure can include performing a first set of one or more actions in response to user input from at least one computerized human user interface device, and/or performing a second set of one or more actions in response to user input from at least one artificial intelligence bot running in the computer system.
  • a technique can include managing a service data structure linked to a user account in the computer system.
  • the service data structure can include a record that can include an indication of at least one scannable code that is linked to the user account in the computer system.
  • the record can also include an indication (such as in settings) of a set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can also include receiving user input that includes an input code into the computer system, the user input requesting a requested action using the input code and the service data structure.
  • the technique can further include, in response to receiving the user input into the computer system that uses the input code, performing a safety check on the input code.
  • the technique can include taking one or more available precautionary measures for the input code if the safety check on the input code results in a safety failure, or avoiding taking the one or more available precautionary measures for the input code if the safety check on the input code does not result in a safety failure (i.e., the safety check succeeds).
  • a technique can include managing a service data structure linked to a user account in the computer system.
  • the service data structure can include a record.
  • the record can include an indication of at least one scannable code that is linked to the user account in the computer system, and an indication of a set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can further include performing the one or more computer-implemented services in response to user input into the computer system that uses the at least one scannable code.
  • the technique can include receiving a request to create a second user account, and in response to receiving the request to create the second user account, creating the second user account.
  • the technique can further include linking the second user account to a tracking code, the tracking code indicating a referral source for the second user account.
  • the referral source can be either a product provider user account of a provider of a product linked to the request to create a second user account, or a referral user account linked to the request to create the second user account.
  • the technique can additionally include adding a credit to a record for the referral source for the creating of the second user account.
  • a technique can include managing a service data structure linked to a user account in the computer system, the service data structure including a record.
  • the record can include an indication of at least one scannable code that is linked to the user account in the computer system, and an indication of a set of one or more computer- implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can also include receiving user input into the computer system that uses the at least one scannable code.
  • the technique can include linking a quick link to the at least one scannable code and presenting the quick link on a user output device.
  • the technique can also include performing the one or more computer-implemented services that are linked to the at least one scannable code. Moreover, the technique can include recycling the quick link to make the quick link available for use in later computer system responses to receiving later user input into the computer system that uses scannable codes, the recycling including undoing the linking of the quick link from the at least one scannable code.
  • the quick link may then be used by the system in subsequent similar acts using that same at least one scannable code and/or other scannable codes with different linked services, and even other scannable codes that are linked to different user accounts than the at least one scannable code discussed earlier in this paragraph.
  • a technique can include presenting a user interface display that represents a current node in a hierarchical data structure as the user interface display moves between nodes in the hierarchical data structure, the hierarchical data structure including multiple service integrations and the user interface display including a context-sensitive user interface control that is displayed in the user interface display at two or more of the nodes, the two or more of the nodes being at multiple levels of the hierarchical data structure.
  • the two or more of the nodes can include: a contacts node in a contacts integration that includes contact nodes linked to profiles for accounts other than an active user account; and a portfolio node in a portfolio integration that is separate from the contacts integration, the portfolio node being a type of node other than a contacts node, the portfolio integration including nodes linked to portfolio integrations that are integrated into the hierarchical data structure to provide services for the active user account, the portfolio integrations including structures other than profiles for accounts.
  • the technique can further include iterating a state of the context-sensitive user interface control as the user interface display moves between nodes, the iterating configuring the context-sensitive user interface control to respond to selection of the context-sensitive user interface control by invoking a context-sensitive integration to perform a triggered process, the triggered process being tailored to the current node being represented in the user interface display as the user interface display moves between the two or more of the nodes, the process being different for each of the two or more of the nodes.
  • a technique can include presenting a user interface display including an outline.
  • the technique can also include partially collapsing a subject entry of a displayed outline in response to a system determination related to the outline, the partial collapsing can include configuring and presenting the outline with entries below the subject entry in a hierarchy of the outline including one or more hidden entries and one or more displayed entries.
  • a technique can include sharing multiple profiles linked to a sharing account with a different account in a profile sharing system.
  • the technique can also include merging profile data from the multiple shared profiles into a blended profile.
  • the technique can further include, in response to user input from the different account requesting display of profile information for the sharing account, displaying profile data from the blended profile.
  • a technique can include presenting a user interface display that represents a current node in a computerized hierarchical data structure as the user interface display moves between nodes in the hierarchical data structure.
  • the user interface display can present a category node user interface area representing a category node below the current node in the computerized hierarchical data structure.
  • the category node user interface area can include a drill down user interface control that is selectable to drill the user interface display down to the category node and display representations of one or more subcategory nodes below the category node; and an access point user interface control that is selectable to display an access display for accessing one or more records linked to the category node.
  • the technique can also include moving the user interface display to a new display in response to selection of the drill down user interface control and/or the access point user interface control.
  • a technique can include maintaining data indicating multiple different locations in a hierarchical data structure system where multiple information data items from an active user account structure for a user account are used.
  • the technique can also include presenting a profile monitoring user interface display for the active user account, the profile monitoring user interface display representing the multiple information data items, the profile monitoring user interface display including one or more indications for each data item of the multiple information data items, the one or more indications indicating one or more of the multiple different locations where the corresponding data item is used.
  • a technique can include maintaining a code record linked to a user account, the code record defining a predetermined code that includes a predefined pattern in one or more of a video pattern, an audio pattern, biometric pattern, and a frequency pattern, the code record further defining a service to be performed using an integration in response to scanning of the code by identifying the predefined pattern by the computer system; scanning input including one or more of video input, audio input, biometric input, and frequency input for the predetermined code; identifying the predetermined code; and in response to identifying the predetermined code, performing the service using the integration in the computer system.
  • a technique can include receiving a user input access point request from a user account for an access point to a service integration that is not fully setup; determining that an access point profile from the user account is to be used in setting up the access point; and in response to the determining that the access point profile from the user account is to be used in setting up the access point, identifying an identified profile for use by the service integration and setting the identified profile as the access point profile for the access point as part of setting up the access point.
  • the identified profile may be an existing profile identified or entered by user input and/or a system generated profile (such as where the system responds by choosing a default profile such as a public profile, or the system responds by generating a required profile for the access point).
  • a technique can be performed via a computer system with a mobile user device and a desktop user device (a device with a larger screen than a typical mobile device, such as a desktop computer, a laptop computer, a tablet computer, etc.).
  • the technique can include presenting a mobile display on the mobile user device and presenting a desktop display on the desktop user device.
  • the desktop display can include a mobile area with a layout and user interface controls that mimic the mobile display; and a content area that is separate from the mobile area, the content area being displayable at the same time as the mobile area and the content area displaying content related to indications displayed in the mobile area.
  • the technique can further include expanding the content area to include at least a portion of the mobile area while hiding the at least a portion of the mobile area.
  • the expanding the content area to include the at least a portion of the mobile area while hiding the at least a portion of the mobile area can include receiving user input directed to a user interface control on the desktop display and responding to the user input by expanding the content area to include the at least a portion of the mobile area while hiding the at least a portion of the mobile area.
  • FIG. 1 is a schematic diagram of a computer services system.
  • Fig. 2 is a schematic diagram of a service data structure.
  • FIG. 4 is an illustration of a user computing device presenting a display.
  • FIG. 5 is an illustration of a user computing device presenting another display.
  • FIG. 6 is an illustration of a user computing device presenting yet another display.
  • Fig. 7 is an illustration of a user computing device presenting yet another display.
  • FIG. 8 is an illustration of a user computing device presenting yet another display.
  • FIG. 10 is an illustration of a user computing device presenting yet another display.
  • FIG. 11 is an illustration of a user computing device presenting yet another display.
  • FIG. 15 is an illustration of a user computing device presenting yet another display.
  • FIG. 16 is an illustration of a user computing device presenting yet another display.
  • FIG. 17 is an illustration of a user computing device presenting yet another display.
  • Fig. 18 is an illustration of a user computing device presenting yet another display.
  • Fig. 19 is an illustration of a user computing device presenting yet another display.
  • Fig. 20 is an illustration of a user computing device presenting yet another display.
  • Fig. 21 is an illustration of a user computing device presenting yet another display.
  • Fig. 22 is an illustration of a user computing device presenting yet another display.
  • Fig. 23 is an illustration of a user computing device presenting yet another display.
  • Fig. 24 is an illustration of a user computing device presenting yet another display.
  • Fig. 25 is an illustration of a user computing device presenting yet another display.
  • Fig. 26 is an illustration of a user computing device presenting yet another display.
  • Fig. 27 is an illustration of a user computing device presenting yet another display.
  • Fig. 28 is an illustration of a user computing device presenting yet another display.
  • Fig. 29 is an illustration of a user computing device presenting yet another display.
  • Fig. 30 is an illustration of a user computing device presenting yet another display.
  • Fig. 31 is an illustration of a user computing device presenting yet another display.
  • Fig. 32 is an illustration of a user computing device presenting yet another display.
  • Fig. 33 is an illustration of a user computing device presenting yet another display.
  • Fig. 34 is an illustration of an example of an encoded thing.
  • Fig. 35 is an illustration of another example of an encoded thing.
  • Fig. 36 is a schematic diagram of example service integration types and service managers.
  • Fig. 37 is a schematic diagram of example service integration types.
  • Fig. 38 is an illustration of a user computing device presenting a display.
  • Fig. 39 is an illustration of a user computing device presenting another display.
  • Fig. 40 is an illustration of a user computing device presenting yet another display.
  • Fig. 41 is an illustration of a user computing device presenting yet another display.
  • Fig. 42 is an illustration of a user computing device presenting yet another display.
  • Fig. 43 is an illustration of a user computing device presenting yet another display.
  • Fig. 44 is an illustration of a user computing device presenting yet another display.
  • Fig. 45 is an illustration of a user computing device presenting yet another display.
  • Fig. 46 is an illustration of a user computing device presenting yet another display.
  • Fig. 47 is an illustration of a user computing device presenting yet another display.
  • Fig. 48 is an illustration of a user computing device presenting yet another display.
  • Fig. 49 is an illustration of a user computing device presenting yet another display.
  • Fig. 50 is an illustration of a user computing device presenting yet another display.
  • Fig. 51 is an illustration of a user computing device presenting yet another display.
  • Fig. 52 is an illustration of a user computing device presenting yet another display.
  • Fig. 53 is an illustration of a user computing device presenting yet another display.
  • Fig. 54 is an illustration of a user computing device presenting yet another display.
  • Fig. 55 is a schematic illustration of a system including a mobile user device, a desktop user device, and a service subsystem.
  • Fig. 56 is a schematic illustration regarding blended profiles.
  • Fig. 57 is an illustration of a user computing device presenting yet another display.
  • Fig. 58 is an illustration of a user computing device presenting yet another display.
  • Fig. 59 is an illustration of a user computing device presenting yet another display.
  • Fig. 60 is a schematic illustration that includes user computing device display layout presentations.
  • Fig. 61 is a flowchart illustrating at least part of a computer service technique.
  • Fig. 62 is a flowchart illustrating at least part of another computer service technique.
  • Fig. 63 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 64 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 65 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 66 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 67 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 68 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 69 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 70 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 71 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 72 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 73 is a flowchart illustrating at least part of yet another computer service technique.
  • Fig. 74 is a flowchart illustrating at least part of yet another computer service technique.
  • aspects described herein are directed to techniques and tools related to computer services. Improvements may result from the use of various techniques and tools separately or in combination. With the explosion of data in computer systems, including acceleration of that explosion from artificial intelligence generated content, computer systems to provide computer services in an organized and useful manner can assist user experiences and effectiveness as well as efficiency of computer systems. At least some tools and techniques discussed herein may provide advanced structured management of encoded and/or standard things.
  • the tools and techniques discussed herein may include tools and techniques for a computer services system.
  • the computer services system can manage records for user accounts.
  • a record can be a service code record which may or may not include an indication of a scannable code that is linked to a user account in the computer system, such as with the record being linked to the user account and to the scannable code.
  • a record such as a service code record can also include a set of one or more computer-implemented services to be performed via the computer system in response to user input using the scannable code(although services may be performed with artificial intelligence and/or human assistance).
  • the computer services system can manage a service data structure for each of multiple user accounts, with each service data structure being linked to a corresponding user account in the computer system.
  • Multiple service data structures each linked to a different user account, can be maintained within a larger data structure, and the different service data structures may be integrated with each other in any of various ways in the larger data structure.
  • multiple service data structures may be linked to a single user account, such as where each such service data structure is linked to a different organization indicator for the user account, and the user account can switch between managing different service data structures for different organizations.
  • an organization indicator or organization designation can be an indicator or designation that allows a user account to be organized into separate record structures, which are categories that include records.
  • a user account may be separated with indications or designations for different jobs that a human user has, different businesses that a human user is managing, different sub- business organizations for a business organization that is using an account (e.g., different divisions, departments or subsidiaries of a company), different hobbies or interests that a human user has, different third-party providers of encoded things and/or services, and/or other ways that the data structures for categories and/or records linked to a user account can be divided or separated.
  • the organizations may be set up and/or modified in response to input from one or more sources, such as user input from an active user account that is linked to the organization in the data structures and/or input from the service subsystem and/or developers/managers of the service subsystem.
  • tools and techniques that can be applied to categories as discussed herein may also be applied to organizations, which may optionally be considered and treated as higher- level categories, above and including the categories discussed herein (such as with categories and records being within organizations, or descendants of the organizations).
  • a service code database could include a database unit (such as a database table, multiple database tables, or a set of database records within a database table) for each of the service data structures.
  • each service data structure may be separate from other service data structures, or service data structures may be integrated with each other in different ways, so long as the structure provides for links between elements in each service data structure, such as to indicate the categories to which other categories and records belong, as discussed herein.
  • Such linking can be implemented in various ways, such as different ways of locating data in computer storage and/or including references between different units of data (e.g., references between different data units in one or more databases or other types of data structures).
  • the computer services system can facilitate the management (such as activation, creation of, setting up, revising, and use) of the records.
  • Use of the records can include providing computer-implemented services that are indicated in a record in response to a computer device scanning the code that is indicated in the record or entering such a code in some other way to indicate the desired record (e.g., as a textual identifier).
  • Services as discussed herein can be any services that are provided with the use of computer systems. Services may involve artificial intelligence bot actions and may include some non-computerized actions, such as where a service includes a human user providing part of the service such as where the human user provides user input as part of the providing of the service.
  • system services can include record services and/or shared services. Record services are services that are provided via the system to user accounts related to the records for which such user accounts have administrator rights and/or duties. Thus, record services can provide enhanced system services for the records and/or categories for such user accounts.
  • shared services can be the services that are provided in response to scanning of a scannable code that has been shared.
  • the system can provide a service wherein a user account can prompt the system to perform a bulk data upload and/or download (which could include uploading and/or downloading records, categories, links, user account data, organization data, and/or other data that is linked to a user account in the computer system).
  • This bulk upload and/or download could be performed via account services or using extended records services.
  • a system service which may include a shared service and/or a record service, can be any one of many services, such as any services selected from the following group of services (or combinations thereof), which can be provided by integrations (including option types of integrations and non-option types of integrations) as appropriate: anthropology service; (ad) copy service; 3D printing service; accounting service; activity(s) service; actuarial science service; ad placement service; administrative service; adult service; advertising service; aerospace service; agent service; agricultural service; agriculture service; alternative medicine service; animal service; animal service; animal welfare service; animal wellness service; anti-counterfeit service; appointment service; archaeology service; architecture service; artist service; assistant service; astrophysics/astronomy service; audio service; automotive service; autonomous device(s) service; autonomous equipment service; autonomous
  • sharing services ride, housing, files, etc.
  • scanned (QR) code entry physical, digital, virtual... access
  • third party services products, systems, networks, applications, content, etc.
  • physical (security) access services doors, elevators, events, rooms, areas, locations, buildings, facilities, gates, vending machines, vehicles, equipment, appliances, utility systems, physical systems, etc.
  • digital (security) access services systems, system-services, data, information, applications, networks, wi-fi networks, frequency networks, transmission networks
  • Al generation services data, information, content, media, profiles, fabrication, websites, apps, builds, business, computing, games, currency, for-pay services, literature, contracts, agreements, financial automation, automated trading, any applicable Al capable generation service, etc.
  • games and game services products, pay-to- eam, web 2.0, web 3.0, crypto, real world integrated, gambling, standard, current, yet developed, etc.
  • financial services banking, credit, loans, trading, automated trading, currency transfers,
  • productivity services personal, business, etc.
  • productivity (software/SaaS) app services business, personal, marketing, ads, sales, project management, resource management, product management, appointment calendars, email, shared email inbox, communications, CRM, support, accounting, forms, documents, storage, customer engagement, signature, mapping, process, system, affiliate, phone/voice, social media, email/SMS campaign, marketing campaign, survey, website, analytics, event management, webinar, ecommerce, marketing automation, business/web funnel, inventory, payment processing, meeting, client, customer, files, data, specifications, procedures, fulfillment, community, group, employee, contractor, recruitment, scheduling, support tickets, coaching, training, bug tracking, developer, business networking, message boards, etc.); telephony services (phone, IVR, call attendants, messaging, auto-responders, call center, etc.); servicecenter services (booking, reservation, virtual business address
  • references herein to services or types of services herein include references to the foregoing services, as applicable in the context of the reference to one or more of the services herein.
  • the user accounts managed by the computer services system can be a mixture of accounts for human users (e.g., with each account being for a single user, a group of users, or an organization such as a company, a group of companies or some portion of a company) and accounts for artificial intelligence bots.
  • the artificial intelligence bots can be configured to analyze output from the system that would normally be provided to human users, to analyze such output, and to provide responsive user input back to the system.
  • the bots themselves can be running within the system, so that such user input is provided from part of the system in which the bots are running to another part of the system.
  • Such providing of input from such artificial intelligence bots that are designed to provide input that is like input from human users is considered herein to be user input.
  • an artificial intelligence bot may provide more repeatable and reliable analysis and input in some situations, especially where similar service and code related tasks are performed repeatedly in the system.
  • a user account is a set of data that represents an entity such as a human user, an artificial intelligence bot user, a group of human users, a computing resource, etc. If references are made herein to a user account performing actions (sending, receiving, etc.), those actions are considered to be performed by a user account if they are performed by computer components in an environment where the user account is active (such as where the user account is logged into an environment and that environment controls the performance of the actions). Often such actions by or for a user account are also performed by or for a human user or artificial intelligence bot user corresponding to the user account.
  • this may be the case where a user account is logged in and active in a computer application and/or a computing device that is performing actions for the user account on behalf of a corresponding human user or artificial intelligence bot user.
  • this usage of terminology related to user accounts applies with references to a user account providing user input, receiving responses, or otherwise interacting with computer components discussed herein.
  • Structured service(s) with related service record(s) can drill down to be as niche specific as feasible/desired; and/or can be specific to an organization or any part of the organization as feasible/desired, making available any number/type/variation of system service(s) and integrated system service(s) as feasible/desired.
  • the structured service(s) can be broad (public) to niche (account), and/or specific (private).
  • Techniques described herein may be used 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 with hardware or software, or a combination of both.
  • the processor, memory, storage, output device(s), input device(s), and/or communication connections discussed below with reference to Fig. 3 can each be at least a portion of one or more hardware components.
  • Dedicated hardware logic components can be constructed to implement at least a portion of one or more of the techniques described herein.
  • such hardware logic components may include Field- programmable Gate Arrays (FPGAs), Program- specific Integrated Circuits (ASICs), Program- specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
  • FPGAs Field- programmable Gate Arrays
  • ASICs Program- specific Integrated Circuits
  • ASSPs Program- specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • Techniques may be implemented using two or more specific interconnected hardware modules or devices with related control and data signals that can be communicated between and through the modules, or as portions of an application- specific integrated circuit. Additionally, the techniques described herein may be implemented by software programs executable by a computer system. As an example, implementations can include distributed processing, component/object distributed processing, and parallel processing. Moreover, virtual computer system processing can be constructed to implement one or more of the techniques or functionalities, as described herein.
  • Communications between the various devices and components discussed herein can be sent using computer system hardware, such as hardware within a single computing device, hardware in multiple computing devices, and/or computer network hardware.
  • a communication or data item may be considered to be sent to a destination by a component if that component passes the communication or data item to the system in a manner that directs the system to route the item or communication to the destination, such as by including an appropriate identifier or address associated with the destination.
  • a data item may be sent in multiple ways, such as by directly sending the item or by sending a notification that includes an address or pointer for use by the receiver to access the data item.
  • multiple requests may be sent by sending a single request that requests performance of multiple tasks.
  • the system 100 may be an interactive linked contacts, calendar, profile, groups, services, etc. live information management, services, sharing, and collaboration platform.
  • Each of the components includes hardware and may also include software.
  • a component of Fig. 1 can be implemented entirely in computer hardware, such as in a system on a chip configuration.
  • a component can be implemented in computer hardware that is configured according to computer software and running the computer software.
  • the components can be distributed across computing machines or grouped into a single computing machine in various ways. For example, a single component may be distributed across multiple different computing machines (e.g., with some of the operations of the component being performed on one or more client computing devices and other operations of the component being performed on one or more machines of a server).
  • the computer services system 100 can include an encoded thing 110.
  • the encoded thing 110 can include a contact element, which can be a scannable code such as a trigger code to trigger system performance of system services, such as a code 112 that includes a visual pattern and/or a transmittable code 114 stored in a device.
  • a contact element which can be a scannable code such as a trigger code to trigger system performance of system services, such as a code 112 that includes a visual pattern and/or a transmittable code 114 stored in a device.
  • the code 112 that includes a visual pattern could be a one-dimensional bar code, a two- dimensional bar code such as a QR code, or some other visual pattern, such as a pattern encoding a trigger uniform resource locator.
  • a device storing a transmittable code 114 could be a device that can provide the code in a transmittable form, such as a code that can be transmitted in a wireless signal, such as a frequency signal and/or a digital signal.
  • the device storing the transmittable code 114 may be an RFID tag, or a near field communications device.
  • a contact element may be a textual identifier that can be manually input into a computing device, such as a uniform resource locator (e.g., a website address).
  • the encoded thing 110 can be any physical thing that can include a scannable code, such as an item that can display a visual code or house a transmittable code.
  • the encoded thing 110 can be a sign (as illustrated in Fig.
  • an encoded thing 110 can be a computing device, such as a user device 120.
  • a user device 120 can have a visual code printed on a housing of the device.
  • a user device 120 can display a visual code on a device display screen.
  • a user device 120 may include a transmittable code, which the user device 120 can send through a wired or wireless connection, such as sending a code to another user device 120 using a protocol such as a near field communications protocol.
  • Encoded things 110 can be mass produced or custom produced. And the encoded things can be provided to end users with codes already included in the encoded things 110. Additionally, the codes for multiple encoded things 110 can be serialized, and such serialized codes can be used for tracking providers of the encoded things 110, such as for purposes of providing credits to such providers via their user accounts.
  • encoded things can be digital things, such as digital files, virtual goods that are encoded and usable in virtual reality and/or augmented reality computing environments, or they may be combinations of different physical and/or digital things. While encoded things are discussed here, the computer services system 100 can manage both encoded things and non-encoded things, such as by including references to the encoded and/or non-encoded things in linked records, as discussed herein.
  • the user devices 120 can include any of various computing devices that can be handled by users, such as mobile devices 122 (e.g., smartphones or tablet computers).
  • a mobile device 122 can run dedicated software applications (apps), such as a services app 124, which can be a dedicated app that is designed to work with a subsystem for providing computer services.
  • the mobile device 122 can also run a third-party app 126, which may be an app that is mainly directed to providing services other than the computer services of a dedicated service subsystem such as a service code subsystem, but the third-party app 126 may provide data to and receive data from such a dedicated service subsystem.
  • the third-party app 126 may be a camera app, a near field communications app, or some other app such as a shopping app that includes programming for scanning codes.
  • the user devices 120 may also include a desktop computer 130, which may be a desktop terminal.
  • the desktop computer 130 can run software applications, such as a general web browser 134, which can be used to browse webpages.
  • the desktop computer 130 may also run specific dedicated applications, such as a services application and other third- party applications. One or more of such applications may be used in code linked computer services and other computer services as discussed herein.
  • Human users 132 may use the user devices 120 (providing user input to the user devices 120 and/or receiving presented output from the user devices 120), but the human users are not considered to be part of the computer services system 100. Indeed, human users 132 may be scanned in biometric scanning operations, but the human users are still not considered to be part of the computer services system 100. Instead, the computer services system 100 can operate for or on human users
  • the user devices 120 can communicate with other computer devices in the computer services system 100 via a network, which can be a wired and/or wireless network. Indeed, such a network may involve two computing devices communicating directly with each other (such as in a peer-to-peer connection), such as using the Bluetooth protocol, near field communications, wired communications, or some other type of communications. Devices may also communicate with each other via network 140 in client-server arrangements.
  • a network which can be a wired and/or wireless network.
  • a network may involve two computing devices communicating directly with each other (such as in a peer-to-peer connection), such as using the Bluetooth protocol, near field communications, wired communications, or some other type of communications.
  • Devices may also communicate with each other via network 140 in client-server arrangements.
  • a service subsystem 150 can be a computer subsystem that can communicate with the user devices 120 via network 140.
  • the service subsystem 150 can operate as a cloud-based server system, which can interact with user devices 120, such as via a services app 124 such as a code services app, a third-party app 126, and/or a browser 134.
  • the service subsystem 150 can include an account manager 160, which can manage an account store 162, which can be a data store that can store user accounts 164.
  • the user accounts can include profiles 165 for the user accounts 164.
  • the account manager 160 may interact with other subsystems besides the service subsystem 150 and may interact with other managing components.
  • the service subsystem 150 can also include a service code data manager 170, which can manage a service code data store 172, which can store service data structures 174 that can be linked to the user accounts 164.
  • a user account 164 may list an identifier for each of one or more service data structures 174 that are linked to the user account 164 and/or a service data structure 174 can list one or more identifiers for each of one or more user accounts 164 linked to the service data structure 174.
  • the service subsystem 150 can also include user interface managers that can interface with other components that interface with users. Each of the user interface managers may interact with the account manager 160 and/or the service code data manager 170, and each may also interact with users or with other components that interact with users.
  • a services app manager 180 such as a code services app manager can interact with user devices 120 using the dedicated services app 124 running on the user devices.
  • the services app manager 180 and the services app 124 can store data and computer-readable instructions for user interface presentations and functionality for computer services as discussed herein.
  • the user interface managers can also include a services web manager 182, which can interact with user devices 120 running a browser 134.
  • the services web manager 182 can store and provide user interface data (webpages, webpage templates, etc.) and backend functionality for webpages for computer services as discussed herein.
  • the user interface managers may also include one or more additional app and web managers 184, which may or may not be managers dedicated to computer services.
  • the user interface managers may also include an artificial intelligence bot manager 186.
  • the artificial intelligence bot manager 186 can run and/or interact with artificial intelligence bots 190, which can run to perform acts that would otherwise be performed by human users and user devices 120 for the computer services system 100.
  • the bots 190 can run on a bot platform 192, which can provide functionality for the bots, but can allow individual bots 190 to be customized for individual use scenarios.
  • the service data structure 174 can include a plurality of levels into which records and record categories (such as portfolios typically for organizing non-profile or non-contact records and categories, and contact groups for organizing profiles or contacts as discussed below) can be included in the data structure. For example, at a top level, level 1 210, a top category 1A 212 can be included. All the other categories and records can be below that top level category 1A 212. However, a data structure may include more than one top level category, and the top level may include records in addition to including a category. Each category can include a descriptive title of the category that applies to child categories and records in that category. That title may be displayed on a user display when a user input device is displaying navigation and record wallet display screens for the service data structure 174.
  • records and record categories such as portfolios typically for organizing non-profile or non-contact records and categories, and contact groups for organizing profiles or contacts as discussed below
  • the example service data structure 174 can also include a level 2220 that is below the level 1 210.
  • Level 2 220 can include one or more service code categories and/or one or more records.
  • level 2220 includes multiple categories that are all within category 1A 212: category 2A 222, category 2B 224, to category 2N 226 (where “N” represents the number of categories in level 2220).
  • category 1A 212 can be considered a “parent” category of the categories in level 2 220, and the categories in level 2 220 can be considered “children” of category 1A 212.
  • the children of the children in a category can also be considered to be in that category, and to be descendants of that category.
  • parents of parents of a category or record can be considered to be ancestors of that category or record.
  • Level 3 230 which is below level 2 220, can include additional categories: category 3A 232 and category 3B 234 that are subcategories in category 2A 222; category 3C 236 in category 2B 224, to category 3N 238 in category 2N 226.
  • level 4240 which is below level 3 230, can include additional categories and records: category 4A 242 in category 3A 232, category 4B 244 in category 3B 234, available record 4A 246 in category 3C 236, to category 4N 248 in category 3N 238.
  • An available record, such as available record 4A 246, can be a record that is available to be linked to the user account to which the current service data structure 174 is linked.
  • the available record may be selected by user input from the linked account for adding to the account’s linked records. This may or may not require a transmission of some value in return for the linking of the record (such as a monetary payment).
  • a linked record can be a record that is already linked to the user account so that functionality of the record (e.g., setting up the record and providing services in response to receiving the code indicated in the record) is available to the user account.
  • a level 5 250 which is below level 4 240, can include a linked record 5A 252, a linked record 5B 254, and an available record 5A 256 in category 4A 242.
  • Level 5 250 can also include a category 5A 258 as a subcategory in category 4B, to a linked service record 5N 264 and an available service record 5N 266 in category 4N 248.
  • the service data structure 174 may continue with additional records and categories in additional levels below level 5 250.
  • the service data structure 174 can include links between a category and the categories and records in that category. Such links may be implemented in different ways. For example, each category may include references to identifiers for all of its direct children and parent categories, and to all of its direct children categories. Each record can include a reference to its direct parent categories. In some implementations, each category and each record may include references to all of its direct and indirect ancestor categories and to all of its direct and indirect descendent categories and records.
  • a record level category may be a “For Sale Signs” category, or the record level category may simply be “Signs.”
  • access to designated service categories, records, and/or record services may be free and/or require payment. For example, access to some service categories may be free, while access to other service categories may be limited to user accounts that are designated as having access to such categories (such as where an indicator in the system indicates the user account has access to that category).
  • referral credit may be applied to user accounts that provided an encoded thing that prompted the payment for the access, a user account that shared an item that resulted in the payment for the access, and/or a user account transferred a record that resulted in the payment for the access.
  • actions that may be performed by the computer services system manage payment transactions, produce trigger uniform resource locators to be encoded in scannable codes, produce scannable codes, produce webpages and websites, produce records and categories and include them in data structures, set default services for records in categories, link records to user accounts, send specifications for encoded things to manufacturers or printers for production, and process orders for encoded things.
  • Users may perform actions such as receiving and using authenticated and activated encoded things, providing user input to instruct the system in managing records via user accounts, and providing user input to instruct the system in managing service pages (such as webpages) via user accounts.
  • recyclable quick links may be used. These quick links can be made available and used when a scannable code is presented. When the scannable code is no longer being used in the system, the quick link can be included in a storage for access and use with other scannable codes later. This can allow for short web addresses that a user could quickly enter into a browser instead of relying on an automated use of a uniform resource locator from a scanning operation. For such quick links, advertising or posting of the quick links could be avoided due to the short-term dynamic nature of the quick links.
  • recycled codes can be produced by the computer system for in-the-moment shares. Such recycled codes can be presented where the dynamically linked scanned code data changes in the background. The recycled code can also be linked to a quick link.
  • FIG. 3 illustrates a generalized example of a suitable computing environment 300 in which one or more of the described aspects may be implemented.
  • one or more such computing environments can be used as a device in a service subsystem, a third- party subsystem, a user device, or some other device in a computer services system.
  • computing system configurations can be used.
  • 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, smart phones, laptop devices, slate devices, game consoles, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
  • the computing environment 300 is not intended to suggest any limitation as to scope of use or functionality of the invention, as the present invention may be implemented in diverse types of computing environments.
  • the computing environment 300 includes at least one processing unit or processor 310 and memory 320. In Fig. 3, this most basic configuration 330 is included within a dashed line.
  • the processing unit 310 executes computer-executable instructions and may be a real or a virtual processor. In a multi-processing 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 some combination of the two.
  • the memory 320 stores software 380 implementing computer services. An implementation of computer services may involve all or part of the activities of the processor 310 and memory 320 being embodied in hardware logic as an alternative to or in addition to the software 380.
  • FIG. 3 Although the various blocks of Fig. 3 are shown with lines for the sake of clarity, in reality, delineating various components is not so clear and, metaphorically, the lines of Fig. 3 and the other figures discussed herein would more accurately be grey and blurred.
  • a presentation component such as a display device to be an VO component (e.g., if the display device includes a touch screen).
  • processors have memory. The inventors hereof recognize that such is the nature of the art and reiterate that the diagram of Fig. 3 is merely illustrative of an example computing device that can be used in connection with one or more aspects of the technology discussed herein. Distinction is not made between such categories as “workstation,” “server,” “laptop,” “handheld device,” etc., as all are contemplated within the scope of Fig. 3 and reference to “computer,” “computing environment,” or “computing device.”
  • a computing environment 300 may have additional features.
  • 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 interconnects the components of the computing environment 300.
  • operating system software typically, operating system software
  • the memory 320 can include storage 340 (though they are depicted separately in Fig. 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, DVDs, which can be used to store information and which can be accessed within the computing environment 300.
  • the storage 340 stores instructions for the software 380.
  • the input device(s) 350 may be one or more of various different input devices.
  • the input device(s) 350 may include a user device such as a mouse, keyboard, trackball, augmented reality interface device, etc.
  • the input device(s) 350 may implement one or more natural user interface techniques, such as speech recognition, touch and stylus recognition, recognition of gestures in contact with the input device(s) 350 and adjacent to the input device(s) 350, recognition of air gestures, head and eye tracking, voice and speech recognition, sensing user brain activity (e.g., using EEG and related methods), and machine intelligence (e.g., using machine intelligence to understand user intentions and goals).
  • natural user interface techniques such as speech recognition, touch and stylus recognition, recognition of gestures in contact with the input device(s) 350 and adjacent to the input device(s) 350, recognition of air gestures, head and eye tracking, voice and speech recognition, sensing user brain activity (e.g., using EEG and related methods), and machine intelligence (e.g., using machine intelligence to understand user intentions and goals
  • the input device(s) 350 may include a scanning device; a network adapter; a CD/DVD reader; thumb drive or other type of removable storage or memory; or another device that provides input to the computing environment 300.
  • the output device(s) 360 may be a display, printer, 3d printer, speaker, CD/DVD-writer, network adapter, computer- controlled mechanical equipment, appliance, door or other barrier, a vehicle, an augmented or virtual reality output device such as goggles, or another device that provides output from the computing environment 300. Examples of output from the output device(s) 360 may include physical action triggers, alerts, instructions (e.g., mail/shipping fulfilment instructions; drone drop off instruction; car service pickup/drop-off instruction), and/or a computer initiated physical tasks.
  • the input device(s) 350 and output device(s) 360 may be incorporated in a single system or device, such as a touch screen or a virtual reality system.
  • the communication connection(s) 370 enables communication over a communication medium to another computing entity. Additionally, functionality of the components of the computing environment 300 may be implemented in a single computing machine or in multiple computing machines that are able to communicate over communication connections. Thus, the computing environment 300 may operate in a networked environment using logical connections to one or more remote computing devices, such as a handheld computing device, a personal computer, a server, a router, a network PC, a peer device, or another common network node.
  • the communication medium conveys information such as data or computer-executable instructions or requests in a modulated data signal.
  • a modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • communication media include wired or wireless techniques implemented with an electrical, optical, RF, infrared, acoustic, or other carrier.
  • Computer-readable media are any available storage media that can be accessed within a computing environment, but the term computer-readable storage media does not refer to propagated signals per se.
  • Computer-readable storage media include memory 320, storage 340, and combinations of the above.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various aspects.
  • Computer-executable instructions for program modules may be executed within a local or distributed computing environment. In a distributed computing environment, program modules may be located in both local and remote computer storage media.
  • Records such as the available and linked records discussed herein, can be included in a service data structure for an account.
  • the service data structure can include a hierarchy of record categories and sub-categories and records in those categories.
  • This structure can be used to provide a structured hierarchical navigation of categories and records such as code records using a user interface of a user device.
  • This hierarchical structure of the service record categories and records can provide an efficient underlying structure for the system to provide user interface navigation through the organized categories and records.
  • Such efficient and organized navigation features can also reduce the computing resources (memory, network bandwidth, etc.) that would be utilized in locating desired records and categories in the computer services system.
  • the screens can include a record wallet display and a navigation display, both of which can be adjusted as user input is provided to move the user interface display between different locations or nodes (categories or records) of the hierarchy.
  • the record wallet display can include user interface controls representing records in the current node of the hierarchy.
  • the record wallet display can also include a user interface control that can be selected to switch from the record wallet display to the navigation display, while staying at the same current node of the hierarchy.
  • the navigation display can include user interface controls for navigating to the record wallet display for the current node and for navigating to each node for 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 the user account, an action item control that can be selected to reveal action items that are waiting for user input, and a captured data control that can be selected to reveal code-linked services data that has been captured for the user account by the system.
  • the record wallet display and the navigation display can each include one or more user interface controls that are included in both displays, such as a live user interface control that can be selected to reveal a display for scanning a code and/or sharing the app with other devices.
  • a record can include a service code, a service record, or a combination thereof.
  • the live user interface can also interact with a device’s global positioning system to locate nearby services, activities, products, geofenced users and/or items, other app users, and/or other proximity items.
  • the proximity item feature and related data and services can be integrated with third party systems and/or provided directly to and/or from the system via an owner account as made available by the system.
  • the live user interface can provide live feed services, such as services provided in real time.
  • the paired hierarchical record wallet and navigation pages can provide a more efficient navigation to desired user interface controls and displays regarding the service code categories and records in the hierarchy linked to the user account. Specifically, it can allow navigation with fewer user input requests and fewer additional screen displays, and therefore less human user time and effort, and less computer system time and resources being used for managing the service code categories and records in the hierarchy.
  • the user interface can keep navigation features and functions familiarly located, which can help to facilitate ease of use by users of different technical capabilities, which can improve the computer system and may invite a wider demographic to have easy access to tools and techniques discussed herein.
  • User input can be provided to request transferring a record either to a different location linked to the same user account (such as to a different organization designation and possibly a different service data structure for the same user account), or to a different user account.
  • This can result in the transferred record being transferred with indications of its ancestor categories, so that the record can be included in the new service data structure with those same ancestor categories after being transferred.
  • Transferring may be done in different ways in different implementations, such as by changing links such as references, and/or by moving data from one storage location to another.
  • Scannable codes can be transferred between records. For example, a code that is linked to a first record can be unlinked from that first record and linked to a different second record. Such transferring of scannable codes between records can be done in response to user input from an account that is linked as an owner of the record from which the scannable code is being transferred. All or part of the data that has been captured and is linked to the sending record (the record from which the code is being transferred) may also be transferred to the receiving record (the record to which the code is being transferred), which can include linking the captured data to the receiving record. A new code may be acquired for the sending record, such as by generating a new code and/or transferring the code from another third record.
  • user input may instruct that the sending record is to be deleted after the transferred code is successfully transferred to the receiving record.
  • the sending record and the receiving record may be in the same or different category, organization. Also, the sending record and the receiving record may be linked to the same user account owner or to different user account owners.
  • the transferability of records related to physical encoded things can allow for custodial exchanges of these encoded things between accounts, thereby allowing the user or group currently controlling the encoded thing to transfer the encoded thing to a different user.
  • Records and categories can be customized using current conditions.
  • current conditions are conditions that may change over time so that different tools and techniques may be appropriate as the conditions change. For example, such changes may include making different records available, making different services available for particular records, and making different service code categories available.
  • Some examples of such conditions may be the data in an account such as the preferences, age, and/or gender of a represented human user, current date and time, the location of the user device, the current or forecast weather in the current location, events occurring at or near the current location, current speed of the user device requesting a service, and preferences indicated in the system for a user account that is requesting the services.
  • Structured category and related record conditions could also consider user account ranking, where such account ranking could be based on one or more factors such as activity level of the user account and/or amount paid by/for the user account. Such conditions and others may be input alone or in combination with others to yield rule-based real-time adaptation based on the conditions.
  • the computer services system may store rules that dictate what the conditions are and how/when they affect operation of the system, such as what services, service records, and/or categories are provided, and possibly how specified services are provided.
  • Conditions for a category and related service(s) (such as various apps, games, stores, software services, customer services, etc.) can be set by an applicable administrator (such as a system administrator, account manager, account representative, etc.) at any applicable level of the service data structure.
  • an administrator can be a person and/or a bot.
  • conditions based on account status and available information, such as verified or unverified account status; number and type of things or assets and/or associations to other accounts or types of accounts; types of categories, records, and services (such as apps including games, productivity apps, etc.); business, service, product, content, post, article, event, subscription, network, charity, group, and/or other affiliations; public/private information/records (arrest, awards, associations, health, wellness, associations, demographics, abilities, physical characteristics, wealth, clubs, job title, roles, business roles/affiliations, etc.); political/religious preference; travel/resident history; contact connections; service providers; causes of interest, charities, events, literature, television, movies, hobbies, interests, etc.; and/or any other available (legally /agreeably) obtained owner related information/associations, can also be utilized as conditions.
  • Customizations based on conditions can provide a more efficient, useful, and even safe computer services system. For example, a customization may avoid providing a service that would be unsafe or undesirable in a particular situation. For example, some services that could be dangerous in severe weather may not be offered if a computerized source of weather information indicates current severe weather in the current location. As another example, a service that is illegal in a particular location may not be provided if it is determined that the user device is currently in that location. As another example, a service may not be offered if it would likely not be deemed useful for the current conditions.
  • Credit can be provided to user accounts for referring a new user account to the computer services system.
  • a referral may be in the form of a user account providing a referral code to refer another user to the computer services system.
  • the referring user account may include a referral code, such as a QR code, for that user account. If another user device scans that QR code, the scanning user’s device can decode a uniform resource locator that can trigger the device to start a process for onboarding the scanning user by setting up a new account.
  • the scanning user’s device can also receive a referral code or identifier that is linked in the computer services system to the referring user account, or such a referral code or identifier can otherwise be provided to the service subsystem and can be linked to the new account of the scanning user.
  • the referral code or identifier for the referring user account may be provided directly at the time of scanning, or it may be stored in the scanning user’s device (e.g., as a cookie) until the scanning user performs an action (such as setting up a new account or ordering a paid service from the computer services system).
  • the service subsystem 150 can store an indication of credit for the referral in the service subsystem, such as in the referring user’ s account, or in a location linked to the referring user’ s account.
  • the credit could be a credit that allows the referring user to receive a benefit, such as being provided with additional services or features by the computer services system or even having money sent digitally or physically to the user represented by the referring user account.
  • scanning a referral code can prompt the system to initiate a system sharing service that initiates the setup of a new user account on the scanning device, and then applies credit to the user account whose code was shared.
  • a service such as an information sharing service (e.g., a contact information swap, an event invite, an eBook transfer, etc.) or some other service.
  • Referral tracking may be based on augmented and/or virtual reality introductions.
  • traditional transmission, sharing, and/or sending of a referral link could also be tracked.
  • a link could be shared via one or more of the share options available on mobile devices, such as email, SMS, or other messaging services.
  • a referral link related code (such as a QR code) could be integrated into a sent encoded thing for scanning by a receiving party.
  • the system response to the referral code could also set a predetermined (e.g., prebuilt) category into the scanning and/or receiving party app, which can optionally be applied instantly (possibly with an install conformation notice that asks for acceptance) if an app is already on a receiving party’s mobile device. Otherwise, if the app were not installed, the option to accept a category template could be incorporated during the new account setup (possibly with a confirmation notice), or via a pending notification to do so. Also, the receiving party app could receive user input from the receiving party to indicate that the receiving user account will complete setup of the new account later, which could prompt the system to remind the user in some manner about the pending account setup (such as by sending one or more reminder messages using contact information provided by the receiving user).
  • a predetermined category e.g., prebuilt category into the scanning and/or receiving party app, which can optionally be applied instantly (possibly with an install conformation notice that asks for acceptance) if an app is already on a receiving party’s mobile device. Otherwise
  • Integrations can be prebuilt by account owners, account administrators, system administrators, and/or app administrators, and provided for transfer for free (possibly with any related services cost) or can be purchased for transfer (again possibly with any related service costs).
  • the prebuilt categories also referred to herein as integrations, can be made available in various ways such as via account private, group (organizations, networks, etc.), and/or public portfolios and/or portfolio related marketplaces.
  • the integrations can also be automatically made available, such as for optional installation based on account (e.g., user) conditions and/or in general.
  • integrations can be shared via scans. In this scenario receipt of an integration could be made known via the notification indication, where a user could review to learn more about it and decide afterward whether to accept.
  • the integrations can be built in response to user input via user accounts and/or generated by the system, and integrations can optionally be shared to other user accounts as related to a sent action and/or share notification.
  • Similar credit may also be provided to providers of encoded things that are used to set up a new account or request some specified type of service (such as a paid service) from the computer services system.
  • an encoded thing may be purchased or given away to a customer by a retailer, who received the encoded thing from a distributor, who received the encoded thing from a manufacturer.
  • the codes (such as the visual pattern codes 112 or the transmittable codes 114 in devices) on the encoded things can be initially recorded in a database and linked to the providers of the corresponding encoded things (the manufacturer, distributor, retailer, etc.).
  • the codes may be serialized and the codes in a particular series may have come from a particular set of providers.
  • the computer services system can check to determine what provider provided the corresponding encoded thing (by matching the code from the new account or service request to the one linked in the system to the providers). Once one or more matches are found, the computer services system can store a credit indicator linked to the user accounts for the providers in manners similar to providing credits to referring users, as discussed above. As discussed herein, referral and credit tracking techniques can include crediting at different levels in the categories of the service data structure.
  • These product and referral tracking and crediting techniques can improve efficiency and accuracy in providing computer-readable value credit to accounts for providers of referrals and products that yield actions using the computer services system that are indicated in the system to be beneficial to the operator of the computer services system (such as setting up new accounts, or requesting particular types of services through the system).
  • the tracking system may avoid having to manually make phone calls, maintain manual credit records, manually provide user input to type in and send messages regarding such credits, and manually inspecting products to provide appropriate credits. And even such manual methods for providing such credits may not have been known prior to the current disclosure.
  • these referral credit and tracking features can provide significant technological benefits.
  • a safety check can be performed.
  • the safety check may include a counterfeit check and/or a malicious code check. If the code fails the safety check, then one or more precautionary measures can be taken by the computer system. For example, for a counterfeit check, the system may check whether the code is included in a list of codes that have been listed as authentic for use in the system. If the code is not found among the list of authentic codes, then the system can refuse to allow use of the code — such as not allowing a record to be generated for that code.
  • the system can perform actions that activate that code, which can allow a record to be generated for that code (or if a record has already been generated, then to allow use of that record to revise the record or use the record to provide services indicated in the record).
  • codes may be included in the list of authenticated codes by submissions from businesses when those businesses provide corresponding encoded things to users.
  • an online or brick-and-mortar provider of physical items may operate a third-party subsystem 196, which may run with one or more third-party apps 126. That third- party subsystem 196 and/or the corresponding third-party app 126 may send the service subsystem 150 indications of the corresponding codes for encoded things as they are provided to their users. The service subsystem 150 can then store indications of those codes in a data structure listing authentic codes.
  • such businesses may use an app running on a device to scan codes to be authenticated, with the app being operable to send identifiers for the codes to the service subsystem 150 for the codes to be authenticated. Also, if an encoded thing 110 is ordered through the service subsystem 150, the service subsystem 150 may store indications of codes for items it provides in that same authentic code data structure listing authentic codes (where that authentic code data structure can be stored in the service subsystem 150).
  • the safety check may include checking for malicious codes.
  • this malicious code check may include checking actions to be performed when the code is scanned, such as examining uniform resource locators linked to the code in the computer system. Such an examination may include examining data (e.g., websites, files, commands, etc.) that is returned when the uniform resource locator is used.
  • data e.g., websites, files, commands, etc.
  • the website can be examined, which can include checking for known types of malicious computer code on the website, checking the website against a list of known malicious websites, checking for valid certificates and/or signatures, and/or checking for valid use of security protocols such as TLS.
  • the system can present the user with a warning about the code.
  • the warning can indicate the type of malicious indication that was found (certificate invalid, found target website on list of malicious websites, etc.).
  • the warning can also include user interface controls to receive user input indicating whether to proceed with use of the code despite the malicious code warning.
  • a mobile device 400 (which is a computing device) can include a display screen 410.
  • the mobile device 400 can run an app such as a camera app that is able to scan a code 412 on an encoded thing 420.
  • the code 412 can be a visual pattern that is a QR code on the encoded thing 420, which can be a for sale sign, or more generally a for-order sign for ordering things whether or not payment is to be made for the things (similarly, in other places where sales are discussed herein, a thing may be provided with or without payment being made in exchange for the thing).
  • the for-sale sign can include instructions, such as saying, “SCAN QR CODE FOR INFORMATION AND OTHER OPTIONS.” If such instructions are included, the instructions and the QR code can together be considered a contact element group, where the instructions and the code can each be a contact element.
  • the code could be another type of code and the encoded thing could be another type of encoded thing, so long as the code is scannable, and the encoded thing is able to include the code (for example as an item bearing an RFID tag that includes the code or another device that includes a transmittable code).
  • An encoded thing can include multiple contact element groups.
  • the mobile device 400 can decode the QR code, which can yield information such as a uniform resource locator in the code.
  • the mobile device 400 can use that information to request a computer resource such as a webpage or an application page for an app.
  • a product setup intro display 500 is illustrated.
  • the intro display 500 can include instructions for beginning a process for setting up a new product, which can begin by instructing the user to log into a valid user account in the services app.
  • the intro display 500 can include an existing user control 510 that can be selected if the user is an existing user that already has an account in the computer services system.
  • the intro display 500 can also include a new user control 520 that can be selected if the user is a new user that does not yet have an account in the computer services system.
  • User selection of the existing user control 510 or the new user control 520 can prompt the mobile device 400 to either launch the services app or download the services app and then launch the services app. Once the services app is launched, the services app can provide a prompt requesting user input to either log into an existing user account or provide information for the system to create a new user account, and then log into the new user account.
  • the live scan display 600 illustrated in Fig. 6 can be displayed.
  • the live scan display 600 can include a scan tab that can indicate that the current display is the scan display.
  • the live scan display 600 can include a live video window 610 that can show a video feed from a camera of the mobile device 400.
  • the live scan display 600 can also include a transmittable code scan status message 620 indicating whether a transmittable code scanning feature, such as near field communications (NFC), is active and ready to scan a transmittable code.
  • NFC near field communications
  • the live scan display 600 can further include a scan initiation user interface control 630, which can be selected to initiate a scan (although a scan may be performed automatically after the mobile device 400 recognizes a visual or transmittable code that is scannable).
  • the live scan display 600 can include a scan tab that can indicate that the current display is the scan display.
  • the live scan display 600 can include a live video window 610 that can show a video feed from a camera of the mobile device 400.
  • the live scan display 600 can also include a close user interface control 640 that can be selected to close the live scan display 600.
  • the live scan display 600 can also include an app share user interface control 650 that can be selected to switch the display to a live app share display discussed below.
  • the system can perform a safety check on the scanned code, as discussed herein. This can include an authentication check and/or a malicious code check.
  • the mobile application can display the safety check display 700 illustrated in Fig. 7, which can include one or more messages about the results of the code scan in a header 705 and one or more messages about results of the safety check in a message window 710.
  • the safety check display 700 can also include a user interface control 720 that can be selected to continue the process.
  • the safety check display may also include a cancel user interface control (not shown) that may be selected to cancel the process and avoid using the scanned code.
  • the safety check display 700 can also include a live user interface control 750 that can be selected to display the live scan display 600 discussed above or the live app share display discussed below.
  • a message or series of prompts could request that the user confirm the action and receive user input confirming the action (such as what integrations are being added and where; potential payment requests related to the pending integrations to be added; and/or other additional actions related to the scan action).
  • the scan action could be performed to transfer (e.g., add, share, etc.) one or more records such as service records and related information (e.g., data, settings, permissions, etc.).
  • This transfer may be with or without associated transferred indications of where in a user account’s portfolio the transferred integrations will be added, and a user account may provide input to indicate where in a user account’s portfolio the transferred integrations will be added.
  • the shared integration could already be preloaded with receiving party data with the share code (e.g., a QR code or associated uniform resource locator) including programming to automatically verify the recipient such as with a verified account to match preloaded shared information before initiating a transfer.
  • the share code e.g., a QR code or associated uniform resource locator
  • a doctor could have a patient scan a code (or share by traditional methods) to share a doctor integration preloaded with patient data including current medications, status and/or a proposed wellness program, which could possibly be assisted with artificial intelligence tools such as an artificial intelligence bot.
  • the patient information in the integration could be integrated into apps, such as third-party apps that are also downloaded to a user’s mobile device that could integrate the patient information.
  • apps such as third-party apps that are also downloaded to a user’s mobile device that could integrate the patient information.
  • a user may manually or automatically provide information feedback through the app back to the doctor for ongoing monitoring and wellness use.
  • This method could similarly be used for other types of providers.
  • a service provider such as a doctor may share a user profile with a current user account that for one of the doctor’s patients, where the profile includes patient information.
  • the profile can be a blended profile, and where appropriate the blended profile may include data from the user profile from the doctor.
  • the service data structure may include a portfolio that is a service provider portfolio, where the service provider portfolio is an integration that provides this functionality.
  • the safety check indicates the code is not authentic, then the system may not allow use of the code in the system. However, if the safety check indicates the code is authentic and it has not yet been linked to a user account in the system, the scanning of the code can prompt the system to activate the code and link it to the current user account (the one that is currently logged into the app).
  • the selection of the user interface control 720 can result in the mobile device 400 displaying a setup display for setting up a record for the scanned code, which can prompt for user input indicating services to be provided when the code is scanned by another device.
  • the live app share display 800 can include a display of a visual share code 810, which can be linked to the currently logged in user account for the computer services system in the services app of the mobile device 400.
  • the visual share code 810 can be scanned by another device with which the app is being shared so that the other device can install the same app and use the computer services system.
  • the live app share display 800 can include a transmittable code status message 820, which can indicate the status of a tool for sharing a share code (which can also be linked to the currently logged in user account on the mobile device 400) via a transmission, such as a near field communications transmission.
  • the computer services system can apply a value credit to the user account that is linked to the share code.
  • the live app share display 800 can include a copy link user interface control 830, which can be selected to copy a link that can be shared with another device to share the app with that other device, which can also result in credit being provided to the currently logged in user account on the mobile device 400 that is sharing the app.
  • Application sharing can be part of a swap contact information service, which can initiate a service that allows users to swap contact information.
  • referral credit can also be added for the other already-existing user account.
  • This joining of the credit and new user account setup with providing an interactive service involving an existing user account may entice engagement with the system and produce additional user accounts using the system.
  • human users who have not signed up to the system may want the service (e.g., the contact information swap or other interactive service) that involves interaction with an existing user account in the system.
  • this joint providing of service, setting up a new user account, and providing credit to the existing user account can also produce a more efficient way of setting up user accounts, providing services, and providing credit to existing user accounts because these processes can be integrated into a single interactive service process involving the existing user account in the system and the new account that is added to the system.
  • the live app share display 800 can include a preview user interface control 840 that can be selected to preview an application share display.
  • the live app share display 800 can also include a close user interface control 850 that can be selected to close the app share display 800, and a scan user interface control 860 that can be selected to open the live scan display 600 discussed above.
  • a new user account is created.
  • the service code app can then display the welcome screen 900 illustrated in Fig. 9, which can include a welcome message 910 and a continue user interface control 920 that can be selected to continue setting up the user account, such as by providing user input regarding the account (name, contact information, preferences, etc.).
  • the mobile device 400 can display a record wallet display 1000 illustrated in Fig. 10.
  • the record wallet display 1000 may also be displayed upon subsequently logging in with a user account that was set up in a previous session.
  • the record wallet display 1000 can include a content list 1010, which can list entries for contents of a current node, such as categories and records in the current category that are direct children of the current category.
  • entries for items such as categories could instead be presented in different ways, such as in images, video tiles, cards, etc.
  • Images and/or videos can have embedded links providing information and/or functionality for categories, record details, demonstrations, etc.
  • the current category can be the top “Wallet” category, which can be indicated in a location indicator 1020 in the header of the record wallet display 1000 to the right of the live user interface control 750.
  • the content list 1010 can include one or more entries 1025, which can each include an item selection user interface control 1030 that can display a record number indicator 1035 that indicates a number of records in the category that are linked to the current user account in a current organization designation for the user account (the record number indicator may be omitted where the entry is for a record) and a title 1040 that is a title for the entry.
  • the letter “n” is used by itself to refer to the record number indicator 1035.
  • the item selection user interface control 1030 can be selected to transition the record wallet display 1000 to the listed category or record.
  • Each entry 1025 in the content list 1010 can also include an information user interface control 1045 that can be selected to display information about the category or record represented by that entry.
  • An entry for a category may be omitted from the display in response to the system determining that there are no records in that category in the current service data structure and/or in response to the system determining there are no records in that category linked to the current user account or to a current organization for the current user account.
  • the categories can include a My Apps category.
  • the service data structure can allow the user input to add applications and navigate potentially different types of app categories below the My Apps category down to an app record level in the hierarchy.
  • displayed user interface controls can be selectable to receive user input to request actions related to the designated app (or multiple apps), such as set settings, access the app, and share the app.
  • apps can be the third-party apps 126 discussed above with reference to Fig. 10, which may include apps that are provided by the same entity that provides the services app 124 or one or more different entities.
  • a general system service option in this case can include allowing a user to scan share an app (provide a scannable code for sharing the app), or transfer an app, to a different organization or a different user account. If an app is transferred, processes may be provided for receiving data to set up a new user account for the transferred app, such as prompting for user input and/or requesting data from other computer components.
  • Apps can operate in single or multiple user configurations (such as playing games or using other apps).
  • the share, transfer, or invite scan (or related shared link invite) can be initiated to invite other user accounts and their associated users to participate in a multiple user app or game, as a paid or free referral.
  • the user account sharing the app could be designated as an administrator with permission to assign roles and/or other administrative duties to user accounts invited by that sharing user account.
  • the original app creator could be allowed to set transfer restrictions and/or share restrictions based on receiving account user conditions and/or based on app policy rules.
  • the categories can include a My Admin Record(s) category, which can include indications of categories and/or records for which the current user account is not the owner but has been granted administrative permissions in the system.
  • the service data structure can allow user input for the user account to prompt the system to navigate other account records for which a current user account was set as an administrator.
  • Setting as an administrator can grant administrator permissions to a user account other than a user account that is designated as an owner of an item in the system (i.e., a primary administrator account for the item), such as an organization (including categories and records within the organization), a category (including categories and records within the category), or a record.
  • Permissions set at one organization or category can apply to items within that organization or category, unless a permission exception to those default permissions is set in the lower category or record, in which case the permission exception would overrule the default permission.
  • Administrator permissions could include View Only (where the permitted user account could only view records, for example), Editor (where the permitted user account could edit records, for example), and Creator (where the permitted user account could edit, add, transfer, reassign, and delete records, for example).
  • an administrator can invite members (such as users who have access with roles as non-administrators or viewers) to have viewing access with service(s) access so that the members can invoke services managers to perform one or more services made available by the records and categories associated with their member roles.
  • Such members may also have permissions to access and modify their own non-administrator settings for associated services.
  • an administrator may add, remove, and/or moderate the activity of members and possibly some other administrators with different administrator roles while also being able to invoke a service manager to perform permissible services made available by the associated records and categories.
  • the categories can include a My Organization(s) category, which can include indications of organizations linked to the current user account.
  • the service data structure can allow user input for the user account to prompt the system to set one or more organizations, and one or more organization indications (indicating divisions, departments, etc.), under which any applicable service categories and related records could be set.
  • Preset and/or predetermined service categories, records, and/or services could be set based on organization descriptors (type, industry, product, service, etc.).
  • the categories can include a Physical Encoded Thing(s) category, which can include indications of physical encoded things that include scannable codes linked to records in the Physical Encoded Thing(s) category (including its sub-categories).
  • the scannable codes (trigger codes) on the physical encoded things can be scanned to make available services indicated in the linked records.
  • the physical encoded things can be physically configured with scannable visual and/or transmitted system linked codes.
  • Record types for physical encoded things can include standard encoded things that can make available existing encoded thing specifications in the records such as service records. Some standard encoded things may initially (during setup) be settable, allowing a user to further configure (such as customizing) the encoded thing with features like additional graphics, setting configured code locations, and/or optionally adding system linked contact elements, such as system linked phone numbers (call routing ID(s) optional), messaging service address(es), uniform resource locators, and/or email address(s).
  • the record types for physical encoded things may include custom encoded things, which can make available encoded things settings, where user input can be provided to manage linked resources such as images, files, services, apps, and/or specifications including custom record code configuration options and/or instructions.
  • the categories can include a Digital Encoded Thing(s) category, which can include indications of digital encoded things that can provide a scannable code in one or more computer devices (such as where a code is transmittable by the computer device and/or a code is displayed on a screen of the computer device).
  • the computer device can be a physical encoded thing that is configured according to the digital encoded thing.
  • the digital encoded things can be digitally configured with system linked codes, which can be configured to be scanned in different ways, such as using visual scanning, auditory scanning, and/or transmission of codes via signals such as electromagnetic waves (e.g., frequency-based transmissions).
  • These digital encoded things can be similar to physical encoded things and can be standard or customized and can be intended for computer output, such as being displayed on screens, projected onto surfaces, and/or incorporated with holographic images.
  • the categories can include a Virtual Encoded Thing(s) category, which can include indications of virtual encoded things that can provide a scannable code in one or more computer devices (such as where a code is transmittable by the computer device and/or a code is displayed on a screen of the computer device).
  • These encoded things can be digitally configured with system linked codes such as visual and/or auditory transmitted system linked codes but can also be virtually tapped or selected to make available linked system services.
  • the computer device can be the encoded thing that is configured according to the digitally encoded thing.
  • These virtual encoded things can be similar to physical encoded things and digital encoded things and can be standard or customized and may be intended for placement in augmented reality(ies), metaverse(s), and/or virtual or simulated world(s) and/or place(s).
  • a scan share service for these encoded things can make available service settings as related to the encoded thing’s virtual reality.
  • Other scan share options can be similar to those discussed with reference to Fig. 23 below.
  • the categories can include an Encoded Template(s) category, which can include indications of encoded templates that can provide a scannable code in one or more computer devices (such as where a code is transmittable by the computer device and/or a code is displayed on a screen of the computer device).
  • These encoded things can be digitally configured such as with visual and/or auditory transmitted system linked codes to computer templates such as video meeting (background) templates for video meeting services; image templates; video templates; document templates; social media post templates; advertisement templates; televised or video broadcast templates; and/or other types of applicable digital media things that incorporate templates.
  • the templates can be configured, downloaded, and manually applied, or be automatically applied via API(s), service sync(s), and/or other or similar configuration and application processes and tools.
  • the categories can include a Posted Encoded Thing(s) category, which can include indications of posted encoded things that can provide a scannable code in one or more computer devices (such as where a code is transmittable by the computer device and/or a code is displayed on a screen of the computer device).
  • These encoded things can be digitally configured with visual and/or transmitted system linked codes incorporated into digital images and/or videos intended for posting to online media services, such as social media services.
  • Posts can be configured, downloaded, and manually posted, or they could be set and/or integrated for automatic creation and/or scheduling via one or more of many available (3 rd Party) posting services like social media services, websites, blogs, forums, customer relationship management services (CRMs), etc.
  • the posts can be automatically posted via API(s), service sync(s), and/or other or similar configuration and application processes and tools.
  • the categories can include an Advertised Encoded Thing(s) category, which can include indications of advertised encoded things that can provide a scannable code in one or more computer devices (such as where a code is transmittable by the computer device and/or a code is displayed on a screen of the computer device).
  • Advertisements can be configured, downloaded, and manually placed, or they can be set and/or integrated for automatic creation and/or scheduling placement via any one of many available online advertising services, such as third-party online advertising services.
  • the advertisements can be automatically applied or placed via API(s), service sync(s), and/or other or similar configuration and application processes and tools.
  • the record wallet display 1000 can also include an add user interface control 1050 and a navigate user interface control 1060.
  • the add user interface control 1050 can be selected to display an order display discussed below.
  • the navigate user interface control 1060 can be selected to open a navigate display 1100 for the current location of the record wallet display 1000 (the top “Wallet” category in this example).
  • the navigate display 1100 for the current location of the record wallet display 1000 (the top “Wallet” category in this example) is illustrated in Fig. 11.
  • the navigate display 1100 can include a location indicator 1120 in the header that can indicate the current location (again, the top “Wallet” category in this example).
  • the navigate display 1100 can also include item indicator controls 1112, or rollup indicator controls as also illustrated in Fig. 23. However, the item indicator controls may be omitted from the navigate display 1100 in some situations, such as for a wallet page.
  • the item indicator controls 1112 can include a services status user interface control 1125 that can indicate whether the system has detected problems with the services linked to the current user account via items such as categories or records in the category of the current location under the currently active organization designation (there may be multiple organization designations for a single user account each with its own set of linked records, and user input can be provided to switch between such organization designations for that user account).
  • the services status user interface control 1125 can be selected to display information about problems with the services.
  • the item indicator controls 1112 can also include an action items user interface control 1130, which can list a number of action items that are waiting for user input (the “n” can be replaced with a number, which is also true in the list items in the record wallet display 1000).
  • the action items user interface control 1130 can be selected to display a list of action items that need user input to proceed.
  • the item indicator controls 1112 can also include a captured data user interface control 1135, which can be selected to reveal data that has been captured, such as data that has been captured in providing services for codes linked to the current user account and organization designation.
  • the item indicator controls 1112 can also include a messaging user interface control 1136, which can indicate a number of pending messages (possibly messages marked as unread) linked to items such as categories and records in the current category, and can be selectable to display the messages.
  • the item indicator controls 1112 can also include an analytical data user interface control 1137, which can be selectable to display analytical data linked to items such as categories and records in the current category (e.g., number of scans of codes and related device identifiers for a particular record and/or for all records in a particular category).
  • the item indicator controls 1112 can also include an administrators user interface control 1138, which can be selectable to display information regarding administrators (i.e., user accounts given administrator permissions) for items such as categories and records in the current category, and optionally allowing user input to edit the permissions of the administrators and/or add or remove administrators for specified items such as categories or records.
  • administrators i.e., user accounts given administrator permissions
  • the item indicator controls 1112 can also include a summary /reports user interface control 1139, which can be selectable to display one or more reports and/or summaries regarding items such as categories and records in the current category. In all the data that can be displayed in response to selection of the item indicator controls 1112, the data can roll up to the current category, so that the data can include the specified types of data for the current category, including its descendants (such as subcategories and records). Item indicator controls 1112 and related action options may be restricted or not included at all in some scenarios, such as on mobile devices. [0180]
  • the navigate display 1100 can further include an account user interface control 1140, which can be selected to display data for the active account and to allow editing of that data.
  • the navigate display 1100 can also include one or more navigation user interface controls 1150, which can include a user interface control for the current location (again, the top “Wallet” category in this example) and ancestor categories of the current location (i.e., the categories that include the current category), if any. Selection of a user interface control in the navigation user interface controls 1150 can result in the display of the record wallet display 1000 for the location indicated by that control (such as the “Wallet” category for the “My Wallet” user interface control in Fig. 10).
  • a user interface control for the current location as the top “Wallet” category in this example
  • ancestor categories of the current location i.e., the categories that include the current category
  • the record wallet display 1000 is illustrated for the Encoded Things category, which is indicated in the content list 1010 of Fig. 10.
  • the record wallet display 1000 in Fig. 12 additionally adds a search user interface control 1260 that can be selected to prompt for entry of text to search for records in the category that match the entered search text (i.e., records that are descendants of the current category of the record wallet display 1000). Selection of the navigate user interface control 1060 in the illustrated record wallet display 1000 of Fig.
  • the mobile device 400 can prompt the mobile device 400 to display the navigate display 1100 at the current location (the “Encoded Things” category) as illustrated in Fig. 13.
  • the navigate display 1100 of Fig. 13 can be similar to the navigate display 1100 of Fig. 11. However, the navigate display 1100 of Fig. 13 can omit the item indicator controls 1112 of Fig. 11. Also, the navigation user interface controls 1150 of the navigate display 1100 of Fig. 13 can further include an Encoded Things user interface control in addition to the Wallet (“My Wallet”) user interface control. Selection of the Encoded Things user interface control can display the record wallet display 1000 of Fig. 12, while selection of the Wallet user interface control can display the record wallet display 1000 of Fig. 10. Alternative and/or additional techniques for acquiring and presenting encoded things can be used, as discussed herein.
  • Selection of the item selection user interface control 1030 for the For Offer Sign in the record wallet display 1000 of Fig. 12 can prompt the mobile device 400 to display the record wallet display at the For Offer Sign Location. Selecting the add user interface control on that record wallet display can prompt the mobile device 400 to display the record wallet display 1000 of Fig. 14, which can be a record wallet display for selecting additional service records to add (i.e., order, which can include to request linking selected available records as linked records for the current user account).
  • the add user interface control like in Fig. 12 may not be included in the record wallet display 1000 of Fig. 14 because that display is already in the add mode, but the record wallet display 1000 of Fig.
  • a user interface control (not shown) to switch to the record wallet display for viewing the already-linked records for the user account, like the one in Fig. 12.
  • selection of the navigate user interface control 1060 in the record wallet display 1000 of Fig. 14 can prompt the mobile device 400 to display the navigate display 1100 for the For Offer Sign category location, as illustrated in Fig. 15, which can be like the display of Fig. 13, but where the navigation user interface controls 1150 can include user interface controls for displaying the record wallet display 1000 for each of the For Offer Sign, Encoded Things and Wallet categories (for the current location and the location for each of its ancestor categories).
  • Selection of the item selection user interface control 1030 for the For Sale Sign category in the record wallet display 1000 of Fig. 14 can prompt the mobile device 400 to display the record wallet display 1000 of Fig. 16 for the For Sale Sign category location.
  • selection of the navigate user interface control 1060 in the record wallet display 1000 of Fig. 16 can prompt the mobile device 400 to display the navigate display 1100 for the For Sale Sign category location, as illustrated in Fig. 17, which can be like the display of Fig. 15, but where the navigation user interface controls 1150 can include user interface controls for displaying the record wallet display 1000 for each of the For Sale Sign, For Offer Sign, Encoded Things and Wallet categories (for the current location and the location for each of its ancestor categories).
  • Selection of the item selection user interface control 1030 for the English Sign category in the record wallet display 1000 of Fig. 16 can prompt the mobile device 400 to display the record wallet display 1000 of Fig. 18 at the English Sign category location. Further, selection of the navigate user interface control 1060 in the record wallet display 1000 of Fig. 18 can prompt the mobile device 400 to display the navigate display 1100 for the English Sign category location, as illustrated in Fig. 19, which can be like the display of Fig. 17, but where the navigation user interface controls 1150 can include user interface controls for displaying the record wallet display 1000 for each of the English Sign, For Sale Sign, For Offer Sign, Encoded Things and Wallet categories (for the current location and the location for each of its ancestor categories).
  • the entries 1025 in the content list 1010 for the English Sign category can be entries for categories Print on Demand Sign and Pre-Manufactured Sign.
  • selection of the item selection user interface control 1030 for the Print on Demand Sign entry can display the order display 2000 illustrated in Fig. 20.
  • the order display 2000 of Fig. 20 can include a description message 2010, describing the thing to be ordered, such as including the titles for corresponding print on demand sign available record and its ancestor categories.
  • the order display 2000 may also include additional information about the available record.
  • the order display 2000 can also include an order user interface control 2020, which can be selected to launch a user interface display or sequence of displays for ordering an encoded thing described by the description message 2010. This may include the system processing payment information (if a payment is to be made for the ordered encoded thing), and shipping information or other information for obtaining the ordered encoded thing for the order.
  • Ordering can also include any applicable system action as related to placing an order, such as the code for the ordered encoded thing being added to an authenticated code list, activating the code and linking the code to the current user account, sending one or more messages to a third party for approval for the order, checking production queues to provide time estimates to produce the encoded thing, prompting for and receiving user input indicating accessory options, prompting for and receiving user input indicating customized specifications, prompting for and receiving user input indicating customized warranty options, third-party compatibility checks, etc.
  • any applicable system action as related to placing an order, such as the code for the ordered encoded thing being added to an authenticated code list, activating the code and linking the code to the current user account, sending one or more messages to a third party for approval for the order, checking production queues to provide time estimates to produce the encoded thing, prompting for and receiving user input indicating accessory options, prompting for and receiving user input indicating customized specifications, prompting for and receiving user input indicating customized warranty options, third-party compatibility checks, etc.
  • the order display 2000 can also include a navigate user interface control 2030, which can be selected to prompt the mobile device 400 to display the navigate display 1100 for the Print on Demand Sign category location, as illustrated in Fig. 21.
  • the navigation user interface controls 1150 can include user interface controls for displaying the record wallet display 1000 for each of the Print on Demand Sign, English Sign, For Sale Sign, For Offer Sign, Encoded Things and Wallet categories (for the current location and the location for each of its ancestor categories).
  • Fig. 22 illustrates a record wallet display 1000 for a category with direct children that are records linked to the current user account in the current organization designation, which can be in the form of a record list.
  • the record wallet display 1000 can include the content list 1010 with entries, where the entries can include entries 1025 for records that are linked to the current user account in the current organization designation.
  • Each such list item can include an item selection user interface control 1030, which can display a title 1040.
  • the record wallet display of Fig. 22 can also include a navigate user interface control 1060 and an add user interface control 1050, both of which can be selectable for the same operations discussed above for such user interface controls.
  • the record wallet display 1000 of Fig. 22 can include a transfer user interface control 2220, which can be selected to begin a process for transferring one or more selected service control records along with indications of each selected record’s ancestor categories (such as transferring the service control record to a different organization designation for the same user or to a different user account, which can include changing one or more linking references such as the linking references between the transferred service control record and the organization designation and/or user account, and/or references between the transferred service control record and categories in the service control data structures).
  • a transfer user interface control 2220 can be selected to begin a process for transferring one or more selected service control records along with indications of each selected record’s ancestor categories (such as transferring the service control record to a different organization designation for the same user or to a different user account, which can include changing one or more linking references such as the linking references between the transferred service control record and the organization designation and/or user account, and/or references between the transferred service control record and categories in the service control data structures).
  • Selection of the item selection user interface control 1030 for the service control record of Fig. 22 can prompt the mobile device 400 to display a record manager display 2300 of Fig. 23.
  • the record manager display 2300 can have some similar features to the navigate display 1100, including the live user interface control 750, the location indicator 1120, and the item indicator controls 1112.
  • the record manager display 2300 can further include a scan share services user interface control 2330, which can be selected to perform a scan share of services, such as displaying a visual linked code that can be scanned and/or activating a tool to transmit a transmittable linked code (scanning the transmittable code), whose scanning can prompt the system to make the linked services available to a scanning device and/or scanning user account.
  • the record manager display 2300 can further include a scan share record user interface control 2332, which can be selected to perform a scan share of a record, such as displaying a visual linked code that can be scanned and/or activating a tool to transmit a transmittable linked code, whose scanning can prompt the system to share the current record with a different organization or user account, which can allow the record to be utilized by the other organization or user account — such as by the other user account providing the associated code in a scan share services process to provide the linked services to a scanning device and/or user account.
  • a scan share record user interface control 2332 can be selected to perform a scan share of a record, such as displaying a visual linked code that can be scanned and/or activating a tool to transmit a transmittable linked code, whose scanning can prompt the system to share the current record with a different organization or user account, which can allow the record to be utilized by the other organization or user account — such as by the other user account providing the associated code in a scan share services process to provide the
  • the record manager display 2300 can further include a set shared services user interface control 2334, which can be selected to display a set shared services display, which can allow the shared services linked to the current record to be set (initially set and/or modified).
  • the record manager display 2300 can further include a set record services user interface control 2336, which can be selected to prompt the system to display one or more displays to receive user input to set record services linked to the current record.
  • the record manager display 2300 can further include a set shared page user interface control 2338, which can be selected to display a set shared page display, which can prompt the system to display one or more displays to receive user input to set a page to be shared as part of the services to be provided when sharing services for the current record.
  • the record manager display 2300 can further include a record items user interface control 2340, which can be selected to list encoded things that are indicated for the current record (for example list item for sale signs that have been marked with a visual code linked in the current record). Other encoded items could be ordered here to include the same code.
  • the record manager display 2300 can further include a transfer record user interface control 2350, which can be selected to begin the process of transferring the record to a different organization designation (which can be a different category) or user account; a delete record user interface control 2355, which can be selected to delete (or possibly remove, archive, or deactivate) the record; and a back to record list user interface control 2360, which can be selected to return to the record wallet display 1000 of Fig. 22.
  • user input can be provided to select the depicted code icon 1042 to prompt the system to present a visual code linked to the associated record.
  • other similar record settings controls could be added as instant access icons to the item selection user interface control 1030, with each being selectable to present indicated information from the linked record. Interfaces related to the record manager display 2300 are not limited in number and/or related function or type.
  • Selection of the scan share services user interface control 2310 of Fig. 23 can prompt the mobile device 400 to display a scan share display 2400 illustrated in Fig. 24.
  • the scan share display 2400 can be similar to the live app share display 800 discussed above, except that instead of sharing a share code, the scan share display 2400 can be operable to share a code that is linked to a record and to services indicated in the record.
  • a device scanning the code from the scan share page can receive the code and use it to request the services indicated in the linked record.
  • the scan share display 2400 can include a location indication 2405 that can indicate a current record whose code is to be shared.
  • the scan share display 2400 can also include a display of a visual trigger code 2410, which can be linked to the current record. This trigger code can be different from the code for sharing the application and tracking application sharing credit for the user account, which is discussed above.
  • the visual trigger code 2410 can be scanned by another device with which the app is being shared so that the other device can invoke the services indicated in the current record. This can begin with the scanning device sending a request to the service subsystem, where the request can include data derived from the scanned code.
  • the scan share display 2400 can include a transmittable code status message 2420, which can indicate the status of a tool for sharing a trigger code (which can also be linked to the current record) via a transmission, such as a near field communications transmission.
  • the scan share display 2400 can include a copy link user interface control 2430, which can be selected to copy a trigger link, such as a uniform resource locator, which can be shared with another device to prompt the other device to trigger the services indicated in the current record, which can also include the receiving device (or even the mobile device 400) sending a request to the service subsystem with data derived from the copied link.
  • a services app such as the services app 124 discussed above with reference to Fig.
  • the system can instead ask for confirmation to add or launch one or more processes to place/set/create data at the appropriate location in the data structures linked to the receiving user account (the user account that is active in the services app when scanning the trigger code); and/or execute a direct account command.
  • the scan share display 2400 can include a preview user interface control 2440 that can be selected to preview an application share display.
  • the scan share display 2400 can also include a close user interface control 2450 that can be selected to close the scan share display 2400.
  • selection of the set shared page user interface control 2338 can prompt the mobile device 400 to display one or more displays to set features of services to be provided in connection with the record.
  • displays may include displays like one or more of the illustrations in Figs. 25, 26, 27, 28, 29, and/or other service feature setting displays.
  • a set page services display 2500 is illustrated in Fig. 25.
  • the set page services display 2500 can include a service list 2510 that can include multiple service entries 2520 representing services that are available for the current record.
  • the available services for a record may be inherited from settings for the category that includes the record.
  • a category may inherit its settings for what services are available from a parent of that category, which may inherit its available service settings from its parent category, and so forth.
  • available services for records in a category may include a subset of the records that are available for the category’s parent category.
  • Each service entry 2520 can include a status indicator 2530, indicating whether the service is active or inactive (on or off) for the current record. Some available services can be free services while others can be paid services.
  • Each service entry 2520 can also include a title 2535 for the service, and an edit user interface control 2540, which can be selected to edit features of the service.
  • the mobile device 400 may respond to user input selection of the edit user interface control 2540 by displaying one or more displays that include user interface controls for editing features of the service when used with the current record, and the resulting input can be stored in the record as settings for that service when used with that record, such as when the service is provided in response to a trigger that includes the code or codes linked to that record.
  • the set page services display 2500 can also include a save/continue user interface control 2560, which can be selected to save changes that have been made and continue to another display for setting up or editing the record.
  • selection of the set shared page user interface control 2338 can result in the display of a for-sale item page format display 2600 of Fig. 26, which can look the same as an actual services display that can be provided as part of providing services in response to an associated trigger code being scanned except that the actual services page could include images for features such as the main image, the interactive map, the photo gallery, and the interactive video (accordingly, such a services page is indicated by the reference for services page 2660 in Fig. 26, rather than including a separate figure for the services page 2660).
  • the for-sale item page format display 2600 can be formatted as a template for a services page that can be displayed in response to scanning of a code linked to the current record.
  • the for-sale item page format display 2600 can include user interface controls 2610 that can be selected to provide content for different page features to be displayed on a corresponding services page, in the same places where the user interface controls 2610 are displayed on the for-sale item page format display 2600.
  • Each of the user interface controls 2610 can be selected to provide relevant data for the page. For example, an item title (“Item For Sale Name”) may be selected to provide a text box into which text may be entered for the item title.
  • a main image (“Item for Sale Image”) may be selected to select an image from available images (e.g., from photographs stored on the mobile device 400).
  • An interactive map (“Interactive Map”) may be selected to provide an address of a location to be shown on an interactive map in the services page.
  • An image gallery (“Photo Gallery”) may be selected to provide multiple images to be included in an image gallery feature in the services page.
  • An interactive video control (“Interactive Video”) may be selected to provide one or more interactive video files for an interactive video feature to be included in the services page.
  • a message system control (“Message System”) may be selected to provide information to allow a feature for sending a message to a messaging profile to be associated with the record.
  • the for-sale item 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).
  • Selection of a save/continue user interface control on a services setup display or selection of the set shared page user interface control 2338 can result in the display of a set shared website display 2700 of Fig. 27.
  • the set shared website display 2700 can include a title user interface control 2710 for receiving user input to set a title for the website to be shared, and a uniform resource locator control 2720 for receiving user input to set a uniform resource locator for the website.
  • the uniform resource locator can be used to provide a service that launches a webpage referenced by the uniform resource locator control.
  • the shared website display 2700 can also include a cancel user interface control 2730 that can be selected to cancel the data entered on the shared website display 2700, and a save/continue user interface control 2740 that can be selected to save data entered on the shared website display 2700 and continue to another display.
  • a cancel user interface control 2730 that can be selected to cancel the data entered on the shared website display 2700
  • a save/continue user interface control 2740 that can be selected to save data entered on the shared website display 2700 and continue to another display.
  • the system could prompt for entry of social media usernames instead of the uniform resource locator.
  • the uniform resource locator here can be entered by user input, but an actual uniform resource locator for use in providing services may be a system-set uniform resource locator that is encoded in a scannable code that is linked to the record, and that uniform resource locator may forward to the uniform resource locator provided in Fig. 27.
  • the set shared contact data display 2800 can include contact data user interface controls 2810 that can be used to enter contact data to be shared, such as a record title, a first name, a last name, an organization indicator, a mobile phone number, a work phone number, an email address, a website address (uniform resource locator), and a memo or notes to be shared.
  • a service linked to the current record can share such data with a scanning device in response to scanning of a code linked to the record.
  • the shared contact data display 2800 can also include a cancel user interface control 2830 that can be selected to cancel the data entered on the shared contact data display 2800, and a save/continue user interface control 2840 that can be selected to save data entered on the shared contact data display 2800 and continue to another display.
  • a cancel user interface control 2830 that can be selected to cancel the data entered on the shared contact data display 2800
  • a save/continue user interface control 2840 that can be selected to save data entered on the shared contact data display 2800 and continue to another display.
  • this can be an encoded command example for initiation of a trigger uniform resource locator command that opens a scan device new contact form and then populates the form, making it ready for saving the resulting contact profile to the scanning device.
  • a similar process may queue device maps to share preconfigured location(s), queue device calendars to set preconfigured events/appointments, queue device text message to send preconfigured texts, queue device email client to send preconfigured emails, queue device phone to call preconfigured phone numbers, queue device Wi-Fi settings to share preconfigured Wi-Fi data, and/or trigger any device capable action including actions via any system linked/ API integrated applications, and/or actions from apps with operating system controls/permissions.
  • An implementation may include optionally populating the website address with a service page link — the service page that the account user provides user input to update anytime by adding the service page link as contact data to a device contact data form. This can expand the options for data being shared. For example, when the scanning device user selects the contact information associated with the record and selects the website link, the service page can be presented with real time, expanded and up to date information.
  • the set trigger message contact exchange display 2900 can include data user interface controls 2910 that can be used to enter data for a trigger message to be sent in response to scanning of a linked code.
  • the data user interface controls 2910 can include a user interface control into which a phone number can be entered.
  • the entered phone number can be provided to a scanning device in response to the scanning device scanning the linked trigger code, so that the scanning device can send its phone number to the entered phone number to receive a reply message with a link (including any number of other possible service page links) to a form, which allows contact information to be exchanged.
  • the data user interface controls 2910 can also include a control for entering a message to be sent, requesting the other scanning device to send back its phone number to receive the link to the form.
  • the data user interface controls 2910 can also include a country entry user interface control that can be used to select a country, such as from a drop-down menu, and a digital contact card user interface control that can be used to select and load a digital contact card to be shared using the form mentioned in the message.
  • the set trigger message contact exchange display 2900 can also include a cancel user interface control 2930 that can be selected to cancel the data entered on the set trigger message contact exchange display 2900, and a save/continue user interface control 2940 that can be selected to save data entered on the set trigger message contact exchange display 2900 and continue to another display.
  • This process can apply to many different scenarios where computer-readable information is transmitted to the scanning device in response to scanning a code, and that information includes data for sending an initial computer communication to request a response computer communication with a link (such as a user- selectable link) that can be used to trigger further system actions.
  • This process can apply to any type of system communication (not just text messages), including email, different messaging systems, calendar invites, etc.
  • the associated service settings page can be configured to match any of the scenarios, including configuring the page to prompt for user input for the appropriate data for the scenario (including the appropriate communication contact information for the type of communication to be used).
  • Figs. 30-32 illustrate displays for custom records that can be added by users of the computer services system.
  • the system can be pre-loaded with standard structured categories and records.
  • user input can also be provided for user accounts to add and revise custom records that can be included in custom categories, which can be created and revised in response to user input.
  • a user may want to print a code onto its own custom encoded things and categorize those things itself.
  • a record wallet display 1000 can include one or more entries 1025 for custom encoded things, with the title “Custom Encoded Things”.
  • User input can be provided to the item selection user interface control 1030 for the custom encoded things, which can reveal a record wallet display of Fig.
  • the record wallet display 1000 of Fig. 31 for custom encoded things records can include a reassign user interface control 3120 for reassigning the custom record to a different position, which may be reassigning within the hierarchy for the current organization designation and user account, or reassigning by transferring the custom record to a different user account or different organization designation for the same user account as discussed herein for standard records.
  • the transferred record can be transferred with indications of its hierarchy — both standard hierarchy ancestors and any custom hierarchy ancestors that may have been added in response to user input.
  • Those hierarchies can be used by the system to include the transferred custom record with the same hierarchy for the new organization designation or user account data structure.
  • user input can be provided to change custom hierarchy category names and/or structure as part of the reassign options.
  • the custom record can then be reassigned using those new category names and/or structure.
  • Selection of the navigate user interface control 1060 on the display of Fig. 31 can prompt the mobile device 400 to display a record manager display 2300 illustrated in Fig. 32, like the record manager display 2300 of Fig. 23 discussed above.
  • the record manager display 2300 of Fig. 32 for a custom record can include a reassign user interface control 3220 instead of the transfer record user interface control 2350.
  • the reassign user interface control 3220 can be like the reassign user interface control 3120 discussed above with reference to Fig. 31.
  • Adding an encoded thing and/or a record could have more complex steps, such as wizard-guided steps, that walk through the service category(ies) setup as related to ordering a service record related service or thing, or the system receiving user input to set up a standard or custom thing.
  • Fig. 33 illustrates a record service setting display 3300 for setting record services for a record and/or for records in a category.
  • These record services can be types of system services, which can be made available to the user account to further expand record capabilities, as with other record services.
  • the record services may include Add Items to Marketplace(s) service(s) (which can include adding items to one or more marketplaces, such as including one or more advertisements or product list items in marketplaces that include scannable codes), Set Social Media posts service(s) (which can include setting up and posting one or more social media posts), and/or Place Advertisements service(s) (which can include setting up and publishing and/or generating one or more advertisements that include scannable codes).
  • the record service setting display 3300 can include user interface controls that can be selected to set up the corresponding services and/or display additional displays that can prompt for user input to set up the services.
  • these user interface controls on the record service setting display 3300 can include an Add Items to Marketplace(s) user interface control 3310, a Set Social Media Posts user interface control 3320, and a Place Advertisements user interface control 3330.
  • the record service setting display 3300 can further include a save/continue user interface control 3350, which can be selected by user input to save changes and continue.
  • the services discussed here could be any of a variety of services, such as one or more of the types of services discussed above.
  • a user account may have rights to change (e.g., add, edit, reorganize, delete, etc.) service data structure items (including organizations, categories, and/or records) that can be generally available to be added (i.e., added with a link) to other user accounts as discussed herein (not merely by the specific transferring or sharing operations from one user account to another, as discussed herein).
  • a change-rights user account may be a user account that has such change permissions to change any or all the available organizations, categories, and/or records. For example, this may be the case for a user account of an employee who is a software developer or system administrator for a business entity that manages the service subsystem and/or other parts of the computer services system discussed herein.
  • the service data structure items that are generally available for other user accounts may be available to all other user accounts, or to some defined subset of all other user accounts, such as where different user accounts have subscribed to access to different subsets of the service data structure items.
  • one or more change-rights user accounts may have such change permissions for only a subset of the available service data structure items that can generally be made available to be added to other user accounts. Accordingly, such a subset of the available service data structure items can be the subject of permissions
  • a third-party business entity (an entity other than the one that manages the overall service subsystem and/or other parts of the computer services system discussed herein).
  • a third-party business entity may manage a third-party subsystem, such as an online marketplace and/or be a provider of encoded things.
  • the third-party business entity may operate an online marketplace to which encoded advertisements that include product offers may be posted from the service subsystem to the third-party online marketplace subsystem.
  • That same third-party business entity may also be a provider of encoded for- sale signs that can be linked to product list items on the online marketplace (where the services provided in response to scanning the trigger code on the encoded for-sale signs and/or the posted advertisements include displaying the product list item in the online marketplace).
  • the change-rights user account that has rights to change service data structure items that are generally available to other user accounts may also be a user account to which specific records can be linked for those records to be used in providing computer services, as discussed herein.
  • a single user account may be used for changing service data structure items that are generally available to be used for creating linked records that are added to other linked user accounts, and that single user account may also be used for managing records and/or other service data structure items that are linked to that single user account.
  • that single user account may have permissions to change records and other related service data structure items that are generally available for other user accounts, and to change and use records and other related service data structure items that are linked to the single user account, as discussed herein.
  • the system may include limits on what changes can be made by user accounts that have permissions to change records and record structures available to other user accounts. For example, the system may inhibit at least some user accounts with such administrative permissions from deleting records, organizations, and/or categories after the records, organizations and/or categories have been made available for adding by other user accounts, or once the records, organizations and/or categories (or records and/or categories within them) have been added to at least one other user account. For example, such deletions may be prohibited by the system, or such deletions may only be allowed if certain conditions are met (e.g., if permission is granted by one or more other user accounts in the system, such as by one or more user accounts for a business entity that generally manages the service subsystem).
  • Such limits may be the same for all user accounts that have permissions to change records and record structures available to other user accounts, or they may be different for different sets of user accounts that have permissions to change records and record structures available to other user accounts (e.g., the limits may be different for user accounts having different roles designated in the system and/or user accounts that are linked in the system to different entities such as business entities).
  • the transfer process can allow a wizard to incorporate the integration into an applicable location in the service data structure for the user account, which may be indicated in the integration or in some other setting.
  • the wizard can move on to allow and/or facilitate any needed financial transfer (such as payment processing for payment for the integration) and/or integration related setup. Instead of managing the setup, the wizard may request simple approval from the user account to accept the integration and place the integration in the location referenced by the Integrations Pending Setup (Review) location list item illustrated in Fig. 48, so that the integration can be set up later. Some integrations, such as those controlled by other user accounts, can be locked so that they are not transferrable from the current user account.
  • An encoded thing can be any of many different things, such as a point-of-sale display.
  • a point-of-sale display 3400 or more generally a point-of-order display for ordering things whether or not payment is made (where point-of- sale display 3400 may be a physical sign, a computing device with a screen display, or some other type of point-of-sale display), can include an instructional message 3410 and a scannable code 3420.
  • the code can be scanned to prompt the system to perform a service that includes providing tools for ordering a thing such as an encoded sign, which can be done using a record that is linked to the scannable code 3420.
  • a sign provider’s user account can be linked to that record for setting up and managing that record that is linked to the scannable code 3420.
  • the encoded sign that is being ordered can also be an encoded thing that can include a scannable code that is different from the scannable code 3420 on the point-of-sale display 3400.
  • the service of ordering the encoded sign may also include a service of signing up a user account or logging into an existing user account in the system (a different user account for the human user that is ordering the sign, rather than for the provider of the point-of-sale display), and linking the code of the ordered encoded sign to that user account and to a created record that is linked to that user account.
  • a point-of-order display may include a scannable code that is linked to a record indicating one or more other types of services to be performed in addition to or instead of a process for ordering an encoded thing. For example, scanning a code on a point-of-sale display may prompt the system to access a record indicating one or more other types of service, prompting the system to provide at least one other type of service in addition to or instead of a process for ordering an encoded thing.
  • the service may be a paid subscription service; a paid event service, like a purchase of a concert ticket; or some other type of service, which may or may not be a service related to an encoded thing that is also being ordered using the point-of-order display.
  • a point-of-sale display 3500 (which may be a physical sign, a computing device with a screen display, or some other type of point-of-sale display), can include an instructional message 3510 and a scannable code 3520.
  • the point-of-sale display 3500 can be structured and can function like the point-of-sale display 3400 discussed above.
  • the scannable code 3520 can be scanned to order an encoded thing that is a pet tag instead of an encoded sign.
  • an encoded thing can be scanned to trigger a process for ordering another encoded thing, and the different codes for the two encoded things can be linked to different corresponding records in the system and can be linked to different user accounts in the system for managing those records.
  • referral credits discussed herein can be provided in the system for one or more providers of the first encoded thing, which can include manufacturers, distributors, and a retail establishment that is displaying an encoded point-of-sale display.
  • integrations are structures that are integrated into a hierarchical services data structure such as the services data structure 174 discussed above.
  • An integration can be a category in the service data structure.
  • An integration can be used in providing one or more services such as the types of services discussed above. For example, services may be provided using the integration via a services manager. Services managers can also manage building and/or modifying service records, which can be included in integrations.
  • the integrations can implement the types of services listed above, as appropriate.
  • An integration can include subcategories within it, including hierarchical categories and records.
  • an integration can include one or more service records that can be used to provide services, such as record services and/or code services (e.g., via a service manager).
  • the integrations may include rollup integrations, in which data and records from lower levels can roll up to be used in higher levels. Integrations may include fixed integrations in which applicable data may roll up to higher levels in the integrations, but each record is considered to be at a particular level and does not roll up to higher levels. Also, in fixed or rollup integrations, some actions performed at a category node on a level (applying settings, etc.) can apply to nodes (such as category and/or record nodes) that are descendants on levels below that category node. Integrations can include temporary integrations that may be activated or deactivated in a structure. The system can also include temporary links to a structure that can be activated or deactivated. Also, options associated with a structure may change. All these types of temporary structures and states for an integration may change based on conditions, which may be internal and/or external conditions.
  • rollup integrations that will be discussed below include a contacts integration in which profiles in contacts groups in a contacts structure can roll up to higher levels of the contacts structure.
  • Another example of a possible rollup integration could be a documents integration for documents management in which the documents can be records that can roll up to higher levels.
  • types of integrations that are discussed herein as being rollup integrations may be used in other implementations as fixed integrations, and types of integrations that are discussed herein as fixed integrations may be used in other implementations as rollup integrations.
  • a portfolio integration can be an integration that provides a hierarchy of structured categories referred to here as portfolios that can include other portfolios as well as records and other integrations that are integrated into the structure of the portfolio integration.
  • portfolios can be another term for the structured categories at and below the “Wallet” category discussed above.
  • Each portfolio in the portfolio integration can remain at a specified level rather than rolling up to higher levels (although in some instances, the portfolios in an integration could be moved to other places in the portfolio structure).
  • a settings integration can be an integration that manages settings, such as settings for other integrations (e.g., settings for portfolios in the portfolio integration, and/or settings for other integrations).
  • a metering integration can be an integration that provides metering services.
  • a metering integration may provide services that track values being metered as those values change over time. The metering itself can be provided at a per-node basis even though it may perform metering operations on data that is rolled up from nodes below that node.
  • Integrations can work together to perform services, including option type services 3630 provided by option types 3610 of integrations and non-option type services 3660 provided by non-option types 3620 of integrations.
  • Managers 3665 for the option type services 3630 can manage service records for the option type services 3630 (e.g., managing the building, editing, etc. of the service records) and can manage the providing of services.
  • managers 3670 for the non-option type services 3660 can manage service records for the non-option type services 3660 and the providing of the non-option type services 3660.
  • option types 3610 and non-option types 3620 can perform services for each other (as indicated by arrows extending between the “SERVICES” boxes and the other types in Fig. 36).
  • option types 3610 of integrations can provide option type services 3630 to non-option types 3620 of integrations.
  • non-option types 3620 of integrations can provide non-option type services 3660 to option types 3610 of integrations.
  • the option types 3610 can include global and current level down types 3720, which can include option integration types that can apply their services at a current level in the hierarchy and below, but can also provide global services that are not specific to the current node or level when they are invoked.
  • the option types 3610 can also include current level down types 3725, which can include option integration types that can apply their services at a current level in the hierarchy and below, and do not typically provide global services.
  • the global and current level down types 3720 can include action notification types 3730 and live types 3735, which will be discussed below.
  • the global and current level down types 3725 can include other context-sensitive option types 3740, such as a communications integration, an interactive calendar integration, marketplace integrations, a support integration, a data integration, a metering integration, assign integrations, a searchable access integration, an associated contacts integration, an experience options integration, a shared profile integration, a related structures integration, a records access integration, and a service access (records manager) integration.
  • Option type integrations may also include other integrations beyond those listed here, including integrations that can be used to perform services mentioned above, as applicable. While the options integrations are discussed herein as being context-sensitive, it is possible that other types of integrations (e.g., records integrations or portfolio integrations) may also be context-sensitive.
  • the non-option types 3620 can include portfolio types 3755, which can be integrated into the portfolio structure of the overall service data structure.
  • the non-option types 3620 can also include calendar types 3760, which can include integrations for providing one or more calendar services for a user account.
  • the non-option types 3620 can also include contacts types 3770, which can include integrations for providing one or more services for contacts between user accounts.
  • the non-option types 3620 can also include profile types 3780, which can include integrations for providing one or more services for profiles linked to user accounts.
  • service subsystem 150 can be structured to facilitate building and integrating additional integrations into the service data structure 174.
  • Such integrations may be built by bots and/or humans who are developing for an entity that controls the service subsystem 150 and/or other bots and/or humans, such as third parties who may build integrations to be included and made available on a digital integration marketplace running in the service subsystem 150.
  • Such bots and/or humans may provide input to managers 3665 and/or managers 3670 in building and/or editing such integrations.
  • integrations in the subsystem 150 may interact with computer resources in other subsystems such as a third-party subsystem 196.
  • integrations that can be integrated into the system discussed herein: possibly Al assisted information organizational service integrations (filtering, sorting, presets, default sets, predictive data input, etc.); possibly Al assisted matching service integrations (mix and matching, people, organizations, events, content, services, activities, courses, curriculum, literature, music, videos, podcasts, art, products, entertainment, etc.); service provider integrations; administrator integrations; integrations controlling other integrations; possibly Al assisted program/project/product management service integrations (structured blueprints with some or all the (paid) related services, schedule, planning, budget, costs, resource allocations, etc.
  • Al assisted interactive library service integrations services capable of creating and then storing, organizing, and intelligently making available library applicable content, like sops, albums, pictures, images, art, procedures, specifications, content, literature, eBooks, videos, courses, training, files, applicable physical/digital/virtual assets, etc.
  • possibly Al assisted file management service integrations management, storage, backups, archiving, creating/as signing albums, setting access to, etc. as related file things, like pictures, documents, images, videos, files, archives, etc.
  • possibly Al assisted content management service integrations identifying, creating, modifying, repurposing, placing, advertising, marketing etc.
  • a first example can include a possibly Al assisted organization development portfolio integration, which would include third party system-integrations with the purpose of the portfolio integration to complete service (real, digital, virtual world... complex) tasks and/or actions, for example, an organization development service integration involving structuring one to several entity(s), where said entity(s) are to be formed in various states/provinces/countries/regions, could include all formations, association, agent registration, IRS/State (or similar filings), etc. including paying related fees and organizing digital contacts and documents.
  • a second example can include a possibly Al assisted real world gaming portfolio integration that would include (real, digital, virtual, etc.) encoded game pieces; game participant peer-to-peer user account to interactive games services; and in addition to standard game pieces would have encoded game pieces to interactive games services to make available different types of (online integrated and/or real- world) gaming experiences.
  • a third example can include fortune cookie (live) integration that would involve fortune cookies with QR code configured fortunes inside, that when scanned by regular method provides basic fortune but when scanned using live scanning as discussed herein provides one or more much-expanded fortune benefits. The basic fortune may communicate to the holder this benefit and offer instant download of the app with referral tracking linked back to the supplier(s).
  • the system can provide for restricted integrations.
  • restricted integrations the system can provide restrictions operations that user accounts can perform on the integrations. For example, restrictions can prohibit some user accounts from performing operations such as scanning to receive a specified restricted integration, shopping for a restricted integration, and/or accepting a restricted integration. These restrictions may be applied at different levels, such as a level of a device, a level of a user account, a level of a node in the service data structure, etc. Additional features and concepts related to integrations are discussed elsewhere in this application.
  • some user interface controls can be context-sensitive so that they iterate to perform different operations as a user interface display moves between nodes of a data structure such as a hierarchical service data structure. Indeed, multiple such controls may be provided in a single display. Additionally, the same control or group of controls can iterate to respond to user input selection of the controls by performing different and appropriate operations in different types of structures, including different types of integrations. For example, one or more user interface controls may iterate to provide one operation responsive to their selection for a contacts node in a contacts structure of a hierarchical services data structure and another operation responsive to their selection in a portfolio data structure. Also, the context-sensitive operations provided in response to selection of the user interface controls can utilize rolled up data including rolled up records. This concept will be discussed more below with regard to particular examples of context-sensitive user interface controls.
  • QR codes Some users of codes such as QR codes may be using codes that are reserved by online code service providers, and those service providers may be maintaining information related to those codes.
  • an online service provider may be providing a service to maintain a uniform resource locator that is related to a code that a user has included in a coded thing 110 (or multiple coded things) owned by that user. But that user may want to use a different service for maintaining that code.
  • a code may be maintained by a third-party subsystem 196, but the user may have a user account 164 with the service subsystem 150 and may want to use the service subsystem 150 to provide services linked to that code and the associated encoded thing 110.
  • the service subsystem 150 and the third-party subsystem 196 can synchronize with each other, such as using application programming interface calls or some other communication technique.
  • the third-party subsystem 196 can communicate the change to the service subsystem 150, and the service subsystem 150 can update the associated data for the code that is linked to the user account 164 in the service subsystem 150.
  • the service subsystem 150 can communicate the change to the third- party subsystem 196, and the third-party subsystem 196 can update the associated data for the code that is linked to the user’s account in the third-party subsystem 196.
  • the subsystems can respond to user input by coordinating a transfer of the records for managing the code from one subsystem to another.
  • the user 132 can provide user input to the service subsystem 150, requesting that its record(s) for the code be transferred to the third-party subsystem 196.
  • the service subsystem 150 can identify such records and send them in one or more communications to the third-party subsystem 196.
  • the third-party subsystem 196 can then incorporate the received records into the third-party subsystem 196 to provide code-enabled services linked to that code.
  • the service subsystem 150 and/or the third-party subsystem 196 can communicate with that standard system to indicate that the hosting of the code is being or has been transferred from the service subsystem 150 to the third-party subsystem 196.
  • the code can be scanned and entered into the new system, along with providing user input requesting that the code hosting be transferred or shared between hosts, allowing the code to be stored and used in a code managing and/or use integration in the new subsystem.
  • a mobile device 3800 can include a display 3810 that is displaying an outline 3820, such as an outline with entries that represent nodes in a hierarchical data structure, such as a hierarchical service data structure.
  • the outline includes entries representing nodes at different levels of the hierarchy.
  • Each entry includes a user interface control on the left side indicating whether that entry is collapsed or expanded. For an expanded entry (indicated by a user interface control indicator to its left), the entry is expanded. In response to user input selection of that user interface control, a single level below that entry can be hidden so that the entry is considered to be partially collapsed.
  • all nodes below that entry can be hidden in response to user input selection of that user interface control so that the entry is considered to be completely collapsed.
  • a single level below the corresponding entry can be revealed so that the entry is considered to be at least partially expanded (which could be partially expanded and partially collapsed if the entries below that entry in the hierarchy include one or more hidden entries and one or more displayed entries).
  • all nodes below that entry can be revealed in response to user input selection of that “+” user interface control so that the entry is considered to be completely expanded.
  • the system can respond by expanding the entry as requested and also collapsing one or more other entries to keep the outline within the available width of the display. This can include collapsing entries above the entry that was requested to be expanded.
  • the outline 3820 includes a TOP NODE entry that is the top-most entry in the outline (representing a highest node such as a root node in a hierarchical data structure, or a node at or below a current node corresponding to the display). Below the TOP NODE entry is a NODE 1 LEVEL 1 entry and a NODE 2 LEVEL 2 entry.
  • the NODE 2 LEVEL 1 entry is completely collapsed, and the NODE 1 LEVEL 1 entry is partially expanded, with displayed entries NODE 1 LEVEL 2 at a next level below the NODE 1 LEVEL 1 entry, and a NODE 1 LEVEL 3 entry below the NODE 1 LEVEL 2 entry.
  • the outline also includes a NODE 1 LEVEL 4 entry and a NODE 2 LEVEL 4 entry below the NODE 1 LEVEL 3 entry.
  • the NODE 2 LEVEL 4 entry includes a “+” user interface control indicating that entry is collapsed.
  • NODE 2 LEVEL 4 entry user input may be provided to expand that NODE 2 LEVEL 4 entry.
  • the system can expand the NODE 2 LEVEL 4 entry, revealing an entry below the NODE 2 LEVEL 4 entry, as illustrated in Fig. 39.
  • the system can also analyze the display when preparing to re-render the display after the expanding user input, determining that the requested expansion will result in the outline extending beyond the available width of the display. Accordingly, the system can respond by collapsing another entry.
  • Fig. 39 user input may be provided to expand that NODE 2 LEVEL 4 entry.
  • the system has partially collapsed the NODE 1 LEVEL 1 entry by hiding the NODE 1 LEVEL 2 entry and moving the entries below the NODE 1 LEVEL 1 entry to the side (to the left in the example), thereby providing room for the newly revealed NODE 1 LEVEL 5 entry below the NODE 2 LEVEL 4 entry.
  • the responsively collapsed entry is an ancestor above the entry to be expanded.
  • the system could responsively collapse an entry that is a descendant below the entry to be expanded in some situations where there are partially expanded entries already in the outline. For example, if user input requested expanding the NODE 1 LEVEL 1 entry, the system could respond by expanding that entry, but then re-collapsing the NODE 2 LEVEL 4 entry.
  • the system may also collapse some outline nodes in response to the system determining that there are not additional records represented by entries in other branches of the outline below those entries other than ones that are shown. For example, referring still to Fig. 38 and Fig. 39, if the only records in (i.e., descendants of) the node represented by NODE 1 LEVEL 3 are the ones in the node represented by NODE 1 LEVEL 5, then the system could collapse the outline between NODE 1 LEVEL 3 and NODE 1 LEVEL 5. This could result in NODE 1 LEVEL 5 being positioned directly below NODE 1 LEVEL 3. This can be done even if doing so is not necessary to keep the outline within the available width of the display. However, the outline could include a display (possibly after selecting a user interface control) to indicate the labels in the nodes that are hidden due to the automatic collapse.
  • This technique for responsive collapsing of a width-constrained outline can be applied to various different types of outlines displayed on computer screens where expanding and collapsing of entries in response to user input is provided and the available width of the display for the outline is limited. However, it can be particularly useful for outlines representing nodes in a services data structure as discussed herein. Indeed, this technique can overcome the uniquely computer-centric problem of such collapsible and expandable displayed outlines that tend to exceed the available width of a computer display for the outline.
  • the solution is technological advancement that uses computer functionality to provide a better user experience and reduce wasted resources in scrolling a computer display (horizontally and possibly vertically if the text for the entries is to be wrapped) when some currently expanded entries could be responsively collapsed by the computer system to avoid or reduce the need for such scrolling.
  • the computer system can perform this responsive collapsing with no added user input beyond the user input that requests the expansion of an entry that would have resulted in the outline exceeding the width of the display.
  • the responsive collapsing may be used in combination with other space-saving features such as text wrapping and text truncation for entries.
  • an account can have one or more profiles and possible other account data. That data can be used in various different locations in the system, such as in various different locations in a services data structure. It could be useful for a display to be provided to indicate which data is used in the system. However, to further include the account user’s control of their own data, a display can be provided with indications of the location(s) where a data unit or data unit group of the account data is being used in the system. And such indications can be provided for multiple different types of data. Referring now to Fig. 40, a mobile device 4000 includes an information display 4010 that is displaying data items of information from a user account, including indications 4020 of where in the system the corresponding data items of information are used.
  • the indications 4020 indicate that the BIRTH DATE data item in the user account is used in a system verification location, as well as in a HIGH SCHOOL FRIENDS GROUP (which can be a contact group), and by another user account with the name JOHN DOE.
  • the display can also include removal user interface controls 4030, which can be selected to remove the use from corresponding indicated locations.
  • the removal user interface controls 4030 to the right of the JOHN DOE list item in Fig. 40 could be selected to cease allowing the JOHN DOE user account to have access to the active user account’s birth date data item.
  • requesting that use of a data item cease may result in the system ceasing that data use, and it may also result in the user account losing access to some resources associated with that use.
  • a contact group integration may require access to birth data information to verify the age of corresponding users who are members of that contact group.
  • demanding that the group’s use of the birth date information cease can result in the user account losing access to that contact group.
  • the system can include an integration that can facilitate processing auditory and/or moving visual input for identification of codes.
  • This auditory and/or visual processing can be performed similarly to existing bot monitoring verbal commands and/or visual commands (e.g., visual user gestures).
  • the system can perform video, audio, biometric input, and/or frequency processing to identify patterns in the video, frequency, biometric input, and/or audio input that match predetermined audio and/or visual data that has been identified as commands.
  • Data regarding the patterns to be matched in the audio, frequency, biometric input, and/or video scanning can be stored in a code record in the service subsystem 150.
  • the processing may be determining whether the input matches a certain audio frequency or frequency of some other signal or a certain word or words structured in a predetermined way.
  • Such input could be identified as a code, and used as with other codes that are scanned, as discussed herein.
  • the pre-identified visual patterns to be identified as codes may include video sequences, visual patterns in a real time camera or a still photograph, or analysis of a video playing on a video display of a device other than the scanning device as seen by a camera of the scanning device.
  • the system may process video, frequency, biometric input, and/or audio input to scan for codes only while in a live mode, only while a services app 124 is running on a user device 120, or possibly at other times while the user device 120 is running, depending on settings, which may be modified by user input according to user privacy preferences. Indeed, for all operations discussed herein it may be helpful to consider and respect users’ desires for privacy and security regarding themselves and data regarding such users. This may be done in various different ways.
  • a bot as discussed herein can be included in an integration or operate in conjunction with an integration to identify audible commands, frequency commands, biometric input, and/or visible gestures and other visual input for commands to perform bot functions such as functions performed by chat bots.
  • the visual, frequency, biometric input, and/or audio scanning discussed herein may be performed by a dedicated user device 120 and/or as one or more software and/or hardware components integrated into another user device.
  • the system can constantly monitor for an auditory, frequency, biometric input, and/or video code and alert now and/or organize/store for quick access later the auditory, frequency, biometric input, and/or video code related data such as labeled date which could include a uniform resource locator.
  • a video, audio, and/or frequency-based broadcast with a possibly constant integrated code can dynamically update moment to moment (e.g., frame by frame) to provide related in the moment information/actions upon a visual and/or auditory scan of the broadcast.
  • a product placement advertisement moment in a movie may open a related information site upon scanning to recognize the code.
  • An embedded code can be any visual or transmitted code, including moment-to-moment, video frames, transmitted frequency durations, etc.
  • Such codes may also include images/pictures; on-location (real/virtual world) image captured scenes, and/or some scenes incorporating identifiable landmarks.
  • a user device may combine input from its location system with visual input to identify and/or verify a landmark that is to be used as a code upon scanning.
  • a live scanner can perform biometric scanning, where a biometric feature of a user can be a code for which a device is scanning.
  • a biometric feature of a user can be a code for which a device is scanning.
  • a device can perform facial recognition or an iris scan
  • a fingerprint scanner can perform a fingerprint scan, etc.
  • a scan matches a pattern for a code stored in the system, then in response, services linked to that code in the system can be performed by the system, as with other codes discussed herein.
  • a mobile device 4100 can include a root node display 4110, which can be a node display like the record wallet displays discussed above.
  • the root node display 4110 can include a location indicator 4120 in the header that can indicate the current location, which can be a node referred to in the example as “My ObDEX,” which can be a reference to a root node, or highest node, in the hierarchical services data structure for the active user account. However, an account node and possibly other nodes may be above this “My ObDEX” node.
  • the root node display 4110 can include option user interface controls 4125, which can be context sensitive.
  • the option user interface controls 4125 can be selected to prompt the system to invoke option integrations to perform processes that can adapt to different node locations corresponding to the user interface displays where the option user interface controls can be displayed for selection by user input.
  • Different sets of option 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.
  • the option user interface controls 4125 can include user interface controls in a header 4127 (which can include the option user interface controls 4125 and the location indicator 4120).
  • the header 4127 can be included in all the displays as either the multi-level header of Fig. 41, or as a single level header illustrated in some other figures, such as the single level header of Fig. 41. In either case, the header 4127 can include one or more option user interface controls 4125.
  • the option user interface controls 4125 can include a live user interface control 4130. In response to selection of the live user interface control, the system can invoke a live integration and display a live display, such as one which will be discussed more below. Additionally, the option user interface controls 4125 can include an action user interface control 4135, which can be selected to invoke an action integration and display an action display, such as one which will be discussed more below. Additionally, the option user interface controls 4125 can include an option integration user interface control 4140, which can be selected to invoke an option integration and display an option display, such as one which will be discussed more below. The option user interface controls 4125 can include a communication integration user interface control 4145, which can be selected to invoke a communication integration and display a communication display.
  • the communication display can display communications, such as communications between the current user account and other user accounts.
  • the communications can include communications linked to the current node (the root node in the example of the root node display 4110).
  • the communications may be communications with links to the current node or nodes below the current node (which could be all communications in the example of the root node being the current node).
  • the communications could be communications with user accounts that have roles that give them permissions for the current node, such as viewers, members, or administrators (host, editor, moderator, etc.). Each of these roles (and possibly other roles) can have sets of permissions that may be set and altered in settings.
  • the option user interface controls 4125 can include an interactive calendar user interface control 4150, which can be selected to invoke an interactive calendar integration and display an interactive calendar display.
  • the interactive calendar display can display calendar information for interactive calendaring, such as interactive calendaring of events, tasks, or other calendar items that involve multiple user accounts, such as calendaring between user accounts with roles that are linked to the current node and/or nodes below the current node where the interactive calendar user interface control 4150 is selected.
  • the option user interface controls 4125 can also include a marketplace integrations user interface control 4155, which can be selected to invoke an integration for management of the current user account’s marketplace integrations and display an integration management display such as the marketplace integrations display, which is discussed more below.
  • the option user interface controls 4125 can also include a search user interface control 4160, which can be selected to invoke a search integration and display a search display.
  • the search user interface control can be a text box in which search terms may be entered to perform a search and reveal the search display or a button that may be selected to move the user interface display to the search display.
  • the search display 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 in the search results may be selected to reveal additional data about list items, such as by moving the user interface display to a node represented by a search list item.
  • the option user interface controls 4125 can also include a settings user interface control 4165, which can be selected to invoke a settings integration and display a settings display.
  • the settings display can display settings for the current node.
  • the settings may include user interface controls for the settings, allowing user input from the current user account to prompt the settings integration to change the settings for the current node.
  • Settings that are changed for the current node may apply to the current node, and by default such settings may also apply to nodes below the current node.
  • settings applied in nodes below the current node may override those defaults for the nodes in which they are applied (and possibly by default to nodes below the nodes in which they are applied).
  • other techniques may be used for applying settings in some implementations, such as having a setting only apply to the current node and not to nodes below the current node.
  • the option user interface controls 4125 can also include a marketplace button 4170, which can be selected to invoke the marketplace integration and display the add marketplace integrations display allowing the current user account to view and register for marketplace integrations applicable at the current level, which will be discussed more below.
  • the option user interface controls 4125 can also include a navigate button 4172, which can be selected to display a navigation display, which will be discussed more below.
  • the option user interface controls 4125 can also include a structure user interface control 4174, which can be selected to toggle between a node display as in the root node display 4110 and a structure display, which will be discussed more below.
  • the structure user interface control 4174 can change to indicate whether the current display is a structure display. For example, in Fig. 41, the structure user interface control 4174 is darkened, indicating that the current display is not a structure display. However, in other figures such as Fig. 53, the structure user interface control 4174 can be filled in light indicating that the current display is a structure display.
  • the root node display 4110 can also display node list items 4176 for nodes directly below the current node.
  • Each such list item can include a structure user interface control 4178, which can be selected to display a structure display, which will be discussed more below.
  • Each structure user interface control can be displayed as an icon that can be different for different types of structures at the indicated node and below that node.
  • An icon with no border or solid fill in the icon can indicate a fixed structure where the current user account does not have permission to include new integrations or change the structure.
  • An icon that is filled in (with black in the drawings) can indicate a flex open structure, where the current user account has permission to include new integrations and change the structure.
  • An icon that is not filled in and does not have a border can indicate a flex closed structure, where the current user account can choose and/or change some things within the structure but is constrained in what the current user account can do in terms of including new integrations and/or changing structure (for example, the current user account may be able to include new integrations as specified, but not change the structure).
  • the displays a multilevel hierarchy structure this indicates that not everything is rolling up to the current level (for example, some data may roll up to the current level, but records may not roll up to the current level).
  • a structure icon only includes a single level hierarchy (indicated by three squares arranged horizontally without another square above them, as indicated in structure icons in Fig.
  • this can indicate a rollup structure, such as structure where data and records can roll up to the corresponding node indicated in the list item.
  • a rollup structure such as structure where data and records can roll up to the corresponding node indicated in the list item.
  • icons and their indications can apply to the structure user interface control 4174 for the current level and the structure user interface controls in node list items 4176. They can also apply for similar list items in other displays discussed herein.
  • Each list item of the node list items 4176 can also include a number indicated by the “[n]” in each list item, which can include a number for the indicated node, such as indicating a number representing how many records are at or below that indicated node.
  • Each list item can also include a title 4180, which can also be part of a user interface control that can be selected to move the user interface display to the node display for the indicated node (a display that can be similar to Fig. 41, but for the indicated node instead of the root node of Fig. 41).
  • At least some of the list items can also include an access user interface control 4182, which can be selected to access records such as integrations for the listed node (records that are immediately below the listed node in the hierarchy).
  • selection of the access user interface control 4182 can move the user interface display directly to that record. If there are multiple records for the node represented by the list item, then selection of the access user interface control 4182 can move the user interface display to a listing of user interface controls to access those records. If there are no records for the listed node or the access point to those records has not been set
  • an access setup user interface control 4184 may be displayed instead of the access user interface control 4182.
  • a profile may be automatically set for the access point, or one may be selected and/or entered by user input as part of the access point setup for a user account at a particular access point.
  • the process could include receiving a user input access point request from a user account for an access point to a service integration that is not fully set up (i.e., where the access point is not fully set up).
  • the process could also include determining that a profile from the user account is to be used in setting up the access point.
  • the process can include identifying a profile for use by the service integration and setting the identified profile for the access point as part of setting up the access point.
  • Identifying the profile may include determining that neither a fixed profile nor a custom profile has been designated to be set for the access point, and setting a default profile as the identified profile for the access point.
  • the default profile may be a public profile or a non-public profile.
  • the identified profile may be an existing profile identified or entered by user input and/or a system generated profile (such as where the system responds by choosing a default profile such as a public profile, or the system responds by generating a required profile (such as by generating a specific required profile by identifying and using corresponding data from other profiles from the same user account) for the access point).
  • the node list items 4176 can include a My Profile list item, which can be selected to invoke a profile integration and display a portfolio display for the current user account, which will be discussed more below.
  • the node list items 4176 can also include a My Contacts list item, which can be selected to invoke a contacts integration and display a contacts page for contacts, which will be discussed more below.
  • the node list items 4176 can also include a My Calendar list item, which can be selected to invoke a calendar integration and display a calendar display for the current user account.
  • the node list items 4176 can also include a My Portfolio list item, which can be selected to invoke a portfolio integration and display a portfolio display for the current user account.
  • the My Portfolio structure can be a structure that the current user account has created and generated, so the current user account may have permissions to revise the structure including the structure of categories within My Portfolio and to include and remove integrations in that structure.
  • the node list items 4176 can also include a My Shared Portfolio list item, which can be selected to invoke a portfolio integration and display a portfolio display for parts of the current user account’ s portfolio that are shared with other user accounts (including with groups of user accounts, such as contact groups).
  • the current user account can also have permissions to change structure and build structure within the My Shared Portfolio structure.
  • Provider Portfolio at this top functional level, which can include integrations that can be used with the current user account and providers, such as the doctor example discussed above, where an integration can allow the doctor to share patient information with the user account using an integration.
  • Such an integration and other provider integrations can be integrated in the Provider Portfolio for the user account.
  • My Shared Marketplace Portfolio which could be specifically and functionally tailored to user account provided or built integrations that provide shopping services, so that they are intended for user accounts to browse and/or shop.
  • a user account can share portfolios and parts of portfolios (such as integrations within portfolios or even services within integrations in portfolios) with other user accounts in the system.
  • the user account can also transfer portfolios to other user accounts in the system.
  • sharing or transferring occurs, the structure of the shared or transferred portfolio (or the part of it that is shared) can be maintained and be transferred or shared with the portfolio.
  • the node list items 4176 can also include a My Network Portfolio list item, which can be selected to invoke a portfolio integration and display a portfolio display that can be automatically built by the system based on the current user account’s network, such as based on links of the current user account to other user accounts, such as user accounts for organizations that have networks that can use integrations associated with the organizations.
  • a university may maintain an integration that can be used by students at the university, another integration that can be used by alumni of the university, and another integration that can be used by faculty of the university. If the current user account is an alumnus of the university, the user account’s My Network Portfolio can automatically include the university’s alumni integration so that the user account can access and use services from that university alumni integration.
  • An integration such as the alumni integration could have an administrator that manages the portfolio, such as an employee of the university or just an alumnus of the university.
  • Examples of network connections that could prompt inclusion in a network include colleges, previous or current workplaces, clubs, professional organizations, and user accounts with indications that they are in those networks could have possibly conditional verified or unverified access to the corresponding integrations that provide services for user accounts in those networks.
  • the node list items 4176 can also include a Portfolio, As Member list item, which can be selected to invoke a portfolio integration and display a portfolio display that can include portfolios, including portfolio integrations, where the current user account is assigned with the role of a member, having associated permissions for members of those portfolios.
  • the node list items 4176 can also include a Portfolio, As Admin list item, which can be selected to invoke a portfolio integration and display a portfolio display that can include portfolios, including portfolio integrations, where the current user account is assigned with the role of a type of administrator, having associated permissions for that type of administrator, such as a host, editor, moderator, or some other administrator roll.
  • user input may be provided to drill down into the node represented by the list item by selecting the title 4180, to access records for the node represented by the list item by selecting an access user interface control 4182 (or setting up an access point to produce an access user interface control 4182 for that list item in the future by selecting the access setup user interface control 4184), or user input can be provided to reveal a display of the structure of the node represented by the list item (including the structure of nodes below that list item) by selecting the structure user interface control 4178 for that list item.
  • a user input selection of the navigate button 4172 can prompt the system to display the navigation display 4210 illustrated in Fig. 42.
  • the navigation display 4210 for the root node can include a location indicator 4220, which can indicate the current node being represented and also indicate that the current display is a navigation display.
  • the navigation display 4210 can include the option user interface controls 4125, but it may include a different set of the option user interface controls 4125.
  • the option user interface controls 4125 can include the live user interface control 4130 and the action user interface control 4135.
  • the navigation display 4210 can also include a shortcuts user interface control 4230, which can be selected by user input to prompt the system to display a shortcuts display that can display list items of shortcuts to different locations, such as different displays and/or different nodes.
  • Such shortcuts can be set by selecting a user interface control to set a shortcut as is discussed in an example below.
  • Other convenient navigation-based features similar to the shortcut feature can be added or turned on via account settings.
  • another navigation feature may be “Most Accessed” list and associated user control for accessing the list, which can provide a list of most frequently accessed locations for the current user account.
  • the list of shortcuts and the My Information list discussed herein can include data that has rolled up to the current level, so that they include data from the current node and its descendants.
  • the navigation display 4210 can also include an information user interface control 4235, which can be selected to display an information display, such as a display like the information display 4010 of Fig. 40, which can display data from the current user account.
  • an information user interface control 4235 can be selected to display an information display, such as a display like the information display 4010 of Fig. 40, which can display data from the current user account.
  • the navigation display 4210 can also include node list items 4240 for the current node and ancestor nodes above the current node (with the current node being the root node in this example, no nodes above the current node are listed).
  • Each of the node list items 4240 may be similar to the node list items 4176 discussed above with reference to Fig. 41.
  • the node list item for the root node (My ObDEX) may not include records at the root node level, so there may not be an access user interface control like the access user interface control 4182 discussed above. Also, there may not be any available access points to set up, so the access setup user interface control may also be omitted from the list item.
  • the navigation display 4210 can also include an account user interface control
  • the account management display can display data from the current account.
  • the account management may be structured to include multiple nodes and displays for different features in the account.
  • the account management integration can also modify the current account in response to user input for modifiable portions of the account.
  • the account management integration can have associated integrations such as options integrations that can provide services to the account management integration to enhance its functionality.
  • the navigation display 4210 can also include a public profile user interface control 4250, which can be selected to preview and/or modify a public profile for the current user account.
  • the public profile can be a profile that can be viewed by all user accounts in the system.
  • a user account can also have one or more other profiles that can be shared in different locations in the hierarchical service data structure.
  • Selection of the marketplace button 4170 from a display such as the root node display 4110 can prompt the system to invoke a marketplace integration to display an add marketplace integrations display 4310 such as the add marketplace integrations display 4310 of Fig. 43.
  • the add marketplace integrations display 4310 can include a location indicator 4320 indicating the display is an add marketplace integrations display.
  • the location indicator may also indicate a corresponding current node because the marketplace integration (which is an integration for adding or registering for other integrations for the current user account) can be context sensitive.
  • the add marketplace integrations display 4310 may only list available integrations that are applicable to the current corresponding node (such as a portfolio node or a contacts node, and possibly also those applicable to nodes below the current node) from which the marketplace integration was invoked.
  • the add marketplace integrations display 4310 can include option user interface controls 4125. Additionally, the add marketplace integrations display 4310 can include available integrations list items 4330. The available integrations list items 4330 can each include a register user interface control 4335 and a register later user interface control 4340. A register user interface control 4335 can be selected by user input to initiate a process to register a corresponding integration, adding that integration into the structure for the current user account.
  • This registration process can include collecting information from user input and/or from existing information associated with the user account. For example, a user profile for the user account may be selected or created for use with the new integration. Also, settings for the integration may be set. As part of the registration process, access points for the new integration may also be set up. The new integration can then be integrated into the hierarchical structure for the user account, allowing the new integration to be used to provide services for the user account such as via a services manager.
  • the add marketplace integrations display 4310 can also include an exit user interface control 4345, which can be selected to exit the marketplace integration and return to the display from which the user interface display entered the marketplace integration.
  • the add marketplace integrations display 4310 can include a save user interface control 4350, which can be selected to save changes that have been made while in the marketplace integration. For example, this could include saving selections of integrations to be added (such as by selecting the register user interface control 4335 or register later user interface control 4340 for registering listed registrations now or later). This could also include saving selections and input made during registration of one or mor new integrations to be added for the current user account.
  • the add marketplace integrations display 4310 can also include a continue user interface control 4355, which can be selected to continue, such as initiating a selected registration process or continuing with a current registration process that has already begun.
  • a continue user interface control 4355 which can be selected to continue, such as initiating a selected registration process or continuing with a current registration process that has already begun.
  • an options display 4410 will be discussed.
  • the options display can be displayed in response to user input selecting the option integration user interface control 4140 in another display to invoke the options integration, which can manage the options display.
  • the options display 4410 can include many of the same user interface controls as in the displays discussed above. Those corresponding types of user interface controls will not be discussed again here. However, the options display 4410 can also include some types of user interface controls not discussed above.
  • the options display 4410 can include an experience selection user interface control 4430, which can be selected to choose from a selection of different experience types for viewing and managing the data and services provided by the listed options from the options display 4410.
  • the experience selection user interface control 4430 and similar selection user interface controls discussed herein can be selectable to invoke option types of integrations that can be context-sensitive (i.e., an option type of integration can be used in managing the experience selection user interface control 4430).
  • such integrations may provide functions such as sorting, searching, and filtering the selections provided in the selection user interface control.
  • experience types could include experiencing as the current user account (My User Experience, as listed in Fig. 44), or as a set type of permissions role, such as experienced as a viewer, as a member, as a host, as a moderator, etc.
  • the options display 4410 can also include a back button 4440 that can be selected to return to a previous display.
  • the options display 4410 can include a set shortcut button 4445 that can be selected (displaying in a select-on state) to prompt the system to add the current display as a shortcut on the My Shortcuts list of shortcuts.
  • the options display 4410 can also include options list items 4450 of corresponding option integrations (also called “options” herein), which can be list items like the node list items 4176 discussed above.
  • each list item in the options list items 4450 may include either a structure user interface control 4178 or a access user interface control 4182 as appropriate for the particular list item and the corresponding particular option integration (with the access user interface control 4182 providing direct record access and the structure user interface control 4178 providing a structure display for the corresponding option integration).
  • the Communications list item can be selected to invoke a communications display, as discussed above with reference to the communication integration user interface control 4145 of Fig. 41.
  • the Communications list item can include a highlighted star icon indicating that a corresponding user interface control is included in the option user interface controls 4125 at the top of the display (and possibly indicating the corresponding user interface control will be included at the same location on other displays).
  • the list items with star icons that are not highlighted can indicate that the corresponding user interface controls are not listed in the option user interface controls 4125 at the top of the display (and possibly indicating the corresponding user interface control will not be included at the same location on other displays).
  • the set of option user interface controls 4125 at the top of displays can be automatically set by the system.
  • user input may be provided to select which option user interface controls 4125 are displayed in the set of option user interface controls 4125 at the top of displays.
  • user input may be provided by selecting a non-highlighted star icon to highlight the icon and include the corresponding user interface control in the option user interface controls 4125 at the top of the display(s), and user input may be provided by selecting a highlighted star icon to remove the highlighting and exclude the corresponding user interface control from the option user interface controls 4125 at the top of the display(s).
  • the options list items 4450 can also include an
  • Interactive Calendar list item that can correspond to the interactive calendar user interface control 4150 discussed above with reference to Fig. 41.
  • the options list items 4450 can include a Marketplace Integrations list item, which can correspond to the marketplace integrations user interface control 4155 discussed above with reference to Fig. 41.
  • the options list items 4450 can also include a Support list item, which can be selected to invoke a support integration to facilitate user input requests for support.
  • the support request can be tailored to the node from which they are sent. For example, if this options display 4410 was invoked from a display corresponding to node “N”, then the support integration can facilitate a communication with a user account that is assigned to provide support for node “N”. For example, this may be a user account assigned as a host or other type of administrator role for node N.
  • the provided support communications could include messages, audio calls, video calls, live chats, etc.
  • the option user interface controls 4125 can also include a Data list item, which can be selected to invoke a data integration to provide data services, such as displaying data itself and/or data analytics. Such data services can be provided for data in the current node and nodes below the current node (i.e., the data can roll up to the current node for use in the data integration).
  • the option user interface controls 4125 can also include a metering list item, which can be selected to invoke a metering integration to provide metering services, such as displaying metering calculation results and other metering values and related data. Metering will be discussed more below with reference to a metering display.
  • the option user interface controls 4125 can also include an assign integrations list item, which can be selected to invoke an assignment integration to facilitate the assignment of integrations.
  • this can include assigning integrations, such as transferring, sending, or sharing integrations.
  • assigning may include transferring or sending an integration from one user account to another, along with that integration’s structure. It may also include sharing an integration between multiple user accounts.
  • Fig. 45 another options display 4510 is displayed.
  • the options display 4510 can be like the options display 4410 discussed above with reference to Fig. 44.
  • the options display 4510 can include a different set of options list items 4550.
  • the options display 4510 may be a screen displayed after scrolling down in the options display 4410 and changing the experience selection user interface control 4430 to “As Experienced by a Member.”
  • the options list items 4550 of Fig. 45 can include a Searchable Access list item, which can be selected to invoke a searchable access integration that can allow searchable access to contacts links such as access to the current node and nodes below the current node.
  • the searchable access integration can allow for drilling down into the structure below the current node to refine the contacts revealed by the searchable access integration.
  • the contacts and associated user profiles (as available to the current user account) for such contacts can be listed in a structured manner in the contacts display discussed below.
  • the different set of options list items 4550 can also include an Associated Contacts list item, which can be selected to invoke an associated contacts integration.
  • the associated contacts integration can list and provide access to profile data for contacts that are associated with the current user account through the current node or nodes below the current node, such as where the user accounts for the associated contacts are assigned roles such as administrator roles for the current node and/or nodes below the current node.
  • the associated contacts integration may provide for drilling down into the structures below the current node to refine the contacts listed by the associated contacts integration.
  • the different set of options list items 4550 can also include an Experience Options list item that can be selected to invoke an experience options integration.
  • the experience options integration can allow user input to select a permissions role (as a viewer, as a member, as an administrator (for example, as a host, as a moderator, as an editor), etc.). This can allow the current user account to experience the current node and nodes below the current node as if the current user had a different level of permissions than the current user account actually has.
  • the current user account may be an owner of the current node, but the current user could select to experience as a member, and then the experience options integration can modify the experience of the user account in using the current node and nodes below it to be as if the user account were a member rather than an owner for the current node. As an example, this may be done for settings where settings may be modified.
  • the different set of options list items 4550 can also include a Shared Profile list item that can be selected to invoke a shared profile integration.
  • the system can allow a user account to create multiple custom profiles and/or form profiles to be shared with different parts of the hierarchical structure.
  • the shared profile integration can allow access to profiles that the current user account has shared via the user account’ s links to nodes in the system that include the current node and links below the current node. This can include drilling down into the integration hierarchy to see what profiles are shared at different levels of the hierarchy at the current node and below. Additionally, in this drilling down or elsewhere, user interface controls and associated functions can be provided to set a profile solely related to the current level.
  • the set of options list items 4550 can also include a Related Structures list item, which can be selected to invoke a related structures integration.
  • the related structures integration can be invoked to display representations of portfolio structures, record structures, services (which can include structures), etc. that are related or linked to the current node and nodes below the current node.
  • the set of options list items 4550 can also include a Records Access list item, which can be selected to invoke a records access integration.
  • the records access integration can provide direct access to records. This may include going directly to a record or providing list items of records (such as service records) that allow selection of a list item to gain direct access to the record.
  • the set of options list items 4550 can also include a Service Access list item, which can be selected to invoke a service access integration.
  • the service access integration can be similar to the records access integration, but the service access integration can provide access to a record manager for a service record corresponding to a service.
  • a structure display 4610 is illustrated for a My Portfolio node with a location indicator 4620.
  • this page may be displayed in response to user input selecting the structure user interface control 4178 of the My Portfolio list item in the node list items 4176 of Fig. 41.
  • the structure display 4610 can include a structure representation of the hierarchy of the current node and nodes below the current node, such as in the form of the outline 4630 illustrated in Fig. 46.
  • These nodes may include portfolio integration nodes, which can include organizational type nodes and service nodes.
  • the outline 4630 can include a list item for the current node and each node below the current node.
  • the outline 4630 can also indicate which of the nodes includes one or more records that can be directly accessed at that level through an access point, and an access user interface control 4635 can be included for selection to access the corresponding record(s). That is commonly the case for bottom level nodes (nodes without other nodes below them in the hierarchy of the outline 4630, although even such nodes may include hierarchical structures within them).
  • the outline 4630 can include the responsive collapsing features discussed above as well as collapse and expand user interface controls 4640 for collapsing and expanding in response specific user input requests.
  • the structure display 4610 can include some option 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 a My Portfolio node display similar to the root node display 4110.
  • the system can begin an access process for accessing the requested records. If the access point is set up, this can result in direct access to the record or a list of accessible records for the ACME CORP node. If the access point is not completely set up, this can result in the display of an access setup display such as the access setup display 4710 illustrated in Fig. 47.
  • the access setup display 4710 can include a location indicator 4720 and option user interface controls 4125, which may include user interface controls as in Fig. 41.
  • the access setup display can also include an exit user interface control 4345, a save user interface control 4350, and a continue user interface control 4355.
  • an area labeled NODE DEPENDENT OPTIONS or CONTEXT OPTIONS indicates the presence of option user interface controls 4125, but without specific which option user interface controls are included because different user interface controls can be included depending on location in the system and possibly depending on other factors such as user preferences.
  • controls for invoking option integrations such as those listed in
  • the access setup display 4710 can include an input information area 4730, which can include displayed information regarding the access, such as information about an integration being accessed.
  • the input information area 4730 can also include user interface controls to input information for setting up the access point.
  • input information may include providing a pre-existing or newly created profile for the user account to be used in an integration being accessed through the access point.
  • Other examples include providing verification of information and settings preferences to be used in an integration being accessed through the access point.
  • the user account may be provided with access to the requested resource, such as the requested record, which can be an integration.
  • a marketplace integrations display 4810 will be discussed.
  • the marketplace integrations display 4810 may be displayed in response to user input selecting the marketplace integrations user interface control 4155 of Fig. 41.
  • the marketplace integrations display 4810 can include a location indicator 4820, which can indicate that the location of the current display is at a node in the system for the current user’s marketplace integrations, which can be integrations from or for the system marketplace with connections to the current user account.
  • the marketplace integrations display 4810 can also include user interface controls like those discussed above, including option user interface controls 4125, a back button 4440, a navigate button 4172, a marketplace button 4170, and a set shortcut button 4445.
  • the marketplace integrations display 4810 can also include my marketplace integrations list items 4850 for the current user account.
  • Each list item can include a structure user interface control 4178 and an indicator of numbers of records (indicated by “[n]”).
  • each of the marketplace integrations list items 4850 can include a title 4180.
  • the structure user interface controls 4178 all indicate that the listed node is a records-level node (see the differences in the icons in Fig. 48 and other figures such as Fig. 41). In this case, selection of the structure user interface control 4178 can prompt the system to display a node display for indicated node. Selection of the title 4180 can also prompt the system to display a node display for the indicated node, which can list nodes below that node.
  • the marketplace integrations list items 4850 can include an “ObDEX” Integrations list item, which can be selected to access list items of integrations and integrations themselves that are available from the marketplace.
  • the marketplace integrations list items 4850 can also include a My ObDEX Integrations list item, which can be selected to access list items of integrations and integrations themselves from the marketplace for which the current user account has registered.
  • the My Integrations Workshop can be selected to access list items of integrations and integrations themselves that the current user account is working on, such as integrations the current user account is in the process of building.
  • the user account may add the integration to be used by the current user account and/or other user accounts. For example, the user account may add a completed integration into the controlled integrations structure indicated by the My Controlled Integrations list item in the marketplace integrations list items 4850, which can allow the current user account to control the integration.
  • the user account may add it built integration into the marketplace, allowing all other user accounts to register to use it.
  • the current user account may only allow some subset of users to register for a created integration, such as only user accounts with whom the current user account directly shares the integration, user accounts in contact groups that the current user account specifies, etc.
  • the user account may share control with one or more other user accounts, giving those user accounts permission roles for the integration such as administrator rolls (e.g., a roll as a co- host of the integration or a co-owner of the integration).
  • Such integrations where control of the integration is shared between the current user account and one or more other user accounts may be accessed by selecting the Shared Control Integrations list item in the marketplace integrations list items 4850.
  • the marketplace integrations list items 4850 can also include an Integrations Pending Setup (Review) list item, which can be selected to review and continue registering for integrations for which the current user account has started a registration process but not finished it, or for which the current user account has indicated that it will register for the integration later but has not yet completed the registration.
  • Review Integrations Pending Setup
  • integrations can roll up to the level of the indicated node, so that such integrations from the indicated node and its descendants can be viewed at the level of the indicated node.
  • ObDEX integrations display 4910 may be displayed in response to user input selecting the ObDEX Integrations list item title from the marketplace integrations display 4810 of Fig. 48.
  • the ObDEX integrations display 4910 can include a location indicator 4920, which can indicate that the location of the current display is at a node in the system for the current user’s marketplace integrations, which can be integrations from or for the system marketplace with connections to the current user account.
  • the ObDEX integrations display 4910 can also include user interface controls like those discussed above, including option user interface controls 4125, a back button 4440, a navigate button 4172, a marketplace button 4170, and a set shortcut button 4445.
  • the structure user interface control 4174 in Fig. 49 can include three squares instead of its normal multi-level structure icon, indicating that the structure user interface control 4174 is not selectable in this display.
  • the ObDEX integrations display 4910 can also include ObDEX integrations list items 4950 for the current ObDEX integrations node.
  • the ObDEX integrations node can include list items of integrations that are available to be registered by user accounts.
  • each of the ObDEX integrations list items 4950 can be selected to initiate a registration process for the integration.
  • selecting the list item can result in the integration being invoked to provide one or more services as appropriate for the integration via a services manager.
  • selecting the list item could bring the user into a development environment for building the integration, which can be provided by a services manager.
  • the ObDEX integrations list items 4950 can include list items for different integrations that are available.
  • each list item can be represented by a tile, and some tiles can have different features, depending on the features made available for the tile and the represented integration.
  • the (Structure) Integration- 1 list item can include an area for information about the list item, images that are included for the list item, descriptions of the represented integration, and/or other displays related to the integration represented by the list item (see the area that says “ ⁇ Area for Info, Images, Description, etc. ⁇ .”
  • a list item may be simpler, such as in the (Structure) Integration-2 list item, which merely includes a title in the list item.
  • the indicated integrations could provide any of the services listed above, as appropriate.
  • list items can include other features.
  • the (Structure) Integration-n list item can include a structure user interface control 4178 like the structure user interface controls discussed above for other list items.
  • the structure user interface control 4178 can be selected to prompt the system to navigate to a display that provides an at- a-glance representation of the structure of the represented feature, in this case the integration labeled (Structure) Integration-n.
  • selection of the (Structure) Integration-n list item can make available the node locations under which the structure sits (i.e., the ancestor nodes of the structure of the represented feature).
  • the (Structure) Integration-n list item can also include a code share user interface control 4970.
  • the code share user interface control 4970 can be selected to prompt the system to display a code share display that can share a code, which other user accounts can scan via other user devices to prompt the system to navigate the other users to a display representing the referenced integration. This could include prompting the device receiving the code to log in with a user account via a services app 124 if they do not already have such an app active on the receiving device. Also, if they do not have a user account, the receiving user device could prompt the receiving device to install the services app 124 and create a user account. The user account could then be brought to the integration represented by the shared code. Also, integrations and list items for integrations can also be shared in other ways, such as by sending communications through the service subsystem 150 between user accounts in the system.
  • an integration manager display 5010 can be a service manager that can provide services to manage an integration. This can include providing development tools for building and/or modifying integrations, including the services provided by the integrations. Also, managers may provide tools for running and providing integration services, and services may be provided via an integration manager, or service manager.
  • the integration manager display 5010 represents a display provided by such a manager.
  • the integration manager display 5010 can include a location indicator 5020, which can indicate that the location of the current display is an integration manager for a current integration.
  • the integration manager display 5010 can also include user interface controls like those discussed above, including option user interface controls 4125, an exit user interface control 4345, a save user interface control 4350, and a continue user interface control 4355.
  • the integration manager display 5010 can also include a manager window 5050, which can be a display area that includes information and user interface controls for receiving output from the manager and providing input to the manager. The manager can run services in the manager window, such as by displaying service pages that are discussed above.
  • a user account and the manager may use the manager window to play a game, to interact with a chat board, or to engage in some other service.
  • a manager may also provide tools for building and/or modifying an integration including services provided within an integration, such as to modify service records and/or service pages to be used in providing services.
  • a current user account may need to have an appropriate permission role to be able to access the manager and/or to use specified functionality of the manager.
  • a user account may need to be a member of the integration.
  • a user account may need some particular level of administrator permissions (e.g., as a host, as a moderator, etc.).
  • user interface controls may be provided for the user account to request such access or permissions (e.g., for Records Manager access for the integration).
  • the registration process may automatically set a profile for the access, such as by selecting a default profile, or the registration process may require user input to create or select a profile for the access.
  • This can produce a profile for the access, which may include using a unique profile or using a profile such as a public or default profile that may also be used for other access points in the system.
  • the creation of a profile for an access point may involve including a link between the access point and an existing profile, such as a default profile that may be a public profile.
  • the identified profile for an access point may be an existing profile identified or entered by user input and/or a system generated profile (such as where the system responds by choosing a default profile such as a public profile, or the system responds by generating a required profile (such as by generating a specific required profile by identifying and using corresponding data from other profiles from the same user account) for the access point).
  • a system generated profile such as where the system responds by choosing a default profile such as a public profile, or the system responds by generating a required profile (such as by generating a specific required profile by identifying and using corresponding data from other profiles from the same user account) for the access point).
  • a metering display 5110 is illustrated.
  • the metering display 5110 can be displayed in response to selection of the metering option, as discussed above.
  • the metering display 5110 can include a location indicator 5120, which can indicate a current location, i.e., the metering display at the indicated current node or level (indicated by “CL” in the example of Fig. 51).
  • the metering display can also include the user interface controls that are common to some other displays, including the option user interface controls 4125, the back button 4440, the navigate button 4172, the marketplace button 4170, and the set shortcut button 4445.
  • the metering display 5110 can include metering list items 5150, which can list metering values indicating parameters that are being metered and other related values.
  • the metering (billing) integration represented by the live display 5110 can manage and/or track in-system and third-party system and/or account related inbound and/or outbound metered resource transactions. Data can roll up to the current node and be used in analysis and calculations to produce the parameter values displayed in the metering list items 5150. Under rollup options, the metering integration can allow access to payment and metered billing for third-party integrated application programming interface services. Examples of payment options could include linking and withdrawing options to crypto wallets, bank accounts, credit cards, payment processing providers, and/or other payment implementing options. Notifications that can be accessed through the action user interface control 4135 from the metering display 5110 can include notifications related to metered billing status.
  • the metering integration can also facilitate setting shared bill metering options. Each user account can pay for its own engagement related and metered costs. And each user account may be required to agree and provide payment information first.
  • the metering integration may cause a temporary loss of portfolio access if a user account is delinquent in its payments for the metered charges.
  • Another option may include temporarily freezing billed services and/or temporarily limiting access to affected paid services.
  • Third party cash transfer/payment services may be integrated to the billed metered system for both receiving and sending payments, as related to transfers, product/service/content (sells, barters, purchase, etc.).
  • Metered resources may include tracking of manhours for work to be rendered by user and/or for the user by another.
  • Work hours and rates could be job experience, type, location, association, hours, dates, worktime, holidays worked, time off, perks, bonus, etc. dependent and/or related.
  • features and/or services could include resumes, work experience, certifications, education levels, affiliations, third party cross-app job services integrated data, and/or user job requirements. More generally, information used for services can be obtained via other integrated third-party services and/or systems.
  • the system and the metering integration is not limited in what parameters are tracked, including web 2.0, web 3.0, crypto (coins, tokens, NFTs, services, etc.), work hours, service and/or product related credits, referral credits, third party account transactions and/or balances, and/or variations, alternatives, and combinations thereof.
  • Metered items may include threshold limits that turn on or off the metering function when an account system function threshold is met.
  • the service metering options integration can include a metering service that can be run via a manager at the bottom of the service metering options integration. This metering service can retrieve and analyze underlying parameter values such as usage amounts and the usage rates in settings to produce the metered parameters such as those illustrated in Fig. 51 and/or other metering parameters. [0309] Referring still to Fig.
  • the specific examples of metered parameters in the metering display 5110 can include the following for an example user account: in use codes such as QR codes, estimated (next) payment, remaining credit, auto replenish limit: auto replenish amount, daily drawdown rate, code rate (the charge rate per code such as a QR code), code scan rate (the rate charged per code scan), SMS rate (the rate charged per SMS message sent), storage rate (such as a per megabyte rate for system storage used), and system utilization rate (a rate for resources used in the system (such as a per data unit or processing usage rate), and/or other parameters as appropriate for metering.
  • codes such as QR codes
  • estimated (next) payment estimated (next) payment
  • remaining credit the amount charged per code
  • auto replenish amount auto replenish amount
  • daily drawdown rate code rate (the charge rate per code such as a QR code)
  • code scan rate the rate charged per code scan
  • SMS rate the rate charged per SMS message sent
  • storage rate such as a per megabyte rate for system storage used
  • system utilization rate a rate for resources
  • a live display 5210 will be discussed.
  • the live display 5210 can be displayed in response to user input selecting the live user interface control 4130.
  • the features in the live display 5210 can be context-sensitive, so that they can change depending on a location in the system from which the live display 5210 was invoked.
  • Features can also change depending on conditions, such as conditions in the subsystem (e.g., data in a profile of a current user account, including settings and profile data such as age, current residence city, etc.) and conditions outside the subsystem (e.g., current events outside the system, current weather, etc.). Such conditions are also discussed elsewhere in this disclosure.
  • context-sensitive features that depend on the current location in the subsystem may include code scanning, sharing, and sensing features.
  • some features available through the live display can be global features that do not depend on the location in the system from which the live display 5210 was invoked, such as some current happenings features.
  • such features may depend on other conditions, such as external conditions and/or internal conditions.
  • the live display 5210 can include a location indicator 5220, which can indicate a current location, i.e., the live display at the indicated current node or level (indicated by “CL” in the example of Fig. 52).
  • the live display can also include the user interface controls that are common to some other displays, including the option user interface controls 4125, the back button 4440, the navigate button 4172, the marketplace button 4170, and the set shortcut button 4445.
  • the live display 5210 can include live list items 5250, which can list additional integrations that are available from within the live integration.
  • the live list items 5250 can include controls similar to the controls discussed above in other list items in other displays.
  • list items of the live list items 5250 may include a structure user interface control 4178, a title 4180, and/or an access user interface control 4182.
  • the live list items 5250 can include an ObDEX Smart Scanner list item, which can be selected to invoke a scanning integration, which can scan codes and respond accordingly, as discussed above.
  • this scanning may include scanning various different types of codes, such as visual codes on things, codes in video, codes in audio, codes in frequencies, and codes from biometric scanning.
  • the scanner can bio scan using a user or non-user bio metrics or physical characteristics that can be used to uniquely identify individuals.
  • This process can allow the current user account and associated user to use the system to bio scan another user or potential user, which in the case of scanning another active user, can allow for the sending/exchange of service integration related information, and in the case of a non-user could register non-user as a referred user with options to register a new user account at that moment or at a later moment.
  • a bio scan can involve a user and associated user account setting up their own bio scan related integrations specific to what is presented (typically dependent on the user to user relationship) when scanned by another user.
  • scanning of codes may be context sensitive. For example, scanning could be prevented for at least some types of scans when scanning is initiated from some nodes in the hierarchy. For example, a particular code scanning function may only be available if the scanner is accessed at an approved node location.
  • the live list items 5250 can also include an ObDEX Quick Share list item.
  • the system can invoke an integration that when selected can display a user device presented code to be scanned for a related referral information exchange for the system with a scanning party user device. Such sharing is discussed above.
  • the live list items 5250 can also include an ObDEX Smart Sensing list item.
  • This list item can be selected to invoke smart sensing, such as sensing of video, frequency, biometric input, and/or audio data and possibly biometric identification such as facial recognition when such data is identified by the system, similar to chat bot identification of audio commands.
  • a bio scan can be used to identify heart beats, other movements, or other signs of life. This type of scan can be turned on and used to monitor life signs of people who are at risk, such as infants, elderly people, etc.
  • An alert can be sent to one or more user accounts such as family members, friends, and/or emergency personnel if signs of life cease for a specified time period.
  • the ObDEX Smart Sensing list item can include an activation user interface control 5280, which can be selected to toggle between on and off states to activate (turn on) and deactivate (turn off) the smart sensing.
  • the live list items 5250 can also include a Quick Shared Services list item.
  • the Quick Shared Services list item can be selected to prompt the system to quickly share convenient services, as discussed above. For example, such sharing can include sharing convenient services like contact information swapping, upcoming event sharing, etc. This may be done by the system responding to a user input selection by presenting a service- related code for scanning a related service information exchange with a scanning party user device.
  • the live list items 5250 can also include a Happenings Now list item, which can be selected to make available information and/or services related to things local and/or of interest to a user as represented by data in the corresponding user account and other conditions such as time, date, and geographic location of the user device. Such things of local and/or of interest could include things like restaurants, other businesses, events, sales at retail stores or other things that are currently available. The things may relate to any of the services discussed herein, as appropriate.
  • the live list items 5250 can also include a Current Level Now list item, which can be selected to access services linked to the current node and descendants of the current node. This could include node services that are happening now or at a near future date.
  • live list items can include any live-related integrations with services that would typically be considered quick accessibly convenient to the user corresponding to the user account.
  • a live list item can refer to a digital wallet integration, like digital wallets available in mobile operating systems.
  • the digital wallet can be context-sensitive and can be integrated at any applicable level or node of the service data structure.
  • Available user integrations can allow a user account to build and/or incorporate live integrations, in addition to system and third-party integrated system administrator select permissions to incorporate live integrations.
  • integrations can be built and integrated into various locations in the system as appropriate, including such integrations into the list items at various nodes as the integrations are integrated into the subsystem.
  • additions, modifications, and/or deletions to integrations can be made to update and improve the system.
  • This extensibility of the system can produce technical benefits in terms of a flexible, more efficient, and function-rich subsystem.
  • the integrations of the current subsystem can be made to interact and function together with other subsystems as discussed herein.
  • an actions display 5310 can include a location indicator 5320, which can indicate a current location, i.e., the actions display at the indicated current node or level (indicated by “CL” in the example of Fig. 53).
  • the actions display 5310 can also include the user interface controls that are common to some other displays, including the option user interface controls 4125, the back button 4440, the navigate button 4172, the marketplace button 4170, and the set shortcut button 4445.
  • An action in this context is a record that can request that the user account take some type of action, such as reviewing a message, responding to a message, performing a task in the subsystem, etc.
  • Top category and sub-category actions integrations could include services to allow the representation of actions to be identified, sorted, filtered, etc. at any integration node level, such as node levels for options, contacts, calendars, etc. Also, the actions could be assigned priority, levels from another user, such as the sender of the action. Actions could have deliverability setting options which could determine whether, when, and how frequently (if at all), etc. related action notifications send schedules. Applicable actions could be routed or assigned permanently or temporarily to one or more other user accounts or groups of user accounts (e.g., a contacts group).
  • action integrations can include new (not seen); reviewed (read/unread); snoozed (such as for some period in duration, as appropriate); skipped (for later review); saved (later reference, important, etc.); archived (for records); removed (deleted); transfers (one to many); assigned different designation; any applicable service integration related action, and/or applicable combinations, variations, and/or similarities thereof.
  • a selection list for actions may be organized with top categories such as the following as examples: sub-category action integration types including user notifications and user action requests can involve information (new/updated content); communications (chat, audio, video, posting/messaging board, etc., types of messages, and could also include live call notifications; approvals (related to projects, etc.); receipt approvals/confirmations such as for shared and/or transferred integrations, received things such as physical or electronic mail, requests such as for information, actions, etc.; invites such as for contact links, events, groups, clubs, subscriptions, organizations, etc.; calendar items such as tasks, events, content, reminders, appointments, etc.; and/or any applicable service integration related sub-category action, and/or applicable combinations, variations, and/or similarities thereof.
  • the structure user interface control 4174 can be filled in light in Fig. 53 (as compared to the structure user interface control 4174 of Fig. 41 that is filled in dark) indicating that the current display is a structure display, as explained above.
  • the actions display 5310 can include a selection list in the form of an outline 5330 that is structured and outlines a structure of representations of actions and groupings of actions nested into categories.
  • Each list item in the outline 5330 with associated accessible access point for the current user account to access one or more actions can include an access user interface control 4182 that can be selected to access the associated actions.
  • the access user interface control 4182 can advance the user interface display to related action type integration related service records for user selection upon which the selected action type manager would be presented to review, resolve, forward, save, delay, archive, share, (integration) place, etc. the service action.
  • the outline 5330 can include collapse and expand user interface controls 4640 that can be selected to collapse and expand nodes of the outline 5330. Additionally, the responsive collapsing and expanding of outline nodes discussed above can be used for the outline 5330 and other displayed outlines discussed and illustrated herein.
  • An action list display type user interface control 5340 in the actions display 5310 can indicate a type of display for the representations of the actions and action groupings in the actions display 5310.
  • the action list display type user interface control 5340 currently indicates the display type is New Actions All.
  • the groupings of actions include a highest- level node for New Actions All, which can list new (not yet reviewed or acted upon) actions.
  • the New Actions All node of the outline 5330 can include children nodes for different levels of priority for the actions.
  • the outline 5330 can also include a highest-level node for Previously Reviewed actions with children nodes for how long ago the actions were reviewed or received.
  • the outline 5330 can also include a highest-level node for Snoozed Actions, which can also include children node groupings.
  • the actions feature discussed here can produce technical advantages to deal with the computer-centric problem of overload of computer-initiated acts that need to be performed, and the often-disorganized nature of those acts. For example, the actions feature discussed here can allow organized optimization for users to view, control, manage, and respond to action requests from potentially a huge number of integration sources, all in one organized integration.
  • Fig. 54 illustrates an action types display 5410, which can be displayed by selecting Action Types (All) from the action list display type user interface control 5340.
  • the action types display 5410 can include a location indicator 5420, which can indicate a current location, i.e., the action types display at the indicated current node or level (indicated by “CL” in the example of Fig. 54).
  • the action types display 5410 can also include the user interface controls that are common to some other displays, including the option user interface controls 4125, the back button 4440, the navigate button 4172, the marketplace button 4170, and the set shortcut button 4445.
  • the display can include an outline 5430 that can group actions by action types.
  • the types can include an Information node with a New Training child node with an access user interface control 4182 for an associated action access, a Requests node with an Information child node with an access user interface control 4182, an Invites node with an Events child node and a Contact Links child node, each with an associated access user interface control 4182, Communications node with a collapse and expand user interface control 4640 that is collapsed indicating it has hidden children nodes below it, and a node that states, (Type/Sub-n) Action-n, indicating that other types can be included and the illustrated nodes are examples. Accordingly, any applicable service integration related action type integration such as those discussed herein may be included in a display such as the display of Fig. 54.
  • a mobile device 5510 and a desktop device 5520 can both be user devices that are running services apps 124 that can interact with the service subsystem 150 to implement features such as the ones discussed herein.
  • the mobile device 5510 and a desktop device 5520 can each connect separately to the service subsystem 150 and/or be connected to each other through a local or remote connection.
  • the mobile device 5510 may be connected to the service subsystem 150 and also be connected to the desktop device 5520, with the desktop device 5520 being connected to the service subsystem 150 indirectly through the mobile device 5510.
  • the mobile device 5510 may be linked to the desktop device 5520 in the form of a desktop computer or a smart display to play an online game.
  • the mobile device 5510 can display a mobile display 5530 via the services app 124 with a layout.
  • the desktop device 5520 can also display a desktop display
  • a service app 124 which may be different from the services app 124 for the mobile device 5510 (for example, the services 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 either desktop or mobile devices, such as by modifying app operation based on device screen size).
  • the mobile display 5530 and/or the desktop display 5540 may be on a single display screen, extend over multiple screens (such as with extended display features, foldable smart phones, etc.), be a virtual display, or be a projected display.
  • the desktop display 5540 can include a mobile area 5550, which can mimic the layout of the mobile display 5530.
  • the desktop display 5540 can also include a content area 5555 that is separate from the mobile area 5550.
  • the mobile area can operate like the mobile display 5530 when performing the same operations.
  • 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 typically displayed in the central display area (between the top and bottom user interface control areas) of the displays discussed herein and illustrated in other figures. This can provide for a consistent look and feel, and operation, between the mobile device 5510 and the desktop device 5520, but it can provide a large area for content in the content area 5555.
  • Blended profiles will now be discussed.
  • user accounts may have access to different user profiles for a single user account due to different connections or links within the system. For example, and with reference to the schematic diagram of Fig.
  • a user account for Alice may include multiple profiles 5610 and a user account for Joe may include multiple profiles 5620.
  • Both user accounts may be members of a high school friends contact group 5630 in the system, and that group may include a service that gives members access to other members’ profile that includes the other member’s name, year of high school graduation, and a list of extra-curricular activities the member was involved in during high school.
  • the user account for Alice and the user account for Joe may also both have access to a gaming integration 5640 that provides a service of allowing users to play online games with each other. That gaming integration may give members access to the other members’ profiles that include names, high scores on a particular game, and a list of digital resources available in a particular game.
  • the user account for Joe and the user account for Alice may have directly shared email addresses with each other through the system, which can be considered another profile in a contact share location 5650.
  • the system can respond by creating a blended profile 5660 for Alice that can include the information from the user account for Alice that the user account for Joe has access to through the gaming integration 5640 and through the high school friends contact group 5630 (and through other connections, such as the information (email addresses) directly shared between the user accounts for Alice and Joe at the contact share location 5650).
  • the blended profile can include merging the profile used by the gaming integration and the profile used by the high school friends’ group.
  • the system can include in the blended profile all the information from all three profiles (from the integration, contact group, and direct share), and de-duplicating duplicate information that appears in both profiles.
  • the blended profile 5660 for the user account of Alice to be shared with the user account of Joe can include the name (which can be de-duplicated, so it only appears once), high scores on a particular game, a list of digital resources available in the particular game, year of high school graduation, a list of extra-curricular activities involved in during high school from the user account of Alice, and the email address.
  • the blended profile 5670 for the user account of Joe shared with the user account of Alice could include the same types of information.
  • the merging of profile data for a blended profile can include filtering out data from one or more of the multiple profiles.
  • the filtered-out data can be excluded from the display of the data from the blended profile.
  • the filtered-out data can be one of the multiple profiles.
  • data from non-filtered profiles could still be displayed even if such data is the same as some data in the filtered profile.
  • This blended profile feature can overcome the problem of trying to bring together information from the same user account that is available in multiple different ways in a computer system. This could involve going to different locations to try to piece together the information, which could waste significant computer resources and user’ s time, and cause significant frustrations with the computer system.
  • the blended profile feature can overcome these issues by efficiently bringing the available account information from multiple profiles together into a single blended profile that can be displayed to the user in a user display.
  • the integration structure display 5710 can include a location indicator 5720, which can indicate a current location, i.e., the integration structure display at the indicated current node or level (indicated by “CL” in the example of Fig. 57).
  • the integration structure display 5710 can also include user interface controls that are common to some other displays, including the option user interface controls 4125, the back button 4440, the navigate button 4172, the marketplace button 4170, and the set shortcut button 4445.
  • the integration structure display 5710 can also include an outline 5730.
  • the outline can include structured nested node list items, and can also include collapse and expand user interface controls 4640 for nodes with descendent nodes below them.
  • a checkmark preceding a list item indicates the list item is an access type of integration node with an associated access point and an access user interface control 4182.
  • the current node can be considered a parent node
  • the highest-level nodes represented in the outline 5730 can be children of the current node
  • the nodes (sub) in the second level down in the outline 5730 can be grandchildren nodes of the current node.
  • Nodes with accessible access points can each include an access user interface control 4182, which can indicate the related node is a control point, also known as an optional access registry point, through which a user account can access any number of different types of integrations including service managers, which in some cases could integrate manager integrations that integrate other managers of different types.
  • the integration structure display 5710 can also include an integration display type user interface control 5740, which can be selected to choose between different displays for the current node.
  • the integration structure display 5710 can be used for representing any applicable service integration, such as integrations that can provide the types of services discussed herein via managers.
  • Integration access types may include a records access, including a single record access which when accessed would display a related display from a service manager.
  • An example of an integrations records list is depicted in Fig. 49, where a record manager example can be seen in Fig. 50.
  • integration access types may include related integration access as related to integrations discussed in the document and any applicable service integrations related to any applicable services as discussed herein.
  • Integration access types may also include service manager direct access.
  • a user upon selection of an access node could be introduced directly into an integrated productivity app, game, chat, messaging service, live video meeting, 3D/print make-on-demand service, and/or any other applicable service-related option.
  • Access record types for records that can be accessed can include as examples things, including standard things and encoded things with related thing options made available via related things managers.
  • thing options can include fabrication services for creating made-on demand standard or encoded things, such as physical things, digital things, virtual things, etc.
  • Thing options can also include reproduction services for creating additional ones of the same things.
  • Thing options could also include complementary marketplace services for ordering things-related complimentary things.
  • Thing options could also include encoded things services settings for defining, creating, updating, setting, controlling, etc. related scan shared (with associated uniform resource locators and/or commands) actions, which may include conditional actions.
  • the thing options could also include other types of services applicable to standard and/or encoded things, as discussed herein.
  • Access record types could also include contact cards with additional contact options made available via related contact card managers.
  • Contact card options could include making available one or more of the following: shared profile information including blended profile information, as linked between users and/or possibly conditionally applicable registry integration nodes, etc.; live communications like group and/or individual audio and/or video calls, live collaborative services such as related to project (program, product, etc.) and productivity services, etc.; messaging services like chat, messages, bulletin boards, voice and/or video messaging services, etc.; calendaring services like possibly shared services that allow for conceptualizing, building, managing, etc.
  • Accessed record types may include records related to any of the types of services discussed herein, as applicable.
  • the contact records list display 5810 can include a location indicator 5820, which can indicate a current location, i.e., the integration structure display at the indicated current node or level (indicated by “CL” in the example of Fig. 58).
  • the contact records list display 5810 can also include the user interface controls that are common to some other displays discussed herein, including the option user interface controls 4125, the back button 4440, the navigate button 4172, the marketplace button 4170, and the set shortcut button 4445.
  • the contact records list display 5810 can be at the record level, so there may be no additional categories below. However, there may be scenarios such as scenarios of structured managers and/or services that could in some contexts fall below this level. Accordingly, the structure user interface control 4174 can include three squares instead of its normal multi-level structure icon, indicating that the structure user interface control 4174 is not selectable in this display.
  • the structure user interface control can also include contact records list items 5830. In this example, each of the contact records list items 5830 can be a tile, as with the ObDEX integrations list items 4950 of Fig. 49 discussed above for integrations. However, the contact records list items 5830 can each represent a contact record.
  • each of the contact records list items 5830 can include a structure user interface control 4178 like the structure user interface controls discussed above for other list items.
  • the structure user interface control 4178 can be selected to prompt the system to navigate to a display that provides an at-a-glance representation of the structure of the represented feature, in this case the structure of the referenced contact record.
  • the list item can also include a code share user interface control 4970.
  • the code share user interface control 4970 can be selected to prompt the system to display a code share display that can share a code, which may navigate to a current level contact live integration for code sharing.
  • one or more of the contact records list items 5830 can display an image user interface control 5840, which can display an image such as a picture.
  • User input selecting the image user interface control 5840 can prompt the system to perform an action such as displaying a larger image of the profile picture in the display.
  • user input can select one of the contact records list items 5830 (such as a click on the list item but outside the specific user interface controls on the list item) to prompt the system to display a contact navigation view, which can allow for navigation and viewing of data in the contact record.
  • the linked contact record display 5910 can include a location indicator 5920, which can indicate a current location, i.e., the linked contact record display at the indicated current node or level (indicated by “CL” in the example of Fig. 59).
  • the linked contact record display 5910 can also include the user interface controls that are common to some other displays discussed herein, including the option user interface controls 4125, the back button 4440, the navigate button 4172, the marketplace button 4170, and the set shortcut button 4445.
  • the user interface controls can also include an image user interface control 5925 that can display a profile picture or other profile image for the current user account, which can display a profile image for the current user account.
  • the image user interface control 5925 can be selected to prompt the system to perform an action such as displaying a larger version of the image and/or displaying a profile for the current user account such as a blended profile tailored to the current location.
  • the structure user interface control 4174 can be a toggle switch as discussed above, with the structure user interface control 4174 being filled in with a light color in Fig. 59, indicating the linked contact record display 5910 is a structure display or structure view, displaying the structure of nodes below the current node.
  • the linked contact record display 5910 can also include an outline 5930.
  • the outline can include structured nested node list items, and can also include collapse and expand user interface controls 4640 for nodes with descendent nodes below them.
  • a checkmark preceding a list item indicates the list item is an access type of integration node with an associated access point and an access user interface control 4182.
  • the current node can be considered a parent node
  • the highest-level nodes represented in the outline 5930 can be children of the current node
  • the nodes (sub) in the second level down in the outline 5930 can be grandchildren nodes of the current node.
  • Nodes with accessible access points can each include an access user interface control 4182, which can indicate the related node is a control point.
  • the linked contact record display 5910 can also include a contact display type user interface control 5940, which can be selected to choose between different display types for the current node, such as different contact sharing option types, which can yield different structures and groupings of contacts.
  • the group type is a Shared Node Access type, indicating that the included contact nodes will be ones that are linked to the current user account by each having access to one or more of the same nodes in the system, and possibly sharing profiles for access points at such nodes. Accordingly, the outline 5930 can be grouped by nodes to which access is shared and/or some other type of grouping.
  • the contact display type user interface control 5940 can be selected to choose a different sharing type from a list of sharing types, to choose a list of contacts that have that chosen sharing type with the current user account.
  • sharing types may include shared communications, any applicable type of shared service(s), any applicable type of shared integration(s), contacts sharing profiles (which can be blended) and/or integrations with the current user account, the current user account sharing profiles (which can be blended) and/or integrations with the current user account), common shared integration access node profiles and/or common shared integrations.
  • access node profiles (such as profiles set for access points at the nodes) related to a node and/or manager access point may be set during integration registration processes.
  • Contact shared connections can occur as user accounts are linked as contacts, typically through access node registrations, initiated by exploring, invites, requests, referrals, automatic system matching, etc. as related to interconnected accounts.
  • Access node registrations as disclosed may be via any applicable type of service integration node discussed herein, including user and/or system contact group and/or network nodes.
  • Node access down to linked contact levels typically requires and/or encourages profile information to be shared (set for the access point, which can result in the profile information being shared with other user accounts with access to the same access point), and typically making available a default profile (which may be a public profile) when another profile is not indicated for sharing (i.e., being set) at the access point.
  • profile information which may be shared with other user accounts with access to the same access point
  • typically making available a default profile which may be a public profile
  • sharing can yield contacts between the associated user accounts whose profiles are shared to the same access point(s) as each other.
  • any applicable historic things between the current user account and the linked contact can be made available. And access could be provided to other structures and/or integrations and/or to service manager direct access as appropriate, such as for performance, building, and/or modifying structures as appropriate.
  • the linked contact record display 5910 can be used for representing any applicable contacts groups and/or records.
  • FIG. 60 a display layout flow 6000 will be discussed.
  • the flow illustrates different display areas and changes to those areas with some different types of displays discussed herein as a user input is provided to prompt the user interface displays to traverses nodes of the integration hierarchy discussed herein.
  • the display areas can include a header area 6010, a context area 6015, an integration node navigation and content area 6020, and a command button area 6025.
  • the header area 6010 (which can be an optional area) can include an information line 6035 such as a location indicator or title for the current display, which may indicate information such as a location of the current display in the hierarchy.
  • the header may include one or more user interface controls, such as a live user interface control 4130 and/or an action user interface control 4135.
  • the context area 6015 can include context-sensitive options user interface controls, where the controls and operations performed when they are selected can iterate as the user interface traverses the nodes of the integration hierarchy.
  • the context area may include a structure user interface control 4174.
  • the structure user interface control 4174 can operate as a toggle switch between a structure display (such as a structure at a glance display) and a node or navigation display, and the structure user interface control 4174 can changes between dark and light to indicate whether the current display is a structure display (light) and a node or navigation display (dark).
  • the context area 6015 can include different selections of context-sensitive user interface controls, and even the selection of which user interface controls to include in the context area may change, and such a change can iterate and be context-sensitive as the user interface traverses the nodes of the integration hierarchy (different sets of user interface controls can be selected and displayed for different node locations in response to traversing between nodes). Examples of such nodes can include those discussed above, and may include others such as a sort-filter user interface control to sort and/or filter list items in the current display, a search field as illustrated in figures discussed above. Also, the user interface controls in the header area 6010 can be context-sensitive (though they may also include global aspects that are not context- sensitive).
  • At least some user interface controls that would otherwise be in the header may be included in the context area 6015. This may be done with the with the information line 6035 omitted, or incorporated into the integration node navigation and content area 6020.
  • the integration node navigation and content area 6020 can include a structure view (such as an outline of structure illustrated in figures and discussed above, although different types of structures such as tree views (schematically illustrated in the integration node navigation and content area 6020 of the middle display in Fig. 60) could be used) in some displays, for structured nodes at a glance structure integration navigation.
  • the integration node navigation and content area 6020 can include a navigation view or node view for upline (as in the navigation displays above) and/or downline (as in the node displays above) node navigation.
  • the integration node navigation and content area 6020 can include a tile and/or icon user interface navigation view for upline and/or downline node navigation.
  • the integration node navigation and content area 6020 can include a service manager display, such as where a service manager is being invoked to perform, build, and/or modify services in integrations (see, e.g., the display on the left in Fig. 20 indicating a service manager area).
  • the command button area 6025 can be optional. When it is included in a display, the command button area 6025 may include standard buttons, such as the back button 4440 illustrated in other figures, the navigate button 4172, the marketplace button 4170, and the set shortcut button 4445 illustrated in other figures. The command button area 6025 may include other buttons such as the buttons illustrated in the bottom of displays above and/or other buttons.
  • User interface features discussed herein can vary in many ways as illustrated herein and in other ways as user interface elements can be rearranged, mixed, changed in type such as between text and image-based user interface elements.
  • User interface elements can also include variations, counts, types, functions, so that particular illustrations herein should not be considered limiting.
  • Fig. 60 includes an arrow from left to right, different flows of navigation between the different types of user interface displays discussed herein can be selected by users, so this particular order should not be considered to be limiting.
  • Marketplace Integrations can be for purchase, rent, barter, free, etc.; credit referral tracked; made generally available or specific to (predesignated) user (type) of accounts, like (conditional accounts related to specific organizations, divisions, affiliations, networks, groups, departments, etc.
  • the system can include a (Portfolio) Integration related niche specific Onboarding (Al assisted) Quiz to help the User by making available useful (recommended/free/paid/trade) Integrations for (Portfolio) Incorporation.
  • (Service) Integrations and the related (Record) Managers could incorporate (Webpage/Website) Builders to build (Profile, Resume, Service, Product, etc.) Page/Display Types.
  • An app and overall system can allow for hold, pause, archive, transfer, share etc. of Integration and/or Specified Integration Services, and adjust Metering accordingly.
  • Action can include a related ability to prioritize, block, skip snooze down to the Integrations (Services) level.
  • App Display could be integrated to Device, Online Browser, etc.
  • Marketplace Things can be listed to other Integrated Marketplaces with Encoded Things able to be listed to either Integrated or Non-Integrated Marketplaces since the system integration happens when Encoded Things are scanned.
  • App Indications could auto-sort by order or last or most accessed.
  • Encoded (standard) things, including customized things, or portions thereof, can be Al (assisted) generated.
  • the Al could assist in placing and/or making available options for (free, paid, trial, privileged access, etc.) placements (integrations, posts, etc.) of encoded things in (real or virtual world) marketplaces (to various markets, locations, advertisement systems, etc.).
  • Some of these encoded things and/or portions can be (or can be incorporated to) pictures, icons, logos, thumbnails, presentations, multimedia displays, projected display, holographic display, any display (real, digital, and/or virtual), content video browsers (google meet, zoom, etc.), frequency broadcasts (in the form of audio or frequency-based code), videos (posts, content, commercials, etc.), screensavers, in game, in virtual simulations, billboards (real, digital, and/or virtual), etc.
  • (visual, digital, and/or virtual) codes could be (sublimely) incorporated into the encoded thing itself, for example the app scanner could be pointed to a system integrated and (visually) encoded commercial, to return a predesignated system action.
  • an integrated an option to share an encoded commercial to (marketplace) integrated billboards in Time Square can be made available (or presented) to which the user could simply select time, place, and when to run ads, in this case with appropriate fees.
  • the UI can allow for gradual introduction/adoption by slowly adding functionality (adding more Top-Level Structures) while using an increasing familiar (Stable/Non-Changing) UI Header.
  • the system could launch a code scanning subsystem along with other types of subsystems. This can allow Niche Focused introduction to the overall system and platform at some stage with raving Users familiar with the overall system, then the system can seamlessly implement Upgrades, including new feature lines. This process can repeat until ultimately the User Base is all on overall system with recognition of that overall system.
  • the system can make available a simple/intuitive (Dynamically) Structured Application that can manage unlimited number of services and related, content, actions, people interactions, etc. not before available and needed in this (Al incendiary) exponentially expanding data driven world.
  • a record can have more than one sharable code associated with the record, such a different code for each of multiple different types of services to be performed using the record, and possibly a different code to share related integration services.
  • Al/bot functionality may constantly analyze account data to assist in filling in account input forms.
  • an Al bot could be assigned to a user account to build out a unique or tailored experience integrations suggestion list based on user account use patterns, associations, information, and/or other data associated with the user account.
  • the names of services listed herein can be used in naming and labeling related nodes, such as nodes for integrations providing such services.
  • each technique may be performed in a computer system that includes at least one processor and memory including instructions stored thereon that when executed by at least one processor cause at least one processor to perform the technique (memory stores instructions (e.g., object code), and when processor(s) execute(s) those instructions, processor(s) perform(s) the technique).
  • the computer system can be included in a services system that can further include one or more encoded things that each includes a scannable code in a scannable form, as discussed herein.
  • one or more computer-readable memory may have computer-executable instructions embodied thereon that, when executed by at least one processor, cause at least one processor to perform the technique.
  • the techniques discussed below may be performed at least in part by hardware logic. Features discussed in each of the techniques and tools below may be combined with each other in any combination not precluded by the discussion herein, including combining features from a technique discussed with reference to one figure in a technique discussed with reference to a different figure. Also, a computer system may include means for performing each of the acts discussed in the context of these techniques and tools, in different combinations. [0361]
  • a computer system can include a user account and a service data structure linked to the user account in the computer system.
  • a technique can include receiving a request from the at least one change-rights user account to make a change to at least one of the generally available data structure items.
  • the technique can further include, in response to receiving the request, verifying that the at least one change-rights user account has permission to make the change, the verifying including accessing the indication that the at least one change-rights user account has the at least one indicated permission.
  • the technique can include, in response to verifying that the at least one change-rights user account has permission to make the change, proceeding with a process to make the change from the request, which can include making the requested change.
  • the encoded thing can be a point-of-order display
  • the one or more computer-implemented services can include ordering an ordered thing that is a type of thing indicated in the point-of-order display.
  • the record can be a first record
  • the ordered thing can be an encoded thing that includes a scannable code that is configured to be linked to a second record in the computer system that is different from the first record.
  • the ordered thing may be a thing such as a produced physical thing or some other type of thing.
  • the ordered thing may be an encoded sign.
  • the computer system can further include a limited access indicator, which can be data that indicates whether a specified user account has access to a code-linked service resource such as a specified structured category, a specified record, a specified record service, or a specified combination thereof.
  • the computer system can limit access to some such resources to user accounts that include limited access indicators indicating those user accounts have such access rights. In some instances, the computer system can limit access to some such resources to user accounts that do not include limited access indicators indicating those user accounts do not have such access rights. In other instances, such resources may be generally available, so that access rights are not allowed to be limited for such resources.
  • Resource- specific indicators may indicate whether indicated resources are limited-access resources or generally available resources (i.e., whether access is public or account specific).
  • the technique can include presenting 6110 a representation of at least a portion of the service data structure, with the representation indicating a current location in the hierarchy of the service data structure.
  • the technique can also include, in response to receiving user input directed at the representation, navigating 6120 between levels in the service data structure. Additionally, the technique can include changing 6130 the representation to reflect the navigation between levels.
  • the representation may include displays, such as ones like the user interface displays discussed above or different user interface displays.
  • the representation discussed above can include a record wallet display and a navigation display, the record wallet display including a category content display including user interface controls representing items in a current category, and the navigation display including user interface controls representing the current category and categories above the current category in the hierarchy.
  • the record wallet display can include a user interface control that is selectable to switch to the navigation display configured for the current category represented in the record wallet display.
  • the user interface controls of the navigation display which represent the current category and categories above the current category in the hierarchy, can each be selectable to switch to the record wallet display for a category represented by a selected user interface control of the user interface controls of the navigation display.
  • the record wallet display and the navigation display can each include one or more of the same user interface controls that are in the same position in both the record wallet display and the navigation display.
  • the presenting 6110 of the representation may include presenting a customized subset of categories from the service data structure, the customized subset of categories being customized via the computer system based on current conditions identified by the computer system.
  • the presenting 6110 of the representation may include presenting a representation of a customized subset of the set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code, the customized subset of services being customized via the computer system based on current conditions identified by the computer system.
  • the navigating 6120 between levels in the service data structure can include drilling down into the hierarchy of the service data structure to reach the record.
  • the changing 6130 of the representation can include presenting indications of the set of one or more computer- implemented services.
  • the record discussed above can be a first record, and the service data structure can further include a second record in the second category.
  • the second record may be in a third category, the third category being at the second level.
  • the first category discussed above can include an indication of a set of services available for records in the first category.
  • the second category can include an indication of a set of services available for records in the second category, and the set of services available for records in the second category can include a subset of the set of services available for records in the first category.
  • the set of one or more computer- implemented services to be performed via the computer system in response to user input using the at least one scannable code can include a subset of the set of services available for records in the second category.
  • the technique can include receiving 6210 a user input request that requests a transfer of the record to a new hierarchical location in the computer system.
  • the technique can also include, in response to receiving the user input request, transferring 6220 the record and/or a category structure indicator for the record to a new hierarchical location in the computer system.
  • the category structure indicator can indicate a category structure including categories of the hierarchy that include the record.
  • the categories of the hierarchy that include the record can include the first category and the second category, and the record can retain a category structure indicated in the category structure indicator in the new hierarchical location in the computer system.
  • transferring the record can include transferring the record to a second service data structure linked to a second user account instead of being linked to the first user account.
  • transferring the record can include transferring the record to a second service data structure linked to the user account.
  • the first service data structure can be linked to a first organization designation for the user account
  • the second service data structure can be linked to a second organization designation for the user account instead of being linked to the first organization designation.
  • the technique can include managing 6310 a service data structure linked to a user account in the computer system.
  • the service data structure can include a record.
  • the record can include an indication of at least one scannable code that is linked to the user account in the computer system, and an indication of a set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can also include performing 6320 the one or more computer-implemented services in response to a user input into the computer system that uses the at least one scannable code.
  • the managing 6310 of the service data structure can include performing a first set of one or more actions in response to user input from at least one computerized human user interface device, and/or performing a second set of one or more actions in response to user input from at least one artificial intelligence bot running in the computer system.
  • the technique can include managing 6410 a service data structure linked to a user account in the computer system.
  • the service data structure can include a record that can include an indication of at least one scannable code that is linked to the user account in the computer system.
  • the record can also include an indication (such as in settings) of a set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can also include receiving 6420 user input that includes an input code into the computer system, the user input requesting a requested action using the input code and the service data structure.
  • the technique can further include, in response to receiving the user input into the computer system that uses the input code, performing a safety check 6430 on the input code.
  • the technique can include taking 6440 one or more available precautionary measures for the input code if the safety check on the input code results in a safety failure, or avoiding 6450 taking the one or more available precautionary measures for the input code if the safety check on the input code does not result in a safety failure (i.e., the safety check succeeds).
  • the safety check can include searching a database of authentic codes that includes the at least one scannable code to determine whether the input code matches one of the authentic codes in the database.
  • the safety check can fail if it is determined that the input code does not match any of the authentic codes in the database, and the safety check can succeed if it is determined that the input code matches one of the authentic codes in the database.
  • Taking 6440 one or more available precautionary measures for the input code can include refusing to perform the requested action, and avoiding 6450 taking the one or more available precautionary measures for the input code can include taking the requested action.
  • the requested action may include performing a management action for managing the record that includes an indication of the at least one scannable code.
  • the requested action can include performing a management action for managing the record that includes an indication of the at least one scannable code.
  • the safety check can include determining whether the input code is malicious (i.e., if the safety check reveals some indication that the input code is malicious, even if the input code is ultimately not actually malicious).
  • the determining of whether the input code is malicious can include analyzing the requested action.
  • the safety check can fail if it is determined that the requested action is malicious, and the safety check can succeed if it is determined that the requested action is not malicious.
  • Taking the one or more available precautionary measures for the input code can include presenting a user output warning. Also, avoiding taking the one or more available precautionary measures for the input code can include avoiding presenting the user output warning.
  • Determining whether the input code is malicious can include analyzing maliciousness of a uniform resource locator linked to the input code in the computer system. Where the input code matches the at least one scannable code, determining whether the input code is malicious can include analyzing the record that includes the indication of the at least one scannable code, such as analyzing the record to determine whether a uniform resource locator indicated in the record is malicious. Where the input code matches the at least one scannable code, the requested action can include performing a management action for managing the record that includes an indication of the at least one scannable code.
  • a technique can include managing 6510 a service data structure linked to a user account in the computer system.
  • the service data structure can include a record.
  • the record can include an indication of at least one scannable code that is linked to the user account in the computer system, and an indication of a set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can further include performing 6520 the one or more computer-implemented services in response to user input into the computer system that uses the at least one scannable code.
  • the technique can include receiving 6530 a request to create a second user account, and in response to receiving the request to create the second user account, creating 6540 the second user account.
  • the technique can further include linking 6550 the second user account to a tracking code, the tracking code indicating a referral source for the second user account.
  • the referral source can be either a product provider user account of a provider of a product linked to the request to create a second user account, or a referral user account linked to the request to create the second user account.
  • the technique can additionally include adding 6560 a credit to a record for the referral source for the creating of the second user account.
  • scanning of an account produced code that is linked to a first user account (such as a trigger code that is scanned for sharing one or more services) and/or system tracked code related to products or services can initiate the setup of a new second account, and credit can be set for user accounts linked to the providing of the product and/or service and/or the first user account.
  • Yet another computer services tools technique can include managing a service data structure linked to a user account in the computer system using a service code computer subsystem.
  • the managing of the service data structure can use at least one user device computer application that is dedicated for use with the service code computer subsystem and at least one user device computer application that is designed for use with a service- specific computer subsystem other than the service code computer subsystem.
  • the service data structure can include a record that can include an indication of at least one scannable code that is linked to the user account in the computer system and an indication of a set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can further include performing the one or more computer-implemented services in response to a user input into the computer system that uses the at least one scannable code.
  • the technique can include managing 6610 a service data structure linked to a user account in the computer system, the service data structure including a record.
  • the record can include an indication of at least one scannable code that is linked to the user account in the computer system, and an indication of a set of one or more computer-implemented services to be performed via the computer system in response to user input using the at least one scannable code.
  • the technique can also include receiving 6620 user input into the computer system that uses the at least one scannable code.
  • the technique can include linking 6630 a quick link to the at least one scannable code and presenting 6640 the quick link on a user output device.
  • the technique can also include performing 6650 the one or more computer-implemented services that are linked to the at least one scannable code.
  • the technique can include recycling 6660 the quick link to make the quick link available for use in later computer system responses to receiving later user input into the computer system that uses scannable codes, the recycling including undoing the linking of the quick link from the at least one scannable code.
  • the quick link may then be used by the system in subsequent similar acts using that same at least one scannable code and/or other scannable codes with different linked services, and even other scannable codes that are linked to different user accounts than the at least one scannable code discussed earlier in this paragraph.
  • the technique can include presenting 6710 a user interface display that represents a current node in a hierarchical data structure as the user interface display moves between nodes in the hierarchical data structure, the hierarchical data structure including multiple service integrations and the user interface display including a context-sensitive user interface control that is displayed in the user interface display at two or more of the nodes, the two or more of the nodes being at multiple levels of the hierarchical data structure.
  • the two or more of the nodes can include: a contacts node in a contacts integration that includes contact nodes linked to profiles for accounts other than an active user account; and a portfolio node in a portfolio integration that is separate from the contacts integration, the portfolio node being a type of node other than a contacts node, the portfolio integration including nodes linked to portfolio integrations that are integrated into the hierarchical data structure to provide services for the active user account, the portfolio integrations including structures other than profiles for accounts.
  • the technique can further include iterating 6720 a state of the context-sensitive user interface control as the user interface display moves between nodes, the iterating configuring the context-sensitive user interface control to respond to selection of the context-sensitive user interface control by invoking a context-sensitive integration to perform a triggered process, the triggered process being tailored to the current node being represented in the user interface display as the user interface display moves between the two or more of the nodes, the process being different for each of the two or more of the nodes.
  • this iterating technique may be performed between two contacts nodes or two portfolio nodes rather than a contacts node and a portfolio node. Indeed, the technique may be performed between any of the types of nodes discussed herein, including between nodes of the same type and/or between nodes of different types.
  • the technique can further include performing operations on an integration of the hierarchical data structure to change functionality of the integration based on predetermined conditions.
  • a managed integration of the contacts integrations or the portfolio integrations can be managed by one or more computer- implemented managers.
  • the technique can include the manager managing the managed integration, the managing can include performing operations to build, modify, and/or operate the managed integration.
  • the technique can further include using the contacts integration to generate a blended profile derived from multiple profiles connected to different nodes in the hierarchical data structure.
  • the technique can further include, in response to receiving user input selecting the context-sensitive user interface control while the user interface display represents the contacts node, performing the triggering process with the triggering process being tailored to the contacts node.
  • the technique can also include, in response to receiving user input selecting the context-sensitive user interface control while the user interface display represents the portfolio node, performing the triggering process with the triggering process being tailored to the portfolio node.
  • the triggering process can include displaying current node data that is rolled up to a level of the current node so that the current node data includes data for one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be a search control and the triggering process can include searching for data items, the data items being limited to items linked to one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be an action control and the triggered process can include displaying an action display that displays one or more specific controls representing an available action set including one or more digital actions, the one or more digital actions being limited to actions linked to one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be a marketplace control and the triggered process can include displaying a digital marketplace that is operable to receive user input to register an available structure set including one or more structures that is configured to be integrated into the hierarchical data structure, the selection of structures in the available structure set being tailored to the current node.
  • the context-sensitive user interface control can be a metering control and the triggered process can include displaying metering data for the current node, the displayed metering data including node-limited data that is limited to metering data for one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be a data analytics control and the triggered process can include displaying data analytics for the current node, the displayed data analytics can include node-limited data analytics that are limited to data analytics for one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be a data control and the triggered process can include displaying data for the current node, the displayed data including node-limited data that is limited to data for one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be a communications control and the triggered process can include displaying one or more specific controls for the current node.
  • the one or more specific controls can include one or more node-limited specific controls for communications that are limited to communications linked to one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be a settings control and the triggered process can include displaying specific controls for displaying and editing settings that apply to one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be an information control and the triggered process can include displaying information for the current node, the displayed information including node-limited information that is limited to information regarding one or more of the current node and descendants of the current node. Also, the information may include action items that can represent actions that are requested of the active user account.
  • the context-sensitive user interface control can be a support control and the triggered process can include displaying a support request control for the current node, the support request control being selectable to send a support request to a user profile that is linked to the current node as a support provider.
  • the context-sensitive user interface control can be a live control and the triggered process can include displaying live information for the current node, the displayed live information including node-limited live information being information regarding current events linked to one or more of the current node and descendants of the current node.
  • the context-sensitive user interface control can be an options control and the triggered process can include displaying options for the current node and descendants of the current node, the options including at least two displayed controls of the following kinds of controls: information control, settings control, marketplace control, communications control, data control, data analytics control, support control, metering control, action control, and live control.
  • the technique can include presenting 6810 a user interface display including an outline.
  • the technique can also include partially collapsing 6820 a subject entry of a displayed outline in response to a system determination related to the outline, the partial collapsing can include configuring and presenting the outline with entries below the subject entry in a hierarchy of the outline including one or more hidden entries and one or more displayed entries.
  • the outline can represent multiple nodes in a computerized hierarchical data structure, one or more entries of the outline being collapsed in the user interface display to hide one or more entries below the one or more collapsed entries, the outline fitting within an available width for the user interface display.
  • the partial collapsing can include receiving user input indicating the outline is to be expanded by revealing one or more revealed entries of the outline below the one or more collapsed entries of the outline.
  • the partially collapsing can also include, in response to the user input, performing the following: expanding the outline by revealing the one or more revealed entries of the outline; and continuing to fit the outline within the available width for the user interface display by collapsing the outline to hide one or more newly hidden entries of the outline other than the revealed entries.
  • the at least one of the one or more newly hidden entries can be higher than the revealed entries in a hierarchy of the outline.
  • the one or more newly hidden entries can be directly above the revealed entries in a hierarchy of the outline.
  • the partial collapsing can include collapsing some outline entries in response to the system determining that there are not additional records represented in other branches of the outline below those entries other than ones that are displayed.
  • the technique can include sharing 6910 multiple profiles linked to a sharing account with a different account in a profile sharing system.
  • the technique can also include merging 6920 profile data from the multiple shared profiles into a blended profile.
  • the technique can further include, in response to user input from the different account requesting display of profile information for the sharing account, displaying 6930 profile data from the blended profile.
  • the merging of the profile data can include identifying duplicate data in the multiple profiles linked to a sharing account and deduplicating the duplicate data in the blended profile.
  • the merging of the profile data can include filtering out excluded data from one or more of the multiple profiles, the excluded data being excluded from the display of the data from the blended profile.
  • the excluded data can include all data in a filtered profile, or part of the data in a filtered profile.
  • the technique can include presenting 7010 a user interface display that represents a current node in a computerized hierarchical data structure as the user interface display moves between nodes in the hierarchical data structure.
  • the user interface display can present a category node user interface area representing a category node below the current node in the computerized hierarchical data structure.
  • the category node user interface area can include a drill down user interface control that is selectable to drill the user interface display down to the category node and display representations of one or more subcategory nodes below the category node; and an access point user interface control that is selectable to display an access display for accessing one or more record structures linked to the category node.
  • the technique can also include moving 7020 the user interface display to a new display in response to selection of the drill down user interface control and/or the access point user interface control.
  • the category node user interface area can further include a structure user interface control that is selectable to display a structure display for the category node, the structure display displaying a structure of the category node and its descendent nodes in a single display.
  • the access display can display data from one or more record structures linked to the category node.
  • the access display can display one or more user interface controls that are selectable to initiate adding of representations of one or more record structures to the access display, the one or more record structures being linked to the category node.
  • the access display may not currently display representations of record integrations linked to the category node.
  • the category node may be a portfolio node or contact group node.
  • the technique can include maintaining 7110 data indicating multiple different locations in a hierarchical data structure system where multiple information data items from an active user account structure for a user account are used.
  • the technique can also include presenting 7120 a profile monitoring user interface display for the active user account, the profile monitoring user interface display representing the multiple information data items, the profile monitoring user interface display including one or more indications for each data item of the multiple information data items, the one or more indications indicating one or more of the multiple different locations where the corresponding data item is used.
  • the technique can further include, in response to user input at the user interface display requesting that use of one of the information data items be ceased at a location indicated on the user interface display, ceasing use of the one of the information data items at the indicated location.
  • the technique can further include, in response to user input at the user interface display requesting that use of one of the information data items be ceased at a location indicated on the user interface display, revoking permission for the user account to use computer resources linked to the indicated location.
  • the multiple different locations can include a profile structure and/or a contact group structure.
  • the user account can be a first user account, and the multiple different locations can include a second user account other than the first user account, such as where data is directly shared between user accounts.
  • the technique can include maintaining 7210 a code record linked to a user account, the code record defining a predetermined code that includes a predefined pattern in one or more of a video pattern, a frequency pattern, biometric pattern, and an audio pattern, the code record further defining a service to be performed using an integration in response to scanning of the code by identifying the predefined pattern by the computer system; scanning 7220 input including one or more of video input, frequency input, biometric input, and audio input for the predetermined code; identifying 7230 the predetermined code; and in response to identifying the predetermined code, performing 7240 the service using the integration in the computer system.
  • the pattern can be a video pattern, frequency pattern, biometric pattern, and/or an audio pattern.
  • the scanning of input can include scanning a broadcast on an electronic output device and/or scanning a live scene using a camera of a user device in the computer system.
  • the technique can include receiving 7310 a user input access point request from a user account for an access point to a service integration that is not fully setup; determining 7320 that an access point profile from the user account is to be used in setting up the access point; and in response to the determining that the access point profile from the user account is to be used in setting up the access point, identifying 7330 an identified profile for use by the service integration and setting the identified profile as the access point profile for the access point as part of setting up the access point.
  • Identifying the identified profile can include determining that neither a fixed profile nor a custom profile has been designated to be set for the access point, and setting a default profile as the identified profile for the access point or generating a new profile for the access point based on one or more existing profiles for the user account.
  • the default profile can be a public profile.
  • the technique can be performed via a computer system with a mobile user device and a desktop user device (a device with a larger screen than a typical mobile device, such as a desktop computer, a laptop computer, a tablet computer, etc.).
  • the technique can include presenting 7410 a mobile display on the mobile user device and presenting 7420 a desktop display on the desktop user device.
  • the desktop display can include a mobile area with a layout and user interface controls that mimic the mobile display; and a content area that is separate from the mobile area, the content area being displayable at the same time as the mobile area and the content area displaying content related to indications displayed in the mobile area.
  • the technique can further include expanding 7430 the content area to include at least a portion of the mobile area while hiding the at least a portion of the mobile area, which can include shrinking or contracting the overall mobile area.
  • the expanding the content area to include the at least a portion of the mobile area while hiding the at least a portion of the mobile area can include receiving user input directed to a user interface control on the desktop display and responding to the user input by expanding the content area to include the at least a portion of the mobile area while hiding the at least a portion of the mobile area.
  • the expanding the content area to include the at least a portion of the mobile area while hiding the at least a portion of the mobile area can include receiving user input directed to a user interface control on the desktop display and responding to the user input by expanding the content area to include the at least a portion of the mobile area while hiding the at least a portion of the mobile area.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Tourism & Hospitality (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Health & Medical Sciences (AREA)
  • Game Theory and Decision Science (AREA)
  • Data Mining & Analysis (AREA)
  • User Interface Of Digital Computer (AREA)
  • Devices For Executing Special Programs (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Des techniques de services informatiques sont divulguées, dont certaines concernent l'utilisation de codes pour des services activés par code. En outre, une structure hiérarchique et des sous-structures qui peuvent être utilisées dans un système informatique pour fournir des services informatiques sont divulguées en ce qui concerne certaines caractéristiques liées au service, telles que l'itération de processus d'interface utilisateur sensibles au contexte. De plus, l'utilisation d'intégrations dans la structure hiérarchique et le système informatique associé est divulguée, en particulier en ce qui concerne la fourniture de services à l'aide des intégrations. Sont également divulguées des caractéristiques d'interface utilisateur avantageuses. D'autres caractéristiques liées au service informatique sont également divulguées.
EP24771693.9A 2023-03-13 2024-03-13 Services informatiques Pending EP4681407A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363489845P 2023-03-13 2023-03-13
PCT/US2024/019817 WO2024192187A2 (fr) 2023-03-13 2024-03-13 Services informatiques

Publications (1)

Publication Number Publication Date
EP4681407A2 true EP4681407A2 (fr) 2026-01-21

Family

ID=92756024

Family Applications (1)

Application Number Title Priority Date Filing Date
EP24771693.9A Pending EP4681407A2 (fr) 2023-03-13 2024-03-13 Services informatiques

Country Status (6)

Country Link
EP (1) EP4681407A2 (fr)
JP (1) JP2026510951A (fr)
KR (1) KR20260004332A (fr)
AU (1) AU2024236755A1 (fr)
MX (1) MX2025010946A (fr)
WO (1) WO2024192187A2 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8270952B2 (en) * 2009-01-28 2012-09-18 Headwater Partners I Llc Open development system for access service providers
US11869005B2 (en) * 2019-09-17 2024-01-09 Plaid Inc. System and method linking to accounts using credential-less authentication
US11875319B2 (en) * 2021-07-23 2024-01-16 Visa International Service Association Data processing utilizing a digital tag

Also Published As

Publication number Publication date
AU2024236755A1 (en) 2025-10-30
WO2024192187A3 (fr) 2024-12-26
MX2025010946A (es) 2026-01-07
WO2024192187A2 (fr) 2024-09-19
JP2026510951A (ja) 2026-04-10
KR20260004332A (ko) 2026-01-08

Similar Documents

Publication Publication Date Title
US20230252540A1 (en) User applications store and connecting, registering, following with and synchronizing or accessing user data of user applications from/to parent application and other user applications
Walker From big data to big profits: Success with data and analytics
US20190205148A1 (en) System and method for providing intelligent operant operating interface and intelligent personal assistant as a service
US20210383489A1 (en) Scheduling, booking, and pricing engines
US20180181378A1 (en) Method, system and apparatus for generating, editing, and deploying native mobile apps
US11232523B2 (en) System and method for providing an intelligent operating interface and intelligent personal assistant as a service on a crypto secure social media and cross bridge service with continuous prosumer validation based on i-operant tags, i-bubble tags, demojis and demoticons
US20200234003A1 (en) Method, system and apparatus for generating, editing, and deploying native mobile apps and utilizing deep learning for instant digital conversion
US20140172630A1 (en) Social media interface for use with a global shopping cart
JP2017519312A (ja) 映画産業プロフェッショナルのためのグローバル交換プラットホーム
US20140188585A1 (en) Organizational Tools and or a Collaboration System Utilizing the Same Therein
US20220121809A1 (en) Method, system and apparatus for generating, editing, and deploying native mobile apps and utilizing deep learning for instant digital conversion
Baskerville et al. Reconceptualizing users: The roles and activities of people as they engage with digital technologies
Basu et al. Competitive digital innovation: Transforming products, processes and business models to win in the digital economy
Abraham et al. Personalized: Customer strategy in the age of AI
JP2022506910A (ja) Ｉ－オペラント・タグ、ｉ－バブル・タグ、ｄ絵文字及びｄエモーティコンに基づく連続的生産消費者確認を伴う暗号セキュア・ソーシャル・メディア及びクロス・ブリッジ・サービスに関するインテリジェント・オペレーティング・インターフェース及びサービスとしてのインテリジェント・パーソナル・アシスタントを提供するためのシステム及び方法
US9218399B2 (en) Global value networks
CN112313649A (zh) 分散式数字通信平台的系统和方法
EP4681407A2 (fr) Services informatiques
CA3231296A1 (fr) Systemes et procedes pour l'organisation de manifestations et l'ecosysteme des participants
Mohammad Evaluating the Suitability of the MERN Stack in the Development of Food Delivery Applications
Koukopoulos et al. Intelligent management of outdoor cultural events promoting exploitation in smart city environments
Leitner The role of Human–Computer Interaction (HCI) in change management
Talbott et al. Electronic Resources Librarianship: A Practical Guide for Librarians
OPOKU et al. DEVELOPMENT AND IMPLEMENTATION OF A LOCAL FOOD FINDER ANDROID APPLICATION
Rangdale et al. A Comprehensive Analysis of the Cloud-Based Method for Using Salesforce Technology to Optimize Event Venue Reservations

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20251013

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR