KR20240140620A - Method, server and system for sending text message via mobile phone mail application - Google Patents

Abstract

The present invention relates to a method, device and system for transmitting a text message via a mobile phone mail application, comprising: a step of identifying a recipient format of a mail written using the mail application; a step of calling a text message API based on the identification that the recipient format is a mobile phone number; a step of generating a text message using the text message API with the mobile phone number as the recipient; and a step of transmitting the generated text message.

Description

METHOD, SERVER AND SYSTEM FOR SENDING TEXT MESSAGE VIA MOBILE PHONE MAIL APPLICATION

The present invention relates to a method, device and system for transmitting a text message via a mobile phone mail application, and more specifically, to a method, device and system for transmitting a text message for increasing the convenience of using a mobile phone for message transmission.

Currently, text messaging services on mobile phones have a function that allows you to send a text message by specifying an email address instead of a mobile phone number (CTN). For example, if a user runs a text messaging app on their mobile phone, writes a text message, and then enters an email address instead of the recipient's phone number, the text message can be sent as an email.

On the other hand, there is no function in mobile phone mail services that allows you to send a text message by specifying the recipient's mobile phone number instead of the recipient's email address. For example, if a user runs the mail app on their mobile phone to compose an email and then enters a phone number instead of the recipient's email address, the email they wrote will fail to be sent as a text message and an error message may be displayed.

In other words, there are restrictions on sending emails written in the mail application as text messages. Due to these restrictions, users have had difficulty sending written emails as text messages or sending emails and text messages at the same time.

Korean Patent No. 10-0838020

The present invention is intended to solve the above-described problems, and its purpose is to provide a method, device and system for sending a text message by calling a text message API according to the format of the recipient address while composing a mail via a mobile phone mail application.

According to one aspect of the present invention, a method for transmitting a text message via a mail application of a mobile phone is provided. The method for transmitting the text message includes a step of identifying a recipient format of a mail written using the mail application, a step of calling a text message API based on the identification that the recipient format is a mobile phone number, a step of generating a text message using the text message API with the mobile phone number as a recipient, and a step of transmitting the generated text message.

In one aspect, the step of identifying the recipient format includes the step of identifying, as the recipient format, at least one of a mail address format and a mobile phone number format.

In another aspect, in the step of identifying the recipient format, the method further includes a step of transmitting an e-mail based on at least one protocol among SMTP, POP3 and IMAP in response to identifying the mail address format as the recipient format.

In another aspect, in the step of identifying the recipient format, the method further includes a step of simultaneously transmitting an email and a text message to the email address and the mobile phone number, respectively, corresponding to identifying both the email address format and the mobile phone number format as the recipient format.

In another aspect, the step of identifying the recipient format includes a step of identifying the recipient format as a mobile phone number format when the input recipient format includes at least one of a network number, an area code, and a subscriber number.

In another aspect, the step of identifying the recipient format includes the step of identifying the recipient format as a mobile phone number format when the input recipient format consists of multiple numbers and multiple hyphens (-).

In another aspect, the step of identifying the recipient format includes the step of identifying the recipient format as a mail address format if the input recipient format includes the term @, com or net.

In another aspect, the step of calling the text message API of the mobile phone includes the step of the mail application calling an SMS function of the SMS application using the text message API.

In another aspect, the step of calling the above SMS function calls the Mobile_SMS() function to pass the subject, content, and mobile phone number of the above-mentioned written mail.

In another aspect, the step of generating the text message includes the step of generating the text message using the mobile number of the mobile phone as the sender and the mobile phone number, the subject and the content included in the composed email as arguments.

In another aspect, the step of generating the text message includes the step of inputting the subject of the composed mail as the subject of the text message and inputting the content of the composed mail as the content of the text message.

In another aspect, the method further comprises the step of updating the mail application based on the transmission result for the text message.

In another aspect, the step of updating the mail application includes the step of returning a normal transmission result of the text message to the mail application and the step of updating the sent mailbox of the mail application based on the returned normal transmission result.

