US8320896B1 - Unified communication access system - Google Patents

Unified communication access system Download PDF

Info

Publication number
US8320896B1
US8320896B1 US12/699,666 US69966610A US8320896B1 US 8320896 B1 US8320896 B1 US 8320896B1 US 69966610 A US69966610 A US 69966610A US 8320896 B1 US8320896 B1 US 8320896B1
Authority
US
United States
Prior art keywords
mobile device
communication system
unified communication
unified
communication service
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.)
Expired - Fee Related, expires
Application number
US12/699,666
Inventor
Lyle Walter Paczkowski
Pallavur Sankaranaraynan
Warren B. Cope
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sprint Communications Co LP
Original Assignee
Sprint Communications Co LP
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Sprint Communications Co LP filed Critical Sprint Communications Co LP
Priority to US12/699,666 priority Critical patent/US8320896B1/en
Assigned to SPRINT COMMUNICATIONS COMPANY L.P. reassignment SPRINT COMMUNICATIONS COMPANY L.P. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: COPE, WARREN B., PACZKOWSKI, LYLE WALTER, SANKARANARAYNAN, PALLAVUR
Application granted granted Critical
Publication of US8320896B1 publication Critical patent/US8320896B1/en
Assigned to DEUTSCHE BANK TRUST COMPANY AMERICAS reassignment DEUTSCHE BANK TRUST COMPANY AMERICAS GRANT OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS Assignors: SPRINT COMMUNICATIONS COMPANY L.P.
Assigned to DEUTSCHE BANK TRUST COMPANY AMERICAS reassignment DEUTSCHE BANK TRUST COMPANY AMERICAS SECURITY AGREEMENT Assignors: ASSURANCE WIRELESS USA, L.P., BOOST WORLDWIDE, LLC, CLEARWIRE COMMUNICATIONS LLC, CLEARWIRE IP HOLDINGS LLC, CLEARWIRE LEGACY LLC, ISBV LLC, Layer3 TV, Inc., PushSpring, Inc., SPRINT COMMUNICATIONS COMPANY L.P., SPRINT INTERNATIONAL INCORPORATED, SPRINT SPECTRUM L.P., T-MOBILE CENTRAL LLC, T-MOBILE USA, INC.
Assigned to SPRINT COMMUNICATIONS COMPANY L.P. reassignment SPRINT COMMUNICATIONS COMPANY L.P. TERMINATION AND RELEASE OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS Assignors: DEUTSCHE BANK TRUST COMPANY AMERICAS
Assigned to PUSHSPRING, LLC, CLEARWIRE COMMUNICATIONS LLC, IBSV LLC, CLEARWIRE IP HOLDINGS LLC, LAYER3 TV, LLC, ASSURANCE WIRELESS USA, L.P., SPRINT SPECTRUM LLC, SPRINTCOM LLC, BOOST WORLDWIDE, LLC, SPRINT COMMUNICATIONS COMPANY L.P., SPRINT INTERNATIONAL INCORPORATED, T-MOBILE CENTRAL LLC, T-MOBILE USA, INC. reassignment PUSHSPRING, LLC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: DEUTSCHE BANK TRUST COMPANY AMERICAS
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

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/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
    • H04M2207/20—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place hybrid systems

Abstract

Embodiments disclosed herein provide systems and methods that allow a mobile device to fully access unified communication services. In a particular embodiment, a mobile device receives a user input indicating a destination identifier for a call and processes the destination identifier to determine whether the destination identifier is associated with a unified communication service. If no, the mobile device connects the call. If yes, the mobile device generates and transfers a text message indicating that the mobile device is requesting the service to an intermediate communication system in a first carrier network. The intermediate system receives and processes the text message to determine a first portion of the service that is associated with the mobile device. The intermediate system initiates the call to the mobile device to connect the mobile device with a unified communication system via the intermediate system and provides the first portion of the service.

Description

