NOTIFYING NETWORK ELEMENTS OF UNREACHABLE USER EQUIPMENT

CROSS REFERENCE TO RELATED APPLICATION:

[0001] This application claims priority to U.S. Provisional Patent Application No. 62/482,971, filed on April 7, 2017. The entire content of the above- referenced application is hereby incorporated by reference.

BACKGROUND:

Field:

[0002] Various communication systems may benefit from improved network notifications. For example, notifying an internet protocol multimedia subsystem (IMS) that a user equipment (UE) is operating in a mode where it cannot be reached may be useful in various communication systems.

Description of the Related Art:

[0003] 3rd Generation Partnership Project (3GPP) technology includes two new coverage enhancement (CE) modes (A and B) for the Long-Term Evolution (LTE) communication standard. A UE operating in CE mode A, or A and B simultaneously, may be used by any category of UE, including smartphones and UE with machine-type communications (MTC) applications. Using this dual-mode function, CE mode A allows the UE to receive a full set of services when in normal cell coverage zones, while CE mode B allows the UE to continue receiving limited services when operating within unfavorable cell coverage zones.

[0004] When operating exclusively in CE mode B, the extended coverage for the UE relies on uplink and downlink data transmission repetitions over a radio interface. At the same time, non-access stratum (NAS) timers for the UE and mobility management entity (MME) are extended for a UE that has indicated it is currently operating in CE mode B. CE mode B applies in coverage conditions having low throughput and longer setup delays, and is not intended for services with stringent quality of service (QoS) requirements, such as voice over LTE (VoLTE). As a result, only a subset of services, such as those not requiring a dedicated bearer, may be supported while exclusively in CE mode B.

[0005] The determination of whether a UE operates in CE mode A or CE mode B depends on whether the UE is operating in ECM-CONNECTED mode or ECM-IDLE mode. While in ECM-CONNECTED mode, the evolved node B (eNB) connected to the UE controls whether the UE operates in CE mode A or CE mode B. On the other hand, when operating in ECM-IDLE, the UE makes a determination as to which mode to use, and does not notify the network of the determination.

[0006] Under 3 GPP technology, without any indication that the UE is operating exclusively in CE mode B, the IMS may attempt to continuously page the UE to reconnect and provide IMS terminating services, such as terminating a voice call or short message service (SMS) message. Even after the expiration of existing IMS session initiation protocol (SIP) timers, the IMS network elements may re-attempt delivery, resulting in significant wasted network and radio resources. A policy and charging rules function (PCRF) may transmit radio access network (RAN)/NAS release-cause data via a receiving interface to a proxy-call session control function (P-CSCF). For example, when handling RAN/NAS release cause values, if the P-CSCF is required by operator policy to provide the RAN/NAS release cause information, it includes this information in a corresponding SIP message when received from the PCRF.

SUMMARY:

[0007] According to an embodiment, there is a method that comprises receiving, at a network entity, one or more failure indications. The method further comprises mapping, by the network entity, the one or more failure indications to one or more rejection reason codes. The one or more rejection reason codes indicate that a user equipment is temporarily unavailable. The method further comprises transmitting, from the network entity, the one or more rejection reason codes to a network application function to suspend further attempts by the network application function to contact the user equipment.

[0008] According to an embodiment, an apparatus can include at least one processor, and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least receive one or more failure indications. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least map the one or more failure indications to one or more rejection reason codes. The one or more rejection reason codes indicate that a user equipment is temporarily unavailable. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least transmit the one or more rejection reason codes to a network application function to suspend further attempts by the network application function to contact the user equipment.

[0009] According to an embodiment, there is a method that comprises transmitting, from a network application function, a request to subscribe to bearer event notifications regarding the state of a signaling transmission path. The method further comprises receiving, by the network application function, one or more indications that a user equipment is temporarily unavailable. The one or more indications cause the network application function to suspend further attempts to contact the user equipment.

[0010] According to an embodiment, an apparatus can include at least one processor, and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least transmit a request to subscribe to bearer event notifications regarding the state of a signaling transmission path. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least receive one or more indications that a user equipment is temporarily unavailable. The one or more indications cause the apparatus to suspend further attempts to contact the user equipment.

