KR20060028028A - Method for providing short messages service - Google Patents

Abstract

The present invention relates to a method for providing a short message service for processing a short message based on a user setting in a communication system, particularly in an asynchronous next-generation mobile communication system, wherein a called subscriber registers an incoming form of a short message in a short message service center. Accordingly, the short message service center presetting the incoming call format for the called subscriber, and when the short message to be delivered to the called subscriber is received, processing the short message into the preset incoming call format; It comprises the step of transmitting a short message of the incoming call type to the called subscriber, to provide a more convenient and improved short message service to the subscriber.

Short Message, Short Message Service (SMS) Center

Description

How to provide short message service {method for providing short messages service}

1 is a diagram illustrating a network configuration for a general short message service (SMS).

2 is a diagram illustrating a processing procedure of an outgoing short message according to the prior art.

3 is a diagram illustrating a processing procedure of an incoming short message according to the prior art;

Fig. 4 is a diagram showing the procedure of creating a message when the recipient's e-mail address is entered.

5 is a diagram illustrating a message writing procedure when a telephone number of a called party's mobile communication terminal is input.

6 illustrates an SMS command (SMS-COMMAND) message format.

7 is a diagram illustrating a short message service providing procedure according to an embodiment of the present invention.

The present invention relates to a method for providing a short message service for processing a short message based on user setting in a communication system, particularly in an asynchronous next generation mobile communication system.                         

In the current technology, short messages can be written and sent in short text in plain text and e-mail.

On the other hand, when the calling party transmits the short message in the plain text format, the called party receives the short message in the plain text format.

In addition, when the calling subscriber sends a short message in an e-mail format, the called subscriber can check the short message only in an e-mail format. That is, when the calling subscriber transmits the short message in the e-mail format, the called subscriber can check the contents of the incoming short message only through the e-mail client.

A wideband code division multiple access (W-CDMA) system, which is one of the next generation mobile communication systems, has a network configuration for short message processing as shown in FIG.

1 is a diagram illustrating a network configuration for a general short message service (hereinafter, abbreviated as SMS).

Referring to FIG. 1, user equipments (hereinafter, referred to as UEs) 1 and 2 are mobile communication terminals (eg, mobile stations) that support short message transmission and reception functions.

Node-B 2 is a base station (eg, a base station) that supports SMS to multiple UEs 1, 2.

The radio network controller (hereinafter, abbreviated as RNC) 3 is a base station controller (eg, a base station controller) that provides a connection and coordination function for a base station.

Mobile Switching Center (hereinafter referred to as MSC) 5 is a system in charge of circuit switching service, and a Serving GPRS Support Node (hereinafter referred to as SGSN) 6 is a packet. It is a system in charge of exchange service.

The Home Location Register (hereinafter referred to as HLR) 7 is a database that manages subscriber information and device information for mobile subscribers.

The SMS center 8 is a server that performs a function of storing and delivering a short message.

The operation according to the above network configuration will be described below.

Short messages originating from certain UEs 1, 2 are delivered to MSC / SGSN 5, 6 via Node-B 3 and RNC 4.

The MSC / SGSN (5, 6) forwards the outgoing short message to the SMS center 8 in which the outgoing subscriber is registered.

The SMS center 8 obtains the location information of the called subscriber from the HLR 7 to deliver the received outgoing short message to the called subscriber. Thus, the SMS center 8 obtains the address information of the called MSC / SGSN where the called subscriber is located from the HLR 7 and transmits an outgoing short message to the called MSC / SGSN.

The called MSC / SGSN performs paging to the called subscriber. When receiving a response from the called subscriber, the received short message is transmitted to the called UE.

2 is a diagram illustrating a processing procedure of an outgoing short message according to the prior art.

Referring to Figure 2, the calling subscriber enters the recipient's telephone number to send in plain text format after writing the short message, and enter the recipient's email address to send in the e-mail format.

After entering either of the two formats described above, the originating subscriber presses the "send" button of the originating UE.

The originating UE 10 then establishes a Radio Resource Control (RRC) connection with the RNC 12 (S1).

The originating UE 10 then sends an Initial Direct Transfer message to the RNC 12 (S2).

The RNC 12 then forwards an Initial UE (Initial UE) message to the MSC / SGSN 13, 14 to establish an interface with the MSC / SGSN 13, 14 (S3). In this case, the RNC 12 carries a CM Service Request message in an initial UE message to an MSC, and sends a service request message to an initial UE message in an SGSN. Pass it on.

The MSC / SGSN 13, 14 then delivers a direct transfer message to the RNC 12 (S4). In this case, the MSC 13 carries a CM Service Accept message in a direct transfer message to the RNC 12, and the SGSN 14 directly delivers a Service Accept message. It is delivered to the RNC 12 in a (Direct Transfer) message.

