EP1620817A2 - Managing contacts in a communication network - Google Patents
Managing contacts in a communication networkInfo
- Publication number
- EP1620817A2 EP1620817A2 EP04750778A EP04750778A EP1620817A2 EP 1620817 A2 EP1620817 A2 EP 1620817A2 EP 04750778 A EP04750778 A EP 04750778A EP 04750778 A EP04750778 A EP 04750778A EP 1620817 A2 EP1620817 A2 EP 1620817A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- contact
- user
- contacts
- indication
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/18—Comparators
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/60—Aspects of automatic or semi-automatic exchanges related to security aspects in telephonic communication systems
- H04M2203/6009—Personal information, e.g. profiles or personal directories being only provided to authorised persons
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42085—Called party identification service
- H04M3/42093—Notifying the calling party of information on the called or connected party
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42085—Called party identification service
- H04M3/42102—Making use of the called party identifier
- H04M3/4211—Making use of the called party identifier where the identifier is used to access a profile
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42136—Administration or customisation of services
- H04M3/42153—Administration or customisation of services by subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42365—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
- H04M3/4931—Directory assistance systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99945—Object-oriented database structure processing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99948—Application of database or data structure, e.g. distributed, multimedia, or image
Definitions
- This disclosure relates generally to communication systems, and more particularly to managing contacts in a communication network.
- Call processing functions such as screening inbound calls and restricting outbound calls as well as other functions such as managing contact information are desirable for certain communication systems.
- Known techniques for providing such functions may use raw scripting systems or ad hoc policy representations. These known techniques, however, are typically cumbersome and inefficient. Consequently, known techniques for providing such functions may be undesirable in certain situations.
- managing contacts involves accessing a database or message fields of a signaling protocol that includes information associated with communication devices or communication services.
- Contacts associated with the user are generated in accordance with the data from the database.
- An indication is associated with each of the one or more contacts, where the indication corresponds to a processing rule specifying a condition and an action to be performed if the condition is satisfied.
- At least one contact is provided to process a communication session associated with the user in accordance with the indication of the provided contact.
- a technical advantage of one embodiment may be that a rules engine provides inbound call screening and outbound call restriction. According to the embodiment, both caller preferences and callee capabilities are provided to the rules engine, which applies rules dealing with explicit call acceptance and rejection to the caller preferences and callee capabilities.
- Another technical advantage of one embodiment may be that a user may manage a list of contacts at which the user can be reached. As particular examples, the contacts may represent communication devices, such as wireline telephones, wireless telephones, and pagers. The contacts may also represent communication services, such as an electronic mail account, an instant message service, and an auto-attendant service.
- FIGURE 1 is a block diagram illustrating an example communication system
- FIGURE 2 is a flowchart illustrating one embodiment of a method for processing an incoming call
- FIGURE 3 is a flowchart illustrating one embodiment of a method for processing an outgoing call
- FIGURE 4 is a diagram illustrating one embodiment of a display that may be uses to generate an ordered list of actions
- FIGURES 5A through 5C illustrate example contacts associated with a user in a communication system
- FIGURE 6 is a flowchart illustrating one embodiment of a method for managing contacts in a communication system
- FIGURE 7 is a flowchart illustrating one embodiment of a method for editing contacts in a communication system
- FIGURE 8 is a flowchart illustrating one embodiment of a method for controlling call redirect functions in a communication system.
- FIGURE 9 is a flowchart illustrating one embodiment of a method for presence control in a communication system. DETAILED DESCRIPTION OF THE DRAWINGS
- FIGURE 1 is a block diagram illustrating an example communication system 100.
- system 100 matches caller preferences and callee capabilities to determine one or more allowed renderings desired by a caller and supported by a callee. Rules for processing incoming and outgoing communication sessions are applied to the allowed renderings.
- System 100 also manages contacts that represent various communication devices and/or services associated with a user.
- system 100 includes endpoints 102, a call processing server 104, a database 106, and a network 108 coupled as shown in
- FIGURE 1 the term “couple” refers to any direct or indirect physical, logical, virtual, or other type of communication between two or more components, whether or not the components are in physical contact with one another.
- Other embodiments of system 100 may be used without departing from the scope of this disclosure.
- system 100 uses the Session Initiation Protocol (SIP) to establish communication sessions in system 100.
- the communication session may comprise a bi-directional session, such as a telephone call, or a uni-directional session, such as an instant message or a page.
- System 100 may be described as handling voice telephone calls to and from endpoint 102, although endpoint 102 could also transmit and or receive other types of traffic in system 100.
- endpoint 102 may transmit and receive voice traffic, facsimile traffic, data traffic, and/or other types of traffic.
- Endpoint 102 may include any hardware, software, firmware, or combination thereof for communicating with system 100.
- Endpoint 102 may, for example, comprise a wireline telephone, a wireless telephone, a pager, a computer, a personal digital assistant, or any suitable other communication device.
- Network 108 facilitates communication between components coupled to network 108.
- network 108 may communicate packets comprising voice traffic between network addresses.
- packet refers to an IP packet, a frame relay frame, an Asynchronous Transfer Mode (ATM) cell, or any other suitable segment of information.
- Network 108 may include one or more local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of a global network such as the Internet, or any other communication system or systems at one or more locations.
- Network 108 may also operate according to any appropriate type of protocol or protocols, such as Ethernet, IP, X.25, frame relay, or any other packet data protocol.
- Network 108 may further support the conveyance of non- voice packets between endpoints 102 and/or other devices in system 100.
- system 100 may include one or more external networks, such as a public switched telephone network (PSTN) 110, and one or more gateways, such as a PSTN gateway 112.
- PSTN 110 facilitates communication with and between standard telephony devices like fixed telephones 114, mobile telephones
- Gateway 112 facilitates communication between network 108 and PSTN 110. For example, gateway 112 may convert voice packets from network 108 to a format suitable for PSTN 110. Gateway 112 may also convert voice traffic from PSTN 110 to a format suitable for communication over network 108. In this way, endpoints 102 may communicate with standard telephony devices 114, 116, 117.
- FIGURE 1 illustrates the use of PSTN 110 and PSTN gateway 112, other or additional external networks and gateways could be used in system 100.
- Server 104 performs one or more functions to provide services to endpoints 102, and database 106 stores and facilitates retrieval of information used by server
- Server 104 may include any hardware, software, firmware, or combination thereof for providing services to endpoints 102.
- Database 106 may include any hardware, software, firmware, or combination thereof for storing and facilitating retrieval of information. Also, database 106 may use any of a variety of data structures, arrangements, and compilations to store and facilitate retrieval of information.
- server 104 includes at least one processor 118, at least one memory 120, a caller-callee integrator 123, a rules manager 124, a rules engine 126, a contacts manager 127, and a graphical user interface (GUI) 128, and database 106 includes rules 132, contacts 133, directory 134, and addresses of record
- the modules of server 104 may include any hardware, software, firmware, or combination thereof, and may, for example, represent one or more software routines executed by processor 118.
- caller-callee integrator 123 matches caller preferences and callee capabilities to determine one or more allowed renderings desired by the caller and supported by the callee.
- Rules 132 for incoming and outgoing communication sessions are applied to the allowed renderings.
- Rules manager 124 creates and manages rales 132, and rules engine 126 executes rules 132 on the allowed renderings to determine resulting actions.
- Contacts manager 127 manages contacts 133 that represent various communication devices and/or services associated with a user.
- Directory 134 includes a list of users of system 100, and addresses of records (AoRs) 136 records the AoRs of the users.
- Graphical user interface 128 allows server 104 to provide information to and receive information from a user.
- processor 118 executes instructions and manipulates data to perform the operations of server 104.
- FIGURE 1 illustrates a single processor 118 of server 104, multiple processors 118 may be used according to particular needs.
- Memory 120 stores and facilitates retrieval of information used by processor 118 to perform the functions of server 104, and may, for example, store instructions to be performed by processor 118 and data used by processor 118.
- Memory 120 may include any volatile or non- volatile storage and retrieval device or devices.
- Caller-callee integrator 123 matches caller preferences and callee capabilities to generate a partially ordered list of allowed renderings.
- Caller preferences describe preferences associated with a caller, for example, do not divert a call to a voice mailbox or set a call at high priority.
- Callee capabilities describe capabilities associated with a callee, for example, do not accept anonymous calls or accept calls with video.
- caller preferences and callee capabilities may each be expressed as a feature set defined using a Boolean function over an n- dimensional space.
- Each dimension of the space represents a media feature that describes facilities assumed to be available for a message to be properly rendered or otherwise presented.
- Media features may include, for example, languages, methods, or MIME types.
- a feature set includes a feature collection, represented by a single point of the n-dimensional space.
- a feature collection represents a particular rendering for an endpoint. For example, a rendering may define an instantaneous mode of operation that an endpomt may support.
- the caller preferences may be expressed as a caller feature set that includes feature collections that satisfy the requirements of the caller.
- the callee capabilities may be expressed as a callee feature set that includes feature collections that the callee supports.
- the caller preferences and the callee capabilities may be matched by determining the intersection between the caller feature set and the callee feature set.
- the intersection represents one or more renderings desired by the caller and supported by the callee. If there is more than one feature collection in the intersection, the feature collections may be ordered.
- Rules manager 124 is used to create and manage rules 132.
- rules manager 124 may receive logic defining a rule and create a new rule 132 in database 106 embodying the logic.
- Rules manager 124 may also be used to modify or delete rules, or to move a particular rule 132 up or down in the order in which server 104 evaluates rules 132.
- Rules engine 126 executes rules 132 to perform call processing functions such as screening incoming call sessions and restricting outgoing call sessions. For example, when an incoming or outgoing call is received at server 104, rules engine
- rules engine 126 identifies the user associated with the communication and the contacts 133 and the rules 132 associated with the user. Rules engine 126 then executes the identified rules 132 to determine how to handle the communication, for example, to determine where to route an incoming call or whether an outgoing call is allowable. Both caller preferences and callee capabilities may be available to rules engine 126 to allow for screening of incoming call sessions and restriction of outgoing call sessions. According to one embodiment, rules engine 126 may operate on the allowed renderings generated by caller-callee integrator 123. Rules engine 126 may be instantiated at any suitable node of system 100 such as at a contact server, a proxy server, or a domain server.
- rules 132 may specify processing of incoming and outgoing communication sessions.
- rules 132 may be used to screen incoming communication sessions and to restrict outgoing communication sessions.
- a rale 132 may specify that an incoming high-priority call causes server 104 to signal the devices represented by the retrieved contacts 133. If no one answers the call on any of the signaled devices, server 104 directs the call to an instant messaging service.
- Rules 132 may control the operation of an endpoint 102. As a particular example, a rule 132 may control whether an outgoing call from an endpoint 102 can proceed, allowing for restriction of outgoing communications. Examples of other features that rales 132 may provide for an endpoint 102 include performing an auto- answer for a callee endpoint, alerting a callee endpoint of a call, performing a device- based do-not-disturb function for a callee endpoint, and performing a user-based do- not-disturb function for a callee endpoint.
- a rale 132 may be expressed as a Boolean expression, where the primitive terms are represented by a three-tuple ⁇ variable, relational-operator, value>.
- a variable may include, for example, a header field of the SIP protocol, system-defined variables, presence and registration states, or external function calls.
- Relational operators may include, for example, mathematical operators such as "equal,” “not equal,” “greater than,” or “less than,” or string operators such as “starts with” or “contains.” Primitive terms may be combined using Boolean operators such as "and,” "or,” or “not.”
- header fields of SIP that correspond to variables may include, for example, the to and from fields. Certain header fields may correspond to a single variable, for example, accept-contact and reject-contact fields may correspond to a caller preferences variable. Additionally, some header fields may correspond to more than one variable, for example, a priority field may correspond to a priority variable and a resource priority variable.
- System-defined variables may include, for example, variables that provide the current date and time or the IP address of the host on which the instance of rules engine 126 is running.
- Rules 132 may be categorized in any suitable manner. For example, rales 132 may be organized into rale sets, which may be distinguished by the action types that correspond to the rule set. For example, the set of actions for handling incoming calls may not be the same as the set of actions for handling outgoing calls. Rule sets may include, for example, incoming call rale sets and outgoing call rale sets. Other rale sets may include, for example, subscription screening rale sets, presence information filtering rale sets, and access control rale sets.
- a rule set may have subclasses that include rales associated with a particular level of execution.
- an incoming call rule set may have subclasses including persona incoming call rale sets and contact incoming call rule sets.
- a persona level rale may be used to personalize call screening and restriction.
- a contact level rule may be used to screen calls for the specific appearance of a persona at an endpoint.
- An endpoint level rale may be used to provide default call screening for an endpoint.
- a domain level rale may be used for non-discretionary call screening on a domain-wide basis.
- non-discretionary domain rules may be executed before persona rules, which are in turn executed before non-discretionary endpoint rales, contact rales, and default endpoint and domain-level rales.
- persona rales may be executed before default rales, followed by non-discretionary domain rales.
- server 104 executes rales 132 in response to receiving a SIP request.
- a server 104 may receive a SIP Invite message representing an incoming call for a particular address of record 136. If server 104 handles the particular address of record 136, server 104 executes any user-defined rules 132 and then any discretionary default rales 132. If the server 104 is a trusted SIP proxy in the domain in which the address of record 136 is registered, server 104 executes any non-discretionary default rales 132.
- a server 104 may receive a SIP Invite message representing an outgoing call from a particular address of record
- server 104 If server 104 handles the particular address of record 136, the server 104 executes any user-defined rales 132 and then any discretionary default rules 132. If server 104 does not handle the address of record 136 but operates in the domain in which the address of record 136 is registered, the server 104 executes any non- discretionary default rules 132.
- Contacts manager 127 manages contacts 133 that represent various communication devices and/or services associated with a user.
- a contact 133 may include information about an endpoint 102, a fixed telephone 114, a mobile telephone 116, or a pager 117, or may include information about a service, such as an electronic mail account, unified messaging, or voicemail.
- Example contacts 133 are described with reference to FIGURES 5A through 5C.
- Contacts manager 127 may allow a user to manage the user's contacts 133.
- the user may modify a list of the user's contacts 133 by adding, deleting, or editing the list.
- contacts manager 127 may, for example, access a directory 134 that includes a list of other users and display the list to a user. The user selects one -of the other users, and contacts manager 127 displays the contacts 133 associated with the selected user. The user selects a contact 133, and contacts manager 127 adds the selected contact 133 to the user's contacts.
- Contacts manager 127 may be used to control forwarding of calls to a device represented by a contact 133.
- the contact 133 may represent, for example, a standard telephony device 114, 116, 117, or a Uniform Resource Locator (URL) corresponding to a communication service. If an incoming call is received, the call may be redirected to the location identified by the contact 133.
- Contacts manager 127 may be used to route a call to a device associated with a different user in system 100. When a call arrives for a first user, server 104 can route the incoming call to a second user's device as if the device belonged to the first user.
- Contacts manager 127 may be used to specify whether and how the presence status of an endpoint 102 may be disclosed to other users of system 100. For example, a list may designate users who can look at the present status of an endpoint 102 associated with a contact 133. Presence status may refer to whether a devise is "online" or "off-line", which indicates whether a device can receive service from network 108. For example, an off-line device may refer to a deactivated device that cannot receive service from network 108, while an on-line device refers to an activated device that has registered with network 108 can receive service from network 108. Unlike known techniques such as SIMPLE and LMPP that merely associate presence with contacts, contacts manager 127 integrates presence with the state of the contacts, and displays presence information via GUI 128.
- Contacts manager 127 may automatically create a contact 133 associated an endpoint 102 that has registered with server 104. Endpoint 102 may be able to identify various characteristics about itself, such as the voice coders supported by the endpoint 102 and whether that endpoint 102 is video capable. Contacts manager 127 may populate a contact 133 for the endpoint 102 with this information. As an example, some user input may be needed to generate a contact, and contacts manager 127 may prompt a user before generating the contact 133.
- contacts manager 127 may be used to manually create contacts 133 and enter information about standard telephony devices 114, 116, 117 into the new contacts 133. This may occur even when some or all of the devices are served by external networks such as PSTN 110.
- Contacts manager 127 may update a contact 133 if the status of a device or service associated with the contact 133 changes. For example, contacts manager 127 may detect if an endpoint 102 is on-line or off-line in system 100, such as when a wireless endpoint 102 roams into network 108. If this occurs, contacts manager 127 may update the contact 133 associated with the endpoint 102 to show that the endpoint 102 may now receive incoming calls. As another example, contacts manager 127 may detect if an endpoint 102 is in use or not in use and update contact 133 with that status. The presence of a communication device in system 100 can be detected, calls may be routed accordingly.
- An address of record (AOR) 136 identifies unique address information for a user of system 100.
- an address of record 136 may comprise an address in the form user@domain, where user represents the user name assigned to a user and domain represents a domain of system 100 in which the user operates.
- contacts 133 for a particular user are bound to or otherwise associated with an address of record 136 for the user.
- Graphical user interface manager 128 allows the server 104 to provide information to and receive information from a user.
- graphical user interface 128 may be used to display a list of contacts 133 or rules 132 to a user, and may be used to allow the user to add, modify, and delete contacts 133 or rules 132 of the list.
- graphical user interface 128 may be used to generate displays, such as web pages, that may be navigated by a user.
- FIGURE 1 illustrates one example of a communication system 100, various changes may be made to FIGURE 1. Modifications, additions, or omissions may be made to the system without departing " from the scope of the invention.
- the functional division of server 104 is for illustration only.
- server 104 may be divided among multiple servers or other computing devices.
- other protocols other than the SIP protocol can be supported and used in system 100.
- any type and number of external networks could be coupled to network 108, including voice and data networks.
- functions may be performed using any suitable logic comprising software, hardware, other logic, or any suitable combination of the preceding.
- FIGURE 2 is a flowchart illustrating one embodiment of a method for processing an incoming call.
- the method matches caller preferences with callee capabilities to determine allowed renderings, and then executes rales on the allowed renderings.
- the method begins at step 150, when an incoming call request from a caller endpoint to a callee endpoint is received.
- Non-discretionary domain rales are executed at step 151.
- Non-discretionary domain rales may include screening rales that result in screening actions such as rejecting calls from adult content websites.
- Caller preferences are accessed at step 152.
- Caller preferences describe preferences associated with the caller, for example, set the call at high priority or do not divert the call to a voice mailbox, and may be taken from the call request.
- Caller preferences may be expressed as a caller feature set that includes a number of feature collections, any one of which would satisfy the requirements of the caller endpoint.
- Callee capabilities are accessed at step 154.
- Callee capabilities describe capabilities associated with the callee, for example, the requirements of the callee's communication device.
- the callee capabilities may be expressed as a feature set that includes feature collections, any one of which the callee endpoint supports.
- the caller preferences are matched with the callee capabilities in order to generate a list of allowed renderings at step 156.
- the caller preferences and the callee capabilities may be matched by determining an intersection between the caller feature set and the callee feature set. The intersection may correspond to an ordered list of allowed contacts. Steps 157 through 162 describe executing the rales of rule sets on the allowed renderings until a call has been properly routed.
- the rale sets may be executed in the following order: persona-level rule set, domain-level rale set, and endpoint-level rule set.
- the rales of a rules set are executed before the actions selected by executing the rules are performed.
- a rale set is selected at step 157.
- a rale is selected from the rale set at step 158, and the rale is executed on the allowed renderings at step 160.
- the rale may remove or add a contact to the ordered list of contacts, or may permute the ordered list of contacts. If there is a next rule at step 162, the method returns to step 158 to select the next rale. If there is no next rale at step 162, the method proceeds to step 164 to perform the appropriate actions determined by executing the rules on the allowed renderings. Whether the call has been properly routed is determined at step 166. If the call has not been properly routed, the method proceeds to step 168 to determine if there is a next rale set.
- step 157 the method returns to step 157 to select the next rale set. If there is no next rale set, the method proceeds to step 170, where the call is terminated. If the call has been properly routed, the method terminates. Modifications, additions, or omissions may be made to the method without departing from the scope of the invention. For example, the method may be used with any other suitable system. Additionally, steps may be performed in any suitable order without departing from the scope of the invention.
- FIGURE 3 is a flowchart illustrating one embodiment of a method for processing an outgoing call.
- the method begins at step 350, where a caller endpoint initiates a call.
- An invite message is sent by the caller endpoint at step 352.
- a caller proxy executes rales associated with the caller endpoint at step 354.
- the rales executed by the endpoint proxy may comprise, for example, persona rules and discretionary domain rales, and may be executed on a preferences associated with caller endpoint.
- the rales for handling outgoing calls may result in an action such as an action to allow the call, to divert the call, or to redirect the call.
- step 356 a decision to allow the call is made.
- the caller preferences are added to the invite message at step 358.
- the invite message is routed to the domain proxy at step 360.
- the domain proxy executes rales on the caller preferences at step 362.
- the rules executed by the domain proxy may include, for example, non-discretionary domain rales. After executing the rales at the domain proxy, the method terminates.
- step 354 If the execution of the rules at step 354 results in an action to divert the call, the method proceeds to step 364, where a decision to divert the call is made.
- the call is forked to a service at step 366.
- the service may comprise, for example, an auto- attendant service, an operator, a messaging service, or other suitable service. After forking the call, the method terminates.
- step 354 If the execution of the rules at step 354 results in an action to redirect the call, the method proceeds to step 368, where a decision to redirect the call is made.
- the caller endpoint is informed to retry the call at step 370.
- An SIP redirect may be sent to the caller endpoint with a message to retry with a specific URL. After informing the caller, the method terminates.
- FIGURE 4 is a diagram illustrating one embodiment of a display 250 that may be used to generate an ordered list of actions.
- Display 250 includes sections that may be used to select actions of the ordered list. Sections include a try contacts section 252, a reject section 254, a divert section 256, and a forward section 258. Display
- Try contacts section 252 allows a user to select one or more contacts that are to be tried for an incoming call session and to organize the selected contacts. Try contacts section 252 includes a select element 260, a grouping element 262, a parallel element 264, and a series element 266. Select element 260 allows a user to select from a list of contacts associated with the user, which may be parallel-forked. Grouping element 262 allows a user to group the contacts, which may be parallel- forked. Parallel element 264 parallel-forks all contacts, and series element 266 series- forks all contacts.
- Reject section 254 allows a user to reject an incoming call, and includes a select element 270 and a reason element 272.
- Select element 270 allows a user to select the action to reject the call. The user may enter a reason for rejecting the call using reason element 272.
- Divert section 276 includes a select element 274 and a destination element 276.
- Select element 274 allows a user to divert an incoming call to another destination such as voicemail, electronic mail, or a pager.
- the destination may be specified using destination element 276.
- Forward section 258 allows a user to forward an incoming call, and includes a select element 278 and a destination element 280.
- Select element 278 allows a user to select the forward option. The user may specify the forward destination using destination element 280.
- the destination may include, for example, another user, another phone number, or a web address.
- FIGURES 5 A through 5C illustrate example contacts 133 a- 133c associated with a user of a communication system 100.
- contact 133a may be associated with endpoints 102 that are operable to communicate with and receive service from network 108.
- contact 133a includes a name
- Name 202 represents an alpha-numeric string or other identifier that uniquely identifies a contact 133.
- Registration information 204 identifies various characteristics about a communication device associated with the contact 133a.
- registration information 204 may include a device type 206.
- Device type 206 identifies whether the communication device represents a cellular or mobile telephone, a "soft" IP telephone or other application running on a computer, a fixed telephone, or other type of communication device.
- Video capability flag 208 identifies whether the communication device can transmit and receive video information.
- Supported coders 210 identify the voice coder or coders supported by the communication device such as one or more voice codecs.
- User interface 212 identifies the type of interface used by the communication device such as a color interface.
- registration information 204 can be supplied to server 104 by the endpoint 102 itself.
- Registration status 214 identifies whether the contact 133a represents a currently registered device or service or whether it represents a previously registered but now unused device or service.
- system 100 remembers a portion or all of the contacts 133 created for a user unless the user deletes the contacts 133.
- the user may instruct server 104 to delete contacts 133 that have not been used for a particular amount of time.
- registration status 214 acts as a flag to distinguish between devices and services currently used by the user and devices and services no longer used by the user. If an incoming communication is directed at the user, server 104 may route the communication to a device or service currently used by the user, and server 104 may ignore devices and services no longer being used.
- Redirect override 216 controls whether a redirect function of a communication device can override the control of server 104. For example, a user may forward calls directed at a communication device to another destination. A rale 132 may specify an action for the device that does not involve forwarding the call to the destination. In this case, redirect override 216 defines whether the communication device forwards the call or whether the action defined by rale 132 controls. Privacy indicator 218 controls whether another user of system 100 can use the contact 133a. For example, privacy indicator 218 may represent a flag identifying whether contact 133a is public or private. If private, no other user can select and use contact 133a. If public, any user can select and use contact 133a. In another embodiment, privacy indicator 218 represents a list of users authorized to use contact 133a. A user on the list can select and use contact 133a, while other users cannot.
- Presence status 220 identifies the status of the communication device associated with contact 133a. For example, presence status 220 may identify whether the communication device is on-line in network 108. Presence status 220 may also identify whether the communication device is being used, such as whether a telephone is on-hook or off-hook. The presence status 220 of the communication device may or may not be made available to other users in system 100. For example, a rule 132 may define which users can view the presence status 220 of contact 133a. Rule 132 could also filter the presence status 220 supplied to another user. For example, the rale 132 could dictate that another user only be able to determine whether or not the device is on-line in network 108.
- contact 133a also includes a group 222.
- a user of system 100 can group contacts 133 into one or more groups.
- the groups may include could user-defined groups and/or default groups.
- group 222 identifies the group to which contact 133a belongs.
- contacts 133 may be grouped together in other ways.
- each contact 133 may represent an object, and objects can be collected into a group without requiring an additional field in contact 133.
- the term "each" refers to each of at least a subset of the identified items.
- Contact 133a may be used for a communication device that can register with a server 104.
- the same structure may be used by a first user that selects a contact created by a second user. In that case, the contents of the contact created by the second user may be copied into a new contact 133a associated with the first user.
- the contact associated with the second user may be identified using a pointer or other mechanism without requiring a duplicate contact 133a to be created.
- contact 133b may be associated with a standard telephony device 114, 116, 117.
- contact 133b includes a name 202, an International Telecommunication Union - Telecommunication (ITU-T) E.164 number 224 or other identifier, and a group 222.
- the E.164 number 224 identifies a telephone number or other identifier associated with the standard telephony device
- Server 104 may use the E.164 number 224 to route a communication to the standard telephony device 114, 116, 117.
- Contact 133b may be used to create a contact 133b for a standard telephony device 114, 116, 117 that is unable to register itself with server 104. The same structure may be used to forward a call to a standard telephony device 114, 116, 117.
- contact 133c may be associated with a service.
- contact 133c includes a name 202, a uniform resource locator 226, and a group 222.
- URL 226 identifies a resource location associated with the service that corresponds to the contact 133c.
- URL 226 could represent an electronic mail address or any other suitable communication resource.
- Contact 133c may be used to register a service.
- FIGURES 5A through 5C illustrate examples of the contacts 133a-
- FIGURE 6 is a flowchart illustrating one embodiment of a method for editing contacts in a communi cation system.
- the method begins at step 402, where server 104 displays a list of contacts 133 to a user.
- Contacts manager 127 may retrieve the contacts 133 from database 106, and may generate one or more displays containing information about the contacts 133.
- Server 104 receives a request from the user to add a new contact 133 at step 404.
- a user may select a button or other option of the display to add a contact 133.
- Server 104 determines whether the contact to be added belongs to another user at step 406. The user selecting an option of the display may indicate that the contact 133 to be added belongs to another user.
- server 104 displays a directory of users at step 408. For example, contacts manager 127 may access directory 134 and display a list of authorized users. Server 104 receives a selection of one of the users in the display at step 410. Server 104 displays contacts 133 associated with the selected user at step 412. Before displaying contacts 133, contacts manager 127 may identify any contacts 133 associated with the selected user, and determine if any of the identified contacts 133 can be selected by the user. For example, contacts manager 127 may determine whether the privacy indicator 218 of an identified contact 133 indicates that the contact 133 is public. As another example, privacy indicator 218 of an identified contact 133 may list users authorized to select contact 133, and contacts manager 127 may determine whether the user attempting to add contact 133 is named in the list.
- Server 104 receives a selection of one of the displayed contacts 133 at step 414. Server 104 adds the selected contact to the user's list of contacts 133 at step 416. Contacts manager 127 may copy the selected contact 133 into a new contact 133 associated with the user, or may create a pointer or other indicator identifying the selected contact 133.
- server 104 adds the new contact 133 to the user's list at step 418.
- Server 104 receives a request to remove or modify an existing contact 133 in the list at step 420.
- Server 104 removes or modifies the existing contact 133 at step 422.
- Contacts manager 127 may alter the information in an existing contact 133 or delete an existing contact 133 from database 126. After removing or modifying the contact, the method terminates. Modifications, additions, or omissions may be made to the method without departing from the scope of the invention. For example, the method may be used with any other suitable system. As another example, the same method or a similar method could be used to add, modify, and delete a rule 132 in system 100.
- steps may be performed in any suitable order without departing from the scope of the invention.
- the method illustrates contacts manager 127 adding a contact 133 before modifying or removing a contact 133
- contacts manager 127 could add, modify, or delete a contact 133 in any suitable order.
- FIGURES 7 through 9 illustrate examples of methods that manage contacts as well as process a call in a communication system.
- FIGURE 7 is a flowchart illustrating one embodiment of a method for managing contacts and processing a call in a communication system. The method begins at step 302, where server 104 automatically registers one or more endpoints 102 associated with a user. For example, contacts manager 127 may identify each endpoint 102 registered in system 100 using the user's address of record 136 or the user's authentication information such as a user name or password, and may generate a contact 133a for each of the identified endpoints 102.
- Server 104 allows the user to register additional devices and/or services at step 304.
- contacts manager 127 may allow the user to register additional devices or services, and may generate contacts 133a-133c for the devices or services.
- Server 104 receives a request to establish a communication session involving the user at step 306.
- server 104 may receive a SIP Invite message to establish a communication session involving an incoming communication for the user or an outgoing communication from the user.
- Server 104 determines whether the communication session represents an incoming communication or an outgoing communication at step 308. If the communication session represents an incoming communication, server 104 retrieves one or more rales 132 at step 310.
- the rales 132 may represent user defined rales 132 and/or default rales 132 associated with incoming calls.
- Server 104 identifies one or more devices and or services to be used to handle the incoming communication at step 312.
- Rules engine 126 may execute the rales 132 to identify one or more devices to be signaled and or one or more services to be used to handle the call.
- Server 104 routes the incoming communication to the identified devices and/or services at step 314.
- Server 104 may signal one or more devices and route the call to the device that answers the call, or may route the call to an instant messaging service, an electronic mail account, an auto-attendant service, or other suitable service. After routing the call, the method terminates.
- server 104 executes one or more rales 132 at step 316.
- the rales 132 may represent user- defined rales 132 and/or default rales 132 associated with outgoing calls.
- Server 104 determines whether the outgoing communication is restricted at step 318.
- Rules engine 126 may determine whether the outgoing call is allowed or restricted by one or more rales 132. If the call is restricted, the outgoing call is rejected at step 320, and the method terminates. Otherwise, server 104 allows the call to proceed at step 322, and the method tenninates.
- FIGURE 8 is a flowchart illustrating one embodiment of a method for controlling call redirect functions in a communication system.
- Server 104 detects the presence of a user device in a network at step 502. For example, server 104 may receive a SIP Subscribe message from an endpoint 102 after the endpoint 102 initiates communication with network 108.
- Server 104 updates the contact 133 associated with the device at step 504. For example, contacts manager 127 in server 104 may update the presence status 220 in contact 133 to show that the device is present in network 108.
- Server 104 determines whether the device is set to redirect calls at step 506. For example, endpoint 102 may inform server 104 whether the call redirect feature of endpoint 102 has been activated. If the endpoint 102 is not set to redirect calls, the method terminates. If the endpoint 102 is set to redirect calls, the method proceeds to step 508. Server 104 dete ⁇ nines whether the device can override a rale 132 or other control of server 104 at step 508, by, for example, establishing whether the redirect override flag 216 of contact 133 allows the device to override the control of server
- server 104 If the device can override the control of server 104, server 104 allows the device to forward calls at step 510, and the method terminates. Otherwise, server 104 ignores the redirect function of the device at step 512. For example, server 104 could execute rales 132 to identify where to route the call. After ignoring the redirect function, the method terminates.
- server 104 may allow the user to determine whether or not to allow the device to override the control of server 104. Additionally, steps may be performed in any suitable order without departing from the scope of the invention.
- FIGURE 9 is a flowchart illustrating one embodiment of a method for presence control in a communication system.
- Server 104 detects the presence of a user device in a network at step 602. For example, server 104 may receive a SIP Subscribe message from an endpoint 102 after the endpoint 102 initiates communication with network 108.
- Server 104 identifies a list associated with the user at step 604. For example, server 104 may identify a rale 132 associated with the user, where the rale 132 identifies a list of one or more users.
- Server 104 allows the users of the list to see the status of the device at step 606, by, for example, allowing users of the list to access the presence status 220 of the user.
- Server 104 may also execute one or more rales 132 to filter the presence status 220 of the user. After allowing users to see the status, the method terminates. Modifications, additions, or omissions may be made to the method without departing from the scope of the invention. For example, the method may be used with any other suitable system. As another example, the same method or similar method could occur when the device leaves the network 108 or when any status of the device changes. Additionally, steps may be performed in any suitable order without departing from the scope of the invention.
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/430,062 US7533126B2 (en) | 2003-05-05 | 2003-05-05 | Managing contacts in a communication network |
PCT/US2004/013028 WO2004100428A2 (en) | 2003-05-05 | 2004-04-27 | Managing contacts in a communication network |
Publications (3)
Publication Number | Publication Date |
---|---|
EP1620817A2 true EP1620817A2 (en) | 2006-02-01 |
EP1620817A4 EP1620817A4 (en) | 2011-10-26 |
EP1620817B1 EP1620817B1 (en) | 2014-07-30 |
Family
ID=33416171
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP04750778.5A Expired - Lifetime EP1620817B1 (en) | 2003-05-05 | 2004-04-27 | Managing contacts in a communication network |
Country Status (6)
Country | Link |
---|---|
US (1) | US7533126B2 (en) |
EP (1) | EP1620817B1 (en) |
CN (1) | CN100445992C (en) |
AU (1) | AU2004237682A1 (en) |
CA (1) | CA2520507A1 (en) |
WO (1) | WO2004100428A2 (en) |
Families Citing this family (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7991843B2 (en) * | 2003-10-29 | 2011-08-02 | Nokia Corporation | System, method and computer program product for managing user identities |
US20050114514A1 (en) * | 2003-11-21 | 2005-05-26 | Bostrom Kevin L. | Advising a network component for control of communication session connection through employment of one or more communication session restrictions |
US7522712B2 (en) * | 2004-01-29 | 2009-04-21 | Comverse Ltd. | Method for initiating a session in a store and forward messaging system |
US20060223568A1 (en) * | 2005-03-30 | 2006-10-05 | Harris John M | System and method for initiating and conducting polite communications |
KR100815665B1 (en) | 2005-03-30 | 2008-03-20 | 모토로라 인코포레이티드 | System and method for initiating and conducting polite communications |
CN103763684B (en) * | 2005-04-04 | 2018-04-13 | 艾利森电话股份有限公司 | Answer-mode in key call mobile communication service |
WO2006124325A1 (en) | 2005-05-16 | 2006-11-23 | Cisco Technology, Inc. | Management network access for network users |
US8190568B2 (en) * | 2005-05-20 | 2012-05-29 | Cisco Technology, Inc. | System and method for providing interactive communications |
US8537997B2 (en) | 2005-07-27 | 2013-09-17 | Cisco Technology, Inc. | RFID for available resources not connected to the network |
US8438235B2 (en) * | 2005-08-25 | 2013-05-07 | Cisco Technology, Inc. | Techniques for integrating instant messaging with telephonic communication |
CN100413249C (en) * | 2005-11-19 | 2008-08-20 | 腾讯科技(深圳)有限公司 | Contact management method |
KR100663477B1 (en) * | 2005-12-23 | 2007-01-02 | 삼성전자주식회사 | Apparatus and method for providing receiving/sending information |
US8391165B2 (en) * | 2005-12-30 | 2013-03-05 | Motorola Mobility Llc | Method and apparatus for identifying caller preferences matched to callee capabilities for IMS communications |
US7917523B2 (en) | 2006-04-05 | 2011-03-29 | Cisco Technology, Inc. | Method and system for providing improved URL mangling performance using fast re-write |
US8255464B2 (en) * | 2006-05-09 | 2012-08-28 | Wilkins John T | Contact management system and method |
US9294520B2 (en) * | 2006-08-02 | 2016-03-22 | Cisco Technology, Inc. | Entitlement for call routing and denial |
JP2008109223A (en) * | 2006-10-23 | 2008-05-08 | Fujitsu Ltd | Portable terminal device, request transmission and reception control method, and request transmission and reception control program |
FR2912519A1 (en) | 2007-02-08 | 2008-08-15 | Alcatel Lucent Sas | METHODS OF MANAGING AND ALLOCATING RESOURCES |
US8156098B1 (en) | 2007-04-29 | 2012-04-10 | Aol Inc. | Generating and implementing A-lists to manage user relationships |
CN101325487B (en) * | 2007-06-15 | 2011-11-30 | 中兴通讯股份有限公司 | Method for limiting display of subscriber number in conference business notification message |
US8301699B1 (en) | 2008-10-29 | 2012-10-30 | Cisco Technology, Inc. | Dynamically enabling features of an application based on user status |
JP5458110B2 (en) * | 2009-01-20 | 2014-04-02 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Processing communication session invitations |
US9392110B2 (en) * | 2009-09-17 | 2016-07-12 | Motorola Solutions, Inc. | Facilitating interoperability among communication systems via inter- and intra-agency communications using a shared network |
US9397861B1 (en) | 2010-07-16 | 2016-07-19 | Shoretel, Inc. | Unified communication |
US9455946B1 (en) * | 2010-07-16 | 2016-09-27 | Shoretel, Inc. | Server for providing unified communications |
CN102655484B (en) * | 2012-04-16 | 2017-05-24 | 上海量明科技发展有限公司 | Method for adding contact persons by email, client side and system |
EP2663048B1 (en) | 2012-05-11 | 2015-07-08 | Telefonaktiebolaget L M Ericsson (publ) | Method and user terminal for supporting provision of capabilities |
US20170103231A1 (en) * | 2013-07-20 | 2017-04-13 | Keith Lipman | System and method for distributed, policy-based confidentiality management |
US20150026760A1 (en) * | 2013-07-20 | 2015-01-22 | Keith Lipman | System and Method for Policy-Based Confidentiality Management |
US9628400B2 (en) | 2013-07-24 | 2017-04-18 | Cisco Technology, Inc. | Interest forwarding for interactive client anonymity |
CN103927393A (en) * | 2014-04-30 | 2014-07-16 | 张家栋 | Method and system for achieving automatic confirmation of nicknames based on different social situations |
GB2528479A (en) * | 2014-07-23 | 2016-01-27 | Gamma Telecom Ltd | Session handling in a communications network |
US20170061444A1 (en) * | 2015-08-25 | 2017-03-02 | Schneider Electric Usa Inc. | Analysis engine that correlates business operations with facility energy use |
CN107592403A (en) * | 2016-07-07 | 2018-01-16 | 中兴通讯股份有限公司 | A kind of multiple users method for processing business and device |
US11470195B2 (en) * | 2019-11-21 | 2022-10-11 | Avaya Inc. | Configurable auto-answer for incoming communication requests |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001045342A2 (en) * | 1999-12-14 | 2001-06-21 | Nortel Networks Limited | Presence management system |
US20020073207A1 (en) * | 2000-09-28 | 2002-06-13 | Ian Widger | Communication management system for managing multiple incoming communications, such as from one graphical user interface |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5841854A (en) * | 1994-02-16 | 1998-11-24 | Priority Call Management, Inc. | Wireless telephone integration system and method for call centers and workgroups |
US5862208A (en) | 1994-02-16 | 1999-01-19 | Priority Call Management, Inc. | Method and system for enabling a party to change terminals during a call |
US5652789A (en) | 1994-09-30 | 1997-07-29 | Wildfire Communications, Inc. | Network based knowledgeable assistant |
KR19990067327A (en) * | 1995-11-02 | 1999-08-16 | 내쉬 로저 윌리엄 | Equipment for creating services for telecommunication networks |
US5778053A (en) * | 1995-12-21 | 1998-07-07 | Intel Corporation | Answering machine services for data conferences |
EP0885516A1 (en) * | 1996-12-06 | 1998-12-23 | AT & T Corp. | Intelligent call redirection |
US6021181A (en) | 1997-02-24 | 2000-02-01 | Wildfire Communications, Inc. | Electronic voice mail message handling system |
US6311186B1 (en) * | 1998-02-20 | 2001-10-30 | Priority Call Management, Inc. | Telecommunications switching system utilizing a channelized database access mechanism |
US6263060B1 (en) | 1998-08-18 | 2001-07-17 | Priority Call Management, Inc. | Transportable logic to facilitate a large calling card transaction network supporting dynamic changes |
US6564261B1 (en) * | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US6917947B2 (en) * | 2001-06-21 | 2005-07-12 | Kevin Wade Jameson | Collection command applicator |
-
2003
- 2003-05-05 US US10/430,062 patent/US7533126B2/en not_active Expired - Lifetime
-
2004
- 2004-04-27 CN CNB200480010190XA patent/CN100445992C/en not_active Expired - Fee Related
- 2004-04-27 AU AU2004237682A patent/AU2004237682A1/en not_active Abandoned
- 2004-04-27 EP EP04750778.5A patent/EP1620817B1/en not_active Expired - Lifetime
- 2004-04-27 WO PCT/US2004/013028 patent/WO2004100428A2/en active Application Filing
- 2004-04-27 CA CA002520507A patent/CA2520507A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001045342A2 (en) * | 1999-12-14 | 2001-06-21 | Nortel Networks Limited | Presence management system |
US20020073207A1 (en) * | 2000-09-28 | 2002-06-13 | Ian Widger | Communication management system for managing multiple incoming communications, such as from one graphical user interface |
Non-Patent Citations (1)
Title |
---|
See also references of WO2004100428A2 * |
Also Published As
Publication number | Publication date |
---|---|
US7533126B2 (en) | 2009-05-12 |
EP1620817A4 (en) | 2011-10-26 |
US20040225679A1 (en) | 2004-11-11 |
CN1846208A (en) | 2006-10-11 |
EP1620817B1 (en) | 2014-07-30 |
CA2520507A1 (en) | 2004-11-18 |
AU2004237682A1 (en) | 2004-11-18 |
WO2004100428A3 (en) | 2005-11-10 |
WO2004100428A2 (en) | 2004-11-18 |
CN100445992C (en) | 2008-12-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1620817B1 (en) | Managing contacts in a communication network | |
US10218606B2 (en) | Producing routing messages for voice over IP communications | |
US7970388B2 (en) | Methods and apparatus for providing multiple communications services with unified parental notification and/or control features | |
EP1263244B1 (en) | Call party profile presentation service in a multimedia network | |
US8681959B2 (en) | Method and system for customized caller identification | |
US7945253B2 (en) | Method, system, and storage medium for providing comprehensive originator identification services | |
US9462118B2 (en) | VoIP communication content control | |
KR101352647B1 (en) | Pluggable contact resolution | |
US7050861B1 (en) | Controlling a destination terminal from an originating terminal | |
US7433455B1 (en) | Processing a communication session using a rules engine | |
EP1695573A1 (en) | Control decisions in a communication system | |
US20020186828A1 (en) | Context driven alternate point of contact service | |
US20060025113A1 (en) | Methods, systems, and storage mediums for providing message delivery and notification services | |
KR20100074237A (en) | Accommodation of two independent telephony systems | |
US8488768B2 (en) | System and method of providing a single service destination in a telecommunications network | |
US20040170267A1 (en) | Authorization-based forwarding | |
JP4441288B2 (en) | Subscriber mobility in telephone systems. | |
WO2003036504A1 (en) | Application server domains | |
EP1111875B1 (en) | Controlling a destination terminal from an originating terminal | |
KR101369583B1 (en) | Voip client information | |
US7100107B2 (en) | Method of changing service attributes in a service logic execution environment | |
CN114679516A (en) | Method for realizing video color ring for mobile phone small number | |
SE518175C3 (en) | Server and method for providing information to a subscriber's terminal | |
Wang | Building value-added services using mobile agents in SIP based internet telephony |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20051025 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL HR LT LV MK |
|
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20110922 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04M 3/436 20060101AFI20110916BHEP Ipc: H04L 29/08 20060101ALI20110916BHEP |
|
17Q | First examination report despatched |
Effective date: 20130416 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602004045552 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: G06F0017300000 Ipc: H04L0029080000 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04M 3/42 20060101ALI20140124BHEP Ipc: H04L 29/08 20060101AFI20140124BHEP Ipc: H04M 3/493 20060101ALI20140124BHEP Ipc: H04M 3/436 20060101ALI20140124BHEP |
|
INTG | Intention to grant announced |
Effective date: 20140220 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 680427 Country of ref document: AT Kind code of ref document: T Effective date: 20140815 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602004045552 Country of ref document: DE Effective date: 20140911 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 680427 Country of ref document: AT Kind code of ref document: T Effective date: 20140730 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20140730 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20141202 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20141030 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20141031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 12 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602004045552 Country of ref document: DE |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20150504 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 Ref country code: LU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20150427 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150430 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150430 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 13 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150427 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 14 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20040427 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140730 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20200427 Year of fee payment: 17 Ref country code: DE Payment date: 20200429 Year of fee payment: 17 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20200427 Year of fee payment: 17 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602004045552 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602004045552 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0029080000 Ipc: H04L0065000000 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20210427 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211103 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210430 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210427 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230525 |