WO2012146129A1 - Procédé et système de gestion de support, et point d'ancrage prenant en charge l'accès multiple - Google Patents

Procédé et système de gestion de support, et point d'ancrage prenant en charge l'accès multiple Download PDF

Info

Publication number
WO2012146129A1
WO2012146129A1 PCT/CN2012/073839 CN2012073839W WO2012146129A1 WO 2012146129 A1 WO2012146129 A1 WO 2012146129A1 CN 2012073839 W CN2012073839 W CN 2012073839W WO 2012146129 A1 WO2012146129 A1 WO 2012146129A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
rat type
core network
network gateway
update
Prior art date
Application number
PCT/CN2012/073839
Other languages
English (en)
Chinese (zh)
Inventor
卢飞
梁爽
宗在峰
周晓云
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012146129A1 publication Critical patent/WO2012146129A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/81—Dynamic pricing, e.g. change of tariff during call

Definitions

  • the present invention relates to bearer management technologies in the field of mobile communications, and in particular, to a bearer management method, system and anchor point supporting multiple access. Background technique
  • the EPS mainly includes the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and the Evolved Packet Core (EPC).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • EPC Evolved Packet Core
  • the system's EPC is capable of supporting users' access from the GSM EDGE Radio Access Network (GERAN) and the Universal Terrestrial Radio Access Network (UTRAN).
  • GSM GSM EDGE Radio Access Network
  • UTRAN Universal Terrestrial Radio Access Network
  • the EPC packet core network includes a Home Subscriber Server (HSS), a Mobility Management Entity (MME), a Serving Gateway (SGW), and a Packet Data Network Gateway (PGW, PDN). Gateway), Serving GPRS Support Node (SGSN) and Policy and Charging Enforcement Function (PCRF) entities, where:
  • the HSS/Home Location Register (HLR) is the permanent storage location for user subscription data. It is located in the home network to which the subscriber is contracted and is the primary user database supporting the call/session.
  • the MME is the location where the subscriber subscription data is stored in the current network, and is responsible for the non-access stratum (NAS, Non-Access Stratum) signaling management of the user equipment (UE) to the network, and the tracking and paging management functions and bearers in the user idle mode. management;
  • the SGW is the gateway of the core network to the wireless system, and is responsible for the user plane bearer of the UE to the core network.
  • the PGW is the gateway of the EPS and the external network of the system, and is responsible for the functions of the UE's IP address allocation, billing function, packet filtering, and policy application.
  • the SGSN is a service support point for GERAN and UTRAN users to access the EPC network.
  • the specific functions are similar to those of the MME. They are responsible for the location update, paging management, and bearer management functions of the UE.
  • the GPRS Gateway Support Node supports the edge routing function of the GPRS network. That is, the GGSN is responsible for routing and forwarding data of the GPRS network, and protecting the integrity of the GPRS network data through the firewall and filtering functions. In addition, the GGSN also has a billing function.
  • the PGW may include all the functions of the GGSN, and the GGSN may be considered as a sub-function of the PGW and embedded in the PGW. Therefore, the SGSN can connect directly to the PGW and use the Gn/Gp interface.
  • Dual-mode or tri-mode UEs can access the network through GERAN/UTRAN/EUTRAN, and need to register separately when accessing different networks.
  • the UE simultaneously aggregates to the SGW-PGW through the Radio Network Controller (RNC)-SGSN and the eNodeB-MME access; as shown in FIG. 2, the UE simultaneously accesses and aggregates to the RNC through the NodeB and the eNodeB, and The RNC is directly connected to the SGSN-SGW-PGW.
  • Both the SGW and the PGW can perform differential charging according to different RAT types. Since the current single access system does not have multiple RATs of the UE and different RAT types, it does not appear in bearer management such as bearer establishment and modification. In the process, the gateway does not know the RAT type of the bearer. However, in a multiple access system, multiple bearers of a UE will have different RAT types. In the process of bearer management such as bearer establishment and modification, the current gateway cannot know the RAT type of the bearer, and thus cannot accurately perform the UE. Differential billing, billing is not accurate. Summary of the invention
  • the main purpose of the present invention is to provide a bearer management method, system, and anchor point that support multiple access, so that the core network gateway knows the RAT type of the bearer, and performs accurate differential charging according to the RAT type.
  • the present invention provides a bearer management method for supporting multiple access, the method includes: in a bearer management process, an anchor point determines a RAT type that a bearer establishes or updates, and in a bearer setup or update process, the RAT type Notify the core network gateway.
  • the anchor point determines that the RAT type of the bearer establishment or update is: the anchor point determines the RAT type of the bearer establishment or update according to the preset local policy.
  • the local policy is based on radio base station signal quality and/or radio base station load.
  • the RAT type is notified to the core network gateway, that is: in the process of establishing or updating, the anchor point is carried in a bearer setup response message returned to the core network gateway.
  • the RAT type, or the bearer update response message returned to the core network gateway carries the RAT type, or carries the RAT type in the Radio Access Bearer (RAB) assignment response message sent to the core network gateway.
  • RAB Radio Access Bearer
  • the method further includes: the core network gateway performing differential charging according to the type of the RAT carried.
  • the invention provides a bearer management system supporting multiple access, the system comprising: an anchor point, Core network gateway; among them,
  • the anchor point is used to determine a RAT type of a bearer establishment or update in a bearer management process, and notify the core network gateway of the RAT type in a bearer setup or update process;
  • the core network gateway is configured to obtain a RAT type of the bearer.
  • the anchor point includes: a RAT type determining module, a notification module, where the RAT type determining module is configured to determine, in the bearer management process, a RAT type that is established or updated by the bearer;
  • the notification module is configured to notify the core network gateway of the RAT type determined by the RAT type determining module during the bearer setup or update process.
  • the RAT type determining module is specifically configured to determine, according to a preset local policy, a RAT type that is established or updated by the bearer in the bearer management process.
  • the notification module is specifically configured to carry the RAT type in the bearer setup response message returned to the core network gateway in the bearer setup or update process, or in the bearer update response message returned to the core network gateway.
  • the RAT type is carried in the RAB assignment response message carrying the RAT type or in the core network gateway.
  • the core network gateway is further configured to perform differential charging according to the RAT type of the bearer.
  • An anchor point provided by the present invention includes: a RAT type determining module and a notification module; wherein
  • a RAT type determining module configured to determine, in a bearer management process, a RAT type of a bearer establishment or update
  • the notification module is configured to notify the core network gateway of the RAT type determined by the RAT type determining module during the bearer setup or update process.
  • the invention provides a bearer management method, system and anchor point supporting multiple access.
  • the anchor point determines the RAT type of the bearer establishment or update, and is established in the bearer or During the update process, the RAT type is notified to the core network gateway. In this way, the core network gateway can learn the RAT type of the bearer, and can perform accurate differential charging according to the RAT type to avoid the problem of inaccurate charging.
  • 1 is a system architecture for supporting UEs to access and register at multiple RATs simultaneously in the prior art
  • 2 is another system architecture for supporting UEs to access and register simultaneously in multiple RATs in the prior art
  • FIG. 3 is a schematic flowchart of a bearer management method for supporting multiple access according to the present invention
  • FIG. 4 is a schematic structural diagram of a bearer management system supporting multiple access according to the present invention
  • FIG. 6 is a schematic flowchart of a method for implementing bearer management for supporting multiple access according to Embodiment 2 of the present invention
  • FIG. 7 is a schematic diagram of a bearer management method for supporting multiple access according to Embodiment 3 of the present invention
  • FIG. 8 is a schematic flowchart of a bearer management method for supporting multiple access according to Embodiment 4 of the present invention.
  • the anchor point determines the RAT type of the bearer establishment or update, and notifies the core network gateway of the RAT type in the bearer setup or update process.
  • the anchor point is used to aggregate network elements of each RAT type in a multiple access system, as shown in the figure.
  • the RAT type includes: an LTE system, a GERAN system, a UTRAN system, and the like.
  • the present invention implements a bearer management method supporting multiple access. As shown in FIG. 3, the method includes the following steps: Step 101: In the bearer management process, the anchor point determines the RAT type that the bearer establishes or updates;
  • the anchor point determines the RAT type of the bearer establishment or update according to the preset local policy; the local policy is based on the signal quality of the radio base station and/or the load of the radio base station; for example, the local policy is selected.
  • the radio base station has the best signal quality, and/or the RAT type with the lightest load on the radio base station establishes or updates the bearer.
  • Step 102 The anchor point notifies the core network gateway of the RAT type during the bearer setup or update process;
  • the anchor point carries the RAT type in the bearer setup response message returned to the core network gateway, or carries the RAT type in the bearer update response message returned to the core network gateway, or
  • the RAB assignment response message sent to the core network gateway carries the RAT type and the like.
  • the carrying may be to add a field indicating the RAT type or an identifier indicating the RAT type in the message body, such as the identifier L indicates the LTE system, the identifier G indicates the GERAN system, the identifier U indicates the UTRAN system, and the like.
  • the foregoing method further includes the step 103: the core network gateway performs differential charging according to the RAT type of the bearer, for example, the core network gateway performs different standard charging for the LTE system, the UTRAN, and the GERAN system.
  • the present invention further provides a bearer management system supporting multiple access.
  • the system includes: an anchor point 41, and a core network gateway 42;
  • the anchor point 41 is configured to determine, in a bearer management process, a RAT type that is established or updated by a bearer, and notify the core network gateway 42 of the RAT type in a bearer setup or update process; Obtaining a RAT type of the bearer according to the notification of the anchor point 41;
  • the anchor point 41 includes: a RAT type determining module 411, a notification module 412; a RAT type determining module 411, configured to determine, in a bearer management process, a RAT type of a bearer establishment or update;
  • the notification module 412 is configured to notify the core network gateway 42 of the RAT type determined by the RAT type determining module 411 during the bearer setup or update process;
  • the RAT type determining module 411 is specifically configured to determine, according to a preset local policy, a RAT type of a bearer establishment or update in a bearer management process;
  • the notification module 412 is specifically configured to carry the RAT type in the bearer setup response message returned to the core network gateway 42 or carry the bearer update response message returned to the core network gateway 42 in the bearer setup or update process.
  • the RAT type, or the RAB assignment response message sent to the core network gateway 42 carries the RAT type and the like;
  • the core network gateway 42 is further configured to perform differential charging according to the type of the RAT of the bearer.
  • the present invention also provides an anchor point.
  • the anchor point 41 includes: a RAT type determining module 411, a notification module 412, where
  • the RAT type determining module 411 is configured to determine, in the bearer management process, a RAT type that is established or updated by the bearer;
  • the notification module 412 is configured to notify the core network gateway 42 of the RAT type determined by the RAT type determining module 411 during the bearer setup or update process;
  • the RAT type determining module 411 is specifically configured to determine, according to a preset local policy, a RAT type of a bearer establishment or update in a bearer management process;
  • the notification module 412 is specifically configured to carry the RAT type in the bearer setup response message returned to the core network gateway 42 or carry the bearer update response message returned to the core network gateway 42 in the bearer setup or update process.
  • the RAT type, or the RAB assignment response message sent to the core network gateway 42 carries the RAT type and the like.
  • Embodiment 1 This embodiment is based on the system architecture shown in FIG. 1 , and the SGW is used as an anchor point to implement a bearer management method supporting multiple access. As shown in FIG. 5 , the method includes the following steps:
  • Step 501 The PGW sends a bearer setup request message to the SGW, where the message carries the uplink user plane IP address of the PGW and the tunnel endpoint identifier (TEID, Tunnel Endpoint Identifier).
  • Step 502 The SGW receives the bearer setup request message, and determines according to the local policy.
  • the bearer established RAT type is an LTE system, and the SGW sends a bearer setup request message to the MME, and carries the uplink user plane IP address and TEID of the PGW, the uplink user plane IP address and the TEID of the SGW;
  • Step 503 The MME receives the bearer setup request message of the SGW, establishes a bearer and allocates an EPS bearer identifier (EBI, EPS Bearer ID), and the MME establishes a session management request message, where the message carries the EBI and the quality of service (QoS, Quality of Service) And the MME sends a bearer setup request message to the eNodeB, where the message carries the session management request message, the EBI, the bearer QoS, the uplink user plane IP address of the SGW, and the TEID;
  • EBI EPS bearer identifier
  • QoS Quality of Service
  • Step 504 The eNodeB receives the bearer setup request message of the MME, and sends a radio resource connection (RRC) reconfiguration message to the UE, where the message carries the radio bearer QoS, the radio bearer ID, and the session management request message.
  • RRC radio resource connection
  • Step 505 The UE returns an RRC reconfiguration complete message to the eNodeB.
  • Step 506 The eNodeB returns a bearer setup response message to the MME, where the message carries the bearer ID, the downlink IP address of the eNodeB, and the TEID.
  • Step 507 the UE non-access stratum establishes a session management response message, and delivers the message to the eNodeB through a direct transmission message;
  • Step 508 The eNodeB delivers the session management message to the MME by using the uplink direct transmission message.
  • Step 510 The SGW returns a bearer setup response message to the PGW, where the message carries the EBI, The downlink IP address and TEID of the SGW, and the RAT type;
  • the RAT type is a LET system.
  • Step 511 The PGW learns the RAT type of the bearer according to the bearer setup response message returned by the SGW.
  • step 502 if the SGW determines that the RAT type of the bearer establishment is a UTRAN or GERAN system, the method for establishing a bearer in the UTRAN system or the GERAN system is similar to the foregoing method, and details are not described herein again.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • This embodiment is based on the system architecture shown in FIG. 1, and the SGW is used as an anchor point to implement a bearer management method supporting multiple access. As shown in FIG. 6, the method includes the following steps:
  • Step 601 The PGW sends a bearer update request to the SGW.
  • Step 602 The SGW receives the bearer update request, and determines that the RAT type of the bearer update is an LTE system according to the local policy, that is, the bearer is migrated from the UTRAN system or the GERAN system to the LTE system, and the SGW sends a bearer setup request message to the MME, where the message carries The upstream user plane IP address and TEID of the PGW, the uplink user plane IP address of the SGW, and the TEID;
  • Step 603 The MME receives the bearer setup request message of the SGW, establishes a bearer and allocates an EBI, and the MME establishes a session management request message, where the message carries the EBI, the QoS, and the MME, and sends a bearer setup request message to the eNodeB, where the message carries the session management.
  • Step 604 The eNodeB receives the MME reconfiguration request message, and sends an RRC reconfiguration message to the UE, where the message carries the radio bearer QoS, the radio bearer ID, and the session management request elimination step 605, and the UE returns an RRC reconfiguration complete message to the eNodeB.
  • Step 606 The eNodeB returns a bearer setup response message to the MME, where the message carries the bearer ID, the downlink IP address of the eNodeB, and the TEID.
  • Step 607 The UE non-access stratum establishes a session management response message, and delivers the message to the eNodeB through the uplink direct transmission message.
  • Step 608 The eNodeB delivers the session management message to the MME by using the uplink direct transmission message.
  • Step 610 The SGW returns a bearer update response message to the PGW, where the message carries a RAT type.
  • the RAT type is an LTE system.
  • the SGW may notify the PGW of the RAT type by using other messages returned to the PGW in step 610;
  • the SGW decides to migrate the UTRAN or the GERAN system to the LTE system, the SGW also needs to release the processing of the bearer of the UTRAN or the GERAN system, and the specific steps include steps 611-616;
  • Step 611 The SGW sends a bearer release request to the SGSN.
  • Step 612 The SGSN sends an RAB assignment request message for requesting the RNC to release the bearer to the RNC.
  • Step 613 After receiving the RAB assignment request message, the RNC sends a radio bearer release request message to the UE.
  • Step 614 After receiving the radio bearer release request message, the UE sends a radio bearer release response message to the RNC.
  • Step 615 The RNC returns an RAB assignment response message to the SGSN.
  • Step 616 The SGSN returns a release response message to the SGW.
  • step 602 if the SGW determines that the RAT type of the bearer update is a UTRAN or GERAN system, and the bearer is to be migrated from the LTE system to the UTRAN or GERAN system, the method of updating the bearer to the UTRAN or GERAN system is similar to the above method, and is no longer Narration.
  • Embodiment 3
  • This embodiment is based on the system architecture shown in FIG. 2, and the RNC is used as an anchor point to implement a bearer management method supporting multiple access. As shown in FIG. 7, the method includes the following steps:
  • Step 701 The PGW sends a bearer setup request message to the SGW, where the message carries the uplink user plane IP address and the TEID of the PGW.
  • Step 702 The SGW receives the bearer setup request message, and sends a bearer setup request message to the SGSN, where the message carries the uplink user plane IP address of the PGW, the TEID, the uplink user plane IP address of the SGW, and the TEID.
  • Step 703 After receiving the bearer setup request message, the SGSN sends an RAB assignment request message to the RNC, where the message carries the uplink user plane IP address and TEID of the SGSN.
  • Step 704 After receiving the bearer setup request message of the SGSN, the RNC determines, according to the local policy, that the RAT type of the bearer setup is the LTE system, the RNC sends a bearer setup request message to the eNodeB, and carries the uplink user plane IP address and the TEID of the eNodeB.
  • Step 705 The eNodeB sends an RRC reconfiguration message to the UE, where the message carries the radio bearer.
  • Step 706 The UE sends an RRC reconfiguration complete message to the eNodeB.
  • Step 707 The eNodeB sends a bearer setup response message to the RNC, where the message carries the bearer ID, the downlink user plane IP address of the eNodeB, and the TEID.
  • Step 708 The RNC sends an RAB assignment response message to the SGSN, where the message carries the bearer ID, the downlink user plane IP address of the RNC, the TEID, and the RAT type.
  • the RAT type is a LET system.
  • Step 709 The SGSN sends a bearer setup response message to the SGW, where the message carries the bearer ID, the downlink user plane IP address of the SGSN, the TEID, and the RAT type.
  • Step 710 The SGW sends a bearer setup response message to the PGW, where the message carries the bearer ID, the downlink user plane IP address of the SGW, and the TEID and RAT type.
  • the RNC determines that the RAT type of the bearer establishment is a UTRAN or a GERAN system, the method for establishing a bearer in the UTRAN system or the GERAN system is similar to the foregoing method, and details are not described herein again.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • This embodiment is based on the system architecture shown in FIG. 2, and the RNC is used as an anchor point to implement a bearer management method supporting multiple access. As shown in FIG. 8, the method includes the following steps:
  • Step 801 The PGW sends a bearer update request to the SGW.
  • Step 802 The SGW sends a bearer update request to the SGSN.
  • Step 803 The SGSN sends an RAB Assignment Request message to the RNC to request to update the bearer.
  • Step 805 The eNodeB sends an RRC reconfiguration message to the UE, where the message carries the bearer QoS.
  • Step 806 The UE sends an RRC reconfiguration complete message to the eNodeB.
  • Step 807 The eNodeB sends a bearer setup response message to the RNC, where the message carries the bearer ID, the downlink user plane IP address of the eNodeB, and the TEID.
  • Step 808 The RNC sends an RAB assignment response message to the SGSN, where the message carries a RAT type.
  • Step 809 the SGSN returns a bearer update response message to the SGW, where the message carries a RAT type;
  • Step 810 The SGW returns a bearer update response message to the PGW, where the message carries a RAT type.
  • the steps are 808-810 may notify the SGSN, the SGW, and the PGW by using other notification messages;
  • Step 811 the RNC sends a bearer release request message to the NodeB, requesting to release the bearer in the UTRAN or GERAN system;
  • Step 812 The NodeB sends a radio bearer release request message to the UE.
  • Step 813 The UE returns a radio bearer release response message to the NodeB.
  • step 814 the NodeB returns a release response message to the RNC.
  • step 804 if the RNC determines that the RAT type of the bearer update is UTRAN or GERAN, and the bearer is to be migrated from the LTE system to the UTRAN or GERAN system, the method of updating the bearer to the UTRAN or GERAN system is similar to the above method, and is no longer Narration.
  • the core network gateway can know the RAT type of the bearer, and can perform accurate differential charging according to the RAT type, thereby avoiding the problem of inaccurate charging.