[0011] In accordance with an embodiment, an apparatus can include means for receiving one or more failure indications. The apparatus can further include means for mapping the one or more failure indications to one or more rejection reason codes. The one or more rejection reason codes indicate that a user equipment is temporarily unavailable. The apparatus can further include means for transmitting the one or more rejection reason codes to a network application function to suspend further attempts by the network application function to contact the user equipment.

[0012] In accordance with an embodiment, an apparatus can include means for transmitting a request to subscribe to bearer event notifications regarding the state of a signaling transmission path. The apparatus can further includes means for receiving one or more indications that a user equipment is temporarily unavailable. The one or more indications cause the apparatus to suspend further attempts to contact the user equipment.

[0013] A non-transitory computer readable medium can, in certain embodiments, be encoded with instructions that, when executed in hardware, perform a process. The process can include a method according to any of the steps performed by any of the above discussed apparatuses.

[0014] A computer program product can, according to certain embodiments, encode instructions for performing a process. The process can include a method according to any of the steps performed by any of the above discussed apparatuses. [0015] An apparatus can, according to certain embodiments, include circuitry for performing a process. The process can include a method according to any of the steps performed by any of the above discussed apparatuses.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0016] For proper understanding of this disclosure, reference should be made to the accompanying drawings, wherein:

[0017] Figure 1 illustrates an example of a system according to certain embodiments.

[0018] Figure 2 illustrates another example of a system according to certain embodiments.

[0019] Figure 3 illustrates an example of a signal flow diagram according to certain embodiments.

[0020] Figure 4 illustrates an example of a signal flow diagram performed by a network application function according to certain embodiments.

[0021] Figure 5 illustrates an example of another signal flow diagram performed by a network application function according to certain embodiments.

[0022] Figure 6 illustrates an example of a method performed by a network entity according to certain embodiments.

[0023] Figure 7 illustrates another example of a method performed by a network application function according to certain embodiments.

[0024] Figure 8 illustrates another example of a system according to certain embodiments.

DETAILED DESCRIPTION:

[0025] A P-CSCF may transmit raw RAN/NAS release-cause data in a SIP Reason header towards downstream IMS nodes for charging and statistical purposes, with no interpretation of the RAN/NAS release-cause data. Thus, there is currently no solution for how a Policy and Charging Control (PCC) and IMS may use NAS failure data to function optimally while UE operates in an unreachable mode, such as CE mode B.

[0026] Certain embodiments may have various benefits and/or advantages. For example, certain embodiments allow the IMS network elements to be aware that a UE is operating in an unreachable mode, such as CE mode B, where it will not be reachable until the UE leaves that mode. Thus, certain embodiments are directed to improvements in computer-related technology, specifically, providing techniques to notify an IMS that a UE is operating in a mode that prevents contact. Furthermore, certain embodiments are directed to improvements in computer-related technology, specifically, minimizing waste of network and radio resources used in attempting to communicate with a UE that is in a mode that prevents contact.

[0027] Figure 1 illustrates an example of a system according to certain embodiments. IMS 101 may include at least one or more of user equipment (UE) 103, IP connectivity access network (IP-CAN) Evolved Packet Core (EPC) 105, PCRF 107, P-CSCF 109, telephony application server (TAS)/serving-call session control function (S-CSCF) 111, and/or eNB 113. TAS/S-CSCF 111 may be in communication with P-CSCF 109, and may send terminating SIP invite requests to P-CSCF 109. P-CSCF 109 may be in communication with PCRF 107 to request the required network resource from IP-CAN (EPC) 105, and may forward the terminating SIP invite to IP-CAN (EPC) 105. PCRF 107 may be in communication with IP-CAN (EPC) 105, and may instruct IP-CAN (EPC) 105 to provide the needed network resources as requested by P-CSCF 109. eNB 113 may be in communication with UE 103. IP-CAN (EPC) 105 may also be in communication with UE 103. For example, IP-CAN (EPC) 105 may be able to page UE 103.

[0028] UE 103 may operate in one or more modes, and may change between the several modes. For example, UE 103 may operate in ECM-CONNECTED mode or ECM-IDLE mode. While in ECM-CONNECTED mode, eNB 113 connected to UE 103 may control whether UE 103 operates in CE mode A or CE mode B. However, while operating in ECM-IDLE, UE 103 may make its own determination as to which mode to use, and may not notify IMS 101 or any of its network elements of the determination. In certain embodiments, UE 103 may operate in a power-saving mode, an extended discontinuous reception (eDRx) mode, and/or other mode in which UE 103 cannot be contacted. IP-CAN (EPC) 105 may provide a radio access network (RAN) release cause to PCRF 107. The RAN release cause may be transferred via a Gx procedure, such as a 3 GPP Diameter Gx interface.

[0029] PCRF 107 may perform mapping functions on the RAN release cause data received from IP-CAN (EPC) 105. PCRF 107 may map the RAN/NAS release cause received from IP-CAN (EPC) 105 to a standardized value. The standardized value may be defined in a specific-action attribute-value pair (A VP) and/or a new value defined in an experimental-result A VP.

[0030] The mapping function may be performed based upon an IMS application being invoked, or the media being used from a session description protocol (SDP). The mapping function may also be performed based upon an RAN/NAS release cause that identifies the current CE mode of UE 103. For example, the CE mode may be CE mode A, CE mode B, or CE mode A and B simultaneously. If UE 103 is operating in CE mode B, PCRF 107 may map the release cause as transient failure. Alternatively, if the RAN/NAS release cause indicates that UE 103 is operating using a narrow band or very low bandwidth, PCRF 107 may map the release cause as permanent failure. The mapping function may also be implementation-dependent or standardized, for example, in accordance with the Global System for Mobile Communication Association (GSMA).

[0031] Using a specific-action A VP, the reason received from IP-CAN (EPC) 105 may be mapped to a new, standardized value, for example: INDICATION OF RELEASE OF BEARER INCOMPATIBLE UE MOD

E (new value). Within a re-authorization request (RAR), this value shall be used when the server reports the release of a bearer to the application function (AF). This value may inform the application function that the current mode of operation of UE 103 is not compatible with the quality of service requirement being requested for this service, for example, IMS voice/video.

[0032] In some embodiments, the reasons received from IP-CAN (EPC) 105 may be mapped to a new, standardized value according to an experimental- result AVP. For example, for transient failures: new value (42xx): REQUESTED SERVICE TEMPORARILY NOT AUTHORIZED due to incompatible UE mode. In other embodiments, for Permanent Failures: new value (50xx): REQUESTED SERVICE TEMPORARILY NOT AUTHORIZED due to incompatible UE mode .

[0033] Both the specific-action AVP and experimental-result AVP may be used to indicate one or more conditions that UE 103 may not be reachable via paging, UE 103 may be in a power-saving mode, and/or that UE 103 may be using eDRx. In some embodiments, UE 103 may be able to be paged for SMS services while in eDRx mode.

[0034] In some embodiments, PCRF 107 may use a combination of another AVP together with a numeric value of the specific-action AVP and additional values for the experimental-result AVP. For example, a new specific-action AVP value could include: UE IN UNREACHABLE STATE.

The possible states for this AVP may include:

1. UE IN COVERAGE ENHANCED MODE

2. UE PAGING NOT REACHABLE

3. UE IN PSM MODE

4. UE IN DRX MODE

In some embodiments, PCRF 107 may perform the mapping using a new standalone AVP, coupled with additional values in the experimental-result AVP.

[0035] PCRF 107 may transmit a message to P-CSCF 109. The message may be transmitted from PCRF 107 to P-CSCF 109 according to a Rx procedure. P-CSCF 109 may subscribe to PCRF 107 for notifications regarding the state of the signaling transmission path. For example, PCRF 107 may transmit a message, such as a RAR command, to PCRF 107 notifying P-CSCF 109 about the loss of the signaling transmission path. The RAR command may include the one or more reason codes mapped by PCRF 107.

