Device and method

Abstract

The purpose of the present invention is to provide a device and a method whereby spoofed SMS messages can be appropriately managed.　In a user terminal 100 according to the present disclosure, an SMS message reception unit 101 receives an SMS message over a communication line. Furthermore, a determination unit 103 functions as an acquisition unit, and when a message is to be received, the determination unit 103 accesses a customer information management ledger 400 (management database) accessible by a telecommunications carrier that manages a line for receiving the message, and acquires a Sender ID (identification information of the sender) from the customer information management ledger 400 on the basis of the telephone number (transmission source information) of the message. In addition, a thread management unit 104 manages the SMS message on the basis of the Sender ID.

Description

Apparatus and method

[0001] The present invention relates to an apparatus and method for managing messages.

[0002] The 3GPP (3rd Generation Partnership Project) describes SMS (Short Message Service) and how to connect it internationally.

[0003] 3GPPTS23.040

[0004] By exploiting a mechanism called International SMS (international connection) in the SMS specifications established by 3GPP, it is possible for SMS senders to spoof their Sender ID. Therefore, if the receiving party manages threads using Sender ID, there is a problem in that SMS messages with spoofed Sender IDs can be mixed into threads of SMS messages sent from genuine companies.

[0005] Therefore, an object of the present disclosure is to provide an apparatus and method that can appropriately manage spoofed SMS messages.

[0006] The device disclosed herein includes a receiving unit that receives a message, an acquisition unit that, upon receiving the message, acquires the sender's identification information based on the sender information of the message from a management database accessible by a communications carrier that manages the line for receiving the message, and a management unit that manages the message based on the identification information.

[0007] According to the present disclosure, even if a message is received in which the sender's identification information has been forged, the message can be managed appropriately.

[0008] FIG. 1 is an explanatory diagram illustrating problems with a conventional SMS message communication system. FIG. 2 is a diagram illustrating a process for confirming an SMS message using the customer information management ledger 400 of the present disclosure. FIG. 3 is a diagram illustrating a specific example of a database stored in the customer information management ledger 400. FIG. 4 is a block diagram illustrating the functional configuration of the user terminal 100. FIG. 5 is a flowchart illustrating the operation of the user terminal 100. FIG. 6 is a diagram schematically illustrating the above process. FIG. 7 is a diagram illustrating an example of the hardware configuration of the user terminal 100 according to an embodiment of the present disclosure.

[0009] The present disclosure will be described with reference to the accompanying drawings. Whenever possible, the same parts are designated by the same reference numerals and redundant description will be omitted.

[0010] 1 is an explanatory diagram for explaining the problems with a conventional SMS message communication system. As shown in the diagram, when an SMS message is sent from a message sender, it is received by the recipient via an SMS gateway service 200 and an SMS center 300 of a communications carrier.

[0011] Here, it is assumed that a message sender S1, which is a delivery company A, sends SMS messages M1 and M2 to a recipient R. When the terminal of sender S1 sends SMS messages M1 and M2, the user terminal 100 of recipient R manages the messages so that they are displayed in a thread T of delivery company A. Conventionally, this thread T is distinguished based on a sender ID (also called a sender ID; in this disclosure, referred to as Sender ID) that indicates the sender of the SMS message, and the messages are displayed in the same thread T.

[0012] On the other hand, consider the case where there is a malicious user S2 who wants to pose as delivery company A. In this case, when user S2's terminal sends an SMS message M21 containing a spoofed Sender ID indicating delivery company A to recipient R, the SMS message M21 is managed in the same thread as SMS messages M11 and the like (assumed to be legitimate messages here) from delivery company A in recipient R's user terminal 100. This is because the Sender ID set in the SMS message M21 is spoofed so that it is managed in the same thread. Generally, the terminal 100 manages messages with the same Sender ID to be displayed in the same thread.

[0013] 2 is a diagram showing the SMS message confirmation process using the customer information management ledger 400 of the present disclosure. As shown in the figure, when the user terminal 100 of the recipient R receives an SMS message, it accesses the customer information management ledger 400 to confirm that the sender of the received SMS message is a legitimate user and obtains the sender ID. The user terminal 100 then manages the thread based on the sender ID obtained from the customer information management ledger 400.

[0014] Even if the sender of an SMS message falsifies the sender ID, the user terminal 100 accesses the customer information management ledger 400 and manages the thread of the SMS message based on the sender ID obtained therefrom, so the sent SMS message will not be included in the same thread.

