Transferring of a message
Abstract
An object of the invention is a method for inquiring about information relating to a terminal (MS) of a cellular network, from the cellular network from a messaging server (MMSC) external to the cellular network. The method comprises sending an inquiry from the messaging server (MMSC) to the cellular network, to determine said information relating to the terminal (MS), the inquiry comprising a first identifier for identifying said terminal (MS), the first identifier being a specific identifier external to the cellular network. In the cellular network said first identifier is mapped to a specific second identifier, which is an internal identifier of the cellular network. Said information relating to the terminal (MS) is determined with the aid of said second identifier. A response message is sent from hte cellular network to said messaging server (MMSC) external to the cellular network in response to said inquiry. In the response message, said information relating to the terminal (MS) is indicated with the aid of said first identifier. Furthermore, an object of the invention is a system implementing the method and a server (MMSC) and a network element of a cellular network (GGSN), as well as computer program products implementing the method.

Term
Term ended
Expired 23 December 2019, 6.8 years ago.
- Priority and filed
- Granted
- Expired
- Today
22 claims: 8 independent, 14 dependent
- 1Patenttivaatimukset 1. Menetelmä solukkoverkon päätelaitteeseen (MS) liittyvän tiedon kysymiseksi solukkoverkosta solukkoverkon ulkopuolisesta sanomanvälityspalvelimesta 5 (MMSC) käsin, jossa menetelmässä:lähetetään sanomanvälityspalvelimelta (MMSC) solukkoverkkoon mainitun päätelaitteeseen (MS) liittyvän tiedon selvittämiseksi kysely (41), tunnettu siitä, että kysely käsittää ensimmäisen tunnisteen (MMS-ID) mainitun päätelaitteen (MS) tunnistamiseksi, joka ensimmäinen tunniste on 10 määrätty solukkoverkon ulkopuolinen tunniste;kohdennetaan solukkoverkossa mainittu ensimmäinen tunniste (MMS-ID) määrättyyn toiseen tunnisteeseen (IMSI, IMUI), joka toinen tunniste on solukkoverkon sisäinen tunniste;selvitetään mainitun toisen tunnisteen (IMSI, IMUI) avulla mainittu 15 päätelaitteeseen (MS) liittyvä tieto;lähetetään solukkoverkosta mainitulle solukkoverkon ulkopuoliselle sanomanvälityspalvelimelle (MMSC) vastausviesti (47) vasteena mainittuun kyselyyn (41), jossa vastausviestissä ilmaistaan mainitun ensimmäisen tunnisteen (MMS-ID) avulla mainittu päätelaitteeseen (MS) liittyvä tieto.
- 2Patenttivaatimuksen 1 mukainen menetelmä, tunnettu siitä, että mainittu kysely (41) tehdään vasteena sanomanvälityspalvelimeen (MMSC) saapuneeseen päätelaitteelle (MS) osoitettuun sanomaan. 25
- 3Patenttivaatimuksen 2 mukainen menetelmä, tunnettu siitä, että mainittu sanoma on multimediasanoma.
- 4Patenttivaatimuksen 1 mukainen menetelmä, tunnettu siitä, että tiedonsiirto menetelmässä suoritetaan pakettivälitteisesti.
- 5Patenttivaatimuksen 2 mukainen menetelmä, tunnettu siitä, että menetelmässä:ennen mainitun kyselyn (41) lähettämistä solukkoverkkoon 11215 kohdennetaan sanomanvälityspalvelimessa (MMSC) päätelaitteelle (MS) osoitettuun sanomaan liittyvä osoite mainittuun päätelaitteen ensimmäiseen tunnisteeseen (MMS-ID). 5
- 6Patenttivaatimuksen 1 mukainen menetelmä, tunnettu siitä, että mainittu toinen tunniste on yksi seuraavista:IMSI-koodi (International Mobile Subscriber Identity), IMUI-koodi (International Mobile User Identity).
- 7Patenttivaatimuksen 1 mukainen menetelmä, tunnettu siitä, että mainittu 10 kysely (41) lähetetään solukkoverkkoon määrätylle verkkoelementille (GGSN) ja että mainittu verkkoelementti selvittää mainitun päätelaitteeseen (MS) liittyvän tiedon käyttäen mainittua toista tunnistetta (IMSI, IMUI).
- 8Patenttivaatimuksen 7 mukainen menetelmä, tunnettu siitä, että mainittu 15 verkkoelementti on yhdyskäytävätukisolmu (GGSN) ja että kysely (41) lähetetään sanomanvälityspalvelimelta aina samalle yhdyskäytävätukisolmulle (GGSN).
- 9Patenttivaatimuksen 2 mukainen menetelmä, tunnettu siitä, että mainittu 20 verkkoelementti on yhdyskäytävätukisolmu (GGSN), ja mainittu sanomanvälityspalvelin (MMSC) vastaanottaa mainitun vastausviestin (47), jossa mainittu päätelaitteeseen (MS) liittyvä tieto ilmaistaan ja että mainittu tieto on yksi seuraavista:päätelaitteen (MS) datan 25 vastaanottovalmius, päätelaitteen kytkeytyminen verkkoon.
- 10Patenttivaatimuksen 9 mukainen menetelmä, tunnettu siitä, että mainittu päätelaitteeseen (MS) liittyvä tieto on päätelaitteen datan vastaanottovalmius, jolloin mainittu vastausviesti (47) ilmaisee, onko 30 mainitulla päätelaitteella aktivoitu PDP-konteksti (Packet Data Protocol) jonkin yhdyskäytävätukisolmun (GGSN) kanssa, jolloin:tapauksessa, jossa päätelaitteella (MS) on aktivoitu PDP-konteksti jonkin yhdyskäytävätukisolmun (GGSN) kanssa, mainittu sanoma lähetetään sanomanvälityspalvelimelta (MMSC) päätelaitteelle vasteena mainitun vastausviestin (47) vastaanottamiselle;ja tapauksessa, jossa päätelaitteella (MS) ei ole aktivoitua PDPkontekstia minkään yhdyskäytävätukisolmun (GGSN) kanssa, mainittua 5 sanomaa ei lähetetä päätelaitteelle.
- 11Patenttivaatimuksen 10 mukainen menetelmä, tunnettu siitä, että tapauksessa, jossa päätelaitteella (MS) ei ole aktivoitua PDP-kontekstia minkään yhdyskäytävätukisolmun (GGSN) kanssa, toistetaan mainittu kysely 10 (41) määrätyn ajan kuluttua.
- 12Patenttivaatimuksen 1 mukainen menetelmä, tunnettu siitä, että mainittu ensimmäinen tunniste käsittää:ensimmäisen osion (User ID), joka ilmaisee sanomanvälityspalvelun 15 tilaajan;toisen osion (MMSC ID), joka ilmaisee kyseessä olevan sanomanvälityspalvelimen (MMSC);ja kolmannen osion (Security ID), joka on määritettävissä mainittujen ensimmäisen ja toisen osion perusteella turvallisuustarkoitusta varten.
- 13Solukkoverkon ulkopuolinen palvelin (MMSC) määrätyn solukkoverkon päätelaitteeseen (MS) liittyvän tiedon kysymiseksi solukkoverkosta, tunnettu siitä, että palvelin käsittää:välineet (55, 56) määrätyn solukkoverkon ulkopuolisen ensimmäisen 25 tunnisteen (MMS-ID) määrittämiseksi mainitun päätelaitteen (MS) tunnistamiseksi;välineet (51,55) kyselyn (41) lähettämiseksi palvelimelta (MMSC) solukkoverkkoon mainitun päätelaitteeseen (MS) liittyvän tiedon selvittämiseksi, joka kysely käsittää mainitun ensimmäisen tunnisteen (MMS30 ID).
- 14Patenttivaatimuksen 13 mukainen palvelin (MMSC), tunnettu siitä, että se käsittää:välineet (51,55) solukkoverkosta mainitulle solukkoverkon ulkopuoliselle palvelimelle (MMSC) vasteena mainittuun kyselyyn (41) lähetetyn vastausviestin (47) vastaanottamiseksi, joka vastausviesti käsittää mainitun ensimmäisen tunnisteen (MMS-ID) avulla ilmaistun mainittuun 5 päätelaitteeseen (MS) liittyvän tiedon.
- 15Patenttivaatimuksen 13 mukainen palvelin (MMSC), tunnettu siitä, että palvelin on järjestetty lähettämään mainitun kyselyn (41) vasteena palvelimeen saapuneeseen päätelaitteelle (MS) osoitettuun sanomaan; ja 10 että palvelin (MMSC) käsittää:välineet (51,56) päätelaitteelle osoitettuun sanomaan liittyvän osoitteen kohdentamiseksi mainittuun päätelaitteen ensimmäiseen tunnisteeseen. 15
- 16Solukkoverkon ulkopuolisessa palvelimessa (MMSC) suoritettavissa oleva tietokoneohjelmatuote määrätyn solukkoverkon päätelaitteeseen (MS) liittyvän tiedon kysymiseksi solukkoverkosta, tunnettu siitä, että tietokoneohjelmatuote käsittää ohjelmakoodin:määrätyn solukkoverkon ulkopuolisen ensimmäisen tunnisteen 20 (MMS-ID) määrittämiseksi mainitun päätelaitteen (MS) tunnistamiseksi;mainitun palvelimen (MMSC) saamiseksi lähettämään kyselyn (41) solukkoverkkoon mainitun päätelaiteeseen (MS) liittyvän tiedon selvittämiseksi, joka kysely käsittää mainitun ensimmäisen tunnisteen (MMSID) mainitun päätelaitteen tunnistamiseksi.
- 17Solukkoverkon verkkoelementti (GGSN), joka käsittää:välineet (66, 67) määrätyn solukkoverkon ulkopuolisen palvelimen lähettämän kyselyn (41) vastaanottamiseksi, joka kysely käsittää pyynnön määrätyn solukkoverkon päätelaitteeseen (MS) liittyvän tiedon 30 selvittämiseksi, tunnettu siitä, että kysely käsittää ensimmäisen tunnisteen (MMS-ID) mainitun päätelaitteen tunnistamiseksi, joka ensimmäinen tunniste on määrätty solukkoverkon ulkopuolinen tunniste;välineet (67, 69, DNS) mainitun ensimmäisen tunnisteen (MMS-ID) kohdentamiseksi määrättyyn toiseen tunnisteeseen (IMSI, IMUI), joka toinen tunniste on solukkoverkon sisäinen tunniste;välineet (61,62, 67) mainitun päätelaitteeseen (MS) liittyvän tiedon selvittämiseksi mainitun toisen tunnisteen (IMSI, IMUI) avulla;5 välineet (66, 67) vastausviestin (47) lähettämiseksi solukkoverkon ulkopuoliselle palvelimelle (MMSC) vasteena mainittuun kyselyyn (41), joka vastausviesti käsittää mainitun ensimmäisen tunnisteen (MMS-ID) avulla ilmaistun mainittuun päätelaitteeseen (MS) liittyvän tiedon. 10
- 18Patenttivaatimuksen 17 mukainen verkkoelementti (GGSN), tunnettu siitä, että mainittu verkkoelementti on solukkoverkon yhdyskäytävätukisolmu.
- 19Solukkoverkon verkkoelementissä (GGSN) suoritettavissa oleva tietokoneohjelmatuote, joka käsittää ohjelmakoodin:15 verkkoelementin (GGSN) saamiseksi vastaanottamaan määrätyn solukkoverkon ulkopuolisen palvelimen (MMSC) lähettämän kyselyn (41), joka kysely käsittää pyynnön määrätyn solukkoverkon päätelaitteeseen (MS) liittyvän tiedon selvittämiseksi, tunnettu siitä, että kysely käsittää ensimmäisen tunnisteen (MMS-ID) mainitun päätelaitteen (MS)
- 2020 tunnistamiseksi, joka ensimmäinen tunniste on määrätty solukkoverkon ulkopuolinen tunniste;mainitun ensimmäisen tunnisteen (MMS-ID) kohdentamiseksi määrättyyn toiseen tunnisteeseen (IMSI, IMUI), joka toinen tunniste on solukkoverkon sisäinen tunniste;
- 2125 verkkoelementin (GGSN) saamiseksi selvittämään mainitun päätelaitteeseen (MS) liittyvän tiedon mainitun toisen tunnisteen (IMSI, IMUI) avulla;verkkoelementin (GGSN) saamiseksi lähettämään vastausviestin (47) solukkoverkon ulkopuoliselle palvelimelle (MMSC) vasteena mainittuun
- 2230 kyselyyn (41), joka vastausviesti käsittää mainitun ensimmäisen tunnisteen (MMS-ID) avulla ilmaistun mainittuun päätelaitteeseen (MS) liittyvän tiedon. 20. Järjestelmä, joka käsittää solukkoverkon ulkopuolisen palvelimen (MMSC) ja solukkoverkon verkkoelementin (GGSN), solukkoverkon päätelaitteeseen (MS) liittyvän tiedon kysymiseksi solukkoverkolta solukkoverkon ulkopuolisesta palvelimesta käsin, tunnettu siitä, että palvelin käsittää:välineet (55, 56) määrätyn solukkoverkon ulkopuolisen ensimmäisen 5 tunnisteen (MMS-ID) määrittämiseksi mainitun päätelaitteen (MS) tunnistamiseksi;välineet (51,55) kyselyn (41) lähettämiseksi palvelimelta (MMSC) solukkoverkkoon verkkoelementille (GGSN) mainitun päätelaitteeseen (MS) liittyvän tiedon selvittämiseksi, joka kysely käsittää mainitun ensimmäisen 10 tunnisteen (MMS-ID), ja että solukkoverkon verkkoelementti käsittää: välineet (66, 67) mainitun kyselyn (41) vastaanottamiseksi;välineet (67, 69, DNS) mainitun ensimmäisen tunnisteen (MMS-ID) kohdentamiseksi määrättyyn toiseen tunnisteeseen (IMSI, IMUI), joka toinen tunniste on solukkoverkon sisäinen tunniste;15 välineet (61,62,67) mainitun päätelaitteeseen (MS) liittyvän tiedon selvittämiseksi mainitun toisen tunnisteen (IMSI, IMUI) avulla;välineet (66, 67) vastausviestin (47) lähettämiseksi solukkoverkon ulkopuoliselle palvelimelle (MMSC) vasteena mainittuun kyselyyn (41), joka vastausviesti käsittää mainitun ensimmäisen tunnisteen (MMS-ID) avulla 20 ilmaistun mainittuun päätelaitteeseen (MS) liittyvän tiedon.
Independent claims22
120 paragraphs, as filed
Message forwarding - Förmedling av ett meddelande
The present invention relates to a messaging service.
In particular, but not necessarily, the invention relates to store-and-forward messaging in a wireless communication system.
Wireless communication networks and the Internet are expanding rapidly and have a growing number of users. Global System for Mobile (GSM)
Communications) The General Packet Radio Service (GPRS) provides means for packet data transmission over a cellular radio network. GPRS also provides an interface to other packet switched networks, such as the Internet.
Figure 1 illustrates communications network connections in a packet switched GPRS15 service. The main element of the network infrastructure for GPRS services is the GPRS support node. The GPRS support nodes are divided into serving GPRS support nodes SGSN (Serving GPRS Support Node), which in packet data transmission correspond to known GSM network switching centers MSC (Mobile Switching Centers).
Switching Center), and GPRS Gateway GPRS Support Node (GGSN). The SGSN is a support node that transmits data packets to a wireless terminal MS (Mobile Station) and receives data packets transmitted by a wireless terminal through a base station system BSS consisting of base stations BTS and base station controllers BSC. By wireless terminal MS in this specification is meant all terminals that communicate over a particular radio interface. Thus, a computer terminal that communicates via a mobile station connected thereto is also referred to herein as a wireless terminal. SGSN also maintains location information of wireless terminals moving within its service area with GPRS registers (not shown in Figure 1). Physically, the SGSN is typically implemented as a separate network element. The GGSN communicating with the SGSN implements the interconnection and communication with other networks. Such other networks may include, but are not limited to, another operator's GPRS (cellular) network or a private network such as a corporate intranet, a public switched packet data network (PSPDN) such as the Internet or X. 25 network.
The user of a computer terminal connected to the Internet has long been able to retrieve multimedia elements such as images, text, video clips and audio clips in electronic form from his Internet terminal to a server on the Internet. server).
With increasing data rates and improved mobile capabilities, interest in the multimedia messaging service, and in the messaging service in general, has now also arisen in the wireless network. In particular, the GPRS network and third generation mobile networks, such as CDMA2000 (Code Division Multiple Access) and WCDMA (Wideband CDMA), are well suited for implementing multimedia messaging services as packet switched networks.
A multimedia messaging service has been proposed for third generation mobile networks, which would be implemented in a manner similar to the Short Message Service (SMS) in a GSM network, i.e., substantially step-by-step transmitting messages addressed to a wireless terminal to a specified terminal to a wireless terminal. Preferably, said messaging server would be located outside the cellular network in question, for example on the Internet.
Let's look at the GPRS network below. In the GSM network GPRS service '/ 25 The attached wireless terminal can send and receive short messages. The wireless terminal may send and receive packet data if it is connected to a GPRS network and has an activated PDP context (PDP = Packet Data).
Protocol) with a GGSN. Activation of the PDP context can occur at the request of either · · 30 wireless terminals or the network.
From time to time, it is appropriate for the proxy to make specific '·: requests to the GPRS network. For example, upon receipt of a message addressed to a particular wireless terminal, it is convenient for the messaging server, before sending the message to the GPRS network, to verify that the wireless terminal is actually ready to receive the message (i.e., having PDP context activated with a GGSN). In cellular networks, dynamic PDP addresses (such as dynamic IP addresses, Internet Protocol) are often allocated to terminals. In this case, the wireless terminal may not always have the same PDP address, but when requesting the wireless terminal PDP, the network will provide it with a PDP address, which may be the same PDP address that the wireless terminal was last used or another PDP address. , which PDP addresses are available for wireless terminals at any given time on the network.
When using dynamic IP addresses to perform the above query from outside the cellular network (GPRS network), there is a problem with identifying said wireless terminal: How to identify the wireless terminal from outside the cellular network to reliably perform queries about the wireless terminal even when the wireless terminal has a dynamic PDP address ?
A new solution has now been devised for wireless terminal identification. According to a first aspect of the invention, there is provided a method of querying cellular network terminal information from a cellular network ** from an external messaging server outside the cellular network.
The process is characterized in that the process:
Sending a query from the messaging server to find out information about said terminal in the cellular network, the query comprising a first identifier ,, for identifying said terminal device, the first identifier being a specific identifier outside the cellular network;
targeting the first identifier mentioned in the cellular network to the specified second »
'; 30 identifiers, the second identifier being an intra-cellular identifier;
The clearing of said second identifier by said terminal related information;
sending a response message from said cellular network to said external cellular messaging server in response to said query, wherein:
11215 said response message expressing said terminal related information by said first identifier.
According to another aspect of the invention, a server external to the cellular network 5 is implemented for requesting information about a particular cellular network terminal from the cellular network.
The server is characterized in that the server comprises:
means for determining a first identifier outside a particular cellular network to identify said terminal;
means for transmitting a query from the server to the cellular network for retrieving information related to said terminal, said query comprising said first identifier.
According to a third aspect of the invention, a computer program product executable on a server external to a cellular network is implemented for requesting information about a particular cellular network terminal from a cellular network. A computer program product is characterized in that the computer program product comprises program code:
determining a first identifier outside a particular cellular network to identify said terminal;
<sup>;</sup> causing said server to send a query to the cellular network for retrieving information related to said terminal, said query comprising said first identifier for identifying said terminal.
» <
According to a fourth aspect of the invention, a network element of a cellular network is implemented.
The network element is characterized in that it comprises:
. means for receiving a request transmitted by a server external to a specified cellular network, the request comprising a request for a specific cellular network; 30 for retrieving information relating to a terminal, the query comprising a first identifier for identifying said terminal, the first, identifier being a specific identifier outside a cellular network;
means for assigning said first identifier to a specific second identifier, the second identifier being an intra-cellular identifier; means for retrieving said terminal-related information by said second identifier;
means for transmitting a response message to a server external to the cellular network in response to said inquiry, the response message comprising information related to said terminal being detected by said first identifier.
According to a fifth aspect of the invention there is provided a computer program product executable in a network element of a cellular network.
A computer program product is characterized in that the computer program product comprises program code:
for causing the network element to receive a request transmitted by a server external to a particular cellular network, the request comprising a request for retrieving information relating to a terminal of a specific cellular network, and the query comprising a first identifier for identifying said terminal device; for assigning said first identifier to a specific second identifier, the second identifier being an intra-cellular identifier; causing the network element to retrieve said terminal-related information by said second identifier;
for causing the network element to send a response message to a server outside the cellular network in response to said request, the response message comprising information related to said terminal device detected by said first identifier.
According to a sixth aspect of the invention there is provided a system comprising an external cellular network server and a cellular network network element for requesting cellular network terminal information from an external cellular network server.
The system is characterized in that the server comprises:
means for determining a first identifier outside a particular cellular network to identify said terminal;
means for transmitting a query from a server to a cellular network network element for retrieving said terminal related information comprising said first identifier, and the cellular network network element comprising: means for receiving said query;
means for assigning said first identifier to a specific second identifier, the second identifier being an intra-cellular identifier;
means for retrieving said terminal-related information by said second identifier;
means for transmitting a response message to a server external to the cellular network in response to said inquiry, the response message comprising information related to said terminal being detected by said first identifier.
The terminal here may be any wireless terminal that can be connected to a GPRS network or a third generation network, for example a cellular network mobile station or a computer terminal connected to a GPRS network (e.g., a cellular network telephone). The term cellular network is to be interpreted broadly in this application, whereby the term cellular network is also considered to include, for example, the network elements of the GPRS service of the GSM network and the core network of the third generation network. Said server is a messaging server in a preferred embodiment of the invention, more particularly it is a multimedia messaging server located outside the cellular network in a packet data network such as an Intranet, Internet or X.25 network.
Said request from a server for cellular network cellular terminal information related information is addressed to a GPRS network network element, GGSN, in a preferred embodiment of the invention, to an external server.
To identify the terminal between the server and the cellular network, a predetermined non-cellular first identifier is used, which in the preferred embodiment of the invention is called an MMS-ID. Said first identifier is assigned to a specified second identifier in the cellular network. Said second identifier, which is an internal identifier of the cellular network and which may be, for example, an International Mobile Subscriber Identity (IMSI) code or the like, is used to identify the terminal within the cellular network and is not disclosed to network elements outside the cellular network.
The invention will now be described in detail with reference to the accompanying drawings, in which Figure 1 illustrates communications in a packet switched network
In the GPRS service, Figure 2 illustrates an arrangement according to the invention for implementing a messaging service, Figure 3 is a flowchart illustrating a method for implementing a messaging service according to the invention, and Figure 4 is a message diagram illustrating message flow in the method is a block diagram illustrating the functional blocks of the GGSN.
Figure 1 is described above in connection with the description of the prior art. Figure 2 illustrates an arrangement according to a first preferred embodiment of the invention for carrying out a messaging between a wireless terminal MS supporting GPRS and a messaging server. Figure 2 shows a wireless terminal MS, a base station system BSS, a serving GPRS support node SGSN and a GPRS gateway support node GGSN, a GPRS gateway support node GGSN located in a public operator mobile network (PLMN) of another operator.<sub>2</sub>, a packet data network PDN, which in a preferred embodiment of the invention is an IP network, a messaging server connected to an IP network, which in a first preferred embodiment of the invention is a Multimedia Messaging Service Center (MMSC), and a Home Location Register (HLR). MS routing information and GPRS subscriber information. By IP, this means either an intranet managed by a company and / or an operator, or an open public Internet10 network.
Figure 2 also shows interfaces between different network elements: Um interface between wireless terminal MS and base station system BSS, Gb interface between base station system BSS and SGSN, Gn interface between SGSN and GGSN, Gi interface with GGSN and the IP network, the Gr interface between the SGSN and the location register HLR, the Gc interface between the GGSN and the location register HLR, and the logical interface 22 of the invention between the GGSN and the MMSC. In addition, Figure 2 shows a logical Gp interface between GPRS cellular networks of different operators.
Technically, the GPRS support nodes of the same operator are interconnected in a cellular network by an operator's internal IP network (Intra-PLMN Backbone). However, this should not be confused with the above-mentioned intranet-based intranet network managed by the company and / or operator. Preferably, however, said IP25 networks (Intra-PLMN Backbone Network and Operator Managed Intranet) are interconnected, for example through a gateway.
By agreement between the operators, the GPRS networks of different operators are connected by a GPRS (Inter-PLMN Backbone) network between operators. In practice, there is typically still a firewall and a Border Gateway (BG) between the IntraPLMN Backbone network and the Inter-PLMN Backbone network. These are not shown in Figure 2.
The purpose of the interface 22 is to enable communication between the GGSN and the MMSC, inter alia, so that the GGSN is able to handle and respond to queries from the MMSC. The MMSC is preferably located outside the cellular network by the operator
Intranet network. Interface 22 is preferably implemented using the same protocol used in the operator's Intra-PLMN Backbone network, i.e., the IP protocol. The interface 22 may alternatively be implemented by another protocol of the same level.
Fig. 3 is a flowchart illustrating, in general terms, a method for implementing a messaging service according to a first preferred embodiment of the invention. The method determines the data reception capability of the wireless terminal MS, transmits this information to the MMSC and transmits in the case where the wireless terminal MS is ready to receive the data, the multimedia message
MMSCJ over the GPRS network to the wireless terminal MS.
Initially, the multimedia message addressed to the wireless terminal arrives at the MMSC and stores it in its memory (block 31). Next, the MMSC transmits to the GGSNs via interface 22 a query, or message, requesting the GGSNs to know whether the wireless terminal MS to which the multimedia message is addressed is ready to receive data (block 32). Said query uses the external cellular network identifier MMS-ID assigned in accordance with the invention to identify the wireless terminal, which will be presented later. The GGSN assigns the extracellular identifier mentioned in block 33 to a specific intracellular identifier (IMSI or the like). In block 34, the GGSN determines, using said cellular network identifier, whether the wireless terminal MS is ready to receive data. In the case of a GPRS network, the GGSN determines whether the PDP context of the wireless terminal is activated with any GGSN. If the wireless terminal MS is ready to receive data (PDP context activated with a GGSN), the GGSN transmits a positive response message to the MMSCJ via interface 22, again comprising said extracellular identifier (block 35a), after which the multimedia message transfer to the MMSCJ (block 36a). If the wireless terminal MS is not ready to receive data (PDP context is not activated), the GGSN sends a negative response message to the MMSC via interface 22 comprising said extracellular identifier (block 35b), whereupon multimedia message transfer from the MMSC to the wireless terminal MS cannot be initiated. 36b). Hereby, the query to determine the data reception capability of the wireless terminal MS can be repeated, for example, after a certain time (dashed line to block 32).
Said multimedia message may comprise a plurality of multimedia elements such as images in electronic form, text, video clips and audio clips. The address of the recipient of the multimedia message associated with the multimedia message may be, for example, the telephone number of the wireless terminal MS, the logical network address of the computer terminal connected to the GPRS network, or another address supported by GPRS. Typically, said address is in this form in the RFC822 format. RFC822 is an Internet standard that defines a format for communicating a logical address to a user in an understandable format. For example, one of the addresses in the RFC822 format is outi.aho@mmsc1.nokia1.com. Here mmscl .nokial .com is the logical address (so called domain name) of the MMSC in question. Also, the telephone number of the wireless terminal in the IP network can be converted to RFC822 format. Unique Resource Locator (URL) pointers may also be attached to said multimedia message.
The MMSC typically transmits the data readiness request of said wireless terminal MS to the same GGSN, hereafter referred to as the default GGSN. The default GGSN address (typically expressed as a logical domain name, such as ggsn1.nokia1.com) is stored in the MMSC. The MMSC is located in a packet data network. Preferably, the MMSC is located outside the GPRS cellular network in the IP network (Intranet30 network) of the operator that also controls said default GGSN. Alternatively, the MMSC may be controlled by an external service provider, such as an Internet network.
The plain-language address of the recipient of the multimedia message stored in the MMSC in the RFC822 format is mapped to a specific extracellular identifier in the MMSC, which is then used for communication between the default GGSN and the MMSC as the identifier of the wireless terminal MS.
Said extracellular identifier is referred to herein as the Multimedia Messaging Service IDentity (MMS-ID). For the purpose of targeting, the MMSC comprises a specific database for storing subscriber information of the multimedia messaging service of the wireless terminal MS. Similarities between the MMS-ID and the addresses of the wireless terminal in RFC822 format are also stored in said database. Said MMSC database is presented in conjunction with the description of Figure 5.
The MMS-ID is an identifier, parameter, or set of parameters outside the cellular network that indicates to the MMSC that the wireless terminal MS (terminal owner) in question has subscribed to the multimedia messaging service. MMS-ID is a generic data format, so it can look like text and look like this:
I MMSC ID I User ID I Security ID I, where the vertical line (I) separates different sections of the MMS ID, such as the MMSC ID, which is the identifier of the MMSC in question, the User ID, which is (multimedia messaging) subscriber identifier, and Security ID, which may be generated based on the MMSC ID and the User ID by a predetermined algorithm in the MMSC and the default GGSN. The Security ID can be used in a cellular network to ensure that the correct MMSC and the right subscriber are involved.
On the GPRS network side, the MMS-ID correspondence is stored in the IMSI code of the wireless terminal in question, which is an internal identifier of the cellular network. The database in which the recording is made can be implemented on a GPRS network, for example, using a Domain Name System (DNS) server. The IMSI code is used as the main subscriber identifier of a mobile terminal MS (mobile subscriber)
GPRS network. The IMSI code is typically stored on a SIM (Subscriber Identity Module) card. The SIM card is used as a subscriber identity unit in the wireless terminal MS. Thus, when referring, for example, to the IMSI code of a wireless terminal, this refers to the subscriber's known network
An IMSI code stored on a SIM card or the like, which in turn is placed in the wireless terminal MS. Similarly, when referring to a multimedia message addressed to a wireless terminal MS, this means a multimedia message addressed to a subscriber whose SIM card is in the wireless terminal MS, and so on.
Depending on the implementation, the database where the correspondences between the wireless terminal's MMS-ID and IMSI code are stored may be located at different locations in the telecommunications operator's GPRS network. The database should be easily accessible to the default GGSN. Said database may also be implemented in a manner suitable for a purpose other than a DNS server. It is also possible to integrate said database into the HLR, but this is preferably not done because the amount of data to be stored in the HLR is kept to a minimum.
Figure 4 is a message diagram illustrating the flow of messages in the MMSC and
Between parts of a GPRS network in a first preferred embodiment of the invention. After assigning the address of the recipient to the MMS-ID, the MMSC sends a query to determine the reception capability of the wireless terminal data to the default GGSN as a Client Identification Request message 41. The MMS-ID is supplied with this message. Thereafter, specific authentication and security functions 42 may be performed to ensure that the MMSCJ is authorized to execute said query. Typically, the Security ID section of the MMS-ID is utilized here, whereby the default GGSN builds the Security ID based on the MMSC ID and User ID contained in the MMS-ID by a certain predetermined algorithm and compares it with the MMS-ID: n provided with the Security ID (provided by the MMSC). Alternatively, another security mechanism may be used.
The default GGSN assigns the MMS ID supplied with the Client Identification Request message 41 to the IMSI code of the wireless terminal to which the MMSID belongs. The default GGSN performs said assignment by asking the aforementioned database, where the correspondences between the wireless terminal's MMS-ID and IMSI code are stored (e.g., a DNS server), an IMSI code corresponding to said MMS-ID.
Next, the default GGSN, which maintains the PDP context parameters and fields (e.g., the IP address) of the wireless terminals, examines whether the wireless terminal having that IMSI code has the PDP context activated with the default GGSN in question. If the PDP context is activated, the default GGSN knows that the wireless terminal MS is ready to receive data. In this case, the default GGSN also knows the IP address of the wireless terminal, whether statically or dynamically allocated. Now, the default GGSN sends a positive Client Identification Response message 47 in response to the query, stating that the wireless terminal MS having that MMS ID is ready to receive data. Said positive Client Identification Response message 47 may indicate the IP address (either dynamic or static) of the wireless terminal ready to receive the data, or simply indicate that the wireless terminal MS having said MMS ID is ready to receive data via said default GGSN. .
If the MMSC is logically located in a GPRS (cellular) network, for example in the operator's own Intranet, the interface 22 can then be used to send the multimedia message itself to the default GGSN (and further to the wireless terminal MS). If the MMSC is located in a packet data network (e.g., an Internet network) which is controlled by an external service provider, the multimedia message is also typically sent to the MS via the Internet network. According to the invention, the multimedia message on the cellular network side is no longer preferably stored in any network element, but data packets are continuously provided to the wireless terminal MS. This advantage is achieved by placing the MMSC outside the cellular network. Sending data from a packet data network to a GPRS network is well known to those skilled in the art.
If the wireless terminal MS has no activated PDP context with the default GGSN, the default GGSN determines whether the wireless terminal MS has an activated PDP context (data connection) with any other GGSN. To resolve this, the default GGSN preferably performs a query PDU Info Request message 43 (PDU = Protocol Data Unit) over interface Gc to the home location register HLR. Alternatively, if the interface Gc is not implemented in the system, the GGSN may send the PDU Info Request message 43 'over the interface Gn to the SGSNs and request the SGSN to forward the message 43' to the Gryli HLR.
It should be noted here that the PDU Info Request message 43, 43 'need not be transmitted at all if the wireless terminal MS has a PDP context activated with the default GGSN, i.e., the GGSN to which the Client Identification Request message 41 originally originated from the MMSC. sent. Therefore, the PDU Info Request message 43, 43 'and the PDU Info Response message to be sent in due course
44, 44 'is indicated by a broken line in Fig. 4.
HLR maintains GPRS subscriber data for wireless terminals. For example, information about PDP contexts that may be activated by a wireless terminal with a particular IMSI code can be found in the HLR PDP context subscription records. PDP context
·. ·. The 20 subscription records fields also include an Access Point Name (APN) field, which indicates for each IMSI the Access Point from which that wireless terminal MS may connect to an external packet data network. An external packet data network refers here, for example, to> «'· *: an Internet network. Upon receipt of the PDU Info Request message 43,43 ', in the next step of the method, based on the IMSI code of the wireless terminal MS transmitted with the PDU Info Request message 43,43', the APN field is used to determine what are the logical j access points for that IMSLI. names.
: · - · 30 The logical names of the access points mentioned are transmitted by HLR in the default * ·, GGSNJee PDU Info Response message 44,44 '. The PDU Info Response message is sent from the HLR to the default GGSN either directly via the Gc interface (Message 44)
IM or SGSN over interfaces Gr and Gn (message 44 '). The access point names indicate to the default GGSN the GGSNs to which the wireless terminal MS may have PDP context activated. The PDP context may be activated, for example, with the GGSN of another GPRS network or the GGSN of another GPRS network (other PLMN) managed by a telecommunications operator, such as
GGSN<sub>2</sub>(Figure 2).
In the next step, the default GGSN that received the initial query from the MMSC determines whether any of the GGSNs with which the wireless terminal MS can have the PDP context activated, based on the PDU Info Response message, is actually activated. This clarification is done by sending a message 45 (Other GGSN, Figure 4) to said GGSNs, providing the IMSI code of the wireless terminal in question and requesting, based on said IMSI code, each GGSN to investigate from its own PDP context field whether the wireless terminal context activated with the GGSN in question. The GGSNs managed by the same operators are interconnected by an intra-operator IP network (Intra-PLMN Backbone Network) so that the address of the recipient of the clearing message 45 can be the domain name of each GGSN. Settlement messages to the GGSNs of the other 45 operators may be sent via the Gp interface between different operators defined in the GPRS or via the IP20 network over the Gi interface. Preferably, however, the Gi interface is not used because the secret IMSI code of the wireless terminal is not intended to be communicated to non-GPRS network elements for security reasons. Each GGSN to which said message is sent responds to the default GGSN that sent 46 messages 45, whether the GGSN has an activated PDP context with the wireless terminal MS having that IMSI code. Preferably, in the case where said GGSNJ has a PDP context activated with said wireless terminal MS, the response message comprises a PDP address (e.g., an IP address) of said wireless terminal, especially if it is of a dynamic type. Said information is derived from the context parameter values maintained by each of said GGSNs for said PDP30.
After receiving the replies, 46 default GGSNs send either positive or negative
47 over the interface 22 of the Client Identification Response message in the MMSC.
11215
The positive Client Identification Response message 47 includes the knowledge that the wireless terminal having the MMS ID in question is ready to receive data through a specific GGSN. Preferably, the message 47 thus includes the MMS ID in question.
Said specific GGSN is the GGSN with which the wireless terminal MS is PDP context activated. If a PDP context with more than one GGSN is activated on the wireless terminal, the addresses of all these GGSNs can be reported to the MMSCs. In addition, said positive Client Identification Response message 47 may indicate a PDP address, such as an IP address, of a wireless terminal ready to receive data.
The negative Client Identification Response message 47 includes information that the wireless terminal having the MMS ID is not ready to receive data, for example, the MMSC may send a new query to the default GGSN to determine the data readiness of the wireless terminal MS after a predetermined time. dispatch.
Alternatively, the default GGSN may check the wireless terminal's data readiness by sending a slightly modified PDU Info Request message to the 43.43 'HLR. In this case, HLR first looks at its SGSN Address
field, the address of the SGSN currently serving the wireless terminal MS, and then asking that SGSNJ based on the IMSI code of the wireless terminal over the Gr interface whether the wireless terminal MS has a PDP context activated with any GGSN. The GGSN with which the wireless terminal MS has activated the PDP context is evident, for example, from the value of the GGSN Address in use parameter maintained by that SGSN. Upon receiving its request from the SGSNJ, the HLR forwards the PDU Info Response message 44, 44 'to the default GGSN as described above. It is also possible that the HLR provides the SGSN address of the SGSN serving the wireless terminal MS with a default GGSNJ, after which the default GGSN asks said SGSNJ based on its IMSI code
The GGSN address with which the wireless terminal MS has the PDP context activated.
According to the invention, the GGSN may also refuse to forward the message from the MMSC to the wireless terminal. For example, if the telephone bills of the wireless terminal MS have not been paid, the default GGSN may return a negative Client Identification Response message 47 to the MMSC indicating that multimedia messaging to that wireless terminal MS is not allowed.
Naturally, the database where the billing information of the wireless terminal MS is stored in the GPRS network should then be accessible to the default GGSN. Said negative Client Identification Response message 47 is also typically sent in the event that the aforementioned authentication and security functions 42 fail. In this case, the execution of the method according to the invention is also typically terminated in the cellular network even before the MMS-ID is assigned to IMSL.
Upon receipt of a positive Client Identification Response message 47, the MMSC transmits a multimedia message as data packets to the GGSN with which the PDP context is activated by the wireless terminal. Said GGSN forwards the data packets to the wireless terminal MS.
The MMSC may send data packets to said GGSNs via a default GGSN or via a packet data network such as an IP network (e.g., Intranet, Internet). If said GGSN is served by an MMSC that is different from the MMSC that communicates with the default GGSN above, data packets may alternatively be sent to said GGSN via this other MMSC. For communication between the MMSC and the wireless terminal MS, IP protocols or other protocols supported by the GPRS network can be used.
In the first preferred embodiment of the invention, said multimedia message transmitted by the MMSC to the wireless terminal subscribed to the multimedia service may originate from a variety of sources. It can be, for example, a photo, fax, home video clip, or audio message sent from one wireless terminal to another in electronic form. It may also include, for example, an e-mail message sent from the TCP / IP network to the MMSC containing a multimedia component for transmission to the wireless terminal, or any message containing multimedia components. Although primarily referred to as a multimedia message, the invention is not limited to the multimedia messaging service,
11215 but may be used in any similar messaging service.
Alternatively, the messaging service may be implemented on a suction-type basis. In this case, the messaging server sends a notification message to the wireless terminal MS in its memory as a token of the message addressed to the wireless terminal. The wireless terminal may then decide to retrieve said message from the messaging server to the wireless terminal MS. Said notification message can be sent as a short message (SMS) to the wireless terminal MS if it is connected to a GPRS network even if it has no PDP context activated with any GGSN. However, if the wireless terminal MS is connected to a GPRS network (MS is in GPRS attach mode), for example, said notification message may request the wireless terminal MS to activate the PDP context to be able to receive messages (e.g., multimedia messages from the messaging server).
According to another preferred embodiment of the invention, a request is made from the messaging server to determine whether the wireless terminal is GPRS attach to know whether the wireless terminal can receive said short message message. This is done by sending, after storing the message addressed to the wireless terminal, the MMSC a slightly modified Client Identification Request message 41 requesting the default GGSN to determine whether the wireless terminal having that MMS ID is connected to the GPRS network.
The default GGSN uses the DNS server to allocate the MMS-ID to the IMSL of that wireless terminal and checks whether the wireless terminal is connected to the GPRS network by sending a PDU Info Request message 43, 43 'to the HLR. In this case, HLR will look at the SGSN Address field it maintains for the IMSI in question to determine whether
SGSN Address field filled with SGSN address. If the SGSN address is found in that field, said wireless terminal is connected to the GPRS network. If the SGSN Address field is blank, said wireless terminal is not connected to the GPRS network.
After judging whether said wireless terminal MS is connected to a GPRS network, the HLR transmits a PDU Info Response message 44, 44 'to a default GGSN, which sends either a positive or negative Client Identification Response message 47 to the MMSC.
A positive Client Identification Response message 47 indicates that the wireless terminal MS having that MMS ID is connected to the GPRS network and is thus ready to receive the notification message as a short message. The negative Client Identification Response message 47 indicates that said wireless terminal MS is not connected to a GPRS network, and it is not appropriate to send the notification message yet.
In addition to the GPRS network, the invention can also be implemented in third generation networks such as the WCDMA network, since the highest protocol levels correspond to the highest protocol levels of the GPRS network. GGSN is equivalent to 3G - GGSN (3rd generation network)<sup>rd</sup> Generation GGSN), SGSN corresponds to 3G-SGSN and BSS corresponds to 3G-RAN (3<sup>rd</sup> Generation Radio Access Network). According to one proposal, the IMSI (International Mobile User Identity) code and the SIM card a UIM (User Identification Module) are terminologically equivalent to the IMSI code in a third generation network.
The invention is also applicable to a WAP system. There is then a WAP gateway between the MMSC and the default GGSN, through which messages typically passing between the MMSC and the default GGSN are typically transparent.
The invention can be implemented programmatically by making the necessary changes to the program code in the GGSN. MMSC functionality can also be implemented programmatically. Such computer program products may be stored on a medium, such as memory, transferred, and run, for example, on a computer.
Figure 5 is a block diagram illustrating functional blocks of the MMSC in connection with the implementation of the present invention. The MMSC comprises a GPRS interface 51 through which the MMSC communicates with the GGSN of the GPRS network.
Communication via external interface 52 to other external networks such as the Internet and MMSC interface 53 to other multimedia messaging service centers is provided. Data warehouse 54 is a database in which multimedia messages are stored and stored. The control unit 55 controls
Activities of the MMSC. To map the multimedia message recipient's plain-language (RFC822 address) to the correct MMS-ID, the MMSC comprises a database 56 that maintains correspondences between plain-language RFC822 addresses and the MMS-IDs. In addition, the MMSC comprises some blocks related to authentication and MMSC maintenance (these are not shown in the figure).
According to the invention, multimedia messages addressed to the wireless terminal MS arrive at the MMSC via one of its interfaces (51-53) and are stored in a data warehouse 54. Based on the information in the database 56, the control unit assigns the plain language address (e.g. RFC82215 format) . Database 56 may be maintained, for example, by a telecommunications network operator or by an external service provider. Adding a new MMS-ID to said database 56 can be done, for example, as follows: When the owner of a particular wireless terminal MS subscribes to a multimedia messaging service, he provides the service provider with the wireless terminal MS addresses used (e.g., telephone number, email type address). The multimedia messaging service provider then agrees with the GPRS operator in question the appropriate MMS-ID value for uniquely identifying the wireless terminal. Said wireless terminal addresses and their corresponding MMS-ID are stored in the MMSC database 56. Similarly, the same MMS25-ID is stored on an operator-managed DNS server in the GPRS network at the IMSI code corresponding to these addresses. The Client Identification Request to be sent to the GGSN is preferably generated in the GPRS interface 51 at the command of the control unit 55, and is transmitted through the GPRS interface 51. GPRS interface 51 and the GGSN to be introduced in connection with the description of Figure 6
The MMSC interface 66 jointly implements the interface 22. Also, the Client Identification Response sent by the GGSN is received via the GPRS interface 51. The MMSC interface (51-53) through which multimedia messages are transmitted in due course to the wireless terminal MS may vary depending on the location of the MMSC and the wireless terminal.
Figure 6 is a block diagram illustrating functional blocks of a GGSN in connection with the implementation of the present invention. The GGSN comprises an SGSN5 interface 61 through which the GGSN communicates with a cellular network operated by its own operator (Intra-PLMN Backbone Network). The GGSN communicates with the HLR via the HLR interface 62. Through this it is also possible to communicate with other elements of the signaling network (e.g. SS7). Through IP interface 63, GGSN communicates with IP networks (e.g. Internet) and via the X.25 interface 64 with the X.25 packet network. Through the MMSC interface 66, the GGSN transmits and receives messages to the MMSC GPRS interface 51 and the MMSC GPRS interface 51 according to the invention. MMSC interface 66 and MMSC GPRS interface 51 together implement interface 22.
The routing fuction 65 transmits data packets both within the operator-managed network and between the operator-managed network and other networks. A DNS server is a separate device that is typically controlled by the same operator as GGSN. The GGSN control unit 67, which controls the operation of the GGSN, has a connection 69 to a DNS server. The DNS server has information
MMS IDs and IMSI codes for wireless terminals. The control unit 67, in accordance with the invention, assigns the MMS-ID received with the Client Identification Request message 41 from the MMSC to the correct IMSI code, asking the DNS server over the above connection 69 for an IMSI code corresponding to said MMS-ID.
According to the present invention, an external identifier, such as an MMS ID, is used to identify the wireless terminal MS, which uniquely identifies that wireless terminal MS, regardless of the RFC822 wireless address of the wireless terminal being used.
Thus, the IMSI code used to uniquely identify a wireless terminal within a cellular network need not be disclosed outside the cellular network. The use of the MMS-ID further provides the advantage that if the RFC822 address of the wireless terminal changes, no changes need to be made to the cellular network (GPRS network). It is sufficient to update the new RFC822 address on the messaging server to match the wireless terminal's MMS-ID, which can still be used for communication between the messaging server and the cellular network.
The invention also enables wireless terminal queries to be performed from outside the cellular network also when using dynamic PDP addresses, since the MMS10 ID independent of the dynamic PDP address is used for communication between the messaging server and the cellular network. Said queries include, for example, a query to determine the wireless terminal's data reception capability and a query to determine the wireless terminal's connection to the GPRS network (i.e., a query to determine the short message's reception capability).
This description illustrates the implementation and embodiments of the invention by way of examples. It will be apparent to one skilled in the art that the invention is not limited to the details of the above embodiments, and that the invention may be embodied in other forms without departing from the features of the invention. The embodiments shown should be considered as illustrative but not limiting. Thus, the scope of the invention is limited only by the appended claims. Thus, the various embodiments of the invention as defined by the claims, including equivalent embodiments, are within the scope of the invention.
5 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5
10 members in 8 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 19992783 | Finland | A | |
| FI19990002783 | – | – | – |
Members10
| Document | Office | Kind | |
|---|---|---|---|
| FI19992783A | Finland | A | |
| US2001005675A1 | United States of America | A1 | |
| WO0149048A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU2379501A | Australia | A | |
| KR20020064955A | Republic of Korea | A | |
| EP1240787A1 | European Patent Office (EPO) | A1 | |
| CN1413421A | China | A | |
| JP2003518885A | Japan | A | |
| FI112151BThis record | Finland | B | |
| US6885870B2 | United States of America | B2 |
1 legal event, as the office reported them to INPADOC
Events
| Event | Code | |
|---|---|---|
| Patent expiredExpiredMA | MA |
Numbers
- Publication, DOCDB
- 112151
- Publication, EPODOC
- FI112151B
- Application
- 992783
- Application, DOCDB
- 19992783
- Application, EPODOC
- FI19190992783
Titles3
- English
- Messaging
- Finnish
- Sanoman välitys
- Swedish
- Förmedling av ett meddelande
Classification
- CPC, 2
- H04W4/12
- H04W88/184
- IPC, 3
- H04L12 56
- H04W4 12
- H04W88 18