WO2017101592A1 - 呼叫方法及*** - Google Patents

呼叫方法及*** Download PDF

Info

Publication number
WO2017101592A1
WO2017101592A1 PCT/CN2016/103511 CN2016103511W WO2017101592A1 WO 2017101592 A1 WO2017101592 A1 WO 2017101592A1 CN 2016103511 W CN2016103511 W CN 2016103511W WO 2017101592 A1 WO2017101592 A1 WO 2017101592A1
Authority
WO
WIPO (PCT)
Prior art keywords
calling
playback
called
user
called number
Prior art date
Application number
PCT/CN2016/103511
Other languages
English (en)
French (fr)
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 中兴通讯股份有限公司
Publication of WO2017101592A1 publication Critical patent/WO2017101592A1/zh

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • 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
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H04W8/28—Number portability ; Network address portability

Definitions

  • the present disclosure relates to wireless communication technologies, for example, to a call method and system.
  • the operator's network to which the number of the called user belongs is usually unclear. For example, when the calling user makes a call, it is usually unclear whether the called user's number is a mobile number or a Unicom number. Or a telecommunication number and so on. Since the billing price of communication between different carrier networks is different, for some users who are sensitive to the communication cost, if there is an information processing scheme, when the user makes a call, the user can be prompted whether the called user is the same as the calling user.
  • the carrier network so that the calling user can decide the communication mode with the called user based on the determination result, which can greatly enhance the user experience.
  • the embodiment of the present disclosure provides a calling method and system, which can prompt the called user whether the called user is a local network user when the calling user initiates a call.
  • An embodiment of the present disclosure provides a calling method, where the method includes:
  • the gateway mobile switching center GMSC After receiving the calling routing request, the gateway mobile switching center GMSC sends a mobile application part MAP request message to the mobile number carrying MNP network element, where the MAP request message includes a calling number, a called number, and a call playback function label;
  • the MNP network element determines, according to the MAP request message, that the call play function tag is enabled, determines a call play attribute corresponding to the calling number based on the calling number, and obtains the call based on the called number search Carrying attribute corresponding to the called number;
  • the MNP network element sends a MAP response message to the GMSC, where the MAP response message carries a carrying attribute and a calling and playing attribute corresponding to the called number;
  • the GMSC indicates whether to output the playback prompt information based on the carried attribute and the calling playback attribute corresponding to the called number in the MAP response message.
  • the determining, according to the calling number, determining a calling party corresponding to the calling number Sex can include:
  • the MNP network element searches the home location register database HLRDB based on the calling number, determines whether the calling number is a local network user, and generates a calling playback attribute corresponding to the calling number based on the determination result.
  • the generating, by the determining result, the calling play attribute corresponding to the calling number may include:
  • the HRLDB is searched based on the calling number, the subscription information corresponding to the calling number is obtained, and the calling playback attribute is generated based on the subscription information. Call-to-play playback or caller suppression;
  • the calling playback attribute is generated as the main playback suppression.
  • the obtaining, by the called number, the carrying attribute corresponding to the called number may include:
  • the MNP network element searches the MNP database based on the called number, and obtains a carrying attribute corresponding to the called number.
  • the GMSC may indicate whether to output the playback prompt information based on the carrying attribute and the calling playback attribute corresponding to the called number in the MAP response message, which may include:
  • the GMSC identifies the calling playback attribute, and when the calling playback attribute is called playback suppression, indicating that the playback prompt information is not output;
  • the carrying attribute corresponding to the called number indicates whether to output the playback prompt information.
  • the carrying the attribute corresponding to the called number to indicate whether to output the playback prompt information may include:
  • the carrying attribute corresponding to the called number indicates that the called number belongs to an external network user, indicating that the playback prompt information indicates that the called user is an external network user.
  • the embodiment of the present disclosure further provides a call system, where the system includes: a GMSC and an MNP network element; among them,
  • the GMSC configured to send a mobile application part MAP request message to the MNP network element, after receiving the call routing request, where the MAP request message includes a calling number, a called number, and a call play function label; And indicating, according to the carried attribute and the calling play attribute corresponding to the called number in the MAP response message, whether to output the playback prompt information;
  • the MNP network element is configured to determine, according to the MAP request message, that the call play function tag is enabled, determine a call play attribute corresponding to the calling number based on the calling number, and search according to the called number Obtaining a carrying attribute corresponding to the called number; and sending a MAP response message to the GMSC, where the MAP response message carries a carrying attribute and a calling play attribute corresponding to the called number.
  • system may further include a home location register database HRLDB;
  • the MNP network element is configured to search for the HLRDB based on the calling number, determine whether the calling number is a local network user, and generate a calling playback attribute corresponding to the calling number based on the determination result.
  • the MNP network element may be further configured to: when the judgment result is that the calling number is a local network user, searching for the HHLDB based on the calling number, and obtaining the calling number corresponding to the calling number Signing information, generating, according to the subscription information, a calling playback attribute, a calling playback or a calling playback suppression; and when the determining result is that the calling number is a non-local user, generating a calling The playback property is called playback suppression.
  • the system may further include an MNP database
  • the MNP network element is configured to search the MNP database based on the called number, and obtain a carrying attribute corresponding to the called number.
  • the GMSC may be further configured to identify the calling playback attribute, and when the calling playback attribute is called playback suppression, indicating that the playback prompt information is not output; When the calling playback attribute is called the playback, the carrying attribute corresponding to the called number indicates whether to output the playback prompt information.
  • the GMSC may be further configured to: when the carrying attribute corresponding to the called number indicates that the called number belongs to a user of the local network, indicating that the playback prompt information indicates that the called user is a local network user; And when the carrying attribute corresponding to the called number indicates that the called number belongs to an external network user, indicating that the playback prompt information indicates that the called user is an external network user.
  • the present disclosure also provides a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the above method.
  • the present disclosure also provides an electronic device, including:
  • At least one processor At least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to:
  • MAP request message After receiving the call routing request, sending a mobile application part MAP request message to the mobile number carrying MNP network element, where the MAP request message includes a calling number, a called number, and a call play function label;
  • the present disclosure also provides an electronic device, including:
  • At least one processor At least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to:
  • the MNP network element sends a MAP response message to the gateway mobile switching center GMSC, where the MAP response message carries the carrying attribute and the calling and playing attribute corresponding to the called number.
  • the calling method and system provided by the embodiment of the present disclosure initiates a MAP request message carrying a call play function tag through the GMSC, and obtains a MAP response message carrying the carried attribute and the calling play attribute corresponding to the called number, and the GMSC according to the GMSC Whether the carried attribute and the calling playback attribute corresponding to the called number indicate whether to output
  • the play prompt prompts whether the called user is a local network user when the calling user initiates a call, so that the calling user can decide whether to continue communication with the called number according to the playback prompt, or control and call the called party.
  • the communication time of the number meets the communication fee requirement of the calling user, which greatly enhances the user experience.
  • FIG. 1 is a schematic flowchart of a calling method according to Embodiment 1 of the present disclosure
  • FIG. 2 is a schematic structural diagram of a structure of a call system according to Embodiment 2 of the present disclosure
  • FIG. 3 is a schematic structural diagram of a structure of a call system according to Embodiment 3 of the present disclosure
  • FIG. 4 is a schematic flowchart of a calling method according to Embodiment 4 of the present disclosure.
  • FIG. 5 is a schematic structural diagram of an electronic device provided by the present disclosure.
  • FIG. 1 is a schematic flowchart diagram of a calling method according to Embodiment 1 of the present disclosure. As shown in FIG. 1, the method includes steps 110 to 140.
  • the Gateway Mobile Switching Center sends a Mobile Application Part (MAP) to the Mobile Number Portability (MNP) network element.
  • MAP Mobile Application Part
  • MNP Mobile Number Portability
  • the call play function represented by the call play function label can be customized, for example, does not support the call release function, or supports the call release function, or supports the caller for a specific called user. Playback function and more.
  • the MNP network element determines, according to the MAP request message, that when the call play function tag is enabled, determining a call release attribute corresponding to the calling number based on the calling number, based on the called The number search obtains the carrying attribute corresponding to the called number.
  • the MNP network element is in a Home Location Register Database (Home Location Register Database, The HLRDB searches for the calling number, determines whether the calling number is a local network user, and generates a calling playback attribute corresponding to the calling number based on the determination result.
  • Home Location Register Database Home Location Register Database
  • the carrier uses the mobile operator network as an example. Under the mobile operator network, there is a communication system, including mobile operations.
  • the Home Location Register (HLR) under the quotient network; and the HLR is a database managed by the mobile user for storing and recording the subscription information of the users in the jurisdiction area, and dynamically updating the location information of the user for the call service. Provides the network route of the called user.
  • the MNP network element After receiving the MAP request message, the MNP network element obtains the calling number carried in the MAP request message, performs a lookup in the HHLDB, and determines whether the HRLDB records the location. The calling number. When it is determined that the calling number is recorded in the HHLDB, it is determined that the calling number is a local network user, and when it is determined that the calling number is not recorded in the HHLDB, determining that the calling number is external Web users.
  • the local network user or the external network user is the same as the carrier network to which the network element device in the embodiment belongs, that is, the network element device (including the GMSC and the MNP) in this embodiment. If the network element device such as the network element or the HLR belongs to an operator network, the corresponding calling number of the user belonging to the local network is also attributed to the carrier network, and the calling number of the external network user is not attributed to the operation. Business network.
  • the generating, by the determining result, the calling play attribute corresponding to the calling number including:
  • the calling number is searched in the HHLRB, the subscription information corresponding to the calling number is obtained, and the calling voice is generated based on the subscription information.
  • the attribute is called playback or caller suppression;
  • the calling playback attribute is generated as the main playback suppression.
  • the HLRDB should store the subscription information corresponding to the calling number, and the MNP network element can search for the calling number based on the calling number.
  • the HLRDB obtains the subscription information corresponding to the calling number.
  • the calling number can be personalized to whether the calling and playing function is enabled, that is, when the subscription information corresponding to the calling number is obtained, the MNP network element can obtain the Whether the calling party's playback function is enabled corresponding to the calling number included in the subscription information.
  • the subscription information includes the open calling playback function corresponding to the calling number
  • the calling playback attribute generated by the MNP network element is called the playback of the calling party.
  • the calling play attribute generated by the MNP network element is called the playback suppression.
  • the playing of the calling party indicates that when the calling number initiates a call, the playback prompt function is enabled; and the playback suppression of the calling party indicates that the playback prompt function is not enabled when the calling number initiates a call. .
  • the obtaining, by the called number, the carrying attribute corresponding to the called number may include:
  • the MNP network element searches the MNP database based on the called number, and obtains a carrying attribute corresponding to the called number.
  • the carrying attribute corresponding to the called number indicates whether the called number is a local network user.
  • the carrying attribute corresponding to the called number may include: the carrying type of the local network, the carrying type of the external network to the local network, the carrying type of the unknown state, the carrying type of the local network, the carrying type of the external network to the external network, and of course It is not limited to the types of carrying mentioned above.
  • the local network does not carry the carrying type and the external network to the local network carrying type, and the called number is the user of the local network; the unknown state carrying type, the carrying type carried by the local network, and the external network carrying the external network Type Characterization
  • the called number is an external network user.
  • the network is a mobile operator network
  • the type of the carrier that is not carried in the local network can be understood as that the called number is subscribed to the local network, that is, the network element device described in this embodiment.
  • a network element device including a GMSC, an MNP network element, or an HLR is attributed to an operator network.
  • the type of the external network to the local network can be understood as that the called number is originally signed under the external network (such as the telecommunication carrier network), and is now moved out of the external network to the local network (such as the mobile operator network), that is,
  • the called number is currently associated with a network element device (including a network element device such as a GMSC, an MNP network element, or an HLR) in the present embodiment.
  • the unknown state carrying type can be understood as that the MNP does not recognize the carrying type of the called number, and is processed as an external network user.
  • the carrying type of the local network can be understood as that the called number is originally signed under the local network (such as a mobile operator network), and is now moved out of the network to an external network (such as a telecom carrier network), that is,
  • the network element device (including the network element device such as the GMSC, the MNP network element, or the HLR) in the present embodiment belongs to a different carrier network.
  • the type of the external network to the external network can be understood as that the called number is originally signed under an external network (such as the Unicom carrier network), and is now contracted under another external network (such as a telecom carrier network), that is, The called number is currently assigned to a different carrier network by the network element device (including the GMSC, the MNP network element, or the network element device such as the HLR).
  • an external network such as the Unicom carrier network
  • another external network such as a telecom carrier network
  • step 130 the MNP network element sends a MAP response message to the GMSC,
  • the MAP response message carries the carried attribute and the calling play attribute corresponding to the called number.
  • step 140 the GMSC indicates whether to output the playback prompt information based on the carried attribute and the calling playback attribute corresponding to the called number in the MAP response message.
  • the GMSC according to the carrying attribute and the calling and playing attribute of the called number in the MAP response message, indicating whether to output the playback prompt information, may include:
  • the GMSC identifies the calling playback attribute, and when the calling playback attribute is called playback suppression, indicating that the playback prompt information is not output;
  • the carrying attribute corresponding to the called number indicates whether to output the playback prompt information.
  • the carrying attribute corresponding to the called number indicates whether to output the playback prompt information, including:
  • the carrying attribute corresponding to the called number indicates that the called number belongs to a user of the local network, indicating that the playback prompt information indicates that the called user is a local network user;
  • the carrying attribute corresponding to the called number indicates that the called number belongs to an external network user, indicating that the playback prompt information indicates that the called user is an external network user.
  • the GMSC When the carrying attribute corresponding to the called number does not carry the carrying type or the external network to the local network carrying type, and the called number is the local network user, the GMSC indicates that the output playback prompt information is characterized. The calling user is the user of this network. And when the carrying attribute corresponding to the called number is an unknown state carrying type, a carrying type of the local network, or an external network carrying type, the characterization of the called number is an external network user, and the GMSC indicates outputting The tone prompt information indicates that the called user is an external network user.
  • the MAP request message carrying the call play function label is initiated by the GMSC, and the MAP response message carrying the carried attribute and the calling play attribute corresponding to the called number is obtained, and the GMSC according to the
  • the carrying attribute corresponding to the called number and the calling play attribute indicate whether the playback prompt is output, and the calling user is prompted to be the local network user when the calling user initiates the call, so that the calling user can decide whether to make a decision according to the playback prompt.
  • the communication with the called number continues, or the communication time with the called number is controlled to meet the communication fee requirement of the calling user, which greatly improves the user experience.
  • Embodiments of the present disclosure also provide a call system.
  • 2 is a calling system according to Embodiment 2 of the present disclosure Schematic diagram of the composition, as shown in FIG. 2, the system includes: a GMSC 21 and an MNP network element 22. among them,
  • the GMSC 21 is configured to send a MAP request message to the MNP network element 22 after receiving the call routing request, where the MAP request message includes a calling number, a called number, and a call play function label;
  • the carrying attribute and the calling play attribute corresponding to the called number in the MAP response message indicate whether to output the playback prompt information.
  • the MNP network element 22 is configured to determine, according to the MAP request message, that the call play function tag is enabled, determine a call play attribute corresponding to the calling number based on the calling number, and search based on the called number Obtaining a carrying attribute corresponding to the called number; and sending a MAP response message to the GMSC 21, where the MAP response message carries a carrying attribute and a calling play attribute corresponding to the called number.
  • the call play function represented by the call play function label can be customized, for example, does not support the call release function, or supports the call release function, or supports the caller for a specific called user. Playback function and more.
  • the system may also include an HHLDB24;
  • the MNP network element 22 may be configured to search the HRLDB 24 based on the calling number, determine whether the calling number is a local network user, and generate a calling playback attribute corresponding to the calling number based on the determination result. .
  • the carrier uses the mobile operator network as an example.
  • Under the mobile operator network there is a communication system, including mobile operations.
  • HLR under the business network.
  • the HLR is a database managed by the mobile user for storing and recording the subscription information of the users in the area under the jurisdiction, and dynamically updating the location information of the user, so as to provide the network route of the called user in the call service.
  • the MNP network element 22 After receiving the MAP request message, the MNP network element 22 obtains the calling number carried in the MAP request message, searches for the HHLDB 24, and determines whether the HRLDB 24 records the location. The calling number. When it is determined that the calling number is recorded in the HHLDB 24, it is determined that the calling number is a local network user; when it is determined that the calling number is not recorded in the HHLDB 24, determining the calling number It is an external network user.
  • the MNP network element 22 is configured to: when the determination result is that the calling number is a local network user, the generated calling playback attribute is called a playback of the calling party; and when the determining result is When the calling number is a non-local user, the generated calling property is called the playback suppression.
  • the HRLDB 24 should store the subscription information corresponding to the calling number, and the MNP network element 22 can search based on the calling number.
  • the HLRDB 24 obtains subscription information corresponding to the calling number.
  • the calling number can be personalized to whether the calling and playing function is enabled; that is, when the subscription information corresponding to the calling number is obtained, the MNP network element 22 can be obtained. Whether the calling number corresponding to the calling number included in the subscription information turns on the calling playback function.
  • the subscription information includes the open calling playback function corresponding to the calling number
  • the calling playback attribute generated by the MNP network element 22 is called the playback of the calling party.
  • the calling play attribute generated by the MNP network element 22 is called the playback suppression.
  • the playing of the calling party indicates that when the calling number initiates a call, the playback prompt function is enabled; and the playback suppression of the calling party indicates that the playback prompt function is not enabled when the calling number initiates a call. .
  • the system may also include a MNP database 23.
  • the MNP network element 22 may be configured to search the MNP database 23 based on the called number to obtain a carrying attribute corresponding to the called number.
  • the carrying attribute corresponding to the called number indicates whether the called number is a local network user.
  • the carrying attribute corresponding to the called number may include: the carrying type of the local network, the carrying type of the external network to the local network, the carrying type of the unknown state, the carrying type of the local network, the carrying type of the external network to the external network, and of course It is not limited to the types of carrying mentioned above.
  • the local network does not carry the carrying type and the external network to the local network carrying type, and the called number is the user of the local network, the unknown state carrying type, the carrying type carried by the local network, and the external network carrying the external network.
  • Type Characterization The called number is an external network user.
  • the network is a mobile operator network
  • the type of the carrier that is not carried in the local network can be understood as that the called number is subscribed to the local network, that is, the network element device described in this embodiment.
  • the network element device including the GMSC 21, the MNP network element 22 or the HLR is attributed to a carrier network.
  • the type of the external network to the local network can be understood as that the called number is originally signed under the external network (such as the telecommunication carrier network), and is now moved out of the external network to the local network (such as the mobile operator network), that is,
  • the called number is currently associated with a network element device (including a network element device such as a GMSC 21, an MNP network element 22, or an HLR) in the present embodiment.
  • the unknown state carrying type can be understood as that the MNP does not recognize the carrying type of the called number, and is processed as an external network user.
  • the carrying type of the local network can be understood as that the called number is originally signed under the local network (such as a mobile operator network), and is now moved out of the network to an external network (such as a telecom carrier network), that is, The called number is currently assigned to a different carrier network by the network element device (including the GMSC 21, the MNP network element 22, or the network element device such as the HLR) described in this embodiment.
  • the type of the external network to the external network can be understood as that the called number is originally signed under an external network (such as the Unicom carrier network), and is now contracted under another external network (such as a telecom carrier network), that is, The called number is currently assigned to a different carrier network by the network element device (including the GMSC 21, the MNP network element 22, or the network element device such as the HLR).
  • an external network such as the Unicom carrier network
  • another external network such as a telecom carrier network
  • the GMSC 21 may be configured to identify the calling playback attribute, and when the calling playback attribute is called playback suppression, indicating that the playback prompt information is not output; When the calling playback attribute is called the playback, the carrying attribute corresponding to the called number indicates whether to output the playback prompt information.
  • the GMSC 21 is further configured to: when the carrying attribute corresponding to the called number is used to indicate that the called number belongs to a user of the local network, indicating that the output prompt information indicates that the called user is a local network user; When the carrying attribute corresponding to the called number indicates that the called number belongs to an external network user, indicating that the playback prompt information indicates that the called user is an external network user
  • the GMSC 21 When the carrying attribute corresponding to the called number does not carry the carrying type or the external network to the local network carrying type, and the called number is the local network user, the GMSC 21 indicates that the output playback prompt information is characterized. The called user is the user of this network. And when the carrying attribute corresponding to the called number is an unknown state carrying type, a carrying type of the local network, or an external network to an external network carrying type, indicating that the called number is an external network user, the GMSC 21 indicates the output. The playback prompt information indicates that the called user is an external network user.
  • the MAP request message carrying the call play function label is initiated by the GMSC 21, and the MAP response message carrying the carried attribute and the calling play attribute corresponding to the called number is obtained, and the GMSC 21
  • the carrying attribute corresponding to the called number and the calling play attribute indicate whether the playback prompt is output, and the calling user is prompted to be the local network user when the calling user initiates the call, so that the calling user can prompt the calling user according to the playback prompt. Whether the decision continues to communicate with the called number or control the communication time with the called number to meet the communication fee requirement of the calling user greatly improves the user experience.
  • FIG. 3 is a schematic structural diagram of a call system according to Embodiment 3 of the present disclosure.
  • the system includes: a GMSC 21, an MNP network element 22, an HLR database 24, and an MNP database 23, wherein
  • the MNP network element 22 may include: a Signaling Relay Function (SRF) function unit 221 and a Mobile Application Terminal Function (MATF) function unit 222;
  • SRF Signaling Relay Function
  • MATF Mobile Application Terminal Function
  • the GMSC 21 is configured to send a MAP request message to the SRF function unit 221 after receiving the call routing request of the user, where the MAP request message includes a calling number, a called number, and a call play function label; And indicating whether to output the playback prompt information based on the carried attribute and the calling playback attribute corresponding to the called number in the MAP response message.
  • the SRF function unit 221 is configured to receive the MAP request message, forward the MAP request message to the MATF function unit 222, and send the MAP response message to the GMSC 21.
  • the MATF function unit 222 is configured to determine, according to the MAP request message, that the call play function label is turned on, search the HRLDB 24 based on the calling number, and determine whether the calling number is a local network user, based on the judgment result. Generating a calling play attribute corresponding to the calling number; searching the MNP database 23 based on the called number, and obtaining a carrying attribute corresponding to the called number, where the carrying attribute corresponding to the called number includes: The network does not carry out, the external network to the local network carrying type and the unknown state, the local network carries out, the external network to the external network carrying type; and sends a MAP response message to the SRF functional unit 221, wherein the MAP response message Carrying the carrying attribute and the calling and playing attribute corresponding to the called number.
  • the SRF function unit 221 and the MATF function unit 222 may be used by a central processing unit (CPU) and a digital signal processor (DSP) in the MNP network element 22 in practical applications. , Digital Signal Processor) or Field Programmable Gate Array (FPGA) implementation.
  • CPU central processing unit
  • DSP digital signal processor
  • FPGA Field Programmable Gate Array
  • FIG. 4 is a schematic flowchart diagram of a calling method according to Embodiment 4 of the present disclosure. As shown in FIG. 4, the method includes steps 410 through 460.
  • step 410 after receiving the call routing request of the user, the GMSC sends a MAP request message to the SRF function unit (referred to as MNP-SRF) of the MNP network element, where the MAP request message includes the calling number and the called party. Number and call playback feature label.
  • MNP-SRF SRF function unit
  • the MNP-SRF forwards the MAP request message to the MATT function unit (denoted as MNP-MATF) of the MNP network element, wherein the MAP request message includes a calling number, a called number, and a call playback. Feature tag.
  • the MNP-MATF determines that the call play function label indicates that the call play function is enabled, and searches the home location register database (HLRDB) based on the calling number to determine whether the calling number is the local network.
  • HRDB home location register database
  • the carrier uses the mobile operator network as an example.
  • the mobile operator network there is a communication system, including mobile operations.
  • the HLR is a database managed by the mobile subscriber, and is used for storing and recording the subscription information of the users in the jurisdiction area, and dynamically updating the location information of the user to provide the network route of the called subscriber in the call service.
  • the MNP-MATF obtains the calling number carried in the MAP request message, searches for the HLRDB, and determines whether the calling party is recorded in the HHLDB. a number; when it is determined that the calling number is recorded in the HHLDB, determining that the calling number is a local network user; and when determining that the calling number is not recorded in the HHLDB, determining the calling The number is an external network user.
  • the subscription information corresponding to the calling number should be stored in the HLRDB; the MNP-MATF may be based on the calling The number is searched for the HHLDB, and the subscription information corresponding to the calling number is obtained.
  • the calling number can be personalized to whether the calling and playing function is enabled, that is, when the subscription information corresponding to the calling number is obtained, the MNP-MATF can obtain the location. Whether the calling party's playback function is enabled corresponding to the calling number included in the subscription information.
  • the calling playback attribute generated by the MNP-MATF is called the playback of the calling party; when determining the subscription information
  • the call release function is not enabled corresponding to the calling number, the calling play attribute generated by the MNP-MATF is called the playback suppression.
  • the playing of the calling party indicates that when the calling number initiates a call, the playback prompt function is enabled; and the playback suppression of the calling party indicates that the playback prompt function is not enabled when the calling number initiates a call. .
  • step 440 the MNP-MATF searches the MNP database based on the called number, and obtains the carrying attribute corresponding to the called number.
  • the carrying attribute corresponding to the called number indicates whether the called number is the local network. user.
  • the carrying attributes corresponding to the called number include: the carrying type of the local network, the carrying type of the external network to the local network, the carrying type of the unknown state, the carrying type of the local network, the carrying type of the external network to the external network, and of course not Limited to the types of carrying mentioned above.
  • the local network does not carry the carrying type and the external network to the local network carrying type, and the called number is the user of the local network, the unknown state carrying type, the carrying type carried by the local network, and the external network carrying the external network.
  • Type Characterization The called number is an external network user.
  • the network is a mobile operator network
  • the type of the carrier that is not carried in the local network can be understood as that the called number is subscribed to the local network, that is, the network element device described in this embodiment.
  • a network element device including a GMSC, an MNP network element, or an HLR is attributed to an operator network.
  • the type of the external network to the local network can be understood as that the called number is originally signed under the external network (such as the telecommunication carrier network), and is now moved out of the external network to the local network (such as the mobile operator network), that is,
  • the called number is currently associated with a network element device (including a network element device such as a GMSC, an MNP network element, or an HLR) in the present embodiment.
  • the unknown state carrying type can be understood as that the MNP-MATF does not recognize the carrying type of the called number, and is treated as an external network user.
  • the carrying type of the local network can be understood as that the called number is originally signed under the local network (such as a mobile operator network), and is now moved out of the network to an external network (such as a telecom carrier network), that is,
  • the network element device (including the network element device such as the GMSC, the MNP network element, or the HLR) in the present embodiment belongs to a different carrier network.
  • the type of the external network to the external network can be understood as that the called number is originally signed under an external network (such as the Unicom carrier network), and is now contracted under another external network (such as a telecom carrier network), that is, The called number is currently assigned to a different carrier network by the network element device (including the GMSC, the MNP network element, or the network element device such as the HLR).
  • an external network such as the Unicom carrier network
  • another external network such as a telecom carrier network
  • step 450 the MNP-MATF returns a MAP response message to the GMSC, where the MAP response message carries the calling playback attribute and the carrying attribute corresponding to the called number.
  • step 460 the GMSC indicates whether to output the playback prompt information based on the calling playback attribute and the carrying attribute corresponding to the called number.
  • the GMSC When the carrying attribute corresponding to the called number does not carry the carrying type or the external network to the local network carrying type, and the called number is the local network user, the GMSC indicates that the output playback prompt information is characterized. The calling user is the user of this network. And when the carrying attribute corresponding to the called number is an unknown state carrying type, a carrying type of the local network, or an external network carrying type, the characterization of the called number is an external network user, and the GMSC indicates outputting The tone prompt information indicates that the called user is an external network user.
  • the GMSC Adopting the technical solution of the embodiment of the present disclosure, launching a label carrying a call playback function through the GMSC
  • the MAP request message, and the MAP response message carrying the carrying attribute corresponding to the called number and the calling playback attribute, the GMSC indicates whether to output the playback prompt according to the carrying attribute and the calling playback attribute corresponding to the called number.
  • the calling user initiates a call
  • the user is prompted whether the called user is a local network user, so that the calling user can decide whether to continue communication with the called number according to the playback prompt, or control communication with the called number. Time to meet the communication charges of the calling user, greatly improving the user experience.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner such as: multiple units or components may be combined, or Can be integrated into a system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated.
  • the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units. Some or all of the units may be selected according to actual needs to implement the solution of the embodiment.
  • the functional units in the embodiments of the present disclosure may all be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit, the above integrated
  • the unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the methods of the above embodiments.
  • the present disclosure also provides a schematic structural diagram of a first electronic device.
  • the electronic device includes:
  • At least one processor 501 which is exemplified by a processor 501 in FIG. 5; and a memory 502, may further include a communication interface 503 and a bus 504.
  • the processor 501, the communication interface 503, and the memory 502 can complete communication with each other through the bus 504.
  • Communication interface 504 can be used for information transfer.
  • Processor 501 can invoke logic instructions in memory 502 to perform the methods performed by the GMSC in the above embodiments.
  • logic instructions in the memory 502 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the memory 502 is a computer readable storage medium and can be used to store software programs, computer executable programs, program instructions or modules corresponding to the methods in the embodiments of the present disclosure.
  • the processor 501 executes the function application and the data processing by executing a software program, an instruction or a module stored in the memory 502, that is, implementing the calling method in the above method embodiment.
  • the memory 502 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the terminal device, and the like. Further, the memory 502 may include a high speed random access memory, and may also include a nonvolatile memory.
  • the present disclosure also provides a second electronic device, the second electronic device being different from the first electronic device in that the processor 501 can call the logic instructions in the memory 502 to perform the method of performing the MNP network element in the above embodiment. .
  • GMSC and NMP can also be implemented in one device.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing storage device includes the following steps: the foregoing storage medium includes: a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • ROM read-only memory
  • RAM random access memory
  • magnetic disk or an optical disk.
  • optical disk A medium that can store program code.
  • the above-described integrated unit of the present disclosure may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product.
  • the technical solution of the embodiments of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (may be A personal computer, server, or network device, etc.) performs all or part of the methods described in the embodiments of the present disclosure.
  • the foregoing storage medium includes: a plurality of media that can store program codes, such as a mobile storage device, a ROM, a RAM, a magnetic disk, or an optical disk.
  • the calling method and system provided by the present disclosure enable the called party to be called when the calling user initiates a call. Whether the user is a user of the local network, so that the calling user can decide whether to continue communication with the called number according to the playback prompt, or control the communication time with the called number to meet the communication tariff requirement of the calling user, and greatly improve The user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本公开实施例公开了一种呼叫方法及***。所述方法包括：网关移动交换中心GMSC接收到主叫路由请求后，向移动号码携带MNP网元发送移动应用部分MAP请求消息，MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签；MNP网元基于MAP请求消息确定呼叫放音功能标签开启时，基于主叫号码确定所述主叫号码对应的主叫放音属性，基于被叫号码查找获得被叫号码对应的携带属性；MNP网元向GMSC发送MAP响应消息，MAP响应消息中携带被叫号码对应的携带属性和主叫放音属性；以及GMSC基于MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息。

