US20090052460A1 - Method of updating core domain information for routing a service, communication device, and communication environment - Google Patents
Method of updating core domain information for routing a service, communication device, and communication environment Download PDFInfo
- Publication number
- US20090052460A1 US20090052460A1 US11/841,103 US84110307A US2009052460A1 US 20090052460 A1 US20090052460 A1 US 20090052460A1 US 84110307 A US84110307 A US 84110307A US 2009052460 A1 US2009052460 A1 US 2009052460A1
- Authority
- US
- United States
- Prior art keywords
- information
- communication device
- network
- core
- core domain
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000004891 communication Methods 0.000 title claims abstract description 139
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000012546 transfer Methods 0.000 claims description 39
- 238000012545 processing Methods 0.000 claims description 26
- 230000015654 memory Effects 0.000 claims description 19
- 230000008859 change Effects 0.000 claims description 9
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 230000004044 response Effects 0.000 claims description 3
- 230000003936 working memory Effects 0.000 description 17
- 230000006870 function Effects 0.000 description 13
- 102000018059 CS domains Human genes 0.000 description 11
- 108050007176 CS domains Proteins 0.000 description 11
- 238000005259 measurement Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/34—Reselection control
- H04W36/36—Reselection control by user or terminal equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- This disclosure relates to a method of updating core domain information for use by a communication device for routing a service for the communication device in a communication environment, a communication device, and a communication environment.
- 3rd generation (3G) systems, such as the Universal Mobile Telecommunication System (UMTS) have been developed and deployed to further enhance the communication services provided to mobile users compared to those communication services provided by the 2nd generation (2G) communication system known as the Global System for Mobile communication (GSM). In such 3G systems two distinct switch domains or networks have been identified for Radio Access Networks (RANs) which communicate with the mobile devices. These domains are the circuit switched (CS) domain and the packet switched (PS) domain. In the CS domain signals are physically routed to the appropriate destination through a unique connection whereas in the PS domain message packets are routed to the appropriate destination based on addresses in the packet. So for example, a UMTS CS domain is a UMTS RAN (known as UTRAN) communicating via a CS network and a UMTS PS domain is a UTRAN communicating via a PS network. In UMTS, the base stations which are part of the UTRAN are known as Node Bs and a mobile terminal is known as User Equipment (UE).
- Other IP-based communication systems, such as wireless LAN (WLAN), Worldwide interoperability for Microwave Access (Wi-MAX), Wi-Fi, Long Term Evolution (LTE) systems, provide communication via a PS domain. It will be appreciated that a GSM system comprising a General Packet Radio System (GPRS) network includes a PS domain through the GPRS network.
- With an increase in the number of wireless communication systems deployed and with the development of UEs having multi-mode capability (i.e. CS domain and PS domain), situations arise where a mobile device may be able to communicate via a PS domain or a CS domain or simultaneously via a PS domain and a CS domain. For example, to originate or receive a voice call or to continue a voice call which is already established in a particular coverage area, a mobile device may have the option to use a GSM CS domain or a GSM PS domain or a UMTS PS domain or a Wireless Local Area Network (WLAN) PS domain in that coverage area.
- In the case when a voice call is already established, Voice Call Continuity (VCC) requires a voice call to be maintained when the voice call is handed over between different domains or different communication systems and between base stations in the same system. Handling call handovers within the same RAN is relatively easy. Handling call handovers or call establishment between different communication systems with different RANs and between different domains, each of which may involve completely different service providers, is more complicated and this is being addressed and standardised within the third Generation Partnership Project (3GPP).
- The current approach defined in the 3GPP standards (3GPP TS 23.206 and TS 24.206) requires a mobile device to select a RAN and domain for call establishment and for call transfer decisions for implementing VCC based on the radio signal strength/quality of the RANs available to the mobile device and on a set of predefined operator VCC rules or policies. These operator policies are typically configured into the mobile device during initial provisioning and may be changed at a later time, for example, by over the air (OTA) provisioning, as the network VCC capabilities evolve.
- As stated above, the VCC mobility approach currently defined in the 3GPP standards by which an appropriate RAN and domain are selected requires the mobile device to be the decision maker and to determine the events which trigger a decision. Other than the received signal strengths that are monitored by the mobile device and the predefined operator VCC rules or policies, the mobile device has no visibility into the overall network characteristics and thus, does not make selection decisions based on network resource related parameters, such as load-balancing, available bandwidth or Quality of Service (QoS) thresholds for triggering a decision. Thus, the current approach does not allow for a selection mechanism which is flexible enough to be controlled in real-time so as to take account of real-time network resource issues. For example, in a situation when a particular RAN and domain are specified in the predefined operator VCC rules and are available to the mobile device (as determined from monitoring the signal strengths from the RAN) but the domain is overloaded, a call will not be established or if a call is already established, the call will be terminated even though another domain and RAN may be available to the mobile device.
- U.S. Pat. No. 6,567,667 discloses a domain selecting system which enables the network to tell the mobile device which services (e.g. services such as voice calls) are supported and/or preferred over which domains. The mobile device can then use this information to influence its decision as to which domain to use when initiating a particular service. For example, the network sends domain preference information for the services to the mobile device when the mobile device connects to a particular RAN. This patent is aimed at supporting migration of services from one domain to another and thus, although discloses sending network specified information such as mapping of certain services and applications to certain domains, or routing certain percentages of calls to one domain or routing calls to a domain that offers the lowest cost, this patent does not disclose the domain selection decisions being based on real-time network resource information. Nor does it address changing domains during an established call. Thus, the result for the specific situation described above would be the same for the system disclosed in this patent.
- PCT patent application no. WO 2007/079582 describes a system for selecting a domain in a network for directing an incoming call to the mobile device. Domain selection policies or rules are stored in a network server and may be modified by the mobile device. User preferences are uploaded to the network with operator policies normally overriding user preferences. The domain selection policies are used by the network to select a domain for directing an incoming call to the mobile device.
- There is therefore a need for an improved process for updating domain selection information which is flexible and takes account of information provided by the mobile device and network resource information.
- A method of updating core domain information for use by a communication device for routing a service for the communication device in a communication environment, a communication device, and a communication environment, in accordance with the disclosure will now be described, by way of example only, with reference to the accompanying drawings in which:
-
FIG. 1 is a block schematic diagram of a communication environment; -
FIG. 2 is a block schematic diagram of a UE in accordance with an embodiment of the present disclosure for use in the communication environment ofFIG. 1 ; -
FIG. 3 is a simplified flow diagram showing a method of updating core domain information for routing a service for a UE in accordance with an embodiment of the disclosure; -
FIG. 4 is a simplified representation of exemplary information sent from the UE to the core network in accordance with the disclosure; and -
FIG. 5 is a simplified representation of exemplary information sent from the core network to the UE in accordance with the disclosure. - The term service as used herein is intended to cover services for the end user of the communication device and includes voice calls, video, audio or other multimedia sessions, file delivery services, bulletin board and broadcast notification services like news feed, web-surfing network gaming, database access, email, SMS or similar services which provide the capability for information transfer. The disclosure will however be described in relation to voice calls for illustrative purposes.
- Referring firstly to
FIG. 1 , acommunication environment 2 comprises a plurality of communication devices (User Equipment (UE) devices) 4 capable of communicating with anaccess environment 5 including a plurality of radio access networks RANs 6. Examples of RANs which may be part of theaccess environment 5 include GSM access network (including GSM/EDGE RAN (GERAN)), UMTS access network, CDMA 1X, CDMA EV-DO, HSPA (HSDPA/HSUPA) access networks, WLAN access network, Wi-Max access network, Evolved-UTRAN (E-UTRAN). Note, the term RAN is also intended to cover the radio elements that couple a UE to networks such as a PSTN or a cable operators HFC/IP network which would be part of theaccess environment 5. The radio elements, e.g. a base station or Wi-Fi Access Point, communicate with the UE over radio communication links but may themselves be coupled via a wired connection to the access network. Each of the RANs 6 in theaccess environment 5 may include CS elements and PS elements. - A
core network 8, which in an embodiment, is an IP Multimedia Subsystem (IMS) as defined in the 3GPP standards, is coupled to theaccess environment 5 and for managing applications and the radio access domains in order to provide services to or from the UE 4. As is well known, the IMS core network is designed to allow service providers to manage a variety of services that can be delivered via IP over any network type, including CS networks, wherein IP is used to transport both traffic information and Session Initiation Protocol (SIP) based signalling information. - The IMS 8 is divided into a plurality of core domains including a CS domain and a PS domain with some of the IMS elements, such as Mobile services Switching Centre (MSC), and Gateway MSC being CS elements, some of the IMS elements, such as Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN) being PS elements and some of the IMS elements such as Visitor Location Register (VLR) and Home Location Register (HLR) being shared by both domains. The structure of the IMS 8 is well known in the art. The core domains are represented by
elements FIG. 1 . Each of the RANs 6 are associated with at least one of thecore domains - The IMS
core network 8 further includes, amongst other things,application servers 12 to support various IMS services such as Push-To-Talk (PTT), Rich Voice Call (RVC) and VCC andvarious SIP servers 10 for the routing of SIP signalling messages between end users (e.g. UEs) and theapplication servers 12. - An
application server 12 in theIMS 8 is arranged to implement the VCC function represented byelement 14 inFIG. 1 . VCC policy information for a UE indicates the rules the UE should take into account when deciding which domain to use when establishing a voice call or before considering initiating a domain transfer when performing a handover of a voice call for VCC, respectively. VCC policy information for a specific user are provisioned in theIMS 8 by the network operator and stored on a Device Management Server (DMS) (not shown) in theIMS 8. The VCC policy information is communicated to the UE during initial provisioning of the UE or The DMS is arranged to use an over-the-air device management protocol (e.g. OMA DM) to download the policy information to the UE 4. Any updates to the VCC policy information made by the operator are communicated to the UE via OMA DM. TheVCC function element 14 in theapplication server 12 obtains access to the VCC policy information stored in the DMS in order to help it make domain selection decisions when implementing the VCC function. The VCC policy information of a user may be updated by theIMS 8 and/or a user via a UE 4. - The 3GPP standard in technical specification TS 23.206 currently defines the VCC policy information as including the following type of information:
- Preferred domain—If a domain is preferred for originating calls/sessions (for example, GSM CS domain, GSM PS domain, UMTS PS domain etc).
- Immediate Domain Transfer (DT) allowed. True or false?—Whether domain transfer is to be initiated immediately to the preferred domain when that domain becomes available.
- DT CS-to-PS direction allowed. True or false?
- DT PS-to-CS direction allowed. True or false?—Whether domain transfer is restricted to a single direction (i.e. PS to CS or CS to PS).
- In addition, the policy information may indicate whether domain transfer is restricted when the UE is engaged in an active and a held/waiting call/session on the transferring-out domain (the restriction does not apply in the case when the UE is going to lose coverage in the transferring-out domain).
- Referring now also to
FIG. 2 which is a partial schematic block diagram of an exemplary communication device operable as aUE 4 having multi-mode capability (e.g. CS domain and PS domain capability). As will be apparent to a skilled person, only those functional components of the UE that are necessary for an understanding of the disclosure have been shown and will be described. TheUE 4 may be a portable or handheld or mobile telephone, a Personal Digital Assistant (PDA), a portable computer, portable television and/or similar mobile or other communication devices. - The
UE 4 comprises aprocessing unit 200 for configuration and control of theUE 4. Theprocessing unit 200 is communicably coupled to aRF communication unit 202 which typically comprises a receiver (203), transmitter (205), a modulation/demodulation section (not shown), a coding/decoding section (not shown) as is well known in the art, and to a Man Machine Interface (MMI) 204. TheMMI 204 includes elements such as a key pad, microphone, speaker, a display, for providing an interface between theUE 4 and the user of theUE 4. If theUE 4 incorporates a removable Subscriber Identity Module (SIM) to control access and provide storage of data, then aSIM interface 208 is further coupled to theprocessing unit 200. TheRF communication unit 202 is coupled to anantenna 209. - The
processing unit 200 may be a single processor or may comprise two or more processors carrying out all processing required for the operation of theUE 4. The number of processors and the allocation of processing functions to the processor is a matter of design choice for a skilled person. TheUE 4 also has aprogram memory 206 in which is stored programs containing processor instructions for operation of theUE 4. The programs may contain a number of different program elements or sub-routines containing processor instructions for a variety of different tasks, for example, for: communicating with the user via theMMI 204; and processing signalling messages received from the radio access networks 6. Specific program elements stored inprogram memory 206 include an domainselection program element 212 for selecting a new core domain and a Radio Access Technology (RAT)measurement program element 213. - The
UE 4 under the control of the RATmeasurement program element 213 is arranged to take measurements with respect to one or more RANs at regular intervals, for example by measuring the signal strengths and/or quality of any signals received by theUE 4 from RANs. For instance, the GSM system requires mobile devices to take measurements with respect to neighbouring cell base station transmitters. In GSM, this is known as a neighbouring cell measurement (MX) period. Such measurement periods facilitate handover between cells of a single RAN and between different RANs and different core domains. From the measurements, theUE 4 can then determined which RANs are available for communication. For example, only those RANs with signals measured to be of sufficient strength to support a voice call would be able to route services successfully to and from theUE 4. TheUE 4 can also determine whether the RAN supports either domain: for example, whether a GSM RAN supports PS access or not. If the GSM signal strength is strong enough and the GSM RAN supports both CS and PS access, then both domains would be available. Note, there may be other factors such as maximum bandwidth (bit rate) that determine whether a PS GSM RAN would be an appropriate candidate for an available PS domain. For example, a 2.5G GPRS access network would have insufficient bandwidth to support VoIP but a EDGE GPRS (EGPRS) or UMTS access network would. - The
UE 4 further comprises amemory 214 for storing predefined VCC policy information. As indicated in the introduction, predefined VCC policy information is determined by the network operator and is typically configured into thememory 214 of theUE 4 during initial set-up of the UE. The predefined VCC policy information in the UE may be changed at a later time by theIMS 8, for example, by OTA provisioning. Thememory 214 is shown inFIG. 2 as being separate to theprocessing unit 200 but may be part of theprocessing unit 200 or the SIM (not shown). The VCC policy information stored inmemory 214 generally corresponds to the VCC policy information stored for theUE 4 in the DMS (not shown) in theIMS 8. - The
processing unit 200 further comprises a workingmemory 216 for storing core domain information or current VCC policy information (hereinafter referred to as working core domain information or working VCC policy information) which working VCC policy information is used by the communication device for routing a service. The workingmemory 216 may be a buffer, a register, some sort of volatile memory and although shown as part ofprocessing unit 200 may be separate to theprocessing unit 200. In an embodiment, the working VCC policy information held in the workingmemory 216 is in the same format and includes the same types of information as the predefined VCC policy information stored inmemory 214. At power up of theUE 4, the working VCC policy information is initialized to the predefined VCC policy information stored inmemory 214. The working VCC policy information may be updated at any time and the way it is updated will be described in more detail below. - The
processing unit 200 under the control of the domainselection program element 212 controls theUE 4 to perform domain transfers or to select a core domain according to the working VCC policy information held in the workingmemory 216. - The
VCC function element 14 may also communicate the working VCC policy information to other functions in theapplication server 12 as required. - A method of updating core domain information (working core domain information) for routing a service, such as a voice call, for a
UE 4 in accordance with an embodiment of the disclosure will now be described with reference to the flow chart shown inFIG. 3 . A decision to select one of the core domains based on the updated core domain information may occur during idle mode (when the UE is idle and not in a call or other service) or during a call in progress to trigger a handover and ensure VCC. - At
step 302, information including connectivity information identifying the RANs of the plurality of RANs 6 which are available to theUE 4 for communication are transmitted to theIMS 8. In an embodiment, this step is event triggered and events which trigger thestep 302 include a change in the RANs which are available to theUE 4 for communication, with a change including for example a new RAN being identified as being available or an existing RAN being identified as becoming unavailable. As discussed above, the available RANs are identified by the periodic measurements performed by theUE 4 to determine those RANs that can support voice calls or other services. The connectivity information sent by theUE 4 to theIMS 8 may simply indicate whether a CS RAN is available or not or whether a PS RAN is available or not. This is sufficient to support basic VCC operation. However, in an embodiment, connectivity information identifying all the CS RANs and PS RANs that are available to theUE 4 is transmitted to theIMS 8. - The connectivity information is transmitted to the
IMS 8 and theVCC function element 14 via one of the available RANs 6 to which theUE 4 is currently registered. In an embodiment, the information transmitted by theUE 4 to theIMS 8 further includes the current working VCC policy information which is being held in the workingmemory 216 and which is currently determining the domain transfers of theUE 4 is also transmitted along with the available RAN information. An example representation of the information that may be transmitted to theIMS 8 is shown inFIG. 4 .Field 400 represents the current working VCC policy information andfield 402 represents the information concerning the available RANs. In the example shown, theUE 4 is a dual-mode device supporting VCC and can only support two communication systems for voice calls: GSM CS represented byfield 404 and WLAN represented byfield 406. - At
step 304, theVCC function element 14 uses the connectivity information received from theUE 4, including the identified available RANs, and network based parameters to generate network information including information identifying a preferred core domain of the plurality ofcore domains UE 4. In other words, theVCC function element 14 uses the information received from theUE 4 as to the RANs available to theUE 4 and the network based parameters to determine whether it is appropriate to change the current preferred core domain as indicated in the current working VCC policy information to a new preferred core domain and generates the network information as a result. The network information may also identify a new preferred RAN of the available RANs 6 based on the information received from theUE 4 and the network based parameters in addition to the new preferred core domain. - The network based parameters may include one or more of the following: load information of the RANs and/or
core domains - In an embodiment, the network information may include fields for the same type of information as the VCC policy information for the
UE 4 e.g. information on the preferred domain, Immediate DT, etc.. Thus, in an embodiment the network information may include new working VCC policy information. The network information is then sent by the IMS 8 (the VCC function element 14) to theUE 4. An example representation of the information that may be transmitted to theUE 4 is shown inFIG. 5 .Field 500 represents the new working VCC policy information which has been generated by theIMS 8 based on the network based parameters and RAN available information provided by theUE 4.Field 504 includes information concerning the current available RANs. The current available RANs information in thisfield 504 corresponds to the latest information provided, for example, infield 402 in the information received from the UE 4 (seeFIG. 4 ) and is used for synchronization purposes. In other words, theIMS 8 informs theUE 4 that the new working VCC policy information infield 500 is based on the list of available RANs infield 504 which it believes to be the current list (i.e. the last list of available RANs received from the UE). If this list is no longer correct, then theUE 4 will upload a new list of available RANs in a message, such as that shown inFIG. 4 , which may cause theIMS 8 to send new working VCC policy information to theUE 4.FIG. 5 (as doesFIG. 4 ) only shows two available RANs: WLAN and GSM CS. This is for illustrative purposes only. It will be appreciated that more than two RANs may be available to theUE 4 in which case more than two boxes (404, 406) will be transmitted to theIMS 8 and more than two boxes will be transmitted to theUE 4 from theIMS 8. When there are more than one available PS RANs and listed in the available RAN list, theIMS 8 needs to identify to theUE 4 which of the available PS RANs is the preferred one (assuming PS core domain is preferred). This enables theIMS 8 and UE to support and control PS to PS domain VCC (e.g. inter RAN) as well as VCC between CS and PS domains. The preferred PS RAN would be identified in the information sent to theUE 4 by theIMS 8. This information is not shown inFIG. 5 . - In an embodiment, the network information sent to the
UE 4 further includesfield 502 including control bits. Reset bit(s) 506 is used by theIMS 8 to indicate to theUE 4 that theUE 4 should reset the working VCC policy information in workingmemory 216 to the predefined VCC policy information. Enable/disable bit(s) 508 is used by theIMS 8 to enable or disable the feature of updating the working VCC policy information. When the feature is disabled, theUE 4 does not transmit the information indicating available RANs to theIMS 8 and theIMS 8 does not generate new working VCC policy information and the control of domain selection and VCC procedures revert to the known methods which are based on the predefined VCC policy information. This allows the core network to control usage of this feature of updating the working VCC policy information to when it is really needed, such as during peak calling hours or when maintenance is being performed on the network infrastructure. This feature of updating the working VCC policy information is automatically enabled in theUE 4 at power up: that is, at power up, theUE 4 uploads its list of candidate available RANs to theIMS 8 and theIMS 8 may then decide whether to continue operating the feature or to disable it by means of the enable/disable bit(s). - In an embodiment, the
UE 4 uses a V3 interface (defined in the 3GPP Technical Specification TS 23.206) to communicate with theVCC function element 14 in theVCC application server 12. TheVCC function element 14 uses the V3 interface to communicate with theUE 4. The V3 interface may be implemented over either CS (e.g. using USSD) or PS transport (e.g. using Ut interface (HTTP)). So the V3 interface is available for communication between theUE 4 and theVCC function element 14 when theUE 4 is using any of thecore domains UE 4 and theIMS 8 may be used. - At
step 306, the network information, including in an embodiment the new working VCC policy information, is received at theUE 4 from theIMS 8. The new working VCC policy information received from theIMS 8 is written to the workingmemory 216 so as to update the working VCC policy information held in the workingmemory 216 to the new working VCC policy information (step 307). The new working VCC policy information takes effect immediately so that future domain selection decisions are based on the new working VCC policy information in the workingmemory 216. - At
step 308, theUE 4 selects the preferred core domain for routing the service based on the network information. This may involve a domain transfer from an existing core domain to the preferred core domain indicated in the new working VCC policy information if the preferred core domain has changed. TheUE 4 may also select a new preferred RAN of the available RANs 6 based on the network information. - If the
UE 4 is in idle mode (e.g. not in a call) and the preferred core domain has not changed, then theUE 4 just updates the working VCC policies. If theUE 4 is in idle mode (e.g. not in a call) and the preferred core domain has changed, then theUE 4, in addition to updating the working VCC policies, selects which core domain it wants to use to originate/receive calls based on the working VCC policy information and RAN availability and performs what's called an idle mode domain transfer. This involves registering in the new preferred core domain (if not already done so) and typically deregistering from the old preferred core domain. TheUE 4 needs to be registered in a core domain (PS or CS) in order to use it (i.e., originate and receive calls in that domain). Normally a dual-mode UE 4 will only be registered in a single core domain unless it is preparing to handover a call, in which case it needs to be temporarily registered in both core domains (i.e., the old and the new core domains). A reason for only being registered in one core domain at a time (i.e., the preferred domain) is, for example, to conserve battery life. - While in a call, the
UE 4 may also select a different core domain (based on the working VCC policy information and the available RANs) but that causes a domain transfer of the call (handover). In this case, theUE 4 registers in the new preferred core domain, transfers the call to the new preferred core domain, and optionally, deregisters from the old core domain. TheUE 4 may want to remain dual registered while in a call in order to facilitate back and forth handoffs. Once a call is ended, theUE 4 deregisters from the old core domain. - In an embodiment, the
processing unit 200 under the control of the domainselection program element 212 controls theUE 4 to perform domain selection according to the new working VCC policy information held in the workingmemory 216. If the Immediate DT field of the new working VCC policy information is set ‘true’, then once the new working VCC policy information is stored in the workingmemory 216, a domain selection and transfer is triggered during an existing or established call (for VCC), by which a domain transfer from an existing core domain to the preferred core domain is performed. The Immediate DT field only impacts domain transfer of a call. It does not apply to idle mode transfers which should occur immediately. - In an embodiment, additional information may be included in the network information which sets a time period for which the network information sent by the
IMS 8 is valid. In the example shown inFIG. 5 , atime stamp 510 is provided in the network information sent to theUE 4. Thetime stamp 510 may indicate an expiration time associated with the new working VCC policy information infield 500 which limits the time that the new working VCC policy information is to be in effect. Upon expiration of the time specified in thetime stamp 510, theprocessing unit 200 resets the working VCC policy information in workingmemory 216 to the predefined VCC policy information. - As discussed above, the
UE 4 uploads information identifying the available RANs to theIMS 8 in response to an event and theIMS 8 provides network information to theUE 4 based on the connectivity information received from theUE 4 and on network based parameters. However, theIMS 8 may send network information, including a new working VCC policy information, to theUE 4 at any time in which case the method of selecting a core domain starts atstep 304. For example, theIMS 8 may wish to initiate a domain transfer irrespective of whether there has been a change in available RANs, for example when the QoS provided by a core domain is determined by theIMS 8 to reach a predetermined threshold. In this case, the currently available connectivity information (previously received from the UE 4) on the available RANs is used by theIMS 8 to generate the new working VCC policy information. The new working VCC policy information may take effect immediately and may trigger idle mode or VCC domain transfers in theUE 4. - As a further illustration of the above described embodiment of the disclosure, a couple of example scenarios are described below.
- Scenario: The preferred domain as specified in the VCC policy information is to be changed while a UE is in a voice call so as to initiate an immediate domain transfer of the voice call.
- Initial conditions: The UE is in both GSM CS and Wi-Fi coverage and has an ongoing PS Voice over IP (VoIP) call via the
IMS 8. - Old working VCC policy information held in working memory 216:
-
- Preferred domain: IMS preferred
- Immediate DT: True
- DT CS-to-PS direction: Not restricted
- DT PS-to-CS direction: Not restricted
- New working VCC policy information sent to
UE 4 byIMS 8 and stored in working memory 216: -
- Preferred domain: GSM CS preferred
- Immediate DT: True
- DT CS-to-PS direction: Restricted
- DT PS-to-CS direction: Not restricted
- Outcome: The
UE 4 performs an immediate domain selection and transfer of its IMS VoIP call to a GSM CS call because the preferred domain field has been changed to GSM CS and the Immediate DT field is set to true. Also, since the DT CS-to-PS direction field has been changed to restricted, the UE cannot transfer the call back toIMS 8. - Scenario: The
IMS 8 desires to disable IMS VoIP for a period of time in order to do maintenance. - Initial conditions: The UE is in both GSM CS and Wi-Fi coverage and is in IMS idle mode (i.e. there is no ongoing voice call).
- Old working VCC policy information held in working memory 216:
-
- Preferred domain: IMS preferred
- Immediate DT: True
- DT CS-to-PS direction: Not restricted
- DT PS-to-CS direction: Not restricted
- New working VCC policy information (time stamped in
time stamp field 510 to expire in 3 hours) sent toUE 4 byIMS 8 and stored in working memory 216: -
- Preferred domain: GSM CS only
- Immediate DT: True
- DT CS-to-PS direction: Not restricted
- DT PS-to-CS direction: Not restricted
- Outcome: The
UE 4 performs an idle mode domain selection and transfer to GSM CS domain because the preferred domain field has been changed to GSM CS only. Consequently, from now on and for the next 3 hours, all new voice calls will be GSM CS voice calls. The new working VCC policy information held in the workingmemory 216 will expire in 3 hours after which time the working VCC policy information will be reset to the predefined VCC policy information held in thememory 214. - In a second embodiment of the disclosure, instead of downloading new working VCC policy information to the
UE 4 as in the first embodiment described above, the core network is arranged to tell theUE 4 exactly which core domain to use. Thus, in the second embodiment, the core network has more direct control over which core domain the UE can use compared to the first embodiment. - In order to support this, a new working parameter called “Current Domain/RAN” is defined and is maintained by the
UE 4. The Current Domain/RAN parameter identifies the core domain and RAN currently used by theUE 4 for routing a service, such as originating/receiving calls and calls in progress. - As in the first embodiment, the
UE 4 transmits to theIMS 8 information including connectivity information identifying the RANs of the plurality of RANs 6 which are available to theUE 4 for communication. TheIMS 8 uses the connectivity information received from theUE 4, including the identified available RANS, and factors, for example, the network resource parameters identified above with respect to the first embodiment, to generate a new value of the parameter “Current Domain/RAN”. However, instead of downloading new working VCC policy information to theUE 4, the core network/IMS 8 downloads the new value of the parameter “Current Domain/RAN” to theUE 4 and the new value of the parameter is used to update the current “Current Domain/RAN” parameter held in theUE 4. - Thus, the parameter “Current Domain/RAN” can be dynamically updated at any time by the
IMS 8, based on the connectivity information sent to it by the UE and the network resource parameters. The updated “Current Domain/RAN” parameter takes effect immediately. - If the
UE 4 has call(s) in a different core domain and/or RAN, then theUE 4 must domain transfer the call(s) to the new core domain and/or RAN specified in the updated “Current Domain/RAN”. - If the
UE 4 is in idle mode in a different core domain and/or RAN, then theUE 4 does an idle mode domain transfer to the new core domain and/or RAN specified in the updated “Current Domain/RAN”. - The
UE 4 remains in the core domain and RAN according to the “Current Domain/RAN” parameter until it is changed by the core network or the feature is disabled by the core network. - If connectivity to the new core domain specified in the updated “Current Domain/RAN” parameter is not possible, then the
UE 4 may remain in it's current core domain and RAN until connectivity to the updated “Current Domain/RAN” is achieved at which time a domain transfer is executed. - At power up, the
UE 4 determines the “Current Domain/RAN” parameter from the current RAN connectivity status and the predefined VCC policy information held in thememory 214 of theUE 4. - As with the first embodiment, the
core network 8 may, at any time, disable and, at a later time, re-enable this feature of updating the “Current Domain/RAN” parameter in theUE 4. When this feature is disabled, theUE 4 reverts to using the predefined VCC policy information and current RAN connectivity status to determine its “Current Domain/RAN” parameter which is used by the UE for routing a service. - As a further illustration of the second embodiment of the disclosure, a couple of example scenarios are described below.
- Scenario: Force immediate domain transfer of an established call
- Initial Conditions: UE is in GSM CS coverage and has an ongoing GMS CS call. UE then enters WiFi coverage and when the WiFi signal becomes strong enough, the UE sends a new list of candidate access networks to the
IMS 8. However, the UE does not domain transfer to IMS upon entering WiFi coverage because the “Current Domain/RAN” parameter is currently set to GSM CS and direct network control is enabled. - Action:
IMS 8 sets “Current Domain/RAN” parameter to WLAN and sends new value to the UE. - Final Outcome: Upon receiving the new value for “Current Domain/RAN” parameter from the
IMS 8, the UE performs an immediate domain transfer of its GSM CS call to an IMS VoIP call over WiFi in PS domain. Subsequent calls will be originated/terminated via IMS until further notice from network. - Scenario: Disable IMS VoIP for a period of time in order to do maintenance.
- Initial Conditions: UE is in both GSM CS and WiFi coverage and direct network control of VCC is disabled. Consequently, the UE is using its predefined VCC policy information which indicates that the preferred domain is “IMS Preferred”. The UE currently has no active calls.
- Action: The
IMS 8 activates direct network control of VCC and sets the “Current Domain/RAN” parameter to GSM CS and sends new value to UE. - Final Outcome: Upon receiving the new value for “Current Domain/RAN” from the network, the UE performs an immediate idle mode domain transfer to GSM CS domain. Subsequent calls will be originated/terminated via GSM CS until further notice from network.
- The implementation of the second embodiment is very similar to that described above with respect to the first embodiment (e.g.
FIGS. 1-3 and the accompanying description apply accordingly to the second embodiment). - Thus, the method in accordance with the disclosure allows for the core domain information (including for example VCC policy information or a “Current Domain/RAN” parameter) used by the UE for routing a service to be updated in real-time by the core network supporting VCC service so that the core network can dynamically change the working core domain information (VCC policy information or a “Current Domain/RAN” parameter) for a specific user based on network based parameters and the RANs which are available for communication. This enables the core network to change the preferred domain for originating and receiving calls and change the supported handover direction and if the conditions are right, trigger a domain transfer of an established call. Furthermore, the core network can, at any time, dynamically reset the working core domain information (VCC policy information or a “Current Domain/RAN” parameter) used by the UE based on the predefined VCC policy information. Thus, the disclosure enables the UE to have visibility into the network characteristics so that the UE can make call handover decisions and call establishment decisions (UE originated or UE terminated) based on network based parameters.
- The present invention has been described above with respect to selecting a core domain for routing voice calls for call establishment and for handovers for VCC. It will be appreciated that the disclosure is not intended to be limited to voice call services and may apply to any services which may require core domain transfers.
Claims (30)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/841,103 US8879565B2 (en) | 2007-08-20 | 2007-08-20 | Method of updating core domain information for routing a service, communication device, and communication environment |
PCT/US2008/073533 WO2009026264A1 (en) | 2007-08-20 | 2008-08-19 | Method of updating core domain information for routing a service, communication device, and communication environment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/841,103 US8879565B2 (en) | 2007-08-20 | 2007-08-20 | Method of updating core domain information for routing a service, communication device, and communication environment |
Publications (2)
Publication Number | Publication Date |
---|---|
US20090052460A1 true US20090052460A1 (en) | 2009-02-26 |
US8879565B2 US8879565B2 (en) | 2014-11-04 |
Family
ID=39855182
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/841,103 Active US8879565B2 (en) | 2007-08-20 | 2007-08-20 | Method of updating core domain information for routing a service, communication device, and communication environment |
Country Status (2)
Country | Link |
---|---|
US (1) | US8879565B2 (en) |
WO (1) | WO2009026264A1 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060234720A1 (en) * | 2005-04-14 | 2006-10-19 | Masaaki Takizawa | Wireless communication system, access point and wireless station composing the wireless communication system, and communication load balancing method for access point |
US20090086719A1 (en) * | 2007-10-02 | 2009-04-02 | Nokia Corporation | Dynamic initiation of I1-ps signaling in IMS centralized services |
US20100208694A1 (en) * | 2007-08-29 | 2010-08-19 | Hisao Kumai | Mobile communication system, radio communication method, core network, user equipment, and program |
US20100309847A1 (en) * | 2009-06-04 | 2010-12-09 | Qualcomm Incorporated | Method and apparatus for ims application domain selection and mobility |
US20110058520A1 (en) * | 2008-04-24 | 2011-03-10 | Ralf Keller | Method, apparatus and computer program for supporting a session identifier in case of a transfer between different radio access networks |
US20110058480A1 (en) * | 2008-01-30 | 2011-03-10 | Telefonaktiebolaget L M Ericsson (Publ) | Core Network Processing Load Reduction |
US20110164564A1 (en) * | 2010-01-06 | 2011-07-07 | Lg Electronics Inc. | Mobile switching centre server |
US20110188467A1 (en) * | 2008-06-23 | 2011-08-04 | Ntt Docomo, Inc. | User device, base station, and communication method for mobile communication system |
US20110249624A1 (en) * | 2010-04-12 | 2011-10-13 | Qualcomm Incorporated | System, apparatus, and method to enable domain selection in a multimode device |
US20130173801A1 (en) * | 2009-12-23 | 2013-07-04 | Roy Rajan | Systems and methods for managing preferred client connectivity to servers via multi-core system |
US20150055572A1 (en) * | 2012-03-19 | 2015-02-26 | Sharp Kabushiki Kaisha | Wireless communication system, communication method, terminal device, and base station |
US20230057565A1 (en) * | 2013-03-15 | 2023-02-23 | E.F. Johnson Company | Distributed land mobile radio architectures |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9854004B2 (en) * | 2014-05-09 | 2017-12-26 | Qualcomm Incorporated | Systems and methods for managing different types of registrations for IMS services on SIMs of a wireless communication device |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070195785A1 (en) * | 2006-02-06 | 2007-08-23 | Lg Electronics Inc. | Method for requesting domain transfer and terminal and server thereof |
US20070238467A1 (en) * | 2006-01-10 | 2007-10-11 | Research In Motion Limited | System and method for routing an incoming call to a proper domain in a network environment including IMS |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102004057311B4 (en) | 2004-11-26 | 2007-12-20 | T-Mobile International Ag & Co. Kg | Method and system for supporting service continuity for mobile communication over different access networks |
WO2007091808A1 (en) | 2006-02-06 | 2007-08-16 | Lg Electronics Inc. | Method for placing call in voice call continuity and terminal and server thereof |
KR20070108427A (en) | 2006-02-06 | 2007-11-12 | 엘지전자 주식회사 | Method for restriction of domain transfer and terminal and server thereof |
US8411641B2 (en) | 2006-12-05 | 2013-04-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods for controlling access domain switching, network nodes, user terminal and computer program product therefor |
-
2007
- 2007-08-20 US US11/841,103 patent/US8879565B2/en active Active
-
2008
- 2008-08-19 WO PCT/US2008/073533 patent/WO2009026264A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070238467A1 (en) * | 2006-01-10 | 2007-10-11 | Research In Motion Limited | System and method for routing an incoming call to a proper domain in a network environment including IMS |
US20070195785A1 (en) * | 2006-02-06 | 2007-08-23 | Lg Electronics Inc. | Method for requesting domain transfer and terminal and server thereof |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7818014B2 (en) * | 2005-04-14 | 2010-10-19 | Hitachi, Ltd. | Wireless communication system, access point and wireless station composing the wireless communication system, and communication load balancing method for access point |
US20060234720A1 (en) * | 2005-04-14 | 2006-10-19 | Masaaki Takizawa | Wireless communication system, access point and wireless station composing the wireless communication system, and communication load balancing method for access point |
US20100208694A1 (en) * | 2007-08-29 | 2010-08-19 | Hisao Kumai | Mobile communication system, radio communication method, core network, user equipment, and program |
US20090086719A1 (en) * | 2007-10-02 | 2009-04-02 | Nokia Corporation | Dynamic initiation of I1-ps signaling in IMS centralized services |
US8660009B2 (en) * | 2008-01-30 | 2014-02-25 | Telefonaktiebolaget L M Ericsson (Publ) | Core network processing load reduction |
US20110058480A1 (en) * | 2008-01-30 | 2011-03-10 | Telefonaktiebolaget L M Ericsson (Publ) | Core Network Processing Load Reduction |
US20110058520A1 (en) * | 2008-04-24 | 2011-03-10 | Ralf Keller | Method, apparatus and computer program for supporting a session identifier in case of a transfer between different radio access networks |
US8948127B2 (en) * | 2008-04-24 | 2015-02-03 | Telefonaktiebolaget L M Ericsson (Publ) | Method, apparatus and computer program for supporting a session identifier in case of a transfer between different radio access networks |
US9136996B2 (en) * | 2008-06-23 | 2015-09-15 | Ntt Docomo, Inc. | User device, base station, and communication method for mobile communication system |
US20110188467A1 (en) * | 2008-06-23 | 2011-08-04 | Ntt Docomo, Inc. | User device, base station, and communication method for mobile communication system |
US20100309847A1 (en) * | 2009-06-04 | 2010-12-09 | Qualcomm Incorporated | Method and apparatus for ims application domain selection and mobility |
US20130173801A1 (en) * | 2009-12-23 | 2013-07-04 | Roy Rajan | Systems and methods for managing preferred client connectivity to servers via multi-core system |
US8935399B2 (en) * | 2009-12-23 | 2015-01-13 | Citrix Systems, Inc. | Systems and methods for managing preferred client connectivity to servers via multi-core system |
US8855049B2 (en) * | 2010-01-06 | 2014-10-07 | Lg Electronics Inc. | Mobile switching centre server |
US20110164564A1 (en) * | 2010-01-06 | 2011-07-07 | Lg Electronics Inc. | Mobile switching centre server |
US20110249624A1 (en) * | 2010-04-12 | 2011-10-13 | Qualcomm Incorporated | System, apparatus, and method to enable domain selection in a multimode device |
US9699718B2 (en) * | 2010-04-12 | 2017-07-04 | Qualcomm Incorporated | System, apparatus, and method to enable domain selection in a multimode device |
US20150055572A1 (en) * | 2012-03-19 | 2015-02-26 | Sharp Kabushiki Kaisha | Wireless communication system, communication method, terminal device, and base station |
US20230057565A1 (en) * | 2013-03-15 | 2023-02-23 | E.F. Johnson Company | Distributed land mobile radio architectures |
US11936466B2 (en) * | 2013-03-15 | 2024-03-19 | E.F. Johnson Company | Distributed land mobile radio architectures |
Also Published As
Publication number | Publication date |
---|---|
US8879565B2 (en) | 2014-11-04 |
WO2009026264A1 (en) | 2009-02-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8879565B2 (en) | Method of updating core domain information for routing a service, communication device, and communication environment | |
US11589271B2 (en) | Communication fallback in 5G systems and methods | |
KR102130231B1 (en) | Network slicing behavior | |
US9699763B2 (en) | Network node, method, and mobile terminal for providing voice calls to a mobile terminal in a packet-switched-only network | |
US9432891B2 (en) | Method and apparatus for selecting equivalent PLMN | |
CN113767672B (en) | Mobile communication core network apparatus and method for managing wireless communication after inserting an intermediate session management function | |
JP5646647B2 (en) | Method and apparatus for use in a communication network | |
EP2890186B1 (en) | Apparatus,method and non-transitory computer readable storage medium for inter-domain handover | |
CN110741680B (en) | Method and unit for determining PDU session handover | |
CN111567068B (en) | Voice indication processing method and user equipment thereof | |
US20120020325A1 (en) | Method and apparatus for a hand off of a communication session across service provider networks | |
US20130122921A1 (en) | Dynamic optimization of radio network resources based on user equipment type | |
JP2016513418A (en) | Service control method, mobility management entity, and mobile switching center | |
US10785694B2 (en) | Method, network functions and a computer program product for supporting the handing over of a user equipment, UE, from a first type of radio access technology, RAT, to a second type of RAT | |
EP3425959A1 (en) | Communication handovers from networks using unlicensed spectrum to circuit-switched networks | |
CN110719613A (en) | Method and device for establishing voice service | |
KR20150099367A (en) | Method and apparatus for improving service quality of video call in mobile communication systems | |
US11343745B2 (en) | Use of dynamic connection priority information to control network connectivity | |
US20230362740A1 (en) | 5g multicast broadcast service handover | |
KR20130023971A (en) | Traffic control gateway and traffic control method using the same | |
JP5882821B2 (en) | Discovery information distribution device, mobility management device, and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MOTOROLA, INC., ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COULAS, MICHAEL F.;HORVATH, ROBERT;SALKINTZIS, APOSTOLIS K.;REEL/FRAME:019949/0496;SIGNING DATES FROM 20071004 TO 20071010 Owner name: MOTOROLA, INC., ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COULAS, MICHAEL F.;HORVATH, ROBERT;SALKINTZIS, APOSTOLIS K.;SIGNING DATES FROM 20071004 TO 20071010;REEL/FRAME:019949/0496 |
|
AS | Assignment |
Owner name: MOTOROLA MOBILITY, INC, ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA, INC;REEL/FRAME:025673/0558 Effective date: 20100731 |
|
AS | Assignment |
Owner name: MOTOROLA MOBILITY LLC, ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA MOBILITY, INC.;REEL/FRAME:028829/0856 Effective date: 20120622 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: GOOGLE TECHNOLOGY HOLDINGS LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA MOBILITY LLC;REEL/FRAME:034371/0612 Effective date: 20141028 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551) Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |