An applicant can instantiate a parsing framework, provide an input stream, attach observers, and initiate parsing, which inverts control to the parsing framework. The parsing framework can have an observer manager, a parser controller, and parsers. The observer manager manages observer design patterns from which the observers are instantiated. The parser controller determines which parser would be appropriate for parsing the input stream and instantiate the appropriate parser(s). The parser controller gets the callbacks from the parsers and communicates outcomes to the observer manager. The observer manager determines which of the observers is to be notified, generates parsing notifications accordingly, and dispatches the parsing notifications directly to the observers. The application can be any application that needs parsing in an electronic information exchange platform. The input stream can be created by the application opening a document received from a backend system communicatively connected to the electronic information exchange platform.
A system for isolating requests that comprises, a shared command queue, a first virtual computational resource and a second virtual computational resources. The first virtual computational resources comprises a policy engine configured to access policies comprising criteria for assigning commands corresponding to requests from tenants to compartments, determine, according to the policies, compartments to which to assign the commands corresponding to the requests, produce the commands corresponding to the requests, and queue the commands in the shared command queue, each command comprising compartment assignment information. The second virtual computational resource comprises a command consumer configured to access a subscription to determine a subscribed compartment to which the second virtual computational resource is subscribed, select commands from the shared command queue according to selection criteria that include the subscribed compartment, and consume the selected commands from the shared command queue for processing by the second virtual computational resource.
An information exchange platform referred to as a Trading Grid (TG) may perform relationship-based data processing utilizing a trading partner (TP) graph that describes relationships amongst operating units (OUs) on the TG. When the TG receives a request from an OU to exchange data with a TP, the TG accesses the TP graph and determines a relationship between the OU and their TP as reflected in the TP graph. The TP graph is maintained and controlled by the system independently of the OU and the TP. The TG may route the data based on instructions associated with the relationship that is reflected in the TP graph. The instructions associated with the relationship may specify network based services provided by the TG. An orchestration component may operate to orchestrate the performance of the network based services. The TG then communicates the processed and/or produced data to the TP.
G06Q 10/101 - Collaborative creation, e.g. joint development of products or services
G06T 11/20 - Drawing from basic elements, e.g. lines or circles
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
4.
Just-in-time auto-provisioning systems and methods for information exchange platform
An information exchange platform receives a file from a client system and processes the file for delivery to a trading partner (TP) of the client system. The TP does not need to be a client of the information exchange platform. So long as the file has some identifying information such as an email address that uniquely identifies the TP within a custom solution for the client system, the information exchange platform can automatically and programmatically provision the TP. An auto-provisioning subsystem is operable to create and/or configure information needed to complete the processing of the file just in time, including creating a legal entity and a routing address for the TP. When completed, the file is processed into a deliverable, which is then provided for delivery to the TP just in time as the file is received from the client system.
A system for electronic data interchange (EDI) management includes a memory for storing the EDI document data and a machine learning model representing a set of features of EDI documents and a corresponding status. The system further includes a processor and a non-transitory computer readable medium storing instructions for: accessing an EDI file, the EDI file comprising envelope metadata for an envelope and a first EDI document: and translating the EDI file into a first translated EDI document containing the envelope metadata and a set of EDI document data extracted from the first EDI document, the first translated EDI document formatted according to a hierarchical structure comprising attributes translatable into features processable by the machine learning model to determine a status of the first EDI document.
An any-to-any (A2A) connector system provides an A2A integration framework that includes an ingress router, a connector system, and enhancements to an orchestration service framework of an information exchange platform. At design time, an application programming interface (API) connector can be generated based on API documentation for the external service. At runtime, in processing an itinerary that includes a universal service, the external service is called through the universal service using the API connector. The universal service is operable to parse a request from a client system, query a connector database, and, based on a result from the connector database, sends a request to a connector engine. The connector engine fetches the API connector from the connector database, calls the external service using the API connector, handles results of the call, and returns the results to the universal service.
An any-to-any (A2A) connector system provides an A2A integration framework that includes an ingress router, a connector system, and enhancements to an orchestration service framework of an information exchange platform. At design time, an application programming interface (API) connector can be generated based on API documentation for the external service. At runtime, in processing an itinerary that includes a universal service, the external service is called through the universal service using the API connector. The universal service is operable to parse a request from a client system, query a connector database, and, based on a result from the connector database, sends a request to a connector engine. The connector engine fetches the API connector from the connector database, calls the external service using the API connector, handles results of the call, and returns the results to the universal service.
An information exchange platform referred to as a Trading Grid (TG) may perform relationship-based data processing utilizing a trading partner (TP) graph that describes relationships amongst operating units (OUs) on the TG. When the TG receives a request from an OU to exchange data with a TP, the TG accesses the TP graph and determines a relationship between the OU and their TP as reflected in the TP graph. The TP graph is maintained and controlled by the system independently of the OU and the TP. The TG may route the data based on instructions associated with the relationship that is reflected in the TP graph. The instructions associated with the relationship may specify network based services provided by the TG. An orchestration component may operate to orchestrate the performance of the network based services. The TG then communicates the processed and/or produced data to the TP.
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
G06T 11/20 - Drawing from basic elements, e.g. lines or circles
G06Q 10/101 - Collaborative creation, e.g. joint development of products or services
9.
Systems and Methods for Managed Services Provisioning Using Service-Specific Provisioning Data Instances
A technical solution for significantly improving the scalability of the capability of an electronic information exchange platform is disclosed. Services provided by the platform may be described in a uniform way via service-specific provisioning descriptors. To provision services for a client system, a managed services provisioning system provides a service configuration interface through which a service associated with a tuple of a particular sender, receiver, and document type can be selected for further configuration. A service provisioning interface is dynamically generated for obtaining service-specific provisioning information from a user for generating a service-specific provisioning data instance that can be deployed to a backend system. At runtime, the backend system utilizes the service-specific provisioning data instance to provide the provisioned service for a client system. In this way, a variety of services can be efficiently provisioned for a diverse set of clients in a scalable, streamlined, and cost-effective manner.
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
G06F 3/04847 - Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
H04L 41/0233 - Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
H04L 41/08 - Configuration management of networks or network elements
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 67/00 - Network arrangements or protocols for supporting network services or applications
An applicant can instantiate a parsing framework, provide an input stream, attach observers, and initiate parsing, which inverts control to the parsing framework. The parsing framework can have an observer manager, a parser controller, and parsers. The observer manager manages observer design patterns from which the observers are instantiated. The parser controller determines which parser would be appropriate for parsing the input stream and instantiate the appropriate parser(s). The parser controller gets the callbacks from the parsers and communicates outcomes to the observer manager. The observer manager determines which of the observers is to be notified, generates parsing notifications accordingly, and dispatches the parsing notifications directly to the observers. The application can be any application that needs parsing in an electronic information exchange platform. The input stream can be created by the application opening a document received from a backend system communicatively connected to the electronic information exchange platform.
An information exchange platform receives a file from a client system and processes the file for delivery to a trading partner (TP) of the client system. The TP does not need to be a client of the information exchange platform. So long as the file has some identifying information such as an email address that uniquely identifies the TP within a custom solution for the client system, the information exchange platform can automatically and programmatically provision the TP. An auto-provisioning subsystem is operable to create and/or configure information needed to complete the processing of the file just in time, including creating a legal entity and a routing address for the TP. When completed, the file is processed into a deliverable, which is then provided for delivery to the TP just in time as the file is received from the client system.
Systems, methods, and computer program products for producer-side prioritization of message processing. Producer-side prioritization of message processing may include receiving an input message according to a messaging protocol for communicating between software components, where the input message comprises message priority information for the input message, producing a command for a next step in the processing flow, the command including a target time determined using the message priority information from the input message, queuing the command in a command queue, selecting the command from the command queue based on a determination that the target time has expired, and processing the command.
A system for electronic data interchange (EDI) management includes a memory for storing the EDI document data and a machine learning model representing a set of features of EDI documents and a corresponding status. The system further includes a processor and a non-transitory computer readable medium storing instructions for: accessing an EDI file, the EDI file comprising envelope metadata for an envelope and a first EDI document; and translating the EDI file into a first translated EDI document containing the envelope metadata and a set of EDI document data extracted from the first EDI document, the first translated EDI document formatted according to a hierarchical structure comprising attributes translatable into features processable by the machine learning model to determine a status of the first EDI document.
A system for isolating requests that comprises, a shared command queue, a first virtual computational resource and a second virtual computational resources. The first virtual computational resources comprises a policy engine configured to access policies comprising criteria for assigning commands corresponding to requests from tenants to compartments, determine, according to the policies, compartments to which to assign the commands corresponding to the requests, produce the commands corresponding to the requests, and queue the commands in the shared command queue, each command comprising compartment assignment information. The second virtual computational resource comprises a command consumer configured to access a subscription to determine a subscribed compartment to which the second virtual computational resource is subscribed, select commands from the shared command queue according to selection criteria that include the subscribed compartment, and consume the selected commands from the shared command queue for processing by the second virtual computational resource.
An information exchange platform referred to as a Trading Grid (TG) may perform relationship-based data processing utilizing a trading partner (TP) graph that describes relationships amongst operating units (OUs) on the TG. When the TG receives a request from an OU to exchange data with a TP, the TG accesses the TP graph and determines a relationship between the OU and their TP as reflected in the TP graph. The TP graph is maintained and controlled by the system independently of the OU and the TP. The TG may route the data based on instructions associated with the relationship that is reflected in the TP graph. The instructions associated with the relationship may specify network based services provided by the TG. An orchestration component may operate to orchestrate the performance of the network based services. The TG then communicates the processed and/or produced data to the TP.
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
G06T 11/20 - Drawing from basic elements, e.g. lines or circles
G06Q 10/101 - Collaborative creation, e.g. joint development of products or services
16.
Rules/model-based data processing system for intelligent event prediction in an electronic data interchange system
An electronic data interchange (EDI) management system may comprise a memory for storing EDI document data and a machine learning prediction model representing element information of EDI documents of a first type and a corresponding status. A processor can be configured to extract elements from an EDI document, create a document record for the EDI document, the document record comprising elements extracted from the EDI document; determine a first status for the EDI document of the first type by processing the extracted elements using a machine learning model, the machine learning model trained on a training set of elements to classify documents according to a plurality of statuses, and add the first status to the document record for the EDI document of the first type, the first status accessible to a client computer via a presentation layer.
An information exchange platform receives a file from a client system and processes the file for delivery to a trading partner (TP) of the client system. The TP does not need to be a client of the information exchange platform. So long as the file has some identifying information such as an email address that uniquely identifies the TP within a custom solution for the client system, the information exchange platform can automatically and programmatically provision the TP. An auto-provisioning subsystem is operable to create and/or configure information needed to complete the processing of the file just in time, including creating a legal entity and a routing address for the TP. When completed, the file is processed into a deliverable, which is then provided for delivery to the TP just in time as the file is received from the client system.
A message processing system that provides a processing flow, the message processing system comprising an input message consumer configured to consume input messages from an input message queue, where the input messages comprise priority information. The message processing system includes a command producer configured to produce commands for a next step in the processing flow. Each command produced may include a target time determined using priority information extracted from an input message to which that command corresponds. The message processing system comprises a queue for commands. The message processing system further comprises a command consumer configured to select commands that have expired target times from the command queue for processing and consume the selected commands from the command queue.
An applicant can instantiate a parsing framework, provide an input stream, attach observers, and initiate parsing, which inverts control to the parsing framework. The parsing framework can have an observer manager, a parser controller, and parsers. The observer manager manages observer design patterns from which the observers are instantiated. The parser controller determines which parser would be appropriate for parsing the input stream and instantiate the appropriate parser(s). The parser controller gets the callbacks from the parsers and communicates outcomes to the observer manager. The observer manager determines which of the observers is to be notified, generates parsing notifications accordingly, and dispatches the parsing notifications directly to the observers. The application can be any application that needs parsing in an electronic information exchange platform. The input stream can be created by the application opening a document received from a backend system communicatively connected to the electronic information exchange platform.
An electronic data interchange (EDI) management system may comprise a memory for storing EDI document data and a machine learning prediction model representing element information of EDI documents of a first type and a corresponding status. A processor can be configured to extract elements from an EDI document, create a document record for the EDI document, the document record comprising elements extracted from the EDI document; determine a first delivery status for the EDI document of the first type by processing the extracted elements using a machine learning delivery model, the machine learning delivery model trained on a training set of elements to classify documents according to a plurality of delivery statuses, and add the first status to the document record for the EDI document of the first type, the first status accessible to a client computer via a presentation layer.
A system for isolating requests that comprises, a shared command queue, a first virtual computational resource and a second virtual computational resources. The first virtual computational resources comprises a policy engine configured to access policies comprising criteria for assigning commands corresponding to requests from tenants to compartments, determine, according to the policies, compartments to which to assign the commands corresponding to the requests, produce the commands corresponding to the requests, and queue the commands in the shared command queue, each command comprising compartment assignment information. The second virtual computational resource comprises a command consumer configured to access a subscription to determine a subscribed compartment to which the second virtual computational resource is subscribed, select commands from the shared command queue according to selection criteria that include the subscribed compartment, and consume the selected commands from the shared command queue for processing by the second virtual computational resource.
A message processing system that provides a processing flow, the message processing system comprising an input message consumer configured to consume input messages from an input message queue, where the input messages comprise priority information. The message processing system includes a command producer configured to produce commands for a next step in the processing flow. Each command produced may include a target time determined using priority information extracted from an input message to which that command corresponds. The message processing system comprises a queue for commands. The message processing system further comprises a command consumer configured to select commands that have expired target times from the command queue for processing and consume the selected commands from the command queue.
A message processing system that provides a processing flow, the message processing system comprising an input message consumer configured to consume input messages from an input message queue, where the input messages comprise priority information. The message processing system includes a command producer configured to produce commands for a next step in the processing flow. Each command produced may include a target time determined using priority information extracted from an input message to which that command corresponds. The message processing system comprises a queue for commands. The message processing system further comprises a command consumer configured to select commands that have expired target times from the command queue for processing and consume the selected commands from the command queue.
A technical solution for an electronic information exchange platform is disclosed. Services provided by the platform may be described in a uniform way via service-specific provisioning descriptors. To provision services for a client system, a managed services provisioning system provides a service configuration interface through which a service associated with a tuple of a particular sender, receiver, and document type can be selected for further configuration. A service provisioning interface is dynamically generated for obtaining service-specific provisioning information from a user for generating a service-specific provisioning data instance that can be deployed to a backend system. At runtime, the backend system utilizes the service-specific provisioning data instance to provide the provisioned service for a client system. In this way, a variety of services can be efficiently provisioned for a diverse set of clients in a scalable, streamlined, and cost-effective manner.
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
G06F 3/04847 - Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
H04L 41/0233 - Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
H04L 41/08 - Configuration management of networks or network elements
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 67/00 - Network arrangements or protocols for supporting network services or applications
25.
Trading partner relationship graph for information exchange platform
An information exchange platform referred to as a Trading Grid (TG) may perform relationship-based data processing utilizing a trading partner (TP) graph that describes relationships amongst operating units (OUs) on the TG. When the TG receives a request from an OU to exchange data with a TP, the TG accesses the TP graph and determines a relationship between the OU and their TP as reflected in the TP graph. The TP graph is maintained and controlled by the system independently of the OU and the TP. The TG may route the data based on instructions associated with the relationship that is reflected in the TP graph. The instructions associated with the relationship may specify network based services provided by the TG. An orchestration component may operate to orchestrate the performance of the network based services. The TG then communicates the processed and/or produced data to the TP.
An electronic data interchange (EDI) management system may comprise a memory for storing EDI document data and a machine learning prediction model representing element information of EDI documents of a first type and a corresponding status. A processor can be configured to extract segments and elements from an EDI document, create a document record for the EDI document, the document record comprising a hierarchy of segments and elements extracted from the EDI document; create a feature vector for the EDI document from the elements extracted from the EDI document, determine a first status for the EDI document by processing the feature vector for the EDI document using the prediction model and add the first status to the document record for the EDI document of the first type, the first status accessible to a client computer via a presentation layer.
An electronic data interchange (EDI) management system may comprise a memory for storing EDI document data and a machine learning prediction model representing element information of EDI documents of a first type and a corresponding status. A processor can be configured to extract segments and elements from an EDI document, create a document record for the EDI document, the document record comprising a hierarchy of segments and elements extracted from the EDI document; create a feature vector for the EDI document from the elements extracted from the EDI document, determine a first status for the EDI document by processing the feature vector for the EDI document using the prediction model and add the first status to the document record for the EDI document of the first type, the first status accessible to a client computer via a presentation layer.
An intelligent and versatile information exchange platform provides a delivery service operable to perform, in a network environment, processing a document in a first process context according to a first itinerary associated with a sender, including determining whether any receiver policy rule is applicable to the document. If so, the delivery service can determine a second itinerary in view of the receiver policy rule and automatically transition to act as a receive service for the receiver such that the document is processed is a second process context according to the second itinerary associated with the receiver. When no receiver policy rule is found or applicable to the document based on the document type of the document, the delivery service can deliver the document to the receiver under the first process context.
An applicant can instantiate a parsing framework, provide an input stream, attach observers, and initiate parsing, which inverts control to the parsing framework. The parsing framework can have an observer manager, a parser controller, and parsers. The observer manager manages observer design patterns from which the observers are instantiated. The parser controller determines which parser would be appropriate for parsing the input stream and instantiate the appropriate parser(s). The parser controller gets the callbacks from the parsers and communicates outcomes to the observer manager. The observer manager determines which of the observers is to be notified, generates parsing notifications accordingly, and dispatches the parsing notifications directly to the observers. The application can be any application that needs parsing in an electronic information exchange platform. The input stream can be created by the application opening a document received from a backend system communicatively connected to the electronic information exchange platform.
An information exchange platform receives a file from a client system and processes the file for delivery to a trading partner (TP) of the client system. The TP does not need to be a client of the information exchange platform. So long as the file has some identifying information such as an email address that uniquely identifies the TP within a custom solution for the client system, the information exchange platform can automatically and programmatically provision the TP. An auto-provisioning subsystem is operable to create and/or configure information needed to complete the processing of the file just in time, including creating a legal entity and a routing address for the TP. When completed, the file is processed into a deliverable, which is then provided for delivery to the TP just in time as the file is received from the client system.
A proxy framework communicatively connected to source systems and backend systems can intercept a call from a client device to a legacy backend system, interprets the call, and determines whether an account associated with the client device has migrated to an information exchange platform. If so, the proxy framework can direct the call to a native backend system that is native to the information exchange platform, instead of the legacy backend system. If not, the call is forwarded to the legacy backend system.
An applicant can instantiate a parsing framework, provide an input stream, attach observers, and initiate parsing, which inverts control to the parsing framework. The parsing framework can have an observer manager, a parser controller, and parsers. The observer manager manages observer design patterns from which the observers are instantiated. The parser controller determines which parser would be appropriate for parsing the input stream and instantiate the appropriate parser(s). The parser controller gets the callbacks from the parsers and communicates outcomes to the observer manager. The observer manager determines which of the observers is to be notified, generates parsing notifications accordingly, and dispatches the parsing notifications directly to the observers. The application can be any application that needs parsing in an electronic information exchange platform. The input stream can be created by the application opening a document received from a backend system communicatively connected to the electronic information exchange platform.
An information exchange platform referred to as a Trading Grid (TG) may perform relationship-based data processing utilizing a trading partner (TP) graph that describes relationships amongst operating units (OUs) on the TG. When the TG receives a request from an OU to exchange data with a TP, the TG accesses the TP graph and determines a relationship between the OU and their TP as reflected in the TP graph. The TP graph is maintained and controlled by the system independently of the OU and the TP. The TG may route the data based on instructions associated with the relationship that is reflected in the TP graph. The instructions associated with the relationship may specify network based services provided by the TG. An orchestration component may operate to orchestrate the performance of the network based services. The TG then communicates the processed and/or produced data to the TP.
A technical solution for significantly improving the scalability of the capability of an electronic information exchange platform is disclosed. Services provided by the platform may be described in a uniform way via service-specific provisioning descriptors. To provision services for a client system, a managed services provisioning system provides a service configuration interface through which a service associated with a tuple of a particular sender, receiver, and document type can be selected for further configuration. A service provisioning interface is dynamically generated for obtaining service-specific provisioning information from a user for generating a service-specific provisioning data instance that can be deployed to a backend system. At runtime, the backend system utilizes the service-specific provisioning data instance to provide the provisioned service for a client system. In this way, a variety of services can be efficiently provisioned for a diverse set of clients in a scalable, streamlined, and cost-effective manner.
H04L 12/24 - Arrangements for maintenance or administration
H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
G06F 3/0484 - Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
09 - Scientific and electric apparatus and instruments
38 - Telecommunications services
39 - Transport, packaging, storage and travel services
Goods & Services
Computer software to allow users to perform electronic business transactions via a global computer network Electronic transmission of message data, namely, electronic data interchange services and electronic store-and-forward services; providing multiple user access to a global computer network; providing on-line electronic bulletin boards for transmission of messages among computer users concerning business transactions. Secure electronic storage of data primarily relating to business-to-business transactional information