Description

呼叫方法及*** 技术领域
本公开涉及无线通信技术，例如涉及一种呼叫方法及***。
背景技术
相关技术中，用户在拨打电话时，通常不清楚被叫用户的号码归属的运营商网络，例如，主叫用户在拨打电话时通常不清楚被叫用户的号码是移动号码、或是联通号码、或是电信号码等等。由于不同的运营商网络之间通信的计费价格不同，对于部分对通信费用敏感的用户，如果有一种信息处理方案，能够在用户拨打电话时，能够提示被叫用户是否与主叫用户属于同一运营商网络，以便主叫用户可基于判定结果决策与该被叫用户的通信方式，这样能够大大提升用户的体验。
发明内容
本公开实施例提供一种呼叫方法及***，能够在主叫用户发起呼叫时，提示被叫用户是否是本网用户。
本公开实施例提供了一种呼叫方法，所述方法包括：
网关移动交换中心GMSC接收到主叫路由请求后，向移动号码携带MNP网元发送移动应用部分MAP请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签；
所述MNP网元基于所述MAP请求消息确定呼叫放音功能标签开启时，基于所述主叫号码确定所述主叫号码对应的主叫放音属性，基于所述被叫号码查找获得所述被叫号码对应的携带属性；
所述MNP网元向所述GMSC发送MAP响应消息，所述MAP响应消息中携带所述被叫号码对应的携带属性和主叫放音属性；以及
所述GMSC基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息。
上述方案中，所述基于所述主叫号码确定所述主叫号码对应的主叫放音属 性，可以包括：
所述MNP网元基于所述主叫号码查找归属位置寄存器数据库HLRDB，判断所述主叫号码是否是本网用户，基于判断结果生成所述主叫号码对应的主叫放音属性。
上述方案中，所述基于判断结果生成所述主叫号码对应的主叫放音属性，可以包括：
当所述判断结果为所述主叫号码为本网用户时，基于所述主叫号码查找所述HLRDB，获得所述主叫号码对应的签约信息，基于所述签约信息生成主叫放音属性为主叫放音开启或主叫放音抑制；以及
当所述判断结果为所述主叫号码为非本网用户时，则生成主叫放音属性为主叫放音抑制。
上述方案中，所述基于所述被叫号码查找获得所述被叫号码对应的携带属性，可以包括：
所述MNP网元基于所述被叫号码查找MNP数据库，获得所述被叫号码对应的携带属性。
上述方案中，所述GMSC基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息，可以包括：
所述GMSC识别所述主叫放音属性，当所述主叫放音属性为主叫放音抑制时，指示不输出放音提示信息；以及
当所述主叫放音属性为主叫放音开启时，基于所述被叫号码对应的携带属性指示是否输出放音提示信息。
上述方案中，所述基于所述被叫号码对应的携带属性指示是否输出放音提示信息，可以包括：
当所述被叫号码对应的携带属性表征所述被叫号码归属于本网用户时，指示输出放音提示信息表征被叫用户是本网用户；
当所述被叫号码对应的携带属性表征所述被叫号码归属于外网用户时，指示输出放音提示信息表征被叫用户是外网用户。
本公开实施例还提供了一种呼叫***，所述***包括：GMSC和MNP网元； 其中，
所述GMSC，设置为接收到主叫路由请求后，向所述MNP网元发送移动应用部分MAP请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签；以及基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息；
所述MNP网元，设置为基于所述MAP请求消息确定呼叫放音功能标签开启时，基于所述主叫号码确定所述主叫号码对应的主叫放音属性，基于所述被叫号码查找获得所述被叫号码对应的携带属性；以及向所述GMSC发送MAP响应消息，所述MAP响应消息中携带所述被叫号码对应的携带属性和主叫放音属性。
上述方案中，所述***还可以包括归属位置寄存器数据库HLRDB；
所述MNP网元，设置为基于所述主叫号码查找所述HLRDB，判断所述主叫号码是否是本网用户，基于判断结果生成所述主叫号码对应的主叫放音属性。
上述方案中，所述MNP网元，还可以设置为当所述判断结果为所述主叫号码为本网用户时，基于所述主叫号码查找所述HLRDB，获得所述主叫号码对应的签约信息，基于所述签约信息生成主叫放音属性为主叫放音开启或主叫放音抑制；以及当所述判断结果为所述主叫号码为非本网用户时，则生成主叫放音属性为主叫放音抑制。
上述方案中，所述***还可以包括MNP数据库；
所述MNP网元，设置为基于所述被叫号码查找MNP数据库，获得所述被叫号码对应的携带属性。
上述方案中，所述GMSC，还可以设置为识别所述主叫放音属性，当所述主叫放音属性为主叫放音抑制时，则指示不输出放音提示信息；以及当所述主叫放音属性为主叫放音开启时，基于所述被叫号码对应的携带属性指示是否输出放音提示信息。
上述方案中，所述GMSC，还可以设置为当所述被叫号码对应的携带属性表征所述被叫号码归属于本网用户时，指示输出放音提示信息表征被叫用户是本网用户；以及当所述被叫号码对应的携带属性表征所述被叫号码归属于外网用户时，指示输出放音提示信息表征被叫用户是外网用户。
本公开还提供了一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述方法。
本公开还提供了一种电子设备，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器执行：
接收到主叫路由请求后，向移动号码携带MNP网元发送移动应用部分MAP请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签；以及
基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息。
本公开还提供了一种电子设备，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器执行：
基于移动应用部分MAP请求消息确定呼叫放音功能标签开启时，基于主叫号码确定所述主叫号码对应的主叫放音属性，基于被叫号码查找获得所述被叫号码对应的携带属性；
基于所述MAP请求消息确定呼叫放音功能标签开启时，基于所述主叫号码确定所述主叫号码对应的主叫放音属性，基于所述被叫号码查找获得所述被叫号码对应的携带属性；以及
所述MNP网元向网关移动交换中心GMSC发送MAP响应消息，所述MAP响应消息中携带所述被叫号码对应的携带属性和主叫放音属性。本公开实施例提供的呼叫方法及***，通过GMSC发起携带有呼叫放音功能标签的MAP请求消息，以及获得携带有被叫号码对应的携带属性和主叫放音属性的MAP响应消息，GMSC根据所述被叫号码对应的携带属性和主叫放音属性指示是否输出 放音提示，实现了在主叫用户发起呼叫时，提示被叫用户是否是本网用户，便于主叫用户根据放音提示决策是否与该被叫号码继续进行通信，或者控制与所述被叫号码的通信时间，以满足主叫用户的通信资费需求，大大提升了用户的体验。
附图说明
图1为本公开实施例一的呼叫方法的流程示意图；
图2为本公开实施例二的呼叫***的组成结构示意图；
图3为本公开实施例三的呼叫***的组成结构示意图；
图4为本公开实施例四的呼叫方法的流程示意图；以及
图5是本公开提供的电子设备的结构示意图。
具体实施方式
下面结合附图及实施例对本公开作详细的说明。
实施例一
本公开实施例提供了一种呼叫方法。图1为本公开实施例一的呼叫方法的流程示意图。如图1所示，所述方法包括步骤110至步骤140。
在步骤110中，网关移动交换中心(Gateway Mobile Switching Center，GMSC)接收到用户的主叫路由请求后，向移动号码携带(Mobile Number Portability，MNP)网元发送移动应用部分(Mobile Application Part，MAP)请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签。
本实施例中，所述呼叫放音功能标签表征的呼叫放音功能可自定义设置，例如不支持主叫放音功能、或支持主叫放音功能、或者针对特定的被叫用户支持主叫放音功能等等。
在步骤120中，所述MNP网元基于所述MAP请求消息确定呼叫放音功能标签开启时，基于所述主叫号码确定所述主叫号码对应的主叫放音属性，基于所述被叫号码查找获得所述被叫号码对应的携带属性。
所述MNP网元在归属位置寄存器数据库(Home Location Register Database， HLRDB)查找所述主叫号码，判断所述主叫号码是否是本网用户，基于判断结果生成所述主叫号码对应的主叫放音属性。
对于每一个运营商网络下的通信***，均有其对应的一套通信设备网络，以运营商为移动运营商网络为例，在移动运营商网络下，具有一套通信***，其中包括移动运营商网络下归属位置寄存器(Home Location Register，HLR)；而HLR是移动用户管理的数据库，用于存储和记录所辖区域内用户的签约信息，并动态地更新用户的位置信息，以便在呼叫业务中提供被呼叫用户的网络路由。基于此，在本实施例中，所述MNP网元接收到所述MAP请求消息后，获得所述MAP请求消息中携带的主叫号码，在HLRDB中进行查找，判断所述HLRDB中是否记录所述主叫号码。当判定所述HLRDB中记录所述主叫号码时，则确定所述主叫号码是本网用户以及当判定所述HLRDB中未记录所述主叫号码时，则确定所述主叫号码是外网用户。
本实施例中，所述本网用户或外网用户是相对于本实施例中的网元设备归属的运营商网络而言，即当本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于一运营商网络，则相应的属于本网用户的主叫号码也归属于所述运营商网络，属于外网用户的主叫号码不归属于所述运营商网络。
可选地，所述基于判断结果生成所述主叫号码对应的主叫放音属性，包括：
当所述判断结果为所述主叫号码为本网用户时，在所述HLRDB中查找所述主叫号码，获得所述主叫号码对应的签约信息，基于所述签约信息生成主叫放音属性为主叫放音开启或主叫放音抑制；以及
当所述判断结果为所述主叫号码为非本网用户时，则生成主叫放音属性为主叫放音抑制。
当所述判断结果为所述主叫号码为本网用户时，则所述HLRDB中应存储有所述主叫号码对应的签约信息，所述MNP网元可基于所述主叫号码查找所述HLRDB，获得所述主叫号码对应的签约信息。本实施例中，在用户签约时，可个性化设置所述主叫号码是否开启主叫放音功能，也即在获得所述主叫号码对应的签约信息时，所述MNP网元可获得所述签约信息中包含的所述主叫号码对应的是否开启主叫放音功能。当确定所述签约信息中包含所述主叫号码对应的开启主叫放音功能时，则所述MNP网元生成的主叫放音属性为主叫放音开启。 当确定所述签约信息中包含所述主叫号码对应的不开启主叫放音功能时，则所述MNP网元生成的主叫放音属性为主叫放音抑制。其中，所述主叫放音开启表明当所述主叫号码发起呼叫时，开启放音提示功能；所述主叫放音抑制表明当所述主叫号码发起呼叫时，不开启放音提示功能。
本实施例中，所述基于所述被叫号码查找获得所述被叫号码对应的携带属性，可以包括：
所述MNP网元基于所述被叫号码查找MNP数据库，获得所述被叫号码对应的携带属性。
本实施例中，所述被叫号码对应的携带属性表征所述被叫号码是否是本网用户。所述被叫号码对应的携带属性可以包括：本网未携出携带类型、外网到本网携带类型，以及未知状态携带类型、本网携出携带类型、外网到外网携带类型，当然不限于上述提出的几种携带类型。其中，所述本网未携出携带类型和外网到本网携带类型表征所述被叫号码是本网用户；所述未知状态携带类型、本网携出携带类型、外网到外网携带类型表征所述被叫号码是外网用户。其中，以本网为移动运营商网络为例，所述本网未携出携带类型可以理解为所述被叫号码签约在本网下，也即与本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于一运营商网络。所述外网到本网携带类型可以理解为所述被叫号码原签约在外网(如电信运营商网络)下，现由外网迁出至本网(如移动运营商网络)下，也即所述被叫号码当前与本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于一运营商网络。基于此，说明上述两种携带类型表征被叫号码是本网用户。所述未知状态携带类型可以理解为所述MNP未识别出所述被叫号码的携带类型，作为外网用户处理。所述本网携出携带类型可以理解为所述被叫号码原签约在本网(如移动运营商网络)下，现由本网迁出至外网(如电信运营商网络)下，也即所述被叫号码当前与本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于不同的运营商网络。所述外网到外网携带类型可以理解为所述被叫号码原签约在一外网(如联通运营商网络)下，现签约在另一外网(如电信运营商网络)下，也即所述被叫号码当前与本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于不同的运营商网络。
在步骤130中，所述MNP网元向所述GMSC发送MAP响应消息，所述 MAP响应消息中携带所述被叫号码对应的携带属性和主叫放音属性。
在步骤140中，所述GMSC基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息。
所述GMSC基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息，可以包括：
所述GMSC识别所述主叫放音属性，当所述主叫放音属性为主叫放音抑制时，则指示不输出放音提示信息；以及
当所述主叫放音属性为主叫放音开启时，基于所述被叫号码对应的携带属性指示是否输出放音提示信息。
可选地，所述基于所述被叫号码对应的携带属性指示是否输出放音提示信息，包括：
当所述被叫号码对应的携带属性表征所述被叫号码归属于本网用户时，指示输出放音提示信息表征被叫用户是本网用户；以及
当所述被叫号码对应的携带属性表征所述被叫号码归属于外网用户时，指示输出放音提示信息表征被叫用户是外网用户。
当所述被叫号码对应的携带属性为本网未携出携带类型或外网到本网携带类型，表征所述被叫号码是本网用户，则所述GMSC指示输出放音提示信息表征被叫用户是本网用户。当所述被叫号码对应的携带属性为未知状态携带类型、本网携出携带类型或外网到外网携带类型时，表征所述被叫号码是外网用户，则所述GMSC指示输出放音提示信息表征被叫用户是外网用户。
采用本公开实施例的技术方案，通过GMSC发起携带有呼叫放音功能标签的MAP请求消息，以及获得携带有被叫号码对应的携带属性和主叫放音属性的MAP响应消息，GMSC根据所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示，实现了在主叫用户发起呼叫时，提示被叫用户是否是本网用户，便于主叫用户根据放音提示决策是否与该被叫号码继续进行通信，或者控制与所述被叫号码的通信时间，以满足主叫用户的通信资费需求，大大提升了用户的体验。
实施例二
本公开实施例还提供了一种呼叫***。图2为本公开实施例二的呼叫*** 的组成结构示意图，如图2所示，所述***包括：GMSC 21和MNP网元22。其中，
所述GMSC 21设置为接收到主叫路由请求后，向所述MNP网元22发送MAP请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签；以及基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息。
所述MNP网元22设置为基于所述MAP请求消息确定呼叫放音功能标签开启时，基于所述主叫号码确定所述主叫号码对应的主叫放音属性，基于所述被叫号码查找获得所述被叫号码对应的携带属性；以及向所述GMSC 21发送MAP响应消息，所述MAP响应消息中携带所述被叫号码对应的携带属性和主叫放音属性。
本实施例中，所述呼叫放音功能标签表征的呼叫放音功能可自定义设置，例如不支持主叫放音功能、或支持主叫放音功能、或者针对特定的被叫用户支持主叫放音功能等等。
所述***还可以包括HLRDB24；
所述MNP网元22，可以设置为基于所述主叫号码查找所述HLRDB 24，判断所述主叫号码是否是本网用户，基于判断结果生成所述主叫号码对应的主叫放音属性。
对于每一个运营商网络下的通信***，均有其对应的一套通信设备网络，以运营商为移动运营商网络为例，在移动运营商网络下，具有一套通信***，其中包括移动运营商网络下HLR。而HLR是移动用户管理的数据库，用于存储和记录所辖区域内用户的签约信息，并动态地更新用户的位置信息，以便在呼叫业务中提供被呼叫用户的网络路由。基于此，在本实施例中，所述MNP网元22接收到所述MAP请求消息后，获得所述MAP请求消息中携带的主叫号码，查找HLRDB 24，判断所述HLRDB 24中是否记录所述主叫号码。当判定所述HLRDB 24中记录所述主叫号码时，则确定所述主叫号码是本网用户；当判定所述HLRDB 24中未记录所述主叫号码时，则确定所述主叫号码是外网用户。
可选地，所述MNP网元22设置为当所述判断结果为所述主叫号码为本网用户时，则生成的主叫放音属性为主叫放音开启；以及当所述判断结果为所述主叫号码为非本网用户时，则生成的主叫放音属性为主叫放音抑制。
当所述判断结果为所述主叫号码为本网用户时，则所述HLRDB 24中应存储有所述主叫号码对应的签约信息，所述MNP网元22可基于所述主叫号码查找所述HLRDB 24，获得所述主叫号码对应的签约信息。本实施例中，在用户签约时，可个性化设置所述主叫号码是否开启主叫放音功能；也即在获得所述主叫号码对应的签约信息时，所述MNP网元22可获得所述签约信息中包含的所述主叫号码对应的是否开启主叫放音功能。当确定所述签约信息中包含所述主叫号码对应的开启主叫放音功能时，则所述MNP网元22生成的主叫放音属性为主叫放音开启。当确定所述签约信息中包含所述主叫号码对应的不开启主叫放音功能时，则所述MNP网元22生成的主叫放音属性为主叫放音抑制。其中，所述主叫放音开启表明当所述主叫号码发起呼叫时，开启放音提示功能；所述主叫放音抑制表明当所述主叫号码发起呼叫时，不开启放音提示功能。
所述***还可以包括MNP数据库23。
所述MNP网元22可以设置为基于所述被叫号码查找MNP数据库23，获得所述被叫号码对应的携带属性。
本实施例中，所述被叫号码对应的携带属性表征所述被叫号码是否是本网用户。所述被叫号码对应的携带属性可以包括：本网未携出携带类型、外网到本网携带类型，以及未知状态携带类型、本网携出携带类型、外网到外网携带类型，当然不限于上述提出的几种携带类型。其中，所述本网未携出携带类型和外网到本网携带类型表征所述被叫号码是本网用户，所述未知状态携带类型、本网携出携带类型、外网到外网携带类型表征所述被叫号码是外网用户。其中，以本网为移动运营商网络为例，所述本网未携出携带类型可以理解为所述被叫号码签约在本网下，也即与本实施例中所述的网元设备(包括GMSC 21、MNP网元22或HLR等网元设备)归属于一运营商网络。所述外网到本网携带类型可以理解为所述被叫号码原签约在外网(如电信运营商网络)下，现由外网迁出至本网(如移动运营商网络)下，也即所述被叫号码当前与本实施例中所述的网元设备(包括GMSC 21、MNP网元22或HLR等网元设备)归属于一运营商网络。基于此，说明上述两种携带类型表征被叫号码是本网用户。所述未知状态携带类型可以理解为所述MNP未识别出所述被叫号码的携带类型，作为外网用户处理。所述本网携出携带类型可以理解为所述被叫号码原签约在本网(如移动运营商网络)下，现由本网迁出至外网(如电信运营商网络)下，也即所 述被叫号码当前与本实施例中所述的网元设备(包括GMSC 21、MNP网元22或HLR等网元设备)归属于不同的运营商网络。所述外网到外网携带类型可以理解为所述被叫号码原签约在一外网(如联通运营商网络)下，现签约在另一外网(如电信运营商网络)下，也即所述被叫号码当前与本实施例中所述的网元设备(包括GMSC 21、MNP网元22或HLR等网元设备)归属于不同的运营商网络。
本实施例中，所述GMSC 21可以设置为识别所述主叫放音属性，当所述主叫放音属性为主叫放音抑制时，则指示不输出放音提示信息；以及当所述主叫放音属性为主叫放音开启时，基于所述被叫号码对应的携带属性指示是否输出放音提示信息。
可选地，所述GMSC 21还设置为当所述被叫号码对应的携带属性表征所述被叫号码归属于本网用户时，指示输出放音提示信息表征被叫用户是本网用户；以及当所述被叫号码对应的携带属性表征所述被叫号码归属于外网用户时，指示输出放音提示信息表征被叫用户是外网用户
当所述被叫号码对应的携带属性为本网未携出携带类型或外网到本网携带类型，表征所述被叫号码是本网用户，则所述GMSC 21指示输出放音提示信息表征被叫用户是本网用户。当所述被叫号码对应的携带属性为未知状态携带类型、本网携出携带类型或外网到外网携带类型时，表征所述被叫号码是外网用户，则所述GMSC 21指示输出放音提示信息表征被叫用户是外网用户。
采用本公开实施例的技术方案，通过GMSC 21发起携带有呼叫放音功能标签的MAP请求消息，以及获得携带有被叫号码对应的携带属性和主叫放音属性的MAP响应消息，GMSC 21根据所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示，实现了在主叫用户发起呼叫时，提示被叫用户是否是本网用户，便于主叫用户根据放音提示决策是否与该被叫号码继续进行通信，或者控制与所述被叫号码的通信时间，以满足主叫用户的通信资费需求，大大提升了用户的体验。
实施例三
基于实施例二，本公开实施例还提供了一种呼叫***，图3为本公开实施例三的呼叫***的组成结构示意图。如图3所示，在本实施例中，所述***包括：GMSC 21、MNP网元22、HLR数据库24和MNP数据库23，其中，所述 MNP网元22可以包括：信今终止功能(Signaling Relay Function，SRF)功能单元221和移动应用终端功能(Mobile Application Terminal Function，MATF)功能单元222；其中，
所述GMSC 21设置为接收到用户的主叫路由请求后，向所述SRF功能单元221发送MAP请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签；以及基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息。
所述SRF功能单元221设置为接收到所述MAP请求消息，将所述MAP请求消息转发至所述MATF功能单元222；以及将所述MAP响应消息发送至所述GMSC 21。
所述MATF功能单元222设置为基于所述MAP请求消息确定呼叫放音功能标签开启时，基于所述主叫号码查找所述HLRDB 24，判断所述主叫号码是否是本网用户，基于判断结果生成所述主叫号码对应的主叫放音属性；基于所述被叫号码查找MNP数据库23，获得所述被叫号码对应的携带属性，其中，所述被叫号码对应的携带属性包括：本网未携出、外网到本网携带类型以及未知状态、本网携出、外网到外网携带类型；以及发送MAP响应消息至所述SRF功能单元221，其中，所述MAP响应消息中携带所述被叫号码对应的携带属性和主叫放音属性。
本实施例中，所述SRF功能单元221和所述MATF功能单元222，在实际应用中均可由所述MNP网元22中的中央处理器(CPU，Central Processing Unit)、数字信号处理器(DSP，Digital Signal Processor)或可编程门阵列(FPGA，Field Programmable Gate Array)实现。
实施例四
基于实施例三提供的呼叫***，本公开实施例还提供了一种呼叫方法。图4为本公开实施例四的呼叫方法的流程示意图。如图4所示，所述方法包括步骤410至步骤460。
在步骤410中，GMSC接收到用户的主叫路由请求后，向MNP网元的SRF功能单元(记为MNP-SRF)发送MAP请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签。
在步骤420中，MNP-SRF将所述MAP请求消息转发至MNP网元的MATF功能单元(记为MNP-MATF)，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签。
在步骤430中，MNP-MATF确定所述呼叫放音功能标签表征呼叫放音功能开启启时，基于所述主叫号码查找归属位置寄存器数据库(HLRDB)，判断所述主叫号码是否是本网用户；当所述主叫号码是本网用户时，查找HLRDB获得所述主叫号码的签约信息，基于所述签约信息生成主叫放音属性。
对于每一个运营商网络下的通信***，均有其对应的一套通信设备网络，以运营商为移动运营商网络为例，在移动运营商网络下，具有一套通信***，其中包括移动运营商网络下HLR，而HLR是移动用户管理的数据库，用于存储和记录所辖区域内用户的签约信息，并动态地更新用户的位置信息，以便在呼叫业务中提供被呼叫用户的网络路由。基于此，在本实施例中，所述MNP-MATF接收到所述MAP请求消息后，获得所述MAP请求消息中携带的主叫号码，查找HLRDB，判断所述HLRDB中是否记录所述主叫号码；当判定所述HLRDB中记录所述主叫号码时，则确定所述主叫号码是本网用户；以及当判定所述HLRDB中未记录所述主叫号码时，则确定所述主叫号码是外网用户。
可选地，当所述判断结果为所述主叫号码为本网用户时，则所述HLRDB中应存储有所述主叫号码对应的签约信息；所述MNP-MATF可基于所述主叫号码查找所述HLRDB，获得所述主叫号码对应的签约信息。本实施例中，在用户签约时，可个性化设置所述主叫号码是否开启主叫放音功能，也即在获得所述主叫号码对应的签约信息时，所述MNP-MATF可获得所述签约信息中包含的所述主叫号码对应的是否开启主叫放音功能。当确定所述签约信息中包含所述主叫号码对应的开启主叫放音功能时，则所述MNP-MATF生成的主叫放音属性为主叫放音开启；当确定所述签约信息中包含所述主叫号码对应的不开启主叫放音功能时，则所述MNP-MATF生成的主叫放音属性为主叫放音抑制。其中，所述主叫放音开启表明当所述主叫号码发起呼叫时，开启放音提示功能；所述主叫放音抑制表明当所述主叫号码发起呼叫时，不开启放音提示功能。
在步骤440中，MNP-MATF基于所述被叫号码查找MNP数据库，获得所述被叫号码对应的携带属性。
本实施例中，所述被叫号码对应的携带属性表征所述被叫号码是否是本网 用户。所述被叫号码对应的携带属性包括：本网未携出携带类型、外网到本网携带类型，以及未知状态携带类型、本网携出携带类型、外网到外网携带类型，当然不限于上述提出的几种携带类型。其中，所述本网未携出携带类型和外网到本网携带类型表征所述被叫号码是本网用户，所述未知状态携带类型、本网携出携带类型、外网到外网携带类型表征所述被叫号码是外网用户。其中，以本网为移动运营商网络为例，所述本网未携出携带类型可以理解为所述被叫号码签约在本网下，也即与本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于一运营商网络。所述外网到本网携带类型可以理解为所述被叫号码原签约在外网(如电信运营商网络)下，现由外网迁出至本网(如移动运营商网络)下，也即所述被叫号码当前与本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于一运营商网络。基于此，说明上述两种携带类型表征被叫号码是本网用户。所述未知状态携带类型可以理解为所述MNP-MATF未识别出所述被叫号码的携带类型，作为外网用户处理。所述本网携出携带类型可以理解为所述被叫号码原签约在本网(如移动运营商网络)下，现由本网迁出至外网(如电信运营商网络)下，也即所述被叫号码当前与本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于不同的运营商网络。所述外网到外网携带类型可以理解为所述被叫号码原签约在一外网(如联通运营商网络)下，现签约在另一外网(如电信运营商网络)下，也即所述被叫号码当前与本实施例中所述的网元设备(包括GMSC、MNP网元或HLR等网元设备)归属于不同的运营商网络。
在步骤450中，MNP-MATF向GMSC返回MAP响应消息，其中，所述MAP响应消息携带所述主叫放音属性以及被叫号码对应的携带属性。
在步骤460中，GMSC基于所述主叫放音属性以及被叫号码对应的携带属性指示是否输出放音提示信息。
当所述被叫号码对应的携带属性为本网未携出携带类型或外网到本网携带类型，表征所述被叫号码是本网用户，则所述GMSC指示输出放音提示信息表征被叫用户是本网用户。当所述被叫号码对应的携带属性为未知状态携带类型、本网携出携带类型或外网到外网携带类型时，表征所述被叫号码是外网用户，则所述GMSC指示输出放音提示信息表征被叫用户是外网用户。
采用本公开实施例的技术方案，通过GMSC发起携带有呼叫放音功能标签 的MAP请求消息，以及获得携带有被叫号码对应的携带属性和主叫放音属性的MAP响应消息，GMSC根据所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示，实现了在主叫用户发起呼叫时，提示被叫用户是否是本网用户，便于主叫用户根据放音提示决策是否与该被叫号码继续进行通信，或者控制与所述被叫号码的通信时间，以满足主叫用户的通信资费需求，大大提升了用户的体验。
在本申请所提供的几个实施例中，应该理解到，所揭露的设备和方法，可以通过其它的方式实现。以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到一个***，或一些特征可以忽略，或不执行。另外，所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元，即可以位于一个地方，也可以分布到多个网络单元上，可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案。
另外，在本公开实施例中的功能单元可以全部集成在一个处理单元中，也可以是每个单元分别单独作为一个单元，也可以两个或两个以上单元集成在一个单元中，上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
本公开实施例还提供了一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述实施例中的方法。
本公开还提供了第一种电子设备的结构示意图。参见图5，该电子设备包括：
至少一个处理器(processor)501，图5中以一个处理器501为例；和存储器(memory)502，还可以包括通信接口(Communications Interface)503和总线504。其中，处理器501、通信接口503、存储器502可以通过总线504完成相互间的通信。通信接口504可以用于信息传输。处理器501可以调用存储器502中的逻辑指令，以执行上述实施例中GMSC执行的方法。
此外，上述的存储器502中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。
存储器502作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如本公开实施例中的方法对应的程序指令或模块。处理器501通过运行存储在存储器502中的软件程序、指令或模块，从而执行功能应用以及数据处理，即实现上述方法实施例中的呼叫方法。
存储器502可包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使用所创建的数据等。此外，存储器502可以包括高速随机存取存储器，还可以包括非易失性存储器。
本公开还提供了第二种电子设备，第二种电子设备与第一种电子设备的区别在于：处理器501可以调用存储器502中的逻辑指令，以执行上述实施例中MNP网元执行的方法。
其中，GMSC和NMP的功能也可以在一个设备中实现。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：移动存储设备、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等多种可以存储程序代码的介质。
或者，本公开上述集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开实施例的技术方案本质上可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一个或多个指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本公开实施例所述方法的全部或部分。而前述的存储介质包括：移动存储设备、ROM、RAM、磁碟或者光盘等多种可以存储程序代码的介质。
工业实用性
本公开提供的呼叫方法及***，实现了在主叫用户发起呼叫时，提示被叫 用户是否是本网用户，便于主叫用户根据放音提示决策是否与该被叫号码继续进行通信，或者控制与所述被叫号码的通信时间，以满足主叫用户的通信资费需求，大大提升了用户的体验。

