HK1235181A - Identifying a domain for delivery of message service information - Google Patents

Description

Identifying domains for communicating message service information

The present application is a divisional application of chinese patent application having application number 201080035314.5, application date 2010, 8/10 and entitled "identifying a domain for transmitting message service information".

Priority requirement

The present application claims benefit and priority from U.S. provisional patent application No. 61/232,733, assigned attorney docket No. 093206P1, filed on 10/8/2009, and the contents of this provisional application are hereby incorporated by reference into the present application.

Technical Field

The present application relates generally to communication, and more particularly, but not by way of limitation, to selecting a domain for transmitting message service information.

Background

A wireless communication network is deployed over a defined geographic area to provide various types of services (e.g., voice, data, multimedia services, etc.) to users in the geographic area. In a typical implementation, access points (e.g., corresponding to different cells) are distributed throughout a network to provide wireless connectivity for access terminals (e.g., cellular telephones) operating in a geographic area served by the network.

Various types of information may be sent between the access terminal and the network, and the information may be sent over different types of domains. For example, an access terminal may send voice traffic, web browsing traffic, streaming traffic, Short Message Service (SMS) traffic (e.g., for communicating up to 160 characters), and other types of traffic to a network. Further, in various scenarios, the traffic may be sent over an Internet Protocol (IP) domain or some other type of domain, such as a Circuit Switched (CS) domain. For example, an access terminal of a GSM EDGE Radio Access Network (GERAN) or UMTS Terrestrial Radio Access Network (UTRAN) system can communicate over an IP domain such as an IP Multimedia Subsystem (IMS) domain or a CS domain. Also, an access terminal of an evolved UTRAN (E-UTRAN) system can communicate over an IP domain such as an IMS domain or a CS fallback (CSFB) domain. Accordingly, there is a need for an efficient technique that facilitates communicating information from an access terminal over different types of domains.

Disclosure of Invention

A brief overview of exemplary aspects of the invention is given below. In the discussion of the present application, any reference to the term "aspect" refers to one or more aspects of the present invention.

In some aspects, the present invention relates to providing an indication that controls how information for message traffic (e.g., text communication traffic such as SMS) is routed over different domains. For example, the access terminal may be configured with an indication (e.g., the access terminal receives an indication and maintains the indication) indicating whether the message service is preferably invoked over the IP domain or not. The access terminal then transmits message service information according to the value of the indication. For example, if the indication indicates a preference for delivery of SMS over IMS, the access terminal first attempts to deliver SMS using the IMS domain. If the attempt fails, the access terminal may then attempt to transport the SMS over a non-Access stratum (NAS) domain. In this case, the access terminal may register with the CS domain (e.g., with the mobile switching center) if the access terminal is not already registered. Conversely, if the indication indicates that IMS is not to be used to deliver the SMS, the access terminal may simply attempt to deliver the SMS over NAS (including, if appropriate, registering with the CS domain).

Accordingly, after determining that message service information is to be sent, the access terminal may identify a domain for communicating the message service information based on an indication maintained at the access terminal. The access terminal then transmits the message service information over the identified domain.

In some cases, a network entity may generate an indication and send the indication to an access terminal. For example, a home operator may specify an OMA-DM flag for sending to an access terminal to indicate the home operator's preferences or capabilities with respect to domain selection.

In some aspects, the present invention relates to selecting a domain based on a domain selected for a particular type of service. For example, after determining to send message service information, the access terminal may identify a domain for voice service. The access terminal then attempts to transmit the message service information over the domain.

Drawings

These and other exemplary aspects of the present invention will be described in the following detailed description and appended claims, and in the accompanying drawings, in which:

FIG. 1 is a simplified block diagram of some example aspects of a communication system in which a domain for communicating message service information is selected based on an indication;

FIG. 2 is a flow diagram of some example aspects of operations for selecting a domain for communicating message service information in accordance with an indication;

FIG. 3 is a flow diagram of some example aspects of operation for communicating message service information over an identified domain;

FIG. 4 is a flow diagram of some example aspects of operations for domain selection for an access terminal camped on E-UTRAN;

fig. 5 is a flow diagram of some example aspects of operations for domain selection for an access terminal camped on UTRAN;

FIG. 6 is a flow diagram of some example aspects in one example of operation for domain selection for an access terminal that is camped on, but not connected to, an E-UTRAN;

FIG. 7 is a flow diagram of some example aspects in another example of operation for domain selection for an access terminal that is camped on, but not connected to, an E-UTRAN;

fig. 8 is a flow diagram of operation of some example aspects that may be used to implement domain selection in a system supporting cdma2000 wireless technology;

FIG. 9 is a flow diagram of some example aspects of operation of selecting a domain for communicating message service information based on domains for a specified type of service;

FIG. 10 is a simplified diagram depicting different domains for communicating message service information in an exemplary E-UTRAN communication system;

FIG. 11 is a simplified diagram depicting different domains for communicating message service information in an example UTRAN communication system;

fig. 12 is a simplified diagram depicting different domains for communicating message service information in an example GERAN communication system;

fig. 13 is a simplified diagram depicting an example system supporting a cdma2000 domain for communicating messaging service information;

FIG. 14 is a simplified block diagram of some example aspects of components that may be used in a communication node;

FIG. 15 is a simplified block diagram of some example aspects of a communications component;

fig. 16-19 are simplified block diagrams of some example aspects of apparatuses that support selecting a domain for communicating message service information as described herein.

In accordance with common practice, the various features illustrated in the drawings are not drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may be simplified for clarity. Thus, the drawings may not depict all of the components of a given apparatus (e.g., device) or method. Finally, like reference numerals refer to like features throughout the specification and drawings.

Detailed Description

Various aspects of the invention are described below. It should be apparent that the disclosure herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely illustrative. In light of the disclosure herein, one of ordinary skill in the art will appreciate that aspects disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be implemented using any number of the aspects set forth herein. Such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. Furthermore, an aspect may include at least one unit of a claim.

Fig. 1 depicts some nodes (e.g., portions of a communication network) of an example communication system 100. For purposes of illustration, various aspects of the invention are described in the context of one or more access terminals, access points, and network entities communicating with each other. However, it should be understood that the present disclosure may be applied to other types of devices or other similar devices that are referenced using other terms. For example, in various implementations, an access point refers to or is implemented as an evolved node B (enodeb), a node B, a base station, etc., and an access terminal refers to or is implemented as a user equipment, a mobile station, etc.

An access point in system 100 provides one or more services (e.g., network connectivity) to one or more wireless terminals (e.g., access terminal 102) that may be installed in the coverage area of system 100 or that may be roaming in the coverage area of system 100. For example, at various points in time, the access terminal 102 may connect to the access point 104 or some other access point (not shown) in the system 100. Each of these access points may communicate with one or more network entities (represented for convenience as network entity 106) to facilitate wide area network connectivity. For example, these network entities may take various forms such as one or more wireless and/or core network entities. Thus, in various implementations, the network entity 106 may represent functionality such as at least one of the following: network management (e.g., by an operation, maintenance, management, and provisioning entity), call control, session management, mobility management, gateway functions, interworking functions, or some other appropriate network function.

In accordance with the subject application, the access terminal 102 is configured with a message service indication 108, wherein the access terminal 102 uses the message service indication 108 to identify a domain for communicating message service information (e.g., an SMS message). For example, depending on the value of the indication, the message service domain selector 108 may choose to communicate message service information to the IP domain 112 or other domain 114. In some implementations, the network entity 106 can configure the access terminal 102 using the message service indication 108 (as indicated by the corresponding dashed line). For example, an entity associated with a Home Public Land Mobile Network (HPLMN) operator of the access terminal 102 may use the indication to configure the access terminal 102 to control the preferred behavior of the access terminal 102.

The 3GPP specifications provide two mechanisms for SMS delivery: SMS carried by IMS (IP domain) and SMS carried by NAS (e.g., CS domain). In SMS over IMS bearers, the SMS is transported using IMS in the Packet Switched (PS) domain user plane.

In SMS over NAS bearers, SMS is transported by NAS signaling. This signaling may take various forms depending on the Radio Access Technology (RAT) in which the access terminal is currently camped. For access terminals on GERAN, NAS signaling involves SMS over CS NAS signaling bearers. For access terminals on UTRAN, NAS signaling involves SMS over General Packet Radio Service (GPRS) NAS signaling and a Gs interface between the Mobile Switching Center (MSC) and the Serving GPRS Support Node (SGSN). For access terminals on E-UTRAN, NAS signaling involves SMS over EPS NAS signaling and SG interface between MSC and Mobility Management Entity (MME).

For an access terminal with CSFB and IMS capabilities that resides in E-UTRAN, or for an access terminal with CS and IMS capabilities that resides in GERAN/UTRAN, the access terminal may use the teachings of the present application to decide how to transmit SMS. Furthermore, similar techniques may be used to communicate SMS over other domains. For example, for an access terminal with E-UTRAN and cdma2000 radio technologies, the access terminal may use SMS over IMS or SMS over S102 when the access terminal is located in E-UTRAN.

Accordingly, in some aspects, the present invention relates to a method of SMS domain selection for CS/CSFB and IMS capable access terminals using radio access technology. In some implementations, an access terminal uses one configuration: that is, the access terminal uses SMS of the IMS bearer or the access terminal does not use SMS of the IMS bearer (e.g., for SMS using NAS or S102 bearer). When an access terminal is used for SMS using an IMS bearer, the access terminal first attempts to transmit the SMS through the IMS. If not, the access terminal attempts to transmit the SMS over the NAS (or S102). When the access terminal is not configured to use SMS of the IMS bearer, then the access terminal only attempts SMS of the NAS (or S102) bearer.

Example operations that may be performed by a system, such as system 100, in accordance with the present disclosure are described in more detail in conjunction with the flow diagrams of fig. 2 and 3. For convenience, the operations of fig. 2 and 3 (or any other operations discussed or taught herein) may be described as being performed by specific components (e.g., components as described in fig. 1 and 10-14). However, it should be understood that these operations may be performed by other types of components, and that these operations may be performed using a different number of components. Further, it should also be understood that one or more of the operations described herein may not be used in a given implementation.

Referring first to fig. 2, blocks 202 and 204 describe operations that may be used to configure an access terminal using a message service indication. Here, at some point in time, a message traffic indication is generated and then transmitted to the access terminal.

The indication may take a variety of forms. For example, the indication may indicate (e.g., by a first specified value such as "0") that the message service is preferably invoked over the IP domain, or the indication may indicate (e.g., by a second specified value such as "1") that the message service is not invoked over the IP domain. As one particular example, an "IMS-carried SMS" indication may indicate that SMS is preferably invoked over IMS, or not invoked over IMS (e.g., SMS is instead invoked over NAS or some other domain). Thus, in some aspects, such an indication may indicate whether a network (e.g., a home network) supports a given domain.

For example, the operations of blocks 202 and 204 may be performed by various entities such as a network entity or a configuration entity. As an example of the former, the home operator may generate a flag defined in MO (mobile originated) IMS OMA-DM (open mobile alliance device management) that indicates whether the home operator of the access terminal wishes to use SMS over IMS. The home operator may then send an indication to the access terminal over the network connection to pre-configure and/or dynamically update/configure the access terminal. As one example of the latter, a configuration entity may configure (e.g., pre-configure) an access terminal when the access terminal is initially programmed, when the access terminal is initially deployed, or at some other point in time (e.g., by downloading the indication to the access terminal).

As shown at block 206, the access terminal will therefore receive the message service indication at some point in time (e.g., during a pre-configuration operation or during an update/configuration operation). The access terminal may receive the indication through a wireless connection (e.g., from some network entity through the access point) or through a wired connection (e.g., during pre-configuration when the access terminal is manufactured).

After receiving the indication, the access terminal maintains the indication (e.g., stores it in a memory device) for subsequent use during message service operations, as shown at block 208. Here, the indication received by the access terminal (e.g., during dynamic update) may override any static configuration maintained by the access terminal with respect to SMS.

The access terminal transmits message service information according to the maintained indication (e.g., according to the value of the maintained indication), as shown at block 210. For example, as shown at block 212, if the indication indicates that an IP domain (e.g., IMS) is preferred, the access terminal attempts to communicate the message service information over the IP domain. If the attempt fails, the access terminal attempts to transmit the message service information over another domain (e.g., NAS), as shown at block 214. In this case, the access terminal may register with the CS domain if the access terminal is not already registered with the CS domain. For example, in E-UTRAN, the access terminal may perform a combined tracking area update using an IMSI connection. Conversely, if the indication indicates that the IP domain is not to be used, the access terminal attempts to convey this message service information over another domain (e.g., NAS), as shown at block 216. The access terminal registers with the domain if needed.

Fig. 3 illustrates some operations that may be performed by an access terminal to communicate message service information over a selected domain. At some point in time, the access terminal determines that it needs to send message service information, block 302. For example, an application running at the access terminal may need to send a mobile-originated SMS message to another entity over the network.

The access terminal identifies a domain for communicating the message service information based on an indication maintained at the access terminal, as shown in block 304. For example, as described above, the access terminal may determine whether to transmit the SMS over IMS or NAS. The access terminal then transmits the message service information over the identified domain, as shown in block 306.

In some aspects, the selection of a domain at an access terminal is dependent on other domain selection operations performed by the access terminal. For example, for a voice-capable access terminal, voice domain selection may be performed by the access terminal to determine a voice traffic domain between voice over IMS (VoIMS) and voice over CS (CS).

In some implementations, if voice domain selection is to be performed by the access terminal, it is preferable that the selection be performed independently of the SMS configuration of the access terminal to give voice domain selection priority over the SMS method of delivering the selection. In this case, the SMS domain selection does not change the radio access technology selected according to the result of the voice domain selection process. Thus, if voice domain selection has been performed at the access terminal, the scenario discussed below exists for SMS domain selection.

With respect to the IMS registration state, the access terminal may or may not have registered with the IMS.

With respect to current radio access technologies, an access terminal may be camped on E-UTRAN (the access terminal is an Evolved Packet System (EPS)), or the access terminal may be camped on 2G/3G (e.g., GERAN or UTRAN).

For the case where the access terminal is camped on E-UTRAN, the International Mobile Subscriber Identity (IMSI) connected state (non-EPS service) of the access terminal may be one of the following: 1) the access terminal has attempted an IMSI attach but failed (in this case, CSFB is not allowed); 2) the access terminal has not attempted an IMSI connection (e.g., if "PS IMS voice only" is selected); 3) the access terminal is IMSI attached. With this in mind, fig. 4 and 5 depict exemplary SMS domain selection operations that may be performed by an access terminal that resides in an E-UTRAN or 2G/3G radio access technology, respectively.

FIG. 4 depicts an exemplary SMS domain selection operation that may be performed for a CS/CSFB and IMS capable access terminal that resides in E-UTRAN. In this example, it is assumed that the access terminal is already connected to EPS traffic (e.g., as a result of the voice domain selection process).

The access terminal determines whether it is to be used for SMS that preferentially uses IMS bearers, block 402. For example, the access terminal may verify the value of the maintained "SMS for IMS bearer" indication as discussed herein.

If the access terminal is configured to use SMS of the IMS bearer, the access terminal attempts to use SMS of the IMS bearer. Thus, the access terminal determines whether it is registered with the IMS, as shown in block 404. For example, the access terminal has registered with the IMS during voice domain selection. If the access terminal is registered with the IMS, the access terminal selects an IMS domain and uses SMS over IMS bearers (block 406).

If the access terminal has not registered with the IMS at block 404, the access terminal attempts to register with the IMS at block 408. If the registration is successful, the access terminal uses SMS over the IMS bearer (block 406).

If the IMS registration attempt at block 408 fails, the access terminal attempts SMS over EPSNAS (SG). Thus, the access terminal determines whether an IMSI connection has been attempted (e.g., during voice domain selection), as shown in block 410. If an IMSI connection has been attempted and has been successful (i.e., the access terminal has connected to non-EPS traffic), the access terminal selects a NAS domain and uses SMS over a NAS (SG) bearer, as depicted at block 412.

Referring again to block 410, if an IMSI connection has been attempted but failed, SMS service is not available (block 414). In this case, the access terminal stays in the E-UTRAN without SMS service (after radio access technology selection by voice domain selection).

If, at block 410, the access terminal determines that an IMSI connection has not been attempted, the access terminal attempts to register with the CS domain (e.g., with an MSC) via a combined Tracking Area Update (TAU) with the IMSI connection (SMS with "flag" only), as shown at block 416. If the registration attempt is successful, the access terminal uses SMS over NAS (SG) bearers at block 412. Otherwise, the access terminal will stay in E-UTRAN with no SMS service (block 414).

Referring again to block 402, if the access terminal is not configured to use SMS of IMS bearers, the access terminal will attempt to use SMS of nas (sg) bearers. Accordingly, operation flows to block 410 where the access terminal performs conditional operations as described above (e.g., the access terminal registers with the CS domain if needed) at block 410.

Fig. 5 depicts an exemplary SMS domain selection operation that may be performed for a CS and IMS capable access terminal that is camped on a 2G/3G radio access technology (e.g., UTRAN).

The access terminal determines whether it is for SMS, preferably using an IMS bearer, as shown in block 502. If the access terminal is configured to use SMS over an IMS bearer, the access terminal determines whether it is registered to IMS, block 504. If registered, the access terminal uses SMS over IMS bearers (block 506).

If the access terminal has not registered with the IMS at block 504, the access terminal attempts to register with the IMS at 508. If the registration is successful, the access terminal uses SMS over the IMS bearer (block 506).

If the IMS registration attempt at block 508 fails, the access terminal uses SMS over NAS (CS signaling) bearers, which is always available in 2G/3G radio access technology, as shown at block 510.

Referring again to block 502, if the access terminal is not configured to use SMS of IMS bearers, the access terminal will use SMS of NAS bearers, as shown in block 510.

Referring now to fig. 6 and 7, in some cases, when a mobile-originated SMS message is to be transmitted, an access terminal resides on a network but is not connected to the network. For example, some access terminals (e.g., data cards) that do not have voice call capability and do not perform voice domain selection may still use SMS. Thus, SMS domain selection as shown in the present application may be used for such access terminals. Fig. 6 and 7 depict two examples of how domain selection for CS and IMS capable access terminals residing in E-UTRAN, which may be performed for the case where the access terminal is not connected (e.g., when voice domain selection is not applied).

In the example of fig. 6, the access terminal performs an EPS/IMSI connection only when the access terminal is not configured to use SMS of the IMS bearer. Thus, the access terminal determines whether it is for SMS, preferably using an IMS bearer, as shown in block 602. If so, the access terminal performs an EPS connection (EPS only) and then attempts SMS using the IMS bearer, as shown in block 604. Accordingly, the access terminal attempts to register with the IMS, as shown in block 606. If the registration is successful, the access terminal uses SMS over the IMS bearer (block 608).

If the IMS registration attempt at block 606 fails, the access terminal will attempt to use the SMS of the NAS bearer. Thus, as shown in block 610, the access terminal performs a combined Tracking Area Update (TAU) using the IMSI connection. If the attach procedure is successful, the access terminal uses SMS over the NAS bearer, as shown in block 612.

If the connection process of block 610 fails, as shown at block 616, the actions taken by the access terminal at this point are implementation-specific. As shown at block 618, in some implementations, the access terminal reselects another radio access technology. As shown in block 620, in some implementations, the access terminal stays in E-UTRAN with no SMS service available.

Referring again to block 602, if the access terminal is not configured to use SMS of an IMS bearer, the access terminal will attempt to use SMS of a NAS bearer. In this case, the access terminal performs a combined EPS/IMSI connection. If the attach procedure is successful, the access terminal uses SMS over the NAS bearer, as shown in block 612. If the connection procedure of block 614 fails, the actions taken by the access terminal at this point may be implementation-specific, as shown at block 616 (discussed above).

Referring now to fig. 7, in this example, the access terminal always performs an EPS/IMSI connection regardless of its SMS configuration. Thus, as shown in block 702, the access terminal initially performs a combined EPS/IMSI connection.

If the connection procedure is successful, the access terminal determines if it prefers to use SMS over IMS bearers, as shown in block 704. If so, the access terminal attempts to register with the IMS, as shown in block 706. If the registration is successful, the access terminal uses SMS over the IMS bearer (block 708).

If the IMS registration attempt at block 706 fails, the access terminal determines if it is IMSI-attached, as shown at block 710. If so, the access terminal uses SMS over the NAS bearer, as shown at block 712.

If the access terminal is not IMSI-attached at block 710, the actions taken by the access terminal at this point are implementation-specific, as shown at block 714. As shown at block 716, in some implementations, the access terminal reselects another radio access technology. As shown in block 718, in some implementations, the access terminal stays in E-UTRAN with no SMS service available.

Referring again to block 704, if the access terminal is not configured to use SMS of the IMS bearer, the access terminal will attempt to use SMS of the NAS bearer. Accordingly, operation flow passes to block 710 where the access terminal performs conditional operations as discussed above at block 710.

Fig. 8 illustrates example operations that may be performed by an access terminal having E-UTRAN and cdma2000 technologies. In this case, the access terminal in E-UTRAN may use SMS over IMS bearer or SMS over S102 bearer. SMS over S102 bearer is implemented using CDMA2000 Protocol Data Units (PDUs) between the access terminal and the MME, and S102 tunneling between the MME and the CDMA1x interworking function.

The example begins at block 802, where first an access terminal with 1x/LTE and IMS capabilities resides in E-UTRAN, but is not connected. If the access terminal is already connected, operational flow begins at block 804.

The access terminal performs an EPS connection, as shown in block 802. If the connection procedure is successful, the access terminal determines whether it prefers to use SMS over IMS bearers, as shown in block 804. If so, the access terminal attempts to register with the IMS, as shown in block 806. If the registration is successful, the access terminal uses SMS over the IMS bearer (block 808).

If the IMS registration attempt at block 806 fails, the access terminal attempts CDMA1x registration, as shown at block 810. If the registration is successful, the access terminal uses the SMS carried by S102, as shown in block 812.

If the access terminal is unable to register with CDMA1x at block 810, the actions taken by the access terminal at this point may be implementation-specific, as shown at block 814. As represented by block 816, in some implementations, the access terminal reselects another radio access technology. As shown in block 818, in some implementations, the access terminal stays in E-UTRAN with no SMS service available.

Referring again to block 804, if the access terminal is not configured to use SMS over IMS bearers, the access terminal will attempt to use SMS over S102 bearers. Accordingly, the operational flow will pass to block 810 where the access terminal will perform conditional operations as discussed above at block 810.

Fig. 9 depicts one implementation that may be used in the case where, for example, SMS, which prefers to use IP domain (e.g., IMS) bearers, is not configured for the access terminal. In this case, the access terminal attempts to use the same domain for SMS as it is for other services (e.g., voice services in the example of fig. 9).

At some point in time, the access terminal determines that it needs to send message service information, as shown in block 902. For example, as described above, a mobile-originated SMS message needs to be sent over the network to another entity.

The access terminal identifies the selected domain for voice service, as shown in block 904. For example, the access terminal determines that the SMS of the NAS bearer has been used for voice traffic.

The access terminal attempts to communicate this message service information over the identified domain, as shown at block 906. If the attempt fails, the access terminal may attempt to deliver the message service information over another domain (e.g., IMS), as shown at block 908.

As described above, an SMS can be delivered using the teachings of the present application for an access terminal using a different type of wireless technology. Fig. 10-13 depict in a simplified manner how SMS is delivered over different domains provided by different wireless technologies.

Fig. 10 depicts a simplified example of an E-UTRAN system 1000 (i.e., an LTE network). Here, a user equipment (i.e., an access terminal) communicates with an evolved node b (enodeb) through radio signals via an E-UTRA Uu interface.

The eNodeBs communicate with the MME through the S1-MME interface. Further, in this example, the MME also communicates with the MSC server over an SG interface. Thus, NAS domain signaling (as shown by dashed line 1002) is available to the User Equipment (UE) through the eNodeB, MME and MSC server.

The eNodeB also communicates with the Serving Gateway (SGW) over the S1-U interface. The SGW communicates with a packet data network gateway (PGW) through an S5 or S8 interface. The PGW communicates with a packet data network entity, such as an IP Multimedia Subsystem (IMS), over an SGi interface. Thus, IMS domain signaling (as shown by dashed line 1004) may be used for the UE through an IMS tunnel via eNodeB, SGW, PGW and IMS.

Fig. 11 depicts a simplified example of a UTRAN system 1100. In this case, the UE communicates with the node B by radio signals via the UTRA Uu interface. The node B communicates with the SGSN.

The SGSN communicates with the MSC server through a Gs interface. Thus, CS domain signaling (as indicated by dashed line 1102) is available to the UE through node B, SGSN and the MSC server.

The SGSN also communicates with a Gateway GPRS Support Node (GGSN) over a Gn interface. The GGSN then communicates with packet data network entities such as IP Multimedia Subsystem (IMS) over the Gi interface. Thus, IMS domain signaling (as indicated by dashed line 1104) is available to the UE through an IMS tunnel via the node B, SGSN, GGSN and IMS.

Fig. 12 depicts a simplified example of a GERAN system 1200. Here, an Access Terminal (AT) communicates with a Base Transceiver Station (BTS) through a wireless signal. The BTS communicates with a Base Station Controller (BSC).

The BSC communicates with the MSC server over the a interface. Thus, CS domain signaling (as indicated by dashed line 1202) is available to the UE through the BTS, BSC, and MSC server.

The BSC also communicates with the SGSN. The SGSN communicates with a GGSN, which communicates with packet data network entities such as an IP Multimedia Subsystem (IMS). Thus, IMS domain signaling (as indicated by dashed line 1204) is available to the AT through an IMS tunnel via the BTS, BSC, SGSN, GGSN, and IMS.

Fig. 13 depicts a simplified example of an E-UTRAN system 1300 that provides cdma2000 connectivity. In a similar manner as described above with respect to fig. 10, the UE communicates with the eNodeB over wireless signals and IMS domain signaling (as indicated by dashed line 1304) is available to the UE through an IMS tunnel via the eNodeB, SGW, PGW and IMS.

However, in this case, the SMS domain signaling (as shown by dashed line 1302) is provided through cdma2000 PDUs between the UE and the MME and S102 tunneling between the MME and the 1x interworking function.

Various advantages may be realized through the use of the teachings of the present application. For example, SMS domain selection may be implemented using a single configuration parameter. Furthermore, voice domain selection and SMS domain selection can be decoupled, simplifying the domain selection process. In addition, access terminal behavior can be specified for various radio access technologies.

Fig. 14 depicts some example components that may be incorporated into nodes such as an access terminal 1402 (e.g., corresponding to the access terminal 102) and a network entity 1404 (e.g., of a home PLMN) to perform message service operations as shown herein. When implemented, the described components may also be incorporated into other nodes in a communication system. For example, other nodes in the system may include components similar to those described for network entity 1404 to provide similar configuration functionality. Further, a given node may include one or more of the described components. For example, an access terminal may include multiple transceiver components that enable the access terminal to operate on multiple frequencies and/or communicate via different technologies.

As shown in fig. 14, an access terminal 1402 includes a transceiver 1406 for communicating with other nodes. The transceiver 1406 includes a transmitter 1408 for transmitting signals (e.g., message service information such as SMS messages) and a receiver 1410 for receiving signals (e.g., message service indications).

Network entity 1404 includes a network interface 1412 for communicating with other nodes (e.g., other network nodes). For example, network interface 1412 may be used to communicate with one or more network nodes over a wire-based or wireless backhaul. In some aspects, the network interface 1412 may be implemented as a transceiver to support wire-based or wireless communications. To this end, the network interface 1412 is depicted as including a transmitter component 1414 (e.g., for sending message traffic indications) and a receiver component 1416 (e.g., for receiving messages).

Access terminal 1402 and network entity 1404 can also include other components that can be employed in connection with message service operations as illustrated herein. For example, access terminal 1402 can comprise a message service processor 1418 that can be employed to perform message service-related operations (e.g., communicating message service information, identifying a domain, attempting to communicate message service information via a domain), and to provide other functionality related thereto as described herein. Access terminal 1402 can additionally include a communication processor 1422 that is configured to perform operations related to communication (e.g., determining that message service information is to be transmitted), and to provide other related functions as described herein. In addition, access terminal 1402 can comprise a memory component 1424 (e.g., that comprises or interacts with a memory device) for maintaining information (e.g., maintaining message traffic indications) and for providing other related functionality as described herein. The network entity 1404 includes a message service processor 1420 for performing message service-related operations (e.g., generating message service indications) and for providing other related functionality as shown herein.

In some implementations, the components of fig. 14 may be implemented in one or more processors (e.g., each of which uses and/or incorporates data storage for storing information or code used by the processor to provide its functionality). For example, some of the functions in block 1406, as well as some or all of the functions in blocks 1418, 1422, and 1424, may be implemented by a processor or processors of an access terminal and data storage of the access terminal (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Further, some of the functions in block 1412, as well as some or all of the functions in block 1420, may be implemented by a processor or processors of a network entity and data storage of the network entity (e.g., by execution of appropriate code and/or by appropriate configuration of processor components).

The present disclosure may be used in a wireless multiple-access communication system that may simultaneously support communication for multiple wireless access terminals. Here, each terminal can communicate with one or more access points via transmissions on forward and reverse links. The forward link (or downlink) refers to the communication link from the access points to the terminals, and the reverse link (or uplink) refers to the communication link from the terminals to the access points. Such a communication link may be established by a single-input single-output system, a multiple-input multiple-output (MIMO) system, or some other type of system.

MIMO system using multi-pair (N)_TSub) transmitting antenna and multi-pair (N)_RAnd) a receiving antenna for data transmission. From N_TA secondary transmitting antenna and N_RThe MIMO channel formed by the sub-receiving antennas can be decomposed into N_SIndividual channels, which may also be referred to as spatial channels, where N_S≤min{N_T,N_R}。N_SEach of the individual channels corresponds to a dimension. If used, theThe other dimensionalities created by the multiple transmit and receive antennas enable the MIMO system to provide improved performance (e.g., higher throughput and/or greater reliability).

MIMO systems support Time Division Duplexing (TDD) and Frequency Division Duplexing (FDD). In a TDD system, the forward link transmission and the reverse link transmission use the same frequency domain, enabling reciprocity (reciprocity) principles to estimate the forward link channel from the reverse link channel. This enables the access point to obtain transmit beamforming gain on the forward link when multiple antennas are available at the access point.

Fig. 15 depicts a wireless device 1510 (e.g., an access point) and a wireless device 1550 (e.g., an access terminal) of an example MIMO system 1500. At the device 1510, traffic data for a number of data streams is provided from a data source 1512 to a Transmit (TX) data processor 1514. Each data stream is then transmitted over a respective transmit antenna.

TX data processor 1514 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data. The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. Typically, the pilot data is a known data pattern that is processed in a known manner and may be used by the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream can then be modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream can be determined by instructions performed by processor 1530. A data memory 1532 may store program code, data, and other information used by the processor 1530 or other components of the device 1510.

Modulation symbols for all data streams can then be provided to a TX MIMO processor 1520, and the modulation symbols can be further processed (e.g., OFDM) by the TX MIMO processor 1520. Then, TXMIMO processor 1520 to N_TN is provided by transceivers (XCVR)1522A through 1522T_TA stream of modulation symbols. In some aspects, the TX MIMO processor 1520 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transceiver 1522 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. Then, respectively from N_TThe sub-antennas 1524A through 1524T transmit N from the transceivers 1522A through 1522T_TA modulated signal.

At device 1550, from N_RThe antennas 1552A through 1552R receive the transmitted modulated signals and provide received signals from each antenna 1552 to a respective transceiver (XCVR)1554A through 1554R. Each transceiver 1554 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

A Receive (RX) data processor 1560 then operates from N based on a particular receiver processing technique_RN is received and processed by a transceiver 1554_RA received symbol stream to provide N_TA "detected" symbol stream. The RX data processor 1560 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 1560 is complementary to that performed by TX MIMO processor 1520 and TX data processor 1514 of device 1510.

A processor 1570 periodically determines which pre-coding matrix to use (discussed below). Processor 1570 formulates a reverse link message comprising a matrix index portion and a rank value portion. A data memory 1572 may store program code, data, and other information used by processor 1570 or other components of device 1550.

The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor 1538, modulated by a modulator 1580, conditioned by transceivers 1554A through 1554R, and transmitted back to device 1510, where TX data processor 1538 also receives traffic data for a number of data streams from a data source 1536.

At the device 1510, the modulated signals from the device 1550 are received by the antennas 1524, conditioned by the transceivers 1522, demodulated by a demodulator (DEMOD)1540, and processed by a RX data processor 1542 to extract the reverse link message transmitted by the device 1550. Processor 1530 then determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.

Fig. 15 also depicts a communications component that may include one or more components that perform message control operations as shown herein. For example, the message control component 1592 may cooperate with the processor 1570 and/or other components of the device 1550 to send message service information to another device (e.g., via the device 1510). It should be understood that for each device 1510 and 1550, the functionality of two or more of the described components can be provided by a single component. For example, a single processing component may provide the functionality of the message control component 1592 and the processor 1570.

The present disclosure may be incorporated into various types of communication systems and/or system components. In some aspects, the subject matter of the present application can be employed in a multiple-access system that can support communication with multiple users by sharing available system resources (e.g., by specifying one or more of bandwidth, transmit power, coding, interleaving, and the like). For example, the content of the present application may be applied to any one or a combination of the following technologies: code Division Multiple Access (CDMA) system, multi-carrier CDMA (MCCDMA), wideband CDMA (W-CDMA), high speed packet access (HSPA, HSPA +) system, Time Division Multiple Access (TDMA) system, Frequency Division Multiple Access (FDMA) system, single carrier FDMA (SC-FDMA) system, orthogonal frequency division multiple access (OF)DMA) systems or other multiple access techniques. The wireless communication system using the present disclosure may be designed to implement one or more standards, such as IS-95, CDMA2000, IS-856, W-CDMA, TDSCDMA, and others. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA2000, or some other technology. UTRA includes W-CDMA and Low Chip Rate (LCR). cdma2000 technology covers IS-2000, IS-95, and IS-856 standards. TDMA networks may implement wireless technologies such as global system for mobile communications (GSM). OFDMA networks may implement methods such as evolved UTRA (E-UTRA), IEEE802.11, IEEE 802.16, IEEE 802.20, flashAnd so on. UTRA, E-UTRA and GSM are part of the Universal Mobile Telecommunications System (UMTS). The present disclosure may be implemented in 3GPP Long Term Evolution (LTE) systems, Ultra Mobile Broadband (UMB) systems, and other types of systems. LTE is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents from an organization named "third generation partnership project" (3GPP), while cdma2000 is described in documents from an organization named "third generation partnership project 2" (3GPP 2). While certain aspects of the present invention are described using 3GPP terminology, it should be understood that the present disclosure may apply to 3GPP (e.g., Re199, Re15, Re16, Re17) technologies, as well as 3GPP2 (e.g., 1xRTT, 1xEV-DO Rel0, RevA, RevB) technologies, and other technologies.

The present disclosure may be incorporated into (e.g., implemented in or performed by) a variety of devices (e.g., nodes). In some aspects, a node (e.g., a wireless node) implemented in accordance with the subject matter may comprise an access point or an access terminal.

For example, an access terminal may comprise, be implemented as, or referred to as user equipment, a subscriber station, a subscriber unit, a mobile station, a mobile node, a remote station, a remote terminal, a user agent, user equipment, or some other terminology. In some implementations, an access terminal may comprise a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having wireless connection capability, or some other suitable processing device connected to a wireless modem. Accordingly, one or more aspects illustrated herein may be incorporated into a phone (e.g., a cellular phone or smart phone), a computer (e.g., a laptop), a portable communication device, a portable computing device (e.g., a personal data assistant), an entertainment device (e.g., a music device, a video device, or a satellite radio), a global positioning system device, or any other suitable device for communicating over a wireless medium.

The access point may include, be implemented as, or be referred to as: a node B, an evolved node B, a Radio Network Controller (RNC), a Base Station (BS), a Radio Base Station (RBS), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a Transceiver Function (TF), a radio transceiver, a radio router, a basic service set (BSs), an Extended Service Set (ESS), a macrocell, a home enb (henb), a femtocell, a femto node, a pico node, or some other similar terminology.

In some aspects, a node (e.g., an access point) may comprise an access node for a communication system. For example, the access node may provide a connection to or from a network (e.g., a wide area network such as the internet or a cellular network) through a wired or wireless communication link to the network. Thus, an access node may enable another node (e.g., an access terminal) to access a network or have some other functionality. Further, it should be understood that one or all of these nodes may be portable or, in some cases, relatively non-portable.

Further, it should be understood that a wireless node may be capable of sending and/or receiving information in a non-wireless manner (e.g., through a wired connection). Thus, receivers and transmitters as described herein may include appropriate communication interface components (e.g., electrical or optical interface components) to communicate over a non-wireless medium.

The wireless nodes may communicate over one or more wireless communication links based on or supporting any suitable wireless communication technology. For example, in some aspects a wireless node may associate with a network. In some aspects, the network may comprise a local area network or a wide area network. The wireless device may support or use one or more of a variety of wireless communication technologies, protocols, or standards such as those discussed herein (e.g., CDMA, TDMA, OFDM, OFDMA, WiMAX, Wi-Fi, etc.). Likewise, the wireless node may support or use one or more of a variety of corresponding modulation or multiplexing schemes. Thus, the wireless node may include appropriate components (e.g., air interfaces) to establish communications over one or more wireless communication links using the above or other wireless communication techniques. For example, a wireless node may include a wireless transceiver with associated transmitter and receiver components including various components (e.g., signal generators and signal processors) that facilitate communication over a wireless medium.

In some aspects, the functionality described herein (e.g., with reference to one or more of the figures) corresponds to the functionality "module" similarly specified in the appended claims. Referring to fig. 16-19, devices 1600, 1700, 1800, and 1900 are shown as a series of interrelated functional modules. Here, the indication maintenance module 1602 may correspond at least in some aspects to, for example, a memory component as discussed herein. The message service information delivery module 1604 may correspond at least in some aspects to, for example, a message service processor as discussed herein. The indication receiving module 1606 may correspond at least in some aspects to, for example, a receiver as discussed herein. The indication generating module 1702 may correspond at least in some aspects to, for example, a message service processor as discussed herein. The indication sending module 1704 may correspond at least in some aspects to, for example, a transmitter as discussed herein. The to-send message service information determination module 1802 may correspond at least in some aspects to, for example, a communication processor as discussed herein. The domain identification module 1804 may correspond at least in some aspects to, for example, a message service processor as discussed herein. The message service information delivery module 1806 may correspond at least in some aspects to, for example, a message service processor as discussed herein. The to-send message service information determination module 1902 may correspond at least in some aspects to, for example, a communication processor as discussed herein. The domain identification module 1904 may correspond at least in some aspects to, for example, a message service processor as discussed herein. The identified domain carries message service information, transfer attempt module 1906 may correspond at least in some aspects to, for example, a message service processor as discussed herein. Another domain carries message service information, transfer attempt module 1908 may correspond at least in some aspects to, for example, a message service processor as discussed herein.

The functionality of the modules of fig. 16-19 may be implemented in a variety of ways consistent with the present disclosure. In some aspects, the functionality of these modules may be implemented as one or more electrical components. In some aspects, the functionality of these blocks may be implemented as a processing system including one or more processor components. In some aspects, the functionality of these modules may be implemented using, for example, at least a portion of one or more integrated circuits (e.g., an ASIC). As described herein, an integrated circuit may include a processor, software, other related components, or some combination thereof. The functionality of these modules may also be implemented in some other way, as shown in this application. In some aspects, one or more of any of the dashed boxes of fig. 16-19 are optional.

It will be understood that any reference to an element of the present application using designations such as "first", "second", etc. does not generally limit the number or order of such elements. Rather, these designations are used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, reference to a first element and a second element does not imply that only two elements are used herein or that the first element must somehow precede the second element. Further, a set of elements can include one or more elements unless explicitly stated otherwise. Furthermore, a phrase in the form of "A, B or at least one of C" as used in the specification or claims means "A or B or C or any combination of these elements".

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of ordinary skill would further appreciate that the various illustrative logical blocks, modules, processors, hardware modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as "software" or a "software module"), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with Integrated Circuits (ICs), access terminals, or access points. The IC may include a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof operable to perform the functions described herein, and may execute code or instructions that are stored in, external to, or both to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

It should be understood that any particular order or hierarchy of steps in any disclosed process is merely one example of an exemplary method. It is understood that the specific order or hierarchy of steps in the processes may be rearranged based on design preferences while remaining within the scope of the present invention. The accompanying method claims present various step elements in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

In one or more exemplary embodiments, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. It should be understood that the computer-readable medium may be embodied in any suitable computer program product.

The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the invention. Thus, the present invention is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (18)

1. A method for communication, comprising:

attempting a combined Evolved Packet System (EPS) and International Mobile Subscriber Identity (IMSI) connection process;

determining, after an access terminal stores an indication that the access terminal is to send a short message service, SMS, the indication indicating whether the SMS originated by the access terminal is preferred to be invoked over an Internet protocol domain or whether the SMS is not to be invoked over the Internet protocol domain;

identifying a domain for transmitting the SMS based on the indication stored at the access terminal, wherein the domain for transmitting the SMS is identified when the access terminal initiates a message service, wherein identifying the domain comprises: determining to attempt to transmit the SMS over non-access stratum (NAS) signaling if the stored indication indicates that the SMS is not invoked over the Internet protocol domain; and

sending the SMS from the access terminal through NAS signaling if the attempted combined EPS and IMSI connection is successful.

2. The method of claim 1, wherein the internet protocol domain comprises an internet protocol multimedia subsystem domain.

3. The method of claim 1, wherein identifying the domain comprises: determining whether the SMS is capable of being delivered over Internet protocol multimedia subsystem signaling in response to the indication stored at the access terminal indicating that the SMS is preferred to be invoked over the Internet protocol domain.

4. The method of claim 3, wherein determining whether the SMS is capable of being delivered via Internet protocol multimedia subsystem signaling comprises: in response to the access terminal having a current communication connection with a network, determining whether to register the access terminal with an internet protocol multimedia subsystem.

5. The method of claim 3, wherein determining whether the SMS is capable of being delivered via Internet protocol multimedia subsystem signaling comprises: in response to the access terminal not having a current communication connection with a network, a connection procedure with the network is performed and an attempt is then made to register the access terminal with an internet protocol multimedia subsystem.

6. The method of claim 1, further comprising: determining whether the connection procedure is successful in response to the access terminal not having a current communication connection with an evolved UMTS terrestrial radio access network.

7. The method of claim 1, further comprising:

identifying a voice domain for transmitting voice traffic, and

wherein the access terminal independently identifies the speech domain and the domain for transmitting SMS.

8. The method of claim 7, wherein the identification of the domain for transmitting SMS does not change a radio access technology selected as a result of the identification of the voice domain.

9. An apparatus for communication, comprising:

a memory for storing an indication of whether an access terminal-initiated short message service, SMS, is preferred to be invoked over an Internet protocol domain or whether the SMS is not invoked over the Internet protocol domain;

a communication processor for determining that the access terminal is to send the SMS after storing the indication in the memory;

a message service processor for attempting a combined evolved packet system, EPS, and international mobile subscriber identity, IMSI, connection procedure and identifying a domain for communicating the SMS according to the indication stored in the memory, wherein the message service processor is for identifying the domain for communicating the SMS when a message service is initiated by the access terminal;

wherein the message service processor is further configured to attempt to transmit the SMS over non-access stratum (NAS) signaling if the stored indication indicates that the SMS is not to be invoked over the Internet protocol domain; and

wherein the message traffic processor is further configured to send the SMS from the access terminal over NAS signaling if the attempted combined EPS and IMSI connection is successful.

10. The apparatus of claim 9, wherein the internet protocol domain comprises an internet protocol multimedia subsystem domain.

11. The apparatus of claim 9, wherein the message service processor is further configured to: identifying the domain by determining whether the SMS is deliverable by Internet protocol multimedia subsystem signalling in response to the stored indication indicating that the SMS is preferably invoked over the Internet protocol domain.

12. The apparatus of claim 9, wherein the apparatus is configured to identify a voice domain for transmitting voice traffic, and

wherein the access terminal is further configured to independently identify the speech domain and the domain for transmitting SMS.

13. The apparatus of claim 12, wherein the apparatus is to not change a radio access technology selected as a result of the identification of the voice domain when identifying the domain for transmitting SMS.

14. An apparatus for communication, comprising:

means for attempting a combined Evolved Packet System (EPS) and International Mobile Subscriber Identity (IMSI) attach procedure;

means for determining, after an access terminal stores an indication that the access terminal is to send a Short Message Service (SMS), the indication indicating whether the SMS originated by the access terminal is preferred to be invoked over an Internet protocol domain or whether the SMS is not to be invoked over the Internet protocol domain;

means for identifying a domain for transmitting the SMS based on the indication stored at the access terminal, wherein the domain for transmitting the SMS is identified when the access terminal initiates a message service, wherein the means for identifying the domain comprises: means for determining to attempt to transmit the SMS over non-access stratum (NAS) signaling if the stored indication indicates that the SMS is not to be invoked over the Internet protocol domain; and

means for sending the SMS from the access terminal through NAS signaling if the attempted combined EPS and IMSI connection is successful.

15. The apparatus of claim 14, wherein the internet protocol domain comprises an internet protocol multimedia subsystem domain.

16. The apparatus of claim 14, wherein the means for identifying a domain comprises: means for determining whether the SMS can be delivered over Internet protocol multimedia subsystem signaling in response to the indication stored at the access terminal indicating that the SMS is preferred to be invoked over the Internet protocol domain.

17. The apparatus of claim 14, further comprising:

a module for identifying a voice domain for transmitting voice traffic, and

wherein the access terminal is to independently identify the speech domain and the domain for transmitting SMS.

18. The apparatus of claim 17, wherein the means for identifying the domain for transmitting SMS does not change a radio access technology selected by the means for identifying the voice domain.