Upon the Web Browser’s request for /index.html, the Web Server will respond with the index.html HTML file and a 200 status code.

Upon the Web Browser’s request for another HTML file, the Web Server will respond with a response with 409 status code.

Upon the Web Browser’s request, the Web Server will respond with the Javascript files linked in and a 200 status code.

Upon the Web Browser’s request for an unknown or not approved Javascript script, the Web Server will respond with a response with 409 status code.

Upon the Web Browser’s request, the Web Server will respond with the CSS Stylesheet files linked in and a 200 status code.

Upon the Web Browser’s request for an unknown or not approved CSS Stylesheet file, the Web Server will respond with a response with 409 status code.

Upon the Web Browser’s request, the Web Server can start a new VIN insertion process and if a new database entry is created, it will respond with a ‘Row Inserterd’ message in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a new VIN insertion process and if a database entry already exists, it will respond with a ‘VIN alread exists’ message in the response body and a 409 status code.

Upon the Web Browsers’s request, the Web Server can look for the Package ID lookup process and if the Package exists, it will respond with a ‘Campaign created’ message in the response body and a 200 status code.

Upon the Web Browsers’s request, the Web Server can lookup for the Package ID, and if the Package does not exist, it will respond with a ‘Unknown Package ID’ message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a new Filter insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a new Filter insertion process and if a database entry already exists, it will respond with a ‘Filter already exists’ message in the response body and a 409 status code.

Upon the Web Browser’s request, the Web Server can start a new Filter/Package association insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a new Filter/Package association insertion process and if a database entry already exists, it will respond with a ‘Filter/Package association already exists’ message in the response body and a 409 status code.

Upon the Web Browser’s request, the Web Server can start a Queue Package Request process and if a request is processed without errors, it will respond with a unique Install Request ID in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Queue Package Request process and if the given package ID is not found, it will respond with a ‘Package ID does not exist’ message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a Queue Package Request process and if no filters are associated with the package, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon receiving unauthenticated request from Web Browser, Web Server sends login page HTML and assets over HTTPS (port 443) to Web Browser.

When user enters and submit credentials in Web Browser, Web Browser sends the credentials to Web Server over HTTPS POST (port 443),

If the credentials are valid, Web Server sends Admin GUI page content and session cookie to Web Browser over HTTPS (port 443)

If the credentials are invalid, Web Server sends Access Denied (HTTP 401) to Web Browser over HTTPS (port 443)

In response to a request from a Web Browser, Web Server may include an HTTP Cookie to establish a session

When requesting resources from Web Server, Web Browser may include any locally stored HTTP Cookie associated with the Admin GUI domain

In response to HTTPS (port 443) requests from a Web Browser, the Web Server may send HTTPS 301 redirect responses to unauthenticated clients

In response to HTTPS (port 443) requests from a Web Browser that include valid login credentials, the Web Server may send an HTTPS 301 response to authenticated clients for protected resources.

Web Browser may send HTTPS (port 443) requests to Web Server on behalf of user for protected Admin GUI resources

Requests may include any locally stored Cookies associated with the Admin GUI Domain

In response to authenticated HTTPS (port 443) requests from Web Browser for protected Admin GUI resources, Web Server may send back associated HTML and resources to render resource details and necessary hyperlinks, JavaScript code, assets, etc. to Web Browser.

Upon the Web Browser’s request, the Web Server can start a List Queue Package Request process and if a request is processed without errors, it will respond with a unique Install Request ID in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a List Queue Package Request process and if the given package ID is not found, it will respond with a ‘Package ID does not exist’ message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a List Queue Package Request process and if no filters are associated with the one of the packages, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a get Queued Package Request process and if a request is processed without errors, it will respond with a list of queued update requests in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a get Queued Package Request process and if there are no pending update requests, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a List Queue Package Request process and if no filters are associated with the one of the packages, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a Search VINs Request process and if a request is processed without errors, it will respond with a list of VINs matching the search criteria in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Search VINs Request process and if there are no VINs matching the search criteria, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Search VINs Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can receive a binary package and its associated metadata and perform an Upload New Package process and if the request is processed without errors, it will respond with a message informing for successful persistence in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can receive a binary package and its associated metadata and perform an Upload New Package process and if the request is processed with errors, it will respond with a message informing for the generated error in the response body and a 500 status code.

Upon the Web Browser’s request, Web Server can receive the metadata associated with a new package and if SOTA Core fails to authenticate, it will respond with an ‘Authentication Failed’ message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a Search Filters Request process and if a request is processed without errors, it will respond with a list of Filters matching the search criteria in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Search Filters Request process and if there are no Filters matching the search criteria, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Search Filters Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a Search List Request process and if a request is processed without errors, it will respond with a list of available Filters in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Search Filters Request process and if there are no available Filters, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a List Filters Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a Update Filter Request process and if a request is processed without errors, it will respond with a list of available Filters in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Update Filter Request process and if there is no Filter with the given Filter ID, it will respond with a ‘Filter does not exist’ message in the response body and a 409 status code.

Upon the Web Browser’s request, the Web Server can start a Update Filter Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a Delete Filter Request process and if a request is processed without errors, it will respond with a list of available Filters in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Delete Filter Request process and if there is no Filter with the given Filter ID, it will respond with a ‘Filter does not exist’ message in the response body and a 409 status code.

Upon the Web Browser’s request, the Web Server can start a Delete Filter Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start an Update Packages per VIN Request process and if a request is processed without errors, it will respond with the modified package data for the selected VIN in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start an Update Packages per VIN Request process and if the given VIN does not exist, it will respond with a ‘VIN does not exist’ message in the response body and a 409 status code.

Upon the Web Browser’s request, the Web Server can start an Update Packages per VIN Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a View Packages per VIN Request process and if a request is processed without errors, it will respond with the installed packages on the selected VIN in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a View Packages per VIN Request process and if the given VIN does not exist, it will respond with a ‘VIN does not exist’ message in the response body and a 409 status code.

Upon the Web Browser’s request, the Web Server can start a View Packages per VIN Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a View VINs per Package Request Request process and if a request is processed without errors, it will respond with the VINs that have installed the selected Package in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a View VINs per Package Request process and if the given Package does not exist, it will respond with a ‘Package does not exist’ message in the response body and a 409 status code.

Upon the Web Browser’s request, the Web Server can start a View VINs per Package Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a new Component insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a new Component insertion process and if a database entry already exists, it will respond with a ‘Component already exists’ message in the response body and a 409 status code.

Upon the Web Browser’s request, the Web Server can start a Search Components Request process and if a request is processed without errors, it will respond with a list of Components matching the search criteria (regex, ID/IDs or name) in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Search Components Request process and if there are no Components matching the search criteria, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Browser’s request, the Web Server can start a Search Components Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can send a "Get Install Request Completed" and if the request has been processed without errors, it will respond with a list of VINs where the Install Request was successfully completed and the associated timestamp when the Request was finished in the response body and a 200 response code.

Upon the Web Browser’s request, the Web Server can send a "Get Install Request Completed" and if no VINs have been returned, it will return an empty list in the response body and a 200 response code.

Upon the Web Browser’s request, the Web Server can send a "Get Install Request Completed" and if the request has been processed with errors, it will respond with the apropriate error message in the response body and a 200 response code.

Upon the Web Server’s request, SOTA Core can start a new Package insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can start a new Package insertion process and if a database entry already exists, it will respond with a ‘Package already exists’ message in the response body and a 409 status code.

Upon the Web Server’s request, SOTA Core can start a new VIN insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can start a new VIN insertion process and if a database entry already exists, it will respond with a ‘VIN already exists’ message in the response body and a 409 status code.

