IP Library Patent Application 15723443
Patent Application
App. No. 15/723,443

SPLIT ENTERPRISE/PROVIDER WORKFLOWS

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 None
App. No.
15/723,443
Abstract

A provider system (e.g., a cloud based provider system) receives a workflow. For example, the workflow may be for handling a voice communication session in a contact center. The workflow comprises a plurality of workflow tasks. The workflow tasks comprise enterprise workflow tasks and provider workflow tasks. The identified provider workflow tasks are executed on the provider system according the workflow. The provider system initiates execution of the identified enterprise workflow tasks on the enterprise system according to the workflow. By allowing a split workflow between the provider system and the enterprise, exposure to sensitive information used by the provider system may be limited.

Claims (32)

1 . A method comprising:

receiving, by a microprocessor, a workflow;

identifying, by the microprocessor, one or more provider workflow tasks in the workflow;

identifying, by the microprocessor, one or more enterprise workflow tasks in the workflow;

executing, by the microprocessor, the identified one or more provider workflow tasks on a provider system according to the workflow; and

initiating, by the microprocessor, execution of the identified one or more enterprise workflow tasks on an enterprise system according to the workflow.

2 . The method of claim 1 further comprising:

sending, by the microprocessor, to the enterprise system, software objects for the identified one or more enterprise workflow tasks.

3 . The method of claim 2 , wherein sending the software objects to the enterprise system further comprises sending, to the enterprise system, software objects for the identified one or more provider workflow tasks.

4 . The method of claim 1 , wherein at least one of the one or more provider workflow tasks includes an identifier for a variable that is received from one of the one or more enterprise workflow tasks and wherein the variable is identified to not be storable in a memory after use.

5 . The method of claim 1 , wherein initiating execution of the identified one or more enterprise workflow tasks further comprises executing a plurality of consecutive workflow tasks on the enterprise system.

6 . The method of claim 5 , wherein initiating execution of the identified one or more enterprise workflow tasks comprises sending an identifier to the enterprise system that identifies each of the consecutive workflow tasks to execute on the enterprise system.

7 . The method of claim 5 , wherein initiating execution of the identified one or more enterprise workflow tasks comprises sending an identifier to the enterprise system that identifies a first workflow task in the consecutive workflow tasks.

8 . The method of claim 1 , wherein the provider system supports a plurality of enterprises and wherein initiating execution of the identified one or more enterprise workflow tasks comprises sending an enterprise identifier.

9 . The method of claim 8 , wherein the enterprise system confirms that the enterprise identifier is valid before executing the identified one or more enterprise workflows tasks on the enterprise system.

10 . The method of claim 1 , wherein the enterprise system and/or the provider system determines parameters to be sent between the enterprise system and the provider system by analyzing input and output parameters of the workflow provided to the enterprise system and/or the provider system.

11 . A system comprising:

a microprocessor; and

a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that program the microprocessor to execute:

a provider system that receives a workflow, identifies one or more provider workflow tasks in the workflow, identifies one or more enterprise workflow tasks in the workflow, executes the identified one or more provider workflow tasks on the provider system according to the workflow, and initiates execution of the identified one or more enterprise workflow tasks on an enterprise system according to the workflow.

12 . The system of claim 11 wherein the provider system sends, to the enterprise system, software objects for the identified one or more enterprise workflow tasks.

13 . The system of claim 12 , wherein the provider system sends, to the enterprise system, software objects for the identified one or more provider workflow tasks.

14 . The system of claim 11 , wherein at least one of the one or more provider workflow tasks includes an identifier for a variable that is received from one of the one or more enterprise workflow tasks and wherein the variable is identified to not be storable in a memory after use.

15 . The system of claim 11 , wherein initiating execution of the identified one or more enterprise workflow tasks further comprises executing a plurality of consecutive workflow tasks on the enterprise system.

16 . The system of claim 15 , wherein initiating execution of the identified one or more enterprise workflow tasks comprises sending an identifier to the enterprise system that identifies each of the consecutive workflow tasks to execute on the enterprise system.

17 . The system of claim 15 , wherein initiating execution of the identified one or more enterprise workflow tasks comprises sending an identifier to the enterprise system that identifies a first workflow task in the consecutive workflow tasks.

18 . The system of claim 11 , wherein the provider system supports a plurality of enterprises and wherein initiating execution of the identified one or more enterprise workflow tasks comprises sending an enterprise identifier.

19 . The system of claim 18 , wherein the enterprise system confirms that the enterprise identifier is valid before executing the identified one or more enterprise workflows tasks on the enterprise system.

20 . A software development system comprising:

a user interface module that receives input from a user to build a workflow;

a workflow builder that takes the user input to build the workflow, wherein the workflow comprises a plurality of workflow tasks, wherein the plurality of workflow tasks further comprise one or more provider workflow tasks and one or more enterprise workflow tasks.

a compiler that complies the workflow to indicate that the one or more provider workflow tasks will be executed on a provider system and the one or more enterprise workflow tasks will be executed on an enterprise system.

Assignments (7)
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 3, 2017
From: EZELL, JOEL
To: AVAYA INC.
Reel/Frame 043765/0399 →