A method and a vehicle machine system for logging in and logging out of a vehicle machine account and an ecological application account

Abstract

The application relates to a car machine account and ecological application account association login and logout method and a car machine system. Through construction of One ID, the current situation of data islands is broken, customer behavior is accurately identified, and a complete "identity and behavior" "business card" is customized for each user, which provides support for the landing and lean operation of marketing scenarios. The ecological application account and the car machine account are associated with login and logout effects, and are not limited to the logged-in vehicle. For a new vehicle, after the account is logged in, the application should also be able to realize automatic login. The application can be controlled under different modes of the car machine, and the ecological application account and the car machine account are associated with login and logout effects. Through One ID, user data scattered on various platforms is connected, the whole life cycle journey of customers is integrated, the data stored on various platforms is connected, and thus the business efficiency and user experience are improved.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of Internet of Vehicles, in particular to a method for associating login and logout of a vehicle machine account and an ecological application account and a vehicle machine system. BACKGROUND

[0002] The existing login operation of the vehicle machine ecological application is performed by scanning the code of the mobile phone APP of the application. If the vehicle owner wants to log in to the application on the vehicle machine, the mobile phone APP must be downloaded. For the vehicle owner, the process of downloading the application and completing the registration and login is relatively cumbersome, and the vehicle owner's experience is poor. For the vehicle manufacturer, whether it is an ecological application or a system application, it is hoped that the vehicle owner can complete most of the interactions in the cockpit. After the vehicle owner account is logged out, the logged-in ecological application account is not automatically logged out. The vehicle owner can only log out of the different ecological applications one by one to log out, which not only fails to protect the account privacy of the vehicle owner, but also makes the operation of the vehicle owner very cumbersome.

[0003] Each application, product and service in the cockpit defines and stores its own data, so that these data are mutually isolated and difficult to associate, thus becoming a "island" in reality, and it is difficult to play a greater role in business value. SUMMARY

[0004] To solve the above problems, the present application provides a method for associating login and logout of a vehicle machine account and an ecological application account and a vehicle machine system.

[0005] In one aspect of the present application, a method for associating login and logout of a vehicle machine account and an ecological application account is provided, comprising the following steps:

[0006] opening a vehicle machine application;

[0007] selecting an ecological application account, authorizing login and requesting an application account from the vehicle machine account One ID;

[0008] obtaining the application account, according to the authorization process, the user selects the application account, authorizes login to the vehicle machine application, and sends a Token for login to the current vehicle machine application to the vehicle machine application;

[0009] The vehicle machine application receives the Token, queries the Token of the vehicle machine application logged in by the application account through the vehicle machine application background, judges whether there is a Token corresponding to the application account, and performs association login / association logout according to the judgment result.

[0010] As an optional embodiment of the present application, the Token of the vehicle machine application logged in by the application account is queried through the vehicle machine application background, it is judged whether there is a Token corresponding to the application account, and association login / association logout is performed according to the judgment result, comprising:

[0011] If the car machine application background queries the Token of the car machine application logged in by the application account and finds that the Token of the application account exists in the car machine application, it indicates that the application account has successfully logged in the car machine application.

[0012] As an optional embodiment of the present application, the Token of the car machine application logged in by the application account is queried by the car machine application background, and it is determined whether the Token corresponding to the application account exists. According to the determination result, the login or logout is performed. Further, the method comprises the following steps:

[0013] If the car machine application background queries the Token of the car machine application logged in by the application account and finds that the Token of the application account does not exist in the car machine application, it indicates that the application account has not successfully logged in the car machine application.

[0014] The car machine application displays the application account to the user and prompts the user to input the verification code.

[0015] The user inputs the verification code according to the prompt.

[0016] The car machine application is waited for verification.

[0017] As an optional embodiment of the present application, the Token of the car machine application logged in by the application account is queried by the car machine application background, and it is determined whether the Token corresponding to the application account exists. According to the determination result, the login or logout is performed. Further, the method comprises the following steps:

[0018] The car machine application receives and determines whether the verification code is correct.

[0019] If the verification code is incorrect, the user is prompted to input the correct verification code again.

[0020] If the verification code is correct, the car machine application requests the Token of the car machine application logged in by the application account from the car machine application background and sends the verification code to the car machine application background.

[0021] The car machine application background receives the verification code, registers or logs in by using the verification code of the application account, and returns the corresponding Token to the car machine application.

[0022] The car machine application receives and verifies the Token, indicating that the login is successful.

[0023] As an optional embodiment of the present application, when the user selects the application account and authorizes to log in the car machine application, the method further comprises the following steps:

[0024] The car machine account One ID cancels the authorization, and the user has no right to log in the car machine application.

[0025] As an optional embodiment of the present application, after the login or logout is performed according to the determination result, the method further comprises the following steps:

[0026] logging into the vehicle machine application to obtain a vehicle machine account ID;

[0027] mapping and matching the vehicle machine account ID and the vehicle machine account One ID to obtain a vehicle owner state;

[0028] logging in or logging out of the vehicle machine application according to the vehicle owner state.

[0029] As an optional embodiment of the present application, logging in or logging out of the vehicle machine application according to the vehicle owner state comprises:

[0030] If the vehicle owner state shows that the vehicle owner has not logged in, it is determined whether the vehicle machine account logged in by the current vehicle machine application has a binding relationship with the vehicle machine:

[0031] If yes, the vehicle machine account logged in by the current vehicle machine application is logged out;

[0032] If no, the current login state is maintained.

[0033] As an optional embodiment of the present application, logging in or logging out of the vehicle machine application according to the vehicle owner state comprises:

[0034] If the vehicle owner state shows that the vehicle owner has logged in but has not been authorized, the current login state is maintained.

[0035] As an optional embodiment of the present application, logging in or logging out of the vehicle machine application according to the vehicle owner state comprises:

[0036] If the vehicle owner state shows that the vehicle owner has logged in and has been authorized, it is determined whether the vehicle machine account has been bound to an application account:

[0037] If the vehicle machine account has been bound to the application account, the bound application account is queried, and a login process is performed using the queried application account;

[0038] If the vehicle machine account has not been bound to the application account, the current login state is maintained.

[0039] In another aspect of the present application, a vehicle machine system is provided, comprising:

[0040] a processor;

[0041] a memory for storing processor executable instructions;

[0042] The processor is configured to execute the executable instructions to implement the vehicle machine account and ecological application account login and logout method.

[0043] In another aspect of the present application, a

[0044] Technical effects of the present application:

[0045] This application, through the construction of One ID, breaks down the current data silos, accurately identifies customer behavior (browsing, purchasing, entertainment, etc.), essentially creating a personalized "identity and behavior" "business card" for each user. This supports the implementation of marketing scenarios (targeted advertising, precise push notifications, personalized recommendations, add-on purchases, churn warnings, etc.) and the needs of lean operations (precise customer data analysis, precise audience targeting, precise segmented operations, etc.). In terms of data management, it helps in the accumulation of data assets, facilitating enterprise data management, visualization, and evaluability of data assets. It also enables seamless login and logout between ecosystem application accounts and vehicle system accounts, and is not limited to already logged-in vehicles; for new vehicles, the application should also be able to automatically log in after the account is logged in.

[0046] The practical use cases of this invention connect user data between the vehicle infotainment system, the car owner's app, and the vehicle's ecosystem applications. Applications seen in different vehicle infotainment modes are controllable, enabling joint login and logout of ecosystem application accounts and vehicle infotainment accounts. These include:

[0047] Vehicle owner APP registration and login, vehicle system login, and vehicle ecosystem application registration and login support mobile phone number verification code;

[0048] In different driving modes, car owners can control the ecosystem applications they can see;

[0049] Switch vehicle system accounts to enable joint login and logout of ecosystem application accounts.

[0050] By leveraging One ID to connect user data scattered across various platforms, the entire customer lifecycle journey can be integrated, enabling data fusion across different platforms and thereby improving business efficiency and user experience.

[0051] Other features and aspects of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0052] The accompanying drawings, which are included in and form part of this specification, illustrate exemplary embodiments, features, and aspects of this disclosure together with the specification and serve to explain the principles of this disclosure.

