Method for detecting forgery of forwarded message and electronic device therefor

Abstract

A message authentication method of at least one server is disclosed. The message authentication method may comprise the operations of: generating a first signature for an RCS business message by using a signing key and a designated encryption scheme; transmitting, to a first electronic device (10a), a first RCS business message including the RCS business message, the signing key, and information on the designated encryption scheme; receiving, from a second electronic device (10b), an IMDN including an identifier of the first RCS business message and a second signature generated by the second electronic device; and authenticating a second RCS message associated with the IMDN by comparing the first signature and the second signature.

Description

Method for detecting forgery of a transmitted message and electronic device for the same

[0001] The embodiments disclosed in this document relate to a method for detecting forgery of a forwarded 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 forged and / or altered, the company's brand image may be degraded, and the brand image may be used for criminal activities such as fraud.

[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] At least one server configured to provide RCS according to an embodiment disclosed in this document may be configured to perform the following operations: generating a first signature for an RCS business message using a signature key and a specified encryption method; transmitting a first RCS business message, which includes information on the RCS business message, the signature key, and the specified encryption method, to a first electronic device (10a); receiving an IMDN (instant message disposition notification) from a second electronic device (10b), which includes an identifier of the first RCS business message and a second signature generated by the second electronic device; and performing authentication of a second RCS message associated with the IMDN by comparing the first signature and the second signature.

[0006] A message authentication method by at least one server according to an embodiment disclosed in this document may include: generating a first signature for an RCS business message using a signing key and a specified encryption method; transmitting a first RCS business message, which includes information on the RCS business message, the signing key, and the specified encryption method, to a first electronic device (10a); receiving an IMDN (instant message disposition notification) from a second electronic device (10b), which includes an identifier of the first RCS business message and a second signature generated by the second electronic device; and performing authentication of a second RCS message associated with the IMDN by comparing the first signature and the second signature.

[0007] 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 message authentication when executed by a processor of at least one server.

[0008] 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, the electronic device, using the at least one communication circuit, receive a second RCS message generated from an external electronic device based on a first RCS business message, generate a signature for the second RCS message using a signature key and encryption method included in the second RCS message, and transmit an IMDN containing the signature to an RCS server for authentication of the second RCS message.

[0009] A method for authenticating a message of an electronic device according to an embodiment disclosed in this document may include receiving a second RCS message generated based on a first RCS business message from an external electronic device, generating a signature for the second RCS message using a signature key and an encryption method included in the second RCS message, and transmitting an IMDN containing the signature to an RCS server for authentication of the second RCS message.

[0010] A computer-readable storage medium according to one embodiment disclosed in this document may store instructions that perform a method for message authentication when executed by a processor of an electronic device.

[0011] An electronic device according to one embodiment disclosed in this document may include a communication circuit, at least one processor including at least one processing circuit, and a memory electrically connected to the at least one processor and storing instructions. When the instructions are executed collectively or in combination by the at least one processor, the electronic device may: receive a first message from a first external device to be delivered to a first user device, transmit a second message including the first message and first signature information to the first user device through a network associated with the electronic device, receive a third message from a second user device including second signature information and associated with the second message, and determine whether the delivered message associated with the third message is forged based on the first signature information of the second message and the second signature information of the third message.

[0012] A method for authenticating a message of an electronic device according to an embodiment disclosed in this document may include: receiving a first message to be delivered to a first user device from a first external device; transmitting a second message including the first message and first signature information to the first user device through a network associated with the electronic device; receiving a third message from a second user device that includes second signature information and is associated with the second message; and determining whether a delivery message associated with the third message is forged based on the first signature information of the second message and the second signature information of the third message.

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

[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. 5 illustrates a signal flow diagram for detecting forgery of a transmitted message according to one embodiment.

[0019] FIG. 6 illustrates a transmitted RCS message according to one embodiment.

[0020] FIG. 7 is a flowchart of an RCS message authentication method of at least one server according to one embodiment.

[0021] FIG. 8 is a flowchart of an RCS message authentication method of an electronic device according to one embodiment.

[0022] FIG. 9 illustrates a flowchart of an RCS message transmission method of an electronic device in one embodiment.

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

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

[0025] 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.

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

[0027] 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 RCS platform (20) may include a MaaP server (30). 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) network).

[0028] 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.

[0029] 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 (91) may be transmitted from a first electronic device (10a) to a second electronic device (10b). The RCS platform (20) may transmit an RCS message (91) from the first electronic device (10a) to the second electronic device (10b) if the second electronic device (10b) supports RCS messaging.

[0030] 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.

[0031] 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).

[0032] In the example of FIG. 1, a user of the first electronic device (10a) may want to share an RCS enterprise message (90) with the second electronic device (10b). In this case, the first electronic device (10a) may reconstruct the RCS enterprise message (90) based on the user request to generate an RCS message (91). For example, the first electronic device (10) may reconstruct the RCS enterprise message (90) to generate an RCS message (91) that includes at least some of the content of the RCS enterprise message (90). For example, the RCS message (91) may not include user response tools (e.g., interaction buttons and / or links) among the content of the RCS enterprise message (90). The RCS message (91) includes at least some of the content of the RCS enterprise message (90), but may have the following differences. The sender of the RCS corporate message (90) is a specific brand, but the sender of the RCS message (91) can correspond to the first electronic device (10a). The RCS corporate message (90) is an A2P (application-to-person) message, but the RCS message (91) can be a P2P message.