Upon the Web Server’s request, SOTA Core can look for the Package ID lookup process and if the Package exists, it will respond with a ‘Campaign created’ message in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can lookup for the Package ID, and if the Package does not exist, it will respond with a ‘Unknown Package ID’ message in the response body and a 404 status code.

Upon the Web Server’s request, Core can start a Queue Package Request process and if a request is processed without errors, it will respond with a unique Install Request ID in the response body and a 200 status code.

Upon the Web Server’s request, Core can start a Queue Package Request process and if the given package ID is not found, it will respond with a ‘Package ID does not exist’ message in the response body and a 404 status code.

Upon the Web Browser’s request, the Web Server can start a Queue Package Request process and if no filters are associated with the package, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon the Web Server’s request, SOTA Core can start a List Queue Package Request process and if a request is processed without errors, it will respond with a unique Install Request ID in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can start a List Queue Package Request process and if the given package ID is not found, it will respond with a ‘Package ID does not exist’ message in the response body and a 404 status code.

Upon the Web Server’s request, SOTA Core can start a List Queue Package Request process and if no filters are associated with the one of the packages, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon the Web Server’s request, the SOTA Core can start a get Queued Package Request process and if a request is processed without errors, it will respond with a list of queued update requests in the response body and a 200 status code.

Upon the Web Server’s request, the SOTA Core can start a get Queued Package Request process and if there are no pending update requests, it will respond with an empty list of queued update requests in the response body and a 200 status code.

Upon the Web Server’s request, the SOTA Core can start a get Queued Package Request process and if no filters are associated with the one of the packages, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon the Web Server’s request, SOTA Core can start a Search VINs Request process and if a request is processed without errors, it will respond with a list of VINs matching the search criteria in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can start a Search VINs Request process and if there are no VINs matching the search criteria, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can start a Search VINs Request process and if no filters are associated with the one of the packages, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon the Web Server’s request, the SOTA Core can start an Update Packages per VIN Request process and if a request is processed without errors, it will respond with the modified package data for the selected VIN in the response body and a 200 status code.

Upon the Web Server’s request, the SOTA Core can start an Update Packages per VIN Request process and if the given VIN does not exist, it will respond with a ‘VIN does not exist’ message in the response body and a 409 status code.

Upon the Web Server’s request, the SOTA Core can start an Update Packages per VIN Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Server’s request, the SOTA Core can start a View Packages per VIN Request process and if a request is processed without errors, it will respond with the installed packages on the selected VIN in the response body and a 200 status code.

Upon the Web Server’s request, the SOTA Core can start a View Packages per VIN Request process and if the given VIN does not exist, it will respond with a ‘VIN does not exist’ message in the response body and a 409 status code.

Upon the Web Server’s request, the SOTA Core can start a Update Package per VIN Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Server’s request, SOTA Core can start a View VINs per Package Request Request process and if a request is processed without errors, it will respond with the VINs that have installed the selected Package in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can start a View VINs per Package Request process and if the given Package does not exist, it will respond with a ‘Package does not exist’ message in the response body and a 409 status code.

Upon the Web Server’s request, SOTA Core can start a View VINs per Package Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Server’s request, SOTA Core can look for the Component ID lookup process and if the Component exists, it will respond with a ‘Component already created’ message in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can lookup for the Component ID, and if the Component does not exist, it will respond with a ‘Unknown Package ID’ message in the response body and a 404 status code.

Upon the Web Server’s request, SOTA Core can start a Search Components Request process and if a request is processed without errors, it will respond with a list of Components matching the search criteria (regex, ID/IDs or name) in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can start a Search Components Request process and if there are no Components matching the search criteria, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Server’s request, SOTA Core can start a Search Components Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Server’s request, the SOTA Core can send a "Get Install Request Completed" and if the request has been processed without errors, it will respond with a list of VINs where the Install Request was successfully completed and the associated timestamp when the Request was finished in the response body and a 200 response code.

Upon the Web Server’s request, the SOTA Core can send a "Get Install Request Completed" and if no VINs have been returned, it will return an empty list in the response body and a 200 response code.

Upon the Web Server’s request, the SOTA Core can send a "Get Install Request Completed" and if the request has been processed with errors, it will respond with the apropriate error message in the response body and a 200 response code.

Upon the Web Server’s request, the External Resolver can start a new Package insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a new Package insertion process and if a database entry already exists, it will respond with a ‘VIN already exists’ message in the response body and a 409 status code.

Upon the Web Server’s request, the External Resolver can start a new VIN insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a new VIN insertion process and if a database entry already exists, it will respond with a ‘VIN already exists’ message in the response body and a 409 status code.

Upon the Web Server’s request, the External Resolver can start a new Filter/Package association insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a new Filter/Package association insertion process and if a database entry already exists, it will respond with a ‘Filter/Package association already exists’ message in the response body and a 409 status code.

Upon the Web Server’s request, the External Resolver can start a new Filter/Package association insertion process and if the Filter does not exist, it will respond with a ‘Filter label does not exist’ message in the response body and a 404 status code.

Upon the Web Server’s request, the External Resolver can start a new Filter/Package association insertion process and if the Package does not exist, it will respond with a Package ID does not exist’ message in the response body and a 404 status code.

Upon the Web Server’s request, the External Resolver can start a new Filter insertion process and if a new database entry is created, it will respond with a ‘Row Inserted’ message in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a new Filter insertion process and if a database entry already exists, it will respond with a ‘Filter already exists’ message in the response body and a 409 status code.

Upon the Web Server’s request, the External Resolver can start a new Filter insertion process and if the Filter expression fails validation, it will respond with a ‘Filter failed validation’ message in the response body and a 406 status code.

Upon the Web Server’s request, the External Resolver can resolve the dependencies for all VINs involved and if the request is processed without errors, it will respond with the subset of all VINs that passed all filters in the response body and a 200 status code.

Upon Web Server’s request, the External Resolver can resolve the dependencies for all VINs involved and if no filters are associated with the package, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon the Web Server’s request, the External Resolver can start a Search Filters Request process and if a request is processed without errors, it will respond with a list of Filters matching the search criteria in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a Search Filters Request process and if there are no Filters matching the search criteria, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a Search Filters Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Server’s request, the External Resolver can start a Search List Request process and if a request is processed without errors, it will respond with a list of available Filters in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a Search Filters Request process and if there are no available Filters, it will respond with an empty list in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a List Filters Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Server’s request, the External Resolver can start a Update Filter Request process and if a request is processed without errors, it will respond with a list of available Filters in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a Update Filter Request process and if there is no Filter with the given Filter ID, it will respond with a ‘Filter does not exist’ message in the response body and a 409 status code.

Upon the Web Server’s request, the External Resolver can start a Update Filter Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

Upon the Web Server’s request, the External Resolver can start a Delete Filter Request process and if a request is processed without errors, it will respond with a list of available Filters in the response body and a 200 status code.

Upon the Web Server’s request, the External Resolver can start a Delete Filter Request process and if there is no Filter with the given Filter ID, it will respond with a ‘Filter does not exist’ message in the response body and a 409 status code.

