WO2013072403A1 - Procédé de prise en charge de connectivité pdn d'un terminal mobile et terminal mobile - Google Patents

Procédé de prise en charge de connectivité pdn d'un terminal mobile et terminal mobile Download PDF

Info

Publication number
WO2013072403A1
WO2013072403A1 PCT/EP2012/072693 EP2012072693W WO2013072403A1 WO 2013072403 A1 WO2013072403 A1 WO 2013072403A1 EP 2012072693 W EP2012072693 W EP 2012072693W WO 2013072403 A1 WO2013072403 A1 WO 2013072403A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile terminal
information
pdn
establishing
dns
Prior art date
Application number
PCT/EP2012/072693
Other languages
English (en)
Inventor
Tarik Taleb
Stefan Schmid
Johannes LESSMANN
Original Assignee
Nec Europe Ltd.
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 Nec Europe Ltd. filed Critical Nec Europe Ltd.
Publication of WO2013072403A1 publication Critical patent/WO2013072403A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/17—Selecting a data network PoA [Point of Attachment]
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup

Definitions

  • the present invention relates to a method for supporting PDN (Packet Data Network) connectivity of a mobile terminal in a mobile operator network, wherein said mobile terminal is capable of establishing PDN connections via different anchor points in the core network.
  • PDN Packet Data Network
  • the present invention relates to a mobile terminal with PDN connectivity support, wherein said mobile terminal is capable of establishing PDN connections via different anchor points in the core network.
  • PDN-GWs Packet Data Network Gateways
  • S-GWs Serving GWs
  • MMEs Mobility Management Entities
  • 'data anchor gateways' or 'anchor points' will be employed synonymously to generally denote the GW in the mobile network that provides mobile terminals an IP address and serves as a mobility anchor for a PDN connection (in case of LTE/EPC (Long Term Evolution/Evolved Packet Core)) or in a PDP (Packet Data Protocol) context (in case of GPRS, General Packet Radio Service).
  • PDN-GW EPC
  • GGSN Gateway GPRS Support Node
  • This GW basically connects a mobile terminal to a PDN such as the Internet, a corporate Network, or an IMS (IP Multimedia Subsystem) network.
  • Access Point Name has been designed for GPRS and was carried over to UMTS (Universal Mobile Telecommunications System) and EPS (Evolved Packet System) as a scheme to separate logical from physical points of interconnection between a 3GPP operator's IP network and connected-to external PDNs.
  • An APN allows to associate one logical name with a particular type of traffic and maps it flexibly - but constant for the duration of an IP/PDN connection - to a route and point of interconnection. The mapping is done by the network based on DNS (Domain Name System) and the UE may not be aware of it. The UE is not concerned with details of the backend connectivity.
  • DNS Domain Name System
  • the UE not necessarily the user, may become involved at least partially with network topology for the sake of its optimal backend connectivity, e.g. minimal network resource consumption, cost and/or latency; even with active data transmission over relatively long durations and with larger scale mobility.
  • EPS Evolved Packet System
  • Fig. 1 illustrates the problems associated with the above mentioned anchor point selection process in decentralized mobile network deployment.
  • PGW1 Packet Data Network Gateway, playing the role of data anchor gateway.
  • MME Mobility Management Entity
  • a UE wants to connect to a different server, denoted target server.
  • the UE has two options: 1 ) either to connect to the target server via the current gateway, PGW1 , or to establish a new PDN (Packet Data Network) connection via another PGW, exemplarily denoted PGW2 in Fig. 1.
  • PGW1 Packet Data Network Gateway
  • the numbers nearby the links represent a routing cost associated with the respective link (e.g. hop count, etc).
  • the route according to option 1 (UE-PGW1 -target server) incurs a cost of 6
  • the alternative route according to option 2 (UE-PGW2 -Target server) incurs a cost of 5.
  • the question that has to be answered is whether the UE shall still use PGW1 , or whether it shall ask for a new PDN connection via PGW2?
  • the aforementioned object is accomplished by a method comprising the features of claim 1.
  • a method for supporting PDN connectivity of a mobile terminal in a mobile operator network is characterized in that the method comprises the steps of
  • said mobile terminal initiating a process for establishing an IP session with a target node with respect to an application
  • a mobile terminal comprising the features of claim 21.
  • a mobile terminal with PDN connectivity support is characterized in that said mobile terminal comprises means for initiating a process for establishing an IP session with a target node with respect to an application of a particular type, wherein said mobile terminal is equipped with a logic adapted to performing a decision process in which a suitable anchor point for establishing a PDN connection for said IP session is selected by taking into consideration at least one of application type information and E2E connection information according to configurable selection rules.
  • E2E end-to-end
  • application type information within a data anchor gateway selection process.
  • E2E connection and application type is reflected in anchor point selection.
  • certain functionalities e.g. content caches
  • services e.g. machine-to-machine, M2M
  • PDN GWs specific data anchor gateways
  • the application type gives an indication how critical the selection of a more optimal anchor point really is. In some cases, e.g. when the load on a candidate anchor point is already above a critical threshold, it might be more advisable to leave its remaining resources to more sensitive applications, and stick to the current anchor or choose a second-best one for the session under consideration.
  • the mobile terminal only selects the PDN connection.
  • the network e.g. MME
  • selects the anchor point in particular based on an APN provided by the mobile terminal when establishing a new PDN connection.
  • the present invention enables mobile communications via optimal data anchor gateways.
  • Optimality of the data anchor gateways is based on load balancing, geographical and/or topological proximity not only of the mobile node to the data anchor gateways but also vis-a-vis the whole end-to-end connection, and/or the application type.
  • E2E connection and/or application type-oriented smart selection of data anchor gateways efficient usage of the network resources will be achieved.
  • the present invention results in E2E route optimization along with the associated energy savings.
  • the E2E connection information may include information on the location and/or IP address of the mobile terminal as well as information on the location and/or IP address of the target server.
  • the IP address of the target server may be exchanged by the corresponding URL and/or FQDN (Full Qualified Domain Name).
  • the mobile terminal decides according to configurable criteria whether to request a new PDN connection for establishing said IP session.
  • the configurable criteria may take into consideration at least one of application type information and information regarding the target node's location.
  • the mobile terminal may run a logic that decides whether the mobile terminal should consult MME, DNS, ANDSF (Access Network Discovery and Selection Function) or any other relevant node in the mobile core network for a new PDN connection to establish the new IP session with the target node. Triggers for this logic could be, e.g., the range of the target node's IP address, content size, application/service type (e.g., video), application running time/service duration, location and/or time difference (compared to the currently existing PDN connection set), etc.
  • MME Mobility Management Entity
  • DNS Global System for Mobile communications
  • ANDSF Access Network Discovery and Selection Function
  • the application type itself could be represented in multiple ways, for example, but not limited to any of MIME (Multipurpose Internet Mail Extensions) type, server URL and/or domain name, and/or a target node's IP/network address and/or transport protocol type and ports, or even an application ID as currently being discussed and defined in the ongoing 3GPP Work Item on "Data Identification in Access Network Discovery and Selection Function (ANDSF)" (DIDA) [3GPP TR 23.855].
  • the important issue here is that the application type must reveal enough information for the anchor point selection process. For example, a target server domain name such as 'facebook.com' does not say much about the requested content, as Facebook hosts many media types.
  • a MIME type such as application/video does not allow to judge whether the requested video will be cached in the operator network or not, i.e. whether an anchor point with cache support is preferable or not.
  • Embodiments of the present invention can benefit from the outcome of the DIDA WID and other relevant work attempting to define unique identifiers for known and widely used applications.
  • a mobile terminal can be pre-configured with a list of such application names mapped to unique application IDs. This list could be regularly updated by the network via one or more suitable nodes such as ANDSF.
  • ANDSF suitable nodes
  • the mobile terminal in case it decides to request a new PDN connection for establishing the IP session, it transmits at least one of application type information and E2E connection information, in particular the target node's IP address, towards the mobile core network, in particular to a mobility management entity MME.
  • the mobile core network in particular a mobility management entity MME, may indicate information on the location of the target node, application type information and/or information on anchor points currently used by the mobile terminal within an APN query sent to a DNS server.
  • an entity within the mobile core network in particular a DNS server, MME or ANDSF determines an optimal APN or anchor point for the mobile terminal according to configurable criteria based on information received within the APN query or within a PDN connection request.
  • the DNS reply's TTL value is chosen to be smaller than a configurable threshold value. This proves to be beneficial since the higher a TTL value the higher is the chance that the mobile terminal is not triggered to query the DNS server (since previously resolved server names are still available in the mobile terminal's local DNS cache) and no new anchor point would be selected even though a better one might be available.
  • an optimal APN or anchor point determined by an entity within the mobile core network, in particular a DNS server may be reported to the mobile terminal or to MME within a DNS reply message.
  • a list of suitable anchor points determined by an entity within the mobile core network, in particular a DNS server may be reported to the mobile terminal within a DNS reply message, wherein the suitable anchor points are ranked according to a predefined intelligent ranking scheme (considering, for instance, load information, etc.).
  • the DNS, MME, ANDSF, or any external functions at other dedicated nodes to be interrogated by the DNS, MME or ANDSF may decide the optimal anchor point for the mobile terminal based on the IP address/location of the mobile terminal, the IP address/FQDN/location of the target node, application/MIME/service type/ID (e.g., video applications could be handled by anchor points, i.e.
  • PGWs with cache support
  • task type e.g., in case of MTC (Machine Type Communications), emergency warning, delay tolerant measurement
  • user class i.e. user can be the mobile user or the owner/operator of the target node such as MTC server
  • home zone e.g., MTC (Machine Type Communications)
  • MTC Machine Type Communications
  • emergency warning e.g., delay tolerant measurement
  • user class i.e. user can be the mobile user or the owner/operator of the target node such as MTC server
  • home zone i.e. user can be the mobile user or the owner/operator of the target node such as MTC server
  • the mobile core network may reject any PDN connectivity request initiated by the mobile terminal. More specifically, the mobile core network may send a Request Reject message in response to a mobile terminal-initiated PDN connectivity request specifying the cause and indicating to the mobile terminal to establish the IP session to the target node via the current data anchor gateway.
  • the DNS servers and/or ANDSFs provided in the mobile core network are configured to find out from the mobile terminal's IP address the current location of the mobile terminal and/or the anchor point currently being used by the mobile terminal.
  • DNS servers and/or ANDSFs provided in the mobile core network may be equipped with some intelligence adapted to infer the application type/ID from well-known domain names, URLs, e.g., video for www.youtube.com, IP subnetwork and/or transport protocol/ports.
  • a DNS server may indicate to the mobile terminal in the DNS reply message to establish the IP session with the target node via another anchor point than the anchor point currently being used by said mobile terminal.
  • the DNS server may insert a FLAG or the APN via which a more optimal anchor point can be reached in the DNS reply.
  • the mobile terminal may ignore and dismiss the indication in case of conflicting information from the application layer.
  • the application layer could indicate that the IP session is going to be short.
  • the mobile terminal may "overrule" the proposal from the mobile core network and may continue to use the existing PDN connection also for the establishment of the IP session with the target server.
  • the mobile terminal may be provided a priori with operator policies that it refers to in order to decide, which APN to use for PDN connectivity to access a specific range of IP servers, to launch a particular application type, and/or to carry out a specific task.
  • Fig. 1 is a schematic view of a mobile operator network illustrating the problem underlying the present invention
  • Fig. 2 is a diagram showing the message exchange flow of an anchor point selection process in accordance with an embodiment of the present invention
  • Fig. 3 is a flow diagram of a logic run by the mobile terminal for deciding on the issuance of a new PDN connection request in accordance with an embodiment of the present invention
  • Fig. 4 is a diagram showing the message exchange flow of an anchor point selection process in accordance with a further embodiment of the present invention
  • Fig. 5 is a diagram showing the message exchange flow of an anchor point selection process in accordance with a still further embodiment of the present invention.
  • the embodiments of the present invention described hereinafter in connection with Figs. 2-5 are based on two main assumptions.
  • data anchor gateways such as Packet Data Network - PDN GW in case of the Evolved Packet System (EPS)
  • EPS Evolved Packet System
  • mobile terminals are capable of establishing multiple connections via different data anchor gateways, i.e., mobile terminals supporting multiple access point names (APNs) in 3GPP networks, and that is via the same or different wireless access technologies.
  • APNs access point names
  • UE 1 has an ongoing PDN connection via current PGW1 .
  • UE 1 wants to connect to a target server 2 identified with a URL, which is assumed to be www.server.com, and an IP address, which is assumed to be IP@.
  • a different PGW, PGW2 is assumed to be optimal for establishing the connection between the UE 1 and the target server 2.
  • UE 1 sends a query to a name resolution server indicating the target server's 2 URL.
  • a name resolution server a DNS server 3 is assumed in the present as well as in the following embodiments.
  • the name resolution (i.e. DNS) server 3 provides the IP address of the target server 2, i.e. IP@.
  • the UE 1 runs a logic that decides whether the UE 1 should consult the Mobility Management Entity MME 4 for a new PDN connection to establish the new IP session to the target server 2. In Fig. 1 , this logic is indicated by Circle 1 .
  • Triggers for this logic could be based on the range of the target server's 2 IP address, on content size, on the application type (e.g., video, email, audio, etc), on a location and/or time difference compared to the existing PDN connection(s), etc.
  • Fig. 3 illustrates an embodiment of such logic that is run by the UE 1 in order to decide whether or not to request a new PDN connection.
  • the UE in a first step the UE checks the instant of time of the last PDN connection request. In case the last PDN connection request was made less than a configurable period of time ago, the UE does not request a new PDN connection. Otherwise, the UE continues by checking the application type. If the application type fulfills certain criteria, i.e.
  • the UE continues by checking whether a common prefix of the IP address of the target server and a reference IP address (named ReferenceJP), which refers to the UE's own IP address, is smaller than a given threshold n.
  • ReferenceJP a reference IP address
  • the "ReferenceJP” is an IP address that is taken to measure the proximity of the target server's IP address to some reference in order to decide whether they are sufficiently different for a new PDN connection to make sense. If the application type does not fulfill certain criteria, i.e.
  • the UE continues by checking whether the IP address of the target server is part of certain subnets. If so, the UE requests a new PDN connection, otherwise it does not.
  • the variables "x", "a x ", "subnet/, "n”, and "ReferenceJP" are configurable.
  • the UE 1 if it decides to ask for a new PDN connection, it issues the "UE-initiated PDN connectivity Request" to the MME 4 as part of the "UE-requested PDN connectivity" procedure of 3GPP TS 23.401.
  • the UE 1 indicates the IP address of the target server 2 and/or the application type/ID to MME 4.
  • Modified information elements according to the embodiment of the present invention of Fig. 2 the additional new values/fields IP@ and application type are marked in bold, italic and underlined in Fig. 2.
  • the UE 1 could also send the URL, Fully Qualified Domain Name (FQDN), or any other known identifier of the target server 2 to the MME 4.
  • FQDN Fully Qualified Domain Name
  • MME 4 sends an APN query to DNS server 3 indicating the APN (like in the above standard) and (in addition according to the present embodiment) IP@ of the target server 2, optionally PGW1 - the current PGW (or list of PGWs) the UE 1 is connected to - and/or application type.
  • the DNS server 3 acquires a logic, indicated by Circle 2, to decide an optimal anchor point based on UE location, target server location, and/or application type. For instance, according to the logic it could be provided that, e.g., video applications are handled by PGWs with cache support.
  • the DNS server 3 inserts the new PGW, PGW2 in the present case, in the DNS reply and sends it to MME 4.
  • the MME 4 uses this information and establishes for the UE 1 the PDN connection to PGW2.
  • the procedure terminates with a request accept message as in the usual UE- requested PDN connectivity procedure (TS 23.401 , section 5.10.2).
  • the DNS server 3 may suggest a list of anchor points (different than the current PGW1 ) ranked in order of preferences following a certain intelligent ranking scheme. This ranking method could be determined by the DNS server 3 itself or could be explicitly requested/specified by the MME 4 .
  • the MME 4 follows the ordered list of suggested PGWs to select the optimal PGW for the requesting UE 1.
  • the following gives an example of a suitable logic in Circle 2 in terms of pseudocode where the "importance threshold I" can be configured and the chosen routing metric is hop count.
  • anchor : current_anchor;
  • the DNS server 3 determines all available anchor points. Then, the DNS server 3 preselects those anchor points that are suitable for a given application type. For instance, in case of a video application only those anchor points comprising content cache functionality may be preselected as suitable candidates. However, this preselection is only performed in case the "importance" of the application type exceeds a predefined threshold. In this regard, the term "importance" may refer to, e.g., certain QoS or priority requirements of the application. If, on the other hand, the applications type is below the importance threshold since, for example, the application is uncritical in terms of the above requirements (e.g.
  • the minimum distance from the UE 1 via the respective anchor point to the target server 2 is determined in terms of hop counts.
  • other routing metrics can be deployed likewise.
  • the candidate anchor point having the minimum distance is selected as anchor point for the PDN connection from the UE 1 to the target server 2.
  • TTL time-to-live
  • the DNS reply's TTL value should be reasonable small, probably in the order of minutes.
  • Another aspect to note here is that the way the above embodiment makes use of DNS is different from other "location-based" DNS resolution mechanisms as used, e.g. in CDNs like the Akamai solution. While Akamai will also dynamically resolve a server name to varying IP addresses based on the location of source and target host, the proposition according to the above embodiment does not actually resolve an end host at all.
  • an intermediate gateway i.e., PDN Gateway
  • PDN Gateway IP address of an intermediate gateway
  • Akamai determines a suitable target host, given a source host
  • a suitable intermediate anchor point/gateway is determined, given both a source and a target host (and an application type, which Akamai does not use at all).
  • Fig. 4 illustrates the flow of main messages according to another embodiment of the present invention.
  • the embodiment shown in Fig. 4 resembles the embodiment described in connection with Fig. 2 up to the point where the MME 4 sends the APN query to DNS server 3. Therefore, in order to avoid repetitions, the respective description is omitted here.
  • the MME 4 indicates only the APN.
  • the DNS seven 3 replies with a list of appropriate PGWs that are ranked, e.g., based on load information.
  • the MME 4 runs a logic to decide the optimal anchor point from the list of PGWs based on UE location, target server location, and/or application type (e.g., video applications could be handled by PGWs with cache support).
  • the network if the network decides that the PGW does not need to change, the network, namely MME 4, sends a Request Reject message in response to the UE-initiated PDN connectivity request to indicate to the UE 1 to establish the IP session to the target server 2 via the current PGW.
  • an optimal anchor point i.e. the logic represented by Circle 2 in Figs. 2 and 4
  • the MME 4 has acquired information about the different candidate anchor points' current load situation. In that case, as mentioned earlier, based on the provided application type it might decide to not select the most optimal candidate, if the latter's load has exceeded a certain threshold and is to be kept free for applications of more critical application types.
  • the MME 4 might still select a loaded anchor point, if there is a strong likelihood that additional sessions from the same UE requiring the same anchor point will follow in the future. This could be the case, for example, when a UE initially connects to a roaming partner's PLMN (e.g. in a different country) with a visited PLMN's PGW (i.e., local breakout scenario). In this situation, it is very likely that multiple future sessions will be targeted for the UE's home country, for which a different PGW, e.g. a home PLMN PGW, will be the better choice.
  • a roaming partner's PLMN e.g. in a different country
  • PGW i.e., local breakout scenario
  • the notion of a "home zone" of a UE could also directly assist in the decision whether the UE's anchor point will be in the visited or home PLMN instead of configuring this statically based on the APN only.
  • the "home zone" of a UE could be specified as an IP address range, a PLMN ID, etc.
  • Fig. 5 illustrates the flow of main messages according to still another embodiment of the present invention.
  • the UE 1 makes a DNS query indicating the URL of the target server.
  • the UE 1 may also include the current location (e.g. PGW1 ), and/or the application type (e.g. in form of an application ID), and/or its "home zone".
  • the DNS 3 may also find out from the IP address of the UE 1 its current location (i.e. PGW1 ).
  • the DNS may be equipped with some intelligence that can infer the application type/ID from well-known URLs (e.g., video for www.youtube.com).
  • DNS server 3 is assumed to a have the logic - indicated by Circle 1 in Fig. 5 - to decide what data anchor gateway is optimal for the UE 1 based on the UE location, the target server's 2 IP address, and the application/service type (i.e., if known to DNS). If the DNS server 3 - or an external function, e.g. ANDSF (Access Network Discovery and Selection Function), which has implemented the logic and which performs the anchor point selection process and provides the result to the DNS 3 - judges that the current PGW needs to be changed (e.g.
  • ANDSF Access Network Discovery and Selection Function
  • the DNS server 3 inserts a FLAG or the APN (via which the determined optimal PGW can be reached) in its reply. It shall be noted that in current DNS specifications, there are optional fields in the DNS reply messages that can be used for carrying such flag or APN.
  • the UE 1 receives FLAG (or APN) as an indication to ask for a new PGW for the specific connection to be established with target server 2. Still UE 1 can dismiss this operation if the application layer indicates otherwise, e.g., if the session is going to be short. If, however, UE 1 decides to establish a new PDN connection for the new IP session - the respective logic being indicated by Circle 2 in Fig. 5 - it issues a normal PDN connectivity request indicating the APN received from the DNS server 3 or any of the other solution variants described above. As mentioned earlier, the DNS reply's TTL value needs to be chosen carefully so that a long- lasting cache entry does not lead to the UE 1 accessing stale information which is not optimal for the current (changed) request.
  • FLAG or APN
  • Another variant to the above mentioned solutions would be by having UE 1 querying directly the ANDSF for an appropriate APN (e.g., after resolving the domain name). Following the same logic of Circle 1 at the UE 1 in Fig. 2, whenever the UE 1 sees the need for establishing a new PDN connectivity for launching a particular application, it sends a query to the ANDSF indicating the PGWs/APNs currently used by the UE 1 , the application type/ID and/or the URL/FQDN/IP address of the target server 3. The ANDSF then runs a logic similar to that of Circle 2 in Fig. 2 to sort out an adequate PGW/APN, which is communicated to the UE 1.
  • an appropriate APN e.g., after resolving the domain name
  • ANDSF proposes a new APN/PGW different from the APNs/PGWs currently used by the UE 1 , the UE 1 requests MME 4 to establish a new PDN connectivity specifying the APN recommended by the ANDSF.
  • OPIIS Operating Policies for IP Interface Selection
  • WID Wired Equivalent Privacy
  • ANDSF could also provide a priori (and optionally on a regular basis) some operator policies that indicate to the UE 1 which APN to use for PDN connectivity to a specific range of IP servers and/or application IDs/types.
  • the logic for selecting an optimal data anchor gateway can be part of the DNS, MME or ANDSF, or it can be implemented with a dedicated and external function that the MME, DNS, or ANDSF can interrogate.
  • MTC Machine Type Communications
  • the MTC device may interrogate the DNS, ANDSF, or MME (as in the above embodiments) for the best P-GW (or best MTC Interworking Function MTC-IWF as in TR 23.888) to connect to for communicating to a specific MTC server (or one MTC server out of a set of MTC servers administrated by a particular MTC user).
  • MTC Machine Type Communications
  • the MTC device may indicate the MTC user class (e.g., Golden customer), the MTC operation/task type (e.g., emergency warning or delay tolerant measurement), the MTC server location, the MTC device location, and/or other MTC-related information.
  • the node that receives the interrogation message i.e., DNS, ANDSF, MME or the like

Landscapes

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

Abstract

L'invention concerne un procédé de prise en charge de connectivité PDN (réseau de donnée par paquets) d'un terminal mobile (1) dans un réseau d'opérateur mobile, ledit terminal mobile (1) étant capable d'établir des connexions PDN par l'intermédiaire de différents points d'ancrage dans le réseau central, qui est caractérisé en ce que le procédé comprend les étapes consistant, pour ledit terminal mobile (1), à lancer un processus d'établissement d'une session IP avec un nœud cible (2) relativement à une application, et effectuer un processus de décision dans lequel un point d'ancrage approprié pour établir une connexion PDN pour ladite session IP est sélectionné par prise en considération d'informations de type d'application et/ou d'information de connexion E2E conformément à des règles de connexion configurables. En outre, un terminal mobile à prise en charge de connectivité PDN est décrit.
PCT/EP2012/072693 2011-11-15 2012-11-15 Procédé de prise en charge de connectivité pdn d'un terminal mobile et terminal mobile WO2013072403A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP11189209.7 2011-11-15
EP11189209 2011-11-15

Publications (1)

Publication Number Publication Date
WO2013072403A1 true WO2013072403A1 (fr) 2013-05-23

Family

ID=47358097

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2012/072693 WO2013072403A1 (fr) 2011-11-15 2012-11-15 Procédé de prise en charge de connectivité pdn d'un terminal mobile et terminal mobile

Country Status (1)

Country Link
WO (1) WO2013072403A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3169105A1 (fr) * 2015-11-11 2017-05-17 Vodafone GmbH Procédé, terminal mobile et élément de réseau pour établir une connexion de communication, de préférence une liaison de données et/ou ip, entre un terminal mobile dans un réseau de communication mobile et un fournisseur de services dans un réseau de communication de données
WO2017176790A1 (fr) * 2016-04-04 2017-10-12 Motorola Mobility Llc Sessions pdu ayant divers types de continuité de session
RU2776678C2 (ru) * 2017-08-15 2022-07-25 Хуавей Текнолоджиз Ко., Лтд. Способ и устройство обработки сеанса
US11540337B2 (en) 2017-08-15 2022-12-27 Huawei Technologies Co., Ltd. Session handling method and apparatus

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090047947A1 (en) * 2007-08-02 2009-02-19 Qualcomm Incorporated Dynamic gateway selection based on data service and roaming protocol
WO2009150003A1 (fr) * 2008-06-11 2009-12-17 Telefonaktiebolaget Lm Ericsson (Publ) Résolution apn optimisée

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090047947A1 (en) * 2007-08-02 2009-02-19 Qualcomm Incorporated Dynamic gateway selection based on data service and roaming protocol
WO2009150003A1 (fr) * 2008-06-11 2009-12-17 Telefonaktiebolaget Lm Ericsson (Publ) Résolution apn optimisée

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Pseudo-CR on PGW node selection based on DNS", 3GPP DRAFT; C4-080816_PCR_PGW NODE SELECTION BASED ON DNS SRV PA10, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. Jeju Island; 20080411, 11 April 2008 (2008-04-11), XP050039387 *
MARTIN SAUTER: "Communication Systems for the Mobile Information Society", 6 November 2006, JOHN WILEY & SONS, ISBN: 978-0-47-002676-2, article MARTIN SAUTER: "Chapter 2: General Packet Radio Service (GPRS)", pages: 65 - 120, XP055057094 *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3169105A1 (fr) * 2015-11-11 2017-05-17 Vodafone GmbH Procédé, terminal mobile et élément de réseau pour établir une connexion de communication, de préférence une liaison de données et/ou ip, entre un terminal mobile dans un réseau de communication mobile et un fournisseur de services dans un réseau de communication de données
WO2017176790A1 (fr) * 2016-04-04 2017-10-12 Motorola Mobility Llc Sessions pdu ayant divers types de continuité de session
KR20180127385A (ko) * 2016-04-04 2018-11-28 모토로라 모빌리티 엘엘씨 다양한 유형의 세션 연속성을 갖는 ｐｄｕ 세션
US10667181B2 (en) 2016-04-04 2020-05-26 Motorola Mobility Llc PDU sessions with various types of session continuity
EP3796739A1 (fr) * 2016-04-04 2021-03-24 Motorola Mobility LLC Sessions pdu ayant divers types de continuité de session
US11102682B2 (en) 2016-04-04 2021-08-24 Motorola Mobility Llc PDU sessions with various types of session continuity
KR102364495B1 (ko) 2016-04-04 2022-02-18 모토로라 모빌리티 엘엘씨 다양한 유형의 세션 연속성을 갖는 ｐｄｕ 세션
KR20220025255A (ko) * 2016-04-04 2022-03-03 모토로라 모빌리티 엘엘씨 다양한 유형의 세션 연속성을 갖는 ｐｄｕ 세션
KR102437915B1 (ko) 2016-04-04 2022-08-30 모토로라 모빌리티 엘엘씨 다양한 유형의 세션 연속성을 갖는 ｐｄｕ 세션
US11601852B2 (en) 2016-04-04 2023-03-07 Motorola Mobility Llc PDU sessions with various types of session continuity
RU2776678C2 (ru) * 2017-08-15 2022-07-25 Хуавей Текнолоджиз Ко., Лтд. Способ и устройство обработки сеанса
US11540337B2 (en) 2017-08-15 2022-12-27 Huawei Technologies Co., Ltd. Session handling method and apparatus

Similar Documents

Publication Publication Date Title
US11838858B2 (en) System and method for UE context and PDU session context management
JP5323861B2 (ja) ネットワーク・リソースをプールするための方法および装置
KR101346407B1 (ko) 통신 방법, 통신 과정 중의 데이터 메시지 전달 방법 및 통신 노드
EP2920937B1 (fr) Sélection de noeud de service dans un réseau de communication sur la base d'informations de serveur d'applications
US8060590B2 (en) Distance-aware service discovery mechanism for determining the availability of remote services in wireless personal area networks
US9131473B2 (en) Method, device, and communication system for establishing connection with network management system
EP2782372B1 (fr) Procédé, élément réseau et équipement utilisateur permettant de réaliser une séparation d'identifiant et d'emplacement et une attribution d'identifiant d'interface
EP2810477B1 (fr) Sélection de serveur dans un réseau de communication relativement à un usager mobile
CN103262506B (zh) 用于允许区分处置移动网络数据业务的方法和装置
US20240048524A1 (en) Distance-based selection
JP5384745B2 (ja) セルラ通信に基づいたｐ２ｐネットワークを管理する方法
JP6945296B2 (ja) ネットワークエレメントシステム
CN113785552B (zh) 会话管理功能选择
JP2023516037A (ja) エッジコンピューティングのための分散アンカーのアプリケーショントリガセットアップ
WO2015035915A1 (fr) Procédé de traitement de paquet de protocole de convergence de données par paquets, dispositif, et système de communication
CN101651588A (zh) 选择网关方法、连接建立方法及相关装置和通信系统
WO2013072403A1 (fr) Procédé de prise en charge de connectivité pdn d'un terminal mobile et terminal mobile
Taleb et al. On efficient data anchor point selection in distributed mobile networks
EP2716090B1 (fr) Procédé de transmission de données et entité de réseau local
CN102238756A (zh) 网络连接的建立方法、装置及系统
WO2014140003A1 (fr) Optimisation de trafic de couche application transporté par une connexion ip sur un réseau mobile
WO2015028057A1 (fr) Traitement de paquet dans des communications
KR20130007254A (ko) 이기종 네트워크에서의 애니캐스트 주소를 이용한 서버 접속 지원 방법 및 그 장치
Bochow et al. Internet integration

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: 12801472

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: 12801472

Country of ref document: EP

Kind code of ref document: A1