In embodiments, a first resource is produced for a first dataset having a time indicator, by applying a first digital rule. A first notification can be caused to be transmitted about an aspect of the first resource to a remote device. A second dataset can be stored, which has values derived from the first dataset, and encodes a parameter of the first resource. A second digital rule may be stored to replace the first digital rule, at an updating time (Tupd). The second digital rule may have an effective time (Teff) prior to the actual updating time Tupd. A second resource may be produced by applying the second digital rule. A second notification can be caused to be transmitted about an aspect of the second resource to a remote device.
Online software platform (OSP) querying client data about relationship instances for application of permission digital rules in addition to resource digital rules for the relationship instances
Systems and methods electronically determine whether a dataset is permitted or excluded based on permission digital rules. Primary entities often are required, or choose to, exclude proposed relationship instances with secondary entities. The systems and methods described herein allow permission digital rules to be defined and applied to datasets obtained from secondary entities relating to a proposed relationship instance with the primary entity, and permit or exclude a resource from being produced for the dataset based on the permission digital rules.
G06F 21/00 - Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
G06F 21/62 - Protecting access to data via a platform, e.g. using keys or access control rules
3.
ONLINE SERVICE PLATFORM (OSP) GENERATING AND TRANSMITTING ON BEHALF OF PRIMARY ENTITY TO THIRD PARTY PROPOSAL OF THE PRIMARY ENTITY WHILE MAINTAINING THE PRIMARY ENTITY ANONYMOUS
An online software platform (OSP) produces, by applying resource digital rules to previous relationship instance data of a primary entity data associated with one or more secondary entities of the domain, a domain resource regarding the domain. The OSP may then determine, by applying an alignment digital rule of the domain to the relationship instance data and the domain resource, whether or not an alignment condition of the domain is met, which indicates whether resources for relationship instances of the primary entity should have been remitted to the domain. If the alignment condition is not met, then the OSP may assemble proposal components, and communicate some of them to the domain on behalf of the primary entity to remit the resources, without initially communicating those proposal components that would reveal the identity of the primary entity.
Automated systems and methods for a secure electronic ledger provide a technical solution such that entities referencing the electronic ledger that are associated with a relationship instance can (a) form a consensus that the outcome of the relationship instance is legitimate and (b) determine whether future relationship instances between entities are compliant. An authority entity publishes to the secure electronic ledger data on which digital rules regarding aspects of the relationship instance between a first entity and second entity are based. Entities subscribed to the secure electronic ledger make digitally signed entries in real-time in the secure electronic ledger including data regarding the relationship instance that are visible by all entities associated with the relationship instance. A trusted third entity is electronically entrusted, by at least the system of the first entity and a system of an authority entity, to validate in real-time the data regarding the relationship instance contained in the entries and all such entries may be approved or rejected in real-time by one or more entities associated with the relationship instance. The approvals and rejections of the entries in the secure electronic ledger, and reasons therefor, are also recorded and visible in the secure electronic ledger to all entities associated with the transaction.
G06Q 20/00 - Payment architectures, schemes or protocols
G06F 9/451 - Execution arrangements for user interfaces
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
G06Q 20/02 - Payment architectures, schemes or protocols involving a neutral third party, e.g. certification authority, notary or trusted third party [TTP]
G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists
G06Q 50/00 - Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
H04L 9/06 - Arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
An online software platform (OSP) classifies challenges to digital rules into buckets according to respective challenged digital rules that were applied to produce respective challenged resources. The OSP computes respective statistics for the buckets. Each bucket may have a corresponding statistic associated with the bucket based on a current total number of challenges that have been classified into that bucket. The OSP ranks the buckets according to the respective statistics of the buckets. The OSP may correct, based on the ranking of the buckets, the respective challenged stored digital rule of the selected bucket without yet correcting the respective challenged digital rule of at least one of the other buckets. This correction is stored and included in digital rules to be used to produce resources going forward.
Systems and method electronically generate a resource code for an item based on attributes of the item and a proposed relationship instance associated with the item. Entities are often required to identify a resource code for items that move between jurisdictions. The systems and methods described herein allow entities to easily obtain resource codes for items moving between jurisdictions.
A service engine determines that an entity meets a first nexus establishment condition for a first domain and a second nexus establishment condition for a second domain. The service engine then computes a first selected resource for the first domain and a second selected resource for the second domain. When the service engine determines that the entity no longer meets the second nexus establishment condition for the second domain, the service engine determines a nexus-ending date for the second domain. Prior to the nexus-ending date being satisfied, the service engine continues to compute the first selected resource for the first domain and the second selected resource for the second domain. In response to the nexus-ending date being satisfied, the service engine computes the first selected resource for the first domain but does not compute the second selected resource for the second domain.
A software configuration includes to store, in a strings memory, combinations of possible source locations and of possible destination locations that are subject to rules pairwise, and to further store respective code strings in association with the respective combinations. The possible locations may be stored by alphanumeric designators, for convenience in looking up the code strings. These code strings may be in a form that is mostly alphanumeric, may embed numerical parameters, and may even represent numerical operations. In fact, a code string of this type may even be configured in the form of code which, upon being executed, implements the rule that is applicable to the combination of the code string's source location and their destination location. The looked-up code string, or a code module generated from it, may then indeed be executed, to produce a resource that complies with the applicable rule.
A service engine determines that an entity meets a first nexus establishment condition for a first domain and a second nexus establishment condition for a second domain. The service engine then computes a first selected resource for the first domain and a second selected resource for the second domain. When the service engine determines that the entity no longer meets the second nexus establishment condition for the second domain, the service engine determines a nexus-ending date for the second domain. Prior to the nexus-ending date being satisfied, the service engine continues to compute the first selected resource for the first domain and the second selected resource for the second domain. In response to the nexus-ending date being satisfied, the service engine computes the first selected resource for the first domain but does not compute the second selected resource for the second domain.
Primary entity requesting from online service provider (OSP) to produce a resource and to prepare a digital exhibit that reports the resource, receiving from the OSP an access indicator that leads to the digital exhibit, and sending the access indicator to secondary entity
In embodiments, a computer system of a primary entity receives from a secondary entity a first communication about a relationship instance between the primary entity and the secondary entity, and transmits to an Online Service Provider (OSP) a second communication with a dataset. The dataset has dataset parameters about the relationship instance. The second communication causes the OSP to select a file template per the dataset, to produce a resource for the dataset, and to prepare a digital exhibit that is arranged to report the resource as answering the identified requirement. The OSP then transmits to the computer system a third communication that includes an access indicator adapted to facilitate viewing the digital exhibit. Upon receiving the third communication, the computer system transmits a fourth communication to the device of the secondary entity, the fourth communication including the access indicator.
G06F 15/177 - Initialisation or configuration control
G06K 7/14 - Methods or arrangements for sensing record carriers by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
H04L 41/084 - Configuration by using pre-existing information, e.g. using templates or copying from other elements
H04L 41/0895 - Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
11.
Versatile integration framework for software-as-a-service (SaaS) functionality
An online software platform (OSP) electronically receives a selection of a workflow framework of a plurality of workflow frameworks. Each workflow framework includes a configuration to embed software-as-a-service (SaaS) functionality provided by the OSP into an application that uses the SaaS functionality. The OSP electronically provides services for determining respective resources for individual relationship instances between different entities. In response to receiving the selection, the OSP causes a remote system that hosts the application to implement the selected workflow framework. This is performed by transmitting a software package to the remote system, in which the software package exposes a set of pre-defined integration points with the SaaS provided by the OSP to provision the steps in one or more of the workflows of the selected workflow framework or defines a specific set of requests and responses with the SaaS provided by the OSP.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 67/561 - Adding application-functional data or data for application control, e.g. adding metadata
H04L 67/566 - Grouping or aggregating service requests, e.g. for unified processing
12.
SUMMARIZATION AND PERSONALIZATION OF BIG DATA METHOD AND APPARATUS
Systems and methods for a user interface to summarize and personalize a large amount of price and product information, to identify patterns therein, and to generate recommendations in relation thereto are described herein.
Some embodiments of the present disclosure may relate generally to platforms for providing software services. Other embodiments may be disclosed and/or claimed.
G06F 16/14 - File systems; File servers - Details of searching files based on file metadata
H04L 41/5041 - Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
14.
Accessing stored code strings for execution to produce resources for diverse situations
A software configuration includes to store, in a strings memory, combinations of possible source locations and of possible destination locations that are subject to rules pairwise, and to further store respective code strings in association with the respective combinations. The possible locations may be stored by alphanumeric designators, for convenience in looking up the code strings. These code strings may be in a form that is mostly alphanumeric, may embed numerical parameters, and may even represent numerical operations. In fact, a code string of this type may even be configured in the form of code which, upon being executed, implements the rule that is applicable to the combination of the code string's source location and their destination location. The looked-up code string, or a code module generated from it, may then indeed be executed, to produce a resource that complies with the applicable rule.
Systems and methods electronically uniquely imprint a digital watermark on produced resources, such as on data or electronic documents produced by an online software platform (OSP), in nearly invisible ways that are likely to survive subsequent processing. In one embodiment the OSP stores a plurality of resource digital rules used for producing resources for respective relationship instances of primary entities with other entities; receives a dataset on behalf of a primary entity, in which the dataset includes data representing a relationship instance between the primary entity and a secondary entity; in response to the received dataset, produces a resource based on applying one or more of the plurality of resource digital rules to the dataset; and digitally watermarks the produced resource with a digital watermark such that the produced resource is identifiable via the digital watermark as having been produced by the OSP.
Systems and methods electronically uniquely imprint a digital watermark on produced resources, such as on data or electronic documents produced by an online software platform (OSP), in nearly invisible ways that are likely to survive subsequent processing. In one embodiment the OSP stores a plurality of resource digital rules used for producing resources for respective relationship instances of primary entities with other entities; receives a dataset on behalf of a primary entity, in which the dataset includes data representing a relationship instance between the primary entity and a secondary entity; in response to the received dataset, produces a resource based on applying one or more of the plurality of resource digital rules to the dataset; and digitally watermarks the produced resource with a digital watermark such that the produced resource is identifiable via the digital watermark as having been produced by the OSP.
ONLINE SOFTWARE PLATFORM (OSP) DERIVING RESOURCES, PRODUCING REPORT DOCUMENT ABOUT THEM, AND CREATING GALLERY WITH DATA SUBSTANTIATING THE REPORT DOCUMETN FOR VIEWING BY THIRD PARTY
In embodiments, a method for an Online Software Platform (OSP) computer system includes receiving datasets having dataset values that represent relationship instance data of relationship instances between a client primary entity and other secondary entities, selecting digital rules responsive to these dataset values, producing resources for the datasets by applying the selected digital rules to the dataset values, deriving a total value of the produced resources, generating a report document that mentions at least the derived the total value, and preparing an instantiation that enables viewing a data record that substantiates the derived total value. The method may further include making this instantiation available for viewing to a domain entity that has access to the report document and wants to confirm the derived total value.
An online software platform (OSP) classifies challenges to digital rules into buckets according to respective challenged digital rules that were applied to produce respective challenged resources. The OSP computes respective statistics for the buckets. Each bucket may have a corresponding statistic associated with the bucket based on a current total number of challenges that have been classified into that bucket. The OSP ranks the buckets according to the respective statistics of the buckets. The OSP may correct, based on the ranking of the buckets, the respective challenged stored digital rule of the selected bucket without yet correcting the respective challenged digital rule of at least one of the other buckets. This correction is stored and included in digital rules to be used to produce resources going forward.
Systems and methods electronically produce a local estimate of less-than-critical resources based on a client side version of digital rules and a coarse values received from an online service provider. Although using the client side version of digital rules and the coarse values may not include all the parameters and values needed to provide a fully accurate estimate of the resource, the ability to locally estimate resources without having to make network calls to the online service provider, such as when there are unfavorable conditions or latency of the network, imminent overloading of the online service provider or other operating conditions or demands on the online service provider preventing it from producing a timely more accurate estimate, provides a faster and more efficient way of obtaining a potentially useful estimate of resources.
A service engine determines whether there is a potential lack of transaction tax compliance in a plurality of jurisdictions for a plurality of entities. The service engine generates and/or transmits tax compliance data which may include information about potential lack of tax compliance of an entity in various jurisdictions based on rules about establishing nexus for purposes of remitting transaction tax in the jurisdictions. The tax compliance data may include a notification about the generation of the information, such as a notification to the entity that there exists a potential lack of tax compliance of that entity in specific jurisdictions. The service engine may update the tax compliance data dynamically and send corresponding notifications, automatically in real time or near real time for the applicable entity as sales of the entity change and/or rules for establishing nexus change for various jurisdictions.
Systems and methods for a user interface to summarize and personalize a large amount of price and product information, to identify patterns therein, and to generate recommendations in relation thereto are described herein.
42 - Scientific, technological and industrial services, research and design
Goods & Services
Providing temporary use of non-downloadable cloud-based software for use in assisting in tax collection and reporting tax information and taxable events
24.
Selected resource computation for mobile employees
A specialized resource computation service engine electronically and automatically provides, in a timely and efficient manner, accurate and reliable tracking of mobile employees across domains and correctly apportions, calculates, and remits selected resources to those domains for employee compensation (including non-cash compensation) earned over a period of time according to the various different rules in various different domains. The system aggregates data indicative of different geographical locations and durations spent in the geographical locations by an employee over a time period, apportions respective amounts of time to each domain based on the aggregated data and computes, for the employee, a respective selected resource for each domain based on the respective amounts of time apportioned to each domain.
G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
In embodiments, a computer system produces a first resource for a first dataset having a time indicator, by applying a first digital rule. A first notification can be caused to be transmitted about an aspect of the first resource to a remote device. A second dataset can be stored, which has values derived from the first dataset, and encodes a parameter of the first resource. A second digital rule may be stored to replace the first digital rule, at an updating time (Tupd). The second digital rule may have an effective time (Teff) prior to the actual updating time Tupd. A second resource may be produced by applying the second digital rule. A second notification can be caused to be transmitted about an aspect of the second resource to a remote device.
Systems and methods electronically obtain data regarding a plurality of sources and corresponding amounts of resources received from the sources for a plurality of relationship instances each associated with one or more respective domains of a plurality of domains. For each relationship instance of the plurality of relationship instances: the system electronically identifies a rate to calculate an amount of resource due to one or more respective domains associated with the relationship instance based on a source of a resource received for the relationship instance and the one or more respective domains and calculates an amount of resources due to at least one respective domain associated with the relationship instance based on the identified rate. For each domain of the plurality of domains, the system aggregates a total amount of resources due to the domain based on the calculated amount of resources due for each relationship instance associated with the domain. The system may then prepare and send, via a computer network, a reporting document to a system of the domain indicating the aggregated total amount of resources due.
G06Q 20/14 - Payment architectures specially adapted for billing systems
G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists
Techniques are provided for facilitating creation, modification, provisioning and transfer of trusted electronic compliance documents. For each of multiple user requests to provide or receive trusted electronic compliance documents, automated operations are performed to determine whether the request is directed to one of a plurality of maintained trusted electronic compliance documents. Each trusted electronic compliance document references information regarding parties to a potential transaction and confers at least partial eligibility for parties to participate in the potential transaction. When it is determined that the request is directed to a maintained trusted electronic compliance document, access to the indicated trusted electronic compliance document is provided, including modifying a copy of the indicated trusted electronic compliance document to include information referenced with respect to an entity associated with the user request and an originator of the trusted electronic compliance document. A secure interface is provided for creating an indicated compliance document when it is determined that the request is not directed to a maintained compliance document.
Systems and methods electronically produce a local estimate of less-than-critical resources based on a client-side version of digital rules and coarse values received from an online service provider. Although using the client-side version of digital rules and the coarse values may not include all the parameters and values needed to provide a fully accurate estimate of the resource, the ability to locally estimate resources without having to make network calls to the online service provider, such as when there are unfavorable conditions or latency of the network, imminent overloading of the online service provider or other operating conditions or demands on the online service provider preventing it from producing a timely more accurate estimate, provides a faster and more efficient way of obtaining a potentially useful estimate of resources.
A service engine of a processor-based system determines an estimated amount of taxes due in association with a proposed transaction based on a risk tolerance value specified by a party to the transaction, such as a seller. Multiple classification code queries are generated for classifying an item that is the subject of the proposed transaction, from which a plurality of classification code candidates are determined. Each such classification code candidate is considered in determination of multiple corresponding possible tax-due amounts, and the taxes due for the proposed transaction are determined by the service engine based on a statistical calculation corresponding to the specified risk tolerance value. The service engine provides the estimated tax due amount to one or more parties to the proposed transaction.
A particular option selection may be provided by an online service platform (OSP) to a client regarding one or more predefined services that the OSP can be configured to perform. These may include automatic activities option selection(s) that may trigger the OSP to automatically start one or more activities upon one or more thresholds being crossed. The OSP may apply digital rules to the dataset(s) of the client to determine whether or not to automatically start or stop activities, including producing respective resources, upon a threshold being crossed, to determine a requested resource and then push, send, or otherwise cause to be transmitted a notification regarding the produced resource or other activities.
G06F 16/28 - Databases characterised by their database models, e.g. relational or object models
32.
Primary entity requesting from online service provider (OSP) to produce a resource and to prepare a digital exhibit that reports the resource, receiving from the OSP an access indicator that leads to the digital exhibit, and sending the access indicator to secondary entity
In embodiments, a computer system of a primary entity receives from a secondary entity a first communication about a relationship instance between the primary entity and the secondary entity, and transmits to an Online Service Provider (OSP) a second communication with a dataset. The dataset has dataset parameters about the relationship instance. The second communication causes the OSP to select a file template per the dataset, to produce a resource for the dataset, and to prepare a digital exhibit that is arranged to report the resource as answering the identified requirement. The OSP then transmits to the computer system a third communication that includes an access indicator adapted to facilitate viewing the digital exhibit. Upon receiving the third communication, the computer system transmits a fourth communication to the device of the secondary entity, the fourth communication including the access indicator.
G06F 15/177 - Initialisation or configuration control
H04L 41/084 - Configuration by using pre-existing information, e.g. using templates or copying from other elements
H04L 41/0895 - Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
G06K 7/14 - Methods or arrangements for sensing record carriers by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
33.
COMPUTATION MODULE CONFIGURED TO ESTIMATE RESOURCE FOR TARGET POINT FROM KNOWN RESOURCES OF DOTS NEAR THE TARGET POINT
Systems and methods electronically generate sample dots, produce resources associated with the dots and estimate a resource for a target point from known resources of dots near the target point based on client side version of digital rules, cataloged data and coarse values previously received from the online service platform. A client receives cataloged data of a cataloged domain in which the cataloged data includes data representing a plurality of dots and a respective computed resource value for each of the dots and each dot of the plurality of dots represents a point in the cataloged domain. In response to confirming a target point is in the cataloged domain, the system discovers a closest one or more dots to the target point based on the cataloged data, estimates a statistic for a resource for the target point based on the respective computed resource values of the closest one or more dots, stores the estimated statistic in a memory, and produces the local estimate based on the estimated statistic.
In embodiments, diagnostics are electronically determined and provided as to why historical resource values differ from resource values determined according to more-trusted ways. Historical relationship instance data regarding a plurality of historical relationship instances between a primary entity and a plurality of secondary entities are received along with a plurality of historical resource values, in which each historical relationship instance of the plurality of historical relationship instances is associated with a respective historical resource value of the plurality of historical resource values. The system produces a respective trusted resource values based on the respective historical relationship instance. Based on differences between the respective trusted resource value and the respective historical resource value associated with the dataset, the system outputs one or more diagnostic comments associated with the detected difference.
A system for automated preparation and submission of electronic registration may obtain a pre-existing entity identifier that had been previously used by an electronic system of at least one authority entity to identify a primary entity. The system may electronically associate the pre-existing entity identifier with the primary entity and use it to perform automated actions to electronically collect one or more support content from the Internet or other sources regarding the primary entity. The system may electronically identify data from the support content relevant to the electronic registration and electronically extract the identified data from the support content. The system may also electronically verify the extracted data before electronically generating and submitting the electronic registration based on the extracted data. An adaptive UI may be automatically modified in response to a determination whether to electronically present a query via the adaptive UI for the supplemental data.
Systems and methods are disclosed for automated preparation and transmission of electronic registrations, data sheets and resources. This may include electronically initiating a process to collect data via a graphical user interface (GUI) to facilitate automated preparation of an electronic registration, including electronically obtaining a pre-existing entity identifier. The system may use the entity identifier to perform automated actions to electronically collect one or more support content. The system may generate the electronic registration based on the one or more support content and also receives interchange data. The system then automatically generates an electronic data sheet based on the registration and interchange data. The system may then electronically file the generated electronic data sheet, electronically issuing an alert to electronically request additional resources and automatically transmitting the finalized amount of resources to the domain.
A disclosed method may include receiving user information for electronically filing or updating an electronic data sheet that corresponds to a user and a domain; maintaining a record of past electronic activities by the user; electronically receiving interchange data associated with interchanges executed by the user; automatically generating the electronic data sheet for the user based on the user information and the interchange data, the electronic data sheet indicating a finalized amount of resources to be transmitted to the domain; and electronically adjusting an electronic value for the user according to a remittance risk determination that is based on the interchange data and the record of past electronic activities by the user, the adjusted electronic value indicating a maximum amount of resources for which an online software platform will transmit and receive protocols to enable providing by the online software platform the maximum amount of resources.
A disclosed method may include receiving user information for electronically filing or updating an electronic data sheet that corresponds to a user and a domain; maintaining a record of past electronic activities by the user; electronically receiving interchange data associated with interchanges executed by the user; automatically generating the electronic data sheet for the user based on the user information and the interchange data, the electronic data sheet indicating a finalized amount of resources to be transmitted to the domain; and electronically adjusting an electronic value for the user according to a remittance risk determination that is based on the interchange data and the record of past electronic activities by the user, the adjusted electronic value indicating a maximum amount of resources for which an online software platform will transmit and receive protocols to enable providing by the online software platform the maximum amount of resources.
A system for automated preparation and submission of electronic registration may obtain a pre-existing entity identifier that had been previously used by an electronic system of at least one authority entity to identify a primary entity. The system may electronically associate the pre-existing entity identifier with the primary entity and use it to perform automated actions to electronically collect one or more support content from the Internet or other sources regarding the primary entity. The system may electronically identify data from the support content relevant to the electronic registration and electronically extract the identified data from the support content. The system may also electronically verify the extracted data before electronically generating and submitting the electronic registration based on the extracted data. An adaptive UI may be automatically modified in response to a determination whether to electronically present a query via the adaptive UI for the supplemental data.
Online service platform (OSP) generating and transmitting on behalf of primary entity to third party proposal of the primary entity while maintaining the primary entity anonymous
An online software platform (OSP) produces, by applying resource digital rules to previous relationship instance data of a primary entity data associated with one or more secondary entities of the domain, a domain resource regarding the domain. The OSP may then determine, by applying an alignment digital rule of the domain to the relationship instance data and the domain resource, whether or not an alignment condition of the domain is met, which indicates whether resources for relationship instances of the primary entity should have been remitted to the domain. If the alignment condition is not met, then the OSP may assemble proposal components, and communicate some of them to the domain on behalf of the primary entity to remit the resources, without initially communicating those proposal components that would reveal the identity of the primary entity.
A disclosed method may include receiving user information for electronically filing or updating an electronic data sheet that corresponds to a user and a domain; maintaining a record of past electronic activities by the user; electronically receiving interchange data associated with interchanges executed by the user; automatically generating the electronic data sheet for the user based on the user information and the interchange data, the electronic data sheet indicating a finalized amount of resources to be transmitted to the domain; and electronically adjusting an electronic value for the user according to a remittance risk determination that is based on the interchange data and the record of past electronic activities by the user, the adjusted electronic value indicating a maximum amount of resources for which an online software platform will transmit and receive protocols to enable providing by the online software platform the maximum amount of resources.
Systems and methods are disclosed for automated preparation and transmission of electronic registrations, data sheets and resources. This may include electronically initiating a process to collect data via a graphical user interface (GUI) to facilitate automated preparation of an electronic registration, including electronically obtaining a pre-existing entity identifier. The system may use the entity identifier to perform automated actions to electronically collect one or more support content. The system may generate the electronic registration based on the one or more support content and also receives interchange data. The system then automatically generates an electronic data sheet based on the registration and interchange data. The system may then electronically file the generated electronic data sheet, electronically issuing an alert to electronically request additional resources and automatically transmitting the finalized amount of resources to the domain.
A disclosed method may include receiving user information for electronically filing or updating an electronic data sheet that corresponds to a user and a domain; maintaining a record of past electronic activities by the user; electronically receiving interchange data associated with interchanges executed by the user; automatically generating the electronic data sheet for the user based on the user information and the interchange data, the electronic data sheet indicating a finalized amount of resources to be transmitted to the domain; and electronically adjusting an electronic value for the user according to a remittance risk determination that is based on the interchange data and the record of past electronic activities by the user, the adjusted electronic value indicating a maximum amount of resources for which an online software platform will transmit and receive protocols to enable providing by the online software platform the maximum amount of resources.
Systems and methods electronically generate sample dots, produce resources associated with the dots and estimate a resource for a target point from known resources of dots near the target point based on client side version of digital rules, cataloged data and coarse values previously received from the online service platform. A client receives cataloged data of a cataloged domain in which the cataloged data includes data representing a plurality of dots and a respective computed resource value for each of the dots and each dot of the plurality of dots represents a point in the cataloged domain. In response to confirming a target point is in the cataloged domain, the system discovers a closest one or more dots to the target point based on the cataloged data, estimates a statistic for a resource for the target point based on the respective computed resource values of the closest one or more dots, stores the estimated statistic in a memory, and produces the local estimate based on the estimated statistic.
In embodiments, given a surface that has domains on it and a first location, a second location is generated in the surface. The second location belongs in the same domains as the first location, and does not belong in the same domains as the second location. An advantage can be that, in embodiments, the second location can be used in lieu of the first location. A use case can be where it is desired to protect the privacy of location data of an entity, such as its address.
In embodiments, given a surface that has domains on it and a first location, a second location is generated in the surface. The second location belongs in the same domains as the first location, and does not belong in the same domains as the second location. An advantage can be that, in embodiments, the second location can be used in lieu of the first location. A use case can be where it is desired to protect the privacy of location data of an entity, such as its address.
Online software platform (OSP) querying client data about relationship instances for application of permission digital rules in addition to resource digital rules for the relationship instances
Systems and methods electronically determine whether a dataset is permitted or excluded based on permission digital rules. Primary entities often are required, or choose to, exclude proposed relationship instances with secondary entities. The systems and methods described herein allow permission digital rules to be defined and applied to datasets obtained from secondary entities relating to a proposed relationship instance with the primary entity, and permit or exclude a resource from being produced for the dataset based on the permission digital rules.
Automated systems and methods for a secure electronic ledger provide a technical solution such that entities referencing the electronic ledger that are associated with a relationship instance can (a) form a consensus that the outcome of the relationship instance is legitimate and (b) determine whether future relationship instances between entities are compliant. An authority entity publishes to the secure electronic ledger data on which digital rules regarding aspects of the relationship instance between a first entity and second entity are based. Entities subscribed to the secure electronic ledger make digitally signed entries in real-time in the secure electronic ledger including data regarding the relationship instance that are visible by all entities associated with the relationship instance. A trusted third entity is electronically entrusted, by at least the system of the first entity and a system of an authority entity, to validate in real-time the data regarding the relationship instance contained in the entries and all such entries may be approved or rejected in real-time by one or more entities associated with the relationship instance. The approvals and rejections of the entries in the secure electronic ledger, and reasons therefor, are also recorded and visible in the secure electronic ledger to all entities associated with the transaction.
G06Q 20/00 - Payment architectures, schemes or protocols
G06Q 50/00 - Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
G06Q 20/02 - Payment architectures, schemes or protocols involving a neutral third party, e.g. certification authority, notary or trusted third party [TTP]
G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists
H04L 9/32 - Arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
G06Q 40/04 - Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
G06F 9/451 - Execution arrangements for user interfaces
H04L 9/06 - Arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for blockwise coding, e.g. D.E.S. systems
An Online Software Platform (OSP) may receive a first dataset from a remote client device, and compute an estimated resource, from the first dataset and also per stored digital rules. The OSP may then communicate an aspect of the resource to the remote client device and receive a confirmation of the first dataset. The OSP may then process the first dataset, for matching it with another dataset, either internally or by outsourcing. Either way, the OSP may establish that the first dataset has been matched with a compatible second dataset. The OSP may then input a resource for the first dataset, which is determined according to stored digital rules. The OSP may further create one or more notifications and documents about the matching and the resource, and make them available to the remote client device or even to the device of another remote entity.
Techniques are provided for facilitating creation, modification, provisioning and transfer of trusted electronic compliance documents. For each of multiple user requests to provide or receive trusted electronic compliance documents, automated operations are performed to determine whether the request is directed to one of a plurality of maintained trusted electronic compliance documents. Each trusted electronic compliance document references information regarding parties to a potential transaction and confers at least partial eligibility for parties to participate in the potential transaction. When it is determined that the request is directed to a maintained trusted electronic compliance document, access to the indicated trusted electronic compliance document is provided, including modifying a copy of the indicated trusted electronic compliance document to include information referenced with respect to an entity associated with the user request and an originator of the trusted electronic compliance document. A secure interface is provided for creating an indicated compliance document when it is determined that the request is not directed to a maintained compliance document.
A service engine determines that an entity meets a first nexus establishment condition for a first domain and a second nexus establishment condition for a second domain. The service engine then computes a first selected resource for the first domain and a second selected resource for the second domain. When the service engine determines that the entity no longer meets the second nexus establishment condition for the second domain, the service engine determines a nexus-ending date for the second domain. Prior to the nexus-ending date being satisfied, the service engine continues to compute the first selected resource for the first domain and the second selected resource for the second domain. In response to the nexus-ending date being satisfied, the service engine computes the first selected resource for the first domain but does not compute the second selected resource for the second domain.
Some embodiments of the present disclosure may relate generally to software-based service platforms and graphical user interface (GUI) architectures for determining and presenting rule-based conclusions, along with explanations identifying the factor or factors influencing the conclusions. Other embodiments may be disclosed and/or claimed.
Systems and methods electronically provide information regarding digital rules related to a potential relationship instance. Users often wish to know which digital rules apply to a specified item before engaging in a relationship instance with a host entity regarding the item. The system and methods described herein allow a computing facility to identify an item and receive resource information related to the item and the digital rules applicable to the item.
Systems and methods electronically provide information regarding digital rules related to a potential relationship instance. Users often wish to know which digital rules apply to a specified item before engaging in a relationship instance with a host entity regarding the item. The system and methods described herein allow a computing facility to identify an item and receive resource information related to the item and the digital rules applicable to the item.
G06F 18/214 - Generating training patterns; Bootstrap methods, e.g. bagging or boosting
55.
Online service platform (OSP) generating and transmitting on behalf of primary entity to third party proposal of the primary entity while maintaining the primary entity anonymous
An online software platform (OSP) produces, by applying resource digital rules to previous relationship instance data of a primary entity data associated with one or more secondary entities of the domain, a domain resource regarding the domain. The OSP may then determine, by applying an alignment digital rule of the domain to the relationship instance data and the domain resource, whether or not an alignment condition of the domain is met, which indicates whether resources for relationship instances of the primary entity should have been remitted to the domain. If the alignment condition is not met, then the OSP may assemble proposal components, and communicate some of them to the domain on behalf of the primary entity to remit the resources, without initially communicating those proposal components that would reveal the identity of the primary entity.
Some embodiments of the present disclosure may relate generally to software-based service platforms and graphical user interface (GUI) architectures for determining and presenting rule-based conclusions, along with explanations identifying the factor or factors influencing the conclusions. Other embodiments may be disclosed and/or claimed.
Online service platform (OSP) generating and transmitting on behalf of primary entity to third party proposal of the primary entity while maintaining the primary entity anonymous
An online software platform (OSP) produces, by applying resource digital rules to previous relationship instance data of a primary entity data associated with one or more secondary entities of the domain, a domain resource regarding the domain. The OSP may then determine, by applying an alignment digital rule of the domain to the relationship instance data and the domain resource, whether or not an alignment condition of the domain is met, which indicates whether resources for relationship instances of the primary entity should have been remitted to the domain. If the alignment condition is not met, then the OSP may assemble proposal components, and communicate some of them to the domain on behalf of the primary entity to remit the resources, without initially communicating those proposal components that would reveal the identity of the primary entity.
Geospatial data is gathered for generation of a geodatacube encompassing data from multiple geospatial data sets for efficient processing and optimization. A method for gathering, storing and processing geospatial data includes identifying a plurality of geospatial data sets for intake, each defining a geospatial data parameter. For each geospatial data set, a plurality of subregions is defined such that each subregion corresponds to a portion of the geographic entity having the same value for the data parameter defined by the respective geospatial data set. In other words, subdividing the geographic entity along demarcations defined by variances in the data parameter(s) defined by the geospatial data set. A number of geospatial data sets for intake are arranged into layers, where each layer defines the data parameter for the respective subregions of the geographic entity. A partition defining polygons common to all layers represents a union of the subregions.
G06V 10/44 - Local feature extraction by analysis of parts of the pattern, e.g. by detecting edges, contours, loops, corners, strokes or intersections; Connectivity analysis, e.g. of connected components
Online software platform (OSP) querying client data about relationship instances for application of permission digital rules in addition to resource digital rules for the relationship instances
Systems and methods electronically determine whether a dataset is permitted or excluded based on permission digital rules. Primary entities often are required, or choose to, exclude proposed relationship instances with secondary entities. The systems and methods described herein allow permission digital rules to be defined and applied to datasets obtained from secondary entities relating to a proposed relationship instance with the primary entity, and permit or exclude a resource from being produced for the dataset based on the permission digital rules.
A service engine determines that an entity meets a first nexus establishment condition for a first domain and a second nexus establishment condition for a second domain. The service engine then computes a first selected resource for the first domain and a second selected resource for the second domain. When the service engine determines that the entity no longer meets the second nexus establishment condition for the second domain, the service engine determines a nexus-ending date for the second domain. Prior to the nexus-ending date being satisfied, the service engine continues to compute the first selected resource for the first domain and the second selected resource for the second domain. In response to the nexus-ending date being satisfied, the service engine computes the first selected resource for the first domain but does not compute the second selected resource for the second domain.
An online software platform (OSP) classifies challenges to digital rules into buckets according to respective challenged digital rules that were applied to produce respective challenged resources. The OSP computes respective statistics for the buckets. Each bucket may have a corresponding statistic associated with the bucket based on a current total number of challenges that have been classified into that bucket. The OSP ranks the buckets according to the respective statistics of the buckets. The OSP may correct, based on the ranking of the buckets, the respective challenged stored digital rule of the selected bucket without yet correcting the respective challenged digital rule of at least one of the other buckets. This correction is stored and included in digital rules to be used to produce resources going forward.
Geospatial data is gathered for generation of a geodatacube encompassing data from multiple geospatial data sets for efficient processing and optimization. A method for gathering, storing and processing geospatial data includes identifying a plurality of geospatial data sets for intake, each defining a geospatial data parameter. For each geospatial data set, a plurality of subregions is defined such that each subregion corresponds to a portion of the geographic entity having the same value for the data parameter defined by the respective geospatial data set. In other words, subdividing the geographic entity along demarcations defined by variances in the data parameter(s) defined by the geospatial data set. A number of geospatial data sets for intake are arranged into layers, where each layer defines the data parameter for the respective subregions of the geographic entity. A partition defining polygons common to all layers represents a union of the subregions.
G06V 10/26 - Segmentation of patterns in the image field; Cutting or merging of image elements to establish the pattern region, e.g. clustering-based techniques; Detection of occlusion
G06V 10/44 - Local feature extraction by analysis of parts of the pattern, e.g. by detecting edges, contours, loops, corners, strokes or intersections; Connectivity analysis, e.g. of connected components
An online software platform (OSP) classifies challenges to digital rules into buckets according to respective challenged digital rules that were applied to produce respective challenged resources. The OSP computes respective statistics for the buckets. Each bucket may have a corresponding statistic associated with the bucket based on a current total number of challenges that have been classified into that bucket. The OSP ranks the buckets according to the respective statistics of the buckets. The OSP may correct, based on the ranking of the buckets, the respective challenged stored digital rule of the selected bucket without yet correcting the respective challenged digital rule of at least one of the other buckets. This correction is stored and included in digital rules to be used to produce resources going forward.
Systems and methods electronically tag received data associated with an entity with an electronic tag including an identifier uniquely associated with the entity. The system may electronically store the received data such that the received data is identifiable via the electronic tag. Then, when a request for deletion of all the entity's data is made by the particular entity, it is fulfilled with much less effort, namely by searching for elements with that entity's tag. Whenever that data is copied, transformed, or derivative data is made, the system copies the electronic tag with it. Thus, even when the data is copied or modified, it can be more efficiently identified as being associated with the particular entity. In some embodiments, the tagging includes electronically recording an association of the electronic tag with the received data as a transaction on a blockchain, the transaction on the blockchain being associated with the electronic tag and with the received data.
Systems and methods electronically tag received data associated with an entity with an electronic tag including an identifier uniquely associated with the entity. The system may electronically store the received data such that the received data is identifiable via the electronic tag. Then, when a request for deletion of all the entity's data is made by the particular entity, it is fulfilled with much less effort, namely by searching for elements with that entity's tag. Whenever that data is copied, transformed, or derivative data is made, the system copies the electronic tag with it. Thus, even when the data is copied or modified, it can be more efficiently identified as being associated with the particular entity. In some embodiments, the tagging includes electronically recording an association of the electronic tag with the received data as a transaction on a blockchain, the transaction on the blockchain being associated with the electronic tag and with the received data.
Systems and methods electronically uniquely imprint a digital watermark on produced resources, such as on data or electronic documents produced by an online software platform (OSP), in nearly invisible ways that are likely to survive subsequent processing. In one embodiment the OSP stores a plurality of resource digital rules used for producing resources for respective relationship instances of primary entities with other entities; receives a dataset on behalf of a primary entity, in which the dataset includes data representing a relationship instance between the primary entity and a secondary entity; in response to the received dataset, produces a resource based on applying one or more of the plurality of resource digital rules to the dataset; and digitally watermarks the produced resource with a digital watermark such that the produced resource is identifiable via the digital watermark as having been produced by the OSP.
Systems and methods electronically tag received data associated with an entity with an electronic tag including an identifier uniquely associated with the entity. The system may electronically store the received data such that the received data is identifiable via the electronic tag. Then, when a request for deletion of all the entity’s data is made by the particular entity, it is fulfilled with much less effort, namely by searching for elements with that entity’s tag. Whenever that data is copied, transformed, or derivative data is made, the system copies the electronic tag with it. Thus, even when the data is copied or modified, it can be more efficiently identified as being associated with the particular entity. In some embodiments, the tagging includes electronically recording an association of the electronic tag with the received data as a transaction on a blockchain, the transaction on the blockchain being associated with the electronic tag and with the received data.
Systems and methods electronically obtain lodging operator data regarding a plurality of sources and corresponding amounts of resources received from the sources for lodging stays. The lodging operator data includes lodging stay data regarding the lodging stays associated with a lodging operator and other data regarding the lodging operator. The system electronically determines lodging inventory data of the lodging operator in the domains based on the lodging operator data and electronically generates, based on the lodging stay data and the domain-specific lodging inventory data, lodging occupancy rates of lodging inventory for the one or more of the plurality of domains. Comparing domain-specific lodging inventory data to lodging occupancy rates, as well as considering data indicative of resources received for lodging stays, results in a prediction value being generated regarding future lodging availability and/or an amount of resources recommended for lodging operators to receive for providing lodging stays.
Systems and methods electronically obtain lodging operator data regarding a plurality of sources and corresponding amounts of resources received from the sources for lodging stays. The lodging operator data includes lodging stay data regarding the lodging stays associated with a lodging operator and other data regarding the lodging operator. The system electronically determines lodging inventory data of the lodging operator in the domains based on the lodging operator data and electronically generates, based on the lodging stay data and the domain-specific lodging inventory data, lodging occupancy rates of lodging inventory for the one or more of the plurality of domains. Comparing domain-specific lodging inventory data to lodging occupancy rates, as well as considering data indicative of resources received for lodging stays, results in a prediction value being generated regarding future lodging availability and/or an amount of resources recommended for lodging operators to receive for providing lodging stays.
Systems and methods electronically obtain lodging operator data regarding a plurality of sources and corresponding amounts of resources received from the sources for lodging stays. The lodging operator data includes lodging stay data regarding the lodging stays associated with a lodging operator and other data regarding the lodging operator. The system electronically determines lodging inventory data of the lodging operator in the domains based on the lodging operator data and electronically generates, based on the lodging stay data and the domain-specific lodging inventory data, lodging occupancy rates of lodging inventory for the one or more of the plurality of domains. Comparing domain-specific lodging inventory data to lodging occupancy rates, as well as considering data indicative of resources received for lodging stays, results in a prediction value being generated regarding future lodging availability and/or an amount of resources recommended for lodging operators to receive for providing lodging stays.
G06Q 10/06 - Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
G06Q 10/08 - Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
71.
Online service platform (OSP) generating and transmitting on behalf of primary entity to third party proposal of the primary entity while maintaining the primary entity anonymous
An online software platform (OSP) produces, by applying resource digital rules to previous relationship instance data of a primary entity data associated with one or more secondary entities of the domain, a domain resource regarding the domain. The OSP may then determine, by applying an alignment digital rule of the domain to the relationship instance data and the domain resource, whether or not an alignment condition of the domain is met, which indicates whether resources for relationship instances of the primary entity should have been remitted to the domain. If the alignment condition is not met, then the OSP may assemble proposal components, and communicate some of them to the domain on behalf of the primary entity to remit the resources, without initially communicating those proposal components that would reveal the identity of the primary entity.
Systems and methods electronically assist a user in searching for codes corresponding to items by using decision trees. Entities are often required to follow specific rules based on classifications, or codes, corresponding to items. The systems and methods described herein allow entities to easily search for and obtain codes corresponding to entities by facilitating navigation through multiple decision trees by navigating from one decision tree to another.
Systems and methods electronically produce a local estimate of less-than-critical resources based on a client side version of digital rules and a coarse values received from an online service provider. Although using the client side version of digital rules and the coarse values may not include all the parameters and values needed to provide a fully accurate estimate of the resource, the ability to locally estimate resources without having to make network calls to the online service provider, such as when there are unfavorable conditions or latency of the network, imminent overloading of the online service provider or other operating conditions or demands on the online service provider preventing it from producing a timely more accurate estimate, provides a faster and more efficient way of obtaining a potentially useful estimate of resources.
In embodiments, diagnostics are electronically determined and provided as to why historical resource values differ from resource values determined according to more-trusted ways. Historical relationship instance data regarding a plurality of historical relationship instances between a primary entity and a plurality of secondary entities are received along with a plurality of historical resource values, in which each historical relationship instance of the plurality of historical relationship instances is associated with a respective historical resource value of the plurality of historical resource values. The system produces a respective trusted resource values based on the respective historical relationship instance. Based on differences between the respective trusted resource value and the respective historical resource value associated with the dataset, the system outputs one or more diagnostic comments associated with the detected difference.
ONLINE SOFTWARE PLATFORM (OSP) DERIVING RESOURCES, PRODUCING REPORT DOCUMENT ABOUT THEM, AND CREATING GALLERY WITH DATA SUBSTANTIATING THE REPORT DOCUMENT FOR VIEWING BY THIRD PARTY
In embodiments, an Online Software Platform (OSP) is configured to receive datasets having dataset values that represent relationship instance data of relationship instances between a client primary entity and other secondary entities, select digital rules responsive to these dataset values, produce resources for the datasets by applying the selected digital rules to the dataset values, derive a total value of the produced resources, generate a report document that mentions at least derived the total value, and prepare an instantiation that enables viewing a data record that substantiates the derived total value. The OSP may further make this instantiation available for viewing to a domain entity that has access to the report document and wants to confirm the derived total value. For instance, the OSP may provide an access instruction for viewing the instantiation, or even augment the report document itself with such an access instruction.
Systems and methods electronically assist a user in searching for codes corresponding to items by using decision trees. Entities are often required to follow specific rules based on classifications, or codes, corresponding to items. The systems and methods described herein allow entities to easily search for and obtain codes corresponding to entities by facilitating navigation through multiple decision trees by navigating from one decision tree to another.
G06F 16/901 - Indexing; Data structures therefor; Storage structures
77.
ONLINE SOFTWARE PLATFORM (OSP) DERIVING RESOURCES, PRODUCING REPORT DOCUMENT ABOUT THEM, AND CREATING GALLERY WITH DATA SUBSTANTIATING THE REPORT DOCUMENT FOR VIEWING BY THIRD PARTY
In embodiments, an Online Software Platform (OSP) is configured to receive datasets having dataset values that represent relationship instance data of relationship instances between a client primary entity and other secondary entities, select digital rules responsive to these dataset values, produce resources for the datasets by applying the selected digital rules to the dataset values, derive a total value of the produced resources, generate a report document that mentions at least derived the total value, and prepare an instantiation that enables viewing a data record that substantiates the derived total value. The OSP may further make this instantiation available for viewing to a domain entity that has access to the report document and wants to confirm the derived total value. For instance, the OSP may provide an access instruction for viewing the instantiation, or even augment the report document itself with such an access instruction.
G06F 9/50 - Allocation of resources, e.g. of the central processing unit [CPU]
78.
Online software platform (OSP) deriving resources, producing report document about them, and creating gallery with data substantiating the report document for viewing by third party
In embodiments, an Online Software Platform (OSP) is configured to receive datasets having dataset values that represent relationship instance data of relationship instances between a client primary entity and other secondary entities, select digital rules responsive to these dataset values, produce resources for the datasets by applying the selected digital rules to the dataset values, derive a total value of the produced resources, generate a report document that mentions at least derived the total value, and prepare an instantiation that enables viewing a data record that substantiates the derived total value. The OSP may further make this instantiation available for viewing to a domain entity that has access to the report document and wants to confirm the derived total value. For instance, the OSP may provide an access instruction for viewing the instantiation, or even augment the report document itself with such an access instruction.
Systems and methods electronically assist a user in searching for codes corresponding to items by using decision trees. Entities are often required to follow specific rules based on classifications, or codes, corresponding to items. The systems and methods described herein allow entities to easily search for and obtain codes corresponding to entities by facilitating navigation through multiple decision trees by navigating from one decision tree to another.
A service engine determines that an entity meets a first nexus establishment condition for a first domain and a second nexus establishment condition for a second domain. The service engine then computes a first selected resource for the first domain and a second selected resource for the second domain. When the service engine determines that the entity no longer meets the second nexus establishment condition for the second domain, the service engine determines a nexus-ending date for the second domain. Prior to the nexus-ending date being satisfied, the service engine continues to compute the first selected resource for the first domain and the second selected resource for the second domain. In response to the nexus-ending date being satisfied, the service engine computes the first selected resource for the first domain but does not compute the second selected resource for the second domain.
Systems and methods electronically generate sample dots, produce resources associated with the dots and estimate a resource for a target point from known resources of dots near the target point based on client side version of digital rules, cataloged data and coarse values previously received from the online service platform. A client receives cataloged data of a cataloged domain in which the cataloged data includes data representing a plurality of dots and a respective computed resource value for each of the dots and each dot of the plurality of dots represents a point in the cataloged domain. In response to confirming a target point is in the cataloged domain, the system discovers a closest one or more dots to the target point based on the cataloged data, estimates a statistic for a resource for the target point based on the respective computed resource values of the closest one or more dots, stores the estimated statistic in a memory, and produces the local estimate based on the estimated statistic.
Systems and methods electronically generate sample dots, produce resources associated with the dots and estimate a resource for a target point from known resources of dots near the target point based on client side version of digital rules, cataloged data and coarse values previously received from the online service platform. A client receives cataloged data of a cataloged domain in which the cataloged data includes data representing a plurality of dots and a respective computed resource value for each of the dots and each dot of the plurality of dots represents a point in the cataloged domain. In response to confirming a target point is in the cataloged domain, the system discovers a closest one or more dots to the target point based on the cataloged data, estimates a statistic for a resource for the target point based on the respective computed resource values of the closest one or more dots, stores the estimated statistic in a memory, and produces the local estimate based on the estimated statistic.
Systems and methods electronically generate sample dots, produce resources associated with the dots and estimate a resource for a target point from known resources of dots near the target point based on client side version of digital rules, cataloged data and coarse values previously received from the online service platform. A client receives cataloged data of a cataloged domain in which the cataloged data includes data representing a plurality of dots and a respective computed resource value for each of the dots and each dot of the plurality of dots represents a point in the cataloged domain. In response to confirming a target point is in the cataloged domain, the system discovers a closest one or more dots to the target point based on the cataloged data, estimates a statistic for a resource for the target point based on the respective computed resource values of the closest one or more dots, stores the estimated statistic in a memory, and produces the local estimate based on the estimated statistic.
Receiving a dataset and parsing from the dataset an XP coordinate value on an x-axis, a YP coordinate value on a y-axis, and a ZP coordinate value on a z-axis all within a domain having 3-dimensional features. The x-axis and y-axis are perpendicular and define a horizontal earthbound main surface. The ZP coordinate value is on the z-axis perpendicular to the horizontal earthbound main surface. The XP, YP and ZP define a place associated with a 3-dimensional feature. Stored resource rules for places in the domain are accessed that indicate a first resource if the ZP has a first value, and a second resource if the ZP has a second value. One of the resource rules that applies to the place is identified based on XP, YP and ZP. A resource for the dataset is determined by applying the identified rule. The resource is caused to be transmitted.
Embodiments of the invention relate to generating and obtaining multiple exemption certificates for multiple sellers in a single transaction, and methods and systems for performing the same.
An online software platform (OSP) classifies challenges to digital rules into buckets according to respective challenged digital rules that were applied to produce respective challenged resources. The OSP computes respective statistics for the buckets. Each bucket may have a corresponding statistic associated with the bucket based on a current total number of challenges that have been classified into that bucket. The OSP ranks the buckets according to the respective statistics of the buckets. The OSP may correct, based on the ranking of the buckets, the respective challenged stored digital rule of the selected bucket without yet correcting the respective challenged digital rule of at least one of the other buckets. This correction is stored and included in digital rules to be used to produce resources going forward.
Some embodiments of the present disclosure may relate generally to software-based service platforms and graphical user interface (GUI) architectures for determining and presenting rule-based conclusions, along with explanations identifying the factor or factors influencing the conclusions. Other embodiments may be disclosed and/or claimed.
Online software platform (OSP) querying client data about relationship instances for application of permission digital rules in addition to resource digital rules for the relationship instances
Systems and methods electronically determine whether a dataset is permitted or excluded based on permission digital rules. Primary entities often are required, or choose to, exclude proposed relationship instances with secondary entities. The systems and methods described herein allow permission digital rules to be defined and applied to datasets obtained from secondary entities relating to a proposed relationship instance with the primary entity, and permit or exclude a resource from being produced for the dataset based on the permission digital rules.
Systems and methods electronically obtain data regarding a plurality of sources and corresponding amounts of resources received from the sources for a plurality of relationship instances each associated with one or more respective domains of a plurality of domains. For each relationship instance of the plurality of relationship instances: the system electronically identifies a rate to calculate an amount of resource due to one or more respective domains associated with the relationship instance based on a source of a resource received for the relationship instance and the one or more respective domains and calculates an amount of resources due to at least one respective domain associated with the relationship instance based on the identified rate. For each domain of the plurality of domains, the system aggregates a total amount of resources due to the domain based on the calculated amount of resources due for each relationship instance associated with the domain. The system may then prepare and send, via a computer network, a reporting document to a system of the domain indicating the aggregated total amount of resources due.
G06Q 30/02 - Marketing; Price estimation or determination; Fundraising
G06Q 20/14 - Payment architectures specially adapted for billing systems
G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists
36 - Financial, insurance and real estate services
Goods & Services
Financial information provided by electronic means in the field of lending; Financial services, namely, money lending
92.
ONLINE SOFTWARE PLATFORM (OSP) EXTRACTING DATA OF CLIENT FROM AN ENTERPRISE RESOURCE PLANNING SERVER AND RETURNING A DATA DEPENDENT DETERMINATION RESULT TO THE CLIENT
A novel architecture of connections and Graphical User Interfaces (GUIs) is used to facilitate extracting a client business's data that is stored in some locations, and copying it to other locations for further processing according to digital rules.
ONLINE SOFTWARE PLATFORM (OSP) EXTRACTING DATA OF CLIENT FROM AN ENTERPRISE RESOURCE PLANNING SERVER AND RETURNING A DATA DEPENDENT DETERMINATION RESULT TO THE CLIENT
A novel architecture of connections and Graphical User Interfaces (GUIs) is used to facilitate extracting a client business's data that is stored in some locations, and copying it to other locations for further processing according to digital rules.
A novel architecture of connections and Graphical User Interfaces (GUIs) is used to facilitate extracting a client business's data that is stored in some locations, and copying it to other locations for further processing according to digital rules.
Some embodiments of the present disclosure may relate generally to a dynamic graphical user interface (GUI) architecture that helps provide a user-friendly and flexible capability for software users to create and manage software application rules. These rules may help with processing by a software service or software platform. Other embodiments may be disclosed and/or claimed.
An Online Software Platform (OSP) may receive a first dataset from a remote client device, and compute an estimated resource, from the first dataset and also per stored digital rules. The OSP may then communicate an aspect of the resource to the remote client device and receive a confirmation of the first dataset. The OSP may then process the first dataset, for matching it with another dataset, either internally or by outsourcing. Either way, the OSP may establish that the first dataset has been matched with a compatible second dataset. The OSP may then input a resource for the first dataset, which is determined according to stored digital rules. The OSP may further create one or more notifications and documents about the matching and the resource, and make them available to the remote client device or even to the device of another remote entity.
In response to receiving a request from a querying entity, such as a seller of goods or services, embodiments of a service engine present to a client computing device of the querying entity a set of queries about goods or services sold by the querying entity and other characteristics of the business of the querying entity. The service engine may intelligently determine which queries to present based on responses to preceding queries. The service engine may then compare the entries in response to the queries against stored rules for a one or more of a plurality of tax jurisdictions, the stored rules being about establishing nexus for purposes of remitting transaction tax in the certain tax jurisdiction. The service engine may then determine information regarding potential lack of tax compliance of the querying entity based on the comparison, and notify accordingly.
In response to receiving a request from a querying entity, such as a seller of goods or services, embodiments of a service engine present to a client computing device of the querying entity a set of queries about goods or services sold by the querying entity and other characteristics of the business of the querying entity. The service engine may intelligently determine which queries to present based on responses to preceding queries. The service engine may then compare the entries in response to the queries against stored rules for a one or more of a plurality of tax jurisdictions, the stored rules being about establishing nexus for purposes of remitting transaction tax in the certain tax jurisdiction. The service engine may then determine information regarding potential lack of tax compliance of the querying entity based on the comparison, and notify accordingly.
Systems and methods electronically provide information regarding digital rules related to a potential relationship instance. Users often wish to know which digital rules apply to a specified item before engaging in a relationship instance with a host entity regarding the item. The system and methods described herein allow a computing facility to identify an item and receive resource information related to the item and the digital rules applicable to the item.
G06K 7/10 - Methods or arrangements for sensing record carriers by corpuscular radiation
G06K 7/14 - Methods or arrangements for sensing record carriers by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
100.
Independently procurable item compliance information
Systems and methods electronically provide information regarding digital rules related to a potential relationship instance. Users often wish to know which digital rules apply to a specified item before engaging in a relationship instance with a host entity regarding the item. The system and methods described herein allow a computing facility to identify an item and receive resource information related to the item and the digital rules applicable to the item.
G06K 7/10 - Methods or arrangements for sensing record carriers by corpuscular radiation
G06K 7/14 - Methods or arrangements for sensing record carriers by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
