US7787602B2

Methods and apparatus to provide a telephone system configuration interface

Summary by NHIP

Telephone Service Configuration

The method allows a subscriber to configure telephone service for multiple users at a single location containing telephones, numbers, and a shared voicemail box. The system visually provides options to assign numbers to telephones, grant exclusive number access via unique account identifiers, and control voicemail access permissions for each user.

Claim Score by NHIP

Read claim 27, the broadest

Abstract

Methods and apparatus for a telephone customer to configure telephone service for multiple users at a single location associated with the customer. The location has at least two telephones, at least two phone numbers and a voice mail box. The telephone customer is visually provided an option to assign one of the phone numbers to one of the telephones. The telephone customer is visually provided an option to assign each of the multiple users exclusive access to at least one of the telephone numbers via their account identifier. The telephone customer is visually provided the option to, for each of the multiple users, allow access or deny access via their account identifier to the voicemail box.

US7787602B2, drawing sheet 1 — Sheet 1 of 11

Term

Projected expiry 6 May 2029.

33 claims: 4 independent, 29 dependent

1
A method for providing a telephone related service allowing a telephone subscriber to configure telephone service for multiple users at a single location associated with the telephone subscriber, the single location having a plurality of telephones, a plurality of phone numbers and a shared voicemail box, the multiple users each having a unique account identifier, the method comprising:visually providing the telephone subscriber an option to specify one of the phone numbers to one of the telephones;and visually providing the telephone subscriber an option to assign each of the multiple users exclusive access to at least one of the telephone numbers via their account identifier.
18
A graphical user interface to allow a telephone subscriber to configure a telephone system with multiple users for a single location associated with the telephone subscriber, the single location having at least a plurality of telephones, a plurality of phone numbers and a shared voicemail box comprising:a number assignment control graphic to assign one of the phone numbers to at least one of the multiple users;a user assignment control graphic to assign one of the multiple users exclusive access to at least one of the telephones;and a voicemail assignment control graphic to allow access or deny access to the voicemail box for each of the multiple users.
27
Broadest claimClaim Score 72, broad(NHIP)A method for a telephone customer to configure voicemail box service for multiple users, each having an account identifier, at a single location associated with the telephone customer, the location having at least one telephone and at least two voicemail boxes, the method comprising:visually providing the telephone customer an option to select one of the at least two voicemail boxes;and visually providing the telephone customer an option to allow access or deny access to the selected one of the at least two voicemail boxes for each of the selected one of the multiple users based on their account identifier.
28
A tangible article of manufacture storing machine readable instructions which, when executed, cause a machine to:read a telephone customer account relating to a location having at least two telephones each having a phone number and a voicemail box;visually provide a telephone customer associated with the telephone customer account an option to assign exclusive access for one of a multiple number of users, each of the multiple number of users having an individual account identifier, to a phone number from the at least two phone numbers;and visually provide the telephone customer an option to allow access or deny access to the voicemail box for each of the multiple number of users via their individual account identifier.

Independent claims4

49 paragraphs in 4 sections, as filed

FIELD OF THE DISCLOSURE

This disclosure relates generally to telephone systems, and, more particularly, to methods and apparatus to provide a telephone system configuration interface.

BACKGROUND

As the sophistication of phone service has increased, consumers, such as subscribers/users, have the ability to install multiple phones in a residence or small business. Such phones may be land line telephones (i.e., telephones that are hardwired to a telephone network) or may be mobile telephones (e.g., cellular telephones or the like). Additionally, these phones may have multiple shared phone numbers associated with individual phones or each phone may have its own separate private phone number. Further, services such as voicemail boxes may be associated with an individual private phone or shared phones.

The numerous combinations of telephones, telephone numbers, and services must be initially configured to insure that all phone, phone number, and services (e.g., voicemail box options) are properly associated with one another. Furthermore, as the needs of subscribers/users change, the telephones, telephone numbers, and services may need to be reconfigured. In terms of initial configuration, a Consumer Voice over Internet Protocol (CVoIP) product, which routes consumer telephone calls over Internet Protocol (IP) networks requires set up including mapping customer Single Sign-On (SSO) within a household to telephones and voicemail boxes. One challenge is to automate the configuration processes and/or the reconfiguration processes, while at the same time obeying the business rules for CVoIP and voicemail.

Currently, the set up of telephone service, voicemail boxes, etc. for different users in the same household requires expertise from the service provider. This service is costly in terms of resources and creates antagonism by a customer if the service is inadequate or untimely. Further, such service may require information from a customer thereby inconveniencing the customer who must be present when service is initiated. Customers may set up the voicemail and telephone services, but currently customers cannot set up voicemail and telephone services specific to a particular user in a household for whom it is desired to have different services or access to different voicemail boxes. That is, consumer (i.e., home) telephone services provide only a single level of access during which full system access is allowed. For example, a consumer telephone service conventionally includes only a single login that provides any person logging in with the ability to configure or reconfigure systems and/or services. Such a full access-type configuration prevents segmentation between users of a particular consumer system. Thus, users either have complete and total control over the system or no control whatsoever.