[0033] Although the RCS message (91) is not an actual RCS corporate message (90), because it contains the content of the RCS corporate message (90), the user of the second electronic device (10b) may mistake the RCS message (91) for being sent by the brand. If the received RCS message (91) is forged and / or altered, the RCS message (91) may be used for crimes (e.g., spam and / or smishing) that exploit the brand image. Additionally, the brand image of the associated brand may be degraded by the forged and / or altered RCS message (91). For example, during the reconstruction process of the RCS corporate message (91), parts of the content of the RCS corporate message (91) may be altered. For example, an RCS corporate message that was not sent by the brand server (40) may be delivered to the second electronic device (10b) as the RCS message (91). For example, a sender of a spam message may request the first electronic device (10a) to transmit an RCS message (91). In this case, because the RCS message (91) has a format similar to an RCS corporate message, the user of the second electronic device (10b) may mistake the RCS message (91) for a message sent by a specific brand. The user of the second electronic device (10b) may have false trust in the content of the RCS message (91) due to trust in the specific brand. Additionally, if there is a relationship between the users of the first electronic device (10a) and the second electronic device (10b), the user of the second electronic device (10b) may have false trust in the content of the RCS message (91) due to trust in the user of the first electronic device (10a).

[0034] Hereinafter, methods for detecting forgery of an RCS message may be described with reference to FIGS. 2 through 10. According to an embodiment of the present disclosure, an RCS corporate message (90) may include information on a signature key and an encryption method. For example, a MaaP server (30) may store a signature (e.g., a digital signature) generated using a signature key and an encryption method. When an RCS message (91) transmitted based on the RCS corporate message (90) is received, a second electronic device (10b) may transmit the signature of the received RCS message (91) to the MaaP server (30). The MaaP server (30) may determine whether the RCS message (91) is forged by comparing the received signature with the stored signature. Through the detection of forgery, forgery of the RCS corporate message (90) can be prevented. Through the prevention of forgery, the corporate brand image can be preserved and users can be protected from criminal acts.

[0035] In the disclosure below, the term forgery may include tampering. Forgery may include altering at least a portion of the content of a received RCS corporate message (90). Forgery may include delivering an RCS corporate message that was not sent by the brand server (40). In the disclosure, the term signature may include a digital signature. In the disclosure, the term “sharing of a message” may include the delivery of a message. The delivery of a message may include the transmission of a message reconstructed to include the body of the original message. The retransmission of a message may include the delivery of a message identical to the previously transmitted message, as well as the transmission or delivery of a message that differs in at least a portion from the previously transmitted message.

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

[0037] Referring to FIG. 2, electronic devices associated with the transmission and reception of RCS 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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).

[0042] 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.

[0043] 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).

[0044] 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.

[0045] 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., 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.

[0046] According to one embodiment, a delivery message indicator (225) can handle a disposition message (e.g., a delivered notification response and / or a displayed notification response) for a delivered RCS message. For example, an electronic device (10) can receive an RCS message delivered from an external electronic device. Based on the reception of the delivered RCS message, the electronic device (10) can send a disposition message (e.g., a delivered notification response and / or a displayed notification response) for the delivered RCS message to an RCS platform (20). The delivery message indicator (225) can send the received disposition message to a MaaP server (30). As described below, the MaaP server (30) can use the disposition message to determine whether the delivered RCS message is forged.

[0047] 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.

[0048] According to one embodiment, the MaaP server (30) may include a message service (231), an alert service (233), and a key-signature database (235). It may include a delivery 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). According to one embodiment, the alert service (233) may determine whether the delivered RCS message is forged. For example, the alert service (233) may determine whether the delivered RCS message is forged by using the signature of the disposition message and the signature of the key-signature database (235). If forgery of the delivered RCS message is detected, the alert service (233) may transmit information indicating the forgery of the delivered RCS message to the brand server (40) and / or electronic device (10). According to one embodiment, the key-signature DB (235) may store information associated with each RCS corporate message. For example, the information associated with the RCS corporate message may include the identifier of the transmitted RCS corporate message and / or the signature of the RCS corporate message. The identifier of a specific RCS corporate message may be mapped to the signature of the RCS corporate message and stored in the key-signature DB (235).

[0049] 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 request the transmission of an RCS corporate message from the MaaP server (30).

[0050] With reference to FIGS. 1 and FIGS. 2, a forgery detection method according to an embodiment of the present disclosure may be described. For example, a first electronic device (10a) may receive an RCS corporate message (90) and transmit the received RCS corporate message (90) to a second electronic device (10b). In this case, the first electronic device (10a) may reconstruct the RCS corporate message (90) into an RCS message (91) and then transmit the RCS message (91) to the second electronic device (10b).

[0051] For example, an RCS corporate message (90) may be transmitted based on a request from a brand server (40). When a request from the brand server (40) is received, the MaaP server (30) may generate a signature key for signing the RCS corporate message (90). For example, the MaaP server (30) may generate a random signature key using a known method. The MaaP server (30) may generate a signature (e.g., a hash value) by signing the body of the RCS corporate message (90) using the generated signature key. For example, the MaaP server (30) may generate a signature using a specified encryption method. The specified encryption method may include a known one-way encryption method (e.g., a hash algorithm and / or a MAC (message authentication code) algorithm). The MaaP server (30) may store the identifier of the RCS corporate message (90) and the generated signature in a key-signature DB (235).