According to another aspect of the present invention, a device for transmitting a text message via a mail application is provided. The device for transmitting the text message includes a processor for identifying a recipient format of a mail written using the mail application, wherein the recipient format is a mobile phone number, and calling a text message API of the mobile phone based on the identification, and generating a text message with the mobile phone number as a recipient using the text message API, and a communication module for transmitting the generated text message.

According to another aspect of the present invention, a system for transmitting a text message via a mail application is provided. The system for transmitting the text message includes a mobile phone which identifies a recipient format of a mail written using the mail application, and, based on identifying that the recipient format is a mobile phone number, calls a text message API of the mobile phone, generates a text message with the mobile phone number as a recipient using the text message API, and transmits the generated text message, and a server which receives the text message and transmits a transmission result of the text message to the mobile phone.

In one aspect, the server side identifies whether the mobile phone number is a number registered with the IMS (IP Multimedia Subsystem), and transmits the text message to a subscriber ID matching the mobile phone number based on the identification that it is registered with the IMS.

In another aspect, the server side includes a server operating at the IMS layer (IP Multimedia Core Network Subsystem Layer) and a gateway operating at the Transport Layer.

In another aspect, the server performs the functions of P-CSCF and S-CSCF, but evaluates the initial filter criteria (IFC) using the S-CSCF.

In another aspect, the gateway performs reporting on the change of message type and the transmission result of the text message.

Embodiments of the present invention may have effects including the following advantages. However, it should not be understood that the embodiments of the present invention should include all of these, and thus the scope of the rights of the present invention should not be limited thereby.

A method, device and system for sending a text message via a mobile phone mail application according to one embodiment of the present invention has the effect of enabling users to easily contact each other using contact information stored in a mobile phone instead of an email address that is difficult for the user to remember.

In addition, it has the effect of increasing convenience by sending the contents of the email written by the user as a text message or sending text messages and emails simultaneously.

Additionally, it has the effect of preventing duplicate writing by calling the text message API through the mail application.

FIG. 1 is a schematic diagram illustrating a system for transmitting a text message via a mobile phone mail application according to one embodiment of the present invention.
FIG. 2 is a flowchart of a method for transmitting a text message according to one embodiment of the present invention.
Figure 3 is a detailed flowchart showing specific details of operations after step (S210) of Figure 2.
Figure 4 is a diagram showing composing an email on a mobile phone's email application.
FIG. 5 is a block diagram of a device for transmitting a text message according to one embodiment of the present invention.
Figure 6 is a diagram showing the message transmission and reception flow of a mobile phone.

The present invention can have various modifications and various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, but should be understood to include all modifications, equivalents, or substitutes included in the spirit and technical scope of the present invention.

Although the terms first, second, A, B, etc. may be used to describe various components, the components should not be limited by the terms. The terms are only used to distinguish one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and/or includes any combination of a plurality of related described items or any item among a plurality of related described items.

When it is said that a component is 'connected' or 'connected' to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components in between. On the other hand, when it is said that a component is 'directly connected' or 'directly connected' to another component, it should be understood that there are no other components in between.

The terminology used herein is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, it should be understood that the terms "comprises" or "has" and the like are intended to specify the presence of a feature, number, step, operation, component, part or combination thereof described in the specification, but do not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms defined in commonly used dictionaries, such as those defined in common dictionaries, should be interpreted as having a meaning consistent with the meaning they have in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless expressly defined in this application.

Before going into a detailed description of the drawings, it should be made clear that the division of components in this specification is only based on the main function of each component. In other words, two or more components described below may be combined into one component, or one component may be divided into two or more parts with more detailed functions.

In addition to the main function that it is responsible for, each component described below may additionally perform some or all of the functions that other components are responsible for, and some of the main functions that each component is responsible for may be exclusively performed by other components. Accordingly, the existence of each component described throughout this specification should be interpreted functionally.

