[go: up one dir, main page]

WO2002007454A1 - Declenchement non lie aux appels dans un reseau intelligent - Google Patents

Declenchement non lie aux appels dans un reseau intelligent Download PDF

Info

Publication number
WO2002007454A1
WO2002007454A1 PCT/EP2000/006757 EP0006757W WO0207454A1 WO 2002007454 A1 WO2002007454 A1 WO 2002007454A1 EP 0006757 W EP0006757 W EP 0006757W WO 0207454 A1 WO0207454 A1 WO 0207454A1
Authority
WO
WIPO (PCT)
Prior art keywords
detection point
short message
ussd
control means
service
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.)
Ceased
Application number
PCT/EP2000/006757
Other languages
English (en)
Inventor
Szamuel Pal
Auvo Hartikainen
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.)
Nokia Inc
Original Assignee
Nokia Inc
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 Nokia Inc filed Critical Nokia Inc
Priority to AU2000262740A priority Critical patent/AU2000262740A1/en
Priority to PCT/EP2000/006757 priority patent/WO2002007454A1/fr
Publication of WO2002007454A1 publication Critical patent/WO2002007454A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking

Definitions

  • the present invention relates to call-unrelated services in an Intelligent Network (IN) , and in particular to triggering a Short Message (SM) in a Short Message Service (SMS) or a USSD chain in an Unstructured Supplementary Service Data (USSD) Service.
  • SM Short Message
  • SMS Short Message Service
  • USSD Unstructured Supplementary Service Data
  • SMS Short Message Service
  • SMS Mobile Stations in an Intelligent Network.
  • SMSC Short Message Service Center
  • MO Mobile Originated
  • MT Mobile Terminated
  • the Unstructured Supplementary Service Data Service provides a means of carry textual data with limited size between a mobile station and an application in the network. This functionality can be seen as a tool to implement operator specific services, which require communication with the mobile subscriber.
  • the USSD transfer can be initiated by the mobile subscriber - Mobile Initiated (MI) - or by the application in the network - Network Initiated (NI) USSD.
  • MI mobile subscriber - Mobile Initiated
  • NI Network Initiated
  • a Service Switching Point comprising a Service Switching Function (SSF) on a Mobile Switching Center (MSC) and Visitor Location Register (VLR) side.
  • the SM is forwarded from the Visitor MSC to an Interworking Mobile Switching Center (I MSC) capable of receiving an SM from a Visitor MSC and submitting it to a recipient Short Message Service Center (SMSC) .
  • I MSC Interworking Mobile Switching Center
  • SMSC Short Message Service Center
  • the SMSC forwards the SM to a Gateway Mobile Switching Center (GMSC) capable of receiving a Short Message from the service center, interrogating a Home Location Register of a recipient mobile subscriber, and delivering the SM to the MSC of the recipient subscriber.
  • GMSC Gateway Mobile Switching Center
  • USSD In case of USSD there are two cases. The first one is the Mobile Initiated USSD.
  • the Visitor MSC receives and analyses the USSD string. The result of the analysis can be a supplementary service or a routing to an application entity. According to the Service Code the proper application will be switched with the Mobile Station and a conversation will start between them.
  • the second one is the Network Initiated case. In that case there is no analysis, and no Service Code.
  • the USSD string is simply forwarded to the Mobile Station.
  • the network can initiate a Notification type operation, meaning that the Subscriber is just notified about something, and the Subscriber does not respond to the notification (this operation consists just one dialogue) .
  • the request type operation requires the interaction of the Subscriber, it has to answer the request.
  • the operation between the mobile and the network both in Mobile Initiated and Network Initiated case can consist of one or more dialogues (the Notification in NI case is an exception - just one dialogue in this operation) .
  • the overall operation is called a session.
  • an intelligent network system supporting a call-unrelated service like the Short Message Service (SMS) or the Unstructured Supplementary Service Data (USSD) service between at least two network entities.
  • the system comprises a switching means (SSP) for receiving a call-unrelated data chain like a short message or a USSD string and processing it on the basis of stored subscriber data, and a control means (SCP) for controlling the processing operation of the switching means which is able to detect detection points in the subscriber data and reports to the control means upon detection of an event detection point previously armed by the control means .
  • SSP switching means
  • SCP control means
  • the object is achieved by a method of supporting a call-unrelated service like a Short Message Service (SMS) or Unstructured Supplementary Service Data Service in an intelligent network system between at least two network entities.
  • subscriber data including detection points are stored.
  • a call-unrelated data chain like a short message or a USSD string is received, it is processed on the basis of the stored subscriber data.
  • a short message or a USSD string is received, it is processed on, the basis of the stored subscriber data.
  • an event detection point is detected, which has previously been armed by a control means, it is reported to the control means.
  • the detection points comprise trigger detection points upon detection of which the control of the processing operation is transferred to the control means.
  • the trigger detection point may comprise a mobile originated detection point which is detected by the switching means upon receiving a short message from a sending subscriber.
  • the trigger detection point may comprise a mobile terminated detection point and a status report detection point, which are detected by the switching means upon receiving a short message from a short message serving means (SMSC, GMSC) .
  • SMSC short message serving means
  • GMSC GMSC
  • the trigger detection point may comprise a Mobile Initiated (MI) USSD detection point which is detected upon receiving a USSD string from a mobile subscriber.
  • MI Mobile Initiated
  • the trigger detection point may also comprise a Network Initiated (NI) USSD detection point which is detected upon receiving a USSD string from the Application Entity.
  • NI Network Initiated
  • the detection point may be an event detection point armed by the control means by Report Requesting upon detection of which the switching means reports to the control means a result of the processing operation.
  • the control means can request (arming operation) the switching means to send a report upon a certain outcome of the SMS or USSD operation.
  • the control means may be arranged to change short message data of the short message received by the switching means.
  • the subscriber data is stored in a subscriber database in the switching means.
  • an operator is allowed to create, implement new and better services based on call- unrelated control like SMS and USSD, and manage the interaction between GSM (Global System for Mobile communications) and IN services.
  • GSM Global System for Mobile communications
  • the Service Control Point SCP
  • SSP Service Switching Point
  • This is important because, for example, according to the result of the Short Message transfer, a prepaid subscriber can be charged properly, for example, the prepaid subscriber does not have to pay after unsuccessful SMS transfer, and USSD service can be provided for prepaid subscribers.
  • SMS triggering detection points like MO, MT and Status Report (SR) triggering detection points enable redirection of Short Messages to another subscriber. Moreover, a user is allowed to prevent short messages from a certain source.
  • MO Metal Organic Chemical Vapor
  • SR Status Report
  • USSD triggering detection points like MI and NI USSD triggering detection points enable the operator to provide the USSD for the prepaid subscribers. With the introduced event detection points for successful and unsuccessful USSD operations the account of the prepaid subscriber can be handled in a correct way.
  • the end-user is able to use the new services created within the IN SMS. For example, the end-user can designate where he wants to receive short messages from and when he wants to forward them to another person. Because of the introduction of event reporting the prepaid subscribers can be charged properly.
  • the present invention will be described by way of preferred embodiments thereof by taking into account the accompanying drawings .
  • Fig. 1 shows a state model according to a Mobile Originated SMS.
  • Fig. 2 shows a block diagram of a network system performing a Continue/Connect operation for a Mobile Originated SMS.
  • Fig. 3 shows a block diagram of a network system performing a Release Call operation for a Mobile Originated SMS.
  • Fig. 4 shows a state model according to a Mobile Terminated SMS.
  • Fig. 5 shows a state model according to a Status Report SMS.
  • Fig. 6 shows a block diagram of a network system performing a Continue operation for Mobile Terminated and Status Report SMSs.
  • Fig. 7 shows a block diagram of a network system performing a Connect operation for Mobile Terminated and Status Report SMSs.
  • Fig. 8 shows a block diagram of a network system performing a Release Call operation for a Mobile Terminated SMS.
  • Fig.9 shows a block diagram of a network system performing a Mobile Initiated USSD-Continue operation.
  • Fig. 10 shows a block diagram of a network system performing a Mobile Initiated USSD-Release Operation.
  • Fig.11 shows a block diagram of a network system performing a Network Initiated USSD-Continue operation.
  • Fig. 12 shows a block diagram of a network system performing a Network Initiated USSD-Release operation.
  • the basic idea of the present invention is to introduce Triggering for call-unrelated cases, like SMS and USSD service.
  • Possible interfaces for implementing the triggering according to the present invention are the INAP (Intelligent Network Application Protocol) interface and the CAP (Camel Application Protocol) interface which is standardized in CAMEL (Customized Applications for Mobile Network Logic) .
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • other IP-based interfaces may serve as possible interfaces for implementing the present invention.
  • SSP Service Switching Point
  • MSC subscriber's Mobile Switching Center
  • SCP Service Control Point
  • SCF Service Control Function
  • the SCP can request the SSP for monitoring (arming) for a certain event and sending a report.
  • EDP Event Detection Point
  • the event itself is reported to the SCP by the SSP, if the EDP itself has been armed by the SCP.
  • Fig. 1 shows a state model for a Mobile Originated SMS (MO- SMS) transaction.
  • the Trigger Detection Point (TDP) SMS-DP1 which is a call processing point at which the activity in the SSP is suspended and the control is transferred to the SCP, is met after authentication and ciphering for the MO-SMS have been carried out and the MSC has received the Short Message from a subscriber or Mobile Station (MS) in an RP (Relay layer Protocol) -Data message (communication 1 in Fig. 2).
  • RP Real-layer Protocol
  • the SSP sends an Initiation request to the SCP as shown in communication 2 in Fig. 2.
  • the SCP can arm an Event Detection Point (EDP) as to whether the SMS is transmitted successfully (Successful outcome reporting) or an Event Detection Point as to whether a failure occurred in transmitting the SMS (Unsuccessful outcome reporting) or both as shown in Fig. 1, by sending a message RRB (Report Requesting: Bearer Capability SM) to the SSP (communication 3 in Fig. 2) .
  • EDP Event Detection Point
  • RRB Report Requesting: Bearer Capability SM
  • EDPs EDPs
  • the type of these EDPs is notification, so that the SCP does not do any further action after receiving the report from the SSP. Later, the SSP will respond with this report, i.e. a Event Reporting message (communication 8 in Fig. 2) if the event has been armed before and the conditions are met.
  • the SCP can react to the Initial DP message (SMS-DP1 in case of Fig. 1) in several ways. In the following cases, the short message transfer continues successfully.
  • Fig. 2 shows the Continue/Connect operation, when the EDP(s) are armed.
  • the SCP responds with the Continue message (communication 5 in Fig. 2) .
  • the short message transfer continues normally.
  • the MSC/VLR forwards the original Short Message to the original Interworking MSC (IWMSC) in a message MAP-MO-FSM (Mobile Application Part- Mobile Originated-Forward SM) (communication 6 in Fig. 2) .
  • MAP-MO-FSM Mobile Application Part- Mobile Originated-Forward SM
  • the IWMSC responds with a message MAP-MO-FSMAck (communication 7 in Fig. 2) .
  • the SCP responds with a Connect message (communication 5 in Fig.2) .
  • the SCP may change the destination, i.e. both an SMSC address and a called party where the Short Message was originally sent to.
  • the SCP may also change other parameters in an SM-Transfer Layer (SM-TL) message header, for example, the type of the message.
  • SM-TL SM-Transfer Layer
  • the MSC/VLR changes the SMSC address, if needed.
  • the MSC/VLR inserts the new header into the Short Message and sends it to the IWMSC.
  • the SCP may arm one or both EDPs by sending the message RRB to the SSP (communication 3 in Fig. 2) .
  • the MSC/VLR responds with the message ERB (communication 8 in Fig. 2) .
  • the SCP may send FurnishCharginglnformation (FCI) message (s) related to the Connect or Continue message (communication 4 in Fig. 2) .
  • FCI FurnishCharginglnformation
  • the MSC/VLR When the MSC/VLR receives the FCI message, it generates an IN Charging Data Record (IN CDR) .
  • the transparent information of the FCI message is included in the IN CDR. Note that the MSC/VLR may receive up to five sequential FCI messages which it combines to get the content of the IN CDR.
  • the short message transfer is successful and, thus, the MSC/VLR responds with a message RP Acknowledge (RP-Ack) to the MS (communication 9 in Fig. 2) .
  • RP-Ack message RP Acknowledge
  • the IN charging information is always sent at the end of the conversation from the MSC/VLR to the SCP, independently of the outcome of the SM transfer and the armed event type.
  • the MSC/VLR also generates a Short Message Mobile Originated (SMMO) CDR.
  • SMMO Short Message Mobile Originated
  • the generation of the SMMO CDR is not directly related to the SMS TDP, but as a result of the FCI message (s), the MSC/VLR includes additional information elements in the SMMO CDR.
  • the SCP responds with a Release Call message (communication 5) .
  • the MSC/VLR acknowledges the MS with an error cause given by the SCP (communication 6 in Fig. 3) .
  • the Short Message is not forwarded to the IWMSC.
  • the SCP may also send the RRB message and FCI message (s) (communications 3 and 4), but no ERB message is sent to the SCP and no IN CDR is created.
  • Fig. 4 shows a state model for a Mobile Terminated SMS (MT- SMS) transaction and Fig. 5 shows a state model for a Status Report transaction.
  • MT- SMS Mobile Terminated SMS
  • the TDPs are met at the earliest possible point after the MSC has received a Short Message from a GMSC in a MAP-MT-FSM message according to Fig. 6, and the recipient subscriber data in the VLR have been checked.
  • the MSC/VLR sends an Initial DP request (SMS-DP2 in Fig. 4 and SMS-DP3 in Fig. 5) to the SCP.
  • the SCP can react to the Initial DP message (communication 2 in Fig. 6) in several ways. In the following cases, the short message transfer continues: 1.
  • the SCP responds with the Continue message (communication 5 in Fig. 6) .
  • the short message transfer continues normally. After receiving the Continue message, the MSC/VLR starts paging (communication 6) and forwards the Short Message to the MS (communication 7). Moreover, the MSC/VLR acknowledges the receipt of the Short Message to the GSMC in communication 9.
  • the SCP can arm the EDP_SMS_Successful and/or EDP_SMS_Failure detection points with the RRB message (communication 3) . Later the MSC/VLR will respond with the ERB message (communication 10) to the SCP if the conditions are met.
  • the SCP responds with a Connect message according to Fig. 7.
  • the SCP wants to reroute the Short Message, it sends the Connect message to the MSC/VLR (communication 5) after receiving the Initial DP request therefrom.
  • the SCP may affect the transfer as follows.
  • the SCP provides the address of the SMSC. If it is not provided, the Short Message is forwarded to the SMSC which originated the message.
  • the SCP may arm the EDPs. But in the case of an MT- or State Report-SMS Connect, the MSC/VLR disarms the request of the SCP.
  • the SCP changes the SM-TL message header of the Short Message.
  • the requirement for the SCP is that it must change the short message type from MT to MO.
  • the SCP may change the called number.
  • the MSC/VLR When the MSC/VLR has received the Connect message, it generates an MO SM and forwards it to the specified IWMSC (communication 6) . After receiving the acknowledgment from the IWMSC (communication 7), the MSC can report the success of the transfer to the GMSC (communication 8) . The event will not be reported to the SCP. If the short message transfer to the SMSC is unsuccessful, the MSC reports an error back to the GMSC.
  • the SCP may send FCI messages (communication 4 in Figs. 6 and 7) .
  • FCI messages communication 4 in Figs. 6 and 7.
  • the MSC/VLR receives the FCI message, it generates the IN CDR.
  • the transparent information of the FCI message is included in the CDR. Note that the MSC/VLR may receive up to five sequential FCI messages which it combines to get the content of the IN CDR.
  • the MSC/VLR also generates the SMMT (Short Message Mobile Terminated) CDR or SMMF (Short Message Mobile Forwarded) CDR.
  • the generation of these CDRs is note directly related to the SMS TDP, but as a result of the FCI message (s), the MSC/VLR includes additional information elements in the SMMT CDR or SMMF CDR.
  • Figs. 6 and 7 show the Continue and Connect operations for MT and SR cases.
  • the SMSC may send several Short Messages via the GSMC within the same MAP transaction.
  • the handling of the MoreMessagesToSend is defined as a condition for " the MT-SMS and the SR-SMS TDP.
  • the SSP is either triggered in each message or only once in the whole transaction.
  • the IN CDR and ERB messages are also sent for each Short Message or just for the first message depending on the condition. In the following case the short message transfer is rejected:
  • the SCP responds with a Release Call message, which is shown in Fig. 8.
  • the MSC/VLR acknowledges the GMSC with an error cause given by the SCP (communication 6) . As a result, the message is not forwarded to the MS.
  • the SCP Before sending the Release Call in communication 5, the SCP may arm the EDP(s) in communication 3. Related to the Release Call message, the SCP may send the FCI message (s) in communication 4, but no IN CDR is created and no ERB is sent to the SCP.
  • Figure 9 shows a Mobile Initiated USSD operation, when the instruction of the SCP is to Continue normally.
  • the MSC/VLR receives the USSD string from the MS, and analyses it. The result of the analysis is routing.
  • the triggering for MI USSD is set.
  • the conditions are met for the SSP to contact with the SCP with the Initiation message.
  • the SCP can instruct the SSP for reporting with a Report Requesting message. This is called arming operation.
  • the Report Requesting the SCP specifies the event. In case of USSD the event can be successful and/or unsuccessful outcome. If the conditions are met, the SSP sends an Event Report either after each dialogue • or at the end of the whole operation (session) . This option can be set by the operator.
  • FIG 10 shows the case when the instruction of the SCP is to Release the connection in Mobile Initiated USSD case.
  • the MSC/VLR receives the USSD string from the MS, and the MSC/VLR analyses the string and the result is routing.
  • the subscription information fetched from VLR indicates that triggering must be done for MI USSD.
  • the SSP contacts with the SCP with the Initiation message.
  • the SCP responds with the Report Requesting operation, requesting the SSP to send report when the outcome of the USSD operation is successful and/or unsuccessful. Thereafter, it is followed by the instruction of the SCP to Release the connection.
  • the operation is stopped, a NACK message is sent back to the MS. There is no Event Report sent back to the SCP.
  • FIG. 11 shows the Network Initiated USSD operation with the Continue instruction.
  • the MSC/VLR receives the USSD string, and analyses it. The result is routing.
  • the triggering for NI USSD is set.
  • the conditions are met for triggering the control to SCP (with Initiation message) .
  • the SCP responds with Report Requesting, including the Event (s) for which the SSP must send a report.
  • the instruction of the SCP is to continue normally.
  • the SSP sends Event Report either after every USSD dialogue or at the end of the USSD operation, depending on the settings of the operator.
  • Figure 12 shows a Network Initiated USSD operation, where the instruction of the SCP is to Release the connection.
  • the MSC/VLR receives the USSD string, and analyses it. The result is routing.
  • the triggering for NI USSD is set.
  • the conditions are met for triggering the control to SCP (with Initiation message) .
  • the SCP responds with Report Requesting, including the Event (s) for which the SSP must send a report.'
  • the instruction of the SCP is to Release the connection.
  • the operation is stopped, a NACK message is sent back to the USSDC. There is no Event Report sent back to the SCP.
  • a preferred way to implement the present invention is to add a new field in subscribers' IN information for MO, MT and Status Report TDPs (DPI, DP2 and DP3) and for Mobile Initiated (MI) and Network Initiated (NI) USSD operation TDPs in the HLR and VLR subscriber database.
  • This information will be transferred for an SMS application program block in case of SM and for a USSD application program block in case of USSD, and according to the setting of this information, the SM or USSD can be triggered to the SCP.
  • the end-user is charged by generating the SMMO, SMMT or SMMF Charging Data Record (CDR) , depending on the case, and the IN CDR, when the FCI message is received in the MSC/VLR.
  • CDR Charging Data Record
  • the MSC In MT-SMS and SR-SMS cases the MSC generates the IN CDR and SMMT CDR, if the SCP responds with Continue. If the SCP responds with Connect, the MSC generated the IN CDR and SMMF CDR.
  • the contents of up to five FCI messages are included in the CDR.
  • the content of this information is transparent to the MSC/VLR.
  • the use of the IN CDR is similar to call-related cases except for the following:
  • the SMS reference is additionally needed in the IN CDR.
  • the reference is used to connect the SMMO, SMMT or SMMF CDR to the IN CDR.
  • the information content of the SMMO CDR is changed as follows :
  • the information content of the SMMT CDR is changed as follows : - Number of IN records. If set to 1, it indicates that the TDP is met and the FCI has been received.
  • the reference is used to connect the SMMT CDR to the IN CDR.
  • the SMMF CDR is a new CDR.
  • the content of this CDR is the same as the SMMT CDR, except for the following parameters: - Forwarded-to number. The changed number of the destination subscriber.
  • the IN CDR is generated at the end of the conversation between the SSP and the SCP. In case of Release Call the IN CDR is not created.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un système de réseau intelligent et un procédé correspondant qui se rapportent à des services non liés aux appels tels qu'un service de messages courts (SMS) et un service de données de complément de service non structuré (USSD). Un message court ou une chaîne USSD est reçu(e) et traité(e) par un système de commutation (SSP) sur la base des données d'abonné enregistrées. L'invention concerne aussi un système de commande (SCP) pour commander l'opération de traitement du système de commutation qui informe le système de commande (SCP) de la détection d'un point de détection d'événement préalablement armé par le système de commande.