[0053] Figure 1 The diagram illustrates the implementation process of the vehicle-mounted system application of the present invention using vehicle-mounted system account authorization login;

[0054] Figure 2 The diagram illustrates the implementation process of the vehicle-mounted system application obtaining the vehicle-mounted system account login status according to the present invention. Detailed Implementation

[0055] Various exemplary embodiments, features, and aspects of this disclosure will now be described in detail with reference to the accompanying drawings. The same reference numerals in the drawings denote elements that have the same or similar functions. Although various aspects of the embodiments are shown in the drawings, they are not necessarily drawn to scale unless specifically indicated otherwise.

[0056] The term “exemplary” as used herein means “serving as an example, embodiment, or illustration.” Any embodiment illustrated herein as “exemplary” is not necessarily to be construed as superior to or better than other embodiments.

[0057] Furthermore, to better illustrate this disclosure, numerous specific details are set forth in the following detailed description. Those skilled in the art will understand that this disclosure can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art have not been described in detail in order to highlight the main points of this disclosure.

[0058] The implementation of this embodiment involves vehicle-mounted applications, vehicle-mounted application backends, users, and vehicle-mounted accounts (One ID). Specifically, by utilizing the integrated One ID SDK, vehicle-mounted accounts and vehicle-mounted ecosystem application accounts are interconnected and bound together.

[0059] The One ID system was built to break down these data silos. Also known as ID-Mapping, One ID maps various device IDs (such as phone MAC, IMEI, IMSI, etc.), phone numbers, ID card numbers, email addresses, in-vehicle tokens, usernames, etc., to a single, unified ID using tagging systems, knowledge graphs, machine learning, and other technologies and algorithms. This means that regardless of the user's login ID—whether through the in-vehicle system or a mobile app—the system can identify them as a unique individual.

[0060] By leveraging One ID to connect user data scattered across various platforms, the entire customer lifecycle journey can be integrated, enabling data fusion across different platforms and thereby improving business efficiency and user experience.

[0061] This embodiment uses a technical solution for identity verification based on a requested token and a method for unified management of application account IDs using One ID. These are existing technologies in the industry and will not be elaborated upon in this embodiment.

[0062] This invention enables account interoperability, binding, and joint login / logout by integrating with the OneID SDK. On one hand, it identifies vehicle owners (phone number, name, ID number, VIN, license plate number, etc.) from multiple data sources according to certain rules, integrates customer data, and assigns a unique ID to the same vehicle owner. On the other hand, it binds and isolates the relationship between vehicle account and ecosystem application account by modifying the system code.

[0063] Example 1

[0064] This embodiment describes the process of authorizing login using a vehicle account for in-vehicle applications: The in-vehicle application obtains the mobile phone number bound to the account through vehicle account authorization, and logs into the application account system using the mobile phone number after entering the SMS verification code.

[0065] like Figure 1 As shown, this application proposes a method for joint login and logout of vehicle system accounts and ecosystem application accounts, including the following steps:

[0066] Open the in-vehicle infotainment app; the user selects the in-vehicle infotainment app, opens the app, and then logs in by authorizing their mobile phone number.

[0067] Select an ecosystem application account, authorize login, and request the application account from the vehicle's One ID account; the vehicle application requests account login from the vehicle's One ID account (similar to an account manager), the vehicle's One ID account receives the request, and issues the account;

[0068] The system obtains the application account, and following the authorization process, the user selects the application account, authorizes login to the vehicle infotainment application, and sends a token for logging into the current vehicle infotainment application to the vehicle infotainment application; the user obtains the account and follows the vehicle infotainment system's login process to select authorized login.

[0069] The vehicle infotainment application receives the token and queries the vehicle infotainment application backend for the token of the application account that logged in to the vehicle infotainment application. It then determines whether there is a token corresponding to the application account and performs joint login / logout based on the determination result.

[0070] After a user authorizes login to the vehicle infotainment application, the application needs to use its backend (backend server, etc.) to query the login token for that phone number for identity verification. If the application's token for that phone number is found, it means that the phone number can successfully log in to the vehicle infotainment application; otherwise, the phone number needs to be displayed, prompting the user to enter a verification code to log in.

[0071] Using the above login method allows for simultaneous login / logout of in-vehicle applications under the One ID account management system. In-vehicle applications obtain the account-linked mobile phone number through vehicle account authorization, and then log in to the application account system using this mobile phone number after entering an SMS verification code.

[0072] The following is the process for users to log in again using verification codes. Please refer to the appendix for the specific implementation process for each entity. Figure 1 This will be understood, and will not be elaborated further below.

[0073] As an optional implementation of this application, optionally, the system queries the vehicle infotainment application backend for the token of the login account to determine whether a token corresponding to the application account exists, and performs joint login / logout based on the determination result, including:

[0074] If the vehicle infotainment application backend finds that the application account has the application account's token in the vehicle infotainment application it is logged into, it means that the application account has successfully logged into the vehicle infotainment application.

[0075] As an optional implementation of this application, optionally, the system queries the vehicle infotainment application backend for the token of the login account to determine whether a token corresponding to the application account exists, and performs joint login / logout based on the determination result. This also includes:

[0076] If the vehicle infotainment application backend query finds that the application account does not have the application account's token in the vehicle infotainment application it is logged into, it means that the application account has not successfully logged into the vehicle infotainment application.

[0077] The in-vehicle application displays the application account to the user and prompts the user to enter a verification code;

[0078] The user enters the verification code as prompted;

[0079] Awaiting verification of the in-vehicle infotainment application.

[0080] As an optional implementation of this application, optionally, the system queries the vehicle infotainment application backend for the token of the login account to determine whether a token corresponding to the application account exists, and performs joint login / logout based on the determination result. This also includes:

[0081] The vehicle-mounted application receives and verifies whether the verification code is correct.

[0082] If incorrect, prompt the user to re-enter the correct verification code;

[0083] If correct, the vehicle infotainment application requests the token of the vehicle infotainment application logged in by the application account from the vehicle infotainment application backend, and sends the verification code to the vehicle infotainment application backend;

[0084] The vehicle infotainment application backend receives the verification code, uses the verification code of the application account to register / login, and returns the corresponding Token to the vehicle infotainment application;

[0085] The vehicle-mounted application receives and verifies the token, indicating successful login.

[0086] As an optional implementation of this application, when the user selects the application account and authorizes login to the vehicle-mounted application, the following method may also be included:

[0087] The One ID account for the vehicle infotainment system has been deauthorized, and the user is no longer authorized to log in to the vehicle infotainment application.

[0088] Based on the above login, users can log in / out of the vehicle terminal application.

[0089] Therefore, by adopting this method, the registration and login of the car owner's APP, the vehicle system, and the vehicle ecosystem applications support mobile phone verification codes. Under different car owner modes, the visible ecosystem applications can be controlled.

[0090] The next step requires the vehicle infotainment application to obtain the vehicle account login status:

[0091] Because the vehicle system account may switch to different accounts depending on the actual user, the application needs to call the interface to get the latest account status after startup or when it receives an account change notification.

[0092] Example 2

[0093] like Figure 2 As shown, as an optional implementation of this application, optionally, after performing joint login / refund based on the judgment result, it further includes:

[0094] Log in to the vehicle's infotainment system and obtain your vehicle account ID;

[0095] Map and match the vehicle system account ID with the vehicle system account One ID to obtain the vehicle owner status;

[0096] Login / logout to in-vehicle applications based on the vehicle owner's status.

[0097] As an optional implementation of this application, the vehicle-mounted application may optionally be logged in / out based on the vehicle owner's status, including:

[0098] If the vehicle owner's status shows "not logged in," then it is determined whether the vehicle account currently logged into the vehicle infotainment application is linked to the vehicle infotainment system:

[0099] If so, log out of the vehicle infotainment account currently logged into the vehicle infotainment application;

[0100] If not, then remain logged in.

[0101] As an optional implementation of this application, the vehicle-mounted application may optionally be logged in / out based on the vehicle owner's status, including:

