[go: up one dir, main page]

WO2010130270A1 - Branchement local et sélection d'adresse ip - Google Patents

Branchement local et sélection d'adresse ip Download PDF

Info

Publication number
WO2010130270A1
WO2010130270A1 PCT/EP2009/003335 EP2009003335W WO2010130270A1 WO 2010130270 A1 WO2010130270 A1 WO 2010130270A1 EP 2009003335 W EP2009003335 W EP 2009003335W WO 2010130270 A1 WO2010130270 A1 WO 2010130270A1
Authority
WO
WIPO (PCT)
Prior art keywords
connectivity request
network address
packet network
local breakout
local
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.)
Ceased
Application number
PCT/EP2009/003335
Other languages
English (en)
Inventor
Petri Olavi Jappila
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.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Siemens Networks Oy
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 Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2009/003335 priority Critical patent/WO2010130270A1/fr
Publication of WO2010130270A1 publication Critical patent/WO2010130270A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
    • 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/50—Address allocation
    • H04L61/5084—Providing for device mobility
    • 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]

Definitions

  • the present invention generally relates to access such as radio access and also relates to methods, apparatuses and computer program products for providing access via a radio access network to a network such as a packet-switched network, for example - but not limited to - universal mobile communications system (UMTS) or long term evolution, LTE, networks, such as LTE/ evolved universal terrestrial radio access network, EUTRAN, (incl. LTE time division duplex, TDD), or local area networks, LANs
  • UMTS universal mobile communications system
  • LTE long term evolution
  • EUTRAN LTE/ evolved universal terrestrial radio access network
  • TDD time division duplex
  • LANs local area networks
  • Base stations such as home base stations, home NodeBs, femto eNodeBs (enhanced NodeBs, eNBs) or any type of access device such as an home access device (in the following generally referred to as "HNB") allow, e.g. when deployed in homes and offices, subscribers to use their existing handsets - for example in a building - with significantly improved coverage and increased broadband wireless performance.
  • IP Internet Protocol
  • LBO local IP breakout
  • Allowing for local breakout (also referred to as "route optimization") of IP traffic enables both shortening the end-to-end route and reducing the load on relatively expensive IP backbones which inherently provides a high quality of service.
  • Local IP access may differentiate user's local IP traffic in the base station, e.g. HNB so that local IP traffic to/from IP devices connected to home based networks may e.g. be forwarded on the shortest path so that it does not transit outside the home based network and remains intranet traffic.
  • local IP access traffic to the Internet does not need to transit across the operator's evolved packet core (EPC), i.e., the Internet traffic may be forwarded to and received from the Internet via a gateway local to a base station without having to transit through the operator's core nodes.
  • EPC evolved packet core
  • a base station such as a nodeB or eNodeB is configured to allocate at least one packet network address such as an IP address for a terminal, e.g. a mobile or stationary user equipment, UE, and to signal the allocated address to a control entity such as a mobility management entity, MME, in an easy and effective way.
  • a packet network address such as an IP address for a terminal, e.g. a mobile or stationary user equipment, UE
  • MME mobility management entity
  • the terminal does not need to have or use address allocation such a dynamic host configuration protocol, DHCP, functionality.
  • One or more implementations of the proposed local breakout solution are able to work without UE modifications, e.g. when IP address can be delivered in the existing messages.
  • a base station such as eNB supporting local breakout or local IP access allocates IP addresses for the terminals from the local area network.
  • the base station When a terminal sends a message to a control entity via its home cell or local IP access cell, the base station includes an address such as a selected or pre-allocated IP address for the terminal into a message to the control entity.
  • the control entity can include this IP address value to a response or setup request message.
  • the terminal may get a proper IP address for the local IP access service included into a packet data unit and does not need to start an address selection process such as DHCP or IPv6 address autoconfiguration process.
  • the proposed solution is suitable for simpler or lower cost terminals as well, e.g. for terminals that may not support or use IETF specified automatic IP address configuration but rely just on 3GPP proprietary signaling mechanisms.
  • the control entity such as mobility management, MME 1 may allocate the IP address after being informed by the eNodeB on the at least one local IP address assigned to the terminal.
  • a base station such as nodeB supporting local breakout or local IP access allocates one or more IP addresses for the UEs from the local area network.
  • a terminal such as user equipment sends a message such as a NAS message to the control entity such as MME via its home cell or local IP access cell
  • the base station may include a pre-allocated or selected IP address for the UE into the message to the control entity, such as a S1AP: UPLINK NAS Transfer message.
  • the control entity such as MME can now include this IP address value to a request message such as S1AP: E-RAB Setup Request message, so that the terminal gets a proper IP address for the local IP access service included into NAS-packet data unit, PDU.
  • the terminal 10 thus does not need to start an address generation or allocation process such as a DHCP or IPv6 Address Autoconfiguration process.
  • the proposed solution works also with lower cost UEs that may not support IETF specified automatic IP address configuration but rely just on 3GPP proprietary signaling mechanisms.
  • the proposed solution can be used in a control entity such as a mobility management entity, MME, and in a base station such as eNodeB (e.g. HomeNodeB, eNodeB).
  • a control entity such as a mobility management entity, MME
  • a base station such as eNodeB (e.g. HomeNodeB, eNodeB).
  • At least some of the proposed implementations are fully transparent to the user equipment UE. No modifications are needed due to local or IP breakout.
  • an apparatus comprising a receiver configured to receive a connectivity request from a terminal, the connectivity request not comprising a packet network address for a packet data network for local breakout.
  • the apparatus further comprises means for, or is configured to at least one of adding, to the received connectivity request, a packet network address assigned to the terminal for local breakout, or for generating, based on the received connectivity request, a connectivity request having a packet network address assigned to the terminal for local breakout.
  • the apparatus may comprise means for, or be configured for, sending the connectivity request comprising the packet network address to a control entity, receiving a response from the control entity comprising said, or another, packet network address for local breakout, and sending the packet network address received from the control entity to the terminal for use for local breakout.
  • control entity may be is a mobility management entity.
  • the packet network address may be an internet protocol address.
  • the apparatus may comprise a pool of local packet network addresses, and means for selecting at least one of the local packet network addresses to be added to the received or a newly generated connectivity request.
  • the apparatus may comprise at least one, more or all of the following: the apparatus is configured to generate the at least one packet network address using an external, local, or internal dynamic host configuration protocol device, the apparatus is configured to provide a network address translation function; the apparatus is configured to provide an address resolution protocol; the apparatus is configured to allocate the same packet network address to all terminals attached to the apparatus; the apparatus is configured to provide a field for the packet network address in an uplink message; the apparatus is configured to add at least one of further information, an access point, or an access point name to the connectivity request; the apparatus is configured to recommend whether or not local breakout is to be used.
  • the apparatus may be a base station device for a cellular network, or a part, module or chipset of or for a base station.
  • an apparatus may be configured to, or comprise means configured to send a connectivity request to a base station, the connectivity request not comprising a packet network address for a packet data network for local breakout; means for receiving a response to the connectivity request, means for checking validity of address information for local breakout included in the received response, means for deriving a valid packet network address depending on the result of the validity check.
  • the apparatus may be a terminal device for a cellular network, or a part, module or chipset of or for a terminal device.
  • an apparatus may be configured to, or comprise a receiver configured to receive a connectivity request, the connectivity request comprising a packet network address for local breakout for a terminal; means for checking whether local breakout is to be allowed for said terminal, means for returning a response indicating acceptance, a packet network address for said terminal for local breakout, or denial of local breakout, depending on the check result.
  • the apparatus may e.g. be a control entity or mobility management entity, or a part, module or chipset of or for a control device.
  • a method comprises: receiving a connectivity request from a terminal, the connectivity request not comprising a packet network address for a packet data network for local breakout; at least one of adding, to the received connectivity request, a packet network address assigned to the terminal for local breakout, or for generating, based on the received connectivity request, a connectivity request having a packet network address assigned to the terminal for local breakout.
  • a method comprises sending a connectivity request to a base station, the connectivity request not comprising a packet network address for a packet data network for local breakout; receiving a response to the connectivity request, checking validity of address information for local breakout included in the received response, deriving a valid packet network address depending on the result of the validity check.
  • a method comprises receiving a connectivity request, the connectivity request comprising a packet network address for local breakout for a terminal; checking whether local breakout is to be allowed for said terminal, returning a response indicating acceptance, a packet network address for said terminal for local breakout, or denial of local breakout, depending on the check result.
  • a computer program product may comprise code means for carrying out a method as defined above or in the following description or attached drawings, when run on a computing device.
  • the program or product may e.g. be stored on a data carrier or recording medium.
  • Fig. 1 shows a schematic network architecture with a HNB
  • Fig. 2 shows a more detailed architecture of the network system and involved network elements
  • Fig. 3 shows another implementation of a basic network configuration
  • Fig. 4 shows a signalling and processing diagram indicating signalling messages and specific processings performed at involved entities in accordance with one or more embodiments
  • Fig. 5 shows schematic block diagrams of embodiments of entities
  • Fig. 6 shows a schematic flow diagram of a processing at a terminal side
  • Fig. 7 shows a schematic flow diagram of a procedure at an access device side
  • Fig. 8 shows a schematic flow diagram of a processing at a core network side
  • Fig. 9 shows a schematic block diagram of a software based implementation according to another embodiment. DESCRIPTION OF EMBODIMENTS
  • Fig. 1 shows a schematic network architecture comprising at least one base station such as a home nodeB, HNB, 20 with a memory 220 for storing at least one local IP address for a terminal 10 such as a stationary or mobile user equipment in a subscriber home environment, e.g. within a building, and connected to at least one of an operator's core network (CN) 600, an IP network 500 and a home based local area network, LAN, 300 comprising an access router (AR) 30.
  • the HNB 20 may comprise an IP switch (IP-SW) for switching IP traffic directly to the IP network 500 or the LAN 300 without involvement of the CN 600.
  • the IP traffic may originate from or terminate at the UE 10 which optionally is wirelessly connected to the HNB 20 via an air interface.
  • the HNB 20 which serves the UE 10 comprises an interface towards the LAN 300 and the IP network 500, which provides a termination point for the UE 10 from the LAN 300 and the IP network 500.
  • the gateway functionality at the HNB 20 may be simplified to operate as a switching or bridging function for user IP traffic between the LAN 300 (home based network) or the IP network 500 and an UE specific point-to-point link over the radio interface (bearer service).
  • the switching or bridging functionality may be an IP aware functionality.
  • Fig. 2 shows a more detailed block diagram of network entities involved in a local IP access or local breakout, LBO, procedure and corresponding interfaces between those network entities.
  • the exemplary network architecture of Fig. 2 is based on an evolved universal terrestrial radio access network, EUTRAN.
  • LBO 1 of IP traffic via a visited public land mobile network (PLMN) is supported, when network policies and user subscription allow it.
  • LBO may be combined with support for multiple simultaneous packet data network (PDN) connections.
  • PLMN public land mobile network
  • the bold dashed line in Fig. 2 separates the EUTRAN part of the network system from the evolved packet core (EPC) of the network system.
  • the terminal or user equipment, UE, 10 is connected via a LTE-Uu interface to the base station HNB 20.
  • the base station HNB 20 is connected via a IPv4/IPv6 interface to a Home/Local LAN 300.
  • the HNB 20 is connected via a S1-MME interface to at least one control entity such as a mobility management entity, MME, 30 of the EPC.
  • This S1-MME interface forms a reference point for the control plane protocol between the EUTRAN and the MME.
  • the MME 30 is connected via a S3 interface to a serving node such as a serving general packet radio services (GPRS) support node (SGSN) 40.
  • GPRS general packet radio services
  • SGSN serving general packet radio services support node
  • the S3 interface enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state.
  • the MME 30 is connected via a S6a interface to a home subscriber server (HSS) 50 in which subscriber data are stored.
  • HSS home subscriber server
  • the S6a interface enables transfer of subscription and authentication data for authenticating/authorizing user access to the evolved system between the MME 30 and the HSS 50.
  • the HSS 50 is also connected to an authentication, authorization, and accounting (AAA) server 60 which manages fundamental system access functions.
  • AAA authentication, authorization, and accounting
  • the core network EPC may comprise as additional entities a serving gateway of a system architecture evolution, SAE gateway (S-GW), 70 and a packet data network, PDN SAE, gateway (P-GW) 80 which provide a gateway function to external IP networks 500.
  • S-GW 70 is connected via a S11 interface to the MME 30, wherein the S11 interface provides a reference point between the MME 30 and the S-GW 70.
  • S-GW 70 is connected via a S1_U interface to the HNB 20, wherein the S1-U interface provides a reference point between the EUTRAN and the S-GW 70 for the per bearer user plane tunnelling and inter-HNB path switching during handover.
  • a S10 interface provides a reference point between MMEs for MME relocation and MME to MME information transfer.
  • the S-GW 70 and P- GW 80 are connected via a S5 interface which provides user plane tunnelling and tunnel management between these gateways. It can be used for S-GW relocation due to UE mobility and if the S-GW 70 needs to connect to a non-co- located PDN gateway for the required PDN connectivity. It is noted that the P- GW 80 and the S-GW 70 may be implemented in one physical node or separate physical nodes.
  • the S-GW 70 is the gateway which terminates the interface towards the EUTRAN.
  • the P-GW 80 is the gateway which terminates the interface towards the PDN, e.g., the external IP network 500.
  • the PDN may be any operator external public or private packet data network or an intra-operator packet data network, e.g. for provision of IP multimedia subsystem (IMS) services. If the UE 10 is accessing multiple PDNs, there may be more than one P-GW for that UE 10.
  • IMS IP multimedia subsystem
  • a simple local IP access feature may be controlled with modifications in the existing S1 control plane interface (or Iu interface for 3G systems), keeping the RRC and NAS protocols unmodified.
  • the LBO session management can be handled at NAS level using multiple PDN support. From the UE point of view local U-plane handling can be made transparent and LBO sessions can be mapped to an UE requested PDN connectivity if the access point name (APN) is associated to the local virtual gateway provided at the HNB 20. Then, the MME 30 can still work according to the 3GPP specifications with a modified gateway handling procedure.
  • APN access point name
  • LBO subscription Users that have no local IP access subscription (LBO subscription) or HNBs that do not support LBO can use conventional EPS bearer services provided by the core network.
  • the UE 10 may be anchored to the MME 30 on the control plane.
  • the default EPS bearer service may be activated and handled from the S-GW 70 and/or the P-GW 80 of the core network (EPC).
  • EPC core network
  • the S11 control interface may be omitted at the HNB 20.
  • Fig. 3 shows another implementation of a basic network configuration wherein a base station 20 such as a nodeB or enhanced nodeB is connectable, or able to communicate, with one or more IP-based networks 500 via a local breakout LBO 1 a gateway such as gateway 70 of Fig. 2, and a server such as a mobility management entity 30.
  • a base station 20 such as a nodeB or enhanced nodeB is connectable, or able to communicate, with one or more IP-based networks 500 via a local breakout LBO 1 a gateway such as gateway 70 of Fig. 2, and a server such as a mobility management entity 30.
  • Fig. 4 shows a signalling and processing diagram which indicates messages, procedures and processing in connection with a terminal requested PDN connectivity procedure for local IP access or LBO setup, in accordance with one or more embodiments of the invention.
  • a base station such as nodeB 20 supporting local breakout or local IP access allocates one or more packet data network addresses such as IP addresses for the terminals 10 from or for the local area network.
  • a terminal such as user equipment 10 sends a connectivity request message such as a NAS message to a control entity such as a mobility management entity MME 30 via its home cell or local IP access cell
  • the base station eNB 20 may include a selected or pre-allocated packet data network address such as an IP address for the UE 10 into the message to the control entity 30, such as a S1AP: UPLINK NAS Transfer message.
  • the control entity 30 can now include this packet data network address such as IP address value to a request message such as S1AP: E-RAB Setup Request message, so that the terminal 10 gets a proper packet network address such as IP address for the local packet network, e.g. IP, access service included into NAS-packet data unit, PDU.
  • the terminal 10 thus does not need to start an address generation or allocation process such as a DHCP or IPv6 address autoconfiguration process.
  • the proposed solution may be applied to terminals of any kind and works also with lower cost UEs that may not support IETF specified automatic IP address configuration but rely just on 3GPP proprietary signaling mechanisms.
  • the proposed solution may be fully transparent to the terminal, and no modifications are needed due to local breakout.
  • the base station such as a nodeB or eNodeB keeps at least one, some or a pool of free local packet network addresses such as IP addresses.
  • the at least one free local free address can be provided or generated e.g. using a local DHCP server.
  • the base station such as the nodeB or eNodeB can keep the pool ready, or allocate a new address using e.g DHCP only when needed.
  • the base station may alternatively or additionally allocate one or more free packet network addresses by itself, e.g. when the base station is, or has the function of, a local DHCP server by itself.
  • the base station may additionally or alternatively use network address translation, NAT, and may allocate always the same packet network address such as IP address to all terminals attached to the base station.
  • NAT network address translation
  • the base station When the base station receives a connectivity request such as a packet data network, PDN 1 connectivity request from the terminal, the base station such as eNodeB may insert a valid IP address that can be used, to the connectivity request sent to the the control entity such as MME and/or to a response sent to the terminal, if the control entity, MME, decides to use or allow LBO.
  • a new field may be provided for this packet network address which may be the only mandatory addition to the whole signalling. This field optionally is additional to UPLINK NAS transfer message part.
  • the base station can use to inform e.g. about an access point or access point name, APN.
  • APN access point or access point name
  • most of the extra information can be similar to the information that the control entity MME receives from a gateway of the network, e.g. PDN GW, when LBO is not used.
  • the base station 20 may even recommend that local breakout is or can be used.
  • control entity 30 such as MME makes a decision whether it wants to allocate LBO for a requesting user. If not, then the control entity may just omit or disregard the extra values the base station has inserted.
  • the control entity 30 can add the correct IP address that the control entity had received in the connectivity request, e.g. PDN connectivity, from the base station, to the response to the base station, e.g. an E-RAB Setup request. This allows that the terminal can receive a response message such as a reconfiguration message, e.g. a NAS message, with a correct IP address. Local breakout then works without any modifications to the terminal 10.
  • the base 20 gets one or more local IP addresses for one or more possible terminals 10, and optionally stores these local IP addresses.
  • the user equipment 10 sends a packet data network, PDN, connectivity request message 3. e.g. via a radio resource control, RRC, direct transfer in uplink (UL) direction to the HNB 20 (step 3) which can act as a dynamic host configuration protocol, DHCP, relay.
  • the HNB 20 adds in step or process 4. one or more local IP addresses that can be used for the user equipment 20, e.g.
  • the base station 20 forwards the received connectivity request together with the added IP addresses via the S1 interface as an uplink NAS transfer to the MME 30 (step 5).
  • the connectivity request may include an access point name, APN pointing to a virtual gateway at the HNB 20.
  • the MME 30 verifies in a step 6. the UE subscription for LBO e.g. by initiating a query to the HSS 50 or a corresponding subscriber data base. Based on the result of the query, the MME 30 issues an E-RAB Setup Request message 7 including a NAS packet data unit (PDU) via the S1 interface (step 7).
  • PDU NAS packet data unit
  • the base station 20 detects that the user equipment 10 is requesting for local breakout, e.g. due to tunneling end point identifierTEID and transmission network layerTNL address being zero, and configures a gateway such as a virtual S-/P- GW.
  • the base station HNB 20 modifies its user equipment radio access network, UE RAN, context, optionally initializes a dynamic host configuration protocol, DHCP client (step or process 9) and sends an RRC connection reconfiguration message 10. including the NAS-PDU to the UE 10.
  • the user equipment 10 thus gets the correct IP address from the MME entity 30.
  • the UE 10 responds with a RRC Connection Reconfiguration Complete message based on which the HNB 20 enables user plane connectivity.
  • the HNB 20 detects that bearer setup is for a Local IP Access service using a HNB internal virtual gateway function.
  • the connection reconfiguration message 10. from the HNB 20 comprises one or more IP addresses for the UE 10, so that the UE 10 does not need to initiates an address configuration procedure at a DHCP client. Based on the received IP address, the UE 10 may configure its packet data network context, access point name, and IP stack in a step or process 13.
  • the base station HNB 20 may store the IP context of the UE 10. Of course, other address configuration procedures, such as IPv6 address auto- configuration or the like may be used in the base station 20 as well.
  • the base station HNB 20 may forward in step 12 a E-RAB Setup Response message to the MME 30 and broadcasts in step 14 to all nodes a notification or request with the own IP address allocated to the UE 10 as a target address in order to check whether this IP address is used more than once and/or to update tables or stacks in other nodes.
  • This notification 14. may be a gratuitous address resolution protocol, ARP 1 request packet, wherein "gratuitous" in this case means a request/reply that is not normally needed according to the ARP specification but may be used in some cases.
  • a corresponding IPv6-N-adv (Neighbor Advertisement) message may be sent.
  • control entity such as MME may send one or more zero addresses as local IP addresses to the base station which may forward the one or more zero addresses to the terminal.
  • the terminal may start to use a process such as e.g. DHCP for deriving a valid IP address.
  • the base station may keep some pool of free local IP addresses. This can be done e.g. using local DHCP server, or even eNodeB can allocate those addresses by itself, e.g. if it is local DHCP server by itself. It can even use NAT and allocate always same address to all UEs.
  • the base station such as eNodeB optionally inserts a valid IP address that can be used, if MME decides to use or allow local breakout, LBO.
  • This new field is the only mandatory addition to whole signalling in this embodiment. This field is additional to UPLINK NAS transfer message part.
  • the base station eNodeB can inform e.g. about access point or access point name, APN.
  • APN access point or access point name
  • most of the extra information may be similar to the information the control entity such as MME will receive from a packet data network gateway PDN GW, when LBO is not used.
  • the base station may even recommend that LBO can or is to be used.
  • the control entity such as MME makes a decision, if it wants to allocate LBO for that user(s). If not, the control entity may just omit the extra values such as IP address or other information inserted by the base station involved.
  • the control entity can add the correct IP address that was received in the e.g. PDN connectivity request to the setup request, e.g. E-RAB Setup request (step 7 of Fig. 4). This allows the terminal 10 to receive the NAS message (step 10) with correct IP address (and then LBO works without any modifications to terminal UE.)
  • the S1-U and S5-U GTP tunnels become internal issues of the HNB 20 and are thus not needed, which means that all related GTP tunnel configuration data (e.g. TEIDs) can be omitted.
  • the base station 20, or the MME 30, may act as a decision manager and may know all local IP access bearer service parameters which can be used by or delivered to the HNB 20.
  • An enhancement for the E-RAB Setup Request via the S1 interface could be the use of the APN aggregate maximum bitrate (AMBR) parameter for LBO bearer(s). This would allow guaranteeing a certain relation of the resource usage of the LBO bearer(s) compared to the bearers carried via the operator network.
  • This or other traffic shaping parameters can be provided to the HNB 20 by management or manual configuration generally for all APNs. E.g., n percent of the backhaul of RAN capacity of core network based bearers (e.g. default EPS bearers) could be reserved.
  • IP address(es) for the UE 10 are assigned from the IP subnet or LAN where the HNB 20 is connected, i.e., locally with assistance of the HNB 20 or itself by the UE 10. In case flatrate charging is used in connection with the local IP access or LBO, charging functions can be omitted in the HNB 20.
  • the local IP access or LBO bearer service can be configured in the HNB 20 without S11 interface or other interfaces with core network gateways by using only the S1 interface ("S1 +") requiring minimal modifications of the use of the S1 application protocol and for example in the Bearer setup request and bearer setup response messages (e.g. E-RAB Setup Request and E-RAB Setup Response).
  • S1 + S1 interface
  • Bearer setup request and bearer setup response messages e.g. E-RAB Setup Request and E-RAB Setup Response
  • Fig. 5 shows schematic block diagrams of the terminal, UE, 10, the base station HNB 20 and the control entity MME 30. It is noted that this block diagram is a simplified representation without separation of control plane and user plane connections.
  • the UE 10 comprises a radio frequency (RF) unit 101 which is configured to transmit and receive radio signals via the radio interface (e.g. LTE-Uu interface) towards the HNB 20 of the radio access network, RAN. Furthermore, the UE 10 comprises a LBO control function or unit 104 configured to perform LBO related processing and detect LBO related signalling.
  • the LBO control unit 104 checks received messages or broadcast information from the RAN, detects LBO services and initiates LBO related network entry if it has detected an LBO service. Furthermore, the initial LBO related message exchange with the MME 30 via the HNB 20 indicates that at least one IP address has been reserved or proposed for the UE 10.
  • an address selection procedure may be initiated by an address selection function or unit (AS) 102 which provides information to a message generator (MG) function or unit 105 to initiate an address configuration operation, e.g., based on DHCP or IPv6.
  • Messages generated at the message generator unit 105 are transmitted via the RF unit 101 to the radio interface.
  • the address selection unit 102 can access an access point name, APN 1 storage 103 where APNs can be stored for various connections or purposes.
  • the HNB 20 also comprises a RF unit 201 in order to enable communication to UEs or other terminal devices via the radio interface. Traffic received via the RF unit 201 can be monitored in a traffic monitoring function or unit (TrM) 202. Additionally, traffic received from the RF unit 201 or sent to the RF unit 201 can be forwarded via a traffic bridging function or unit (TrB) 203 which provides a bridging function between radio bearer services and PDN related connections.
  • TrM traffic monitoring function or unit
  • TrB traffic
  • the HNB 20 comprises a LBO control function or unit 204 which is configured to control a gateway configuring function or unit (GWC) 205 which can access a context storage unit (CT) 208.
  • the storage unit 208 or another memory, can additionally or alternatively store one or more local IP addresses which can be used for a user equipment 10 requesting local breakout, as described above.
  • the traffic monitoring unit 202 and the gateway configuring unit 205 both can control the traffic bridging unit 203. Traffic flowing through the traffic bridging unit 203 is routed to or from a transceiver unit (TRX) 301 of the MME 30 via the S1 interface.
  • TRX transceiver unit
  • the traffic received from or transmitted to the transceiver unit 301 can be supplied to a LBO control function or unit 304 which controls a tunnel configuration function or unit (TC) 305 configured to provide tunnel configuration signalling towards the core network.
  • the LBO control unit 304 accesses the HSS 50 or another subscriber-related data base 90 in order to derive LBO-related parameters needed to establish local IP access or LBO.
  • the functions or unit described in connection with Fig. 5 can be implemented as discrete hardware units or circuits or as software routines controlling a processor unit or several processor units provided at the UE 10, the HNB 20 and/or the MME 30.
  • Fig. 6 shows a schematic flow diagram of an LBO or local IP access related processing at the UE 10.
  • the UE 10 e.g. the LBO control unit 104 detects a LBO service
  • an APN which points to the virtual gateway at the HNB 20 is selected in step S101 (e.g. by the address selecting unit 102).
  • a connectivity request e.g. generated by the message generator 105 is sent with the related APN to the network targeted to MME 30 in step S102.
  • the UE 10 waits for receipt of a reconfiguration message (step S103).
  • the NAS PDU provided in the reconfiguration message is checked in step S104 (e.g. by the LBO control unit 104). Further, an IP address assigned to the user equipment 10 and received with the reconfiguration message is checked, and the received IP address is used, step S105. Finally, the UE 10 responds to its application layer that IP connectivity is available with the selected APN and IP address, step S108, using the local IP access or LBO with virtual gateway function at the HNB 20.
  • Fig. 7 shows a schematic flow diagram of a local IP access or LBO related processing at the HNB 20.
  • the procedure of Fig. 7 may be initiated when the HNB 20 receives a connectivity request, e.g. a packet data connectivity request, from the user equipment 10, e.g. message 3. of Fig. 4, or may also start when receiving a bearer setup request from the MME 30.
  • the HNB 20 selects an IP address, e.g. from a pool of free local IP addresses stored for one or more user equipment 10, and inserts or adds the selected IP address to the connectivity request message to be sent to the entity 30.
  • the base station 20 may also detect bearer-related parameters (e.g.
  • a virtual gateway at the HNB 20 may be configured in step S203 (e.g. under control of the LBO control unit 204).
  • step S204 the context of the UE 10 to which the LBO is related is modified (e.g. in the context storage 208 under control of the gateway configuring unit 205). Then, in step S205, a connection reconfiguration request is generated based on the detected bearer-related parameters (e.g. by the LBO control unit 204) and sent to the UE 10.
  • the context of the UE 10 to which the LBO is related is modified (e.g. in the context storage 208 under control of the gateway configuring unit 205).
  • step S205 a connection reconfiguration request is generated based on the detected bearer-related parameters (e.g. by the LBO control unit 204) and sent to the UE 10.
  • the HNB 20 waits for receipt of a connection reconfiguration complete message (step 206). If a reconfiguration complete message is received and local access type is determined to be set (step 207), the procedure continues in step S208, where the UE traffic is monitored and the local IP address selected for the user equipment 10 in step S201 , or a received local UE IP address is added to the UE context (e.g. by the traffic monitoring unit 202). Then, in step S209 user traffic between the radio bearer service and the IP based PDN is transmitted for the local IP access or LBO. In step S210, local traffic may be aligned with allowed Quality of Service (QoS) according to the allowed maximum bitrate if defined in the bearer-related parameters.
  • QoS Quality of Service
  • the base station 20 may broadcast a gratuitous or IPv6 neighbor advertisement in step S211.
  • Fig. 8 shows a schematic flow diagram of a local IP access or LBO related processing at the MME 30.
  • step S301 LBO subscription is verified (e.g. by the LBO control unit 304 based on a query of the HSS 50). If it is determined in step S302 that LBO is not allowed, the MME 30 may optionally respond to the UE 10 via HNB 20 with a connectivity rejection message, and the procedure ends. Otherwise, a corresponding parameter setting which indicates connectivity rejection may be signalled in subsequent steps. If LBO is allowed, an IP address received for the user equipment 10 in the connection request is used and subscription parameters are obtained in step S304 (e.g. based on a query at the HSS 50 or the other data base 90).
  • a corresponding LBO profile is selected in step S305 (e.g. by the LBO control unit 304). Then, in step S306 a bearer setup request with corresponding default parameter values and the received local IP address, or a revised IP address for the user equipment 10, is sent.
  • the default parameter values indicate the LBO profile (e.g. whether GPRS tunnel protocol, GTP, tunnelling is required, etc.).
  • step S307 the procedure checks in step S307 whether tunnelling is required, e.g. based on a corresponding parameter provided in the setup response. If tunnelling is required, e.g. since the virtual gateway at the HNB 20 is not used, a GTP tunnel is setup in step S308 (e.g. by the tunnel configuration unit 305). Furthermore, the S11 bearer between the external gateway of the core network and the HNB 20 is updated in step S309. If no tunnelling is required, the procedure ends directly after step S307.
  • the HNB may detect based on received predefined (e.g. zero) values in the transport layer address and TEID information elements that this bearer setup is intended to use a co-located (internal) virtual gateway for the local IP access or LBO service.
  • predefined e.g. zero
  • the HNB configures its local virtual gateway function according to the received bearer parameters.
  • the HNB can send the connection reconfiguration message in order to configure the radio bearer service for the requested radio bearer with the given parameters.
  • the HNB can forward among other information the NAS PDU that is the response from the MME to the UE's connectivity request.
  • the UE configures its EPS bearer service according to the parameters received in the reconfiguration message and the NAS PDU and responds to the HNB with the connection reconfiguration complete message.
  • the message can include the LBO addresses and DHCP or other means are not needed to get IP address or addresses to the UE.
  • the UE can prepare itself to configure an IP address for this PDN connectivity (local IP access or LBO) using either DHCP or IPv6 address auto-configuration or the like over the newly established EPS bearer service.
  • the HNB can prepare to monitor UE traffic over the newly established bearer service in order to assist the UE either as a DHCP relay or a proxy function in IPv6 neighbour discovery procedures towards the LAN.
  • the proposed approach provides the advantage of a simplified LBO control procedure with minimal number of messages using an interface between the access network and the core network with no need for terminating additional core network interfaces at the access node (e.g. HNB) of the access network.
  • a simplified implementation of a local IP mobility function is enabled in inter-HNB handovers with LBO in L2 switched LAN networks like home/office/campus LANs without a need to perform S-/P-GW relocation procedures on every handover, as it would be the case if other interfaces (like the S11 interface) would be terminated at the HNB.
  • the management of the co-located virtual gateway for a simple local IP access can be handled locally after the local IP access service has been setup.
  • inter-HNB handovers there is no need to perform tunnel path switching for local IP access bearer services via the MME to the S-GW.
  • NAS and RRC interfaces do not need to be modified.
  • Implementation of the MME functionality can be based on an attach to a home cell or a use of UE requested PDN connectivity procedure in the home cell (with APN or default APN indicator).
  • the MME can check if a local breakout bearer (LBB) shall be established. Criteria for this check are whether the UE is in the home cell (according to the cell identifier) or whether it accesses a network that can provide a local IP access. Additionally, a criteria could be whether the APN is allowed for LBO (e.g. a dedicated APN or a default APN), or whether the UE is allowed for LBO (by checking the subscription data). Additionally, the MME can check if the UE is allowed for CSG access (e.g.
  • the MME may perform optionally a gateway selection procedure, wherein a reserved value of the S-/P-GW address (e.g. 127.0.0.1 ) may indicate that the UE requests LBO and that LBO is allowed for this APN. Or, the MME may decide if LBO is allowed for that APN with a new procedure. The MME may apply operator policies for LBO allowed APNs (like for the Internet) to allow LBO or not. In certain conditions, the LBO possibility may be overruled and the MME may assign a gateway address of the mobile network operator.
  • a reserved value of the S-/P-GW address e.g. 127.0.0.1
  • the MME may decide if LBO is allowed for that APN with a new procedure.
  • the MME may apply operator policies for LBO allowed APNs (like for the Internet) to allow LBO or not. In certain conditions, the LBO possibility may be overruled and the MME may assign a gateway address of the mobile network operator.
  • the MME may check if LBO is allowed for that user (based on subscription data stored in the HSS). For this purpose, the subscription data in the HSS could be enhanced and/or a maximum APN restriction feature could be used to decide whether LBO is allowed in parallel to other mobile network operator bearers if other bearers of that UE are established through the operators S-GW and P-GW (for the UE requested PDN connectivity procedure).
  • the MME may setup a session management context for that bearer that can be identified in later procedures as LBO (e.g. by an LBO indicator, a reserved S-/P-GW address or a stored APN). This contact triggers a special LBO handling in the MME for later actions for that bearer.
  • the MME may skip gateway selection procedures and may assign a reserved value for the P- and S-GW addresses. Additionally, the MME may skip a create default bearer request procedure.
  • the MME may select the right LBO profile to setup the message parameters for the bearer setup request.
  • the reserved S-GW address or a LBO indicator may indicate to the HNB that an LBB shall be used.
  • the handover can be performed for the bearers that are terminated in the operator network only.
  • the HNB may remove the LBB from the list of bearers to be handed over (SAE bearer setup list) and releases the bearer towards the UE.
  • the MME removes those bearers marked as LBB from the UE session management context.
  • Fig. 9 shows a schematic block diagram of an alternative software-based implementation according to another embodiment.
  • the required functionality can be implemented in any base station type network entity 400 with a processing unit 410, which may be any processor or computing device with a control unit which performs control based on software routines of a control program stored in a memory 412.
  • the control program may also be stored separately on a computer readable medium.
  • Program code instructions are fetched from the memory 412 and are loaded to a control unit of the processing unit 410 in order to perform the processing steps of the device-specific functionalities described in connection with Figs. 3 to 8, which may be implemented as the above mentioned software routines.
  • the processing steps may be performed on the basis of input data Dl and may generate output data DO.
  • the input data Dl may correspond to a signalling received via the radio interface and the output data DO may correspond to the connectivity request and/or connection reconfiguration complete message.
  • the input data Dl may correspond to messages received from the core network (e.g. MME) and the output data DO may correspond to the bearer setup response issued to the core network.
  • the processing at the core network entity (e.g. MME) 1 the input data Dl may correspond to messages received via the S1 interface and the output data DO may correspond to the bearer setup request issued to the access device.
  • the functionalities of the above embodiments of the terminal device, access device and core network entity may be implemented as respective computer program products comprising code means for generating each individual step of the processing and/or signalling procedures for the respective entities or functions when run on a computer device or data processor of the respective entity.
  • Embodiments of the present invention thus relate to methods, apparatuses, and computer program products for interrelated entities of a network system for providing access via a cellular access network to a packet network, wherein a local IP access or local breakout (LBO) feature is provided, which may use a bridging function between a packet data network interface and a radio interface at an access device (e.g. base station device or (H)NB) that can be controlled by a single control plane interface.
  • an access device e.g. base station device or (H)NB
  • H base station device

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Les modes de réalisation permettent un accès IP local ou un raccordement local, une station de base pouvant ajouter une adresse de réseau à commutation par paquets à une demande de connectivité reçue en provenance d'un terminal sans adresse de réseau à commutation par paquets.
PCT/EP2009/003335 2009-05-11 2009-05-11 Branchement local et sélection d'adresse ip Ceased WO2010130270A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2009/003335 WO2010130270A1 (fr) 2009-05-11 2009-05-11 Branchement local et sélection d'adresse ip

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2009/003335 WO2010130270A1 (fr) 2009-05-11 2009-05-11 Branchement local et sélection d'adresse ip

Publications (1)

Publication Number Publication Date
WO2010130270A1 true WO2010130270A1 (fr) 2010-11-18

Family

ID=41508083

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2009/003335 Ceased WO2010130270A1 (fr) 2009-05-11 2009-05-11 Branchement local et sélection d'adresse ip

Country Status (1)

Country Link
WO (1) WO2010130270A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120182972A1 (en) * 2009-09-28 2012-07-19 Huawei Device Co., Ltd. Method and device for establishing or modifying local ip access bearer
US8619647B2 (en) 2011-09-15 2013-12-31 International Business Machines Corporation Macro diversity in a mobile data network with edge breakout
US8837318B2 (en) 2011-09-15 2014-09-16 International Business Machines Corporation Mobile network services in a mobile data network
DE102012220932B4 (de) * 2011-11-16 2016-03-31 International Business Machines Corporation Abmildern von Auswirkungen von vorhergesagten wetterbedingten Störungen in einer Basisstation eines Mobilfunknetzes
EP3160113A1 (fr) * 2015-10-22 2017-04-26 NTT DoCoMo, Inc. Procédé et appareil permettant d'attribuer une adresse ip à un équipement utilisateur d'un réseau mobile
EP3189632A4 (fr) * 2014-09-02 2017-07-26 Telefonaktiebolaget LM Ericsson (publ) Noeud de réseau et procédé de gestion d'un flux de trafic relatif à un nuage de service local
US12255972B2 (en) 2020-08-21 2025-03-18 Intel Corporation Edge computing local breakout

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080285492A1 (en) * 2007-05-18 2008-11-20 Seppo Vesterinen System and Method for Providing Local IP Breakout Services Employing Access Point Names
WO2009024182A1 (fr) * 2007-08-20 2009-02-26 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil fournissant une sortie locale àun réseau mobile

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080285492A1 (en) * 2007-05-18 2008-11-20 Seppo Vesterinen System and Method for Providing Local IP Breakout Services Employing Access Point Names
WO2009024182A1 (fr) * 2007-08-20 2009-02-26 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil fournissant une sortie locale àun réseau mobile

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
GUNDAVELLI K LEUNG CISCO V DEVARAPALLI AZAIRE NETWORKS K CHOWDHURY STARENT NETWORKS B PATIL NOKIA SIEMENS NETWORKS S: "Proxy Mobile IPv6; draft-ietf-netlmm-proxymip6-00.txt", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, vol. netlmm, 8 April 2007 (2007-04-08), XP015049635, ISSN: 0000-0004 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120182972A1 (en) * 2009-09-28 2012-07-19 Huawei Device Co., Ltd. Method and device for establishing or modifying local ip access bearer
US8743829B2 (en) * 2009-09-28 2014-06-03 Huawei Device Co., Ltd. Method and device for establishing or modifying local IP access bearer
US8619647B2 (en) 2011-09-15 2013-12-31 International Business Machines Corporation Macro diversity in a mobile data network with edge breakout
US8837318B2 (en) 2011-09-15 2014-09-16 International Business Machines Corporation Mobile network services in a mobile data network
US9014023B2 (en) 2011-09-15 2015-04-21 International Business Machines Corporation Mobile network services in a mobile data network
US9693241B2 (en) 2011-11-16 2017-06-27 International Business Machines Corporation Mitigating effects of predicted failures in a mobile network basestation due to weather
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
DE102012220932B4 (de) * 2011-11-16 2016-03-31 International Business Machines Corporation Abmildern von Auswirkungen von vorhergesagten wetterbedingten Störungen in einer Basisstation eines Mobilfunknetzes
EP3189632A4 (fr) * 2014-09-02 2017-07-26 Telefonaktiebolaget LM Ericsson (publ) Noeud de réseau et procédé de gestion d'un flux de trafic relatif à un nuage de service local
US10735372B2 (en) 2014-09-02 2020-08-04 Telefonaktiebolaget Lm Ericsson (Publ) Network node and method for handling a traffic flow related to a local service cloud
EP3160113A1 (fr) * 2015-10-22 2017-04-26 NTT DoCoMo, Inc. Procédé et appareil permettant d'attribuer une adresse ip à un équipement utilisateur d'un réseau mobile
WO2017068122A1 (fr) * 2015-10-22 2017-04-27 Ntt Docomo, Inc. Procédé et appareil d'attribution d'adresse ip à un équipement utilisateur de réseau mobile
US12255972B2 (en) 2020-08-21 2025-03-18 Intel Corporation Edge computing local breakout

Similar Documents

Publication Publication Date Title
EP2407004B1 (fr) Raccordement local à interface optimisée
US9794970B2 (en) Decentralizing core network functionalities
US9167413B2 (en) Local breakout with parameter access service
US8724509B2 (en) Mobile communication method, mobile communication system, and corresponding apparatus
US8462696B2 (en) Method, radio system, mobile terminal and base station for providing local breakout service
KR20100119349A (ko) 펨토 셀을 포함하는 무선 통신 네트워크에서의 로컬 ｉｐ 액세스 지원 방법 및 장치
WO2010130270A1 (fr) Branchement local et sélection d'adresse ip
JP5872066B2 (ja) 非３ｇｐｐによってコアネットワークにアクセスする方法、装置及びシステム
US10187914B2 (en) Establishment of a wireless backhaul connection from a small cell RBS
WO2012130133A1 (fr) Point d'accès et procédé d'accès par un terminal
WO2012068837A1 (fr) Procédé et dispositif pour sélectionner une passerelle d'accès
KR20140081497A (ko) 이종망간 이동성 제공 시스템 및 이동성 제공 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09776601

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09776601

Country of ref document: EP

Kind code of ref document: A1