KR100783265B1 - System for providing calling information with multimedia message in wireless telecommunication network - Google Patents

Abstract

A system for offering call origination information as a multimedia message in a wireless communication network is provided to deliver the call origination information as the multimedia message if a call attempt for a receiving subscriber by a sending subscriber is not established, and to obtain service attribute information of the receiving subscriber. If catch call data is generated when a call is not established though a sending subscriber attempts to call a receiving subscriber, an HLR(Home Location Register)(20) transmits catch call generation trigger information. If the catch call generation trigger information is received, a CCS(Catch Call Service) server(40) generates a multimedia message which combines media data with catch call text, and demands transmission of the message. An LMSC(Long Message Service Center)(60) receives the demand to send the message to a terminated MSC(Mobile Switching Center)(25).

Description

System for Providing Calling Information with Multimedia Message in Wireless Telecommunication Network}

1 is a block diagram showing the overall configuration of a wireless network implemented system for providing call origination information in a multimedia message according to the present invention.

2 is a flowchart of a catch call data call processing process according to the first embodiment of the present invention.

3 is a flow chart of catch call data call processing according to a second embodiment of the present invention.

4 is a flowchart of a catch call data call processing process according to a third embodiment of the present invention;

The present invention relates to a system for providing call origination information in a wireless communication network, and more particularly, to a system for providing call origination information in a multimedia form.

The catch call service provided by the Applicant is a catch call subscriber's telephone that is unreachable (e.g., when the telephone is powered off, the telephone is in a shaded area, or is busy or unanswered). If incomplete call data (i.e., catch call data) occurs because the call attempt for this subscriber is not completed, the caller of the past (information of catch call data) is sent to the short message service (when the subscriber's telephone becomes available later). SMS: A service that allows you to check through Short Message Service. This catch call service is performed in four cases.

(1) If Call Forwarding Unconditional (CFU), Voice Mail Unconditional (VMU), and Do Not Disturb (DND) services are enabled for the called party,

(2) when the state of the telephone terminal of the called subscriber is power off,

(3) if the called party is busy

(4) The called party did not answer the phone or left the coverage.

As described above, a technique of transmitting incomplete call data to a called subscriber in a short message has been described in various conventional documents.

For example, Patent No. 10-0374964 No. 10-0374964, registered on February 21, 2003, has a separate system for processing incomplete call data and has a separate system for processing incomplete call data. It determines whether the short message can be received and transmits the incomplete call data to the short message service center only when the short message can be received. In addition, Japanese Patent Laid-Open No. 6-165247, published on June 10, 1994, targets an incoming call to an incoming call to a mobile terminal when the mobile terminal is outside the service area of the base station or when the mobile terminal is turned off. Notifying the caller of the inability to answer the mobile terminal, and storing the caller's telephone number and incoming time in a memory means, and when the mobile terminal returns to the available state, the caller's telephone number and incoming time are sent to the mobile terminal as a short message. A method of notifying is disclosed.

In the conventional incomplete call notification system or method, since the information of the calling subscriber is delivered only in the form of a short message, the message to be transmitted is monotonous and the format is uniform.

It is an object of the present invention to provide a system for transmitting call origination information in a multimedia message when a call attempt by a calling subscriber to a called subscriber is not established.

According to an embodiment of the present invention, a system for providing call origination information as a multimedia message includes (A) when the calling subscriber attempts to make a call to the called subscriber but fails to establish a call, the catch call data is transmitted to catch call generation trigger information. A home location register (HLR), and (B) a catch call service server for generating a multimedia message fused with media data to the catch call text and requesting transmission thereof, when the catch call generation trigger information is received from the HLR; ) A long message service center (LMSC) which receives a request for transmission of a multimedia message and transmits it to a destination exchange.

According to another embodiment of the present invention, a system for providing call origination information as a multimedia message includes (A) a call call generation trigger information when catch call data is generated because a call is not established but a call is made by a calling party. A home location register (HLR) for transmitting, (B) a catch call service server requesting transmission of a catch call message when the catch call generation trigger information is received from the HLR, and (C) a catch call message from the catch call service server. A multimedia service center (MMSC) that receives a request for transmission and generates a multimedia message fused with media data to catch-call text, and (D) a long message service center (LMSC) that receives a request for transmission of a multimedia message and transmits it to a destination exchange. Include.

