Recherche Images Maps Play YouTube Actualités Gmail Drive Plus »
Connexion
Les utilisateurs de lecteurs d'écran peuvent cliquer sur ce lien pour activer le mode d'accessibilité. Celui-ci propose les mêmes fonctionnalités principales, mais il est optimisé pour votre lecteur d'écran.

Brevets

  1. Recherche avancée dans les brevets
Numéro de publicationUS5761288 A
Type de publicationOctroi
Numéro de demandeUS 08/461,451
Date de publication2 juin 1998
Date de dépôt5 juin 1995
Date de priorité5 juin 1995
État de paiement des fraisPayé
Autre référence de publicationCA2178153A1, CA2178153C, DE19622347A1, DE19622347B4
Numéro de publication08461451, 461451, US 5761288 A, US 5761288A, US-A-5761288, US5761288 A, US5761288A
InventeursDeborah L. Pinard, Thomas A. Gray
Cessionnaire d'origineMitel Corporation
Exporter la citationBiBTeX, EndNote, RefMan
Liens externes: USPTO, Cession USPTO, Espacenet
Service context sensitive features and applications
US 5761288 A
Résumé
A method of providing communication service to a plurality of subscribers comprised of allocating various services to roles to be filled by the subscribers, receiving a trigger for the service to a subscriber in a particular role, and providing different features to a user associated with the service which are restricted to those services which are allocated to the particular role.
Images(3)
Previous page
Next page
Revendications(12)
We claim:
1. A method of providing communication service to a plurality of subscribers comprising:
(a) allocating various services to be provided to said subscribers to roles to be filled by said subscribers,
(b) receiving a trigger for a service to be provided to a subscriber in a particular role, and
(c) providing different system resources to said subscriber to enable the subscriber to utilize the triggered service, which system resources are restricted to those services which are allocated to said particular role.
2. A method as defined in claim 1 in which the subscriber has more than one role, including designating which role the subscriber is fulfilling for the receipt of the trigger based on a service requested by a calling party, and providing said services to said calling party restricted to those services allocated to the role that the subscriber is fulfilling.
3. A method as defined in claim 2 including designating which role the subscriber is fulfilling by a software user agent.
4. A method as defined in claim 2 in which the system resources providing step includes pointing to a service in a list of services stored in a database, the service pointed to depending on which particular role is allocated to the subscriber, acquiring a basic service task associated with the pointed to service, pointing to a list of allowed system resources from each basic service task, and completing the service by software programs corresponding to each basic service task with an associated group of allowed system resources, which correspond to the service pointed to in the list of services.
5. A method as defined in claim 4 in which the service in the list of services is pointed to by a software program user agent which receives a trigger goal indicating that a call is to be completed to a particular called subscriber in a particular role.
6. A method as defined in claim 4 in which a service stored in the database is a telephone service.
7. A method as defined in claim 1 in which the subscriber has more than one role, including designating which role the subscriber is fulfilling for the receipt of the trigger based on role-indicating data temporarily stored in a database by the subscriber.
8. A method as defined in claim 1 including analyzing call request data input to a software user agent and determining said role based on context of said data input.
9. A method as defined in claim 8 in which the input data is input to said software user agent as a result of the receipt of a trigger.
10. A method as defined in claim 8 in which the input data is input to the software user agent as a result of the initiation of an outgoing trigger from a call requesting device.
11. A method as defined in claim 1 in which a service provided to a subscriber is a telephone service.
12. A method of providing telephone service to a plurality of subscribers comprising:
(a) allocating various telephone services to roles to be filled by said subscribers,
(b) receiving a telephone call to a directory number associated with a subscriber in a particular role, and
(c) providing telephone services to a telephone set associated with the directory number for the telephone call, which are restricted to those services which are allocated to said particular role.
Description
FIELD OF THE INVENTION

This invention relates to the field of communication or control systems, and in particular to a method of providing services to subscribers with services based on roles that the subscribers fill.

BACKGROUND TO THE INVENTION

Communication systems have in the past provided services to subscribers based on services purchased or otherwise allocated to a telephone line (e.g. classes of service) . In the most usual case, classes of service are allocated to subscriber lines on the basis of directory numbers wherein there is one directory number per subscriber line. Classes of service have also been allocated to specific subscribers designated by directory number in cases in which the directory numbers are distinct to the subscriber and are separated from strict association with particular singular subscriber lines, for example as described U.S. patent application 08/262,783, filed Jun. 20, 1994, entitled PORTABLE TELEPHONE USER PROFILES, invented by Deborah Pinard et al and assigned to Mitel Corporation. Thus the classes of service are allocated to subscribers who are identified by directory number. Services roam with the subscriber and move to whatever telephone the subscriber is using, once the subscriber has logged into the system. In the latter case, the service data to be accessible by the subscriber is stored in one or more databases which also store a correlation between the directory number and the subscriber line used by the subscriber.

In all of such cases there is only one group of services which is allocated to the subscriber line or to the subscriber.

There are cases in which the subscriber fulfills several roles, and requires different services for each of the roles. For example, a subscriber can act in the role of a supervisor of a company department conducting electronic hardware design, and can also act in the role of an electronic hardware designer. In the former role, the subscriber may need to be able to make long distance calls, but in the latter may be restricted from doing so. In the latter role the subscriber may need to be able to transmit and receive data via telephone line using a high speed modem, but in the latter role need not do so. Similarly, the subscriber may need a high quality subscriber line to receive data when in the role of a designer, and a standard quality line as a supervisor. The subscriber as supervisor may be given executive style voicemail, and no voicemail when acting as a designer.

