[go: up one dir, main page]

EP2487973A1 - Notification à un équipement utilisateur dans un réseau mobile d'une requête de déclenchement d'application de l'équipement utilisateur d'un serveur d'application de réseau - Google Patents

Notification à un équipement utilisateur dans un réseau mobile d'une requête de déclenchement d'application de l'équipement utilisateur d'un serveur d'application de réseau Download PDF

Info

Publication number
EP2487973A1
EP2487973A1 EP11290085A EP11290085A EP2487973A1 EP 2487973 A1 EP2487973 A1 EP 2487973A1 EP 11290085 A EP11290085 A EP 11290085A EP 11290085 A EP11290085 A EP 11290085A EP 2487973 A1 EP2487973 A1 EP 2487973A1
Authority
EP
European Patent Office
Prior art keywords
application
trigger request
request information
sgsn
mme
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.)
Withdrawn
Application number
EP11290085A
Other languages
German (de)
English (en)
Inventor
Omar Elloumi
Laurent Thiebaut
Bruno Landais
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.)
Alcatel Lucent SAS
Original Assignee
Alcatel Lucent SAS
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 Alcatel Lucent SAS filed Critical Alcatel Lucent SAS
Priority to EP11290085A priority Critical patent/EP2487973A1/fr
Priority to PCT/EP2012/052124 priority patent/WO2012107485A1/fr
Priority to CN2012800166665A priority patent/CN103477690A/zh
Priority to KR1020137023952A priority patent/KR20130135912A/ko
Priority to US13/984,751 priority patent/US20140113609A1/en
Priority to JP2013552951A priority patent/JP2014505445A/ja
Priority to TW101104391A priority patent/TW201246989A/zh
Publication of EP2487973A1 publication Critical patent/EP2487973A1/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • 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
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/02—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration by periodical registration
    • 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
    • H04W8/205—Transfer to or from user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal

Definitions

  • the present invention generally relates to mobile networks and systems and to the support of application services in such networks and systems.
  • a terminal also called User Equipment UE
  • 3GPP 3 rd Generation Partnership Project
  • a terminal also called User Equipment UE
  • 3GPP 3 rd Generation Partnership Project
  • EPS Evolved Packet System
  • PS Packet Switched
  • EPS architecture is recalled in figure 1 , taken from 3GPP TS 23.401.
  • EPS comprises EPC (Evolved Packet Core) that may be accessed via E-UTRAN or via UTRAN/GERAN.
  • EPC comprises entities such as MME (Mobility Management Entity), SGSN (Serving GPRS Support Node) supporting an S4 interface to a SGW and thus called S4-SGSN, SGW (Serving Gateway) and PGW (Packet Data Network PDN Gateway).
  • GPRS/UMTS (not specifically illustrated) comprises GPRS/UMTS Packet Core which may be accessed via GERAN/UTRAN and which comprises entities such as SGSN supporting a Gn interface with a GGSN and thus called Gn-SGSN) and GGSN (Gateway GPRS Support Node).
  • MTC Machine-Type-Communication
  • M2M Machine-to-Machine M2M
  • 3GPP 3GPP TS 22.368
  • MTC Device an UE equipped for Machine Type Communication
  • MTC Server(s) providing MTC application services.
  • Network and system improvements are needed due to the specific nature of MTC. For example, there is a need, for MTC Devices that are not continuously attached to the network or that have no always-on PDP/PDN connection, to trigger these MTC Devices to contact the MTC server. There is also a need to provide remote MTC device configuration or management.
  • DM Device Management
  • OMA Open Mobile Alliance
  • a Notification Message is sent from a DM Server to a DM Client to cause the DM Client to initiate a connection back to the DM Server, as illustrated for example in figure 3 taken from "OMA Device Management Notification Initiated Session" Open Mobile Alliance, OMA-TS-DM_Notification-V1_3-20101207-C, where such Notification to DM Client is also noted “Package 0".
  • This Notification Message is sent using a protocol called Push OTA (Over The Air) protocol, running on top of an associated transport protocol.
  • Push OTA Over The Air
  • Different variants have been specified by OMA for the Push OTA protocol and associated transport protocol. However, as recognized by the inventors and as will be explained later in more detail, none of these variants are satisfactory, particularly for data only (or PS only) terminals such as Machine-To-Machine (M2M) terminals or MTC devices.
  • M2M Machine-To-Machine
  • a method for notifying a User Equipment UE (or a group of UE), over a mobile network, of an UE Application trigger request from a Network Application Server comprising, in an embodiment:
  • entities for performing such method including, in particular: Network Application Server, subscriber database (such as the HLR/HSS), gateway between Network Application Server and mobile network, node controlling UE access to the mobile network (such as a SGSN/MME), , UE.
  • OMA DM Open Mobile Alliance Device Management
  • the application server sends a specific SMS to the device (UE) which triggers:
  • SMS mandates that each device is assigned an MSISDN number, a resource that is used to identify a terminal as per ITU-T E.164 specification.
  • SMS For LTE terminals, usage of SMS requires the support of a CS domain subscription (as MME do not support SMS native delivery, MME can only relay a SMS service coming from a MSC over CS domain). Such need for CS domain subscription is costly for the operator (M2M devices are always-on attached to MSC just to be able to receive a few SMS per year).
  • M2M related devices may apply to other kind of devices such as USB dongles, for which such solution as SMS sending is only used for back-office operations (device configuration) and not for person to person communication service.
  • SMS sending is only used for back-office operations (device configuration) and not for person to person communication service.
  • Several other solutions have been considered in OMA to replace the need for SMS, these include the use of SIP, UDP message sent to the device (UDP connection request), HTTP push. These methods need pre-conditions:
  • the method based on a SIP message sent to the device assume that the M2M device supports a full sip stack (and may require a full IMS subscription) just for infrequent OMA DM device management procedures. This is believed to be too heavy for M2M which should correspond to as small/simple as possible devices and network subscriptions.
  • the method based on a HTTP push assumes that a HTTP/TCP session/connection is permanently opened between the M2M device and M2M server. With the potential explosion of the number of M2M devices, the scalability of this method is questionable. Furthermore when the device is roaming and served by a PGW/GGSN in the VPLMN in a LBO (Local Break Out) roaming deployment nothing guarantees that the IP @ allocated to the UE by the PGW/GGSN in the VPLMN belongs to a (public) @ range allowing to contact the DM server of the HPLMN without traversing a NAT. Requiring the NAT to keep permanently a NAT context for all devices that may one day possibly require a DM transaction is not scalable and leads to similar (NAT refresh) issues than those described for the UDP based solution.
  • LBO Local Break Out
  • MSISDN(s) are user friendly numbers that have been used for CS domain services.
  • SMS could be sent to an IMSI number instead.
  • this solution does not remove the need to allocate a CS (Circuit Switched) context for each M2M terminal even if it uses data only services (*).
  • M2M puts a strong pressure on ARPU (Average Revenue Per User), which tends to be 10 times less than the case of personal communication.
  • SMS may be sent over PS domain (via a SGSN), thus removing the need of a CS domain subscription for devices that only camp over such radio.
  • SMS service over LTE relies on a SGs link between a MME and a MSC for the SMS delivery.
  • Embodiments of the present invention are based on a different approach, enabling in particular to avoid above-mentioned problems.
  • Embodiments of the present invention propose a solution allowing a network application to trigger a UE (or a group of UE) to initiate communication with the network application server based on a trigger indication from the application server, without the need for the network application server to send SIP push, HTTP push, UDP message or SMS.
  • the solution works in particular for UEs with PS only subscription without MSISDN.
  • This approach may be used e.g. by an MTC Server or by a Device Management Server for remote device configuration.
  • a network application e.g. Device Management
  • a network application server e.g. Device Management
  • UE application trigger request When the network application server needs to initiate the contact with an UE it informs the HSS/HLR about this need ("UE application trigger request") and the UE is notified via signaling exchange through the MME/SGSN (MME/SGSN means MME or SGSN) that is serving it.
  • MME/SGSN means MME or SGSN
  • Such UE application trigger request signaling through the MME or/and SGSN may occur only next time the UE initiates signaling to the MME or/and SGSN if there is no on-going signaling connection between the UE and MME/SGSN, or may take place immediately if there is an on-going signalling connection with the UE or if this is an urgent request.
  • the UE e.g. Device Management
  • the network application e.g. Device Management
  • the Device Management server wants to configure (or change the SW of) a particular device/UE it informs the HSS/HLR about this need (UE application trigger request) and the UE is notified via signaling exchange through the MME or/and SGSN.
  • Each of the UE targeted by the network application server request is then notified about that request via signalling exchange through the serving MME/SGSN, during the next NAS signalling exchange with the UE if there is no on-going signalling connection between the UE and MME/SGSN, or immediately if there is an on-going signalling connection with the UE or if this is an urgent request.
  • the UE application Upon reception of this "UE application trigger request” information, the UE application is triggered and contacts the network application server.
  • Procedures that ensure reliable delivery of (signaling) messages between UE and network (MME/SGSN) over the radio and messages between the HSS/HLR and the MME/SGSN are used to make sure that message loss or network node failure do not involve a loss of the UE application trigger request.
  • the firewall/NAT issue is solved because all signaling between the UE and the network application (e.g. DM) server is always initiated by the UE while there is no need to use SMS (and no need of CS subscription for the UE or MSISDN allocation to the UE)
  • the network application e.g. DM
  • a further benefit of this approach is that the (UE application trigger request) mechanism allows M2M devices not to have to listen to paging channels in order to be triggered for Device Management purpose: thus such UE may have VERY long DRX (Discontinuous Reception) periods and be very efficient in terms of battery consumption. If SMS would be used to carry such information, such UE would have to have the same kind of DRX period than regular devices, even though they would actually receive a page only a few times per year to update their SW or configuration.
  • DRX Continuous Reception
  • the steps described above may be implemented as follows, as illustrated in figure 4 , showing the case where the next contact between the MME/SGSN and the UE is for a Routing Area / Tracking Area update.
  • the steps numbers below correspond also to the steps numbers in the figure.
  • An urgency request parameter may also be associated with the "UE application trigger request” notification. If the request is urgent, the UE is notified as soon as possible i.e. the serving MME/SGSN pages the UE as soon as it receives the "UE application trigger request" information from the HSS/HLR. Otherwise the UE is notified only the next time it exchanges signalling with the MME/SGSN. As an example a request for a regular new SW version download or for M2M is non urgent. A request associated with a call from an end-user to a customer care help desk is urgent and requires the MME/SGSN to page the UE.
  • existing nodes or functionalities may be impacted as follows:
  • UEs receive and acknowledge UE application trigger requests via NAS signalling and trigger the corresponding application.
  • This (UE application trigger request) notification procedure is to be reserved to well-behaving applications controlled by the operator in order to avoid overflow of the HSS/HLR and MME/SGSN by spamming.
  • Embodiments of the present invention propose following approach for triggering an UE application from a network application server, for sending the trigger information from the application to the UE:
  • Embodiments of the present invention provide an elegant migration scenario for Device Management for data only cellular devices (e.g. M2M devices but also possibly other types of devices such as USB dongles). This removes the need to use SMS and CS domain, but does not include additional operational complexity to allow pinholing of firewalls. The additional complexity to the Device software is minimal.
  • a method for notifying a User Equipment UE (or a group of UE), over a mobile network, of an UE Application trigger request from a Network Application Server comprising, in an embodiment, a step of:
  • said method comprises a step of:
  • said UE application trigger request information contains one or more of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • said method comprises a step of:
  • entities comprising means for performing such method, said entities including, in particular: Network Application Server, HLR/HSS, gateway between Network Application Server and mobile network, SGSN/MME, UE.
  • Network Application Server comprising, in an embodiment:
  • a subscriber database (such as the HLR/HSS), comprising, in an embodiment:
  • the subscriber database (such as the HLR/HSS) comprises:
  • the subscriber database (such as the HLR/HSS) comprises:
  • the subscriber database (such as the HLR/HSS) comprises:
  • the subscriber database (such as the HLR/HSS) comprises:
  • the subscriber database (such as the HLR/HSS) comprises:
  • the subscriber database (such as the HLR/HSS) comprises:
  • the subscriber database (such as the HLR/HSS) comprises:
  • the subscriber database (such as the HLR/HSS) comprises:
  • a node controlling UE access to the mobile network comprising, in an embodiment:
  • the node controlling UE access to the mobile network (such as a SGSN/MME) comprises:
  • the node controlling UE access to the mobile network (such as a SGSN/MME) comprises:
  • the node controlling UE access to the mobile network (such as a SGSN/MME) comprises:
  • the node controlling UE access to the mobile network (such as a SGSN/MME)comprises:
  • the node controlling UE access to the mobile network (such as a SGSN/MME) comprises:
  • the node controlling UE access to the mobile network (such as a SGSN/MME) comprises:
  • the node controlling UE access to the mobile network (such as a SGSN/MME) comprises:
  • the node controlling UE access to the mobile network (such as a SGSN/MME)comprises:
  • the node controlling UE access to the mobile network (such as a SGSN/MME) comprises:
  • an User Equipment UE comprising, in an embodiment:
  • the UE comprises:
  • the UE comprises:
  • the UE comprises:
  • the UE comprises:
  • the UE comprises:
  • the UE comprises:
  • the UE comprises:
  • the UE comprises:
  • program storage devices e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods.
  • the program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.
  • the embodiments are also intended to cover computers programmed to perform said steps of the above-described methods.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