[0102] If the vehicle owner's status shows "First Time / Logged In But Not Authorized", then the current login status will remain.

[0103] As an optional implementation of this application, the vehicle-mounted application may optionally be logged in / out based on the vehicle owner's status, including:

[0104] If the vehicle owner's status shows "login" and "authorized," then determine whether the vehicle's infotainment system account is already linked to the application account:

[0105] If an application account has been linked, query the linked application account and use the queried application account to execute the login process;

[0106] If no application account is linked, the current login status will remain.

[0107] Please refer to the appendix for details of the above process. Figure 2 The application implementation process of each entity will not be described in detail in this embodiment.

[0108] Let's take a few users as examples:

[0109] User A1 logs in to their account on vehicle A, opens the application, and logs in using their account. User A2 logs in to their account on vehicle A, opens the application, and logs in using their account. When switching between users A1 and A2 on vehicle A, the application synchronously switches the corresponding account. If a new user A3 logs in on vehicle A, while other ecosystem users remain logged in, the application's business logic guides the user to log in or bind their account.

[0110] When user A1 logs into their account in vehicle B, and the user opens the application, the application can simultaneously log into user A1's account.

[0111] Therefore, this application enables simultaneous login and logout of ecosystem application accounts and vehicle infotainment system accounts, and is not limited to logged-in vehicles. It allows control over which ecosystem applications are visible across different vehicle owner modes. Switching between vehicle infotainment system accounts enables simultaneous login and logout of ecosystem application accounts.

[0112] For new vehicles, applications should also be able to log in automatically after the account is logged in. User data should be integrated between the vehicle's infotainment system, the owner's app, and other ecosystem applications. Applications seen in different vehicle modes should be controllable, enabling simultaneous login and logout of ecosystem application accounts and vehicle account.

[0113] It should be noted that although the above authentication method is illustrated using a token as an example, those skilled in the art will understand that this disclosure is not limited to this. In fact, users can flexibly set the authentication mechanism according to their actual application scenarios, as long as the technical functions of this application can be achieved by following the above technical methods.

[0114] Obviously, those skilled in the art should understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above control methods.

[0115] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the control methods described above. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk drive (HDD), or solid-state drive (SSD), etc.; the storage medium can also include combinations of the above types of memory.

[0116] Example 3

[0117] Furthermore, in another aspect, this application proposes an in-vehicle infotainment system, comprising:

[0118] processor;

[0119] Memory used to store processor-executable instructions;

[0120] The processor is configured to implement the method for jointly logging in and out of vehicle system accounts and ecosystem application accounts when executing the executable instructions.

[0121] This disclosure discloses a vehicle-mounted system including a processor and a memory for storing processor-executable instructions. The processor is configured to implement, when executing the executable instructions, any of the aforementioned methods for joint login and logout of vehicle-mounted accounts and ecosystem application accounts.

[0122] It should be noted here that the number of processors can be one or more. Furthermore, the vehicle infotainment system of this embodiment may also include input devices and output devices. The processor, memory, input devices, and output devices can be connected via a bus or other means, without specific limitations herein.

[0123] The memory, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and various modules, such as the program or module corresponding to the method for jointly logging in and out of a vehicle-mounted account and an ecosystem application account according to an embodiment of this disclosure. The processor executes various functional applications and data processing of the vehicle-mounted system by running the software programs or modules stored in the memory.

[0124] Input devices can be used to receive input digital numbers or signals. These signals can be key signals related to user settings and function control of the device / terminal / server. Output devices can include display devices such as screens.