As used herein, “A or B” can mean “only A”, “only B”, or “both A and B”. In other words, as used herein, “A or B” can be interpreted as “A and/or B”. For example, as used herein, “A, B or C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”.

As used herein, a slash (/) or a comma can mean "and/or". For example, "A/B" can mean "A and/or B". Accordingly, "A/B" can mean "only A", "only B", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

As used herein, “at least one of A and B” can mean “only A”, “only B” or “both A and B”. Additionally, as used herein, the expressions “at least one of A or B” or “at least one of A and/or B” can be interpreted identically to “at least one of A and B”.

Additionally, in this specification, "at least one of A, B and C" can mean "only A", "only B", "only C", or "any combination of A, B and C". Additionally, "at least one of A, B or C" or "at least one of A, B and/or C" can mean "at least one of A, B and C".

Hereinafter, with reference to the attached drawings, a preferred embodiment of the present invention will be described in more detail. In order to facilitate an overall understanding in describing the present invention, the same reference numerals are used for the same components in the drawings, and redundant descriptions of the same components are omitted.

FIG. 1 is a schematic diagram illustrating a system for transmitting a text message via a mobile phone mail application according to one embodiment of the present invention.

Referring to FIG. 1, a text message transmission system (100) according to the present embodiment is a system that transmits a mail or a text message to a recipient or transmits both simultaneously based on identifying the recipient format while composing a mail using a mail application of a mobile phone, and may include a transmitting terminal (110), a server (120), and receiving terminals (130a, 130b).

The transmitting terminal (110) is a device that allows a user to write an e-mail. The transmitting terminal (110) may be implemented as a user's mobile phone, mobile terminal, portable terminal, smart phone, PDA, etc. The embodiments of the transmitting terminal (110) described below are embodiments in the case of a smart phone, but the above-described PDA, mobile phone, or portable terminal may also be applied.

The server (120) is a device that receives an e-mail transmitted from a transmitting terminal (110) and transmits it to a receiving terminal (130a, 130b). The server (120) may be implemented as an IMS server, an application server (e.g., may include a mail management server, a text message management server, etc.), a gateway, etc. The embodiments of the server (120) described below are embodiments in the case of an IMS server, but the application server described above may also be applied. Alternatively, a combination of an IMS server and a gateway may be applied in the form of a server unit.

The receiving terminal (130a, 130b) is a device that receives an e-mail or text message from the server (120). The receiving terminal (130a, 130b) may be implemented as a mobile phone, a mobile terminal, a portable terminal, a smart phone, a laptop, a PC, etc. For example, in the case of receiving an e-mail written by a user, the receiving terminal may be implemented as a PC (130a). However, it may also be implemented as a smart phone (130b). As another example, in the case of receiving a text message based on an e-mail written by a user, the receiving terminal may be implemented as a smart phone (130b). The embodiments of the user terminal (130) described below are described using a smart phone (130b) as an example, but other types of user terminals, such as a PC, may be applied here. Based on the text message transmission system (100) of FIG. 1, a business model (BM) for transmitting a text message via a mail application of a mobile phone may be implemented.

The user can compose an email using the email application provided in the sending terminal (110). Specifically, the sending terminal (110) can send an email using protocols such as SMTP, POP3, and IMAP in the email application. At this time, if the recipient's address in the form of a mobile phone number (CTN) is recognized, a text message related function can be called that can send a text message with the recipient's number, subject, and content information as arguments. By using the called text message related function, the mail content can be created as a text message and sent to the server (120).

For example, a user can compose an email through a mail application on a smartphone, and the composed message can be delivered to a recipient address through a server that processes an email protocol. At this time, if the recipient's address is in a mobile phone number format such as 010-XXXX-XXXX, the mail application can call an SMS service API. Then, a text message with 010-XXXX-XXXX as the recipient can be generated using the SMS service API. Then, the generated text message can be transmitted to the recipient's mobile phone that uses 010-XXXX-XXXX as its mobile phone number. In this specification, the format of the text message to be transmitted has been described using SMS as an example, but it will be apparent to those skilled in the art that other formats of text messages, such as MMS, can be used in the part where SMS is written.

