Method for transferring business message and electronic device therefor

Abstract

Disclosed is an electronic device comprising at least one communication circuit, at least one processor, and a memory. The electronic device may be configured to: receive a first rich communication services (RCS) business message via the at least one communication circuit; identify an event for sharing the first RCS business message; and transmit, to a network, retransmission request information for the first RCS business message on the basis of the identification of the event. The retransmission request information may be contained in a disposition notification response of the first RCS business message. The retransmission request information may include information on an entity with which the first RCS business message is to be shared.

Description

Method for delivering corporate messages and electronic device for the same

[0001] The embodiments disclosed in this document relate to a method for delivering a business message and an electronic device for the same.

[0002] Rich communication services (RCS) are services developed to replace existing short message services (SMS) and can support various forms of multimedia messages. RCS-based messaging can support a variety of features compared to existing SMS or multimedia message services (MMS). For example, RCS-based messaging can support high-resolution images and videos, file sharing, improved group chat features, and typing indicators.

[0003] RCS technical specifications are managed by the GSMA (Global System for Mobile Communications Association). RCS technical specifications support not only person-to-person (P2P) messages but also application-to-person (A2P) messages. For example, RCS business messaging can be used for business-to-client (B2C) messages. Companies can use RCS business messages to provide enhanced marketing services to a large number of customers. If RCS business messages are tampered with, the company's brand image may be degraded, and the brand image may be exploited for criminal activities such as fraud. To prevent tampering with RCS business messages, the senders of RCS business messages are strictly limited. Therefore, sharing of RCS business messages by recipients may be restricted.

[0004] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art in relation to the present disclosure.

[0005] An electronic device according to one embodiment disclosed in this document may include at least one communication circuit, at least one processor electrically connected to the at least one communication circuit and comprising at least one processing circuit, and a memory electrically connected to the at least one processor. The memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to use the at least one communication circuit to receive a first rich communication services (RCS) business message in accordance with the GSMA (global system for mobile communications association) standard, identify an event for sharing the first RCS business message, and, based on the identification of the event, transmit an instant message disposition notification (IMDN) containing retransmission request information of the first RCS business message to a transmitting node of the first RCS business message. The retransmission request information may include information of the sharing target.

[0006] A method for transmitting an RCS business message of an electronic device according to one embodiment disclosed in this document may include: receiving a first RCS business message in accordance with the GSMA (global system for mobile communications association) standard; identifying an event for sharing the first RCS business message; and, based on the identification of the event, transmitting an IMDN (instant message disposition notification) containing retransmission request information of the first RCS business message to a transmitting node of the first RCS business message. The retransmission request information may include information of the sharing target.

[0007] A computer-readable storage medium according to one embodiment disclosed in this document can store instructions that, when executed by a processor of an electronic device, enable the method for delivering the RCS business message to be performed.

[0008] At least one server configured to provide RCS according to an embodiment disclosed in this document may be configured to perform the following operations: receiving a transmission request for a first RCS corporate message from an external device; transmitting the first RCS corporate message to a first electronic device indicated by the first RCS corporate message based on the transmission request; receiving retransmission request information for the first RCS corporate message from the first electronic device; and transmitting a second RCS corporate message corresponding to the first RCS corporate message to a second electronic device based on the retransmission request information. The retransmission request information may be included in a disposition notification response of the first RCS corporate message.

[0009] A method for delivering corporate messages by at least one server according to an embodiment disclosed in this document may include: receiving a transmission request for a first RCS corporate message from an external device; transmitting the first RCS corporate message to a first electronic device indicated by the first RCS corporate message based on the transmission request; receiving retransmission request information for the first RCS corporate message from the first electronic device; and transmitting a second RCS corporate message corresponding to the first RCS corporate message to a second electronic device based on the retransmission request information. The retransmission request information may be included in a disposition notification response of the first RCS corporate message.

[0010] A computer-readable storage medium according to one embodiment disclosed in this document may store instructions that cause the at least one server to perform a method for delivering an RCS business message when executed by a processor of at least one server.

[0011] An electronic device according to one embodiment disclosed herein may include at least one communication circuit, at least one processor electrically connected to the at least one communication circuit and comprising at least one processing circuit, and a memory electrically connected to the at least one processor. The memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to use the at least one communication circuit to receive a message, receive a transmission input of the message to an external electronic device, and determine whether the type of the message is a specified type based on the reception of the input. When executed individually or collectively by the at least one processor, the instructions may cause the electronic device to transmit the message to an external electronic device if the type of the message is not a specified type, and to request the sender of the message to retransmit the message if the type of the message is a specified type.

[0012] A method for transmitting a message of an electronic device according to an embodiment disclosed in this document may include: receiving a message; receiving a transmission input of the message to an external electronic device; determining, based on the reception of the input, whether the type of the message is a specified type; transmitting the message by sending the message to the external electronic device when the type of the message is not the specified type; and requesting the sender of the message to retransmit the message when the type of the message is the specified type.

[0013] A computer-readable storage medium according to one embodiment disclosed in this document may store instructions that, when executed by a processor of an electronic device, cause a method for delivering a message to be performed.

[0014] FIG. 1 illustrates a network environment for providing RCS according to one embodiment.

[0015] FIG. 2 illustrates block diagrams of electronic devices according to one embodiment.

[0016] FIG. 3 illustrates a signal flow diagram for corporate message delivery according to one embodiment.

[0017] FIGS. 4a and 4b illustrate user interfaces (UIs) for corporate message delivery of an electronic device according to one embodiment.

[0018] FIG. 5a illustrates a signal flow diagram for corporate message retransmission according to one embodiment.

[0019] FIG. 5b illustrates a signal flow diagram for corporate message retransmission according to one embodiment.

[0020] FIG. 6 illustrates a retransmitted corporate message according to one embodiment.

[0021] FIG. 7a illustrates a signal flow diagram for a transmission notification following a successful transmission according to one embodiment.

[0022] FIG. 7b illustrates a signal flow diagram for a transmission notification following a transmission failure according to one embodiment.

[0023] FIG. 8a illustrates a flowchart of a method for requesting the retransmission of an RCS corporate message of an electronic device according to one embodiment.

[0024] FIG. 8b illustrates a flowchart of a message retransmission method of an electronic device according to one embodiment.

[0025] FIG. 9 illustrates a flowchart of a method for retransmitting an RCS enterprise message of an RCS platform according to one embodiment.

[0026] FIG. 10 is a block diagram of an exemplary electronic device capable of performing the operations described in this document.

[0027] In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components.

[0028] Hereinafter, various embodiments of the present invention are described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments and should be understood to include various modifications, equivalents, and / or alternatives of the embodiments of the present invention.

[0029] FIG. 1 illustrates a network environment for providing RCS according to one embodiment.

[0030] Referring to FIG. 1, an exemplary network environment for providing RCS may be described. In the example of FIG. 1, the network environment is described based on a plurality of user devices (e.g., first to third electronic devices (10a, 10b, 10c)), an RCS platform (20), a MaaP (messaging-as-a-platform) server (30), and a brand server (40). A person skilled in the art will understand that the network environment of FIG. 1 is exemplary and that embodiments of the present disclosure are not limited thereto. For example, the number of illustrated user devices is not limited to the number in FIG. 1. For example, a plurality of brand servers may exist, and the plurality of brand servers may communicate with the MaaP server (30) through a separate aggregator (not shown). In the example of FIG. 1, each component can be connected to communicate via any wired or wireless network (e.g., WLAN (wireless local area network), cellular network, and / or IP (internet protocol)).

[0031] For example, the network environment of FIG. 1 may include a first electronic device (10a), a second electronic device (10b), and a third electronic device (10c). Each of the first electronic device (10a), the second electronic device (10b), and the third electronic device (10c) may correspond to any user device. Although FIG. 1 depicts the first electronic device (10a), the second electronic device (10b), and the third electronic device (10c) in the form of a mobile phone, the embodiments of the present disclosure are not limited thereto. The first electronic device (10a), the second electronic device (10b), and / or the third electronic device (10c) may correspond to any user device that supports message services.

[0032] For example, the RCS platform (20) may include at least one server configured to provide RCS. The RCS platform (20) may support person-to-person (P2P) messaging. For example, an RCS message may be transmitted from a first electronic device (10a) to a third electronic device (10c). The RCS platform (20) may transmit an RCS message from the first electronic device (10a) to the third electronic device (10c) if the third electronic device (10c) supports RCS messaging.

[0033] The RCS platform (20) can support B2C (business-to-customer) messaging (e.g., application-to-person messaging). For example, the RCS platform (20) can transmit an RCS corporate message (90) sent by the brand server (40) to the first electronic device (10a) and the third electronic device (10c). The RCS platform (20) can receive a request to transmit the RCS corporate message (90) from the brand server (40) via the MaaP server (30). The brand server (40) may include any electronic device (e.g., client device) configured to communicate with the MaaP server (30). The brand server (40) may be referred to as any electronic device operated by the company. For example, the brand server (40) may include a chatbot operated by the company.

[0034] The MaaP server (30) can operate as an interface between the brand server (40) and the RCS platform (20). The MaaP server (30) may allow the sending of RCS enterprise messages only if the sender of the RCS enterprise message is a designated sender. For example, the designated sender may be set by an operator (e.g., a mobile network operator (MNO) and / or an RCS platform provider). In the example of FIG. 1, the MaaP server (30) is shown separately from the RCS platform (20), but the MaaP server (30) may be implemented as part of the RCS platform (20). The MaaP server (30) may be operated, for example, by the provider of the RCS platform (20).

[0035] In the example of FIG. 1, the user of the first electronic device (10a) may wish to share an RCS corporate message (90) with the second electronic device (10b). In this case, since the sending of the RCS corporate message (90) by the end user is restricted, the first electronic device (10a) may transmit the contents of the RCS corporate message (90) to the second electronic device (10b) using a P2P (person-to-person) message rather than a corporate message. Accordingly, some of the contents of the RCS corporate message (90) may be excluded or transmitted to the second electronic device (10b) without maintaining the format. In this case, the user of the second electronic device (10b) may not be able to use the main functions of the RCS corporate message (90). Additionally, there is a possibility that some of the contents of the RCS corporate message (90) may be altered. The user of the first electronic device (10a) may alter some of the contents of the RCS corporate message (90) and transmit the altered message to the second electronic device (10b). In this case, the credibility of the company associated with the brand server (40) may be used for fraud and / or spam.

[0036] Hereinafter, methods for sharing RCS corporate messages may be described with reference to FIGS. 2 through 11. The sharing of RCS corporate messages according to an embodiment of the present disclosure can prevent tampering with the message through retransmission by the MaaP server (30) and / or the brand server (40). By preventing tampering, the brand image of the company can be preserved and users can be protected from criminal acts. The sharing of RCS corporate messages according to an embodiment of the present disclosure can reduce the risk of personal information being leaked to the company. The sharing of RCS corporate messages according to an embodiment of the present disclosure can notify the first electronic device (10a) of the result of message delivery. The sharing of RCS corporate messages according to an embodiment of the present disclosure can enable promotion to potential customers by users by facilitating the sharing of RCS corporate messages among users.

[0037] FIG. 2 illustrates block diagrams of electronic devices according to one embodiment.

[0038] With reference to FIG. 2, electronic devices associated with the transmission and reception of RCS enterprise messages of the present disclosure may be described. For example, the electronic device (10) of FIG. 2 may correspond to the first electronic device (10a), the second electronic device (10b), and / or the third electronic device (10c) of FIG. 1.

[0039] According to one embodiment, the electronic device (10) may include a processor (120), memory (130), a display (160), and / or a communication circuit (190). The configurations of the electronic device (10) described above are exemplary, and each configuration may consist of one module and / or multiple modules. The structure of the electronic device (10) shown in FIG. 2 is exemplary, and the embodiments of this document are not limited thereto. For example, the electronic device (10) may further include configurations not shown in FIG. 2 (e.g., configurations of the electronic device (1000) of FIG. 10). For example, the electronic device (10) may not include at least some of the configurations shown in FIG. 2.

[0040] The processor (120) may include at least one processing circuit. For example, the processor (120) may control various configurations of the electronic device (10) so that the electronic device (10) performs various operations. For example, the processor (120) may correspond to the processor (1010) of FIG. 10. For example, the operations of the electronic device (10) described below may be referred to as being performed by the processor (120). The processor (120) may perform various operations of the electronic device (10) by executing one or more instructions stored in memory (130). The processor (120) may control the electronic device (10) so that the electronic device (10) performs various operations by executing instructions stored in memory (130). The processor (120) may include one processor or a plurality of processors. For example, the processor (120) may include an application processor (AP), a communication processor (CP), and / or a modem. In one example, the processor (120) may be implemented as a single chipset or multiple chipsets.

[0041] The processor (120) may be electrically, operatively, or functionally connected to the memory (130), display (160), and / or communication circuit (190). In the present disclosure, when one component is “operatively” connected to another component, it may mean that the component is connected to enable the other component to operate. For example, the component may enable the other component by transmitting a control signal to the other component directly or through another component. In the present disclosure, when one component is “functionally” connected to another component, it may mean that the component is connected to enable the function of the other component. For example, the component may enable the function of the other component by transmitting a control signal to the other component directly or through another component.

[0042] For example, the memory (130) may be implemented as a single chip or chipset with the processor (120). For example, the memory (130) may be implemented as a separate chip from the processor (120). In one example, the memory (130) may correspond to the memory (1020) of FIG. 10. As described above, the memory (130) may store instructions (e.g., computer programs or program code) that are executable by the processor (120).

[0043] The display (160) may include at least one pixel configured to display an image. In one example, the display (160) may include a plurality of displays. For example, the display (160) may include a left-eye display and a right-eye display. The display (160) may include a front display and / or a rear display. The display (160) may include at least one of a see-through display, a flexible display, a rollable display, a foldable display and / or a rigid display. In one example, the display (160) may include at least one projector for projecting an image.

[0044] The communication circuit (190) may include at least one communication circuit. In one example, the communication circuit (190) may include any configurations for transmitting and receiving wireless signals. For example, the communication circuit (190) may correspond to the communication circuit (1060) of FIG. 10. The communication circuit (190) may transmit and / or receive signals using an antenna (not shown) of the electronic device (10). For example, the communication circuit (190) may convert the received signal into a baseband signal and transmit it to the processor (120). For example, the communication circuit (190) may convert the baseband signal received from the processor (120) into a radio frequency signal and transmit the converted radio frequency signal through the antenna. In one example, the communication circuit (190) may include an interface for transmitting and receiving wired signals. The processor (120) may communicate with an external electronic device by controlling the communication circuit (190).

[0045] According to one embodiment, the RCS platform (20) may include at least one server. For example, each of the at least one server included in the RCS platform (20) may include a processor (e.g., processor (120)), memory (e.g., memory (130)), and communication circuit (e.g., communication circuit (190)) as described above in relation to the electronic device (10). The configurations of the RCS platform (20) described below in relation to FIG. 2 may correspond to software modules implemented by executing instructions stored in memory by the processor.

[0046] According to one embodiment, the RCS platform (20) may include an application-to-person (A2P) message service (221), a person-to-person (P2P) message service (223), and a delivery message indicator (225). The application-to-person (A2P) message service (221) may be configured to provide services associated with an application-to-person (A2P) message that includes an RCS enterprise message. For example, the application-to-person (A2P) message service (221) may transmit an RCS enterprise message requested by the MaaP server (30) to a user (e.g., an electronic device (10)). The electronic device (10) may transmit an acknowledgment of receipt of the RCS enterprise message (e.g., a delivered notification response and / or a displayed notification response) to the RCS platform (20). The acknowledgment of receipt of the electronic device (10) can be processed by an A2P (application-to-person) message service (221). A P2P (person-to-person) message service (223) can be configured to process RCS messages between user terminals.

[0047] According to one embodiment, an electronic device (10) may transmit a request for retransmission of an RCS enterprise message to a network (e.g., an RCS platform (20)). For example, the electronic device (10) may transmit a retransmission request (e.g., a delivery notification) to the RCS platform (20) based on the identification of a designated event described below in relation to FIG. 3. In one example, the electronic device (10) may transmit a retransmission request to the RCS platform (20) using a response to a disposition notification of an RCS enterprise message (e.g., an instant message disposition notification (IMDN)).

[0048] According to one embodiment, a forwarding message indicator (225) may be configured to process a retransmission request (e.g., a message containing retransmission request information). For example, when a retransmission request for an RCS enterprise message is received from an electronic device (10), an A2P (application-to-person) message service (221) may delegate or forward the retransmission request to the forwarding message indicator (225). The forwarding message indicator (225) may transmit the retransmission request to a MaaP server (30). In one example, the forwarding message indicator (225) may convert the retransmission request based on a server-to-server interface and transmit the converted retransmission request to a MaaP server (30). The conversion of the retransmission request may include a conversion of the format. The retransmission request of the electronic device (10) may be described later in relation to FIG. 3.

[0049] According to one embodiment, the MaaP server (30) may include at least one server. For example, each of the at least one server included in the MaaP server (30) may include a processor (e.g., processor (120)), memory (e.g., memory (130)), and communication circuit (e.g., communication circuit (190)) as described above in relation to the electronic device (10). The configurations of the MaaP server (30) described below in relation to FIG. 2 may correspond to software modules implemented by executing instructions stored in memory by the processor.

