JP2010519790A - System and method for identifying voice call continuity (VCC) subscribers - Google Patents

Abstract

Mobile devices, methods and machine instructions for mobile device communication are provided. The mobile device determines a voice call continuity state by including a voice call continuity state checker, and uses the voice call state to determine whether to initiate an activity related to the voice call continuity. The method includes determining a voice call continuity state and using the voice call continuity state to determine whether to initiate an activity related to voice call continuity. When executed, the machine instructions perform a method that includes determining voice call continuity and using the voice call continuity state for activities related to voice call continuity.

Description

  Easily transportable devices with wireless telecommunications capabilities (eg, devices such as mobile phones, personal digital assistants, handheld computers, etc.) are referred to herein as mobile devices. Some mobile devices communicate in circuit switched mode, and typically there may be a dedicated communication path between the two devices. All data exchanged between the two devices during the duration of the call travels along a single path. An example of a telecommunications protocol that uses circuit switching is Global System for Mobile Communication (GSM).

  Some mobile devices also have the ability to communicate in a packet switched mode. In packet switching, the data stream is divided into a plurality of packets, which are given a plurality of unique identifiers. Multiple packets may then be transmitted from the source to the destination along multiple different paths and may arrive at the destination at multiple different timings. Upon arrival at the destination, the multiple packets are reconstructed into their original sequence of multiple packets based on the multiple identifiers. An example of a telecommunications protocol that uses packet switching is the Session Initiation Protocol (SIP).

  Communication performed via the circuit switched protocol may be said to occur in the circuit switched domain, and communication performed via the packet switched protocol may be said to occur in the packet switched domain. Mobile devices that can communicate only in the circuit switched domain or only in the packet switched domain may be referred to as single domain devices or single mode devices. Mobile devices that can communicate in both circuit switched and packet switched domains may be referred to as dual domain devices or dual mode devices. A communication connection in a circuit switched domain or a packet switched domain may be referred to as a call or session. These calls or sessions may carry voice or data.

  Although exemplary implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and / or methods are presently known or exist in any number of It should be understood first that it may be implemented using technology. The present disclosure should not be limited to the example implementations, drawings, and techniques (exemplary designs and implementations shown and described herein) set forth below, but of the appended claims Modifications may be made within the scope and equivalents thereof.

  Voice Call Continuity (VCC) technology is a service that allows a mobile device to transfer a voice call from a circuit switched domain to a packet switched domain, or from a packet switched domain to a circuit switched domain. The circuit switched domain provides ancillary services such as call hold and call waiting to mobile device service subscribers. Both of these services are controlled by a visitor mobile switching center (VMSC), where service subscribers of mobile devices are registered at the VMSC. However, once the VCC operation is invoked, the mobile device may no longer be able to communicate with the VMSC to control these services. The standard for mobile devices is that mobile devices that are connected to both active and inactive calls (eg, call hold or call waiting) will be informed before the mobile device performs VCC when VCC is invoked. It is defined that an active call is dropped. However, in some examples this may not be desirable. For example, if the user of the mobile device is not a VCC subscriber, the mobile device may not perform a VCC switch to the packet switched domain when the call is dropped because the user is not subscribed to the VCC service. possible. Thus, non-VCC subscribers suffer from service degradation when service degradation should not occur.

  Since the mobile device needs to drop the inactive call as part of the domain transfer procedure, the mobile device needs to determine whether the subscriber is a VCC. For example, if a VCC subscriber gives his mobile device to a non-VCC subscriber, the non-subscriber may move the mobile device into range of a wireless local area network. A mobile device may attempt to transfer a call from a more expensive circuit switched domain to a less expensive packet switched domain by reducing the cost of the call by invoking the VCC. The mobile device drops the inactive call before attempting the VCC, even if the VCC may fail for non-VCC subscribers. Thus, non-VCC subscribers can unnecessarily lose inactive calls because non-VCC exchanges are not performed indefinitely.

  The present disclosure provides a VCC state (eg, whether or not the subscriber is a VCC subscriber) before initiating a VCC-related activity (eg, dropping a second call or attempting a domain transfer), Or a system and method for determining whether a call is anchored to a VCC server. The VCC state can be obtained by the mobile device during registration, call setup, or by information stored in the memory of the mobile device.

  In one embodiment, a mobile device is provided. The mobile device includes a voice call continuity status checker that determines a voice call continuity status and initiates an activity related to voice call continuity based on the voice call continuity status. It is configured to determine whether or not. In another embodiment, a mobile device communication method is provided. The method includes determining a voice call continuity state and determining whether to initiate an activity related to voice call continuity based on the voice call continuity state. In still other embodiments, a machine instruction is provided that, when executed, determines a voice call continuity state and executes a voice call continuity state for activities related to voice call continuity. Using.