Claims (13)

  1. 一种呼叫方法，包括：
    网关移动交换中心GMSC接收到主叫路由请求后，向移动号码携带MNP网元发送移动应用部分MAP请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签；
    所述MNP网元基于所述MAP请求消息确定呼叫放音功能标签开启时，基于所述主叫号码确定所述主叫号码对应的主叫放音属性，基于所述被叫号码查找获得所述被叫号码对应的携带属性；
    所述MNP网元向所述GMSC发送MAP响应消息，所述MAP响应消息中携带所述被叫号码对应的携带属性和主叫放音属性；以及
    所述GMSC基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息。
  2. 根据权利要求1所述的方法，其中，所述基于所述主叫号码确定所述主叫号码对应的主叫放音属性，包括：
    所述MNP网元基于所述主叫号码查找归属位置寄存器数据库HLRDB，判断所述主叫号码是否是本网用户，基于判断结果生成所述主叫号码对应的主叫放音属性。
  3. 根据权利要求2所述的方法，其中，所述基于判断结果生成所述主叫号码对应的主叫放音属性，包括：
    当所述判断结果为所述主叫号码为本网用户时，基于所述主叫号码查找所述HLRDB，获得所述主叫号码对应的签约信息，基于所述签约信息生成主叫放音属性为主叫放音开启或主叫放音抑制；以及
    当所述判断结果为所述主叫号码为非本网用户时，则生成主叫放音属性为主叫放音抑制。
  4. 根据权利要求1所述的方法，其中，所述基于所述被叫号码查找获得所述被叫号码对应的携带属性，包括：
    所述MNP网元基于所述被叫号码查找MNP数据库，获得所述被叫号码对应的携带属性。
  5. 根据权利要求4所述的方法，其中，所述GMSC基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息，包括：
    所述GMSC识别所述主叫放音属性，当所述主叫放音属性为主叫放音抑制时，指示不输出放音提示信息；以及
    当所述主叫放音属性为主叫放音开启时，基于所述被叫号码对应的携带属性指示是否输出放音提示信息。
  6. 根据权利要求5所述的方法，其中，所述基于所述被叫号码对应的携带属性指示是否输出放音提示信息，包括：
    当所述被叫号码对应的携带属性表征所述被叫号码归属于本网用户时，指示输出放音提示信息表征被叫用户是本网用户；以及
    当所述被叫号码对应的携带属性表征所述被叫号码归属于外网用户时，指示输出放音提示信息表征被叫用户是外网用户。
  7. 一种呼叫***，包括：网关移动交换中心GMSC和移动号码携带MNP网元；其中，
    所述GMSC，设置为接收到主叫路由请求后，向所述MNP网元发送移动应用部分MAP请求消息，其中，所述MAP请求消息包括主叫号码、被叫号码以及呼叫放音功能标签；以及基于所述MAP响应消息中所述被叫号码对应的携带属性和主叫放音属性指示是否输出放音提示信息；
    所述MNP网元，设置为基于所述MAP请求消息确定呼叫放音功能标签开启时，基于所述主叫号码确定所述主叫号码对应的主叫放音属性，基于所述被叫号码查找获得所述被叫号码对应的携带属性；以及向所述GMSC发送MAP响应消息，所述MAP响应消息中携带所述被叫号码对应的携带属性和主叫放音属性。
  8. 根据权利要求7所述的***，所述***还包括归属位置寄存器数据库HLRDB；
    所述MNP网元，设置为基于所述主叫号码查找所述HLRDB，判断所述主叫号码是否是本网用户，基于判断结果生成所述主叫号码对应的主叫放音属性。
  9. 根据权利要求8所述的***，其中，所述MNP网元，设置为当所述判断结果为所述主叫号码为本网用户时，基于所述主叫号码查找所述HLRDB，获得所述主叫号码对应的签约信息，基于所述签约信息生成主叫放音属性为主叫放音开启或主叫放音抑制；以及当所述判断结果为所述主叫号码为非本网用户时，则生成主叫放音属性为主叫放音抑制。
  10. 根据权利要求7所述的***，所述***还包括MNP数据库；
    所述MNP网元，设置为基于所述被叫号码查找MNP数据库，获得所述被叫号码对应的携带属性。
  11. 根据权利要求10所述的***，其中，所述GMSC，设置为识别所述主叫放音属性，当所述主叫放音属性为主叫放音抑制时，则指示不输出放音提示信息；以及当所述主叫放音属性为主叫放音开启时，基于所述被叫号码对应的携带属性指示是否输出放音提示信息。
  12. 根据权利要求11所述的***，其中，所述GMSC，设置为当所述被叫号码对应的携带属性表征所述被叫号码归属于本网用户时，指示输出放音提示 信息表征被叫用户是本网用户；以及当所述被叫号码对应的携带属性表征所述被叫号码归属于外网用户时，指示输出放音提示信息表征被叫用户是外网用户。
  13. 一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-6中任一项的方法。
