EP3524006A1 - Procédé et appareil d'entretien d'informations d'état de session d'up dans un nuage de périphérie - Google Patents

Procédé et appareil d'entretien d'informations d'état de session d'up dans un nuage de périphérie

Info

Publication number
EP3524006A1
EP3524006A1 EP16784597.3A EP16784597A EP3524006A1 EP 3524006 A1 EP3524006 A1 EP 3524006A1 EP 16784597 A EP16784597 A EP 16784597A EP 3524006 A1 EP3524006 A1 EP 3524006A1
Authority
EP
European Patent Office
Prior art keywords
handover
source
status information
target
base station
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.)
Granted
Application number
EP16784597.3A
Other languages
German (de)
English (en)
Other versions
EP3524006B1 (fr
Inventor
Hans Eriksson
Lars Westberg
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3524006A1 publication Critical patent/EP3524006A1/fr
Application granted granted Critical
Publication of EP3524006B1 publication Critical patent/EP3524006B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/30—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • Embodiments of the subject matter disclosed herein generally relate to methods and apparatuses for locally maintaining user-plane (UP) session status information needed to supply data to core-executed functions relative to a user at the cloud edge.
  • UP user-plane
  • Edge computing is a technology emerging with the ongoing evolution of mobile networks into 5G (5 th generation wireless mobile network standards).
  • Edge computing relates to placing processing and storage capabilities (referred to as the "cloud") closer to the user equipment (UE) in a mobile network.
  • the edge cloud enables locally running different types of user and system services, thereby decreasing latency and volume of data transferred across the network.
  • Applications deployed locally i.e., executed in the edge cloud for users connected at the network edge) run faster and have higher throughput than when the service endpoint is in the core network or on the Internet.
  • Ll/charging functions run in the network core but use local data, and thus must have support within the edge cloud.
  • the interfaces to Ll/charging functions are defined in 3GPP (3 rd Generation Partnership Project), a known group of standards documentation. Traffic to/from UE connected to the edge cloud may be copied and forwarded to the network device that performs LI. Information related to the UE's activity (known as logs) is provided to the charging function to enable it to generate billing information.
  • logs Information related to the UE's activity
  • LI and charging functions operate in the user-plane part of a PGW, per client, using a state record for the client using UE.
  • a client has a network subscription and accesses the network using his credentials via UE (i.e., the physical device).
  • UE i.e., the physical device
  • UE as a physical device may be used by different clients.
  • the term "UE” and the terms "client” or “user” in this document mean a network subscriber using the physical device to log into the network, uniquely identified by the network core.
  • the state records of clients are stored in state tables, which are updated to reflect the actual state.
  • the PGW is may be implemented as a split user-plane/control-plane architecture as exemplary illustrated in Figure 1.
  • UE 1 10 accesses the network via base station 120, and uses various applications executed in the edge cloud, via user-plane gateway (UP-GW) 130.
  • Traffic break-out (TBO) function 140 splits user-plane traffic (represented by a continuous line) into edge traffic and traffic to the network core. Dashed lines in Figure 1 represent control-plane traffic, for example, from base station 120 to MME 150.
  • the UP session status information which corresponds to content of the state tables, enables UP-GW 130 to decide whether and what type of information to forward for Ll/charging function execution.
  • SGW 155 and PGW 160 are divided into user-plane and control-plane architecture.
  • the Ll/charging functions are part of the PGW functionality.
  • PGW 160 executes the LI and charging functions for UE 1 10. If a UE is target of legal interception, then PGW 160 supplies the summoned information to the legal interception system 170.
  • the control-plane part of PGW 160 controls UP-GW 130, and is able to operate as a centralized controller for many UP-GWs that may be placed at different sites.
  • Various other functional blocks and interfaces marked in Figure 1 are described in 3GPP standards documentation and are, therefore, not detailed here.
  • the LI and charging functions are partly user-plane and partly control-plane functions.
  • the LI function targeting a user triggers user-plane copying of packets of the targeted user, which are then sent from the edge site to the network core with appended header information for further analysis.
  • the charging function may be a bucket-charging type, which requires counting bytes of the passing packets to produce a log that is sent over the charging interfaces to the billing system.
  • TBO, UP-GW and edge computing resources may be placed on a hub 200, which is physically close to plural cells 210, at a network edge site.
  • Functions executed at the core-network site 220 communicate with the hub via S1 -type interfaces in the control-plane (CP) and the user-plane (UP) respectively (i.e., S1 -UP and S1 -CP).
  • the cell-sites i.e., sites where antenna is placed
  • the hub-site usually includes base station and transmission aggregation functionality concentrating the backhaul transmission to several base stations providing edge computing for plural base stations.
  • the hub may include
  • router/switching for transport aggregation functionality, TBOs, cloud platform and core- network functions.
  • execution of the Ll/charging function is based on a per-client state recorded by the state records and reflected as UP session status information of an edge-connected user in the UP-GW. This information indicates the appropriate treatment of users' packets passing through a node.
  • this state is statically configured by the management interfaces of the Ll/charging function, with no mobility impacting the UE status information's storage location.
  • a problem with LI and charging functionality in the edge cloud is that a mobile UE often changes the serving base station, triggering a handover process between base stations.
  • the PWG which is fixed, provides a central anchor for the Ll/charging functions, but the UP-GW may be changed (e.g., another UP-GW for one of cells 212 or 214).
  • the UE's status information has to be relocated on a new UP-GW when UP-GW is changed during the handover. Importing such UE status information from the network core does not reliably ensure continuity of the LI and charging functions.
  • a method for maintaining UP session status information of a UE in an edge cloud includes determining that a handover of the UE has occurred, the UE having been served by a source base station before the handover, and being served by a target base station after the handover.
  • the source base station and the target base station are located at an edge site.
  • the method further includes adding a status-information-acquisition mechanism to a handover signaling chain, to trigger providing up session status information of the UE to a target gateway, which intermediates traffic between the target base station and at least one network device outside the edge cloud.
  • the UP session status information of the UE is then used by the target gateway to determine UE-related data to be reported to the at least one network device for execution of at least one function.
  • an apparatus including an interface and a data processing unit.
  • the interface is configured to receive and transmit messages related to a handover signaling chain involving a source base station and a target base station, which serve the UE before and after a handover, respectively, and at least one network device outside the edge cloud.
  • the data processing unit is configured to determine that the handover of the UE has occurred, and to initiate an status-information-acquisition mechanism inserted in the handover signaling chain to trigger obtaining UP session status information of the UE at a target gateway.
  • the UP session status information of the UE is then used by the target gateway to determine UE-related data to be reported to the at least one network device for execution of at least one function.
  • a network apparatus configured to maintain UP session status information in an edge cloud.
  • the apparatus includes a communication module configured to receive and transmit messages related to a handover signaling chain involving a source base station and a target base station, which serve an UE before and after a handover, respectively, and at least one network device outside the edge cloud.
  • Apparatus further includes a handover detection module configured to determine that the handover of the UE has occurred, and an UP session status information maintenance module configured to initiate an status-information- acquisition mechanism inserted in the handover signaling chain, to trigger obtaining UP session status information of the UE at a target gateway intermediating traffic between the target base station and the at least one network device.
  • the UP session status information of the UE is then used by the target gateway to determine UE-related data to be reported to the at least one network device for execution of at least one function.
  • Figure 1 is a functional system architecture
  • Figure 2 is illustrates the location of various functions
  • Figure 3 illustrates an S1 handover scenario
  • Figure 4 illustrates a handover signaling chain for the scenario in Figure 3, according to an embodiment
  • Figure 5 is an embodiment of a status-information-acquisition mechanism related to the handover signaling chain in Figure 4, according to an embodiment
  • Figure 6 is another embodiment of a status-information-acquisition mechanism related to the handover signaling chain in Figure 4.
  • Figure 7 is yet another embodiment of a status-information-acquisition mechanism related to the handover signaling chain in Figure 4;
  • Figure 8 illustrates another S1 handover scenario
  • Figure 9 illustrates a handover signaling chain for the scenario in Figure 8, according to another embodiment
  • Figure 10 is an embodiment of a status-information-acquisition
  • Figure 1 1 is another embodiment of a status-information-acquisition mechanism related to the handover signaling chain in Figure 9;
  • Figure 12 illustrates an X2 handover scenario
  • Figure 13 illustrates a handover signaling chain for the scenario in Figure 12, according to another embodiment
  • Figure 14 is an embodiment of a status-information-acquisition
  • Figure 15 is another embodiment of a status-information-acquisition mechanism related to the handover signaling chain in Figure 13;
  • Figure 16 illustrates an X2 handover scenario with UP_GW stand-alone function
  • Figure 17 illustrates a handover signaling chain for the scenario in Figure 16, according to an embodiment
  • Figure 18 is a flowchart of a method for maintaining UP session status information of UE in an edge cloud according to an embodiment
  • Figure 19 is a schematic diagram of an apparatus configured to maintain
  • Figure 20 is a block diagram of an apparatus according to another embodiment.
  • UP session status information (USSI) of UE is information used in the edge cloud to determine UE-related data to be reported for execution of a function at another location.
  • An example of such a function is the LI function or the charging function executed in the network core, at a central location.
  • the USSI may indicate simply an ON/OFF state for the LI.
  • the LI header may provide other information such as LI target, correlation number, a time stamp, direction, the target location, etc.
  • the USSI for the charging function may be more complex to include various charging parameters according to which the log for the UE is generated.
  • a status-information-acquisition (SIA) mechanism is added to a handover signaling chain.
  • FIG. 3 illustrates an S1 handover scenario.
  • UE 310 is served by source base station 320, which communicates via source gateway 330 with source core network (CN) instance 340.
  • CN source core network
  • UE 310 is served by target base station 350, which communicates via target gateway 360 with target CN instance 370.
  • the base stations and the gateways in Figure 3 are located at an edge site, while the CN instances and devices are at a central site.
  • the "central" qualifier applied to the site means a different location more distant from the UE than the edge site.
  • Gateways are configured to intermediate traffic between base stations at the network edge and core-network devices. The gateways probe UE traffic and generate logs for the LI and charging functions. In other words, the gateway hosts an edge-side part of a distributed Ll/charging function and supplies UE-related data to a central part of the distributed function.
  • the handover signaling chain for the S1 handover scenario in Figure 3 is illustrated in Figure 4.
  • This handover signaling chain includes messages exchanged between the source and the target base stations, the source and the target gateways, as well as the source and the target mobility management entities (MMEs) 345 and 375, which are parts of the source and target CN instances 340 and 370 (which may be located at different sites).
  • MME may conform to the definitions in current 3GPP technical documents, but it is not limited to these definitions.
  • MME in this document is a function handling the mobility management and session management functions for a UE.
  • target MME 375 upon receiving message 10 related to the access context modification, verifies whether a gateway different from the source gateway will be employed for UE 310 after the handover. If indeed a target gateway different from the source gateway will be employed after the handover, then target MME 375 triggers SIA mechanism 400 to update the USSI.
  • SIA mechanism 500 includes source MME 345 retrieving the USSI of UE 310 from source gateway 330 at 510 and 520, and providing the retrieved USSI to target gateway 360 at 530.
  • target gateway 360 may take the appropriate internal actions listed at 540 (i.e., storing the IP address of UE 310, setting the UE charging parameters and the indication of whether the Li function is active for UE 310).
  • Target gateway 360 may then send an acknowledgement to source MME 345 at 550, to continue the handover signal chain as shown in Figure 4.
  • SIA mechanism 600 includes source MME 345 requesting source gateway 330 to transfer the USSI of UE 310 to target gateway 360 at 610.
  • source gateway 330 transfers the USSI to target gateway 360 at 620.
  • target gateway 360 may take the appropriate internal actions listed at 630 (i.e., storing the IP address of UE 310, setting the UE charging parameters and the indication of whether the L! function is active for UE 310).
  • Figure 7 illustrates an alternative embodiment in which target MME 375 triggers SIA mechanism 700 combined with and at the moment when bearer
  • target MME 375 retrieves the USSI of the UE from the source gateway 330 at 710 and 720. MME 375 then provides the retrieved USSI of the UE to target gateway 360 in combination with a modify-bearer request, at 730. Target gateway 360 responds to the request at 740. Upon receiving the USSI, target gateway 360 may take the appropriate internal actions listed at 750 (i.e., storing the IP address of UE 310, setting the UE charging parameters and the indication of whether the legal interception function is active for UE 310).
  • Figure 8 illustrates another S1 handover scenario.
  • UE 810 is served by source base station 820, which communicates via source gateway 830 with CN 840.
  • UE 810 is served by target base station 850, which communicates via target gateway 860 with the same CN 840.
  • the base stations and the gateways in Figure 8 are located at an edge site, while CN 840 is at a central site.
  • SiA mechanism 1000 includes source MME 845 retrieving the USSI of UE 810 from source gateway 830 at 1010 and 1020, and providing the retrieved USSI to target gateway 860 at 1030.
  • target gateway 880 may store the IP address of UE 810, set the UE charging parameters and the indication of whether the legal interception function is active for UE 810, at 1040.
  • Target gateway 660 may then send an
  • SIA mechanism 1 100 includes source MME 845 requesting source gateway 830 to transfer the USSI of UE 810 to target gateway 860 at 1 1 10. in response to this request, source gateway 830 transfers the USSI to target gateway 860 at 1 120. Upon receiving the USSI, target gateway 860 will then store the IP address of UE 810, set the UE charging parameters and the indication of whether the Li function is active for UE 810 at 1 130.
  • Figure 12 illustrates an X2 handover scenario.
  • UE 1210 is served by source base station 1220, which communicates via source gateway 1230 with CN 1240.
  • UE 1210 is served by target base station 1250, which communicates via target gateway 1260 with CN 1240.
  • Source base station 1220 and target base station 1250 communicate via an X2 interface.
  • the base stations and the gateways in Figure 12 are located at an edge site, while the CN instance is at a central site.
  • the handover signaling chain for the X2 handover scenario in Figure 12 is illustrated in Figure 13.
  • the signaling chain is the same and the following remarks remain valid whether or not distinct source and target CN instances are involved.
  • the handover preparation and execution takes place directly between source base station 1220 and target base station 1250 via the X2 interface. During the handover
  • MME 1245 upon receiving a path-switch request, triggers SIA mechanism 1300 to update the USSI of UE 1210 if indeed a target gateway different from the source gateway is employed.
  • S!A mechanism 1400 includes MME 1245 retrieving the USSI of UE 1210 from source gateway 1230 at 1410 and 1420, and providing the retrieved USSI to target gateway 1280 at 1430.
  • target gateway 1260 may take the appropriate interna! actions listed at 1440 (i.e., storing the IP address of UE 1210, setting the UE charging parameters and the indication of whether the LI function is active for UE 1210).
  • Target gateway 1260 may then send an acknowledgement to MME 1245 at 1450 to continue the handover signal chain as shown in Figure 13.
  • SIA mechanism 1500 includes MME 1245 requesting source gateway 1230 to transfer the USSI of UE 1210 to target gateway 1260 at 1510.
  • source gateway 1230 transfers the USSI to target gateway 1260 at 1520.
  • target gateway 1260 may take the internal actions listed at 1530 (i.e., storing the IP address of UE 1210, setting the UE charging parameters and the indication of whether the LI function is active for UE 1210).
  • Source gateway 1230 may also send to MME 1245 an acknowledgement of the request at 1540.
  • Figure 16 illustrates an X2 handover scenario with UP_GW stand-alone function.
  • UE 1610 Before the handover, UE 1610 is served by source base station 1620, which communicates via source gateway 1630 with communication network CN 1640. After the handover, UE 1610 is served by target base station 1650, which communicates via target gateway 1660 with CN 1640.
  • the base stations and the gateways in Figure 16 are located at an edge site, while the CN is at a central site.
  • target base station 1650 sends a handover trigger to target gateway 1660.
  • the target gateway determines that the handover has occurred and requests source gateway 1630 to transfer the USSI of UE 1610 at 1710.
  • target gateway 1660 stores the IP address of UE 1610, and sets its charge parameters and the indication of whether the LI function is active for UE 1610, at 1730.
  • Target gateway 1660 then acknowledges the handover trigger at 1740. In this case, the USSI information is relocated without employing MME 1645.
  • Figure 18 is a flowchart of a method 1800 for effectively maintaining USSI information of UE connected to an edge cloud.
  • the method is effective in the sense that interruptions in the operation of distributed functions are avoided.
  • Method 1800 includes determining that a handover of the user equipment has occurred. That is, the UE was served by a source base station before the handover, and is served by a target base station after the handover, with the source and target base stations located at an edge site at S1830.
  • Method 1800 further includes adding an SIA mechanism to a handover signaling chain to trigger providing USSI of the UE to a target gateway at 1820.
  • the target gateway intermediates traffic between the target base station and a core network device.
  • the USSi of the UE is then used by the target gateway to determine UE-related data to be reported for execution of at least one function in the network core.
  • UE and at least some base stations using the edge cloud are at cell-sites distinct from the hub-site hosting the edge cloud's processing and memory resources.
  • the MMEs are also outside the edge cloud. Although a typical deployment would not have the MME executed in the Edge Cloud, having MME executed in one of the Edge clouds is foreseeable.
  • FIG 19 is a schematic diagram of an apparatus 1900 according to an embodiment.
  • Apparatus 1900 includes a communication interface 1910 and a processing unit 1920.
  • the communication interface is configured to receive and transmit messages related to a handover signaling chain involving a source base station and a target base station, which serve the UE before and after a handover, respectively, and a network device outside the edge cloud.
  • Data processing unit 1920 is configured to determine that the handover of the UE has occurred, and to initiate a status- information-acquisition mechanism inserted in the handover signaling chain to trigger obtaining UP session status information of the UE at a gateway (which uses the UP session status information of the UE to determine UE-related data to be reported to the at least one network device for execution of at least one function after the handover).
  • the data processing unit may also be configured to perform an MME function before or after the handover, and/or to manage UE ! s traffic.
  • Apparatus 1900 may also include a memory 1940 and an operator interface 1930.
  • the memory may store executable codes which, when executed by the processing unit, make the processing unit perform any of the methods described in this section.
  • FIG 20 is a block diagram of an apparatus 2000 according to another embodiment.
  • Apparatus 2000 includes a communication module 2010 configured to receive and transmit messages related to a handover signaling chain involving a source base station and a target base station, which serve UE before and after a handover, respectively, and at least one network device outside the edge cloud.
  • this module's functionality may be executed by a transceiver.
  • Apparatus 2000 further includes a handover detection module 2020 configured to determine that the handover of the UE has occurred, and a UP session status information maintenance module 2030 configured to initiate a status-information- acquisition mechanism inserted in the handover signaling chain.
  • Modules 2020 and 2030 may be implemented on one or more processors and other electronic circuits.
  • UE status information is maintained at the edge (in a target gateway intermediating traffic between the new base station and a network core device).
  • UE status information is maintained at the edge (in a target gateway intermediating traffic between the new base station and a network core device).
  • the embodiments disclosed in this section provide methods and network devices for maintaining user-plane session status information at a network edge. It should be understood that this description is not intended to limit the invention. On the contrary, the exemplary embodiments are intended to cover alternatives, modifications and equivalents, which are included in the spirit and scope of the invention. Further, in the detailed description of the exemplary embodiments, numerous specific details are set forth in order to provide a comprehensive understanding of the invention. However, one skilled in the art would understand that various embodiments may be practiced without such specific details.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés et des appareils qui entretiennent des informations d'état de session de plan d'utilisateur (UP) d'un équipement d'utilisateur dans un nuage de périphérie. Lorsqu'il est déterminé qu'un transfert d'UE au niveau d'une périphérie de réseau a eu lieu, un mécanisme d'acquisition d'informations d'état est ajouté à une chaîne de signalisation de transfert. Le mécanisme d'acquisition d'informations d'état déclenche la fourniture d'informations d'état de session d'UP de l'UE à une passerelle de destination, qui assure une intermédiation de trafic entre la station de base de destination et un dispositif de réseau à l'extérieur du nuage de périphérie. Les informations d'état de session d'UP de l'UE sont ensuite utilisées par la passerelle de destination pour déterminer des données liées à l'UE devant être rapportées au dispositif de réseau pour l'exécution d'une fonction telle qu'une interception légale (LI) ou une facturation.