If all of the services were obtained by the company for each of the employees of the company which might need only one or a few of the services, clearly the cost of equipment and/or service fee for providing the services is higher than the cost would be if only the required services for the role of the subscriber were provided.

SUMMARY OF THE INVENTION

In accordance with the present invention, particular features, restrictions and applications (referred to herein as services) are provided to a subscriber in a corresponding role. In the event the subscriber assumes a different role, the features, restrictions and applications can be different. Thus the system resources needed only for the defined roles in the company can be obtained, minimizing the cost.

It is preferred that the system should be implemented in a communication type system which uses agents, such as is described in U.S. patent application entitled ADAPTIVE COMMUNICATION SYSTEM, Ser. No. 08/257,917, filed on Jun. 10, 1994, and invented by Deborah Pinard et al, which is incorporated herein by reference. That system will be referred to below as the CATA system.

In accordance with a preferred embodiment of the invention, a method of providing a communication service to a plurality of subscribers is comprised of allocating various communication services to roles to be filled by said subscribers, receiving a call to a directory number associated with a subscriber in a particular role, and providing communication services to a telephone set associated with the directory number for the call, which are restricted to those services which are allocated to the particular role.

In accordance with another embodiment, in the method described above, the communication providing services step includes pointing to a service in a list of services stored in a database, the service pointed to depending on which particular role is allocated to the called party, acquiring a basic service list associated with the pointed to service, pointing to a list of allowed features from each basic service task, and completing the call by software programs corresponding to each basic service task with an associated group of allowed features, which correspond to the service pointed to in the list of services.

Preferably the service in the list of services is pointed to by a user agent which receives a trigger goal indicating that a call is to be completed to a particular called subscriber in a particular role. Communication services can be, for example, telephone service, electronic mail, printing, voice mail, facsimile, etc.

In accordance with another embodiment, a method of providing communication service to a plurality of subscribers is comprised of allocating various services to roles to be filled by the subscribers, receiving a trigger for the service to a subscriber in a particular role, and providing different features to a user associated with the service which are restricted to those services which are allocated to the particular role.

In accordance with another embodiment, a method of providing telephone service to a plurality of subscribers is comprised of allocating various telephone services to roles to be filled by the subscribers, receiving a telephone call to a directory number associated with a subscriber in a particular role, and providing telephone services to a telephone set associated with the directory number for the telephone call, which are restricted to those services which are allocated to the particular role.

BRIEF INTRODUCTION TO THE DRAWINGS

A better understanding of the invention will be obtained by reading the description of the invention below, with reference to the following drawings, in which:

FIG. 1 is a block diagram of parts of a system in which the present invention can be implemented,

FIG. 2 is a block diagram of a service view used to create services belonging to a role,

FIG. 3 is an illustration used in explaining the relationship between roles and services,

FIG. 4 is an illustration used to explain an example of the operation of the invention, and

FIG. 5 is another illustration used to explain an example of the operation of the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a basic summary block diagram of part of a CATA system on which the present invention can be implemented. A main processor 1, which stores various control programs and databases in memory 2, is connected to a local area network ATM (LAN) 3. Various resources 5, such as DTMF receivers, dialers, etc. are connected to the LAN 3. User agents 7, which are programs running on a client or server, are programs running on are connected to the LAN, and to various station apparatus, such as telephone sets 9. The telephone sets can be used in conjunction with various computer or other data terminals (not shown). A terminal 11 is also connected to the LAN, which can be used to input setup data to the system, and which can be stored for example in memory 2.

Alternative to using an ATM LAN, the user agents can be a server 10 which is connected to a non-ATM LAN.

The processor memory 2 stores programs which can provide a user interface on terminal 11 to receive data for storage in a database, in a well known manner. One of the types of data to be input via terminal 11 is a list and locations (addresses) of resources, another is a designation of what services are basic (e.g. unenhanced voice telephone service), another is a list of services to be provided in groups (i.e. service template creation), another is a list of roles that are assumed by employees within the company, and the reporting relationships (the hierarchy), and another is a list of services that can be provided. By a list, it is meant that the database stores not only the title of the service, but also the address in memory 2 of a service software program that can be called by an agent in order to provide the service.

For example, a basic service software program stored in memory 2 can be called by an agent to perform the completion of a voice telephone call from one party to another. An enhanced service software program stored In memory 2 can be called by an agent to connect a high speed modem resource to the LAN and to establish a channel between the telephone set and the modem. Another enhanced service software program stored in memory 2 can be called by an agent to select a stored sequence of digits and to send them to a dialer resource with an instruction to dial them over a telephone line, and to establish a channel between a telephone set and another or to a trunk, following the user agent recognizing that the subscriber has dialed a limited number of speed call digits following the invoking of a speed call. Of course the above is merely illustrative of a small number of services which can be provided in a system.

For example, assume that an employee called Tom is both a software and a hardware designer, and thus has two roles in the company, each of which requires a different group of services to be provided by the system. In addition, roles may be filled for different groups within an enterprise. Each group may have purchased its own resources. Thus the invention provides a way of arbitrating access to authorized resources as well as services.

When the database service view is called up on the display of the terminal 11, services are associated with roles which have been defined in the functional view. FIG. 2 illustrates a functional view which is called up for the role of software designer, and which can be used for each software designer in the company. A service is created by linked basic services 13A, 13B, etc. For example, the basic services can be to accept a call, to generate speech, to make a call, etc.

