EP2471226B1 - Identification de corrélation pour accès ip local - Google Patents

Identification de corrélation pour accès ip local Download PDF

Info

Publication number
EP2471226B1
EP2471226B1 EP10827123.0A EP10827123A EP2471226B1 EP 2471226 B1 EP2471226 B1 EP 2471226B1 EP 10827123 A EP10827123 A EP 10827123A EP 2471226 B1 EP2471226 B1 EP 2471226B1
Authority
EP
European Patent Office
Prior art keywords
base station
correlation
pdn
cellular base
home cellular
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP10827123.0A
Other languages
German (de)
English (en)
Other versions
EP2471226A2 (fr
EP2471226A4 (fr
Inventor
Saso Stojanovski
Arnaud Vedrine
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of EP2471226A2 publication Critical patent/EP2471226A2/fr
Publication of EP2471226A4 publication Critical patent/EP2471226A4/fr
Application granted granted Critical
Publication of EP2471226B1 publication Critical patent/EP2471226B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/32—Hierarchical cell structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • LIPA local IP access
  • fixed-mobile convergence aims at proposing single communication devices able to connect both to a cellular network (e.g. when travelling) and to a local network (such as a home network, when at home, or a corporate network, or a hotspot). While fixed-mobile convergence is not yet a widespread reality, many communication devices already have both a radio interface to connect to cellular networks, and another radio interface to connect to a local network. Most often the two radio interfaces are used independently though (i.e.
  • the user selects manually, either explicitly or implicitly, which radio technology he wants to use).
  • Having two radio interfaces forces the communication device to embed two different radio technologies (e.g. WLAN interface and cellular radio interface), which is more expensive, takes more space (while size and weight are important characteristics), and consumes a lot of energy since two radio interfaces need to be powered, which reduces the autonomy of the communication device (and also reduces battery life).
  • two radio technologies e.g. WLAN interface and cellular radio interface
  • Cellular networks are very convenient because they offer an extremely broad coverage (for example a GSM user can typically make phone calls from almost anywhere in the world). However, their bandwidth is typically rather low compared to the bandwidth offered to users of local networks (which are typically connected to the Internet through rather high speed connections such as fiber, DSL or cable, for home networks). In addition, they are in general more expensive to use. Despite their extensive coverage, cellular networks are not always available, for example they are not available in certain remote locations (such as certain rural areas, or certain very small villages), or indoor locations not reachable by the cellular network's signals (basements, rooms surrounded by several layers of walls, etc.).
  • Femtocells can be used to mitigate the unavailability of cellular networks, as long as an alternate network access (typically a wired network) is available.
  • Femtocells can typically be simple devices installed by end users themselves. Femtocells behave like a cellular network with respect to communication devices (which can use their regular cellular network radio interface to communicate with them), and connect to a cellular network operator's core network through the alternate network access (such as Internet access via fiber, DSL or cable subscriptions).
  • Femtocells can be developed for any types of cellular networks technologies, for example WCDMA, GSM, CDMA2000, TD-SCDMA, WiMAX or LTE technologies.
  • the 3GPP refers to 3G femtocells as Home Node Bs (HNBs), and in LTE the proper terminology for a femtocell is Home eNode B (HeNB). Femtocells are in fact "home" cellular base stations.
  • HNBs Home Node Bs
  • HeNB Home eNode B
  • femtocells In the context of fixed-mobile convergence of voice services, the use of femtocells is an advantageous alternative to the embedding of two different radio technologies in a communication device, since the communication device becomes simpler to implement, can be smaller, lighter, cheaper, and have a better battery autonomy.
  • LIPA goes one step further and aims at providing access from a communication device to a home-based network (for any kind of IP based services, not only for voice) through a femtocell.
  • a home-based network is in fact any kind of local network (e.g. it can be in a residential or corporate environment, or a public hotspot), i.e. it is not necessarily a network in the home of an individual (the term "home” has to be understood in a broad sense, the same applies to other expressions such as "home” cellular base station).
  • LIPA LIPA is still being specified as not all issues have been addressed. LIPA is therefore the subject of standardization efforts at 3GPP. Many aspects of LIPA are still expressed as goals to be achieved, without indications on how to achieve these goals.
  • the technical report 3GPP°TR°23.8xy v0.2.0 (“Local IP Access and Selected IP Traffic Offload ”) is a study of architectural solutions for LIPA to the home-based network from a femtocell (Home NodeB or Home eNodeB), as well as a study of architectural solutions for Selected IP Traffic Offload (SIPTO) for both femtocells and macrocells.
  • the number 23.8xy was a temporary name for the technical report on LIPA when the first patent application ( US 61/375,016 ) which priority is claimed in the present patent application was filed (November 2, 2009). It was later assigned a permanent TR number by the 3GPP administration (TR 23.829).
  • the first category is of particular interest in the context of the invention.
  • the technical report was still in study phase and did not contain any full-blown architecture figure agreed in the standard at the priority date of the present application. Instead it contained a list of architectural requirements, architectural principles and a list of open issues and proposed solutions to such issues.
  • Figure°1 highlights some of the possible architecture requirements for a LIPA solution for HeNB using a local PDN connection according to the technical report.
  • a Local PDN Gateway (L-GW) function is collocated with the HeNB (for example it can be embedded in the HeNB, or each function can be embedded in a corresponding device, both devices being in the same geographical location).
  • the local PDN Gateway provides direct IP access to the home-based IP network.
  • the Mobility Management Entity (MME) and Serving GateWay (SGW) nodes are located in the operator's Evolved Packet Core (EPC).
  • EPC Evolved Packet Core
  • a Security Gateway (SeGW) node is located at the edge of the operator's core network; its role is to maintain a secure association with the HeNB across the IP backhaul network that is typically owned by a different provider and is therefore considered insecure.
  • a Home router (which typically behaves as a NAT device) is located at the boundary of the home-based IP network and the IP backhaul network, as typically found in DSL or cable access deployments today. It is also possible to have an element (optional), depicted in Figure°1 consisting of an external PDN Gateway (PGW) located in the operator's core network. This element may be used when the user needs to access services provided by the operator, in parallel to accessing the home-based network.
  • PGW PDN Gateway
  • 3GPP TR 23.8xy v0.2.0 identifies the following open issues with the type of architectures described above.
  • optical routing or “optimized routing information issue”
  • the kind of information that could be used by the HeNB to discriminate between uplink packets destined to the home-based network (i.e. the L-GW) and uplink packets destined to the external PGW was unknown.
  • the kind of information to be used by the HeNB to map the downlink packets received from the L-GW on the appropriate Radio Bearers was also unknown.
  • L-GW local breakout point
  • NAT issue operation behind a NAT device
  • the 3GPP specifications make provisions for access to a private enterprise network (intranet) from any macro cell. This is often referred to as network-based VPN access.
  • a major difference between the macro versus femto scenarios resides in the Gateway that represents the ingress point to the intranet.
  • the terminal establishes a Packet Data Network (PDN) connection to a PDN Gateway (PGW) that is part of the operator's Evolved Packet Core (EPC) and has pre-established a layer 2 tunnel to an ingress point in the intranet.
  • PDN Packet Data Network
  • PGW PDN Gateway
  • EPC Evolved Packet Core
  • L-GW Local Gateway
  • APN Access Point Name
  • Figure 2 depicts a scenario where the UE can access the Enterprise network via either a macro cell (eNodeB - eNB) or a femto cell (Home eNodeB ? HeNB).
  • eNodeB - eNB macro cell
  • HeNB femto cell
  • the signaling path for PDN connection establishment is illustrated with an arrow going from the UE to the PGW (with two solid lines) .
  • the Mobility Mobility Management Entity MME
  • the Mobility Mobility Management Entity checks the APN requested by UE against its subscription record in the HSS, as described in 3GPP TS 23.401 ("Evolved Packet Core for 3GPP access"). If the UE is authorized to access the requested APN, the MME performs PGW selection relying on DNS resolution of the APN-FQDN i.e. a Fully Qualified Domain Name that is constructed with the APN substring, as specified in 3GPP TS 23.003 ("Numbering, Addressing and Identification") and 3GPP TS 29.303 ("Domain Name System Procedures; Stage 3").
  • the corresponding APN-FQDN used for DNS resolution, will typically be constructed as: "companyABCvpn.epc.mnc015.mcc234.3gppnetwork.org”.
  • the signaling path for PDN connection establishment is depicted with an arrow going from the UE to the L-GW (with two dotted lines).
  • the MME would need to override the usual DNS resolution based on APN-FQDN and perform L-GW selection based on information other than, or in addition to, the APN.
  • the first proposal is to have the L-GW address signaled from the RAN (Radio Access Network, i.e. from the HeNB).
  • the other proposal is to use DNS based resolution with an FQDN that contains the CSG identifier of the femtocell.
  • Figure 2 makes the assumption that the Serving Gateway (SGW) is located outside of the Enterprise network, even for LIPA access. While this is a possibility, it is more likely that for LIPA access the system would select a SGW that resides inside the Enterprise network (L-SGW in Figure 3 ) and is collocated with the L-GW, as depicted in Figure 3 .
  • SGW Serving Gateway
  • the current solution is problematic when the same APN may be used to access the Enterprise network via both a macrocell and a femtocell.
  • MME Mobility Management Entity
  • the APN may be identified as being "LIPA only”, “LIPA prohibited”, or "LIPA conditional”, but without regard to the CSG from which the PDN connection request originates.
  • the MME is aware whether the terminal is inside a femtocell, thanks to the CSG ID that is provided by the RAN in all UE-associated signaling messages.
  • the user's subscription record in the HSS (at the time the first priority application was filed) provides no information about possible linkage between the requested APN and the CSG ID of the femtocell where the UE is currently residing.
  • the MME selected the Enterprise L-GW whenever the UE requests the Enterprise APN from a femtocell, this would lead to the error case depicted in Figure 4 .
  • the MME must not select the L-GW residing in the Enterprise network (arrow going from the UE to the L-GW, with two dotted lines), instead it must select the PGW (arrow going from the UE to the PGW, with two solid lines), in the same manner as if the UE were in a macrocell.
  • IMSI is the main reference key.
  • MSISDN The basic MSISDN of the UE (Presence of MSISDN is optional).
  • IMEI / IMEISV International Mobile Equipment Identity - Software Version Number MME Identity The Identity of the MME currently serving this MS.
  • MME Capabilities Indicates the capabilities of the MME with respect to core functionality e.g. regional access restrictions.
  • MS PS Purged from EPS Indicates that the EMM and ESM contexts of the UE are deleted from the MME.
  • ODB parameters Indicates that the status of the operator determined barring Access Restriction Indicates the access restriction subscription information.
  • EPS Subscribed Charging Characteristics The charging characteristics for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing subscription.
  • Trace Reference Identifies a record or a collection of records for a particular trace.
  • Trace Type Indicates the type of trace, e.g. HSS trace, and/or MME/ Serving GW / PDN GW trace.
  • OMC Identity Identifies the OMC that shall receive the trace record(s).
  • Subscribed-UE-AMBR The Maximum Aggregated uplink and downlink MBRs to be shared across all Non-GBR bearers according to the subscription of the user.
  • APN-OI Replacement Indicates the domain name to replace the APN OI when constructing the PDN GW FQDN upon which to perform DNS queries.
  • CSG Subscription Data is a list of CSG IDs per PLMN and for each CSG ID optionally an associated expiration date which indicates the point in time when the subscription to the CSG ID expires; an absent expiration date indicates unlimited subscription.
  • Each subscription profile contains one or more PDN subscription contexts: Context Identifier Index of the PDN subscription context. PDN Address Indicates subscribed IP address(es).
  • PDN Type Indicates the subscribed PDN Type (IPv4, IPv6, IPv4v6) APN-OI Replacement APN level APN-OI Replacement which has same role as UE level APN-OI Replacement but with higher priority than UE level APN-OI Replacement. This is an optional parameter. When available, it shall be used to construct the PDN GW FQDN instead of UE level APN-OI Replacement.
  • Access Point Name A label according to DNS naming conventions describing the access point to the packet data network (or a wildcard) (NOTE 6).
  • EPS subscribed QoS profile The bearer level QoS parameter values for that APN's default bearer (QCI and ARP) (see clause 4.7.3).
  • PDN Subscribed Charging Characteristics The charging characteristics of this PDN Subscribed context for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing subscription. The charging characteristics is associated with this APN.
  • VPLMN Address Allowed Specifies whether for this APN the UE is allowed to use the PDN GW in the domain of the HPLMN only, or additionally the PDN GW in the domain of the VPLMN.
  • PDN GW identity The identity of the PDN GW used for this APN. The PDN GW identity may be either an FQDN or an IP address.
  • the PDN GW identity refers to a specific PDN GW.
  • PDN GW Allocation Type Indicates whether the PDN GW is statically allocated or dynamically selected by other nodes. A statically allocated PDN GW is not changed during PDN GW selection.
  • PLMN of PDN GW Identifies the PLMN in which the dynamically selected PDN GW is located. Homogenous Support of IMS Over PS Sessions for MME Indicates whether or not "IMS Voice over PS Sessions" is supported homogeneously in all TAs in the serving MME.
  • APN - PDN GW ID relations for PDN subscription context with wildcard APN: APN - P-GW relation #n
  • the PDN GW identity may be either an FQDN or an IP address.
  • the PDN GW identity refers to a specific PDN GW.
  • the invention seeks to improve the situation.
  • the invention relates in particular to a direct path enablement method implemented in a home cellular base station (Home eNodeB in the LTE environment), in accordance with claim 1.
  • the invention also relates to a home cellular base station in accordance with claim 3.
  • the traffic follows a short-cut path, as follows.
  • Uplink packets sent by the UE and received by the HeNB are forwarded directly to the collocated L-GW function, which relays them towards the home-based network.
  • Downlink packets received by the L-GW function are forwarded directly to the collocated HeNB, which relays them on the radio interface towards the UE.
  • S5-GTP GTP-based S5
  • S1 eNB TEID is a tunnel endpoint identifier used in the GTP-U protocol on S1, assigned by eNB, stored in eNB and SGW.
  • S1 SGW TEID is a tunnel endpoint identifier used in the GTP-U protocol on S1, assigned by SGW, stored in eNB, SGW and MME.
  • S5 SGW TEID is a tunnel endpoint identifier used in the GTP-U protocol on S5, assigned by SGW, stored in SGW and PGW.
  • S5 PGW TEID is a tunnel endpoint identifier used in the GTP-U protocol on S5, assigned by PGW, stored in SGW, PGW and MME.
  • S5 PGW TEID is known by the MME and is signaled to HeNB across S1-MME as part of the E-RAB context setup in messages like INITIAL CONTEXT SETUP REQUEST or E-RAB SETUP REQUEST, etc.
  • This S5 PGW TEID abbreviated PGW TEID, can therefore be used as a first correlation ID in an embodiment of the invention.
  • the L-GW function performs a usual bearer binding onto EPS bearers, which results in identifying the underlying S5 PGW TEID parameter.
  • the L-GW function then passes (internally) the S5 PGW TEID parameter to the HeNB function along with the IP packet. This is an internal operation in the sense that the L-GW and the HeNB are collocated (so the information does not have to travel through an external network).
  • the interface between the L-GW and the HeNB can however rely on a network protocol, in order (for example) to reuse software bricks developed for a regular PGW which is not collocated with the HeNB.
  • the HeNB function maps S5 PGW TEID to the corresponding S1 eNB TEID and thus identifies the appropriate E-RAB context and the corresponding Radio Bearer on which to send the packet to the UE.
  • the very presence of the S5 PGW TEID parameter in the Radio Bearer context indicates that the packet should be forwarded to the L-GW function, rather than over S1-U (user plane interface).
  • the S5 PGW TEID parameter may be passed (internally) along with the IP packet; this could be used by the L-GW function e.g. to perform bearer binding verification.
  • Figure°6 shows the user-plane information, stored in various EPS nodes according to a known architecture, that is used for packet forwarding inside the network with S5-PMIP.
  • the stored information related to S5 is different from the S5-GTP case (bold italics are used in Figure 6 for PMIP-specific information) and is described as follows:
  • S5 SGW GRE is the GRE key used in the GRE encapsulated IP packets on S5, assigned by SGW, stored in SGW and in PGW.
  • GRE stands for Generic Routing Encapsulation and is a tunneling protocol that can encapsulate a wide variety of network layer protocol packet types inside IP tunnels.
  • S5 PGW GRE is the GRE key used in the GRE encapsulated IP packets on S5, assigned by PGW, stored in SGW, PGW and MME.
  • S5 PGW GRE is known by the MME and is signaled to HeNB across S1-MME as part of the E-RAB context setup in messages such as INITIAL CONTEXT SETUP REQUEST or E-RAB SETUP REQUEST, etc.
  • the L-GW function For downlink packets, the L-GW function identifies the S5 PGW GRE key corresponding to the local PDN connection for this UE.
  • the L-GW function passes (internally) the S5 PGW GRE parameter to the HeNB function along with the IP packet.
  • the HeNB function maps S5 PGW GRE to the corresponding S1 eNB TEID and thus identifies the appropriate E-RAB context and the corresponding Radio Bearer.
  • the very presence of the S5 PGW GRE parameter in the Radio Bearer context indicates that the packet should be forwarded to the L-GW function, rather than over S1-U.
  • the proposed solution for PMIP works only in case there is only one EPS bearer per PDN connection (i.e. the default EPS bearer), which is expected to be the most common LIPA deployment scenario.
  • FIG. 8 describes an Attach procedure according to 3GPP TS 23.401 ("Evolved Packet Core architecture for 3GPP accesses; Stage 2") modified according to an embodiment of the invention, in which an S5 PGW TEID parameter (for S5-GTP) or an S5 PGW GRE parameter (for S5-PMIP) is added in step°17 of the procedure (i.e. INITIAL CONTEXT SETUP REQUEST message of the S1-AP protocol as specified in 3GPP TS 36.413 "S1 Application Protocol (S1-AP)").
  • the attach/accept is based on NAS (Non-Access-Stratum, a functional layer in the Wireless Telecom protocol stack between Core Network and User Equipment), i.e.
  • the MME decides to attach the correlation ID only if this is necessary. If the connection which establishment is requested is not a LIPA connection, no correlation ID is needed. In step 11, whether the requested connection is LIPA or not, it may be determined that the current CSG is not authorized for LIPA, and should accordingly be denied (as LIPA). It is useful to distinguish the authorization of a LIPA connection from the mere request of a LIPA connection.
  • Figure°9 shows a Dedicated Bearer Activation procedure from 3GPP TS 23.401, modified according to an embodiment of the invention, in which an S5 PGW TEID parameter is added in step°4 of the procedure (i.e. BEARER SETUP REQUEST message of the S1-AP protocol).
  • S5 PGW TEID parameter is added in step°4 of the procedure (i.e. BEARER SETUP REQUEST message of the S1-AP protocol).
  • S5 PGW TEID parameter is added in step°4 of the procedure (i.e. BEARER SETUP REQUEST message of the S1-AP protocol).
  • S5-GTP is applicable (no PMIP).
  • Figure°10 shows an UE Requested PDN Connectivity procedure from 3GPP 23.401, modified according to an embodiment of the invention, in which an S5 PGW TEID parameter (for S5-GTP) or an S5 PGW GRE parameter (for S5-PMIP) is added in step°7 of the procedure (i.e. BEARER SETUP REQUEST message of the S1-AP protocol).
  • an S5 PGW TEID parameter for S5-GTP
  • S5 PGW GRE parameter for S5-PMIP
  • Figure°11 shows an S1-based Handover procedure from 3GPP 23.401, modified according to an embodiment of the invention, in which an S5 PGW TEID parameter (for S5-GTP) or an S5 PGW GRE parameter (for S5-PMIP) is added in step°5 of the procedure (i.e. HANDOVER REQUEST message of the S1-AP protocol).
  • an S5 PGW TEID parameter for S5-GTP
  • S5 PGW GRE parameter for S5-PMIP
  • Figure°12 is the Service Request procedure from 3GPP 23.401, modified according to an embodiment of the invention, in which an S5 PGW TEID parameter (for S5-GTP) or the S5 PGW GRE parameter (for S5-PMIP) is added in step°4 of the procedure (i.e. INITIAL CONTEXT SETUP REQUEST message of the S1-AP protocol).
  • an S5 PGW TEID parameter for S5-GTP
  • S5 PGW GRE parameter for S5-PMIP
  • the S1-MME and S1-U reference points can be secured by tunneling inside an IPsec tunnel, established between the HeNB and the SeGW, as specified in 3GPP TS 33.320 v1.0.0 "3GPP Security Aspect of Home NodeB and Home eNodeB".
  • Figure°1 proposes that the S5 reference point (between SGW and L-GW) be also secured by tunneling inside the same IPsec tunnel established between the HeNB and the SeGW.
  • the L-GW function resides in the home network and uses a private IP address. As such, it is not easily reachable from the outside e.g. for signaling transactions initiated by the SGW over S5.
  • S5 By tunneling S5 inside an IPsec tunnel, the L-GW function becomes reachable via an IP address assigned from the Evolved Packet Core network.
  • S5 could be tunneled in a different IPsec tunnel than the one used for S1, however, it is advantageous not to do it. Indeed, contrary to the IPsec tunnel for S1 that is up and running permanently, the S5 IPsec tunnel is needed only when the femtocell user needs access to the home-based network.
  • opening two IPsec tunnels could typically require twice more credentials (different credentials are typically required to authenticate parties through different IPsec tunnels), and could pose scalability issues while increasing complexity. Reusing the same credentials would be conceivable in certain instances but may lower the security, depending on the specific situation.
  • GTP-U When using S5-GTP, there are two instances of the GTP-U protocol inside the IPsec tunnel: GTP-U over S1-U and GTP-U over S5. This creates an issue as explained in Figure°7.
  • Figure°7 shows the user plane protocol stacks on S1-U and S5.
  • the GTP-U protocol is transported over UDP and has a well-known UDP port number (port number 2152). If the combined HeNB/L-GW node uses the same IP address for both S1-U and S5, the SGW will be unable to discriminate packets flowing on S1-U from packets flowing on S5.
  • a possible embodiment of the combined HeNB/L-GW node uses two different addresses: one for the HeNB function and the other one for the L-GW function.
  • an IPsec tunnel between HeNB and SeGW is established, in accordance with 3GPP TS 33.320 v1.0.0 ("3GPP Security Aspect of Home NodeB and Home eNodeB") with the IKEv2 protocol (IETF RFC 4306 "Internet Key Exchange IKEv2 protocol").
  • the IKEv2 protocol allows the "initiator” to request multiple "internal IP addresses” via the CFG_REQUEST configuration payload during the initial IKEv2 exchange (see clause 3.15.1 in RFC 4306).
  • the combined HeNB/L-GW node may then request at least two internal IP addresses and assign one to the HeNB and another one to the L-GW functions.
  • the L-GW address is passed to the MME as part of the S1 SETUP REQUEST message defined in 3GPP TS 36.413 ("S1 Application Protocol (S1-AP) ").
  • S1-AP Application Protocol
  • the L-GW address can be passed in the INITIAL UE MESSAGE message defined in TS 36.413, however this is typically less efficient than sending it in the S1 SETUP REQUEST message.
  • the HeNB function and the L-GW function share the same IP address, and to configure the TEID assignment logic in the HeNB and the L-GW so that the same TEID is never used simultaneously on both S5 and S1-U. For instance this can be achieved by dividing the TEID value range into two disjoint subranges that are reserved for the HeNB and L-GW function, respectively.
  • the Subranges are preferably contiguous, however any subrange is in principle acceptable, for example one could arbitrarily decide that odd TEIDs are for S5 and even TEIDs are for S1-U, or vice versa.
  • the entity assigning the TEIDs is not the SGW, but the HeNB/ L-GW.
  • FIG.14 shows the IKEv2 signaling for establishment of IPsec tunnel between HeNB and SeGW from 3GPP TS 33.320 v1.0.0 ("3GPP Security Aspect of Home NodeB and Home eNodeB"), modified according an embodiment of the invention so that the call flow involves a CFP_REQUEST configuration payload in step°4 of the procedure modified to request two "internal" IP addresses: one for the HeNB and another one for the L-GW functions. Similarly, the CSF_REPLY in step°7 is used by the SeGW to provide the requested IP addresses.
  • CFP_REQUEST configuration payload in step°4 of the procedure modified to request two "internal" IP addresses: one for the HeNB and another one for the L-GW functions.
  • the CSF_REPLY in step°7 is used by the SeGW to provide the requested IP addresses.
  • the MME may request from the HeNB (e.g. in INITIAL CONTEXT SETUP REQUEST message or E-RAB SETUP REQUEST message or UE CONTEXT MODIFICATION REQUEST message) to send a copy of every uplink packet on S1-U.
  • the HeNB e.g. in INITIAL CONTEXT SETUP REQUEST message or E-RAB SETUP REQUEST message or UE CONTEXT MODIFICATION REQUEST message
  • Each packet copy is tagged as such via a new flag in the GTP-U encapsulation header, so that it can be consumed at the SGW without being forwarded on S5.
  • the MME may request from the L-GW function (e.g. Create Session Request message and Modify Bearer Request with S5-GTP; Proxy Binding Update with S5-PMIP) to send a copy of every downlink packet on S5.
  • L-GW function e.g. Create Session Request message and Modify Bearer Request with S5-GTP; Proxy Binding Update with S5-PMIP
  • Each packet copy is tagged as such via a new flag in the GTP-U or GRE encapsulation header, so that it can be consumed at the SGW without being forwarded on S1-U.
  • the HeNB function in the combined HeNB/L-GW node can then internally request the activation of the Lawful Intercept feature from the collocated L-GW function.
  • FIG. 15 shows the UE Context Modification procedure from 3GPP TS 36.413 ("S1 Application Protocol (S1-AP)"), modified according to an embodiment of the invention so that the flow involves an UE CONTEXT MODIFICATION REQUEST message used to turn the Lawful Intercept feature on or off.
  • S1-AP Application Protocol
  • the HeNB function in the combined HeNB/L-GW function then internally notifies the L-GW function to activate or deactivate the Lawful Intercept feature.
  • a solution is proposed to optimize paging for multiple PDN connections.
  • Paging may work in the manner proposed in 3GPP S2-095348 "Open issues and solution for SIPTO and LIPA services ".
  • 3GPP S2-095348 Open issues and solution for SIPTO and LIPA services
  • the downlink packets are consequently sent to the SGW across S5.
  • SGW buffers the downlink packets and triggers the paging procedure via the MME; there are no modifications compared to how paging works in the original EPC architecture described in 3GPP TS 23.401 ("Evolved Packet Core architecture for 3GPP accesses; Stage 2").
  • 3GPP TS 23.401 Evolved Packet Core architecture for 3GPP accesses; Stage 2
  • UE responds to paging and enters Connected mode the direct path between HeNB and L-GW becomes active. All future packet exchanges between HeNB and L-GW follow the direct path, until the UE is moved to Idle mode again.
  • the UE may have an established external PDN connection in addition to the LIPA PDN connection.
  • the SGW When downlink data arrive at the SGW either from the L-GW or from the external PGW, and the UE is in IDLE mode, the SGW sends a Downlink Data Notification (DDN) message to the MME triggering the latter to start paging the UE.
  • DDN Downlink Data Notification
  • the DDN message contains no information about the PDN connection on which the downlink data are arriving.
  • a possible scenario in which the invention can be advantageous is the following.
  • a User's femtocell is in the same Tracking Area as the surrounding macrocell. Therefore the MME does not always know whether the idle UE is camping on the femtocell or on the macrocell.
  • the UE should ideally be paged only in the femtocell rather than in the whole Tracking Area. This can be achieved by indicating the PDN connection in the Downlink Data Notification message.
  • a femtocell e.g. in a house
  • offers a spotty coverage e.g. a big house or thick walls.
  • the user goes out of femtocell coverage in which case the communication is handed over to a macrocell.
  • the MME does not release the LIPA PDN connection in order to avoid unnecessary signaling.
  • the user sends a Tracking Area Update so that the MME knows whether the idle UE is in femtocell or macrocell coverage.
  • the MME When downlink data arrive on the local network the MME should not page the UE if the UE is in a macro cell. This can be achieved by indicating the PDN connection in the Downlink Data Notification message.
  • Figure°13 is a Network triggered Service Request procedure from 3GPP 23.401, modified according to an embodiment of the invention, in which a Linked EPS Bearer ID (LBI) parameter is added in step°2a of the procedure (i.e. DOWNLINK DATA NOTIFICATION message of the GTPc-v2 protocol defined in 3GPP TS 29.274 "GPRS Tunneling Protocol; Stage 3").
  • LBI Linked EPS Bearer ID
  • user subscription information stored in the HSS is enhanced by associating the Packet Data Network's (PDN's) Access Point Name (APN) with the Closed Subscriber Group identifier (CSG ID) of the femtocell(s) from which the user is allowed to establish a PDN connection according to the Local IP Access (LIPA) principles.
  • PDN Packet Data Network's
  • APN Access Point Name
  • CSG ID Closed Subscriber Group identifier
  • LIPA Local IP Access
  • the enhanced user's subscription information allows the Mobility Management Entity (MME) to override the usual PDN Gateway (PGW) selection algorithm with a LIPA-specific Local Gateway (L-GW) selection algorithm.
  • MME Mobility Management Entity
  • PGW PDN Gateway
  • L-GW LIPA-specific Local Gateway
  • the CSG Subscription Data i.e. a list of CSG IDs to which the user can have femtocell access, is specified outside of the PDN subscription contexts.
  • the APN that can be used for LIPA access be explicitly associated with the CSG IDs from which the user can access the corresponding PDN in LIPA fashion.
  • MME Capabilities Indicates the capabilities of the MME with respect to core functionality e.g. regional access restrictions.
  • MS PS Purged from EPS Indicates that the EMM and ESM contexts of the UE are deleted from the MME.
  • ODB parameters Indicates that the status of the operator determined barring Access Restriction Indicates the access restriction subscription information.
  • EPS Subscribed Charging Characteristics The charging characteristics for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing subscription.
  • Trace Reference Identifies a record or a collection of records for a particular trace.
  • Trace Type Indicates the type of trace, e.g.
  • OMC Identity Identifies the OMC that shall receive the trace record(s).
  • Subscribed-UE-AMBR The Maximum Aggregated uplink and downlink MBRs to be shared across all Non-GBR bearers according to the subscription of the user.
  • APN-OI Replacement Indicates the domain name to replace the APN OI when constructing the PDN GW FQDN upon which to perform DNS queries. This replacement applies for all the APNs in the subscriber's profile.
  • RFSP Index An index to specific RRM configuration in the E-UTRAN URRP-MME UE Reachability Request Parameter indicating that UE activity notification from MME has been requested by the HSS.
  • the CSG Subscription Data is a list of CSG IDs per PLMN and for each CSG ID optionally an associated expiration date which indicates the point in time when the subscription to the CSG ID expires; an absent expiration date indicates unlimited subscription.
  • Each subscription profile contains one or more PDN subscription contexts: Context Identifier Index of the PDN subscription context.
  • PDN Address Indicates subscribed IP address(es).
  • PDN Type Indicates the subscribed PDN Type (IPv4, IPv6, IPv4v6) APN-OI Replacement APN level APN-OI Replacement which has same role as UE level APN-OI Replacement but with higher priority than UE level APN-OI Replacement. This is an optional parameter.
  • Access Point Name A label according to DNS naming conventions describing the access point to the packet data network (or a wildcard) (NOTE 6).
  • Field Description CSG IDs for Local IP Access For PDNs that can be accessed via Local IP Access (LIPA) this optional parameter indicates the CSG IDs from which such access is possible EPS subscribed QoS profile
  • QCI and ARP The bearer level QoS parameter values for that APN's default bearer (QCI and ARP) (see clause 4.7.3).
  • Subscribed-APN-AMBR The maximum aggregated uplink and downlink MBRs to be shared across all Non-GBR bearers, which are established for this APN.
  • EPS PDN Subscribed Charging Characteristics The charging characteristics of this PDN Subscribed context for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing subscription. The charging characteristics is associated with this APN.
  • VPLMN Address Allowed Specifies whether for this APN the UE is allowed to use the PDN GW in the domain of the HPLMN only, or additionally the PDN GW in the domain of the VPLMN.
  • PDN GW identity The identity of the PDN GW used for this APN.
  • the PDN GW identity may be either an FQDN or an IP address.
  • the PDN GW identity refers to a specific PDN GW.
  • PDN GW Allocation Type Indicates whether the PDN GW is statically allocated or dynamically selected by other nodes. A statically allocated PDN GW is not changed during PDN GW selection. PLMN of PDN GW Identifies the PLMN in which the dynamically selected PDN GW is located. Homogenous Support of IMS Over PS Sessions for MME Indicates whether or not "IMS Voice over PS Sessions" is supported homogeneously in all TAs in the serving MME.
  • APN - PDN GW ID relations for PDN subscription context with wildcard APN: APN - P-GW relation #n
  • the PDN GW identity may be either an FQDN or an IP address.
  • the PDN GW identity refers to a specific PDN GW.
  • MS PS Purged from EPS Indicates that the EMM and ESM contexts of the UE are deleted from the MME.
  • ODB parameters Indicates that the status of the operator determined barring Access Restriction Indicates the access restriction subscription information.
  • EPS Subscribed Charging Characteristics The charging characteristics for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing subscription.
  • Trace Reference Identifies a record or a collection of records for a particular trace.
  • Trace Type Indicates the type of trace, e.g. HSS trace, and/or MME/ Serving GW / PDN GW trace.
  • OMC Identity Identifies the OMC that shall receive the trace record(s).
  • APN-OI Replacement Indicates the domain name to replace the APN OI when constructing the PDN GW FQDN upon which to perform DNS queries. This replacement applies for all the APNs in the subscriber's profile.
  • RFSP Index An index to specific RRM configuration in the E-UTRAN URRP-MME UE Reachability Request Parameter indicating that UE activity notification from MME has been requested by the HSS.
  • the CSG Subscription Data is a list of CSG IDs per PLMN and for each CSG ID optionally an associated expiration date which indicates the point in time when the subscription to the CSG ID expires; an absent expiration date indicates unlimited subscription.
  • CSG IDs that can be used to access a specific PDN via Local IP Access (LIPA)
  • LIPA Local IP Access
  • the CSG ID entry is associated with the Access Point Name (APN) of that PDN.
  • Each subscription profile contains one or more PDN subscription contexts: Context Identifier Index of the PDN subscription context.
  • PDN Address Indicates subscribed IP address(es).
  • PDN Type Indicates the subscribed PDN Type (IPv4, IPv6, IPv4v6) APN-OI Replacement APN level APN-OI Replacement which has same role as UE level APN-OI Replacement but with higher priority than UE level APN-OI Replacement. This is an optional parameter. When available, it shall be used to construct the PDN GW FQDN instead of UE level APN-OI Replacement.
  • Field Description Access Point Name A label according to DNS naming conventions describing the access point to the packet data network (or a wildcard) (NOTE 6).
  • EPS subscribed QoS profile The bearer level QoS parameter values for that APN's default bearer (QCI and ARP) (see clause 4.7.3).
  • PDN Subscribed Charging Characteristics The charging characteristics of this PDN Subscribed context for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing subscription. The charging characteristics is associated with this APN.
  • VPLMN Address Allowed Specifies whether for this APN the UE is allowed to use the PDN GW in the domain of the HPLMN only, or additionally the PDN GW in the domain of the VPLMN.
  • PDN GW identity The identity of the PDN GW used for this APN. The PDN GW identity may be either an FQDN or an IP address.
  • the PDN GW identity refers to a specific PDN GW.
  • PDN GW Allocation Type Indicates whether the PDN GW is statically allocated or dynamically selected by other nodes. A statically allocated PDN GW is not changed during PDN GW selection.
  • PLMN of PDN GW Identifies the PLMN in which the dynamically selected PDN GW is located. Homogenous Support of IMS Over PS Sessions for MME Indicates whether or not "IMS Voice over PS Sessions" is supported homogeneously in all TAs in the serving MME.
  • APN - PDN GW ID relations for PDN subscription context with wildcard APN: APN - P-GW relation #n
  • the PDN GW identity may be either an FQDN or an IP address.
  • the PDN GW identity refers to a specific PDN GW.
  • the above enhancements in the user's subscription record stored in the HSS are advantageous, in particular due to their ability to assist the Mobility Management Entity (MME) in deciding whether the user can be granted access to the requested packet data network via Local IP Access (LIPA).
  • MME Mobility Management Entity
  • LIPA Local IP Access
  • the invention is not limited to the above described exemplary embodiments, and also encompasses many different variants.
  • most embodiments have been described in the context of E-UTRAN (with a HeNB), but can be adapted in straightforward manner to a UTRAN context (with a HNB connecting to the Evolved Packet Core EPC, the EPC network supporting a S4-SGSN node described in 3GPP TS 23.401 "Evolved Packet Core architecture for 3GPP accesses; Stage 2".
  • An example of equivalent LIPA architecture for HNB femtocells is shown on Figure°16.
  • HeNB and MME are replaced by HNB and SGSN, respectively.
  • An extra node referred to as HNB GW (specified in 3GPP TS 25.467 "UTRAN architecture for 3G Home Node B (HNB); Stage 2") is added, and is connected to the HNB and the SGW via the Iuh and the S12 reference point, respectively.
  • the S11 interface is replaced by an S4 interface.
  • the S5 PGW TEID or the S5 PGW GRE parameter is carried within the RAB ASSIGNMENT REQUEST message (defined in 3GPP TS 25.413 "RANAP protocol").
  • the L-GW address is carried within the INITIAL UE MESSAGE message (defined in 3GPP TS 25.413).
  • the L-GW address is carried within the HNB REGISTER REQUEST message (defined in 3GPP TS 25.467).
  • the L-GW address is carried within the UE REGISTER REQUEST message (defined in 3GPP TS 25.467).
  • a copy of each uplink IP packet is forwarded across Iuh/S12.
  • the user plane protocol being the same as in the S1-U case (i.e. GTP-U)
  • the new tag in the GTP-U encapsulation described earlier is exactly the same.
  • UE SPECIFIC INFORMATION INDICATION message (defined in 3GPP TS 25.413) can be used (instead of the UE CONTEXT MODIFICATION REQUEST message) to turn the Lawful Intercept feature on or off.
  • the invention is applicable to other wireless technologies such as WCDMA, GSM, CDMA2000, TD-SCDMA, or WiMAX.
  • the vocabulary used in the described embodiment is the conventional vocabulary in the context of LTE, however other standards use a different terminology.
  • the invention is not limited to LTE by the use of LTE vocabulary.
  • the GSM standard refers to "mobile stations” comprising a “mobile equipment” (typically a cell phone) equipped with a SIM card.
  • any communication device compliant with the requirement laid out in relation with said embodiments is appropriate, even a GSM compliant communication device.

Claims (3)

  1. Procédé d'activation de voie directe comprenant :
    l'obtention, dans une station de base cellulaire de rattachement, d'un premier identifiant de corrélation pour activer une voie directe de plan d'utilisateur entre la station de base cellulaire de rattachement et une passerelle locale fournissant un accès à un réseau IP local ;
    la réception, dans la station de base cellulaire de rattachement, d'un paquet IP de liaison montante sur un support radio ;
    la vérification, dans la station de base cellulaire de rattachement, de la présence du premier identifiant de corrélation pour ledit support radio ; et
    la transmission, dans la station de base cellulaire de rattachement, du paquet IP de liaison montante à destination de la passerelle locale si le premier identifiant de corrélation est présent, et la transmission, dans la station de base cellulaire de rattachement, du paquet IP de liaison montante à destination d'une passerelle de desserte si le premier identifiant de corrélation n'est pas présent,
    dans lequel la passerelle locale se trouve au même emplacement que la station de base cellulaire de rattachement,
    dans lequel le premier identifiant de corrélation est obtenu par l'intermédiaire d'une interface de plan de commande de la station de base cellulaire de rattachement par la réception, dans la station de base cellulaire de rattachement, d'une demande de configuration de contexte initial ou d'une demande de configuration E-RAB,
    dans lequel l'interface de plan de commande est une interface S1-MME définie entre la station de base cellulaire de rattachement et une entité de gestion de mobilité, MME,
    dans lequel le premier identifiant de corrélation est un identifiant de point d'extrémité de tunnel de passerelle de réseau de données en paquets S5, PGW TEID ou une clé d'encapsulation d'acheminement générique GRE, S5 PGW.
  2. Procédé d'activation de voie directe selon la revendication 1, comprenant la réception d'un paquet IP de liaison descendante et l'identification d'un deuxième identifiant de corrélation par la passerelle locale au cours d'une liaison de support du paquet IP de liaison descendante, et la mise en correspondance du premier identifiant de corrélation avec le deuxième identifiant de corrélation, afin de déterminer le support radio sur lequel transmettre le paquet IP de liaison descendante à destination d'un équipement d'utilisateur par l'intermédiaire d'une interface radio de la station de base cellulaire de rattachement.
  3. Station de base cellulaire de rattachement, comprenant :
    des moyens pour l'obtention d'un premier identifiant de corrélation pour activer une voie directe de plan d'utilisateur entre la station de base cellulaire de rattachement et une passerelle locale fournissant un accès à un réseau IP local ;
    des moyens pour la réception d'un paquet IP de liaison montante sur un support radio ;
    des moyens pour la vérification de la présence du premier identifiant de corrélation pour ledit support radio ; et
    des moyens pour la transmission du paquet IP de liaison montante à destination de la passerelle locale si le premier identifiant de corrélation est présent, et la transmission du paquet IP de liaison montante à destination d'une passerelle de desserte si le premier identifiant de corrélation n'est pas présent,
    dans laquelle la passerelle locale se trouve au même emplacement que la station de base cellulaire de rattachement,
    dans laquelle le premier identifiant de corrélation est obtenu par l'intermédiaire d'une interface de plan de commande de la station de base cellulaire de rattachement par la réception, dans la station de base cellulaire de rattachement, d'une demande de configuration de contexte initial ou d'une demande de configuration E-RAB,
    dans laquelle l'interface de plan de commande est une interface S1-MME définie entre la station de base cellulaire de rattachement et une entité de gestion de mobilité, MME,
    dans laquelle le premier identifiant de corrélation est un identifiant de point d'extrémité de tunnel de passerelle de réseau de données en paquets S5, PGW TEID, ou une clé d'encapsulation d'acheminement générique, GRE, S5 PGW.
EP10827123.0A 2009-11-02 2010-10-29 Identification de corrélation pour accès ip local Active EP2471226B1 (fr)

Applications Claiming Priority (7)

Application Number Priority Date Filing Date Title
US25743909P 2009-11-02 2009-11-02
US25744209P 2009-11-02 2009-11-02
US25743409P 2009-11-02 2009-11-02
US25743609P 2009-11-02 2009-11-02
US35935210P 2010-06-29 2010-06-29
US37501610P 2010-08-18 2010-08-18
PCT/KR2010/007518 WO2011053039A2 (fr) 2009-11-02 2010-10-29 Identification de corrélation pour accès ip local

Publications (3)

Publication Number Publication Date
EP2471226A2 EP2471226A2 (fr) 2012-07-04
EP2471226A4 EP2471226A4 (fr) 2017-01-04
EP2471226B1 true EP2471226B1 (fr) 2018-09-19

Family

ID=43922864

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10827123.0A Active EP2471226B1 (fr) 2009-11-02 2010-10-29 Identification de corrélation pour accès ip local

Country Status (7)

Country Link
US (2) US9325531B2 (fr)
EP (1) EP2471226B1 (fr)
JP (3) JP5427958B2 (fr)
KR (1) KR101388315B1 (fr)
CN (2) CN102598604B (fr)
CA (1) CA2773126C (fr)
WO (1) WO2011053039A2 (fr)

Families Citing this family (121)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2452698B (en) * 2007-08-20 2010-02-24 Ipwireless Inc Apparatus and method for signaling in a wireless communication system
WO2010069402A1 (fr) * 2008-12-19 2010-06-24 Telefonaktiebolaget L M Ericsson (Publ) Plan utilisateur gre
US8331384B2 (en) * 2009-05-12 2012-12-11 Cisco Technology, Inc. System and method for femto coverage in a wireless network
WO2011053039A2 (fr) 2009-11-02 2011-05-05 Lg Electronics Inc. Identification de corrélation pour accès ip local
KR20140068261A (ko) * 2009-12-04 2014-06-05 인터디지탈 패튼 홀딩스, 인크 하이브리드 네트워크에서 통합 게이트웨이에 대한 확장형 로컬 ｉｐ 액세스
WO2011078756A1 (fr) * 2009-12-23 2011-06-30 Telefonaktiebolaget L M Ericsson (Publ) Procédé et agencement dans un système de communication
JP2013526087A (ja) * 2010-04-16 2013-06-20 パナソニック株式会社 ローカルｉｐネットワークに接続するｕｅのハンドオーバ方法、ハンドオーバシステム、装置
CN102271405B (zh) * 2010-06-04 2014-09-10 中兴通讯股份有限公司 一种承载资源分配方法及装置
US9386607B2 (en) 2010-06-17 2016-07-05 Qualcomm Incorporated Method and apparatus for managing packet data network connectivity
WO2012032782A1 (fr) * 2010-09-09 2012-03-15 パナソニック株式会社 Système de communication, procédé de communication, terminal mobile et dispositif de station de base
US8554933B2 (en) * 2010-10-05 2013-10-08 Verizon Patent And Licensing Inc. Dynamic selection of packet data network gateways
EP2625826B1 (fr) * 2010-10-06 2016-01-06 Nokia Solutions and Networks Oy Traitement d'abonnés dans des réseaux de télécommunication radio
WO2012061967A1 (fr) * 2010-11-08 2012-05-18 Motorola Mobility, Inc. Système de communication sans fil, procédé de routage de données dans un système de communication sans fil et procédé de transfert intercellulaire d'un dispositif de communication sans fil, ayant une connexion de données établie avec un réseau local
US8971244B2 (en) 2010-11-09 2015-03-03 Qualcomm Incorporated Access point name list based network access management
US8649359B2 (en) 2010-11-19 2014-02-11 Nokia Corporation Apparatus and method for selection of a gateway of a local area network
JP5396375B2 (ja) * 2010-11-30 2014-01-22 株式会社Ｎｔｔドコモ 移動通信方法及び移動局
EP2656592B1 (fr) * 2010-12-22 2019-04-17 Telefonaktiebolaget LM Ericsson (publ) Sélection de noeud dans un réseau central de transmission par paquets
CN102547610B (zh) * 2010-12-31 2016-03-30 华为技术有限公司 消息处理方法、设备及系统
CN107750050B (zh) * 2011-01-06 2022-03-04 北京三星通信技术研究有限公司 一种支持用户设备ue移动性的方法和设备
JP5403562B2 (ja) * 2011-01-07 2014-01-29 株式会社日立製作所 ネットワークシステム
US9723531B2 (en) * 2011-02-15 2017-08-01 Nokia Solutions And Networks Oy Method and apparatus for in sequence delivery of downlink local IP access (LIPA) packets
US9094864B2 (en) 2011-03-02 2015-07-28 Qualcomm Incorporated Architecture for WLAN offload in a wireless device
WO2012136812A1 (fr) * 2011-04-06 2012-10-11 Nec Europe Ltd. Procédé et système de distribution de contextes d'équipement utilisateur dans un système paquet évolué
US9515986B2 (en) * 2011-05-05 2016-12-06 Telefonaktiebolaget Lm Ericsson (Publ) Methods providing public reachability and related systems and devices
WO2012157863A2 (fr) * 2011-05-16 2012-11-22 주식회사 케이티 Procédé de fourniture de continuité de service pendant un transfert de communication entre des réseaux ou dans un réseau et ses dispositifs
JP5879751B2 (ja) * 2011-06-01 2016-03-08 住友電気工業株式会社 通信システムおよび通信制御方法
US20140133458A1 (en) * 2011-06-28 2014-05-15 Kyocera Corporation Communication control method and home base station
CN102858013B (zh) * 2011-06-29 2017-09-01 北京三星通信技术研究有限公司 寻呼优化的方法
CN103650552B (zh) * 2011-06-30 2018-03-13 瑞典爱立信有限公司 WiFi固定无线个人服务
EP2727387A1 (fr) * 2011-07-01 2014-05-07 Interdigital Patent Holdings, Inc. Procédé et appareil pour une décharge de trafic de protocole internet (ip) sélectionnée (sipto) et une mobilité d'accès ip local (lipa)
CN109005602B (zh) 2011-07-05 2021-03-02 北京三星通信技术研究有限公司 避免切换失败的方法
CN102868994A (zh) * 2011-07-08 2013-01-09 北京三星通信技术研究有限公司 一种支持用户设备ue移动性的方法
US9088928B2 (en) * 2011-08-30 2015-07-21 Alcatel Lucent Local network access control via small wireless cells in wireless networks
US8493898B2 (en) 2011-09-15 2013-07-23 International Business Machines Corporation Macro diversity in a mobile data network with edge breakout
US9014023B2 (en) 2011-09-15 2015-04-21 International Business Machines Corporation Mobile network services in a mobile data network
US8625452B2 (en) 2011-09-15 2014-01-07 International Business Machines Corporation Maintenance of high-speed channels by inserting channel maintenance data in a mobile data network to avoid channel type switching
IN2014KN01008A (fr) * 2011-10-14 2015-10-09 Ericsson Telefon Ab L M
WO2013060363A1 (fr) * 2011-10-26 2013-05-02 Telefonaktiebolaget L M Ericsson (Publ) Dispositif et procédé pour débit binaire maximum par des agrégats d'équipements d'utilisateurs
US10021696B2 (en) 2011-11-16 2018-07-10 International Business Machines Corporation Data caching at the edge of a mobile data network
US8971192B2 (en) 2011-11-16 2015-03-03 International Business Machines Corporation Data breakout at the edge of a mobile data network
US9681317B2 (en) 2011-11-16 2017-06-13 International Business Machines Corporation Mitigating effects of predicted failures in a mobile network basestation due to weather
US8717872B2 (en) 2011-11-16 2014-05-06 International Business Machines Corporation Fail to wire removable module for network communication link
US9603037B2 (en) 2011-12-08 2017-03-21 Htc Corporation Method of handling delayed signaling of target mobile device
US8639951B2 (en) 2011-12-19 2014-01-28 International Business Machines Corporation States for breakout appliance in a mobile data network
US9137171B2 (en) 2011-12-19 2015-09-15 Cisco Technology, Inc. System and method for resource management for operator services and internet
US8611208B2 (en) 2011-12-19 2013-12-17 International Business Machines Corporation Autonomic error recovery for a data breakout appliance at the edge of a mobile data network
US8769615B2 (en) 2011-12-19 2014-07-01 International Business Machines Corporation Key storage and retrieval in a breakout component at the edge of a mobile data network
US9408177B2 (en) * 2011-12-19 2016-08-02 Cisco Technology, Inc. System and method for resource management for operator services and internet
US9042864B2 (en) 2011-12-19 2015-05-26 International Business Machines Corporation Appliance in a mobile data network that spans multiple enclosures
US8797981B2 (en) * 2011-12-19 2014-08-05 International Business Machines Corporation Subscriber database for services at the edge of a mobile data network
US20130155963A1 (en) 2011-12-19 2013-06-20 International Business Machines Corporation Push based services in a mobile data network with data breakout at the edge
US9210728B2 (en) 2011-12-19 2015-12-08 Cisco Technology, Inc. System and method for resource management for operator services and internet
US8479271B1 (en) 2011-12-20 2013-07-02 International Business Machines Corporation Hosting edge applications at the edge of a mobile data network
US8761827B2 (en) 2011-12-21 2014-06-24 International Business Machines Corporation Layered control of service interface for a breakout component in a mobile data network
CA2768483C (fr) * 2011-12-30 2019-08-20 Sandvine Incorporated Ulc Systemes et procedes pour gerer la qualite du service
US8782387B2 (en) 2011-12-31 2014-07-15 International Business Machines Corporation Secure boot of a data breakout appliance with multiple subsystems at the edge of a mobile data network
US9578586B2 (en) * 2012-01-11 2017-02-21 Saguna Networks Ltd. Methods circuits devices systems and associated computer executable code for providing data connectivity between a mobile communication device communicatively coupled to a mobile communication network and a third party data source
US8724455B2 (en) 2012-01-20 2014-05-13 International Business Machines Corporation Distributed control of a fail-to-wire switch for a network communication link
CN103297947B (zh) 2012-02-22 2018-06-26 中兴通讯股份有限公司 一种实现本地ip业务的方法及系统
US8793504B2 (en) 2012-02-22 2014-07-29 International Business Machines Corporation Validating a system with multiple subsystems using trusted platform modules and virtual platform modules
US9894501B2 (en) * 2012-03-30 2018-02-13 Arris Enterprises Llc Handover of on-hold session between fixed packet network and cellular network
US9112792B2 (en) 2012-04-10 2015-08-18 International Business Machines Corporation Hosting device-specific edge applications at the edge of a mobile data network
US8913556B2 (en) 2012-06-18 2014-12-16 International Business Machines Corporation Reducing packet loss in a mobile data network with data breakout at the edge
US8521153B1 (en) 2012-06-18 2013-08-27 International Business Machines Corporation Using the maintenance channel in a mobile data network to provide subscriber data when a cache miss occurs
JP5758354B2 (ja) * 2012-07-04 2015-08-05 株式会社Ｎｔｔドコモ 無線通信システム
US8873382B2 (en) 2012-07-06 2014-10-28 International Business Machines Corporation Overload detection and handling in a data breakout appliance at the edge of a mobile data network
US8897160B2 (en) 2012-07-06 2014-11-25 International Business Machines Corporation IP flow based offload for subscriber data optimization and scheduling at the basestation in a mobile data network
WO2014008912A1 (fr) * 2012-07-09 2014-01-16 Telefonaktiebolaget L M Ericsson (Publ) Procédé et nœuds pour exécuter une transmission par radiomessagerie dans un réseau d'accès radio
US9668161B2 (en) 2012-07-09 2017-05-30 Cisco Technology, Inc. System and method associated with a service flow router
US9001733B2 (en) 2012-07-17 2015-04-07 International Business Machines Corporation Offloading running a needed edge application to a neighboring basestation in a mobile data network
US8989141B2 (en) 2012-07-17 2015-03-24 International Business Machines Corporation Transferring a session for user equipment to a different basestation running a needed edge application
US9030944B2 (en) 2012-08-02 2015-05-12 International Business Machines Corporation Aggregated appliance in a mobile data network
US20140045486A1 (en) 2012-08-07 2014-02-13 International Business Machines Corporation Cooperative mobility management in a mobile data network with data breakout at the edge
US9071449B2 (en) 2012-08-07 2015-06-30 International Business Machines Corporation Charging and policy for services at the edge of a mobile data network
US8797905B2 (en) 2012-08-09 2014-08-05 International Business Machines Corporation Lawful interception in a mobile data network with data offload at the basestation
US9167438B2 (en) 2012-08-31 2015-10-20 International Business Machines Corporation Mobility detection for edge applications in wireless communication networks
US9019843B2 (en) 2012-09-13 2015-04-28 International Business Machines Corporation Utilizing stored data to reduce packet data loss in a mobile data network with data breakout at the edge
US8929292B2 (en) 2012-10-04 2015-01-06 International Business Machines Corporation Mobility support in a mobile data network
EP2906008B1 (fr) * 2012-10-05 2021-09-01 NEC Corporation Système de communication radio, première et deuxième station radio, terminal radio, appareil de réseau et procédés correspondants pour mettre en oeuvre l'agrégation de porteuse inter-enb
KR20140045215A (ko) * 2012-10-08 2014-04-16 삼성전자주식회사 그룹 기반 연결 설정 방법 및 장치
CN103731811B (zh) * 2012-10-11 2018-08-31 中兴通讯股份有限公司 一种演进的分组核心网络实现移动性管理的方法和系统
US9042379B2 (en) 2012-10-29 2015-05-26 International Business Machines Corporation Network management for wireless appliances in a mobile data network
US9788188B2 (en) * 2012-12-14 2017-10-10 Ibasis, Inc. Method and system for hub breakout roaming
CN111225386B (zh) * 2012-12-20 2023-07-18 北京三星通信技术研究有限公司 小小区通信的方法、系统及其设备
US9060308B2 (en) 2013-01-11 2015-06-16 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Avoiding network address translation in a mobile data network
CN104956762B (zh) * 2013-02-01 2019-10-08 瑞典爱立信有限公司 使用pcrf节点与移动性管理节点之间的直接连接的移动网关选择
US8879551B2 (en) 2013-02-22 2014-11-04 International Business Machines Corporation Collection of subscriber information for data breakout in a mobile data network
WO2014158275A1 (fr) * 2013-03-29 2014-10-02 Intel IP Corporation Établissement d'une connexion à internet dans un réseau cellulaire
US10021643B2 (en) * 2013-07-03 2018-07-10 Nokia Solutions And Networks Gmbh & Co. Kg User plane IDLE mode buffering within software defined network architecture
EP3020248B1 (fr) * 2013-07-09 2023-05-03 Telefonaktiebolaget LM Ericsson (publ) Procédé et appareil dans un système de télécommunication
EP2844022B1 (fr) * 2013-08-29 2019-07-31 Alcatel Lucent Procédé et système de routage de trafic cdn avec une passerelle de réseau de données par paquets d'ombre
CN105265007A (zh) * 2013-10-16 2016-01-20 华为技术有限公司 通信方法、本地网关、基站、mme和系统
WO2015062040A1 (fr) * 2013-10-31 2015-05-07 华为技术有限公司 Procédé, système et appareil de négociation de capacité
KR102219415B1 (ko) * 2014-01-20 2021-02-25 삼성전자 주식회사 Lte 망에서 최적 데이터 경로를 위한 mme와 로컬 서버, 이들 간 인터페이스 및 데이터 송수신 방법
KR101587416B1 (ko) * 2014-02-26 2016-01-21 주식회사 이노와이어리스 Ｌｔｅ 펨토셀에서 이동통신 단말기의 ｉｐ 주소 획득 방법
US10306685B2 (en) 2014-04-22 2019-05-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and nodes for handling a GTP-U direct tunnel
EP2950564B1 (fr) * 2014-05-28 2021-06-23 Alcatel Lucent International Noeud d'un réseau de télécommunication pour le trafic de réseau de distribution de contenu
WO2015191835A1 (fr) * 2014-06-11 2015-12-17 Convida Wireless, Llc Service de mappage pour la redirection d'un contenu local
CN105338655B (zh) 2014-06-19 2021-02-02 北京三星通信技术研究有限公司 一种用户平面承载建立的方法及装置
WO2015195014A1 (fr) * 2014-06-19 2015-12-23 Telefonaktiebolaget L M Ericsson (Publ) Procédé et agencement pour traiter des ressources radio
CN105323736A (zh) * 2014-06-27 2016-02-10 中兴通讯股份有限公司 Imsi获取方法及装置、信令监测系统
US10505621B2 (en) * 2014-10-07 2019-12-10 Nec Corporation Relay radio terminal, core network apparatus, and method therefor
US9807669B1 (en) * 2014-10-24 2017-10-31 Sprint Communications Company L.P. Identifying communication paths based on packet data network gateway status reports
US9955345B2 (en) * 2015-02-05 2018-04-24 StarHome Mach GmbH System and method for mobile network access point name virtualization
EP3277006B1 (fr) * 2015-04-22 2020-07-08 Huawei Technologies Co., Ltd. Procédé, appareil et système permettant d'autoriser un nom de point d'accès
SG11201802201YA (en) 2015-09-18 2018-04-27 Huawei Tech Co Ltd Method for accessing local network, and related device
EP3823239A1 (fr) * 2015-10-28 2021-05-19 Huawei Technologies Co., Ltd. Procédé et système de traitement de support, et appareil associé
CN106686666A (zh) * 2015-11-09 2017-05-17 中兴通讯股份有限公司 一种网关信息更新的方法及装置
CN105791066B (zh) * 2016-04-26 2019-08-20 中国联合网络通信集团有限公司 控制信息发送方法和装置
US10887927B2 (en) * 2016-05-16 2021-01-05 Telefonaktiebolaget Lm Ericsson (Publ) Evolved packet system (EPS) bearer identity based active flag extension for cellular internet of things (CIoT) devices
US10470031B2 (en) 2016-05-20 2019-11-05 Ibasis, Inc. Voice over IMS roaming gateway
WO2018001537A1 (fr) 2016-06-30 2018-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Réacheminement d'informations liées à un ims en vue d'une interception licite pour une mobilité en s8hr
EP3482542B1 (fr) 2016-07-11 2023-04-26 Nokia Solutions and Networks Oy Procédés et appareils pour mettre en corrélation des informations relatives à une interception avec un contenu d'appel
WO2018061601A1 (fr) * 2016-09-29 2018-04-05 日本電気株式会社 Station de base, passerelle, procédé, programme et support d'enregistrement
WO2018095506A1 (fr) * 2016-11-22 2018-05-31 Nokia Solutions And Networks Oy Sélection optimisée de trajet de plan utilisateur
CN106789538A (zh) * 2017-01-20 2017-05-31 福建三元达网络技术有限公司 一种兼容现网的无线回传方法及系统
CN108934007B (zh) * 2017-05-25 2022-03-25 中兴通讯股份有限公司 一种upf重选的策略控制方法、pcf及smf
US10701667B2 (en) * 2018-04-09 2020-06-30 Qualcomm Incorporated Paging techniques in a wireless backhaul network
JP6623268B1 (ja) * 2018-09-26 2019-12-18 ソフトバンク株式会社 制御プレーン機器、プログラム、システム及び情報処理装置
WO2020072652A1 (fr) * 2018-10-03 2020-04-09 Intel Corporation Systèmes, procédés, et appareils pour l'activation de services relais devant permettre à un équipement utilisateur d'accéder à un réseau 5gc via une passerelle résidentielle
US11224012B1 (en) 2020-06-18 2022-01-11 T-Mobile Usa, Inc. Simulating continuous millimeter wave band access to a telecommunications network

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001449B (zh) 2006-01-10 2010-05-12 中兴通讯股份有限公司 不同接入系统间的寻呼方法
WO2008072687A1 (fr) * 2006-12-15 2008-06-19 Sharp Kabushiki Kaisha Système de communication radio et procédé de commande de trajet de transmission radio
FI20075297A0 (fi) 2007-04-27 2007-04-27 Nokia Siemens Networks Oy Menetelmä, radiojärjestelmä ja tukiasema
US20090003359A1 (en) * 2007-06-29 2009-01-01 Cisco Technology, Inc. Selecting a Visited Bearer Manager (VBM)
CN101136835B (zh) * 2007-09-30 2011-09-21 中兴通讯股份有限公司 一种空闲模式下承载建立方法
EP2201743A4 (fr) 2007-10-17 2016-01-27 Ericsson Telefon Ab L M Procédé et agencement pour déterminer un réglage de sécurité
US8514809B2 (en) * 2007-11-16 2013-08-20 Nokia Siemens Networks Oy Mapping quality of service for intersystem handover
US8179903B2 (en) * 2008-03-12 2012-05-15 Qualcomm Incorporated Providing multiple levels of service for wireless communication devices communicating with a small coverage access point
US9143540B2 (en) * 2008-04-24 2015-09-22 Oracle International Corporation System and method for providing service correlation in a service access gateway environment
US8654709B2 (en) * 2008-04-29 2014-02-18 Nokia Siemens Networks Oy Decentrallizing core network functionalities
KR101579714B1 (ko) 2008-04-29 2016-01-04 애플 인크. 펨토 접속된 네트워크에 대한 유비쿼터스 액세스
EP2286615B1 (fr) * 2008-05-15 2011-12-14 Telefonaktiebolaget LM Ericsson (publ) Réacheminement de données durant un transfert dans une cellule à liaison terrestre autonome
EP3229507B1 (fr) * 2009-03-13 2023-05-31 Nokia Solutions and Networks Oy Raccordement local à interface optimisée
CN102396250A (zh) * 2009-04-17 2012-03-28 松下电器产业株式会社 用于在分段移动通信系统中管理本地ip访问的设备
MX2011010539A (es) * 2009-04-23 2011-10-24 Ericsson Telefon Ab L M Acceso de ip local a traves de una estacion base femto.
JP2013502121A (ja) * 2009-08-13 2013-01-17 エヌイーシー ヨーロッパ リミテッド （ｅ）ＮｏｄｅＢに対するローカルＩＰ接続性をサポートするシステムおよび方法
WO2011053039A2 (fr) 2009-11-02 2011-05-05 Lg Electronics Inc. Identification de corrélation pour accès ip local
CN102001449A (zh) * 2010-11-09 2011-04-06 邱世军 双层轨道机械手系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
WO2011053039A2 (fr) 2011-05-05
JP5899288B2 (ja) 2016-04-06
US9860934B2 (en) 2018-01-02
CN104901875B (zh) 2018-03-02
EP2471226A2 (fr) 2012-07-04
CA2773126C (fr) 2015-12-29
CN102598604A (zh) 2012-07-18
US20110103310A1 (en) 2011-05-05
US20160219643A1 (en) 2016-07-28
KR20120071401A (ko) 2012-07-02
CN102598604B (zh) 2015-05-13
JP2015029289A (ja) 2015-02-12
KR101388315B1 (ko) 2014-04-29
US9325531B2 (en) 2016-04-26
JP5427958B2 (ja) 2014-02-26
JP5612753B2 (ja) 2014-10-22
JP2013509787A (ja) 2013-03-14
CA2773126A1 (fr) 2011-05-05
WO2011053039A3 (fr) 2011-10-27
JP2014060792A (ja) 2014-04-03
CN104901875A (zh) 2015-09-09
EP2471226A4 (fr) 2017-01-04

Similar Documents

Publication Publication Date Title
US10027710B2 (en) NAT traversal for local IP access
US9860934B2 (en) Correlation ID for local IP access
JP6536850B2 (ja) 通信システム
US8804682B2 (en) Apparatus for management of local IP access in a segmented mobile communication system
US9769852B2 (en) Maintaining current cell location information in a cellular access network

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20120328

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20161205

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/02 20090101ALN20161129BHEP

Ipc: H04L 12/28 20060101ALI20161129BHEP

Ipc: H04L 12/66 20060101AFI20161129BHEP

Ipc: H04W 8/08 20090101ALI20161129BHEP

Ipc: H04W 76/04 20090101ALN20161129BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/28 20060101ALI20180315BHEP

Ipc: H04W 8/08 20090101ALI20180315BHEP

Ipc: H04L 12/66 20060101AFI20180315BHEP

INTG Intention to grant announced

Effective date: 20180406

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: LG ELECTRONICS INC.

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010053757

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1044546

Country of ref document: AT

Kind code of ref document: T

Effective date: 20181015

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181219

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181219

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181220

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1044546

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190119

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190119

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010053757

Country of ref document: DE

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20181031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181029

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

26N No opposition filed

Effective date: 20190620

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181031

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181029

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181029

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180919

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20101029

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 602010053757

Country of ref document: DE

Owner name: ROSEDALE DYNAMICS LLC, WILMINGTON, US

Free format text: FORMER OWNER: LG ELECTRONICS INC., SEOUL, KR

Ref country code: DE

Ref legal event code: R081

Ref document number: 602010053757

Country of ref document: DE

Owner name: TAISSA RESEARCH LLC, CHICAGO, US

Free format text: FORMER OWNER: LG ELECTRONICS INC., SEOUL, KR

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20230504 AND 20230510

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 602010053757

Country of ref document: DE

Owner name: ROSEDALE DYNAMICS LLC, WILMINGTON, US

Free format text: FORMER OWNER: TAISSA RESEARCH LLC, CHICAGO, IL, US

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20230913

Year of fee payment: 14

Ref country code: GB

Payment date: 20230907

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230911

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230906

Year of fee payment: 14