In order to send a text message based on mail, the mail application of the sending terminal (110) can identify the format of the recipient of the mail being written. The recipient format can be identified as a mail address format, a mobile phone number format, or both formats at the same time.

For example, if the email address format is identified by the recipient format, an email written in a mail application can be sent to the recipient's email address as is without any special processing.

As another example, when a mobile phone number format is identified as the recipient format, the mail being written can be automatically converted into a text message (SMS, MMS) and transmitted to the receiving terminal (130a, 130b).

As another example, when the mail address format and the mobile phone number format are identified at the same time in the recipient format, the mail can be sent without any special processing, and at the same time, it can be converted to a text message and sent. Here, the recipient's mail address and mobile phone number can be the same recipient's mail address and mobile phone number, or can be different recipients' mail addresses and mobile phone numbers. Of course, it can be the recipient's mobile phone number stored in the sending terminal (110), or it can be an unstored mobile phone number.

Meanwhile, as described above, it is necessary to identify whether the recipient format corresponds to a mobile phone number format in the mail application of the sending terminal (110). To this end, the mail application may include a function that automatically identifies or recognizes a mobile phone number entered by a user.

For example, if the input recipient format includes at least one of a network number, area code, and subscriber number, the recipient format can be identified as a mobile phone number format. In the case of Korea, the current network number used is unified as 010, so it can be determined that the recipient format is a mobile phone number by identifying 010 in the input recipient format. However, since it is sometimes used overseas, identification is not limited to 010. Since the area code or subscriber number also consists of 3 to 4 digits, it can be determined that it is a mobile phone number by identifying 3 to 4 digits in the recipient format.

As another example, if the input recipient format includes multiple numbers, the recipient format can be identified as a mobile phone number format. By identifying the numbers in the same manner as above, it can be determined that the recipient format is a mobile phone number.

As another example, if the input recipient format includes multiple numbers and multiple hyphens (-), the recipient format can be identified as a mobile phone number format. In some cases, the user may insert a hyphen between the network number, area code, and subscriber number. Therefore, by identifying that multiple numbers and multiple hyphens are entered, it is possible to determine whether the recipient format is a mobile phone number.

Meanwhile, the mail application of the sending terminal (110) may include a function for identifying or recognizing not only the mobile phone number but also the mail address.

For example, if the input recipient format includes terms such as @, com, or net, the recipient format can be identified as a mail address format. The terms @, com, or net are terms commonly used in e-mail systems. Therefore, by identifying the presence or absence of the terms @, com, or net in the input recipient format, it is possible to determine whether the recipient format is a mail address format.

If it is identified that the entered recipient format is a mobile phone number based on any of the examples described above, the text message API of the mobile phone can be called. Calling the text message API means calling the SMS function of the SMS application using the text message API while the mail application is running.

In other words, when a user is composing an email and does not know or has difficulty remembering the recipient's email address, the user can enter a mobile phone number as the recipient address instead of the email address without having to rewrite the email content as a text message. The text message API can then call the SMS function to create a text message based on the content of the email and send it as an SMS. As an example, the SMS function is called, but the text message to be sent can be either an SMS or an MMS depending on the capacity, length, and attachment of the composed email. For example, if the recipient format is identified as a mobile phone number and the composed email has an attachment, the SMS can be converted to an MMS and sent. In other words, the MMS function can be called to send an MMS.

The sending terminal (110) can automatically input the subject of the written mail as the subject of the text message, and automatically input the content of the mail as the content of the text message. That is, the recipient's mobile phone number entered in the mail application, and the subject and content included in the written mail can be applied as input values for the text message, i.e., arguments.