For each of the basic services, various common attributes are listed, with an indication whether they are available to the role or not, for that basic function. For example, for the accept call service 13A, the list of attributes 15A shown are transfer=Y (yes), conference=N (no), privacy=N, etc. For the make call service, the attributes 15B shown are transfer=N, restriction to local calls only, etc. The resources (and their addresses) that are required to perform each of the services are also defined with the services (not shown in FIG. 2).

Thus the attributes assigned to the basic services are particular to the service being created and areas assigned in the service view of the database as noted above, and are stored in memory 2. The resources that can provide each of the services are also defined and their addresses indicated. It should be noted that in the agent form of system, one or more of the resources that can perform particular services can be designated by people, represented by their agents.

Thus, for example, there may be an incoming call to the president of the company, which is defined by an incoming caller designating the company president by dialing a digit in response to an automated attendant. The automated attendant agent, looking up the service list to complete a call to the president, would locate the resource that identifies the president by name, and could announce the incoming caller to the president by name on a loudspeaking telephone. The automated attendant agent could locate the telephone line associated with the president, assuming that the president has logged the telephone line that he is using into the system, or that the system assumes a particular default telephone line that he uses, and provide the services associated with the role of the president to that line.

In the event the president is out of the office, and there is an acting president, the identity of the line used by the acting president, and if desired the identity of the person who is acting president, is stored in the memory 2 upon modification of the service view. In this manner, the services that can be invoked by, or which are extended to, the president, are associated with the line used by the acting president.

Another example of this could be the assignment of "experts" to assist customers calling about problems. The "expert" role could be filled on a rate basis by different people. This rate could assign experts by shift, vacation, coverage, etc.

Turning to FIG. 3, two of the roles, software designer 17A and hardware designer 17B are illustrated. The identity of the person Tom 19 is a resource. The identity of Tom is associated with both roles software designer 17A and hardware designer 17B.

Tom, of course, will typically have access to a telephone set 21. Services A and B are associated with the software designer role 17A and services C and D are associated with the hardware designer role 17B.

When a telephone call is received on telephone 21, what Tom can do with the call is dependent on the roll that he is providing at that time. The telephone also takes on the characteristics of the service.

Several techniques can be used to identify whether services A and B or C and D should be used for the call. One technique is to have Tom log into the system that he is assuming a particular role. To do this, he need only lift his telephone 9 handset (FIG. 1, which corresponds to telephone set 21 in FIG. 3), which causes his user agent 7 to be allocated to his call in a manner as described in the aforenoted CATA patent application, and dial a predetermined digit or group of digits prefixed by a command digit such as the # symbol. Of course his telephone set could have dedicated command keys to generate prefix signals.

Alternatively, the system could itself determine from the context of the incoming call which of Tom's roles are to be used. For example, the incoming caller could be connected to an automated attendant resource 5 which requests, using synthesized voice, the keying of a particular key in a voiced keying tree by the calling subscriber which identifies the role.

The incoming call could be a "call by name" call, with an accompanying identifier of Tom's role for that call.

The incoming call could be a request for a particular service that could only be provided by Tom in a particular role. For example, assume that Tom in his role as software designer had stored data or a program in a file that is to be retrieved by a remote calling party. The calling party dials Tom's line by computer terminal to access Tom's computer terminal which is connected to the LAN (not shown, but connected in a manner similar to telephone sets 9).

The signals provided to Tom's user agent from the remote terminal to request connection to Tom's computer terminal allows that agent to identify from the context of the signals that it is Tom in his role as a software designer, rather than as a hardware designer that is desired. In response Tom's user agent causes services A and B to be allocated to the call, rather than services C and D.

Services A and B could be, for example, include a program that communicates with the computer of the calling subscriber asking for a password, and which allows certain resources 5 (such as a modem of a particular speed) which could facilitate access to Tom's computer and downloading of the data or program file to the computer of the calling subscriber.

In this manner, services can be allocated to a role by recognition of the context of the incoming call (or of an outgoing call), and the call controlled thereby.

Another example of the context of the signals of a call causing allocation of services based on the role of the subscriber is as follows. Assume that a software or hardware designer is given the services of up to 10 speed call numbers (0-9), while the company president is given the services of up to 100 (00-99). The user agent can count how many digits are being dialed, and in the event there is only one (following a speed call invoking signal), assign services that have been allocated in the function view during a setup process. In the event two digits are dialed for speed call, the user agent assumes that it is the company president who is dialing, and services that have been allocated for the president are allocated to the call.

Turning to FIG. 4, assume that an incoming call has been received, designated for Tom. In a manner explained in the aforenoted CATA patent application, the process proceeds to provide a goal to Tom's user agent 7. In accordance with the present invention, the call has been identified as being designated not only for Tom, but Tom in a particular role. Thus all of the services to be allocated to Tom in that role are provided, for example services A and B.

Services A and B are designated by goals 1 and 2, which are communicated from the processor 1 to Tom's user agent 7 in response to the incoming call. These goals are communicated to the goal resolution portion of agent 7, in a bulletin board manner as described in the aforenoted CATA patent application. At the same time, the user agent having identified the goals, obtains the identification of corresponding particular service to be carried out, from the processor 1 memory. From an identification of the service, the attributes stored in the database in memory 2 that were input in the service view described with reference to FIG. 2 are communicated to Tom's user agent 7.