BRIEF DESCRIPTION OF DRAWINGS

<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of an example broadband service network system.

<figref idrefs="DRAWINGS">FIG. 2A</figref> is a block diagram of an example customer premises in the example broadband service network system of <figref idrefs="DRAWINGS">FIG. 1</figref> with the initial installation of example VoIP telephones.

<figref idrefs="DRAWINGS">FIG. 2B</figref> is a block diagram of the example customer premises in <figref idrefs="DRAWINGS">FIG. 2A</figref> after an example configuration entered by a customer using an example customer premises telephone system set up interface.

<figref idrefs="DRAWINGS">FIG. 3</figref> is a screen shot of the first screen of the example customer premises telephone system set up interface.

<figref idrefs="DRAWINGS">FIG. 4</figref> is a screen shot of an example interface screen for selecting users in the customer premises telephone system set up interface.

<figref idrefs="DRAWINGS">FIGS. 5A-5C</figref> are screen shots of example interface screens for assigning phones to users as shared or private phones in the customer premises telephone system set up interface.

<figref idrefs="DRAWINGS">FIGS. 6A-6C</figref> are screen shots of example interfaces that allow a user to record a voicemail greeting in the customer premises telephone system set up interface.

<figref idrefs="DRAWINGS">FIG. 7</figref> is a block diagram illustrating an example apparatus to implement the configuration entered by a customer using the example customer premises telephone system set up interface.

<figref idrefs="DRAWINGS">FIGS. 8A-8B</figref> are flow diagrams of an example process followed by certain components of the telephone system such as the example apparatus of <figref idrefs="DRAWINGS">FIG. 7</figref> to implement the configuration entered by a customer using the example customer premises telephone system set up interface.

<figref idrefs="DRAWINGS">FIG. 9</figref> is an example processor which may be used to implement the example interfaces in <figref idrefs="DRAWINGS">FIGS. 3-6</figref> and/or the implementation of the configurations in <figref idrefs="DRAWINGS">FIG. 8</figref>.

DETAILED DESCRIPTION

In general, example methods and apparatus for a telephone system set up interface are disclosed. In one example, a method for providing a telephone related service allowing a telephone subscriber to configure telephone service for multiple users at a single location associated with the telephone subscriber, the single location having a plurality of telephones, a plurality of phone numbers and a shared voicemail box, the multiple users each having a unique account identifier, includes visually providing the telephone subscriber an option to specify one of the phone numbers to one of the telephones; and visually providing the telephone subscriber an option to assign each of the multiple users exclusive access to at least one of the telephone numbers via their account identifier.

<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of an example broadband service network system 10. The broadband service network system 10 allows for the service and operation of multiple communication devices such as a cellular telephone 12 and a Voice over Internet Protocol (VoIP) phone 14, each belonging to a customer or multiple customers. The telephones 12 and 14 are merely for example purposes, and it is to be understood that the cellular phone 12 may be any wireless device such as a cell phone or personal digital assistant (PDA) and the VoIP phone 14 may be any VoIP device such as a sound card or other hardware used in conjunction with a personal computer, a universal serial bus (USB) phone or a Bluetooth wireless phone. It is to be understood by those of ordinary skill in the art that each phone 12 and 14 may represent multiple devices of the same general configuration used by many other customers. The VoIP phone 14 and other devices such as VoIP phones 16, 18 and 20 are located in a customer premises 22. The VoIP phones 14, 16, 18 and 20 each have different assigned phone numbers in this example. It is to be understood, that any number of different phones or other IP based or other communications devices may be installed in the customer premises 22. Alternatively, the customer premises 22 may have a single phone.

The cellular telephone 12 receives signals from and sends signals to a wireless network 32, while the VoIP phones 14, 16, 18 and 20 send to and receive IP signals from a VoIP network 34. In this example, both the wireless network 32 and the VoIP network 34 are coupled to an IP multi-media subsystem (IMS) core 36. The IMS is an open, standardized, operator friendly, Next Generation Networking (NGN) multi-media architecture for mobile and fixed IP services. The IMS in this example is a VoIP implementation based on a third generation partnership project (3GPP) variant of session initiation protocol (SIP), and runs over the standard Internet protocol (IP). It may be used by telecommunications operators in NGN networks that combine voice and data in a single packet switched network, to offer network controlled multi-media services. The IMS core 36 is designed to provide Internet services for all customers of the IMS core 36 on different devices such as the VoIP phone 14 in <figref idrefs="DRAWINGS">FIG. 1</figref>. The example IMS core 36 uses open standard IP protocols allowing the merger of the Internet with cellular systems, using cellular technologies to provide ubiquitous access and Internet technologies to provide other services.

