WO2010124543A1 - Procédé et appareil permettant de réaliser une portabilité de numéro dans un système de messages courts - Google Patents

Procédé et appareil permettant de réaliser une portabilité de numéro dans un système de messages courts Download PDF

Info

Publication number
WO2010124543A1
WO2010124543A1 PCT/CN2010/071232 CN2010071232W WO2010124543A1 WO 2010124543 A1 WO2010124543 A1 WO 2010124543A1 CN 2010071232 W CN2010071232 W CN 2010071232W WO 2010124543 A1 WO2010124543 A1 WO 2010124543A1
Authority
WO
WIPO (PCT)
Prior art keywords
npdb
information
short message
network
built
Prior art date
Application number
PCT/CN2010/071232
Other languages
English (en)
Chinese (zh)
Inventor
王巍
张道平
黄剑玮
崔新峰
孔韬
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to BRPI1013595-2A priority Critical patent/BRPI1013595B1/pt
Publication of WO2010124543A1 publication Critical patent/WO2010124543A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H04W36/385—Reselection control by fixed network equipment of the core network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • the present invention relates to number portability technology, and more particularly to a method and apparatus for implementing a number carried in a short message system. Background technique
  • NP Numberer Portability
  • the application number is 200810114269.7, and the Chinese patent application entitled "A method and system for implementing short message service supporting number portability" proposes a method and system for implementing short message service supporting number portability: setting NP in the local network a Home Location Register (HLR) unit; for carrying the number on the local network, the NPHLR unit initiates a location update request message to the original HLR of the number, and carries a specific global code (GT) in the request message, so that the short message center ( SMSC, Short Message Center) can identify the current subscription network of the number carried by the local network according to the specific GT number; for the external network to carry the number, the NPHLR unit acts as the current HLR of the external network carrying number, and the NPHLR unit is currently based on the number The contracted network issues a specific GT number.
  • HLR Home Location Register
  • GT global code
  • the short message center sends a short message routing query message to the gateway; the gateway queries the number to carry the server. If the query result returned by the number portability server indicates that the called user is a number portability user, the gateway returns a short message to the short message center that carries the network. Message routing query response message.
  • the short message center that carries the network sends the short message to the short message center of the network that corresponds to the network number, and carries the network number as the prefix of the called number in the called number;
  • the internal HLR queries the short message routing information of the called user and sends the short message to the called user.
  • Patent No. 02102173.2 the Chinese patent entitled “Method for Realizing Mobile Number Portability” proposes a scheme for realizing mobile number portability (MNP) by using the signaling procedure of the existing mobile network standard, for the current network Visiting the mobile switching center (VMSC), gateway office (GMSC) and HLR and other master devices without any modification, only need to increase the number portability database (NPDB, Number Portability Database) + equipment, that is, the combination of NPDB and NPHLR.
  • the method carries the original local network user number to the other network, and becomes the NP OUT user of the other network user.
  • NPDB+ In the home network of the number segment, it is necessary to be able to assign a virtual roaming number to identify the user's number carrying situation;
  • the number is carried to the local network and becomes the NP IN user of the local network user.
  • the new NPDB+ device is used to save the MNP mobile user data into the local network and complete related functions.
  • the data storage of NPDB+ adopts the distribution technology, the database reliability is high, the scheme has no voice path, and the network settlement is convenient.
  • the newly added equipment NPDB+ is superimposed on the existing network, and the network can be expanded very well, especially suitable for the existing network scale. Large mobile operators.
  • the essence of the above three schemes is that before the short message is terminated, the SMSC goes to the NPDB outside the local network to query the routing number (RN, Routing Number), and then determines the destination destination.
  • the disadvantages are: the external NPDB device needs Separate construction, high cost, and complicated implementation; In addition, if the operator does not have an NPDB device, the implementation of the number portability is limited; therefore, the patent document with the patent number 02102173.2 emphasizes "suitable for the existing network. A very large mobile operator", that is, for networks with NPDB devices.
  • the SMSC queries the RN in the external NPDB, it needs to occupy a certain network resource.
  • the SMSC needs to be queried through the signaling message ⁇ 1; and in the case of a busy network or a processing capacity bottleneck, the RN's outbound query failure rate will be greatly improved, and the number may be segmented by the number.
  • the RN it is possible to match the wrong RN, so that when the short message is sent by the RN, the possibility of error is relatively large.
  • the main purpose of the present invention is to provide a method and apparatus for implementing number portability in a short message system, which eliminates the need to construct an NPDB related device, and is convenient to implement.
  • a method for implementing a number carried in a short message system comprising:
  • the short message center queries the built-in number portability database (NPDB) of the called party's routing number (RN) information;
  • NPDB built-in number portability database
  • the SMSC determines, according to the RN information that is queried, whether the RN information is directed to the local network where the SMSC is located, and if yes, the SMSC performs a short message termination call; otherwise, the SMSC is based on the acquired RN. And sending the short message to the network pointed by the RN information, and performing a termination call on the short message.
  • the RN information includes: an RN carrying a number carrying network and an RN carrying a number into the network.
  • Determining whether the RN information points to the local network is: determining whether the RN that the number carries into the network points to the local network;
  • Sending the short message to the network pointed by the RN information is: sending the short message to a network pointed by the RN that the number carries into the network.
  • the method further includes: determining whether the query is successful, and if the query is successful, determining whether the RN information points to the local network; if the query fails, And matching the number corresponding to the called user to the RN of the network in the correspondence table of the preset number segment and the RN according to the number segment to which the user number of the called user belongs.
  • the method further includes: synchronizing data in the built-in NPDB, specifically: periodically synchronizing data stored in the global NPDB in the entire network to the built-in NPDB; or, the built-in NPDB periodically synchronizes with the built-in NPDB of other networks. .
  • the method further includes: adding, and/or deleting, and/or 4 tampering, and/or updating the data of the built-in NPDB.
  • An implementation device for carrying a number in a short message system comprising: a built-in NPDB, an NPDB management module, a service processor, and a front-end machine;
  • the built-in NPDB is configured to store user RN information
  • the NPDB management module is configured to query the RN information in the built-in NPDB; and feed back the RN information that is queried to the service processor;
  • the service processor is configured to determine, according to the RN information that is queried, whether the RN information is directed to the local network, and obtain a determination result;
  • the front-end machine is configured to: according to the determination result, when the RN information points to the local network, perform a short message termination call; when the RN information does not point to the local network, send a short message to the The network to which the RN information points.
  • the service processor is further configured to send a message for querying the called user RN information to the NPDB management module;
  • the NPDB management module is further configured to receive the message for querying the called user RN information, and query the RN information according to the message.
  • the service processor is further configured to: when the RN information returned by the NPDB management module is not received, corresponding to the RN according to the number segment to which the user number of the called user belongs Matching the RN information corresponding to the called user in the table;
  • the apparatus further includes: a configuration station, configured to preset a correspondence table between the number segment and the RN, and synchronize the correspondence table to the service processor.
  • a configuration station configured to preset a correspondence table between the number segment and the RN, and synchronize the correspondence table to the service processor.
  • the configuration station is further configured to: control the number of the built-in NPDB by the NPDB management module Additions, and/or deletions, and/or modifications, and/or updates are made.
  • the built-in NPDB includes: an NPDB physical library and an NPDB memory library for respectively storing user RN information;
  • the NPDB management module includes: an NPDB physical library management module and an NPDB memory library management module;
  • the configuration station controls the NPDB physical library management module to add, and/or delete, and/or modify, and/or update the NPDB physical library;
  • the NPDB physical library management module controls the NPDB memory library management module to add, and/or delete, and/or modify, and/or update the NPDB memory library.
  • the NPDB is set in the local network by establishing the NPDB physical library and/or the memory library, preferably the NPDB is built in the SMSC, and thus, the query is performed.
  • the NPDB process is implemented inside the SMSC, so that the SMSC can query the built-in NPDB to obtain the required data without querying the RN information.
  • the internal query NPDB is not affected by the network factor. Improve the efficiency of querying and processing data.
  • FIG. 1 is a schematic flowchart of a method for implementing a number carrying in a short message system according to the present invention
  • FIG. 2 is a schematic diagram of Embodiment 1 of a networking mode according to the present invention
  • Embodiment 2 of a networking mode of the present invention
  • FIG. 4 is a schematic structural diagram of an apparatus for implementing a number carried in a short message system according to the present invention. detailed description
  • the present invention sets the NPDB in the local network, preferably the NPDB is built in the SMSC: an independent NPDB physical library can be created inside the SMSC, and can also be inside the SMSC. A part of the memory bank is divided into a part to establish an NPDB memory library, so that the NPDB is built in the SMSC, and the implementation is relatively simple.
  • SMSC can query the required data in the NPDB physical library by accessing the database write/read (DBI/0) interface of the NPDB physical library in the local network; or synchronizing the NPDB physical library to In the NPDB memory library, SMSC can query the required information from the NPDB memory library directly through the internal message interface.
  • DBI/0 database write/read
  • the method for implementing the number of the present invention in a short message system is as shown in FIG. 1, and the method includes:
  • Step 101 After receiving the short message, the SMSC queries the built-in NPDB of the called user for the RN corresponding to the current subscription network of the called user.
  • the NPDB is mainly used to store the NP information of the user.
  • the NP information includes at least: the user number, the RN carrying the number and the RN carrying the number and the RN carrying the number into the network.
  • the number-carrying network is the network to which the user belongs before the number is carried.
  • the number-carrying network is the network to which the user belongs after the number is carried, that is, the current subscription network.
  • the SMSC After receiving a short message, the SMSC first needs to query the RN information of the called user corresponding to the short message: the RN including the number carrying the network and the RN carrying the number into the network. It should be noted that, for the forwarding of short messages, the present invention only cares about the current subscription network of the called user, and the SMSC of the current subscription network makes a final call for the short message. Therefore, after obtaining the RN information of the called user, the SMSC only cares about the RN that the number carries into the network and the RN that corresponds to the current subscription network.
  • the SMSC sends an inquiry request for the current called user RN information to the NPDB through an internal message, such as an NPQry_Req message, where the message includes at least the user number of the called user; the NPDB finds the corresponding according to the user number.
  • the RN information is encapsulated in the query result and fed back to the SMSC through an internal message, such as an NPQry_Ack message.
  • Step 102 Determine whether the query is successful. If yes, go to step 103; if no, go to step 106.
  • a field may be set in the query result to indicate whether the query is successful. SMSC determines if the query was successful by reading the value of this field. Of course, there are other ways to judge, such as setting the SMSC to receive the RN information as a successful query; otherwise, the query fails.
  • the SMSC get to the called subscriber's RN message stating the called user number portability users; If the query fails, the shellfish 1 j SMSC can not get to the called subscriber RN information that is not stored in the built-in NPDB
  • the RN information of the user indicates that the called user is not a number carrying user.
  • Steps 103 to 104 determining whether the obtained RN points to the local network, and if yes, the SMSC performs the termination call, and the current processing flow ends; if not, step 105 is performed.
  • the SMSC is internally configured with a correspondence table between the RN and the network, and the table can be loaded in the memory library, and each network corresponds to one RN.
  • a network contains an HLR, and the RN and HLR are also corresponding.
  • some networks may contain multiple HLRs. In this case, these multiple HLRs correspond to one RN, and each HLR corresponds to a preset number segment. If the SMSC does not obtain the RN information corresponding to the called user from the NPDB for some reason, it can also match the HLR by the number segment to which the user number of the called user belongs, thereby matching the corresponding RN information. Specifically, the SMSC does not obtain the RN information corresponding to the called user from the NPDB for some reason, which will be explained in the following steps.
  • the RN After the RN obtains the RN information of the called user, the RN that carries the number of the called user determines whether the RN points to the local network, that is, whether the current subscription network of the called user is the local network. Specifically, the RN and the corresponding table of the network can be queried to know whether the current RN corresponds to the local network, that is, whether the RN points to the local network. If it is determined that the RN points to the local network, the current subscription network of the called user is the local network, and step 104 is performed, and the SMSC performs a terminal call for the current short message; otherwise, step 105 is performed.
  • Step 105 The SMSC sends the short message to the corresponding network according to the obtained RN, and the current processing flow ends.
  • the RN According to the determination in step 103 as to whether the RN is directed to the local network, if the RN carrying the number in the network does not point to the local network, indicating that the current subscription network of the called user is not the local network, the RN needs to be found according to the correspondence table between the RN and the network.
  • the network pointed to, and the current short message is sent to the network pointed by the RN after being converted by the protocol, and the network terminates the current short message. Since the network is the network pointed by the RN that the number is carried into the network, the network is the network that the called user is currently signing, and the SMSC of the network can make a final call for the short message.
  • the specific implementation of the conversion of the short message protocol is the prior art, and details are not described herein again.
  • Step 106 Match the RN of the current subscription network of the called user according to the number segment to which the user number of the called user belongs.
  • the RN needs to match the RN according to the number segment to which the user number of the called user belongs, and the matched RN is the RN corresponding to the current subscription network of the called user.
  • SMSC fails to query the RN information of the called user:
  • the number of the called user does not occur.
  • the RN information is not stored in the built-in NPDB. If the RN carrying the network and the RN carrying the number into the network, the SMSC will not obtain the RN information of the called user. .
  • the user has carried the number, but the built-in NPDB has an error and cannot return the user's RN information to the SMSC.
  • the SMSC may fail to query the RN information of the called user.
  • the SMSC needs to match the RN according to the number segment to which the user number of the currently called user belongs.
  • the query may be The pre-configured number segment and the RN correspondence table are used to query the RN that matches the current user number.
  • the corresponding table of the number segment and the RN can be loaded in the memory library.
  • the prior art is based on the external NPDB, and the RN obtained by matching the RN of the currently called user's subscription network by the number segment may be erroneous.
  • the RN of the network A is A
  • the HLR of the network A is pre-assigned a specific number N, that is, the HLR manages all users belonging to the segment N
  • the home network of the users that is, the subscription network is the network A.
  • the NP information of the user a needs to be recorded in the NPDB, including at least the user number of the user a and the RN carrying the network.
  • a and number carry the RN of the network: B. If the RNDB of the SMSC obtains the RN information of the user a at this time, the SMSC needs to pass the RN information of the user a from the external NPDB due to the common network busy or the bottleneck of the network processing capability.
  • the RN information of the query number segment and the RN is obtained to obtain the RN information of the user a.
  • the user a belongs to the segment N, and the RN corresponding to the segment N is A.
  • the shell SMSC thus obtains that the current subscription network of the user a is the network A. Because the current subscriber a's subscription network is network B, if the SMSC sends a short message to network A, network A cannot forward the short message to user a to provide service for user a.
  • the SMSC does not need to query the RN information for outgoing calls, and is not affected by common network factors.
  • the SMSC only needs to obtain the RN information directly from the built-in NPDB through an internal interface, such as a database interface or a message interface. can.
  • an internal interface such as a database interface or a message interface. can.
  • the SMSC query RN information are performed inside the SMSC, the possibility of querying the RN information is very small, and thus the possibility that the SMSC sends a short message according to the RN is very small. This step is set by the present invention in the case where the SMSC cannot acquire the RN due to an accident.
  • SMSC only needs to query the built-in NPDB once for each short message.
  • NPDB Network Address Translation
  • switches can be understood as a number portability. Therefore, before each terminal call, the SMSC needs to query the NPDB for the RN information of the called user to determine whether the called user has the number portability and the network carried by the number.
  • the present invention can also collect the relevant parameters of the NPDB query through the short message center, thereby reflecting the situation in which the user carries the number for reference by the operator.
  • the statistical parameters include the number of times the RN is queried, the number of times the query result is received, and the number of successful queries.
  • the present invention also proposes a related implementation of charging, specifically:
  • the SMSC needs to send the calling number to the prepaid platform through the prepaid debit request message. , to calculate the rate at which the calling user uses the relevant service.
  • the prepaid platform also needs to calculate the rate based on the calling subscriber's subscription network.
  • some prepaid platforms do not support the NP query function. If the SMSC does not add RN information in the prepaid debit request message, the prepaid platform cannot know the calling network of the calling user. The rate cannot be calculated.
  • the SMSC needs to add RN information in the prepaid debit request message for the prepaid platform to calculate the rate; while some prepaid platforms support the NP query function, the prepaid platform is directly based on The calling number can find the corresponding contracted network to calculate the rate.
  • the SMSC also needs to add RN information to the caller's ticket to perform differential charging for the number portability user and the non-number portability user. For example, you can set the number of users carrying RN information in the ticket to be number-bearing users, otherwise it is a non-number carrying user.
  • the bill sorting system can also set whether to sort the RN information in the ticket according to the need. To ensure the validity and integrity of the built-in NPDB data, you need to periodically synchronize the data of the built-in NPDB.
  • the data stored in the global NPDB is synchronized to the built-in NPDB.
  • the data interface can be transmitted through the FTP interface. If there is no global NPDB in the whole network, it is periodically synchronized with the built-in NPDB of other networks.
  • the built-in NPDBs can share stored data with each other. This synchronization can also be performed by means of text interface processing, and data files are transmitted through the FTP interface.
  • Synchronizing the built-in NPDB includes: adding, and/or deleting, and/or modifying, and/or updating data stored by the NPDB.
  • the networking mode of the present invention will be specifically described below based on the above-described implementation of data synchronization with the built-in NPDB.
  • FIG. 2 is a schematic diagram of Embodiment 1 of the networking mode of the present invention.
  • the global NPDB is mainly used to store NP information of users of the entire network, and operations such as adding, and/or deleting, and/or modifying, and/or updating the information are managed by a third party.
  • the SMSC1 needs to query the RN information only from the global NPDB.
  • the network 2 has an external NPDB.
  • the SMSC2 queries the RN information it needs to query from the external NPDB. Both of these queries require SMSC outbound queries, which are so susceptible to network factors that the query failure rate will be higher.
  • the network 3 to the network n adopt the method of the built-in NPDB of the present invention.
  • the built-in NPDB periodically synchronizes data from the global NPDB to maintain the validity and integrity of user information.
  • the built-in NPDB and the global NPDB adopt an FTP interface.
  • the global NPDB writes the changed NP information into the database file; the built-in NPDB periodically downloads the database file through the FTP interface, and updates itself.
  • NP information At SMSC3 Or when SMSNn queries the RN information, it can go directly to the corresponding built-in NPDB to query, without going out of the query, so that it will not be affected by network factors, greatly reducing the probability of query errors.
  • FIG. 3 is a schematic diagram of Embodiment 2 of the networking mode of the present invention.
  • the built-in NPDB in each network synchronizes the NP information by forming an FTP file sequential transmission ring.
  • the SMSC corresponding to the built-in NPDB writes the changed NPDB to a database file, and then sends the database file to the next level according to the configuration information.
  • SMSC the SMSC updates its own built-in NPDB according to the database file, and sends the database file to its next-level SMSC according to the configuration data, until the built-in NPDB in each network of the whole network is updated.
  • SMSC1 When the RN information in the built-in NPDB1 of SMSC1 changes, SMSC1 writes the changed RN information to the corresponding database file 1 and sends the database file 1 to its next-level SMSC2 by FTP. It should be noted that the database file 1 stores the number of the SMSC that generated the database file, such as SMSC1. Moreover, the current SMSC can obtain its own next-level SMSC number based on the configuration data of the database file.
  • SMSC2 periodically detects the FTP directory and updates the changed RN information to its built-in NPDB2 according to the detected database file 1. SMSC2 can know that the receiver of database file 1 is SMSC3 through the configuration data, so SMSC2 will use the FTP method to database. File 1 is sent to its next level SMSC3; the number of SMSC in the file name of database file 1 is still SMSCl o
  • SMSCn periodically detects the FTP directory, and updates the changed RN information to its built-in NPDBn according to the detected database file 1.
  • SMSCn can know that the receiver of database file 1 is SMSC1 and the file of database file 1 through configuration data. In the name, the SMSC number is also SMSC1, so SMSCn no longer FTPs database file 1. In this way, the built-in NPDB of each network in the entire network completes the synchronization of the RN information for the change.
  • the present invention also provides an apparatus for implementing number portability in a short message system, and the device is applied in the SMSC.
  • the SMSC 40 in the present invention is used.
  • the method includes: a built-in NPDB 41, an NPDB management module 42, a service processor 43 and a front-end machine 44, wherein
  • the NPDB management module 42 is configured to query the RN information in the built-in NPDB 41; and feed back the RN information that is queried to the service processor 43;
  • the service processor 43 is configured to determine, according to the RN information that is queried, whether the RN information points to the local network, and obtain a determination result;
  • the front-end machine 44 is configured to perform a short message termination call when the RN information points to the local network according to the judgment result, and send the short message to the network pointed to by the RN information when the RN information does not point to the local network.
  • the service processor 43 is further configured to send a message for querying the called user RN information to the NPDB management module 42.
  • the NPDB management module 42 is further configured to receive a message for querying the called user RN information, and query the RN information according to the message.
  • the service processor 43 is further configured to: when the RN information returned by the NPDB management module 42 is not received, match the preset number segment with the RN correspondence table according to the number segment to which the user number of the called user belongs. Calling the RN information corresponding to the user;
  • the SMSC 40 further includes: a configuration station 45, configured to preset a correspondence table between the number segment and the RN, and synchronize the correspondence table to the service processor 43 for use by the service processor 43.
  • the configuration station 45 can synchronize the correspondence table to the service processor 43 through the FTP interface.
  • the configuration station 45 is further configured to control the NPDB management module 42 to perform operations such as adding, and/or deleting, and/or modifying, and/or updating data of the built-in NPDB 41.
  • the built-in NPDB 41 of the present invention may include: an NPDB physical library 411 and an NPDB memory library 412 for storing user's RN information, respectively.
  • the NPDB physical library 411 can be created inside the SMSC by using existing database development software; the NPDB memory library 412 can be created by dividing a part of the area in the internal memory of the SMSC.
  • the NPDB management module 42 can directly query the RN information in the NPDB physical library 411, or directly query the RN information from the NPDB memory library 412, but the information is read through the memory rather than directly accessing the physical library. The speed has been greatly improved.
  • the NPDB management module 42 includes: an NPDB physical library management module 421 and an NPDB memory library management module 422.
  • the NPDB physical library management module 421 can adopt the DBI/0 module; the NPDB memory library management module 422 can use the public database load query module (GDB, Global Date Base).
  • the user can also query, and/or add, and/or delete, and/or modify, and/or update data stored by the built-in NPDB 41 through the configuration station 45:
  • the configuration station 45 sends a message.
  • the NPDB physical library management module 421 is notified that the required data is read out from the NPDB physical library 411 and fed back, displayed on the configuration station 45; when the data stored in the built-in NPDB 41 is added, and/or deleted, and/or modified, and/or updated.
  • the configuration station 45 can control the NPDB physical library management module 421 to perform operations such as adding, and/or deleting, and/or modifying, and/or updating the NPDB physical library 411; meanwhile, the NPDB physical library management module 421 controls the NPDB memory library.
  • the management module 422 performs operations such as adding, and/or deleting, and/or modifying, and/or updating the NPDB memory bank 412.
  • the configuration station 45 and the NPDB physical library management module 421 are message interfaces, and may adopt a browser/server (B/S) architecture or a client/server (C/S) architecture; the NPDB physical library management module.
  • NPDB physical library 411 Between the 421 and the NPDB physical library 411 is a database interface; between the NPDB physical library management module 421 and the NPDB memory library management module 422 is a message interface, and the NPDB memory library management module 422 and the NPDB memory library 412 are message interfaces.
  • the service processor 43 When querying the RN information, the service processor 43 sends a message for querying the called user RN information.
  • the manner in which the NPDB memory library 412 is based in the present invention is more efficient when performing operations such as querying, and/or adding, and/or deleting, and/or modifying, and/or updating.
  • the NPDB memory library 412 exists as long as the device does not lose power.
  • the device of the present invention is protected as follows:
  • the NPDB memory library management module 422 When the NPDB memory library management module 422 is started, it is found that the NPDB memory library 412 is not established, and the NPDB memory library management module 422 reads data from the NPDB physical library 411 through the database interface and loads it into the NPDB memory library 412.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention se rapporte à un procédé et à un appareil permettant de réaliser une portabilité de numéro dans un système de messages courts. Le procédé comprend les étapes suivantes : un centre de message court (SMSC) recherche dans sa propre base de données de portabilités de numéro (NPDB) intégrée les informations de numéro de routage (RN) d'une personne appelée après réception d'un message court; le centre SMSC détermine si les informations de numéro RN indiquent un réseau local auquel appartient le centre SMSC selon les informations de numéro RN recherchées; lorsque les informations de numéro RN indiquent le réseau local, le centre SMSC établit finalement une connexion pour le message court; lorsque les informations de numéro RN n'indiquent pas le réseau local, le centre SMSC envoie le message court au réseau indiqué par les informations de numéro RN selon les informations de RN obtenues et établit finalement une connexion pour le message court. Le procédé et l'appareil peuvent être réalisés de façon simple et il n'est pas nécessaire de fabriquer le dispositif associé de la base de données NPDB.