Upon the Web Server’s request, the External Resolver can start a Delete Filter Request process and if an error occurs, it will respond with an error message in the response body and a 404 status code.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new VIN data and if a new database entry is created, it will respond with a ‘Success’ message.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new VIN data and if the VIN already exists, it will respond with a ‘Record exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Package data and if a new database entry is created, it will respond with a ‘Success’ message.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Package data and if the Package already exists, it will respond with a ‘Record exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given Package ID and if an entry is found, it will respond with the Package’s data.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given Package ID and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given Update ID and if an entry is found, it will respond with the Package’s data.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given Update ID and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given search criteria and if an entry is found, it will respond with the VINs’ data.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given search criteria and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given VIN and if an entry is found, it will respond with Package data associated with the VIN.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given VIN and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an UPDATE operation with the package data for the selected VIN and if an entry is found, it will respond with the VINs’ data.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given VIN and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given Package ID and if an entry is found, it will respond with the VINs who have installed the given package.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given Package ID and if no VINs are found, it will respond with a ‘No VINs have this package installed’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Component data and if a new database entry is created, it will respond with a ‘Success’ message.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Component data and if the VIN already exists, it will respond with a ‘Record exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given Component ID and if an entry is found, it will respond with the Package’s data.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given Component ID and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given Install Request ID and if one or more VINs with the a successful installation for the given Install Request ID is found, it will respond with the VINs and the timestamp the installation has been completed data.

If SOTA Core authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given Install Request ID and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

Upon the SOTA Core’s request, the External Resolver can resolve the dependencies for all VINs involved and if the request is processed without errors, it will respond with the subset of all VINs that passed all filters in the response body and a 200 status code.

Upon SOTA Core’s request, the External Resolver can resolve the dependencies for all VINs involved and if no filters are associated with the package, it will respond with a ‘No filters associated with package’ message in the response body and a 404 status code.

Upon SOTA Core’s request, the External Resolver can update the External Resolver Database with the result of the install report and if the result code is SUCCESS it will update the installed package list and reply with a 'package installed' message in the response body and a 200 status code.

Upon SOTA Core’s request, the External Resolver can update the External Resolver Database with the result of the install report and if the result code is not SUCCESS, reply with a 'package installation failed' message in the response body and a 500 status code.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new VIN data and if a new database entry is created, it will respond with a ‘Success’ message.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new VIN data and if the VIN already exists, it will respond with a ‘Record exists’ message.

If the External Resolver does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Package data and if a new database entry is created, it will respond with a ‘Success’ message.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Package data and if the Package already exists, it will respond with a ‘Record exists’ message.

If the External Resolver does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Filter data and if a new database entry is created, it will respond with a ‘Success’ message.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Filter data and if the Filter already exists, it will respond with a ‘Record exists’ message.

If the External Resolver does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Filter/Package association and if a new database entry is created, it will respond with a ‘Success’ message.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Filter/Package association and if the Filter/Package association already exists, it will respond with a ‘Record exists’ message.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Filter/Package association and if the Filter does not exist exist, it will respond with a ‘Filter does not exist’ error message.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an INSERT operation with the new Filter/Package association and if the Package does not exist exist, it will respond with a ‘Package does not exist’ error message.

If the External Resolver does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation for all filters associated with the given Package ID and if one or more entries are found, it will respond with the Filters’ data.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation for all filters associated with the given Package ID and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given VIN and if an entry is found, it will respond with the VIN’s data.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given VIN and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given VIN and if an entry is found, it will respond with all the software dependencies for the given VIN data.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given VIN and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a SELECT operation with the given Filter ID or IDs and if an entry is found, it will respond with all the software dependencies for the given VIN data.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an SELECT operation with the given Filter ID or IDs and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an UPDATE operation with the given Filter ID or IDs and if an entry is found, it will respond with the number of Filters correctly updated.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an UPDATE operation with the given Filter ID or IDs and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a DELETE operation with the given Filter ID or IDs and if an entry is found, it will respond with the number of Filters deleted.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform a DELETE operation with the given Filter ID or IDs and if no entry is found, it will respond with a ‘Record does not exists’ message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an UPDATE operation with the given Package ID on the given VIN or VINs and if an entry is found, it will respond with the number of VINs update.

If the External Resolver authenticates successfully with the correct Username/Password credentials, upon its request, the Database Server can perform an UPDATE operation with the given Package ID on the given VIN or VINs and if no entry is found, it will respond with a 'Record does not exists' message.