In this example, the IMS core 36 has an Application Programming Interface (API), which is an open service access (OSA)/gateway (GW) 38, providing an interface for different programs exchanging data. For example the OSA/GW 38 can support telephone protocols (e.g., Parlay) or a multimedia communication protocol (e.g., session initiation protocol (SIP)). Those of ordinary skill in the art will appreciate that different cores may be used for the wireless network 32 and the VoIP network 34.

The example IMS core 36 of <figref idrefs="DRAWINGS">FIG. 1</figref> includes a call server 40 and a call manager 42. The call server 40 represents different SIP servers or proxies that are collectively termed CSCF (Call Server Control Function). CSCF elements are used to process SIP signaling packets within the IMS core 36 from the VoIP phones such as the VoIP phones 14, 16, 18 and 20 and perform session control. The call manager 42 provides a web services interface to external applications which are used to set profile information and configure customer phones.

The IMS core 36 is in communication with a mediation database server 44 which stores identification and customer account information used by the IMS core 36. The mediation database server 44 is the master user information database supporting the IMS network elements involved in call processing and sessions. The mediation database server 44 contains profile information, manages user authentication and authorization, and physical SIP endpoint location information. The profile information includes customer account information such as the identity and number of phone users, telephone numbers and voicemail boxes associated with a customer account.

The call manager 42 of the IMS core 36 is coupled via web communication protocols such as hypertext transfer protocol (http) and/or hypertext transfer protocol security (https) to the world wide web 50. The IMS core 36 may draw customer instructions from various portals such as a VoIP service provider portal 52, a wireless service provider portal 54 and an Internet content provider portal 56. Of course, other portals may be provided that allow customers to reset their options for the various services. Different customers may access the portals 52, 54 and 56 via web browser devices such as a personal computer 58. Of course, other web browser capable devices such as cell phones, PDAs, etc. may be used to access the portals 52, 54 and 56.

The mediation database server 44 also communicates with portals such as portals 52, 54 and 56 to send and receive customer information to and from the portals. The mediation database server 44 communicates with an Internet based multi-media support network 60 with a network management system (NMS) and an operational support system (OSS) to support functions such as billing, network management, repairs and servicing. In this example, the network management system is the SBC Lightspeed network, but other network management systems may be used for supporting Internet based multi-media services.

<figref idrefs="DRAWINGS">FIG. 2A</figref> is a block diagram of an example household such as the customer premises 22 in <figref idrefs="DRAWINGS">FIG. 1</figref> after the initial installation of the VoIP phones 14, 16, 18 and 20. In this example, each of the phones 14, 16, 18 and 20 has a separate phone number. Each of the phones 14, 16, 18 and 20 allows access to a common voicemail box 62. Each of the phone numbers is associated with separate users 64, 66, 68 and 70 respectively. The users 64, 66, 68 and 70 are each associated with a customer account with separate identification information such as a user ID stored in the mediation database 42. One user, such as the user 64, is responsible for the customer account (i.e., receives the bills) and thus is authorized to request service changes and configurations for any of the phones 14, 16, 18 and 20 and any of the users 64, 66, 68 and 70. The users 64, 66, 68 and 70 may have access to different telephones such as the phones 14, 16, 18 and 20, different telephone numbers and different voicemail boxes via their customer identification information. Further each of the users 64, 66, 68 and 70 may be granted the ability to change and/or access different telephone features including, for example, long distance service, 1-900 numbers, ringtones, call forwarding and conference calling.

At the initial installation, all features relating to the VoIP phones 14, 16, 18 and 20 are associated with the user 64 for the customer premises 22 and are equally accessible to all of the users 66, 68 and 70 who are associated with the customer account.

As will be described below, a customer such as the user 64 in the example customer premises 22 may use a set up interface to configure the VoIP phones 14, 16, 18 and 20 as well as the voicemail box 62 and set up separate voicemail boxes for each of the persons 64, 66, 68 and 70. The set up interface allows many different configurations of phone numbers, private and public phones, voicemail boxes and greetings and other services to set up the use of the phones 14, 16, 18 and 20 on the customer premises 22 and the access by each of the persons 64, 66, 68 and 70 according to their individual user IDs. The set up interface may also allow the user 64 to grant, deny and/or restrict access to other telephone features and services for each of the other users 66, 68 and 70. Depending on the access granted, each of the other users 66, 68 and 70 may individually configure phone service for their particular identification information. For example, if the user 66 is allowed access to change a voicemail box greeting, the user 66 may change the greeting by providing the proper identification information. The configurations are set via the interface which is available on a web browser device such as the computer 58 in <figref idrefs="DRAWINGS">FIG. 1</figref> by accessing a portal such as the VoIP service provider portal 52 and are storing the configurations in the mediation database 44 for implementation by the IMS core 36.