[0036] In certain embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in Figures 1-8. Circuitry, in one example, may be hardware-only circuit implementations, such as analog and/or digital circuitry. Circuitry, in another example, may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuit(s) with software or firmware, and/or any portions of hardware processor(s) with software (including digital signal processor(s)), software, and at least one memory that work together to cause an apparatus to perform various processes or functions. In yet another example, circuitry may be hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that include software, such as firmware for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.

[0037] Figure 2 illustrates another example of a system according to certain embodiments. PCRF 205 may be in communication with UE 203, P-CSCF 207, and IP-CAN 209. UE 203 may transmit a SIP Register message to P- CSCF 207 via IP-CAN 209. P-CSCF 207 may transmit a Diameter AA- Request (AAR) command message to PCRF 205 to authorize resources based upon QoS resources, and to obtain network provided location information (NPLI) from IP-CAN 209. NPLI may be available in the form of the user location and/or the time zone information related to UE 203. The SIP message between P-CSCF 207 and UE 203 may include SIP re-INVITE, SIP 18x, and/or SIP 200 OK. QoS and NPLI information may be transmitted between PCPvF 205 and IP-CAN 209.

[0038] PCRF 205 may perform a session binding function with P-CSCF 207. PCRF 205 may transmit a Diameter Rx:AA-Answer command message to P- CSCF 207. P-CSCF 207 may transmit a 200 OK message back to UE 203. P- CSCF 207 may also subscribe to bearer level event notifications from PCRF 205.

[0039] Figure 3 illustrates an example of a signal flow diagram according to certain embodiments. For example, Figure 3 illustrates an IMS interacting with a UE operating in CE mode B and ECM-IDLE. In step 301, a terminating SIP-INVITE message intended for UE 330 may be received within an IMS network. TAS 370 with S-CSCF on the terminating side may receive the terminating SIP-INVITE message first. TAS 370 may then forward the terminating SIP-INVITE message to P-CSCF 360 that serves as the application function. P-CSCF 360 may then forward the terminating SIP- INVITE message to IP-CAN 340. P-CSCF 360 may also serve as an application function to PCRF 350 to request network resources from IP-CAN 340. PCRF 350 may then request the authorized network resources from IP- CAN (EPC) 340.

[0040] In addition, PCRF 350 may be aware of an IMS application being invoked. This may be based upon the IMS communication service identifier (ICSI) AF-application-ID AVP and/or the media being used from the SDP. The SDP may include one or more indications regarding the real-time transport protocol (RTP)-real time media for voice.

[0041] In step 303, IP-CAN 340 may attempt to page UE 330 to provide IMS terminating service to UE 330. The IMS terminating service may include terminating a voice call, terminating a SMS, or any other text or voice communication or message. After IP-CAN 340 attempts but fails to contact UE 330, IP-CAN 340 may generate a RAN/NAS reason for the failure. The reason may include that the service is incompatible with the current UE mode of operation. [0042] In step 305, IP-CAN 340 may transmit a RAN/NAS release cause to PCRF 350. The release cause may be transmitted via an interface between IP- CAN (EPC) 340 and PCRF 350, such as a Gx procedure. In step 307, PCRF 350 may perform cause mapping. PCRF 350 may map the RAN/NAS release cause received from IP-CAN 340 to a standardized value. The standardized value may be defined in a specific-action AVP and/or a new value defined in an experimental-result AVP.

[0043] The mapping function may be performed based upon the IMS application being invoked, or the media being used from SDP. The mapping function may also be performed based upon an RAN/NAS release cause that identifies the current CE mode of UE 330. For example, the CE mode may be CE mode A or CE mode B. If UE 330 is operating in CE mode B, PCRF may map the Rx cause to transient failure. Alternatively, if the RAN/NAS release cause indicates that UE 330 is operating using a narrow band or very low bandwidth, PCRF 350 may map the Rx cause to permanent failure. The mapping function may also be implementation dependent or standardized, for example, in accordance with the Global System for Mobile Communication Association (GSMA).

[0044] Using a specific-action AVP, the reason received from the IP-CAN may be mapped to a new, standardized value, for example: INDICATION OF RELEASE OF BEARER INCOMPATIBLE UE MOD

