Improved messaging system

The messaging system uses a centralized database to manage chats and media in specified and unspecified formats, ensuring unauthorized access is prevented by requiring authentication, addressing the lack of privacy in existing systems.

JP7583394B2Active Publication Date: 2024-11-14SOCIAL MEDIA EMOTIONS SRL +1
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2021560575
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-04-17
Filing Date
2020-04-16
Publication Date
2024-11-14
Estimated Expiration
2040-04-16

AI Technical Summary

Technical Problem

Existing messaging systems lack the ability to hide the existence and content of chats, messages, and graphical/audio elements from unauthorized users, allowing third parties to access sensitive information without consent, even when end-to-end encryption is enabled.

Method used

A messaging system that employs a centralized database to manage chats, messages, and graphical/audio elements in two formats: unspecified (always visible) and specified (hidden by default, requiring authentication with a personal or shared access key to view).

Benefits of technology

Ensures that unauthorized users cannot detect the presence of hidden chats, messages, or elements, maintaining privacy by requiring authentication to access sensitive content, thus preventing unauthorized viewing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007583394000005
    Figure 0007583394000005
  • Figure 0007583394000006
    Figure 0007583394000006
  • Figure 0007583394000007
    Figure 0007583394000007
Patent Text Reader

Abstract

A messaging system (2), preferably an instant messaging system, comprising at least one sending device (4) and at least one receiving device (6) configured to send and / or receive messages (60) by at least one aggregation base station (8) with which both are in communication, a first software module loaded and / or executed on the sending device (4) and / or the receiving device (6), and a second software module loaded and / or executed on the aggregation base station (8), the first software module and / or the second software module being configured to communicate within the messaging system (2) in a first unspecified format (14',and a second designated type (14″, 60″, 33″) of items including at least one chat (14) and / or message (60) and / or digital element (33) that is always viewable in a corresponding screen (42, 57) realized on the display of said device (4, 6). The second designated type (14″, 60″, 33″) of items includes at least one chat (14) and / or message (60) and / or digital element (33), said at least one chat (14) and / or message (60) and / or digital element (33) being in a display state, and said at least one chat (14) and / or message (60) and / or digital element (33) being in a display state, and a display state in which a preview of the at least one chat (14) and / or message (60) and / or digital element (33) is not displayed in the corresponding screen (42, 57) realized on the display of the device (4, 6) and occupies a specific range / area of ​​the screen, and a hidden state in which the at least one chat (14) and / or message (60) and / or digital element (33) is not displayed in the corresponding screen (42, 57) realized on the display of the device (4, 6) and does not occupy the specific range / area of ​​the corresponding screen that it occupied when in the display state.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an improved messaging system, and preferably to an improved instant messaging system. [Background technology]

[0002] Currently, messages exchanged through known messaging systems are protected from privacy and security by end-to-end encryption, specifically in this way ensuring that only the sender and the recipient can read and view the transmissions, and no one else, not even the messaging system administrators. However, all this happens automatically, i.e. without activating specific settings and without creating special secret chats, and therefore, with access to the sender's and / or recipient's devices, the content of the individual messages and chats can be viewed essentially at will.

[0003] So, in essence, access to chats, messages and content offered within a user's messaging system is currently exclusively conditioned on successfully passing an authentication system (password, access code or fingerprint) designed to access device-wide functionality (both when powered on and in standby).

[0004] Thus, in order for a third-party user, who is not the owner of a particular device, to be able to freely use the messaging system present on that device, the device owner must necessarily, as a precaution, correctly go through an authentication system, thereby unlocking all the functions of the entire device. However, in doing so, the third-party user can fully and indiscriminately view all the content present on the messaging system of the owner's device, and in particular, a series of conversations and / or messages that the owner wants to keep private for various reasons. Basically, there are situations where the device owner wants / has to allow the third-party user access to the messaging system (both in terms of viewing and use), but at the same time does not want the third-party user to fully and indiscriminately view how much content (in terms of conversations, messages and elements in general) is present on the messaging system itself.

[0005] In this regard, currently, within known instant messaging systems, there is no possibility of hiding certain messages of a chat, nor of hiding graphic and / or audio elements inserted in a message (e.g. emoticons, stamps and / or any multimedia elements), much less of hiding an entire chat, whether it is a chat between only two users or a chat between several users (group).

[0006] Thus, in some circumstances, users of messaging systems, both as senders and recipients, need to hide both the existence and content of entire chats and / or messages and / or graphical and / or audio elements within the system itself, so that these can only be displayed on the device's display after prior unlocking and authentication operations.

[0007] Patent document 1 basically proposes a system for "censoring" or "masking" messages, so that the messages are sent blank or with parts cut off, and the recipient receives the message and, in order to properly understand its contents, can unlock it so that it is displayed in its entirety by clicking on the corresponding button.

[0008] Patent document 2 describes a keyboard with various solutions that hide messages, for example by anagramming or removing some terms (prepositions, pronouns, conjunctions, etc.) By means of a button, the message can be unlocked so that it can be correctly reconstructed, so that the content of the message can be understood.

[0009] Patent document 3 describes a solution in which a message is sent blank or blurred and then displayed via a button activating Touch ID (fingerprint) so that its content can be understood.

[0010] Patent documents 1, 2 and 3 propose solutions to avoid undesirable situations where a third party can look over the shoulder of the device owner / administrator, peer into the display of another person's device and view or explore the content present on the device itself. However, these known solutions are not suitable to guarantee sufficient confidentiality in cases where a third party can obtain the device without the consent of the legitimate owner / operator of the device (e.g. as a result of the theft or loss of the device) or even if he does obtain the consent, and thereby directly and freely manage it, for example by accessing the release button, etc.

[0011] Furthermore, US Pat. No. 6,299,433, US Pat. No. 6,333,666 and US Pat. No. 6,493,898 propose solutions for "masking" the text of the message, while the presence of the message itself remains visible. In particular, the frame containing the text of the message remains visible even if it is empty or if the text is blurred, cut or rearranged in various ways. Thus, in this case, a third party who has obtained another person's device is always aware of the existence of the message, even if he or she cannot understand the content of the message. In other words, with the solutions of US Pat. No. 6,299,433 and US Pat. No. 6,333,666, the third party cannot read and understand the message, but still knows that a confidential secret message exists.

[0012] Moreover, the solutions of US Pat. Nos. 5,233,363, 5,389,403 and 5,433,520 always only obscure the text of the exchanged messages and thus configure them to be incomprehensible for both the sender and the recipient of said messages, and therefore do not allow for managing situations where the text of a message, or even the existence of an entire chat, must be made invisible only to the sender but visible to the recipient(s) or vice versa. [Prior art documents] [Patent documents]

[0013] [Patent Document 1] US Patent Application Publication No. 2015 / 007351 [Patent Document 2] US Patent Application Publication No. 2016 / 094495 [Patent Document 3] US Patent Application Publication No. 2018 / 219812 Summary of the Invention

[0014] The object of the present invention is to propose a messaging system capable of overcoming the above-mentioned drawbacks present in the prior art.

[0015] Another object of the invention is to propose a messaging system that makes it possible to hide both the existence as well as the content of chats, messages or their graphic and / or audio elements, thus avoiding fraudulent subjects becoming aware of their presence.

[0016] Another object of the invention is to propose a messaging system in which fraudulent subjects are unaware of the existence of chats and / or messages and / or graphic and / or audio elements that are hidden.

[0017] Another object of the invention is to propose a messaging system in which chats (i.e. message exchanges sent and received in the messaging system) can be hidden, so that the screen containing the chats concerned (chat rooms) is only viewable after a prior unlocking and / or authorization procedure.

[0018] Another object of the invention is to propose a messaging system in which chats (i.e. message exchanges sent and received in the messaging system) can be hidden, so that they appear viewable in the relevant overview preview screen of a user's chats only after a prior unblocking and / or authorization procedure has been carried out.

[0019] Another object of the invention is to propose a messaging system in which messages, both sent and received by it, can be hidden, so that the relevant frames containing the messages as well as the messages themselves can only be viewed after a prior unlocking and / or authorization procedure.

[0020] Another object of the invention is to propose a messaging system that makes it possible to hide the graphical and / or audio elements present in both messages sent and received through the messaging system, so that the place occupied by them in the messages, as well as the elements themselves, become viewable only after a prior unlocking and / or authorization procedure.

[0021] Another object of the invention is to propose a messaging system that allows hiding chats between multiple authenticated parties ("groups").

[0022] Another object of the invention is to propose a messaging system that allows creating sub-chats between groups of a main chat, or even between users of a main chat.

[0023] Another object of the invention is to propose a messaging system in which several systems can be used to unlock access to the contents present in said messaging system and to unlock the contents to display them.

[0024] Another object of the invention is to propose a messaging system in which a key can be shared between two or more users to access and display hidden content present in the messaging system.

[0025] Another object of the invention is to propose a messaging system that allows sharing of keys for accessing and viewing hidden content present in the messaging system, without the need for external means.

[0026] Another object of the invention is to propose an improved and / or alternative messaging system to the prior art.

[0027] Another object of the invention is to propose a messaging system with alternative features to the conventional ones, both in terms of functionality and implementation.

[0028] Another object of the invention is to propose a messaging system that is simple, easy and intuitive to use.

[0029] Another object of the invention is to propose a messaging system that allows reducing the consumption of resources of the hardware devices involved and reducing the bandwidth occupied by the network.

[0030] Another object of the invention is to propose a messaging system which is simple, fast and low-cost to implement.

[0031] According to the present invention, all these objects, as well as others arising from the following description, are achieved by means of a messaging system having the characteristics set out in claim 1. [Brief description of the drawings]

[0032] The invention will be further elucidated in the following preferred embodiments, purely by way of non-limiting example, with reference to the accompanying drawings, in which: [Figure 1] 1 shows a schematic diagram of a messaging system infrastructure according to the present invention; [Diagram 2] 1 shows a schematic diagram of a centralized database based messaging system infrastructure according to the present invention; [Diagram 3] 3 illustrates a schematic diagram of local subsets derived from the centralized database of FIG. 2 and downloaded locally to devices managed by a particular user. [Figure 4] An example of the centralized database of FIG. 2 is shown in schematic diagram form. [Diagram 5]5 illustrates a schematic diagram of an example of a local subset derived from the centralized database of FIG. 4 and downloaded onto devices managed by user "0001." [Figure 6] 2 shows a schematic diagram of a variant of a centralized database based messaging system infrastructure according to the present invention; [Figure 7] 7 illustrates a schematic diagram of a variation of a local subset derived from the centralized database of FIG. 6 and loaded locally on devices managed by a particular user. [Figure 8] FIG. 7 shows a schematic diagram of details of the database of FIG. 6 configured and populated by way of example for managing sub-chats; [Figure 9a] A list of only chats in the "unspecified" format is displayed, while chats in the specified format are shown in a hidden state. [Figure 9b] The screen of FIG. 9a is shown after an unlocking procedure has been performed to display chat in a specified format, thereby moving from a hidden state to a visible state. [Figure 10] 1 shows a screen where chat is displayed with relevant "unspecified" type messages while specified types are hidden, and 2 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 3 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 4 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 5 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 6 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 7 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 8 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 9 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 10 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 11 shows a screen where chat is displayed with relevant "unspecified" type messages hidden, while 12 shows a screen where chat is displayed with relevant "unspecified" type [Figure 11] 1 shows a screen in which chat is displayed with relevant "unspecified" style messages and graphic elements, with the specified style graphic elements in a hidden state, and 2 shows a screen in which the chat is displayed with relevant "unspecified" style messages and graphic elements in a hidden state, and 3 shows a screen in which the chat is displayed with relevant "unspecified" style graphic elements in a hidden state. [Figure 12]a shows a screen in which the keyboard is displayed with only the "unspecified" type graphic elements and the inserted specified type graphic elements are in a hidden state, and b shows the screen in a after an unlock procedure has been performed to display the specified type graphic elements, thereby moving from a hidden state to a visible state. [Figure 13] 14 illustrates a sequence of various screens that are displayed when going through the unlocking procedure to display chat in a specified format. [Figure 14] 14 illustrates a sequence of the various screens that are displayed when going through the procedure to access a specified style chat. [Figure 15] 1 shows the screen at the stage of inserting an access key. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] It should be noted in advance that hereinafter a "message" (60) refers to any set of both textual, graphical (both still and animated) and / or audio and / or video elements that are represented on the screen of a display and occupy a certain area of ​​said screen (a "display"). Preferably, said area is delimited by a frame (59), hereinafter defined as a "speech bubble", or may have a different graphical characteristic (e.g. color) than the background (and the rest of the screen) of said display. Advantageously, within the screen, each message (60), including its frame (59) and its textual, graphical and / or audio and / or video elements, is represented in such a way that it is separated or graphically separated from the other messages of the chat.