[0052] The MaaP server (30) may include information on a signing key and a specified encryption method in an RCS corporate message (90). The MaaP server (30) may transmit the RCS corporate message (90) containing information on a signing key and a specified encryption method to the RCS platform (20). The A2P message service (221) of the RCS platform (20) may transmit the received RCS corporate message (90) to the first electronic device (10a).

[0053] The first electronic device (10a) can share the received RCS corporate message (90) with the second electronic device (10b). For example, the first electronic device (10a) can share the RCS corporate message (90) with the second electronic device (10b) by reconstructing the received RCS corporate message (90) and delivering the RCS message (91). The RCS message (91) may include information on the identifier of the RCS corporate message (90), the signature key of the RCS corporate message (90), and the specified encryption method of the RCS corporate message. For example, the identifier of the RCS message (91) and the identifier of the RCS corporate message (90) may be different. The first electronic device (10a) can transmit the RCS message (91) to the RCS platform (20) for delivery of the RCS message (91).

[0054] An RCS platform (20) (e.g., P2P message service (223)) can transmit an RCS message (91) to a second electronic device (10b). The second electronic device (10b) can receive an RCS message (91) from the RCS platform (20). Based on the reception of the RCS message (91), the second electronic device (10b) can transmit a delivered notification response (e.g., delivered IMDN (instant message disposition notification)) for the RCS message (91) to the RCS platform (20).

[0055] According to one embodiment, the delivered notification response may include a signature. For example, the second electronic device (10) may generate a signature by signing the body of the RCS message (91) using a signature key included in the RCS message (91). The second electronic device (10) may generate a signature according to information on a specified encryption method included in the RCS message (91). The second electronic device (10) may include the identifier of the RCS enterprise message (90) and the signature generated by the second electronic device (10a) in the delivered notification response.

[0056] The P2P message service (223) of the RCS platform (20) can receive a delivered notification response. If the delivered notification response contains information about the delivered RCS enterprise message (90), the delivered message indicator (235) can send the delivered notification response to the MaaP server (30).

[0057] The alert service (233) of the MaaP server (30) can determine whether the RCS message (91) is forged from the RCS enterprise message (90) by using the received delivery notification response. The alert service (233) can obtain the signature mapped to the RCS enterprise message (90) from the key-signature DB (235) by using the identifier of the RCS enterprise message (90) included in the delivery notification response. By comparing the signature stored in the key-signature DB (235) with the signature included in the delivery notification response, the alert service (233) can determine whether the RCS message (91) is forged. If the two signatures match, the alert service (233) can determine that the RCS message (91) is not forged. If the two signatures do not match, the alert service (233) can determine that the RCS message (91) is forged. If forgery of an RCS message (91) is detected, the alarm service (233) may transmit information instructing the brand server (40), the MNO (mobile network operator), and / or the second electronic device (10b) to forge the RCS message (91). A procedure for detecting forgery of an RCS message (91) may be described later in relation to FIGS. 3 to 5.

[0058] Hereinafter, operations related to the operations of FIG. 2 may be described with reference to FIG. 3 through 5. For convenience of explanation, in the examples of FIG. 3 through 5, it may be assumed that the first electronic device (10a) of FIG. 2 requests the sharing of an RCS enterprise message (90) to the second electronic device (10b). Unless otherwise stated, the description of FIG. 2 may apply equally to the operations described below. The operations described below are described with reference to RCS messages, but the embodiments of the present disclosure are not limited to RCS messages. For example, the method described below may be used in digital rights management (DRM) of a content manager. For example, when content is shared by a user, the content manager may determine whether the shared content is forged by comparing signatures.

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

[0060] Referring to FIGS. 2 and FIGS. 3, according to one embodiment, the first electronic device (10a) can transmit an RCS message (e.g., a forwarding message) reconstructed from an RCS corporate message for sharing an RCS corporate message.

[0061] 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)).

[0062] 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).

[0063] In operation 313, the MaaP server (30) can generate a message (e.g., an RCS enterprise message) based on the reception of a message transmission request. For example, the generation of the message can be performed by the message service (231). In one example, the MaaP server (30) can use a signature key associated with the brand server (40). In one example, the MaaP server (30) can generate a signature key based on the reception of a message transmission request. The MaaP server (30) can generate a signature for the message by signing the body of the message requested for transmission using the signature key. The MaaP server (30) can generate the signature according to a specified encryption method. The MaaP server (30) can store the identifier of the message and the generated signature (e.g., in the key-signature DB (235)). The MaaP server (30) can include information about the signature key and the encryption method in the generated message. For example, the MaaP server (30) can include information about the signature key and encryption method in the header of the message.

[0064] In one example, for signing a message, the MaaP server (30) may generate a signature for a portion of the body of the message. As described below in relation to operation 343, some components of the body of the original message may be changed and / or deleted during the process of generating the forwarded message. The MaaP server (30) may generate a signature using the remaining portion of the body excluding the components that may be changed and / or deleted.

[0065] A message generated by the MaaP server (30) may include a header and a body. For example, the generated message may have a message format of the CPIM (common presence and instant messaging) content type (e.g., a type defined by RFC 3862). For example, the header of the generated message may include information related to the destination, time of dispatch, message identifier, signature key, and / or signature method (e.g., signature algorithm). Table 1 below shows one example of a message header.

[0066] To:<sip:anonymous@anonymous.invalid> cc:<sip:anonymous@anonymous.invalid> DateTime: 2019-01-07T22:17:08.589ZNS: imdn <urn:ietf:params:imdn>imdn.Message-ID: VGGlhy188mimdn.Message-Signature-Key: jo98e-0fahj809-34b-p98hpisha8f9pj8ewhnpiouhjnf349imdn.Message-Signature-Algorithm: SHA256

[0067] In the example in Table 1, the To and cc fields represent recipient information. The DateTime field represents the time the message was sent. The NS (namespace) field represents the uniform resource identifier (URI) of the namespace. The imdn.Messga-ID field represents the identifier of the message (e.g., VGG1hy188m). The Imdn.Message-Signature-Key field represents information about the signature key to be used to sign the message (e.g., jo98e-0fahj809-34b-p98hpisha8f9pj8ewhnpiouhjnf349). The Imdn.Message-Signature-Algorithm can represent the encryption method to be used to sign the message (e.g., SHA256).

[0068] 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 a message service (231). A message transmission request sent from the MaaP server (30) to the RCS platform (20) may include an identifier assigned to the RCS enterprise message (e.g., msgId), recipient information (e.g., identification information of the first electronic device (10a)), a signature key, encryption method information, and / or the content of the RCS enterprise message.

[0069] 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)), a signature key, encryption method information, and / or the content of the RCS corporate message.

[0070] 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 was successfully received by the first electronic device (10a). Table 2 below shows an example of the content of a delivered notification response.

[0071] <imdn xmlns=" / "urn:ietf:params:xml:ns:imdn / ""> <message-id>VGGlhy188m < / message-id> <datetime> 2019-01-07T23:15:17.609Z < / datetime> <delivery-notification> <status> <delivered / > < / status> < / delivery-notification> < / imdn>

[0072] 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 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 RCS corporate message.

[0073] 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.

[0074] 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).

[0075] 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 3 below shows an example of the content of a displayed notification response.

[0076] <imdn xmlns=" / "urn:ietf:params:xml:ns:imdn / ""> <message-id> VGGlhy188m < / message-id> <datetime> 2019-01-07T23:18:37.456Z < / datetime> <display-notification> <status> <displayed / > < / status> < / display-notification> < / imdn>

[0077] In Table 3, <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 3, the display status of the RCS enterprise message can be displayed as a displayed state.

[0078] 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).

[0079] Similarly, in a person-to-person (P2P) RCS message, a delivered notification response and / or a displayed notification response may be used for acknowledgment of receipt and / or read acknowledgment. For example, as described below in relation to FIG. 5, when a first electronic device (10a) delivers an RCS message to a second electronic device (10b), the second electronic device (10b) may transmit a delivered notification response to an RCS platform (20).

[0080] In operation 340, the first electronic device (10a) can identify an event. For example, the event may include an event that directs 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.

[0081] In operation 343, the first electronic device (10a) may generate a forwarding message (e.g., an RCS message or a P2P RCS message) based on the identification of an event. For example, the first electronic device (10a) may generate a forwarding message by reconstructing a received message (hereinafter referred to as the original message). The first electronic device (10a) may remove at least a portion of the content included in the original message. For example, the first electronic device (10a) may generate a forwarding message by removing interaction elements (e.g., links and / or interaction affordances) from the body of the original message. For example, the forwarding message may include a P2P RCS message. The first electronic device (10a) may include the identifier and signature of the original message in the forwarding message. The identifier and signature of the original message may be included in the header or body of the forwarding message.

[0082] According to one embodiment, in operation 345, the first electronic device (10a) may include a request to transmit a transmission message to the RCS platform (20). For example, the request to transmit a transmission message may include a generated transmission message and recipient information (e.g., information of the second electronic device (10b)). As described below in relation to FIG. 5, the RCS platform (20) may transmit a transmission message to the second electronic device (10b) based on the reception of the request to transmit a transmission message.

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

[0084] Referring to FIGS. 2, FIG. 3 and FIG. 4a, according to one embodiment, a first electronic device (10a) can display an RCS corporate message (410) (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 the received RCS corporate message (410).

[0085] 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 an action set for the interaction object (415) (e.g., open a webpage).

[0086] 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).

[0087] 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.

[0088] Referring to FIGS. 2, FIGS. 3 and FIG. 4b, according to one embodiment, a first electronic device (10a) may receive an input (492) for delivery through an additional operation 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) (e.g., transmit the delivery message of FIG. 3). For example, the first electronic device (10a) can transmit a transmission request to a network (e.g., operation 345 of FIG. 3) that includes information of a first contact (431) and a forwarding message generated by reconstructing an RCS corporate message (410). During the process of reconstructing the message, the first electronic device (10a) can remove an interaction object (415) from the RCS corporate message (410).

[0089] FIG. 5 illustrates a signal flow diagram for detecting forgery of a transmitted message according to one embodiment.

