Residential/enterprise network connection management and csfb scenarios
Abstract
A method, in a first network element of a wireless communications network, such that the method comprises: receiving a first message (21-6, 22-6) from a mobility management entity, "MME", ( 2108, 2208), such that the first message is associated with causing a circuit switched alternative option procedure, "CSFB" to move a User Equipment, "UE", (2102, 2202) from a first network element (2104, 2204) to a second network element (2106, 2206); determine that Packet Switched Delivery, "PS HO" is not available for the CSFB procedure because the UE has only one or more Packet Data Network connections, "PDN", Local IP Access, "LIPA ", in the first network element; and sending a second message (21-7b, 22-9b) to the UE in response to said determination, such that the second message is a signal exchange message intended to trigger a connection release of Radio Resource Control, "RRC", with redirection to the second network element, such that the signal exchange message to trigger RRC connection release comprises one or more physical cell identities and associated system information in case the second network element is a Global System for Enhanced Mobile Data Speeds , destined to the Global System for the base station of the Evolution Radio Access Network for Mobile, "GERAN", or for the base station of the Terrestrial Radio Access Network of the Universal Mobile Telecommunications System, "UTRAN", and for the UE and the wireless communications network to support the "RRC connection release with redirection and System information from Multiple Cells to GERAN / UTRAN ", such that the second network element is one of a GERAN base station and a UTRAN base station.