The server (120) can receive a request for transmission of an e-mail or a text message (SMS, MMS) converted based on an e-mail from a transmitting terminal (110). When the server (120) receives the converted text message, it can identify whether the recipient's mobile phone number included in the text message is a number registered in IMS (IP Multimedia Subsystem). Then, based on identifying that it is a mobile phone number registered in IMS, it can transmit the text message to a subscriber ID matching the recipient's mobile phone number.

The server (120) can transmit the transmission result of the text message to the transmitting terminal (110). The transmitting terminal (110) can receive the transmission result and update the sent mailbox of the mail application.

FIG. 2 is a flowchart of a method for transmitting a text message according to one embodiment of the present invention.

Referring to FIG. 2, a method for transmitting a text message includes steps S210 to S250. The method for transmitting a text message according to the present embodiment is described as an operation by the transmitting terminal (110) described through FIG. 1. More specifically, steps S210 to S230 and S250 are operations by the mail application of the transmitting terminal (110), and step S240 is an operation by the text message application (SMS application) of the transmitting terminal (110). Since the mail application and the text message application are included in the same transmitting terminal (110), for convenience of explanation, each step is described with the transmitting terminal (110) as the executing subject.

In step S210, the transmitting terminal (110) identifies whether the recipient format is a mobile phone number (mobile number). The transmitting terminal (110) receives information about the mail title, content, and recipient address from the user. Then, it identifies whether the format of the recipient address among the input contents is a mobile phone number format. For example, the transmitting terminal (110) can identify whether a mobile phone number is entered in a location where the recipient address is entered (e.g., may include a recipient category, a recipient item, a recipient input field, and/or a reference recipient input field).

At step S220, the transmitting terminal (110) calls a text message API (SMS API) based on identifying that the format of the recipient address is a mobile phone number format. When the mail application of the transmitting terminal (110) needs to convert the mail content into a text message and transmit it because the format of the recipient address is a mobile phone number, the mail application can call the text message API to utilize the function of the text message application.

At step S230, the transmitting terminal (110) requests the text message application (SMS application) to create and send a text message using the text message API. At this time, the mail application of the transmitting terminal (110) may still be running. That is, while the mail application is running, the mail application may perform an operation of requesting the text message application to send a text message.

In step S240, the transmitting terminal (110) generates and transmits a text message based on a transmission request from the mail application. At this time, the text message application (SMS application) obtains information about the subject, content, and recipient address of the mail written by the user on the mail application. Then, it generates a text message based on this. In other words, even if the user does not rewrite a text message with the same content as the mail written separately in the text message application, the text message can be generated based on the content of the mail written based on calling the text message API.

The transmitting terminal (110) transmits the generated text message to the recipient's mobile phone number. The operations according to steps S210 to S240 may be operations processed internally in the transmitting terminal (110). This may be automatically processed without requiring the user to make additional requests or input information.

In step S250, the transmitting terminal (110) receives the transmission result for the text message from an external source (e.g., a server side) and updates the mail application based on this. When a text message is sent through the text message application, the transmission result of the text message is returned through the server side (which may include an IMS server and a gateway). The transmission result may include information (e.g., ACK information) on whether the text message was properly delivered to the recipient. The transmitting terminal (110) may update the mail application based on the returned transmission result. More specifically, a record such as successful or failed text message transmission may be updated in the sent mailbox of the mail application. The transmitting terminal (110) may provide the user with the updated text message transmission result in the form of a notification. For example, a transmission completion message may be output on the screen of the transmitting terminal (110) or a notification sound indicating the completion of transmission may be output through the speaker of the transmitting terminal (110).

Figure 3 is a detailed flowchart showing specific details of operations after step (S210) of Figure 2.

Referring to FIG. 3, steps S310 to S340 are described as operations by the mail application of the sending terminal (110). The sending terminal (110) performs steps S310 to S330 in the same manner as steps S210 to S230 of FIG. 2, but may additionally perform step S340 depending on the result of identifying the recipient address in step S310.

Prior to performing step S310, the transmitting terminal (110) can drive an e-mail application based on the user's input. Then, information about e-mail can be received through the driven e-mail application.