The multimedia message includes catch call text and media data, which is composed of one or a combination of pictures, video, voice, and audio data. The catch call text includes, for example, the telephone number of the calling party, the time when the calling party tried to make a call, a phrase indicating that incomplete call data occurred.

Embodiment

Hereinafter, specific embodiments of the present invention will be described with reference to the accompanying drawings.

1 is a block diagram showing the overall configuration of a wireless network that implements a call origination information providing system according to the present invention.

As shown in FIG. 1, the wireless network is a network for communication between the calling subscriber 10 and the called subscriber 30, and includes an originating mobile switching center (OMSC) and a home location register 20 (HLR: Home Location). Register), terminating MS (25, tMSC: terminating MSC), SS7 network (35, Signaling System No. 7 Network), catch call service server 40, IP network 45, customer service and billing center (50, CS : Customer Service and Billing System (CRM) and Customer Relation Management (65). In the first embodiment of the present invention, in addition to these components, the multimedia message service center 55 (MMSC: Multimedia Message Service Center) and the long message service center (LMSC: 60) are further included in the wireless network. In the second embodiment of the present invention, the MMSC 55, the LMSC 60, and the content provider 70 (CP: Contents Provider) are further included in the wireless network. In the third embodiment of the present invention, the LMSC 60, content The provider 70 and the provider attribute providing server 80 (FNPS: Flexible Number Portability Server) are further included in the wireless network.

If the calling subscriber 10 attempts to make a call to the called subscriber 30, but the call fails to be established and catch call data is generated in the four cases described above, the HLR 20 triggers catch call generation information. To the catch call service server 40 through the SS7 network (40). The catch call service server 40 processes the catch call service call in conjunction with the HLR 20, tMSC 25, CS 50, MMSC 55, LMSC 60, and CRM 65 (first) Implementation), in conjunction with the HLR (20), tMSC (25), CS (50), MMSC (55), LMSC (60), CRM (65), CP (70) to handle the call call service ( 2 implementation), the catch call service call processing in conjunction with the HLR (20), tMSC (25), CS (50), LMSC (60), CRM (65), CP (70), FNPS (80) ( Third embodiment). Here, the "catchcall service call processing" refers to the MAP (Mobile Application Part) message (ie, "information directive") triggered from the HLR 20, MMSC (55), LMSC (60), In conjunction with the CRM (65), CP (70), FNPS (80) and the like to provide a call origination information to the called party 30 and the subscriber 30 to check the call origination information through the CRM (65) Means a procedure.

The catch call service server 40 includes the HLR 20, oMSC 15, tMSC 25, CS 50, MMSC 55, LMSC 60, CRM 65, CP 70, and FNPS ( 80) and a separate system. The catch call service server 40 notifies the called party 30 of the call origination information as a multimedia message (multi mail), and transmits the occurrence information of the catch call and the history information on the processing result to the CRM 65. The subscriber profile managed by the catch call service server 40 for the catch call service includes, for example, a terminal identification number (MSID), the subscriber's telephone number (MDN), whether the catch call service is activated, the subscriber's registration time, and the latest catch call message. It may include data such as an occurrence time, a recent catch call message generation telephone number, and the like. The reason why the latest catch call message occurrence time data is managed is that the catch call message is generated only for the first catch call data or the latest catch call data without transmitting the catch call message every time when multiple consecutive catch call data are generated from the same sender. It is to eliminate the inconvenience that the called party receives the successive catch call message by sending a.

In FIG. 1, the HLR 20 may include 2G-HLR for CDMA network subscribers and 3G-HLR for WCDMA network subscribers. 2G stands for "second generation" and 3G stands for "third generation". The CS 50 registers, inquires, changes, and deletes the catch call subscriber information to the CCS 40. The CRM 65 receives the call call generation information received from the CCS 40 and history information on the processing result. Is provided to the called party in a web environment and / or a WAP environment.

The catch call service server 40 (CS) is an interface for delivering SS7 messages to an application program, a controller that manages the entire catch call service call processing scenario, and formats and transmits and receives an interworking message with the MMSC 55 for catch call text data processing. Process of formatting and transmitting and receiving a CRM 65 interworking message, managing a subscriber profile, formatting and sending and receiving an interworking message with the CS 50, a process in charge of retransmission of a message that fails to interwork with the CRM 65, Performs database access control process and operator command (MML) necessary to determine whether to store the last catch call data during catch call call and transmit the last catch call data generated within a certain time to MMSC 55. Interface process, CCS system performance, failures, statistics, status, configuration, etc. Operational management processes, operator interfaces, etc. can be included as internal components.