Abstract

La présente invention concerne un procédé de gestion de support prenant en charge l'accès multiple. Un point d'ancrage détermine un type de technologie d'accès radio (RAT) pour la configuration ou la mise à jour du support dans une procédure de gestion de support, et indique le type de RAT à une passerelle de réseau central dans une procédure de configuration ou de mise à jour de support. L'invention concerne également un système de gestion de support et un point d'ancrage prenant en charge l'accès multiple. Grâce aux solutions de la présente invention, la passerelle de réseau central peut acquérir un type de RAT d'un support et effectuer une taxation différenciée précise selon le type de RAT, de façon à éviter le problème de taxation inexacte.
PCT/CN2012/073839 2011-04-28 2012-04-11 Procédé et système de gestion de support, et point d'ancrage prenant en charge l'accès multiple WO2012146129A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110108998.3A CN102761958B (zh) 2011-04-28 2011-04-28 一种支持多接入的承载管理方法和系统
CN201110108998.3 2011-04-28

Publications (1)

Publication Number Publication Date
WO2012146129A1 true WO2012146129A1 (fr) 2012-11-01

Family

ID=47056246

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/073839 WO2012146129A1 (fr) 2011-04-28 2012-04-11 Procédé et système de gestion de support, et point d'ancrage prenant en charge l'accès multiple