TECHNICAL BACKGROUND
Unified communication services allow for the integration of real time communication services, such as voice calling and instant messaging, with non-real time communication services, such as voicemail and short message service (SMS). For example, unified communication services may allow multiple phones to be accessed by a single phone number and have the same voicemail inbox. A unified communication system may provide at least a subset of the services that make up unified communication services.
In some cases, other systems on a communication network, such as an Internet Protocol Multimedia Subsystem (IMS) platform, may be necessary to provide other subsets of unified communication services. Mobile devices that access the unified communication system on the same communication network as the IMS platform may be automatically routed through the IMS platform to the unified communication system. However, mobile devices that are not on the same network as the IMS platform may not be routed through the IMS platform and, thus, may only be provided with the subset of unified communication services provided by the unified communication system.
OVERVIEW
Embodiments disclosed herein provide systems and methods that allow a mobile device to fully access unified communication services from a carrier service provider. In a particular embodiment, a mobile device receives a user input indicating a destination identifier for a call. The mobile device processes the destination identifier to determine whether the destination identifier is associated with a unified communication service. If the destination identifier is not associated with the unified communication service, the mobile device initiates the call to the identified destination. If the destination identifier is associated with the unified communication service, the mobile device generates a text message indicating that the mobile device is requesting the unified communication service and transfers the text message to an intermediate communication system in a first carrier network. The intermediate communication system receives the text message from the mobile device and processes the text message to determine at least a first portion of the unified communication service that is associated with the mobile device. The call is initiated by the intermediate communication system to the mobile device that connects the mobile device to a unified communication system via the intermediate communication system. The intermediate communication system provides the first portion of the unified communication service.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates a wireless communication system.
FIG. 2 illustrates the operation of a wireless communication system.
FIG. 3 illustrates a wireless communication system.
FIG. 4 illustrates the operation of a wireless communication system.
FIG. 5 illustrates the operation of a wireless communication system.
FIG. 6 illustrates a mobile communication device.
FIG. 7 illustrates an intermediate communication system.
 DETAILED DESCRIPTION
The following description and associated figures teach the best mode of the invention. For the purpose of teaching inventive principles, some conventional aspects of the best mode may be simplified or omitted. The following claims specify the scope of the invention. Note that some aspects of the best mode may not fall within the scope of the invention as specified by the claims. Thus, those skilled in the art will appreciate variations from the best mode that fall within the scope of the invention. Those skilled in the art will appreciate that the features described below can be combined in various ways to form multiple variations of the invention. As a result, the invention is not limited to the specific examples described below, but only by the claims and their equivalents.
FIG. 1 illustrates wireless communication system 100. Wireless communication system 100 includes mobile device 101, carrier network 102, carrier network 103, intermediate communication system 104, unified communication system 105, and communication network 106. Mobile device 101 and carrier network 102 communicate over wireless link 110. Carrier network 102 and communication network 106 communicate over link 111. Communication network 106 and carrier network 103 communicate over link 112. Communication network 106 and unified communication system 104 communicate over link 113. Carrier network 103 and intermediate communication system 104 communicate over link 114.
In operation, communication network 100 is capable of providing unified communication services. Unified communication services allow for the integration of real time communication services, such as voice calling and instant messaging, with non-real time communication services, such as voicemail and short message service (SMS). Unified communication system 105 provides at least a portion of the unified communication services. Intermediate system 104 is a system within carrier network 103 that may provide, or enable, another portion of the unified communication service, such as SMS, trigger detection, or the like. Therefore, a call request for a unified communication service must go through both intermediate system 104 and unified communication system 105 in order to access all portions of the unified communication service.
A mobile device, such as mobile device 101 will only be provided with the portion of the unified communication service that is provided by intermediate communication system 104 if mobile device 101 is associated with the unified communication service. Mobile device 101 may be associated with the unified communication service if it belongs to, or is supplied by, a customer of the unified communication service or has otherwise been given the permissions necessary to access the unified communication service. The permissions necessary to access the unified communication service may be provided by the user, possibly in the form of an identification code entered into mobile device 101.
If mobile device 101 is associated with the unified communication service and requests access to a unified communication service from within carrier network 103, then the request will be sent through intermediate system 104 before being routed to unified communication system 105. Mobile device 101 will then be capable of accessing all portions of the unified communication service to which mobile device 101 is entitled. However, if mobile device 101 is associated with the unified communication service and requests access to a unified communication service from within carrier network 102, then the request may not be routed through intermediate system 104 before being routed to unified communication system 105. In that case mobile device 101 will only be able to access the first portion of the unified communication service that is provided by unified communication system 105, but not the second portion of the unified communication service that is provided by intermediate system 104.
FIG. 2 illustrates the operation of wireless communication system 100. Mobile device 101 receives a user input indicating destination identifier for a call (step 200). The destination identifier may be a phone number, a Session Initiation Protocol (SIP) identifier, an IP address, or some other identifier that may be used to identify a call destination. A user may indicate the destination identifier in mobile device 101 by dialing a number, selecting the identifier out of a contact list, selecting the identifier off of a web page, selecting the identifier out of an email, or some other way that a user may select an identifier on a mobile device. The destination identifier may be for a standard voice call but may also be a VoIP call or a request for some other unified communication service such as voicemail or messaging.
Mobile device 101 processes the destination identifier to determine whether the destination identifier is associated with a unified communication service (step 202). The destination identifier is associated with the unified communication service if the destination identifier directs a call to the unified communication service. Mobile device 101 may process the destination identifier by using a lookup table or otherwise comparing the destination identifier to those identifiers that are associated with the unified communication service. A database of associated identifiers for comparison may be stored on mobile device 101. Alternatively, the database of associated identifiers may be stored elsewhere, such as on intermediate system 104 or unified communication system 105.
If the destination identifier is not associated with the unified communication service, then mobile device 101 initiates the call to the identified destination (step 204). If the destination identifier is associated with the unified communication system, then mobile device 101 generates and transfers a text message indicating that mobile device 101 is requesting the unified communication service to intermediate communication system 104 in carrier network 103 (step 206). The text message may be sent using short message service (SMS), multimedia messaging service (MMS), email, or some other service capable of sending text-based messages.
Intermediate communication system 104 receives the text message from mobile device 101 (step 208). Intermediate communication system 104 processes the text message to determine a first portion of the unified communication service that is associated with mobile device 101 (step 210). Intermediate communication system 104 may determine whether the first portion of the unified communication service is associated with mobile device 101 by identifying mobile device 101 and determining which portion of the unified communication service is associated with the destination identifier and mobile device 101. Mobile device 101 may be identified by the return number of mobile device 101, possibly located in a header of the text message, or by some other form of identification for mobile device 101 included in the text message or otherwise.
Intermediate communication system 104 then initiates the call to mobile device 101 that connects mobile device 101 to unified communication system 105 via intermediate system 104 (step 212). Intermediate communication system 104 provides the first portion of the unified communication service (214). Therefore, mobile device 101 has identified itself to intermediate communication system 104 as being associated with the requested unified communication service, which allows mobile device 101 to access the first portion of the unified communication service that is provided by intermediate communication system 104.
Referring back to FIG. 1, wireless communication device 101 comprises Radio Frequency (RF) communication circuitry and an antenna. The RF communication circuitry typically includes an amplifier, filter, modulator, and signal processing circuitry. Wireless communication device 101 may also include a user interface, memory device, software, processing circuitry, or some other communication components. Wireless communication device 101 may be a telephone, computer, e-book, mobile Internet appliance, wireless network interface card, media player, game console, or some other wireless communication apparatus—including combinations thereof.
Carrier networks 102 and 103 and communication network 106 are communication networks that comprise telephony switches, wireless access nodes, Internet routers, network gateways, computer systems, communication links, or some other type of communication equipment—including combinations thereof.
Intermediate system 104 comprises a computer system and communication interface. Intermediate system 104 may also include other components such a router, server, data storage system, and power supply. Intermediate system 104 may reside in a single device or may be distributed across multiple devices. Intermediate system 104 is shown externally to carrier network 103, but intermediate system 104 could be integrated within the components of carrier network 103. Intermediate system 104 could be a mobile switching center, network gateway system, Internet access node, application server, IMS core, service node, or some other communication system—including combinations thereof. Intermediate system 104 may provide audio, video, VoIP, unified communication, or some other application or service that mobile device 101 could access over carrier network 103.
Unified communication system 105 comprises a computer system and communication interface. Unified communication system 105 may also include other components such a router, server, data storage system, and power supply. Unified communication system 105 may reside in a single device or may be distributed across multiple devices. Unified communication system 105 is shown externally to carrier network 103, but unified communication system 105 could be integrated within the components of carrier network 103. Unified communication system 105 could be a mobile switching center, network gateway system, Internet access node, application server, IMS core, service node, or some other communication system—including combinations thereof. Unified communication system 105 provides at least a portion of unified communication services that mobile device 101 could access over carrier networks 102 and 103.
Wireless link 110 uses the air or space as the transport media. Wireless link 110 may use various protocols, such as Code Division Multiple Access (CDMA), Evolution Data Only (EVDO), Worldwide Interoperability for Microwave Access (WIMAX), Global System for Mobile Communication (GSM), Long Term Evolution (LTE), Wireless Fidelity (WIFI), High Speed Packet Access (HSPA), or some other wireless communication format. Communication links 111-114 use metal, glass, air, space, or some other material as the transport media. Communication links 111-114 could use various communication protocols, such as Time Division Multiplex (TDM), Internet Protocol (IP), Ethernet, communication signaling, CDMA, EVDO, WIMAX, GSM, LTE, WIFI, HSPA, or some other communication format—including combinations thereof. Communication links 111-114 could be a direct link or may include intermediate networks, systems, or devices.
FIG. 3 illustrates wireless communication system 300 in an example embodiment. Wireless communication system 300 includes mobile device 301A, mobile device 301B, carrier network 302, carrier network 303, Internet Protocol Multimedia Subsystem (IMS) platform 304, unified communication system 305, and communication network 306. Mobile device 301A and carrier network 302 communicate over wireless link 310. Mobile device 301B and carrier network 302 communicate over wireless link 315. Carrier network 302 and communication network 306 communicate over link 311. Communication network 306 and carrier network 303 communicate over link 312. Communication network 306 and unified communication system 305 communicate over link 313. Carrier network 303 and IMS platform 304 communicate over link 314.
Wireless links 310 and 315 use the air or space as the transport media. Wireless links 310 and 315 may use various protocols, such as Code Division Multiple Access (CDMA), Evolution Data Only (EVDO), Worldwide Interoperability for Microwave Access (WIMAX), Global System for Mobile Communication (GSM), Long Term Evolution (LTE), Wireless Fidelity (WIFI), High Speed Packet Access (HSPA), or some other wireless communication format. Communication links 311-314 use metal, glass, air, space, or some other material as the transport media. Communication links 311-314 could use various communication protocols, such as Time Division Multiplex (TDM), Internet Protocol (IP), Ethernet, communication signaling, CDMA, EVDO, WIMAX, GSM, LTE, WIFI, HSPA, or some other communication format—including combinations thereof. Communication links 311-314 could be a direct link or may include intermediate networks, systems, or devices.
Unified communication system 305 is shown external to carrier network 303 and communication network 306 but may be part of either network. Unified communication system 305 may be integrated into IMS platform 304.
IMS platform 304 provides a portion of unified communication services but may also provide other services for carrier network 303.
In FIG. 3 IMS platform 304 is located within carrier network 303 while mobile devices 301A and 301B are located on carrier network 302. Hence, if mobile devices 301A and 301B are associated with a unified communication service and access unified communication system 306 for the unified communications service, then mobile devices 301A and 301B will not be automatically routed through IMS platform 304 because carrier network 303 is not handling the call. Without accessing IMS platform 304, mobile devices 301A and 301B may not have access to at least a portion of the unified communication service.
Mobile devices 301A and 301B are associated with a unified communication service provided by IMS platform 304 and unified communication system 305. In order to receive the portion of the unified communication service that is provided by IMS platform 305, mobile devices 301A and 301B are configured to determine whether a user indicated destination identifier is associated with the unified communication services and transfer a text message to IMS platform 304. This functionality is described in further detail below in reference to FIGS. 4 and 5.
FIG. 4 is a sequence diagram illustrating the operation of communication network 300. Mobile device 301A begins by receiving a user input indicating a destination identifier for a call. The user input may be a user dialed number or a user selected identifier out of a contact list, website, email, or other type of user destination indication. In this example, the destination identifier indicated by the user is not associated with the unified communication service. Mobile device 301A processes the destination identifier to determine that the identifier is not associated with the unified communication service. Since the destination identifier is not associated with the unified communication service, mobile device 301A initiates the call to the indicated destination through carrier network 302. The indicated destination is not shown in FIG. 3 but may be a communication device or system located within carrier networks 302 or 303, communication network 306, or some other communication network.
FIG. 5 is a sequence diagram illustrating the operation of communication network 300. Mobile device 301B begins by receiving a user input indicating a destination identifier for a call. The user input may be a user dialed number or a user selected identifier out of a contact list, website, email, or other type of user destination indication. In this example, the destination identifier indicated by the user is associated with the unified communication service. Mobile device 301B processes the destination identifier to determine that the identifier is associated with the unified communication service. Upon determining that the destination identifier is associated with the unified communication service, mobile device 301 may save the identifier in a list of associated identifiers for quick reference. Thus, if the user indicates the same identifier at a later time, mobile device 301 will only need to check whether the identifier is on the associated identifier list before having to fully process the identifier.
Mobile device 301B generates a text message indicating that mobile device 301B is requesting the unified communication service. The text message may indicate the phone number from the user and an identifier for mobile device 301B, or any other information necessary for mobile device 301B to access the unified communication service. Mobile device 301B then transfers the text message to IMS platform 304.
IMS platform 304 receives the text message from mobile device 301B and processes the message to determine a first portion of the unified communication service that is associated with mobile device 301B. IMS platform 304 determines a first portion of the unified communication service based on the unified communication service that is associated with the destination identifier and the unified communication service that is associated with mobile device 301B. Thus, the portion of the unified communication service that is provided by IMS platform 304 depends on whether the portion is needed for the requested unified communication service and whether mobile device 301B is allowed to access the portion of the unified communication service by being associated with the unified communication service.
After determining the first portion of the unified communication service that is associated with the destination identifier, IMS platform 304 initiates the call to mobile device 301B that connects mobile device 301B to unified communication system 305 via IMS platform 304. IMS platform provides the first portion of the unified communication service mobile device 301B while unified communication system 305 provides a second portion. Therefore, even though mobile device 301B is not accessing the unified communication service from within carrier network 303, mobile device 301B can still access the portion of the unified communication service that is provided by IMS platform 304.
In both FIGS. 4 and 5, mobile device 301 may be preconfigured to process the user indicated destination identifier. However, mobile device 301 may also install and run an application that processes the destination identifier, generates the text message, and transfers it to IMS platform 304. The application may run in the background and automatically process user indicated destination identifier or the application may be executed by the user for the purpose of indicating a destination identifier. The application may be provided by the unified communication service.
Additionally, the application may be a text message application supplied with mobile device 301 or otherwise installed on mobile device 301. A user may input the unified communication service information or destination identifier into a text message field in the application and send the text message to IMS platform 304 without mobile device 301 performing those steps automatically.
In some embodiments, unified communication system 305 provides a second portion of the unified communication service to mobile device 301. In those embodiments, mobile device 301 is provided with both the first portion of the unified communication service that is provided by intermediate system 304 and the second portion of the unified communication service that is provided by unified communication system 305. Thus, mobile device 301 is provided with both portions of the unified communication service even though mobile device 301 is located on carrier network 302 instead of carrier network 303.
In other embodiments, before transferring the text message to IMS platform 304, mobile device 301 determine whether the mobile device is operating within carrier network 303. If mobile device is operating within carrier network 303, then mobile device 301 is operating on the same carrier network as IMS platform 304. Therefore, mobile device 301 connects the call to unified communication system 305 because the call will be routed through IMS platform 304 automatically.
FIG. 6 illustrates mobile device 600. Mobile device 600 is an example of mobile devices 101, 301A, and 301B, although mobile devices 101, 301A, and 301B use alternative configurations. Mobile device 600 comprises communication interface 601, user interface 602, and processing system 603. Processing system 603 is linked to communication interface 601 and user interface 602. Processing system 603 includes processing circuitry 605 and memory device 606 that stores operating software 607.
Communication interface 601 comprises components that communicate over communication links, such as network cards, ports, RF transceivers, processing circuitry and software, or some other communication devices. Communication interface 601 may be configured to communicate over metallic, wireless, or optical links. Communication interface 601 may be configured to use TDM, IP, Ethernet, optical networking, wireless protocols, communication signaling, or some other communication format—including combinations thereof.
User interface 602 comprises components that interact with a user. User interface 602 may include a keyboard, display screen, touch screen, mouse, touch pad, or some other user input/output apparatus. User interface 602 may be omitted in some examples.
Processing circuitry 605 comprises microprocessor and other circuitry that retrieves and executes operating software 607 from memory device 606. Memory device 606 comprises a disk drive, flash drive, data storage circuitry, or some other memory apparatus. Operating software 607 comprises computer programs, firmware, or some other form of machine-readable processing instructions. Operating software 607 may include an operating system, utilities, drivers, network interfaces, applications, or some other type of software. When executed by circuitry 605, operating software 607 directs processing system 603 to operate communication mobile device 600 as described herein.
In particular, user interface 602 receives a user input indicating a destination identifier for a call. Processing system 603 processes the destination identifier to determine whether the destination identifier is associated with a unified communication service. If the destination identifier is not associated with the unified communication service, processing system 603 initiates the call to the identified destination using communication interface 601. If the destination identifier is associated with the unified communication service, processing system 603 generates a text message indicating that the mobile device is requesting the unified communication service and transfers the text message to an intermediate communication system in a first carrier network using communication interface 601. Communication interface 601 further receives a call from the intermediate communication system in order to access the unified communication service.
FIG. 7 illustrates intermediate communication system 700. Intermediate system 700 is an example of intermediate system 104 and IMS platform 304, although intermediate system 104 and IMS platform 304 may use alternative configurations. Intermediate system 700 comprises communication interface 701, user interface 702, and processing system 703. Processing system 703 is linked to communication interface 701 and user interface 702. Processing system 703 includes processing circuitry 705 and memory device 706 that stores operating software 707.
Communication interface 701 comprises components that communicate over communication links, such as network cards, ports, RF transceivers, processing circuitry and software, or some other communication devices. Communication interface 701 may be configured to communicate over metallic, wireless, or optical links.
Communication interface 701 may be configured to use TDM, IP, Ethernet, optical networking, wireless protocols, communication signaling, or some other communication format—including combinations thereof.
User interface 702 comprises components that interact with a user. User interface 702 may include a keyboard, display screen, touch screen, mouse, touch pad, or some other user input/output apparatus. User interface 702 may be omitted in some examples.
Processing circuitry 705 comprises microprocessor and other circuitry that retrieves and executes operating software 707 from memory device 706. Memory device 706 comprises a disk drive, flash drive, data storage circuitry, or some other memory apparatus. Operating software 707 comprises computer programs, firmware, or some other form of machine-readable processing instructions. Operating software 707 may include an operating system, utilities, drivers, network interfaces, applications, or some other type of software. When executed by circuitry 705, operating software 707 directs processing system 703 to operate intermediate communication system 700 as described herein.
In particular, communication interface 701 receives a text message indicating that a mobile device is requesting a unified communication service. Processing system 703 processes the test message to determine at least a first portion of the unified communication service that is associated with the mobile device. Processing system 703 initiates a call to the mobile device using communication interface 701. The call connects the mobile device to a unified communication system via intermediate communication system 700. Processing system 703 provides the first portion of the unified communication service to the mobile device.
The above description and associated figures teach the best mode of the invention. The following claims specify the scope of the invention. Note that some aspects of the best mode may not fall within the scope of the invention as specified by the claims. Those skilled in the art will appreciate that the features described above can be combined in various ways to form multiple variations of the invention. As a result, the invention is not limited to the specific embodiments described above, but only by the following claims and their equivalents.