Next, the RNC 12 transmits a downlink direct transfer message to the UE 10 (S5).                         

In response thereto, the UE 10 transmits an Uplink Direct Transfer message including the created short message to the RNC 12 (S6).

The RNC 12 then sends a direct delivery message including the short messages CP-DATA and RP-DATA delivered from the UE 10 to the MSC / SGSN 13, 14 (S7). In the above description, "CP-DATA" is control protocol data, and "RP-DATA" is relay protocol data.

The MSC / SGSN 13, 14 then sends a direct delivery message to the RNC 12 including a response message (CP-ACK) for short message (CP-DATA, RP-DATA) reception (S8). The RNC 12 transmits a downlink direct transfer message to the UE 10 (S9).

On the other hand, the MSC / SGSN 13, 14 obtains the address information of the SMS center 15 included in the short message CP-DATA received from the RNC 12, and the " MO- FORWARD-SHORT-MESSAGE "is transmitted (S10). Then, when the SMS center 15 normally receives the "MO-FORWARD-SHORT-MESSAGE", the SMS center 15 sends the message to the MSC / SGSN (13, 14) which sent the message using the "MO-FORWARD-SHORT-MESSAGE-ACK". Answer (S11).

Subsequently, the MSC / SGSN (13, 14) is a direct delivery message including a response message (CP-DATA, RP-ACK) to the short message (CP-DATA, RP-DATA) received from the RNC (12) Is transmitted to the RNC 12 (S12).

Subsequently, the RNC 12 transmits a downlink direct transfer message to the UE 10 (S13), and the UE 10 transmits an uplink direct transfer message to the RNC 12 (S14).

Receiving an uplink direct transfer message from the UE 10, the RNC 12 sends a response message (CP-ACK) to a response message (CP-DATA, RP-ACK) received from the MSC / SGSN (13, 14). The direct transfer message is transmitted to the MSC / SGSN 13 and 14 (S15).

When the above procedures are completed, the MSC / SGSN 13 and 14 transmits a release command message to the RNC 12 for releasing an interface with the RNC 12 (S16).

Accordingly, the RNC 12 performs an RRC connection release procedure with the UE 10 (S17).

When the RRC connection with the UE 10 is released, the RNC 12 sends a Release Complete message to the MSC / SGSN 13, 14 indicating that the interface with the MSC / SGSN 13, 14 has been released. (S18).

3 is a diagram illustrating a processing procedure of an incoming short message according to the prior art.

Referring to Fig. 3, the SMS center 25 first receives "MO-FORWARD-SHORT-MESSAGE" from the calling MSC / SGSN (13, 14 of Fig. 2) as described above and then sends them to the "MO- Reply with "FOR-ARD-SHORT-MESSAGE-ACK".

If the short message delivered through "MO-FORWARD-SHORT-MESSAGE" is analyzed and the message is in an e-mail format and is displayed in an e-mail format, the SMS center 25 sends an e-mail. The short message received by the server 27 is transmitted. This is not shown in FIG. 3.

On the other hand, if the short message delivered through "MO-FORWARD-SHORT-MESSAGE" is in plain text format and is expressed in plain text format, the SMS center 25 may display the MSC / SGSN (23) where the called subscriber is located. Requests the HLR 26 address information. To this end, the SMS center 25 transmits a "SEND-ROUTING-INFO-FOR-SMS" message to the HLR 26 (S20).

The HLR 26 responds to the SMS center 25 with the address information of the MSC / SGSN 23 and 24 where the called subscriber is located in the message “SEND-ROUTING-INFO-FOR-SMS-ACK” (S21).

The SMS center 25 transmits "MT-FORWARD-SHORT-MESSAGE" to the corresponding MSC / SGSN 23, 24 which has received the address information from the HLR 26 (S22). Here, the "MT-FORWARD-SHORT-MESSAGE" includes a short message received in the aforementioned "MO-FORWARD-SHORT-MESSAGE".

Accordingly, the MSC / SGSN 23 and 24 transmit a paging message to the RNC 22 (S23). The RNC 22 transmits a call message to the destination UE 20 again (S24).

The receiving UE 20 receiving the call message establishes an RRC connection with the RNC 22 (S25).

The terminating UE 10 then sends an Initial Direct Transfer message to the RNC 22 (S26).

The RNC 22 then forwards an Initial UE message to the MSC / SGSN 23, 24 (S27). In this case, the RNC 22 transfers a paging response to the MSC 23 in an initial UE message, and the SGSN 24 transmits a service request message to the initial UE. ) Deliver it in a message.

The MSC / SGSN 23, 24 then delivers a direct transfer message to the RNC 22 (S28). Here, the MSC / SGSN 23, 24 transmits a direct delivery message including the short messages CP-DATA and RP-DATA transmitted from the SMS center 25 to the RNC 22.