PCT/CN2016/103511 2015-12-16 2016-10-27 呼叫方法及*** WO2017101592A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510942990.5A CN106888438A (zh) 2015-12-16 2015-12-16 一种呼叫方法及***
CN201510942990.5 2015-12-16

Publications (1)

Publication Number Publication Date
WO2017101592A1 true WO2017101592A1 (zh) 2017-06-22

Family

ID=59055696

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/103511 WO2017101592A1 (zh) 2015-12-16 2016-10-27 呼叫方法及***

Country Status (2)

Country Link
CN (1) CN106888438A (zh)
WO (1) WO2017101592A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113676855B (zh) * 2021-08-25 2022-08-23 中国联合网络通信集团有限公司 携号转网方法、携号转网服务器、运营商服务器
CN113630767B (zh) * 2021-08-25 2022-09-16 中国联合网络通信集团有限公司 终端寻址方法及服务器

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101090566A (zh) * 2006-06-15 2007-12-19 中国电信股份有限公司 漫游接入模式下实现智能业务的方法和网关移动交换中心
CN101340717A (zh) * 2008-08-12 2009-01-07 ***通信集团江苏有限公司 一种基于智能网的分区、分时、分群综合业务解决方法
US7664496B1 (en) * 2006-07-14 2010-02-16 At&T Mobility Ii Llc Local number portability for mobility management
CN102487496A (zh) * 2009-10-27 2012-06-06 中国电信股份有限公司 移动通信***和在号码携带业务中呼叫路由的实现方法
CN103415028A (zh) * 2013-07-22 2013-11-27 中国联合网络通信集团有限公司 业务发起提示方法和网元设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101090566A (zh) * 2006-06-15 2007-12-19 中国电信股份有限公司 漫游接入模式下实现智能业务的方法和网关移动交换中心
US7664496B1 (en) * 2006-07-14 2010-02-16 At&T Mobility Ii Llc Local number portability for mobility management
CN101340717A (zh) * 2008-08-12 2009-01-07 ***通信集团江苏有限公司 一种基于智能网的分区、分时、分群综合业务解决方法
CN102487496A (zh) * 2009-10-27 2012-06-06 中国电信股份有限公司 移动通信***和在号码携带业务中呼叫路由的实现方法
CN103415028A (zh) * 2013-07-22 2013-11-27 中国联合网络通信集团有限公司 业务发起提示方法和网元设备