[0050] According to one embodiment, the MaaP server (30) may include a message service (231) and a forwarding message service (233). The message service (233) may operate as an interface between the brand server (40) and the MaaP server (30) and an interface between the MaaP server (30) and the RCS platform (20). The message service (231) may receive a retransmission request (e.g., a converted retransmission request) from, for example, the RCS platform (20) (e.g., a forwarding message indicator (225)). When the message service (231) receives a retransmission request, it may delegate or forward the retransmission request to the forwarding message service (233).

[0051] According to one embodiment, the forwarding message service (233) may be configured to process a retransmission request. For example, the forwarding message service (233) may generate a retransmission RCS corporate message corresponding to the RCS corporate message indicated by the retransmission request and transmit the retransmission RCS corporate message to the RCS platform (20) through the message service (231). The retransmission of the RCS corporate message by the forwarding message service (233) may be described later in relation to FIG. 5a. For example, the forwarding message service (233) may request the brand server (40) to retransmit the RCS corporate message indicated by the retransmission request. In this case, the forwarding message service (233) may anonymize at least some of the information for retransmission (e.g., information of the target device). The forwarding message service (233) may store information for decrypting the anonymized information. For example, the brand server (40) may generate a retransmission RCS corporate message based on a request from the forwarding message service (233) and request the MaaP server (30) to transmit the retransmission RCS corporate message. The forwarding message service (233) may decrypt the anonymized information of the retransmission RCS corporate message and transmit the retransmission RCS corporate message to the RCS platform (20) through the message service (231). The retransmission of the RCS corporate message by the RCS brand server (40) may be described later in relation to FIG. 5b.

[0052] According to one embodiment, the brand server (40) may include at least one electronic device. For example, each of the at least one electronic device included in the brand server (40) may include a processor (e.g., processor (120)), a memory (e.g., memory (130)), and a communication circuit (e.g., communication circuit (190)) as described above in relation to the electronic device (10). For example, the brand server (40) may generate a retransmitted RCS enterprise message based on a request from the MaaP server (30).

[0053] According to one embodiment, the RCS platform (20) can provide a message retransmission result to the electronic device (10). For example, the RCS platform (20) can provide a retransmission result to the electronic device (10) as described below in relation to FIG. 7a and / or FIG. 7b.

[0054] In the present disclosure, the term “retransmission” may include “forwarding.” For example, “sharing” of a message may be achieved through retransmission or forwarding. A “sharing request” may include a retransmission request, a forwarding request, and / or any request to consequently cause a message to be shared. Additionally, the retransmission or forwarding of a message may include the retransmission or forwarding of a message identical to the previously transmitted message, as well as the transmission or forwarding of a message that differs from the previously transmitted message in at least a part.

[0055] Hereinafter, operations related to the operations of FIG. 2 may be described with reference to FIG. 3 through 7b. For convenience of explanation, in the examples of FIG. 3 through 7b, it may be assumed that the first electronic device (10a) of FIG. 2 requests the sharing of an RCS enterprise message to the second electronic device (10b). Unless otherwise stated, the description of FIG. 2 may apply equally to the operations described below.

[0056] FIG. 3 illustrates a signal flow diagram for corporate message delivery according to one embodiment.

[0057] Referring to FIGS. 2 and FIGS. 3, according to one embodiment, the first electronic device (10) can transmit retransmission request information for an RCS corporate message for sharing an RCS corporate message.

[0058] In operation 305, the brand server (40) may send a message transmission request to the MaaP server (30). For example, the message transmission request may include the content of an RCS enterprise message and / or recipient information of an RCS enterprise message. For example, the recipient information may include identification information of the first electronic device (10a) (e.g., phone number, account information, and / or MSISDN (mobile station international subscriber directory number)).

[0059] In operation 310, the MaaP server (30) may send a reception response to the brand server (40) in response to the reception of a message transmission request. The reception response may include an identifier (e.g., msgId) assigned to the requested RCS enterprise message. In one example, the transmission of the reception response may be omitted. For example, the MaaP server (30) may process the message transmission request using the message service (231).

[0060] In operation 315, the MaaP server (30) can send a message transmission request to the RCS platform (20). For example, the MaaP server (30) can send a message transmission request to the RCS platform (20) using the message service (231). In one example, the MaaP server (30) can reformat a message transmission request from the brand server (40) and send it to the RCS platform (20). The message transmission request sent from the MaaP server (30) to the RCS platform (20) may include an identifier assigned to the RCS corporate message (e.g., msgId), recipient information (e.g., identification information of the first electronic device (10a)), and / or the content of the RCS corporate message.

[0061] In operation 320, the RCS platform (20) can transmit a message to the first electronic device (10a) based on a message transmission request. The RCS platform (20) can perform operations corresponding to the message transmission request, for example, using an A2P message service (221). The RCS platform (20) can transmit an RCS corporate message to the first electronic device (10a) using recipient information of the message transmission request. The transmitted RCS corporate message may include an identifier assigned to the RCS corporate message (e.g., msgId), recipient information (e.g., identification information of the first electronic device (10a)), and / or the content of the RCS corporate message.

[0062] In operation 325, the first electronic device (10a) may transmit a delivered notification response based on the reception of an RCS enterprise message. The delivered notification response (e.g., delivered IMDN) may include information indicating that the RCS enterprise message has been successfully received by the first electronic device (10a). Table 1 below shows an example of the content of a delivered notification response.

[0063] <imdn xmlns=" / "urn:ietf:params:xml:ns:imdn / ""> <message-id>4dbf7832-2e6c-4fc6-b2bb-2b689d < / message-id> <datetime> 2019-01-07T23:15:17.609Z < / datetime> <delivery-notification> <status> <delivered / > < / status> < / delivery-notification> < / imdn>

[0064] In Table 1, <message-id>The field represents the identifier assigned to the RCS corporate message transmitted to the first electronic device (10a). <datetime>The field indicates the time when the RCS corporate message was received by the first electronic device (10a). <delivery-notification>The field indicates the reception status of the RCS enterprise message. In the example in Table 1, the reception status of the RCS enterprise message is successful. <delivered>It can be indicated as such. If the reception status indicates a reception failure, the RCS platform (20) may attempt to resend the corresponding RCS corporate message.

[0065] The first electronic device (10a) may provide a notification to the user of the first electronic device (10a) instructing the user to receive the message upon receipt of an RCS corporate message. The notification may include at least some of the information contained in the RCS corporate message.

[0066] In operation 330, the first electronic device (10a) can display a received message. For example, the first electronic device (10a) can display a received message through a display (160) when a user input requesting the display of a received message is received, or when the display of a received message is allowed by user settings. In one example, the first electronic device (10a) can display a message from an external electronic device that is communicationally connected to the first electronic device (10a).

[0067] In operation 335, the first electronic device (10a) may transmit a displayed notification response (e.g., displayed IMDN) to the RCS platform (20) based on a message display. Table 2 below shows an example of the content of a displayed notification response.

[0068] <imdn xmlns=" / "urn:ietf:params:xml:ns:imdn / ""> <message-id> 4dbf7832-2e6c-4fc6-b2bb-2b689d < / message-id> <datetime> 2019-01-07T23:18:37.456Z < / datetime> <display-notification> <status> <displayed / > < / status> < / display-notification> < / imdn>

[0069] In Table 2, <message-id>The field represents the identifier assigned to the RCS corporate message transmitted to the first electronic device (10a). <datetime>The field indicates the time when the RCS corporate message was displayed by the first electronic device (10a). <display-notification>The field indicates the display status of the RCS enterprise message. In the example in Table 2, the display status of the RCS enterprise message can be displayed as a displayed state.

[0070] For example, the RCS platform (20) can transmit information based on delivered notification responses and / or displayed notification responses to the MaaP server (30) and / or the brand server (40). The sender of the RCS enterprise message (e.g., the brand server (40)) can recognize the status of receipt of the message based on the delivered notification response. The sender of the RCS enterprise message (e.g., the brand server (40)) can recognize the status of the recipient's message read based on the displayed notification response. For example, the RCS platform (20) can process the delivered notification response and / or displayed notification response using the A2P message service (221).

[0071] Similarly, in person-to-person (P2P) RCS messages, a delivered notification response and / or a displayed notification response may be used for acknowledgment and / or read confirmation. For example, a first electronic device (10a) may send an RCS message to another electronic device. When a delivered notification response for the message is received, the first electronic device (10a) may display an acknowledgment indicator (e.g., information indicating the number of the recipient) for the sent RCS message. The first electronic device (10a) may change the acknowledgment indicator based on the displayed notification response. For example, if a displayed notification response is received from three of four recipients, the first electronic device (10a) may display a receipt acknowledgment indicator according to the number of recipients (e.g., 1) that have not yet sent a displayed notification response. When a displayed notification response is received from all recipients, the first electronic device (10a) may stop displaying the receipt acknowledgment indicator.