EP16784597.3A 2016-10-07 2016-10-07 Méthode et appareil pour maintenir à jour les informations de l'état d'une session up dans un reseau décentralisé. Active EP3524006B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2016/050964 WO2018067049A1 (fr) 2016-10-07 2016-10-07 Procédé et appareil d'entretien d'informations d'état de session d'up dans un nuage de périphérie

Publications (2)

Publication Number Publication Date
EP3524006A1 true EP3524006A1 (fr) 2019-08-14
EP3524006B1 EP3524006B1 (fr) 2022-04-27

Family

ID=57178461

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16784597.3A Active EP3524006B1 (fr) 2016-10-07 2016-10-07 Méthode et appareil pour maintenir à jour les informations de l'état d'une session up dans un reseau décentralisé.

Country Status (4)

Country Link
US (1) US10674329B2 (fr)
EP (1) EP3524006B1 (fr)
CN (1) CN109792645B (fr)
WO (1) WO2018067049A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020011134A1 (fr) * 2018-07-09 2020-01-16 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de transmission de données
CN110290506B (zh) * 2019-04-17 2020-08-14 中国联合网络通信集团有限公司 一种边缘云移动性管理方法及设备
US11729587B1 (en) * 2021-03-22 2023-08-15 T-Mobile Usa, Inc. Dynamic relocation of account information based on mobility of wireless device

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8243679B1 (en) * 2007-12-05 2012-08-14 Sprint Communications Company L.P. Initiating a handover in a communication network
WO2014110410A1 (fr) * 2013-01-11 2014-07-17 Interdigital Patent Holdings, Inc. Gestion de congestion de plan utilisateur
KR102219415B1 (ko) * 2014-01-20 2021-02-25 삼성전자 주식회사 Lte 망에서 최적 데이터 경로를 위한 mme와 로컬 서버, 이들 간 인터페이스 및 데이터 송수신 방법
US10080163B2 (en) * 2014-07-15 2018-09-18 T-Mobile Usa, Inc. Telecommunication network pre-establishment service interruption response
CN106797555A (zh) * 2014-10-03 2017-05-31 英特尔Ip公司 切换期间的分组数据网连接建立
US10574833B2 (en) 2015-02-26 2020-02-25 Nokia Solutions And Networks Oy Charging and control of edge services
US11071032B2 (en) * 2015-03-02 2021-07-20 Corning Optical Communications LLC Gateway coordinating multiple small cell radio access networks
CN104796918B (zh) * 2015-03-17 2018-09-28 无锡北邮感知技术产业研究院有限公司 无线通信组网的方法
US10321496B2 (en) * 2015-06-03 2019-06-11 Parallel Wireless, Inc. Inter-PGW handover architecture