<figref idrefs="DRAWINGS">FIG. 2B</figref> is a block diagram of the example customer premises 22 after one example set up of the phones 14, 16, 18 and 20 has been performed by the head of the household such as the person 64. In this example, the phones 14, 16, 18 and 20 have been configured to access different voicemail boxes and to be shared among different people. The new configuration shown in <figref idrefs="DRAWINGS">FIG. 2B</figref> allows the person 64 to share access to the phone 14 with the person 66. The common voicemail box 62 has been configured to be accessible from the phone 14 for the persons 64 and 66. A new secondary voicemail box 72 has been set up. The person 66 now has access to the phone 14 as well as private access to the phone 16. Both the phone 14 and phone 16 have been configured to allow access to the secondary voicemail box 72 for use by the person 66.

The person 68 has private access to the phone 18 and private access to a new configured common voicemail box 74. The phone 20 has been configured to allow the person 68 and the person 70 to have access to the phone 20. The phone 20 has been configured to allow access to the common voicemail box 72 for the person 70. The phone 20 allows access to a new secondary voicemail box 76 for the person 70. Further, different phone services may be enabled for the phones 14, 16, 18 and 20 which are accessible to the different users 64, 66, 68 and 70 on supplying their account information.

<figref idrefs="DRAWINGS">FIG. 3</figref> is a screen shot of an example of a customer interface 200 generated by the example VoIP service provider portal 52 and displayed for a customer on a web browser enabled device such as the example personal computer 58 in <figref idrefs="DRAWINGS">FIG. 1</figref>. The personal computer 58 in <figref idrefs="DRAWINGS">FIG. 1</figref> may be located in the customer premises 22 in <figref idrefs="DRAWINGS">FIG. 1</figref> or may be off site. The customer interface 200 is accessible by a customer who is responsible for the customer account such as the person 64 in <figref idrefs="DRAWINGS">FIG. 2A</figref> via entry of a user identification and password or other security verification. The user interface 200 allows the customer to configure the telephones and services at the customer premises 22 via commands to the IMS core 36 to control access to phones and/or voicemail boxes which are associated with the customer account. It is to be understood that other adjustments and information such as service requests, billing, quality of service reporting, etc. may be made via the VoIP service provider portal 52 on the customer interface 200 or similar interfaces.

The customer interface 200 is a graphical user interface that includes a main menu options area 202 containing different options for other customer services and/or display of customer account information. The user interface 200 includes a user selection window 210. The user selection window 210 includes a name column 212 and an account identifier column 214. The name column 212 lists the names of the users (persons 64, 66, 68 and 70) in the customer premises 22 and the account identifier column 214 lists an account identifier such as an e-mail address associated with each person. The interface 200 obtains the user names and account identifiers from the database server 44 via the portal 52. The name column 208 initially lists the names of the user who is responsible for the customer account and a series of blank name fields 216. The user may enter the name or names of additional users, for example members of the household in the customer premises 22 in the fields blank 216. These names and their associated account identifiers will be displayed in the account identifier column 214. A check box 218 allows the customer to select the user name(s) of the user(s) who will use the telephones and have access to a voicemail box. The initial set up window area 204 also includes a next button 220, a cancel button 222 and a reset button 224 to navigate throughout the different windows which will be detailed below. Selecting the next button 220 will cause the customer interface 200 to display the next configuration window such as a phone number set up window 250 in <figref idrefs="DRAWINGS">FIG. 4</figref>. Selecting the cancel button 222 will cause the entered information in the window to be erased. Selecting the reset button 224 will cause the fields to revert to the previous setting. A complete later button 226 allows the customer to complete the configuration at a later point in time.

<figref idrefs="DRAWINGS">FIG. 4</figref> shows an example phone number set up window 250 that is displayed in the customer interface 200 after the names of the users are entered in the user selection window 210 in <figref idrefs="DRAWINGS">FIG. 3</figref>. The user interface 200 also includes a previous button 228 which, when selected, returns to the previous configuration window (user selection window 210 in this example). The phone number set up window 250 includes an instruction area 254 including instructions to the user and/or information regarding the phone numbers that are associated with the account. The information regarding the phone numbers and phones is taken from the database server 44. In this example, the instruction area 254 indicates there are four phones and associated numbers with the customer account. A telephone number column 256 lists the phone numbers that are associated with the account. The listing of telephone numbers may be telephone numbers associated with household telephones (e.g., landline telephones), VoIP telephones, and/or mobile telephones. Each of the listed phone numbers has a shared button 258 and a private phone button 260. By selecting the shared button 258 for the each of the listed phone numbers, the customer may designate the phone associated with the phone number in the telephone number column 256 as associated with multiple users. By selecting the private phone button 260 for each of the listed phone numbers, the customer may designate the phone associated with the phone number in the telephone number column 256 as associated with a single user. Each telephone number also has an associated text field 262 which may be filled in by the customer to identify or describe each phone number. For example, a phone number may be described by the location of the associated phone.