When receiving information about an e-mail, the sending terminal (110) identifies the format of the recipient address according to step S310. The sending terminal (110) can identify whether the format of the recipient address included in the information about the e-mail (e-mail subject, content, recipient address) is an e-mail address format, a mobile phone number (CTN) format, or both.

For example, if the format of the recipient address is identified as a mobile phone number (CTN) format, the transmitting terminal (110) calls the SMS API according to step S320. Then, it requests SMS creation and transmission according to step S330. That is, steps S320 and S330 can be performed in the same manner as steps S220 and S230 described above through FIG. 2.

As another example, if the format of the recipient address is identified as an email address format, the sending terminal (110) transmits information about the email (mail subject, content, recipient address) to the recipient's email address according to step S340. Here, information indicating who the sender is (e.g., the mobile number of the sending terminal (110) or the email address of the user of the sending terminal (110)) may be additionally included and transmitted.

As another example, if it is identified that the format of the recipient address is both a mobile phone number format and an e-mail address format, the transmitting terminal (110) performs steps S330 and S340 simultaneously. That is, if a mobile phone number and an e-mail address are input as recipient addresses from a user, an e-mail and a text message can be simultaneously transmitted to the input recipient's mobile phone number and e-mail address, respectively.

Figure 4 is a diagram showing composing an email on a mobile phone's email application.

Referring to FIG. 4, a user can input a mobile phone number in the format of 010-XXXX-XXXX in the recipient field on the mail composition screen of a mobile phone email application. Then, information related to the mail can be input sequentially for each item as shown in FIG. 4. For example, a user can input a recipient field, and then input mail content in the following order: a Cc field, a Bcc field, a Sender field, a Subject field, and an Email Composition field. In this case, the mail application identifies whether the items that can indicate the recipient among the above items are in the format of a mobile phone number or an email address. Basically, since the Recipient field, Cc field, and Bcc field are items related to the recipient, the criteria for identifying the recipient format can be set to be applied only to these. In some cases, the user can set the recipient format identification operation to be performed only on the Recipient field, and not to be performed on the Cc field and the Sender field.

FIG. 5 is a block diagram of a device for transmitting a text message according to one embodiment of the present invention.

Referring to FIG. 5, a device (500) for transmitting a text message includes a user interface (510), a display (520), a processor (530), a memory (540), and a communication module (550). The device (500) for transmitting a text message can be implemented as a transmitting terminal (110) described above with reference to FIG. 1.

The user interface (510) is provided for the user to write an email. The user interface (510) can be implemented as a keypad or touchpad for writing an email.

The display (520) outputs the email written by the user on the screen. The display (520) may be provided as an integral part with the user interface (510). That is, it may be provided in the form of a touch screen or a touch display.

The processor (530) identifies the recipient format of the mail created using the mail application. Based on the identification that the recipient format is a mobile phone number, the processor (530) calls the text message API of the mobile phone. The processor (530) generates a text message with the mobile phone number as the recipient using the text message API.

The memory (540) stores a mail application and a text message application. The memory (540) may be implemented as a storage device such as an HDD or SSD. The mail application and the text message application stored in the memory (540) may be executed under the control of the processor (530).

The communication module (550) transmits a text message generated by the processor (530). The communication module (550) can be implemented as a communication module or communication modem capable of communicating with the server end.

Meanwhile, the device (500) for transmitting the above-described text message may be implemented as a program (or application) including an executable algorithm that can be executed on a computer. The program may be provided by being stored on a temporary or non-transitory computer readable medium.

Figure 6 is a diagram showing the message transmission and reception flow of a mobile phone.

Referring to Fig. 6, it is shown that a user terminal (UE) performs MO SMS Signal Flow based on an existing registered session (P-CSCF, S-CSCF, IP-SM-GW). The user terminal (UE), server (P-CSCF, S-CSCF), and gateway (IP-SM-GW) can perform message exchange operations for SMS transmission processing by exchanging information from (1)Message to (14)Message.