Also Published As

Publication number Publication date
CN109792645B (zh) 2022-01-21
US20190215665A1 (en) 2019-07-11
CN109792645A (zh) 2019-05-21
EP3524006B1 (fr) 2022-04-27
US10674329B2 (en) 2020-06-02
WO2018067049A1 (fr) 2018-04-12

Similar Documents

Publication Publication Date Title
JP6697570B2 (ja) データ伝送方法、装置及びシステム
US10375609B2 (en) Operation of a serving node in a network
US11089520B2 (en) Session migration method and device
US20200137672A1 (en) Handling a ue that is in the idle state
EP3544232B1 (fr) Procédé, dispositif et système de traitement pour anomalie de composant nf
KR20140023435A (ko) 통신 방법 및 시스템, 액세스 네트워크 장치, 및 애플리케이션 서버
EP2996388B1 (fr) Changement de cellule adapté aux communications de type machine avec transfert de données utilisant le plan de signalisation
WO2017036248A1 (fr) Procédé, dispositif, et système de transmission de données
US10630530B2 (en) Cache method, cache edge server, cache core server, and cache system
JP2010530193A (ja) アイドルモードシグナリングリダクションのための方法およびシステム
JP5566527B2 (ja) 非アクセス層（ｎａｓ）のメッセージ・トンネリング中に異常状態を通知する方法
KR20120079875A (ko) 계층적 셀 구조의 무선통신 시스템에서 게이트웨이를 이용한 기지국 간의 연동 방법 및 장치
US20220272607A1 (en) Network Access Method and Communication Apparatus
US10674329B2 (en) Method and apparatus for maintaining up session status information in an edge cloud
WO2018023222A1 (fr) Procédé et dispositif de commande d'accès réseau
JP5844735B2 (ja) 位置特定プロセス終了方法及び装置
KR20130035987A (ko) 로컬 네트워크에서 단말 이동성 지원 방법 및 장치
TW201735684A (zh) 一種資料傳輸方法及裝置
JP2018504074A (ja) 音声スイッチング方法および装置
EP3468252B1 (fr) Procédé permettant d'établir un tunnel entre des passerelles locales, et passerelle
WO2018176439A1 (fr) Procédé d'obtention d'adresse, élément de réseau ouvrant une capacité de services et élément de réseau calculant une limite mobile
JPWO2021015502A5 (fr)
WO2019154048A1 (fr) Procédé de communication dans un réseau nb-iot, appareil, et support de stockage
EP3352504A1 (fr) Procédé, passerelle et produit-programme informatique de transfert d'une session de communication
KR20150045693A (ko) 컨텐츠 전송 방법 및 이를 위한 장치

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

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

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190417

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20200907

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20220107