[0034] Specifically, the message (60) is written in a frame or speech bubble (59): - Text (39) only, or - only one or more graphic and / or audio elements (33), or - A combination of text (39) and one or more graphic and / or audio elements (33). may include:

[0035] Advantageously, the message (60) may include any digital element capable of being transferred via the Internet in addition to or instead of the text (39). Advantageously, the message (60) may include one or more multimedia elements, such as, but not limited to, graphic elements, audio elements, video elements, text documents, biometric identifiers or others, that are digitally represented and can be exchanged by the messaging system (2) according to the present invention in addition to or instead of the text (39).

[0036] In particular, the graphic elements (33) include symbols, icons or images in general (both still and animated) that are inserted in the speech bubbles (59) of the message itself, together with or between any text (39) or even without the latter. Preferably, although not necessarily, these images (33) represent a concept, emotion or mood, substantially corresponding to an "emoji".

[0037] By "chat" (14) or "conversation" is meant the set of all messages (60) exchanged between two users (i.e. between a sending user and a receiving user) or between several users (so-called "group chat") and regularly (and temporarily) displayed in a dedicated page or window (also called a "chat room") that is displayed on the screen (57) of the corresponding display. Advantageously, when creating a chat (14), the corresponding dedicated page or window may also be free of messages.

[0038] "Sub-chat" (49) means a specific type of chat that is subordinate to / derived from another chat (hereinafter referred to as "parent chat") and in which participating users are automatically all or a subset of users of the parent chat. Specifically, users who are not participating in the parent chat cannot be present in a sub-chat. A sub-chat is displayed in a dedicated page or window that is different from that of the parent chat, as it appears on the display screen. Preferably, when creating a sub-chat, the corresponding dedicated page or window may also be empty of messages.

[0039] "Avatar" (48) means a graphic representation used to verify the identity of a user when communicating with other users, for example in chat (14) or when sending messages (60).

[0040] "Item" means one or more chats (14), and / or one or more subchats (49), and / or one or more messages (60), and / or one or more graphic elements and / or sounds and / or media (33), and / or any digital element capable of being transmitted via the Internet.

[0041] By "action" is meant an input given by a user that is correctly and unambiguously detectable by a computer system. Preferably, the action includes a single tap ("tap"), a double tap ("double tap"), a scroll ("swipe"), or other movement that can be interpreted by a device with a touch screen. The action may also include a mouse click (single or double click), optionally assisted or replaced by pressing one or more keys of a keyboard if the device is in desktop form, or the pronunciation of a sound or a series of sounds, e.g. a word, if the device has voice commands, or may further include a facial expression or the framing of a defined pattern ("QR code" or barcode).

[0042] Advantageously, the messaging system according to the present invention may include one or more features provided in PCT / IB2018 / 055193, the disclosure content of which is intended to be incorporated herein by reference in its entirety.

[0043] Preferably, the messaging system of the present invention may include one or more features provided in PCT / IB2020 / 050173, the disclosure of which is intended to be incorporated herein by reference in its entirety.

[0044] As can be seen from the drawings, the messaging system infrastructure of the present invention is generally indicated using the reference numeral (2) and includes at least one sending device (4) and at least one receiving device (6), which are provided with communication means for transmitting and receiving data to and from at least one aggregation base station (8).

[0045] Preferably, the sending device (4) and / or the receiving device (6) may comprise a client, which may be a computer or a portable device, such as a smartphone or a tablet.

[0046] Preferably, the aggregation base station (8) may include at least a computer (10), such as a real server or a virtual remote server and / or a cloud system.

[0047] The first and second devices (4)(6) are configured to transmit a message (60) including text (39) and / or graphical elements (33) and / or audio (e.g., multimedia content) via an aggregation base station (8) through which both devices communicate, send and receive, over a network, either via the Internet or locally.

[0048] Conveniently, the first software module is loaded and / or executed on the first and second devices (4)(6), while the second software module is executed on the aggregation base station (8). Conveniently, in the case of a portable device such as a smartphone or tablet, the first software module consists of a native mobile software application, also known as an app. Advantageously, the first software module may also be in the form of a web application or a desktop application.

[0049] In particular, the first software module is configured to send the message (60) by making a request to the aggregation base station (8) (server) based on a communication protocol, preferably HTTP. Advantageously, this request is made by the PSOT method to send the content of the message (in particular in a data structure of a suitable form) to the aggregation base station (8) without indicating the content of the message in a search string (query string), although this request may also be made using the GET method, thereby transferring data in the search string.

[0050] Advantageously, data transfer between the devices 4, 6 and the aggregation base station 8 is performed according to a conventional client-server architecture, for example using the HTTP transfer / communication protocol (HyperText Transfer Protocol). Preferably, this transfer / communication protocol is secured, i.e. it is for example in the HTTPS format, using an encrypted connection, for example according to the TLS (Transport Layer Security) or SSL (Secure Sockets Layer) encryption protocols.

[0051] The first software module, loaded and executed on the receiving device (6), is configured to download from the aggregation base station (8) a message (60) (in the form of a structured data packet) sent by the sending device (4) and prepared by the aggregation base station (8). The download of the message (60) from the aggregation base station (8) by the receiving device (6) or, in any case, the transfer of the message (60) from the aggregation base station (8) to the receiving device (6) is preferably performed using a REST (REpresentational State Transfer) or GraphQL architecture, preferably, but not necessarily, over HTTPS protocol, or alternatively over MQTT over WebSockets.

[0052] Advantageously, the first software module loaded and executed on the receiving device (6) may be configured to periodically, at a predetermined frequency, access and query the aggregation base station (8) since there may be / may be one or more messages (60) addressed to the receiving device (6) and thus download said messages (60) from the aggregation base station (8) according to a client-server interactive mode called "polling".

[0053] Preferably, as shown in Fig. 1, the system (2) according to the invention may also include a notification platform (50), such as Google Cloud Messaging, or Apple Push Notification Service, or Firebase Cloud Messaging, which acts as an intermediary between the devices (4) (6) and the aggregation base station (8) and is configured to asynchronously notify the devices when new data intended for them is available at the aggregation base station, following a method called "push notification". In particular, for this purpose, the second software module is also configured to send a notification (52) to the notification platform (50) based on a message (60) sent by the sending device (4), which notification platform (50) is then configured to forward this alert to the corresponding receiving device (6). Advantageously, the notification (52) sent by the aggregation base station (8) to the notification platform (50) contains an identification code of the aggregation base station (8) sending the notification, an identification code of the receiving device (6) to which the notification has to be sent, and the content of the notification (52).

[0054] Preferably, the first software module loaded in the sending device (4) and / or the receiving device (6) is configured to have a first operating state in which a bidirectional connection with the aggregation base station (8) is established and maintained, and a second stationary state in which the sending device (4) and / or the receiving device (6) are not connected to the aggregation base station (8). Advantageously, the first software module is also configured, when in said first operating state, for the receiving device (6) not to periodically (i.e. in "polling" mode) query the aggregation base station (8) but only upon receiving a notification, preferably through the notification platform (50), according to a method called "push notification". Advantageously, correspondingly, when new data is available at the aggregation base station (8) for a particular receiving device (6) for which the first software module is in an operating state, the second software module is configured to send an alert to said receiving device (6) to query the aggregation base station (8). This allows the aggregation base station (8) to be queried only when there is new data to be downloaded, thereby avoiding periodic and unnecessary queries, which is particularly advantageous in that it reduces data traffic and in particular avoids unnecessary bandwidth consumption associated with data transmission.

[0055] Preferably, data in messages (60) exchanged between a sending device (4) and a receiving device (6) within the messaging system (2) is encrypted by an end-to-end encryption system.

[0056] Centralized Database (12) The aggregation base station (8) is loaded with (or associated with) at least one database (12) to appropriately define a centralized database containing, in an aggregated and organized manner, the data of all users of the messaging system (2) and of all items (chats, messages, graphic and / or audio elements) that can be created, managed and exchanged by the users within said messaging system (2).

[0057] The database (12) is conveniently and conventionally provided with support for storing data and a processor for processing the former (a database server) and software applications (i.e. a database management system) for creating, manipulating, managing and efficiently interrogating the data stored on the medium.

[0058] Preferably, as shown in FIG. 2, the database (12) includes: - a user data set (15) containing data on each user of the messaging system according to the invention, - a chat data set (18) containing data on all chats (14) of all users of the messaging system, - a messages data set (20) containing data on all messages (60) of all chats (14) of a messaging system, - one or more element data sets (22) containing at least a unique identification code (ID_ELEMENT) of all graphic elements (33) (both still and animated) and / or audio and / or video elements that can be managed through the messaging system (2); and in particular in the case of graphical elements, the data set includes for each graphical element at least a unique identification code of the graphical element (ID_ELEMENT), which preferably defines a primary key of the data set.

[0059] Conveniently, the user data set (15) contains a unique identification code of the user (ID_USER), which preferably defines a primary key for this data set.

[0060] The user data set (15) preferably includes the user's unique ID code, username and password, as well as preferably first name, last name, contact details (eg email address) and other conventional registration data.

[0061] The chat data set (18) preferably includes a unique identification code (ID_CHAT) for each chat (14), and preferably the chat's unique identification code (ID_CHAT) defines the primary key for this data set.

[0062] Preferably, the message data set (20) contains a unique identification code ID (MESSAGE_ID) for each message (60), which preferably defines the primary key for this data set.

[0063] Preferably, the element data set (22) contains, in addition to the unique identification code (ID_ELEMENT) of the graphic and / or audio element (33), the address / location (e.g. URL) of a further database in the cloud and, preferably, the exact address / location of the corresponding record in this further database, where the data defining the actual graphic and / or audio element (33) are systematically stored. Advantageously, according to a preferred embodiment, in the element data set (22) of the centralized database (12), the unique identification code (ID_ELEMENT) of the graphic and / or audio element (33) corresponds to an univocal address / location (preferably Web), which univocal address / location identifies the record in the further database (47) (in the cloud) where the data defining the actual element (33) are stored.