EP11290085A 2011-02-11 2011-02-11 Notification à un équipement utilisateur dans un réseau mobile d'une requête de déclenchement d'application de l'équipement utilisateur d'un serveur d'application de réseau Withdrawn EP2487973A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP11290085A EP2487973A1 (fr) 2011-02-11 2011-02-11 Notification à un équipement utilisateur dans un réseau mobile d'une requête de déclenchement d'application de l'équipement utilisateur d'un serveur d'application de réseau
PCT/EP2012/052124 WO2012107485A1 (fr) 2011-02-11 2012-02-08 Notification à un équipement utilisateur, sur un réseau mobile, d'une demande de déclenchement d'application d'équipement utilisateur provenant d'un serveur d'application de réseau
CN2012800166665A CN103477690A (zh) 2011-02-11 2012-02-08 通过移动网络通知用户设备来自网络应用服务器的ue应用触发请求
KR1020137023952A KR20130135912A (ko) 2011-02-11 2012-02-08 네트워크 애플리케이션 서버로부터 사용자 장비(ｕｅ) 애플리케이션 트리거 요청을 이동 네트워크를 통해 ｕｅ에 통지
US13/984,751 US20140113609A1 (en) 2011-02-11 2012-02-08 Notifying a user equipment ue, over a mobile network, of an ue application trigger request from a network application server
JP2013552951A JP2014505445A (ja) 2011-02-11 2012-02-08 ネットワーク・アプリケーション・サーバからのｕｅアプリケーション・トリガー要求について、モバイル・ネットワークを通じてユーザ装置ｕｅに通知
TW101104391A TW201246989A (en) 2011-02-11 2012-02-10 Notifying a user equipment UE, over a mobile network, of an UE application trigger request from a network application server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP11290085A EP2487973A1 (fr) 2011-02-11 2011-02-11 Notification à un équipement utilisateur dans un réseau mobile d'une requête de déclenchement d'application de l'équipement utilisateur d'un serveur d'application de réseau