PCT/EP2000/006757 2000-07-14 2000-07-14 Declenchement non lie aux appels dans un reseau intelligent Ceased WO2002007454A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU2000262740A AU2000262740A1 (en) 2000-07-14 2000-07-14 Call-unrelated triggering in intelligent network
PCT/EP2000/006757 WO2002007454A1 (fr) 2000-07-14 2000-07-14 Declenchement non lie aux appels dans un reseau intelligent

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2000/006757 WO2002007454A1 (fr) 2000-07-14 2000-07-14 Declenchement non lie aux appels dans un reseau intelligent

Publications (1)

Publication Number Publication Date
WO2002007454A1 true WO2002007454A1 (fr) 2002-01-24

Family

ID=8164024

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2000/006757 Ceased WO2002007454A1 (fr) 2000-07-14 2000-07-14 Declenchement non lie aux appels dans un reseau intelligent

Country Status (2)

Country Link
AU (1) AU2000262740A1 (fr)
WO (1) WO2002007454A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1465441A1 (fr) * 2003-04-04 2004-10-06 Siemens Aktiengesellschaft Extension d'un service d'envoi de messages courts (SMS) par utilisant des caractéristiques standardisées du type CAMEL
US7027799B2 (en) 2002-05-15 2006-04-11 Telefonaktiebolaget Lm Ericsson (Publ) Real time charging of delivery and receipt of short message service in a telecommunications network
EP1662815A1 (fr) * 2004-11-26 2006-05-31 Alcatel Gestion de SMS élevée dans un système de communication à base de CDMA
WO2006069595A1 (fr) * 2004-12-31 2006-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Systeme de telecommunications et procede de transfert de messages courts (sms) entre des terminaux et des services reseau intelligent
EP1763261A4 (fr) * 2004-07-23 2007-09-05 Huawei Tech Co Ltd Mise en oeuvre de service sms
CN100377606C (zh) * 2005-12-08 2008-03-26 华为技术有限公司 一种实现集群呼叫无关业务的方法及系统
CN100420317C (zh) * 2005-12-09 2008-09-17 华为技术有限公司 一种实现集群呼叫无关业务的方法及系统
WO2008130565A1 (fr) 2007-04-16 2008-10-30 Roamware, Inc. Procédé et système pour insérer un contenu publicitaire dans un message texte

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997050237A1 (fr) * 1996-06-24 1997-12-31 Ericsson Inc. Validation d'un acheminement a un numero dans un systeme de telecommunication mobile
WO1998028920A2 (fr) * 1996-12-20 1998-07-02 Telefonaktiebolaget Lm Ericsson (Publ) Transport de messages d'un service de courts messages (sms) dans un reseau de telecommunications
DE19717588A1 (de) * 1997-04-25 1998-12-24 Siemens Ag Verfahren und Kommunikationsnetz zur Administrierung zusätzliche Dienste

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997050237A1 (fr) * 1996-06-24 1997-12-31 Ericsson Inc. Validation d'un acheminement a un numero dans un systeme de telecommunication mobile
WO1998028920A2 (fr) * 1996-12-20 1998-07-02 Telefonaktiebolaget Lm Ericsson (Publ) Transport de messages d'un service de courts messages (sms) dans un reseau de telecommunications
DE19717588A1 (de) * 1997-04-25 1998-12-24 Siemens Ag Verfahren und Kommunikationsnetz zur Administrierung zusätzliche Dienste

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7027799B2 (en) 2002-05-15 2006-04-11 Telefonaktiebolaget Lm Ericsson (Publ) Real time charging of delivery and receipt of short message service in a telecommunications network
EP1465441A1 (fr) * 2003-04-04 2004-10-06 Siemens Aktiengesellschaft Extension d'un service d'envoi de messages courts (SMS) par utilisant des caractéristiques standardisées du type CAMEL
EP1763261A4 (fr) * 2004-07-23 2007-09-05 Huawei Tech Co Ltd Mise en oeuvre de service sms
JP2008507867A (ja) * 2004-07-23 2008-03-13 華為技術有限公司 ショートメッセージサービスの実現方法
EP1662815A1 (fr) * 2004-11-26 2006-05-31 Alcatel Gestion de SMS élevée dans un système de communication à base de CDMA
WO2006069595A1 (fr) * 2004-12-31 2006-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Systeme de telecommunications et procede de transfert de messages courts (sms) entre des terminaux et des services reseau intelligent
US7865199B2 (en) 2004-12-31 2011-01-04 Telefonaktiebolaget L M Ericsson (Publ) Telecommunication system and method for transferring SMS messages between terminals and intelligent network services
US9295104B2 (en) 2004-12-31 2016-03-22 Telefonaktiebolaget Lm Ericsson (Publ) Telecommunication system and method for transferring SMS messages between terminals and intelligent network services
CN100377606C (zh) * 2005-12-08 2008-03-26 华为技术有限公司 一种实现集群呼叫无关业务的方法及系统
CN100420317C (zh) * 2005-12-09 2008-09-17 华为技术有限公司 一种实现集群呼叫无关业务的方法及系统
WO2008130565A1 (fr) 2007-04-16 2008-10-30 Roamware, Inc. Procédé et système pour insérer un contenu publicitaire dans un message texte