PCT/CN2010/071232 2009-04-28 2010-03-23 Procédé et appareil permettant de réaliser une portabilité de numéro dans un système de messages courts WO2010124543A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
BRPI1013595-2A BRPI1013595B1 (pt) 2009-04-28 2010-03-23 Método e aparelhos para realizar a portabilidade em um sistema de mensagem curta

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910082717.4 2009-04-28
CN2009100827174A CN101540969B (zh) 2009-04-28 2009-04-28 号码携带在短消息系统中的实现方法和装置

Publications (1)

Publication Number Publication Date
WO2010124543A1 true WO2010124543A1 (fr) 2010-11-04

Family

ID=41123898

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/071232 WO2010124543A1 (fr) 2009-04-28 2010-03-23 Procédé et appareil permettant de réaliser une portabilité de numéro dans un système de messages courts

Country Status (3)

Country Link
CN (1) CN101540969B (fr)
BR (1) BRPI1013595B1 (fr)
WO (1) WO2010124543A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110248321A (zh) * 2019-05-22 2019-09-17 中国联合网络通信集团有限公司 一种携号转网号码管理的方法和系统
CN112423293A (zh) * 2020-11-18 2021-02-26 山东兆永信息科技有限公司 一种应用在携号转网情况下的提升消息指令送达率的方法

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101540969B (zh) * 2009-04-28 2012-01-25 中兴通讯股份有限公司 号码携带在短消息系统中的实现方法和装置
CN101699875B (zh) * 2009-10-20 2015-07-22 中兴通讯股份有限公司 消息发送方法和互通网关
CN101707766B (zh) * 2009-11-24 2013-01-16 中兴通讯股份有限公司 号码携带业务的查询方法、装置以及系统
CN101754128B (zh) * 2009-12-31 2012-12-19 上海粱江通信系统股份有限公司 一种实现移动网携出用户接收短消息的方法
CN102480721A (zh) * 2010-11-22 2012-05-30 中兴通讯股份有限公司 运营商路由号码的获取方法及服务器
CN103916458B (zh) * 2014-01-27 2017-08-01 国家电网公司 基于短信技术的电力企业内部应用程序远程监控系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101031149A (zh) * 2007-03-31 2007-09-05 华为技术有限公司 实现号码携带业务的装置、系统及其业务设备
CN101389075A (zh) * 2008-09-05 2009-03-18 中兴通讯股份有限公司 一种号码携带的短消息系统及其业务方法
CN101540969A (zh) * 2009-04-28 2009-09-23 中兴通讯股份有限公司 号码携带在短消息系统中的实现方法和装置
CN101661745A (zh) * 2009-09-28 2010-03-03 西安理工大学 一种将五线谱图像转换为声音文件的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101031149A (zh) * 2007-03-31 2007-09-05 华为技术有限公司 实现号码携带业务的装置、系统及其业务设备
CN101389075A (zh) * 2008-09-05 2009-03-18 中兴通讯股份有限公司 一种号码携带的短消息系统及其业务方法
CN101540969A (zh) * 2009-04-28 2009-09-23 中兴通讯股份有限公司 号码携带在短消息系统中的实现方法和装置
CN101661745A (zh) * 2009-09-28 2010-03-03 西安理工大学 一种将五线谱图像转换为声音文件的方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110248321A (zh) * 2019-05-22 2019-09-17 中国联合网络通信集团有限公司 一种携号转网号码管理的方法和系统
CN110248321B (zh) * 2019-05-22 2021-03-19 中国联合网络通信集团有限公司 一种携号转网号码管理的方法和系统
CN112423293A (zh) * 2020-11-18 2021-02-26 山东兆永信息科技有限公司 一种应用在携号转网情况下的提升消息指令送达率的方法
CN112423293B (zh) * 2020-11-18 2022-12-06 山东兆永信息科技有限公司 一种应用在携号转网情况下的提升消息指令送达率的方法

