Patent Application
20140269611
Use of packet-switched connections for transmitting synchronous communications, such as voice calls, and data across telecommunication networks is increasing. Such packet-switched connections allow for greater speed and throughput, while making packet-switched data from other networks, such as the Internet, more readily available. Most telecommunication networks, however, still utilize access networks that provide circuit-switched connections, such as Global System for Mobile Communications (GSM) networks or Universal Mobile Telecommunications System (UMTS) networks, due to the substantial infrastructure investment needed to expand packet-switched access networks. Such circuit-switched access networks may provide comparable or, at times, better speed and quality than packet-switched access networks for some types of data, including synchronous communications.
Because packet-switched access networks are not available to the same extent as circuit-switched access networks, techniques have been developed for switching from one of type of packet-switched access network—the Long Term Evolution (LTE) access network—to circuit-switched access networks while maintaining continuity for a communication session, such as a voice call. One technique for handover of a communication session from a LTE access network to a circuit-switched access network involves the use of the Third-Generate Partnership Project (3GPP)'s single radio voice call continuity (SRVCC) standard. With SRVCC, an eNode B of a LTE access network determines that a communication session handover should occur based on a measurement report received from a user device. The eNode B communicates this to a mobility management entity (MME), which makes a handover request of a mobile switching center (MSC) server of a circuit-switched access network that is available to the user device. The MSC server then prepares the circuit-switched access network for the handover, and communicates with an Internet Protocol (IP) multimedia subsystem (IMS) of the telecommunication network, the IMS maintaining continuity for the communication session during the handover. The MSC server then sends a handover response to the MME, and the MME instructs the user device to connect to the circuit-switched access network to continue the communication session.
The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.
This disclosure describes, in part, a telecommunication network device configured to initiate a handover of a communication session of a user device from an access network associated with unlicensed spectrum, such as a WiFi access network, to a circuit-switched access network. The telecommunication network device may be a gateway device, such as an evolved packet data gateway (ePDG). The telecommunication network device may provide a handover request to a server associated with the circuit-switched network, such as a MSC server, receive a response from the server indicating that the circuit-switched access network has been prepared for the handover, and instruct the user device connect to the circuit-switched access network to continue the communication session. The telecommunication network device may initiate the handover responsive to measurement reports received from the user device. In some embodiments, the telecommunication network device may also enable registration of the communication session when that session is first initiated by the user device. Also, the telecommunication network device may determine a session transfer number identifying one or more components of the telecommunication network which maintain continuity for the communication session, such as an IMS of the telecommunication network, and provide that session transfer number to the server associated with the circuit-switched access network as part of the handover request.
The user device 106 may be any sort device capable of cellular or wireless network communication, such as a cellular phone, a tablet computer, a personal digital assistant (PDA), a personal computer (PC), a laptop computer, a media center, a work station, etc. An example user device 106 is illustrated in
In some embodiments, the user device 106 may have a radio and be configured to tune that radio to licensed wireless spectrum utilized by circuit-switched access networks and packet-switched access networks, such as LTE access networks. The user device 106 may also be configured to tune the radio to unlicensed wireless spectrum utilized by packet-switched access networks, such as WiFi access networks or WiMax access networks. When equipped with a single radio, the user device 106 may only be connected to one of these access networks at a time.
The user device 106 may further be configured to initiate or receive a communication session, such as a voice call, a video call, or another sort of synchronous communication. Initiation of such communications may involve communication clients and session initiation protocol (SIP) clients to communicate with session continuity components 114 of the telecommunication network. Both the initiation of a communication session and the components involved in the initiation are illustrated in
In various embodiments, the user device 106 may measure access networks that are proximate to the user device 106 and provide measurements of those access networks in a measurement report to a device of the telecommunication network, such as telecommunication network device 102. The measurements may include signal strength, packet loss, packet discard, or network congestion. The proximate access networks may include both access networks that are detected by the user device 106 and those of neighboring cells, which the user device 106 may learn of from the telecommunication network. The proximate access networks also include both access networks associated with licensed spectrum, and access networks associated with unlicensed spectrum.
The user device 106 may initiate the communication session using a connection to the access network 108 associated with the unlicensed spectrum (e.g., as a WiFi voice call). In various embodiments, the access network 108 associated with unlicensed spectrum may be a WiFi access network, a WiMax access network, or any other type of wireless access network that utilizes unlicensed spectrum. The access network 108 may be provided by a wireless router, such as a router operating in accordance with IEEE 802.11 standards. Such routers send and receive data in packets, such as IP packets, and use packet-based communication standards, such as the Transmission Control Protocol (TCP)/IP standard. As such, the access network 108 is a packet-based (also known as “packet-switched”) access network. The access network 108 may be secured by, for example, requiring a login, key, or other form of authentication, or may be unsecure. The access network 108 connects the user device 106 to a telecommunication network by communicating with the telecommunication network over a public network, such as the Internet. The router of the access network 108 may communicate with a device of the telecommunication network, such as the telecommunication network device 102, which sits at the edge of the telecommunication network. In some embodiments, the communication session may be secured (e.g., by encryption or tunneling) when communicated over the public network.
The telecommunication network device 102 may be a gateway device, such as an ePDG. An example telecommunication network device 102 is illustrated in
In various embodiments, the telecommunication network device 102 may enable the user device 106 to initiate the communication session by passing messages to appropriate device(s) of the telecommunication network, such as the session continuity components 114. The telecommunication network device 102 may also receive measurement reports from the user device 106 and may apply one or more models, thresholds, rules, or criteria to the measurements included in the measurement reports to determine whether a handover 104 is appropriate. For example, if the signal strength of the access network 108 falls below a threshold, the telecommunication network device 102 may initiate the handover 104. In other embodiments, the telecommunication network device 102 may select a circuit-switched access network 110 that is not included in the measurement reports to receive the handover. For example, the measurement reports may include measurements associated with the access network 108 and with a LTE access network, but no measurements for the circuit-switched access network 110. The telecommunication network device 102, as part of the telecommunication network, may have access to measurements of the circuit-switched access network 110, however, and may use those measurements in conjunction with those provided in the measurement reports in making a handover decision.
Upon initiating a handover 104, the telecommunication network device 102 selects a circuit-switched access network 110 to transition the communication session to. For example, the telecommunication network device 102 may select the circuit-switched access network 110 based on signal congestion levels of the circuit-switched access networks included in the measurement report. The telecommunication network device 102 may then determine the server 112 associated with the selected circuit-switched access network 110 by referencing mappings, such as a table.
As part of the handover 104, the telecommunication network device 102 may send instructions to the user device 106 preparing the user device 106 for the handover 104. Such instructions may include a directive to automatically tune the radio of the user device 106 to the circuit-switched access network 110 if the user device 106 has not heard from the telecommunication network device 102 within a threshold period of time.
The telecommunication network device 102 then sends a handover request, such as a SRVCC packet-switched (PS) to circuit-switched (CS) request. The request may be made over an interface between the telecommunication network device 102 and the server 112 or through a MME, which may have an SV interface with the server 112. The handover request may include at least information identifying the user device 106, such as an international mobile subscriber identity (IMSI), information identifying the communication session, such as a correlation mobile station international subscriber directory number (C-MSISDN), and an identifier of the session continuity components 114, such as a session transfer number-single radio (STN-SR).
In some embodiments, the server 112 may be an MSC server associated with the circuit-switched access network 110. The circuit-switched access network 110 may be any sort of circuit-switched access network 110, such as a GSM or UMTS network. The circuit-switched access network 110 may also be referred to as a universal terrestrial radio network (UTRAN) or a GSM EDGE radio access network (GERAN) and may include a base station or Node B, as well as a radio network controller (RNC). The circuit-switched access network 110 may provide circuit-switched connections over a given signal spectrum and may use any sort of air interface, such as a code division multiple access (CDMA), time division multiple access (TDMA), or frequency division multiple access (FDMA) air interface. Communications received by the circuit-switched access network 110 from the user device 106 are transmitted to a server 112 of the telecommunication network, such as an MSC server.
Upon receiving a handover request, the server 112 prepares the circuit-switched access network 110 for the handover 104 by, for example, allocating resources at a base station and RNC of the circuit-switched access network 110. The server 112 also uses the identifier of the session continuity components 114 included in the handover request to request that the session continuity components perform a session transfer. The session transfer enables the handover 104 to occur without loss of continuity to the communication session.
In various embodiments, the session continuity components 114 represent components of an IMS of the telecommunication network. Examples of such components, and of the session transfer, are described further herein. Upon receiving a session transfer request from the server 112 and performing the session transfer, the session continuity components 114 respond to the server 112, indicating completion of the session transfer.
In further embodiments, upon receiving a response indicating completion of the session transfer, and after preparing the circuit-switched access network 110 for the handover 104, the server 112 send a handover response, such as an SRVCC PS to CS response, to the telecommunication network device 102. The telecommunication network device 102 then instructs the user device 106 to tune its radio to the circuit-switched access network 110 in order to connect to the circuit-switched access network 110 and continue the communication session. Upon receiving such instructions, the user device 106 carries them out, completing the handover 104.
The telecommunication network may also include a number of devices or nodes not illustrated in
The devices and networks illustrated in
The devices and networks of
In initializing the communication session, the user device 204 must register the communication session with the IMS 210 of the telecommunication network. To do this, the user device 204 sends an initiation SIP register request to the IMS 210 via the WiFi access point 206, public network 208, and gateway device 202. The gateway device 202 may transmit the SIP register request to the IMS 210 directly or through a packet data network gateway (PDN-GW) of the telecommunication network. A P-CSCF of the IMS 210 may receive the SIP register request, and may provide the SIP register request to the ATCF/ATGW 220 of the IMS 210. The ATCF/ATGW 220 allocates a session transfer number, such as an STN-SR, and includes the STN-SR in the SIP register request to ensure that the ATCF is included in the signaling path for future SIP requests, such as session transfer requests from MSC servers 212. The ATCF/ATGW 220 then sends the SIP register request to an interrogating call session control function (I-CSCF)/serving call session control function (S-CSCF), which in turn sends the SIP register request to the SCCAS 224. Alternatively, the STN-SR may be allocated by and associated with the SCCAS 224. The SCCAS 224 then sends a pull message to the HLR/HSS 222 to determine whether the user device 204 is SRVCC capable and to retrieve an STN-SR stored in the HLR/HSS 222. If the STN-SR received from the HLR/HSS 222 differs from the STN-SR included in the SIP register request, the SCCAS 224 updates the HLR/HSS 222 with the STN-SR included in the SIP register request. The SCCAS 224 may then send a SIP register response to the user device 204 to complete the IMS registration of the communication session.
In various embodiments, the gateway device 202 determines the STN which identifies the IMS 210 during an attach procedure. As mentioned above, the STN-SR is an example of a STN. There are a number of different ways that the gateway device 202 can determine the STN during an attach procedure. A first option is for the STN to be statically defined and mapped to an ATCF 220 or SCCAS 224. In the first option, the gateway device 202 learns the P-CSCF address that the SIP register request is sent to, and retrieves the STN from a mapping of P-CSCFs to ATCFs/SCCASs and STNs. A second option is for the HLR/HSS 222 to send an Insert Subscriber Data message, which includes the STN, to the gateway device 202. The HLR/HSS 222 does this in response to the gateway device performing a subscriber update during the attach procedure. This second option creates a binding between the gateway device 202 and the HLR/HSS 220 for the user. In a third option, the gateway device 202 interacts with the MME 216 to have the MME 216 perform the location update and receive the STN via an Insert Subscriber Data message from the HLR/HSS 222. With this third option, the gateway device 202 would not receive the STN, but would instead act through the MME 216 during a handover, such as the handover 104. A fourth option is for the gateway device 202 would use a SIP subscribe/notify message to obtain the STN from the IMS 210.
An example handover 104 of a communication session of a user device 106 from an access network 108 associated with unlicensed spectrum to a circuit-switched access network 110 is describe above. In order to relate an example handover in further detail, and with reference to the devices and networks of
In various embodiments, the user device 204 may send measurement reports to the gateway device 202 via the WiFi access network and public network 208. The user device 204 measures access networks based on measurement gap instructions and includes those measurements in the measurement reports. Measurement gap instructions may be received by the user device 204 and utilized to create gaps in the communication session and to use those gaps to tune the radio to the different access networks and to obtain measurements for those access networks. The measurement gap instructions may be provided by the gateway device 202 or by any other node or device of the telecommunication network.
These measurement reports may include measurements of the WiFi access network, of a circuit-switched access network provided by the CS base station 214, and of a LTE access network provided by the eNode B 218. Alternatively, they may include only measurements of a subset of those access networks. Such measurements may include signal strength, packet loss, packet discard, or network congestion. The gateway device 202 may apply models, thresholds, rules, or criteria to the measurements and may initiate a handover based on the application of those models, thresholds, rules, or criteria to the measurements. As mentioned above, the gateway device 202 may consider measurements for access networks not included in the measurement reports. For example, the measurement reports may include measurements for the WiFi access network and LTE access network, but not for the circuit-switched access network. The gateway device 202 may have access to measurements of the circuit-switched access network and may use those measurements, in conjunction with those reported in the measurement reports, in making the handover decision. Upon initiating the handover, the gateway device 202 may select the circuit-switched access network to receive the communication session. Such a selection may also be based on the measurement report, other measurements know to the telecommunication network, or both. The gateway device 202 may also send instructions to the user device 204 to prepare the user device for the handover. Such instruction may include, for example, a directive to automatically tune the radio of the user device to the circuit-switched access network if the user device 204 has not received a communication from the gateway device during a time period.
The gateway device 202 may then provide a handover request for the MSC server 212 associated with the selected circuit-switched access network. The gateway device 202 may determine the identity of the MSC server 212 by referencing mappings that associate MSC servers and circuit-switched access networks. The handover request may be a SRVCC PS to CS request and may include an IMSI for the user device 204, the STN-SR, a C-MSISDN for the communication session, a generic source to target transparent container, a mobility management (MM) context, and an emergency indication. The gateway device 202 may provide the handover request directly to the identified MSC server 212 through an interface. Such an interface may be similar to or the same as the SV interface between the MME 216 and the MSC server 212. Alternatively, the gateway device 202 may send a Handover Required Message to the MME 216 and utilize the MME 216 to make the handover request of the MSC server 212.
In various embodiments, upon receiving the handover request, the MSC server 212 performs resource allocation with the target CS base station 214 by exchanging handover request/acknowledgement messages with the CS base station 214. The MSC server 212 also initiates a session transfer by sending a SIP invite, which includes the STN-SR, to the IMS 210.
Because the STN-SR is included in the SIP invite, the SIP invite initiating the session transfer is received by whichever of the ATCF 220 or SCCAS 224 is associated with the STN-SR. If the STN-SR is associated with the SCCAS 224, the SCCAS 224 performs the handover of the session from the source access leg (i.e., the access leg for the WiFi access network) to the newly allocated CS leg (i.e., transmitting those packets using the circuit-switched access network) and causes the user device 224 and its communication partner device to communicate with each other to establish a new media path that utilizes the CS access leg. As part of performing the handover, the SCCAS 224 releases the source access leg, and the IMS 210 responds to the SIP invite of the MSC server 212, completing the session transfer.
If the STN-SR is associated with the ATCF 220, the ATCF 220 receives the SIP invite, switches the session from the source access leg to the CS access leg, sends a SIP invite to the SCCAS 224 to inform the SCCAS 224 of the switch and cause it to release the source access leg, and responds to the SIP invite of the MSC server 212, completing the session transfer. The media remains anchored at the ATGW 220 during the session transfer, and the conversation partner device is not made aware of session transfer.
The MSC server 212 then sends a handover response to the gateway device 202 (either directly or to the MME 216). Such a handover response may be a SRVCC PS to CS response, which may include a target to source transparent container. The gateway device 202 then sends a handover command message to the user device 204, instructing the user device 204 to tune its radio to the circuit-switched access network of the CS base station 214. Handover detection then occurs at the CS base station 214, and the CS base station 214 sends a handover complete message to the MSC server 212. The MSC server 212 may then send a SRVCC PS to CS complete notification message to the gateway device 202, and the gateway device 202 responds with an acknowledgment, completing the handover.
In various embodiments, system memory 302 is volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. The communication client(s) 304 stored in the system memory 302 may enable the user device 300 to initiate and carry on communication sessions. The communication client(s) 304 may include voice call handlers, video calling clients, gaming and media clients, etc. The communication client(s) 304 may utilize a policy, preferences, etc. in determining which of a number of available access networks the communication client(s) 304 should use in initiating communication sessions. For example, the communication client(s) 304 may utilize a policy or preference that prefers WiFi access networks to LTE access networks, and LTE access networks to circuit-switched access networks.
The SRVCC module 306 may perform a number of functions, such as interfacing with the radio 318 through the radio resource control 310, receiving instructions, such as measurement gap instructions, instructions preparing the user device 300 for a handover, and instructions to complete a handover by tuning the radio 318, performing measurements of access networks, generating measurement reports that include the measurements, and providing the measurement reports to the telecommunication network.
The SIP client 308 may participate with the communication client(s) 304 in initiating a communication session by, for example, formulating a SIP register request and sending the SIP register request to the telecommunication network.
The radio resource control 310 may, for example, be a radio resource control layer of the user device 300 and may interact with the radio 318 and other modules and components of the user device 300 in order to tune the radio 318 and communicate using the radio 318.
In some embodiments, the processor(s) 312 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or any other sort of processing unit.
User device 300 also includes additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
In some embodiments, the radio 318 includes any sort of radio known in the art. For example, radio 318 may be a radio transceiver that performs the function of transmitting and receiving radio frequency communications. The radio interface may facilitate wireless connectivity between the user device 300 and various cell towers, base stations and/or access points of access networks. The radio interface may further perform the function of transmitting and receiving wireless communications using, for example, the IEEE 802.11, 802.16 and/or 802.20 standards. The radio 318 may also include a wireless communication transceiver or a near field antenna for communicating over local wireless data networks and personal area networks (e.g., Bluetooth or near field communication (NFC) networks).
In various embodiments, the display 320 is a liquid crystal display or any other type of display commonly used in telecommunication devices. For example, display 320 may be a touch-sensitive display screen, and can then also act as an input device or keypad, such as for providing a soft-key keyboard, navigation buttons, or the like.
In some embodiments, the output devices 322 include any sort of output devices known in the art, such as a display (already described as display 320), speakers, a vibrating mechanism, or a tactile feedback mechanism. Output devices 322 also include ports for one or more peripheral devices, such as headphones, peripheral speakers, or a peripheral display.
In various embodiments, input devices 324 include any sort of input devices known in the art. For example, input devices 324 may include a camera, a microphone, a keyboard/keypad, or a touch-sensitive display (such as the touch-sensitive display screen described above). A keyboard/keypad may be a push button numeric dialing pad (such as on a typical telecommunication device), a multi-key keyboard (such as a conventional QWERTY keyboard), or one or more other types of keys or buttons, and may also include a joystick-like controller and/or designated navigation buttons, or the like.
In various embodiments, system memory 402 is volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. The handover module 404 stored in the system memory 402 may perform a number of functions, including initiating a handover of a communication session based on measurement reports, selecting a circuit-switched access network for the handover, providing a handover request to a server associated with the circuit-switched access network, either directly or through an MME, receiving a handover response, and instructing the user device to connect to the circuit-switched access network to complete the handover. The handover module 404 may also provide measurement gap instructions to a user device and instruct the user device to prepare for a handover.
The mapping and STN data 406 may include mappings of circuit-switched access networks to servers, such as MSC servers, and mappings of proxy call session control functions (P-CSCFs) to ATCFs and STN-SRs.
The SIP client 408 may enable a user device to perform a SIP registration for a communication session with an IMS or other session continuity components.
In some embodiments, the processor(s) 410 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or any other sort of processing unit.
The telecommunication network device/gateway device 400 also includes additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
In some embodiments, the transceivers 416 include any sort of transceivers known in the art. For example, transceivers 416 may be a radio transceiver that performs the function of transmitting and receiving radio frequency communications. Also, or instead, the transceivers 416 may include other wireless or wired connectors, such as Ethernet connectors or near field antennas. The transceivers 416 may facilitate connectivity between a public network, such as public network 208, and one or more other devices of a telecommunication network.
In some embodiments, the output devices 418 include any sort of output devices known in the art, such as a display, speakers, a vibrating mechanism, or a tactile feedback mechanism. Output devices 418 also include ports for one or more peripheral devices, such as headphones, peripheral speakers, or a peripheral display.
In various embodiments, input devices 420 include any sort of input devices known in the art. For example, input devices 420 may include a camera, a microphone, a keyboard/keypad, or a touch-sensitive display (such as the touch-sensitive display screen described above). A keyboard/keypad may be a push button numeric dialing pad (such as on a typical telecommunication device), a multi-key keyboard (such as a conventional QWERTY keyboard), or one or more other types of keys or buttons, and may also include a joystick-like controller and/or designated navigation buttons, or the like.
At 504, the telecommunication network device receives a measurement report from the user device. The measurement report may include measurements associated with a plurality of access networks that include at least a circuit-switched access network and the access network associated with unlicensed spectrum.
At 506, the telecommunication network device initiates a handover of the communication session of the user device from the access network associated with unlicensed spectrum to the circuit-switched access network. At 506a, the initiating is based at least in part on the measurement report. At 506b, the telecommunication network device also selects the circuit-switched access network based on the measurement report and determines the identity of a server associated with the circuit-switched access network, such as a MSC server.
At 508, the telecommunication network device determines a session transfer number identifying one or more components of the telecommunication network which maintain continuity for the communication session, such as an IMS.
At 510, the telecommunication network device provides a handover request to the server associated with the circuit-switched access network. The handover request may include at least an IMSI, the determined session transfer number, and a C-MSISDN. At 510a, the providing includes sending the handover request to the server or sending the handover request to a MME for the MME to transmit to the server. The handover request may be a SRVCC PS to CS request.
At 512, the telecommunication network device receives a handover response from the server indicating that the circuit-switched access network has been prepared for the handover.
At 514, the telecommunication network device instructs the user device to connect to the circuit-switched access network to continue the communication session.
At 604, the gateway device determines a session transfer number identifying one or more components of the telecommunication network which maintain continuity for the communication session. At 604a, the determining may comprise determining a STN-SR that is statically assigned to an ATCF of the one or more components. At 604b, the determining may comprise obtaining a STN-SR from a HLR or a HSS as part of a location update performed by the gateway device for the user device. At 604c, the determining may comprise determining the session transfer number comprises utilizing a MME to obtain a STN-SR. At 604d, the determining may comprise determining the session transfer number comprises utilizing a SIP subscribe mechanism to receive a STN-SR.
At 606, the gateway device utilizes the session transfer number in a handover of the communication session from the access network associated with the unlicensed spectrum to a circuit-switched access network.
At 704, the user device receives instructions including gaps in the communication session for performing measurements of a plurality of access networks, including at least a circuit-switched access network and the access network associated with unlicensed spectrum.
At 706, the user device measures the plurality of access networks. At 706a, the measuring is performed based at least in part on the instructions including the gaps. The measurements may include at least one of signal strength, packet loss, packet discard, or network congestion.
At 708, the user device provides a measurement report that includes the measurements of the plurality of access networks to a gateway device via the access network associated with unlicensed spectrum.
At 710, the user device receives instructions preparing the user device for a handover of the communication session to the circuit-switched access network. At 710a, the instructions include instructions for the user device to automatically tune the radio to the circuit-switched access network after a threshold period of time following receipt of the instructions preparing the user device for the handover.
At 712, the user device receives instructions from the gateway device to tune the radio to the circuit-switched access network.
At 714, the user device continues the communication session using the circuit-switched access network.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.