According to an embodiment of the present invention, the CCS 40 may include a module for generating a multimedia message in which media data such as an image is fused to the catch call text. 2 and 3 illustrate that the multimedia message is generated by the CCS 40 as an example, it is also possible for the MMSC 55 to generate the multimedia message without the CCS 40. In the following description, the technology and method for generating a multimedia message by the MMSC 55 is the same as the technology for generating a multimedia message by the multimedia message generating module of the CCS 40.

The MMSC 55 generates a multimedia message (multi mail) which combines catch call text with media data such as pictures, videos, speech, and audio. In order to generate such a multimedia message, the MMSC 55 collects and combines multimedia data from the client server or collects and combines multimedia data from the CP 70. The MMSC 55 may use the TCP / IP protocol to collect multimedia data.

The multimedia message generated by the MMSC 55 is a format in which the elements constituting the message are combined, for example, the Multipurpose Internet Mail Extensions (MIME) multipart format defined in RFC 2046, an Internet Engineering Task Force (IETF) standard document. format is a single MM (Multimedia Message) format. The text included in the multimedia message may be a character encoding that includes a subset of Unicode logical characters (eg, US-ASCII, ISO-8859-1, UTF-8, GSM 7-bit default alphabet, Shift_JIS, etc.). ) Can be used. On the other hand, the voice data is data that supports the 3GPP2 13K or Adaptive Multi-Rate (AMR) codec, the audio data is audio data that supports MPEG-4 Advanced Audio Coding (AAC), or SD-MIDI (Scalable Polyphony Musical Instrument Digital Interface) ) Content format is synthetic audio data supported, and picture data includes still image (JPEG) and bitmap image (GIF) data.

In addition to the data listed above, visual data, notification and acknowledgment data may be included in the multimedia message, and media synchronization and presentation procedures may be used to generate a multimedia message.

In the present invention, since the multimedia message is transmitted to the receiving subscriber 30 through the MMSC 55, the receiving subscriber 30 preferably includes a telephone supporting a multimedia message service (MMS) client.

The LMSC 60 is a connection interface system for the switching network using the SS7 network. The LMSC 60 receives the multi-mail generated in the MMSC 55 and transmits it to the switching center 25 of the subscriber 30.

The FNPS 80 has a database of 2G service subscribers, 3G service subscribers, and number portable service subscribers. When performing call processing, the switching network queries the FNPS 80 to determine the attributes of the called subscriber.

2 is a flowchart of a catch call data call processing process according to the first embodiment of the present invention.

The originating exchange 15 receiving the originating call of the originating subscriber 10 sends the Location Request message of the called party, which is the target of the originating call, to the HLR 20 of the called party, and the HLR 20 sends to the destination exchange. Routing Request message is sent, and returning receipt message (routing request_ack, location request_ack) is returned. When the HLR 20 has information indicating that the called party is inactive, the HLR 20 sends a catch call request message (Information Directive) to the CCS 40.

On the other hand, when the HLR 20 does not have information indicating that the called subscriber is inactive, the originating exchange 15 sends an initial address message to the called exchange 25, and the called exchange 25 Paging the called subscriber 30. If there is no response from the called subscriber as a result of the call, the destination switching center 25 sends an Address Complete Message (Address Complete Message) to the calling switching station 15, and sends a TTNR (Transfer To Number Request) message to the HLR 20. Then, the HLR 20 sends a catch call request message (Information Directive) to the CCS 40.

The catch call request message sent by the HLR 20 to the CCS 40 includes a calling party number string corresponding to the MSID (Mobile Station Identifier) of the called party, the Mobile Directory Number (MDN) of the called party, and the telephone number of the calling party. 1) or an electronic serial number (ESN) of the calling subscriber.

Upon receiving the catch call request message from the HLR 20, the CCS 40 creates a multimedia message and delivers it to the MMSC 55. When the CCS 40 requests the catch call multimail to the MMSC 55, a destination address, an originating address, a callback number, a multimedia message including the catch call text, a message identifier assigned by the CCS, and a status Send data such as report indicators.

The catch call multi-mail is requested to be sent to the destination exchange station 25 via the MMSC 55 and the LMSC 60, and the destination exchange station 25 transmits the multi-mail to the destination subscriber 30.

3 is a flowchart of a catch call data call processing process according to a second embodiment of the present invention.