Also Published As

Publication number Publication date
AU2000262740A1 (en) 2002-01-30

Similar Documents

Publication Publication Date Title
EP1457061B1 (fr) Traitement d'appels dans des reseaux de telecommunications mobiles
US9369590B2 (en) System and method for blocking the use of a service in a telecommunication system
EP1683375B2 (fr) Procede pour acheminer des messages sms au moyen d'un noeud de routage intelligent
CA2495232C (fr) Chargement en temps reel d'un service d'envoi de messages courts dans un reseau de telecommunication
EP2061284B1 (fr) Procédé et système fournissant une service de transferts des messages courts (SMS) inconditionelle
US6690942B2 (en) Mobile application part (MAP) interface for exchanging short messages with a SCP
US7684553B2 (en) Method for transmitting data in a communication network
US20110294462A1 (en) Charging of a short message transmission
WO2002007454A1 (fr) Declenchement non lie aux appels dans un reseau intelligent
US20100234003A1 (en) Who-called system for detecting and reporting slamdown calls in a mobile network
EP1865731B1 (fr) Procede pour realiser un service de messages courts (sms) et systeme de traitement de messages courts
US9247031B2 (en) Transaction proxy in a telecommunications or messaging system and related methods
WO2010075890A1 (fr) Gestion de rapports de remise de messages ayant une relation de type 1-plusieurs ou plusieurs-1
GB2411085A (en) Disrtibuted Message Transmission System

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

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

AL Designated countries for regional patents

Kind code of ref document: A1

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
ENP Entry into the national phase

Ref document number: 2003130958

Country of ref document: RU

Kind code of ref document: A

Format of ref document f/p: F

Ref document number: 2003128644

Country of ref document: RU

Kind code of ref document: A

Format of ref document f/p: F

Ref document number: 2003130959

Country of ref document: RU

Kind code of ref document: A

Format of ref document f/p: F

NENP Non-entry into the national phase

Ref country code: JP