For a more complete understanding of the present disclosure, reference is now made to the following brief description, taken in conjunction with the accompanying drawings and detailed description. The same reference number represents the same part.
FIG. 1 is a block diagram of a system including a mobile device operable in a circuit switched domain and a packet switched domain according to an embodiment of the present invention. FIG. 2 is a block diagram of another embodiment of a system including a mobile device. FIG. 3 is a call flow diagram of a call set up in a circuit switched domain according to one embodiment of the present disclosure. FIG. 4 is a call flow diagram for a mobile device registering with a communication network in accordance with one embodiment of the present disclosure. FIG. 5 is a diagram of a method for identifying a state of voice call continuity according to an embodiment of the present disclosure. FIG. 6 is an illustration of a wireless communication system including a mobile device operable for some of the various embodiments of the present disclosure. FIG. 7 is a block diagram of a mobile device operable for some of the various embodiments of the present disclosure. FIG. 8 is an illustration of a software environment that may be implemented on a mobile device operable for some of the various embodiments of the present disclosure.

  FIG. 1 is a block diagram of an embodiment of a system 100 that includes a mobile device 102, a circuit switched domain 104, a packet switched domain 106 and a telecommunications network 108. Mobile device 102 may send message 110, for example, when attempting setup, handover, or when attempting to manage a call in circuit switched domain 104. Message 112 may be transmitted to mobile device 102 from circuit switched network 104 and / or telecommunications network 108. Similarly, mobile device 102 may send message 114, for example, when attempting setup, handover, or when attempting to manage a call in packet-switched domain 106. Message 116 may be sent to mobile device 102 from packet switched network 104 and / or telecommunications network 108. Although shown as a separate entity, telecommunications network 108 may be part of circuit-switched and / or packet-switched networks 104 and 106 or may include circuit-switched and / or packet-switched networks 104 and 106. Can do.

  The mobile device 102 includes a device timer 118 that measures the length of time after a call is set up and before the message answers the call setup. In some embodiments, the mobile device 102 includes a voice call continuity (VCC) status checker 120, a memory 122 and a removable memory module 124. The removable memory module 124 may be a component such as a universal subscriber identification module, a removable user identification module, a secure digital card, a compact flash (registered trademark), or the like. Although FIG. 1 illustrates that the memory 122 includes data 126, the removable memory module 124 may alternatively include the data 126. Data 126 may maintain information about the subscriber or user (service subscriber subscription details, eg, whether the subscriber using mobile device 102 is a VCC subscriber).

  The mobile device 102 can be used by multiple users, each user having a different user identifier and subscribing to a different service. For example, one of the users of mobile device 102 may be a VCC subscriber and may subscribe to other services provided by telecommunications network 108 or the like. A user may lend or share the mobile device 102 to another user that subscribes to different services. Other users may not be VCC subscribers, for example. Prior to using the device, any user may insert his personal removable memory module 124, which specifically contains a list of subscribed services. Subscribers may also identify themselves by entering a private identity or a public identity that the network can map to a private identity.

  The VCC status checker 120 may read the data 126 to determine whether the mobile device 102 subscriber is a VCC subscriber. Subscription data 126 may be obtained and updated in various ways. In one embodiment, subscription data 126 is stored in removable memory module 124 during registration, for example when the mobile device is turned on and first communicates with telecommunications network 108 or during periodic re-registration. It can be embedded or acquired from the telecommunications network 108. The telecommunications network 108 may maintain a list of contracts for each consumer, user or subscriber and may provide contract information related to the current user of the mobile device 102. The VCC status checker 120 may also determine whether any VCC activity has been performed correctly for the subscriber by checking the data 126. For example, data 126 may be updated each time a VCC domain transfer is performed.

  Mobile device 102 has a first mode for communicating via circuit switched domain 104 and a second mode for communicating via packet switched domain 106. Module 128 may also include a VCC function that enables mobile device 102 to perform domain transfer of calls between circuit switched domain 104 and packet switched domain 106.

  Telecommunications network 108 communicates with circuit switched domain 104 and packet switched domain 106. The telecommunications network 108 includes a network timer 130 that measures the length of time after the telecommunications network 108 sends a message and before receiving an acknowledgment of the message. obtain.

  FIG. 2 is a block diagram of an embodiment of a system 200 that includes a mobile device 102, a telecommunications network 108, a serving call session control function (S-CSCF) 204, a VCC server 206, and Another telecommunication network 202 is included. Another communication network 202 is provided as an example of a network in which a party to a call makes a call to or receives a call from the mobile device 102.

  The S-CSCF 204 is an IP Multimedia Subsystem (IMS) packet switched base component, which can be considered a SIP server. The VCC server 206 is a component to which calls that can be transferred between circuit switched and packet switched domains are typically anchored. As can be easily understood by those skilled in the art, in this embodiment, the VCC server 206 includes a Domain Transfer Function (DTF), a CS Selection Function (CSAF), a Domain Selection Function (DSF), and a Camel Service PP. TS) 23.206. During setup, a registration process takes place, during which the mobile device 102 designates an S-CSCF 204 that is capable of performing both circuit-switched and packet-switched calls, and a VCC anchor (eg, a VCC server). 206) specify the components that can function. S-CSCF 204 and VCC server 206 may be part of telecommunications network 108.

  FIGS. 3 and 4 are call flow diagrams 300 and 400 illustrating an example of a series of events that may occur between the mobile device 102 and the communication network 104. In some embodiments, the protocol used for call attempts in the circuit switched domain is UTRAN (UMTS Terrestrial Radio Access Network), and the protocol used for call setup in the packet switched domain is SIP. is there. Other circuit switched protocols and / or packet switched protocols may be used in other embodiments.

  FIG. 3 is a call flow diagram 300 illustrating an example of a series of events that may include VCC services with the mobile device 102 and the telecommunications network 108. At Event 302, the mobile device 102 initiates call setup in the circuit switched domain with the telecommunications network 108 or network node. In this embodiment, the protocol used for call setup in the circuit switched domain is UMTS per 3GPP TS 24.008, although other protocols may be used. Mobile device 102 may be configured based on operator policies and / or user preferences. Establishment of VCC server 206 as a VCC anchor for the call may also occur at event 302.

  Device timer 118 initiates event 302 when a setup message is sent by mobile device 102 to telecommunications network 108. The telecommunications network 108 must provide VCC specific information to the mobile device 102 until the timer expires, otherwise the mobile device 102 has no VCC contract or the call is VCC anchored. It can be assumed that it is not. Such information may be provided by protocols such as USSD, SMS, SIP.

  At Event 304, telecommunications network 108 sends a message (eg, message 112) to mobile device 102. The content of the message is based on the VCC state determined by the telecommunications network 108 for the mobile device 102 and the current mobile device 102 subscriber. The telecommunication network 108 may determine the VCC status based on whether the mobile device 102 subscriber is a VCC subscriber or based on whether the call is anchored to the VCC server 206. If the call setup by the mobile device 102 is anchored to the VCC server 206, the subscriber using the mobile device 102 is a VCC subscriber because the call should only be anchored to the VCC server 206 for the VCC subscriber. Can be inferred. The call anchored to the VCC server 206 suggests that the telecommunications network 108 has already determined that the subscriber of the mobile device 102 is a VCC subscriber and is anchoring the call accordingly. The telecommunications network 108 includes data identifying subscribers that are VCC subscribers.

  The message may indicate that the subscriber currently registered with the mobile device 102 is a VCC subscriber. The message may also indicate that the subscriber currently registered with the mobile device 102 is not a VCC subscriber. In addition, the message may indicate that the subscriber currently registered with the mobile device 102 is a VCC subscriber but domain transfer is not permitted. Domain forwarding, for example, may allow the telecommunication network 108 to determine that the VCC server 206 is currently over capacity and cannot handle any further traffic.

  The VCC status checker 120 determines the VCC status for the mobile device 102 by reading parameters in response to a message sent by the telecommunications network 108 at event 304. The mobile device 102 uses the VCC state to determine whether to transfer the active call to the domain and whether to drop the inactive call. If the message from the telecommunications network 108 indicates that the call is not anchored to the VCC server 206 and / or indicates that the subscriber is not a VCC subscriber, the mobile device 102 may Or may not attempt to drop the inactive call and may not attempt domain transfer. If the message indicates that the subscriber is a VCC subscriber and / or that the call is VCC anchored, the mobile device 102 drops the inactive call and performs the VCC. In other embodiments, the present disclosure similarly provides transfer of both active calls and one or more inactive calls.

  The mobile device 102 also stops the device timer 118 upon receiving a response message at event 304. If the device timer 118 expires before the mobile device 102 receives the response message from the telecommunications network 108, the mobile device 102 indicates that the subscriber is not a VCC subscriber or that the call is not VCC anchored. Can be determined.

  The telecommunications network 108 may retransmit the response message sent at event 304. The number of times the telecommunications network 108 attempts to resend the response message is configurable. The message may be transmitted using various data transfer protocols, such as GSM, SIP, Code Division Multiple Access (CDMA), Universal Mobile Telecommunications System (UMTS), and the like.

  FIG. 4 is a call flow diagram 400 illustrating examples of events that may occur when the mobile device 102 registers with the telecommunications network 108. It is well known in the art that a mobile device undergoes a registration process, and in the registration process the mobile device specifies its capabilities. The mobile device 102 initiates the registration process when the mobile device 102 is turned on, but the mobile device 102 may also initiate the registration process after an extended period of inactivity of the mobile device 102.

  Since the mobile device 102 subscriber may change when the mobile device is turned off, the mobile device 102 initiates the registration process each time the mobile device 102 is turned on. In this way, the telecommunication network 108 and / or the computer network with which the mobile device 102 can communicate is whether the mobile device 102 is a dual mode or single mode device, and the mobile device 102 provides VCC functionality. It can be recognized whether or not the module 128 is included.

  At Event 402, the mobile device 102 initiates a process in the circuit switched domain by sending a registration message, for example by sending a message 110 to the telecommunications network 104. The protocol used for the registration message may be a protocol such as SIP register, CDMA Register, GPRS attach.

  The device timer 118 is started at event 402 when a registration message is sent by the mobile device 102 to the telecommunications network 108. The telecommunications network 108 must provide VCC-specific information to the mobile device 102 until the timer expires, otherwise the mobile device 102 may indicate that the subscriber is not a VCC subscriber or the VCC It can be assumed that the function is not available.

  At Event 404, the telecommunications network 108 sends an optional acknowledgment message (eg, message 112). The optional acknowledgment message is an acknowledgment that the telecommunications network 108 has received a registration message sent by the mobile device at event 402.

  At Event 406, telecommunications network 108 sends a message (eg, message 112) to mobile device 102. The message may be transmitted using a method such as SMS, Unstructured Supplementary Service Data (USSD), or Internet Protocol (IP) transport. The message includes registration information used to configure the mobile device 102 for operation. The message may also include parameters based on the VCC contract status determined by the telecommunications network 108 for the mobile device 102. The telecommunications network 108 may determine the VCC status based on whether the mobile device 102 subscriber is a VCC subscriber. The telecommunications network 108 includes data that identifies which subscribers are VCC subscribers.

  The VCC status checker 120 determines the VCC status for the mobile device 102 by reading parameters in the response message sent by the telecommunications network 108 at event 406. After event 406, mobile device 102 uses the VCC state to determine whether to transfer the active call to the domain and whether to drop the inactive call.

  When the mobile device 102 receives the response message at event 406, the mobile device 102 stops the device timer 118. If the device timer 118 expires before the mobile device 102 receives a response message from the telecommunications network 108, the mobile device 102 indicates that the subscriber is not a VCC subscriber or that the VCC is currently in the telecommunications network 108. It can be determined that it is not available.

  In other embodiments, the mobile device 102 may determine the VCC status without communicating with the telecommunications network 108. Instead, the VCC status checker 120 on the mobile device determines the VCC status of the mobile device 102 by checking the VCC status information stored in the mobile device 102. Information may be stored in the memory 122 or the removable memory module 124 of the mobile device 102. The storage device may include data 126 that identifies, for example, a subscriber or whether the subscriber is a VCC subscriber. Subscribers can use the International Mobile Subscriber Identifier (IMSI), IMS Protocol Multimedia Private User Identity (IMPI) examples. It may include an identification system such as TS 23.003, Mobile Identifier Number (MIN). The mobile device 102 uses the VCC state to determine how to handle the VCC activity, for example, drop an inactive call and transfer an active call. The data 126 may also be configurable by various wireless mechanisms, such as wireless SMS (Short Message Service), OMA / DM (Open Mobile Alliance Device Management) or dedicated or other methods.

  In still other embodiments, the above-described combination of VCC states may be used. For example, if the VCC state is determined during registration, the removable memory module 124 on the mobile device 102 or somewhere on the mobile device 102 can be stored. A flag is set when the removable memory module 124 is removed or changed to indicate that the VCC state needs to be updated. However, as long as the same removable memory module 124 is used in the mobile device 102, the VCC state stored in the memory is up-to-date.

  While communicating with the mobile device 102, the network timer 130 may be used at various times to determine whether the mobile device is available for VCC. The network timer can be started in response to a message sent by the mobile device. The mobile device 102 must then provide the mobile device's VCC capability information to the telecommunications network 108 by the time the timer expires, otherwise the telecommunications network 108 may allow the mobile device 102 to use the VCC. It can be assumed that this is not possible.

  FIG. 5 is a diagram of a method for identifying whether a subscriber is a VCC subscriber, according to one embodiment. In box 602, the mobile device 102 communicates via the circuit switched domain 104 for the active first call. For example, the user of the mobile device 102 places a voice call or is currently on a voice call. In box 604, the mobile device 102 communicates over the circuit switched domain 104 for the inactive second call. For example, the mobile device 102 receives a second call and puts it on call waiting, or the user of the mobile device 102 places the second call on hold.

  In box 606, the mobile device 102 identifies accessibility to the packet switched domain 106. For example, while participating in a first active call and a second inactive call, the user comes close to the wireless access point and provides accessibility to the packet network. It may be beneficial to transfer from the circuit switched domain 104 to the packet switched domain 106 at this point, for example by providing a cheaper call.

  In box 692, the VCC status checker 120 determines the VCC status associated with the mobile device 102. In box 696, the VCC status checker 120 determines whether the subscriber of the mobile device 102 is a VCC subscriber. For example, the VCC status checker 120 determines the VCC status by reading parameters in a response message sent by the telecommunications network 108 during call setup or registration. Alternatively, the VCC status checker 120 determines the VCC status for the mobile device 102 by checking the storage device for subscriber subscription information.

  In box 698, the VCC state checker 120 determines whether the call of the mobile device 102 is anchored to the VCC server 206. For example, the VCC status checker 120 reads the parameters in the response message sent by the telecommunications network 108, or determines whether the call is anchored to the VCC server, thereby determining the VCC status for the mobile device 102. decide. One or both of blocks 696 or 698 may be performed in various embodiments. Although FIG. 5 shows boxes 692, 696, and 698 between boxes 606 and 608, boxes 692, 696, and 698 are in other locations in other embodiments (eg, boxes 602 and 604). Before).

  In box 608, the VCC state checker 120 determines whether the mobile device 102 can attempt a domain transfer based on the determined VCC state. The VCC status checker 120 determines that the mobile device 102 can attempt a domain transfer and the method proceeds to box 610.

  In box 610, the mobile device 102 drops the second inactive call and attempts a domain transfer to the packet switched domain 106 for the first active call. For example, because domain transfer to the packet switched domain 106 has a higher priority than maintaining an inactive call, the mobile device 102 drops the inactive call and for the active call from the circuit switched domain 104 to the packet switched domain. Attempt domain transfer to 106. In other embodiments, both active and inactive calls can be VCC domains that are forwarded to the packet switched domain.

  If the VCC status checker 120 determines in box 608 that the mobile device 102 may not attempt domain transfer, the method proceeds to block 612. In box 612, the mobile device 102 maintains the second inactive call and does not attempt a domain transfer to the packet switched domain 106. For example, since the VCC state indicates that domain transfer is not currently allowed for the user of mobile device 102, mobile device 102 does not attempt domain transfer to packet-switched domain 106 for active calls. Furthermore, the mobile device 102 does not drop the inactive call. Although only two calls have been described, the present disclosure contemplates a situation involving any number of active calls and inactive calls.

  Although this disclosure describes domain forwarding from circuit switched domain 104 to packet switched domain 106, the present disclosure also applies to domain forwarding from packet switched domain 106 to circuit switched domain 104 in other embodiments. Can be applied. In any case, the functionality of mobile device 102 applies equally whether or not the subscriber is a VCC subscriber and whether or not the call is VCC anchored. Further, although the present disclosure has been applied in examples that include one or more inactive calls, in other embodiments, the present disclosure can also be applied in examples where there are no inactive calls.

  FIG. 6 illustrates a wireless communication system that includes one embodiment of a mobile device 102. Although the mobile device 102 is operable to implement aspects of the present disclosure, the present disclosure should not be limited to these implementations. Although shown as a mobile phone, the mobile device 102 may take various forms including a wireless handset, pager, personal digital assistant (PDA), portable computer, tablet computer, laptop computer. Many suitable mobile devices combine some or all of these functions. In some embodiments of the present disclosure, the mobile device 102 is not a general purpose computing device such as a portable, laptop or tablet computer, but rather an application specific communication device such as a mobile phone, wireless handset, pager or PDA. It is. In another embodiment, the mobile device can be a portable, laptop, or other computing device.

  Mobile device 102 includes a display 702. The mobile device 102 may also include input keys such as touch-sensitive surfaces, keyboards, etc., for input by the user, these are generally referred to as 704. The keyboard is a sequence type full or reduced alphanumeric keyboard such as QWERTY, DVORAK, AZERTY, or a traditional numeric keypad with letters associated with the telephone keypad. It can be. Input keys may include navigation keys or function keys such as a track wheel, exit or escape key, trackball, etc., which may provide additional input functions when pressed inward. The mobile device 102 may provide the user with options for selection, control, provide the user with options for activation, and / or provide instructions to the user, such as a cursor for instructions. The mobile device 102 may further accept data input from a user including a dial number or various parameter values for configuring the operation of the mobile device 102. These applications may configure mobile device 102 to perform various customized functions in response to user interaction.

  Among other applications, an application that can be executed by the mobile device 102 is a web browser that allows the display 702 to display a web page. The web page is obtained via wireless communication with the cell tower 706, a wireless network access node, or any other wireless communication network or system. Cell tower 706 (or wireless network access node) is coupled to wired network 708 (eg, the Internet). Via a wireless link or wired network, the mobile device 102 accesses information on various servers (eg, server 710). Server 710 may provide content that may be shown on display 702.

  FIG. 7 shows a block diagram of the mobile device 102. Mobile device 102 includes a digital signal processor (DSP) 802 and memory 804. As shown, mobile device 102 further includes antenna and front-end unit 806, radio frequency (RF) transceiver 808, analog baseband processing unit 810, microphone 812, earpiece speaker 814, headset port 816, input / Output interface 818, removable memory card 820, universal serial bus (USB) port 822, short range wireless communication subsystem 824, alert 826, keypad 828, liquid crystal display (LCD) 830 that may include touch sensitive surfaces, LCD controller 832, a charge coupled device (CCD) camera 834, a camera controller 836, and a global positioning system (GPS) sensor 838.

  The DSP 802 or some other type of controller or central processing unit operates to control various components of the mobile device 102 in accordance with software or stored firmware embedded in the memory 804. The DSP 802 executes other applications stored in the memory 804 in addition to the embedded software or firmware, or via an information carrying medium such as a portable data storage medium such as a removable memory card 820, for example. Alternatively, it may be made available via wired network communication or wireless network communication. The application software may include a compiled set of machine-readable instructions that configure the DSP 802 to provide the desired functionality, or the application software may be an interpreter or compiler to indirectly configure the DSP 802 It can be a high level software instruction processed by.

  An antenna and front end unit 806 may be provided to convert between wireless and electrical signals and for the mobile device 102 to send and receive information from a cellular network or other available wireless communication network. The RF transceiver 808 provides frequency shifting, converting received RF signals to baseband, and converting baseband transmission signals to RF. The analog baseband processing unit 810 can provide channel equalization and signal demodulation to extract information from the received signal, can modulate information to form a transmission signal, and can analogize audio signals. Filtering may be provided. To that end, the analog baseband processing unit 810 may have a port for connecting to a built-in microphone 812, an earpiece speaker 814, which allows the mobile device 102 to be used in a cell phone. The analog baseband processing unit 810 may further include a port for connecting to a headset or other hands-free microphone and speaker configuration.

  The DSP 802 may send and receive digital communications with the wireless network via the analog baseband processing unit 810. In some embodiments, these digital communications provide Internet connectivity, allow users to gain access to content on the Internet, and allow users to send and receive email or text messages. Can make it possible. Input / output interface 818 interconnects DSP 802 with various memories and interfaces. Memory 804 and removable memory card 820 may provide software or data for configuring the operation of DSP 802. Among other interfaces, the USB interface 822 and the short-range wireless communication subsystem 824 may be important. The USB interface 822 may be used to charge the mobile device 102 or may be used to allow the mobile device 102 to exchange information with a computer system such as a personal computer by functioning as a peripheral device. Can do. The short range wireless communication subsystem 824 is an infrared port, Bluetooth interface, IEEE 802.11 compliant wireless interface, or optional that allows the mobile device 102 to wirelessly communicate with other nearby mobile devices and / or wireless base stations. Other short-range wireless communication subsystems.

  The input / output interface 818 may further connect the DSP 802 to an alert 826, which when triggered triggers the mobile device 102 to notify the user, for example, by a ring tone, melody performance, or vibration. Like that. The alert 826 can be any of a variety of events, such as incoming calls, new text messages and appointment reminders, by silently vibrating or playing a specific melody pre-designated for a particular caller. It can function as a mechanism for warning the user.

  Keypad 828 couples to DSP 802 via interface 818 to provide the user with one mechanism for making selections, entering information, and providing input to mobile device 102. The keypad 828 is a sequence type full or reduced alphanumeric keyboard such as QWERTY, DVORAK, AZERTY, etc., or a traditional numeric keypad with letters associated with a telephone keypad It can be. Input keys may include navigation keys or function keys such as a track wheel, exit or escape key, trackball, etc., which may provide additional input functions when pressed inward. Another input mechanism may be an LCD 830, which may include touch screen functionality and may display text and / or graphics to the user. LCD controller 832 couples DSP 802 to LCD 830.

  CCD camera 834, if implemented, allows mobile device 102 to take a digital picture. The DSP 802 communicates with the CCD camera 834 via the camera controller 836. The GPS sensor 838 is coupled to the DSP 802 to decode the global positioning system signal, thereby allowing the mobile device 102 to determine its location. Various other peripheral devices may also be included to provide additional functionality (eg, radio and television reception).

  FIG. 8 illustrates a software environment 902 that may be implemented by the DSP 802. The DSP 802 executes an operating system driver 904 that provides a platform from which the rest of the software operates. The operating system driver 904 provides a standardized interface to mobile device hardware drivers that allows access to application software. The operating system driver 904 includes an application management service (AMS) 906 that transfers control between applications executing on the mobile device 102. A web browser application 908, a media player application 910, and a Java applet 912 are also shown in FIG. The web browser application 908 operates as a web browser and allows a user to extract and view web pages by entering information into a form and selecting a link. The mobile device 102 is configured. Media player application 910 configures mobile device 102 to extract and play audio and audiovisual media. The Java (registered trademark) applet 912 configures the mobile device 102 so as to provide functions such as games and utilities. The component 914 may be substantially similar to the VCC status checker 120 of FIG. 1, which reads the data 126, determines whether the mobile device 102 subscriber is a VCC subscriber, a call Can be checked to determine if any of the VCC activities have been performed correctly for the subscriber. Component 914 can also be a firmware component, a hardware component, or a combination of software, firmware and / or hardware.

  Although several embodiments have been provided in the present disclosure, the disclosed systems and methods can be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The examples herein are to be considered merely illustrative and not limiting, and the intention should not be limited to the details given herein. For example, various elements or components may be combined or integrated in another system, or certain features may be omitted or not implemented.

  In addition, the techniques, systems, subsystems and methods described and illustrated separately or separately in various embodiments may be combined with other systems, modules, techniques or methods without departing from the scope of the present disclosure. Can be combined or integrated. Other items shown or discussed as being coupled, directly coupled, or communicating with each other, via any interface, device, or intermediate component, It can be coupled or communicated electrically, mechanically, or otherwise indirectly. Those skilled in the art will recognize, and be able to implement other examples of modifications, substitutions, and substitutions without departing from the spirit and scope disclosed herein.