If SOTA Server does not authenticate successfully due to incorrect Username/Password credentials against the Database Server, the Database Server should reject the connection.

Upon Core’s request, the RVI Node can schedule the installation of the software packages listed for every given VIN if the task is scheduled without errors, it will respond with the subset of all VINs that passed all filters in the response body and a 200 status code.

Upon Core’s request, the RVI Node can schedule the installation of the software packages listed for every given VIN and if any errors occur, it will respond with a ‘Task scheduling’ message in the response body and a 412 status code.

Upon SOTA Core’s request, the RVI Node Server can start the software update process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon SOTA Core’s request, the RVI Node Server can start the software update process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server X times to resume the update.

Upon the RVI Node Server’s request, SOTA Core can start the update download process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon the RVI Node Server’s request, SOTA Core can start the update download process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server to resume the update.

Upon the RVI Node Server’s “Cancel Software Download” request, SOTA Core can interrupt the update download process.

Upon SOTA Core’s request, RVI Node Server can start the download process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon the RVI Node Server’s request, SOTA Core can start the update download process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server to resume the update.

Upon the RVI Node Server’s “Cancel Software Download” request, SOTA Core can interrupt the update download process.

Upon SOTA Core’s request, RVI Node Server can accept the lowest numbered data block and if the data block is received without errors, it will acknowledge of successful data block receipt in the response body and a 200 status code.

Upon SOTA Core’s request, RVI Node Server can accept the lowest numbered data block and if the data block has been received before the data block will be discarded and the next data block will be requested.

Upon SOTA Core’s request, RVI Node Server can accept the lowest numbered data block and if the data block is interrupted due to network loss, it will attempt to reconnect X times and transmit again the data block.

Upon SOTA Core’s request, RVI Node Server can confirm the completion of download process and if the download is finished without errors, it will respond with ‘Download of Package ID complete’ in the response body and a 200 status code.

Upon SOTA Core’s request, RVI Node Server can confirm the completion of download process and if data blocks are missing, it will respond with ‘Incomplete Download’ in the response body and a 400 status code.

Upon the RVI Node Server’s request, SOTA Core can start the update download process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server to resume the update.

Upon the SOTA Client’s request, RVI Node Client can accept the Install Report and if the installation was finished without errors, it will respond with ‘Package ID success’ in the response body and a 200 status code.

Upon the SOTA Client’s request, RVI Node Client can accept the Install Report and if the VIN is already marked as complete, it will respond with ‘Package ID failed’ in the response body and a 409 status code.

Upon the SOTA Client’s request, RVI Node Client can accept the Install Report and if the VIN is already marked as failed, it will respond with ‘Package ID failed’ in the response body and a 409 status code.

Upon the SOTA Core’s request, RVI Node Server can accept a "Get All Packages" request and if it has been responded without errors, it will respond with a list of installed package IDs in the response body and a 200 status code.

Upon the SOTA Core’s request, RVI Node Server can accept a "Get All Packages" request if the response contained errors, it will respond with an error message in the response body and a 409 status code.

Upon the RVI Node Clients’s request, the SOTA Client can start the software update process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon the RVI Node Client’s request, the SOTA Client can start the software update process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server X times to resume the update.

Upon RVI Node Client’s request, SOTA Client can start the download process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon the RVI Node Client’s request, SOTA Client can start the update download process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server to resume the update.

Upon the RVI Node Client’s “Cancel Software Download” request, SOTA Client can interrupt the update download process.

Upon RVI Node Client’s request, SOTA Client can accept the lowest numbered data block and if the data block is received without errors, it will acknowledge of successful data block receipt in the response body and a 200 status code.

Upon RVI Node Client’s request, SOTA Client can accept the lowest numbered data block and if the data block has been received before the data block will be discarded and the next data block will be requested.

Upon RVI Node Client’s request, SOTA Client can confirm the completion of download process and if the download is finished without errors, it will respond with ‘Download of Package ID complete’ in the response body and a 200 status code.