Accordingly, the RNC 22 transmits a downlink direct transfer message to the UE 20 (S29), and the UE 20 sends an uplink direct transfer message to the RNC 22. Transmit (S30).

Receiving an Uplink Direct Transfer message from the UE 20, the RNC 22 sends a direct transfer message including a response message (CP-ACK) to the short message (CP-DATA, RP-DATA). Transmit to MSC / SGSN 23,24 (S31).

The UE 20 again transmits an Uplink Direct Transfer message to the RNC 22 (S32). Accordingly, the RNC 22 includes a direct delivery message including a response message (CP-DATA, RP-ACK) to the short message (CP-DATA, RP-DATA) received from the MSC / SGSN (23, 24). Is transmitted to the MSC / SGSN (23, 24) (S33).

The MSC / SGSN 23 and 24 transmit a direct transfer message to the RNC 22 including a response message (CP-ACK) to the response messages CP-DATA and RP-ACK received from the RNC 22. (S34).

Thereafter, the RNC 22 transmits a downlink direct transfer message to the UE 20 (S35). On the other hand, the MSC / SGSN 23, 24 sends the message “MT-FORWARD-SHORT-MESSAGE-ACK” to the SMS center 25 in response to the “MT-FORWARD-SHORT-MESSAGE” received from the SMS center 25. (S36).

When the above procedures are completed, the destination MSC / SGSN 23, 24 transmits a release command message to the RNC 22 to release the interface with the RNC 22 (S37).

Accordingly, the RNC 22 performs an RRC connection release procedure with the destination UE 20 (S38).

When the RRC connection with the UE 20 is released, the RNC 22 sends a Release Complete message to the MSC / SGSN 23, 24 indicating that the interface with the MSC / SGSN 23, 24 has been released. (S39).

In the above-described prior art, when the called party receives the short message, the called party can receive the message only in the form of the short message prepared by the calling party. That is, when the calling subscriber composes and sends a short message in the plain text format, the called party receives the short message only in the plain text format. Similarly, when the calling subscriber composes and sends a short message in an e-mail format, the called subscriber receives a short message only in the e-mail format. As described above, in the related art, a process of preparing a short message to transmitting / receiving is very monotonous, thereby providing a system-oriented service in which subscriber convenience is excluded.

In addition, in the prior art, it is inconvenient for the subscriber to use different input interfaces to compose short messages in a plain text format or an email format. For example, the program environment for writing short messages in plain text is different from the program environment for writing short messages in e-mail.

Disclosure of Invention An object of the present invention is to provide a method for providing a short message service which allows the processing of an incoming call of a short message based on a setting of a called user in a next generation mobile communication system.

Another object of the present invention is to provide a short message service providing method for receiving a short message in a predetermined email account as well as a mobile communication terminal number, and checking a short message even in an email account.

Another object of the present invention is to eliminate the operation of distinguishing the form of the short message, and also to the subscriber to receive all the short message that is received by the recipient in the form of the recipient set in advance in the SMS center subscribers To provide a more convenient and improved way to provide a short message service.

A first feature of the present invention for achieving the above object is that, as the incoming subscriber registers the incoming form for the short message to the short message service center, the short message service center is to receive the incoming form for the called subscriber. Setting a preset message; if a short message to be delivered to the called subscriber is received, processing the short message into the preset called format; and transmitting the processed short message to the called subscriber; It is done by.

More preferably, a short message service command message (SMS-COMMAND) is used for registration of the incoming format. More specifically, the terminating type is registered by using a reserved bit of a Transfer Protocol-Command-Type field defined in the short message service command message (SMS-COMMAND). In more detail, the incoming format includes a reception format and a presentation format, wherein the reception format is at least one of reception to a mobile communication terminal number and reception to an e-mail address, and the presentation format. Is at least one of a plain text format and an e-mail format. Here, the short message service center sets the reception format and the presentation format according to the registration of the incoming format in the control area of the database of the called party. In more detail, the control area includes fields for setting the communication terminal number of the called subscriber, the address of the MSC registered with the called subscriber, the SGSN address, and the HLR address, respectively, and a terminal for setting the expression format. And a terminating message handling (TMH) field, and the control area further includes a field for setting an e-mail address of the called party so as to set a reception format to the e-mail address among the reception formats. do.

On the other hand, the application for registration of the incoming form is provided in the terminal of the called subscriber. Accordingly, when the called subscriber requests registration of the incoming type through the application, the registration requested information is inserted into the short message service command message (SMS-COMMAND) and transmitted to the short message service center, and the short message is received. The message service center registers the called subscriber according to the information inserted in the short message service command message (SMS-COMMAND).

More preferably, the processing of the short message checks whether the sending format of the short message is the same as the incoming format, and when the outgoing format is different from the incoming format, the short message is registered by the called subscriber. Convert to incoming format. Wherein the short message service center searches for information registered by the called subscriber when the calling format is a format for transmitting to a mobile communication terminal number and the called format is for receiving with an e-mail address. The e-mail address corresponding to the called party's mobile communication terminal number inserted in the short message is confirmed, and then the short message is transmitted to an e-mail server for transmitting to the confirmed e-mail address. In addition, when the calling format is a format for transmitting to an e-mail address and the called format is a format for receiving with a mobile communication terminal number, the short message service center searches for information registered by the called subscriber and inserts it into the short message. Confirm the mobile communication terminal number corresponding to the called party's e-mail address, and then identify identification information of the relay device for transmitting the short message to the confirmed mobile communication terminal number, and then the short message. Deliver the message to the identified relay. The identification information of the relay device is any one of the address of the MSC and the address of the SGSN. The short message service center converts the short message into an e-mail format when the transmission format is written in a plain text format and the incoming format is set to be expressed in an e-mail type. The short message service center converts the short message into a plain text format when the outgoing format is written in an email format and the incoming format is set to be expressed in a plain text format.

A second aspect of the present invention for achieving the above object is that the short message service center confirms the called party identification information of a predetermined outgoing short message, and corresponds to the called party identification information by the called subscriber in advance. Retrieving a received short message format and a received short message format; and processing the originated short message in the received short message format and transmitting the received short message format to the called party.

More preferably, the reception and presentation format is set in advance in accordance with a registration request of the called subscriber identified by the identification information.

Also, preferably, the reception format is at least one of a format for receiving with an e-mail address and a format for receiving with a mobile phone number. Here, when the reception format preset by the called subscriber is a format for receiving an email address, the outgoing short message is transmitted to an e-mail server, and the presentation format of the outgoing short message is a plain text format. In such case, the outgoing short message is converted into an e-mail format.

On the other hand, when the reception format set in advance by the called subscriber is a format of receiving by the mobile communication terminal number, the outgoing short message is transmitted to the mobile communication terminal number of the called party. Here, when the presentation format of the outgoing short message is an email format, the outgoing short message is converted into a plain text format.

More preferably, the presentation format is either plain text format or email format. If the presentation format preset by the called subscriber is different from the presentation format of the outgoing short message, the outgoing short message is converted into the presentation format set by the called subscriber.

Other objects, features and advantages of the present invention will become apparent from the following detailed description of embodiments taken in conjunction with the accompanying drawings.

Hereinafter, with reference to the accompanying drawings illustrating the configuration and operation of the embodiment of the present invention, the configuration and operation of the present invention shown in the drawings and described by it will be described by at least one embodiment, By the technical spirit of the present invention described above and its core configuration and operation is not limited.

Once in the present invention, the network configuration shown in Figure 1 is used as it is. That is, there is no node added for controlling the short message of the present invention. However, at each node, software modules (applications) for the implementation of the present invention are added.

If the terms used below are defined in advance, the short message mentioned below is an SMS message. In addition, the terminal (terminal) described below is a UE including a mobile communication terminal that supports the sending and receiving of SMS messages.

The following describes the procedure for creating a short message at the originating terminal.

4 is a diagram illustrating a message writing procedure when a recipient's e-mail address is input, and FIG. 5 is a diagram showing a message writing procedure when a telephone number of a receiver's mobile communication terminal is input.

4 is a flowchart illustrating a message writing procedure when a recipient's e-mail address is input in a recipient subscriber input box in a short message input window, and FIG. 5 shows a mobile communication terminal number of the other party in a recipient subscriber input box in a short message input window. It shows the order of message writing for one case.

Meanwhile, in the present invention, the subscriber (user) uses a common input interface regardless of the format of the short message. Therefore, the subscriber writes in either plain text or email format using a common input interface, regardless of the short message format.

On the other hand, in the present invention, the receiving subscriber sets the receiving format (receiving format and / or display format) of the short message that is received by the recipient in advance so as not to be dependent on the format created by the calling party and the transmitted format. . In particular, the terminal of the receiving subscriber is provided with an application for registration of the incoming format, when the receiving subscriber requests registration of the incoming format through the application, the registration requested information is described later SMS command message (SMS-COMMAND) It is inserted into and sent to the SMS center. The SMS center then registers the incoming call type for the called subscriber according to the information inserted in the SMS command message (SMS-COMMAND).

In other words, the called party should display the short message in plain text format, in e-mail format, in plain text and in whatever format the originating subscriber has created and sent with any identifying information. It registers itself in SMS center by setting whether it is expressed in all e-mail formats, and registers in SMS center by setting where to receive short messages sent to itself (mobile communication terminal number or e-mail address). The SMS center then processes according to the presentation form registered by the called party and delivers it to the called party in the registered receiving form (destination).