Claims (20)

1. A communication system comprising:
a mobile device configured to:
receive a user input indicating a destination identifier for a call;
process the destination identifier to determine whether the destination identifier is associated with a unified communication service;
if the destination identifier is not associated with the unified communication service, initiate the call to the identified destination;
if the destination identifier is associated with the unified communication service, generate a text message indicating that the mobile device is requesting the unified communication service and transfer the text message to an intermediate communication system in a first carrier network;
the intermediate communication system configured to:
receive the text message from the mobile device;
process the text message to determine at least a first portion of the unified communication service that is associated with the mobile device;
initiate the call to the mobile device that connects the mobile device to a unified communication system via the intermediate communication system;
provide the first portion of the unified communication service.
2. The communication system of claim 1 wherein the mobile device is further configured to:
if the destination identifier is associated with the unified communication service, determine whether the mobile device is in the first carrier network;
if the mobile device is in the first carrier network, connect the call to the unified communication system.
3. The communication system of claim 1 further comprising the unified communication system configured to provide a second portion of the unified communication service.
4. The communication system of claim 1 wherein the destination identifier is received in an application running on the mobile device.
5. The communication system of claim 2 wherein the application is a text messaging application.
6. The communication system of claim 1 wherein destination identifier is received and processed by an application running in the background on the mobile device.
7. The communication system of claim 1 wherein the unified communication system is integrated into the intermediate communication system.
8. The communication system of claim 3 wherein at least one of the first and second portions of the unified communication service comprises real time voice communication services.
9. The communication system of claim 3 wherein at least one of the first and second portions of the unified communication service comprises unified messaging services.
10. A method of operating a communication system comprising:
in a mobile device:
receiving a user input indicating a destination identifier for a call;
processing the destination identifier to determine whether the destination identifier is associated with a unified communication service;
if the destination identifier is not associated with the unified communication service, initiating the call to the identified destination;
if the destination identifier is associated with the unified communication service, generating a text message indicating that the mobile device is requesting the unified communication service to an intermediate communication system in a first carrier network;
in the intermediate communication system:
receiving the text message from the mobile device;
processing the text message to determine at least a first portion of the unified communication service that is associated with the mobile device;
initiating the call to the mobile device that connects the mobile device to a unified communication system via the intermediate communication system;
providing the first portion of the unified communication service;
in the unified communication system, providing a second portion of the unified communication service.
11. The method of claim 10 further comprising:
in the mobile device, if the destination identifier is associated with the unified communication service, determining whether the mobile device is in the first carrier network;
if the mobile device is in the first carrier network, connecting the call to the unified communication system.
12. The method of claim 10 further comprising, in the unified communication system, providing a second portion of the unified communication service.
13. The method of claim 9 wherein the destination identifier is received in an application running on the mobile device.
14. The method of claim 10 wherein the application is a text messaging application.
15. The method of claim 9 wherein the destination identifier is received and processed by an application running in the background on the mobile device.
16. The method of claim 9 wherein the unified communication system is integrated into the intermediate communication system.
17. The method of claim 12 wherein at least one of the first and second portions of the unified communication service comprises real time voice communication services.
18. The method of claim 12 wherein at least one of the first and second portions of the unified communication service comprises unified messaging services.
19. A mobile device comprising:
a user interface configured to receive a user input indicating a destination identifier for a call;
a processing system configured to:
process the destination identifier to determine whether the destination identifier is associated with a unified communication service;
if the destination identifier is not associated with the unified communication service, initiate the call to the identified destination;
if the destination identifier is associated with the unified communication service, generate a text message indicating that the mobile device is requesting the unified communication service to an intermediate communication system in a first carrier network;
a communication interface configured to:
transfer the text message to the intermediate communication system;
receive the call from the intermediate communication system that connects the mobile device to a unified communication system via the intermediate communication system wherein the intermediate communication system provides a first portion of the unified communication service and the unified communication system provides a second portion of the unified communication service.
20. The mobile device of claim 19 wherein processing system is further configured to:
if the destination identifier is associated with the unified communication service, determine whether the mobile device is in the first carrier network;
if the mobile device is in the first carrier network, connect the call to the unified communication system.
US12/699,666 2010-02-03 2010-02-03 Unified communication access system Expired - Fee Related US8320896B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/699,666 US8320896B1 (en) 2010-02-03 2010-02-03 Unified communication access system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12/699,666 US8320896B1 (en) 2010-02-03 2010-02-03 Unified communication access system

Publications (1)

Publication Number Publication Date
US8320896B1 true US8320896B1 (en) 2012-11-27

Family

ID=47190945

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/699,666 Expired - Fee Related US8320896B1 (en) 2010-02-03 2010-02-03 Unified communication access system

Country Status (1)

Country Link
US (1) US8320896B1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5657383A (en) 1995-06-06 1997-08-12 Lucent Technologies Inc. Flexible customer controlled telecommunications handling
US6891929B2 (en) 2001-08-15 2005-05-10 Microsoft Corporation Automated and integrated call control server
US20090181702A1 (en) * 2008-01-14 2009-07-16 Microsoft Corporation Multi-mode communication
US20110195691A9 (en) * 2001-12-26 2011-08-11 Michael Maguire User interface and method of viewing unified communications events on a mobile device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5657383A (en) 1995-06-06 1997-08-12 Lucent Technologies Inc. Flexible customer controlled telecommunications handling
US6891929B2 (en) 2001-08-15 2005-05-10 Microsoft Corporation Automated and integrated call control server
US20050152507A1 (en) * 2001-08-15 2005-07-14 Microsoft Corporation Automated and integrated call control server
US20110195691A9 (en) * 2001-12-26 2011-08-11 Michael Maguire User interface and method of viewing unified communications events on a mobile device
US20090181702A1 (en) * 2008-01-14 2009-07-16 Microsoft Corporation Multi-mode communication