Also Published As

Publication number Publication date
CN101540969A (zh) 2009-09-23
BRPI1013595B1 (pt) 2021-04-27
BRPI1013595A2 (pt) 2016-08-23
CN101540969B (zh) 2012-01-25

Similar Documents

Publication Publication Date Title
WO2010124543A1 (fr) Procédé et appareil permettant de réaliser une portabilité de numéro dans un système de messages courts
CN109361526B (zh) 策略控制的路由方法、pcrf/pcf以及dra
JP4399599B2 (ja) Ｉｐドメインのｐｌｍｎメッセージングサービスの制御
US8812597B2 (en) Method and system for instant messaging traffic routing
CN102026124B (zh) 短信智能业务平台系统及基于该系统的短信业务实现方法
US20060031399A1 (en) Methods and systems for remotely securing data in a wireless device in a communications network
WO2011022967A1 (fr) Procédé, système et dispositif de mise en œuvre d'intercommunication de service de minimessages (sms) entre réseaux dans le service de conservation du numéro
BRPI0514485B1 (pt) Sistema de mensagens de multimídia e método para o envio de mensagens de multimídia
CN103765849A (zh) 使用哈希函数来分发网络标识
JP2007531387A (ja) ハードウェア部分をアドレス指定することにより移動機へメッセージを送信するための方法及び装置
WO2007115480A1 (fr) Procédé, système et équipement d'abonné itinérant intelligent de déclenchement de service intelligent dans son site nominal
WO2010108338A1 (fr) Procédé et système pour réaliser une communication basée sur un mode d'annuaire téléphonique en ligne
WO2010034192A1 (fr) Procédé et dispositif de déclenchement de demande d'acheminement et procédé, dispositif et système de traitement de demande d'acheminement
CN103188756A (zh) 一种跨域业务路由方法、装置、系统及相关设备
CN111970688A (zh) eSIM携号转网方法、终端设备及计算机可读存储介质
WO2011127717A1 (fr) Procédé et système de synchronisation de données pour demande de portabilité d'un numéro mobile de travail sur internet
CN103442357A (zh) 一种扩充最大支持用户数的方法及装置
WO2011157158A2 (fr) Procédé, système et centre de service de messages courts destinés à envoyer des messages courts
CN102244844A (zh) 一种发送彩信的方法，装置和系统
CN101483834B (zh) 一种使用短号码进行多媒体消息通信的方法及系统
CN100364346C (zh) 一种实现手机短号发送短消息的方法
WO2012000259A1 (fr) Procédé et système de réalisation de portabilité du numéro pour message court
AU2010262617B2 (en) Method and system for allocating delivery reports
JP2020500434A (ja) 通信サービスを端末通信装置に提供する通信ネットワークを決定する方法及び装置
WO2006119696A1 (fr) Procede de realisation de transferabilite de numero de telephone mobile base sur un service de donnees

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10769232

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10769232

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: PI1013595

Country of ref document: BR

REG Reference to national code

Ref country code: BR

Ref legal event code: B01E

Ref document number: PI1013595

Country of ref document: BR

Free format text: IDENTIFIQUE O SIGNATARIO DA PETICAO NO 020110098660 DE 22/09/2011, UMA VEZ QUE NAO E POSSIVEL IDENTIFICAR O NOME DO RESPONSAVEL PELA ASSINATURA DO FORMULARIO, NAO SENDO POSSIVEL DETERMINAR SE ESTE FAZ PARTE DOS PROCURADORES ELENCADOS NA PROCURACAO E SE TEM PODERES PARA ATUAR EM NOME DO DEPOSITANTE, E O ARTIGO 216 DA LEI 9.279/1996 DE 14/05/1996 (LPI) DETERMINA QUE OS ATOS PREVISTOS NESTA LEI SERAO PRATICADOS PELAS PARTES OU POR SEUS PROCURADORES, DEVIDAMENTE QUALIFICADOS .

ENP Entry into the national phase

Ref document number: PI1013595

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20110922