[0090] Referring to FIGS. 2 and FIGS. 5, according to one embodiment, the RCS platform (20) may receive a request to transmit a forward message in accordance with operation 345. For example, the forward message may be an RCS message reconstructed from an RCS enterprise message and may be processed by a P2P message service (223).

[0091] According to one embodiment, in operation 505, the RCS platform (20) may transmit a forwarding message to the second electronic device (10b) based on the reception of a forwarding message transmission request. In operation 505, the second electronic device (10b) may receive the forwarding message. The forwarding message is generated from the RCS corporate message of FIG. 3 and may include at least a portion of the body of the RCS corporate message. The forwarding message may include information of the RCS corporate message (e.g., identifier, signature key, and signature). The identifier of the forwarding message itself may be different from the identifier of the original message (e.g., RCS corporate message). The information of the RCS corporate message may be included in the header or body of the forwarding message. If the information of the RCS corporate message is included in the header of the forwarding message, the forwarding message may indicate that it is a message reconstructed from the RCS corporate message. If the information of the RCS corporate message is included in the body of the forwarding message, the second electronic device (10b) may be configured not to output at least a portion of the information of the RCS corporate message within the forwarding message.

[0092] According to one embodiment, in operation 510, the second electronic device (10b) may generate a delivered notification based on the reception of a delivered message. The second electronic device (10b) may generate a signature from the delivered message using a signature key and an encryption method included in the delivered message. For example, the second electronic device (10b) may generate a signature by signing at least a portion of the body of the delivered message using the signature key. The second electronic device (10b) may include the generated signature and the identifier of the original message (e.g., the identifier of the RCS enterprise message) in the delivered notification. The delivered notification is intended to notify the RCS platform (20) of the delivery status of the delivered message, but in embodiments of the present disclosure, the delivered notification may include information of the original message (e.g., the identifier and signature of the original message) as well as information of the delivered message. For example, Table 4 below may show an example of a delivered notification generated by the second electronic device (10b).

[0093] <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> <message-id> VGGlhy188m < / message-id> <signature> J;aom834u-0n98y9wney9pynep9yhofho873b2g9876tv9ciojopfd9hlkh;8khghnbmbnxzc< / signature> < / delivery-notification> < / imdn>

[0094] In Table 4, the upper <message-id>The field represents the identifier assigned to the forwarded message. <datetime>The field may indicate the time when a message (e.g., an RCS message) is received by the second electronic device (10b). <delivery-notification>The field can indicate the reception status of a delivered message. Unlike the delivered notification in Table 2, the delivered notification in Table 4 is <deliver-notification>The field may further include information about the original message of the forwarded message (e.g., RCS enterprise message).

[0095] The information of the original message may include the identifier and signature of the original message. The second electronic device (10b) may obtain the identifier of the original message from the transmitted message. <delivery-notification>within the field <message-id>The item may represent an identifier of the original message. The second electronic device (10b) may obtain information on a signature key and an encryption method from the transmitted message. The second electronic device (10b) may generate a signature by signing at least a portion of the body of the transmitted message using the signature key according to the information on the encryption method. <delivery-notification>within the field <signature>The item may represent the signature of the transmission message generated by the second electronic device (10b).

[0096] In the example in Table 4, the information of the original message (e.g., message identifier and signature) is <deliver-notification>Although described as a sub-item of, the embodiments of the present disclosure are not limited thereto. For example, information from the original message may be inserted at any location in the delivered notification. For example, information from the original message <delivery-notification>Inserted into a field different from the field or <delivery-notification>It can be included in a new field different from the field.

[0097] According to one embodiment, in operation 515, the second electronic device (10b) may transmit a delivered notification to the RCS platform (20). The delivered notification is for a P2P RCS message and may be processed by the P2P message service (223). The RCS platform (20) may determine whether the delivered notification contains information of the original message. If the delivered notification contains information of the original message, the delivered notification may be processed by the delivery message indicator (225). The delivery message indicator (225) may deliver the delivered notification containing information of the original message to the MaaP server (30). If the delivered notification does not contain information of the original message, the P2P message service (223) may process the delivered notification according to normal procedures. In this case, the RCS platform (20) may not deliver the delivered notification to the MaaP server (30).

[0098] According to one embodiment, in operation 520, the RCS platform (20) may transmit a delivered notification to the first electronic device (10b). The delivered notification of operation 520 may be a delivered notification for a delivered message of delivery 505. The delivered notification of operation 520 may include an identifier of the delivered message. Based on the reception of the delivered notification, the first electronic device (10a) may identify the reception status of the delivered message by the second electronic device (10b). For example, the RCS platform (20) may perform operation 520 regardless of whether the delivered notification of operation 515 includes original message information. For example, if the delivered notification of operation 520 includes original message information, the performance of operation 520 may be omitted.

[0099] According to one embodiment, in operation 525, the RCS platform (20) may send a delivered notification to the MaaP server (30). For example, the RCS platform (20) may determine whether to deliver the delivered notification to the MaaP server (30) based on the delivered notification received from the user device. If the delivered notification contains original message information, the RCS platform (20) may send the delivered notification to the MaaP server (30). If the delivered notification does not contain original message information, the RCS platform (20) may not deliver the delivered notification to the MaaP server (30).