If the user selects any phone number which will be a shared number, a series of configuration windows are displayed as shown in <figref idrefs="DRAWINGS">FIGS. 5A-5C</figref> by the customer interface 200. <figref idrefs="DRAWINGS">FIG. 5A</figref> shows a sharing configuration window 280 which includes an all share option 282 and an assignment option 284. The all share option 282 configures all the shared numbers to all users in the household. Selecting the assignment option 284 results in the display of a user sharing configuration window 300 as shown in <figref idrefs="DRAWINGS">FIG. 5B</figref> in the customer interface 200.

The user sharing configuration window 300 in <figref idrefs="DRAWINGS">FIG. 5B</figref> includes a main number user list field 302, a second number user list field 304 and a third number user list field 306. Initially, the main number user list field 302 has a list of all the users associated with the customer account. The user list field 302 and the user list field 304 are each associated with a phone number which the user had previously designated as shared in the phone number set up window 250 in <figref idrefs="DRAWINGS">FIG. 4</figref>. The user list field 306 is associated with the phone numbers which the user had previously designated as private in the phone number set up window 250. By using a move button 308, the user may assign a particular user to a particular list field such as the user list field 304 and thereby give that user sharing privileges to that phone. The user list field 306 lists users which will be assigned a private phone.

<figref idrefs="DRAWINGS">FIG. 5C</figref> shows a private phone set up window 330 in the customer interface 200. The private phone set up window 330 has a private phone column 332 listing all the phones that were designated as private in the phone set up window 250 in <figref idrefs="DRAWINGS">FIG. 4</figref>. The private phone set up window 330 includes a telephone number column 334 which lists the respective phone numbers next to the phones in the private phone column 332. A user pull down menu field 336 is located next to each of the phone numbers in the telephone number column 334. The user pull down menu 336 includes each user name in the customer premises 22 which was designated as a private phone user in the user sharing configuration window 300 in <figref idrefs="DRAWINGS">FIG. 5B</figref>. The customer selects the user name to be associated with the listed private phone from the user pull down menu 336.

<figref idrefs="DRAWINGS">FIG. 6A</figref> shows an example general voicemail box set up window 350 which is displayed by the user interface 200 after the initial names of users are entered. The voicemail set up window 350 includes an instruction area 352 which includes instructions on setting up a voicemail message and the identification of the phone number to which the voicemail box is being assigned. A name column 354 lists the names of the users entered in the phone number set up window 350 in <figref idrefs="DRAWINGS">FIG. 4</figref> above. The first name is the user who is responsible for the customer account and assigned to the first voicemail box. Each following name includes an associated pull down menu 356 which includes the mail box numbers available. The customer assigns a mailbox number to the names by selecting the mail box number in the pull down menu 356.

<figref idrefs="DRAWINGS">FIG. 6B</figref> shows an example voicemail identification set up window 380 which is displayed by the customer interface 200 after the mailboxes are assigned in the voicemail box general set up window 350 in <figref idrefs="DRAWINGS">FIG. 6A</figref>. The voicemail identification set up window 380 includes an information area 382 which indicates the phone number of the voicemail box which is being set up. The window 380 includes a name column 384 and a mail box column 386. The name column 384 shows the names of users and associated mail boxes in the mail box column 386. Each mail box listing has a personal identification (PIN) number field 388 which allows the customer to enter a PIN for accessing the associated voicemail box.

<figref idrefs="DRAWINGS">FIG. 6C</figref> shows a voicemail message set up window 400 which is displayed to a customer assuming that the personal computer has a microphone for recording a message to be stored with the associated mailbox at the media content server 44 in <figref idrefs="DRAWINGS">FIG. 1</figref>. The voicemail message set up window 400 has a set of recording controls 402 which enable a user to input a voicemail message to an attached microphone. The set up window 400 includes instructions regarding entry of a voicemail greeting by computer entry and by phone entry. The set up window 400 also indicates the phone number associated with the voicemail box. The recording controls include a record symbol 404, a stop symbol 406, a play symbol 408, a volume slider 410 and a time slider 412. Selecting the record symbol 404 enables the microphone to record a message for association with the mail box. The stop symbol 406 stops the recording. The play symbol 408 plays the message recording. The time slider 412 allows for the playback of the recorded message.

Those of ordinary skill in the art will understand that other features and services including, for example, long distance service, 1-900 numbers, ringtones, call forwarding and conference calling, may be configured for the users such as the users 66, 68 and 70 by the primary account holder such as the user 64 via input screens similar to those in <figref idrefs="DRAWINGS">FIGS. 5-6</figref>. For example, features and services may be made available to a particular user. Other features and services may be made available and the particular user may be given the ability to configure the feature and/or service to their own personal preference using their account information. For example, if a user is given the option for a different ringtone, the user can adjust the ringtone via their customer identification.