[0015] In the present disclosure, the customer information management ledger 400 is managed on a consortium blockchain, and the contract information stored in the customer information management ledger 400 is stored in a state that makes it difficult to tamper with. The customer information management ledger 400 stores, in association with telephone numbers, an encryption key for decrypting SMS messages, the contract name (corporate name or individual name) set when signing the communication line contract, the contract type (corporate contract or individual contract), and the sender ID. A consortium blockchain is a blockchain in which multiple companies act as administrators, and access requires the administrators or their permission. In the present disclosure, the telecommunications carrier that provides the communication line acts as the administrator, and only the telecommunications carrier can access the blockchain (to register and retrieve information).

[0016] In the present disclosure, when a business user (e.g., the above-mentioned delivery business A) enters into a contract with a telecommunications carrier, the user sets a Sender ID that identifies the sender. This Sender ID is managed on a blockchain, making it difficult to tamper with.

[0017] FIG. 3 shows a specific example of a database stored in the customer information management ledger 400. As shown in the figure, the customer information management ledger 400 stores the telephone number, contract name, Sender ID, encryption key, and contract type. The Sender ID is used by the user terminal 100 to manage threads of received messages and is displayed as the sender. As mentioned above, the Sender ID is ID information set by the sender when signing up for a line contract. The encryption key is a key used to decrypt messages encrypted by the sender. The sender uses this encryption key to generate an encrypted SMS message.

[0018] The contract type is information that indicates whether the contract is corporate or personal. In the case of a corporate contract, one Sender ID is set for one contract name, and multiple phone numbers are linked to one contract name. In a typical corporate contract, each employee has their own phone number, and a combined Sender ID is assigned to all of them. This is because the contract is for one corporation.

[0019] The user terminal 100 obtains the encryption key linked to the telephone number of the sent SMS message from the customer information management ledger 400 and decrypts the received SMS message.

[0020] Next, the functional configuration of the user terminal 100 that performs such processing will be described. Fig. 4 is a block diagram showing the functional configuration of the user terminal 100. As shown in the figure, the user terminal 100 is configured to include an SMS message receiving unit 101 (receiving unit), a decoding unit 102, a determining unit 103 (acquiring unit), a thread management unit 104 (management unit), and a display unit 105 (presenting unit).

[0021] The SMS message receiving unit 101 is a unit that receives an SMS message from a sender terminal. In the present disclosure, this SMS message is encrypted in advance using an encryption key.

[0022] When the decryption unit 102 receives an SMS message, it accesses the customer information management register 400, obtains the encryption key associated with the sender's telephone number, and decrypts the SMS message.

[0023] The judgment unit 103 accesses the customer information management ledger 400 to obtain the contract type, contract name, and Sender ID linked to the telephone number of the sender of the SMS message, and determines whether the contract is a corporate contract or an individual contract based on the contract type.

[0024] The thread management unit 104 is a part that manages received SMS messages on a thread-by-thread basis based on the Sender ID acquired by the determination unit 103. For example, the thread management unit 104 manages SMS messages with the same Sender ID so that they are handled in the same thread.

[0025] The display unit 105 displays SMS messages on a thread-by-thread basis, and displays SMS messages with the same Sender ID in the same thread. In the present disclosure, threads are managed on a Sender ID-by-Sender ID basis, and the contract name is displayed in the thread.

[0026] Next, the operation of the user terminal 100 configured as above will be described. Fig. 5 is a flowchart showing the operation of the user terminal 100. As shown in the figure, when the SMS message receiving unit 101 receives an SMS message (S101), the decryption unit 102 accesses the customer information management ledger 400, obtains the encryption key linked to the telephone number of the sender of the SMS message, and decrypts the SMS message (S102).

[0027] If the decryption unit 102 is unable to decrypt the SMS message (S103: NO), it attempts to obtain the encryption key and decrypt the message a certain number of times, and then discards the received SMS message (S104).

[0028] If the decryption unit 102 is able to decrypt the SMS message, the judgment unit 103 obtains from the customer information management register 400 the contract name, sender ID, and contract type associated with the telephone number described as the sender of the SMS message (S105).

[0029] When the determination unit 103 determines that the contract is a corporate contract based on the contract type (S106), the thread management unit 104 manages the messages according to the thread based on the Sender ID, and the display unit 105 displays the received SMS messages on a thread-by-thread basis (S107). This thread is managed based on the Sender ID set in the customer information management register 400, and the acquired contract name is displayed.

[0030] If the determination unit 103 determines that the contract is personal, the thread management unit 104 manages the thread as an SMS message from a party other than a corporation, and the display unit 105 displays the SMS message (S108). That is, the thread management unit 104 manages the SMS message using the Sender ID set by the individual, and the display unit 105 displays the SMS message together with the contract name.

