WO2009062403A1 - Procédé pour réaliser un service de présentation du nom de l'appelant et dispositif de service d'informations relatives à l'appelant - Google Patents

Procédé pour réaliser un service de présentation du nom de l'appelant et dispositif de service d'informations relatives à l'appelant Download PDF

Info

Publication number
WO2009062403A1
WO2009062403A1 PCT/CN2008/070896 CN2008070896W WO2009062403A1 WO 2009062403 A1 WO2009062403 A1 WO 2009062403A1 CN 2008070896 W CN2008070896 W CN 2008070896W WO 2009062403 A1 WO2009062403 A1 WO 2009062403A1
Authority
WO
WIPO (PCT)
Prior art keywords
calling
called
information
service
party
Prior art date
Application number
PCT/CN2008/070896
Other languages
English (en)
French (fr)
Inventor
Wen Zhou
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to BRPI0806227-7A priority Critical patent/BRPI0806227A2/pt
Priority to EP08169098.4A priority patent/EP2061222B1/en
Publication of WO2009062403A1 publication Critical patent/WO2009062403A1/zh
Priority to ZA2009/03839A priority patent/ZA200903839B/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42034Calling party identification service
    • H04M3/42042Notifying the called party of information on the calling party
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2201/00Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/22Synchronisation circuits