[0072] In operation 340, the electronic device (10a) can identify an event. For example, the event may include an event directing the sharing of a received RCS message. According to one embodiment, the event may be identified in at least one of the following cases: when a user input requesting the sharing of an RCS corporate message is received, when a sender associated with the RCS corporate message corresponds to a specified sender, or when the RCS corporate message contains a specified text. For example, as described below in relation to FIGS. 4a and 4b, the first electronic device (10a) can identify an event when a user input requesting sharing is received. For example, the first electronic device (10a) can support automatic sharing of an RCS corporate message. When an RCS corporate message is received from a sender stored in memory (130), or when the RCS corporate message contains a keyword stored in memory (130), the first electronic device (10a) can identify an event.

[0073] According to one embodiment, in operation 345, the first electronic device (10a) may transmit a delivery notification (e.g., retransmission request information) to the RCS platform (20) based on the identification of an event. For example, the delivery notification may include a message having a format similar to a delivered notification response and / or a displayed notification response. For example, the delivery notification may include any IMDN having a delivery notification field. The delivery notification may include information about the sharing target, encryption information, entity information, and / or status information. For example, the delivery notification may include information about the sharing target of the RCS enterprise message. For example, the delivery notification may include information indicating whether the information about the sharing target is encrypted. For example, the delivery notification may include information about the entity to perform the retransmission of the RCS enterprise message. For example, a notification may include status information of the notification. Table 3 below shows an example of a notification.

[0074] <imdn xmlns=" / "urn:ietf:params:xml:ns:imdn / ""> <message-id> 4dbf7832-2e6c-4fc6-b2bb-2b689d < / message-id> <datetime> 2019-01-07T23:15:17.609Z < / datetime> <forward-notification> <indicator> <maap / > < / indicator> <status> <request / > < / status> <target> +8210112345678< / target> <anonymize> false < / anonymize> < / forward-notification> < / imdn>

[0075] In Table 3, <message-id>The field represents an identifier assigned to an RCS corporate message requested to be delivered by the first electronic device (10a). <datetime>The field indicates the time when the notification was sent by the first electronic device (10a). <forward-notification>The field is information about the sharing target (e.g., <target>), encryption information (e.g.: <anonymize>), entity information (e.g.: <indicator>), and / or status information (e.g., <status>It may include ). As described above <forward-notification>As an example, the information in the field may be omitted, at least some of the remaining information excluding the information of the sharing target.

[0076] For example, the information of the sharing target may include an identifier (e.g., phone number and / or MSISDN) of another electronic device to which the RCS corporate message will be shared. For example, encryption information may indicate whether to perform encryption on the information of the sharing target. If the encryption information indicates encryption (e.g., true), the RCS platform (20) and / or MaaP server (30) may encrypt at least a portion of the information of the sharing target in the creation of the message to be transmitted. For example, the entity information may be set to a first value (e.g., brand) or a second value (e.g., MaaP) indicating the entity to retransmit the RCS corporate message. If set to the second value, the RCS corporate message may be retransmitted by the MaaP server (30), as described below in relation to FIG. 5a. If set to the first value, the RCS corporate message may be retransmitted by the brand server (40), as described below in relation to FIG. 5b.

[0077] For example, status information may indicate the delivery status and / or delivery request of an RCS enterprise message. If the status information is set to a third value (e.g., request), the delivery notification may refer to the delivery request of the RCS enterprise message. If the status information is set to a fourth value (e.g., forwarded), the delivery notification may indicate that the RCS enterprise message has been successfully delivered. If the status information is set to a fifth value, the delivery notification may indicate that the delivery of the RCS enterprise message has failed.

[0078] The format of the notification described in connection with Table 3 is provided as an example, and the embodiments of the present disclosure are not limited thereto. For example, <forward-notification>The names of fields and internal information are exemplary and may differ from the examples in Table 3. For example, <forward-notification>At least some of the information within the field may be omitted. For example, <forward-notification>At least some of the fields are optional information, and the RCS platform (20) can ignore the optional information according to the policy.

[0079] FIGS. 4a and 4b illustrate user interfaces (UIs) for corporate message delivery of an electronic device according to one embodiment.

[0080] Referring to FIGS. 2, FIG. 3 and FIG. 4a, according to one embodiment, a first electronic device (10a) can display an RCS corporate message (e.g., operation 330 of FIG. 3). For example, the first electronic device (10a) can display a first screen (401). The first screen (401) may correspond to any screen containing a received RCS corporate message.

[0081] For example, the first screen (401) may include sender information (405) of an RCS corporate message (410) and the RCS corporate message (410). The sender information (405) may include, for example, a sender name (e.g., Company ABCDE) and / or a sender description (e.g., Free coupon, voucher, etc.). The RCS corporate message (410) may include an image (411), text (413), and an interaction object (415). When input for the interaction object (415) is received, the first electronic device (10a) may perform a set action (e.g., open a webpage) for the interaction object (415).

[0082] For example, the first electronic device (10) may receive user input (491) for a point in an RCS corporate message (410). For example, the user input (491) may include a long-press input, a touch input, and / or a double tap. Based on the user input (491), the first electronic device (10) may provide a second screen (402).

[0083] For example, the first electronic device (10) may display an additional action UI (420) that includes actions associated with a selected RCS corporate message (410). In the example of FIG. 4a, the additional action UI (420) is shown to provide menus associated with copy (e.g., copy text), select (e.g., select text), and forward, but the additional action UI (420) may include other menus in addition to the menus described above.

[0084] Referring to FIGS. 2, FIGS. 3 and FIG. 4b, according to one embodiment, a first electronic device (10a) may receive an input (492) for the delivery of an additional action UI (420). Based on the reception of the input (492), the first electronic device (10a) may provide a third screen (403). For example, the third screen (403) may include contact information of another electronic device to which the RCS corporate message (410) will be shared. For example, the third screen (403) may include a first contact (431), a second contact (432), and a third contact (433). For example, when the first electronic device (10a) receives an input for the first contact (431), it may share the RCS corporate message (410) with the second electronic device (10b) corresponding to the first contact (431). For example, the first electronic device (10a) can transmit a forwarding notification to the network (e.g., operation 345 of FIG. 3) which includes the identifier of the RCS corporate message (410) and the information of the first contact (431).

[0085] FIG. 5a illustrates a signal flow diagram for corporate message retransmission according to one embodiment.

[0086] Referring to FIG. 2 and FIG. 5a, according to one embodiment, the RCS platform (20) may receive a forwarding notification in accordance with operation 345. For example, the forwarding notification may be for an RCS enterprise message and may be processed by an A2P message service (221). The A2P message service (221) may process the forwarding notification based on a field within the received message. A field in the received message that corresponds to a retransmission request (e.g., <forward-notification>If it includes ), the A2P message service (221) can deliver a delivery notification to the delivery message indicator (225).

[0087] According to one embodiment, in operation 505, the RCS platform (20) may send a forwarding request to the MaaP server (30) based on the reception of a forwarding notification. For example, the RCS platform (20) may generate a forwarding request by converting information from the forwarding notification. For example, the generation of the forwarding request may be performed by a forwarding message indicator (225). The forwarding request may include identification information of a destination device (e.g., a second electronic device (10b)), an identifier of the RCS enterprise message to be shared, and / or information of a forwarding request device (e.g., a first electronic device (10a)). Table 4 below may show a forwarding request generated in response to the forwarding notification of Table 3.