[0100] According to one embodiment, in operation 530, the MaaP server (30) can compare signatures based on the reception of a delivered notification. For example, processing of the delivered notification can be performed by an alert service (233). The MaaP server (30) can obtain the identifier of the original message from the message identifier included in the delivered notification. The MaaP server (30) can obtain the signature of the original message from the key-signature DB (235) using the identifier of the original message. The MaaP server (30) can compare the signature of the original message with the signature included in the delivered notification (e.g., the signature of the forward message). If the identifier of the original message does not exist in the key-signature DB (235), the MaaP server (30) can determine that the forward message is forged.

[0101] According to one embodiment, the MaaP server (30) can determine whether the forwarded message is forged by comparing the signatures of the original message and the forwarded message. If the signature of the original message matches the signature of the forwarded message, the MaaP server (30) can determine that the forwarded message is not forged. In one example, if the MaaP server (30) determines that the message is not forged, the MaaP server (30) can transmit information to the brand server (40) indicating that the unforged RCS corporate message has been delivered to another electronic device. If the signature of the original message does not match the signature of the forwarded message, the MaaP server (30) can determine that the forwarded message is forged.

[0102] According to one embodiment, if a delivery message is forged, the MaaP server (30) may transmit information instructing the brand server (40), the first electronic device (10a), and / or the second electronic device (10b) to forge the delivery message. In one example, the MaaP server (30) may transmit deletion information for deleting the forged delivery message to the second electronic device (10b) via the RCS platform (20). When the deletion information is received, the display of the delivery message by the second electronic device (10b) may be stopped. For example, instead of the delivery message, information indicating that the delivery message has been deleted may be displayed.

[0103] FIG. 6 illustrates a transmitted RCS message according to one embodiment.

[0104] Referring to FIGS. 2 and FIGS. 6, according to one embodiment, the second electronic device (10b) may provide a forwarding message (600) (e.g., a shared RCS corporate message). For example, the second electronic device (10b) may display a screen (601) containing the forwarding message (600) through a display.

[0105] The second electronic device (10b) can display sender information (605) of a forwarded message (600). For example, the sender information (605) may include information stored in the second electronic device (10b) regarding the sender of the forwarded message (600). For example, the sender information (604) may include information of the first electronic device (10a) stored in the address book of the second electronic device (10b). For example, when the second electronic device (10b) receives a message from the first electronic device (10a), it can identify a name corresponding to the identification information of the first electronic device (10a) from the contacts stored in the second electronic device (10b). The second electronic device (10b) can display sender information (605) based on the identified name (e.g., Bob).

[0106] The second electronic device (10b) can display a delivery indicator (610) indicating that the received message has been delivered if the received message is a message delivered by another electronic device. For example, the second electronic device (10b) can identify the received message as a delivered message if the received message contains information of the original message.

[0107] In the example of FIG. 6, the forward message (600) may be at least partially identical to the original message, the RCS corporate message (410) of FIG. 4. For example, the forward message (600) may include an image (411) and text (413), just like the RCS corporate message (410).

[0108] In the example of FIG. 6, since the RCS corporate message (410) of FIG. 4 is reconstructed by the first electronic device (10a), the RCS corporate message (410) of FIG. 4 and the forward message (600) may have different points. For example, unlike the RCS corporate message (410), the forward message (600) of FIG. 6 may not include the interaction object (415) of FIG. 4.

[0109] FIG. 7 is a flowchart of an RCS message authentication method of at least one server according to one embodiment.

[0110] Referring to FIGS. 1, FIGS. 2 and FIGS. 7, according to one embodiment, an RCS platform (20) and / or a MaaP server (30) can authenticate a forwarded RCS message. Hereinafter, at least one server may include an RCS platform (20) and / or a MaaP server (30). The order of operations described below in relation to FIG. 7 is an example, and 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. 7 or may be executed substantially simultaneously with other operations of FIG. 7.

[0111] According to one embodiment, in operation 705, at least one server may generate a first signature for an RCS corporate message. For example, at least one server may generate a first signature when it receives a request to send an RCS corporate message from an external device (e.g., a brand server (40)). At least one server may generate the first signature by signing at least a portion of the body of the RCS corporate message using a signature key mapped to the brand server (40) or a generated signature key. At least one server may sign at least a portion of the body of the RCS corporate message according to a specified encryption method.

[0112] According to one embodiment, in operation 710, at least one server may transmit a first RCS corporate message (e.g., RCS corporate message (90)) to a first electronic device (10a) (e.g., operation 320 of FIG. 3). For example, the first RCS corporate message may include information on a signature key and an encryption method used to generate the first signature. The information on the signature key and encryption method may be included in the header of the first RCS corporate message.

[0113] According to one embodiment, in operation 715, at least one server may receive an IMDN from the second electronic device (10b) (e.g., operation 515 of FIG. 5). For example, the second electronic device (10b) may receive a first RCS enterprise message from the first electronic device (10a). For example, at least one server may receive a request to transmit a second RCS message generated based on the first RCS enterprise message from the first electronic device (10a) (e.g., operation 345 of FIG. 3). Based on the reception of the request to transmit the second RCS message, at least one server may transmit the second RCS message to the second electronic device (10b) (e.g., operation 505 of FIG. 5).