Publications (1)

Publication Number Publication Date
EP2487973A1 true EP2487973A1 (fr) 2012-08-15

Family

ID=45569660

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11290085A Withdrawn EP2487973A1 (fr) 2011-02-11 2011-02-11 Notification à un équipement utilisateur dans un réseau mobile d'une requête de déclenchement d'application de l'équipement utilisateur d'un serveur d'application de réseau

Country Status (7)

Country Link
US (1) US20140113609A1 (fr)
EP (1) EP2487973A1 (fr)
JP (1) JP2014505445A (fr)
KR (1) KR20130135912A (fr)
CN (1) CN103477690A (fr)
TW (1) TW201246989A (fr)
WO (1) WO2012107485A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103686952A (zh) * 2012-09-17 2014-03-26 中兴通讯股份有限公司 一种节能方法、用户设备和网络侧网元
JP2015527022A (ja) * 2012-09-03 2015-09-10 テレフオンアクチーボラゲット エル エム エリクソン（パブル） ３ｇｐｐネットワークのマシン型デバイスにおいて使用される外部識別子を自動で提供する方法及び装置
EP2983442A4 (fr) * 2013-04-01 2016-08-10 China Academy Of Telecomm Tech Procédé et dispositif pour mettre en uvre un service de communication de proximité
CN113748694A (zh) * 2019-04-26 2021-12-03 瑞典爱立信有限公司 用于服务发现的方法和装置

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2709291B1 (fr) * 2011-05-11 2018-10-10 LG Electronics Inc. Procédé et appareil pour des communications mtc dans un système de communication sans fil
RU2014116253A (ru) 2011-10-28 2015-10-27 Нек Корпорейшн Защищенный способ запуска устройства связи машинного типа
US20140351949A1 (en) * 2012-01-27 2014-11-27 Nec Corporation Privacy issues in m2m
US8913518B2 (en) 2012-08-03 2014-12-16 Intel Corporation Enhanced node B, user equipment and methods for discontinuous reception in inter-ENB carrier aggregation
US9036603B2 (en) 2012-08-03 2015-05-19 Intel Corporation Network assistance for device-to-device discovery
US9191828B2 (en) 2012-08-03 2015-11-17 Intel Corporation High efficiency distributed device-to-device (D2D) channel access
US9554296B2 (en) * 2012-08-03 2017-01-24 Intel Corporation Device trigger recall/replace feature for 3GPP/M2M systems
US9526022B2 (en) 2012-08-03 2016-12-20 Intel Corporation Establishing operating system and application-based routing policies in multi-mode user equipment
JP5544409B2 (ja) * 2012-11-15 2014-07-09 株式会社Ｎｔｔドコモ 通信端末、移動通信システム及び方法
CN111132169B (zh) 2013-07-15 2023-06-06 皇家Kpn公司 用于控制用户装备的挂接状态的方法和电信节点
US9844080B2 (en) * 2014-06-13 2017-12-12 Verizon Patent And Licensing Inc. Notification triggered device management session
GB2530552B (en) * 2014-09-26 2018-07-25 Telit Tech Cyprus Ltd System and method of controlling operation of connected devices
CN106304404A (zh) * 2015-06-12 2017-01-04 阿尔卡特朗讯 一种用于控制触发请求所对应的操作的方法、设备与系统
WO2018065060A1 (fr) * 2016-10-06 2018-04-12 Telefonaktiebolaget Lm Ericsson (Publ) Distribution fiable de données sur strate de non-accès
US11792266B2 (en) * 2020-09-29 2023-10-17 Aeris Communications, Inc. Method and system for delivering a shoulder-tap for battery-constrained cellular IoT devices

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090154451A1 (en) * 2007-12-12 2009-06-18 At&T Knowledge Ventures, Lp Method and System to Provide Contact Services in a Communication Network
WO2009117443A1 (fr) * 2008-03-18 2009-09-24 Qualcomm Incorporated Procédé de gestion de réseau par assistance depuis un terminal utilisant une signalisation de plan de commande entre le terminal et le réseau

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6611516B1 (en) * 1999-06-21 2003-08-26 Nokia Telecommunications Oyj Short message service support over a packet-switched telephony network
US6920487B2 (en) * 1999-12-22 2005-07-19 Starhome Gmbh System and methods for global access to services for mobile telephone subscribers
CN101715194A (zh) * 2002-10-18 2010-05-26 卡耐特无线有限公司 扩展有执照无线通信系统覆盖区域的装置与方法
WO2006039623A2 (fr) * 2004-10-01 2006-04-13 Nextel Communications, Inc. Systeme et procede d'enregistrement de deplacement reparti
EP1849329A1 (fr) * 2005-02-16 2007-10-31 Starhome GmbH Solution a numeros locaux pour utilisateurs de telephonie mobile en itinerance
US20060291418A1 (en) * 2005-06-22 2006-12-28 International Mobile Communications, Inc. Method and system for optimal call routing in GSM foreign mode for CDMA to GSM roaming
CN100388685C (zh) * 2005-08-30 2008-05-14 华为技术有限公司 Ip多媒体子系统中ims注册触发实现方法
US20080003996A1 (en) * 2006-06-30 2008-01-03 Nokia Corporation Controlling mobile messaging remotely
US20080076425A1 (en) * 2006-09-22 2008-03-27 Amit Khetawat Method and apparatus for resource management
US8499340B2 (en) * 2007-05-29 2013-07-30 Telefonaktiebolaget L M Ericsson (Publ) IMS network identity management
JP5116509B2 (ja) * 2007-08-31 2013-01-09 パナソニック株式会社 無線通信端末装置、無線通信基地局装置及び無線通信方法
KR101575767B1 (ko) * 2008-12-16 2015-12-08 삼성전자주식회사 무선 통신 단말기의 원격 관리 방법 및 시스템
CN101959133A (zh) * 2009-07-15 2011-01-26 华为技术有限公司 M2m用户设备的操作控制方法、系统和m2m用户设备
CN102238477B (zh) * 2010-04-30 2014-02-19 华为终端有限公司 触发一组mtc设备与mtc服务器通信的方法及mtc设备
KR101729336B1 (ko) * 2010-10-15 2017-04-21 삼성전자주식회사 회선 교환 망과 인터넷 프로토콜 멀티미디어 서브시스템 망간 로밍 서비스 제공 방법 및 시스템과 그 장치
TWI533629B (zh) * 2010-12-28 2016-05-11 內數位專利控股公司 非附於無線網路之觸發裝置
WO2012103902A1 (fr) * 2011-02-04 2012-08-09 Telefonaktiebolaget L M Ericsson (Publ) Procédé et agencements pour communication mtc

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090154451A1 (en) * 2007-12-12 2009-06-18 At&T Knowledge Ventures, Lp Method and System to Provide Contact Services in a Communication Network
WO2009117443A1 (fr) * 2008-03-18 2009-09-24 Qualcomm Incorporated Procédé de gestion de réseau par assistance depuis un terminal utilisant une signalisation de plan de commande entre le terminal et le réseau

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Support of Push service (Release 5); 3GPP TR 23.875", ETSI STANDARDS, LIS, SOPHIA ANTIPOLIS CEDEX, FRANCE, no. V5.1.0, 1 March 2002 (2002-03-01), XP014021954, ISSN: 0000-0001 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015527022A (ja) * 2012-09-03 2015-09-10 テレフオンアクチーボラゲット エル エム エリクソン（パブル） ３ｇｐｐネットワークのマシン型デバイスにおいて使用される外部識別子を自動で提供する方法及び装置
CN103686952A (zh) * 2012-09-17 2014-03-26 中兴通讯股份有限公司 一种节能方法、用户设备和网络侧网元
EP2897421A4 (fr) * 2012-09-17 2016-01-20 Zte Corp Procédé d'économie d'énergie, équipement utilisateur et élément de réseau côté réseau
US9565630B2 (en) 2012-09-17 2017-02-07 Zte Corporation Energy saving method, user equipment and network-side network element
CN103686952B (zh) * 2012-09-17 2019-03-12 中兴通讯股份有限公司 一种节能方法、用户设备和网络侧网元
EP2983442A4 (fr) * 2013-04-01 2016-08-10 China Academy Of Telecomm Tech Procédé et dispositif pour mettre en uvre un service de communication de proximité
US10021726B2 (en) 2013-04-01 2018-07-10 China Academy Of Telecommunications Technology Method and device for implementing proximity communication service
CN113748694A (zh) * 2019-04-26 2021-12-03 瑞典爱立信有限公司 用于服务发现的方法和装置
US12375912B2 (en) 2019-04-26 2025-07-29 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for service discovery