[0088] {"messageContact”:{"userContact”: "+821099999999”},"RCSMessage”: {."forward”: {"msgId”: "4dbf7832-2e6c-4fc6-b2bb”,"target”: "+821012345678”}}}

[0089] In the example of Table 4, the forward request may include information of the forward request device (e.g., "userContact"), information of the RCS enterprise message (e.g., msgId), and information of the sharing target (e.g., "target"). The forward request may indicate that the message is a forward of a specific message. For example, the forward message indicator (225) may send the forward request to the MaaP server (30).

[0090] According to one embodiment, in operation 510, the MaaP server (30) can generate a forwarding message based on the reception of a forwarding request. For example, the forwarding request may be received by a message service (231). Based on the reception of the forwarding request, the message service (231) may forward the forwarding request to a forwarding message service (223). The forwarding message service (223) may generate a forwarding message based on the forwarding request.

[0091] For example, the MaaP server (30) can retrieve an RCS corporate message that has already been transmitted to the first electronic device (10a) based on the information of the RCS corporate message included in the forwarding request. The MaaP server (30) can generate a forwarding message (e.g., a retransmitted RCS corporate message) using the previously transmitted RCS corporate message. The recipient of the forwarding message can be set to a recipient specified by the forwarding request (e.g., the second electronic device (10b)).

[0092] According to one embodiment, the MaaP server (30) may modify a portion of the content of a previously transmitted RCS corporate message when generating a forwarding message. For example, the MaaP server (30) may include information of the forwarding requester (e.g., information of the first electronic device (10a)) in the forwarding message. For example, the MaaP server (30) may use the retrieved RCS corporate message as the body of the forwarding message and add a tag and / or header indicating that it is a forwarded RCS corporate message. For example, the information added in the example of Table 4 may be "Forwarded from +821099999999". At this time, the identification information of the generated forwarding message (e.g., msgId 2) may be different from the identification information (e.g., msgId 1) of the RCS corporate message that is the subject of sharing (e.g., the message of operation 320 of FIG. 3). By setting the identification information of the transmitted message and the identification information of the message to be shared differently, the sharing of corporate messages by users can be recorded. For example, the brand server (40) can provide a reward to users who have shared corporate messages among users.

[0093] In operation 515, the MaaP server (30) may request the transmission of a forward message. For example, a forward message generated by the forward message service (233) may be transmitted to the RCS platform (20) (e.g., A2P message service (221)) via the message service (231). The request for transmission of a forward message may include information (e.g., phone number and / or MSISDN) of the forward message to be transmitted and the destination device (e.g., second electronic device (10b)).

[0094] In operation 520, the RCS platform (20) may transmit a forwarding message to the second electronic device (10b) based on the reception of a request to transmit a forwarding message. For example, the forwarding message may include an RCS corporate message that is to be shared (e.g., the message of operation 320 of FIG. 3). The forwarding message may further include information of the electronic device requesting the sharing (e.g., the first electronic device (10a)).

[0095] In the example of FIG. 5a, a delivery message may be generated by the MaaP server (30). For example, the MaaP server (30) may generate a delivery message according to the entity information in the delivery request. The MaaP server (30) may generate a delivery message according to the entity information in the delivery request or according to the settings. If the entity information indicates the brand server (40) or if the entity generating the delivery message is designated as the brand server (40) by the server settings, the delivery message may be generated by the brand server (40) as described below in relation to FIG. 5b.

[0096] FIG. 5b illustrates a signal flow diagram for corporate message retransmission according to one embodiment.

[0097] Referring to FIG. 2 and FIG. 5b, according to one embodiment, the RCS platform (20) may receive a forwarding notification in accordance with operation 345. For example, the forwarding notification may be for an RCS enterprise message and may be processed by an A2P message service (221). The A2P message service (221) may process the forwarding notification based on a field within the received message. A field in the received message that corresponds to a retransmission request (e.g., <forward-notification>If it includes ), the A2P message service (221) can deliver a delivery notification to the delivery message indicator (225).

[0098] In the example of FIG. 5b, the notification may include, for example, the contents of Table 5 below.

[0099] <imdn xmlns=" / "urn:ietf:params:xml:ns:imdn / ""> <message-id> 4dbf7832-2e6c-4fc6-b2bb-2b689d < / message-id> <datetime> 2019-01-07T23:15:17.609Z < / datetime> <forward-notification> <indicator> <brand / > < / indicator> <status> <request / > < / status> <target> +8210112345678< / target> <anonymize> true < / anonymize> < / forward-notification> < / imdn>

[0100] In the example of Table 5, unlike the example of Table 4, the entity information was changed to a brand server (40) and anonymization was performed. Below, the procedure for transmitting a message according to the example of Table 5 can be described.

[0101] According to operation 505, the MaaP server (30) may receive a forwarding request. For example, the MaaP server (30) may receive a forwarding request described above in relation to Table 5.

[0102] According to one embodiment, in operation 525, the MaaP server (30) may anonymize the forwarding request. For example, the MaaP server (30) may anonymize at least a portion of the information to be shared. Table 6 shows one example of an anonymized forwarding request.

[0103] {"messageContact”:{"userContact”: "+821099999999”},"RCSMessage”: {."forward”: {"msgId”: "4dbf7832-2e6c-4fc6-b2bb”,"target”: "+821111111111”}}}

[0104] In the example of Table 6, unlike in Table 4, the information of the destination device may be anonymized (e.g., +821111111111). Anonymization may be performed by the delivery message service (233). The MaaP server (30) may store information for decrypting the anonymized information at the time of anonymization. According to one embodiment, the MaaP server (30) may store a mapping between the anonymized information (e.g., +821111111111) and the original information (e.g., +821012345678). The MaaP server (30) may decrypt the anonymized information (e.g., token) using the mapping information. Through the anonymization of personal information, the risk of personal information being exposed to the company (e.g., brand server (40)) may be reduced. For example, the mapping information may be stored in the MaaP server (30) for a specified period of time. The specified period may be referenced as the delivery request availability time.

[0105] According to one embodiment, in operation 530, the MaaP server (30) may send an anonymized delivery request to the brand server (40). For example, the delivery message service (233) may send an anonymized delivery request to the brand server (40) through the message service (231). The anonymized delivery request may include anonymized information and information about the message to be shared.

[0106] According to one embodiment, in operation 535, the brand server (40) can generate a forwarding message. For example, the brand server (40) can retrieve an RCS corporate message that has been sent to the first electronic device (10a) based on information of the RCS corporate message included in the anonymized forwarding request (e.g., information of the message to be shared). The brand server (40) can generate a forwarding message (e.g., a retransmitted RCS corporate message) using the previously sent RCS corporate message. The recipient of the forwarding message can be set to a recipient specified by the forwarding request (e.g., an anonymized recipient).

[0107] According to one embodiment, the brand server (40) may modify a portion of the content of a previously transmitted RCS corporate message when generating a delivery message. For example, the brand server (40) may include information of the delivery requester (e.g., information of the first electronic device (10a)) in the delivery message. In the example of Table 6, the information of the first electronic device (10a) that requested sharing (e.g., +821099999999) is not anonymized, but according to one example, the information of the electronic device requesting sharing may also be anonymized. In this case, the generated delivery message may include information of the electronic device requesting sharing (e.g., the first electronic device (10a)) in an anonymized state and information of the electronic device that became the target of sharing (e.g., the second electronic device (10b)). In this case, the MaaP server (30) may decrypt the information of the sharing request electronic device during the decryption process described later and include the information of the requester of the transmission (e.g., information of the first electronic device (10a)) in the transmission message. In this case, the MaaP server (30) may store mapping information for decrypting the information of the sharing request electronic device when performing anonymization.

[0108] According to one embodiment, in operation 540, the brand server (540) may send a message transmission request for a generated delivery message to the MaaP server (30). For example, the message transmission request may include a delivery message containing anonymized information (e.g., a token). The anonymized information may include, for example, recipient information of the delivery message.

[0109] In operation 545, the MaaP server (30) may send a reception response to the brand server (40) in response to the reception of a message transmission request. The reception response may include an identifier (e.g., msgId 2) assigned to the requested transmission message. In one example, the transmission of the reception response may be omitted. For example, the MaaP server (30) may process the message transmission request using the message service (231).

[0110] According to one embodiment, in operation 550, the MaaP server (30) may decrypt an anonymized delivery message based on the reception of a message transmission request. The delivery message received from the brand server (40) may contain encrypted information. The MaaP server (30) may decrypt the anonymized information using mapping information generated during the anonymization (525) process.

[0111] After decoding the anonymized information, in operation 515, the MaaP server (30) may request the transmission of a forward message to the RCS platform (20). For example, a forward message generated by the forward message service (233) may be transmitted to the RCS platform (20) (e.g., A2P message service (221)) via the message service (231). The request to transmit a forward message may include the forward message to be transmitted and information (e.g., phone number and / or MSISDN) of the destination device (e.g., second electronic device (10b)). For example, the request to transmit a forward message may include information of the requesting electronic device (e.g., first electronic device (10a)). In operation 520, the RCS platform (20) may transmit the forward message to the second electronic device (10b) based on the reception of the request to transmit a forward message.

[0112] FIG. 6 illustrates a retransmitted corporate message according to one embodiment.

[0113] Referring to FIGS. 2 and FIGS. 6, according to one embodiment, the second electronic device (10b) may provide a retransmitted corporate message (e.g., the forwarded message of FIGS. 5a and 5b). As described above, the retransmitted corporate message may include information from the sharing request electronic device (e.g., the first electronic device (10a)). Referring to the screen (601), the second electronic device (10b) may display sharer information (610) based on the information from the sharing request electronic device. For example, when the second electronic device (10b) receives identification information (e.g., phone number or MSIDSN) of the first electronic device (10a), the second electronic device (10b) may identify a name corresponding to the identification information from the contacts stored in the second electronic device (10b). The second electronic device (10b) may display sharer information (610) based on the identified name (e.g., Bob).

[0114] In the example of FIG. 6, since the RCS corporate message (410) is retransmitted by the brand server (40) or the MaaP server (30), the RCS corporate message (410) may not be tampered with. Additionally, the sender information (405) of the RCS corporate message (410) may be maintained without being changed. Due to the retransmission of the RCS corporate message (410), the reliability of the RCS corporate message (410) may be increased. Also, since it is retransmitted by the brand server (40) or the MaaP server (30) rather than through person-to-person transmission, elements such as the interaction object (415) may be shared with the second electronic device (10b) as is.

[0115] FIG. 7a illustrates a signal flow diagram for a delivery notification following a successful delivery according to one embodiment.

[0116] Referring to FIGS. 2 and FIGS. 7a, according to one embodiment, the RCS platform (20) may provide a delivery notification of a delivery message (e.g., the delivery message of operation 520 of FIGS. 5a and 5b). In the example of FIG. 7a, it may be assumed that the delivery of the delivery message was successfully performed.

[0117] For example, according to operation 520, the second electronic device (10b) may receive a delivery message. According to one embodiment, in operation 705, based on the reception of the delivery message, the second electronic device (10b) may transmit a delivered notification to the RCS platform (20). The delivered notification (e.g., delivered IMDN) may include information indicating that the delivery message (e.g., RCS enterprise message) has been successfully received by the second electronic device (10b). For example, the delivered notification may include information similar to the information described above in relation to Table 1. The delivered notification of operation 705 may include an identifier of the delivery message (e.g., msgId 2).

[0118] According to one embodiment, in operation 710, the RCS platform (20) may transmit a delivered notification to the MaaP server (30). According to one embodiment, in operation 715, the MaaP server (30) may transmit a delivery response to the RCS platform (20) based on the reception of the delivered notification. The delivery response may include, for example, identification information (e.g., msgId) of the message to be delivered (e.g., message of operation 320 of FIG. 3) and information (e.g., phone number or MSIDSN) of the electronic device requesting sharing (e.g., first electronic device (10a)). The MaaP server (30) may store mapping information between the delivered message and the message to be delivered. The MaaP server (30) can identify information of the message to be delivered and the electronic device requesting sharing that corresponds to the identification information (e.g., msgId 2) of the message to be delivered within the delivered notification, and can generate a delivery response based on the identified information.

[0119] According to one embodiment, in operation 720, the RCS platform (20) may transmit a delivery notification to the first electronic device (10a) based on the reception of a delivery response. For example, the delivery notification of operation 720 may have the same format as the delivery notification of FIG. 345. The status of the delivery notification of operation 720 may indicate a delivery result. For example, Table 7 may represent the delivery notification of operation 720.

[0120] <imdn xmlns=" / "urn:ietf:params:xml:ns:imdn / ""> <message-id> 4dbf7832-2e6c-4fc6-b2bb-2b689d < / message-id> <datetime> 2019-01-07T23:45:17.609Z < / datetime> <forward-notification> <indicator> <maap / > < / indicator> <status> <forwarded / > < / status> <target> +821099999999< / target> <anonymize> false< / anonymize> < / forward-notification> < / imdn>

[0121] In Table 7, <message-id>The field represents an identifier assigned to an RCS enterprise message requested for delivery by the first electronic device (10a). State information (e.g., <status>It can indicate that a sharing message has been delivered. The information of the target device can be set to the information of the first electronic device (10a) that requested the sharing.

[0122] For example, the RCS platform (20) can store a delivery notification received from the first electronic device (10a) for a specified period of time. The RCS platform (20) can generate a delivery notification of operation 720 by changing some items of the delivery notification received from the first electronic device (10a).

[0123] FIG. 7b illustrates a signal flow diagram for a notification of transmission failure according to one embodiment.

[0124] Referring to FIGS. 2 and FIGS. 7b, according to one embodiment, the RCS platform (20) may provide a delivery notification of a delivery message (e.g., the delivery message of operation 520 of FIGS. 5a and 5b). In the example of FIG. 7b, it may be assumed that the delivery of the delivery message failed.

[0125] For example, according to operation 345, the RCS platform (20) may receive a delivery notification from the first electronic device (10a). In operation 755, the RCS platform (20) may send a delivery request to the MaaP server (30) based on the reception of the delivery notification. For example, the RCS platform (20) may generate a delivery request by converting the information of the delivery notification. For example, the generation of the delivery request may be performed according to operation 505 of FIG. 5a.

[0126] In operation 760, the MaaP server (30) can generate a forwarding message. For example, the MaaP server (30) can generate a forwarding message according to operation 510 of FIG. 5a. In the example of FIG. 7b, the forwarding message is generated by the MaaP server (30), but a person skilled in the art will understand that the forwarding message can be generated by the brand server (40) as in the example of FIG. 5b.

[0127] In operation 765, the MaaP server (30) may request the transmission of a forwarding message to the RCS platform (20). For example, the description of operation 765 may be referenced by the description of operation 515 in FIG. 5a.

[0128] According to one embodiment, in operation 770, the RCS platform (20) may transmit a transmission notification to the first electronic device (10a) indicating a failure in the transmission of a transmission message. For example, the RCS platform (20) may transmit a transmission notification to the first electronic device (10a) indicating a failure at any point in time when the message transmission fails. For example, the RCS platform (20) may transmit a transmission notification to the first electronic device (10a) indicating a failure in response to the reception of the transmission notification of operation 345.

[0129] The notification of operation 770 may include information similar to that described above in relation to Table 7, provided, however, that the “status” may indicate failed.

[0130] FIG. 8a illustrates a flowchart of a method for requesting the retransmission of an RCS corporate message of an electronic device according to one embodiment.

[0131] Referring to FIGS. 2 and FIG. 8a, according to one embodiment, an electronic device (10) can perform sharing of a received RCS corporate message. For example, the electronic device (10) can share an RCS corporate message by performing the operations described above in relation to FIGS. 1 through 7b.

[0132] The operations described below in relation to FIG. 8a may be referred to as operations of the electronic device (10) of FIG. 2. The order of the operations described below in relation to FIG. 8a is an example, and embodiments of the present disclosure are not limited thereto. For example, at least some of the operations may be performed differently from the order of FIG. 8a or may be performed substantially simultaneously with other operations of FIG. 8a.

[0133] According to one embodiment, an electronic device (10) may include at least one communication circuit (190), at least one processor (120) electrically connected to the at least one communication circuit and comprising at least one processing circuit, and a memory (130) electrically connected to the at least one processor. The memory (130) may store instructions that cause the electronic device (10) to perform the operations described below when executed individually or collectively by the at least one processor.

[0134] According to one embodiment, in operation 805, the electronic device (10) can receive a first RCS (rich communication services) business message (e.g., operation 320 of FIG. 3). For example, the electronic device (10) can receive the first RCS business message using a communication circuit (190).

[0135] In operation 810, the electronic device (10) can identify an event for sharing the first RCS corporate message (e.g., operation 340 of FIG. 3). For example, the electronic device (10) can identify an event when a user input requesting the sharing of the RCS corporate message is received, when the sender associated with the RCS corporate message corresponds to a specified sender, and / or when the RCS corporate message contains specified text.

[0136] In operation 815, the electronic device (10) may transmit retransmission request information of the first RCS enterprise message to the network based on the identification of the event (e.g., operation 345 of FIG. 3). For example, the retransmission request information may be included in the disposition notification response (e.g., delivery notification) of the first RCS enterprise message. The disposition notification response may include an instant message disposition notification (IMDN).

[0137] For example, the electronic device (10) can cause the entity that sent the first RCS corporate message (e.g., MaaP server (30) and / or brand server (40)) to send a second RCS corporate message (e.g., forwarding message of FIG. 5a and 5b) corresponding to the first RCS corporate message by sending retransmission request information. For example, the retransmission request information may include information indicating the entity (e.g., entity information). For example, the retransmission request information may include an identifier of the first RCS corporate message. For example, the retransmission request information may include information of the sharing target (e.g., phone number or MSISDN of the second electronic device (10b)).

[0138] The second RCS corporate message may include information about the electronic device (10) that requested the sharing of the first RCS corporate message.

[0139] According to one embodiment, the electronic device (10) may receive a delivery notification indicating the result of delivering the second RCS corporate message (e.g., operation 720 of FIG. 7a or operation 775 of FIG. 7b).

[0140] FIG. 8b illustrates a flowchart of a message retransmission method of an electronic device according to one embodiment.

[0141] Referring to FIG. 2 and FIG. 8b, according to one embodiment, an electronic device (10) can transmit (e.g., share) a received message. For example, the electronic device (10) may vary the method of transmitting the message based on the type of message.

[0142] The operations described below in relation to FIG. 8b may be referred to as operations of the electronic device (10) of FIG. 2. The order of the operations described below in relation to FIG. 8b is an example, and embodiments of the present disclosure are not limited thereto. For example, at least some of the operations may be performed differently from the order of FIG. 8b, or may be performed substantially simultaneously with other operations of FIG. 8b.

[0143] According to one embodiment, an electronic device (10) may include at least one communication circuit (190), at least one processor (120) electrically connected to the at least one communication circuit and comprising at least one processing circuit, and a memory (130) electrically connected to the at least one processor. The memory (130) may store instructions that cause the electronic device (10) to perform the operations described below when executed individually or collectively by the at least one processor.

[0144] According to one embodiment, in operation 855, the electronic device (10) may receive a message. For example, the message may include an RCS corporate message or any format other than an RCS corporate message (e.g., SMS, MMS, or person-to-person RCS message). For example, the electronic device (10) may receive a first RCS corporate message using a communication circuit (190).

[0145] In operation 860, the electronic device (10) may receive a forwarding input of a received message. For example, the electronic device (10) may receive an input requesting forwarding (e.g., sharing) of the received message to an external electronic device (e.g., a second electronic device).

[0146] In operation 865, the electronic device (10) can determine whether the type of the message is a specified type based on the reception of the forward input. For example, the specified type may include an RCS corporate message. The electronic device (10) can identify the type of the received message based on the format and / or header information of the message. If the received message is an RCS corporate message, the electronic device (10) can determine that the type of the message is a specified type. If the received message is not an RCS corporate message, the electronic device (10) can determine that the type of the message is not a specified type.

[0147] If the type of message is not a specified type (e.g., operation 865-NO), the electronic device in operation 870 may deliver the message to an external electronic device (e.g., a second electronic device). If the type of message is SMS or MMS, the electronic device (10) may deliver the message by sending the same message as the received message to the external electronic device. If the type of message is an RCS peer-to-peer message, the electronic device (10) may deliver the message to the external electronic device through the RCS platform (20). The RCS platform (20) may transmit the RCS peer-to-peer message sent by the electronic device (10) to the external electronic device through the P2P message service (223).

[0148] If the type of the message is of a specified type (e.g., operation 865-YES), in operation 875, the electronic device (10) may request the retransmission of the message. For example, the electronic device (10) may transmit information requesting the retransmission of an RCS enterprise message to the network (e.g., operation 345 of FIG. 3). The electronic device (10) may request the sender of the message to retransmit the message.

[0149] For example, retransmission request information may be included in the disposition notification response (e.g., delivery notification) of an RCS enterprise message. The disposition notification response may include an instant message disposition notification (IMDN).

[0150] For example, the electronic device (10) can cause the entity that sent the first RCS corporate message (e.g., MaaP server (30) and / or brand server (40)) to send a second RCS corporate message (e.g., forwarding message of FIG. 5a and 5b) corresponding to the received RCS corporate message by sending retransmission request information. For example, the retransmission request information may include information indicating the entity (e.g., entity information). For example, the retransmission request information may include an identifier of the first RCS corporate message. For example, the retransmission request information may include information of the sharing target (e.g., phone number or MSISDN of the second electronic device (10b)).

[0151] The second RCS corporate message may include information about the electronic device (10) that requested the sharing of the first RCS corporate message.

[0152] According to one embodiment, the electronic device (10) may receive a delivery notification indicating the result of delivering the second RCS corporate message (e.g., operation 720 of FIG. 7a or operation 775 of FIG. 7b).

[0153] FIG. 9 illustrates a flowchart of a method for retransmitting an RCS enterprise message of an RCS platform according to one embodiment.

[0154] Referring to FIGS. 2 and FIG. 9, according to one embodiment, an RCS platform (20) can transmit RCS enterprise messages. The operations described below may be performed by at least one server by having at least one processor included in at least one server of the RCS platform (20) execute instructions.

[0155]

[0156] The operations described below in relation to FIG. 9 may be referred to as operations of the RCS platform (20) of FIG. 2. Hereinafter, the RCS platform (20) may include a MaaP server (30). The order of the operations described below in relation to FIG. 9 is an example, and the embodiments of the present disclosure are not limited thereto. For example, at least some of the operations may be executed differently from the order of FIG. 9a or may be executed substantially simultaneously with other operations of FIG. 9.

[0157] According to one embodiment, in operation 905, the RCS platform (20) may receive a request to send a first RCS corporate message from an external device (e.g., a brand server (40)) (e.g., operations 305 and 315 of FIG. 3).

[0158] In operation 910, the RCS platform (20) can transmit the first RCS enterprise message to the first electronic device (10a) directed by the first RCS enterprise message based on the transmission request (e.g., operation 320 of FIG. 3).

[0159] In operation 915, the RCS platform (20) may receive retransmission request information for the first RCS enterprise message from the first electronic device (10a) (e.g., operation 345 of FIG. 3). For example, the retransmission request information may be included in the disposition notification response of the first RCS enterprise message. The disposition notification response may include an instant message disposition notification (IMDN).

[0160] In one example, the RCS platform (20) determines whether the received IMDN contains retransmission request information and, if it contains retransmission request information, can identify the retransmission request information.

[0161] In operation 920, the RCS platform (20) can transmit a second RCS corporate message corresponding to the first RCS corporate message to the second electronic device (10b) based on retransmission request information (e.g., operation 520 of FIG. 5a and 5b). The RCS platform (20) can identify the identifier of the first RCS corporate message and the contact (e.g., phone number or MSISDN) of the second electronic device (10b) based on retransmission request information.

[0162] For example, the RCS platform (20) can identify the first RCS corporate message using the identifier of the first RCS corporate message and create a second RCS corporate message (e.g., operation 510 of FIG. 5a) by including information of the first electronic device (10a) (e.g., phone number or MSISDN) in the first RCS corporate message.

[0163] For example, the RCS platform (20) may transmit a transmission request information requesting the transmission of a first RCS corporate message to an external device (e.g., brand server (40)) (operations 505, 525, 530 in FIG. 5b). Based on the transmission of the transmission request information, the RCS platform (20) may receive a transmission request for a second RCS corporate message from the external device (e.g., brand server (40)) (e.g., operation 540 in FIG. 5b). Based on the reception of the transmission request for the second RCS corporate message, the RCS platform (20) may transmit the second RCS corporate message to the second electronic device (10b) (e.g., operation 520 in FIG. 5b). In one example, the RCS platform (20) may anonymize information of the second electronic device (10b) (e.g., operation 525 in FIG. 5b) before transmitting the transmission request information to the external device.

[0164] FIG. 10 is a block diagram of an exemplary electronic device (1000) capable of performing the operations described in this document.

[0165] Referring to FIG. 10, the electronic device (1000) may be one of various forms of electronic devices, such as a notebook (1090), smartphones (1091) having various form factors (e.g., a bar-type smartphone (1091-1), a foldable-type smartphone (1091-2), or a sliderable (or rollable)-type smartphone (1091-3)), a tablet (1092), a cellular phone (not shown), and other similar computing devices (not shown). The components, their relationships, and their functions illustrated in FIG. 10 are illustrative only and are not intended to limit the implementations described or claimed herein. The electronic device (1000) may be referred to as a mobile device, a user device, a multifunction device, a portable device, or a server.

[0166] The electronic device (1000) may include components comprising at least one processor (1010) (hereinafter referred to as processor (1010)), at least one memory (1020) (hereinafter referred to as memory (1020)), at least one display (1040) (hereinafter referred to as display (1040)), at least one image sensor (1050) (hereinafter referred to as image sensor (1050)), at least one communication circuit (1060) (hereinafter referred to as communication circuit (1060)), and / or at least one sensor (1070) (hereinafter referred to as sensor (1070)). The components are merely exemplary. For example, the electronic device (1000) may include other components (e.g., power management integrated circuitry (PMIC), audio processing circuit, antenna, rechargeable battery, or input / output interface). For example, some components may be omitted from the electronic device (1000). For example, some components can be integrated into a single component.

[0167] The processor (1010) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (1010) may include at least one electrical circuit and may process instructions (or programs, data, etc.) stored in memory (1020) individually or collectively in a distributed manner. The processor (1010) may include a processor assembly comprising one or more processing circuits. The processor (1010) may include any processing circuit that is operative to control the performance and operations of one or more components of the electronic device (1000) (e.g., memory (1020), display (1040), image sensor (1050), communication circuit (1060), and / or sensor (1070)). For example, a processor (1010) (e.g., an application processor (AP)) may be implemented as a system on chip (SoC) (e.g., a single chip or a chipset). For example, the processor (1010) may be implemented as a plurality of cores (or at least one core circuit), a plurality of chips, or a plurality of chipsets. For example, the processor (1010) may include one or more processing circuits. For example, the processor (1010) may include one or more processing circuits configured to perform the various functions of the present disclosure individually and / or collectively. As an example without limitation, at least a portion of the processor (1010) may be included in a first chip of the electronic device (1000), and at least another portion of the processor (1010) may be included in a second chip of the electronic device (1000) different from the first chip of the electronic device (1000).

[0168] For example, the processor (1010) may include a central processing unit (CPU) (1011), a graphics processing unit (GPU) (1012), a neural processing unit (NPU) (1013), an image signal processor (ISP) (1014), a display controller (1015), a memory controller (1016), a storage controller (1017), a communication processor (CP) (1018), and / or a sensor interface (1019). These components of the processor (1010) are merely exemplary. For example, the processor (1010) may include other components. For example, some components of the processor (1010) may be omitted from the processor (1010). For example, some components of the processor (1010) may be included as separate components of the electronic device (1000) outside of the processor (1010). For example, some components of the processor (1010) (e.g., memory controller (1016)) may be included in other components (e.g., at least part of memory (1020), an interface (e.g. available for connection to at least one component of the electronic device (100)), a display (1040) and / or an image sensor (1050)).

[0169] The processor (1010) may cause other components of the electronic device (1000) to perform various operations by executing instructions stored in memory (1020). The CPU (1011) (or central processing circuit) may be configured to control the components of the processor (1010) based on the execution of instructions stored in memory (1020) (e.g., volatile memory (1021) and / or non-volatile memory (1022)). The GPU (1012) (or graphics processing circuit) may be configured to execute parallel operations (e.g., rendering). The NPU (1013) (or neural processing circuit, or AI (artificial intelligence) chip) may be configured to execute operations for an artificial intelligence model (e.g., convolution computation). An ISP (1014) (or image signal processing circuit) may be configured to process a raw image acquired through an image sensor (1050) into a format suitable for a component within an electronic device (1000) or a component of a processor (1010). A display controller (1015) (or display control circuit, or DPU (display processing unit)) may be configured to process an image acquired from a CPU (1011), GPU (1012), ISP (1014), or memory (1020) (e.g., volatile memory (1021)) into a format suitable for a display (1040). A memory controller (1016) (or memory control circuit) may be configured to control reading data from the volatile memory (1021) and writing data to the volatile memory (1021). The storage controller (1017) (or storage control circuit) may be configured to control reading data from non-volatile memory (1022) and writing data to non-volatile memory (1022).The CP (1018) (communication processing circuit) may be configured to process data obtained from a component of the processor (1010) into a format suitable for transmitting to another electronic device via the communication circuit (1060), or to process data obtained from another electronic device via the communication circuit (1060) into a format suitable for processing by the component of the processor (1010). For example, the communication circuit (1060) may include one or more communication circuits. The sensor interface (1019) (or sensing data processing circuit, sensor hub) may be configured to process data regarding the state of the electronic device (1000) and / or the state around the electronic device (1000), obtained through the sensor (1070), into a format suitable for the component of the processor (1010).

[0170] Memory (1020) may include one or more storage media (or one or more storage devices). For example, memory (1020) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, a flash memory, a permanent memory such as ROM (read-only memory) (e.g., non-volatile memory (1022)), a semi-permanent memory such as RAM (random access memory) (e.g., volatile memory (1021)), any other suitable type of storage (or storage assembly), or any combination thereof. Memory (1020) may include a cache memory, which is one or more different types of memory used to temporarily store data for a function or feature of the electronic device (1000). As an example not limited to, the cache memory may be included within the processor (1010). The memory (1020) may be fixedly embedded within the electronic device (1000) or incorporated into one or more suitable types of components (e.g., a SIM (subscriber identity module) card and / or an SD (secure digital) card) that can be repeatedly inserted into and removed from the electronic device (1000).

[0171] For example, memory (1020) may store one or more software applications, such as operating system (or system) software applications, firmware software applications, driver software applications, plugin (e.g., add-in, add-on, and / or applet) software applications, and / or any other suitable software applications. For example, the one or more software applications may include instructions executable by the processor (1010). For example, memory (1020) may store instructions that can be called by an application programming interface (API). For example, memory (1020) may store instructions within a library.< / status> < / status> < / indicator> < / anonymize> < / target> < / datetime> < / datetime> < / delivered> < / datetime>

Claims

1. In an electronic device (10, 10a, 1000), At least one communication circuit (190); At least one processor (120) electrically connected to the above at least one communication circuit and including at least one processing circuit; and It includes a memory (130) electrically connected to at least one processor, and When the above memory is executed individually or collectively by the above at least one processor, the electronic device: Using the above-mentioned at least one communication circuit, a first RCS (rich communication services) business message in accordance with GSMA (global system for mobile communications association) standards is received, and Identify an event for sharing the above-mentioned first RCS enterprise message, and Based on the identification of the above event, instructions are stored to transmit an IMDN (instant message disposition notification) containing retransmission request information of the first RCS enterprise message to the transmitting node of the first RCS enterprise message. The above retransmission request information is an electronic device that includes information of a sharing target.

2. In Paragraph 1, An electronic device that, when the above instructions are executed individually or in combination by the at least one processor, causes the electronic device to transmit the retransmission request information, thereby causing the entity (30, 40) that transmitted the first RCS corporate message to transmit a second RCS corporate message corresponding to the first RCS corporate message to an external electronic device (10b) corresponding to the information of the shared target.

3. In Paragraph 2, The above second RCS enterprise message is an electronic device that includes information of the electronic device that requested the sharing of the above first RCS enterprise message.

4. In Paragraph 2, When the above instructions are executed individually or in combination by the at least one processor, the electronic device: An electronic device that receives a forwarding notification indicating the result of the delivery of the above-mentioned second RCS enterprise message.

5. In Paragraph 2, An electronic device comprising information indicating the entity, wherein the above retransmission request information.

6. In Paragraph 2, The above retransmission request information further includes the identifier of the above first RCS enterprise message, and The information of the above-mentioned sharing target is an electronic device including the phone number of the above-mentioned external electronic device.

7. In Paragraph 1, The above event comprises at least one of the following: when a user input requesting the sharing of the first RCS corporate message is received; when a sender associated with the first RCS corporate message corresponds to a specified sender; or when the first RCS corporate message includes a specified text.

8. As a method for delivering RCS business messages of at least one server (20, 30) configured to provide RCS (rich communication services), The operation of receiving a request to transmit a first RCS corporate message from an external device (40); The operation of transmitting the first RCS corporate message to the first electronic device (10a) directed by the first RCS corporate message based on the transmission request; The operation of receiving retransmission request information of the first RCS corporate message from the first electronic device; and The operation includes transmitting a second RCS corporate message corresponding to the first RCS corporate message to the second electronic device (10b) based on the above retransmission request information, and The above retransmission request information is included in the disposition notification response of the above first RCS enterprise message, in an RCS enterprise message delivery method.

9. In Paragraph 8, The above processing notification response is an RCS enterprise message delivery method including IMDN (instant message disposition notification).

10. In Paragraph 9, The operation of receiving retransmission request information of the above-mentioned first RCS enterprise message is: An operation to determine whether the retransmission request information is included in the IMDN above; and An RCS enterprise message delivery method comprising, when the above retransmission request information is included, an operation for identifying the above retransmission request information.

11. In Paragraph 10, The operation of transmitting the above second RCS corporate message is: A method for delivering an RCS corporate message, comprising the operation of identifying the identifier of the first RCS corporate message and the contact of the second electronic device from the retransmission request information.

12. In Paragraph 11, The operation of transmitting the above second RCS corporate message is: An operation of identifying the first RCS corporate message using the identifier of the first RCS corporate message; and A method for delivering an RCS corporate message, comprising the operation of including information of the first electronic device in the first RCS corporate message to generate the second RCS corporate message.

13. In Paragraph 10, The operation of transmitting the above second RCS corporate message is: The operation of transmitting delivery request information to the external device (40) requesting the delivery of the first RCS corporate message; Based on the transmission of the above transmission request information, the operation of receiving a transmission request for the second RCS corporate message from the external device (40); and A method for delivering an RCS corporate message, comprising the operation of transmitting the second RCS corporate message to the second electronic device based on the reception of a request to transmit the second RCS corporate message.

14. In Paragraph 13, The operation of transmitting the above-mentioned transmission request information is, An operation to anonymize information of the second electronic device; and An RCS enterprise message delivery method comprising the operation of transmitting the delivery request information, which includes the information of the anonymized second electronic device, to the external device.

Images