Upon RVI Node Client’s request, SOTA Client can confirm the completion of download process and if data blocks are missing, it will respond with ‘Incomplete Download’ in the response body and a 400 status code.

Upon the RVI Node Client’s request, SOTA Client can start the update download process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server to resume the update.

Upon the SOTA Client’s request, RVI Node Client can accept the Install Report and if the installation was finished without errors, it will respond with ‘Package ID success’ in the response body and a 200 status code.

Upon the SOTA Client’s request, RVI Node Client can accept the Install Report and if the VIN is already marked as complete, it will respond with ‘Package ID failed’ in the response body and a 409 status code.

Upon the SOTA Client’s request, RVI Node Client can accept the Install Report and if the VIN is already marked as failed, it will respond with ‘Package ID failed’ in the response body and a 409 status code.

Upon the RVI Node Client’s request, SOTA Client can accept the "Get All Packages" notification and if it can retrieve all package information without errors, it will respond with a list of installed Package IDs in theresponse body and a 200 status code.

Upon the RVI Node Client’s request, SOTA Client can accept the "Get All Packages" notification and if an error occurs, it will respond with the appropriate error code in the response body and a 409 status code.

Upon SOTA Clients’s request, Software Loading Manager can start the software update process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon the SOTA Clients’s request, Software Loading Manager can start the software update process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server X times to resume the update.

Upon the Software Loading Manager’s request, SOTA Client can start the update download process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon the Software Loading Manager’s request, SOTA Client can start the update download process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server to resume the update.

Upon the Software Loading Manager’s “Cancel Software Download” request, SOTA Client can interrupt the update download process.

Upon the SOTA Client’s request, Software Loading Manager can start the update download process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon the SOTA Client’s request, Software Loading Manager can start the update download process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server to resume the update.

Upon the SOTA Client’s “Cancel Software Download” request, Software Loading Manager can interrupt the update download process.

Upon SOTA Client’s request, Software Loading Manager can start the download process and if the update is finished without errors, it will respond with ‘Installation of Package ID complete’ in the response body and a 200 status code.

Upon the SOTA Client’s request, Software Loading Manager can start the update download process and if the update is interrupted due to lost network, it will try to reconnect to RVI Node Server to resume the update.

Upon the SOTA Client’s “Cancel Software Download” request, Software Loading Manager can interrupt the update download process.

Upon SOTA Client’s request, Software Loading Manager can accept the lowest numbered data block and if the data block is received without errors, it will acknowledge of successful data block receipt in the response body and a 200 status code.

Upon SOTA Client’s request, Software Loading Manager can accept the lowest numbered data block and if the data block has been received before the data block will be discarded and the next data block will be requested.

Upon the Software Loading Manager’s request, SOTA Client can accept the Install Report and if the installation was finished without errors, it will respond with ‘Package ID success’ in the response body and a 200 status code.

Upon the Software Loading Manager’s request, SOTA Client can accept the Install Report and if the VIN is already marked as complete, it will respond with ‘Package ID failed’ in the response body and a 409 status code.

Upon the Software Loading Manager’s request, SOTA Client can accept the Install Report and if the VIN is already marked as failed, it will respond with ‘Package ID failed’ in the response body and a 409 status code.

Upon the SOTA Client’s request, Software Loading Manager can accept the "Get All Packages" notification and if no error occurs, it will respond with a list of installed Package IDs in the response body and a 200 status code.

Upon the SOTA Client’s request, Software Loading Manager can accept the "Get All Packages" notification and if an error occurs, it will reply with the appropriate error code in the response body and a 409 status code.

Upon the Web Server’s request, the Filesystem can write a binary package if the request is processed without errors, it will respond with a success error code.

Upon the Web Server’s request, the Filesystem can write a binary package if the request is processed with errors, it will respond with a failure error code.