First, the UE converts the mail into a text message and transmits it to the P-CSCF as (1)Message. (1)Message includes user mail information such as Content Type: vnd3gpp.sms RP-User-Data. As the UE performs SMS-Submit, (1)Message is transmitted to the P-CSCF.

When P-CSCF receives (1)Message, it forwards (2)Message to S-CSCF.

When S-CSCF receives (2)Message, it evaluates (3)Initial Filter Criteria (IFC).

After the server operating in the IMS layer (IP Multimedia Core Network Subsystem Layer) performs (3) using the S-CSCF function, it transmits (4)Message to the gateway (IP-SM-GW).

When the gateway (IP-SM-GW) operating in the Transport Layer receives (4)Message, it sends (5)202 Accepted message to the S-CSCF of the server as an ACK notifying that message reception was performed normally.

When the S-CSCF receives the (5)202 Accepted message, it sends a (6)202 Accepted message to the P-CSCF.

When the P-CSCF receives the (6)202 Accepted message, it sends a (7)202 Accepted message to the UE.

Meanwhile, the gateway (IP-SM-GW) extracts the message (SM) to be transmitted (8) after transmitting the (5)202 Accepted message and reports the SMS transmission result. The gateway (IP-SM-GW) transmits the message (SM) extracted in the process (8) to the S-CSCF as a (9)Message. The type of the transmitted (9)Message is changed to a form such as Content Type: vnd3gpp.sms RP-ACK-Data. As the gateway (IP-SM-GW) performs the SMS-Submit Report, the (9)Message is transmitted to the S-CSCF.

When S-CSCF receives (9)Message, it forwards (10)Message to P-CSCF.

When the P-CSCF receives (10)Message, it forwards (11)Message to the UE.

When the UE receives the (11)Message, it sends a (12)200 OK message to the P-CSCF as an ACK notifying that the message reception was performed normally.

When the P-CSCF receives the (12)200 OK message, it forwards a (13)200 OK message to the S-CSCF.

When S-CSCSF receives the (13)200 OK message, it forwards the (14)200 OK message to the gateway (IP-SM-GW). An operation to transmit a text message can be performed according to this flow.

When recognizing the mobile number of the recipient of the email entered by the user, the SMS function provided by the SMS application is called and the recipient's mobile number, subject, and content are delivered as arguments. In order to perform this function, it is assumed that the SMS application of the mobile phone provides an SMS API that can be called and used by another application (mail application). In other words, an API that enables interaction between the mail application and the SMS application can be provided on the mobile phone.

For example, an email application might call an SMS function called "Mobile_SMS()". More specifically, the function would look like this:

Result = Return(Mobile_SMS(RX_caller, Subject, Contexts))

Call these SMS functions to pass the subject, content, and recipient number of the email.

Meanwhile, the SMS application that is called and executed creates and sends an SMS message to the mobile number of the corresponding terminal as the sender and to the mobile number of the recipient as the argument.

Meanwhile, the SMS normal transmission result value is sent to the mail application as a return value, and the mail application's sent mailbox is updated with the result. That is, the UE receives the return value from the server side (P-CSCF, S-CSCF, IP-SM-GW) and updates the mail application's sent mailbox.

The method, device and system for transmitting a text message via a mobile phone mail application according to one embodiment of the present invention have been described with reference to the embodiments illustrated in the drawings to help understanding, but these are merely exemplary, and those skilled in the art will understand that various modifications and equivalent other embodiments are possible. Accordingly, the true technical protection scope of the present invention should be defined by the appended claims.

Claims (19)