In order to register the incoming call format for the short message of the called party, the present invention uses an SMS command message (SMS-COMMAND) defined in 3GPP TS23.040.

In particular, the present invention adds new information to the Transfer Protocol (TP) -Command-Type field defined in the SMS command message (SMS-COMMAND).

FIG. 6 is a diagram illustrating an SMS command message format. Table 1 below shows information of a TP-Command-Type field currently defined. Each field in FIG. 6 will be described below.

TP-MTI: TP-Message-Type-Indicator, TP message type indicator

-TP-SRR: TP-Status-Report-Request, TP status report request

TP-UDHI: TP-User-Data-Header-Indicator, TP User Data Header Indicator

-TP-MR: TP-Message-Reference, see TP message

TP-PID: TP-Protocol-Identifier, TP protocol identifier

-TP-CT: TP-Command-Type, TP Command Type

TP-MN: TP-Message-Number, TP message number

TP-DA: TP-Destination-Address, TP destination address

-TP-CDL: TP-Command-Data-Length, TP command data length

-TP-CD: TP-Command-Data, TP command data

In addition, Table 2 shows values of a newly defined delivery protocol command type (TP-Command-Type) field for short message processing in the present invention.

Field value Command Description Status reporting request value 00000000 Investigations related to previous short messages One 00000001 Eliminates status reporting requests related to previous short messages 0 00000010 Remove previous short message 0 00000011 Can report status related to previous short message 0 00000100..00011111 Spare Unspecified value 11100000..11111111 Specific value 1 or 0

Field value Command Description Status reporting request value 00000100 Receive incoming short messages in plain text format One 00000101 Receive incoming short messages in email format One 00000110 Receive incoming short messages in plain text and email format One

In the present invention, the reserved bits from "00000100" to "00011111" defined in Table 1 above are used to set the display format. More specifically, among the reserved bits, "00000100" is a command field value for processing an incoming short message in plain text format, "00000101" is a command field value for processing an incoming short message in email format, and "00000110" is plain text. Defined as command field value for processing in format and email format.

The called party transmits an SMS command (SMS-COMMAND) message having one of the command field values shown in Table 2 to the SMS center. Then, the SMS center checks the setting value in the SMS-COMMAND message received from the called party and registers the called type for the called party. After that, when a short message to be delivered to the called party is received, the short message is processed according to the registered call form of the called party and transmitted to the mobile terminal number or e-mail address of the called party.                     

In this case, the SMS center differs from a procedure of transmitting to a mobile terminal number and a procedure of transmitting to an e-mail address. In other words, when transmitting to the mobile communication terminal number, the SMS center first transmits a short message to the MSC or SGSN address where the mobile communication terminal of the called party is located. Then, the short message transfer procedure between the MSC or SGSN and the mobile communication terminal is performed. On the other hand, when sending to an email address, the SMS center first sends to the email address of the called party via the email server. The called subscriber then accesses his e-mail address and checks his short message received by the e-mail server.

On the other hand, the SMS center keeps the type of the caller registered by the callee using the SMS command message in the caller's database.

In particular, the database of the called subscriber includes one control area for the incoming short message. The control area includes one new control field called Terminating message handling (hereinafter abbreviated as TMH) field and further includes an email address field.

Table 3 below shows the control area of the called subscriber database provided in the SMS center.

IMSI (International Mobile Station Subscriber Identification Number) aaaaaaaaaaaaaaa MSC Address bbbbbbbbbbbbbbb SGSN address ccccccccccccccc HLR address ddddddddddddddd . . . . . . . . TMH Addition in the present invention Email Address Addition in the present invention

In Table 3, the TMH field according to the present invention is set to one of the following three cases. That is, the TMH field is one of control areas for setting the presentation format by the called subscriber.

1. Receive incoming short messages in plain text format.

2. Receive incoming short messages in email format.

3. Receive incoming short messages in plain text and email format.

Meanwhile, a procedure of processing a delivery protocol command type (TP-Command-Type) field value of an SMS command message (SMS-COMMAND) in an SMS center according to the present invention will be described below.

As described above, the receiving subscriber database of the SMS center has new setting information in the control area, and in particular, the information of the receiving format (expression format and receiving format) of the incoming short message with the addition of a new TMH field and email address field. Is added.

More specifically, the TMH field is a field that holds the presentation format of the incoming short message registered by the called subscriber using the SMS command message (SMS-COMMAND). Also, the e-mail address field is a field referred to when an incoming short message is received as an e-mail address. That is, when the called subscriber set to receive an incoming short message as an e-mail address, it is a field holding an e-mail address to which the incoming short message is to be received.

On the other hand, when the SMS center receives a short message that is received by a predetermined called party, the SMS center first checks the setting information registered in advance by the called party by referring to the control area of the database of the called party. In particular, the SMS center checks the setting information by the called subscriber by referring to the TMH field in the control area of the called subscriber database. Here, the setting information is a display form of the short message, and the e-mail address that received the short message.

In addition, the control area of the database of the called party further includes a predetermined field for holding a reception form registered in advance by the called party. The reception format is one of a format for receiving a short message to a mobile communication terminal number and a format for receiving a short message to an email address. Meanwhile, the present invention supports the recipient subscriber to further register the reception type for the incoming short message by using the TP-Command-Type field of the SMS command message (SMS-COMMAND). As an example, the present invention uses some reserved bits of the Transfer Protocol (TP) -Command-Type field defined in the SMS command message (SMS-COMMAND) to register the reception type.

7 is a diagram illustrating a procedure for providing a short message service according to an embodiment of the present invention, and shows a procedure for an SMS center to process an incoming short message (= outgoing short message).

Referring to FIG. 7, the SMS center receives an outgoing short message sent from an outgoing subscriber (S50). Here, the outgoing short message corresponds to the incoming short message in the process of delivering to the called subscriber by the SMS center.

The SMS center checks the called party identification information of the received outgoing short message, and searches for the reception and presentation format of the called short message set in advance corresponding to the called party identification information.

For that purpose, the SMS center examines the control area of the database corresponding to the called subscriber to which the outgoing short message is to be delivered for handling the outgoing short message. Thus, the setting contents of the reception format (reception format and presentation format) for the incoming short message registered in advance by the called subscriber are confirmed.

In FIG. 7, the reception formats are described, respectively, and are only described when the TMH field is checked in the control area of the called subscriber database. Therefore, in the present invention, not only the TMH field but also other fields of the control area having the setting contents of the above-described reception format are examined. Thus, the presentation format and reception format for the incoming short message are confirmed. The presentation format for the incoming short message refers to the value of the TMH field, and the reception format for the incoming short message refers to the value of the other control field. The above expression format has already been described above, and there are three types of reception formats: a format for receiving with a mobile communication terminal number, a format for receiving with an e-mail address, and a format for receiving with a mobile communication terminal number and an e-mail address.

On the other hand, after checking the setting contents of the reception and presentation format for the incoming short message through the inspection of the TMH field (S51, S52), the reception format is divided into a recipient format to the mobile communication terminal number and a recipient format to an email address.

First, it is assumed that the reception format is reception to the mobile communication terminal number, and that the called subscriber has set the plain text format to the presentation format (when the incoming short message is set to be displayed in the plain text format in the TMH field).                     

The SMS center checks whether the outgoing short message is in plain text (S53).

If the outgoing short message is confirmed in the e-mail format (S58), the SMS center first converts the outgoing short message into the plain text format (S59). If the outgoing short message is already in plain text format, no format conversion is required.

Subsequently, the SMS center acquires MSC or SGSN addresses (registered) to which the subscriber station's mobile communication terminal belongs (S54). More specifically, the SMS center sends a "SEND-ROUTING-INFO-FOR-SMS" message to the HLR. Thus, the MSC address or SGSN address where the called party is located is obtained.

The SMS center transmits an incoming short message (= outgoing short message) to the obtained MSC address or SGSN address (S55). The SMS center sends the message “MT-FORWARD-SHORT-MESSAGE” to the obtained MSC address or SGSN address and delivers the incoming short message. That is, a short message transfer procedure between the mobile subscriber station of the called subscriber and the MSC (or SGSN) is performed (S56).

Meanwhile, an incoming short message in a plain text format is displayed on the mobile communication terminal (S57).

The following is a case where the reception format is a reception to an email address, and it is assumed that the receiving subscriber has set the email format to the presentation format (when the incoming short message is set to display in the TMH field in the email format).

The SMS center checks whether the outgoing short message is an email format (S60).

If the outgoing short message is confirmed in an e-mail format (S61), the SMS center delivers the outgoing short message to the email server (S61). Of course, to forward the short message to the email server, you already reference the email address field in the control area of the called party database.

However, if the outgoing short message is confirmed in the plain text format (S62), the SMS center converts the outgoing short message into the email format (S63). After the conversion, the outgoing short message is transmitted to the email server (S61).

The called party accesses his email address and checks the incoming short message from the email server. Accordingly, a short message in an e-mail format is displayed on the terminal of the called subscriber.

On the other hand, when the incoming short message in the TMH field is set to display in the e-mail format as described above, the SMS center does not transmit the "SEND-ROUTING-INFO-FOR-SMS" message to the HLR. That is, the SMS center transfers the incoming short message to the email address set by the called subscriber by referring to the email address field in the control area of the called subscriber database.