<figref idrefs="DRAWINGS">FIG. 7</figref> is a block diagram of an example apparatus 450 to implement the configuration provided by the customer via the user interface 200 shown in <figref idrefs="DRAWINGS">FIGS. 3-6</figref>. The apparatus 450 may, for example, be implemented by a logic circuit in communication with or integral to the IMS core 36, or may be implemented by software and/or firmware executed by components of the IMS core 36 such as the call server 40 and/or the call manager 42. The example apparatus 250 includes a customer data interface 252, a configuration command interface 254, an account verifier 256, a phone user setup module 258, a voice mail setup module 260 and a service setup module 262. The customer data interface 252 exchanges data with the database server 44 and is coupled to the configuration command interface 254 and the account verifier 256. The configuration command interface 254 exchanges data from a web portal such as the VoIP service provider portal 52 and sends configuration data to the phone user setup module 258, the voice mail setup module 260 and the service configuration module 262. The phone user setup module 258, the voice mail setup module 260 and the service configuration module 262 all configure phone service via the call manager 42 in accordance to customer configurations entered via the user interface 200 shown in <figref idrefs="DRAWINGS">FIGS. 3-6</figref>.

<figref idrefs="DRAWINGS">FIGS. 8A-8B</figref> are flow diagrams of an example process used in response to the user interface 200 shown in <figref idrefs="DRAWINGS">FIGS. 3-6</figref> by the apparatus 450 of the IMS core 36 to configure the call server 40 and call manager 42 for the VoIP phones of a customer account such as that of the customer premises 22 in <figref idrefs="DRAWINGS">FIG. 1</figref>. The customer first accesses the customer interface 200 described above via the VoIP service provider portal 52. The customer enters identification information including a password which is sent to the account verifier 256 of the apparatus 450 via the portal 52 to authenticate the customer and allow access to the account (block 500). The customer data interface 252 first determines the account information associated with the customer including the number of phones in the premises, the phone numbers associated with the phones and the names of other users associated with the customer account from the database server 44 (block 501). After the portal displays the user selection window 210 in the customer interface 200 in <figref idrefs="DRAWINGS">FIG. 3</figref> and the customer selects the user names for the phones, the configuration command interface 254 reads the selected user names (block 502). The customer data interface 252 retrieves account identifications for the selected user names from the database server 44 for the display on the user interface 200 (block 504).

After the customer enters the other user names, the user names are sent from the portal 52 to the configuration command interface 254 and to the database server 44 via the customer data interface 252 to be stored with the account information (block 506). The configuration command interface 254 then begins with the phone numbers in the account and receives the customer selection from the phone number set up window 250 in <figref idrefs="DRAWINGS">FIG. 4</figref> to set the phone number as a private phone or a shared phone (block 508). The configuration command interface 254 then determines whether the user has designated a phone as a private phone (block 510). If the phone is a private phone, the customer enters the user name associated with the phone in the private phone set up window 330 in <figref idrefs="DRAWINGS">FIG. 5C</figref> for the phone user setup module 258 and for storage in the database server 44 via the customer data interface 252 (block 512). The configuration command interface 254 then determines whether there are remaining phones associated with the customer account (block 514). If there are remaining phones, the IMS core 36 loops back to block 510 to record the status of the users of that phone.

If the phone is not a private phone, the configuration command interface 254 determines if the customer has selected the option for all users to share the phone from the sharing configuration window 280 in <figref idrefs="DRAWINGS">FIG. 5A</figref> (block 516). If the phone is shared, the phone number is set to be shared by all the users associated with the account via the phone user setup module 258 (block 518). If the phone is not shared, the configuration command interface 254 reads the input names associated with the phone as entered by the user in the user sharing configuration window 300 in <figref idrefs="DRAWINGS">FIG. 5B</figref> and the phone user setup module 258 configures the phone via the call manager 42 (block 520). After the user or users are associated with a phone, the configuration command interface 254 determines whether there are remaining phones to be assigned to users (block 514). If there are remaining phones, the configuration command interface 254 loops back to determine the assigned users for the next phone in block 510.

If all the phones associated with the account have been assigned users and a shared or private designation, the configuration command interface 254 accepts the assignment of voicemail boxes to different users for each phone and the voice mail setup module 260 configures the voice mail via the call manager 42 (block 522). The configuration command interface 254 then accepts the user input of a PIN for each voicemail box from the voicemail identification set up window 380 in <figref idrefs="DRAWINGS">FIG. 6B</figref> (block 524). The configuration command interface 254 then accepts the input voice message for the mail box from the voicemail message set up window 400 in <figref idrefs="DRAWINGS">FIG. 6C</figref> and the voice mail setup module 260 configures the voice mail via the call manger 42 (block 526). The customer data interface 252 stores the message in the database server 44 for use by the call manager 42 (block 526). The services setup module 262 then configures other features and/or services, which have been enabled for the different users, via the call manager 42 (block 528). The configuration command interface 254 determines if there are other voicemail boxes (block 530). If there are other remaining voicemail boxes, the configuration command interface 254 loops up to block 522 to assign the next voicemail box. If there are no remaining voicemail boxes, the configuration command interface 254 terminates the set up process.