In a method of sending a text message through a mail application of a mobile phone,
A step for identifying the recipient format of an email written using the above email application;
A step of calling a text message API based on identifying that the above recipient format is a mobile phone number;
A step of generating a text message with the mobile phone number as the recipient using the text message API; and
A method for transmitting a text message, comprising the step of transmitting the generated text message. In the first paragraph, the step of identifying the recipient format is:
A method for transmitting a text message, comprising the step of identifying at least one format among an email address format and a mobile phone number format in the above recipient format. In the second paragraph,
A method for transmitting a text message, wherein in the step of identifying the recipient format, the method further includes a step of transmitting an e-mail based on at least one protocol among SMTP, POP3, and IMAP in response to identifying the mail address format as the recipient format. In the second paragraph,
A method for transmitting a text message, wherein in the step of identifying the recipient format, the method further includes a step of simultaneously transmitting an email and the text message to the email address and the mobile phone number, respectively, in response to identifying both the email address format and the mobile phone number format as the recipient format. In the first paragraph, the step of identifying the recipient format is:
A method for transmitting a text message, comprising the step of identifying the recipient format as a mobile phone number format when the input recipient format includes at least one of a network number, an area code, and a subscriber number. In the first paragraph, the step of identifying the recipient format is:
A method for transmitting a text message, comprising the step of identifying the recipient format as a mobile phone number format when the input recipient format consists of multiple numbers and multiple hyphens (-). In the first paragraph, the step of identifying the recipient format is:
A method of transmitting a text message, comprising the step of identifying the recipient format as a mail address format when the entered recipient format includes the terms @, com or net. In the first paragraph, the step of calling the text message API of the mobile phone comprises:
A method for sending a text message, comprising the step of the above mail application calling an SMS function of an SMS application using the above text message API. In the 8th paragraph, the step of calling the SMS function is:
A method of sending a text message by calling the Mobile_SMS() function, which transmits the subject, content, and mobile phone number of the above-mentioned written mail. In the first paragraph, the step of generating the text message comprises:
A method for sending a text message, comprising the step of creating a text message using the mobile number of the above-mentioned mobile phone as the sender and the mobile phone number and the subject and content included in the above-mentioned written email as arguments. In the first paragraph, the step of generating the text message comprises:
A method for sending a text message, comprising the step of entering the subject of the above-mentioned written email as the subject of the above-mentioned text message, and entering the content of the above-mentioned written email as the content of the above-mentioned text message. In paragraph 1,
A method for sending a text message, further comprising the step of updating the mail application based on the transmission result for the text message. In the 12th paragraph, the step of updating the mail application is:
A step of returning the normal transmission result of the above text message to the above mail application; and
A method for sending a text message, comprising the step of updating the sent mailbox of the mail application based on the returned normal transmission result. In a device that sends text messages via a mail application,
A processor that identifies the recipient format of a mail created using the above mail application, and based on identifying that the recipient format is a mobile phone number, calls the text message API of the mobile phone, and generates a text message with the mobile phone number as the recipient using the text message API; and
A device for transmitting a text message, comprising a communication module for transmitting the generated text message. In a system that sends text messages via a mail application,
A mobile phone that identifies the recipient format of a mail created using the above mail application, and, based on identifying that the recipient format is a mobile phone number, calls the text message API of the mobile phone, creates a text message with the mobile phone number as the recipient using the text message API, and transmits the created text message; and
A system for transmitting a text message, including a server section that receives the text message and transmits the transmission result of the text message to the mobile phone. In Article 15,
The above server side is a system for transmitting a text message, which identifies whether the mobile phone number is a number registered with IMS (IP Multimedia Subsystem) and transmits the text message to a subscriber ID matching the mobile phone number based on the identification that it is registered with the IMS. In Article 16,
The above server section is a server operating in the IMS layer (IP Multimedia Core Network Subsystem Layer); and
A system for transmitting text messages, including a gateway operating at the Transport Layer. In Article 17,
The above server is a system for transmitting a text message, which performs the functions of P-CSCF and S-CSCF, but evaluates the initial filter criteria (IFC) using the S-CSCF. In Article 17,
A system for transmitting text messages, wherein the above gateway is an IP short message gateway (IP-SM-GW) that performs changing of the message type and reporting on the transmission result of the above text message.

Images