One of the services resulting from one of the goals can be to ring Tom's telephone. Tom's user agent checks the corresponding attributes for that service and determines that there is no ringing restriction on Tom's telephone. Tom's user agent then communicates with the agent 22 of Tom's telephone 21, and sends a message to ring the telephone. The agent of Tom's telephone as a result checks it's database to determine whether Tom's telephone is busy, and if not, calls a ringing signal generator resource 5 to send a ringing signal to Tom's telephone at the address of it's line circuit as connected to LAN 3.

FIG. 5 illustrates an embodiment of the process of the invention in more detail. As described with reference to FIG. 4, a goal is input to a user agent 7. The goal appears as a message to trigger a process (program) to be invoked by the user agent 7.

The user agent, in response produces a pointer to the program code stored in memory 2 which executes the service based on the trigger goal. For example the program code for a plurality of services, i.e. service #1, service #2, . . . service #n is stored in a database 23 or in equivalent files, in memory 2. Thus when a goal is received by the user agent, it points to a particular program stored in database 23 or elsewhere in memory 2.

The particular program, e.g. service #1, pointed to in database 23 is comprised of a list of service tasks 25, for example basic service task #1, basic service task #2, etc. Each service task points to a list 27 of allowed features, such as feature x, feature y, feature z, etc. The feature list can be a list of all possible features, with an indication of which are allowed and which are not allowed for the processing of a particular task.

For example, one of the tasks can be to call a ringing signal generator from the resources 5. The list of allowed features could allow or disallow special ringing cadences.

For an incoming call, for example a voicemail message, the goal which is input to the called party's user agent can be determined from the context of the incoming call, as described earlier. The goal, which is input from the processor in a manner as described in the aforenoted CATA patent application, can be different depending on which role the called party is assuming, as described above. Thus the user agent points to different services in the database 23 depending on the role based nature of the trigger goal.

With different services extended to the user depending on his role, the particular basic service tasks undertaken from the list 25 are unique to the particular role of the called party, and the list of allowed features pointed to by the tasks in the service list 25 also are unique for each particular service task.

For example, the basic service task #1 could be to invoke ringing as described above. The feature list could restrict special cadence ringing. However basic service task #2 could also be to invoke ringing as described above, but the feature list for basic service task #2 could be to allow special cadence ringing. Thus the particular trigger goal which is received by user agent 7, which is role dependent, would cause user agent 7 to point to either service #1 or #2 to invoke ringing, dependent on the allocated service to the particular role of the called party.

It will be understood that while incoming calls have been described, the invention is equally applicable to subscribers making outgoing calls. In such cases, the user agent of the calling party determines either from dialed digits, other signals which are input by the user, or from context analysis of the signals input by the user, what is the role of the user. As a result, features can be provided or restricted from the user.

A person understanding this invention may now conceive of alternative structures and embodiments or variations of the above. All of those which fall within the scope of the claims appended hereto are considered to be part of the present invention.