[0031] The thread management unit 104 manages SMS message threads using the Sender ID set in the customer information management ledger 400, but in the customer information management ledger 400, the Sender ID is managed on a blockchain, making it difficult to tamper with.

[0032] In other words, by setting a Sender ID for each business (company, etc.), the user terminal 100 can receive messages in the same thread. The Sender ID is set when registering in the customer management ledger (at the time of contract or at the request of the corporation). Also, if the subscriber is an individual, they are managed in a thread with the contract name, not the set Sender ID.

[0033] 6 is a diagram showing the above process. As shown in the figure, when the user terminal 100 receives an SMS message, it accesses the customer information management ledger 400 and queries the contract name, contract type, and Sender ID using the telephone number as a key. If the telephone number is a corporate contract, the user terminal 100 obtains the contract name and Sender ID from the customer information management ledger 400. If the telephone number is an individual contract, the contract name is obtained.

[0034] In the case of a corporate contract, the user terminal 100 manages the SMS messages using thread T1 based on the Sender ID set in the customer information management register 400. At this time, the display unit 105 of the user terminal 100 manages the SMS messages using thread T1, and the title of thread T1 is displayed as the contract name.

[0035] In addition, in the case of a personal contract, the user terminal 100 is managed by a thread T2 with a contract name set by the individual, and the thread is managed using the contract name.

[0036] Next, the effects of the user terminal 100 of the present disclosure will be described. In the user terminal 100 of the present disclosure, the SMS message receiving unit 101 receives an SMS message via a communication line. The determination unit 103 functions as an acquisition unit. Upon receiving the message, the determination unit 103 accesses a customer information management ledger 400 (management database) accessible by a communications carrier that manages the line for receiving the message, and acquires a sender ID (sender identification information) from the customer information management ledger 400 based on the phone number (sender information) of the message. The thread management unit 104 then manages the SMS message based on the sender ID.

[0037] In the present disclosure, the thread management unit 104 sorts SMS messages based on the sender ID, and the display unit 105 functions as a presentation unit and presents the thread-managed SMS messages to the user.

[0038] According to this configuration, Sender IDs are stored in a database accessible to a specific business, such as customer information management ledger 400, and are used to manage SMS messages. In the present disclosure, thread management is performed using Sender IDs at the receiving terminal, making it possible to prevent SMS messages with tampered Sender IDs from being included in the same thread.

[0039] For example, there is a problem in that an SMS message from delivery company A and an SMS message from a malicious user who wants to pose as delivery company A are presented in the same thread on the receiving user terminal 100. This is because a malicious user can spoof the Sender ID to the same Sender ID as delivery company A, thereby allowing the message to be mixed into the same thread. Therefore, by managing SMS message threads based on the Sender ID stored in the customer information management ledger 400 managed by the telecommunications carrier, it is possible to prevent spoofing using the Sender ID in SMS messages. This Sender ID is information set by the subscriber at the time of signing a contract, and is set to a character string that is different from that of other subscribers.

[0040] Here, the customer information management ledger 400 stores the contract name in association with the sender ID. The determination unit 103 then extracts the contract name in addition to the identification information, and the display unit 105 displays the SMS message together with the contract name.

[0041] With this configuration, threads are managed by Sender ID, and the name of the thread can be the contract name. Therefore, for example, SMS messages that were previously presented in separate threads for each sender (employee) of a business can now be presented in the same thread. In other words, SMS messages from the same business can be presented in the same thread, making them easier to read.

[0042] In the present disclosure, in a case where SMS messages are sent to each representative of operator A in a separate thread (sent from a different phone number), a malicious user who wants to impersonate operator A could change the profile name specific to the SMS message app (a profile name that can be set in each app) to impersonate operator A. This is because the name of the SMS message can be set independently in the app and SMS on the sender's device. Therefore, by specifying (managing) the thread of the SMS message based on the contract name stored in the customer information management ledger 400 managed by the telecommunications carrier, it is possible to prevent impersonation using a profile name defined by the user.

[0043] In the present disclosure, the customer information management register 400 stores an encryption key in addition to the Sender ID. The decryption unit 102 then obtains the encryption key from the customer information management register 400 and uses the encryption key to decrypt the SMS message.

[0044] With this configuration, an SMS message sent by a user attempting to impersonate another user cannot be correctly decrypted, and therefore is not presented to the recipient, thereby appropriately preventing the reception process of a spoofed SMS message.