E (new value). Within a RAR, this value shall be used when the server reports the release of a bearer, for example, Packet Data Protocol (PDP) context removal for 3GPP-General Packet Radio Service (GPRS) or bearer/PDP context removal for 3 GPP -EPS, to the AF. This indication may inform the application function that the current mode of operation of UE 330 is not compatible with the quality of service requirement being requested for this service, for example, IMS voice/video.

[0045] In some embodiments, the reasons received from IP-CAN 340 may be mapped to a new, standardized value according to an experimental-result AVP. For example, for transient failures: new value (42xx): REQUESTED SERVICE TEMPORAPJLY NOT AUTHOPJZED due to incompatible UE mode. In other embodiments, for permanent failures: new value (50xx): REQUESTED SERVICE TEMPORARILY NOT AUTHORIZED due to incompatible UE mode. Both the specific-action AVP and experimental- result AVP may be used to indicate one or more conditions of that UE 330 is not reachable via paging, UE 330 is in a power-saving mode, and/or UE 330 is using eDRx. It is noted that UE 330 may still be able to be paged for SMS services while in eDRx mode.

[0046] In addition to utilizing these new specific-action AVP codes and experimental-result AVP values, PCRF 350 may use a combination of another AVP together with a numeric value of the specific-action AVP and additional values for the experimental-result AVP.

[0047] For example, a new specific-action AVP value could include, for example: UE IN UNREACHABLE STATE.

The possible states for this AVP may include:

1. UE IN COVERAGE ENHANCED MODE

2. UE PAGING NOT REACHABLE

3. UE IN PSM MODE

4. UE IN DRX MODE

In certain embodiments, PCRF 350 may perform the mapping using a new standalone AVP, coupled with additional values in the experimental-result AVP.

[0048] In step 309, PCRF 350 may transmit a message to P-CSCF 360. The message may be transmitted from PCRF 350 to P-CSCF 360. P-CSCF 360 may subscribe to PCRF 350 for notifications regarding the state of the signaling transmission path. For example, PCRF 350 may transmit a message, such as an RAR command, to P-CSCF 360 notifying P-CSCF 360 about the loss of the signaling transmission path. The RAR command may include the reason code generated in step 307.

[0049] In step 311, P-CSCF 360 may perform a local action. The local action may include a determination of whether P-CSCF 360 should proceed to step 313a and send a SIP rejection message to TAS 370, or whether P-CSCF 360 should proceed to step 313b and reattempt to contact UE 330 by resending a terminating SIP invite message. The determination may be based on the priority of the user, the presence of an MPS, and/or the Rx cause is a transient failure. P-CSCF 360 chooses at least one of these steps to proceed in processing.

[0050] In step 313a, P-CSCF 360 may send a message, for example a SIP rejection message, to the TAS 370. The SIP rejection message may be a SIP 500 with a SIP reason header. The SIP 500 message may contain the reason for failure. The SIP 500 message may contain the RAN/NAS release cause received from the IP-CAN, standardized value defined in a specific-action A VP, and/or a new value defined in an experimental-result A VP.

[0051] In step 315, TAS 370 may invoke another type of service, such as voice mail, call diversion, sending an SMS to UE 330 that UE 330 is missing a call due to limited coverage, or invoking the terminating access domain selection (T-ADS) functionality to attempt paging UE 330 through a secondary IP-CAN 340. In some embodiments, a secondary IP-CAN may include WLAN, a circuit switch domain, or other technique. The invocation may be based at least on the reason for failure received from P-CSCF 360.

[0052] Figure 4 illustrates an example of a method performed by an application function according to certain embodiments. In particular, Figure 4 illustrates a P-CSCF 450 subscribing to bearer event notifications from a PCRF 440 during an IMS registration procedure. In step 401, a UE 430 may transmit a SIP register message to P-CSCF 450 via IP-CAN 460.

[0053] In step 403, P-CSCF 450 may transmit a message to PCRF 440. The message transmitted may include a Diameter AAR message. PCRF 440 may perform a session binding procedure, as shown in step 405. In step 407, PCRF 440 may transmit a message to P-CSCF 450. The message transmitted may include a Diameter AAA message. In step 409, P-CSCF 450 may transmit a SIP Register message to an entity outside the IMS.

[0054] In step 411, P-CSCF 450 may receive a message. The received message may include a SIP 200 OK message. The received message may be transmitted to UE 430.

[0055] In step 413, P-CSCF 450, in certain embodiments, may subscribe to bearer event notifications from PCRF 440. When PCRF 440 becomes aware that UE 430 has entered a particular mode, PCRF 440 may notify P-CSCF 450 with a RAR message. The particular mode of UE 430 may include a power-saving mode, CE mode B, and/or a eDRx mode. The RAR message may include a new specific-action AVP that includes indications of the sleep pattern of UE 430, the sleep duration of UE 430, and/or the next time window that UE 430 will be available.

[0056] Figure 5 illustrates another example of a method performed by an application function according to certain embodiments. Figure 5 illustrates a P-CSCF 550 performing session binding with a PCRF 540 during an IMS registration. In step 501, a UE 530 may transmit a SIP Register message to P-CSCF 550.

[0057] In step 503, P-CSCF 550 may define downlink connection data. In step 505, P-CSCF 550 may transmit a SDP offer message to an entity within or outside the IMS. In step 507, P-CSCF 550 may receive an SDP answer from within or outside the IMS. In step 509, P-CSCF 550 may define uplink connection data.

[0058] In step 511, P-CSCF 550 may transmit a message to PCRF 540. The message may include a Diameter AAR message. In step 513, PCRF 540 may store session information and/or identify an IP-CAN session. PCRF 540 may be aware of the mode of operation of UE 530. For example, PCRF 540 may be aware that the mode of operation of UE 530 includes a power-saving mode, CE mode B, and/or a eDRx mode. The mode of operation may be derived based on other ongoing data sessions. In step 515, PCRF 540 may transmit a message to P-CSCF 550. The message may include a Diameter AAA message. The message may include mapped Rx cause information and/or a new experimental-result AVP.

[0059] In step 517, P-CSCF 550 may transmit a message. The message may include a SDP answer message. The message may be transmitted to UE 530. Alternatively, the message may be transmitted directly from P-CSCF 550 to UE 530. The message may include indications of the sleep pattern of UE 530, the sleep duration of UE 530, and/or the next time window that UE 530 will be available.

[0060] In step 519, PCRF 540 may perform provisioning of PCC and/or QoS rules. In some embodiments, PCRF 540 may transmit a message to P-CSCF 550, as shown in step 521. The message may include a Diameter RAR message. In step 523, P-CSCF 550 may transmit a message to PCRF 540. The message may be a Diameter RAA message. In step 525, P-CSCF 550 may transmit a SIP with NPLI to an entity within or outside the IMS in response to a request for access network information.

[0061] Figure 6 illustrates a method according to certain embodiments. In particular, Figure 6 illustrates a method performed by a network entity. The network entity, for example, may be a PCRF. In step 610, the network entity may receive one or more failure indications. In step 620, the network entity may map the failure indications to one or more rejection reason codes. The one or more rejection reason codes indicate that a user equipment is permanently or temporarily unavailable for connection. In step 630, the network entity may transmit the one or more rejection reason codes to a network application function to permanently or temporarily suspend further attempts by the network application function to contact the user equipment, adjust a retransmission timer in IMS to a greater value, and/or set a time to re-connect. [0062] Figure 7 illustrates a method according to certain embodiments. In particular, Figure 7 illustrates a method performed by a network entity. The network entity, for example, may be a P-CSCF. In step 710, the network application function may transmit a request to subscribe to bearer event notifications regarding the state of a signaling transmission path. In step 720, the network application function may receive one or more indications that a user equipment is permanently or temporarily unavailable for connection, wherein the indications cause the network application function to permanently or temporarily suspend further attempts to contact the user equipment, adjust a re-transmission timer in IMS to a greater value, and/or set a time to re-connect.

[0063] Figure 8 illustrates a system according to certain embodiments. In one embodiment, a system may include multiple devices, such as, for example, network entity 810. Network entity 810 may include one or more of UE, IP- CAN, PCRF, P-CSCF, TAS/S-CSCF, and eNB. A network entity may include a mobility management entity (MME), a base station, such as an evolved node B (eNB), a server, and/or other access node.