<figref idrefs="DRAWINGS">FIG. 9</figref> is a schematic diagram of an example processor platform 1000 which may be used for the personal computer 58 capable of implementing the example machine readable instructions illustrated in <figref idrefs="DRAWINGS">FIGS. 3-6</figref>. For example, the processor platform 1000 can be implemented by one or more general purpose microprocessors, microcontrollers, etc. The processor platform 1000 of the example includes the processor 1012 that is a general purpose programmable processor. The processor 1012 executes coded instructions present in a memory 1020 of the processor 1012. The processor 1012 may be any type of processing unit, such as a microprocessor. The processor 1012 includes a local memory 1014. The processor 1012 may execute, among other things, the example machine readable instructions illustrated in <figref idrefs="DRAWINGS">FIGS. 3-6</figref>.

The processor 1012 is in communication with the main memory including a read only memory (ROM) 1020 and/or a RAM 1018 via a bus 1022. The RAM 1018 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic DRAM, and/or any other type of RAM device. The ROM 1020 may be implemented by flash memory and/or any other desired type of memory device. Access to the memory space 1020 and 1018 is typically controlled by a memory controller (not shown) in a conventional manner. The RAM 1018 may be used by the processor 1012 to implement the memory 1020, and/or to store coded instructions 1016 that can be executed to implement the example machine readable instructions illustrated in <figref idrefs="DRAWINGS">FIGS. 3-6</figref>.

The processor platform 1000 also includes a conventional interface circuit 1024. The interface circuit 1024 may be implemented by any type of well known interface standard, such as an external memory interface, serial port, general purpose input/output, etc. One or more input devices 1026 are connected to the interface circuit 1024. One or more output devices 1028 are also connected to the interface circuit 1024. Additional permanent storage may be offered via a mass storage device 1030 which may be a hard drive. In the illustrated example, a microphone or telephony equipment may be part of the input devices 1026.

At least some of the above described example methods and/or apparatus are implemented by logic, such as one or more software and/or firmware programs running on a computer processor. However, such logic may also include dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement some or all of the example methods and/or apparatus described herein, either in whole or in part. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the example methods and/or apparatus described herein.

It should also be noted that the example software and/or firmware implementations described herein are optionally stored on a tangible storage medium, such as: a magnetic medium (e.g., a magnetic disk or tape); a magneto-optical or optical medium such as an optical disk; or a solid state media such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories; or a signal containing computer instructions. A digital file attached to e-mail or other information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the example software and/or firmware described herein can be stored on a tangible storage medium or distribution medium such as those described above or successor storage media.

To the extent the above specification describes example components and functions with reference to particular standards and protocols, it is understood that the scope of this patent is not limited to such standards and protocols. For instance, each of the standards for Internet and other packet switched network transmission (e.g., Transmission Control Protocol (TCP)/Internet Protocol (IP), User Datagram Protocol (UDP)/IP, HyperText Markup Language (HTML), HyperText Transfer Protocol (HTTP)) represent examples of the current state of the art. Such standards are periodically superseded by faster or more efficient equivalents having the same general functionality. Accordingly, replacement standards and protocols having the same functions are equivalents which are contemplated by this patent and are intended to be included within the scope of the accompanying claims.

Additionally, although this patent discloses example systems including software or firmware executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware and software components could be embodied exclusively in hardware, exclusively in software, exclusively in firmware or in some combination of hardware, firmware and/or software. Accordingly, while the above specification described example systems, methods and articles of manufacture, persons of ordinary skill in the art will readily appreciate that the examples are not the only way to implement such systems, methods and articles of manufacture. Therefore, although certain example methods, apparatus and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.