[0064] Advantageously, the database (12) is arranged and structured such that the user dataset (15) and the chat dataset (18) are related to each other by a first relationship (21) (which essentially constitutes a separate dataset) in order to link the data of each chat in the dataset (18) with the data of the two (or more) users of the dataset (15) participating therein.

[0065] Preferably, the database (12) is arranged and structured such that the chat dataset (18) and the message dataset (20) are related to each other by a second relationship (23) (which essentially constitutes a separate dataset) in order to link the data of each message (60) in the message dataset (20) with the data of the chats (14) exchanged in the chat dataset (18).

[0066] Preferably, the database (12) is arranged and structured such that the message data set (20) and the element data set (22) are related by a third relationship (25) (essentially constituting a separate data set) for linking the data of each message (60) of the message data set (20) with the data of the elements (33) contained in said message.

[0067] Advantageously, the database (12) is arranged and structured such that the user data set (15) and the element data set (22) are related by a fourth relationship (27) (basically constituting another data set) in order to link the data of each user or data of the user data set (15) with the data of the elements (33) of the element data set (22) to which each user has access and / or which are manageable / usable by each user. Advantageously, in said messaging system (2), each element (33) manageable within the messaging system (2) is provided with and associated with said unique identification code ID_ELEMENT.

[0068] Preferably, the messaging system (2) is configured such that each item generally (i.e., each chat (14) or message (60) or element (33)) that is created, exchanged, or generally exists within the messaging system (2) is: - a first form, hereinafter defined as "unspecified" (i.e. freely accessible / visible without specification), in which the corresponding item is always visible on the display of the device and is viewable without the need to carry out any unlocking procedure (preferably by prior authentication and / or by entering any access key), or - a second form, hereinafter defined as "designated" (i.e. accessing / displaying "secret" with designation), in which the appearance of the corresponding item on the display of the device is instead conditional on an unlocking procedure (preferably by prior authentication and / or by correctly entering a specific access key); It is configured to be in two forms:

[0069] In addition, the messaging system (2) is configured such that each item in the second "specified" format is - a first state, hereinafter referred to as "hidden", in which the item is not shown on the display of the device; or - a second state, hereinafter defined as "displayed", in which the item is displayed (fully and / or in preview) on a screen realized on the display of the device; It is configured to be able to take two states:

[0070] In particular, when the item in the second "designated" format is in a visible state, the item itself is displayed in full and / or in preview in the corresponding screen realized on the display of the device (4) and / or (6) and occupies a certain area / surface of the screen (see Fig. 9b, Fig. 10b, Fig. 11b and Fig. 12b). When the item in the "hidden" state is in a "hidden" state, the item is not displayed in the corresponding screen realized on the display of the device (4) and / or (6) and does not occupy the certain area / surface of the screen that it occupies when in a visible state, thereby avoiding awareness of its presence (see Fig. 9a, Fig. 10a, Fig. 11a and Fig. 12a). More particularly, when the item in the second "designated" format is in a "hidden" state, the corresponding display area that would be occupied by the item after the unlocking procedure is never realized on the display and / or is occupied by other (previous or next) items of the first format.

[0071] Advantageously, essentially, when a chat (14) is in the first "hidden" state, the relevant portion of the screen (42) containing the list of the user's chats, containing the chat preview, is not displayed or even realized as such (Fig. 9b). When a message (60) is in the first "hidden" state, the relevant frame (59) containing the content of said message is not displayed or even realized in the screen (57) of the corresponding chat (Fig. 10b). When a graphic and / or audio element (33) is in the first "hidden" state, the place occupied by said graphic and / or audio element in the message (60) (see Fig. 11b) or the keyboard (35) (see Fig. 12b) is not even displayed or is occupied by the surrounding text or graphic and / or audio elements of a first unspecified form. Thus, preferably, when an item of the second "designated" type (chat, message or graphical and / or audio element (33)) is in the first "hidden" state, there is no feedback or visible indication on the display that would allow one to be aware of the presence / existence of the hidden item in the messaging system.

[0072] Furthermore, the messaging system is preferably configured such that the unlocking procedure is configured for transitioning the items of the second "designated" type from the first hidden state to the second visible state, whereby after each failed attempt no visible feedback is provided regarding the failure / failed attempt, and preferably the screen remains the same. This is particularly advantageous in that a third party user who has acquired the device is not even aware of the existence of the designated items of the second type. Indeed, even after an unlocking attempt, either accidentally or spontaneously (e.g. by attempting to enter a password), with an incorrect result, the screen of the display remains the same and the third party does not receive any visible feedback (i.e. there is no message of the kind "wrong password"), and thus the latter does not notice whether the "designated" items of the second type are present or not.

[0073] Preferably, the first software module and / or the second software module are configured in the messaging system (2) to: - a first item in unspecified format, comprising at least one chat (14) and / or message (60) and / or digital element (33), always viewable within a corresponding screen realized on the display of the device (4) and / or (6), and - items of a second type, comprising at least one designated chat (14) and / or message (60) and / or digital element (33), a first non-display state, in which the at least one chat (14) and / or message (60) and / or digital element (33) is never realized or displayed in a corresponding screen realized on the display of the device (4) and / or (6) and therefore does not occupy any display area; a second display state in which said at least one chat (14) and / or message (60) and / or digital element (33) is realized or displayed in full and / or in a preview thereof on a corresponding screen realized on the display of the device (4) and / or (6), thus occupying the display; are created and configured to be exchanged.

[0074] Advantageously, for this purpose, the database (12) includes a user dataset (15), a chat dataset (18), a message dataset (20) and a named items dataset (70) related to the element dataset (22).

[0075] Preferably, each item in the second "specified" format defaults to the first hidden state.

[0076] Preferably, each item of the second "designated" format transitions from a hidden state to a visible state following an unlocking procedure performed on / by the device (4)(6) on whose display the item is intended to be viewed.

[0077] Preferably, each item in the second "specified" format automatically switches from a visible to a hidden state after a predefined time period and / or when the user performs a specific action on the device (4) and / or (6).

[0078] Preferably, in the messaging system according to the invention, each item of the second "designated" format is advantageously not always downloaded automatically from the server, but only if the unlocking procedure has been successfully performed (i.e. a positive result). This is advantageous both in terms of saving data consumption and in terms of confidentiality of the item management, which is downloaded locally to the device (4) and / or (6) from the aggregation base station (8) only after prior authorization. In particular, the designated items data set (70) is such that each record (71) of this data set: a unique identification code ID_ITEM of an item of the chat data set (18), the message data set (20) or the element data set (22), in particular the unique identification code ID_ITEM may be that of a chat (14), a message (60) or an element (33); a unique identification code ID_USER of a user of the user data set (15), in particular for a certain chat (14) or message (60), this identification code corresponds to the identification code of the user participating in said chat or being the sender / recipient of said message, while for an element (33), this identification code corresponds to the identification code of the user having access and / or able to manage / use said element, - a code identifying an access key (ACCESS_KEY) (5) to be entered / typed to enable viewing of the corresponding item on the display of / associated with the device (4)(6), The at least three fields are included:

[0079] Essentially, the specified item dataset (70) is associated with the user dataset (15), the chat dataset (18), the message dataset (20) and the element dataset (22), and thus the user's unique identification code ID_USER from the user dataset (15), the unique identification code ID_CHAT from the chat dataset (18), or the ID_MESSAGE from the message dataset (20), or the ID_ELEMENT from the element dataset (22) is entered and then combined with a code defining the access key (5) to display the corresponding chat (18), message (60) or element (33).

[0080] Preferably, the primary key of each record (71) of the specified item dataset (70) may be defined by a field related to the type of item ("item type"), a unique identification code of the corresponding item ID_ITEM (derived from the chat dataset (18) or message dataset (20) or element dataset (22)), and a unique identification code of the user ID_USER (derived from the user dataset (15)).

[0081] Instead, all items (chats (14), messages (60) and elements (33)) of the messaging system (2) according to the invention, regardless of their format, are uniquely identified in the database (12) by unique identification codes (i.e. the ID_CHAT, ID_MESSAGE and ID_ELEMENT codes are not only unique within one dataset but also unique among all datasets (18), (20), (22)). In particular, this means that in the database (12), each chat of the chat dataset (18) of the messaging system (2) has its own unique identification code ID_CHAT and is therefore certainly distinct and different not only from the identification codes of other chats in the chat dataset (18), but also from the unique identification codes ID_MESSAGE of the individual messages present in the message dataset (20) and the unique identification codes ID_ELEMENT of the individual elements of the element dataset (22). Thus, where appropriate, the primary key of each record in the specified dataset item (70) may be determined solely by the ID_CHAT, ID_MESSAGE and ID_ELEMENT primary keys used in the chat dataset (18), message dataset (20) and element dataset (22), respectively.

[0082] Advantageously, if a particular item for a particular user is present in the named item dataset (70), then that item will be a named item for that particular user only, and conversely, if a particular item for a particular user is not present in the named item dataset (70), then that item will be in an unnamed form for that particular user only.

[0083] More specifically, the chat dataset (18) contains data for all chats (14) (both unspecified and specified formats) exchanged in / through the messaging system (2), the messages dataset (20) contains data for all messages (both unspecified and specified formats) exchanged in / through the messaging system (2), and the elements dataset (22) contains data for all elements (both unspecified and specified formats) exchanged in / through the messaging system (2).

[0084] The named dataset item (70) contains identification data for only chats (14) or messages (20) or elements (33) in the named format. More specifically, this means that identification data for only chats (14) or messages (20) or elements (33) in the unnamed format does not have a corresponding record (71) in the named dataset item (70). Thus, essentially, not all identification codes for chats (14) or messages (20) or elements (33) in the respective datasets (18), (20), (22) are called out and present in the named dataset item (70).

[0085] Advantageously, within the messaging system (2), each item of a designated format (and therefore having a corresponding record (71) in the designated items dataset (70)) is by default in a "hidden" state, and only temporarily switches to a "displayed" state after proper prior insertion of a code corresponding to the access key (5) with which each item is associated in the designated items dataset (70).

[0086] Conversely, each item that is in unspecified format (and therefore does not have a corresponding record (71) in the specified items dataset (70)) always has a "displayed" state only, i.e., the item is always viewable (either fully and / or in preview) on a screen realized on the device's display.

[0087] Chat Dataset(18) Advantageously, the database (12) stores for each chat (14) created / conducted in the messaging system (2): the unique identifier of the chat ID_CHAT, in particular this code defines the primary key of the chat data set (18), - unique identification code of the user participating in the chat; - a code, which identifies a shared access key (ACCESS_KEY_CHAT) (80) that is identical (i.e., common) and shared among chat participants, which code is entered / typed to enable each chat participant to view the corresponding chat on the display of the corresponding device associated therewith; The fields are provided and / or configured and structured to be associated with the fields.