[0125] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, and are not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical applications, or technical improvements to the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for joint login and logout of vehicle-mounted system accounts and ecosystem application accounts, characterized in that, Includes the following steps: Open the car infotainment app; Select an ecosystem application account, authorize login, and request the application account from the vehicle's One ID account. The One ID is used to map the device ID, mobile phone number, ID card number, email address, vehicle's token, and username to a unified ID. By accessing the OneID SDK, account interoperability, binding, and joint login and logout are completed. The vehicle owner's identity from multiple data sources is identified, customer data is integrated, and a unique ID is assigned to the same vehicle owner. By modifying the system code, the relationship between the vehicle account and the ecosystem application account is bound and data is isolated. Obtain the application account, follow the authorization process, the user selects the application account, authorizes login to the vehicle system application, and sends the token for logging into the current vehicle system application to the vehicle system application; The in-vehicle application receives the token and queries the in-vehicle application backend for the token associated with the account logged in, determining whether a token corresponding to the account exists. Based on the determination result, it performs joint login / logout, including: If the vehicle infotainment application backend finds that the application account has the application account's token in the vehicle infotainment application it is logged into, it means that the application account has successfully logged into the vehicle infotainment application. If the vehicle infotainment application backend query finds that the application account does not have the application account's token in the vehicle infotainment application it is logged into, it means that the application account has not successfully logged into the vehicle infotainment application. The in-vehicle application displays the application account to the user and prompts the user to enter a verification code; The user enters the verification code as prompted; Awaiting verification of the aforementioned in-vehicle application; The vehicle-mounted application receives and verifies whether the verification code is correct. If incorrect, prompt the user to re-enter the correct verification code; If correct, the vehicle infotainment application requests the token of the vehicle infotainment application logged in by the application account from the vehicle infotainment application backend, and sends the verification code to the vehicle infotainment application backend; The vehicle infotainment application backend receives the verification code, uses the verification code of the application account to register / login, and returns the corresponding Token to the vehicle infotainment application; The vehicle-mounted application receives and verifies the token, indicating successful login; The in-vehicle application obtains the mobile phone number bound to the account through vehicle account authorization, and logs into the application account system after entering the SMS verification code using the mobile phone number; By using the above method to log in, you can achieve joint login / logout of vehicle-mounted applications under the One ID account management, including: Vehicle owner APP registration and login, vehicle system login, and vehicle ecosystem application registration and login support mobile phone number verification code; In different driving modes, car owners can control the ecosystem applications they can see; Switch vehicle system accounts to enable joint login and logout of ecosystem application accounts; One ID connects user data scattered across various platforms, integrates the entire customer lifecycle journey, and enables data fusion across platforms.

2. The method for joint login and logout of vehicle-mounted account and ecosystem application account according to claim 1, characterized in that, When the user selects the application account and authorizes login to the in-vehicle application, the following is also included: The One ID account for the vehicle infotainment system has been deauthorized, and the user is no longer authorized to log in to the vehicle infotainment application.

3. The method for joint login and logout of vehicle-mounted system account and ecosystem application account according to claim 1, characterized in that, After processing the joint login / logout based on the assessment results, the following is also included: Log in to the vehicle's infotainment system and obtain your vehicle account ID; Map and match the vehicle system account ID with the vehicle system account One ID to obtain the vehicle owner status; Login / logout to in-vehicle applications based on the vehicle owner's status.

4. The method for joint login and logout of vehicle system account and ecosystem application account according to claim 3, characterized in that, Login / logout to in-vehicle applications based on the vehicle owner's status, including: If the vehicle owner's status shows "not logged in," then it is determined whether the vehicle account currently logged into the vehicle infotainment application is linked to the vehicle infotainment system: If so, log out of the vehicle infotainment account currently logged into the vehicle infotainment application; If not, then remain logged in.

5. The method for joint login and logout of vehicle-mounted account and ecosystem application account according to claim 4, characterized in that, Login / logout to in-vehicle applications based on the vehicle owner's status, including: If the vehicle owner's status shows "First Time / Logged In But Not Authorized", then the current login status will remain.

6. The method for joint login and logout of vehicle system account and ecosystem application account according to claim 4, characterized in that, Login / logout to in-vehicle applications based on the vehicle owner's status, including: If the vehicle owner's status shows "login" and "authorized," then determine whether the vehicle's infotainment system account is already linked to the application account: If an application account has been linked, query the linked application account and use the queried application account to execute the login process; If no application account is linked, the current login status will remain.

7. A vehicle infotainment system, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to implement, when executing the executable instructions, a method for jointly logging in and out of vehicle system accounts and ecosystem application accounts as described in any one of claims 1 to 6.

Images