[go: up one dir, main page]

WO2003030474A2 - Controle d'acces mmsc - Google Patents

Controle d'acces mmsc Download PDF

Info

Publication number
WO2003030474A2
WO2003030474A2 PCT/IE2002/000139 IE0200139W WO03030474A2 WO 2003030474 A2 WO2003030474 A2 WO 2003030474A2 IE 0200139 W IE0200139 W IE 0200139W WO 03030474 A2 WO03030474 A2 WO 03030474A2
Authority
WO
WIPO (PCT)
Prior art keywords
recipient
message
messaging system
content
code
Prior art date
Application number
PCT/IE2002/000139
Other languages
English (en)
Other versions
WO2003030474A3 (fr
Inventor
Frederick James Jones
Fergal O'sullivan
John Murtagh
Joseph Johnson
Louis Corrigan
Brendan Mcgee
Original Assignee
Markport Limited
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 Markport Limited filed Critical Markport Limited
Priority to AU2002343183A priority Critical patent/AU2002343183A1/en
Publication of WO2003030474A2 publication Critical patent/WO2003030474A2/fr
Publication of WO2003030474A3 publication Critical patent/WO2003030474A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/301—Name conversion
    • 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/08—Network architectures or network communication protocols for network security for authentication of entities
    • 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/12—Applying verification of the received information
    • H04L63/126—Applying verification of the received information the source of the received data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • 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
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements

Definitions

  • the invention relates to communication of rich messages having content in a mobile network environment.
  • An example is routing of multi-media messages in which a multi-media service centre (MMSC) is used.
  • MMSC multi-media service centre
  • Another example is in WAP or I-Mode in which a notification is pushed to a subscriber and the subscriber then uses a browser to pull the notified content.
  • an MMSC receives a MIME encoded Multimedia Message or E-mail message as defined by the 3GPP, WAP Forum and IETF.
  • This message may contain multimedia elements (e.g. text, audio, video etc.).
  • This message is stored temporarily in an MMSC message store and a notification is sent to one or more mobile device(s) indicating the message characteristics (e.g. size etc.) and a unique message-locator, which can be used to retrieve the message.
  • the device/subscriber then retrieves the MMS message using the message-locator received in the notification.
  • the multimedia parts of the message may contain the actual multimedia content, or may contain a further part-locator which can be used to retrieve the multimedia content. This is typically used in applications where the multimedia content (voice / video) is too large to be stored on the device and is instead streamed from a server in the network.
  • United States Patent Specification No. US6246871B (Nokia) describes a method of messaging in which a notification includes a temporary access code for the stored message. Such a notification is sent to multiple recipients, who can then access the message using the temporary access code.
  • PCT Patent Specification No. W098/58332 (Ericsson) describes a messaging method in which a notification is sent to an intended recipient, the notification having a security key.
  • a method of communication of a rich message from a sender device to a recipient device comprising the steps of:-
  • the sender device transmitting the message to a messaging system
  • the messaging system storing content of the message, and transmitting a notification of the message to the recipient device, and
  • the recipient device requesting the content by accessing the messaging system and retrieving the content
  • the messaging system performs recipient authentication before allowing the recipient device to have access to the content.
  • the messaging system is an MMSC and the message is a multimedia message.
  • the messaging system includes in the notification an address of a substitute location for the content, said substitute location being different from a real location at which the content is stored, and the authentication step controls access to the real location.
  • the locations are URLs.
  • said notification includes a code generated by an encode function of the messaging system, and the authentication step is performed by a decode function.
  • the encode function generates the code using recipient data.
  • the decode function performs authentication by decoding the recipient data and comparing it with recipient data received in the content request.
  • the recipient data includes a recipient subscriber identifier.
  • the recipient subscriber identifier is an MSISDN.
  • the encode function uses the real location address to generate the code, and the decode function determines the real location address by decoding.
  • the code is included in a field of the substitute location address in the notification.
  • the encode function uses a secret key to generate the code, and the decode function uses said key to decode the code.
  • the secret key is randomly generated for each message.
  • the encode function uses a recipient's PKI public key to generate the code and the decode function requests the recipient device to decode the code using its private key and subsequently verifies the recipient device decoding.
  • the messaging system comprises the decode function.
  • the recipient device comprises the decode function.
  • the invention provides a communication device comprising means for performing recipient device steps of a method as defined above.
  • the recipient device may, for example, be a multimedia-enabled mobile device.
  • the invention provides a messaging system comprising means for performing messaging system steps of a method as defined above.
  • the messaging system may, for example, be an MMSC
  • a messaging system such as an MMSC transmitting a notification to a recipient, the notification indicating where message content can be retrieved
  • the recipient device typically a mobile device accessing the server storing the message content but importantly, only being allowed access to the content after authentication of the recipient.
  • the invention provides security at the level of the recipient.
  • control of access by recipients has been achieved by transmitting the notification only to the described reci ⁇ ient(s).
  • the notification is wrongly routed or finds its way to a wrong recipient, or if the message location is accessed by an unintended recipient, there is inadequate control over who accesses the content despite message or sender-level security being imposed.
  • the messaging system and the content server is an MMSC.
  • the MMSC contains a token-encode function for generation of a token using the following:
  • this secret key could be generated randomly for each message
  • the MMSC contains a token-decode function for extraction of the recipient subscriber identification and the actual message-locator or part-locator using the following:
  • token-encode and token-decode functions are such that it will not be feasible in practice for a 3 rd party to generate an alternative token such that the token-decode function will produce the original message-locator or message-part but with the recipient subscriber identification of the 3 rd party, rather than the intended recipient.
  • the MMSC receives the multimedia message from a content supplier indicating a need for token generation.
  • the message is stored in the MMSC server.
  • a token is generated using the token-encode function and is incorporated into a field used as a substitute message-locator.
  • the substitute message-locator addresses a placeholder location (URL), the content being stored in a different, "real" URL location.
  • the MMSC then notifies the recipient of the pending message using the substitute message-locator.
  • the user (“the requester", which should be the recipient), requests the message from the MMSC using the substitute message-locator.
  • the MMSC applies the token-decode function to extract the recipient subscription identification and the actual message-locator.
  • the MMSC then compares the recipient subs ⁇ iption identification with the subscription identification of the requester. If they match, and the message-locator identifies a valid message, the message is transmitted to the requester.
  • the decode function effectively performs recipient authentication for controlling access from the placeholder location to the real location.
  • a single message may be intended for several recipients.
  • separate tokens and message-identifiers are generated for each recipient and are validated individually. The important point is that the security is at the recipient level.
  • the MMSC receives the Multimedia Message from a content supplier indicating a need for token generation.
  • the message is stored in the MMSC server.
  • a token is generated using the token-encode function and is incorporated into the message as a substitute p ⁇ rt-loc ⁇ tor.
  • the user requests (e.g. from a streaming server) the content referenced by each p ⁇ rt-loc ⁇ tor.
  • the MMSC applies the token-decode function to extract the recipient subscription identification and each actual p ⁇ rt-loc ⁇ tor.
  • the MMSC compares the recipient subscription identification with the subscription identification of the requester. If they match, and the p ⁇ rt-loc ⁇ tor identifies a valid multimedia object, the multimedia content is transmitted (e.g. streamed) to the requester.
  • Further examples of implementation of the invention in which a number of alternative token-encode and token-decode mechanisms are described, are described below with reference to Figs. 1 to 3. For these examples, an implementation of the MMSC message store based on standard Web Server capabilities is assumed, i.e. message locators are implemented by URL's, and message content is downloaded using the HTTP protocol.
  • the MMSC receives a multimedia message from a content supplier indicating a need for token generation.
  • the message is stored in the MMSC server under a dynamically generated URL - url, say.
  • a token is generated using the token-encode function and is incorporated into a field of a substitute message-locator, i.e. a substitute URL - url s .
  • the MMSC then notifies the recipient of the pending message using the substitute message-locator, url s .
  • the token-encode function used in this implementation accesses a secure database to retrieve an access control token (ACT) that is uniquely associated with the recipient, e.g. this could be a secret PIN number or password assigned to or selected by the subscriber.
  • ACT access control token
  • the access control token is encoded, along with the actual message URL url herein using a secret key known only to the MMSC and incorporated into a field of the substitute URL url s .
  • the user requests the message from the MMSC by invoking a HTTP GET method on the substitute URL url s .
  • the MMSC applies the token-decode function, which may be invoked as a CGI script or Java servlet associated with the substitute URL url s ..
  • the token-decode function extracts the access control token and the actual message URL url m using the secret key.
  • the MMSC responds to the request by generating a challenge to the requester to enter their access control token (ACT, e.g. PIN or password).
  • ACT access control token
  • the requester returns the requested information using a HTTP POST method. For added security, this exchange could use HTTPS to ensure the access control token was not exchanged in plain-text.
  • the token-decode function now compares the received access control token with the access control token that was decoded from the substitute URL url s . If the access control tokens match, the requester is authenticated and the message content stored under the actual URL url, cooperate, can be returned to the requestor.
  • the MMSC receives the multimedia message from a content supplier indicating a need for token generation.
  • the message is stored in the MMSC server under a dynamically generated URL - url m .
  • a token is generated using the token-encode function and is incorporated into a field of a substitute message-locator, i.e. a substitute URL - url s .
  • the MMSC then notifies the recipient of the pending message using the substitute message-locator, url s .
  • the token-encode function used in this implementation retrieves the recipient's network identity from the destination address of the message, e.g. this could be an MSISDN, MIN or similar identifier.
  • the subscriber identity is encoded, along with the actual message URL url structuring using a secret key known only to the MMSC and incorporated into a field of the substitute URL url s .
  • the user requests the message from the MMSC by invoking a HTTP GET method on the substitute URL url s .
  • the MMSC applies the token-decode function, which may be invoked as a CGI script or Java servlet associated with the substitute URL url s ..
  • the token-decode function extracts the subscriber identifier and the actual message
  • the token-decode function now compares the subscriber identifier provided by the network with the subscriber identifier that was decoded from the substitute URL url s . If the subscriber identifiers match, the requester is authenticated and the message content stored under the actual URL url crulie can be returned to the requestor.
  • the MMSC receives the Multimedia Message from a content supplier indicating a need for token generation.
  • the message is stored in the MMSC server under a dynamically generated URL - url m .
  • a token is generated using the token-encode function and is incorporated into a field of a substitute message-locator, i.e. a substitute URL - url 5 .
  • the MMSC then notifies the recipient of the pending message using the substitute message-locator, url s .
  • the token-encode function first generates a unique access control token using a suitable random function. It then retrieves the recipient's PKI certificate and uses the recipient's public key to encode the access control token - act u .
  • the access control token is also encoded using a secret key known only to the MMSC - act m .
  • the actual message URL url m is also encoded using a secret key known only to the MMSC and all values are incorporated into a field of the substitute URL url s .
  • the user requests the message from the MMSC by invoking a HTTP GET method on the substitute URL url s .
  • the MMSC applies the token-decode function, which may be invoked as a CGI script or Java servlet associated with the substitute URL url s ..
  • the token-decode function extracts act u . It also decodes act,,, and the actual message URL url m using the secret key.
  • the MMSC responds to the request by sending the act u to the requester and asking them to return the decrypted access control token.
  • the requester's mobile terminal decrypts the act u using the subscriber's private key (stored in a secure fashion on the mobile terminal).
  • the decrypted access control token is returned.
  • the token-decode function now compares the decrypted access control token received from the subscriber with the decrypted act,ippo. If the access control tokens match, the requester is authenticated and the message content stored under the actual URL url, cooperate, can be returned to the requestor.
  • the invention provides a very effective mechanism for sending messages with content to only intended recipients. This is very advantageous for ensuring privacy and confidentiality in a range of messaging scenarios, such as communication of sensitive business information.
  • the recipient may use a land-line telephone or other communication device to pull down the content. This may occur, for example, if the functionalities of mobile and fixed phones converge in later years.
  • the token-decode function might be contained in the recipient device.
  • the embodiments described use subscriber data (MSISDN or MIN) to encode the notification. Such data is associated specifically with the user and not necessarily the user's device.
  • the MSISDN may be stored in the user's SIM card.
  • the encode function may alternatively use a device identifier such as an IMEI or GSM network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Selon la présente invention, un MMSC génère un jeton codé fondé sur un localisateur de messages (ou localisateur de parties) et sur l'identification de l'abonnement du destinataire. Ledit jeton est inséré dans le champ du localisateur de messages (ou localisateur de parties) d'une notification envoyée au destinataire. Lorsqu'une demande de message MMS est reçue, le MMS décode le champ du localisateur de messages (ou localisateur de parties) pour authentifier l'abonné et le localisateur. Ladite authentification permet d'accéder de manière efficace, à partir d'un emplacement URL de remplacement compris dans la notification, à un emplacement URL réel du contenu.
PCT/IE2002/000139 2001-09-28 2002-09-30 Controle d'acces mmsc WO2003030474A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002343183A AU2002343183A1 (en) 2001-09-28 2002-09-30 Mmsc access control

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US32520401P 2001-09-28 2001-09-28
US60/325,204 2001-09-28
EP01650118.1 2001-10-08
EP01650118 2001-10-08

Publications (2)

Publication Number Publication Date
WO2003030474A2 true WO2003030474A2 (fr) 2003-04-10
WO2003030474A3 WO2003030474A3 (fr) 2003-12-11

Family

ID=27635774

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IE2002/000139 WO2003030474A2 (fr) 2001-09-28 2002-09-30 Controle d'acces mmsc

Country Status (3)

Country Link
AU (1) AU2002343183A1 (fr)
IE (2) IES82842B2 (fr)
WO (1) WO2003030474A2 (fr)

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004112368A3 (fr) * 2003-05-23 2005-05-26 Heyanita Inc Procede et systeme de communication d'un fichier de donnees sur une reseau et de teleconference sur un reseau de telephonie
DE102004003593A1 (de) * 2004-01-15 2005-08-04 Deutsche Telekom Ag Verfahren zur Übermittlung von benutzerspezifischen Daten auf der Basis des WAP- oder HTML-Protokolls
EP1562342A1 (fr) * 2004-02-05 2005-08-10 France Telecom Procédé et système de traitement d'un message multimédia
WO2006021170A1 (fr) * 2004-08-23 2006-03-02 Daybyday Media Gmbh Procédé et dispositif de transmission sure de courriers électroniques
EP1643744A1 (fr) * 2004-10-04 2006-04-05 Alcatel Méthode de transfert d'information vidéo à plusieurs utilisateurs dans un réseau MMS
EP1523165A3 (fr) * 2003-10-06 2006-10-18 Microsoft Corporation Notification d'événements par Internet
CN100334896C (zh) * 2004-03-13 2007-08-29 乐金电子(中国)研究开发中心有限公司 一种多媒体短信服务信息收发系统及信号收发方法
CN100372391C (zh) * 2004-08-16 2008-02-27 华为技术有限公司 一种多媒体消息系统及转发多媒体消息的方法
CN100456771C (zh) * 2005-12-23 2009-01-28 华为技术有限公司 通信设备及其中模块间交互方法
US7508132B2 (en) 2003-10-20 2009-03-24 Hewlett-Packard Development Company, L.P. Device having a getter structure and a photomask
US7603697B1 (en) * 2003-05-30 2009-10-13 Cellco Partnership Method and system for securely delivering authentication-related data
RU2398355C2 (ru) * 2005-09-01 2010-08-27 Хуавэй Текнолоджиз Ко., Лтд. Способ, система и терминал для реализации услуг передачи информации
RU2465741C2 (ru) * 2008-03-18 2012-10-27 Хуавэй Текнолоджиз Ко., Лтд. Способ, система и устройство для реализации услуги обмена мультимедийными сообщениями
WO2013028589A1 (fr) * 2011-08-23 2013-02-28 Zixcorp Systems, Inc. Authentification à facteurs multiples
US8396928B2 (en) 2007-09-21 2013-03-12 Smartbrief, Inc. Methods and systems for handling electronic message content for electronic communications devices
US8407296B2 (en) 2007-09-24 2013-03-26 Smartbrief, Inc. Multiple and multi-part message methods and systems for handling electronic message content for electronic communications devices
CN104378744A (zh) * 2013-08-13 2015-02-25 中兴通讯股份有限公司 服务提供方法、装置及服务请求方法、装置
WO2020205297A1 (fr) * 2019-04-02 2020-10-08 Microsoft Technology Licensing, Llc Vérification de l'emplacement d'un appelant destinée à être utilisée dans l'attribution de numéros en fonction de l'emplacement

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2357016A1 (fr) * 1999-01-14 2000-07-20 Tumbleweed Communications Corp. Acheminement securise de messages electroniques sur internet
US6725381B1 (en) * 1999-08-31 2004-04-20 Tumbleweed Communications Corp. Solicited authentication of a specific user
US6246871B1 (en) * 1999-09-24 2001-06-12 Nokia Networks Oy Method and apparatus for providing access of messages to multiple recipients in cellular networks

Cited By (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8161116B2 (en) 2003-05-23 2012-04-17 Kirusa, Inc. Method and system for communicating a data file over a network
US7277697B2 (en) 2003-05-23 2007-10-02 Adesh Desai Method and system for establishing a teleconference over a telephony network
WO2004112368A3 (fr) * 2003-05-23 2005-05-26 Heyanita Inc Procede et systeme de communication d'un fichier de donnees sur une reseau et de teleconference sur un reseau de telephonie
US7483525B2 (en) 2003-05-23 2009-01-27 Navin Chaddha Method and system for selecting a communication channel with a recipient device over a communication network
US7603697B1 (en) * 2003-05-30 2009-10-13 Cellco Partnership Method and system for securely delivering authentication-related data
EP1523165A3 (fr) * 2003-10-06 2006-10-18 Microsoft Corporation Notification d'événements par Internet
US7508132B2 (en) 2003-10-20 2009-03-24 Hewlett-Packard Development Company, L.P. Device having a getter structure and a photomask
DE102004003593B4 (de) * 2004-01-15 2016-05-12 Deutsche Telekom Ag Verfahren zur Übermittlung von benutzerspezifischen Daten auf der Basis des WAP- oder HTML-Protokolls
DE102004003593A1 (de) * 2004-01-15 2005-08-04 Deutsche Telekom Ag Verfahren zur Übermittlung von benutzerspezifischen Daten auf der Basis des WAP- oder HTML-Protokolls
EP1562342A1 (fr) * 2004-02-05 2005-08-10 France Telecom Procédé et système de traitement d'un message multimédia
CN100334896C (zh) * 2004-03-13 2007-08-29 乐金电子(中国)研究开发中心有限公司 一种多媒体短信服务信息收发系统及信号收发方法
US8527007B2 (en) 2004-08-16 2013-09-03 Huawei Technologies Co., Ltd. Multimedia message system and method for sending multimedia message
CN100372391C (zh) * 2004-08-16 2008-02-27 华为技术有限公司 一种多媒体消息系统及转发多媒体消息的方法
US8559945B2 (en) 2004-08-16 2013-10-15 Huawei Technologies., Ltd. Routing function multimedia message service gateway
WO2006021170A1 (fr) * 2004-08-23 2006-03-02 Daybyday Media Gmbh Procédé et dispositif de transmission sure de courriers électroniques
EP1643744A1 (fr) * 2004-10-04 2006-04-05 Alcatel Méthode de transfert d'information vidéo à plusieurs utilisateurs dans un réseau MMS
RU2398355C2 (ru) * 2005-09-01 2010-08-27 Хуавэй Текнолоджиз Ко., Лтд. Способ, система и терминал для реализации услуг передачи информации
CN100456771C (zh) * 2005-12-23 2009-01-28 华为技术有限公司 通信设备及其中模块间交互方法
US8396928B2 (en) 2007-09-21 2013-03-12 Smartbrief, Inc. Methods and systems for handling electronic message content for electronic communications devices
US8407296B2 (en) 2007-09-24 2013-03-26 Smartbrief, Inc. Multiple and multi-part message methods and systems for handling electronic message content for electronic communications devices
RU2465741C2 (ru) * 2008-03-18 2012-10-27 Хуавэй Текнолоджиз Ко., Лтд. Способ, система и устройство для реализации услуги обмена мультимедийными сообщениями
WO2013028589A1 (fr) * 2011-08-23 2013-02-28 Zixcorp Systems, Inc. Authentification à facteurs multiples
US8984605B2 (en) 2011-08-23 2015-03-17 Zixcorp Systems, Inc. Multi-factor authentication
US9509683B2 (en) 2011-08-23 2016-11-29 Zixcorp Systems, Inc. Multi-factor authentication
CN104378744A (zh) * 2013-08-13 2015-02-25 中兴通讯股份有限公司 服务提供方法、装置及服务请求方法、装置
EP3035717A4 (fr) * 2013-08-13 2016-08-17 Zte Corp Procédé et dispositif de fourniture de service, et procédé et dispositif de demande de service
WO2020205297A1 (fr) * 2019-04-02 2020-10-08 Microsoft Technology Licensing, Llc Vérification de l'emplacement d'un appelant destinée à être utilisée dans l'attribution de numéros en fonction de l'emplacement
US11350283B2 (en) 2019-04-02 2022-05-31 Microsoft Technology Licensing, Llc Verification of caller location for use in assigning location-based numbers

Also Published As

Publication number Publication date
WO2003030474A3 (fr) 2003-12-11
IES82842B2 (en) 2003-04-30
IE83599B1 (en) 2004-09-22
AU2002343183A1 (en) 2003-04-14
IES20020779A2 (en) 2003-04-16
IE20020780A1 (en) 2003-04-16

Similar Documents

Publication Publication Date Title
EP3008935B1 (fr) Authentification de dispositif mobile dans un scénario à réseaux de communication hétérogène
US9768961B2 (en) Encrypted indentifiers in a wireless communication system
WO2003030474A2 (fr) Controle d'acces mmsc
EP2062457B1 (fr) Enregistrement d'une application mobile
JP4782139B2 (ja) モバイルユーザーをトランスペアレントに認証してウェブサービスにアクセスする方法及びシステム
CN101510877B (zh) 单点登录方法和系统、通信装置
EP1313286A2 (fr) Procédé et dispositif pour la protection des identités des terminaux mobiles sans fil
US20060262929A1 (en) Method and system for identifying the identity of a user
KR20090005340A (ko) 이동 통신 장치들에 대한 전화-번호 발견 및 전화-번호 인증 방법 및 시스템
WO2010094331A1 (fr) Authentification auprès d'un fournisseur d'identité
WO2002019593A2 (fr) Authentification d'un utilisateur final basee sur la boite a outils d'application du module d'identification d'abonne (sat), independante du fournisseur de services
US8156340B1 (en) System and method for securing system content by automated device authentication
WO2011113314A1 (fr) Procédé, système et serveur d'ouverture de service
US7721326B2 (en) Automatic authentication selection server
FI116654B (fi) Menetelmä käyttäjän autentikoimiseksi
CN109120408A (zh) 用于认证用户身份的方法、装置和系统
US10028141B2 (en) Method and system for determining that a SIM and a SIP client are co-located in the same mobile equipment
CN108924142A (zh) 一种基于sip协议的安全语音对讲通讯方法
KR100463751B1 (ko) 무선통신을 위한 패킷데이터 생성 방법과, 이를 이용한무선통신 방법 및 그 장치
US20100255811A1 (en) Transmission of messages
EP3032448A1 (fr) Procede d'autorisation d'acces a des informations dans un systeme de telecommunication
CN1768503A (zh) 使用在用户终端中生成的公共和私有密钥来建立安全连接的方法
EP2399408A1 (fr) Authentification auprès d'un fournisseur d'identité
KR20120037262A (ko) 메시징 서비스 시스템 및 방법
MXPA06005074A (es) Autenticacion y actualizacion de la generacion de claves de sesion entre un nodo de una red de servicio y cuando menos una terminal de comunicaciones con la ayuda de una tarjeta de identificacion

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ OM PH PL PT RU SD SE SG SI SK SL TJ TM TN TR TZ UA UG US UZ VC VN YU ZA ZM

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZM ZW AM AZ BY KG KZ RU TJ TM AT BE BG CH CY CZ DK EE ES FI FR GB GR IE IT LU MC PT SE SK TR BF BJ CF CG CI GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP