JP2012529251A - Voice services in evolutionary packet systems - Google Patents

Abstract

A method and apparatus for managing voice services in an evolved packet system is disclosed. An example method in a user equipment (UE) with at least one voice service indicator (Voice Service Indicator / VSI) in an evolved packet system (Evolved Packet System / EPS) comprises detecting a change in the value of at least one VSI. , Causing the UE to notify the network in response to a change in VSI.
[Selection] 2A

Description

(Related application)
This application is a non-provisional application of US Provisional Application No. 61 / 183,933 (filed June 3, 2009, entitled “Voice Service in Evolved Packet System Using IP Multimedia Subsystem”). The provisional application is hereby incorporated by reference in its entirety.

(Disclosure field)
The present application relates generally to mobile communication systems, and more specifically to providing voice services in an evolved packet system.

In recent years, voice service metrics have been defined in evolved packet system (EPS) mobile communication systems to coordinate network service availability and mobile device capabilities. The voice service index is, for example,
“IMS Voice over PS session supported” instruction,
“Voice Centric” or “Data Centric” indication, and “CS Voice only”, “IMS PS voice only”, “CS Voice Priority, IMS It includes an indication of “CS voice preferred, IMS voice secondary” or “IMS voice preferred, CS voice secondary”.

  An “IMS Voice over PS Session Supported” indication is provided by the network to the user equipment (UE) (Non-Access Layer (NAS) registration (eg, EPS attach) or NAS registration update) Is given in). “Voice Centric” or “Data Centric” indication and “CS Voice Only”, “IMS PS voice only”, “CS Voice Priority”, “CS Voice Only”, “CS Voice Only”, “CS Voice Only” An "IMS voice preferred" or "IMS voice preferred, CS voice secondary" indication is available on the UE. The operator can select “CS Voice Only”, “IMS PS Voice Only”, “CS Voice Priority, IMS Voice Preferred,” or “IMS Voice Secondary”, or An “IMS Voice preferred, CS voice secondary” indication may be configured on the UE.

(Abbreviations and terms)
AS: Access Stratum (Access Stratum)
CN: Core Network
CS: Circuit Switched
CSFB: CS Fallback (CS Fallback)
EMM: Evolved Packet System Mobility Management (Evolved Packet)
System (EPS) Mobility Management)
eNB: eNodeB (eNodeB)
EPC: Evolved Packet Core
EPS: Evolved Packet System (Evolved Packet System)
m)
E-UTRAN: Evolved UTRAN (Evolved UTRAN)
IMS: IP Multimedia Subsystem (IP Multimedia Su
bsystem)
IM CN: IP multimedia core network (IP Multimedia
Core Network)
MAC: Medium access control (Medium Access Control)
MS: Mobile Station
NAS: Non-Access Stratum (Non Access Stratum)
NW: Network
PS: Packet Switched
RA: Routing Area
PDCP: Packet Data Convergence Protocol (Packet Data Conve
rgence Protocol)
RAN: Radio Access Network (Radio Access Network
k)
RAU: Routing Area Update
RB: Radio Bearer
RLC: Radio Link Control
RRC: Radio Resource Control
TA: Tracking Area
TAI: TA identification (TA Identity)
TAU: Tracking area update (Tracking Area Update)
TS: Technical Specification
UE: User equipment UMTS: Universal mobile mobile telecommunications system (Un
universal Mobile Telecommunication
s System)
UTRAN: UMTS Terrestrial RAN (UMTS Terrestrial RAN)
VoIMS: Voice over IMS (Voice over IMS)
In the example implementation described herein, the voice service indications may be network provided VoIMS indications, UE usage settings, and user equipment voice settings. In the following description, the voice service indicator is called as follows.
a) (Network provided) (IMS) VoIMS indicator is
Indicates “IMS Voice over PS session supported” indication referred to above or “IMS Voice over PS session not supported” indication referred to above, Indicates whether voice over PS sessions controlled and managed by the IP multimedia subsystem are supported.
b) UE usage settings are:
Indicates “Voice Centric” or “Data Centric” referred to above. A UE usage setting is a UE setting that indicates whether the UE has a voice service preference for a data service or vice versa. If the UE has a voice service preference, the usage setting of the UE is “Voice Centric”. If the UE has a preference for data services, the usage setting of the UE is “Data Centric”. To avoid suspicion, UEs that are “Data Centric” may still need voice services. If the UE needs only a data service and can accept that there is no voice service, the usage setting of the UE is “Data Only”. The two settings can have the following meanings:
-"Voice Centric": the voice-centric UE must be able to use voice services and thus acquire voice services regardless of how such services can be enabled. try to.
-"Data Centric": The data centric UE prefers to have the best PS service possible, even if it suggests that this is not possible to access voice services.

A further UE usage setting of “Data Only” is possible. In the case where this additional setting is possible, the three settings may have the following meanings.
-"Voice Centric": the voice-centric UE must be able to use voice services and thus acquire voice services regardless of how such services can be enabled. try to.
-"Data Centric": Data-centric UEs prefer to have the best PS service possible (ie stay in E-UTRAN) if access to voice services is not excluded. .
-"Data Only": The data-centric UE prefers to have the best PS service possible even though it suggests that this is not possible to access the voice service.
c) UE voice settings are:
“CS Voice Only”, “PS Voice Only”, “IMS PS Voice Only”, “CS Voice Priority, IMS Voice Secondary” referenced above. (CS Voice Preferred, IMS Voice Secondary) or “IMS Voice Preferred, CS Voice Secondary” indication. The UE voice setting is a UE setting indicating a domain used for voice service.

  Table 1 summarizes this grouping and naming convention.

実装例では、ネットワークメッセージは、ＶｏＩＭＳ指標を含み得る。例えば、３ＧＰＰ ＴＳ ２４．３０１に従ったアタッチ受理（ＡＴＴＡＣＨ ＡＣＣＥＰＴ）メッセージが、表２で示されるように実装され得、および／または表３に示された３ＧＰＰ ＴＳ ２４．００８に従ったＩｕモードで実装され得る。ＶｏＩＭＳ指標は、音声のサポートを示すために、ＩＭＳ用のセッションを介してネットワークによってＵＥに送信され得る。

In an example implementation, the network message may include a VoIMS indication. For example, an attach accept (ATTACH ACCEPT) message according to 3GPP TS 24.301 may be implemented as shown in Table 2 and / or in Iu mode according to 3GPP TS 24.008 shown in Table 3. Can be implemented. The VoIMS indication may be sent by the network to the UE via a session for IMS to indicate voice support.

本明細書で説明されるように、ＵＥは、複数のプロトコル層を有する。本明細書で説明されるＵＥ例は、３つの層（ＩＭＳ層、ＮＡＳ層、およびＡＳ層）を含む。順序付け例は、以下の通りである。ＩＭＳがＮＡＳおよびＡＳ層より上側にあり、ＡＳ層はＮＡＳおよびＩＭＳ層に対する下層である。したがって、ＮＡＳ層および／またはＡＳ層は、ＩＭＳ層の視点から「下層」と呼ばれ得る。ＩＭＳ層は、上層と呼ばれ得る。

As described herein, a UE has multiple protocol layers. The example UE described herein includes three layers: an IMS layer, a NAS layer, and an AS layer. An example of ordering is as follows. The IMS is above the NAS and AS layers, and the AS layer is a lower layer for the NAS and IMS layers. Thus, the NAS layer and / or AS layer may be referred to as the “lower layer” from the IMS layer perspective. The IMS layer can be referred to as the top layer.

  In some implementations, for example, after completion of the attach procedure in Iu mode, a VoIMS indicator is available in the attach accept (ATTACH ACCEPT) message, and “IMS Voice over PS session supported”. ", The successful completion of the attach procedure is indicated in the upper layer, for example, for the start of SIP registration with the IP multimedia subsystem. In some further implementations, the successful completion of the attach procedure is, for example, out of “PS Voice Only” or “IMS Voice Preferred, CS Voice Secondary” It is shown in the upper layer that receives the voice setting of the UE, which is set to one of the following.

  In another example implementation, a TRACKING AREA UPDATE message according to 3GPP TS 24.301 may be implemented as shown in Table 4.

例えば、Ｉｕモードにおける、いくつかの実装例では、追跡領域更新手順の完了の成功ときに、追跡領域更新受理（ＴＲＡＣＫＩＮＧ ＡＲＥＡ ＵＰＤＡＴＥ ＡＣＣＥＰＴ）メッセージの中で受信された場合のＶｏＩＭＳ指標は、上層に示されるであろう。

For example, in some implementations in Iu mode, the VoIMS indication when received in a TRACKING AREA UPDATE ACCEPT message upon successful completion of the tracking region update procedure is shown in the upper layer. Will be.

  A ROUTING AREA UPDATE ACCEPT message may be sent by the network to provide GPRS mobility management data to the UE in response to a routing area update request from the UE (ROUTING AREA UPDATE REQUEST). A ROUTING AREA UPDATE ACCEPT message may include a VoIMS indication as shown in Table 5 when received or provided to a UE, eg, according to 3GPP TS 24.00.

例えば、Ｉｕモードでは、ネットワークは、ＩＭＳのセッションを介した音声のサポートを示すように、ルーティング領域更新受理（ＲＯＵＴＩＮＧ ＡＲＥＡ ＵＰＤＡＴＥ ＡＣＣＥＰＴ）メッセージ（または任意の他のメッセージ）にＶｏＩＭＳ指標を含み得る。