[0064] One or more of these devices may include at least one processor, respectively indicated as 811. At least one memory may be provided in one or more of devices indicated at 812. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Processor 811 and memory 812, or a subset thereof, may be configured to provide means corresponding to the various blocks of Figures 1 through 7. Although not shown, the devices may also include positioning hardware, such as global positioning system (GPS) or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted and may be included to determine location, elevation, orientation, and so forth, such as barometers, compasses, and the like.

[0065] As shown in Figure 8, transceiver 813 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 814. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple radio access technologies. Other configurations of these devices, for example, may be provided.

[0066] Transceiver 813 may be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that is configured both for transmission and reception.

[0067] Processor 811 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

[0068] Memory 812 may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory and which may be processed by the processors may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

[0069] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as UE, IP-CAN, PCRF, P-CSCF, TAS/S-CSCF, and/or eNB, to perform any of the processes described above (see, for example, Figures 1-7). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware. [0070] Furthermore, although Figures 1-7 illustrate systems including a UE, IP-CAN, PCRF, P-CSCF, and TAS/S-CSCF, certain embodiments may be applicable to other configurations, and configurations involving additional elements.

[0071] The features, structures, or characteristics of certain embodiments described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases "certain embodiments," "some embodiments," "other embodiments," or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. Thus, appearance of the phrases "in certain embodiments," "in some embodiments," "in other embodiments," or other similar language, throughout this specification does not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0072] One having ordinary skill in the art will readily understand that certain embodiments discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.

[0073] Partial Glossary

[0074] 3 GPP 3rd Generation Partnership Project

[0075] BL Bandwidth reduced low-complexity

[0076] AAA AA- Answer

[0077] AAR AA-Request [0078] AVP Attribute- Value Pair

[0079] CAN Connectivity Access Network

[0080] CE Coverage Enhancement

[0081] CSCF Call Session Control Function

[0082] DL Downlink

[0083] ECM EPS Connection Management

[0084] eDPvX Extended Discontinuous Reception

[0085] eNB Evolved Node B

[0086] EPC Evolved Packet Core

[0087] EPS Evolved Packet System

[0088] GPRS General Packet Radio Service

[0089] GPS Global Positioning System

[0090] GSMA Global System for Mobile Communications Association

[0091] Gx Interface between IP-CAN (EPC) and PCRF

[0092] ICSI IMS Communication Service Identifier

[0093] IEEE Institute of Electrical and Electronics Engineers

[0094] IETF Internet Engineering Task Force

[0095] IMS IP Multimedia Subsystem

[0096] IP-CAN IP Connectivity Access Network

[0097] ITU International Telecommunication Union

[0098] LTE Long-Term Evolution

[0099] MEMS Microelectricalmechanical System

[0100] MIMO Multiple Input Multiple Output

[0101] MME Mobility Management Entity

[0102] MPS Multimedia Priority Service

[0103] MTC Machine-Type Communications

[0104] NAS Non-Access Stratum

[0105] NPLI Network Provided Location Information

[0106] PCC Policy and Charging Control [0107] PCRF Policy and Charging Rules Function

[0108] P-CSCF Proxy-Call Session Control Function

[0109] PDP Packet Data Protocol

[0110] QCI QoS Class Identifier

[0111] QoS Quality of Service

[0112] RAA Re-Authorization Answer

[0113] RAN Radio Access Network

[0114] RAR Re-Authorization Request

[0115] RF Radio Frequency

[0116] RFC Request for Comments

[0117] RTP Real-time Transport Protocol

[0118] Rx Interface between P-CSCF and PCRF

[0119] S-CSCF Serving-Call Session Control Function

[0120] SDP Session Description Protocol

[0121] SIP Session Initiation Protocol

[0122] SMS Short Message Service

[0123] T-ADS Terminating Access Domain Selection

[0124] TAS Telephony Application Server

[0125] TS Technical Specification

[0126] UE User Equipment

[0127] UL Uplink

[0128] VoLTE Voice over LTE

[0129] WLAN Wireless Local Area Network