Term
5 yearsto projected expiry
Projected expiry 27 September 2031, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
11 claims: 2 independent, 9 dependent
- 1ES 2 631 817 T3 REIVINDICACIONES 1. - Un método, en un primer elemento de red de una red de comunicaciones inalámbrica, de tal modo que el método comprende:recibir un primer mensaje (21-6, 22-6) desde una entidad de gestión de movilidad, «MME», (2108, 2208), de tal modo que el primer mensaje está asociado con provocar un procedimiento de opción alternativa conmutada en circuitos, «CSFB» para trasladar un Equipo de Usuario, «UE», (2102, 2202) desde un primer elemento de red (2104, 2204) a un segundo elemento de red (2106, 2206);determinar que la Entrega Conmutada en Paquetes, «PS HO» no está disponible para el procedimiento de CSFB debido a que el UE tiene únicamente una o más conexiones de Red de Datos en Paquetes, «PDN», de Acceso de IP Local, «LIPA», en el primer elemento de red;y enviar un segundo mensaje (21-7b, 22-9b) al UE en respuesta a dicha determinación, de tal manera que el segundo mensaje es un mensaje de intercambio de señales destinado a desencadenar una liberación de conexión de Control de Recursos de Radio, «RRC», con reconducción al segundo elemento de red, de tal modo que el mensaje de intercambio de señales para desencadenar la liberación de conexión de RRC comprende una o más identidades de celda física e información de sistema asociada en caso de que el segundo elemento de red sea un Sistema Global para Velocidades de Datos Móviles Mejoradas, destinado al Sistema Global para estación de base de Red de Acceso por Radio de Evolución para Móvil, «GERAN», o para estación de base de Red de Acceso por Radio Terrestre del Sistema de Telecomunicaciones Móviles Universal, «UTRAN», y de que el UE y la red de comunicaciones inalámbrica den soporte a la «liberación de conexión de RRC con reconducción e información de Sistema de Múltiples Celdas hacia GERAN/UTRAN», de tal manera que el segundo elemento de red es uno de entre una estación de base de GERAN y una estación de base de UTRAN.
- 2- El método de acuerdo con la reivindicación 1, en el cual el mensaje de intercambio de señales destinado a desencadenar la liberación de conexión RRC con reconducción, provoca una reconducción hacia el segundo elemento de red si el segundo elemento de red es una estación de base de GERAN o de UTRAN.
- 3- El método de acuerdo con la reivindicación 1, en el cual el primer elemento de red es una estación de base de nodo doméstico evolucionado, «HeNB».
- 4- El método de acuerdo con la reivindicación 1, en el cual el primer mensaje es una petición de modificación de contexto de UE, que incluye un indicador de CSFB.
- 5- El método de acuerdo con la reivindicación 1, en el cual dicha determinación de que la PS HO no está disponible para el procedimiento de CSFB comprende detectar una indicación, en el primer mensaje procedente de la MME, de que no está disponible la PS HO.
- 6- El método de acuerdo con la reivindicación 1, en el cual dicha determinación de que la PS HO no está disponible para el procedimiento de CSFB está basada en la existencia de un portador para el UE, que tiene un identificador de correlación asociado.
- 7- El método de acuerdo con la reivindicación 1, en el cual el procedimiento de CSFB está relacionado con una llamada originada por móvil.
- 8- El método de acuerdo con la reivindicación 1, en el cual el procedimiento de CSFB está relacionado con una llamada terminada por móvil.
- 9- El método de acuerdo con la reivindicación 1, en el cual la red de comunicaciones inalámbrica que da soporte a la «liberación de conexión de RRC con reconducción e información de Sistema de Múltiples Celdas hacia GERAN/UTRAN», comprende la red de comunicaciones inalámbrica que da soporte a la liberación de conexión de RRC con reconducción, e información de Sistema de Múltiples Celdas hacia GERAN/UTRAN.
- 10-Un primer elemento de red para una red de comunicaciones inalámbrica, que comprende un procesador configurado para llevar a cabo el método de acuerdo con cualquiera de las reivindicaciones 1 a 9.
- 11- Un producto de programa informático que comprende un medio de almacenamiento legible por computadora, no transitorio, que tiene, incorporado en él, código de programa legible por computadora, de tal manera que dicho código de programa legible por computadora está configurado para, cuando se ejecuta, hacer que un primer elemento de red de una red de comunicaciones inalámbrica lleve a cabo el método de acuerdo con cualquiera de las reivindicaciones 1 a 9.
Independent claims11
446 paragraphs in 25 sections, as filed
ES 2 631 817 T3
DESCRIPTION
CSFB Scenarios and Residential Network Connection Management
Field of the invention
The present invention is directed, in general, to communication systems and methods of operating the same. In one aspect, the present invention refers to the methods, systems and devices for managing the release of connection of access of IP [Internet Protocol - "Internet Protocol" -] local (LIPA "local IP access" -) that result from the mobility of a user equipment.
Description of Related Art
Within the Third Generation Partnership Project (3GPP - “3rd Generation Partnership Project” -), standards are being developed for the interface between the mobile core network and a femtocell, which is a small cellular base station, usually designed to be used in a home or small business. Home NodeB (HNB - “Home NodeB” -), Home eNB (HeNB - “Home eNB” -) and femtocell are concepts introduced for the Universal Mobile Telecommunications System (UMTS - “Universal Mobile Telecommunications System” -) and the Terrestrial Radio Access of evolved UMTS (E-UTRAN - “evolved UMTS Terrestrial Radio Access Network” -), of Long Term Evolution (LTE - “Long Term Evolution” -) to improve indoor and microcell coverage, as well as to promote the return transmission by cable lines to the «home». A femtocell is something widely used outside of 3GPP with the meaning of any cell with very small coverage and typically installed in private facilities (whether private in nature, corporate or residential / business). The Home NodeB (HNB), the Home eNB (HeNB), and the femtocell can have a business or residential IP network. The terms HeNB / HNB are used in 3GPP with specific meanings, that is, that the cell consists of a closed subscriber group (CSG) or a hybrid cell. A CSG identifies the subscribers of an operator who are allowed to access one or more cells of the public land mobile network (PLMN), but who have restricted access. An H (e) NB subsystem supports Local IP Access to provide access to connected, IP-capable User Equipment (UE) devices through an H (e) NB (es) subsystem that is, using H (e) NB radio access), to other IP-capable entities on the same residential IP network or enterprise IP network. The term macrocell, while not meaningful in the 3GPP specifications, is generally used to mean a cell other than a CSG cell.
One aspect of HeNB / HNB's functional capability is the ability to restrict access to individual users. For example, access may be restricted to employees of the company on whose sites the HeBN has been deployed, to customers of a particular coffee shop chain, or (in the case of HeNBs deployed in private homes), to individuals. In order to achieve this functional capability, the 3GPP has defined the concept of a Closed Subscriber Group (CSG). The CSG cell is one that indicates that it is a CSG cell (by means of 1 bit broadcast in the system information) and broadcasts a CSG ID (also in the system information). A cell can only indicate a single CSG ID (or none at all), although multiple cells can share a CSG ID. A UE device can be subscribed to multiple CSGs. The Ue may consist, for example, of a mobile terminal such as a cellular telephone, a personal data assistant (PDA - "personal data assistant" -) or a wirelessly enabled computer, although it is not limited by these. A subscription can be temporary in nature (for example, a coffee shop allows a customer one hour of access to its cSg).
3GPP standards are also being developed for the concept of selected IP traffic offloading (SIPTO), which allows Internet traffic to flow from the femtocell directly to the Internet, bypassing the network of operator core. The SIPTO is used to offload selected types of IP traffic (eg internet traffic) towards a defined IP network close to the UE's point of attachment to the access network. SIPTO is applicable to offloading traffic for the macrocellular access network and for the femtocell subsystem. SIPTO PDN connection capability indicates a PDP context or a PDN [Public Data Network - “Packet Data Network” -] connection that allows downloading of selected types of IP traffic (eg internet traffic) towards a defined IP network, close to the point of attachment of the UE to the access network. SIPTO is applicable to offloading traffic for the macrocellular access network and for the femtocell subsystem.
In addition, standards are being developed for Local IP Access (LIPA - “Local IP Access” -), which allows an IP-capable UE, connected, through direct access by femtocell, to other devices with IP capability of the local residential / corporate IP network. LIPA PDN connectability indicates a PDP context (in the case of a GERAN or UTRAN femtocell connected to a GPRS core network) or a PDN connection (in the case of an E-UTRAN femtocell connected to a GPRS core network) that provides access to services located on the local residential / corporate IP network of the femtocell subsystem.
In connection with these developing standards, the following abbreviations and meanings have been developed. The Connection Capacity Type indicates the type of connection capacity provided for a Connection Context.
ES 2 631 817 T3 packet data protocol (PDP - “packet data protocol” -) or a PDN connection, and it applies both to the connection capacity that is established in a macrocell (in which case, it can be either a remote connection capacity -that is, with a GGSN / PDN GW located in the operator's core network-, or a SIPTO connection capacity or remote IP access connection capacity (RIPA - “remote IP access ”)), as well as the connection capacity that is established in an H (e) NB (in which case, it can be either a SIPTO connection capacity, or a LIPA connection capacity).
A Closed Subscriber Group (CSG) identifies subscribers of an operator who are allowed access to one or more cells of the PLMN, but who have restricted access (CSG cells).
A CSG cell is a cell that is part of the public land mobile network (PLMN) that broadcasts a specific CSG identity, and that is accessible by members of the subscriber group closed to that CSG identity. All CSG cells sharing the same identity are identifiable as a single group for the purposes of mobility and load management. A CSG cell is considered synonymous with HNB or HeNB.
A list of allowed CSGs is a list stored in the network and in the UE, which contains all the CSG identity information of the CSGs to which the subscriber belongs.
A CSG owner is the owner of one or more of the H (e) NBs that have been configured as CSG cell (s) for a particular CSG. A CSG owner can, under the supervision of the H (e) NB operator, add, remove and view the list of CSG members.
Local IP Access (LIPA) provides access for connected IP-capable UEs, through an H (e) NB (i.e. using H (e) NB radio access), to other IP-capable entities from the same residential / business IP network. Traffic for Local IP Access is expected not to pass through the mobile operator network, with the exception of H (e) NB.
A LIPA PDN / PDP context connection is a PDN connection or PDP context that provides the UE with access to services located on the local corporate / residential IP network. The PDN / GGSN GW (or Local GW) is selected in such a way that this type of connection capability is provided. Alternatively, a LIPA PDN / PDP context connection is defined as a PDP context / PDN connection that provides access for connected IP-capable UEs, through an H (e) NB (i.e., using access by radio from H (e) NB), to other IP-capable entities on the same residential / business IP network. Alternatively, a LIPA PDN connection or LIPA PDP context is a PDN connection that the MME authorizes to establish a connection to a PDN GW [gateway - "gateway" -] for a UE connected to a HeNB, based on on a request from the UE for the establishment of a LIPA connection, and based on the CSG ID of the HeNB. Alternatively, a LIPA PDN connection or LIPA PDP context is a PDN connection that has been activated by the UE by requesting with the text "LIPA" the LIPA connection capability, and by informing the UE, by the MME, of the type of connection capacity provided.
LIPA PDN continuity refers to the UE that has a LIPA PDP context / PDN connection while in campaign or connected on an H (e) NB that maintains the connection when moving to another H (e) NB or a macrocell.
An evolved packet core (EPC) capability (eg SGSN, MME, S-GW, PDN GW, GGSN, etc.) is LIPA aware and / or aware of SIPTO, and / or locally aware of SIPTO if the functional capability determines that a given PDN connection or PDP context is a LIPA / SIPTO / locally SIPTO PDN connection or PDP context. Alternatively, the capability is LIPA aware and / or SIPTO aware, and / or locally aware of SIPTO if it has been configured to manage network contexts (e.g. PDN connection descriptors / PDP context and exchange signal signal) for LIPA / SIPTO / locally SIPTO connections.
A Network Address Translator (NAT - “Network Address Translator” -) is a translator that modifies the network address information contained in datagram packet (IP) headers while in transit through a traffic routing device , in order to establish a new mapping relationship from one IP address space to another.
A Packet Data Network (PDN - "Packet Data Network" -) is a network that provides data services, such as the Internet, Intranet and ATM networks.
A PDN connection is a connection to a specific PDN identified by a specific APN.
Remote connectability refers to a PDP context or PDN connection for which the GGSN or PDN GW, respectively, are selected in the PLMN core network according to ongoing selection mechanisms. Remote connection capability does not include providing SIPTO or LIPA connection capability, but could provide RIPA connection capability.
ES 2 631 817 T3
Selected IP Traffic Offload (SIPTO) operations offload selected types of IP traffic (eg internet traffic) to an IP network close to the UE's hitch point to the access network. SIPTO is applicable to offloading traffic for the macrocellular access network and for the H (e) NB subsystem.
The SIPTO PDN / PDP context connection refers to a PDP / PDP context connection for which the traffic extraction point (for example, PDN GW or GGSN) is close to the UE hitch point to the access network.
Locally from SIPTO refers to the offloading of selected types of IP traffic (eg internet traffic) on the H (e) NB, to the internet.
SIPTO Locally PDN / PDP Context Connection is a PDP context / PDN connection for which the traffic extraction point is the H (e) NB to which the UE is connected, and provides access to the internet.
Home Node B (HNB - “Home Node B” -) refers to the equipment at the customer premises that connects a UE according to 3GPP, through a UTRAN wireless air interface, to a mobile operator network, for example, using broadband IP return transmission.
Home Evolved Node B (HeNB - "Home Evolved Node B" -) refers to a customer premises equipment that connects a UE according to 3GPP, through an E-UTRAN wireless air interface, to an operator network mobile, for example, using broadband IP reverse transmission.
An H (e) NB gateway is a mobile network operator equipment (usually physically located at the mobile operator's premises) through which the H (e) NB obtains access to the operator's core network mobile. For HeNBs, the HeNB gateway is optional.
A default PDN connection is the connection to the PDN that the carrier has established by default for the UE (for a PDP connection in EPS or a PDP context in GPRS) (provided in the subscriber's profile). The UE may not know the APN for the default PDN even after the UE has hooked up to the network and obtains connectability for the default PDN.
The network architecture model for CSG cell support has been described in 3GPP TR 23.830 (Architectural Aspects of the Home NodeB and Home eNodeB) and is represented in relation to Figure 1, which shows a model of architecture for a Home NodeB access network 100. As depicted, network 100 includes one or more CSG-capable UEs 170 in communication with an HNB 110 via a Uu 175 reference point. The UEs 170 may consist, for example, of a mobile terminal such as a cellular telephone, a personal data assistant (PDA - "personal digital assistant" -) or a wirelessly enabled computer, although it is not limited by these. The HNB 110 is in communication with a HNB gateway (HNB GW) 120 through a Iuh reference point 115. The HNB GW 120 is in communication with a mobile switching center / visitor location exchange (MSC / VLR) 130 via an IuCS reference point 124. The HNB GW 120 is also in communication with a Support Node of GPRS in service (SGSN “serving GPRS Support Node” -) 140 through a reference point Iu-PS 126. A CSG List Server (CSG List Srv) 150 and a home location register / home subscriber server (HLR / HSS - "home location register" / home subscriber server "-) 160 are part of a home public land mobile network (HPLMN - "home public land mobile network" -) 190. Networks other than the HPLMN 190 in which the UE can operate, constitute a visited public land mobile network (VPLMN - "visited public land mobile network" -) 180. The MSC / VLR 130 and SGSN 140 are each in communication with the HLR / HSS 160 via D 135 and GRs6d 145 reference points, respectively. One of the CSG-enabled UEs 170 is in communication with the CSG List Srv 150 through the C1 set point 185. A more detailed description of the communication set points and elements is provided below. Figure 1.
HNB 110: The HNB 110 provides the RAN connection capability using the Iuh 115 interface, and supports the NodeB and most of the radio network controller (RNC) functions, as well such as HNB authentication, HNB-GW discovery, HNB registration and UE registration through the Iuh 115. The HNB 110 secures communication to / from the SeGW.
HNB GW 120: The HNB GW 120 serves the purpose of an RNC presenting itself, to the core network (CN - “core network” -), as a HNB connection concentrator, that is, the HNB's GW 120 provides a focus function for the control plane and provides a focus function for the user plane. The HNB GW 120 supports the Non Access Stratum (NAS - “Non Access Stratum” -) (NNSF - “NAS Node Selection Function” -).
Uu 175: Standard Uu interface between the UE 170 and the HNB 110.
Iuh 115: Interface between HNB 110 and HNB GW 120. For the control plane, the Iuh 115 uses the HNBAP protocol to support HNB registration, UE registration, and error handling functions. For the user plane, the Iuh supports the handling of the transport carrier at the user plane.
ES 2 631 817 T3
Iu-CS 124: Standard lu-CS interface between the HNB GW 120 and the circuit switched core network (CS “circuit switched” -).
Iu-PS 126: Standard lu-PS interface between the HNB GW 120 and the packet switched (PS) core network.
D 135: Standard D interface between mobile switching center / visitor location exchange (MSC / VLR) 130 and home location register / home subscriber server (HLR / HSS) 160.
Gr / S6d 145: Standard Gr interface between serving GPRS Support Node (SGSN) 140 and HLR / HSS 160.
C1 185: Optional interface between CSG List Server (CSG List Srv) 150 and CSG-capable UEs 170. An over-the-air exchange of signals (OTA - “over-the-air” -) is used to update the list of CSGs allowed in a UE 170 with a Universal Subscriber Identity Module (USIm - “Universal Subscriber Identity Module” - ) of Release 8 (Rel-8 - “Release 8” -). In some embodiments, the Device Management (DM “Device Management” -) of the Open Mobile Alliance (OMA - “Open Mobile Alliance” -) is used to update the list of CSGs Allowed in the UE 170 with a USIM prior to the Red-8.
UEs that are capable of supporting the Rel-8 functional capability of the 3GPP standard can support the CSG functional capability and maintain a list of allowed CSG identities. This list can be empty in case the UE does not belong to any CSG.
Each cell in a HeNB can belong to at most one CSG. It is possible that the cells of a HeNB belong to different CSGs and therefore have different CSG IDs.
The List of Allowed CSGs is provided as part of the CSG subscriber subscription data, to the MME.
The List of Permitted CSGs can be updated in the UE according to the result of the coupling procedure, the Tracking Area Update procedure (TAU - "Tracking Area Update" -), the service request and uncoupling procedures. , or by mechanisms at the application level, such as OMA or DM procedures.
The MME carries out access control for the access of UEs through CSG cells during the latch, combined latch, unlatch, service request and TAU procedures.
The UE is notified of the reason for the rejection by the network in case the UE is not allowed access to a CSG cell.
When a CSG ID that is not included in the UE's Allowed CSG List is manually selected by the user, a TAU procedure can be triggered by means of the selected CSG cell, immediately by the UE, in order to allow the MME carry out the CSG access control.
There are no restrictions on the assignment of the Tracking Area Identity (TAI - “Tracking Area Identity” -) for the E-UTRAN CSG cells. As a result, it is possible that a normal cell (non-CSG cell) and a CSG cell may share the same TAI or have different TAIs. Furthermore, it is possible that CSG cells with different CSG IDs may share the same TAI, or have different TAIs. It is also possible that CSG cells with the same CSG ID can share the same TAI or have different TAIs.
The concept of a list of TAIs also applies to CSG cells. The list of TAIs may include TAIs related to CSG cells and TAIs related to non-CSG cells. The UE does not differentiate these TAIs from the list of TAIs.
For the case of HeNB GW deployment, the TAIs supported in the HeNB GW are the aggregation of TAIs supported by the CSG cells under this HeNB GW.
Various architectures for HeNB CSG cells will now be described with reference to Figures 2-4. Beginning with Figure 2, there is illustrated an architecture model for a HeNB access network 200, which includes a dedicated, or exclusive use, HeNB GW. In the network 200 shown, a single UE 270 is in communication with a HeNB 210 through an LTE-Uu reference point 275. The HeNB 210 is also in communication with a HeNB gateway (HeNB GW) 220 through a reference point S1 215. The HeNB 220 GW is in communication with a mobility management entity (MME - “mobility management entity ”-) 230 through a reference point S1-MME 224, and is also in communication with the serving gateway (S-GW -“ serving gateway ”-) 240 through a reference point S1-U 226 . A CSG List Server (CSG List Srv) 250 and a Home Subscriber Server (HSS) 260 are part of a Home Public Land Mobile Network (HPLMN) 290. Networks other than the HPLMN 290 in which the UE can operate, they are a Visited Public Land Mobile Network (VPLMN) 280. The MME 230 is in communication with the HSS 260 through the reference point S6a 235. The S-GW 240 is in communication with the MME 230 through a point reference S11 245. The UE 270 is in communication with the CSG List Srv 250 through a C1 285 reference point.
ES 2 631 817 T3 below provides a more detailed description of the communication elements and reference points of Figure 2.
HeNB 210: The function supported by the HeNB 210 can be the same as those supported by an eNB (with the possible exception of a No Access Stratum (NAS) (NNSF) node selection function), and the Procedures running between an HeNB and the evolved packet kernel (EPC) may be the same as those running between an eNB and the EPC. The HeNB 210 ensures communication to / from the SeGW 240.
HeNB GW 220: The HeNB GW 220 serves as a hub for the control plane (C Plane), specifically the S1-MME interface 224. The HeNB GW can optionally terminate the user plane in the direction of the HeNB 210 and in the direction of the S-GW 240, and provide a relay function to act as a relay with the User Plane data between the HeNB 210 and S-GW 240. In some embodiments, HeNB's GW 220 supports NNSF.
S-GW 240: Security Gateway 240 is a logical function that can be implemented either as an independent physical entity or as an entity located in conjunction with an existing entity. The SGW 240 ensures communication to / from the HeNB 210.
LTE-Uu 275: Standard LTE-Uu interface between UE 270 and HeNB 210.
S1-MME 224: The interface of S1-MME 224 is defined between HeNB 210 and MME 230 in case a HeNB GW 220 is not used. If the HeNB GW 220 is present, as in Figure 2, the HeNB GW 220 can use an S1-MME interface to both the HeNB (S1 215) and the MME (S1-MME 224).
S1-U 226: The S1-U data plane is defined between HeNB 210, HeNB GW 220 and Serving Gateway (SGW) 240, depending on the arrangement of the network elements. The S1-U interface 226 from the HeNB 210 can be terminated at the HeNB GW 220, or a direct logical U-Plane connection between the HeNB and the S-Gw. S11 245: Standard interface between MME 230 and S-GW 240.
S6a 235: Standard interface between MME 230 and HSS 260.
C1 285: Optional interface between the CSG List Srv 250 and the CSG-capable UEs 270. OTA is used to update the list of CSGs allowed in a UE 270 with a USIM according to Rel-8. OMA is used to update the list of CSGs allowed in a UE with a pre-Rel-8 USIM.
Referring to Figure 3, an architecture model for a HeNB access network 300 is depicted, which does not include any dedicated HeNB GWs. In the network 300 shown, a single UE 370 is in communication with a HeNB 310 through a reference point LTE-Uu 375. The HeNB 310 is in communication with an S-GW 340 through a reference point S1- U 326, and is also in communication with the MME 330 through a reference point S1-MME 324. A CSG List Srv 350 and an HSS 360 are part of an HPLMN 390. Networks other than the HPLMN 390 that the UE can operate on are a VPLMN 380. The MME 330 is in communication with the HSS 360 through a reference point S6a 335. The S-GW 340 is in communication with the MME 330 through a reference point S11 345. The UE 370 is in communication with the CSG List Srv 350 through a reference point C1 385.
Referring to Figure 4, an architecture model for a HeNB access network 400 including a GW of HeNB for plane C is depicted therein. In the depicted network 400, a single UE 470 is in communication with a HeNB 410 via an LTE-Uu 475 benchmark. The HeNB 410 is in communication with an S-GW 440 via an S1-U 426 benchmark, and also in communication with a GW-HeNB 420 via a reference point S1-MME 422. The GW-HeNB 420 is in communication with the MME 430 through a reference point S1-MME 424. A CSG List Srv 450 and an HSS 460 are part of an HPLMN 490. Networks other than the HPLMN 490 in which the UE can operate is a VPLMN 480. The MME 430 is in communication with the HSS 460 through a reference point S6a 435. The S-GW 440 is in communication with the MME 430 through a reference point S11 445 . The UE 470 is in communication with the CSG List Srv 450 through a C1 485 reference point.
Conventionally, the UE connects to services through a remote connection using a PDP Context towards a GGSN of the core network, in the case of 2G / 3G, and a PDN connection to a PGW, in the system in evolved packages (EPS - “evolved packet system” -). As will be appreciated, PDN connection procedures are described in the enhancements to 3GPP TS 23.401 (General Packet Radio Service, GPRS) for the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and the TS of 3GPP 24.301 ("Non-Access Stratum Protocol (NAS) for Evolved Packet System (EPS)"). Additional signal flow information regarding PDN connection capability establishment and delivery procedures is described in U.S. Patent Application No. 12/685651 (filed January 11, 2010) and U.S. Patent Application No. 12/685662 (filed January 11, 2010).
ES 2 631 817 T3
As explained above, 3GPP is introducing the concepts of Local IP Access (LIPA) and Selective IP Traffic Offload (SIPTO) to supplement the conventional way of connecting a UE to services through a remote connection ( PDP context to a core network GGSN, in the case of 2G / 3G, and a PDN connection to a PGW in Evolved Packet System (EPS). With the LIPA and SIPTO connections, the UE is connected to an HNB / HeNB located in a home or corporate environment in order to obtain the local connection capacity, that is, the connection capacity through the IP network. , locally with respect to the HNB (that is, the IP network (residential or business) located at the HNB's 'home' premises). An example of this context is when a given UE application needs to print to a local printer, or an application needs to download an updated music playlist from a local information support media server. Various structures for providing LIPA and SIPTO connections through HNB / HeNB cells will now be described with reference to Figures 5 and 6, in which the difference between the connection capacity of LIPA and normal connection capacity.
Referring to Figure 5, there is illustrated a schematic diagram of an exemplary logical architecture network 1000 for use in an HNB cell illustrating local IP connectability. The network 1000 shown is substantially the same as that of Figure 1, with the addition of a Gateway GPRS Support Node (GGSN) 196 connected to SGSN 140, a PDN 198 connected to GGSN 196, and a home network 104 that has an illustrated coverage area defined by the circle shape. LIPA PDN connection capability has been illustrated from UE 170, through HNB 110, to local service 106, via dashed line 108. The normal PDN connectability through the core network (GW of HNB 120, SGSN 140 and GGSN 196), from UE 170 to PDN 198 via dashed line 105, has been illustrated.
In HNB contexts, the UE 170 determines whether it has access to a given HNB 110, thanks to the fact that the UE 170 is aware of its membership in a specific Closed Subscriber Group (CSG). The operator / owner of an HNB 110 creates a list of CSGs and provides the UEs 170, 172 with lists of CSGs, such that the UE 170, 172 determines which HNBs it can connect to. Therefore, a UE 170, 172 that is moving in macro coverage (that is, within cell cells that do not belong to a CSG / HNB) may encounter a CSG / HNB cell 104. The UE 170, 172 will use the information about the CSG to decide whether or not to attempt a connection with said HNB 110. Information about the CSG is usually configured inside the UE 170, 172 by the operator and can be dynamically modified, for example, using OMA-DM (Device Management). Information on USIM is also provided to support LIPA. Some of this information may also be managed by the party or third party that hosts the H (e) NB.
Referring to Figure 6, there is illustrated a schematic diagram of the logical architecture network 1100 provided by way of example for use in the HeNB cell, illustrating Local IP connectability. The network 1100 depicted is substantially the same as that of Figure 2, with the addition of a PGW 296 connected to the S-GW 240, a PDN 298 connected to the PGW 296, and a home network 204 that has a coverage area illustrated, defined by a circle shape. LIPA PDN connectability from UE 270, via HeNB 210, to local service 206, via dashed line 208 is illustrated. Normal PDN connectability via core network (HeNB 210, HeNB GW 220, S-GW 240 and PGW 296), has been illustrated from UE 270 to PDN 298 by means of the dashed line 205. In HeNB contexts, a UE 270 also determines its access rights to HeNB network 204 using the list of CSGs provided by HeNB 210.
As will be appreciated, the relevant 3GPP specifications in this field include 3GPP TS 23.829, entitled "Local IP Access & Selected IP Traffic Offload '(which describes the mechanisms for offloading IP traffic), and 3GPP S2-096006, entitled “Terminology update to agreed text in TR 23.8xy” (which presented functional capabilities and architectural aspects of LIPA and SIPTO). In addition, 3GPP S2-096050, entitled "LIPA and SIPTO node functions", and 3GPP S2-096013, entitled "Internet offload for macro network), set out the principles relating to the architecture for selected embodiments of the invention relating to Local IP Access and Selected IP Traffic Offload, based on traffic extraction carried out within H (e) NB using a local PDN connection, as well as Local IP Access and Selected IP Traffic Offload in H (e) NB, by NAT [Translation Network Address - “Network Address Translation” -]. 3GPP S2-095900, entitled "Architectural Requirements of Internet Offload", presented the architecture requirement that the offloading of traffic can be carried out without user interaction, and minimizing the impact on existing network entities and procedures due to the introduction of offloading traffic.
In addition to the above, 3GPP S2-096013, entitled “Internet Offload for macro network '), featured an additional SIPTO solution that supports SIPTO for UMTS macros and for HNB subsystems. The additional SIPTO solution has been represented in the schematic diagram of Figure 7, which shows a logical architecture provided as an example showing a Traffic Offload Function (TOF - “Traffic Offload Function” -) 1208 deployed in the Iu-PS. In the architecture shown, the TOF 1208 is located in the UI-PS and provides a standard UI-PS interface to the RNC 1206 and SGSN 1210. Selected IP Traffic Offload is enabled by NAT and SPI / DPI based on the
ES 2 631 817 T3 operator criteria at different levels (for example, for each user, for each APN [Access Point Name - “Access Point Name” -], for each type of service, for each IP address, etc.). The criteria can be configured via, for example, OAM. One PDN connection or PDP context is supported for both download and no-download traffic, while also allowing the use of different PDN connections or PDP contexts for download traffic and for traffic no download (for example, selecting traffic based on APN). The TOF 1208 includes a number of functions. First, the TOF 1208 inspects both NAS and RANAP messages to obtain subscriber information and establish the local UE context. The TOF 1208 also decides the download criteria to apply, based on the above information (eg, during PDP context activation and attack procedures). In addition to that, the TOF 1208 extracts the uplink traffic from the GTP-U tunnel and performs a NAT to offload the traffic if the offload criteria is met. The TOF 1208 can also perform reverse NAT on the received downlink offload traffic, and insert it back into the appropriate GTP-U tunnel.
A local gateway-based architecture solution is also presented in 3GPP S2-096015, titled “Local GWBased Architecture”, which supports Local IP Access for the H (e) subsystem. NB, to the Selected IP Traffic Offload for the H (e) NB subsystem, and to the Selected IP Traffic Offload for macronetwork. The solution applies to both types of approaches: with separate APNs for SIPTO and non-SIPTO traffic, and also with common APNs for SIPTO and non-SIPTO traffic. The local gateway solution has been represented in the schematic diagram of Figure 8, which shows a logical architecture provided by way of example for a proposed extension of non-roaming architecture for accesses according to 3GPP for SIPTO and for LIPA. . In the architecture represented, a Local Gateway (L-GW - "Local Gateway" -) 1306 is located together with the (H) eNB 1304. Between the L-GW 1306 and the GW 1310 of PDN, a Tunnel 1326 has been configured Extension of GW Local. The L-GW 1306 performs the gateway connection and routing to / from an external PDN (eg the internet, a business or home NW) which is equivalent to SGi. In addition, the L-GW 1306 performs tunneling of IP packets through the extension tunnel 1326, to / from the PDN GW 1310 (e.g. based on GTP, PMIP, IP within IP , or another). The L-GW 1306 also performs IP address handling (either assigning the IP address and transporting it to the PDN GW, or alternatively receiving the IP address from the GW of PDN, and carrying out NAT), as well as coordination with the (H) eNM 1304 when making use of local extraction (triggering the eNB for local traffic management). L-GW 1306 also implements a decision function when using local pull for uplink traffic (optionally, it can be part of the eNB). As will be appreciated, the LGW 1306 is not a PDN GW displaced to eNB / E-UTRAN, but encompasses only minimal functional capability.
With the L-GW 1306, the PDN GW 1310 functional capability is enhanced by the establishment of the extension tunnel 1326 by performing the PDN connection establishment for APNs that meet the criteria for local traffic. In addition, the PDN 1310 forwards traffic through the extension tunnel 1326 and to / from the S5 / S8 tunnel, and performs IP address handling (either obtaining the IP address from the L-GW, or alternatively its transport to the L-GW).
In the (H) eNB 1304, information about the UE access status for the cell (s) served by the (H) eNB 1304 is provided, to the L-GW 1306. In addition of this, the (H) eNB 1304 implements a decision function on the use of local extraction for uplink traffic (based on APNs). With the improved architecture shown in Figure 8, mobility between 3GPP and non-3GPP accesses can be managed, as the PDN GW 1310 is always on the road when the UE 1302 leaves the (H) eNB 1304, which means that the mobility support function of handover to non-3GPP accesses can be handled by PDN GW 1310, as usual. As a result, it is not necessary to provide such functional capability as part of the L-GW 1305 or within the (H) eNB 1304. In addition, it is possible to achieve dynamic control for the handling of LIPA / SIPTO in the PDN- GW 1310, which is only activated once the extension tunnel 1326 has been established.
Accordingly, there is a need for an improved method, system and device for managing LIPA connection releases, in order to overcome problems in the art, such as those outlined above. Additional limitations and disadvantages of conventional methods and technologies will become apparent to a person skilled in the art upon review of the remainder of this Application, with reference to the drawings and detailed description that follow.
Brief description of the drawings
The present invention can be understood, and its many purposes, features and advantages obtained, by considering the following detailed description, in combination with the drawings that follow, in which:
Figure 1 is a schematic diagram of an exemplary logic architecture for use in an HNB cell;
Figure 2 is a schematic diagram of an exemplary logical architecture for use in
ES 2 631 817 T3 a HeNB cell in which the network includes a GW of HeNB dedicated, or for exclusive use;
Figure 3 is a schematic diagram of another exemplary logic architecture for use in a HeNB cell where the network does not include a dedicated HeNB GW;
Figure 4 is a schematic diagram of yet another exemplary logic architecture for use in a HeNB cell in which the network includes a HeNB GW for the C-plane;
Figure 5 is a schematic diagram of an exemplary logical architecture for use in an HNB cell, illustrating the establishment of a Local IP connection;
Figure 6 is a schematic diagram of exemplary logic architecture for use in a HeNB cell, illustrating the establishment of a Local IP connection;
Figure 7 is a schematic diagram of an exemplary logical architecture for deploying Selected IP Traffic Offload on a UI-PS;
Figure 8 is a schematic diagram of an exemplary logical architecture for a proposed non-roaming architecture extension for 3GPP accesses for SIPTO and for LIPA;
Figure 9 is a schematic diagram of traffic flows in a HeNB subsystem in which the UE has at least one LIPA PDN connection;
Figure 10 is a schematic diagram of traffic flows in a HeNB subsystem in which the UE moves out of HeNB coverage;
Figure 11 is a signal flow diagram illustrating a LIPA / SIPTO PDN disconnect procedure, implemented as part of a service request procedure in which the MME provides bearers for all EPS bearers excluding bearers from LIPA / SIPTO;
Figure 12 is a signal flow diagram illustrating a LIPA / SIPTO PDN disconnect procedure in which a circuit switched alternate option call (CSFB) causes the MME to send a message. Initial UE context establishment with zero active PDN connections, in order to implicitly unhook the UE from the network;
Figure 13 is a signal flow diagram illustrating a LIPA / SIPTO PDN disconnect procedure in which a Circuit Switched Alternative Option Call (CSFB) causes the MME to send an HO Reject message indicating that it is not possible for the HO PS to implicitly unhook the UE from the network; Y
Figure 14 is a schematic block diagram illustrating exemplary components of a wireless and mobile communication device that may be used with selected embodiments of the present invention.
Detailed description
A method, a system and a device are provided to manage LIPA and / or SIPTO connection releases when a UE moves out of the coverage of a residential / business network, in the event that the connection is not supported. continuity of service for the LIPA / SIPTO PDN connection (s). In selected embodiments where the UE has only a single PDN connection, which is the LIPA PDN connection, automatically releasing it when the UE leaves home / business network coverage will cause the UE to be unhooked. network, since the UE has no PDN connection. In order to address the problems caused by not providing continuity of service for LIPA / SIPTO PDN connection (s), the PDN connection / PDP context creed in the HeNB / HNB by the MME / SGsN includes information context related to the UE indicating whether such connection is a LIPA PDN connection PDN connection or not. Furthermore, each UE can be configured to reconnect (or not reconnect) to the PDN corresponding to a certain APN or service, in the event that the PDN connection has been disconnected by the network as a consequence of mobility from an H (e) NB (where the UE was LIPA connected to such PDN) to a target cell (where no LIPA continuity was provided). In selected embodiments, the UE may have been configured to contain (1) an indication as to whether any PDN that has disconnected due to the lack of continuity of LIPA service, needs to be reconnected, (2) a list of APNs for which the PDN needs to be reconnected if the PDN has been disconnected as a result of the lack of continuity of LIPA service, (3) an indication of availability of continuity of LIPA service, (4) a list of indicators for PDN connection with certain characteristics, (5) an indication of whether non-LIPA disconnection is allowed in case an emergency call with insufficient credentials is not allowed, and / or (6) an indication of whether a UE is to retain at least two PDN connections of which one of the PDN connections is either to a particular APN, or to a default APN.
Various illustrative embodiments of the present invention will now be described in detail, with reference to
ES 2 631 817 T3 the accompanying drawings. While various details are set forth in the following description, it will be appreciated that the present invention can be practiced without these specific details, and that numerous implementation-specific decisions in the invention described herein can be made to achieve the specific goals of the device designer, such as adaptation to process technology or design-related constraints, which will vary from implementation to implementation. While such a development effort could be complex and time consuming, availing of the benefits of this invention would nevertheless be routine practice for those of ordinary skill in the art. For example, For example, selected aspects are shown in block diagram and flow chart form, rather than in detail, in order to avoid limiting or obscuring the present invention. Furthermore, some parts of the detailed descriptions provided in this specification are presented in terms of algorithms or operations on data located within a computer memory. Such descriptions and representations are used by those skilled in the art to describe and convey the substance of their work to other skilled in the art. Various illustrative embodiments of the present invention will now be described in detail, below and with reference to the figures.
Ongoing 3GPP discussions have addressed the treatment of LIPA / SIPTO PDN connection releases associated with UE mobility. In these discussions, there is currently a preference not to provide continuity of service for a LIPA PDN connection if the UE moves out of the coverage of the home / business network and instead releases the PDN connection by LIPA. This preference to release connections is based on a number of factors. First, there is concern that a lawful interception will be applied to local access to IP resources in case the UE resides in macro (e) NB coverage and continuity of service is maintained. Also, it will be difficult to establish charging schemes that change as the UE moves from H (e) NB to macro (e) NB. There may also be authentication complications involved in maintaining service continuity. Based on these discussions, Release 10 of 3GPP S1-100316, entitled “Mobility for Local IP Access (LIPA)”, and 3GPP S1-100321, entitled “Requirements Common SIPTO requirements for macro network and H (e) NB subsystems ”(“ SIPTO requirements common to macro network and H (e) NB subsystems), specifies that mobility of a connection from LIPA to macro network is not supported, whereas mobility of the LIPA connection between H (e) NBs of the same residential / business network is supported / required. In addition, 3GPP Release 10 S1-100321, entitled “Common SIPTO requirements for macro network and H (e) NB subsystems”, specifies that mobility of a SIPTO connection within the macronetwork should be supported, and mobility from H (e) NB to macro and between H (e) NBs may be supported.
In view of the preference against maintaining continuity of service for a LIPA connection when the UE leaves the residential / business network coverage, there are a number of miscellaneous problems that are created as a result of non-UE disconnections. desired. As explained more fully below, these release problems have multiple dimensions, including problems with PS services when UE mobility occurs in a connected mode, problems triggered by CSFB procedures when mobility occurs in a connected mode. , as well as problems with or without ISR, when the mobility of the UE occurs in a free mode. In explaining these issues, LIPA mechanisms should be considered, which also work for UEs in pre-Delivery 10 conformance (that is, UEs that are not aware of LIPA connectability, such as occurs when the network provides the LIPA connection capability to the UE based on the subscription profile or a network decision, without the UE being aware of such decision). For such UEs, the handshake and NAS mechanism cannot be modified in order to solve the identified problems.
For the purposes of illustrating the UE disconnect problem, reference is now made to Figures 9-10, which schematically illustrate the release of a LIPA PDN connection as the UE moves out of the network coverage of the UE. HeNB enterprise, such that the term "PDN connection" refers to both a PDN Connection involving a HeNB and a PDP Context involving an HNB, unless explicitly stated. In particular, Figure 9 is a schematic diagram of traffic flows in a HeNB subsystem 1400, in which the UE 1416 has a LIPA / SIPTO PDN connection 1430 and a core network (cN) PDN connection 1432. . Once the LIPA / SIPTO PDN connection 1430 is established, user plane traffic for LIPA and SIPTO does not go through the core network connection 1432. Instead, traffic goes from UE 1416, through eNB Local 1422, S-GW Local 1424, and P-GW Local 1426, all of which have been illustrated so that they are all located together within HeNB 1420, as indicated by line 1430. If UE 1416 has a non-SIPTO PDN connection, traffic goes through HeNB-GW 1410, S-GW 1408, and P-GW 1406, to core PDN 1404, as indicated by line 1432. Since the PDN connection 1432 can be released at any time (for example, due to predefined UE settings or criteria), there are times, when the UE 1416 has only a single PDN connection when connecting to the H ( e) NB 1420, and such PDN connection is a LIPA PDN connection 1430.
In order to illustrate the UE disconnect problem, reference is now made to Figure 10, which depicts a schematic diagram of traffic flows within a HeNB subsystem 1500 in which the UE 1416 moves out of HeNB coverage when you have only one LIPA PDN connection. In this case, the reference to the transfer "outside the H (e) NB" indicates both such a case that the UE moves from the coverage
ES 2 631 817 T3 from a H (e) NB cell to macrocell coverage, such as the case where the UE moves between H (e) NB cells for which PDN continuity of LIPA (eg, H (e) NBs with different CSGs). LIPA PDN continuity between any H (e) NB cells may not be supported. Thus, Figure 10 illustrates the fact that the UE 1416 moves to a second position 1516 where there is macrocoverage, although the UE 1416 can also move to another H (e) NB for which no support is supported. LIPA PDN continuity. As soon as the MME 1414 detects that the UE is not connected to the H (e) NB 1420 (for example, when the UE has moved to a different cell where LIPA continuity is not supported), the MME 1414 releases the LIPA PDN connection 1430, since there is no need to maintain the capacity of the LIPA PDN connection. As a result, there is no PDN connection for the UE 1516. As described more fully below, the MME 1414 can detect that the UE 1516 is out of range of the H (e) NB 1420 based on a variety of detection mechanisms, such as when the UE 1516 performs an Update Tracking Area (TAU) or a Routing Area Update (RAU - "Routing Area Update" -) from a different cell, or when the UE 1516 responds to a remote warning from a different cell, etc.
In E-UTRAN, a UE has to maintain at least one PDN connection for the UE to be considered hooked to the network. If there is no PDN connection, the UE is unhooked from the network. Figure 10 shows how the disconnection problem arises when a UE 1416 has only a single active LIPA PDN connection 1430, and the MME 1414 releases the LIPA PDN connection 1430 upon detecting that the UE 1416 has moved to a new position that is no longer connected to the H (e) NB 1420. When disconnection occurs, the UE 1516 may not know why it is being disengaged and why the LIPA PDN connection 1430 is being released, and is then forced to re-engage the network. This applies to both NAS free mode mobility and NAS connected mode mobility. As will be appreciated, while the above discussion refers to LIPA PN connections, the same challenges apply to a LIPA PDP Context (in the case of HNB) or to Local SIPTO connection capability, unless otherwise specified. explicitly state otherwise. And, although it is not explicitly shown, it will also be appreciated that similar problems arise when the mobility of the UE is from the H (e) NB 1420 towards a GERAN / UTRAN (that is, involving an SGSN), in which case it is It is necessary to deactivate the active PDP context (corresponding to the LIPA connection), not even when the UE does not need to be unhooked.
In this workplan, a number of problem cases associated with LIPA connection releases are identified and explained more fully below, in relation to Figure 10. In addition, solutions to handle the various connection release issues, as discussed below.
In the case of mobility in the connected mode, there are a number of problem cases that arise in the case of an active delivery in which the UE has mobility in the connected mode of NAS.
In an exemplary problem case, a UE 1416 in connected mode has a LIPA PDN connection or SIPTO connection capability / SIPTO PDN connection 1430. As the UE 1416 in connected mode moves out of the coverage 1420 of the HeNB (which is directly connected to the residential / business network 1402), to a second position 1516 of a target E-UTRAN cell (for example , eNB cell 1412 or other HeNB cell for which LIPA continuity is not supported), the source HeNB 1420 makes the decision to deliver (HO - "handover" -) the UE to the target cell 1412 based on the measurement reports obtained from the UE 1516. The HeNB 1420 sends a HO NECESSARY message to the MME 1414 . As the HO REQUIRED message contains a Target ID, the MME 1414 determines that the LIPA / SIPTO service should not be continued in the target cell 1412 (for example, based on the fact that the target cell is a macrocell or an H (e) NB from a different CSG). Based on this determination, the MME 1414 should release the LIPA / SIPTO PDN connection 1430, but the existing specifications do not specify how the MME 1414 handles the LIPA / SIPTO PDN connection release.
In another troublesome case, a connected mode UE 1416 is delivered from the HeNB 1420 to a GERAN / UTRAN cell (not shown) for which LIPA PDN continuity will not be supported. An example will occur when a UE 1416 having only one LIPA PDN connection 1430 performs an IRAT Ho to GERAN / UTRAN where LIPA continuity is not supported. In this case, the UE can be unhooked from the network or without PDP contexts, in the event that the LIPA connection is released, but the existing specifications do not specify how to handle the IRAT HO. Also, if the UE 1416 has other PDN connections in addition to the existing LIPA PDN connection 1430 in the source cell, then the LIPA PDN connection 1430 needs to be unhooked during this IRAT HO. The context information between the network (SGSN) and the UE containing information about the active PDN connections / PDP contexts, could be out of sync for a moment, until a new RAU is carried out by the UE and the context between the UE and the SGSN is synchronized. In cases where the context is out of sync, the UE incorrectly considers that the PDP context corresponding to the LIPA connection is still active.
In another troublesome case, a connected mode UE 1416 is moved from the HNB cell or coverage (not shown) to a target cell (eg, GERAN / UTRAN) for which no LIPA PDN continuity is provided. An example of this would occur when the UE is within HNB coverage and has a
ES 2 631 817 T3 LIPA / SIPTO PDP context. In the event that continuity of service is not supported, the PDP context will be released when the SGSN detects that the UE has moved out of HNB coverage. However, the context information between the network (the SGSN) and the UE containing information about active PDN connections / PDP contexts, could be out of sync for a while, until a new RAU is performed and the context is synchronized between the UE and the SGSN. Due to the out-of-sync context, the UE, meanwhile, considers the PDP context corresponding to the LIPA connection still active.
Regarding mobility for NAS-free UE, there are a number of troublesome cases that arise when the LIPA connection is disconnected in the course of free-mode mobility and the UE enters NAS-connected mode after leading to perform a free movement outside the H (e) NB.
In a first troublesome case, the UE 1416 moves from a HeNB cell coverage 1420 to a second position 1516 located in a target cell 1412 (eg, an eNB or HeNB cell) for which no provision should be made. continuity. After moving to the target cell, the UE 1516 can perform a SERVICE REQUEST on a target cell (eg one from E-UTRA) that is not directly connected to the residential / business network. Upon receiving the SERVICE REQUEST (SR - "SERVICE REQUEST" -) from the UE, through the target cell, the MME 1414 determines that it cannot serve the ST and needs to release the PDN connection capacity of LIPA 1430. The MME 1414 releases the LIPA PDN connection capability 1430 by rejecting the service request and disconnecting the LIPA PDN connection setup if the UE has other active PDN connections. On the other hand, if the UE has only the LIPA PDN connection before entering the ECM-FREE mode, a release of the LIPA PDN connection results in the UE having no PDN connection left. active, as a result of which the UE is unhooked from the network by the MME without the UE being properly informed, as the current specifications do not require the MME to indicate why the UE was unhooked.
In another troublesome case, the UE 1416 is translated from a HeNB 1420 to GERAN / UTRAN (not shown). In this case, the UE in FREE mode performs a Tracking Area Update (TAU) in a UTRAN cell where no continuity in LIPA service is provided. In particular, the UE will carry out a TAU in FREE mode when (1) the UE enters a new Tracking Area (TA - “Tracking Area” -) that is not on the list of TAIs that the UE obtained from the MME in the last record (hitch or TAU); and (2) the TA periodic update timer has expired. If the target cell is not directly connected to the home / business network when the UE performs the TAU, the MME needs to disconnect the active LIPA PDN connection, but the current specifications do not specify how the MME behaves. in the presence of LIPA connections, since the MME needs to release such PDN connections.
In another problem case, the UE is moved from an HNB to a GERAN / UTRAN. In this case, the UE in FREE mode (having at least one LIPA PDN connection via HeNB) performs a Routing Area Update. In particular, the UE carries out the RAU when the UE enters a new Routing Area (RA - "Routing Area" -), and when the RAU timer expires. The new SGSN sends a CONTEXT REQUEST message to the old MME during the RAU, and this MME responds with a CONTEXT RESPONSE message. Upon determination that the UE has moved to a cell for which LIPA PDN continuity cannot be supported, the network disconnects the LIPA connection, but the current specifications do not specify whether the MME or SGSN should trigger the disconnection. , nor how.
Regarding the delay in the discovery of the loss of connection capacity in active free mobility, there are several problematic cases that arise from mobility in free mode when there is a delay in discovering that the connection capacity has been lost , with or without Reduction in the Exchange of Signals in Free mode (ISR - “Idle mode Signaling Reduction” -).
In a problematic case provided by way of example, the UE 1416 is translated between a HeNB 1420 and an eNB 1412, or between an HNB and a macro GERAN / UTRAN, or between HeNBs (respectively, HNBs) belonging to different CSGs and for the which LIPA continuity is not to be provided. If the UE roams freely within the Routing Area (RA) / Tracking Area (TA), the UE does not perform a NAS handshake to register its position with the network. In case there is a significant delay before the UE conducts any NAS handshake or the UE transmits data, the UE does not realize that it has lost connection capacity, which can be a problem, such as for promotion services when the data to be provided to the EU cannot be provided.
In another problem case, the UE is moved from a HeNB to a GERAN / UTRAN cell where the ISR is active. When free mobility is performed by the UE from the H (e) NB to a cell for which the LIPA PDN connection capability is not to be supported, and the ISR is active and the UE is moves within the ISR area, the UE does not carry out a NAS handshake to register its position with the network and therefore it may take a long time before the UE performs any NAS handshake (unless it needs to transmit data) and before the UE realizes that it has lost connection capability. Such a loss of connection capacity can be a problem for promotion services, since the data to be provided to the UE cannot be provided. In addition, if the UE was using a promotion service that used the LIPA PDN connection, or was using the default bearer of the LIPA connection.
ES 2 631 817 T3
LIPA PDN to transport the data to the UE, the UE will not be able to receive any promotion data until it realizes that it has been disconnected and until it has taken a recovery action, such as a reclosing. Since an RAU (which will synchronize the UE and SGSN contexts) or promotion service survivability can occur long after free-mode mobility, the UE will not receive any data that has been pushed forward from the service of promotion, whereas if the UE has been informed of the PDN disconnection from LIPA, it may have reconnected to the promotion service as appropriate from the target cell with a new PDP context.
Regarding the delay in the discovery of the loss of connection capacity in mobility in active mode, there are several problematic cases that arise from mobility in active mode when there is a delay in discovering that the connection capacity has been lost .
In an exemplary problem case, the connected mode UE moves from a HeNB to the GERAN / UTRAN when the ISR is active, resulting in a delay in discovering a loss of connection capacity. This problem exists if a UE that has performed HO between RATs and finds itself without RABs for a given PDP context, is allowed to still consider the PDP context as active. When a handover has taken place by a UE that is active for a non-LIPA PDP, from the cell coverage of H (e) NB to a target cell (for example, from GERAN / UTRAN) In such a way that the LIPA PDN connection capability is not supported, the PDP context corresponding to the LIPA PDN connection is disconnected. When the ISR is active, the UE will not perform the RAU at the end of the delivery if the delivery is to an RA in the ISR area. However, unless the UE is informed immediately, the UE may believe that the PDP context corresponding to the LIPA PDN is still connected, since even though there are no active RABs for such a connection, the UE still believes that PDP context is active. If the UE was using any promotional service through the LIPA PDN connection, the UE will not be able to receive any promoted data until it realizes that it has been disconnected. Also, since a RAU (which will synchronize the UE and SGSN contexts) or survival mechanisms of the promotion service can happen after a long time from delivery, the UE will lose any promoted data from the promotion service, while , if the UE has been informed of the LIPA PDN disconnection, it may have reconnected to the promotion service as appropriate from the target cell with a new PDP context.
In another problematic case, the connected mode UE drifts from HNB cell coverage to macrocell coverage (eg GERAN / UTRAN), resulting in a delay in discovering the loss of connection capacity. If the UE performs handover from an HNB to a target GERAN / UTRAN cell where the LIPA PDN connectability is not supported, the PDP context is disconnected. However, the UE may not carry out a RAU as part of the handover, in which case the UE and the SGSN are not synchronized with respect to the active PDP context information.
Regarding the delay in disconnection for mobility in free mode, there is a problem related to the temporal sequence, which is orthogonal to the other problem cases, and the solution can be beneficial for both mobility in free mode and for mobility in active mode. In this case, when the UE 1416 moves out of the coverage of the H (e) NB 1420, the LIPA connection is released upon detection, and is then re-established when the UE 1416 moves back into the range. the coverage of the H (e) NB 1420. However, there may be situations in which the UE 1416 may soon return to the H (e) NB 1420, or it may continue to move back and forth between the H (e) NB 1420 and macrocoverage. In these scenarios, the LIPA connection will be established and released repeatedly, resulting in significant handshake header information. As a result, it may be desirable to delay the release of the LIPA connection when the UE 1416 moves out of the coverage of the H (e) NB 1420, in order to optimize the scenario in the event that the UE 1416 returns. to H (e) NB 1420 relatively fast.
Regarding the delivery to GERAN / UTRAN triggered by Alternative Option Switched in Circuits, there are several problematic cases that arise when a UE connected to a HeNB can be hooked in a combined way for CSFB services, such as when the delivery to GERAN / UTRAN it is triggered by CSFB.
In an exemplary problem case, the UE may have one LIPA PDN connection and zero non-LIPA PDN connections, across the core network. When the CSFB is triggered for Mobile Originated (MO - “Mobile Originated” -) or Mobile Terminated (MT - “Mobile Terminated” -) services, a PS HO of the data carriers can be triggered by the HeNB and is permissible over the network, because the target cell supports DTM and PS HO as part of the CSFB procedure. In this case, the network delivers the non-LIPA PDN connections and disconnects the LIPA PDN connections, or, if there are only LIPA PDN connections, the MME rejects the PS hO. If the MME rejects the PS HO, the CSFB, either for mO or for MT, will fail accordingly. In the event that HO PS is possible, but the UE or the network fails to support DMT, then with certain starting conditions, the GERAN PS bearers will be suspended. If the target cell is a GERAN cell and DMT is not supported in the target cell, the UE will suspend the PS bearers (including those corresponding to the LIPA PDN connection). Once the CS service that triggered the alternate CS option has been terminated, the UE can either move back to the E-UTRAN and retake the PS bearers, or it may remain in the GERAN and retake the bearers of . If the UE is
ES 2 631 817 T3 translates back to the initial H (e) NB, then the LIPA PDN connection can be resumed based on the CSFB and EPS mechanisms in progress at that time. For example, when the UE performs NAS handshake to the MME (eg with a Service Request or TAU), the MME picks up the suspended bearers.
In another problem case, the UE may have one LIPA PDN connection and zero or more non-LIPA PDN connections across the core network. When the CSFB is triggered for MO or MT services, a PS HO of the data bearers may not be performed. If the PS HO is not carried out as part of the alternative option procedure, and the UE has suspended the PS bearers, and if the UE moves back to the E-UTRAN, then the UE carries out an exchange of NAS signals (eg, a Service Request or TAU) with the MME. The UE could move back to a target U-TRAN cell that is different from the initial HeNB cell. Said target E-UTRAN cell can be a macrocell or a HeNB with a different CSG ID. Assuming that continuity of service (that is, mobility) is not allowed for a PDN connection, between the initial HeNB (that is, where the LIPA PDN connection was created) and the target HeNB, then the MME ensures that the LIPA PDN connection is disconnected. Also, if the target E-UTRAN cell is a macro cell, then the MME guarantees that the LIPA PDN connection is disconnected.
By maintaining the LIPA PDN connectability in future networks corresponding to networks in accordance with deliveries after Delivery 10, the continuity of LIPA will be enabled, such that there will be problems associated with maintaining the PDN connectability of LIPA. In such future cases, a UE will need to know whether it is connecting to a network that supports LIPA continuity or not. Consequently, a UE cannot know whether, when moving out of the coverage of an H (e) NB, continuity is provided or not in the session.
In view of the above problem cases associated with LIPA connection releases, a number of solutions are described and disclosed herein that can be applied to manage the identified connection release problems. For example, the PDN connection release procedures initiated by the MME can be combined with delivery procedures to release a PDN connection when the UE moves out of H (e) NB coverage in most cases ( and, similarly, the PDP context deactivation procedure initiated by the SGSN). However, there are other solutions disclosed hereinafter in which, when creating a PDN / PDP context connection in a HeNB / HNB, the MME / SGSN stores in the context information related to the UE an indication whether such connection is a LIPA PDN connection PDN connection, or not. In addition, the solution includes configuring the UE (for example, by the operator or by the user) in terms of reconnecting the PDN corresponding to an APN or service if, as a consequence of mobility from an H (e) NB in the Since the UE was LIPA connected to said PDN, to a target cell for which LIPA continuity was not provided, such PDN connection was disconnected by the network. Alternatively, the UE may have been configured not to reconnect the PDN that was disconnected as a result of the UE's mobility.
Description of achievements
In selected embodiments, the operator configures the UE using an OMA DM management object (MO) to contain an indication of whether it is necessary to reconnect any PDN that had been disconnected as a result of the failure. continuity of service from LIPA. The UE may also have been configured to contain a list of APNs for which the PDN needs to reconnect in the event that the PDN had been disconnected as a result of the lack of continuity in the LIPA service. In other embodiments, the UE has been configured to contain an indication of LIPA service continuity availability (i.e., only between CSG cells for which the UE is a member of the CSG, or if not roaming, or if macro mobility is given, or in case macro mobility is given + open CSG cells are given). By default, this indication can be set to some value, for example "LIPA service continuity is not available". The UE may also have been configured to contain a list of flags for a PDN connection with certain characteristics (i.e. an indication that the PDN connection can be used for IMS, or an indication requesting to receive P-CSCFs in the message network response). A configured UE may also contain an indication as to whether non-LIPA disconnection is allowed if an emergency call with insufficient credentials is not allowed, and / or an indication as to whether a UE holds at least two PDN connections in the case of that one of the PDN connections is either to a particular APN or to a default APN (which is known to end with a non-P GW), when it is not in PS mode 2 of operation.
In selected embodiments, when the UE activates a LIPA PDN connection, the MME stores the pair of CSG IDs and the APN for the LIPA PDN connection, such that a LIPA PDN connection is activated in the cell. CSG ID. In other embodiments, when the UE activates a LIPA PDP context, the SGSN stores the pair of CSG IDs and the APN for the LIPA PDP context such that the LIPA PDP context is activated in the cell of CSG ID. In some embodiments, the UE activating the LIPA PDN connection, or the UE activating a LIPA PDP context, includes sending the UE a connection request. the PDN to the MME or the MME receives a PDN connection request from the UE, or the UE sends a hook request to the MME, or the MME receives a hook request from the UE, or
ES 2 631 817 T3 for the UE to send a PDP context request to the SGSN, or for the SGSG to receive a PDP context request from the UE.
As used herein, a LIPA PDN connection is a PDN Connection that the MME authorizes for its ability to connect to a PDN GW for a UE connected to a HeNB, based on a request from the UE for LIPA connectability, and based on HeNB's CSG ID. Alternatively, a LIPA PDN Connection is a PDN Connection that has been activated by the UE by requesting LIPA connection capability with the text "LIPA", and by informing the mMe to the UE of the type of connection capability provided.
In this solution, the TAU procedure is initiated by the UE and is used for various purposes, including synchronizing the EPS bearer context of Ue with the EPS bearer context of MME for the mobility of the U, such that the source cell is a CSG cell and the target cell is not a CSG cell, when the UE has at least one LIPA PDN connection. The TAU procedure is also used to synchronize the UE EPS bearer context with the MME EPS bearer context for the mobility of the UE, such that the source cell is a CSG cell and the cell The target cell is a CSG cell, and so the CGS-ID of the target cell is not the CSG-ID of the source cell, when the UE has at least one LIPA PDN connection.
Accomplishments: The MME releases LIPA / SIPTO PDN connections before sending the Initial Connection Establish Request message. According to selected embodiments, another solution is described with reference to Figure 11 and undertakes NAS free mode mobility case in which UE enters NAS connected mode after starring free mode mobility outside H (e ) NB. In this solution, if a UE 1802 sends a Service Request (SR - “Service Request” -) to MME 1806 from a cell for which LIPA / SIPTO continuity of service is not provided for a previously LIPA PDN connection Established in a HeNB, the MME 1806 clears the LIPA / SIPTO PDN connections before sending an Initial Set Context Request message to the target eNB 1804.
The assumptions applied in this case are (1) that you had a PDN connection going through the core network, as well as a LIPA PDN connection, before going into FREE mode, (2) which is not given support for service continuity for LIPA and locally SIPTO connections, (3) that the UE is in ECM-FREE mode before sending the SERVICE REQUEST, and (4) that relocation of the MME.
In operation, a UE 1802 sends a Service Request ( signal flow 18-1) to the MME 1806 from a cell that does not provide LIPA / SIPTO continuity of service for a previously established LIPA PDN connection in a HeNB. Upon receiving the SR from the UE 1802, the MME 1806 discovers that the UE 1802 is connected to a cell for which no LIPA / SIPTO continuity of service is provided. Before MME 1806 sends an Initial Context Set Request message to target eNB 1804 (signal flow 18-3), the service request is handled in MME 1806 (signal flow 18-2) providing bearers for all EPS media except LIPA media if there are PDN connections that are not LIPA PDN connections. The remainder of the procedure (signal flows 18-4 to 18-9) follows the Service request procedures initiated by the UE.
Embodiments: CSFB selected with PS HO. Another solution is described that handles the case of deliveries to GERAN / UTRAN that are triggered by an alternative option of CS with HP of PS. In this network-based solution, the MME performs delivery preparation and execution during the CSFB procedure only for non-LIPA PDN connections.
In operation, if the UE has one or more active PDN connections in addition to one or more LIPA PDN connections, then, following the triggering of the PS HO to GERAN / UTRAN during the CSFB procedure, the MME performs a preparation and execution of delivery only during for non-LIPA PDN connections, and the mMe requests RAB assignment on the target system only for non-LIPA connections or for all PSN connections, by excluding the LIPA PDN connection, or by not requesting RAB mapping in the target system for LIPA PDN connections. Once the UE has been redirected to the GERAN / UTRAN, the MME releases the LIPA PDN connections. In another embodiment, following triggering of delivery, the MME starts a timer T_O. The MME releases the LIPA PDN connections when the T_O timer expires and the UE has not performed the CSFB procedures to return to the E_UTRAN.
Embodiments: a CSFB that has no PS HO for GERAN without any DTM target cells, and so the UE picks up PS traffic on E-UTRAN. According to selected embodiments, additional solutions are provided to tackle the case of CSFB without any PS HO, and in which the UE picks up the PS traffic in the HeNB, and which address the hysteresis with delayed disconnection of the LIPA connections. . In this network-based solution, the MME disconnects the PDN connections from LIPA after the CS service has terminated, only if the UE returns to the E-UTRAN, a target macrocell or a different HeNB for which it LIPA PDN continuity will not be supported. In these embodiments, there is no DTM target cell and the UE picks up the PS traffic on the E-UTRAN.
ES 2 631 817 T3
In a first embodiment, the solution is applied to a UE that carries out CSFB procedures and moves to a GERAN network or target cell that does not support dual transfer mode (DTM - "dual transfer mode" -), or to a UE that does not support DTM. In this case, the MME disconnects the LIPA PDN connections only if the UE performs the CSFB procedures to return to the E-UTRAN and returns to an E-UTRAN cell that is not a CSG cell, or to a E-UTRAN CSG cell for which LIPA PdN continuity is not supported (such as an E-UTRAN CSG cell with a different CSG ID than the CSG cell in which the connections were created LIPA PDN). In this solution, as a consequence of the triggering, by the UE, of the CSFB procedures, and that the PS delivery is not supported, or that the target network or the target cell is a network or cell If the GERAN does not support DTM, or the UE does not support DTM, the MME stores the CSG ID of the UTRAN cell in which the UE triggers the CSFB procedure. The MME retains such information until the UE returns to E-UTRAN or until the UE retrieves the PS bearers in GERAN / UTRAN.
On the other hand, if the UE sends a NAS handshake with the MME in order to resume service in EUTRAN according to the ongoing CSFB procedures, then the MME checks if the UE is resuming services from the cell. with the same CSG ID as the stored MME when the UE executes the alternate option procedure. If services are being resumed from a cell with a different CSG ID, or services are being resumed from a non-CSG cell or from a cell without a CSG ID, then the MME disconnects the LIPA PDN connections. Otherwise, the MME does nothing.
In another embodiment, the MME starts a timer T when the UE suspends the bearer during the alternate option procedure. Following the expiration of the timer, if the UE has not carried out the CSFB procedures to return to E-UTRAN or the PS bearers are still suspended, then the MME disconnects the LIPA PDN connections.
In this solution, as a consequence of the triggering, by the UE, of the CSFB procedures, and that the PS delivery is not supported, or that the target network or the target cell is a network or cell If the GERAN does not support DTM, or the UE does not support DTM, the MME starts a timer T_P2 and the MME stores the CSG ID of the UTRAN cell in which the UE triggers the CSFB procedure. The MME retains the CSG ID information until the Ue returns to E-UTRAN or until the UE retakes the PS bearers in GERAN / UTRAN. Following the expiration of timer T_P2, if the UE has not carried out the CSFB procedures to return to E-UTRAN, or if the PS bearers are still suspended, then the MME disconnects the LIPA PDN connections. In addition, if the UE sends a NAS handshake with the MME in order to resume service in E-UTRAN according to the ongoing CSFB procedures, before the timer T_P2 expires, then the MME resets the timer and the MME checks if the UE is resuming services from a cell with the same CSG ID as the stored MME by executing the alternate option procedure by the UE. If services have been resumed from a cell with a different CSG ID, or if services have been resumed from a non-CSG cell or from a cell without a CSG ID, then the MME disconnects the PDN connections from LIPA. Otherwise, the MME does nothing.
Embodiments: CSFB without any PS HO, and so that the UE resumes PS traffic in GERAN / UTRAN. According to selected embodiments, additional solutions are provided to tackle the case of deliveries to GERAN / UTRAN triggered by an alternative option of CS without PS HO, such that the UE resumes PS traffic in GERAN / UTRAN. In this solution, the UE performs a NAS to GERAN / UTRAN handshake to regain suspended PS bearers.
In operation, the MME responds to the CONTEXT REQUEST message from the new SGSN, sending a CONTEXT RESPONSE message. When the MME sends the CONTEXT RESPONSE to the target SGSN, the MME omits the information regarding the LIPA PDN connection (s), such that the target SGSN does not create a PDP context for the connection corresponding LIPA PDN. However, the solution is triggered by the UE when it conducts a NAS signal exchange through GERAN / UTRAN to regain suspended PS bearers.
Achievements: Delivery to GERAN / UTRAN triggered by an alternative CS option. According to selected embodiments, additional solutions are described with reference to Figure 12, in which the case of deliveries to GERAN / UTRAN triggered by an alternative CS option is undertaken, when there is no PS HO and there is a call terminated by mobile. In operation, a UE 2102 having only active LIPA pDn connections triggers the PS HO to GERAN / UTRAN during the CSFB procedure. In response to this, MME 2018 decides that no HO PS should be performed for PS bearers, based on the fact that the target cell is GERAN / UTRAN and the UE has only LIPA PDN connections. Once the UE 2102 has been redirected to GERAN / UTRaN, the MME 2108 retains the UE context information until the UE performs a RAU.
As described below, a second exemplary embodiment differs from the first with respect to when the MME has initiated the cell re-selection procedure. The second exemplary embodiment further covers the general case of a handover between RATs.
ES 2 631 817 T3
In a selected embodiment, the UE 2102 has only LIPA PDN connections. When the HO from HeNB 2104 to GERAN / UTRAN is triggered due to the CSFB, the Initial UE Context Set Request from MME 2108 to HeNB 2104 indicates that the HO PS is not available. The HeNB 2104 informs the UE 2102 to move into a GERAN / UTRAN cell, either by using a Network Assisted Cell Swap, or by triggering a handshake connection release from RRC with redirection to GERAN / UTRAN.
In signal flow 21-1, MME 2108 receives a Remote Alert Request message (IMSI, VLR TMSI, location information) from MSC 2112, through an interface of SGs. The MME 2108 then remotely alerts the UE on all TAs.
In signal flow 21-2, the MME 2108 sends a Remote Alert message to each eNodeB. The Remote Alert message includes an appropriate UE identity (i.e., S-TMSI or IMSI), as well as a CN domain indicator indicating which domain (CS or PS) initiated the alert message to distance. In this case, it will be set to "Cs" by the MME.
In signal flow 21-3, the radio resource part of the remote paging procedure occurs, whereby the eNodeB 2104 sends the remote paging message to the UE 2102. The message contains a suitable UE identity ( that is, from S-TMSI or from IMSI) and a CN domain indicator.
In signal flow 21-4, the UE 2102 establishes an RRC connection and sends an extended CS request (CS alternative option indicator) to the MME 2108. The UE 2102 indicates its S-TMSI in the signal exchange of RRC. The Extended Service Request message is encapsulated in RRC and S1-AP messages. The CS alternative option indicator indicates to the MME that the CS alternative option is to be carried out for this UE. In the case of Mobile Originated CSFB (MO - “Mobile Originated” -), the signal flow 21-1 to 21-3 is not carried out.
In signal flow 21-5, the MME 2108 sends the SGs Service Request message to the MSC 2112, which contains an indication that the UE 2102 was in free mode (and consequently, for example, that the UE has not received any calling line identification information). Receipt of the SGs Service Request message prevents the MSC 2112 from retransmitting the SGs interface remote Announcement message.
In signal flow 21-6, MME 2108 sends S1-AP: Initial UE context set (UE capabilities, CS alternate option indicator and other parameters), in order to notify cNodeB to move UE 2102 to UTRAN / GERAN. MME 2108 determines that the HO PS cannot be performed based on the fact that the UE has only LIPA PDN connections and LIPA continuity of service is not supported, and indicates in this message that the PS HO is not available for UE 2102. The eNB will respond with an S1-AP message: Response to initial UE context establishment (not shown). Since the HeNB 2104 determines that the HO PS is not available, the HeNB 2104 performs a signal flow 21-7a or 21-7b, instead of sending a HO REQUIRED message to the MME 2108.
In signal flow 21-7a, if the target cell is from GERAN, the HeNB 2104 can trigger a cell change order between RATs (optionally, with Network Assisted Cell Change (NACC) ”-) to a neighboring GERAN cell, by sending an RRC message to UE 2102. The cell change command between RATs may contain a CS alternative option flag indicating to UE 2102 that the cell change command has been triggered as a result of a CS alternative option request.
In signal flow 21-7b, HeNB 2104 can trigger an RRC connection release with redirection to GERAN or UTRAN, rather than PS HO or NACC. In case UE 2102 and network support "RRC connection release with redirection and multi-cell system information to GERAN / UTRAN", HeNB 2104 can trigger RRC connection release with redirection to GERAN / UTRAN, and includes one or more physical cell identities and their associated system information.
In signal flow 21-8, the UE establishes the RRC connection and then performs the remainder of the procedure for the CSFB, which may include a RAU. As it is possible for the target SGSN 2110 to send a CONTEXT REQUEST message to the source MME 2108 as part of a RAU procedure, the 2108 MME does not release the context information from the UE 2102 until it receives the REQUEST FOR message. CONTEXT. Upon receiving the CONTEXT REQUEST message, the MME 2108 returns a CONTEXT RESPONSE with zero active PDN connections and implicitly unhooks the UE 2102 from the network.
According to selected embodiments, additional solutions are described with reference to Figure 13, for the case that the UE 2202 has only LIPA / SIPTO PDN connections. In this procedure, signal flows 22-1 through 22-6 of Figure 13 are similar to signal flows 21-1 through 21-6 of Figure 12. However, instead of receiving the information that the HO PS is not available for the UE in the initial Set UE Context message, this information (that the HO PS is not available for the UE) is supplied to the HeNB 2204 in the HO PREPARATION FAIL message (on signal flow 22-8) after sending the HO REQUIRED message to MME 2208 (on signal flow 22-7). The cause value of the HO PREPARE FAILURE message will be “PS HO not available”. While this solution may include one or more rounds of
ES 2 631 817 T3 greetings in the messages, this solution can be reused for the case of HO of IRAT as a consequence of the mobility of the UE.
According to selected embodiments, further solutions are described for the case of a UE / mobile home CSFB call procedure or UE / mobile termination call procedure, when the HO PS is not supported and in the case that the UE has only LIPA PDN connections. This procedure is illustrated with reference to the signal flow for a CS call request in E-UTRAN or a call in GERAN / UTRAN, without the HO PS represented in Figure 6.3-1 of 3GPP TS 23.272. According to this solution, the UE receives as signal 3b an RRC connection release from the eNodeB with redirection to GERAN or UTRAN, if the HeNB determines that the UE only has LIPA PDN connections, based on the existence of an Identifier Correlation (ID). In this solution, if the LIPA peer PDN connection is established, the control message signal 1b S1 coming from the MME and directed to the HeNB, includes a correlation ID for each EPS bearer, in order to enable the direct path in the user plane between HeNB and L-GW. In Release 10 of the 3GPP specification, the correlation ID is set equal to the TEID (GTP-based S5) or GRE (PMIP-based S5) key of PDN GW. Thus, the detection, by the HeNB, of the correlation ID in the S1 control message from the MME, indicates that the corresponding EPS carrier is for LIPA.
PDN address
The purpose of the PDN address information element is to assign an IPv4 address to the UE associated with a packet data network and to provide the UE with an interface identifier intended to be used to construct the IPv6 link-local address. The PDF address information element is encoded as shown in Tables 1 and 2 below.
Table 1: PDN address information element
7 6 5 4 3 2 1
<td colspan="2">PDN address IEI</td><td>octet 1</td>
<td colspan="2">PDN address content length</td><td>octet 2</td>
<td> 0 0 0</td><td>Sign of continuity of <sup>Value of you</sup>p<sup>or from PDN</sup></td><td>octet 3</td>
<td>reservation</td><td>service</td><td></td>
<td></td><td></td><td>octet 4</td>
<td colspan="2">PDN address information</td><td></td>
<td></td><td></td><td>octet 5</td>
As shown above in Table 1, the PDN address is a type 4 information element with a minimum length of 7 octets and a maximum length of 15 octets.
Table 2: PDN address information element
<td colspan="5">PDN type value (octet 3)</td>
<td colspan="5">Bits</td>
<td> 3</td><td> 2</td><td> 1</td><td></td><td></td>
<td> 0</td><td> 0</td><td> 1</td><td></td><td>IPv4</td>
<td> 0</td><td> 1</td><td> 0</td><td></td><td>IPv6</td>
<td> 0</td><td> 1</td><td> 1</td><td></td><td>IPv4v6</td>
<td colspan="5"></td>
<td colspan="5">All other values are reserved.</td>
<td colspan="5"></td>
<td colspan="5">Bits 4 to 8 of octet 3 are spare and must be encoded as zero.</td>
<td colspan="5"></td>
<td colspan="5"></td>
<td colspan="5">PDN address information (octets 4 to 15)</td>
<td colspan="5"></td>
ES 2 631 817 T3
PDN type value (octet 3)
If the PDN type value indicates IPv4, the PDN address information contained in octet 4 through octet 7 contains an IPv4 address. Bit 8 of octet 4 represents the most significant bit of the IPv4 address, and bit 1 of octet 7 represents the least significant bit.
If the PDN type value indicates IPv6, the PDN address information contained in octet 4 through octet 11 contains an IPv6 interface identifier. Bit 8 of octet 4 represents the most significant bit of the IPv6 interface identifier, and bit 1 of octet 11 the least significant bit.
If the PDN type value indicates IPv4v6, the PDN address information contained in octet 4 through octet 15 contains an IPv6 interface identifier and an IPv4 address. Bit 8 of octet 4 represents the most significant bit of the IPv6 interface identifier, and bit 1 of octet 11 the least significant bit. Bit 8 of octet 12 represents the most significant bit of the IPv4 address, and bit 1 of octet 15 represents the least significant bit.
If the PDN type value indicates IPv4 or IPv4v6, and DHCPv4 is to be used to assign the IPv4 address, the IPv4 address should be encoded as 0.0.0.0.
Referring now to Figure 14, there is shown a schematic block diagram illustrating exemplary components of a wireless and mobile communication device 101 that may be used with selected embodiments of the present invention. Wireless device 101 has been shown with specific components to implement features described above. It is to be understood that the wireless device 101 has been shown in very specific detail for exemplary purposes only.
A processing device (eg, a microprocessor 128) is schematically shown as being coupled between a keyboard 114 and a display device 127. The microprocessor 128 controls the operation of the display device 127, as well as the overall operation of the device. wireless 101, in response to actuation of keyboard keys 114 by a user.
Wireless device 101 has a housing that can be vertically elongated, or it can take other sizes and shapes (including clamshell housing structures). The keyboard 114 may include a mode select key or other hardware or software for switching between text input and telephony input.
In addition to the microprocessor 128, other parts of the wireless device 101 are schematically shown. These include a communications subsystem 171, a short-range communications subsystem 102, keyboard 114, and display device 127, along with other input / output devices including a set of LEDs 104, a set of E devices. / S (input / output - “Input / Output” -) 106, a serial port 108, a speaker 111 and a microphone 112, as well as memory devices, including a flash-type memory 116 and a Random Access Memory (RAM - "Random Access Memory" -) 108, as well as various other device subsystems 122. The wireless device 101 may have a battery 121 to power the active elements. of the wireless device 101. The wireless device 101 is, in some embodiments, a two-way radio frequency (RF) communication device that has voice and data communication capabilities. In addition, the wireless device 101 in some embodiments has the ability to communicate with other computer systems over the internet.
The operating system software executed by microprocessor 128 is, in some embodiments, stored on a permanent storage device, such as flash memory 116, although it may be stored on other types of memory devices, such as memory stick. read only (ROM - “read only memory” -) or a similar storage element. In addition, system software, device-specific applications, or parts thereof, can be temporarily loaded into a volatile storage device, such as RAM 118. The communication signals received by wireless device 101 can also be stored in RAM 118.
The microprocessor 128, in addition to its operating system functions, makes it possible to run software applications on the wireless device 101. A predetermined set of software applications that control the basic operations of the device, such as a voice communications module 131A and a data communications module 131B, can be installed in the wireless device 101 during manufacture. Furthermore, a personal information manager application module (PIM - "Personal Information Manager") 131C may also be installed in the wireless device 101 during manufacture. The PIM application is, in some embodiments, capable of organizing and managing data items, such as email, calendar events, voice messages, appointments, and to-do items. The PIM application is also, in some embodiments, capable of sending and receiving data items over a wireless network 113. In some
ES 2 631 817 T3 embodiments, the data elements managed by the PIM applications are integrated, synchronized and updated seamlessly, through the wireless network 113, in such a way that the data elements corresponding to the user of the device are stored in , or associated with, a main computer system. Additional software modules, illustrated as another 131N software module, can also be installed during manufacturing.
Communication functions, including data and voice communications, are carried out through communication subsystem 171 and possibly through short-range communication subsystem 102. Communication subsystem 171 includes a receiver 151, a transmitter 152 and one or more antennas, illustrated as a receive antenna 154 and a transmit antenna 156. Furthermore, the communication subsystem 171 includes a processing module, such as a digital signal processor (DSP - "digital signal processor" -) 158, and local oscillators (LOs - "local oscillators" -) 161. In some embodiments, the communication subsystem 171 includes a separate antenna arrangement (similar to antennas 154 and 156) and an RF processing chip / block (similar to Receiver 151, LOs 161, and Transmitter 152) for each RAT, although it is possible to use a common baseband signal processor (similar to DSP 158) for baseband processing for multiple RATs. The specific design and implementation of the communication subsystem 171 depends on the communication network in which the wireless device 101 is intended to operate. For example, the communication subsystem 171 of the wireless device 101 may have been designed to work with the Mobitex ™, DataTAC ™, or General Packet Radio Service (GPRS) mobile data communication networks, and has also been designed to work with any of a variety of voice communication networks, such as the Advanced Mobile Phone Service (AMPS - “Advanced Mobile Phone Service” -), Time Division Multiple Access (TDMA - "Time Division Multiple Access" -), Code Division Multiple Access (CDMA "Code Division Multiple Access" -), Personal Communications Service (pCs - "Personal Communications Service" -) , Global System for Mobile Communications (GSM - “Global System for Mobile communications” -), etc. Examples of CDMA include 1X and 1x EV-DO. The communication subsystem 171 may also have been designed to work with an 802.11 Wi-Fi network with an 802.16 WiMAX network, or with both. Other types of voice and data networks, both standalone and integrated, can also be used with the wireless device 101.
Network access may vary depending on the type of communication system. For example, on the Mobitex ™ and DataTAC ™ networks, wireless devices register on the network using a unique Personal Identification Number (PIN) associated with each device. In GPRS networks, however, network access is usually associated with a subscriber or user of a device. A GPRS device therefore usually has a subscriber identity module, commonly referred to as a Subscriber Identity Card (SIM - "Subscriber Identity Card" -) card, in order to work on a GPRS network.
Upon completion of the network registration or activation procedures, the wireless device 101 can send and receive communication signals over the communication network 113. The signals received from the communication network 113 by the reception antenna 154 are routed to the receiver 151, which provides the amplification of the signals, their downconversion of the frequency, their filtering, channel selection, etc. and it can also provide its analog to digital conversion. The analog-to-digital conversion of the received signal allows the DSP 158 to perform more complex communication functions, such as demodulation and decoding. In a similar manner, the signals to be transmitted to network 113 are processed (for example, modulated and encoded) by DSP 158 and are then provided to transmitter 152 for conversion from digital to analog, conversion in the sense frequency, its filtering, its amplification and its transmission to the communication network (or networks) 113 by means of the transmission antenna 156.
In addition to processing communication signals, DSP 158 makes it possible to control receiver 151 and transmitter 152. For example, the gains that are applied to communication signals at receiver 151 and transmitter 152 can be adaptively controlled to through automatic gain control algorithms implemented in the DSP 158.
In a data communication mode, a received signal, a received signal, such as a text message or a web page download, is processed by communication subsystem 171 and supplied as input to microprocessor 128. The received signal is then further processed by the microprocessor 128 in order to be output to the display device 127 or, alternatively, to various other auxiliary I / O devices 106. A user of the device can also compose data items, such as email messages, using keyboard 114 and / or some other auxiliary I / O device 106, such as a touch pad, a rocker switch, a jog wheel, or some other. other type of input device. The composite data elements can then be transmitted over the communication network 113, through the communication subsystem 171.
In a voice communication mode, the overall operation of the device is substantially similar to the data communication mode, except that the received signals are output to a speaker 111, and the signals for transmission are generated by a microphone. 112. Alternative voice or audio I / O subsystems, such as a voice message recording subsystem, may also be implemented in the wireless device 101. In addition, the display device 127 may also be used in the mode.
Voice communication ES 2 631 817 T3, for example, to display the identity of the calling party, the duration of a voice call, or other voice-related information.
The short-range communications subsystem 102 enables communication between the wireless device 101 and other nearby systems or devices, which need not be similar services. For example, the short-range communications subsystem may include an infrared device and its associated circuitry and components, or a Bluetooth ™ communication module, to enable communication with similarly enabled systems and devices.
It will be understood that, as used herein, terms and expressions such as "coupled", "connected", "electrically connected", "in signal communication" and the like may include direct connections between components, indirect connections between components, or both, as will be apparent in the overall context of a particular embodiment. The term "coupled" is intended to include, but is not limited to, a direct connection.
Although the exemplary embodiments described and disclosed herein have been described with reference to selected communication systems, the present invention is not necessarily limited to embodiments provided by way of example and illustrating inventive aspects of the present invention that are applicable to a wide variety of provisions for network connection capacity. Thus, the particular embodiments disclosed above are only illustrative and should not be taken as limitations on the present invention, insofar as the invention can be modified and practiced in different, but equivalent, ways that are obvious to people. skilled in the art and who have the benefit of the teachings herein. Accordingly, the foregoing description is not intended to limit the invention to the particular form set forth, but, on the contrary, is intended to cover such alternatives, modifications, and equivalents insofar as they may be included within the scope of the invention, as defined by the accompanying claims, such that those skilled in the art will understand that various changes may be made, substitutions and alterations without departing from the scope of the invention, in its broadest form.
• Change in an implementation for 3GPP TS 23.272 ========================= Start of change ========== ====================================
3.1 Definitions
For the purposes of this document, the terms and definitions given in TR 21.905 [1] apply. A term defined herein takes precedence over the definition of the same term, if any, in TR 21.905 [1].
1xCS: The Switched Signal Exchange System on 3GPP2 Legacy Circuits as defined in 3GPP2 X.S0042-0 [22].
CSMT: A flag in an LA update request message that is used in an alternative CS option for MT call, in order to avoid loss of remote alert on a roaming retry.
For the purposes of this document, the following terms and definitions given in 3GPP TR 23.829 [xx] apply:
Local IP Access
LIPA Service Continuity ========================== End of change ================ ================================================== =========== Start of change =================================== ==========
6.3 Mobile origin call in active mode - PS HO is not supported
This procedure runs when PS HO is not supported, in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
ES 2 631 817 T3
<td>EU / MS</td><td></td><td>eNodeB</td><td></td><td>BSS / RNS</td><td></td><td>MME</td><td></td><td>MSC</td><td></td>
1st. NAS Extended Service Request
SGW / PG 'wj
SGSN
-1 B. S1-AP UE Context Modification Request with CS Alternate Option Indicator
K-1-1 I
1 C. Message d | ¡reply from m <^ ¡fication of UE content from S1-AP
two. Request for optional measurement report
3b, 3c. RCC connection release
3rd. NACC,
Four. S1-AC: UE ile S1 context release request
5. UE context release from S1 i 6 UE changes RAT; then update LA or update RA / LA combined, c update RA or LAU and RALI
7a. Suspended see 23.060)
-M
<td></td><td></td><td></td>
<td>7b. I suspended</td><td>The request í res |</td><td>est</td>
3. Carrier update (s)
HH-> l
9. CM service request
9. A / lu-cs message (with CM service request)
10. Refusal of service
If the MSC is changed
10b. Location area update
<td></td><td colspan="2"> 1</td><td></td><td></td><td></td>
<td></td><td>10c. Call d</td><td>ϊ MO from CS</td><td></td><td></td><td rowspan="2">tinada</td>
<td></td><td>11. Update c Γ --------</td><td>e area of carriage Γ -------</td><td>Action or act llz: Γ ---------</td><td>tion of RA / LA I ate Γ --------_ |</td>
Figure 6.3-1: CS call request on E-UTRAN, call on GERAN / UTRAN without PS HO la. The UE sends an Extended Service Request (CS Alternate Option Indicator) to the MME. The Extended Service Request message is encapsulated in RRC and S1-AP messages. The CS Alternate Option Indicator Instructs the MME to carry out the CS Alternate Option. The UE only transmits this request if it is locked to the CS domain (with a combined EPS / IMSI lock) and cannot deny an IMS voice session (because, for example, the UE is not registered with IMS or IMS voice services are not supported by IP-CAN, home PLMN, or serving UE).
lb. The MME sends an S1-AP UE Context Modification Request message to the eNB, which includes a CS Alternate Option Flag. This message indicates to the eNB that the UE is to be moved to
GERAN / UTRAN. The CS Alternate Option Indicator value is set to "CS Alternate Option without PS HO Required" if the MME realizes that the PS HO results in the MME disengaging the UE from the network because the UE context information held by the MME is regarding LIPA PDN connections and LIPA continuity of service is not supported.
1 C. The eNB will respond with an S1-AP UE Context Modification Response message. IF the eNB has received a UE Context Modification Request Message from S1-AP that has “CS Alternate Option without PS HO Required” as the CS Alternate Option Indicator value, the eNB shall not attempt to isolate a PS HO by sending a Delivery Required message to the MME.
two. The eNodeB can optionally request a Measurement Report from the UE to determine the cell of
GERAN / UTRAN target for which the redirection procedure to it will be carried out.
ES 2 631 817 T3
The network carries out one of stages 3a, 3b and 3c.
3rd. If the UE and the network support a cell change order between RATs addressed to GERAN and the target cell is from GERAN:
The eNodeB can trigger a cell change command between RATs (optionally, with NACC) to a neighboring GERAN cell by sending an RRC message to the UE. The cell change order between RATs may contain a CS alternative option indicator that indicates to the UE that the cell change order is triggered as a consequence of a CS alternative option request. If the cell change command between RATs contains a CS alternative option indicator and the UE fails to establish a connection with the target RAT, then the UE considers that the CS alternative option has failed. The service request procedure is considered to be completed successfully when the cell change order procedure is completed successfully.
3b. If the UE or the network does not support the delivery of PS between RATs from E-UTRAN to GERAN / UTRAN or the order of cell change between RATs to GERAN, or the network does not want to make use of these procedures:
The eNodeB can trigger RRC connection release with redirection to GERAN or UTRAN.
3c. If the UE and the network support "RRC connection release with redirection and multi-cell system information to GERAN / UTRAN":
The eNodeB may trigger RRC connection release with redirection to GERAN / UTRAN and include one or more physical cell identities and their associated system information.
NOTE 1: The service request procedure supervision timer needs to be long enough, taking into account the optional measurement reported in step 2.
Four. The eNodeB sends a UE Context Release Request message from S1-AP to the MME. If the target cell is from GERAN and either the target cell or the UE does not support DTM, the message includes an indication that the UE is not available for PS service.
5. The MME releases the UE context contained in the eNodeB as well as all the information related to the eNodeB contained in the S-GW, as specified in TS 23.401 [2].
In the event that the clause indicates that an RRC has been released as a consequence of abnormal conditions, for example due to a radio link failure, the MME suspends the EPS bearers (step 8).
The UE performs one of steps 6a, 6b, and 6c, and THEN performs step 6d.
6th. (Stage 6a is carried out in case stage 3a, Order to change cell to GERAN, has been carried out).
The UE moves to the new cell in GERAN. The UE uses the NACC information and / or receives the information from the broadcasting system and, when it has all the necessary information to access the GERAN cell, establishes a radio signal exchange connection.
6b. (Step 6b is carried out in the case that step 3b, release of RRC with reconduction, has been carried out).
The UE moves to the target RAT, identifies a suitable cell, preferably from the same PLMN, as received in the LAI IE of the combined EPS / IMSI Latch / TAU Accept message, receives the information from the broadcast system and, when it has the necessary information to access GERAN / UTRAN, it establishes a radio signal exchange connection.
6c. (Step 6c is carried out in the case that step 3c, RRC connection release with redirection and multi-cell system information, has been carried out).
The UE moves to the target RAT and identifies a suitable cell, preferably from the same PLMN as the one received in the LAI IE of the combined EPS / IMSI Latch / TAU Accept message. The Ue uses the NACC information and / or receives the information from the broadcasting system, and, when it has all the information necessary for access to GERAN / UTRAN, the UE establishes the radio signal exchange connection.
6d. When the UE arrives at the target cell, if the target RAT is from UTRAN: The UE establishes the radio handshake connection by sending an RRC Initial Direct Transfer message as specified in TS 25.331 [ 7], which contains a NAS message. The CN domain indicator is set to "CS" in the initial Direct Transfer message.
ES 2 631 817 T3
If the target RAT is in GERAN A / Gb mode: The UE establishes a radio handshake connection using procedures specified in TS 44.018 [4] (that is, the UE requests, and is assigns it a dedicated channel through which it sends a SABM containing a NAS message addressed to the BSS, and the BSS responds by sending a UA). Upon receipt of the SABM (containing the NAS message), the BSS sends a LAYER 3 FULL INFORMATION message (containing the NAS message) to the MSC, indicating that CS resources have been allocated in the GERAN cell . After the establishment of the main handshake link as described in TS 44.018 [4], the UE enters the Dual Transfer Mode or the Dedicated Mode.
If the LA of the new cell is different from the one stored in the UE, the UE will initiate a location area update or a combined RA / LA update procedure, as specified in TS 23.060 [3] for the different network operating modes (NMO - "Network Modes of Operation" -). The UE shall set the "continue request" flag in the LAU request in order to indicate to the MSC not to release the Iu / A connection once the LAU procedure has been completed. Additionally, the UE performs any routing area update procedure as specified by TS 23.060 [3].
In NMO I, a CSFB UE may carry out LAU procedures with the "continuation request" flag and separate RAUs, instead of a combined RA / LA update procedure, in order to speed up the CSFB procedure .
7. If the target RAT is from GERAN and DTM is not supported, the UE initiates the suspended procedure specified in TS 23.060 [3], clause 16.2.1.1.2. This triggers the SGSN to send a Hold Request message to the MME. The MME returns a Fail Response to the SGSN, even though the GUTI of the P-TMSI and RAI pair cannot be deduced.
8. If the UE Context Release Request message from S1-AP, received from the eNodeB in step 4, indicates that the UE is not available for PS service in the target cell, then the MME initiates preservation and the suspension of non-GBR carriers, as well as the deactivation of GBR carriers, towards the S-GW and the P-GW (s). The MME stores in the UE context that the UE is in a suspended status.
NOTE 2: Stage 8 cannot be triggered by the suspend procedure since the full GUTI cannot be derived from the P-TMSI and RAI included in the suspend request message.
9. The UE continues with the MO call setup procedure, sending a CM service request.
10a. If the UE is not registered with the MSC serving the 2G / 3G cell, or the UE is not allowed in the LA, the MSC will reject the service request if an implicit location update is not performed.
10b. A UE that detects that the MSC has rejected the service request will perform a location area update or a combined RA / LA procedure, according to existing GERAN or UTRAN procedures, as specified in TS 23.060 [3] for the different Network Operation Modes (NMO).
10c. The UE initiates the CS call establishment procedure.
eleven. Once the CS voice call has been terminated, and if the UE is in GERAN and PS services are suspended, then the UE will resume PS services as specified in TS 23.060 [3]. A Gn / Gp -SGsN will follow TS 23.060 [3] to resume the PDP context (s). An SGSN of S4 will follow TS 23.060 [3] to retake bearers, and informs the S-GW and P-GW (s) that it is resuming suspended bearers. If the UE has returned to E-UTRAN after it has terminated the CS voice call, then the UE should resume PS service by sending a TAU to the MME. The MME will also inform the S-GW and the P-GW (s) that it is resuming the suspended carriers. The resumption of the suspended carriers in the S-GW and in the P-GW must be done by means of an implicit resumption, using the Bearer Modification request message, if this is triggered by the operating procedure, for example, RAU, TAU or service request. The S-GW is aware of the suspended status of the bearers and will forward the Bearer Modification request to the P-GW. An explicit restart should be used using the Restart Notification message, in cases where the Bearer Modification request is not triggered by the operating procedure.
If the UE remains in the UTRAN / GERAN after the CS voice call is terminated, the UE performs normal mobility management procedures as defined in TS 23.060 [3] and TS 24.008 [twenty-one].
========================== End of change ==================== ================================================= ====== Start of change ========================================= =====
ES 2 631 817 T3
7.4 Mobile Termination Call in Active Mode - PS HO Not Supported
This procedure is carried out when PS HO is not supported, in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
<td>EU / MS</td><td></td><td>eNodeB</td><td></td><td>BSS / RNS</td><td></td><td>MME</td><td></td><td>MSC</td><td></td><td>S-GW / PGW</td><td></td><td>SGSN</td>
1A. REQUEST FOR j * 1 A. REMOTE REQUEST
T-11b. NAS extended service request to you. Rejection of av ^ or at a distance from Cí
d. S1-AP UE Context Modification Request with CS Alternative Option Indicator «-1-1<sup>K r</sup>
1e. S1-AP UE context change response message
two. Optional measurement report
3rd. CCO / NACC, 3b, 3c. Signal Exchange Connection Ljberation
Four. S1-AP: EU CONTEXT RELEASE REQUEST FROM S1
5. RELEASE OF CONTEXT
-t.
PE UE DE S1
S. The UE changes RAT. antonces UPDATE OF LAU OR UPDATE OF RA / LA COMBINADA, OR UPDATE OF OR LAU AND RAU
7A. Suspended (see TS 23.060)
7b.
Suspend ^ request I answers:
8. Update carrier (s)
9. Distance warning response
9a. Establish CS connection
9B. Signal exchange connection release 9b .. CONNECTION REJECT .9C. Location area update or combined RA / LA update
SISE CHANGES LAMSC
Figure 7.4-1: CS remote announcement in E-UTRAN, call in GERAN / UTRAN without PS HO
1st. The MSC receives an incoming voice call and responds by sending a Remote Announcement request (IMSI or TMSI, optional caller line connection and identification management information information) to the MME through an interface of SGs. The MSC only sends a CS Remote Announcement for a UE, which provides location update information using the SGs interface. In active mode, the MME has an established S1 connection and if the MME has not returned the "SMS only" indication to the UE during the combined TA / LA latch or update procedures, the MME reuses the existing connection to forward the CS service notification to the UE.
In case the MME has returned the 'SMS only' indication to the UE during the combined TA / LA latch or update procedures, the MME will not send the CS Remote Alert to the UE, and sends an Advisory Rejection CS remote to MSC in order to stop the CS remote alert procedure, so this CSFB procedure is stopped.
The eNB forwards the warning message remotely to the UE. The message contains a CN domain indicator and, if received from the MSC, a Calling Line Identification.
The MME immediately sends the SGs Service Request message to the MSC, which contains an indication that the UE was in connected mode. The MSC uses this connected mode indication to start the call forwarding timer on no answer, for that UE, and the MSC shall send a user indication alerting the calling party. Receipt of the Service Request message from SGs stops the retransmission, by the MSC, of the SGs interface remote Announcement message.
NOTE 1: The previously configured policy can be used by the UE in order to avoid being disturbed
ES 2 631 817 T3 without line display of caller line identification, and detailed handling has to be decided by CT WG1 and CT WG6.
NOTE 2: This procedure can also take place immediately after the MSC receives the PRN_MAP from the HSS, in case the preliminary remote warning has been displayed. Caller's line identification is also provided in the case of preliminary remote announcement.
lb. The UE sends an Extended Service Request message m (CS alternate option indicator, reject or accept) to the MME. The Extended Service Request message is encapsulated in RRC and S1AP messages. The CS alternative option indicator indicates to the MME to carry out a CS alternative option. The UE may decide to reject the CSFB based on the caller's line identification.
lc. Upon receiving the extended service request (CSFB, reject), the MME sends a remote alert rejection towards the MSC in order to stop the CS remote alert procedure, and this CSFB procedure is stopped.
ld. The MME sends a UE Context Modification Request message from S1-AP to the eNodeB, which includes a CS alternative option indicator. This message indicates to the eNB that the UE is to move to UTRAN / GERAN. The value of the CS alternative option indicator is set to "CS alternative option without PS HO required" in case the MME finds that the PS HO has the result that the MME disengages the UE from the network due to because the UE context information kept by the MME is regarding LIPA PDN connections and LIPA continuity of service is not supported.
you. The eNB shall respond with an S1-AP Context Modification Response message. If the eNB has received a UE Context Modification Request message from S1-AP that has "CS Alternative Option No PS HO Required" as the CS Alternative Option Indicator value, the eNB will not attempt to initiate the PS HO by sending a Delivery Required message to the MME.
two. The eNodeB can optionally request a measurement report from the UE to determine the target GERAN / UTRAN cell towards which the redirection procedure will be carried out.
The network carries out one of stages 3a, 3b and 3c.
3rd. If the UE and the network support a cell change order between RATs addressed to GERAN and the target cell is from GeRAN:
The eNodeB can trigger a cell change command between RATs (optionally, with NACC) to a neighboring GERAN cell by sending an RRC message to the UE. The cell change order between RATs may contain an alternative option flag of Cs that indicates to the UE that the cell change order is triggered as a consequence of a CS alternative option request. If the cell change command between RATs contains a CS alternative option indicator and the UE fails to establish a connection with the target RAT, then the UE considers that the CS alternative option has failed. The service request procedure is considered to be completed successfully when the cell change order procedure is completed successfully.
3b. If the UE or the network does not support the delivery of PS between RATs from E-UTRAN to GERAN / UTRAN or the order of cell change between RATs to GERAN:
The eNodeB can trigger RRC connection release with redirection to GERAN or UTRAN, instead of PS HO or NACC.
3c. If the UE and the network support "RRC connection release with multi-cell system information and redirection to GERAN / uTrAN":
The eNodeB may trigger RRC connection release with redirection to GERAN / UTRAN and include one or more physical cell identities and their associated system information.
NOTE 3: The service request procedure supervision timer needs to be long enough, taking into account the optional measurement reported in step 2.
Four. The eNodeB sends a UE Context Release Request message from S1-AP to the MME. If the target cell is from GERAN and either the target cell or the UE does not support DTM, the message includes an indication that the UE is not available for PS service.
5. The MME releases the UE context contained in the eNodeB as well as all the information related to the eNodeB contained in the S-GW, as specified in TS 23.401 [2].
In the event that the clause indicates that an RRC has been released as a consequence of abnormal conditions, for example due to a radio link failure, the MME suspends the EPS bearers (step 8).
ES 2 631 817 T3
The UE performs one of steps 6a, 6b, and 6c, and THEN performs step 6d.
6th. (Stage 6a is carried out in case stage 3a, Order to change cell to GERAN, has been carried out).
The UE moves to the new cell in GERAN. The UE uses the NACC information and / or receives the information from the broadcasting system and, when it has all the necessary information to access the GERAN cell, establishes a radio signal exchange connection.
6b. (Step 6b is carried out in the case that step 3b, release of RRC with reconduction, has been carried out).
The UE moves to the target RAT, identifies a suitable cell, preferably from the same PLMN, as received in the LAI IE of the combined EPS / IMSI Latch / TAU Accept message, receives the information from the broadcast system and, when it has the necessary information to access GERAN / UTRAN, it establishes a radio signal exchange connection.
6c. (Step 6c is carried out in the case that step 3c, RRC connection release with redirection and multi-cell system information, has been carried out).
The UE moves to the target RAT and identifies a suitable cell, preferably from the same PLMN as the one received in the LAI IE of the combined EPS / IMSI Latch / TAU Accept message. The UE uses the NACC information and / or receives the information from the broadcasting system, and when it has the necessary information for access to GERAN / UTRAN, the UE establishes the radio signal exchange connection.
6d. If the LA of the new cell is different from the one stored in the UE, the UE will initiate a location area update or a combined RA / LA update, as specified in TS 23.060 [3] for the different modes network operation (NMO - "Network Modes of Operation" -). The UE shall establish the "CSMT" flag in the LAU request. The “CSMT” flag is used to prevent loss of an MT call in the event of a roaming retry. In NMO I, the UE in GERAN can perform an LA update on RR connection, instead of a combined RA / LA update on packet access, as defined in TS 24.008 [21], clause 4.7.5.2.5, unless setting Enhanced CS in DTM is supported. On the other hand, the Ue carries out any routing area update procedure as specified in TS 23.060 [3].
In NMO I, a CSFB UE may perform LAU (and if it does so, flag 'CSMT') and RAU procedures, instead of a combined RA / LA update procedure to speed up the CSFB procedure.
When the MSC receives an update request from LA, it shall check the pending terminating CS calls, and if the “CSMT” flag has been set, it maintains the CS handshake connection after the update procedure. location area, for pending termination CS calls.
7. If the target RAT is from GERAN and DTM is not supported, the UE initiates the suspended procedure specified in TS 23.060 [3], clause 16.2.1.1.2. This triggers the SGSN to send a Hold Request message to the MME. The MME returns a Fail Response to the SGSN, even though the GUTI of the P-TMSI and RAI pair cannot be deduced.
8. If the UE Context Release Request message from S1-AP, received from the eNodeB in step 4, indicates that the UE is not available for PS service in the target cell, then the MME initiates preservation and the suspension of non-GBR carriers, as well as the deactivation of GBR carriers, towards the S-GW and the P-GW (s). The MME stores in the UE context that the UE is in a suspended status.
NOTE 4: Step 8 cannot be triggered by the suspend procedure since the full GUTI cannot be derived from the P-TMSI and RAI included in the suspend request message.
9. If the UE does not initiate the LAU procedure, the UE responds to the remote alert by sending a Remote Alert Response message as specified in TS 44.018 [4] or TS 25.331 [7]. When received at the BBS / RNS, the remote alert response is forwarded to the MSC.
NOTE 6: The MSC has to be ready to receive a remote alert response after a relatively long time has elapsed from the time the CS remote alert request was sent (step 1a).
9a. In case the UE is registered in the MSC serving the 2G / 3G cell and the UE is allowed in the LA, the MSC will establish the CS call.
ES 2 631 817 T3
9b. If the UE is not registered with the MSC receiving the remote paging response, or the UE is not allowed in the LA, the MSC shall reject the remote paging response by clearing the A / Iu-cs connection. The BSS / RNS, in turn, releases the handshake connection for the CS domain.
9c. The release of the handshake connection will trigger the UE to obtain the LAI, causing the initiation of a location area update or a combined RA / LA procedure, as specified in TS 23.060 [ 3] for the different network operating modes (NMO).
The location area update triggers the roaming retry for the CS alternate option procedure, as defined in clause 7.5.
After carrying out the LAU procedure, the MSC will establish the CS call if the UE is allowed in the LA. With the exception of steps 1a and 1c above, a call forwarding is performed (see TS 23.082 [31] based on the exchange of signals according to TS 24.008 [21] received in the GERAN / UTRAN cell.
Once the CS voice call has been terminated, and if the UE is in GERAN and PS services are suspended, then the UE will resume PS services as specified in TS 23.060 [3]. A Gn / Gp -sGsN will follow TS 23.060 [10] to resume the PDp context (s). An SGSN of S4 will follow TS 23.060 [10] to regain bearers, and informs the S-GW and P-GW (s) that it is resuming suspended bearers. If the UE has returned to E-UTRAN after it has terminated the CS voice call, then the UE should resume PS service by sending a TAU to the MME. The MME will also inform the S-GW and the P-GW (s) that it is resuming the suspended carriers. The resumption of the suspended bearers in the S-GW and in the P-GW must be done by means of an implicit resumption, using the Bearer Modification request message, if this is triggered by the operating procedure, for example, RAU, TAU or service request . The S-GW is aware of the suspended status of the bearers and will forward the Bearer Modification request to the P-GW. An explicit restart should be used using the Restart Notification message, in cases where the Bearer Modification request is not triggered by the operating procedure.
If the UE remains in the UTRAN / GERAN after the CS voice call is terminated, the UE performs normal mobility management procedures as defined in TS 23.060 [3] and TS 24.008 [twenty-one].
========================== End of change ==================== ============================== • Change in an embodiment for 3GPP TS 36.417 ========= ================= Start of change ============================= ================
9.2.3.21 CS remote warning indicator
IE indicates that an alternative option towards the CS domain is necessary.
<td>IE / Group name</td><td>Presence</td><td>Interval</td><td>IE type and reference</td><td>Description semantics</td>
<td>CS remote warning indicator</td><td>M</td><td></td><td>LISTED (CS alternative option required, CS alternative option without require PS HO, ..., high priority to alternative option of CS)</td><td></td>
========================== End of change ==================== ============================== • Change in an embodiment for 3GPP TS 23.272 ========= ================= Start of change ============================= ================
6.3 Mobile origin call in active mode - PS HO is not supported
This procedure is carried out when PS HO is not supported, in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
ES 2 631 817 T3
<td>EU / MS</td><td></td><td>eNodeB</td><td></td><td>BSS / RNS</td><td></td><td>MME</td><td></td><td>MSC</td><td></td>
1st. ÑAS Extended Service Request
SGW / PG 'wj
SGSN
-1 B. S1-AP UE Context Modification Request with CS Alternate Option Indicator
K-1-1 I
1 C. Message d ^ reply from m <^ ification of content from UE from S1-AP
two. Request for optional measurement report
3b, 3c. RCC connection release
3rd. NACC,
Four. S1-AC: UE ile S1 context release request
5. UE context release from S1 i 6 UE changes RAT; then update LA or current ¡z;
RA / LA combined, c update RA or LAU and RALI
7a. Suspended see 23.060)
-M
<td></td><td></td><td></td>
<td>7b. I suspended</td><td>Ja request 1 res |</td><td>est</td>
3. Carrier update (s)
HH-> l
9. CM service request
9. A / lu-cs message (with CM service request)
10. Refusal of service
If the MSC is changed
10b. Location area update
<td></td><td colspan="2"> 1</td><td></td><td></td><td></td>
<td></td><td>10c. Call d</td><td>ϊ MO from CS</td><td></td><td></td><td rowspan="2">nail</td>
<td></td><td>11. Update c Γ --------</td><td>e area of carriage Γ -------</td><td>Nam slow or actualz; Γ ---------</td><td>tion of RA / LA I ate Γ --------_ |</td>
Figure 6.3-1: CS call request on E-UTRAN, call on GERAN / UTRAN without PS HO la. The UE sends an Extended Service Request (CS Alternate Option Indicator) to the MME. The Extended Service Request message is encapsulated in RRC and S1-AP messages. The CS Alternate Option Indicator Instructs the MME to carry out the CS Alternate Option. The UE only transmits this request if it is locked to the CS domain (with a combined EPS / IMSI lock) and cannot deny an IMS voice session (because, for example, the UE is not registered with IMS or IMS voice services are not supported by IP-CAN, home PLMN, or serving UE).
lb. The MME sends an S1-AP UE Context Modification Request message to the eNB, which includes a CS Alternate Option Flag. This message indicates to the eNB that the UE is to be moved to
GERAN / UTRAN.
lc. The eNB will respond with an S1-AP UE Context Modification Response message.
two. The eNodeB can optionally request a Measurement Report from the UE to determine the target GERAN / UTRAN cell for which the redirection procedure to it will be carried out.
The network carries out one of stages 3a, 3b and 3c.
3rd. IF the UE and the network support a cell change order between RATs addressed to GERAN and the target cell is from GERAN:
The eNodeB can trigger a cell change command between RATs (optionally, with NACC) to a neighboring GERAN cell by sending an RRC message to the UE. The cell change order between RATs may contain a CS alternative option indicator that indicates to the UE that the cell change order is
ES 2 631 817 T3 triggered as a result of a CS alternative option request. If the cell change command between RATs contains a CS alternative option indicator and the UE fails to establish a connection with the target RAT, then the UE considers that the CS alternative option has failed. The service request procedure is considered to be completed successfully when the cell change order procedure is completed successfully.
3b. If the UE or the network does not support the delivery of PS between RATs from E-UTRAN to GERAN / UTRAN or the order of cell change between RATs to GERAN, or the network does not want to make use of these procedures, or the HeNB determines that the UE only has LIPA PDN connections based on the existence of correlation TEIDs:
The eNodeB can trigger RRC connection release with redirection to GERAN or UTRAN.
3c. If the UE and the network support "RRC connection release with redirection and multi-cell system information to GERAN / UTRAN":
The eNodeB may trigger RRC connection release with redirection to GERAN / UTRAN and include one or more physical cell identities and their associated system information.
NOTE 1: The service request procedure supervision timer needs to be long enough, taking into account the optional measurement reported in step 2.
Four. The eNodeB sends a UE Context Release Request message from S1-AP to the MME. If the target cell is from GERAN and either the target cell or the UE does not support DTM, the message includes an indication that the UE is not available for PS service.
5. The MME releases the UE context contained in the eNodeB as well as all the information related to the eNodeB contained in the S-GW, as specified in TS 23.401 [2].
In the event that the clause indicates that an RRC has been released as a consequence of abnormal conditions, for example due to a radio link failure, the MME suspends the EPS bearers (step 8).
The UE performs one of steps 6a, 6b, and 6c, and THEN performs step 6d.
6th. (Stage 6a is carried out in case stage 3a, Order to change cell to GERAN, has been carried out).
The UE moves to the new cell in GERAN. The UE uses the NACC information and / or receives the information from the broadcasting system and, when it has all the necessary information to access the GERAN cell, establishes a radio signal exchange connection.
6b. (Step 6b is carried out in the case that step 3b, release of RRC with reconduction, has been carried out).
The UE moves to the target RAT, identifies a suitable cell, preferably from the same PLMN, as received in the LAI IE of the combined EPS / IMSI Latch / TAU Accept message, receives the information from the broadcast system and, when it has the necessary information to access GERAN / UTRAN, it establishes a radio signal exchange connection.
6c. (Step 6c is carried out in the case that step 3c, RRC connection release with redirection and multi-cell system information, has been carried out).
The UE moves to the target RAT and identifies a suitable cell, preferably from the same PLMN as the one received in the LAI IE of the combined EPS / IMSI Latch / TAU Accept message. The Ue uses the NACC information and / or receives the information from the broadcasting system, and, when it has all the information necessary for access to GERAN / UTRAN, the UE establishes the radio signal exchange connection.
6d. When the UE arrives at the target cell, if the target RAT is from UTRAN: The UE establishes the radio handshake connection by sending an RRC Initial Direct Transfer message as specified in TS 25.331 [ 7], which contains a NAS message. The CN domain indicator is set to "CS" in the initial Direct Transfer message.
If the target RAT is in GERAN A / Gb mode: The UE establishes a radio handshake connection using procedures specified in TS 44.018 [4] (that is, the UE requests, and is assigns it a dedicated channel through which it sends a SABM containing a NAS message addressed to the BSS, and the BSS responds by sending a UA). Upon receipt of the SABM (containing the NAS message), the BSS sends a LAYER 3 FULL INFORMATION message (containing the NAS message) to the MSC, indicating that CS resources have been allocated in the GERAN cell . After the establishment of the handshake link
ES 2 631 817 T3 main as described in TS 44.018 [4], the UE enters Double Transfer Mode or Dedicated Mode.
If the LA of the new cell is different from the one stored in the UE, the UE will initiate a location area update or a combined RA / LA update procedure, as specified in TS 23.060 [3] for the different network operating modes (NMO - "Network Modes of Operation" -). The UE shall set the "continue request" flag in the LAU request in order to indicate to the MSC not to release the Iu / A connection once the LAU procedure has been completed. Additionally, the UE performs any routing area update procedure as specified by TS 23.060 [3].
In NMO I, a CSFB UE may carry out LAU procedures with the "continuation request" flag and separate RAUs, instead of a combined RA / LA update procedure, in order to speed up the CSFB procedure .
7. If the target RAT is from GERAN and DTM is not supported, the UE initiates the suspended procedure specified in TS 23.060 [3], clause 16.2.1.1.2. This triggers the SGSN to send a Hold Request message to the MME. The MME returns a Fail Response to the SGSN, even though the GUTI of the P-TMSI and RAI pair cannot be deduced.
8. If the UE Context Release Request message from S1-AP, received from the eNodeB in step 4, indicates that the UE is not available for PS service in the target cell, then the MME initiates preservation and the suspension of non-GBR carriers, as well as the deactivation of GBR carriers, towards the S-GW and the P-GW (s). The MME stores in the UE context that the UE is in a suspended status.
NOTE 2: Stage 8 cannot be triggered by the suspend procedure since the full GUTI cannot be derived from the P-TMSI and RAI included in the suspend request message.
9. The UE continues with the MO call setup procedure, sending a CM service request.
10a. If the UE is not registered with the MSC serving the 2G / 3G cell, or the UE is not allowed in the LA, the MSC will reject the service request if an implicit location update is not performed.
10b. A UE that detects that the MSC has rejected the service request will perform a location area update or a combined RA / LA procedure, according to existing GERAN or UTRAN procedures, as specified in TS 23.060 [3] for the different Network Operation Modes (NMO).
10c. The UE initiates the CS call establishment procedure.
eleven. Once the CS voice call has been terminated, and if the UE is in GERAN and PS services are suspended, then the UE will resume PS services as specified in TS 23.060 [3]. A Gn / Gp -SGsN will follow TS 23.060 [3] to resume the PDP context (s). An SGSN of S4 will follow TS 23.060 [3] to retake bearers, and informs the S-GW and P-GW (s) that it is resuming suspended bearers. If the UE has returned to E-UTRAN after it has terminated the CS voice call, then the UE should resume PS service by sending a TAU to the MME. The MME will also inform the S-GW and the P-GW (s) that it is resuming the suspended carriers. The resumption of the suspended carriers in the S-GW and in the P-GW must be done by means of an implicit resumption, using the Bearer Modification request message, if this is triggered by the operating procedure, for example, RAU, TAU or service request. The S-GW is aware of the suspended status of the bearers and will forward the Bearer Modification request to the P-GW. An explicit restart should be used using the Restart Notification message, in cases where the Bearer Modification request is not triggered by the operating procedure.
If the UE remains in the UTRAN / GERAN after the CS voice call is terminated, the UE performs normal mobility management procedures as defined in TS 23.060 [3] and TS 24.008 [twenty-one].
========================== End of change ==================== ==============================
Examples of the present invention are set forth in the following numbered clauses.
1. A method, in a first network element of a wireless communication network, such that the method comprises:
receive a first message from a mobility management entity (MME), such that the first message is associated with the triggering of a circuit-switched alternative option procedure (CSFB) to redirect a User Equipment (UE) to changing from the first network element to a second network element;
ES 2 631 817 T3 determining that Packet Switched Delivery (PS HO) is not available for the CSFB procedure; and sending a second message to the UE in response to said determination, such that the second message is associated with causing the UE to perform a Radio Resource Control (RRC) connection release procedure.
two. The method according to clause 1, in which said determination includes determining, in the first network element, that the UE has only a Local IP Access Packet Data Network (PDN) connection (LIPA) in the first network element.
3. The method according to clause 1, in which the second network element is one of a GERAN base station and a UTRAN base station.
Four. The method according to clause 3, in which the second message is one of:
an RRC message, including a cell change order between RATs destined for a neighboring GERAN base station, in case the UE and the network support the cell change order between RATs destined for GERAN, and the second network element is from GERAN; or a handshake message, intended to trigger an RRC connection release with redirection to the second network element, in the case that the second network element is a GERAN or UTRAN base station; or a handshake message, intended to trigger an RRC connection release with redirection to the second network element, such that the handshake message to trigger the RRC connection release comprises one or more identities of physical cell and associated system information, in case the second network element is a GERAN or UTRAN base station, and the UE and the network support “RRC connection release with multi-cell system information and redirection to GERAN / UTRAN”.
5. The method according to clause 1, in which the first network element is an evolved home node base station (HeNB).
6. The method according to clause 1, in which the first message is a UE context modification request, including a CSFB flag.
7. The method according to clause 1, wherein said determination that the HO PS is not available to the CSFB comprises detecting an indication in the first message from the MME that the HO PS is not available.
8. The method according to clause 1, in which said determination that the PS HO is not available to the CSFB comprises detecting that all RRC connections for the UE have an associated correlation ID.
9. The method according to clause 1, in which the CSFB procedure is related to a mobile originated call.
10. The method according to clause 1, in which the CSFB procedure is related to a mobile terminated call.
eleven. A method for use in a mobility management entity (MME) of a network, such that the method comprises:
receive an extended service request message with circuit-switched alternative option indicator (CS), from a User Equipment (UE), such that the UE is connected to a first network element that has a first characteristic of ID;
send a UE Context Modification Request message to a second network element of the network, including the CS alternative option indicator to indicate that the UE is to move to a second network element, such that the second network element supports CS services, and such that a value of the CS alternative option indicator is set to "CS alternative option without PS HO required" only when a predetermined condition is met.
12. The method according to clause 11, in which the predetermined condition comprises determining that the UE has only one or more LIPA PDN connections in the first network element, such that one or the other is not supported. more LIPA PDN connections on the second network element.
13. A network element apparatus, in a wireless communication network, comprising logic and / or
ES 2 631 817 T3 processor control circuits for:
receive a first message from a mobility management entity (MME), such that the first message associated with causing a circuit-switched alternative option procedure (CSFB) to redirect a User Equipment (UE) to switch from the network element apparatus to a second network element apparatus;
determining that Packet Switched Delivery (PS HO) is not available for the CSFB procedure;
sending a second message to the UE in response to said determination, such that the second message is associated with causing the UE to perform a Radio Resource Control (RRC) connection release procedure.
14. The network element apparatus according to clause 13, in which the logic and / or processor control circuits determine that the UE has only one Local IP Access Packet Data Network (PDN) connection ( LIPA) on the network element apparatus.
fifteen. The network element apparatus according to clause 13, wherein the network element apparatus comprises an evolved home node base station (HeNB).
16. The network element apparatus according to clause 13, in which the second network element is one of a GERAN base station and a UTRAN base station.
17. A computer program product comprising a non-transient, computer-readable storage medium having, incorporated therein, computer-readable program code, such that said computer-readable program code has been configured to be executed for implement a method in a first network element of a wireless communication network, comprising:
instructions to receive a first message from a mobility management entity (MME), such that the first message is associated with causing a circuit-switched alternative option procedure (CSFB) to redirect a User Equipment (UE) to changing from the first network element to a second network element;
instructions to determine that Packet Switched Delivery (PS HO) is not available for the CSFB procedure; and instructions to send a second message to the UE, in response to said determination, such that the second message is associated with causing the UE to perform a Radio Resource Control (RRC) connection release procedure.
18. The computer program product according to clause 17, in which the instructions for the determination comprise instructions to determine, in the first network element, that the UE has only one Access Packet Data Network (PDN) connection Local IP (LIPA) to the first network element.
19. The computer program product according to clause 17, in which the second network element is one of a GERAN base station and a UTRAN base station.
twenty. The computer program product according to clause 17, in which the first network element is an evolved home node base station (HeNB).
Contents25
11 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11
18 members in 9 offices
Priority claims1
| Document | Office | Kind | Date |
|---|---|---|---|
| 38731010 | United States of America | P |
Members18
| Document | Office | Kind | |
|---|---|---|---|
| CA2816153A1 | Canada | A1 | |
| WO2012050842A1 | World Intellectual Property Organization (WIPO) | A1 | |
| EP2508025A1 | European Patent Office (EPO) | A1 | |
| US2012300750A1 | United States of America | A1 | |
| CN103210682A | China | A | |
| KR20130106845A | Republic of Korea | A | |
| JP2013538030A | Japan | A | |
| JP5629011B2 | Japan | B2 | |
| US8989142B2 | United States of America | B2 | |
| KR101522116B1 | Republic of Korea | B1 | |
| EP2508025B1 | European Patent Office (EPO) | B1 | |
| EP2996385A1 | European Patent Office (EPO) | A1 | |
| CN103210682B | China | B | |
| EP2996385B1 | European Patent Office (EPO) | B1 | |
| HK1222968A | Hong Kong, China | A | |
| HK1222968A1 | Hong Kong, China | A1 | |
| CA2816153C | Canada | C | |
| ES2631817T3This record | Spain | T3 |
Numbers
- Publication
- 2631817
- Application
- 15192061
Titles2
- Spanish
- Gestión de conexión de red residencial/de empresa y escenarios de CSFB
- English
- Management of residential / business network connection and CSFB scenarios
Classification
- CPC, 5
- H04W36/00224
- H04W76/00
- H04W36/1443
- H04W8/02
- H04W60/00
- IPC, 1
- H04W36 00