Also Published As

Publication number Publication date
CN106888438A (zh) 2017-06-23

Similar Documents

Publication Publication Date Title
TW580839B (en) Method and apparatus for providing subscriber-based ringback tone
US11082548B2 (en) System and method for providing a pre-populated second line service to a telecommunications device
EP2747337A1 (en) Online charging method, apparatus, and system based on number portability service
US11323562B2 (en) Communication method for processing crank call
WO2016173349A1 (zh) 一种网络接入方法及移动通信终端
JP2014527661A (ja) サーバおよびクライアントのためのモバイルペイメント方法、装置、およびシステム
WO2017101592A1 (zh) 呼叫方法及***
KR101392018B1 (ko) 단일번호를 이용한 멀티 단말로의 통화 지원 시스템 및 방법
US9485707B2 (en) Direct routing of communication sessions for mobile IP communication end points
US8781084B2 (en) Providing selective voice mail services
CN110086945B (zh) 通信方法、服务器、智能设备、服务器、存储介质
CN109818909B (zh) 一种呼叫处理方法及装置
CN108696829B (zh) 一种补充业务设置处理方法及装置
US20150334251A1 (en) Method and systems for dynamic selection of an originating identifier for billing optimization
CN104735643A (zh) 一种信息处理的方法及数据服务器
CN105530618A (zh) 用于实现虚拟号码业务的方法和***
KR101740611B1 (ko) 다중 번호 서비스를 위한 통신 단말 및 그 통신 단말의 정보 구분 표시 방법
CN114222284A (zh) 终端设备识别方法、装置及可读存储介质
CN109995949B (zh) 改号业务处理方法及装置
CN115529375B (zh) 界面显示方法、装置和电子设备
JP2017050854A (ja) 電気通信サーバと連携する電話番号情報サーバ及びその情報提供方法
CN107548050A (zh) 一种选择网元设备的方法和装置
CN104284036A (zh) 一种网络融合的实现方法及装置
CN105981358B (zh) 存储、拨打电话号码的方法及装置
CN107295202B (zh) 综合虚拟专用网呼叫的方法及***

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: 16874649

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: 16874649

Country of ref document: EP

Kind code of ref document: A1