For example, in lu mode, the network may include a VoIMS indication in a Routing Area Update Accept message (or any other message) to indicate support for voice over an IMS session.

  In another embodiment, SIP registration to the IP multimedia subsystem fails if the MS is in the states GMM-REGISTRED and MM-IDLE, and if the network is operating in network operation mode I and Iu mode. For example, when the UE receives an instruction from the upper layer to receive the usage setting of the UE set to “Voice Centric”, the complex routing area update procedure is performed in the MS operation mode A or B. Initiated by a working GPRS MS.

In some implementations, for example, access to the IM CN may be initiated after completion of an attach procedure or registration procedure according to 3GPP TS 24.008. For example, the access is 3GPP TS 24.229, 6.2 B.B. It can be started according to section 2.2.1. For example, access to the IM CN may be initiated when the UE is not yet registered with the IM CN subsystem and the usage setting of the UE is not “Voice Centric”. In another embodiment, the access to the IM CN is that the UE has not yet registered with the IM CN subsystem and the UE usage setting is “PS Voice Only” or the UE usage. It can be initiated when the setting is “IMS Voice Preferred, CS Voice Secondary”. In yet another example, an indication of IM CN subsystem registration failure may be provided to a lower layer under the following conditions:
If registration to the IM CN subsystem fails, or
After repeated attempts to register with the IM CN subsystem fail, the UE reaches a pre-configured number of retries and terminates further attempts, or
If the user interrupts further attempts to register with the IM CN subsystem after repeated attempts to register fail,
When a user-initiated deregistration is performed, or when the UE is deregistered explicitly or implicitly by the network.

  In some implementations, the UE may take action based on the NAS indication to select a particular RAT. In some implementations, if the UE includes an information element for a “capability update request” and receives a message that includes an information element for a “system specific capability update request list”, the “UE system specific capability” information For each of the RATs required in the element, if the UE supports the described RAT, the described RAT is E-UTRAN and the NAS is providing instructions to the AS to select GERAN or UTRAN. If not, or if the described RAT is not E-UTRAN, the UE may include inter-RAT radio access capability for the described RAT in the IE “UE system specific capabilities” from the variable UE_CAPABILITY_REQUESTED. In addition, if the described RAT is GSM® and PS handover to GPRS is supported, the variable UE_CAPABILITY_REQUESTED includes the IE “MS Radio Access Capability”.

  In some further implementations, the UE may take action based on the NAS indication to select a particular RAT. In some implementations, when performing cell selection when not in the RRC_CONNECTED state, as a result of a NAS indication that selects GERAN or UTRAN, the UE may select a cell on GERAN and UTRAN RAT upon transition from RRC_CONNECTED to RRC_IDLE. And cell selection and reselection to the E-UTRAN cell may be disabled. Similarly, if the NAS provides an indication to the AS to select GERAN or UTRAN while the UE is RRC_IDLE, the UE performs cell selection on the GERAN and UTRAN RAT, and the cell to the E-UTRA cell Selection and reselection will be enabled.

  In some further implementations, as a result of a NAS indication that selects GERAN or UTRAN, when transitioning from RRC_CONNECTED to RRC_IDLE, the UE performs cell selection on GERAN and UTRAN RAT when performing cell selection if it is no longer in the RRC_CONNECTED state. A selection will be made and cell selection and reselection to the E-UTRAN cell will be disabled. If the NAS provides an indication to the AS to select GERAN or UTRAN while the UE is RRC_IDLE, the UE performs cell selection on the GERAN and UTRAN RAT, and selects and re-selects cells to the E-UTRA cell. Will invalidate the selection.

If the NAS provides an instruction to the AS to select GERAN or UTRAN while the UE is RRC_CONNECTED, the UE may take the following actions if it is no longer RRC_CONNECTED, using a “other” release cause: .
Reset the MAC.
All timers that are operating are stopped except T320.
Release all radio resources, including RLC entity, MAC configuration, and release of associated PDCP entity for all established RBs.
Show release of RRC attach to upper layer with cause of release,
If it was not triggered by receiving a MobilityFromEUTRACommand message to be no longer RRC_CONNECTED,
For example, it becomes RRC_IDLE by performing cell selection according to the cell selection process defined for the case where it is not RRC_CONNECTED specified in 3GPP TS 36.304.

FIG. 1A is a diagram of S2-094178 [iii]. 2.1-1. FIG. 1B shows the diagram A.S. 4-1. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 2A to 10C show a flowchart of the embodiment. 11A to 11E show flowcharts of the embodiment. 11A to 11E show flowcharts of the embodiment. 11A to 11E show flowcharts of the embodiment. 11A to 11E show flowcharts of the embodiment. 11A to 11E show flowcharts of the embodiment. FIG. 12 shows a block diagram of a mobile communication device.

  1A and 1B are diagrams of S2-094178 [iii] respectively. 2.1-1 and FIG. 4-1, showing two use case scenarios. The first use case is when the UE voice configuration is set to “IMS voice preferred, CS voice secondary”, and the second use case is UE voice. This is when the setting is set to “IMS voice only”. These figures show the required UE behavior for different combinations of network VoIMS indications and UE usage settings.

  First, referring to FIG. 1A, the behavior of the UE in response to the voice setting of “IMS voice preferred, CS voice secondary” is that the voice setting of the UE is IMS voice priority, CS voice priority. Beginning with block 1A-1, which simply indicates that it is set to secondary (IMS voice preferred, CS voice secondary). In block 1A-2, the UE initiates an EPS attach procedure (non-composite). In block 1A-3, the UE checks the IMS voice support indication from the network received as part of the response to the EPS attach procedure. If IMS voice is supported, at block 1A-4, the UE uses IMS voice. While attached to the system, the UE may perform a tracking area update / TAU periodically or when the UE moves to a different tracking area / tracking area (Tracking Area / TA). When performing a TAU, the UE may receive a new VoIMS indicator, in which case the UE processing returns to block 1A-3 where the VoIMS indicator is checked. If IMS voice is not supported, at block 1A-5, the UE performs a combined TA / LA update procedure for CSFB (also referred to as a combined TAU) as in TS 23.272. If successful, at block 1A-6, the UE stays in E-UTRAN and uses CSFB if it needs voice service. If the tracking area update procedure is successfully completed, the VoIMS indication received in the TRACKING AREA UPDATE ACCEPT message will be indicated in the upper layer. On the other hand, if unsuccessful, in block 1A-7, the UE checks the UE usage setting for the “Voice centric” or “Data centric” setting. If the configuration is data centric, at block 1A-8, the UE remains in the current RAT (E-UTRAN). On the other hand, if the setting is voice-centric, in block 1A-9, the UE selects another RAT from which voice service can be obtained.

  A compound registration procedure, such as a Combined Attach Procedure or Combined Tracking Area Update, is a single NAS registration procedure used to attempt to register with both PS and CS services. Voice services are provided on CSE-UTRAN using CS Fallback (CSFB). For example, in the EMM-REGISTRED state, a UE operating in CS / PS mode 1 or CS / PS mode 2 has failed, for example, in SIP registration to IMS and the usage setting of the UE is “Voice Centric”. The composite tracking region update procedure will be initiated when the UE receives an indication from the upper layer. An example of a combined attached procedure or combined tracking area update can be found in 3GPP TS 24.301.

  Success of the composite registration procedure means that the UE is registered with both PS and CS services. The failure of the composite procedure means that the UE is registered in the PS service but not registered in the CS service. For example, such a failure may include a tracking area update accept or attachment with an indication or cause value set to “CS domain not available” or a value indicating that the PS domain is not available. It may be indicated to the UE by the network sending the Attach Accept message. In addition, there can be other failures such as failures where the UE is not registered with the CS or PS service.

  As a result of the NAS registration procedure or EPS attach procedure, the UE that initiates the procedure is registered in the network. As a result of this NAS registration, the UE and the network obtain information that enables transmission and reception of (IP) messages as part of the non-access layer protocol. The UE and network can send and receive these (IP) messages. The acquired information at the UE and the network may need to be updated. The acquired information can be updated periodically (eg, upon expiration of a timer) or can be updated explicitly. The NAS registration can be a composite or non-composite NAS registration, and a successful composite NAS registration allows the UE to register for EPS services and non-EPS services.

  As used herein, the EPS service may be a GPRS service according to 3GPP TS 24.008. Non-EPS services are services provided by the CS domain. As used herein, a non-EPS service may be a non-GPRS service according to 3GPP TS 24.008. A UE that stays on E-UTRAN can attach to both EPS and non-EPS services. Non-Access Layer (NAS) protocol is a protocol between UE and Mobile Switching Center (MSC) or Serving GRPS Support Node (SGSN) that is not terminated in UTRAN, and is not terminated in E-UTRAN. Protocol between.

  In one implementation, a UE that initiates a NAS registration (eg, complex NAS registration) procedure may be an attach request (ATTACH REQUEST) (eg, complex attach request) message, or a tracking area update request (eg, complex area update request). At least one of the tracking area update request messages may be transmitted. After sending the message, the UE may receive at least one of an ATTACH REQUEST (eg, compound attach request) message or a Tracking Area Update Request (eg, compound tracking region update request) message. One can be received.

  In one implementation, a UE that updates NAS registration (eg, compound NAS registration) information may update routing area information when using a non-access layer protocol between the UE and the SGSN, or between the UE and the MME. It may include updating tracking area information when using a non-access layer protocol, or updating information when using a non-access layer protocol between the UE and the MSC. A UE that updates NAS registration (for example, complex NAS registration) information may perform tracking area update (TRACKING AREA UPDATE) (for example, complex tracking area update) and routing area update (for example, ROUTING AREA UPDATE) (for example, complex routing area update). At least one of them can be transmitted. After sending the message, the UE sends a TRACKING AREA UPDATE (eg, composite tracking area update) (accept / ACCEPT) response, a routing area update (ROUTING AREA UPDATE) (eg, composite routing area update) (accepted). / ACCEPT) response can be received. After successfully updating the NAS registration (eg, compound NAS registration) information, the UE is registered with the EPS service and the non-EPS service.

  In one implementation, after performing the NAS registration procedure, the UE may request service from the network. The UE then sends a service request (eg, extended service request) message to the network. For example, to perform CSFB, the UE is registered with an EPS service and a non-EPS service, and the UE sends an extended service request NAS protocol message. In response, the UE may receive a SERVICE REJECT message.

For example, in some implementations, if the UE receives an attach accept (ATTACH ACCEPT) message with an EMM cause value # 18 indicating “CS domain not available”, the UE conforms to the following in accordance with 3GPP TS 24.301: Measures can be taken.
If it is still running, the UE stops timer T3410, resets the tracking area update attempt counter, sets the EPS update state to EU1 UPDATED, and sets the state EMM-REGISTRED. You will enter NORMAL-SERVICE.
The UE will set the update state to U2 NOT UPDATED.
A UE that is in CS / PS mode 1 of operation may select a GERAN or UTRAN radio access technology rather than E-UTRAN for the selected PLMN or equivalent PLMN.
A UE that is CS / PS mode 2 of operation will not attempt a composite attach or tracking region update procedure with the current PLMN until the UE is switched off or the UICC including the USIM is removed.
A UE whose UE usage setting is “Data Centric” or “Data Only” provides a notification to the user or upper layer that the CS domain is not available.
If the UE usage setting is changed from “Data Centric” or “Data Only” to “Voice Centric”, E- An instruction will be provided to the AS to select GERAN or UTRAN radio access technology rather than UTRAN.

  In some implementations, the UE may disable cell selection and reselection for E-UTRAN cells if the NAS provides an indication to the AS to select GERAN or UTRAN while the UE is RRC_IDLE. If the NAS provides an indication to the AS to select GERAN or UTRAN or E-UTRAN while the UE is RRC_IDLE, the UE may allow cell selection and reselection to the E-UTRAN cell.

  In another implementation, if the service request cannot be accepted by the network, the network returns a SERVICE REJECT message containing the appropriate EMM cause value to the UE. Upon receiving a SERVICE REJECT message, the UE will stop timer T3417 and take appropriate action. For example, the EMM cause value may be # 18 (CS domain not available). If the request is related to CS fallback, the UE will send an indication to the MM sublayer and will not attempt CS fallback until the composite tracking region update procedure is fully completed. The UE then proceeds to state EMM-REGISTRED. You can enter NORMAL-SERVICE. If the UE usage setting is “Data Centric” or “Data Only”, the UE provides a notification to the user or upper layer that the CS domain is not available.

  Referring now to FIG. 1B, the behavior for a UE voice configuration of “IMS PS Voice only” begins at block 1B-1, which simply shows a UE configured for IMS PS voice only. In block 1B-2, the UE initiates an EPS attach procedure (non-composite). In block 1B-3, the UE checks the IMS voice response indication from the network. If IMS voice is supported, the UE uses IMS voice at block 1B-4. While attached to the system, the UE may perform Tracking Area Update / TAU periodically or when the UE moves to a different Tracking Area. When performing a TAU, the UE may receive a new VoIMS indicator, in which case the UE processing returns to block 1B-3 where the VoIMS indicator is checked. If IMS voice is not supported, at block 1B-5, the UE checks UE usage settings for "Voice centric" or "Data centric". If the setting is "Data centric", in block 1B-6, the UE remains in the current RAT (E-UTRAN). On the other hand, if the setting is “Voice centric”, in block 1B-7, the UE selects another RAT from which voice service can be obtained.

(First problem: Inability to start IMS registration)
The first problem associated with the behavior identified in FIGS. 1A and 1B referenced above is that there is no guarantee that the UE will initiate IMS registration. More specifically, when the VoIMS index indicates “IMS voice over PS session supported”, the UE is expected to “use IMS voice”, but the voice setting of the UE is not UE is indeed initiating IMS registration when set to "IMS PS voice only" and "IMS voice preferred, CS voice secondary" There is no guarantee. If the VoIMS indicator indicates "IMS Voice over PS session supported", the UE knows that there is no NAS or AS reason to mean that voice service cannot be realized on IMS. Yes. However, in order for this to be achieved, the UE must first initiate IMS registration.

  Reference to IMS registration to the IMS subsystem generally refers to any of the networks that use IMS to send information to and receive information needed to be able to receive information from the UE. Can be understood as referring to the method. Thus, the network uses IMS to send information to the UE and obtains information required to be able to receive information from the UE, or the network has no information. The network may not have the information due to a registration failure or because the UE could not register (eg, the UE has not started IMS registration to provide the information to the network). SIP registration of voice services to the IMS subsystem according to 3GPP TS 24.229 is a specific example.

  When performing IMS service registration for voice services, the UE must include the proper indication so that the IMS subsystem knows that it is requesting voice services. If the proper indication is not included or not allowed, the UE that remains on the IMS-enabled E-UTRAN cell still does not receive IMS voice service or IMS voice mobile termination session request.

In some implementations, to ensure that the UE reacts appropriately and initiates IMS registration, the UE behaves as follows.
UE voice setting = “IMS PS voice only” or UE voice setting = “IMS voice preferred, CS voice secondary”,
And, when the VoIMS index indicates “IMS voice over PS session supported”,
The IMS registration is then triggered by the appropriate indicator requesting voice service support.

  For example, when the attach procedure is successfully completed, the VoIMS indicator in the attach accept (ATTACH ACCEPT) message indicates “IMS voice over PS session supported (IMS Voice over PS session supported) and receives the voice setting of the UE. Due to the start of SIP registration with IMS, the successful completion of the attach procedure is indicated in the upper layer.

  As indicated above, in some implementations, IMS registration is accomplished through SIP registration. Examples of SIP messages are SIP requests and SIP responses. Examples of SIP requests are SIP INVITE or SIP REGISTER. Examples of IMS functional elements are P-CSCF, S-CSCF, I-CSCF, AS, SCC AS, HSS.

  IMS registration can be performed using a SIP registration request, as described in IETF RFC 3261, and the SIP registration request is documented in 3GPP TS 23.228 and 3GPP TS 24.229, Processed by IMS functional elements.

  FIG. 2A shows a detailed flowchart of an example implementation for the case where the voice setting of the UE is set to “IMS voice preferred, CS voice secondary”. The figure differs from FIG. 1A in the inclusion of block 2A-1 involving attempting IMS registration with the proper indication for voice service. In 1A-4, if the UE uses block IMS voice and then performs TAU, the UE checks the VoIMS indication again in block 1A-3, and if VoIMS is supported, in block 2A-1 If the UE is not already IMS registered with the voice service, the UE will only attempt IMS registration using the appropriate indicator for the voice service.

  FIG. 2B shows a detailed flowchart of an example implementation for the case where the UE voice configuration is set to “IMS PS voice only”. The figure differs from FIG. 1B in the inclusion of block 2B-1 involving attempting IMS registration with the proper indication for voice service. In block 1B-4, if the UE uses IMS voice and then performs TAU, the UE checks the VoIMS indication again in block 1B-3, and if VoIMS is supported, in block 2B-1, If the UE is not already IMS registered with the voice service, the UE will only attempt IMS registration using the appropriate indicator for the voice service.

(Second problem: IMS registration for voice may fail)
A second problem associated with the behavior described above with reference to FIGS. 1A and 1B is that there is no guarantee that IMS registration for voice will be successful. More specifically, there is no guarantee that IMS registration for voice will succeed just because EPS attach or Tracking Area Update is successful and the network supports IMS voice. One example of why registration may fail is because SIP registration does not allow it due to restrictions on user subscriptions. Another example of the reason is that IMS registration fails due to a retracted message or delay in receiving the message. If IMS registration fails and the UE does nothing and remains EPS-attached, but it is not IMS registered with the voice service, an IMS voice session that is mobile origination or mobile termination cannot be realized. This same situation indicates that the SIP registration was successful, but the indicator in the voice service request was not allowed (i.e. the requested indicator for voice was returned in the SIP 200 OK response to the SIP registration request. May not exist). In this case, the UE may be registered with the IMS for use of some services, but may not be allowed to use this registration to carry voice media.

Example 1
In some implementations, the UE has failed IMS registration for voice and the UE's voice setting is set to “IMS Voice Preferred, CS Voice Secondary” Is configured to address this problem. Recognizing this situation, the UE is configured to immediately try the composite registration procedure. This then allows the UE to obtain voice service using CSFB if supported. If the composite registration procedure fails, the UE considers the UE usage settings. If the usage setting of the UE is “Voice Centric” or “Data Centric”, the UE selects another RAT from which voice service can be obtained. If the UE usage setting is “Data Only”, the UE remains in the current RAT (ie, E-UTRAN) without accessing the voice service.

  FIG. 3A shows a detailed flowchart of an implementation for this case. The figure shows that if IMS registration fails after the induction of IMS registration in block 2A-1, as shown at 30, with the implementation of a composite registration procedure for CSFB as in TS 23.272, the process Is different from FIG. 2A in that it continues at block 1A-5. In addition, if the UE is “data only” (as shown at 32), block 1A-8 (stays in the current RAT) is performed and the UE is “voice-centric” (as shown at 34). "Or" Data Center ", block 1A-9 is performed (UE selects another RAT).

  FIG. 3B shows a detailed flowchart of an example implementation for the case where the UE voice configuration is set to “IMS PS voice only”. The figure shows that if IMS registration fails after inducing IMS registration in block 2B-1, as shown at 36, the UE checks the UE usage settings in block 1B-5. Is different. If the UE usage setting is "Data Only" (as shown at 38), the UE remains in E-UTRAN at block 1B-6 and cannot access voice services. If the UE usage setting is “Voice centric” (as shown at 40), or if the UE usage setting is “Data Centric”, then the UE will block 1B. At -7, select another RAT from which voice service can be obtained.

(Example 2A)
In some implementations, the UE addresses this issue by recognizing that the voice service IMS registration has failed and the UE's voice setting is set to “Data Only”. Configured as follows. Recognizing this situation, the UE is configured to remain in the EPS that can provide the best PS service. More specifically, the UE stays in E-UTRAN (“Current RAT” in the figure) and does not select another RAT. The best PS service can be provided by E-UTRAN. PS services can also be provided in GERAN / UTRAN, but these RATs are provided in a less optimized manner. The UE does not make a composite registration attempt, but instead the UE is configured to retry the IMS registration procedure for the voice service. The UE may be successfully registered with the IMS for other services, but as described above, access to the voice service may be denied, in which case the UE performs an IMS registration procedure for the voice service. Note that we will try again. In other implementations, there are multiple retries, which can be performed periodically, for example.

An example of this behavior is depicted in FIGS. 4A and 4B. First, referring to FIG. 4A, FIG. 4A is the same as FIG. 2A except for the following three differences.
The UE makes one or more attempts at 50 after IMS registration fails.
If the usage setting of the UE is “data only”, block 1A-8 is executed after block 1A-7 (shown at 52).
Block 1A-9 is executed after block 1A-7 (shown at 54) when the UE usage setting is "voice center" or "data center".

Referring now to FIG. 4B, FIG. 4B is the same as FIG. 2B except for the following three differences.
The UE makes one or more attempts at 56 after IMS registration fails.
If the UE usage setting is “data only”, block 1B-6 is executed after block 1B-5 (shown at 58).
If the UE usage setting is “voice center” or “data center”, block 1B-7 is executed after block 1B-5 (shown at 60).

(Example 2C)
In some implementations, if the combined attach procedure described in Example 1 above fails and the UE usage setting is “Data Only”, the UE indicates that the voice service is not available. Notify the user (via user interface or some other alert). For example, if the voice service cannot be realized, an indicator can be presented to the user. Any indication to the user (eg, display, audio, vibration, etc. only) to inform the user that voice service is not currently available even if the UE is in the service area Can be used.

An example of this behavior is depicted in FIG. 5A, which is the same as FIG. 2A with the following differences.
Upon IMS registration failure at 70 after the IMS registration attempt, the UE performs a complex TAU at block 1A-5.
After block 1A-7, if the UE usage setting is “data only”, the UE notifies the user that the voice service is not available in block 5A-1, and the UE remains in the current RAT. (Indicated at 72).
Block 1A-9 follows block 1A-7 (shown at 74) when the UE usage setting is "voice center" or "data center".

Another example of this behavior is depicted in FIG. 5B, which is the same as FIG. 2B with the following differences.
Upon IMS registration failure at 71 after the IMS registration attempt, the UE checks the UE usage settings for “Voice Centric” or “Data Centric” in block 1B-5.
After block 1B-5, if the usage setting of the UE is “data only”, the UE notifies the user that the voice service is not available in block 5B-1, and the UE remains in the current RAT. (Indicated at 73).
Block 1B-7 follows block 1B-5 (shown at 75) when the UE usage setting is "voice center" or "data center".

  When notified that the voice service is not available, the user may choose to change the UE usage setting to “Voice Centric” or “Data Centric”. Since the UE has already tried the composite registration procedure and the attempt has failed, changing the UE usage setting to “Voice Centric” or “Data Centric” Have another RAT (GERAN / UTRAN, etc.) that can provide audio selected.

  In some implementations, the notification to the user that the voice service is not available also includes a prompt asking the user if they want to change the UE usage settings to obtain the voice service.

An example of this behavior is depicted in FIG. 6A. FIG. 6A is the same as FIG. 5A with the following differences.
If after block 5A-1, the user accepts "data only", the UE remains in the current RAT at block 1A-8 (shown at 82).
If after block 5A-1, the user changes the UE usage setting to "voice only" or "data only", the UE selects another RAT in block 1A-9 (shown at 84). .

  In some implementations, when the usage setting of the UE is changed from “data-centric” to “voice-centric”, the UE may select a GERAN or UTRAN radio rather than E-UTRAN for the selected or equivalent PLMN. Provide instructions to the AS to select an access technology. For example, such a process may be completed after the UE receives EMM cause value # 18.

Another example of this behavior is depicted in FIG. 6B. FIG. 6B is the same as FIG. 5B with the following differences.
If after block 5B-1, the user accepts "data only", the UE remains in the current RAT at block 1B-6 (shown at 100).
After block 5B-1, if the user changes the UE usage setting to “voice only” or “data only”, the UE selects another RAT in block 1A-9 (shown at 102). .

(Example 2D)
When IMS registration fails after one or more retries and the composite registration procedure is not automatically attempted, the voice setting of the UE is “IMS Voice Preferred, CS Voice Secondary”. And the UE usage setting “Data only” or the UE voice setting is “IMS PS Voice Only” and the UE usage setting is “Data”. When set to “Data only”, the UE is configured to notify the user (via a user interface or some other alert) that the voice service is not available. In this case, the user may choose to change the usage setting of the UE to “Voice Centric” or “Data Centric”. This is a compound registration procedure (UE's voice configuration that, if successful, allows the UE to remain in the ESP until voice service is needed, in this case using CSFB to obtain the voice service. Prompts the UE to try “IMS Voice Preferred, CS Voice Secondary”. When the UE voice setting is “IMS PS Voice Only”, the user changes the UE usage setting to “Voice Centric” or “Data Centric”. It will prompt the UE to reselect another RAT that may support voice service.

An example of this behavior is depicted in FIG. 7A. FIG. 7A differs from FIG. 2A in the following points.
After IMS registration failure (112), the UE notifies the user in block 7A-1 that voice service is not available.
If the user indicates "Voice Centric" or "Data Centric" (116), the method continues at block 1A-5.
If the user indicates "Data only", IMS registration is not retried (114) and then the method continues at block 1A-8.
If the UE usage setting is “Voice Centric” or “Data Centric” (118), block 1A-9 follows block 1A-7.

Another example of this behavior is depicted in FIG. 7B. FIG. 7B differs from FIG. 2B in the following points.
After IMS registration failure (122), the UE notifies the user in block 7B-1 that the voice service is not available.
If the user indicates “Voice Centric” or “Data Centric” (124), the method continues at block 1B-5.
If the user indicates "Data only", IMS registration is not retried (128), and the method then continues at block 1B-6.
If the UE usage setting is “Voice Centric” or “Data Centric” (126), block 1B-9 follows block 1B-5.

(Example 2E)
Continuing with Example 2D, in some implementations, the user is instructed that the IMS registration (original number or some number of attempts) has failed, and alternatively, the user is prompted to “re-register IMS registration for voice”. This request may cause a UE to retire from the UE usage setting set to “Data Centric” or “Voice Centric” and cause periodic attempts in IMS registration. Can be prompted to resume until successful or until a certain number of attempts are attempted and failed. Alternatively, the user can indicate “Data Only”, in which case the UE retreats from the UE usage setting set to “Data Centric” and the UE Do not retry IMS registration.

Another example of this behavior is depicted in FIG. 7C. FIG. 7C differs from FIG. 7A in the following points.
After IMS registration failure (112), the UE informs the user that the voice service is not available at block 7A-1 and if the user indicates "RETRY" at 110, the method is Continue with block 2A-1.

Another example of this behavior is depicted in FIG. 7D. FIG. 7D differs from FIG. 7C in the following points.
After IMS registration failure (122), the UE informs the user that the voice service is not available in block 7B-1, and if the user indicates "RETRY" at 120, the method is Continue with block 2A-1.

(Example 3A)
In some implementations, the UE is configured to recognize a situation where IMS registration has failed and the usage setting of the UE is “Voice Centric”. When the UE recognizes this situation, the voice setting of the UE is “IMS PS voice only” or “IMS Voice Preferred, CS Voice Secondary”. Regardless of whether or not there is configured to trigger the AS to select / reselect another RAT (target RAT) (eg, GERAN / UTRAN) that can implement the voice service.

A first detailed example of this behavior is depicted in FIG. 8A. FIG. 8A differs from FIG. 2A as follows.
After IMS registration failure at 130, the UE checks the UE usage settings for "Voice Centric" or "Data Centric" in block 8A-1.
If the setting is “Data Centric” or “Data Only” as indicated at 132, the method continues at block 1A-5.
If the setting is “Voice Centric” as shown at 138, the method continues at block 1A-9 with the selection of another RAT.
Block 1A-8 follows block 1A-7 for a UE usage setting of “Data only” (indicated by 134).
Block 1A-9 follows block 1A-7 for cases where the UE usage setting is “Voice Centric” or “Data Centric” (indicated by 136).

A second detailed example of this behavior is depicted in FIG. 8B. FIG. 8B differs from FIG. 2B as follows.
After IMS registration failure at 140, the UE checks UE usage settings for “Voice Centric” or “Data Centric” in block 8B-1.
If the setting is “Data Only” as indicated at 142, the method continues at block 1B-6.
If the setting is “Voice Centric” or “Data Centric” as indicated at 144, the method continues at block 1B-7 with the selection of another RAT.
Block 1B-6 follows block 1B-5 for the case where the UE usage setting is “Data Only” (indicated by 146).
Block 1B-7 continues to block 1B-5 for the case where the UE usage setting is “Voice Centric” or “Data Centric” (indicated by 148).

(Example 3B)
In some implementations, once the UE knows that the target system can support IMS voice, following RAT reselection as described with reference to Example 3A above, once the target Once in the system, it is configured to retry IMS registration. If this subsequent attempt at IMS registration at the target system fails, then the UE may obtain voice service via the CS at the target system.

  A first example of this behavior is depicted in FIG. 9A, which is the same as FIG. 8A with the addition of blocks 9A-1, 9A-2, and 9A-3. After block 1A-9, the UE retries IMS registration for voice if it finds in block 9A-1 that the target system can support IMS voice. If successful, the UE obtains voice service via PS in the target system at block 9A-2. If unsuccessful, the UE obtains voice service via CS in the target system at block 9A-3.

  A second example of this behavior is depicted in FIG. 9B, which is the same as FIG. 8B with the addition of blocks 9B-1, 9B-2, and 9B-3. After block 1B-7, the UE retries IMS registration for voice if it finds in block 9B-1 that the target system can support IMS voice. If successful, the UE obtains voice service via PS in the target system at block 9B-2. If unsuccessful, the UE obtains voice service via CS in the target system at block 9B-3.

(Third problem: UE may be bound by inappropriate RAT)
A third problem associated with the behavior identified in FIGS. 1A and 1B is that the UE may be bound with an inappropriate RAT. More specifically, if the UE usage setting in FIGS. 1A and 1B is set to “Data Centric”, this may lead to the UE not getting any voice service. “Data Centric” in FIGS. 1A and 1B means that the UE only asks for data service (even if it excludes any voice service), ie “Data Only” This is not a problem. This behavior is problematic if the “data center” in FIGS. 1A and 1B is interpreted to mean “Data Centric” as defined herein above.

  In addition, since the network VoIMS indication (this indication is per tracking region and therefore within the registered tracking region) did not indicate support, the UE remains in the current RAT and cannot access voice services, If the UE enters the GERAN / UTRAN radio coverage routing area or the E-UTRAN coverage tracking area as indicated by the network VoIMS indicator that IMS PS voice is supported, It is necessary to retry IMS registration for.

  In another situation, the UE voice setting is “IMS PS Voice Only” or “IMS Voice Preferred, CS Voice Secondary” and the UE usage setting. Is set to “Voice Centric” or “Data Centric”, if voice services over IMS in LTE or GERAN / UTRAN may be available due to UE mobility However, the UE may eventually stay in GERAN / UTRAN and use CS voice service for voice. As the UE moves, it may move into a new E-UTRAN tracking area or a new GERAN / UTRAN routing area service area that supports IMS voice, in which case the UE may be on GERAN / UTRAN or LTE IMS voice services can be obtained above, and for “data-centric” UEs, there is a possibility that PS services can be better obtained on LET if not bound to GERAN / UTRAN.

Example 1
In some embodiments, the UE may have the UE usage setting set to “Data Only” and the UE voice setting may be “IMS PS Voice Only” or “IMS Voice Priority, CS Voice Secondary (CS Voice Secondary) ”, and when trying to attach EPS, it is known that“ IMS Voice over PS session not supported ”(IMS Voice over PS session supported) It is configured to recognize the situation, so that the UE stays in E-UTRAN without access to voice services. IMS voice over PS session support is per tracking area (Tracking Area / TA). The UE is then configured to monitor the TA of neighboring E-UTRAN cells until a cell with a different TA / RA (or alternatively, a cell with a TA outside the UE TAI list) is detected. Upon detecting such an LTE cell, the UE attempts to stay on this cell and sends a tracking area update to the network as part of this process. In response to this, the UE receives a tracking area update (Tracking Area Update) response. The Tracking Area Update response includes the network VoIMS indication for this tracking area. If the indicator is “IMS Voice over PS session supported”, the UE retries IMS registration with the indicator requesting voice service. The following behavior may follow the implementation described above, for example, handling IMS registration failures.

  An example of this behavior is depicted in FIG. 10A. When the UE reaches block 1A-8, the scenario described above may occur. The method continues at block 10A-1 where the UE monitors the TAs of neighboring E-UTRAN cells until a cell with a different TA (or alternatively, a cell with a TA outside the UE TAI list) is detected. In block 10A-2, upon detecting such a cell, the UE attempts to stay on this cell and sends a Tracking Area Update to the network as part of this process. In response to this, the UE receives a tracking area update (Tracking Area Update) response. The Tracking Area Update response includes the network VoIMS indication for this tracking area. If the indicator is “IMS Voice over PS session supported” (block 10A-3), then the UE uses the indicator for requesting voice service in block 10A-4 to register with IMS. Try again. The following behavior may follow the implementation described above, for example, handling IMS registration failures. For UE voice configuration with IMS PS voice only, steps 10A-1, 10A-2, 10A-3, and 10A-4 follow block 1B-6 in FIG. 2B.

(Example 2)
In some embodiments, the UE may set the UE usage setting to “Voice Centric” or “Data Centric” and the UE voice setting to “IMS PS Voice Only”. Only ”or“ IMS Voice Preferred, CS Voice Secondary ”, and when attempting to attach an EPS, a VoIMS indicator is received and“ IMS Voice over PS session not supported ( IMS Voice over PS session not supported), so that the UE can use GERAN / UTRA with data services with voice services but not optimal. Stay on. In this case, if the UE is in idle mode, the UE will attempt to reselect a suitable discovered E-UTRAN cell (eg, at regular intervals or based on a timer one or more times). Configured as follows. As explained above, this process induces periodic tracking region updates when the UE voice configuration is “IMS PS Voice Only”, or the UE voice configuration is In the case of “IMS Voice Preferred, CS Voice Secondary”, a compound tracking area update is induced. If the VoIMS indication obtained during the TAU or combined TA / LA update procedure indicates that IMS voice is supported, then the UE will continue to attempt IMS registration with the indication requesting voice service. . The following behavior may follow the implementation described above, for example, handling IMS registration failures.

  An example of this behavior is depicted in FIG. 10B for a UE voice setting of “IMS PS Voice Only”. When the UE reaches block 1B-7, the scenario described above may occur. In this case, when the UE is in idle mode, the UE attempts to reselect a suitable discovered E-UTRAN cell at block 10B-1 (eg, at regular intervals or based on a timer). (One or more times). This process induces periodic tracking area updates when the UE voice configuration is “IMS PS Voice Only”, or the UE voice configuration is “IMS voice priority, CS voice second”. If it is “IMS Voice Preferred, CS Voice Secondary”, it triggers a composite tracking region update. If the VoIMS indication obtained during the TAU or combined TA / LA update procedure indicates that IMS voice is supported, the UE continues with 10B-2 using the indication for requesting voice service. Attempt IMS registration. For UE voice configuration of “IMS Voice Preferred, CS Voice Secondary”, steps 10B-1 and 10B-2 follow block 1A-9 of FIG. 2A.

  Another example is depicted in FIG. 10C. When the UE reaches block 1A-9, the scenario described above may occur. The method continues at block 10C-1 where the UE determines that the RA of the current cell is different from the previous RA. In block 10C-2, upon detecting such a cell, the UE sends a Routing Area Update to the network as part of this process. In response to this, the UE receives a Routing Area Update response. The Routing Area Update response includes the network VoIMS indication for this routing area. If the indicator is “IMS Voice over PS session supported” (block 10C-3), the UE registers in IMS using the indicator for requesting voice service in block 10C-4. Try again. The following behavior may follow the implementation described above, for example, handling IMS registration failures. For UE voice configuration with IMS PS voice only, steps 10C-1, 10C-2, 10C-3, and 10C-4 follow block 1B-6 in FIG. 2B.

  In some implementations, SIP registration to the IP multimedia subsystem fails when the MS is in the states GMM-REGISTRED and MM-IDLE, when the network operates in network operation mode I, and in Iu mode. And when the UE receives an indication from the upper layer that the UE usage setting is “Voice Centric”, the composite routing region update procedure may be initiated by a GPRS MS operating in MS operating mode A or B .

  One aspect of a possible embodiment described for Problem 3 is that the UE performs a VoIMS for TA or RA by performing a NAS registration procedure such as Tracking Area Update or Routing Area Update. To get an indicator. This registration procedure requires signaling between the UE and the network. For example, the NAS registration response message may be a response to an EPS attach procedure, a tracking area update response, a routing area update response, an attach acceptance (ATTACH ACCEPT) response, or a tracking region update acceptance (TRACKING). AREA UPDATE ACCEPT) response. In some implementations, the network is configured to broadcast the VoIMS indication as part of the broadcast system information transmitted by all cells. An example of how this VoIMS indicator can be used can be considered a minor variation of the implementation described in FIG. 10B. Instead of a UE (as shown in block 10B-1 in FIG. 10B) that re-selects the E-UTRAN cell at regular intervals and performs a tracking area update to obtain a VoIMS indication The UE can read the broadcast system information of the E-UTRAN cell at regular intervals to obtain the VoIMS index. If the VoIMS indicator obtained in the broadcast system information indicates that IMS voice is supported, the UE continues to attempt IMS registration using the indicator requesting voice service in 10B-2.

(Fourth problem: after the UE usage setting is changed to “Data Only”, it returns to “Voice Centric” or “Data Centric”)
A fourth problem associated with the behavior identified in FIGS. 1A and 1B referenced above is that in some situations it may be desirable to change the UE usage settings. For example, if the UE is downloading a large amount of data, the UE usage setting is “Data” so that the UE uses E-UTRAN even if the voice service is not available on the E-UTRAN. It may be desirable to be "Data only". When a large amount of data has been downloaded, then the UE usage setting is again “voice-centric (to ensure that voice is available, even if another RAT is selected. It may be desirable to become “Voice Centric” or “Data Centric”. A specific problem is that the user sets the UE usage setting to “data only” but then reverts the setting back to “Voice Centric” or “Data Centric” at a later stage. That you may forget.

Example 1
More specifically, based on user preferences or based on the requirements of applications running on the UE, the UE usage settings in FIGS. 1A and 1B referred to above are set to “Data Centric”. If done, the UE usage preference gives priority to the data service, and thus modifies to “Data Only” to allow the UE to select the best RAT for the data service (ie, E-UTRAN) Can be done. However, it is desirable to be able to later modify the UE usage settings to the original values (ie, “Voice Centric” or “Data Centric”). As an example, the UE usage settings may be changed later by the user. In another embodiment, the application running on the UE is either “Voice Centric” or “Data Centric” based on which the application or user sets the UE usage setting to “Data Only”. Even when changing to (Data Only), we need the best PS service available. However, once the application is terminated, the application or UE returns the UE usage setting to its original value, ie “Voice Centric” or “Data Centric”.

  In such a scenario, once the UE usage setting is changed to “Data Only”, the UE will eventually behave as described in the implementation above for the “Data Only” UE. Based on the RAT. However, once the UE usage settings are modified back to the original values, the UE should try to attach to the appropriate RAT and access voice services based on the availability of the IMS and the UE's UE voice settings. It is. However, with the current behavior defined for the UE, the UE does not attempt to reselect the appropriate RAT or register with the IMS if IMS is available.

  In some scenarios, the UE usage settings may be “Data Centric” or by the user or UE-running application (or set of applications) to allow the best PS service for the UE-running application. It is modified from “Voice Centric” to “Data Only”. Later, the UE usage setting is restored to the original setting based on a set of possible triggering conditions. As a result, one of the means described in the above implementations for a UE based on UE voice configuration to discover whether IMS voice is available, register with IMS and select an appropriate RAT. Do more than one.

  Referring to FIG. 11A, in an implementation, an application (or set of applications) running on the UE modifies the UE usage settings at block 11A-1. In block 11A-2, the application that modified the UE usage settings is terminated (or alternatively, the application required for “data only” operation is terminated) and the UE usage settings are restored to their original values. When the UE voice setting is “IMS Voice Preferred, CS Voice Secondary”, the UE sets the UE voice setting to “IMS Voice Preferred, IMS Voice Preferred, It behaves like the implementation above for a UE that is “CS Voice Secondary”. If the UE voice setting is “IMS PS Voice only”, the UE behaves like the above implementation for a UE whose UE voice setting is “IMS PS Voice only”. To do. This is generally indicated by block 11A-3.

  Referring to FIG. 11B, in the implementation, the user requests a mobile outgoing voice call at block 11B-1. In response to the request for the mobile outgoing voice call, the UE returns to “Voice Centric” or “Data Centric” so that the voice call can be established at block 11B-2. The UE then behaves like the implementation of FIG. 11A depending on the UE voice settings. This entails returning to the original UE usage setting at block 11B-3 and then continuing one of the methods described above (11B-4).

  Referring to FIG. 11C, in an implementation, the UE receives an email with voice mail as an attachment at block 11C-1. Upon receipt of this email, the UE returns to “Voice Centric” or “Data Centric” in block 11C-2 so that the unaccepted call can be returned. The UE then behaves like the implementation of FIG. 11A depending on the UE voice settings. This entails returning to the original UE usage configuration at block 11C-3 and then continuing with one of the methods described above (11C-4).

  Referring to FIG. 11D, in an implementation, the user receives an SMS indication in block 11D-1 that voice mail is waiting or could not receive a call. Upon receipt of this SMS, the UE establishes a voice call and collects voice mail and / or returns to the call that was not received, to “Voice Centric” or “Data Center (Data Return to “Centric)”. The UE then behaves like the implementation of FIG. 11A depending on the UE voice settings. This entails returning to the original UE usage configuration at block 11D-3 and then continuing one of the methods described above (11D-4).

  Referring to FIG. 11E, in the implementation, an incoming IMS voice communication was received by the IMS infrastructure, but the IMS registration for IMS voice was not successful, so the voice call could not be delivered to the UE, and the UE In block 11E-1, a notification of such unaccepted call is received from the IMS. Upon receipt of this notification, the UE returns to “Voice Centric” or “Data Centric” at block 11E-2 so that it can return to the call that was not received. The UE then behaves like the implementation of FIG. 11A depending on the UE voice settings. This entails returning to the original UE usage configuration at block 11E-3 and then continuing one of the methods described above (11E-4).

  In all the above implementations, when modified by an application or user, repair can be achieved, for example, by storing the original UE usage settings and retrieving the values.

(Another mobile device)
Referring now to FIG. 12, a block diagram of a mobile communication device 700 that can implement the UE related methods described herein is shown. It should be understood that the mobile device 700 is shown with very specific details for illustrative purposes only.

  The processing device (microprocessor 728) is shown schematically as being coupled between a keyboard 714 and a display 726. Microprocessor 728 controls the operation of display 726 as well as the overall operation of mobile device 700 in response to user activation of keys on keyboard 714.

  The mobile device 700 has a housing (including a clamshell housing structure) that may be elongated vertically or may have other sizes and shapes. The keyboard 714 may include mode selection keys or other hardware or software for switching between text input and telephone input.

  In addition to the microprocessor 728, other parts of the mobile device 700 are shown schematically. These include a set of auxiliary I / O devices 706, a serial port 708, a speaker 711, and a communication subsystem 770, a short-range communication subsystem 702, a keyboard 714 and a display 726, and other input / output devices including a set of LEDs 704, and It includes a microphone 712 and memory devices including flash memory 716 and random access memory (RAM) 718 and various other device subsystems 720. Mobile device 700 may have a battery 721 to power the active elements of mobile device 700. Mobile device 700 is a two-way radio frequency (RF) communication device that, in some implementations, has voice and data communication capabilities. In addition, the mobile device 700 has the ability to communicate with other computer systems via the Internet in some implementations.

  The operating system software executed by the microprocessor 728 is stored in persistent storage such as flash memory 716 in some implementations, but other types of memory such as read only memory (ROM) or similar storage elements. It can be stored in a memory device. In addition, system software, specific device applications, or portions thereof may be temporarily loaded into volatile storage, such as RAM 718. In some implementations, one or more parameters representing signal array non-uniformity are stored in non-volatile memory or volatile storage. Communication signals received by mobile device 700 can also be stored in RAM 718.

  Microprocessor 728 enables execution of software applications on mobile device 700 in addition to its operating system functions. A predetermined set of software applications that control basic device operations such as voice communication module 730A and data communication module 730B may be installed on mobile device 700 during manufacture. In addition, a personal information manager (PIM) application module 730C may also be installed on the mobile device 700 during manufacture. PIM applications can organize and manage data items such as emails, calendar events, voice mails, appointments, and task items in some implementations. The PIM application may also send and receive data items over the wireless network 710 in some implementations. In some implementations, data items managed by the PIM application are seamlessly integrated via the wireless network 710, with the corresponding data items of the device user stored or associated with the host computer system. , Synchronized and updated. Similarly, additional software modules, illustrated as other software modules 730N, can be installed during manufacture.

Communication functions including data and voice communication are performed through communication subsystem 770 and possibly through short-range communication subsystem 702. Communication subsystem 770 includes a receiver 750, a transmitter 752, and one or more antennas illustrated as receive antenna 754 and transmit antenna 756. In addition, the communication subsystem 770 also includes a processing module, such as a digital signal processor (DSP) 758, and a local oscillator (LO) 760. The specific design and implementation of the communication subsystem 770 depends on the communication network that the mobile device 700 is intended to operate on. For example, the communication subsystem 770 of the mobile device 700 is designed to work with Mobitex ^™ , DataTAC ^™ , or General Packet Radio Service / GPRS mobile data communication networks, and also includes advanced mobile phone services ( Advanced Mobile Phone Service / AMPS), Time Division Multiple Access (Time Division Multiple Access / TDMA), Code Division Multiple Access / CDMA, Personal Communication System Mobile Personal CoS Mobile CoS It may be designed to operate with any of a variety of voice communication networks, such's (Global System for Mobile Communications / GSM (registered trademark)). Other types of data and voice networks, both segregated and integrated, may also be utilized with the mobile device 700. The particular device under consideration here is a multi-mode mobile device, as such they include hardware and / or software for implementing at least two RATs. More specifically, in particular embodiments, there is a respective communication subsystem 770 for each RAT implemented by the device.

Network access may vary depending on the type of communication system. For example, in the Mobitex ^™ and DataTAC ^™ networks, mobile devices are registered on the network using a unique personal identification number (PIN) associated with each device. However, in GPRS networks, network access is typically associated with device subscribers or users. Thus, GPRS devices typically have a subscriber identity module, commonly referred to as a subscriber identity module / SIM card, in order to operate on a GPRS network.

  Upon completion of the network registration or activation procedure, the mobile device 700 may send and receive communication signals over the communication network 710. The signal received from the communication network 710 by the receive antenna 754 is sent to a receiver 750 that provides signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog to digital conversion of the received signal allows the DSP 758 to perform more complex communication functions such as demodulation and decoding. Similarly, signals transmitted to network 710 are processed (eg, modulated and encoded) by DSP 758 and then digital to analog conversion, frequency up conversion, filtering, amplification, and communication network 710 via transmit antenna 756. Provided to transmitter 752 for transmission to (or multiple networks).

  In addition to processing communication signals, DSP 758 provides control of receiver 750 and transmitter 752. For example, the gain applied to the communication signal at receiver 750 and transmitter 752 can be adaptively controlled through an automatic gain control algorithm implemented in DSP 758.

  In the data communication mode, received signals such as text messages or web page downloads are processed by the communication subsystem 770 and input to the microprocessor 728. The received signal is then further processed by microprocessor 728 for output to display 726 or alternatively to some other auxiliary I / O device 706. The device user may also use the keyboard 714 and / or some other auxiliary I / O device 706, such as a touchpad, rocker switch, thumbhole, or some other type of input device, for data items such as email messages. Can be configured. The configured data may then be transmitted over communication network 710 via communication subsystem 770.

  In the voice communication mode, the overall operation of the device is substantially similar to the data communication mode except that the received signal is output to the speaker 711 and the signal for transmission is generated by the microphone 712. Alternative voice or audio I / O subsystems such as a voice message recording subsystem may also be implemented on the mobile device 700. In addition, the display 716 may also be utilized in a voice communication mode, for example, to display caller identification, duration of a voice call, or other voice call related information.

  The short-range communication subsystem 702 enables communication between the mobile device 700 and other proximity systems or devices that are not necessarily similar devices. For example, a short-range communication subsystem may include an infrared device and associated circuitry and components, or a Bluetooth® communication module to provide communication with similarly usable systems and devices.

  Many modifications and variations of the present invention are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims, the invention may be practiced other than as specifically described herein.

Claims (79)

A method in user equipment (UE) with at least one voice service indicator (VSI) in an evolved packet system (EPS) comprising:
Detecting a change in the value of the at least one VSI;
Causing the UE to notify the network in response to a change in the VSI. The at least one VSI is
UE usage settings,
The method of claim 1, comprising at least one of: UE voice configuration.   The method of claim 1, wherein the step of notifying the network comprises a Tracking Area Update message.   The method of claim 3, wherein the TRACKING AREA UPDATE message includes a Tracking Area Update message. The step of notifying the network includes:
Providing instructions to select a specific radio access technology (RAT) from the NAS to the access layer (AS), wherein the specific RAT is global system for mobile communication edge radio access (GERA) and universal mobile telephony; At least one of communication system terrestrial radio access (UTRA);
Removing the evolved UTRA (E-UTRA) RAT from the Capability Update message in response to the indication.   The method of claim 1, wherein the at least one indicator is a UE voice setting, and the value of the UE voice setting changes to a voice center.   The method of claim 4, wherein the change of the UE voice setting value includes the UE voice setting value changing to “voice center”. A method in a user equipment (UE) with a first indicator relating to a voice service in an evolved packet system (Evolved Packet System / EPS), comprising:
Receiving a non-access stratum / NAS protocol response message with a second indication;
Transmitting a notification that voice service is not currently available in response to at least one of the first indicator or the second indicator.   The method according to claim 8, wherein the NAS protocol response message is a NAS registration response message.   9. The method of claim 8, wherein one or both of the first indicator or the second indicator is a voice service indicator (VSI). The VSI is
IMS voice over PS session support (IMS Voice over PS session supported) instructions,
IMS voice over PS session not supported (IMS Voice over PS session not supported) instruction,
Voice-centric (Voice Centric),
Data centric (Data Centric),
CS voice only (CS Voice Only),
IMS PS Voice only (IMS PS Voice Only),
CS Voice Preferred, IMS Voice Secondary, IMS Voice Preferred, CS Voice Preferred, CS Voice Secondary (CS Voice Preferred, CS Voice Preferred)
The method of claim 10, wherein the method is set to at least one of the following: The VSI is
Voice over IP Multimedia Subsystem (Voice over IP Multimedia Subsystem / IMS VoPS) indicator;
UE usage settings,
The method of claim 10, wherein one or more of UE voice settings.   9. The method of claim 8, wherein the second indicator is at least one of a cause value or a failure indication. At least one of the cause value or the failure indication is:
Set to at least one of failure to register UE for circuit switched (CS) or packet switched (PS) services or CS domain not available;
The method of claim 13.   9. The method of claim 8, wherein sending the notification is performed by the UE and the notification is sent to at least one of a user or an upper layer. The NAS registration response message is:
Response to EPS attach procedure,
Tracking area update response (Tracking Area Update),
Routing Area Update response,
Attach (ATTACH) acceptance message,
SERVICE REJECT message,
9. The method of claim 8, wherein the method is at least one of a routing area update accept message or a tracking area update accept message.   9. The method of claim 8, wherein sending the notification is responsive to both the first indicator and the second indicator. A method in a user equipment (UE) with a first indicator relating to a voice service in an evolved packet system (Evolved Packet System / EPS), comprising:
Receiving a non-access stratum / NAS protocol response message with a second indication;
In response to at least one of the first indicator or the second indicator, sending a notification that a voice service is not currently available, the voice service currently providing The notification that it is not possible to include a notification that the CS domain is not available.   The method according to claim 18, wherein the NAS protocol response message is a NAS registration response message.   19. The method of claim 18, wherein one or both of the first indicator or the second indicator is a voice service indicator (VSI). The VSI is
IMS voice over PS session support (IMS Voice over PS session supported) instructions,
IMS voice over PS session not supported (IMS Voice over PS session not supported) instruction,
Voice-centric (Voice Centric),
Data centric (Data Centric),
CS voice only (CS Voice Only),
IMS PS Voice only (IMS PS Voice Only),
CS Voice Preferred, IMS Voice Secondary, IMS Voice Preferred, CS Voice Preferred, CS Voice Secondary (CS Voice Preferred, CS Voice Preferred)
21. The method of claim 20, wherein the method is set to at least one of: The VSI is
Voice over IP Multimedia Subsystem (Voice over IP Multimedia Subsystem / IMS VoPS) indicator;
UE usage settings,
21. The method of claim 20, wherein the method is one or more of UE voice configuration.   The method of claim 18, wherein the second indicator is at least one of a cause value or a failure indication. At least one of the cause value or the failure indication is:
Failure to register UE for circuit switched (CS) or packet switched (PS) services, or CS domain not available,
24. The method of claim 23, wherein the method is set to at least one of:   The method of claim 18, wherein sending the notification is performed by the UE and the notification is sent to at least one of a user or an upper layer. The NAS registration response message is:
Response to EPS attach procedure,
Tracking area update response (Tracking Area Update),
Routing Area Update response,
Attach (ATTACH) acceptance message,
SERVICE REJECT message,
19. The method of claim 18, wherein the method is at least one of a Routing Area Update Accept message or a Tracking Area Update Accept message.   The method of claim 18, wherein sending the notification is responsive to both the first indicator and the second indicator. A method in a user equipment (UE) with a first indicator relating to a voice service in an evolved packet system (Evolved Packet System / EPS), comprising:
Receiving a non-access stratum / NAS protocol response message with a second indication;
Transmitting a notification that voice service is not currently available in response to at least one of the first indicator or the second indicator.   30. The method of claim 28, wherein the NAS protocol response message is a NAS registration response message.   30. The method of claim 28, wherein one or both of the first indicator or the second indicator is a voice service indicator (VSI). The VSI is
IMS voice over PS session support (IMS Voice over PS session supported) instructions,
IMS voice over PS session not supported (IMS Voice over PS session not supported) instruction,
Voice-centric (Voice Centric),
Data centric (Data Centric),
CS voice only (CS Voice Only),
IMS PS Voice only (IMS PS Voice Only),
CS Voice Preferred, IMS Voice Secondary, IMS Voice Preferred, CS Voice Preferred, CS Voice Secondary (CS Voice Preferred, CS Voice Preferred)
32. The method of claim 30, wherein the method is set to at least one of the following. The VSI is
Voice over IP Multimedia Subsystem (Voice over IP Multimedia Subsystem / IMS VoPS) indicator;
UE usage settings,
32. The method of claim 30, wherein the method is one or more of UE voice configuration.   The method of claim 18, wherein the second indicator is at least one of a cause value or a failure indication. At least one of the cause value or the failure indication is:
34. The method of claim 33, set to at least one of failure to register a UE for circuit switched (CS) or packet switched (PS) service or CS domain not available. .   The method of claim 18, wherein sending the notification is performed by the UE and the notification is sent to at least one of a user or an upper layer. The NAS registration response message is:
Response to EPS attach procedure,
Tracking area update response (Tracking Area Update),
Routing Area Update response,
Attach (ATTACH) acceptance message,
SERVICE REJECT message,
19. The method of claim 18, wherein the method is at least one of a Routing Area Update Accept message or a Tracking Area Update Accept message.   The method of claim 18, wherein sending the notification is responsive to both the first indicator and the second indicator. A method in a user equipment (UE) with a first indicator relating to a voice service in an evolved packet system (Evolved Packet System / EPS), comprising:
Receiving a non-access stratum / NAS protocol response message with a second indication;
Determining the availability of a voice service on an IP Multimedia Subsystem / IMS in response to at least one of the first indicator or the second indicator.   The step of determining the availability of voice services on the IP Multimedia Subsystem (IMS) is Long Term Evolution (LTE) or Global System for Mobile Communications Edge Radio Access Network (GERAN) / Universal Mobile Telecommunications System Terrestrial Radio Access Network 39. The method of claim 38, comprising determining the availability of voice services on an IP multimedia subsystem (IMS) in at least one of (UTRAN).   40. The method of claim 38, wherein the NAS protocol response message is a NAS registration response message.   39. The method of claim 38, wherein at least one of the first indicator or the second indicator is a voice service indicator (VSI).   40. The method of claim 38, wherein the second indicator is VSI, and the VSI is a Voice over IP Multimedia Subsystem / IMS VoPS indicator. One or more of the VSIs are
IMS Voice over PS session support (IMS Voice over PS session supported) instructions,
IMS voice over PS session non-supported (IMS Voice over PS session supported) instruction,
Voice-centric (Voice Centric),
Data-centric (Data Centric),
Only CS voice (CS Voice Only)
IMS PS voice only (IMS PS Voice Only)
CS voice priority, IMS voice secondary (CS Voice Preferred, IMS Voice Secondary),
43. The method of claim 42, set to IMS Voice Priority, CS Voice Preferred, CS Voice Secondary.   40. The method of claim 38, wherein the second indicator is at least one of a cause value or a failure indication. At least one of the cause value or the failure indication is:
Failure to register the UE for circuit switched (CS) or packet switched (PS) services, or CS domain not available,
Set to
45. The method of claim 44.   The method of claim 38, wherein determining the availability of the voice service further comprises initiating IMS registration if the UE is not yet IMS registered.   47. The method of claim 46, wherein initiating IMS registration when the UE is not yet IMS registered is determined by at least one of the first indicator or the second indicator.   The step of initiating IMS registration is a trial of IMS registration using at least one of the first indicator or the second indicator when the UE is not yet IMS registered for voice service. 48. The method of claim 46, further comprising the step of: Determining the availability of the voice service comprises:
A UE that has not initiated an IMS registration attempt;
IMS registration failure after IMS registration attempt;
Refusal due to user subscription restrictions;
Withdrawn message,
Delayed messages and
40. The method of claim 38, including the step of determining invalidity of transmission of audio media. After an IMS registration attempt,
Terminating further trials as a result of repeated trials to register with the IMS;
Suspending further attempts for the user to register with the IMS after repeated attempts have failed,
47. The method of claim 46, followed by at least one of a user initiated deregistration step, or the UE is deregistered by a network. At least one of the first index or the second index is:
The UE usage setting is not voice-centric,
At least one of the UE voice setting is PS voice only, or the voice setting of the UE is CS voice priority, IMS voice secondary (IMS Voice Secondary) 48. The method of claim 47, comprising at least one voice service indicator set to.   The NAS protocol response message is a NAS registration response message, and the step of initiating the IMS registration when the UE is not yet IMS registered is a NAS indicating a successful completion of at least one of an attach or registration update. 48. The method of claim 47, determined from a registration response message.   41. The method of claim 40, wherein the NAS registration response message is received by a lower layer of the UE.   40. The method of claim 38, wherein availability of voice service on IMS varies with mobility of the UE. After determining that voice service on IMS is available, the UE determines that voice service on IMS in at least one of LTE or GERAN / UTRAN is not available,
Composite tracking area update for CSFB, (Combined Tracking Area Update),
At least one of selecting or reselecting another radio access technology (RAT) capable of providing voice service;
Selecting at least one of GERAN or UTRAN radio access technologies, or switching off or removing a universal integrated circuit card (UICC) including a universal subscriber identity module (USIM) 40. The method of claim 38, comprising: performing at least one of up to one, not selecting an evolved UTRAN (E-UTRAN) radio access technology. Determining the availability of voice service on the IMS determines that voice service on the IMS in at least one of LTE or GERAN / UTRAN is available, and thereafter
39. The method of claim 38, further comprising performing at least one of user initiated deregistration or network deregistration. Determining the availability of voice service on the IMS determines that the voice service on the IMS in at least one of LTE or GERAN / UTRAN is not available;
Receiving a second NAS registration response message with a third indicator;
39. The method of claim 38, further comprising: performing IMS registration if the UE is not yet IMS registered as determined by the third indicator.   The step of receiving the second NAS registration response message with the third indication includes at least one of a cell with a different tracking area (TA) or a cell with a TA outside the UE tracking area identification (TAI) list. 58. The method of claim 57, preceding the step of detecting.   40. The method of claim 38, wherein determining the availability is responsive to both the first indicator and the second indicator. A method in a user equipment (UE) with a first indicator relating to a voice service in an evolved packet system (Evolved Packet System / EPS), comprising:
Receiving a first non-access stratum / NAS protocol response message with a second indication;
Allowing the UE to select another radio access technology (RAT) in response to at least one of the first indicator or the second indicator.   The step of selecting another RAT further comprises disabling evolved universal mobile telecommunication system terrestrial radio access (E-UTRAN) cell reselection and evolved UTRAN (E-UTRAN) cell selection. 60. The method according to 60.   After receiving the second NAS registration response message with the third indicator, based on the third indicator, the UE enables cell selection to E-UTRAN cell and E-UTRAN cell reselection. 61. The method of claim 60, further comprising a step.   61. further comprising enabling the UE to enable cell selection and cell reselection to an E-UTRAN cell based on at least one of the first indicator or the second indicator. The method described.   61. The method of claim 60, further comprising causing the UE to select another RAT in response to both the first indicator and the second indicator.   61. The method of claim 60, wherein at least one of the first indicator or the second indicator is a voice service indicator (VSI). The VSI is
A network-provided Voice over IP Multimedia Subsystem (VoIMS) indicator;
UE usage settings,
66. The method of claim 65, wherein the method is at least one of user equipment audio settings. One or more of the VSIs are
IMS Voice over PS session support (IMS Voice over PS session supported) instructions,
IMS voice over PS session non-supported (IMS Voice over PS session supported) instruction,
Voice-centric (Voice Centric),
Data-centric (Data Centric),
Only CS voice (CS Voice Only)
IMS PS voice only (IMS PS Voice Only)
CS voice priority, IMS voice secondary (CS Voice Preferred, IMS Voice Secondary),
66. The method of claim 65, set to IMS Voice Priority, CS Voice Preferred, CS Voice Secondary.   61. The method of claim 60, wherein the second indicator is at least one of a cause value or a failure indication. At least one of the cause value or the failure indication is:
69. The method of claim 68, set to failure to register the UE for circuit switched (CS) or packet switched (PS) services, or CS domain not available.   61. The method of claim 60, wherein the first NAS protocol response message is a NAS registration response message. Disabling the E-UTRAN cell reselection and E-UTRAN cell selection comprises:
After compound NAS registration, causing the UE to disable E-UTRAN cell reselection, the compound NAS registration failed,
Causing the UE to disable E-UTRAN cell reselection after changing the UE usage settings;
Allows the UE to remain in the EPS until access to the voice service is required, and in response to an event that requires access to the voice service, after changing the UE usage settings, -Disabling UTRAN cell reselection;
Causing the UE to disable E-UTRAN cell reselection after IMS registration failure;
Retrying IMS registration according to VSI after disabling E-UTRAN cell reselection and E-UTRAN cell selection for the UE, or a different TA / Routing Area (RA) or TA outside UE tracking area identification list 62. The method of claim 61, further comprising at least one of: monitoring a tracking area (TA) of a neighboring E-UTRAN cell until a cell with at least one of is detected. A tangible computer readable medium having instructions stored therein,
When executed, the instructions are directed to a UE with a first indication related to voice service in an evolved packet system (EPS).
Receiving a first non-access stratum / NAS protocol response message with a second indication;
In response to at least one of the first indicator or the second indicator, causing another radio access technology (RAT) to be selected;
Tangible computer readable medium.   The step of selecting another RAT further comprises disabling evolved universal mobile telecommunication system terrestrial radio access (E-UTRAN) cell reselection and evolved UTRAN (E-UTRAN) cell selection. 72. A tangible computer readable medium according to 72.   The command further includes, after receiving a second NAS registration response message with a third indicator, based on the third indicator, allows the UE to perform cell selection for E-UTRAN cell and E-UTRAN cell re-establishment. The tangible computer readable medium of claim 72, wherein the selection is validated.   The instruction further causes the UE to enable cell selection and cell reselection to an E-UTRAN cell based on at least one of the first indicator or the second indicator. A tangible computer-readable medium as described in 1.   73. The tangible computer readable medium of claim 72, wherein the instructions further cause the UE to select another RAT in response to both the first indicator and the second indicator.   74. The tangible computer readable medium of claim 72, wherein at least one of the first indicator or the second indicator is a voice service indicator (VSI). The VSI is
A network-provided Voice over IP Multimedia Subsystem (VoIMS) indicator;
UE usage settings,
78. The tangible computer readable medium of claim 77, wherein the tangible computer readable medium is at least one of user equipment audio settings. One or more of the VSIs are
IMS Voice over PS session support (IMS Voice over PS session supported) instructions,
IMS voice over PS session non-supported (IMS Voice over PS session supported) instruction,
Voice-centric (Voice Centric),
Data-centric (Data Centric),
Only CS voice (CS Voice Only)
IMS PS voice only (IMS PS Voice Only)
CS voice priority, IMS voice secondary (CS Voice Preferred, IMS Voice Secondary),
78. A tangible computer readable medium according to claim 77, set to IMS voice preferred, CS Voice Preferred, CS Voice Secondary.

Images