Country Status (2)

Country Link
CN (1) CN102761958B (fr)
WO (1) WO2012146129A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110337150B (zh) * 2014-04-21 2023-06-27 华为技术有限公司 承载控制方法及系统
CN110890967B (zh) * 2018-09-11 2022-11-08 中国移动通信有限公司研究院 一种计费处理方法、网元及网络系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127629A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 通信系统中策略与计费执行设备、在线计费系统及方法
CN101765223A (zh) * 2008-12-25 2010-06-30 中国移动通信集团公司 业务控制设备获得用户接入类型的方法、sgsn和系统
WO2010079715A1 (fr) * 2009-01-06 2010-07-15 シャープ株式会社 SYSTÈME DE COMMUNICATION MOBILE, STATION DE CONTRÔLE QoS, ET STATION MOBILE
CN101841797A (zh) * 2009-03-21 2010-09-22 中兴通讯股份有限公司 一种终端通过多接入网接入的计费方法和系统及上报方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127652B (zh) * 2006-08-17 2011-04-27 华为技术有限公司 一种确定用户终端访问外部网络锚点的方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127629A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 通信系统中策略与计费执行设备、在线计费系统及方法
CN101765223A (zh) * 2008-12-25 2010-06-30 中国移动通信集团公司 业务控制设备获得用户接入类型的方法、sgsn和系统
WO2010079715A1 (fr) * 2009-01-06 2010-07-15 シャープ株式会社 SYSTÈME DE COMMUNICATION MOBILE, STATION DE CONTRÔLE QoS, ET STATION MOBILE
CN101841797A (zh) * 2009-03-21 2010-09-22 中兴通讯股份有限公司 一种终端通过多接入网接入的计费方法和系统及上报方法

Also Published As

Publication number Publication date
CN102761958A (zh) 2012-10-31
CN102761958B (zh) 2017-09-22

Similar Documents

Publication Publication Date Title
KR101508571B1 (ko) 단일 ａｐｎ을 이용하여 로컬 브레이크아웃 서비스들을 제공하도록 구성되는 방법 및 장치
EP2445261B1 (fr) Procédé, appareil et système pour router des données de plan d'utilisateur dans un réseau mobile
KR101519547B1 (ko) 사용자 장비의 위치 정보를 갱신하기 위한 방법 및 장치
US9320075B2 (en) Method, system and transmission distribution network element for indicating data-distribution
US8855045B2 (en) Method and system for controlling establishment of local IP access
US9655153B2 (en) Method and apparatus for notifying connection attributes for local internet protocol (IP) access
EP2908464A1 (fr) Procédé, système et contrôleur pour transfert de routage
CN101860910B (zh) 本地网络的承载建立方法、系统及装置
US9225726B2 (en) Methods for supporting user equipment accessing local IP services and apparatus therefor
WO2013010415A1 (fr) Procédé, système et sgw pour réaliser une notification d'attributs d'adresse ip
JP2013502858A (ja) 課金システム及び課金の方法
WO2009135431A1 (fr) Procédé, système et équipement pour notifier des données d'utilisateur
WO2012094957A1 (fr) Procédé et système pour effecteur une gestion de mobilité sur un terminal mtc
WO2014166089A1 (fr) Procédé et dispositif de régulation de l'encombrement
WO2011054320A1 (fr) Procédé, dispositif et système permettant de transférer un service de protocole internet du réseau fédérateur
WO2011035732A1 (fr) Procédé, dispositif et système de commande pour un accès ip local ou un déchargement de trafic ip sélectionné
WO2012024989A1 (fr) Procédé et système pour une libération de porteuse
WO2012126302A1 (fr) Procédé et système prenant en charge la communication simultanée pour un terminal à double mode, à double veille
US20150237495A1 (en) Method and system for differentiating between subscribers
WO2012130018A1 (fr) Procédé et système pour la prise en charge de mobilité de connexion de déchargement ip
JP5859680B2 (ja) ローカルアクセス接続の処理方法及び装置
WO2013004121A1 (fr) Procédé et dispositif de traitement d'informations de passerelle locale
JP6446546B2 (ja) データ処理方法、装置、端末、モビリティ管理エンティティ、およびシステム
WO2016019559A1 (fr) Appareil, système, et procédé d'identification d'équipement d'utilisateur de réseau partagé
WO2011085623A1 (fr) Procédé et système permettant à une passerelle d'accès local d'obtenir des informations d'appel d'un terminal

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

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

Country of ref document: EP

Kind code of ref document: A1