Claims (25)

A voice call continuity state checker configured to determine a voice call continuity state and, based on the voice call continuity state, to determine whether to initiate an activity related to the voice call continuity; Mobile device.   The voice call continuity state checker communicates over a circuit switched domain for a first call and an inactive second call when the mobile device is active, and when the mobile device uses the voice call continuity state , Further configured to determine whether to initiate an activity related to voice call continuity, wherein the activity related to voice call continuity disconnects the second call and for the first call The mobile device of claim 1, comprising attempting domain transfer to a packet switched domain.   The mobile device according to claim 2, wherein the second call is one of a held call or a call waiting call, and the first call and the second call are voice calls.   The mobile device of claim 1, wherein the voice call continuity status checker is further configured to determine whether a subscriber of the mobile device is a voice call continuity subscriber.   The voice call continuity status checker is further configured to determine whether the subscriber of the mobile device is a voice call continuity subscriber by checking a storage device on the mobile device. The mobile device according to claim 4.   The voice call continuity status checker includes a mobile device memory and a removable memory module including one of a subscriber identity module, a universal subscriber identity module, a removable user identity module, a secure digital card, and a compact flash. The mobile device of claim 5, further configured to select a storage device from the group consisting of:   The voice call continuity status checker is further configured to determine whether the subscriber of the mobile device is a voice call continuity subscriber based on parameters of a message from a telecommunications network provider system. The mobile device according to claim 4.   The mobile device of claim 7, wherein the voice call continuity status checker is further configured to determine during a registration process.   The mobile device of claim 7, wherein the voice call continuity status checker is further configured to determine during a call setup process.   The voice call continuity status checker is further configured to determine a voice call continuity status based on whether a mobile device call is anchored to a voice call continuity server. Mobile device. The mobile device is
A communication module having a first mode for communicating via a circuit switched domain and having a second mode for communicating via a packet switched domain;
The mobile device of claim 1, further comprising: a voice call continuity module configured to enable voice call continuity for the mobile device. A communication method for a mobile device,
Determining the voice call continuity state;
Determining whether to initiate an activity related to voice call continuity based on the voice call continuity state.   Determining the voice call continuity state includes determining whether a subscriber using the mobile device is a voice call continuity subscriber and the mobile device call is anchored to a voice call continuity server. The method of claim 12, further defined as at least one of determining whether or not. Having a first active call via a circuit switched domain;
Having a second inactive call through the circuit switched domain;
Determining whether to initiate an activity related to voice call continuity in response to the voice call continuity state, the activity dropping the second call; and The method of claim 13, comprising: attempting domain transfer to the packet switched domain. 15. The method of claim 14, further comprising: maintaining the second inactive call and not attempting the domain transfer to the packet switched domain when a subscriber using the mobile device is not a voice call continuity subscriber. The method described. 15. The method of claim 14, further comprising: maintaining the second inactive call and not attempting the domain transfer to the packet-switched domain when the mobile device is not anchored to a voice call continuity server. Method.   The voice call continuity state indicates whether the subscriber of the mobile device is a voice call continuity subscriber and whether a call made by the mobile device is anchored to a VCC server. 14. The method of claim 13, further defined to determine in between.   The method of claim 13, wherein determining the voice call continuity state is further defined to determine whether the subscriber of the mobile device is a voice call continuity subscriber.   Determining the voice call continuity state means that the subscriber of the mobile device is voiced by checking a parameter in a message from a telecommunications network indicating whether the subscriber is a voice call subscriber. 14. The method of claim 13, further defined to determine whether or not a call continuity subscriber.   Determining the voice call continuity state may include determining whether the call made by the mobile device is by checking a parameter in a message from a telecommunications network indicating whether the call is anchored at the VCC server. The method of claim 13, further defined to determine whether it is anchored to the VCC server.   Determining the voice call continuity state includes checking the memory on the mobile device for data indicating that the subscriber is a voice call continuity subscriber, so that the subscriber of the mobile device 14. The method of claim 13, further defined to determine whether or not a voice call continuity subscriber. When executed
Determining the voice call continuity state;
Using the voice call continuity for activities related to voice call continuity.   Determining the voice call continuity state includes determining whether a subscriber using the mobile device is a voice call continuity subscriber and the mobile device call is anchored to a voice call continuity server. 23. The machine instruction of claim 22, further defined as at least one of determining whether or not.   Using the voice call continuity state for activities related to voice call continuity determines whether to drop the call and whether to initiate a domain transfer based on the call continuity state 24. The machine instruction of claim 23, comprising: determining. When the mobile device has a first active call through a circuit switched domain and has a second inactive call through the circuit switched domain, and further when a packet switched domain is identified, the machine instructions are: When executed
When the subscriber is a voice call continuity subscriber and the call is anchored to the voice call continuity server, drop the second call and for the first call to the packet switched domain Attempting a domain transfer,
Maintaining the second inactive call in the circuit switched domain when the call is not anchored and not attempting domain transfer to the packet switched domain for the first active call. 24. The machine instruction of claim 23, further executed.

Images