In the present invention, the SMS center is connected with one or more email servers in order for the SMS center to send the incoming short message to the email server so that the incoming short message is delivered to the email address of the called party.

In addition, if the TMH field is set to display the incoming short message in the incoming plain text and email format, the SMS center is configured to receive the incoming short message in plain text format and that TMH is configured to receive the incoming short message in plain text format. Simultaneously perform a case where the message is set to receive in an e-mail format and process the incoming short message.

As another example, in the present invention, only the TMH field and the e-mail address field are used to set the incoming format of the incoming short message.

More specifically, according to another example of the present invention, the SMS center determines whether the receiving subscriber receives the short message in the e-mail format, the plain text format, or the e-mail format and the plain text format. It supports setting.

Accordingly, if the called subscriber registers to receive in an e-mail format using an application provided in his mobile communication terminal, the SMS center sends the incoming short message to the e-mail server.

Also, if the called party registers to receive in plain text format, the SMS center sends the incoming short message to the MSC address (or SGSN address) where the called party's terminal is located.

In addition, if the called party registers to receive in plain text and e-mail format, the SMS center not only sends an incoming short message to the MSC address (or SGSN address) where the called party's terminal is located, but also to an e-mail server.

However, in the above three cases, the incoming short message sent to the MSC address (or SGSN address) is processed to have a plain text format, and the incoming short message sent to the email address is processed to have an email format.                     

On the other hand, in another example described above, when the incoming short message in the TMH field is set to display in an e-mail format, the SMS center does not transmit a "SEND-ROUTING-INFO-FOR-SMS" message to the HLR. On the other hand, if the TMH field is set to display an incoming short message in plain text format, the SMS center transmits a "SEND-ROUTING-INFO-FOR-SMS" message to the HLR to transmit the incoming short message (MSC). Or SGSN).

Summarizing the incoming processing for the incoming short message according to the present invention, the SMS center first confirms the called party identification information of the outgoing short message. Then, it is checked whether the called format registered in advance by the confirmed called party's subscriber is the same as the calling format of the calling short message.

In particular, in the present invention, if the originating format of the outgoing short message is different from the incoming form registered in advance by the called party, the SMS center converts the outgoing short message into the incoming form registered by the called party. In other words, if the outgoing short message is set to plain text format and the incoming form registered by the incoming subscriber is set to display in e-mail format, the SMS center converts the outgoing short message to email format. do. In addition, when the originating format of the outgoing short message is set in the e-mail format and the incoming form registered by the called subscriber is set to be expressed in the plain text format, the SMS center converts the outgoing short message into the plain text format.

For example, if the outgoing format of the outgoing short message is a form of sending to a mobile communication terminal number, the incoming form registered by the called subscriber is a form of receiving by an e-mail address, and the SMS center first receives the call. The identification information registered by the subscriber is searched to confirm an e-mail address corresponding to the called party's mobile terminal number inserted in the outgoing short message. The outgoing short message is then forwarded to an e-mail server for delivery to the verified email address.

On the other hand, if the outgoing short message is sent to an e-mail address, but the incoming call type registered by the called subscriber is received by the mobile terminal number, the SMS center searches for and sends information registered by the called subscriber. Check the mobile communication terminal number corresponding to the called party's e-mail address inserted in the short message. Then, the identification information (MSC address or SGSN address) of the relay device for transmitting the outgoing short message to the confirmed mobile communication terminal number is further confirmed. Identification information of the relay device is confirmed through the HLR. Then, the outgoing short message is transmitted to the relay apparatus where the identification information is confirmed. Then, the incoming short message transfer procedure is performed between the relay device and the mobile communication terminal.

As described above, according to the present invention, a variety of user-oriented SMS can be provided to an increasing number of SMS subscribers. In other words, when creating and sending a short message in plain text format to a subscriber and creating and sending a short message in an email format, the subscriber interface has a unified interface for creating and inputting a short message. to provide.

Apart from the simple SMS message sending / receiving service thus far, the subscriber can set the receiving processing direction for the short message that is received to the user in advance, thereby providing a flexible service in the next generation communication environment. That is, the subscriber can check the short message through his or her e-mail address by registering to receive an incoming short message at an e-mail address when the terminal cannot be used. In addition, the present invention had to delete previously received messages due to the limitation of the message storage capacity of the terminal. In the present invention, it is possible to simultaneously receive an incoming short message in a plain text format and an email format. Can be archived.

Those skilled in the art will appreciate that various changes and modifications can be made without departing from the spirit of the present invention.

Therefore, the technical scope of the present invention should not be limited to the contents described in the embodiments, but should be defined by the claims.

Claims (24)

