EP2007152B1 - Verfahren, system und einrichtungen für nachrichtenrouten auf der basis der ip-übertragung - Google Patents
Verfahren, system und einrichtungen für nachrichtenrouten auf der basis der ip-übertragung Download PDFInfo
- Publication number
- EP2007152B1 EP2007152B1 EP07720605.0A EP07720605A EP2007152B1 EP 2007152 B1 EP2007152 B1 EP 2007152B1 EP 07720605 A EP07720605 A EP 07720605A EP 2007152 B1 EP2007152 B1 EP 2007152B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- message
- sending
- hss
- hlr
- called party
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 115
- 230000005540 biological transmission Effects 0.000 title claims description 22
- 230000008569 process Effects 0.000 claims description 73
- 102100024381 AF4/FMR2 family member 4 Human genes 0.000 description 23
- 101000833170 Homo sapiens AF4/FMR2 family member 4 Proteins 0.000 description 23
- 230000006870 function Effects 0.000 description 22
- 230000004044 response Effects 0.000 description 17
- 102000018059 CS domains Human genes 0.000 description 8
- 108050007176 CS domains Proteins 0.000 description 8
- 210000000329 smooth muscle myocyte Anatomy 0.000 description 8
- 230000008859 change Effects 0.000 description 5
- 238000003745 diagnosis Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 2
- 230000007423 decrease Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- VJYFKVYYMZPMAB-UHFFFAOYSA-N ethoprophos Chemical compound CCCSP(=O)(OCC)SCCC VJYFKVYYMZPMAB-UHFFFAOYSA-N 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
Definitions
- the present invention relates to the field of network communication technologies, and in particular, to a method, system and apparatus for routing messages based on IP transmission.
- FIG. 1 Currently, a network architecture of interworking between an IP Multimedia Subsystem (IMS)-based message service and a traditional Short Message Service (SMS) is shown in Figure 1 .
- IMS IP Multimedia Subsystem
- SMS Short Message Service
- SMS-SC Short Message Entity
- SMS-GMSC/SMS-IWMSC Gateway Mobile Switching Center for SMS/Interworking Mobile Switching Center for SMS
- HSS/HLR Home Subscriber Server/Home Location Register
- CGF/CDF Charging Gateway Function/Charging Data Function
- OCS Online Charging System
- SMC Short Message Center
- an SMC represents a network device that integrates SM-SC, SMS-GMSC and SMS-IWMSC into one.
- IP-SM-GW IP Short Message Gateway
- UE IP User Equipment
- SMS-GMSC/SMS-IWMSC existing WCDMA/GSM network short message protocols.
- An IMS core network contains core logic entities of an IMS domain: Serving Call Session Control Function (S-CSCF), Proxy Call Session Control Function (P-CSCF), and Interrogation Call Session Control Function (I-CSCF).
- S-CSCF Serving Call Session Control Function
- P-CSCF Proxy Call Session Control Function
- I-CSCF Interrogation Call Session Control Function
- the IMS core network provides a reliable connection between a UE and an IP-SM-GW.
- SIP Session Initiation Protocol
- the IP-SM-GW notifies the HSS that the UE has been registered and notifies the IP-SM-GW address to the HSS.
- the HSS saves the status of the IP user as IP Connected, and stores the IP user address and the registered IP-SM-GW address.
- MMI Message-Waiting-Indication
- the MWI is used for handling failure of sending messages caused by unreachable UE in the network or exceeded memory capacity of the UE in the traditional SMS.
- the MWI includes Messages-Waiting-Data (MWD), Mobile-station-Not-Reachable-for-GPRS (MNRG), Mobile-station-Not-Reachable-Flag (MNRF), Mobile-Not-Reachable-Reason (MNRR), and Mobile-station-Memory-Capacity-Exceeded-Flag (MCEF).
- MWD Messages-Waiting-Data
- MNRG Mobile-station-Not-Reachable-for-GPRS
- MNRF Mobile-station-Not-Reachable-Flag
- MNRR Mobile-Not-Reachable-Reason
- MCEF Mobile-station-Memory-Capacity-Exceeded-Flag
- Figure 2 shows the storage location of the information of the MWI in each Network Element (NE).
- the MWD stores the addresses of the SMCs (SC address).
- SMCs have originated a short message termination process to the UE corresponding to the MSIsdn-Alert.
- the short message termination process fails because the UE is unreachable in the network or memory capacity of the UE has been exceeded.
- the values of MNRF, MNRG, and MCEF are Boolean values.
- the MNRF value indicates that the failure of the short message termination process is caused by unreachable UE in the CS network domain; otherwise, the MNRF value is false. If the MNRG value is true, it indicates that the failure of the short message termination process is caused by unreachable UE in the PS network domain; otherwise, the MNRG value is false. If the MCEF value is true, it indicates that the failure of the short message termination process is caused by exceeded memory capacity of the UE; otherwise, the MCEF value is false.
- the MNRR indicates the cause for unreachable UE in the CS domain and/or PS domain. If the cause for unreachable UE is unknown, the MNRR is in the empty status; otherwise, the MNRR has four status values: No Paging Response via MSC (the UE makes no paging response in the CS domain), No Paging Response via SGSN (the UE makes no paging response in the PS domain), IMSI Detached (the UE is detached in the CS domain), and GPRS Detached (the UE is detached in the PS domain).
- SMS-GMSC When a short message termination process fails, SMS-GMSC receives a message failure delivery report sent by MSC, SGSN, or S-CSCF. In this case, the SMS-GMSC sends a message delivery status report to HSS/HLR.
- the message delivery status report carries the cause for failure of sending the message, such as unreachable UE or exceeded memory capacity of the UE.
- the message delivery status report further indicates whether the UE is unteachable in the CS domain and/or the PS domain, and further indicates the cause for unreachable UE, for example, no paging response, or detached in the network.
- the HSS/HLR updates the stored MWI according to the parameters carried in the message delivery status report sent from the SMS-GMSC. In this way, when the status of the UE changes (for example, when the UE is attached to the CS/PS domain again, or when the UE has free memory capacity), the HSS/HLR invokes the Alert-SC to originate the short message termination process again.
- the IP-SM-GW needs to send a message delivery report to the traditional message routing entity when sending of a termination message fails or succeeds, the traditional message routing entity knows whether the termination message is transmitted successfully only through the received message delivery report. Accordingly, the HSS/HLR knows whether the termination message is transmitted successfully only through the message delivery status report sent from the traditional message routing entity. Therefore, the HSS/HLR is unable to update the stored MWI according to the message delivery status report.
- the HSS/HLR still sends the routing information of the called party in the CS, PS and IMS domains to the IP-SM-GW in the subsequent message routing process of the called party. Therefore, the IP-SM-GW performs an unnecessary message routing process, which results in waste of network resources.
- the MWI stored in the HSS/HLR only reflects the status of UE in the CS and PS domains.
- the HSS/HLR is unable to perform a short message termination process in time. For example, after the short message termination process fails because the UE is unreachable in the CS, PS and IMS domains, if the UE status does not change in the CS and PS domains but changes only in the IMS domain (for example, when the UE is attached to the IMS domain), the HSS/HLR does not originate a short message termination process again. Consequently, the termination message does not be transmitted to the called party in time, the transmission delay of the termination message is high, and the Quality of Service (QoS) of the message service is low.
- QoS Quality of Service
- 3GPP "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Support of SMS and MMS over generic 3GPP IP access; Release 7" 3GPP DRAFT; TR 23.804-100 CLEAN, 3rd GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTR; 650, ROUTE DES LUCIOLES; F-06921 SOPHIA-ANTIPOLIS CEDEX; FRANCE, vol. SA WG2 , no. Budapest discloses an unsuccessful MT delivering procedure. Based on addresses received from the HLR/HSS, the SMS-GMSC shall attempt to deliver the short message via SGSN and/or MSC.
- the SMSC shall decide whether to set the message waiting flags. If it so decides, the SMSC sends MAP-REPORT-SM-DELIVERY-STATUS to the HLR/HSS with the address of the SM-SC having initiated the SMS MT delivery. And an SMS Alerting procedure discloses that if all SMS MT delivery attempts (via MSC, SGSN and IP-MESSAGE-GW) failed (e.g. because the UE was not reachable), the message to be transferred to IP Based UE is queued in the SM-SC, IP Based UE initiates the common registration procedure (e.g. it has recovered the IP connection to WLAN).
- the HLR/HSS receives the registration request from IP Based UE and any of message waiting flags are set, it sends MAP-Alert-SC request message with the list of the SM-SC addresses to SMS-SGMSC.
- the GMSC sends SC Alert request messages to SM-SCs whose addresses are informed by the HLR/HSS.
- 3GPP "3 rd Generation Partnership Project; Technical Specification Group Terminals; Technical realization of the Short Message Service (SMS); Point-to-Point (PP)" 3GPP TS 23.040 V3.1.0 discloses that the Messages-Waiting is the service element that enables the PLMN to provide the HLR, SGSN and VLR with which the recipient MS is associated with the information that there is a message in the originating SC waiting to be delivered to the MS.
- the service element is only used in case of previous unsuccessful delivery attempt(s) due to temporarily absent mobile or MS memory capacity exceeded.
- MNRG Mobile-station-Not reachable-for-GPRS
- MNRF Mobile-station-Not-Reachable-Flag
- the embodiments of the present invention provide a method, a system and an apparatus for routing messages based on IP transmission. Therefore, the HSS/HLR can provide available routing information accurately and quickly in a subsequent procedure of routing a message to a called party. This decreases the message transmission delay, improves the QoS of the message service, and improves the message routing efficiency of the traditional message routing entity and the IP-SM-GW.
- a method for routing messages based on IP transmission includes: when sending of a termination message of at least one called party in a network domain fails, receiving by a Home Subscriber Server/Home Location Register, HSS/HLR, from an IP-SMS-GW, information about failure of sending the termination message in the at least one network domain and storing said information; and performing, by the HSS/HLR, a subsequent procedure of routing the termination message to the called party according to the stored information, wherein the information about failure of sending a termination message comprises a termination message sending failure cause.
- HSS/HLR Home Subscriber Server/Home Location Register
- a system for routing messages based on IP transmission includes: a HSS/HLR and an IP-SM-GW.
- the HSS/HLR is configured to receive information, from an IP-SMS-GW, about from an IP-SMS-GW, failure of sending a termination message in at least one network domain when sending of a termination message of a called party in at least one network domain fails, and storing said information, and to perform a subsequent procedure of routing the termination message to the called party according to the stored information in the subsequent termination message routing process.
- the above technical solution reveals that, when sending of a termination message to a called party in at least one network domain fails, the HSS/HLR receives and stores information about failure of sending the termination message in at least one network domain. So that the HSS/HLR knows that sending of the termination message in certain network domains or all network domains fails. In this way, in the subsequent procedure of routing the termination message to the called party, the process of routing the termination message can be triggered in time when the HSS/HLR detects change of the status of the called party in any network domain. Therefore, the termination message can be transmitted to the called party at the earliest possible time. Moreover, the HSS/HLR can transmit available routing information to the IP-SM-GW or the traditional routing entity, thus avoiding unnecessary routing processes.
- the technical solution under the present invention decreases the message transmission delay, improves the QoS of the message service, and improves the message routing efficiency of the traditional message routing entity and the IP-SM-GW.
- Figure 1 shows a network architecture of interworking between a IMS-based message service and a traditional SMS.
- Figure 2 shows the location of the information in the MWI stored in each NE according to the prior art.
- Figure 3 shows the location of the information in the MWI stored in each NE in an embodiment of the present invention.
- Figure 4 is a flowchart of a method for routing messages based on IP transmission in an embodiment of the present invention.
- Figure 5 is a flowchart of a method for routing messages based on IP transmission in another embodiment of the present invention.
- Figure 6 is a flowchart of a method for routing messages based on IP transmission in further another embodiment of the present invention.
- the HSS/HLR can record the information about failure of sending the termination message in all network domains, the HSS/HLR is able to trigger the process of transmitting the termination message again by invoking the corresponding Alert function when the status of the called party changes in any network domain (for example, IMS domain).
- the network side does not transmit the termination message when the status of called party changes only in the IMS domain. Therefore, the termination message is transmitted to the called party at the earliest possible time, thus reducing the transmission delay of the termination message and improving the QoS of the message service.
- the HSS/HLR when sending of a termination message, in one or two of IMS network domain, CS network domain and PS domain, to the called party fails, if the HSS/HLR can record the information about failure of sending the termination message in these network domains, the HSS/HLR is able to transmit available routing information to the IP-SM-GW or the traditional message routing entity in subsequent procedure of routing the termination message to the called party, thus improving the message routing efficiency.
- the IP-SM-GW or the traditional message routing entity transmits the information about failure of sending the termination message to the HSS/HLR.
- the HSS/HLR receives and stores the information about failure of sending the termination message in these network domains. Therefore, in the subsequent termination message routing process of the called party, the HSS/HLR can transmit available routing information to the IP-SM-GW.
- the process of transmitting the termination message is triggered in time when the HSS/HLR or the IP-SM-GW detects that the status of the called party changes in any network domain and the HSS/HLR stores the information about failure of sending the termination message to the called party in all domains.
- the HSS/HLR stores an MWI.
- the MWI contains MWD, MNRG, MNRF, MNRR and MCEF.
- the MNRF, MNRG and MNRR indicate that the short message termination process fails because the called party is unreachable in the CS or PS network domain, and why the called party is unreachable in the CS or PS network domain.
- the MWI lacks the information indicating that the called party is unreachable in the IMS domain.
- it may define new information rather than using MWI to record the information about failure of sending the termination message caused by unreachable called party in the IMS domain or all domains.
- new information is added on the basis of the MWI stored in the HSS/HLR in an embodiment of the present invention.
- the newly added information can indicate that the called party is unreachable in the IMS network domain.
- it can add indication information into MWI to indicate that the called party is unreachable in all network domains, and add the cause value for why the called party is unreachable in the IMS network domain into the MWI.
- the information related to the message sending status can be stored into IP-SM-GW.
- MWI is stored in the IP-SM-GW.
- the MWI stored in the IP-SM-GW may be the same as the MWI stored in the HSS/HLR, or only part of the MWI stored in HSS/HLR, such as MWD for originating an Alert process and the information indicating that the called party is unreachable in the IMS, CS and PS domains.
- Figure 3 shows MWI in an embodiment of the present invention.
- an MNRA and an MNRI are added into MWI stored in the HSS/HLR, and two status values are added into MNRR.
- the MNRA indicates that the called party is completely unreachable in all network domains; and the MNRI indicates that the called party is unreachable in the IMS network domain.
- the values of MNRA and MNRI may be Boolean values.
- Two status values are added into the MNRR: "No Paging Response via the S-CSCF", which indicates that the called party makes no paging response in the IMS network domain; and "IMS Detached", which indicates that the called party is detached in the IMS network domain.
- the MWI stored in the IP-SM-GW may includes: MWD; MNRI, MNRG and MNRF.
- the parameters in the line box in Figure 3 can be used selectively as required by the implementation method.
- the HSS/HLR can update the MWI, which includes updating MNRA, MNRI and MNRR, according to the information carried in the received message such as the message delivery status report.
- the HSS/HLR receives a message delivery status report, and the HSS/HLR updates the MWI according to the information carried in the message delivery status report. Moreover, when the status of the called party in the network domains changes or memory capacity of the called party is available, the HSS/HLR updates the MWI.
- the HSS/HLR can instruct available routing information to the IP-SM-GW or the traditional message routing entity by invoking the Alert-SC according to the updated MWI, and originate a message termination process.
- the IP-SM-GW needs to update the MWI according to the information carried in the received message such as a message delivery status report.
- the IP-SM-GW can originate a message termination process by invoking the Alert-SC according to the updated MWI.
- the previous process in which the HSS/HLR updates the MWI may be: if the attempts of sending a termination message fail on all transmission paths because the called party is unreachable in all network domains, the HSS/HLR sets the MNRA value to "true”; or else to "false".
- the HSS/HLR sets the MNRI value to "true”; or else to "false”. In this case, the HSS/HLR needs to set the status value of the MNRR accordingly. If the value of the MNRA is "true”, when the status of the called party in the network domain changes, the HSS/HLR may update the MWI in the following three ways:
- the message delivery status report received by the HSS/HLR may be sent from the IP-SM-GW or the traditional message routing entity.
- the HSS/HLR may receive the message delivery status reports sent from the IP-SM-GW and the traditional message routing entity respectively.
- the IP-SM-GW sends the message delivery status report to the HSS/HLR in this process:
- the IP-SM-GW attempts to send the termination message on the paths provided by the HSS/HLR; when the message is sent successfully, or when the attempts of sending the message fail on all transmission paths, the IP-SM-GW may send a message delivery status report to the HSS/HLR.
- the message delivery status report sent by the IP-SM-GW carries the failure cause, that is, the called party is unreachable in all network domains.
- the IP-SM-GW may instruct the HSS/HLR to update the corresponding MWI, such as MNRI, MNRF, MNRG, and MNRR. Therefore, the HSS/HLR may trigger another process of transmitting the termination message by invoking the Alert-SC in a proper situation, for example, when the status of the called party in the network domain changes.
- the IP-SM-GW may update the MWI stored in it, such as MNRI, MNRF and MNRG, according to the status of sending the termination message.
- the process of triggering another process of transmitting the termination message by invoking the Alert-SC may be originated by the IP-SM-GW.
- the message delivery status report sent by the IP-SM-GW to the HSS/HLR carries the information about the failure path(s) and the cause of the unsuccessful sending(s). In this way, the HSS/HLR can know the status of the called party in time, and update the corresponding MWI.
- the IP-SM-GW may also update the MWI stored in it according to the information about the failure path(s).
- the IP-SM-GW may send a message delivery report to the traditional message routing entity. If the attempts of sending the termination message fail on all paths, the IP-SM-GW may send a message failure delivery report to the traditional message routing entity, carrying the failure cause.
- the IP-SM-GW can determined the failure cause carried in the message failure delivery report sent to the traditional routing entity according to the failure cause carried in the message failure delivery report sent from the S-CSCF, and/or SGSN, and/or MSC.
- the message delivery status report may be sent by the traditional message routing entity, rather than the IP-SM-GW, to the HSS/HLR. Nevertheless, the traditional message routing entity may send a message delivery status report to the HSS/HLR even if the IP-SM-GW already sends a message delivery status report to the HSS/HLR.
- the traditional message routing entity sends a message delivery status report to the HSS/HLR in this process:
- the traditional message routing entity receives a message failure delivery report from the IP-SM-GW, and sends a message delivery status report to the HSS/HLR according to the failure cause carried in the message failure delivery report, so as to instruct the HSS/HLR to update the corresponding MWI, such as MNRI, MNRF, MNRG, and MNRR. Therefore, the HSS/HLR may trigger another process of transmitting the termination message by invoking the Alert-SC in a proper situation, for example, when the status of the called party in the network domain changes.
- the process of triggering another process of transmitting the termination message by invoking the Alert-SC may be originated by the IP-SM-GW.
- the traditional message routing entity may determine the failure cause carried in the message failure delivery report sent to the HSS/HLR according to the failure cause carried in the message failure delivery report sent from the IP-SM-GW, and/or SGSN, and/or MSC, and send the message delivery status report to the HSS/HLR.
- IP-based message routing method in an embodiment of the present invention is described below, supposing that the traditional message routing entity sends a message delivery status report to the HSS/HLR.
- the IP-SM-GW receives a termination message from the traditional message routing entity, and stores the termination message. Then, the IP-SM-GW determines the priority of paths of sending the message according to the Network Domain Select (NeDS) function, and sends the termination message to the called party according to the priority of paths. For example, the priority of paths of sending the message is: S-CSCF -> SGSN -> MSC, the IP-SM-GW sends the message to the S-CSCF first; if the attempt of sending the message via the S-CSCF fails, the S-CSCF returns a message failure delivery report to the IP-SM-GW, carrying the failure cause.
- NeDS Network Domain Select
- the failure cause may include that memory capacity of the UE has been exceeded, the UE is unreachable, or the UE is unsupported.
- the S-CSCF may use a SIP message to send the message failure delivery report to the IP-SM-GW, carrying the failure cause in the body of the SIP message; or use a SIP response message to send the message failure delivery report to the IP-SM-GW.
- the IP-SM-GW After receiving the message failure delivery report from the S-CSCF, the IP-SM-GW decides the subsequence processing of the termination message according to the failure cause identified in the message failure delivery report. If the failure cause is exceeded memory capacity of the UE, the IP-SM-GW does not attempt to send the message on other paths, and deletes the stored message and send a message failure delivery report to the traditional message routing entity.
- the message failure delivery report sent by the IP-SM-GW carries the failure cause: exceeded memory capacity of the UE. If the message sending failure cause is not exceeded memory capacity of the UE, the IP-SM-GW may continue to send the message to the SGSN according to the priority of paths.
- the SGSN If the attempt of sending the message through the SGSN fails, the SGSN returns a message failure delivery report to the IP-SM-GW, carrying the failure cause in the failure report.
- the failure cause may include: memory capacity of the UE is unavailable, the UE is unreachable, or the UE is unsupported.
- the IP-SM-GW can decide the subsequent processing of the termination message according to the failure cause identified in the message failure delivery report, the details of which are not described here any further.
- the SGSN and the MSC may send the message failure delivery report to the IP-SM-GW through the existing RP-ERROR message in the current standards.
- the IP-SM-GW sends a message failure delivery report to the traditional message routing entity.
- the IP-SM-GW determines the failure cause of sending the message carried in the message failure delivery report sent to the traditional routing entity according to the failure cause carried in the message failure delivery report sent from the S-CSCF, SGSN, and MSC.
- the IP-SM-GW determines the failure cause in this process: If the message failure delivery report received by the IP-SM-GW contains at least one failure cause that indicates unreachable UE and contains no failure cause that indicates exceeded memory capacity of the UE, the IP-SM-GW determines the failure cause as unreachable called party. If the failure report received by the IP-SM-GW contains at least one failure cause that indicates exceeded memory capacity of the called party, the IP-SM-GW determines the failure cause as exceeded memory capacity of the UE. If the message failure delivery report received by the IP-SM-GW contains a failure cause that indicates unreachable UE and a failure cause that indicates unavailable memory capacity of the UE, the IP-SM-GW determines the failure cause as unavailable memory capacity of the UE.
- the IP-SM-GW decides the failure cause as: the failure cause identified in any message failure delivery report received.
- the IP-SM-GW may send the message failure delivery report to the traditional message routing entity through the existing RP-ERROR message in the current standards.
- the traditional message routing entity After receiving a message failure delivery report from the IP-SM-GW, the traditional message routing entity sends a message delivery status report to the HSS/HLR if determining that the failure cause identified in the message failure delivery report indicates unreachable UE or exceeded memory capacity of the UE.
- the message delivery status report may carry the address of the Short Message Center (SMC) that originates the message termination process, and the failure cause of sending the message, that is, unreachable UE or unavailable memory capacity of the UE.
- SMC Short Message Center
- the traditional message routing entity may send the message delivery status report to the HSS/HLR through an existing MAP-REPORT-SM-DELIVERY-STATUS message in the current standards.
- the HSS/HLR After receiving a message delivery status report from the traditional message routing entity, the HSS/HLR updates the MWI according to the information carried in the message delivery status report.
- the detailed update process may be: If the HSS/HLR determines that the stored MWD dose not contain SMC address carried in the received message delivery status report, the HSS/HLR inserts the SMC address carried in the message delivery status report into the stored MWD. If the failure cause carried in the message delivery status report indicates unreachable UE and the MNRA value stored in the HSS/HLR is "false", the HSS/HLR sets the MNRA value to "true”. If the failure cause carried in the message delivery status report indicates exceeded memory capacity of the UE and the MCEF value stored in the HSS/HLR is "false", the HSS/HLR sets the MCEF value to "true”.
- the HSS/HLR updates the stored MWI according to the change of the status of the called party monitored by the network.
- Table 1 shows how the HSS/HLR updates MWI according to the change of the status of the called party.
- Table 1 Type of notification received by HSS/HLR Value of indication before receiving notification Value of indication after update
- Invoke Alert-SC MCEF MNRA MWD MCEF MNRA MWD UE attaches in any network again True True "not empty” True False "not empty” No True False "not empty” True False "not empty” No False True "not empty” False False Empty Yes False False Empty False False Empty No Available memory capacity of the UE True True "not empty” False False Empty Yes capacity of the UE exists True False "not empty” False False Empty Yes False True "not empty” False False Empty Yes False False Empt
- the HSS/HLR checks the MWI of the MSIsdn-Alert corresponding to the UE. If the MCEF value in the MWI is "false”, the MWD value is "not empty” and the MNRA value is "true”, the HSS/HLR invokes the Alert-SC function to consecutively instruct all SMCs whose address is stored in the MWD to the originate a message termination process again; the HSS/HLR deletes the SMCs address in the MWD, and updates the MNRA value to "false”.
- the HSS/HLR updates the MNRA value to "false”, and updates the flag information corresponding to the network domain to "false”. If the MCEF value is "true”, the MWD value is "not empty” and the MNRA value is “false”, the HSS/HLR updates the flag information corresponding to the network domain in the MWI to "false", without invoking the Alert-SC function.
- the HSS/HLR updates the flag information corresponding to the network domain in the MWI to "false", without invoking the Alert-SC function.
- the HSS/HLR may check the MWI corresponding to the MSIsdn-Alert message of the called party after receiving a UE availability notification (for example, the UE attaches in a network domain again, or memory capacity of the UE is available) sent from any network domain. In this case, if the MCEF value is "false”, the MWD value is "empty” and the MNRA value is "false”, the HSS/HLR responds to the previous notification, without invoking the Alert-SC function.
- a UE availability notification for example, the UE attaches in a network domain again, or memory capacity of the UE is available
- the HSS/HLR invokes the Alert-SC function to consecutively instruct all SMCs whose address is stored in the MWD to originate a message termination process again, the HSS/HLR deletes the SMCs address in the MWD and updates the MCEF value to "false”.
- the HSS/HLR invokes the Alert-SC function to consecutively instruct all SMCs whose address is stored in the MWD to originate a message termination process again, and the HSS/HLR deletes the SMC address in the MWD and updates the MNRA value to "false”.
- the HSS/HLR invokes the Alert-SC function to consecutively instruct all SMCs whose address is stored in the MWD to originate a message termination process again, and the HSS/HLR deletes the SMC address stored in the MWD, updates the MCEF value to "false”, and updates the MNRA value to "false”.
- the IP-SM-GW may invoke the Alert-SC function to trigger the process of transmitting the termination message again according to the indication information in the stored MWI (including the information indicating that the UE is unreachable in this network domain and the MSIsdn-Alert information).
- the IP-SM-GW may also send a message delivery status report to the HSS/HLR.
- the detailed process may be: The IP-SM-GW attempts to send a message via S-CSCF first. If sending of the message via S-CSCF fails, the S-CSCF returns a message failure delivery report to the IP-SM-GW. Suppose that the failure cause carried in the message failure delivery report indicates that the UE is unreachable in the IMS network domain. Then, the IP-SM-GW sends the message to the called party via SGSN according to the priority of sending paths.
- the SGSN If sending of the message via SGSN fails, the SGSN returns a message failure delivery report to the IP-SM-GW Suppose that the failure cause carried in the message failure delivery report indicates that the UE is unreachable in the PS domain. Afterward, the IP-SM-GW finally attempts to send the message to the UE via MSC. Suppose that the message is sent successfully via MSC. In this case, the IP-SM-GW can send a message delivery status report to the HSS/HLR.
- the message delivery status report may further identify the diagnosis information about absent UE of the called party, namely, in which network domain the UE is unreachable, and identify the unreachable status, for example, the UE detaches in the IMS network domain, or the UE makes no paging response in the PS network domain.
- the IP-SM-GW can use a changed MAP-REPORT-SM-DELIVERY-STATUS message to send a message delivery status report to the HSS/HLR.
- the MAP-REPORT-SM-DELIVERY-STATUS message may be changed like this: adding a group of parameters in the message, and using this group of parameters to indicate the result of transmitting the message via the IMS network domain and the diagnosis information about unreachable UE of the called party in the IMS network domain.
- the HSS/HLR After receiving the message delivery status report from the IP-SM-GW, the HSS/HLR updates the stored MWI according to the failure cause carried in the message delivery status report. If the failure cause indicates that the UE detaches in the IMS network domain and the MNRI value stored in the HSS/HLR is "false", the HSS/HLR updates the stored MNRI value to "true”, and updates the MNRR status to "IMS Detached".
- the HSS/HLR updates the corresponding MWI. For example, when the UE of the called party is attached to the IMS network domain again or makes a paging response, the HSS/HLR updates the MNRI value to "false” and deletes the "No Paging Response via S-CSCF" or "IMS Detached" in the MNRR.
- the HSS/HLR updates the MNRF value and/or MNRG value to "false” and deletes the corresponding cause value in the MNRR.
- Figure 4 shows an IP-based message routing method, in which both the IP-SM-GW and the traditional message routing entity send a message delivery status report to the HSS/HLR.
- the IP-SM-GW sends a short message to the UE according to priority of sending paths decided by the NeDS function. If the failure cause identified in the message failure delivery report indicates exceeded memory capacity of the UE, no other sending paths are attempted.
- Step 10 The IP-SM-GW sends a message delivery status report to the HSS/HLR. If the message is sent successfully through more than one path, the message delivery status report sent by the IP-SM-GW to the HSS/HLR carries the information about the path(s) attempted before successful sending and the cause for the unsuccessful attempt(s). If the IP-SM-GW attempts to send the message through every path but fails on all paths, the message delivery status report carries the causes for failure of sending the message on each path.
- Step 11 The IP-SM-GW sends a message delivery report to the traditional message routing entity SMS-GMSC. If sending of the message fails, a message failure delivery report is sent to the traditional message routing entity SMS-GMSC, carrying the failure cause.
- Step 12 Through a MAP-REPORT-SM-DELIVERY-STATUS message, the SMS-GMSC sends a message delivery status report to the HSS/HLR; if the message delivery status report carries an address of the SMC that originates the message termination process, the message sending failure cause is identified in the message delivery status report.
- Step 13 The SMS-GMSC sends a message delivery report to the SMC; if the sending of the message fails, the SMS-GMSC sends a message failure delivery report.
- Described below is a process of triggering the Alert-SC function when the UE is re-registered in the IMS network domain or there is a notification of available memory capacity of the UE after sending of the message fails.
- Step 14 The HSS/HLR or the IP-SM-GW receives a message from the IMS network domain, indicating that the UE of the called party is reachable or has available memory capacity.
- Step 15 The HSS/HLR or the IP-SM-GW sends an Alert message to the SMS-IWMSC by invoking the Alert-SC function.
- Step 16 The SMS-IWMSC sends an Alert message to the SMC through an RP-ALRERT-SC message, instructing the SMC to originate a message termination process to the UE.
- IP-based message routing method provided in another embodiment of the present invention is described below with reference to Figure 5 .
- the IP-SM-GW sends a short message to the UE according to priority of sending paths decided by the NeDS function. If the IP-SM-GW attempts to send the message through every path but fails on all paths, the IP-SM-GW receives message failure delivery reports from S-CSCF, SGSN and MSC consecutively. Suppose that the failure causes identified in these message failure delivery reports are: the UE detaches in the IMS network, the UE makes no paging response in the PS domain, and the UE has no memory capacity available.
- Step 20 The IP-SM-GW sends a message delivery status report to the HSS/HLR.
- the message delivery status report carries the failure cause, namely, the UE has no memory capacity available; and may further identify the diagnosis information about absent UE, namely, the UE detaches in the IMS network domain, and the UE makes no paging response in the PS domain.
- the IP-SM-GW may use a changed MAP-REPORT SM-DELIVERY STATUS message to send the message delivery status report to the HSS/HLR.
- a group of parameters are added into the MAP-REPORT-SM-DELIVERY-STATUS message to indicate the result of transmitting the message through the IMS network domain and the diagnosis information about unreachable UE in the IMS network domain.
- the HSS/HLR After receiving the message delivery status report from the IP-SM-GW, the HSS/HLR updates the corresponding MWI according to the failure cause carried in the message delivery status report, namely, the HSS/HLR updates the MNRI value to "true”, updates the MNRG value to "true” and updates the MNRR value to "IMS Detached, No Paging Response via SGSN".
- Step 21 The IP-SM-GW sends a message failure delivery report to the traditional message routing entity SMS-GMSC through an RP-ERROR message, indicating this failure cause: the UE has no memory capacity available.
- Step 22 Through a MAP-REPORT-SM-DELIVERY-STATUS message, the SMS-GMSC sends a message delivery status report to the HSS/HLR; the message delivery status report carries an address of the SMC that originates the message termination process, and the message sending failure causes identified in the message delivery status report indicates that the UE has no memory capacity available.
- the HSS/HLR After receiving the message delivery status report from the SMS-GMSC, the HSS/HLR updates the corresponding MWI according to the information carried in the report. Namely, when the MWD has no SMC address carried in the message delivery status report, the HSS/HLR inserts the SMC address carried in the message delivery status report into the MWD, and updates the MCEF value to "true".
- Step 23 The SMS-GMSC sends a message failure delivery report to the SMC.
- Step 24 The HSS/HLR or the IP-SM-GW receives a message from any network domain, indicating that the UE of the called party is registered and has available memory capacity.
- Step 25 The HSS/HLR or the IP-SM-GW invokes the Alert-SC function to send an Alert message to the SMS-IWMSC, deletes the corresponding SMC address in the stored MWD, updates the MCEF value of the MSIsdn-Alert corresponding to the UE to "false”, updates the MNRI value to "false”, and deletes the "IMS Detached" in the MNRR.
- Step 26 The SMS-IWMSC sends an Alert message to the SMC through an RP-ALRERT-SC message, instructing the SMC to originate a message termination process to the U E.
- IP-based message routing method provided in further another embodiment of the present invention is further described below with reference to Figure 6 .
- the IP-SM-GW sends a short message to the UE according to priority of sending paths decided by the NeDS function. If the IP-SM-GW attempts to send the message through every path but fails on all paths, the IP-SM-GW receives message failure delivery reports from S-CSCF, SGSN and MSC consecutively. Suppose that the failure causes identified in these message failure delivery reports are: the UE is unreachable in the IMS network domain, the UE fails in the PS domain system, and the UE is unreachable in the CS domain.
- Step 30 The IP-SM-GW sends a message failure delivery report to the SMS-GMSC through an RP-ERROR message, indicating this failure cause: the UE is unreachable.
- Step 31 Through a MAP-REPORT-SM-DELIVERY-STATUS message, the SMS-GMSC sends a message delivery status report to the HSS/HLR.
- the message delivery status report carries an address of the SMC that originates the message termination process and identifies the sending failure cause, namely, unreachable UE.
- the HSS/HLR After receiving the message delivery status report from the SMS-GMSC, the HSS/HLR updates the corresponding MWI according to the information carried in the report. Namely, when the MWD has no SMC address carried in the message delivery status report, the HSS/HLR inserts the SMC address carried in the message delivery status report into the MWD, updates the MNRA value to "true", and accordingly, updates the MNRF, MNRG and MNRI values to "true”.
- Step 32 The SMS-GMSC sends a message failure delivery report to the SMC.
- Step 33 The HSS/HLR or the IP-SM-GW receives a message from any network domain, indicating that the UE attaches in the network again.
- Step 34 The HSS/HLR or the IP-SM-GW invokes the Alert-SC function to send an Alert message to the SMS-IWMSC, deletes the corresponding SMC address in the MWD, and updates the MNRI and MNRA values of the MSIsdn-Alert corresponding to the UE to "false".
- Step 35 The SMS-IWMSC sends an Alert message to the SMC through an RP-ALRERT-SC message, instructing the SMC to originate a message termination process to the UE.
- a system for routing messages based on IP transmission may include: a receiving and storing module, a routing module, and a sending module.
- the receiving and storing module and the routing module may be set in the HSS/HLR.
- the sending module is adapted to transmit the information about failure of sending the termination message in the network domain to the HSS/HLR when sending of the termination message to the called party in the network domain fails.
- the sending module is adapted to transmit the information about failure of sending the termination message in the network domain to the HSS/HLR directly, or transmit the information about failure or success of sending the termination message in the network domain to the HSS/HLR via a traditional message routing entity.
- the sending module may consist of a first sending submodule, a second sending submodule, and a third sending submodule.
- the third sending submodule is adapted to send a message delivery status report to the HSS/HLR directly when the IP-SM-GW attempts to send the termination message through every path provided by the HSS/HLR, and if the termination message is sent successfully or the attempts on all paths fail. If the attempts on all paths fail because the called party is unreachable, the third sending submodule puts the failure cause, that is, the called party is unreachable in all network domains, into the message delivery status report, so as to instruct the HSS/HLR to update the MWI (for example, MNRI, MNRF, MNRG, MNRR) stored in the receiving and storing module.
- MWI for example, MNRI, MNRF, MNRG, MNRR
- the triggering module of the HSS/HLR triggers a second process of transmitting the termination message by invoking the Alert-SC in a proper situation, for example, when the status of the called party in the network domain changes. If the termination message is sent successfully through more than one path, the message delivery status report sent by the third sending submodule to the HSS/HLR carries the information about the path(s) attempted before successful sending and the cause for the unsuccessful attempt(s). In this way, the receiving and storing module of the HSS/HLR can know the status of the called party in time, and update the corresponding MWI. The particulars are given in the preceding method description.
- the first sending submodule is adapted to: (i) when the IP-SM-GW receives one or more delivery failure reports, determine the cause value of sending failure according to the information carried in the delivery failure report, and transmit the cause value to the receiving and storing module through a message delivery status report; or (ii) send a message failure delivery report the second sending submodule after determining that sending of the message in all domains fails according to the information carried in the delivery failure report received by the IP-SM-GW Namely, the first sending submodule sends a message delivery report to the second sending submodule in the traditional message routing entity. If the attempts of sending the termination message fail on all paths, the first sending submodule sends a message failure delivery report to the traditional message routing entity, carrying the failure cause.
- the first sending submodule can decide the failure cause carried in the message failure delivery report sent to the traditional routing entity according to the failure cause carried in the message failure delivery report sent from the S-CSCF, and/or SGSN, and/or MSC.
- the particulars are given in the preceding method description.
- the sending module consists of a first sending submodule and a third sending submodule located in the IP-SM-GW and a second sending submodule located in the traditional message routing entity.
- the receiving and storing module is adapted to update the stored MWI after receiving the information about failure of sending the termination message in all domains sent from the sending module.
- an MNRA and an MNRI are added into the MWI, and two status values are added into the MNRR.
- the MNRA indicates that the called party is completely unreachable in all network domains; and the MNRI indicates that the called party is unreachable in the IMS network domain.
- the values in of MNRA and MNRI may be Boolean values.
- the receiving and storing module may consist of a storing submodule and an updating submodule.
- the storing submodule is adapted to store MWI.
- the MWI additionally contains an MNRA, which indicates that the called party is unreachable in all domains; an MNRI, which indicates that the called party is unreachable in the IMS domain; and an MNRR, which includes two status values.
- the updating submodule is adapted to update the MWI stored in the storing submodule according to the received message delivery status report and the information carried in a user registration message.
- the detailed update process may be: if the updating submodule determines that the MWD stored in the storing submodule contains no SMC address carried in the received message delivery status report, the updating submodule inserts the SMC address carried in the message delivery status report into the MWD stored in the storing submodule; if the failure cause carried in the message delivery status report indicates unreachable UE and the MNRA value stored in the storing submodule is "false", the updating submodule sets the MNRA value to "true”; if the failure cause carried in the message delivery status report is exceeded memory capacity of the UE and the MCEF value stored in the storing submodule is "false", the updating submodule sets the MCEF value to "true”.
- the particulars are given in the preceding method description.
- the routing module may consist of a triggering submodule and a routing submodule.
- the routing module may include only a triggering submodule or only a routing submodule.
- the triggering submodule determines that the status of the called party changes in any network domain and the receiving and storing module stores the information about failure of sending the termination message to the called party in all network domains, the triggering submodule invokes the Alert-SC to trigger the process of retransmitting the termination message.
- the routing submodule After the HSS/HLR receives a route query request, the routing submodule identifies the NE sending the route query request according to the route query request. If the NE sending the route query request is the IP-SM-GW, the routing submodule determines available routing information corresponding to a route query request according to the information stored in the receiving and storing module, and transmits the available routing information to the IP-SM-GW. The particulars are given in the preceding method description.
- a failure information storing module and a first triggering module can be set in the IP-SM-GW provided in an embodiment of the present invention.
- the failure information storing module may store information about failure of sending the termination message in the network domain.
- the failure message storage module may store part of the MWI, as described in the preceding method.
- the first triggering module may invoke an Alert-SC to trigger a process of retransmitting the termination message.
- a system for routing messages based on IP transmission may include a receiving and storing module, a routing module, and a second sending module.
- the receiving and storing module and the routing module are set in the HSS/HLR, and the second sending module is set in the traditional message routing entity.
- the second sending module transmits the information about failure of sending a termination message in network domains to the receiving and storing module after the termination message to the called party is sent unsuccessfully in these network domains.
- these network domains may include CS domain, PS domain and IMS domain.
- the second sending module may send information to the HLR/HSS, indicating the failure of sending the termination message in all network domains;
- the second sending module sends a short message delivery report to the HLR/HSS, indicating the failure of sending the termination message in a certain domain, such as an IMS domain.
- the receiving and storing module and the routing module in this system are basically the same as the equivalents described in the preceding embodiment, and the routing module in this system consists of a triggering submodule and a routing submodule; and the routing module may include only a triggering submodule or only a routing submodule, the details of which are not described here any further.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Claims (13)
- Verfahren zum Routen von Nachrichten auf der Basis von Internet-Protokoll- bzw. IP-Übertragung, umfassend:direktes Empfangen von Informationen über den Fehlschlag des Sendens einer Beendigungsnachricht in mindestens einer Netzwerkdomäne durch einen Home Subscriber Server/Home Location Register, HSS/HLR, von einem IP Short Message Gateway, IP-SM-GW, wenn das Senden der Beendigungsnachricht zu einem angerufenen Teilnehmer in der mindestens einen Netzwerkdomäne fehlschlägt;Speichern der Informationen über den Fehlschlag des Sendens der Beendigungsnachricht in der mindestens einen Netzwerkdomäne durch den HSS/HLR; undDurchführen einer nachfolgenden Prozedur des Routens der Beendigungsnachricht zu dem angerufenen Teilnehmer durch den HSS/HLR gemäß den gespeicherten Informationen;wobei die Informationen über den Fehlschlag des Sendens einer Beendigungsnachricht eine Beendigungsnachricht-Sendefehlschlagsursache umfassen.
- Verfahren nach Anspruch 1, wobei der Prozess des Empfangens von Informationen über den Fehlschlag des Sendens der Beendigungsnachricht in der mindestens einen Netzwerkdomäne Folgendes umfasst:Empfangen der Informationen über den Fehlschlag des Sendens der Beendigungsnachricht durch den HSS/HLR, wenn das Senden der Beendigungsnachricht zu dem angerufenen Teilnehmer in allen Netzwerkdomänen fehlschlägt (10).
- Verfahren nach Anspruch 2, wobei der Prozess des Empfangens von Informationen über den Fehlschlag des Sendens der Beendigungsnachricht, wenn das Senden der Beendigungsnachricht zu dem angerufenen Teilnehmer in allen Netzwerkdomänen fehlschlägt, Folgendes umfasst:Senden einer Nachrichtenablieferungs-Statusmeldung durch das IP-SM-GW zu dem HSS/HLR, wenn das IP-SM-GW bestimmt, dass das Senden der Beendigungsnachricht in allen Domänen fehlschlägt (20);Empfangen der in der Nachrichtenablieferungs-Statusmeldung geführten Informationen durch den HSS/HLR, wobei die Informationen den Fehlschlag des Sendens der Beendigungsnachricht in allen Netzwerkdomänen (20) angeben.
- Verfahren nach Anspruch 1, wobei der Prozess des Empfangens von Informationen über den Fehlschlag des Sendens der Beendigungsnachricht in der mindestens einen Netzwerkdomäne Folgendes umfasst:Empfangen der Informationen über den Fehlschlag des Sendens der Beendigungsnachricht durch den HSS/HLR, wenn das Senden der Beendigungsnachricht zu dem angerufenen Teilnehmer in einer Netzwerkdomäne aufgrund von überschrittener Speicherkapazität des angerufenen Teilnehmers (22) fehlschlägt.
- Verfahren nach Anspruch 4, wobei der Prozess des Empfangens der Informationen über den Fehlschlag des Sendens der Beendigungsnachricht, wenn das Senden der Beendigungsnachricht zu dem angerufenen Teilnehmer in der Netzwerkdomäne aufgrund von überschrittener Speicherkapazität des angerufenen Teilnehmers fehlschlägt, Folgendes umfasst:Senden einer Nachrichtenablieferungs-Statusmeldung durch das IP-SM-GW zu dem HSS/HLR, wenn das IP-SM-GW bestimmt, dass das Senden der Beendigungsnachricht in der Netzwerkdomäne aufgrund von überschrittener Speicherkapazität des angerufenen Teilnehmers (21) fehlschlägt; undEmpfangen der in der Nachrichtenablieferungs-Statusmeldung geführten Informationen durch den HSS/HLR, wobei die Informationen Fehlschlag des Sendens der Beendigungsnachricht in der Netzwerkdomäne aufgrund von überschrittener Speicherkapazität des angerufenen Teilnehmers (21) angeben.
- Verfahren nach einem der Ansprüche 1 bis 5, wobei die gespeicherten Informationen über den Fehlschlag des Sendens der Beendigungsnachricht mindestens eine einer Adresse eines Short Message Center, das den Prozess des Sendens der Beendigungsnachrichten-Beendigung einleitet, umfassen.
- Verfahren nach einem der Ansprüche 1 bis 6, wobei der Prozess des Durchführens des nachfolgenden Routing-Prozesses der Beendigungsnachricht zu dem angerufenen Teilnehmer gemäß den gespeicherten Informationen Folgendes umfasst:Triggern eines Prozesses zum Senden der Beendigungsnachricht durch den HSS/HLR, wenn der HSS/HLR bestimmt, dass sich ein Status des angerufenen Teilnehmers in irgendeiner Netzwerkdomäne ändert und der HSS/HLR die Informationen über den Fehlschlag des Sendens der Beendigungsnachricht zu dem angerufenen Teilnehmer speichert.
- Verfahren nach Anspruch 1, wobei der Prozess des Empfangens von Informationen über den Fehlschlag des Sendens der Beendigungsnachricht in der mindestens einen Netzwerkdomäne Folgendes umfasst:Empfangen der Informationen über den Fehlschlag des Sendens der Beendigungsnachricht durch das IP-SM-GW, wenn das Senden der Beendigungsnachricht zu dem angerufenen Teilnehmer in allen Netzwerkdomänen fehlschlägt oder das Senden der Beendigungsnachricht zu dem angerufenen Teilnehmer in einer Netzwerkdomäne aufgrund von überschrittener Speicherkapazität des angerufenen Teilnehmers fehlschlägt.
- Verfahren nach Anspruch 1 oder 6, wobei der Prozess des Durchführens des nachfolgenden Routing-Prozesses der Beendigungsnachricht zu dem angerufenen Teilnehmer gemäß den gespeicherten Informationen Folgendes umfasst:Triggern eines Prozesses zum Senden der Beendigungsnachricht durch das IP-SM-GW, wenn das IP-SM-GW bestimmt, dass sich ein Status des angerufenen Teilnehmers in irgendeiner Netzwerkdomäne ändert und das IP-SM-GW die Informationen über den Fehlschlag des Sendens der Beendigungsnachricht zu dem angerufenen Teilnehmer speichert.
- Verfahren nach Anspruch 7 oder 9, wobei der Prozess, bei dem der HSS/HLR oder das IP-SM-GW bestimmt, dass sich ein Status des angerufenen Teilnehmers in irgendeiner Netzwerkdomäne ändert, Folgendes umfasst:der HSS/HLR oder das IP-SM-GW bestimmt, dass sich ein Status des angerufenen Teilnehmers ändert, wenn der HSS/HLR oder das IP-SM-GW eine Nachricht von irgendeiner Netzwerkdomäne empfängt, die angibt, dass der angerufene Teilnehmer wieder verfügbar ist oder wieder verfügbare Speicherkapazität hat.
- Home Subscriber Server/Home Location Register, HSS/HLR, zum Routen von Nachrichten auf der Basis von IP- bzw. Internet-Protokoll-Übertragung, der Mittel umfasst, wobei
die Mittel dafür ausgelegt sind, die durch den HSS/HLR bei dem Verfahren nach einem der Ansprüche 1-10 ausgeführten Schritte auszuführen. - Internet-Protokoll- bzw. IP Short Message Gateway, IP-SM-GW, zum Routen von Nachrichten auf der Basis von IP-Übertragung, das Mittel umfasst, wobei die Mittel dafür ausgelegt sind, die durch das IP-SM-GW bei dem Verfahren nach einem der Ansprüche 1-10 ausgeführten Schritte auszuführen.
- System zum Routen von Nachrichten auf der Basis von IP- bzw. Internet-Protokoll-Übertragung, das einen Home Subscriber Server/Home Location Register, HSS/HLR, nach Anspruch 11 und ein IP Short Message Gateway, IP-SM-GW, nach Anspruch 12 umfasst.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200610066872A CN100589454C (zh) | 2006-03-31 | 2006-03-31 | 一种基于ip传输的消息路由方法和系统 |
PCT/CN2007/001031 WO2007112678A1 (fr) | 2006-03-31 | 2007-03-29 | Procédé, système et dispositif d'acheminement de messages basés sur une transmission ip |
Publications (4)
Publication Number | Publication Date |
---|---|
EP2007152A2 EP2007152A2 (de) | 2008-12-24 |
EP2007152A9 EP2007152A9 (de) | 2009-07-15 |
EP2007152A4 EP2007152A4 (de) | 2009-08-05 |
EP2007152B1 true EP2007152B1 (de) | 2013-04-24 |
Family
ID=38563107
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP07720605.0A Active EP2007152B1 (de) | 2006-03-31 | 2007-03-29 | Verfahren, system und einrichtungen für nachrichtenrouten auf der basis der ip-übertragung |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2007152B1 (de) |
CN (1) | CN100589454C (de) |
WO (1) | WO2007112678A1 (de) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
HK1107631A2 (en) | 2007-11-21 | 2008-04-11 | Vi Vi Jewellery Ltd | Movable elevator equipment |
CN102271312A (zh) * | 2010-06-04 | 2011-12-07 | 中兴通讯股份有限公司 | 一种终呼短消息的漫游重试方法和系统 |
CN102647365A (zh) * | 2011-02-16 | 2012-08-22 | 北京大学 | 处理消息及消息状态的方法、装置和数据交换服务器 |
CN107370666B (zh) * | 2012-10-26 | 2020-10-16 | 华为技术有限公司 | 一种短消息信令优化方法、设备和系统 |
CN103929721A (zh) * | 2013-01-11 | 2014-07-16 | 宏碁股份有限公司 | 在网络内提供短信服务的方法 |
CN103476012B (zh) * | 2013-09-04 | 2016-11-23 | 华为技术有限公司 | 一种信息处理方法和设备 |
CN105873009B (zh) * | 2015-01-21 | 2019-06-25 | 中国移动通信集团公司 | 一种ip短消息互通网关的容灾方法、设备和系统 |
CN107786948B (zh) * | 2016-08-26 | 2020-11-03 | 中国移动通信集团北京有限公司 | 一种短消息容灾备份方法、装置、系统和相关设备 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
SE9701509D0 (sv) * | 1997-04-22 | 1997-04-22 | Ericsson Telefon Ab L M | Method of routing a short message in a packet data network |
US6219546B1 (en) * | 1998-07-22 | 2001-04-17 | Ericsson Inc. | System and method of reallocating satellite gateways in a radio telecommunications network |
EP1188328A1 (de) * | 1999-06-01 | 2002-03-20 | Nokia Corporation | Leitweglenkung von nachrichten im falle der subskription von mehreren netzen |
KR100492959B1 (ko) * | 2002-09-11 | 2005-06-07 | 삼성전자주식회사 | 공중 이동통신망과 연동되는 사설 무선망의 단문 메시지서비스 서버 및 방법 |
GB0326368D0 (en) * | 2003-11-12 | 2003-12-17 | Intellprop Ltd | Telecommunications services apparatus |
-
2006
- 2006-03-31 CN CN200610066872A patent/CN100589454C/zh active Active
-
2007
- 2007-03-29 WO PCT/CN2007/001031 patent/WO2007112678A1/zh active Application Filing
- 2007-03-29 EP EP07720605.0A patent/EP2007152B1/de active Active
Non-Patent Citations (1)
Title |
---|
"Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Mobile Application Part (MAP) specification (3GPP TS 29.002 version 6.8.0 Release 6); ETSI TS 129 002", ETSI STANDARDS, LIS, SOPHIA ANTIPOLIS CEDEX, FRANCE, vol. 3-CN2;3-CN4, no. V6.8.0, 1 December 2004 (2004-12-01), XP014027802, ISSN: 0000-0001 * |
Also Published As
Publication number | Publication date |
---|---|
WO2007112678A1 (fr) | 2007-10-11 |
EP2007152A2 (de) | 2008-12-24 |
EP2007152A9 (de) | 2009-07-15 |
CN100589454C (zh) | 2010-02-10 |
CN101047655A (zh) | 2007-10-03 |
EP2007152A4 (de) | 2009-08-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6220906B2 (ja) | ショートメッセージサービスをサポートする、ターミナルのケーパビリティのレポーティング | |
KR101348576B1 (ko) | 이동 통신 시스템에서 단문 메시지 전달의 관리를 위한 방법 | |
EP2007152B1 (de) | Verfahren, system und einrichtungen für nachrichtenrouten auf der basis der ip-übertragung | |
EP1998526B1 (de) | Verfahren und vorrichtung zum routen von nachrichten auf der basis von ip | |
KR100946900B1 (ko) | Ims 재등록 방법 및 이를 위한 시스템 | |
EP2081348A1 (de) | Verfahren zur zusammenarbeit von nachrichten, system, artikel und verfahren zur verarbeitung von reporten der lieferung von nachrichten, system, artikel und endgerät für zusammenarbeit von nachrichten | |
KR101569070B1 (ko) | 이동통신망에서 패킷 교환 전용 가입을 위한 단문 메시지 서비스 제공 방법 및 장치 | |
US10277552B2 (en) | Relating to messaging gateways | |
US20140155112A1 (en) | Support of short message service in ims without msisdn | |
US20100093306A1 (en) | System and method for availing information relating to a circumstance | |
CN101202710A (zh) | 消息发送报告处理方法、系统及用于消息互通实体、终端 | |
KR200402238Y1 (ko) | 단문 메시지 서비스를 지원하는 단말기 성능을 보고하는장치 | |
WO2006099812A1 (fr) | Procédé de transmission de message |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
PUAB | Information related to the publication of an a document modified or deleted |
Free format text: ORIGINAL CODE: 0009199EPPU |
|
17P | Request for examination filed |
Effective date: 20081028 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: DUAN, XIAOQIN Inventor name: SUN, CHENGZHEN |
|
RTI1 | Title (correction) |
Free format text: MESSAGE ROUTE METHOD, SYSTEM AND DEVICE BASED ON IP TRANSMISSION |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20090708 |
|
17Q | First examination report despatched |
Effective date: 20100708 |
|
DAX | Request for extension of the european patent (deleted) | ||
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602007029996 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04Q0007220000 Ipc: H04W0008020000 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 8/02 20090101AFI20121001BHEP |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 609229 Country of ref document: AT Kind code of ref document: T Effective date: 20130515 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602007029996 Country of ref document: DE Effective date: 20130627 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 609229 Country of ref document: AT Kind code of ref document: T Effective date: 20130424 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20130424 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130824 Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130826 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130725 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130804 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130724 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20140127 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602007029996 Country of ref document: DE Effective date: 20140127 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20140329 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140331 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140329 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140331 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 10 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20130424 Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20070329 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 11 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 12 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230524 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240130 Year of fee payment: 18 Ref country code: GB Payment date: 20240208 Year of fee payment: 18 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20240213 Year of fee payment: 18 |