Also Published As

Publication number Publication date
TW201246989A (en) 2012-11-16
US20140113609A1 (en) 2014-04-24
CN103477690A (zh) 2013-12-25
KR20130135912A (ko) 2013-12-11
JP2014505445A (ja) 2014-02-27
WO2012107485A1 (fr) 2012-08-16

Similar Documents

Publication Publication Date Title
EP2487973A1 (fr) Notification à un équipement utilisateur dans un réseau mobile d'une requête de déclenchement d'application de l'équipement utilisateur d'un serveur d'application de réseau
US20240306069A1 (en) Support of user plane transactions over a mobile network
US10993089B2 (en) Application data delivery service for networks supporting multiple transport mechanisms
DK2702793T3 (en) Improvements to completed mobile calls
EP2869610B1 (fr) Procédé et dispositif de mise à jour de zone dans un système de communication sans fil
CN102244854B (zh) Mtc组选择分组数据网网关的方法及移动性管理网元
EP2870819B1 (fr) Procédé de suppression révocable d'une connexion pdn
EP3001702B1 (fr) Support de services mobiles d'applications terminées dans un système portable
CN101626566B (zh) 实现isr场景下终端迁移的方法和设备
CN104144398B (zh) 一种终呼业务的实现方法及系统、hss、scc as

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

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

17P Request for examination filed

Effective date: 20130215

111Z Information provided on other rights and legal means of execution

Free format text: 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

Effective date: 20130410

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

Owner name: ALCATEL LUCENT

D11X Information provided on other rights and legal means of execution (deleted)
17Q First examination report despatched

Effective date: 20170613

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

Owner name: ALCATEL LUCENT

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

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20180103