Contents4

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US8863256B1	Cited by	United States of America	Applicant
US9100415B2	Cited by	United States of America	Search report
US2011028135A1	Cited by	United States of America	Pre-grant
US8514825B1	Cited by	United States of America	Applicant
US9036509B1	Cited by	United States of America	Applicant
US8676180B2	Cited by	United States of America	Applicant
US9083581B1	Cited by	United States of America	Applicant
US10551989B2	Cited by	United States of America	Applicant
US8811969B2	Cited by	United States of America	Search report
US10602329B2	Cited by	United States of America	Applicant
US9888363B2	Cited by	United States of America	Applicant
US8639245B2	Cited by	United States of America	Applicant
US9438742B2	Cited by	United States of America	Search report
US2011149948A1	Cited by	United States of America	Pre-grant
US8848608B1	Cited by	United States of America	Applicant
US2011317826A1	Cited by	United States of America	Pre-grant
US10979875B2	Cited by	United States of America	Applicant
US10117066B2	Cited by	United States of America	Applicant
US9055141B2	Cited by	United States of America	Applicant
US2010311402A1	Cited by	United States of America	Pre-grant
US8634828B2	Cited by	United States of America	Applicant
US8718797B1	Cited by	United States of America	Applicant
US9860709B2	Cited by	United States of America	Applicant
US9277370B2	Cited by	United States of America	Applicant
US8989954B1	Cited by	United States of America	Applicant
US2010311468A1	Cited by	United States of America	Pre-grant
US2011173541A1	Cited by	United States of America	Pre-grant
US12287946B2	Cited by	United States of America	Applicant
US2009191846A1	Cited by	United States of America	Pre-grant
US2010311404A1	Cited by	United States of America	Pre-grant
US2010311444A1	Cited by	United States of America	Pre-grant
US9654937B2	Cited by	United States of America	Applicant
US9225782B2	Cited by	United States of America	Applicant
US8200736B2	Cited by	United States of America	Applicant
US9154900B1	Cited by	United States of America	Applicant
US2010311418A1	Cited by	United States of America	Pre-grant
US8649789B2	Cited by	United States of America	Applicant
US8903593B1	Cited by	United States of America	Applicant
US8705527B1	Cited by	United States of America	Applicant
US2003068019A1	Cites	United States of America	Search report
US2004133888A1	Cites	United States of America	Applicant
US2006062358A1	Cites	United States of America	Search report
US2007121914A1	Cites	United States of America	Search report
US2007269023A1	Cites	United States of America	Search report
US6031904A	Cites	United States of America	Applicant
US6091808A	Cites	United States of America	Applicant
US6356543B2	Cites	United States of America	Applicant
US6526129B1	Cites	United States of America	Applicant
US6529596B1	Cites	United States of America	Applicant
US6879666B2	Cites	United States of America	Search report
US7035385B2	Cites	United States of America	Search report
US7212619B1	Cites	United States of America	Search report

6 members in 1 office

This recordMember, by publication datePriority claim

Priority claims2

Priority claims
Document	Office	Kind	Date
53057806	United States of America	A	2006-09-11
US20060530578	–	–	–

Members6

Family members, oldest first
Document	Office	Kind
US2008075245A1	United States of America	A1	2008-03-27
US7787602B2This record	United States of America	B2	2010-08-31
US2010266109A1	United States of America	A1	2010-10-21
US8396194B2	United States of America	B2	2013-03-12
US2013155908A1	United States of America	A1	2013-06-20
US8903054B2	United States of America	B2	2014-12-02

33 transactions on the USPTO file

Allowed without a rejection on record.

Non-final rejections: 0
Final rejections: 0
RCEs: 0
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2022-10-03	Expire PatentEXP.	EXP.
2022-04-18	Maintenance Fee Reminder MailedREM.	REM.
2018-01-17	Payment of Maintenance Fee, 8th Year, Large EntityM1552	M1552
2014-05-28	Correspondence Address ChangeC.AD	C.AD
2010-08-31	Recordation of Patent Grant MailedPGM/	PGM/
2010-08-31	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2010-08-11	Issue Notification MailedAllowedWPIR	WPIR
2010-07-23	Dispatch to FDCD1935	D1935
2010-07-22	Mail Response to 312 Amendment (PTO-271)MN271	MN271
2010-07-21	Application Is Considered Ready for IssuePILS	PILS
2010-07-19	Response to Amendment under Rule 312N271	N271
2010-07-07	Amendment after Notice of Allowance (Rule 312)AllowedA.NA	A.NA
2010-07-07	Issue Fee Payment VerifiedN084	N084
2010-07-07	Workflow - Drawings FinishedDRWF	DRWF
2010-07-07	Issue Fee Payment ReceivedIFEE	IFEE
2010-04-07	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2010-04-06	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2010-03-11	Case Docketed to Examiner in GAUDOCK	DOCK
2008-11-13	Correspondence Address ChangeC.ADB	C.ADB
2008-04-17	Case Docketed to Examiner in GAUDOCK	DOCK
2008-03-27	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2007-10-17	Withdraw Flagged for 5/25W525	W525
2007-10-15	Flagged for 5/25F525	F525
2006-10-17	IFW TSS Processing by Tech Center CompleteTSSCOMP	TSSCOMP
2006-09-28	Application Is Now CompleteCOMP	COMP
2006-09-27	Application Dispatched from OIPEOIPE	OIPE
2006-09-21	Cleared by OIPE CSRL194	L194
2006-09-19	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2006-09-11	Information Disclosure Statement consideredIDSC	IDSC
2006-09-11	Oath or Declaration Filed (Including Supplemental)C602	C602
2006-09-11	Information Disclosure Statement (IDS) FiledM844	M844
2006-09-11	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2006-09-11	Initial Exam Team nnIEXX	IEXX

11 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2022-10-25	Lapsed due to failure to pay maintenance feeLapsedFP	FP
2022-10-03	Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS	LAPS
2022-10-03	Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH	STCH
2022-04-18	Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2018-01-17	Maintenance fee paymentMAFP	MAFP
2014-01-28	Fee paymentFPAY	FPAY
2010-08-11	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2009-12-08	Fee payment procedurePAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2009-12-08	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2006-09-15	AssignmentAS	AS
2006-09-15	AssignmentAS	AS