RIN1 Information on inventor provided before grant (corrected)

Inventor name: WESTBERG, LARS

Inventor name: ERIKSSON, HANS

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016071546

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1487946

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220515

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20220427

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1487946

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220427

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

Ref country code: NL

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

Effective date: 20220427

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

Ref country code: SE

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

Effective date: 20220427

Ref country code: PT

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

Effective date: 20220829

Ref country code: NO

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

Effective date: 20220727

Ref country code: LT

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

Effective date: 20220427

Ref country code: HR

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

Effective date: 20220427

Ref country code: GR

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

Effective date: 20220728

Ref country code: FI

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

Effective date: 20220427

Ref country code: ES

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

Effective date: 20220427

Ref country code: BG

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

Effective date: 20220727

Ref country code: AT

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

Effective date: 20220427

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

Ref country code: RS

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

Effective date: 20220427

Ref country code: PL

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

Effective date: 20220427

Ref country code: LV

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

Effective date: 20220427

Ref country code: IS

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

Effective date: 20220827

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016071546

Country of ref document: DE

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

Ref country code: SM

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

Effective date: 20220427

Ref country code: SK

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

Effective date: 20220427

Ref country code: RO

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

Effective date: 20220427

Ref country code: EE

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

Effective date: 20220427

Ref country code: DK

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

Effective date: 20220427

Ref country code: CZ

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

Effective date: 20220427

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

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

Ref country code: AL

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

Effective date: 20220427

26N No opposition filed

Effective date: 20230130

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

Ref country code: SI

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

Effective date: 20220427

Ref country code: MC

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

Effective date: 20220427

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20221031

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

Ref country code: LU

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

Effective date: 20221007

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

Ref country code: LI

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

Effective date: 20221031

Ref country code: FR

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

Effective date: 20221031

Ref country code: CH

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

Effective date: 20221031

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

Ref country code: BE

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

Effective date: 20221031

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

Ref country code: IE

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

Effective date: 20221007

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

Ref country code: GB

Payment date: 20231027

Year of fee payment: 8

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

Ref country code: IT

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

Effective date: 20220427

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

Ref country code: DE

Payment date: 20231027

Year of fee payment: 8

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

Ref country code: HU

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

Effective date: 20161007

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

Ref country code: CY

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

Effective date: 20220427