[0114] The second electronic device (10b) may receive a second RCS message reconstructed from a first RCS corporate message by the first electronic device (10a). The second RCS message may include information of the first RCS corporate message (e.g., identifier, signature key, and encryption method information). The information of the first RCS corporate message may be included in the header of the second RCS message. Based on the reception of the second RCS message, the second electronic device (10b) may transmit an IMDN (e.g., delivered IMDN) to at least one server. The IMDN may include a second signature generated by the second electronic device (10b). For example, the second electronic device (10b) may generate a second signature by signing at least a portion of the body of the second RCS message using the signature key and encryption method included in the first RCS corporate message. The IMDN may include the identifier and signature of the first RCS corporate message.

[0115] According to one embodiment, in operation 720, at least one server may perform authentication of a second RCS message (e.g., RCS message (91)) associated with IMDN (e.g., operation 530 of FIG. 5). For example, at least one server may perform authentication of the second RCS message by comparing a first signature and a second signature. If the first signature and the second signature do not correspond to each other, at least one server may transmit information instructing forgery of the second RCS message to at least one of an external device (e.g., brand server (40)) or a second electronic device (10b).

[0116] In one example, the MaaP server (30) may be referred to as an electronic device. The operations described above in relation to FIG. 7 may be described as follows. For example, the MaaP server (30) may be an electronic device comprising a communication circuit, at least one processor, and memory. For example, the memory may store instructions that cause the electronic device to perform the operations described below when executed collectively or in combination by the at least one processor.

[0117] An electronic device may receive a first message from a first external device (e.g., a brand server (40)) to be transmitted to a first user device (e.g., a first electronic device (10a)). The electronic device may transmit a second message (e.g., an RCS enterprise message) containing the first message and first signature information (e.g., a signature key and encryption information) to the first user device through a network associated with the electronic device (e.g., operation 710).

[0118] The electronic device may receive a third message (e.g., IMDN) associated with the second message from a second user device (e.g., second electronic device (10b)), which includes second signature information (e.g., signature). For example, the third message may include an identifier of the second message. For example, the third message may be transmitted from the second user device to the electronic device in response to the reception of the forwarding message by the second user device. The second message may correspond to an a2p (application-to-person) message, and the forwarding message may correspond to a p2p (person-to-person) message.

[0119] The electronic device can determine whether the forwarding message associated with the third message is forged (e.g., operation 720) based on the first signature information of the second message and the second signature information of the third message. For example, the forwarding message may correspond to the second message transmitted to the second user device by the first user device. For example, the second signature information may be generated by the second user device based on the specified encryption method and the forwarding message.

[0120] If the first signature information and the second signature information do not correspond to each other, the electronic device may transmit information instructing at least one of the first external device or the second user device to forge the transmission message.

[0121] FIG. 8 is a flowchart of an RCS message authentication method of an electronic device according to one embodiment.

[0122] Referring to FIGS. 2 and FIGS. 8, according to one embodiment, an electronic device (10) may receive a received RCS message (e.g., an RCS message (91) of FIG. 1). The electronic device (10) may transmit an IMDN for the RCS message to determine whether the received RCS message is forged.

[0123] The operations described below in relation to FIG. 8 may be referred to as operations of the electronic device (10) of FIG. 2. For example, the electronic device (10) may correspond to the second electronic device (10b) of FIG. 1. The order of the operations described below in relation to FIG. 8 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. 8 or may be performed substantially simultaneously with other operations of FIG. 8.

[0124] 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.

[0125] According to one embodiment, in operation 805, the electronic device (10) may receive a second RCS message (e.g., the RCS message (91) of FIG. 1) (e.g., operation 505 of FIG. 5). For example, the electronic device (10) may receive the second RCS message using a communication circuit (190). For example, the second RCS message may be generated based on a first RCS corporate message (e.g., the RCS corporate message (90) of FIG. 1). For example, the electronic device (10) may receive the second RCS message from an external electronic device (e.g., the first electronic device (10a) of FIG. 1). For example, the second RCS message may include a first identifier of the first RCS corporate message.

[0126] In operation 810, the electronic device (10) can generate a signature for the second RCS message using a signature key and an encryption method included in the second RCS message. For example, the electronic device (10) can generate a signature by signing at least a portion of the body (e.g., content) of the second RCS message with a signature key included in the second RCS message. The electronic device (10) can sign the body of the second RCS message using an encryption method included in the second RCS message.

[0127] In operation 815, the electronic device (10) may transmit an IMDN containing a signature. For example, the electronic device (10) may transmit the IMDN to an RCS server (e.g., an RCS platform (20) and / or a MaaP server (30)). The IMDN may include a first identifier of a first RCS enterprise message. For example, the second identifier of the IMDN and the first identifier may be different from each other. For example, the RCS server may perform authentication for a second RCS message by comparing the first signature of the first RCS enterprise message with the signature received from the electronic device (10).

[0128] FIG. 9 illustrates a flowchart of an RCS message transmission method of an electronic device according to one embodiment.

[0129] Referring to FIGS. 2 and FIG. 9, according to one embodiment, an electronic device (10) may transmit an RCS message. For example, the electronic device (10) may correspond to the first electronic device (10a) of FIG. 1. The order of operations described below in relation to FIG. 9 is an example, and 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. 9 or may be executed substantially simultaneously with other operations of FIG. 9.

[0130] 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.