[0045] In the present disclosure, the customer information management ledger 400 is stored on a blockchain. This makes it difficult to tamper with the sender ID, contract name, encryption key, and so on stored in the customer information management ledger 400, thereby appropriately preventing the problems of the present disclosure. Note that the customer information management ledger 400 does not necessarily have to be on a blockchain, as long as it is in a state where it cannot be easily accessed by unspecified users. However, in the present disclosure, telephone numbers, which are the key to obtaining various information, are traded across telecommunications carriers (such as MNP), so managing them on a blockchain can more reliably prevent tampering.

[0046] The device and method of the present disclosure have the following configuration.

[0047] [1] A device comprising: a receiving unit that receives a message; an acquiring unit that, upon receiving the message, acquires identification information of a sender based on sender information of the message from a management database accessible by a communications carrier that manages a line for receiving the message; and a managing unit that manages the message based on the identification information.

[0048] [2] The device according to [1], further comprising a presentation unit that presents the sorted messages based on the identification information.

[0049] [3] The device according to [1] or [2], wherein the management database stores a contract name in association with the identification information, the acquisition unit extracts the contract name in addition to the identification information, and the presentation unit presents the message together with the contract name.

[0050] [4] The device according to any one of [1] to [3], further comprising a decryption unit that decrypts an SMS message using an encryption key stored in the management database, wherein the management database stores an encryption key in addition to the identification information, and the decryption unit further obtains the encryption key from the management database and decrypts the message using the encryption key.

[0051] [5] The device according to any one of [1] to [4], wherein the management database is stored on a blockchain and managed by the telecommunications carrier.

[0052] [6] A method comprising: a receiving step of receiving a message; a confirmation step of, upon receiving the message, accessing a customer information management ledger accessible to a communications carrier that manages the line for receiving the message; an acquisition step of acquiring sender identification information from the customer information management ledger based on sender information of the message; and a management step of managing the message based on the identification information.

[0053] The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., via wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0054] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0055] For example, the user terminal 100 according to an embodiment of the present disclosure may function as a computer that performs processing of the thread management method of the present disclosure. Fig. 7 is a diagram illustrating an example of the hardware configuration of the user terminal 100 according to an embodiment of the present disclosure. The above-described user terminal 100 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0056] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the user terminal 100 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0057] Each function in the user terminal 100 is realized by loading specified software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and storage 1003.

[0058] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, etc. For example, the above-mentioned decoding unit 102, determination unit 103, thread management unit 104, etc. may be realized by the processor 1001.

[0059] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the decoding unit 102, the determination unit 103, and the thread management unit 104 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be used for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0060] The memory 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a thread management method according to an embodiment of the present disclosure.

[0061] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0062] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned SMS message receiving unit 101 may be realized by the communication device 1004. The communication device 1004 may be implemented with a transmitting unit and a receiving unit that are physically or logically separated.

[0063] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0064] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0065] The user terminal 100 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0066] The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0067] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0068] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0069] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0070] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0071] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0072] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0073] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0074] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0075] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0076] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0077] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0078] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.

[0079] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0080] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0081] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0082] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0083] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0084] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0085] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0086] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0087] 100...user terminal, 101...SMS message receiving unit, 102...decryption unit, 103...determination unit, 104...thread management unit, 105...display unit, 200...SMS gateway service, 300...SMS center, 400...customer information management ledger.

Claims

1. A device comprising: a receiving unit that receives a message; an acquiring unit that, upon receiving the message, acquires the sender's identification information based on the sender information of the message from a management database accessible by a communications carrier that manages the line for receiving the message; and a managing unit that manages the message based on the identification information.

2. The device according to claim 1, further comprising a presentation unit that presents the sorted messages based on the identification information.

3. The device according to claim 2, wherein the management database stores a contract name in association with the identification information, the acquisition unit extracts the contract name in addition to the identification information, and the presentation unit presents the message together with the contract name.

4. The device according to claim 1, further comprising a decryption unit that decrypts the SMS message using an encryption key stored in the management database, wherein the management database stores an encryption key in addition to the identification information, and the decryption unit further retrieves the encryption key from the management database and decrypts the message using the encryption key.

5. The device according to claim 1, wherein the management database is stored on a blockchain and managed by the telecommunications carrier.

6. A method comprising: a receiving step of receiving a message; a confirmation step of, upon receiving the message, accessing a customer information management ledger accessible to a communications carrier that manages the line for receiving the message; an acquisition step of acquiring sender identification information from the customer information management ledger based on sender information of the message; and a management step of managing the message based on the identification information.

Images