In FIG. 3, the source switching center 15 transmits the location request message of the called party, which is the target of the originating call, to the HLR 20 of the called party, and the step of sending the catch call request message to the CCS 40 by the HLR 20. Since it is the same as the flowchart of FIG. 2, a detailed description thereof will be omitted.

Receiving a catch call request message from the HLR 20, the CCS 40 requests the CP 70 for image data to be combined with the catch call text, and the image data received from the CP 70 with the catch call text according to the request. Combine to generate catch-call multimail and request MMSC 55 for its transmission. The catch call multi-mail is requested to be sent to the destination exchange station 25 via the MMSC 55 and the LMSC 60, and the destination exchange station 25 transmits the multi-mail to the destination subscriber 30.

4 is a flowchart of a catch call data call processing process according to a third embodiment of the present invention.

In FIG. 4, when the originating switching center 15 transmits the location request message of the called party, which is the target of the originating call, to the HLR 20 of the called party, the step of sending the catch call request message to the CCS 40 by the HLR 20. Since it is the same as the flowchart of FIG. 2, a detailed description thereof will be omitted.

Receiving a catch call request message from the HLR 20, the CCS 40 requests the CP 70 for image data to be combined with the catch call text, and the image data received from the CP 70 with the catch call text according to the request. Combine to generate catch-call multimail. The CCS 40 then requests the FNPS 80 for attribute information of the called subscriber. As described above, the FNPS 80 has 2G subscriber information, 3G subscriber information, and number portable subscriber information, and provides the subscriber attribute information to the CCS 40. The CCS 40 may distinguish a 2G / 3G subscriber from an IMSI (International Mobile Subscriber Identity) value received from the FNPS 80 and a number portable subscriber from a ported value.

Receiving the attribute response of the called subscriber from the FNPS 80, the CCS 40 combines the image with the catch call text to generate a catch call mail. The generated call-call multi-mail is requested to be sent to the destination exchange station 25 via the MMSC 55 and the LMSC 60, and the destination exchange station 25 transmits the multi-mail to the destination subscriber 30.

Although specific embodiments of the present invention have been described with reference to the drawings, this is intended to be easily understood by those skilled in the art and is not intended to limit the technical scope of the present invention. Therefore, the technical scope of the present invention is determined by the matters described in the claims, and the embodiments described with reference to the drawings may be modified or modified as much as possible within the technical spirit and scope of the present invention.

According to the present invention, call origination information may be delivered in a multimedia message when a call attempt for a called party does not hold. In addition, the service attribute information of the called subscriber can be obtained.

Claims (10)

A system for providing call origination information in a multimedia message, A home location register (HLR) that transmits catch call generation trigger information when the calling subscriber attempts to call the called subscriber but the call is not established and the catch call data is generated; A catch call service server for generating a multimedia message in which media data is fused to catch call text and requesting transmission thereof, when the catch call generation trigger information is received from the HLR; And a long message service center (LMSC) for receiving the request for transmission of the multimedia message and transmitting it to a destination exchange. A system for providing call origination information in a multimedia message, A home location register (HLR) that transmits catch call generation trigger information when the calling subscriber attempts to call the called subscriber but the call is not established and the catch call data is generated; A catch call service server for requesting transmission of a catch call message when the catch call generation trigger information is received from the HLR; A multimedia service center (MMSC) for receiving a request for transmission of a catch call message from the catch call service server and generating a multimedia message in which media data is fused to catch call text; And a long message service center (LMSC) for receiving the request for transmission of the multimedia message and transmitting it to a destination exchange. The method of claim 1 or 2, And the media data is any one selected from picture data, video data, voice data, and audio data, or a combination thereof. The method of claim 1 or 2, And the media data is media data provided by a called subscriber. The method of claim 1 or 2, The media data is a call originating information providing system, characterized in that the media data provided by the content providing unit (CP). In claim 1, The catch call service server receives the media data from the content providing unit (CP) to generate the multimedia message, and receives the property information of the called subscriber from the provider property providing server (FNPS) to distinguish the called subscriber. Call origination information providing system. delete In claim 3, Call delivery information providing system, characterized in that the multimedia message further comprises visual data or notification and acceptance data. The method of claim 1 or 2, wherein the catch call service server, Call origination information providing system, characterized in that for providing a history management information on the transmission result of the multimedia message to a customer management device (CRM). The method of claim 1 or 2, And the message requested by the catch call service server includes a called address, a calling address, a callback number, a message identifier, and a status report indicator data.

Images