IP Library Granted Patent US 11,563,629
Granted Patent B2
US 11,563,629 · App. 16/450,787 · Granted Jan 24, 2023

Systems and methods for managed services provisioning using service-specific provisioning data instances

Inventors: Gregory Frederick Bush (Cory, NC); Ricardo Ceppi (Vienna, VA); Tom Gordon (Raleigh, NC); John Theodore Radko (Germantown, MD)
Assignee: OPEN TEXT GXS ULC
H04L41/0806G06F3/04847G06Q10/10H04L41/0233H04L41/0889H04L41/22H04L67/34H04L67/60
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,563,629
App. No.
16/450,787
Granted
Jan 24, 2023
Kind
B2
Abstract

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.

Claims (56)

1. A method for provisioning managed services, the method comprising:

receiving, by a service provisioning system through a user interface, a selection of a service from a plurality of services managed by an electronic information exchange platform, the service provided by a backend system of the electronic information exchange platform, the service provisioning system having a processor and a non-transitory computer-readable medium;

obtaining, by the service provisioning system, a service-specific provisioning descriptor (SSPD) associated with the service, wherein the SSPD and the service have a one-to-one relationship;

dynamically generating, by the service provisioning system utilizing the SSPD associated with the service, a service provisioning interface (SPI);

receiving, by the service provisioning system through the SRI generated utilizing the SSPD associated with the service, service-specific provisioning data for configuring the service provided by the backend system for a client system, wherein the service provided by the backend system has not been provisioned for the client system;

generating, by the service provisioning system using the service-specific provisioning data received through the SRI, a data card for configuring the service provided by the backend system for the client system, wherein the data card is specific to the service managed by the electronic information exchange platform and provided by the backend system to the client system;

receiving, by the service provisioning system through the SRI, an instruction or command to deploy the data card to the backend system; and

communicating, by the service provisioning system responsive to the instruction or command, the data card to the backend system, wherein the data card is utilized by the backend system to configure the service for the client system to thereby provision the service for the client system.

2. The method according to claim 1 , further comprising:

receiving, by the service provisioning system through the SPI, an instruction or command to validate the service-specific provisioning data; and

requesting, by the service provisioning system, the backend system that provides the service to validate the service-specific provisioning data.

3. The method according to claim 2 , further comprising:

notifying, by the service provisioning system responsive to a validation error associated with the service-specific provisioning data, a user to correct the validation error.

4. The method according to claim 2 , further comprising:

persisting, by the service provisioning system responsive to the service-specific provisioning data being valid, the service-specific provisioning data as the data card.

5. The method according to claim 1 , wherein the SPI comprises a RESTful application programming interface (API) that supports a plurality of operations including at least one of search, create, read, update, delete, or validate operations.

6. The method according to claim 1 , wherein the data card is one of a plurality of data cards associated with a plurality of services provisioned by the service provisioning system for the client system, the plurality of services provided by disparate backend systems of the electronic information exchange platform.

7. The method according to claim 6 , wherein the plurality of data cards utilized by the disparate backend systems conforms to a standardized internal representation that is internal to the service provisioning system.

8. A service provisioning system, comprising:

a processor;

a non-transitory computer-readable medium; and

stored instructions translatable by the processor for:

receiving, through a user interface, a selection of a service from a plurality of services managed by an electronic information exchange platform, the service provided by a backend system of the electronic information exchange platform;

obtaining a service-specific provisioning descriptor (SSPD) associated with the service, wherein the SSPD and the service have a one-to-one relationship;

dynamically generating, utilizing the SSPD associated with the service, a service provisioning interface (SPI);

receiving, through the SPI generated utilizing the SSPD associated with the service, service-specific provisioning data for configuring the service provided by the backend system for a client system, wherein the service provided by the backend system has not been provisioned for the client system;

generating, using the service-specific provisioning data received through the SPI, a data card for configuring the service provided by the backend system for the client system, wherein the data card is specific to the service managed by the electronic information exchange platform and provided by the backend system to the client system;

receiving, through the SPI, an instruction or command to deploy the data card to the backend system; and

responsive to the instruction or command, communicating the data card to the backend system, wherein the data card is utilized by the backend system to configure the service for the client system to thereby provision the service for the client system.

9. The service provisioning system of claim 8 , wherein the stored instructions are further translatable by the processor for:

receiving, through the SPI, an instruction or command to validate the service-specific provisioning data; and