[0131] According to one embodiment, in operation 905, the electronic device (10) may receive a first RCS corporate message (e.g., operation 320 of FIG. 3). For example, the first RCS corporate message may include a header and a body. The header of the first RCS corporate message may include information on a signature key and an encryption method (e.g., an algorithm).

[0132] According to one embodiment, in operation 910, the electronic device (10) can identify an event (e.g., operation 340 of FIG. 3). For example, the event may include an event directing the sharing of a received RCS enterprise message. The event may be identified in at least one of the following cases: when a user input requesting delivery of an RCS enterprise message is received, when a sender associated with the RCS enterprise message corresponds to a specified sender, or when the RCS enterprise message contains specified text.

[0133] According to one embodiment, in operation 915, the electronic device (10) can generate a second RCS message based on a first RCS corporate message (e.g., operation 343 of FIG. 3). The electronic device (10) can generate the second RCS message based on the identification of an event. In the process of generating the second RCS message, the electronic device (10) can remove at least a portion of the body of the first RCS corporate message. For example, the electronic device (10) can remove tools for user interaction (e.g., interaction buttons and / or links) from the first RCS corporate message. The electronic device (10) can include information of the first RCS corporate message (e.g., identifier, signature key, and / or encryption method) in the second RCS message. For example, the electronic device (10) can include information of the first RCS corporate message in the header of the second RCS message.

[0134] According to one embodiment, in operation 920, the electronic device (10) can transmit a second RCS message to an external electronic device (e.g., operation 345 of FIG. 3). For example, the electronic device (10) can transmit the second RCS message to an external electronic device (e.g., second electronic device (10b)) through the RCS platform (20). When the second RCS message is successfully received by the external electronic device, the electronic device (10) can receive a delivered notification from the RCS platform (20) (e.g., operation 520 of FIG. 5).

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

[0136] 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.

[0137] 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.

[0138] 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).

[0139] 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)).

[0140] 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 via the sensor (1070), into a format suitable for the component of the processor (1010).

[0141] 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).

[0142] 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. < / signature> < / datetime> < / datetime> < / delivered> < / datetime> < / urn:ietf:params:imdn>

Claims

1. A method for message authentication of at least one server (20, 30) configured to provide RCS (rich communication services), The operation of generating a first signature for an RCS business message using a signing key and a specified encryption method; The operation of transmitting a first RCS corporate message, comprising the above RCS corporate message, the above signature key, and the above specified encryption method information, to a first electronic device (10a); The operation of receiving an IMDN (instant message disposition notification) from a second electronic device (10b) that includes an identifier of the first RCS enterprise message and a second signature generated by the second electronic device; and A method comprising the operation of performing authentication of a second RCS message associated with the IMDN by comparing the first signature and the second signature.

2. In Paragraph 1, The operation of receiving a transmission request for the second RCS message generated based on the first RCS enterprise message from the first electronic device; and A method further comprising the operation of transmitting the second RCS message to the second electronic device based on the reception of the transmission request.

3. In Paragraph 2, A method in which the second RCS message comprises the identifier of the first RCS enterprise message, the signature key, and information on the specified encryption method.

4. In Paragraph 3, A method in which the identifier of the first RCS enterprise message, the signature key, and the information of the specified encryption method are included in the header of the second RCS message.

5. In Paragraph 3, The above second signature is a method generated by the above second electronic device using the above signature key and the above specified encryption method.

6. In Paragraph 2, A method in which the IMDN is transmitted from the second electronic device to the at least one server in response to the reception of the second RCS message by the second electronic device.

7. In Paragraph 1, The operation of receiving a transmission request for the above RCS corporate message from an external device; and A method further comprising the operation of generating the signature key for the RCS enterprise message based on the reception of the transmission request.

8. In Paragraph 7, A method further comprising the operation of transmitting information instructing forgery of the second RCS message to at least one of the external device or the second electronic device when the first signature and the second signature do not correspond to each other.

9. As an electronic device, Communication circuit; At least one processor including at least one processing circuit; and It includes a memory electrically connected to at least one processor and storing instructions, and When the above instructions are executed collectively or in combination by the at least one processor, the electronic device: Receive a first message from a first external device to be transmitted to a first user device, and A second message including the first message and first signature information is transmitted to the first user device through a network associated with the electronic device, and Receive a third message associated with the second message, including second signature information from a second user device, and An electronic device that determines whether a transmission message associated with the third message is forged based on the first signature information of the second message and the second signature information of the third message.

10. In Paragraph 9, The above first signature information is an electronic device comprising a signature key and information of a specified encryption method.

11. In Paragraph 9, The above third message is an electronic device that further includes the identifier of the above second message.

12. In Paragraph 9, The above third message corresponds to the IMDN (instant message disposition notification) for the above transmission message, and The above transmission message is an electronic device corresponding to the second message transmitted to the second user device by the first user device.

13. In Paragraph 10, The above second signature information is an electronic device generated by the second user device based on the above specified encryption method and the above transmission message.

14. In Paragraph 9, The above third message is an electronic device transmitted from the second user device to the electronic device in response to the reception of the transmission message by the second user device.

15. In Paragraph 9, An electronic device in which the second message corresponds to an a2p (application-to-person) message and the transmission message corresponds to a p2p (person-to-person) message.

Images