Citations de brevets
Brevet cité Date de dépôt Date de publication Déposant Titre
US5299260 *29 juil. 199329 mars 1994Unifi Communications CorporationTelephone call handling system
US5323452 *18 déc. 199021 juin 1994Bell Communications Research, Inc.Visual programming of telephone network call processing logic
US5329578 *26 mai 199212 juil. 1994Northern Telecom LimitedPersonal communication service with mobility manager
US5335269 *12 mars 19922 août 1994Rockwell International CorporationTwo dimensional routing apparatus in an automatic call director-type system
US5355404 *29 juin 199311 oct. 1994At&T Bell LaboratoriesMethod of controlling parameter downloading from a communication switching system to customer stations
US5425097 *7 juin 199313 juin 1995At&T Corp.Analog display station apparatus and method of effecting telephone features
US5434906 *13 sept. 199318 juil. 1995Robinson; Michael J.Method and apparatus for processing an incoming call in a communication system
US5450480 *6 nov. 199212 sept. 1995Bell Communications Research, Inc.Method of creating a telecommunication service specification
US5455853 *6 nov. 19923 oct. 1995Bell Communications Research, Inc.Method of creating a telecommunication service template
US5461666 *11 août 199424 oct. 1995Texas Instruments IncorporatedSystem and method for configuring a telephone
US5479491 *16 déc. 199426 déc. 1995Tele Guia Talking Yellow PagesIntegrated voice-mail based voice and information processing system
US5485511 *8 sept. 199416 janv. 1996Siemens Rolm Communications Inc.Method and apparatus for determining the telephony features assigned to a telephone
US5509060 *19 nov. 199316 avr. 1996At&T Corp.Network-accessible intelligent telephone service
US5517562 *1 nov. 199414 mai 1996Independent Telecommunications Network, Inc.Method and system for providing a distributed service network for telecommunications service providers
US5528677 *11 mars 199418 juin 1996Sprint Communications Company L.P.System for providing communications services in a telecommunications network
US5541983 *2 déc. 199430 juil. 1996Mitel CorporationAutomatic telephone feature selector
US5541986 *27 juil. 199330 juil. 1996Bell Communications Research, Inc.Method and system for automated telecommunications service script consolidation and downloading
US5548636 *6 juin 199520 août 1996Northern Telecom LimitedMethod and apparatus for providing user controlled call management services
Référencé par
Brevet citant Date de dépôt Date de publication Déposant Titre
US6031904 *19 juin 199729 févr. 2000Nortel Networks CorporationService order mechanism for telephone subscriber
US6041104 *1 oct. 199721 mars 2000Ameritech CorporationMethod and system for ordering a telecommunication service
US6041110 *27 juin 199721 mars 2000AlcatelMethod and apparatus for providing a telecommunications service
US6075851 *1 avr. 199913 juin 2000Mitel CorporationOrganization chart based call information routing
US6167261 *27 févr. 199726 déc. 2000At&T Wireless Svcs. Inc.Wireless communication service management
US6240172 *29 janv. 199829 mai 2001Lucent Technologies, Inc.Remote reconfiguration method for feature-function telephone sets
US6266404 *31 déc. 199724 juil. 2001Nortel Networks LimitedMethod and apparatus for controlling characteristics of distributed telephone sets from a central telephone switch
US6349137 *5 août 199919 févr. 2002Rockwell Electronic Commerce Corp.Apparatus and method for providing support software for an agent workstation of an automatic call distributor
US6647099 *8 juin 199911 nov. 2003Hewlett-Packard Development Company, L.P.Administrative control and security of modems
US668100110 août 199820 janv. 2004Nortel Networks LimitedComputer integrated telecommunications systems and methods
US67146424 nov. 200230 mars 2004Bank One, DelawareSystem and methods for call decisioning in a virtual call center integrating telephony with computers
US6744870 *25 juil. 20001 juin 2004Nokia CorporationService provision in a telecommunications network
US676040921 janv. 20006 juil. 2004Sbc Properties, L.P.Method and system for ordering a telecommunication service
US6795969 *11 oct. 200121 sept. 2004Mitel CorporationTransfer of basic knowledge to agents
US6816589 *21 août 19989 nov. 2004Mitel CorporationDynamic communications groups
US7093009 *5 juil. 200115 août 2006Intel CorporationUploading personal agents to personalize network services
US7110514 *17 déc. 200119 sept. 2006International Business Machines CorporationIdentifying a context for a call
US715182317 sept. 200319 déc. 2006Hewlett-Packard Development Company, L.P.Determining whether a telephony call is permitted based on permission data
US739238628 janv. 200424 juin 2008J P Morgan Chase BankSetuid-filter method for providing secure access to a credentials store for computer systems
US741526727 janv. 200419 août 2008Jp Morgan Chase BankMethods and systems for managing call reports for the financial services industry
US753600215 mars 200419 mai 2009Jpmorgan Chase Bank, National AssociationSystem and method of intelligent call routing for cross sell offer selection based on optimization parameters or account-level data
US767675113 juil. 20049 mars 2010Jpmorgan Chase Bank, NaSystem and method for processing applicant input information
US768501324 août 200723 mars 2010Jpmorgan Chase BankSystem and method for automatic financial project management
US768950431 oct. 200230 mars 2010Jpmorgan Chase Bank, N.A.System and method for establishing or modifying an account with user selectable terms
US775681612 oct. 200513 juil. 2010Jpmorgan Chase Bank, N.A.System and method for network-based project management
US778357825 janv. 200624 août 2010Jpmorgan Chase Bank, N.A.System for providing cardless payment
US794153319 févr. 200210 mai 2011Jpmorgan Chase Bank, N.A.System and method for single sign-on session management without central server
US796649622 déc. 200621 juin 2011Jpmorgan Chase Bank, N.A.System and method for single sign on process for websites with multiple applications and services
US798750121 déc. 200126 juil. 2011Jpmorgan Chase Bank, N.A.System and method for single session sign-on
US814485024 sept. 200827 mars 2012International Business Machines CorporationLogging calls according to call context
US81455228 nov. 200627 mars 2012Jpmorgan Chase Bank, N.A.System and method for establishing or modifying an account with user selectable terms
US815529712 avr. 200410 avr. 2012Jpmorgan Chase BankSystem and method for providing call-back options
US816096011 déc. 200917 avr. 2012Jpmorgan Chase Bank, N.A.System and method for rapid updating of credit information
US818587722 juin 200522 mai 2012Jpmorgan Chase Bank, N.A.System and method for testing applications
US818594017 juil. 200722 mai 2012Jpmorgan Chase Bank, N.A.System and method for providing discriminated content to network users
US81908931 juil. 200429 mai 2012Jp Morgan Chase BankPortable security transaction protocol
US83014935 nov. 200230 oct. 2012Jpmorgan Chase Bank, N.A.System and method for providing incentives to consumers to share information
US832168226 janv. 200927 nov. 2012Jpmorgan Chase Bank, N.A.System and method for generating and managing administrator passwords
US832180721 nov. 200827 nov. 2012Alcatel LucentSystem and method for generating a visual representation of a service and service management system employing the same
US833585518 mai 200718 déc. 2012Jpmorgan Chase Bank, N.A.System and method for portal infrastructure tracking
US843808628 nov. 20017 mai 2013Jpmorgan Chase Bank, N.A.System and method for providing customers with seamless entry to a remote server
US845807015 juin 20124 juin 2013Jpmorgan Chase Bank, N.A.System and method for providing customers with seamless entry to a remote server
US846823721 nov. 200818 juin 2013Alcatel LucentNormalization engine and method of requesting a key or performing an operation pertaining to an end point
US847373519 mai 200825 juin 2013Jpmorgan ChaseSystems and methods for managing digital certificates
US852788921 nov. 20083 sept. 2013Alcatel LucentApplication and method for dynamically presenting data regarding an end point or a service and service management system incorporating the same
US853302121 nov. 200810 sept. 2013Alcatel LucentSystem and method for remotely repairing and maintaining a telecommunication service using service relationships and service management system employing the same
US854931514 sept. 20121 oct. 2013Jpmorgan Chase Bank, N.A.System and method for generating and managing administrator passwords
US85654025 mars 201222 oct. 2013Jpmorgan Chase BankSystem and method for providing call-back options
US857197524 nov. 199929 oct. 2013Jpmorgan Chase Bank, N.A.System and method for sending money via E-mail over the internet
US858392626 avr. 200612 nov. 2013Jpmorgan Chase Bank, N.A.System and method for anti-phishing authentication
US859000830 oct. 200819 nov. 2013Jpmorgan Chase Bank, N.A.System and method for single sign on process for websites with multiple applications and services
US860083016 juil. 20103 déc. 2013Steven M. HoffbergSystem and method for providing a payment to a non-winning auction participant
US863110821 nov. 200814 janv. 2014Alcatel LucentApplication and method for generating automated offers of service and service management system incorporating the same
US86877907 févr. 20131 avr. 2014Jpmorgan Chase Bank, N.A.System and method of intelligent call routing for cross sell offer selection based on optimization parameters or account-level data
US872601117 mai 201313 mai 2014Jpmorgan Chase Bank, N.A.Systems and methods for managing digital certificates
US873207216 mars 201020 mai 2014Jpmorgan Chase Bank, N.A.System and method for establishing or modifying an account with user selectable terms
US873759925 sept. 201227 mai 201424/7 Customer, Inc.Interaction management
US878109617 sept. 201315 juil. 2014Jpmorgan Chase Bank, N.A.System and method for providing call-back options
US879349013 déc. 200629 juil. 2014Jpmorgan Chase Bank, N.A.Systems and methods for multifactor authentication
US884971614 sept. 200730 sept. 2014Jpmorgan Chase Bank, N.A.System and method for preventing identity theft or misuse by restricting access
US885059821 nov. 200830 sept. 2014Alcatel LucentService management system and method of executing a policy
US890418120 nov. 20122 déc. 2014David P. FelsherSystem and method for secure three-party communications
US894939321 nov. 20083 févr. 2015Alcatel LucentSelf-service application for a service management system and method of operation thereof
US898936612 déc. 201224 mars 2015Jpmorgan Chase Bank, N.A.System and method for managing customer communications over communication channels
US899564317 janv. 201431 mars 2015Jpmorgan Chase Bank, N.A.System and method of intelligent call routing for cross sell offer selection based on optimization parameters or account-level data
US9077804 *11 avr. 20147 juil. 201524/7 Customer, Inc.Interaction management
US914361512 juin 201422 sept. 2015Jp Morgan Chase Bank, N.A.System and method for providing call-back options
US924001224 juin 201419 janv. 2016Jpmorgan Chase Bank, N.A.Systems and methods for multifactor authentication
US937436610 oct. 201321 juin 2016Jpmorgan Chase Bank, N.A.System and method for anti-phishing authentication
US94199511 déc. 201416 août 2016St. Luke Technologies, LlcSystem and method for secure three-party communications
US941995717 mars 201416 août 2016Jpmorgan Chase Bank, N.A.Confidence-based authentication
US9549064 *28 août 200617 janv. 2017Tp Lab Inc.System and method to customize a telephone
US960882629 juin 201028 mars 2017Jpmorgan Chase Bank, N.A.System and method for partner key management
US964630417 juil. 20069 mai 2017Jpmorgan Chase Bank, N.A.System for providing cardless payment
US966102118 mai 201623 mai 2017Jpmorgan Chase Bank, N.A.System and method for anti-phishing authentication
US96792933 déc. 201513 juin 2017Jpmorgan Chase Bank, N.A.Systems and methods for multifactor authentication
US96928727 déc. 201627 juin 2017Tp Lab Inc.System and method to customize a telephone
US97108511 mars 201318 juil. 2017Jpmorgan Chase Bank, N.A.System and method for generating graphical user interface
US20020023119 *11 oct. 200121 févr. 2002Gray Thomas A.Transfer of basic knowledge to agents
US20030007618 *5 juil. 20019 janv. 2003Jose GutermanUploading personal agents to personalize network services
US20030108183 *4 nov. 200212 juin 2003First Usa Bank, NaSystem and methods for call decisioning in a virtual call center integrating telephony with computers
US20030112941 *17 déc. 200119 juin 2003International Business Machines CorporationIdentifying a context for a call
US20040062368 *17 sept. 20031 avr. 2004Durkin David P.Determining whether a telephony call is permitted based on permission data
US20040243641 *13 juil. 20042 déc. 2004Bank One, Delaware, National AssociationSystem and method for generating graphical user interfaces
US20050039041 *14 mai 200417 févr. 2005Shaw Mari MyraAccess, identity, and ticketing system for providing multiple access methods for smart devices
US20050125678 *7 janv. 20059 juin 2005Janssen Scope LlcSystems and methods for configuring digital storage media with multiple access privileges
US20050132187 *27 janv. 200416 juin 2005Scott MalatMethods and systems for managing call reports for the financial services industry
US20080027861 *24 août 200731 janv. 2008Gendler JosephSystem and method for automatic financial project management
US20080063171 *28 août 200613 mars 2008Tp Lab Inc.System and method to customize a telephone
US20090132317 *21 nov. 200821 mai 2009Motive, IncorporatedSystem and method for identifying functions and data with respect to a service and a subscriber and service management system employing the same
US20090132323 *21 nov. 200821 mai 2009Motive, IncorporatedCustomer service representative support application for a service management system and method of operation thereof
US20090132324 *21 nov. 200821 mai 2009Motive, IncorporatedSystem and method for remotely repairing and maintaining a telecommunication service using service relationships and service management system employing the same
US20090132678 *21 nov. 200821 mai 2009Motive, IncorporatedSystem and method for remotely activating a service and service management system incorporating the same
US20090132684 *21 nov. 200821 mai 2009Motive, IncorporatedNormalization engine and method of requesting a key or performing an operation pertaining to an end point
US20090132685 *21 nov. 200821 mai 2009Motive, IncorporatedSystem and method for provisioning and unprovisioning multiple end points with respect to a subscriber and service management system employing the same
US20090132693 *21 nov. 200821 mai 2009Motive, IncorporatedApplication and method for generating automated offers of service and service management system incorporating the same
US20090132709 *21 nov. 200821 mai 2009Motive, IncorporatedApplication and method for dynamically presenting data regarding an end point or a service and service management system incorporating the same
US20090132710 *21 nov. 200821 mai 2009Motive, IncorporatedSelf-service application for a service management system and method of operation thereof
US20090132945 *21 nov. 200821 mai 2009Motive, IncorporatedSystem and method for generating a visual representation of a service and service management system employing the same
US20090133098 *21 nov. 200821 mai 2009Motive, IncorporatedService management system and method of executing a policy
US20090292664 *21 nov. 200826 nov. 2009Motive, IncorporatedService management system and method of operation thereof
US20140219437 *11 avr. 20147 août 201424/7 Customer, Inc.Interaction Management
EP1161056A1 *31 mai 20005 déc. 2001Telefonaktiebolaget Lm EricssonMethod for file transfer between a data generator and a post-processor in a telecommunication system
EP3133507A130 mars 201622 févr. 2017Secude AGContext-based data classification
EP3196798A119 janv. 201726 juil. 2017Secude AGContext-sensitive copy and paste block
WO1999017515A1 *28 sept. 19988 avr. 1999Ameritech CorporationMethod and system for ordering a telecommunication service
WO2001093539A2 *29 mai 20016 déc. 2001Telefonaktiebolaget Lm Ericsson (Publ)Method for file transfer between a data generator and a post-processor in a telecommunication system
WO2001093539A3 *29 mai 200111 avr. 2002Ericsson Telefon Ab L MMethod for file transfer between a data generator and a post-processor in a telecommunication system
WO2002049327A2 *6 nov. 200120 juin 2002Siemens AktiengesellschaftFunction restrictions placed on an operator workstation, based on user characteristics and/or the service selected
WO2002049327A3 *6 nov. 200110 avr. 2003Siemens AgFunction restrictions placed on an operator workstation, based on user characteristics and/or the service selected
WO2002101550A1 *7 juin 200219 déc. 2002Sonera OyjAdding a new service in a distributed object component network
WO2002101551A1 *7 juin 200219 déc. 2002Sonera OyjAuthenticating in a distributed object component network
WO2002102093A1 *7 juin 200219 déc. 2002Sonera OyjService creation in a distributed object component network
WO2013078321A1 *21 nov. 201230 mai 201324/7 Customer, Inc.Interaction management
Classifications
Classification aux États-Unis379/201.03, 379/265.02, 379/309
Classification internationaleH04Q3/00
Classification coopérativeH04Q2213/13517, H04Q2213/13526, H04Q3/0029, H04Q2213/13516
Classification européenneH04Q3/00D3
Événements juridiques
DateCodeÉvénementDescription
2 févr. 1996ASAssignment
Owner name: MITEL CORPORATION, CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PINARD, DEBORAH L.;GRAY, THOMAS A.;REEL/FRAME:007796/0111
Effective date: 19950901
15 oct. 1996ASAssignment
Owner name: MITEL CORPORATION, CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PINARD, DEBORAH L.;GRAY, THOMAS A.;REEL/FRAME:008198/0966
Effective date: 19960901
19 nov. 1998ASAssignment
Owner name: CANADIAN IMPERIAL BANK OF COMMERCE, CANADA
Free format text: GRANTING SECURITY INTEREST;ASSIGNOR:MITEL CORPORATION;REEL/FRAME:009893/0001
Effective date: 19980630
7 mars 2001ASAssignment
Owner name: MITEL SEMICONDUCTOR AMERICAS, INC., A DELAWARE COR
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CANADIAN IMPERIAL BANK OF COMMERCE;REEL/FRAME:011590/0406
Effective date: 20010216
Owner name: MITEL CORPORATION, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CANADIAN IMPERIAL BANK OF COMMERCE;REEL/FRAME:011590/0406
Effective date: 20010216
Owner name: MITEL, INC., A DELAWARE CORPORATION, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CANADIAN IMPERIAL BANK OF COMMERCE;REEL/FRAME:011590/0406
Effective date: 20010216
Owner name: MITEL SEMICONDUCTOR, INC., A DELAWARE CORPORATION,
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CANADIAN IMPERIAL BANK OF COMMERCE;REEL/FRAME:011590/0406
Effective date: 20010216
Owner name: MITEL SEMICONDUCTOR, LIMITED, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CANADIAN IMPERIAL BANK OF COMMERCE;REEL/FRAME:011590/0406
Effective date: 20010216
Owner name: MITEL TELCOM LIMITED CORPORATION, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CANADIAN IMPERIAL BANK OF COMMERCE;REEL/FRAME:011590/0406
Effective date: 20010216
11 mai 2001ASAssignment
Owner name: MITEL KNOWLEDGE CORPORATION, CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MITEL CORPORATION;REEL/FRAME:011871/0001
Effective date: 20010215
27 sept. 2001FPAYFee payment
Year of fee payment: 4
14 juil. 2005ASAssignment
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MITEL KNOWLEDGE CORPORATION;REEL/FRAME:016345/0283
Effective date: 20021101
Owner name: MITEL NETWORKS CORPORATION,CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MITEL KNOWLEDGE CORPORATION;REEL/FRAME:016345/0283
Effective date: 20021101
18 juil. 2005ASAssignment
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: SECURITY AGREEMENT;ASSIGNOR:HIGHBRIDGE INTERNATIONAL LLC;REEL/FRAME:016345/0236
Effective date: 20050427
Owner name: MITEL NETWORKS CORPORATION,CANADA
Free format text: SECURITY AGREEMENT;ASSIGNOR:HIGHBRIDGE INTERNATIONAL LLC;REEL/FRAME:016345/0236
Effective date: 20050427
25 juil. 2005ASAssignment
Owner name: BNY TRUST COMPANY OF CANADA, TRUST COMPANY OF CANA
Free format text: SECURITY AGREEMENT;ASSIGNOR:MITEL NETWORKS CORPORATION, A CORPORATION OF CANADA;REEL/FRAME:016891/0959
Effective date: 20050427
4 nov. 2005FPAYFee payment
Year of fee payment: 8
13 sept. 2007ASAssignment
Owner name: MORGAN STANLEY & CO. INCORPORATED, NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:019817/0847
Effective date: 20070816
Owner name: MORGAN STANLEY & CO. INCORPORATED, NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:019817/0881
Effective date: 20070816
Owner name: MORGAN STANLEY & CO. INCORPORATED,NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:019817/0847
Effective date: 20070816
Owner name: MORGAN STANLEY & CO. INCORPORATED,NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:019817/0881
Effective date: 20070816
21 oct. 2008ASAssignment
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: RELEASE & DISCHARGE OF SECURITY INTEREST;ASSIGNOR:HIGHBRIDGE INTERNATIONAL LLC/BNY TRUST COMPANY OF CANADA;REEL/FRAME:021794/0510
Effective date: 20080304
Owner name: MITEL NETWORKS CORPORATION,CANADA
Free format text: RELEASE & DISCHARGE OF SECURITY INTEREST;ASSIGNOR:HIGHBRIDGE INTERNATIONAL LLC/BNY TRUST COMPANY OF CANADA;REEL/FRAME:021794/0510
Effective date: 20080304
4 nov. 2009FPAYFee payment
Year of fee payment: 12
2 avr. 2013ASAssignment
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:WILMINGTON TRUST, NATIONAL ASSOCIATION FKA WILMINGTON TRUST FSB/MORGAN STANLEY & CO. INCORPORATED;REEL/FRAME:030165/0776
Effective date: 20130227
8 avr. 2013ASAssignment
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, TEXAS
Free format text: SECURITY AGREEMENT;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:030186/0894
Effective date: 20130227
Owner name: WILMINGTON TRUST, N.A., AS SECOND COLLATERAL AGENT
Free format text: SECURITY INTEREST;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:030201/0743
Effective date: 20130227
15 avr. 2013ASAssignment
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF NEW YORK MELLON, THE;MORGAN STANLEY & CO. INCORPORATED;MORGAN STANLEY SENIOR FUNDING, INC.;REEL/FRAME:030264/0470
Effective date: 20130227
6 févr. 2014ASAssignment
Owner name: MITEL US HOLDINGS, INC., ARIZONA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WILMINGTON TRUST, NATIONAL ASSOCIATION;REEL/FRAME:032167/0464
Effective date: 20140131
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WILMINGTON TRUST, NATIONAL ASSOCIATION;REEL/FRAME:032167/0464
Effective date: 20140131
10 févr. 2014ASAssignment
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A.;REEL/FRAME:032210/0245
Effective date: 20140131
Owner name: MITEL US HOLDINGS, INC., ARIZONA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A.;REEL/FRAME:032210/0245
Effective date: 20140131
14 févr. 2014ASAssignment
Owner name: JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT, NE
Free format text: SECURITY AGREEMENT;ASSIGNORS:MITEL US HOLDINGS, INC.;MITEL NETWORKS CORPORATION;AASTRA USA INC.;REEL/FRAME:032264/0760
Effective date: 20140131
1 mai 2015ASAssignment
Owner name: MITEL COMMUNICATIONS INC. FKA AASTRA USA INC., TEX
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT;REEL/FRAME:035562/0157
Effective date: 20150429
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT;REEL/FRAME:035562/0157
Effective date: 20150429
Owner name: MITEL US HOLDINGS, INC., ARIZONA
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT;REEL/FRAME:035562/0157
Effective date: 20150429
28 mai 2015ASAssignment
Owner name: BANK OF AMERICA, N.A.(ACTING THROUGH ITS CANADA BR
Free format text: SECURITY INTEREST;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:035783/0540
Effective date: 20150429
25 mars 2017ASAssignment
Owner name: MITEL NETWORKS CORPORATION, CANADA
Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461
Effective date: 20170309
Owner name: MITEL US HOLDINGS, INC., ARIZONA
Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461
Effective date: 20170309
Owner name: MITEL (DELAWARE), INC., ARIZONA
Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461
Effective date: 20170309
Owner name: MITEL BUSINESS SYSTEMS, INC., ARIZONA
Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461
Effective date: 20170309
Owner name: MITEL COMMUNICATIONS, INC., TEXAS
Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461
Effective date: 20170309
Owner name: MITEL NETWORKS, INC., ARIZONA
Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461
Effective date: 20170309