[0088] Advantageously, within the messaging system (2), each chat (14) comprises: - an unspecified format (14') for all participating users, in which the corresponding chat is always visible on the displays of all devices managed by the users participating in the chat, without the need for prior authentication and / or the need to enter any access key, or - a designated format (14") for all participating users, where the appearance of the corresponding chat on the displays of the devices managed by all participating users of the chat is instead conditioned on the correct insertion of a specific shared access key (80); It can take two forms:

[0089] Specifically, if the ACCESS_KEY_CHAT field is not valued (i.e., empty) or is valued according to a predefined default value, the chat (14) is in an unspecified format (14') for all participating users, and conversely, if the ACCESS_KEY_CHAT field is valued using a specific shared access key (80) (e.g., in the form of a string), the chat (14) is in a specified format (14") for all participating users.

[0090] Furthermore, within the messaging system (2), each chat (14) of a specified format (14") - "Viewed" state, where the entire chat and / or a preview of it is displayed on the screen realized on the display of the device; or - "Hidden" state where chat is not shown on the device display It can take two states:

[0091] Advantageously, within the messaging system (2), each chat (14) of a specified type (14") (and thus having an ACCESS_KEY_CHAT field populated with a particular shared access key (80)) is by default in a "hidden" state, and only temporarily transitions to a "displayed" state after a user participating in that chat has previously correctly inserted the code corresponding to the shared access key (80).

[0092] Conversely, each chat (14) of "unspecified" format (14') always has only the "displayed" state, i.e. the entire chat and / or its preview is always displayed on the screen realized on the device's display.

[0093] Advantageously, each chat (14) may include a field associated with a unique identification code of the user who created the chat and / or a field relating to the date the chat was created.

[0094] Message Data Set (20) Advantageously, the database (12) stores for each message (60) created / exchanged within the messaging system (2): a unique identification code (ID_MESSAGE) of the message (60), which preferably defines a primary key of the message data set (20), the identification code of the chat (14) to which the message (60) belongs, in particular the identification code of the chat (14) defined by the primary key ID_CHAT of the chat data set (18), - the unique identification code of the user who sent the message; - the unique identification code of the user(s) who received the message; - a code, which identifies a shared access key (80) (ACCESS_KEY_MESSAGE) to be entered / typed in order to be able to view a particular message (60) of the chat displayed on a screen realized on the display of the device or a display associated with the device, The fields are provided and / or configured and structured to be associated with the fields.

[0095] Advantageously, within the messaging system (2), each message (60) is an unspecified format (60'), in which the corresponding message (60) is always visible in a particular chat (14) for all participants in that chat (14), without the need to authenticate beforehand and / or to insert a shared access key (80), or - a specified format (60"), in which the display of the message in the chat (14) to which it belongs for all participants in the specific chat (14) is conditional on the correct insertion of a specific shared access key (80); It can take two forms:

[0096] Specifically, if the ACCESS_KEY_MESSAGE field is not populated (i.e., empty) or is populated according to a predefined default value, the message (60) is in an unspecified format (60') for both the sending user and the recipient(s); conversely, if the ACCESS_KEY_MESSAGE field is populated with a specific shared access key (80) (e.g., in the form of a string), the message (60) is in a specified format (60") for both the sending user and the recipient(s).

[0097] Further, within the messaging system (2), each message (60) of a specified format (60") is - "View" state, in which the entire message and / or a preview of it is displayed on the screen realized on the display of the device, or - "Hidden" state where no messages are shown on the device display It can take two states:

[0098] Advantageously, within the messaging system (2), each message (60) of a specified format (60") (and thus having an ACCESS_KEY_MESSAGE field populated with a particular shared access key (80)) defaults to a "hidden" state and only temporarily switches to a "displayed" state after the correct prior insertion of the code corresponding to the shared access key (80).

[0099] Conversely, each message (60) of type "unspecified" (60') always has a "displayed" state only, i.e. its content and / or a preview thereof is always viewable on a screen realised on the display of the device.

[0100] Advantageously, each message (60) also comprises: - the date the message was created, - The date when the ACCESS_KEY_MESSAGE field related to the shared access key (80) was entered In this way, the date when a particular message in the chat became visible subject to the proper prior insertion of a particular shared access key (80) (i.e., when the message (60) became in the specified format) is recorded accordingly.

[0101] Element Data Set (22) Advantageously, the database (12) stores for each graphic and / or audio element (33) inserted in a message (60) created / exchanged within the messaging system (2): a unique identification code (ID_ELEMENT) of the graphic and / or audio and / or media element (33) in general, which preferably defines the primary key of the element data set (22), - the unique identification code of the message (60) in which said graphic and / or audio element (33) is to be inserted, in particular the unique identification code of the message (60) defined by the primary key of the message data set (20), - a code identifying a shared access key (80) (ACCESS_KEY_ELEMENT) to be inserted / typed in order to be able to view, on a screen realized on a display of the sending user's and / or the receiving user's device / a display associated with the device, a particular graphical and / or audio element in the message (60) displayed in the corresponding chat to which the message (60) belongs, The fields are provided / configured and structured to be associated with the fields.

[0102] Preferably, within the messaging system (2), each element comprises: an unspecified format (33'), in which for all users of a particular message (60), the corresponding element (33) is always visible in the message (60) to which it belongs, without the need to authenticate beforehand and / or without the need to insert a shared key access (80), or - a specified format (33"), in which the appearance of the element (33) in the message (60) to which it belongs, for all users of a particular message (60), is conditional on the correct insertion of a specific public access key (80) for that element (33); It can take two forms:

[0103] In particular, if the “ACCESS_KEY_ELEMENT” field is not provided with a value (i.e., it is empty) or is set according to a predefined default value, the element (33) is of unspecified form (33′) for all users (both senders and recipient(s)); conversely, if the “ACCESS_KEY_ELEMENT” field is provided with a value using a specific shared access key (80) (e.g., in the form of a string), the element (33) is of specified form (33”) for all users (both senders and recipient(s).

[0104] Furthermore, within the messaging system (2), each element (33) of the specified format (33") is - "Show" state, where the element is shown in its entirety and / or a preview of it on a screen realised on the device's display, or - "Hidden" state, in which the element (33) is not shown on the device display It can take two states:

[0105] Advantageously, within the messaging system (2), each element (33) of a specified format (33") (and thus having an "ACCESS_KEY_ELEMENT" field populated with a particular shared access key (80) is in a "hidden" state by default, and is temporarily moved to a "displayed" state only after the correct prior insertion of the code corresponding to the shared access key (80).

[0106] Conversely, each element (33) of the unspecified format (33') always has only the "display" state, i.e. its content and / or its preview is always viewable on a screen realised on the display of the device.

[0107] Advantageously, each graphic and / or audio element (33) inserted in a message (60) created / exchanged within the messaging system (2) is provided with: - the unique identification code of the user who has entered the "ACCESS_KEY_ELEMENT" field relating to the shared access key (80), thus keeping track of the person who has made a particular element (33) in the message (60) visible subject to the correct precautionary insertion of a given key (5); - the type of a particular element, which may for example relate to a graphic element (e.g. an emoji or avatar) or to an audio or video element, - The date when the ACCESS_KEY_ELEMENT field related to the shared access key (80) was entered may be associated with one or more fields, suitably thus keeping track of the date that a particular element (33) in a message (60) became displayed dependent upon the correct prior insertion of a particular shared access key (80).

[0108] Software Module A first software module is loaded and / or executed in the sending device (4) and / or the receiving device (6).

[0109] A second software module configured to manage communication with the sending device (4) and the receiving device (6), and thus managing the sending and receiving of messages and notifications, is advantageously loaded and / or executed in the aggregation base station (8).

[0110] In the following, an "item" means one or more chats (14) and / or one or more messages (60) and / or one or more graphic and / or audio elements (33). In particular, an "item" also means even a sub-chats, as will be made clearer hereinafter.

[0111] Create an item with a specified format only for specific users (see Figure 9) Preferably, the first software module, when executed on the device, is configured to create in the database (12) a new record (71) for a specified data set item (70) in which one or more items linked to a user logged into the messaging system (2) are associated with a personal access key (5), thereby creating the items in the specified format for that user.

[0112] Specifically, the first software module is a new record (71) in a specified item data set (70), - ID_ITEM identification code of a particular item, - the ID_USER identification code of the user logged in to the messaging system (2) and associated with the item in question, - the access key ACCESS_KEY(5) that the user logged into the messaging system (2) wants to be associated with that particular item; The system is configured to create a new record (71) including:

[0113] Preferably, the ID_ITEM identification code for a particular item is: - ID_CHAT identification code of the chat (14) in which the user logged into the messaging system (2) is participating, or - the ID_MESSAGE identification code of the message (20) sent / received by the user logged in to the messaging system (2), or - ID_ELEMENT identification code of the element (33) used in the message by the user logged in to the messaging system (2) may include:

[0114] Advantageously, in this manner, a particular item will be in designated form only for those users who have a corresponding ID_USER identification code associated with the ID_ITEM identification code of that particular item in the designated item dataset (70).

[0115] In effect, it may occur, for example, that a particular message has been created in a specified format for the sending user (i.e., there is a corresponding record (71) in the specified dataset item (70) in which the ID_MESSAGE identification code of the message is combined with the ID_USER identification code of the sending user and the KEY_ACCESS access key), while for the receiving user the message remains in an unspecified format (i.e., there is no corresponding record in the specified dataset item (70) in which said ID_MESSAGE identification code of the message is combined with the ID_USER identification code of the receiving user).

[0116] Displaying items with a specified format for a specific user (see Figure 10) Preferably, the first software module, when executed on the device, is configured such that an item that is in a designated format for that particular user logged into the messaging system (2) (i.e. has a corresponding record in the designated dataset items (70)) is temporarily changed from a “hidden” state to a “displayed” state after correct precautionary insertion of the item's ID_ITEM identification code in the corresponding record (71) of the designated items dataset (70) and the corresponding ACCESS_KEY code of the access key (5) associated with the ID_USER identification code of the user logged into the messaging system (2).

[0117] Advantageously, a first software module running on the device is configured to implement a display unlock procedure configured to transition items that are of a specified type for a particular user from a "hidden" state to a "displayed" state. Preferably, this procedure comprises: - receiving an access code entered by a user by performing an operation on the device on which the first software module is executed, preferably on a keyboard (35) provided on the device or on a keyboard (35) displayed on a touch screen display of the device, - checking whether there exists in the specified items data set (70) items (i.e. chats (14) and / or messages (60) and / or graphic and / or audio elements (33)) whose access key ACCESS_KEY code (5) corresponds to the code entered by the user and whose unique ID_USER identification code corresponds to the code of the user logged in to the messaging system, - only if the verification result is positive, the corresponding item(s) having an access key (5) associated to the logged-in user and given a value using the same code entered by the user are displayed (completely and / or even partially by preview), whereas if the verification result is negative, the corresponding item(s) are not shown on the display of the device.

[0118] Advantageously, items of a specified type have a "hidden" state by default and transition to a "displayed" state after an unlock procedure is performed, but items of a specified type only remain in this "displayed" state temporarily (for a predetermined period of time and / or until the user performs a specific action on the device and / or a specific event occurs) and then revert to the "hidden" state until another display unlock procedure is performed.

[0119] Preferably, a first software module executing on the device is configured to temporarily display, on the device's display, items that are in a specified format for a particular user (i.e., those that have a corresponding record (71) in the specified items dataset (70)).

[0120] Advantageously, the first software module executed on the device is configured to automatically prevent the display of the device from displaying the item in the specified format (thus switching it from a "display" state to a "hidden" state) after a predetermined time interval, which can preferably be set by the user, has elapsed.

[0121] Advantageously, the first software module executed on the device is configured to automatically prevent the display of the device from displaying the item in the specified format (thus transitioning it from a "display" state to a "hidden" state) after a user performs a particular action on the device (e.g. a double "tap" on a particular area of ​​the touch screen and / or a long press of a particular key). Preferably, the first software module executed on the device is configured to: - Actions on dedicated on-screen buttons implemented on the device's touchscreen display (e.g. "tap"); - closing or migrating a background dedicated messaging system application; - Action to lock the device screen, - Putting the device into standby or turning it off, - the act of starting a new chat (14) within the messaging system; - The action of returning to the previous screen or changing the screen being displayed is configured to automatically prevent the device's display from displaying the item in the specified format (thus transitioning it from a "display" state to a "hidden" state) following an event activated by one or more of the actions of

[0122] Local Personal Subset Advantageously, each device acting as a sender and / or receiver within the messaging system (2) includes a local memory (90) into which the personal subset (75) derived from the centralized database (12) of the aggregation base station (8) is downloaded and stored, the local memory (90) including all data of items (chats (14), messages (60) and / or elements (33)) of a particular user logged into the messaging system (2) using that particular device.

[0123] Conveniently, the local memory (90) may be a mass memory or a primary memory or a RAM memory, or may be a cache.

[0124] Preferably, the personalized subsets (75) are generated from the centralized database (12) and downloaded and stored in the local memory (90) of the corresponding devices controlled by the users logged into the messaging system (2) with that device.

[0125] Advantageously, the personal subset (75) has a structure that substantially corresponds to the structure of the centralized database (12), but does not include the user dataset (15). In particular, the personal subset (75) includes a chat dataset (18'), a messages dataset (20'), an elements dataset (22') and a named items dataset (70'), each of which specifically includes only corresponding items that are tied to a user who is a user who has logged into the messaging system (2) with / on that particular device.

[0126] Advantageously, according to the invention, the first software module executed on the sending device and / or on the receiving device and the second software module loaded on the aggregation base station (8) are synchronized after the first login and / or after each access to the messaging system (2) on a particular device: - a first software module of the sending device (4) and the receiving device (6) transmits to the aggregation base station (8) data (username and password) entered by the user by performing an action on the device (4) and / or (6) when logging into the messaging system (2); - a second software module of the aggregation base station (8) therefore verifies the received login data (i.e. preferably consults the user data set (15) of the centralized database (12) to check whether both correspond to a user already registered in the messaging system) and extracts the ID_USER identification code of the corresponding user, and thus uses the extracted code to identify all items in the designated items data set (70) in the centralized database (12) at all times, and preferably all items in the chat data set (18), the message data set (20) and the element data set (22) that are associated, preferably through a relationship, with the ID_USER identification code of that user; - a first software module of the sending device (4) and / or the receiving device (6) downloads, as appropriate, the identified items defining the personal subset (75) to a local memory (90) of the device (4) and / or (6). It is configured as follows.

[0127] Advantageously, in this case, when an item of the designated type, which by default has the "hidden" state, is downloaded to the local memory (90) of the device (4) and / or (6) (thus creating locally a personal subset (75) of the designated items data set (70)), it still has the "hidden" state, and preferably only moves to the "displayed" state after a display unlock procedure in which a verification step is performed within said personal subset (75) present in the local memory (90). Advantageously, in this way, a faster speed is obtained for the data access and verification step.

[0128] Instead, when items of designated type, which by default have a "hidden" state, are not downloaded to the device's local memory (90), the verification phase of the unlocking procedure is performed in the designated items data set (70) present in the database (12) loaded into the aggregation base station (8). Advantageously, in this way, better data security is ensured.

[0129] Advantageously, a synchronization step between the database (12) of the aggregation base station (8) and the personal subset (75) of the device's local memory (90) is performed each time a user accesses and / or logs into the messaging system (2) through the device (4) and / or (6). Moreover, advantageously, the aggregation base station (8) may send to each device (4) and / or (6) the items managed and / or exchanged in the messaging system (2) as soon as the items become available on the aggregation base station, preferably via a push notification system.

[0130] Preferably, the first and second software modules are configured such that each new record (71) relating to an item of the designated type is automatically added both to the designated data set item (70) in the database (12) located at the aggregation base station (8) and to the designated data set item (70') of the personal subset (75) located in the local memory (90) of the sending and / or receiving device.

[0131] Advantageously, the first and second software modules are adapted to: each new record, which may relate to an item of unspecified or specified type, - a chat data set (18), a message data set (20) and / or an element data set (22) of a database (12) provided in an aggregation base station (8), and - chat data set (18'), message data set (20') and / or element data set (22') of the personal subset (75) provided in the local memory (90) of the sending device and / or the receiving device; will be configured to be automatically added to the

[0132] Preferably, the first and second software modules are configured to search only the personal subset (75) provided in the local memory (90) of the device for items of unspecified type and items of specified type displayed on the corresponding screen of the device.

[0133] Preferably, the first software module and the second software module are configured to search for items of unspecified type and items of specified type displayed on the corresponding screen of the device in a personal subset (75) provided in a local memory (90) and in a centralized database (12) provided in the aggregation base station (8), preferably first in the personal subset (75) and then in the centralized database (12).

[0134] Subchat Advantageously, the above also applies to the sub-chat (49), which is essentially a separate chat, - It is a specified format, - It is derived from the main chat (hereinafter referred to as the "parent chat") and, specifically, is essentially parallel to the latter.

[0135] Suitably, a sub-chat (49) is structured such that its participants are all participants or a sub-group of the parent chat.

[0136] Thus, advantageously, a sub-chat (49) comprises a series of messages exchanged in sequence between a sender and at least one recipient (particularly, in the case of a group chat, two or more recipients) who also participate in the parent chat. Advantageously, each sub-chat may have a number of participants equal to or less than the number of participants in the parent chat, and in particular, the set of participants in a sub-chat may be a subset of the participants in the parent chat.

[0137] Thus, advantageously, only users of a parent chat may participate in sub-chats derived from that parent chat and, where appropriate, may access the sub-chat using a key associated with that sub-chat. Furthermore, participants in a sub-chat are only aware of the existence of the sub-chat when a user of the parent chat creates the sub-chat and, where appropriate, shares this information with other users of the parent chat as that user selects.

[0138] Preferably, the display / realization of the sub-chat (49) may be on a separate, dedicated screen different from that of the parent chat (14) to which the message belongs. Advantageously, this separate screen is automatically realized upon correct insertion of the shared access key (80) and may occupy the entire display of the device (thus completely covering the previous screen) or may occupy only a part of it (preferably so that the parent chat (14) remains in the background).

[0139] Advantageously, to manage the sub-chats, the database (12) comprises a data set chat (18) including: - it may not be given a value (i.e., it is an empty "null" value) or it may be given a value according to a predefined default value, meaning that the corresponding chat (14) of the record (76) is a parent chat, not subordinate to or derived from other chats (i.e., it is not a sub-chat); - may be given a value with a unique identification code of a particular Chat (14), meaning that the corresponding Chat of the record (76) is a Sub-Chat (49) that is subordinate to / derived from a Parent Chat (14) It is constructed and structured such that a separate PARENT_CHAT field is provided.

[0140] Advantageously, furthermore, in the chat data set (18), a record (76) having a PARENT_CHAT field populated with a unique identification code for a particular chat (14) also has an ACCESS_KEY_CHAT field populated with a code identifying a shared access key (80) so that a participant of a sub-chat (49) (whose identification code is the value populated in the USER field of the chat data set (18)) can switch said sub-chat from a hidden state to a visible state. Advantageously, in this way, the sub-chat (49) is always in a designated form only.

[0141] Basically, if a particular record (76) in the chat dataset (18) has both the PARENT_CHAT and ACCESS_KEY_CHAT fields with values ​​assigned (and no default values), then the corresponding chat is a sub-chat (49); conversely, if a particular record (76) in the chat dataset (18) has no values ​​assigned (or is assigned values ​​using default values) in the PARENT_CHAT and ACCESS_KEY_CHAT fields, then the corresponding chat is either a parent chat (14) of a sub-chat or a simple chat with no sub-chat.

[0142] Additionally, the chat data set (18) is configured such that the user field of a sub-chat (49) contains all or part of the unique identification code of a user participating in the corresponding parent chat (14).

[0143] Advantageously, the database (12) is configured and structured such that each message (60) of the message data set (20) exchanged within (and therefore linked to) a sub-chat (49) is automatically in the specified format.

[0144] Advantageously, the database (12) is configured and structured in such a way that each element (33) of a message (60) exchanged within (and therefore linked to) a sub-chat (49) is automatically in the designated format. Advantageously, all messages (60) and / or all elements (33) of a sub-chat (49) are in the designated format because the corresponding screens containing them, in particular the screens of the sub-chats (49) concerned, are in the designated format.

[0145] Advantageously, the first software module is configured to at least temporarily download the subchat (49) in the designated format to the local memory (90) of the device (on which it is executed) only after successfully performing and completing a download unlock procedure, as described in more detail below. Advantageously, furthermore, the subchat (49) in the designated format is downloaded to the local memory (90) of the device (after performing the download unlock procedure) and is shown temporarily on the display of the device (without or after performing the display unlock procedure), and is then automatically removed from the local memory of the device. Therefore, in this case, another download unlock procedure must be performed before the subchat (49) can be viewed again (i.e. to switch it from the "hidden" to the "visible" state).

[0146] Download unspecified and specified items completely locally Advantageously, in a first embodiment, the first software module is configured to download to the local memory (90) of the device on which it is executed a personal subset (75) of all items (i.e., both unspecified and specified types) associated with a user logged into the messaging system (2) on that device.

[0147] Preferably, in this case, the first software module also - items of the personal subset (75) that are in unspecified format (i.e. those that do not have a corresponding record (71') in the specified items data set (70') and for which the corresponding code of the shared access key (80) of the chat data set (18') or the message data set (20') or the element data set (22') is not valued or is valued using a predefined value) can always be automatically shown on the display of the device on which the first module is executed (i.e. without the need to insert a personal access key (5) or a shared access key (80) beforehand to be able to view them), - items of the personal subset (75) that are of a specified format (i.e. have a corresponding record (71') in the specified items data set (70') and the corresponding code of the shared access key (80) of the chat data set (18') or the message data set (20') or the element data set (22') is given a value and no predefined value is used) can be viewed on the display of the device only after correct, precautionary insertion of the code corresponding to the personal access key (5) or the shared access key (80); It is configured as follows.

[0148] Advantageously, a first software module executed on the device is configured to perform an undisplay procedure, the undisplay procedure being configured to transition items of the second type (i.e. "designated" items) from a "hidden" state to a "displayed" state. Preferably, the procedure comprises: - receiving an access code entered by a user by performing an operation on the device on which the first software module is executed, preferably on a keyboard (35) provided on the device or shown on a display of the device, - storing the access code input by the user in a memory, reloading the corresponding screen, and checking whether or not there is an item having a personal access key (5) or a shared access key (80) corresponding to the input access code in a personal subset (75) present in a local memory (90) of the device among items associated with the screen (specifically, the chat realized on the screen); - only if the verification result is positive, on the corresponding screen of the display of the device (4) the corresponding item is displayed (completely and / or even partially by means of a preview) having a personal access key (5) or a shared access key (80) which has been given a value using the same code entered by the user, whereas, conversely, if the verification result is negative, said item is not shown on the display of the device.

[0149] Advantageously, items of a specified type have a "hidden" state by default and move to a "visible" state after an unlock procedure is performed, but items of a specified type only remain in this "visible" state temporarily (for a predetermined period of time and / or until the user performs a specific action on the device and / or a specific event occurs) and then return to the "hidden" state until another display unlock procedure is performed.

[0150] Preferably, a first software module executed on the device is arranged to cause items of a second format to be temporarily shown on a display of the device itself.

[0151] Advantageously, the first software module executed on the device is preferably configured to automatically remove the item of the specified type from the device's display (thus transitioning it from a "displayed" to a "hidden" state) after a predetermined time interval, which may be set by the user.

[0152] Advantageously, a first software module executed on the device is configured to automatically remove the specified format of the item from the device's display (thus transitioning it from a "displayed" state to a "hidden" state) after a user performs a particular action on the device (e.g. a double "tap" on a particular area of ​​the touchscreen and / or a long press of a particular key).

[0153] Advantageously, the first software module executed on the device (4) comprises: - Actions on dedicated on-screen buttons implemented on the device's touchscreen display (e.g. "tap"); - Moving the dedicated messaging system application to the background or closing it; - Action to set device lock screen, - Putting the device into standby or turning it off, - the act of starting a new chat (14) within the messaging system; - The action of returning to the previous screen or changing the screen being displayed and automatically removes the item of the specified format from the device's display (thus causing it to switch from a "show" state to a "hide" state) following an event triggered by one or more of the operations of.

[0154] Pre-download only unspecified items locally In a second embodiment, the first software module is also configured to pre-download into the local memory (90) of the device on which it is executed only items of unspecified type that are associated with a user logged into the messaging system (2) on that device.

[0155] Advantageously, in this way, only items of unspecified format are downloaded to the local memory (90) of the device and are therefore always automatically viewable on the display of the device, without the need to previously insert a personal access key (5) or a shared access key. Advantageously, in this case, the first software module is also configured so that the downloaded items are always automatically viewable on the display of the device on which it is executed (i.e. without the need to previously insert a personal access key (5) or a shared access key (80) in order to be able to view them).

[0156] Advantageously, in this second embodiment, the first software module is also configured to at least temporarily download items of a specified format into the local memory (90) of the device (on which said module is executed) only after the user has previously correctly inserted a code corresponding to said personal access key (5) or said shared access key (80).

[0157] In particular, a first software module executed on the device and a second software module executed on the aggregation base station (8) are configured to interface with each other to implement a download unlock procedure configured to locally download items of a specified format. Preferably, this procedure comprises: - the first software module of the device transmits to a second software module of the aggregation base station (8) a code entered by the user by performing an action on his device, preferably on a keyboard (35) provided on the device or on a keyboard (35) shown on the display of the device, a second software module of the aggregation base station (8) for verifying the received data, in particular checking whether there is an item in the centralized database (12) addressed to that particular user logged into the messaging system, with a personal access key (5) or a shared access key (80) corresponding to the code entered by the user; - only if the verification result is positive, the first software module downloads (completely and / or even partially by preview) from the aggregation base station (8) the corresponding item having the personal access key (5) or shared access key (80) whose value has been assigned using the same code entered by the user to the local memory of the device (on which the module is executed), whereas, conversely, if the verification result is negative, the first software module does not perform any download.

[0158] Thus, preferably, once downloaded to the device's local memory, these items in the designated format can also be viewed directly on the device's display (without the need to perform any display unlock procedure). Advantageously, in this case, items in the designated format that have a default "hidden" state automatically switch to a "displayed" state once downloaded to the device's local memory after a download unlock procedure has been performed, and only remain in the "displayed" state temporarily (for a predefined period of time and / or until the user performs an action on the device and / or a specific event occurs), before reverting to the "hidden" state and remaining there until another download unlock procedure is performed.

[0159] Instead, once downloaded to the local memory of the device on which the first software module is running, these items are shown on the display of the device only after the user has correctly entered, as an additional precaution, a code corresponding to said personal access key (5) or said shared access key (80) (i.e. by performing the display unlock procedure as described above). Advantageously, in this case, items of a designated type that have a "hidden" state by default, once downloaded to the device's local memory (90) after performing the download unlock procedure, still have a "hidden" state, and only move to a "display" state after performing the display unlock procedure. Moreover, these items only temporarily maintain the "display" state (for a predefined time and / or until the user performs a specific action on the device and / or until a specific event occurs), and then revert to the "hidden" state and remain in that state until another download unlock procedure is not performed.

[0160] Advantageously, items in the specified format are downloaded to the device's local memory (90) (after a download unlock procedure has been performed), briefly shown on the device's display (either without or after a display unlock procedure), and then automatically removed from the device's local storage. Thus, in this case, another download unlock procedure must be performed before the items can be viewed again (i.e., to switch from a "hidden" to a "display" state).

[0161] Personal access key or shared / common access key Advantageously, the code used to populate the Personal Access Key (5) (i.e., ACCESS_KEY in the Named Items Data Set (70) or (70')) or the Shared / Common Access Key (80) (i.e., ACCESS_KEY_CHAT in the Chat Data Set (18) or (18')) field to display the items of the named format is: - an alphanumeric sequence and / or a special character sequence and / or a punctuation symbol sequence, and / or - a sequence of graphic elements (33) in the form of being sent within the messaging system within the limits of the screen occupied by the message (preferably within a frame or speech bubble (59)), advantageously comprising symbols, icons or images in general inserted / selected on an insertable keyboard (35) shown on the display of the device, preferably these images representing concepts, emotions or moods, essentially corresponding to "emojis", - media sequences available in the device's memory, - Responses to open-ended questions, - Biometric codes (fingerprint, retina, iris, facial recognition or voice recognition, etc.) may include:

[0162] Preferably, the Personal Access Key (5) (essentially constituting a "password") or Shared / Common Access Key (80) fields may be defined by homogenous graphic element sequences that can be inserted alone in the message bubble and / or alongside the text in the message itself.

[0163] Preferably, the first software module is configured in such a way that a code corresponding to a personal access key (5) or a shared / common access key (80) is entered and inserted by the user by performing an operation on the device on which the software module is executed, and that during said insertion, this is shown on the display of the device itself, possibly in a mode in which individual components of the code are blurred in the conventional way by using appropriate symbols (e.g. asterisks or dots) in order to transition items of a specified type from a hidden state to a visible state.

[0164] Instead, the first software module is configured in such a way that the code corresponding to the personal access key (5) or the shared / common access key (80), entered and inserted by the user by performing an action on the device on which said software module is running, to move the item of the specified format from the "hidden" state to the "display" state, is never shown on the display of the device itself, in particular not even the individual components of said code are blurred. In other words, when the user performs an action on the typing keyboard (35) and enters said code, the screen realized on the display shown by the device (or at least the part of the screen not occupied by said keyboard (35)) remains substantially the same.

[0165] Preferably, the first software module is configured such that the method of entering a code corresponding to a personal access key (5) or a shared / common access key (80) for transitioning an item of a specified type from a "hidden" to a "displayed" state is activated automatically after entering a specific sequence (tag) of pre-coded characters / symbols / graphic elements (61) before and / or after said access key (5) by means of the typing keyboard (35) (see FIG. 5) or after a specific action is performed by the user on the device (e.g. a double "tap" on a specific area of ​​the touch screen and / or a long press on a specific key).

[0166] Preferably, a sequence of pre-coded characters / symbols / graphic elements, essentially functioning as a "tag", is entered before and after the access key (5). So basically, when the first software module receives a particular sequence of letters / symbols / pre-coded graphic elements or senses a particular action, it wakes up and automatically goes into a "listening" mode, whereby the next insertion made using the typing keyboard (35) is considered as a component of the code defining a personal access key (5) or a shared / common access key (80).

[0167] Modes of operation within the messaging system Advantageously, the first software module comprises: - the item has the specified format from the time of the item's creation (start), and / or - Already created and started items with the unspecified format are converted to the specified format or vice versa It is configured as follows.

[0168] Advantageously, for this purpose, the first software module is configured to allow the user to operate in a first mode (called "hidden"), such that all new items created (i.e. one or more chats (14) and / or one or more messages (60)) or used (i.e. one or more elements (33) inserted in a message) are automatically in the specified format. In particular, in this case, the first software module is configured such that the first mode ("hidden") operates in conjunction with / subordinate to the insertion / typing of a personal access key (5), so that the latter is automatically associated with all items created or used by operating in this first mode.

[0169] Advantageously, the first software module may be configured to allow the user to operate in a second mode (called "public"), where all items created (i.e. one or more chats (14) and / or one or more messages (60)) or used (i.e. one or more graphic and / or audio elements (33) inserted in a message) will be in the unspecified format. Advantageously, in this case, the first software module may be configured to allow the user to select one or more items, which will be in the specified format after entering / typing the corresponding personal access key (thus automatically associated with said items and creating a record (71) corresponding to the specified data set item (70)).

[0170] Preferably, to activate / enter the first mode (called "hidden") and / or convert a selected item from an unspecified to a specified format, a dedicated icon (hereinafter called the "secret icon") is selected, for example by touch ("tap") or clicking with the pointer, and is realised on a screen shown on the device's display.

[0171] screen Preferably, the first software module is also configured to realize, on the screens of the devices (4)(6), a number of screens related to different functions realized in the messaging system (2) according to the invention.

[0172] Advantageously, the first software module is configured to display a typing keyboard (35) on the display of the device, the typing keyboard (35) comprising, on one or more pages, alphanumeric characters, special characters, punctuation symbols, as well as graphic and / or phonetic elements (33). Preferably, the typing keyboard (35) is realised so as to occupy the lower part of the display of the device.

[0173] Advantageously, the first software module is configured to realize, within the screen shown on the display of the device, corresponding selectable areas (47) (preferably defined by dedicated icons (47') and / or suitably defined from a graphical point of view) which, when selected after an external activation event (for example by a short touch "tap" in case of a "touch screen" type display or by clicking for example with a pointer), command the activation of one or more corresponding dedicated functions. Advantageously, said selectable areas (47) are identified by icons (47') or dedicated writing, which represent or are linked to the corresponding functions to be activated.

[0174] Display items with a specified format Advantageously, the first software module is configured such that when the item of the specified format is in the "display" state (and thus displayed within a screen realized on the display of the device), it is displayed together with the item of the unspecified format. Preferably, but not necessarily, in this case, the first software module may also be configured such that when the item of the specified format is in the "display" state, it has a different graphical aspect (e.g. in terms of color and / or shading and / or border) than the item of the unspecified format.

[0175] Instead, the first software module is configured to display an item of the specified type alone, i.e., without any items of the unspecified type, when the item of the specified type is in the "display" state (and thus displayed within a screen realized on the display of the device).

[0176] operation The operation of the messaging system (2) according to the present invention will be apparent from the above description, and preferably, certain specific features are described and presented below for illustrative and non-limiting purposes only.

[0177] As specified above, it is reiterated that hereinafter "item" means one or more chats (14) and / or one or more messages (60) and / or one or more graphic and / or audio elements (33).

[0178] Create a personal access key (5) Advantageously, when a particular user logs into the messaging system (2), the first software module is configured to create and associate a personal access key (5) with one or more items.

[0179] For example, preferably, to do this, the user selects, by a predefined action, e.g. by "tapping", a dedicated icon (e.g. identified by a key symbol) displayed on the screen of the messaging system (2), relating to, e.g., a "user profile".

[0180] Preferably, this selection opens a page where there are various operations to be performed.

[0181] The user may conveniently select, by a specific action, the operation related to the creation of a personal access key (5).

[0182] The user then completes the operation by entering the selected access code using the insert type keypad (35) on the device and selecting the confirm icon. Preferably, action taken on the confirm icon automatically and appropriately stores the code entered by the user in the database (12) (i.e., a corresponding record is created for each item in the designated items data set (70)). Thus, the code entered by the user and stored in the database (12) in this manner may subsequently be used as an access key to display one or more items of the designated type associated with the user logged into the messaging system (2) on that device.

[0183] Remove personal access keys Conveniently, the first software module is configured to remove a previously created personal access key (5) from the local memory of the device.

[0184] Preferably, the first software module is configured such that removing a previously created personal access key (5) automatically removes any named items associated therewith. Alternatively, the first software module is configured such that removing a previously created personal access key (5) causes any named type items associated therewith to become unnamed type and therefore always viewable (i.e., the corresponding records (71) in the named items dataset (70)).

[0185] Create an item with a specified format for a specific user To create a custom format item for a particular user, the following flow chart steps are provided where appropriate.

[0186] [Table 1]

[0187] Create a chat with a specific format To create a chat with a specific format (14), the user must: - opening the "Conversations" screen (42) in which a list (preferably with a partial preview) of the various chats in which the user is a sender or recipient is displayed, - Tap the "Secret" icon on the "Conversation" screen (42) - Opens a dedicated screen showing various functions exclusive to the first mode (hidden), - Tap the icon to create a new chat, - Enter your personal access key (5), - Select recipient contacts The operation can be carried out.

[0188] Instead, to create a chat (14) of the specified format (14"), the user (16) - Create a new chat(14), - Select the recipient user you want to chat with, - Tap the "Secret" icon on the screen of the chat you just created (14) (empty), - Enter your personal access key (5), - confirm that the chat (14) is in the specified format (14"); - insert the first message (60) into the chat (14) thus created The operation can be carried out.

[0189] It should be understood that, preferably, within a chat in a designated format (14"), all messages exchanged therein, as well as all graphical and / or audio elements within the messages, are automatically in the designated format.

[0190] Convert chat from unspecified to specified format To convert an already created chat (14) from the unspecified format (14') to the specified format (14"), the user must: - opening the "Conversations" screen (42) in which a list (preferably with a partial preview) of the various chats in which the user is a sender or recipient is displayed, - On the "Conversations" screen, long press ("press and hold") or drag horizontally ("slide to scroll") on the row of the list of chats in the first ("Unspecified") format (14') to select a specific chat, - Open a new menu with different options - Tap the "Secret" icon in the menu - Enter your personal access key (5), - Determines that the chat is now in the second ("specified") format (14"). The operation can be carried out.

[0191] It should be understood that, preferably, within a chat (14") in a designated format, all messages exchanged therein, as well as all graphical and / or audio elements within the messages, are automatically in the designated format.

[0192] Create one or more messages in a specified format within a chat in an unspecified format To create one or more messages (60) of a specified format (60") within a chat of an unspecified format, a user: - Open a specific chat (14) in the unspecified format (14') in the screen (57), - Tap on the "Secret" icon on the screen related to that particular chat, - Enter your personal access key (5), - Enter a message (60) that will be in the specified format (60") from the time the item is created (started). The operation can be carried out.

[0193] Convert one or more messages from the default format to the default format in a chat To convert one or more messages (60) in a chat in a default format from the default format (60') to a second default format (60"), a user may: - Open a specific chat (14) in the unspecified format (14') in the screen (57), - long press ("press and hold") on the area of ​​the screen occupied by a message (60) displayed on the screen of that particular chat to select that particular message, - Tap on the "Secret" icon on the screen related to that particular chat, - Enter your personal access key (5), - Confirm that the message (60) selected in this way has been changed to the specified format (60"), and preferably, confirm that the screen of this message has disappeared from the corresponding chat screen (57). The operation can be performed.

[0194] Converting specified format elements in unspecified format chats and messages To convert one or more graphic and / or audio elements (33) from the plain format (33') to the specified format (33") within a message (60) of a chat (14), both of which are in the plain format, the user: - Open a specific chat (14) in the unspecified format (14') in the screen (57), - long press ("press and hold") on the area of ​​the display occupied by a particular graphical and / or audio element (33) within a message (60) (displayed on the screen of that particular chat), thus selecting that particular element, - Tap on the "Secret" icon on the screen related to that particular chat, - Enter your personal access key (5), - determining that the graphic and / or audio element (33) thus selected has taken on the designated form (33") and, preferably, that this element, which was made visible, has disappeared from the corresponding screen (57) of the chat; The operation can be carried out.

[0195] Display lock release procedure (see Figure 14a to Figure 14d) Advantageously, with regard to a display unlock procedure for moving items of the second ("specified") type (chat, one or more messages, one or more graphic and / or audio elements) from a "hidden" state to a "displayed" state, the user may: - opening the "Conversations" screen (42), which shows a list (preferably with a partial preview) of the various chats (14') in which the user is a sender or a recipient, in a non-specific format only; - Tap the selection icon (43) on the "Conversation" screen (42), - Open the menu (44) with various functions, - Tap the menu function (45) related to displaying items with a specified format, - opening another screen (46) for typing the components of the code defining the access keys, preferably using a typing keyboard (35) implemented on the touch screen display of the device, - Enter your personal access key (5), - opening a screen (47) in which the items of the designated form are displayed / realized, thereby moving them from the "hidden" state to the "displayed" state, preferably so that the items of the designated form (14"), in particular the chats, are graphically distinguished from the items of the undesignated form (14'), for example by the presence of a symbol (51), as shown in FIG. 9b or FIG. 13d. The operation can be carried out.

[0196] Displaying items with a specified format for a specific user Advantageously, to view items of a specific type for a particular user, the following flow chart steps are provided.

[0197] [Table 2]

[0198] Create an access key that can be shared / shared between two or more users to access a sub-chats Advantageously, the first software module comprises: - Create a common / shared access key (80) associated with a sub-chat (49) derived from a parent chat (14) and used to move that sub-chat (which is always by default only in the specified format) from hidden to visible, - sharing the created common / shared access key (80) for all or some of the users participating in the parent chat (14) so ​​that, after correctly inserting the common / shared access key (80), the corresponding item of the subchat (49) (which is therefore in the specified format) can be viewed on the display of each of the devices of the users participating in the subchat; It is configured as follows.

[0199] Preferably, but not necessarily, once created by a first user participating in a sub-chat, the key is shared with other users participating in the sub-chat by transmitting the key within the messaging system (2) of the present invention in a suitable secured mode performed by the messaging system (2).

[0200] Create a sub-chat with a specified format within an unspecified chat (see Figure 11) To create a sub-chat (49) with a specified format within a chat with an unspecified format (14') (which becomes the corresponding parent chat (14)), a user participating in the parent chat can - opening the "Conversations" screen (42) in which a list (preferably with a partial preview) of the various chats (possibly parent chats) of the first type (14') of which the user is a sender or a recipient is displayed, - Select a specific chat by long pressing ("press and hold") or dragging ("slide to scroll") or "tapping" on the row of the list of primary ("unspecified") style chats (potential parent chats) displayed on the "Conversations" screen, - Tap on the "Secret" icon (47) on the screen (42), - opening another screen (46) for typing components of the code defining the shared / common access keys (80), preferably using a typing keyboard (35) implemented on the touch screen display of the device, - Enter the shared / common access key (80), - opening a separate window (53) in which a sub-chat (49) of a specified format is displayed in relation to or within a parent chat (14) (and therefore within or for some of the participants of the parent chat (14)); The operation can be performed and preferably the subchat (49) will initially have no messages.

[0201] Preferably, - sending an invitation to all or some of the users of the parent chat (14) to join the subchat (49), which will automatically be in the designated format for them; - Sending the same common / shared access key (80) to the devices of all or some of the users participating in the parent chat, thereby changing the sub-chat (49) of the specified format from the "hidden" state to the "displayed" state, i.e. displaying messages and / or graphic elements present in the sub-chat (49). Two other operations are also provided:

[0202] Preferably, to create a custom type sub-chat for participating users, the following flow chart steps are envisaged.

[0203] [Table 3]

[0204] Accessing a subchat with a specified format within a chat with no specified format (see Figure 12 and Figures 14a to 14c) In order to access a sub-chat (49) of the specified type within a parent chat of the unspecified type (14'), a user - opening the "Conversations" screen (42) in which a list (preferably with a partial preview) of the various chats in a non-specific format (14') is displayed, of which the user is a sender or a recipient; - long press ("press and hold"), drag horizontally ("slide to scroll"), or "tap") on a row in the list of chats in the first unspecified format (14') displayed on the "Conversations" screen (42) to select a specific parent chat; - Tap on the "Secret" icon (47) on the screen, - Enter the shared / common access key (80), - opening a screen (53) in which the subchat (49) of the specified format associated with the shared / common access key (80) in question (and therefore the messages (60) and / or the graphic and / or audio elements (33) present in the latter) is displayed; Specifically, in this manner, the subchat (49) is shifted from the "hidden" state to the "displayed" state.

[0205] Preferably, to view a sub-chats of a specific type for participating users, the following flow chart steps are provided.

[0206] [Table 4]

[0207] Remove shared / common keys Advantageously, the first software module is also preferably configured to remove previously created shared / common access keys (80) without requiring the consent of other users participating in the sub-chat.

[0208] Preferably, the first software module is configured such that removing a previously created shared / common access key (80) automatically removes any sub-chat of designated type associated therewith. Alternatively, the first software module is configured such that removing a previously created shared / common access key (80) automatically removes any sub-chat of designated type associated therewith.

[0209] conclusion From what has been said so far, the messaging system according to the invention is particularly advantageous in that it allows the user to selectively hide certain chats and / or messages and / or graphic and / or audio elements within the system itself, thus making it impossible for even a third party who had to access the device and the messaging system to freely and automatically make visible all items with related content present in the messaging system and exchanged and / or used.

[0210] Specifically, in the messaging system of the present invention, a potential third party who must access or obtain the device will never be able to view and understand the contents of the designated items without successfully performing an unlocking procedure, and most importantly, will never be able to notice or know that the designated items exist. In other words, preferably, in the messaging system of the present invention, a potential third party will have no way of knowing / recognizing whether the designated content (i.e., the second type of content) exists or not.

[0211] Furthermore, the particular configuration of the database and the designated item dataset means that the same item exchanged within the messaging system can be in different formats (i.e., "designated" or "public") for the sending user and / or the receiving user, and may even be in different formats among multiple receiving users. For example, the same chat / message / element may have a second format (designated) for the sending user while being in a first format (i.e., undesignated) for the receiving user, or vice versa.

[0212] Furthermore, the particular configuration of the database means that users can force the same items exchanged within the messaging system to be in the same format (i.e., "designated" or "public") for both the sending user and the receiving user(s).

Claims

1. A messaging system (2), comprising: at least one sending device (4) and at least one receiving device (6) configured to send and / or receive messages (60) by at least one aggregation base station (8) with which both are in communication; a first software module that is loaded and / or executed on the sending device (4) and / or the receiving device (6), and a second software module that is loaded and / or executed on the aggregation base station (8); The first software module and / or the second software module, in the messaging system (2), items of a first type (14', 60', 33') that can be freely accessed and / or displayed, comprising at least one chat (14) and / or message (60) and / or digital element (33) that is always viewable in a corresponding screen (42, 57) realized on the display of said device (4, 6); and A second type (14", 60", 33") of items with access and / or viewing restrictions, comprising at least one chat (14) and / or message (60) and / or digital element (33), said at least one chat (14) and / or message (60) and / or digital element (33) comprising: a display state, in which the at least one chat (14) and / or message (60) and / or digital element (33) in its entirety and / or a preview thereof is displayed in a corresponding screen (42, 57) realized on the display of the device (4, 6) and occupies a certain area / region of the screen; a hidden state, in which the at least one chat (14) and / or message (60) and / or digital element (33) is not displayed in the corresponding screen (42, 57) realized on the display of the device (4, 6) and does not occupy the particular range / area of ​​the corresponding screen (42, 57) that it occupied when in the visible state, and is configured to transition from the hidden state to the visible state after an unlocking procedure and / or an authorization procedure. A messaging system, characterized in that it is arranged for:

2. 2. The messaging system of claim 1, wherein when the second type of item (14", 60", 33") is in the display state, the messaging system (2) displays the second type of item (14", 60", 33") on the corresponding screen (42, 57) together with the first type of item and / or within the first type of item, if the first type of item is present.

3. The first software module comprises: The item is of said second type (14", 60", 33") from the time of creation (initiation) of said item; and / or A messaging system according to any one of claims 1 to 2, characterized in that it is arranged so that already created and initiated items of the first format (14', 60', 33') are converted into the second format (14", 60", 33") or vice versa.

4. The messaging system of any one of claims 1 to 3, characterized in that the first software module and / or the second software module are configured to transition an item (14, 60, 33) of the second format (14", 60", 33") from the hidden state to the visible state after a suitable execution of the unlocking procedure on / by the device (4, 6) on whose display the item is intended to be viewed.

5. A messaging system according to any one of claims 1 to 4, characterized in that the unlocking procedure is arranged to provide no visible feedback on a failed attempt for each negative attempt.

6. A messaging system according to any one of claims 1 to 5, characterized in that the first and / or second software modules are configured such that the items in the second format (14", 60", 33") are downloaded locally to each device (4, 6) only if the unlocking procedure performed on / by the device (4, 6) on whose display the items are intended to be viewed is successful.

7. The messaging system of any one of claims 1 to 6, characterized in that the first software module and / or the second software module are configured such that items (14, 60, 33) of the second format (14", 60", 33") are in the hidden state by default and automatically change from the visible state to the hidden state after a predefined time has elapsed and / or when a user performs a specific action on the device (4, 6).

8. The messaging system according to any one of claims 1 to 7, characterized in that the first software module and / or the second software module are configured such that the unlocking procedure is provided with an access code associated with the item (14, 60, 33) of the second format (14", 60", 33") for appropriate typing using a keyboard (35) of the device (4, 6) intended to be viewed on a display.

9. The messaging system according to any one of claims 1 to 8, characterized in that the first software module and / or the second software module are configured such that an unlocking access code (5, 80) of the unlocking procedure comprises alphanumeric characters and / or special characters and / or punctuation symbols.

10. The messaging system according to any one of claims 1 to 9, characterized in that the first software module and / or the second software module are configured such that an unlocking access key code (5, 80) of the unlocking procedure comprises a graphic element (33) in the form of which it is transmitted within the messaging system (2) within the area of ​​the screen occupied by the message.

11. A messaging system according to any one of claims 1 to 10, characterized in that the first software module is configured such that an input mode corresponding to an access key code (5, 80) is activated automatically after inserting, by means of a typing keyboard (35), a specific sequence (tag) of pre-coded letters / symbols / graphic elements (61) in front and / or behind the access key code (5, 80).

12. The messaging system of any one of claims 1 to 11, characterized in that the first software module executed on the device (4, 6) is configured to perform a display unlock procedure configured to transition the items (14, 60, 33) in the second format (14", 60", 33") from the hidden state to the displayed state for a particular user.

13. The messaging system of any one of claims 1 to 12, characterized in that the first software module executed on the device (4, 6) and the second software module executed on the aggregation base station (8) are configured to interface with each other to perform a download unlock procedure before downloading items (14, 60, 33) in the second format (14", 60", 33") to the local memory of the device (4, 6).

14. The messaging system according to any one of claims 1 to 13, characterized in that the messaging system is configured such that for a particular user, items (14, 60, 33) of the second format (14", 60", 33") are switched to the display state only after they have been fully downloaded to a local memory (90) of the device (4, 6) where the user is logged in and a display unlock procedure has been performed.

15. A messaging system according to any one of claims 1 to 14, characterised in that the items (14, 60, 33) of the second format (14", 60", 33") for a predetermined one are shown directly on a display of the device (4, 6) once they have been downloaded into a local memory (90) of the device.

16. The messaging system according to any one of claims 1 to 15, characterized in that the at least one aggregation base station (8) comprises at least one database (12) in which a user data set (15) comprising at least one unique identification code (ID_USER) of each user of the messaging system (2) is associated (27) with at least one element data set (22) comprising at least one unique identification code (ID_ELEMENT) of all digital elements (33) that can be managed through the messaging system (2), thereby defining the digital elements (33) accessible / manageable by each user of the user data set (15).

17. At least one database (12) comprises a chat data set (18) containing at least one unique identification code (ID_CHAT) of each chat (14, 49) of said messaging system (2) and related to a message data set (20) containing at least one unique identification code (ID_MESSAGE) of all messages (60) exchanged within said messaging system (2), wherein said chat data set (18) is related to a user data set (15) to define users participating in each chat (14, 49); A messaging system according to any one of claims 1 to 16, characterised in that the message data set (20) is related to an element data set (22) in such a way as to ultimately link to each message (60) at least one digital element (33) which is inserted / contained in each message.

18. A messaging system according to any one of claims 1 to 17, characterized in that at least one database (12) contains a data set (70) with items of said second type related to a user data set (15) and a chat data set (18) and / or a message data set (20) and / or an element data set (22).

19. The data set (70) of items of the second type has records (71) each of which: a first field that is populated or associated with an identification code of the chat (14) or message (20) or element (33); a second field associated with or populated with a unique identification code (ID_USER) of a user associated with said chat (14) or said message (20) or said element (33); a third field whose value is given by a code defining an access key (5) associated with said chat (14) or said message (20) or said element (33) of said record (71); 20. The messaging system of claim 18, configured to include:

20. 20. The messaging system of claim 19, characterized in that the first and / or second software modules are configured such that if a particular record (71) is present in the dataset (70) of items of the second format with an identification code of a particular chat (14) and / or message (60) and / or element (33), the chat (14) and / or message (60) and / or element (33) will be in the second format only for a user having a unique identification code (ID_USER) corresponding to the second field of the particular record (71).

21. The messaging system according to any one of claims 1 to 20, characterized in that the first software module and / or the second software module and / or the centralized database (12) are configured such that if a particular record (71) with an identification code of a particular chat (14) and / or message (60) and / or element (33) exists in the dataset (70) of items of the second type, the particular record (71) is displayed on the display of the device managed by the user having a unique identification code (ID_USER) corresponding to the second field of the particular record (71) on the condition that the user correctly inserts a code corresponding to an access key (5) provided in a third field of the particular record (71).

22. The first software module and / or the second software module, in the messaging system (2), at least one chat (14) of said first type (14'), which is always visible on the display of the device (4, 6) managed by all users participating in the chat; At least one chat (14) of said second type range (14″) as a result of said unlocking procedure: a first non-display state, in which the at least one chat (14) is not shown on the displays of the devices (4, 6) managed by all users participating in the chat; The messaging system according to any one of claims 1 to 21, characterized in that there is at least one chat (14) of the second type range (14") transitioning between a second display state, in which the at least one chat (14) in its entirety and / or a preview thereof is displayed on a screen realized on the display of the device (4, 6) managed by all users participating in said chat.

23. The messaging system of any one of claims 1 to 22, characterized in that the chat data set (18) includes at least one field having a code identifying a shared access key (ACCESS_KEY_CHAT (80)), said shared access key (ACCESS_KEY_CHAT (80)) being identical for all participants of a chat and being entered / typed so that each chat participant can view the corresponding chat on a display of the corresponding device or a display associated with the corresponding device.

24. Each device (4, 6) functioning as a sender and / or receiver within the messaging system (2) includes a local memory (90) into which a personalized subset (75) derived from the centralized database (12) of the aggregation base station (8) is downloaded and stored, the local memory (90) including all data for items (14, 60, 33) of a particular user logged into the messaging system (2) using that particular device; The messaging system according to any one of claims 1 to 23, characterized in that the first software module and / or the second software module are configured to search in the personal subset (75) provided in the local memory (90) of the device for the items of the first type and the items of the second type (14, 60, 33) displayed on a corresponding screen of the device.

25. The first software module and / or the second software module detects that in the messaging system (2) there is at least one chat in the form of a sub-chat (49), said at least one chat in the form of a sub-chat (49) being: The second type, It is derived from the main chat (14) which defines the chat format of the parent chat, A messaging system according to any one of the preceding claims, characterised in that the participants of the sub-chat are arranged to be all participants or a sub-group of the main chat (14).

26. The messaging system of any one of claims 1 to 25, characterized in that the chat data set (18) includes a field that is populated with a code identifying a shared access key (80), the shared access key (80) being the same for all participants of a chat and entered / typed so that each chat participant can download and / or view the corresponding chat on the display of the device, and the first software module and / or the second software module and / or the centralized database (12) are configured such that, in a particular record of the chat data set (18), if a value is given in the field (ACCESS_KEY_CHAT), then the chat of the particular record is a sub-chat (49).

27. The messaging system of any one of claims 1 to 26, characterized in that the chat dataset (18) includes another field (PARENT_CHAT) that is populated with a unique identification code of a particular chat (14), and the first software module and / or the second software module and / or the centralized database (12) are configured such that if, in a particular record of the chat dataset (18), the other field (PARENT_CHAT) is populated with a value, then the chat of the particular record is a sub-chat (49).

28. A messaging system according to any one of claims 1 to 27, characterised in that the database (12) is arranged and structured so that each message (60) of a message data set (20) exchanged within a subchat (49) and therefore bound to the subchat (49) is automatically in said second format (60").

Citation Information

Patent Citations

  • Message hiding service providing method in chat window

    JP2019102092A

  • Apparatus and Method for Providing Message Hidden Services in Chatting Windows

    KR101896199B1

  • Mobile Messaging Enhanced with Concealable and Selectively Revealable Text, Image, and Video Messages

    US20150007351A1

  • Methods and systems for obscuring text in a conversation

    US20160094495A1

  • Mobile app messaging platform system

    US20180219812A1