When the called subscriber registers an incoming call format for the short message in the short message service center, the short message service center presetting the incoming call format for the called subscriber; When the short message to be delivered to the called subscriber is received, processing the short message in the preset called format; And transmitting the processed short message to the called subscriber. The method of claim 1, wherein a short message service command message (SMS-COMMAND) is used for registration of the incoming format. 3. The short form of claim 2, wherein the incoming type is registered by using a reserved bit of a Transfer Protocol-Command-Type field defined in the short message service command message (SMS-COMMAND). How to provide a message service. The method of claim 2, wherein the incoming format includes a reception format and a presentation format, wherein the reception format is at least one of reception to a communication terminal number and reception to an e-mail address. Method of providing a short message service, characterized in that at least one of the expression in plain text format and e-mail type (e-mail type). 5. The method of claim 4, wherein the short message service center sets the reception format and the presentation format according to the registration of the incoming format in a control area of the database of the called party. 6. The terminal of claim 5, wherein the control area includes a communication terminal number of the called party, an address of a mobile switching center (MSC) in which the called party is registered, and a serving GPRS support node (SGSN). And a terminating message handling (TMH) field for setting the presentation format, and fields for setting an address and a Home Location Register (HLR) address, respectively. How to provide short message service. 7. The method of claim 6, wherein the control area further includes a field for setting an email address of the called party so as to set a reception format to the email address among the reception formats. The method of claim 2, wherein an application for registration of the incoming call type is provided in a terminal of the called subscriber. The method of claim 8, wherein when the called subscriber requests registration of the called type through the application, the registration requested information is inserted into the short message service command message (SMS-COMMAND) and transmitted to the short message service center. And the short message service center registers the called subscriber according to the information inserted in the short message service command message (SMS-COMMAND). The method of claim 1, wherein the processing of the short message is performed by: Check that the origination format of the short message is the same as the incoming format, And when the originating format is different from the terminating format, converting the short message into a terminating format registered by the terminating subscriber. The short message service center of claim 10, wherein the short message service center is registered by the called subscriber when the originating format is a format for transmitting to a communication terminal number and the terminating format is a format for receiving with an e-mail address. Retrieves the information and confirms an e-mail address corresponding to the called party's communication terminal number inserted in the short message, and then delivers the short message to an e-mail server for sending the short message to the confirmed e-mail address. Short message service providing method characterized in that. 11. The method according to claim 10, wherein when the origination format is a format for transmitting to an e-mail address and the terminating format is a format for receiving with a communication terminal number, the short message service center searches for information registered by the terminating subscriber, Confirm the communication terminal number corresponding to the called party's e-mail address inserted in the short message, and then identify the identification information of the relay apparatus for transmitting the short message to the confirmed communication terminal number, and then The short message service providing method, characterized in that for transmitting the short message to the identified relay device. The short message of claim 12, wherein the identification information of the relay device is one of an address of a mobile switching center (MSC) and an address of a serving GPRS support node (SGSN). How we deliver the service. The short message service center of claim 10, wherein the short message service center converts the short message into an e-mail format when the originating format is written in a plain text format and the incoming format is set to be expressed in an e-mail format. Short message service providing method characterized in that. The short text message service of claim 10, wherein the short message service center converts the short message into a plain text format when the outgoing format is written in an email format and the incoming format is set to be expressed in a plain text format. How to provide a message service. Confirming, by the short message service center, called party identification information of the predetermined outgoing short message; Retrieving a format for receiving and presenting a short message preset by the called subscriber in correspondence with the called party identification information; And transmitting the outgoing short message to the called party by processing the outgoing short message in a reception and presentation format. 17. The method of claim 16, wherein the reception and presentation formats are set in advance according to a registration request of the called subscriber identified by the identification information. 17. The method of claim 16, wherein the reception format is at least one of a format received by an e-mail address and a format received by a mobile phone number. 19. The short message service of claim 18, wherein the outgoing short message is transmitted to an e-mail server when the reception format preset by the called subscriber is a form of receiving an e-mail address. Way. 20. The method of claim 19, wherein, when the presentation format of the outgoing short message is a plain text format, the outgoing short message is converted into an e-mail format. 19. The short message service providing according to claim 18, wherein the outgoing short message is transmitted to a communication terminal number of the called party when the reception format preset by the called subscriber is a form of receiving a communication terminal number. Way. 22. The method of claim 21, wherein when the presentation format of the outgoing short message is an email format, the outgoing short message is converted into a plain text format. The method of claim 16, wherein the presentation format is one of a plain text format and an email format. 24. The short message as claimed in claim 23, wherein the outgoing short message is converted into an outgoing format set by the called party when the presentation format preset by the called party is different from the presentation format of the outgoing short message. How we deliver the service.

Images