Similar Documents

Publication Publication Date Title
US9185139B2 (en) Location based routing
US8380858B2 (en) System and method for telecommunication with a web-based network, such as a social network
US20080125123A1 (en) Method and system for to enable communication for a wireless device having a plurality of identifiers
US7773584B2 (en) Method and apparatus for processing session initiation protocol messages associated with a voice over IP terminal
US9692793B2 (en) Communication session allocation
US8831648B2 (en) Methods, systems, and computer program products for routing a short message service (SMS) message from a 2G network to a session initiation protocol (SIP)-based network
US10462294B2 (en) Method and apparatus for processing a communication request from a roaming voice over IP terminal
WO2018208646A1 (en) Network-controlled robocall and scam call handling
US10701112B2 (en) IP-based USSD communications
US10154146B2 (en) Method of managing a communication to a user, and an application server
WO2019245711A1 (en) Session control logic with internet protocol (ip)-based routing
EP3552372B1 (en) Msrp/http file transfer
US9571429B2 (en) Methods and systems for delayed notifications in communications networks
US8467795B2 (en) Location-based routing of IMS calls through femtocells
RU2483352C2 (en) Method, apparatus and system for service identification
EP3515096B1 (en) Processing sms messages
US9294628B2 (en) Method and apparatus for processing network origination calls in a hybrid network
US10033866B2 (en) Facilitation of an internet protocol multimedia platform
US8320896B1 (en) Unified communication access system
US9526121B1 (en) Unified communication access system
US9351136B1 (en) Communication path settings for wireless messaging based on quality of service
US20230117615A1 (en) Api driven subscriber ims registration status changes and ims routing steering
US9083807B2 (en) System for connecting two client entities
US9860722B1 (en) Converting location information into public safety answering point (PSAP) signaling
KR102049587B1 (en) Apparatus for handling Application Server failure in called network, method thereof and computer recordable medium storing the method

