Abstract: The disclosure herein describes processing consent data and using the processed consent data in workflows. Customer consent data is accessed, wherein the customer consent data includes subject consent instances including associated consent purpose-value pairs. The customer consent data is mapped to a raw consent data schema based on mapping selections made on a mapping UI, wherein the mapping includes mapping consent purpose-value pairs of the consent instances to data columns of the raw consent data schema. Metadata representing one or more consent rules related to the raw consent data schema is generated based on rule selections made on a rule configuration UI and the consent rules are applied to one or more workflows. The disclosure enables consent data in different formats and/or from different sources to be ingested and standardized in a single platform such that consent checking functionality can be provided for applications in a consistent and comprehensive manner.

Abstract: A system for providing multicomputer data transfer for transferring data between multiple devices that use the data after the multicomputer data transfer, includes a user profiles repository to store user profiles associated with users of client devices, and a content repository to store communication information. The system includes a platform device communicating with the client devices, the user profiles repository, and the content repository via networks.

Abstract: A system for providing multicomputer data transfer for transferring data between multiple devices that use the data after the multicomputer data transfer, includes a user profiles repository to store user profiles associated with users of client devices, and a content repository to store communication information. The system includes a platform device communicating with the client devices, the user profiles repository, and the content repository via networks.

Abstract: Communication between a first issue tracking system and a second issue tracking system is provided. An integration platform is configured to translate an issue tracking ticket from a form recognizable by the first issue tracking system, which can be a component of a customer network, into a form recognizable by the second issue tracking system, which can be a component of a service provider network. A gateway server is provided to control communications between the integration platform and the issue tracking system of the service provider network.

Abstract: A polymer composition having improved processing properties, in particular improved crystallization behavior, comprising a semi-aromatic polyamide and a graphene material. The graphene material may be a nano-graphene platelet. The semi-aromatic polyamide may comprise recurring units obtainable by a polycondensation reaction between at least one aromatic diamine and at least one non-aromatic diacid or derivatives thereof and/or recurring units obtainable by a polycondensation reaction between at least one aromatic diacid or derivatives thereof and at least one non-aromatic diamine. The composition may further comprise a polyamide different than the semi-aromatic polyamide. The composition may further comprise a filler.

Abstract: A system updates a lightweight directory access protocol (LDAP) database based on changes made to a second database. The system determines differences between Internet Protocol (IP) communication service records stored in the second database and IP communication service records stored in the LDAP database and creates a transaction file based on the differences. The system updates the LDAP database using the transaction file.

Abstract: A method for communicating from an integration platform to a profile management server includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the server. The connector receives the event information, transforms the event information to a format compatible with the server and establishes communications with the server via hypertext transfer protocol (HTTP). The connector downloads the information to the server and the server updates its database. The connector may also determine whether at least one other system received the event information before downloading the information to the server.

Abstract: An approach is provided for a managed navigational service. Real-time positional information corresponding to a user is received over a communication network. An approaching point of interest is determined based on the positional information. The approaching point of interest is correlated with travel information and metadata associated with the approaching point of interest. Information about the approaching point of interest is transmitted over the communication network to the user.

Abstract: Communication between a first issue tracking system and a second issue tracking system is provided. An integration platform is configured to translate an issue tracking ticket from a form recognizable by the first issue tracking system, which can be a component of a customer network, into a form recognizable by the second issue tracking system, which can be a component of a service provider network. A gateway server is provided to control communications between the integration platform and the issue tracking system of the service provider network.

Abstract: A method for communicating from an integration platform to a server that executes object request broker (ORB) software includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the server. The connector receives the event information, transforms the event information to a format compatible with the server and establishes communications with the server. The connector downloads the information to the server and the server updates its database. The connector may also determine whether at least one other system received the event information before downloading the data to the server.

Abstract: An operational support system includes a network interface and a report unit. The network interface receives an identifier and password from a user, determines whether to grant access to the operational support system based on the identifier and password, and transmits, when access is granted, the identifier and password to the report unit. The report unit automatically compares the identifier and password to stored identifiers and passwords and grants access to the report unit when the identifier and password correspond to one of the stored identifiers and passwords.

Abstract: A method for communicating from an integration platform to a directory server includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the directory server. The connector receives the event information, transforms the event information to a format compatible with the directory server and establishes communications with the directory server. The connector downloads the information to the directory server and the directory server updates its database. The connector may also determine whether at least one other system received the event information before downloading the information to the directory server.

Abstract: Processes for preparing block copolymers and the block copolymers prepared therefrom comprising at least two types of homoblock, all belonging to the polysulfone family, wherein each of the said homoblocks has an identical or different molecular weight of at least 1000 and comprises at least 5% of the overall weight of the block copolymer, and wherein the block copolymer has a molecular weight of at least 2000, the process steps comprising preparing each of the aforesaid homoblocks by reacting at least one aromatic diol with at least one aromatic dihalo compound, one of which contains at least one sulfone group, in at least one aprotic solvent in the presence of at least one alkali, optionally in the presence of an azeotropic agent and then reacting the aforesaid homoblocks together in at least an aprotic solvent, optionally followed by end-capping said block copolymer.

Abstract: A method for communicating from an integration platform to a server that executes object request broker (ORB) software includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the server. The connector receives the event information, transforms the event information to a format compatible with the server and establishes communications with the server. The connector downloads the information to the server and the server updates its database. The connector may also determine whether at least one other system received the event information before downloading the data to the server.

Abstract: An operational support system includes a network interface and a report unit. The network interface receives an identifier and password from a user, determines whether to grant access to the operational support system based on the identifier and password, and transmits, when access is granted, the identifier and password to the report unit. The report unit automatically compares the identifier and password to stored identifiers and passwords and grants access to the report unit when the identifier and password correspond to one of the stored identifiers and passwords.

Abstract: A system updates a lightweight directory access protocol (LDAP) database based on changes made to a second database. The system determines differences between Internet Protocol (IP) communication service records stored in the second database and IP communication service records stored in the LDAP database and creates a transaction file based on the differences. The system updates the LDAP database using the transaction file.

Abstract: A method for communicating from an integration platform to a profile management server includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the server. The connector receives the event information, transforms the event information to a format compatible with the server and establishes communications with the server via hypertext transfer protocol (HTTP). The connector downloads the information to the server and the server updates its database. The connector may also determine whether at least one other system received the event information before downloading the information to the server.

Abstract: A method for communicating from an integration platform to a directory server includes receiving user-entered information at the integration platform. The integration platform generates an event based on the user-entered information and publishes the event on a channel subscribed to by a connector associated with the directory server. The connector receives the event information, transforms the event information to a format compatible with the directory server and establishes communications with the directory server. The connector downloads the information to the directory server and the directory server updates its database. The connector may also determine whether at least one other system received the event information before downloading the information to the directory server.

Abstract: An operational support system includes an integration platform and a billing system. The integration platform receives user-entered information and generates an event based on the user-entered information. The integration platform publishes the event on a channel subscribed to by a connector associated with the billing system. The connector transforms the event information to a format compatible with the billing system and forwards the event to a channel that is associated with a data storage system. The connector establishes communication with the billing system and downloads the information to the billing system in response to a message indicating that the data storage system received the event information.