requesting the backend system that provides the service to validate the service-specific provisioning data.

10. The service provisioning system of claim 9 , wherein the stored instructions are further translatable by the processor for:

responsive to a validation error associated with the service-specific provisioning data, notifying a user to correct the validation error.

11. The service provisioning system of claim 9 , wherein the stored instructions are further translatable by the processor for:

responsive to the service-specific provisioning data being valid, persisting the service-specific provisioning data as the data card.

12. The service provisioning system of claim 8 , wherein the SPI comprises a RESTful application programming interface (API) that supports a plurality of operations including at least one of search, create, read, update, delete, or validate operations.

13. The service provisioning system of claim 8 , wherein the data card is one of a plurality of data cards associated with a plurality of services provisioned by the service provisioning system for the client system, the plurality of services provided by disparate backend systems of the electronic information exchange platform.

14. The service provisioning system of claim 13 , wherein the plurality of data cards utilized by the disparate backend systems conforms to a standardized internal representation that is internal to the service provisioning system.

15. A computer program product for managed services provisioning, the computer program product comprising a non-transitory computer readable medium storing instructions translatable by a processor to perform:

receiving, through a user interface, a selection of a service from a plurality of services managed by an electronic information exchange platform, the service provided by a backend system of the electronic information exchange platform;

obtaining a service-specific provisioning descriptor (SSPD) associated with the service, wherein the SSPD and the service have a one-to-one relationship;

dynamically generating, utilizing the SSPD associated with the service, a service provisioning interface (SPI);

receiving, through the SPI generated utilizing the SSPD associated with the service, service-specific provisioning data for configuring the service provided by the backend system for a client system, wherein the service provided by the backend system has not been provisioned for the client system;

generating, using the service-specific provisioning data received through the SPI, a data card for configuring the service provided by the backend system for the client system, wherein the data card is specific to the service managed by the electronic information exchange platform and provided by the backend system to the client system;

receiving, through the SPI, an instruction or command to deploy the data card to the backend system; and

responsive to the instruction or command, communicating the data card to the backend system, wherein the data card is utilized by the backend system to configure the service for the client system to thereby provision the service for the client system.

16. The computer program product of claim 15 , wherein the instructions are further translatable by the processor for:

receiving, through the SPI, an instruction or command to validate the service-specific provisioning data; and

requesting the backend system that provides the service to validate the service-specific provisioning data.

17. The computer program product of claim 16 , wherein the instructions are further translatable by the processor for:

responsive to a validation error associated with the service-specific provisioning data, notifying a user to correct the validation error.

18. The computer program product of claim 16 , wherein the instructions are further translatable by the processor for:

responsive to the service-specific provisioning data being valid, persisting the service-specific provisioning data as the data card.

19. The computer program product of claim 15 , wherein the SPI comprises a RESTful application programming interface (API) that supports a plurality of operations including at least one of search, create, read, update, delete, or validate operations.

20. The computer program product of claim 15 , wherein the data card is one of a plurality of data cards associated with a plurality of services provisioned for the client system, the plurality of services provided by disparate backend systems of the electronic information exchange platform, and wherein the plurality of data cards utilized by the disparate backend systems conforms to a standardized format.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 12, 2019
From: CEPPI, RICARDO; RADKO, JOHN
To: GXS, INC.
Reel/Frame 049740/0412 →
EMPLOYEE INNOVATION AND PROPRIETARY INFORMATION AGREEMENT Recorded Jul 12, 2019
From: GORDON, THOMAS N., JR.
To: GLOBAL EXCHANGE SERVICES, INC.
Reel/Frame 049743/0077 →
CERTIFICATE OF CONTINUANCE Recorded Jul 12, 2019
From: OPEN TEXT GXS, LLC
To: OPEN TEXT GXS ULC
Reel/Frame 049743/0266 →
GXS BUSINESS PURCHASE AGREEMENT Recorded Jul 12, 2019
From: GXS, INC.
To: OPEN TEXT GXS, LLC
Reel/Frame 049743/0275 →
CHANGE OF NAME Recorded Jul 12, 2019
From: GLOBAL EXCHANGE SERVICES, INC.
To: GXS, INC.
Reel/Frame 049745/0931 →
Continuity (3)
Continuation 15223192 · Jul 29, 2016
Provisional Application 62198510 · Jul 29, 2015
Related Publication 20190312773A1 · Oct 10, 2019