Definitions

  • the present invention relates to the field of communication technologies, and specifically relates to implementing a calling name display (Calling Name)
  • the calling name display service also known as the calling information service, is a value-added service. Its main function is that when the user dials the called number as the calling party, the calling information set by the calling user, such as the calling electronic business card, greeting, etc., is sent by the service system to the called terminal by means of flash communication. On the top, the called user can intuitively obtain the caller information. The user can customize the calling information according to the scenario. For example, different calling information can be sent to different called, different time periods, and different areas by setting a personalized filtering rule.
  • the so-called flash message belongs to one of the short messages. After receiving the flash message, the terminal does not need to display the content by operating the button as the traditional short message, but directly displays its content on the screen, and usually does not The content is saved after the display is completed.
  • the calling name display service is different from the caller ID service.
  • the caller ID is sent by the switching system to the called terminal, and the called terminal directly displays the number, or displays the name of the calling user corresponding to the number in the directory book saved by the terminal;
  • the user information corresponding to the calling number is not recorded in the directory, and the called terminal can only display the calling number, and if the called user does not activate the caller ID function, the calling number cannot be seen even.
  • the calling name display service is set by the calling user. When the calling user dials the called telephone, the service system can send the calling information to the called terminal, so that the called party can identify the caller.
  • the calling user terminal sends a call request to the switching system.
  • the switching system judges that the call needs to trigger the calling name display service, and sends a caller information request to the calling information server, and simultaneously performs a call to the called user terminal after receiving the calling information returned by the calling information server. Continue operation.
  • the calling information server stores the calling information set by the calling user, and according to the calling information request sent by the switching system, the corresponding calling information is sent to the called user terminal for display by flashing.
  • the inventor of the present invention finds that, in the call flow capable of implementing the calling name display service, after the call is triggered, the sending operation of the calling information and the connection operation of the called terminal are Two independent processes are difficult to ensure that the calling information is sent to the called terminal at the right time. In some cases, it does not facilitate the called user to identify the incoming call. For example, if the calling information is sent to the called terminal before the called party rings, and the called party is answering another incoming call, or another incoming call is ringing, it will bring misunderstanding to the called user; If the calling information is sent to the called terminal after the calling party and the called party start talking or after the call ends, the called party has lost the meaning of knowing the calling information in advance. Summary of the invention
  • Embodiments of the present invention provide a method for realizing caller ID display service by transmitting caller information to a called terminal at an appropriate timing, and a corresponding caller information service device.
  • a method for implementing a calling name display service comprising: receiving a service request sent by a switching system, where the service request carries an identifier of a calling party and a called party; and querying, by the identity of the calling party, a calling party set by the calling user Information, querying the location information of the called party according to the called identifier; after determining that the called terminal has ringed, sending, according to the called location information, a flash message carrying the calling information to the Called.
  • a caller information service device comprising: a location query unit, configured to query location information of a called party according to an identifier of the called party; a service processing unit, configured to receive a service request sent by the switching system, where the service request carries a calling party And the called identity; query the calling user according to the identity of the calling party The caller information is set; after determining that the called terminal has ringed, the flash message carrying the calling information is sent to the called party according to the location information of the called party found by the location query unit.
  • the embodiment of the invention adopts a method for transmitting a flash message carrying the calling information to the called party after determining that the called terminal has ringed. Since the state judgment of the call connection process is associated with the execution timing of the calling name display service, it is possible to transmit the calling information to the called terminal at an appropriate timing, which is advantageous for the called user to correctly recognize the incoming information.
  • FIG. 1 is a schematic diagram of main steps of a method for implementing a calling name display service according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram showing a basic logical structure of a calling information service device according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a logical structure of a calling information service device corresponding to the method of the first embodiment
  • FIG. 5 is a schematic diagram of a specific signaling process according to the first embodiment
  • FIG. 6 is a schematic flowchart of a method for implementing a calling name display service according to Embodiment 2 of the present invention
  • FIG. 7 is a schematic diagram of a logical structure of a calling information service device corresponding to the second embodiment
  • FIG. 8 is a specific message based on Embodiment 2. Schematic diagram of the process;
  • FIG. 9 is a schematic flowchart of a method for implementing a calling name display service according to Embodiment 3 of the present invention.
  • FIG. 10 is a schematic diagram showing a logical structure of a calling information service device corresponding to the third embodiment;
  • FIG. 11 is a specific message based on Embodiment 3. Diagram of the process. detailed description
  • Step 1 receiving a service request sent by the switching system, where the called service request carries the identifiers of the calling party and the called party.
  • the so-called exchange system refers to the network system that provides communication services for the primary and called users; the switching equipment including the primary and called end offices, such as the mobile services switching center (MSC: Mobile Service Switching) Center ), Service Switching Piont, etc., and devices that provide related data services, such as VLR (Visitor Location Register), Home Location Register (HLR).
  • MSC Mobile Service Switching
  • HLR Home Location Register
  • the so-called service request is a request triggered by the service order information of a certain party during the call process, and may be a request for displaying the service for the calling name or a request for other services.
  • the "other service” is associated with the calling name display service, and the execution of the service can be triggered by the caller name display request for the service.
  • Step 2 Query the calling party information set by the calling user according to the identity of the calling party, and query the location information of the called party according to the called identifier.
  • the two operations in this step are used to obtain the data required for the transmission of the calling information.
  • the execution of the data is not strictly limited. After obtaining the identification of the primary and the called, the execution of the calling information can be performed at any time before the sending of the calling information. Compared with the restrictions in Step3, the two operations are arranged before or after determining that the called terminal has ringed.
  • the executed "query called location information" may be an operation specific to the calling name display business process, or may be an operation in other business execution processes, as long as the result of the query can be used when sending the calling information. Just fine.
  • Step 3 After determining that the called terminal has ringed, send the flash message carrying the calling information to the called party according to the location information of the called party.
  • the sending timing of the calling information is based on the judgment of the current execution state of the call connection process, and different judgment modes can be designed according to the actual system and the characteristics of the specific call flow, including but not limited to the following:
  • the calling information service device of the embodiment of the present invention for performing the above method mainly includes:
  • the location query unit 001 is configured to: query the location information of the called party according to the identifier of the called party; the service processing unit 002 is configured to receive a service request sent by the switching system, where the service request carries the identifier of the calling party and the called party; The called identifier queries the calling information set by the calling user. After determining that the called terminal has ringed, the flashing message carrying the calling information is sent to the called party according to the location information of the called party found by the location query unit 001.
  • the above-mentioned calling information service device may operate through an SCP (Service Control Point), or a combination of SCP and Intelligent Peripheral (IP), or other services.
  • SCP Service Control Point
  • IP Intelligent Peripheral
  • Embodiment 1 A method for implementing a calling name display service, referring to FIG. 3, includes the steps:
  • the calling information request is a request for displaying a service to the calling name, and is initiated by the calling end office in the switching system.
  • the method for initiating the request can be performed by referring to the request initiation mode of the CAMEL (Customized Applications for Mobile Network Enhanced Logic) service, that is, the calling party provided by the calling end office according to the HLR after the call is triggered.
  • the originating CAMEL Subscription Information (0-CSI: Originating CAMEL Subscription Information) knows that the calling user subscribes to the calling name display service, thereby triggering the calling information request.
  • the calling information set by the calling user can be obtained by querying the saved business database.
  • the location information of the called party may be queried by sending a short message routing information request (SRI_for_SM: Send Routing Information for Short Message) to the called HLR.
  • SRI_for_SM Send Routing Information for Short Message
  • the delay timing can be set after receiving the calling information request sent by the calling end office. After the period, it is determined that the called terminal has ringed.
  • the specific value of the delay time n can be determined experimentally according to the application network, and it is recommended to be 3 to 10 seconds.
  • the calling end office supports reporting the ringing event (for example, the calling end office supports CAMEL 4)
  • the calling party may send a reported ringing to the calling end office.
  • the request of the event after receiving the called ringing event reported by the calling end office, it is determined that the called terminal has ringed.
  • A31 After receiving the caller information request sent by the calling end office, send a request to the calling end office to report the call hang-up and/or the called response event.
  • the request of this step may be sent together with the request for reporting the ringing event of the called party.
  • the determination that the called terminal has ringed needs to include: After receiving the caller's on-hook or called response event reported by the calling end office, the caller information service processing is ended.
  • the service termination judgment may be comprehensively performed with the timing judgment, that is, it is determined whether the calling party reported by the calling end office is hanged up during the time limit or The called response event, if yes, ends the caller information service processing; if not, it determines that the called terminal has ringed after the timing expires.
  • An embodiment of the calling information service device for performing the method of the embodiment, with reference to FIG. 4, includes: a location query unit 101, configured to query location information of the called party according to the called identifier.
  • the service processing unit 102 includes a processing subunit 1021 and a control subunit 1022.
  • the processing sub-unit 1021 is configured to receive a caller information request sent by the calling end office according to the subscription information of the calling party, where the calling information request carries the identifier of the calling party and the called party; and the calling user setting is queried according to the identity of the calling party.
  • the caller information is sent to the called party according to the location information of the called party detected by the location query unit 101 according to the indication of the control subunit 1022;
  • the processing subunit 1021 is further configured to: after receiving the caller information request sent by the calling end office, send a report to the calling end office to report the called ringing event.
  • the processing sub-unit 1021 may be further configured to: after receiving the caller information request sent by the calling end office, send the reporting caller to the calling end office to hang up and/or Or the request of the called party to answer the event.
  • the control sub-unit 1022 is configured to perform a confirmation of the ringing of the called terminal after the processing sub-unit 1021 receives the request for the calling information, and the specific function may be one of the following two types:
  • the instructing processing unit 1021 After receiving the called ringing event reported by the calling end office, the instructing processing unit 1021 sends a flash message carrying the calling information. And further, after receiving the call hang-up or called response event reported by the calling end office, ending the calling information service processing.
  • the calling information service device in this embodiment may be implemented by using an SCP.
  • the calling name display service may be triggered by the calling end office according to the 0-CSI using an initial detection point (IDP: Initial Detect Point) message to the SCP;
  • IDP Initial Detect Point
  • the reporting request of the event may be requested by the SCP to be configured to the calling end office by using the BCSM Event (RRBE: Request Report BCSM Event);
  • the location information of the called party may be obtained by the SCP from the SLR that the called HLR initiates SRI_for_SM.
  • the solution in this embodiment can ensure that after the called terminal rings, the called user sends the calling information to the called terminal before (and/or before the calling user hangs up), so that the called user can accurately know that the called user is ringing.
  • the correspondence between the call and the received calling information is convenient for the called user to know the calling information in advance.
  • the SCP is used as the calling information service device, and the calling end office (MSC/VLR/SSP) supports CAMEL 2.
  • the SCP performs the acknowledgment judgment of the called terminal ringing in a delayed timing manner.
  • the call flow for implementing the calling name display service includes: al.
  • the calling MSC/VLR/SSP receives the calling name and displays the call request sent by the service user, and triggers the service according to the 0-CSI of the calling user.
  • the calling party belongs to the SCP to send an IDP message;
  • the calling party belongs to the SCP, and the calling party sets the calling information set by the calling user to the calling party.
  • the MSC/VLR/SSP sends an RRBE message, and configures the calling party to hang up and the called response event;
  • the calling home SCP sends a Continue or Connect message to the calling MSC/VLR/SSP, instructing to continue the call connection, and starts delaying the timing n seconds; during the n seconds, if the calling end office reports the calling party to hang up, Calling the response event, the SCP ends the caller information service processing;
  • the calling MSC/VLR/SSP sends a routing information request to the called home HLR (SRI: Send
  • MSRN Mobile Station Roaming Number
  • the called party HLR sends a roaming code request (PRN: Provide Roaming Number) to the called MSC/VLR/SSP to query the called MSRN;
  • PRN Provide Roaming Number
  • the called party HLR sends a SRI response SRI_ack to the calling MSC/VLR/SSP, carrying the called MSRN;
  • the calling MSC/VLR/SSP sends an initial address message (IAM: Initial Address Message) to the called MSC/VLR/SSP according to the called MSRN, and connects the call to the called MSC/VLR/SSP; A9.
  • the called MSC/VLR/SSP sends a call request to the called terminal (MS: Mobile Station); the called terminal starts ringing;
  • the called MSC/VLR/SSP sends an address (ACM: Address Complete Message) message to the calling MSC/VLR/SSP;
  • ACM Address Complete Message
  • the calling party home SCP sends an SRI_for_SM message to the called HLR;
  • the called HLR returns the SRI_for_SM response SRI_for_SM_Ack to the calling party's home SCP, and carries the location information of the called party, including the called MSC address and the called party's International Mobile Subscriber Identity (IMSI).
  • IMSI International Mobile Subscriber Identity
  • the calling home SCP sends a flashing message Forward_SM carrying the calling information to the called MSC; al4, the called MSC sends a flash message carrying the calling information to the called terminal; the called terminal displays the calling information, and continues to play Ringing tone
  • the called MSC returns to the calling home SCP Forward_SM response Forward_SM_Ack; al6, the called user hears the ringing, sees the calling information, answers the incoming call, and returns a response to the called MSC;
  • the called MSC sends an answer message (ANM: ANswer message) to the calling MSC, and the calling party and the called party start talking.
  • NAM ANswer message
  • Embodiment 2 A method for implementing a calling name display service, the difference between the embodiment and the first embodiment is that the calling information service device directly participates in the call connection process in the embodiment, and indicates the current call connection state according to the call connection process. The message is made to determine that the called terminal has ringed.
  • Process Reference Figure 6 including the steps:
  • This step can be performed by referring to the first step A1 of the first embodiment.
  • the calling information service device After receiving the caller information request sent by the calling end office, sending a call routing request to the calling end office. In this step, the calling information service device notifies the calling end office to route the call to itself, and the calling information service device performs subsequent call connection operations. If the calling information service device is implemented based on the SCP, the Connect message sent to the calling end office in the SCP may be added with a specific access code before the called number, and the calling end office may call according to the access code. Route to the calling information service device.
  • This step can be performed with reference to the usual call connection process.
  • it is required to query the HLR of the called party to obtain the related address information of the called party.
  • the response returned by the called HLR usually includes the IMSI and the called party required to send the short message.
  • the MSC address (VMSC-Address) parameter so the address information obtained by the process can be used for subsequent transmission of the flash message carrying the calling information.
  • it is also possible to query the location information of the called party through a specially executed request process.
  • This step can be performed at any time before the flash message is sent after receiving the caller information request.
  • B5. After receiving the connection response returned by the called end office, determine that the called terminal has ringed, and send the flash message carrying the calling information to the called party according to the location information of the called party.
  • the calling information service device can also play the ring back tone for the calling party according to the usual connection processing procedure, if the called party sets the ring back tone , then connect the CRBT platform to play the ring tones for the calling party.
  • the caller information service device can send a call to the calling end office without requesting the calling end office to report the BCSM event to pay attention to the call status. End the session with the calling end office after the routing request.
  • the calling information service device still requires the calling end office to report the BCSM event, the related process is similar to the first embodiment and will not be described again.
  • An embodiment of the calling information service device for performing the method of the embodiment, with reference to FIG. 7, includes: a location query unit 201, configured to query location information of the called party according to the identifier of the called party.
  • the connection processing unit 203 is configured to receive a call routed by the calling end office according to the call routing request, send a call connection request to the called end office, and receive a connection response returned by the called end office.
  • the service processing unit 202 includes a processing subunit 2021 and a control subunit 2022.
  • the processing subunit 2021 is configured to receive a caller information request sent by the calling end office according to the subscription information of the calling party, where the caller information request carries the identifier of the calling party and the called party; After the information request is sent, the call routing request is sent to the calling end office; the calling information set by the calling user is queried according to the identity of the calling party; according to the instruction of the control subunit 2022, the called location of the called party according to the location query unit 201 is found. The information is sent to the called party with a flash message carrying the calling information;
  • the processing sub-unit 2021 is further configured to: after receiving the caller information request sent by the calling end office, send the reporting caller to the calling end office and hang up and/or Or the request of the called party to answer the event.
  • the control subunit 2022 is configured to, after determining that the connection processing unit 203 receives the subsequent response returned by the called end office, instruct the processing subunit 2021 to send a flash message carrying the calling information. And further, after receiving the call hang-up or called response event reported by the calling end office, ending the calling information service processing.
  • the calling information service device of this embodiment can be implemented by a combination of SCP and IP connected to each other through an interface, and the call connection function is provided by the IP.
  • the service processing unit 202 is set to the SCP
  • the location query unit 201 and the connection processing unit 203 are set to the IP.
  • the location query unit 201 for providing the called location information for the flash transmission may be a logical unit for providing the called address query function for the connection process of the connection processing unit 203.
  • the connection processing unit 203 is found according to the location query unit 201.
  • the called location information sends a call connection request to the called end office.
  • the solution in this embodiment can ensure that after the called terminal rings, the called user sends the calling information to the called terminal before (and/or before the calling user hangs up), so that the called user can accurately know that the called user is ringing.
  • the correspondence between the call and the received calling information is convenient for the called user to know the calling information in advance.
  • the call flow for implementing the calling name display service includes: Bl, the calling MSC/VLR/SSP receives the calling name to display the call request sent by the service user, and triggers the service according to the 0-CSI of the calling user, and sends an IDP message to the calling home SCP;
  • the calling party's home SCP queries the calling party's caller information, sends an RRBE message to the calling MSC/VLR/SSP, and configures the calling party to hang up and answer the responding event (this step can be omitted);
  • the calling party SCP sends a Connect message to the calling MSC/VLR/SSP, and the called number carries a specific routing code, instructing the calling MSC to route the call to the IP;
  • the calling MSC routes the call to the IP in the calling information service device according to the routing code before the called number;
  • B5 ⁇ b8 refer to a4 ⁇ a7, the IP address of the calling information service device acquires the called MSRN and IMSI and VMSC-Address;
  • the calling information service device sends an IAM to the called MSC/VLR/SSP according to the called MSRN, and connects the call to the called MSC/VLR/SSP;
  • the called MSC/VLR/SSP sends a call request to the called MS; the called terminal starts ringing; bll, the called MSC/VLR/SSP sends an ACM message to the calling information service device; bl2, the calling information service device The IP in the middle sends an ACM message to the calling MSC, and plays a ring back tone to the calling party;
  • the SCP in the calling information service device sends the flash message Forward_SM carrying the calling information to the called MSC;
  • the IMSI and VMSC-Address used for the flash message transmission can be obtained from the SRI_ack received in step b8, through IP and SCP The interface between the two is passed to the SCP;
  • the called MSC sends a flash message carrying the calling information to the called terminal; the called terminal displays the calling information, and continues to play the ringing tone;
  • the called MSC returns the Forward_SM response Forward_SM_Ack to the SCP in the calling information service device;
  • Bl6 the called user hears the ringing, sees the calling information, answers the incoming call, and returns a response to the called MSC; Bl7, the called MSC returns to the ANM to the IP in the calling information service device;
  • the IP in the calling information service device returns to the calling MSC to the ANM; the calling party and the called party start the call.
  • Embodiment 3 A method for implementing a calling name display service, the difference between the embodiment and the first embodiment is that the calling name display service is associated with the first service, and the first service is triggered according to the first service.
  • the timing of the service itself, the trigger of the service is regarded as the confirmation that the called terminal has ringed.
  • the process refers to Figure 9, including the steps:
  • the so-called first service request is a request for a first service with a specific trigger opportunity.
  • the so-called first service may be triggered by the calling end office after the calling end office receives the connection response returned by the called end office, or may be triggered by the called end office after the called end office sends a call request to the called terminal. .
  • the CRBT service is selected as the first service, and the corresponding first service request is the CRBT service request.
  • the CRBT service in this embodiment may be in the form of a different order of the calling CRBT or the called CRBT.
  • the triggering may also be performed by the calling end office or the called end office.
  • the specific service execution mode may be from the existing application mode.
  • the called CRBT service mode triggered by the calling end office may be adopted, that is, after the calling end office receives the connection response returned by the called end office, according to the called service code obtained from the HLR to which the called party belongs ( CRBT SS_CODE ), triggers the CRBT service request.
  • C2 After determining, according to the identifier of the calling party carried in the first service request, the calling user subscribes to the calling name display service, and queries the calling party information set by the calling user; and queries the called location information according to the called identifier.
  • the calling name display service is associated with the CRBT service, and the calling name display service is indirectly triggered by the CRBT service request. Obviously, not all callers who call the CRBT service are usually called. The calling name display service is ordered. Therefore, it is possible to determine that the calling party has ordered the calling name display service before querying the calling information.
  • the CRBT service can be regarded as a basic service, and the calling name display service is regarded as its additional service.
  • the additional service ordered by the user or the other party can be realized. For example, if the calling party CRBT service ordered by the calling party is used as the basic service, the calling party needs to simultaneously subscribe the calling ring tone service and the calling name display service to implement the calling name display function, and the calling party's calling information at this time.
  • the called ring back tone service is used as the basic service
  • the called party needs to subscribe to the called color ring back ring service to implement the function of receiving the calling party information.
  • the calling party's calling information is on the same platform as the called user's ring tones information.
  • the CRBT service request sent by the calling or called end office is regarded as the confirmation that the called terminal has ringed, and therefore can be directly executed according to the service association.
  • the calling name shows the business.
  • An embodiment of the calling information service device for performing the method of the embodiment, with reference to FIG. 10, includes: a location query unit 301, configured to query location information of the called party according to the called identifier.
  • the service processing unit 302 includes a first service unit 3021 and a second service unit 3022.
  • the first service unit 3021 is configured to receive, by the calling end office, a first service request sent according to the service order information of the calling or called party after receiving the connection response returned by the called end office; or, receiving the called end office After the call request is sent to the called terminal, the first service request sent according to the service order information of the calling or called party; the first service request is carried with the identifier of the calling party and the called party;
  • the second service unit 3022 is configured to determine, after the calling user subscribes to the calling name display service, according to the identifier of the calling party carried in the first service request obtained by the first service unit 3021, and query the calling user setting according to the identity of the calling party.
  • the calling information is sent to the called party according to the location information of the called party detected by the location query unit 301 after the calling party's location information is queried.
  • the calling information service device in this embodiment may be implemented by using a device capable of providing a CRBT service, such as a CRBT platform, and adding a related function of the calling name display service on the basis of the existing CRBT platform, and triggering the combination of the two services.
  • the trigger mechanism of the CRBT service is a functional unit for processing the CRBT service
  • the second service unit is a functional unit for processing the calling name display service of the synchronous trigger.
  • the solution in this embodiment can ensure that the called party information is sent to the called terminal after the called terminal rings, so that the called user can accurately know the correspondence between the ringing call and the received calling party information;
  • the business function of the ring back tone platform is increased to implement and is convenient to implement.
  • the CRBT platform that displays the service function by adding the calling name is used as the calling information service device, and the called CRBT service mode triggered by the calling end office is adopted.
  • the call flow for implementing the calling name display service includes:
  • the calling MSC receives the calling name to display the call request sent by the service user, sends the SRI to the called HLR, obtains the called MSRN and the CRBT service code SS_CODE;
  • the calling MSC sends an IAM to the called MSC according to the called MSRN, and connects the call to the called MSC;
  • the called MSC sends a call request to the called MS; the called terminal starts ringing; c7, the called MSC sends an ACM message to the calling MSC;
  • the calling MSC temporarily suspends the connection with the called party, and sends the IAM to the ring back tone platform according to the called SS_CODE;
  • the CRBT platform sends an ACM message to the calling MSC; establishes a voice connection with the calling party, and plays a color ring tone to the calling party;
  • Cl0 ⁇ cll refer to all ⁇ al2, the ring back tone platform obtains the called MSC address and the called IMSI from the called HLR;
  • the ring back tone platform sends a flashing message Forward_SM carrying the calling information to the called MSC;
  • the called MSC sends a flash message carrying the calling information to the called terminal;
  • the called terminal displays the calling information, and continues to play the ringing tone;
  • the called MSC returns to the ring back tone platform Forward_SM response Forward_SM_Ack; cl5, the called user hears the ringing, sees the calling information, answers the incoming call, and returns a response to the called MSC;
  • the ring back tone platform returns to the calling MSC to the ANM; the calling MSC releases the voice channel between the ring back tone platform and the calling party, and connects the voice channel between the calling party and the called party, and the calling party and the called party start talking.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Description

实现主叫名显示业务的方法和主叫信息服务设备 技术领域
本发明涉及通信技术领域, 具体涉及实现主叫名显示 (Calling Name
Presentation , CNAP ) 业务的方法以及相应的主叫信息服务设备。 背景技术
主叫名显示业务又称主叫信息业务, 是一种增值业务。 它的主要功能是 当用户在作为主叫拨打被叫号码时,由业务系统将主叫用户设置的主叫信息, 例如主叫电子名片、 问候语等, 通过闪信的方式发送到被叫终端上, 使得被 叫用户可以直观的获得来电信息。 用户可按场景定制主叫信息, 例如可通过 设置个性化的过滤规则对不同被叫、 不同时段、 不同区域发送不同的主叫信 息。 所称闪信属于短消息中的一种, 终端在收到闪信后不必象传统短消息那 样需要用户通过操作按键来显示, 而是直接将其内容在屏幕上显示出来, 并 且通常不会在显示完成后进行内容的保存。
主叫名显示业务与来电显示业务不同。 来电显示是由交换系统将主叫号 码发送到被叫终端上, 由被叫终端直接显示号码, 或者显示终端所保存的号 码薄中与该号码对应的主叫用户姓名等信息; 如果被叫终端的号码薄中没有 记录与主叫号码对应的用户信息, 则被叫终端只能显示主叫号码, 并且, 若 被叫用户没有开通来电显示功能, 则甚至无法看到主叫号码。 而主叫名显示 业务则由主叫用户设置, 主叫用户在拨打被叫电话时, 业务系统能够将主叫 信息发送到被叫终端, 便于被叫识别来电者。
下面筒要介绍目前已有的一种实现主叫名显示业务的呼叫流程, 主要包 括步骤:
①主叫用户终端向交换系统发送呼叫请求。 ②交换系统判断该呼叫需要触发主叫名显示业务, 就向主叫信息服务器 发送主叫信息请求, 并且同时或者在收到主叫信息服务器返回的主叫信息后 进行到被叫用户终端的呼叫接续操作。
③主叫信息服务器中存储有主叫用户设置的主叫信息, 它根据交换系统 发送的主叫信息请求, 将相应的主叫信息通过闪信发送给被叫用户终端进行 显示。
在对现有技术的研究和实践过程中, 本发明的发明人发现, 上述能够实 现主叫名显示业务的呼叫流程中, 呼叫触发后, 主叫信息的发送操作与被叫 终端的接续操作是两个彼此独立的流程, 难以保证主叫信息在恰当的时机发 送到被叫终端上,在某些情况下不能起到方便被叫用户进行来话识别的作用。 例如, 若主叫信息在被叫振铃前发送到被叫终端, 而此时被叫正在接听另一 来话, 或另一来话正在振铃, 会给被叫用户带来误会; 又如, 若主叫信息在 主被叫双方开始通话后或通话结束后才发送到被叫终端, 则对被叫而言已失 去提前了解主叫信息的意义。 发明内容
本发明实施例提供能够在恰当的时机将主叫信息发送到被叫终端上的实 现主叫名显示业务的方法以及相应的主叫信息服务设备。
一种实现主叫名显示业务的方法, 包括: 接收交换系统发送的业务请求, 所述业务请求携带有主叫和被叫的标识; 根据所述主叫的标识查询主叫用户 设置的主叫信息, 根据所述被叫的标识查询被叫的位置信息; 在确定所述被 叫终端已振铃后, 按照所述被叫的位置信息将携带所述主叫信息的闪信发送 给所述被叫。
一种主叫信息服务设备, 包括: 位置查询单元, 用于根据被叫的标识查 询被叫的位置信息; 业务处理单元, 用于接收交换系统发送的业务请求, 所 述业务请求携带有主叫和被叫的标识; 根据所述主叫的标识查询主叫用户设 置的主叫信息; 在确定所述被叫终端已振铃后, 按照所述位置查询单元查到 的被叫的位置信息将携带所述主叫信息的闪信发送给所述被叫。
本发明实施例采用在确定被叫终端已振铃后, 再将携带主叫信息的闪信 发送给被叫的方法。 由于将对呼叫接续流程的状态判断与主叫名显示业务的 执行时机关联起来, 使得能够在恰当的时机将主叫信息发送到被叫终端上, 有利于被叫用户正确识别来话信息。 附图说明
图 1是本发明实施例的实现主叫名显示业务的方法的主要步骤示意图; 图 2是本发明实施例的主叫信息服务设备的基本逻辑结构示意图; 图 3是本发明实施例一实现主叫名显示业务的方法流程示意图; 图 4是与实施例一方法对应的主叫信息服务设备的逻辑结构示意图; 图 5是基于实施例一的一个具体信令流程示意图;
图 6是本发明实施例二实现主叫名显示业务的方法流程示意图; 图 7是与实施例二方法对应的主叫信息服务设备的逻辑结构示意图; 图 8是基于实施例二的一个具体信令流程示意图;
图 9是本发明实施例三实现主叫名显示业务的方法流程示意图; 图 10是与实施例三方法对应的主叫信息服务设备的逻辑结构示意图; 图 11是基于实施例三的一个具体信令流程示意图。 具体实施方式
本发明实施例的实现主叫名显示业务的方法, 参考图 1 , 主要包括步骤: Stepl、 接收交换系统发送的业务请求, 所称业务请求携带有主叫和被叫 的标识。
所称交换系统指为主、 被叫用户提供通信服务的网络系统; 包括主、 被 叫端局的交换设备, 例如移动业务交换中心( MSC: Mobile Service Switching Center ), 业务交换点(SSP: Service Switching Piont )等, 以及提供相关数据 服务的设备, 例如拜访位置寄存器(VLR: Visitor Location Register ), 归属位 置寄存器(HLR: Home Location Register )等。
所称业务请求是在呼叫过程中根据某方用户的业务定购信息触发的请 求, 它可以是对主叫名显示业务的请求, 也可以是对其他业务的请求。 在后 一情况下, 该"其他业务"与主叫名显示业务关联, 能够通过对该业务的请求 触发主叫名显示业务的执行。
Step2、 根据主叫的标识查询主叫用户设置的主叫信息, 根据被叫的标识 查询被叫的位置信息。
此步骤中的两个操作用于获得主叫信息发送所需要的数据, 其执行没有 严格的时机限制, 可在获得主、 被叫的标识后, 在进行主叫信息发送前的任 意时间安排执行, 与 Step3 中的限制相比, 该两个操作安排在确定被叫终端 已振铃之前或之后均可。 此外, 所执行的"查询被叫的位置信息 "可以是专属 于主叫名显示业务流程的操作, 也可是其他业务执行流程中的操作, 只要其 查询的结果能够在发送主叫信息时被使用即可。
Step3、 在确定被叫终端已振铃后, 按照被叫的位置信息将携带主叫信息 的闪信发送给被叫。
主叫信息的发送时机基于对呼叫接续流程当前执行状态的判断, 可根据 实际系统以及具体呼叫流程的特点设计不同的判断方式, 包括但不限于如下 几种:
①基于对呼叫接续流程执行时间的合理预估, 例如采用定时器控制的方 法;
②主动对呼叫接续流程的执行状态进行监控, 例如根据交换系统的能力 配置基本呼叫状态 (BCSM: Basic Call State Machine )事件上报的方法; ③根据呼叫接续流程中指示当前呼叫接续状态的消息进行判断, 此方式 需要主叫信息服务设备直接参与呼叫接续流程; ④利用现有流程中隐含说明当前呼叫接续状态的消息进行被动触发, 例 如将主叫名显示业务与现有通常在被叫终端振铃后才会执行的其他业务相关 联, 将该业务的触发视为被叫终端已振铃的确认, 无需主动进行呼叫接续状 态的判断, 直接根据业务关联执行主叫名显示业务。
用于执行上述方法的本发明实施例的主叫信息服务设备, 参考图 2, 主 要包括:
位置查询单元 001 , 用于 ^据被叫的标识查询被叫的位置信息; 业务处理单元 002, 用于接收交换系统发送的业务请求, 该业务请求携 带有主叫和被叫的标识; 根据主叫的标识查询主叫用户设置的主叫信息; 在 确定被叫终端已振铃后, 按照位置查询单元 001查到的被叫的位置信息将携 带主叫信息的闪信发送给被叫。
基于不同的具体业务实现流程, 上述主叫信息服务设备可通过对智能网 业务控制设备( SCP: Service Control Point ),或 SCP与智能外设( IP: Intelligent Peripheral ) 的组合, 或其他业务的运营设备的改造来实现。
下面基于具体的实施例分别对上述方法和装置进行详细说明。
实施例一、 一种实现主叫名显示业务的方法, 参考图 3, 包括步骤:
Al、 接收主叫端局根据主叫的签约信息发送的主叫信息请求, 所称主叫 信息请求携带有主叫和被叫的标识。
本实施例中, 主叫信息请求为对主叫名显示业务的请求, 由交换系统中 的主叫端局发起。 该请求发起方式可参照移动网络增强逻辑的客户化应用 ( CAMEL: Customized Applications for Mobile network Enhanced Logic )业务 的请求发起方式执行, 即在呼叫触发后, 由主叫端局根据 HLR提供的主叫用 户的签约信息 (0-CSI: Originating CAMEL Subscription Information ), 获知 主叫用户定购有主叫名显示业务, 从而触发主叫信息请求。
A2、 根据主叫的标识查询主叫用户设置的主叫信息, 根据被叫的标识查 询被叫的位置信息。 可通过查询所保存的业务数据库获得主叫用户设置的主叫信息。
可通过向被叫归属的 HLR发起短信路由信息请求(SRI_for_SM: Send Routing Information for Short Message )查询被叫的位置信息。
A3、 在确定被叫终端已振铃后, 按照被叫的位置信息将携带主叫信息的 闪信发送给被叫。
基于主叫端局的能力, 可采用以下两种不同的确认判断方式:
①若主叫端局不支持上报振铃事件 (例如主叫端局仅支持 CAMEL 1 ~ 3 ), 则可在收到主叫端局发送的主叫信息请求后, 设置延迟定时, 在定时到 期后确定被叫终端已振铃。 延迟时间的具体值 n可根据应用网络的情况通过 实验来确定, 建议为 3 ~ 10秒。
②若主叫端局支持上报振铃事件(例如主叫端局支持 CAMEL 4 ), 则可 在收到主叫端局发送的主叫信息请求后, 向主叫端局发送上报被叫振铃事件 的请求; 在收到主叫端局上报的被叫振铃事件后, 确定被叫终端已振铃。
为进一步确保业务的有效执行, 除了设置上述确认判断条件, 此外还可 以设置业务终止的判断条件, 使得在某些情况下, 主叫名显示业务可不必继 续执行, 避免网络资源的浪费。 例如:
A31、 在收到主叫端局发送的主叫信息请求后, 向主叫端局发送上报主 叫挂机和 /或被叫应答事件的请求。
若对被叫终端振铃的确认判断也采用事件上报的方法, 则本步骤的请求 可与上报被叫振铃事件的请求一同发送。
这种情况下, 确定被叫终端已振铃的判断还需要包括: 在收到主叫端局 上报的主叫挂机或被叫应答事件后, 结束主叫信息业务处理。 当然, 若对被 叫终端振铃的确认判断采用延迟定时的方法, 则上述业务终止判断可与定时 判断综合进行, 即: 判断在定时时间内是否收到主叫端局上报的主叫挂机或 被叫应答事件, 若是, 则结束主叫信息业务处理; 若否, 则在定时到期后确 定被叫终端已振铃。 用于执行本实施例方法的主叫信息服务设备的实施例, 参考图 4, 包括: 位置查询单元 101 , 用于 ^据被叫的标识查询被叫的位置信息。
业务处理单元 102, 包括处理子单元 1021和控制子单元 1022。
处理子单元 1021 , 用于接收主叫端局根据主叫的签约信息发送的主叫信 息请求, 该主叫信息请求携带有主叫和被叫的标识; 根据主叫的标识查询主 叫用户设置的主叫信息; 根据控制子单元 1022 的指示, 按照位置查询单元 101查到的被叫的位置信息将携带主叫信息的闪信发送给被叫;
若基于事件上报方式来确认被叫终端振铃, 则处理子单元 1021还用于, 在收到主叫端局发送的主叫信息请求后, 向主叫端局发送上报被叫振铃事件 的请求;
此外, 为进一步提供主叫名显示业务的终止判断能力, 处理子单元 1021 还可用于, 在收到主叫端局发送的主叫信息请求后, 向主叫端局发送上报主 叫挂机和 /或被叫应答事件的请求。
控制子单元 1022, 用于在处理子单元 1021收到主叫信息请求后, 执行 对被叫终端振铃的确认判断, 具体功能可以是下述两种之一:
①设置延迟定时,在定时到期后指示处理子单元 1021发送携带主叫信息 的闪信。 以及进一步的, 判断在定时时间内是否收到主叫端局上报的主叫挂 机或被叫应答事件, 若是, 则结束主叫信息业务处理。
②在收到主叫端局上报的被叫振铃事件后,指示处理子单元 1021发送携 带主叫信息的闪信。 以及进一步的, 在收到主叫端局上报的主叫挂机或被叫 应答事件后, 结束主叫信息业务处理。
本实施例的主叫信息服务设备可采用 SCP来实现, 此时, 主叫名显示业 务可由主叫端局根据 0-CSI采用初始检测点( IDP: Initial Detect Point )消息 触发到 SCP; 各种事件的上报要求可由 SCP采用上报 BCSM事件 ( RRBE: Request Report BCSM Event )请求配置到主叫端局;被叫的位置信息可由 SCP 向被叫归属的 HLR发起 SRI_for_SM获得。 本实施例方案能保证在被叫终端振铃后, 被叫用户接听前(和 /或主叫用 户挂机前)将主叫信息发送到被叫终端, 使得被叫用户能够准确获知正在振 铃的呼叫与收到的主叫信息的对应关系, 便于被叫用户提前了解主叫信息。
为更好的理解上述实施例, 下面给出本实施例方案应用于具体呼叫流程 中的一个示例。 在该示例中, 采用 SCP作为主叫信息服务设备, 主叫端局 ( MSC/VLR/SSP ) 支持 CAMEL 2, SCP采用延迟定时的方式执行对被叫终 端振铃的确认判断。 参考图 5, 该实现主叫名显示业务的呼叫流程包括: al、 主叫 MSC/VLR/SSP收到主叫名显示业务用户发出的呼叫请求, 根 据主叫用户的 0-CSI触发业务, 向主叫归属 SCP发送 IDP消息;
a2、 主叫归属 SCP 查询出主叫用户设置的主叫信息, 向主叫
MSC/VLR/SSP发送 RRBE消息, 配置主叫挂机、 被叫应答事件;
a3、主叫归属 SCP向主叫 MSC/VLR/SSP发送 Continue或 Connect消息, 指示继续进行呼叫接续, 并开始延迟定时 n秒; 在这 n秒期间, 如果主叫端 局上报主叫挂机、 被叫应答事件, 则 SCP结束主叫信息业务处理;
a4、主叫 MSC/VLR/SSP向被叫归属 HLR发送路由信息请求( SRI: Send
Routing Information ) 查询被叫的动态漫游号码 ( MSRN: Mobile Station Roaming Number );
a5、被叫归属 HLR向被叫 MSC/VLR/SSP发送漫游码请求( PRN: Provide Roaming Number )查询被叫的 MSRN;
a6、 被叫 MSC/VLR/SSP向被叫归属 HLR回 PRN应答 PRN_ack, 携带 被叫的 MSRN;
a7、 被叫归属 HLR向主叫 MSC/VLR/SSP回 SRI应答 SRI_ack, 携带被 叫的 MSRN;
a8、 主叫 MSC/VLR/SSP根据被叫的 MSRN向被叫 MSC/VLR/SSP发送 初始地址消息 ( IAM: Initial Address Message ) , 将呼叫接续到被叫 MSC/VLR/SSP; a9、 被叫 MSC/VLR/SSP向被叫终端 (MS: Mobile Station )发送呼叫请 求; 被叫终端开始振铃;
al0、 被叫 MSC/VLR/SSP向主叫 MSC/VLR/SSP发送地址全(ACM: Address Complete Message ) 消息;
al 1、 n秒的延迟定时到达, 主叫归属 SCP向被叫 HLR发送 SRI_for_SM 消息;
al2、 被叫 HLR向主叫归属 SCP回 SRI_for_SM应答 SRI_for_SM_Ack, 携带被叫的位置信息,其中包括被叫 MSC地址和被叫用户的国际移动电话用 户识别码 ( IMSI: International Mobile Subscriber Identity )等;
al3、主叫归属 SCP向被叫 MSC发送携带主叫信息的闪信 Forward_SM; al4、 被叫 MSC将携带主叫信息的闪信发送到被叫终端; 被叫终端显示 主叫信息, 并继续播放振铃音;
al5、被叫 MSC向主叫归属 SCP回 Forward_SM应答 Forward_SM_Ack; al6、 被叫用户听到振铃, 看到主叫信息, 接听来话, 向被叫 MSC返回 应答;
al7、 被叫 MSC向主叫 MSC回应答消息(ANM: ANswer message ), 主 被叫双方开始通话。
实施例二、 一种实现主叫名显示业务的方法, 本实施例与实施例一的区 别在于本实施例中主叫信息服务设备直接参与呼叫接续流程, 根据呼叫接续 流程中指示当前呼叫接续状态的消息进行被叫终端已振铃的判断。 流程参考 图 6, 包括步骤:
Bl、 接收主叫端局根据主叫的签约信息发送的主叫信息请求, 所称主叫 信息请求携带有主叫和被叫的标识。
此步骤可参照实施例一步骤 A1执行。
B2、 在收到主叫端局发送的主叫信息请求后, 向主叫端局发送呼叫路由 请求。 此步骤中, 主叫信息服务设备通知主叫端局将呼叫路由到自身, 由主叫 信息服务设备来执行后续的呼叫接续操作。 若基于 SCP来实现主叫信息服务 设备, 可在 SCP下发给主叫端局的 Connect消息中在被叫号码前加入特定的 接入码, 主叫端局即可根据该接入码将呼叫路由到主叫信息服务设备。
B3、 接收主叫端局根据呼叫路由请求路由过来的呼叫, 向被叫端局发送 呼叫接续请求, 接收被叫端局返回的接续响应。
此步骤可参照通常的呼叫接续过程来执行。 由于在执行呼叫接续的过程 中, 需要查询被叫归属的 HLR获得被叫的相关地址信息, 被叫归属的 HLR 返回的响应中除了 MSRN以外, 通常还包含有发送短信所需要的 IMSI和被 叫 MSC地址( VMSC- Address )参数, 因此可使用该过程获得的地址信息用 于后续携带主叫信息的闪信的发送。 当然, 若通过专门执行的请求过程来查 询被叫的位置信息也是可以的。
B4、 根据主叫的标识查询主叫用户设置的主叫信息。
此步骤可在收到主叫信息请求后, 在闪信发送之前的任意时间执行。 B5、 在收到被叫端局返回的接续响应后, 确定被叫终端已振铃, 按照被 叫的位置信息将携带主叫信息的闪信发送给被叫。
当然, 作为呼叫接续操作的执行者, 主叫信息服务设备在收到被叫端局 返回的接续响应后还可按照通常的接续处理流程为主叫方播放回铃音, 如果 被叫设置了彩铃, 则连接彩铃平台为主叫方播放彩铃。
由于本实施例中主叫信息服务设备直接参与呼叫接续的流程, 可以不必 通过请求主叫端局上报 BCSM事件来关注呼叫的状态, 因此主叫信息服务设 备可在向主叫端局下发呼叫路由请求后结束与主叫端局之间的会话。 当然, 若主叫信息服务设备仍要求主叫端局上报 BCSM事件也是可以的, 相关过程 与实施例一类似, 不再赘述。
用于执行本实施例方法的主叫信息服务设备的实施例, 参考图 7, 包括: 位置查询单元 201 , 用于 ^据被叫的标识查询被叫的位置信息。 接续处理单元 203, 用于接收主叫端局根据呼叫路由请求路由过来的呼 叫; 向被叫端局发送呼叫接续请求; 接收被叫端局返回的接续响应。
业务处理单元 202, 包括处理子单元 2021和控制子单元 2022。
处理子单元 2021 , 用于接收主叫端局根据主叫的签约信息发送的主叫信 息请求, 该主叫信息请求携带有主叫和被叫的标识; 在收到主叫端局发送的 主叫信息请求后, 向主叫端局发送呼叫路由请求; 根据主叫的标识查询主叫 用户设置的主叫信息; 根据控制子单元 2022的指示, 按照位置查询单元 201 查到的被叫的位置信息将携带主叫信息的闪信发送给被叫;
此外, 为进一步提供主叫名显示业务的终止判断能力, 处理子单元 2021 还可用于, 在收到主叫端局发送的主叫信息请求后, 向主叫端局发送上报主 叫挂机和 /或被叫应答事件的请求。
控制子单元 2022, 用于在确定接续处理单元 203收到被叫端局返回的接 续响应后, 指示处理子单元 2021发送携带主叫信息的闪信。 以及进一步的, 在收到主叫端局上报的主叫挂机或被叫应答事件后,结束主叫信息业务处理。
本实施例的主叫信息服务设备可采用通过接口互相连接的 SCP和 IP的组 合来实现, 由 IP提供呼叫接续功能。 此时, 业务处理单元 202设置于 SCP, 而位置查询单元 201和接续处理单元 203设置于 IP。 为闪信发送提供被叫位 置信息的位置查询单元 201可以是为接续处理单元 203的接续过程提供被叫 地址查询功能的逻辑单元,此时,接续处理单元 203是根据位置查询单元 201 查到的被叫的位置信息向被叫端局发送呼叫接续请求。
本实施例方案能保证在被叫终端振铃后, 被叫用户接听前(和 /或主叫用 户挂机前)将主叫信息发送到被叫终端, 使得被叫用户能够准确获知正在振 铃的呼叫与收到的主叫信息的对应关系, 便于被叫用户提前了解主叫信息。
为更好的理解上述实施例, 下面给出本实施例方案应用于具体呼叫流程 中的一个示例。 在该示例中, 采用 SCP + IP作为主叫信息服务设备。 参考图 8, 该实现主叫名显示业务的呼叫流程包括: bl、 主叫 MSC/VLR/SSP收到主叫名显示业务用户发出的呼叫请求, 根 据主叫用户的 0-CSI触发业务, 向主叫归属 SCP发送 IDP消息;
b2、 主叫归属 SCP 查询出主叫用户设置的主叫信息, 向主叫 MSC/VLR/SSP发送 RRBE消息, 配置主叫挂机、被叫应答事件(本步骤可省 略);
b3、 主叫归属 SCP向主叫 MSC/VLR/SSP发送 Connect消息, 被叫号码 前携带特定的路由码, 指示主叫 MSC将呼叫路由到 IP;
b4、主叫 MSC根据被叫号码前的路由码将呼叫路由到主叫信息服务设备 中的 IP;
b5 ~ b8、 参照 a4 ~ a7, 主叫信息服务设备中的 IP获取被叫的 MSRN以 及 IMSI和 VMSC- Address;
b9、 主叫信息服务设备根据被叫的 MSRN 向被叫 MSC/VLR/SSP发送 IAM, 将呼叫接续到被叫 MSC/VLR/SSP;
bl0、被叫 MSC/VLR/SSP向被叫 MS发送呼叫请求;被叫终端开始振铃; bll、 被叫 MSC/VLR/SSP向主叫信息服务设备发送 ACM消息; bl2、 主叫信息服务设备中的 IP向主叫 MSC发送 ACM消息, 并向主叫 播放回铃音;
bl3、主叫信息服务设备中的 SCP向被叫 MSC发送携带主叫信息的闪信 Forward_SM; 闪信发送所使用的 IMSI和 VMSC-Address可以从步骤 b8中接 收的 SRI_ack中获得, 通过 IP与 SCP之间的接口传递给 SCP;
bl4、 被叫 MSC将携带主叫信息的闪信发送到被叫终端; 被叫终端显示 主叫信息, 并继续播放振铃音;
bl5、 被叫 MSC 向主叫信息服务设备中的 SCP 回 Forward_SM应答 Forward_SM_Ack;
bl6、 被叫用户听到振铃, 看到主叫信息, 接听来话, 向被叫 MSC返回 应答; bl7、 被叫 MSC向主叫信息服务设备中的 IP回 ANM;
bl8、 主叫信息服务设备中的 IP向主叫 MSC回 ANM; 主被叫双方开始 通话。
实施例三、 一种实现主叫名显示业务的方法, 本实施例与实施例一和二 的区别在于本实施例中将主叫名显示业务与第一业务相关联, 根据第一业务 的触发时机本身所具有的特点,将该业务的触发视为被叫终端已振铃的确认。 流程参考图 9, 包括步骤:
Cl、 接收主叫端局在收到被叫端局返回的接续响应后, 根据主叫或被叫 的业务定购信息发送的第一业务请求; 或者, 接收被叫端局在向被叫终端发 送呼叫请求后, 根据主叫或被叫的业务定购信息发送的第一业务请求, 所称 第一业务请求携带有主叫和被叫的标识。
所称第一业务请求为对具有特定触发时机的第一业务的请求。 所称第一 业务可在主叫端局收到被叫端局返回的接续响应后由主叫端局触发, 也可在 被叫端局向被叫终端发送呼叫请求后由被叫端局触发。
本实施例中选择彩铃业务作为第一业务, 相应的第一业务请求为彩铃业 务请求。 本实施例所称彩铃业务可以采用主叫彩铃或被叫彩铃等不同的定购 形式, 其触发也可以由主叫端局或被叫端局进行, 其具体业务执行模式可根 据应用需要从现有众多可行方案中进行选择, 本实施例不作限定。 例如, 可 采用由主叫端局触发的被叫彩铃业务模式, 即, 主叫端局在收到被叫端局返 回的接续响应后, 根据从被叫归属的 HLR 获得的被叫业务代码 (彩铃 SS_CODE ), 触发彩铃业务请求。
C2、 在根据第一业务请求携带的主叫的标识确定主叫用户定购了主叫名 显示业务后, 查询主叫用户设置的主叫信息; 根据被叫的标识查询被叫的位 置信息。
本实施例中将主叫名显示业务与彩铃业务相关联, 通过彩铃业务请求间 接触发主叫名显示业务。 显然, 通常并非所有触发彩铃业务的呼叫的主叫方 都定购了主叫名显示业务, 因此, 可在查询主叫信息前先确定主叫已定购主 叫名显示业务。
基于彩铃业务与主叫名显示业务的关联关系, 可将彩铃业务视为基础业 务, 将主叫名显示业务视为其附加业务。 在呼叫过程中, 一方用户需要定购 有基础业务, 己方或另一方用户定购的附加业务才能实现。 例如, 若以主叫 定购的主叫彩铃业务作为基础业务, 则主叫需要同时定购主叫彩铃业务和主 叫名显示业务来实现主叫名显示的功能, 此时主叫用户的主叫信息与彩铃信 息在同一平台; 若以被叫定购的被叫彩铃业务作为基础业务, 则当主叫定购 有主叫名显示业务时, 被叫需要订购被叫彩铃业务来实现接收主叫信息的功 能, 此时主叫用户的主叫信息与被叫用户的彩铃信息在同一平台。
C3、 按照被叫的位置信息将携带主叫信息的闪信发送给被叫。
基于彩铃业务本身具有的触发时机上的特点, 本实施例中以收到主叫或 被叫端局发送的彩铃业务请求视为对被叫终端已振铃的确认, 因此可根据业 务关联直接执行主叫名显示业务。
用于执行本实施例方法的主叫信息服务设备的实施例,参考图 10, 包括: 位置查询单元 301 , 用于 ^据被叫的标识查询被叫的位置信息。
业务处理单元 302, 包括第一业务单元 3021和第二业务单元 3022;
第一业务单元 3021 , 用于接收主叫端局在收到被叫端局返回的接续响应 后, 根据主叫或被叫的业务定购信息发送的第一业务请求; 或者, 接收被叫 端局在向被叫终端发送呼叫请求后, 根据主叫或被叫的业务定购信息发送的 第一业务请求; 所称第一业务请求携带有主叫和被叫的标识;
第二业务单元 3022, 用于在根据第一业务单元 3021获得的第一业务请 求携带的主叫的标识确定主叫用户定购了主叫名显示业务后, 根据主叫的标 识查询主叫用户设置的主叫信息; 在查询到主叫用户设置的主叫信息后, 按 照位置查询单元 301查到的被叫的位置信息将携带主叫信息的闪信发送给被 叫。 本实施例的主叫信息服务设备可采用能够提供彩铃业务的设备, 例如彩 铃平台来实现, 在现有彩铃平台的基础上增加主叫名显示业务的相关功能即 可, 两项业务的触发合用彩铃业务的触发机制。 此时第一业务单元即为处理 彩铃业务的功能单元, 第二业务单元即为处理同步触发的主叫名显示业务的 功能单元。
本实施例方案能保证在被叫终端振铃后将主叫信息发送到被叫终端, 使 得被叫用户能够准确获知正在振铃的呼叫与收到的主叫信息的对应关系; 并 且可基于现有彩铃平台的业务功能增加来执行, 实现方便。
为更好的理解上述实施例, 下面给出本实施例方案应用于具体呼叫流程 中的一个示例。 在该示例中, 以增加主叫名显示业务功能的彩铃平台作为主 叫信息服务设备, 采用由主叫端局触发的被叫彩铃业务模式。 参考图 11 , 该 实现主叫名显示业务的呼叫流程包括:
cl ~ c4、参考 a4 ~ a7,主叫 MSC收到主叫名显示业务用户发出的呼叫请 求, 向被叫归属的 HLR发送 SRI, 获得被叫的 MSRN 以及彩铃业务代码 SS—CODE;
c5、主叫 MSC根据被叫的 MSRN向被叫 MSC发送 IAM,将呼叫接续到 被叫 MSC;
c6、 被叫 MSC向被叫 MS发送呼叫请求; 被叫终端开始振铃; c7、 被叫 MSC向主叫 MSC发送 ACM消息;
c8、 主叫 MSC暂时挂起与被叫侧的话路连接, 根据被叫的 SS_CODE向 彩铃平台发送 IAM;
c9、 彩铃平台向主叫 MSC发送 ACM消息; 建立与主叫之间的话路连接 向主叫播放彩铃;
cl0 ~ cll、 参考 all ~ al2, 彩铃平台向被叫 HLR获取被叫 MSC地址和 被叫的 IMSI;
cl2、 彩铃平台向被叫 MSC发送携带主叫信息的闪信 Forward_SM; cl3、 被叫 MSC将携带主叫信息的闪信发送到被叫终端; 被叫终端显示 主叫信息, 并继续播放振铃音;
cl4、 被叫 MSC向彩铃平台回 Forward_SM应答 Forward_SM_Ack; cl5、 被叫用户听到振铃, 看到主叫信息, 接听来话, 向被叫 MSC返回 应答;
cl6、 被叫 MSC向彩铃平台回 ANM;
cl7、 彩铃平台向主叫 MSC回 ANM; 主叫 MSC释放彩铃平台与主叫之 间的话路, 接通主被叫之间的话路, 主被叫双方开始通话。
以上对本发明实施例所提供的实现主叫名显示业务的方法以及相应的主 叫信息服务设备进行了详细介绍, 本文中应用了具体个例对本发明的原理及 实施方式进行了阐述, 以上实施例的说明只是用于帮助理解本发明的方法及 其核心思想; 同时, 对于本领域的一般技术人员, 依据本发明的思想, 在具 体实施方式及应用范围上均会有改变之处, 综上所述, 本说明书内容不应理 解为对本发明的限制。

Claims

权 利 要 求
1、 一种实现主叫名显示业务的方法, 其特征在于, 包括:
接收交换系统发送的业务请求,所述业务请求携带有主叫和被叫的标识; 根据所述主叫的标识查询主叫用户设置的主叫信息, 根据所述被叫的标 识查询被叫的位置信息;
在确定所述被叫终端已振铃后, 按照所述被叫的位置信息将携带所述主 叫信息的闪信发送给所述被叫。
2、 根据权利要求 1所述的实现主叫名显示业务的方法, 其特征在于: 所述接收交换系统发送的业务请求的步骤具体为: 接收主叫端局根据主 叫的签约信息发送的主叫信息请求。
3、 根据权利要求 2所述的实现主叫名显示业务的方法, 其特征在于: 所述确定被叫终端已振铃的判断方法包括:在收到所述主叫信息请求后, 设置延迟定时, 在定时到期后确定被叫终端已振铃。
4、 根据权利要求 3所述的实现主叫名显示业务的方法, 其特征在于, 在 收到主叫端局发送的主叫信息请求后, 还包括: 向主叫端局发送上报主叫挂 机和 /或被叫应答事件的请求;
所述确定被叫终端已振铃的判断方法还包括: 判断在定时时间内是否收 到主叫端局上报的主叫挂机或被叫应答事件, 若是, 则结束主叫信息业务处 理; 若否, 则在定时到期后确定被叫终端已振铃。
5、 根据权利要求 2所述的实现主叫名显示业务的方法, 其特征在于: 在 收到主叫端局发送的主叫信息请求后, 还包括: 向主叫端局发送上报主叫挂 机和被叫应答及被叫振铃事件的请求, 或者, 向主叫端局发送上报主叫挂机 和被叫振铃事件的请求, 或者, 向主叫端局发送上报被叫应答和被叫振铃事 件的请求;
所述确定被叫终端已振铃的判断方法包括: 在收到主叫端局上报的主叫 挂机或被叫应答事件后, 结束主叫信息业务处理; 在收到主叫端局上报的被 叫振铃事件后, 确定被叫终端已振铃。
6、 根据权利要求 2所述的实现主叫名显示业务的方法, 其特征在于: 在 收到主叫端局发送的主叫信息请求后, 还包括: 向主叫端局发送呼叫路由请 求; 接收主叫端局根据所述呼叫路由请求路由过来的呼叫; 向被叫端局发送 呼叫接续请求; 接收被叫端局返回的接续响应;
所述确定被叫终端已振铃的判断方法包括: 在收到被叫端局返回的接续 响应后, 确定被叫终端已振铃。
7、 根据权利要求 1所述的实现主叫名显示业务的方法, 其特征在于: 所述接收交换系统发送的业务请求的步骤具体为: 接收主叫端局在收到 被叫端局返回的接续响应后, 根据主叫或被叫的业务定购信息发送的第一业 务请求; 或者, 接收被叫端局在向被叫终端发送呼叫请求后, 根据主叫或被 叫的业务定购信息发送的第一业务请求;
在所述根据主叫的标识查询主叫用户设置的主叫信息之前还包括: 根据 所述主叫的标识确定所述主叫用户定购了主叫名显示业务;
所述确定被叫终端已振铃的判断方法包括: 在收到主叫或被叫端局发送 的第一业务请求后, 确定被叫终端已振铃。
8、 根据权利要求 7所述的实现主叫名显示业务的方法, 其特征在于: 所 述第一业务请求为彩铃业务请求。
9、 一种主叫信息服务设备, 其特征在于, 包括:
位置查询单元, 用于根据被叫的标识查询被叫的位置信息;
业务处理单元, 用于接收交换系统发送的业务请求, 所述业务请求携带 有主叫和被叫的标识; 根据所述主叫的标识查询主叫用户设置的主叫信息; 在确定所述被叫终端已振铃后, 按照所述位置查询单元查到的被叫的位置信 息将携带所述主叫信息的闪信发送给所述被叫。
10、 根据权利要求 9所述的主叫信息服务设备, 其特征在于: 所述业务 处理单元包括处理子单元和控制子单元;
所述处理子单元, 用于接收主叫端局根据主叫的签约信息发送的主叫信 息请求, 所述主叫信息请求携带有主叫和被叫的标识; 根据所述主叫的标识 查询主叫用户设置的主叫信息; 根据所述控制子单元的指示, 按照所述位置 查询单元查到的被叫的位置信息将携带所述主叫信息的闪信发送给所述被 叫;
所述控制子单元, 用于在所述处理子单元收到主叫信息请求后, 设置延 迟定时, 在定时到期后指示所述处理子单元发送所述携带主叫信息的闪信。
11、 根据权利要求 10所述的主叫信息服务设备, 其特征在于: 所述处理 子单元还用于, 在收到主叫端局发送的主叫信息请求后, 向主叫端局发送上 报主叫挂机和 /或被叫应答事件的请求;
所述控制子单元还用于, 判断在定时时间内是否收到主叫端局上报的主 叫挂机或被叫应答事件, 若是, 则结束主叫信息业务处理; 若否, 则在定时 到期后指示所述处理子单元发送所述携带主叫信息的闪信。
12、 根据权利要求 9所述的主叫信息服务设备, 其特征在于: 所述业务 处理单元包括处理子单元和控制子单元;
所述处理子单元, 用于接收主叫端局根据主叫的签约信息发送的主叫信 息请求, 所述主叫信息请求携带有主叫和被叫的标识; 在收到主叫端局发送 的主叫信息请求后, 向主叫端局发送上报主叫挂机和 /或被叫应答事件、 以及 被叫振铃事件的请求; 根据所述主叫的标识查询主叫用户设置的主叫信息; 根据所述控制子单元的指示, 按照所述位置查询单元查到的被叫的位置信息 将携带所述主叫信息的闪信发送给所述被叫;
所述控制子单元, 用于在收到主叫端局上报的主叫挂机或被叫应答事件 后, 结束主叫信息业务处理; 在收到主叫端局上报的被叫振铃事件后, 指示 所述处理子单元发送所述携带主叫信息的闪信。
13、 根据权利要求 9所述的主叫信息服务设备, 其特征在于, 还包括: 接续处理单元, 用于接收主叫端局根据呼叫路由请求路由过来的呼叫; 向被叫端局发送呼叫接续请求; 接收被叫端局返回的接续响应;
所述业务处理单元包括处理子单元和控制子单元;
所述处理子单元, 用于接收主叫端局根据主叫的签约信息发送的主叫信 息请求, 所述主叫信息请求携带有主叫和被叫的标识; 在收到主叫端局发送 的主叫信息请求后, 向主叫端局发送呼叫路由请求; 根据所述主叫的标识查 询主叫用户设置的主叫信息; 根据所述控制子单元的指示, 按照所述位置查 询单元查到的被叫的位置信息将携带所述主叫信息的闪信发送给所述被叫; 所述控制子单元, 用于在确定所述接续处理单元收到被叫端局返回的接 续响应后, 指示所述处理子单元发送所述携带主叫信息的闪信。
14、 根据权利要求 13所述的主叫信息服务设备, 其特征在于: 所述主叫 信息服务设备包括通过接口互相连接的智能网业务控制设备和智能外设; 所 述业务处理单元设置于所述智能网业务控制设备; 所述位置查询单元和接续 处理单元设置于所述智能外设, 所述接续处理单元是根据所述位置查询单元 查到的被叫的位置信息向被叫端局发送呼叫接续请求。
15、 根据权利要求 9所述的主叫信息服务设备, 其特征在于: 所述业务 处理单元包括第一业务单元和第二业务单元;
第一业务单元, 用于接收主叫端局在收到被叫端局返回的接续响应后, 根据主叫或被叫的业务定购信息发送的第一业务请求; 或者, 接收被叫端局 在向被叫终端发送呼叫请求后, 根据主叫或被叫的业务定购信息发送的第一 业务请求; 所述第一业务请求携带有主叫和被叫的标识;
第二业务单元, 用于在根据所述第一业务请求携带的主叫的标识确定所 述主叫用户定购了主叫名显示业务后, 根据所述主叫的标识查询主叫用户设 置的主叫信息; 在查询到所述主叫用户设置的主叫信息后, 按照所述位置查 询单元查到的被叫的位置信息将携带所述主叫信息的闪信发送给所述被叫。
16、 根据权利要求 15所述的主叫信息服务设备, 其特征在于: 所述主叫 信息服务设备为能够提供彩铃业务的设备, 所述第一业务请求为彩铃业务请 求。
PCT/CN2008/070896 2007-11-16 2008-05-07 Procédé pour réaliser un service de présentation du nom de l'appelant et dispositif de service d'informations relatives à l'appelant WO2009062403A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
BRPI0806227-7A BRPI0806227A2 (pt) 2007-11-16 2008-05-07 método e aparelho para a implementação do serviço de cnap
EP08169098.4A EP2061222B1 (en) 2007-11-16 2008-11-14 Method and apparatus for implementing the CNAP service
ZA2009/03839A ZA200903839B (en) 2007-11-16 2009-06-02 A method for realizinng the caller name presentation service and a caller information service device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007101883115A CN101437089B (zh) 2007-11-16 2007-11-16 实现主叫名显示业务的方法和主叫信息服务设备
CN200710188311.5 2007-11-16

Publications (1)

Publication Number Publication Date
WO2009062403A1 true WO2009062403A1 (fr) 2009-05-22

Family

ID=40638329

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070896 WO2009062403A1 (fr) 2007-11-16 2008-05-07 Procédé pour réaliser un service de présentation du nom de l'appelant et dispositif de service d'informations relatives à l'appelant

Country Status (5)

Country Link
US (1) US8571531B2 (zh)
CN (1) CN101437089B (zh)
BR (1) BRPI0806227A2 (zh)
WO (1) WO2009062403A1 (zh)
ZA (1) ZA200903839B (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102088698A (zh) * 2010-12-24 2011-06-08 中国联合网络通信集团有限公司 呼叫方法和系统、呼叫码生成器、呼叫控制器和msc

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101437089B (zh) 2007-11-16 2013-01-02 华为技术有限公司 实现主叫名显示业务的方法和主叫信息服务设备
US8977242B1 (en) * 2009-04-06 2015-03-10 Wendell Brown Method and apparatus for content presentation in association with a telephone call
CN101702793B (zh) * 2009-11-10 2013-08-21 中兴通讯股份有限公司 Cdma网络中ussd业务的实现方法、系统及设备
US9444854B2 (en) 2010-09-07 2016-09-13 T-Mobile Usa, Inc. Session initiation protocol (SIP) router
CN102625258A (zh) * 2011-01-26 2012-08-01 广州晨扬通信技术有限公司 一种智能网方式实现通话后信息推送的方法和系统
CN102158821A (zh) * 2011-02-25 2011-08-17 中兴通讯股份有限公司 一种主叫用户向被叫用户发送信息的方法及系统
EP3216199B1 (en) 2014-11-03 2021-04-07 Telia Company AB Provision of caller information
CN104469744A (zh) * 2014-11-21 2015-03-25 百度在线网络技术(北京)有限公司 通信终端的通话处理方法、通话信息处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1549560A (zh) * 2003-05-10 2004-11-24 华为技术有限公司 一种pstn网络中固网短信终端显示主叫用户信息的方法
KR20060020115A (ko) * 2004-08-31 2006-03-06 햄펙스 주식회사 무선단말기의 플래시 메시지 서비스 방법
CN1798203A (zh) * 2004-12-20 2006-07-05 华为技术有限公司 主叫名显示业务的实现方法
CN1798207A (zh) * 2004-12-21 2006-07-05 华为技术有限公司 一种在被叫用户终端上显示主叫信息的方法
CN1980289A (zh) * 2006-11-03 2007-06-13 北京恒信彩虹信息技术有限公司 一种由主叫方向被叫方主动推送来电显示信息的方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5604797A (en) * 1995-12-19 1997-02-18 Adcock; Stanley J. Ring-tone muting device and processing method
US5883943A (en) 1997-11-06 1999-03-16 Ericsson Inc. Calling party name delivery to digital phone subscriber
US20070047523A1 (en) 2001-08-16 2007-03-01 Roamware, Inc. Method and system for call-setup triggered push content
FI20010929A (fi) * 2001-05-04 2002-11-05 Sonera Oyj Tietoliikenneverkko ja menetelmä soittajan tietojen välittämiseksi
CN100440906C (zh) * 2003-04-30 2008-12-03 华为技术有限公司 主叫名显示业务中号码信息的存储与查询方法
WO2006052083A1 (en) * 2004-11-09 2006-05-18 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks
CN100583746C (zh) 2004-12-29 2010-01-20 美国博通公司 用于生成安全密钥的方法和系统
CN101437089B (zh) 2007-11-16 2013-01-02 华为技术有限公司 实现主叫名显示业务的方法和主叫信息服务设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1549560A (zh) * 2003-05-10 2004-11-24 华为技术有限公司 一种pstn网络中固网短信终端显示主叫用户信息的方法
KR20060020115A (ko) * 2004-08-31 2006-03-06 햄펙스 주식회사 무선단말기의 플래시 메시지 서비스 방법
CN1798203A (zh) * 2004-12-20 2006-07-05 华为技术有限公司 主叫名显示业务的实现方法
CN1798207A (zh) * 2004-12-21 2006-07-05 华为技术有限公司 一种在被叫用户终端上显示主叫信息的方法
CN1980289A (zh) * 2006-11-03 2007-06-13 北京恒信彩虹信息技术有限公司 一种由主叫方向被叫方主动推送来电显示信息的方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102088698A (zh) * 2010-12-24 2011-06-08 中国联合网络通信集团有限公司 呼叫方法和系统、呼叫码生成器、呼叫控制器和msc
CN102088698B (zh) * 2010-12-24 2013-09-04 中国联合网络通信集团有限公司 呼叫方法和系统、呼叫码生成器、呼叫控制器和msc

Also Published As

Publication number Publication date
US8571531B2 (en) 2013-10-29
US20090129578A1 (en) 2009-05-21
CN101437089A (zh) 2009-05-20
CN101437089B (zh) 2013-01-02
ZA200903839B (en) 2016-09-28
BRPI0806227A2 (pt) 2011-09-06

Similar Documents

Publication Publication Date Title
WO2009062403A1 (fr) Procédé pour réaliser un service de présentation du nom de l'appelant et dispositif de service d'informations relatives à l'appelant
KR100632007B1 (ko) 멀티미디어 링백톤 대체음 제공 방법
US8131265B2 (en) System and method for implementing multimedia ring back tone service
JP5486055B2 (ja) テレビ電話のための呼出方法およびシステム
WO2008119272A1 (fr) Procédé, terminal et système de mise en oeuvre d'une liaison vidéo dans un réseau de communication vocale
US8442211B2 (en) Method and system for providing a ring back tone in a communication network
WO2009146616A1 (zh) 一种实现主叫信息显示业务的方法及信息服务器
KR20040102834A (ko) 통화 연결음 서비스 방법
WO2009059501A1 (fr) Procédé, système et dispositif de transfert automatique d'appel
WO2010108425A1 (zh) 提供ip语音交换机业务的方法及装置
WO2008138187A1 (fr) Procédé de réalisation pour un appel de nouvelle réponse
WO2006128360A1 (fr) Procede et systeme pour realiser un signal de rappel base sur un central telephonique mobile de groupe
CN100471208C (zh) 在卡号业务中主叫用户重新发起呼叫的方法
KR20020036262A (ko) 이동 통신 교환 시스템 발신 단말에서의 착신 응답 표시방법
WO2010066174A1 (zh) 非跨接彩振通信的方法、终端及系统
KR100712681B1 (ko) 멀티미디어 데이터 서비스 방법 및 이를 수행하기 위한시스템
KR100608282B1 (ko) 화상전화 시도시 제공되는 멀티미디어 서비스 방법
CN101009729B (zh) 一种实现码分多址网络彩铃业务的方法
KR100908355B1 (ko) 이동통신망의 통화중 호 처리 방법
KR100335994B1 (ko) 차세대 지능망에서 유선 전화를 이용하여 개인용 컴퓨터를호출하는 폰투피시 지능망 서비스 제공 방법
KR100577919B1 (ko) 전화 발신 중 링백톤 대체음을 이용하여 다른 부가서비스의 음원을 설정하는 방법 및 장치
JP4225259B2 (ja) キャリア選択処理方法、発信処理方法、およびip電話装置
KR100470545B1 (ko) 통신단말기를 이용한 화상정보 제공 장치 및 그 방법
EP2061222B1 (en) Method and apparatus for implementing the CNAP service
KR100630636B1 (ko) 비동기 방식의 이동통신 시스템에서의 통화연결음 서비스방법

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2239/KOLNP/2009

Country of ref document: IN

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

Ref document number: 08734251

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: PI0806227

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20090616