Legal Events

Date Code Title Description
AS Assignment

Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PACZKOWSKI, LYLE WALTER;SANKARANARAYNAN, PALLAVUR;COPE, WARREN B.;REEL/FRAME:023894/0340

Effective date: 20100202

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK

Free format text: GRANT OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:SPRINT COMMUNICATIONS COMPANY L.P.;REEL/FRAME:041895/0210

Effective date: 20170203

AS Assignment

Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS

Free format text: TERMINATION AND RELEASE OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:052969/0475

Effective date: 20200401

Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNORS:T-MOBILE USA, INC.;ISBV LLC;T-MOBILE CENTRAL LLC;AND OTHERS;REEL/FRAME:053182/0001

Effective date: 20200401

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20201127

AS Assignment

Owner name: SPRINT SPECTRUM LLC, KANSAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: SPRINT INTERNATIONAL INCORPORATED, KANSAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: SPRINTCOM LLC, KANSAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: CLEARWIRE IP HOLDINGS LLC, KANSAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: CLEARWIRE COMMUNICATIONS LLC, KANSAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: BOOST WORLDWIDE, LLC, KANSAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: ASSURANCE WIRELESS USA, L.P., KANSAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: T-MOBILE USA, INC., WASHINGTON

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: T-MOBILE CENTRAL LLC, WASHINGTON

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: PUSHSPRING, LLC, WASHINGTON

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: LAYER3 TV, LLC, WASHINGTON

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822

Owner name: IBSV LLC, WASHINGTON

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001

Effective date: 20220822