Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/10—Office automation; Time management
  • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
  • H04L51/21—Monitoring or handling of messages
  • H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/12—Messaging; Mailboxes; Announcements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W84/00—Network topologies
  • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

• the invention relates to thread processing in a mobile communication apparatus.
• a thread refers to an electronic discussion.
• a set of messages may be grouped visually. Such a set may be called a topic thread or simply thread.
• the messages may be grouped visually in a hierarchy by a topic. Storage of information into threads is known from electronic mail systems or from electronic discussion forums, for example.
• a person may send a message and another person may reply to it. Threads are processed in a centralized manner, i.e. a server maintains and stores the threads and messages into a database, whereas the clients create them.
• the present invention seeks to provide an improved mobile communication apparatus, an improved method, and an improved computer program.
• a mobile communication apparatus as specified in claim 1 .
• Figure 4 illustrates embodiments of a user interface
• Figure 5 illustrates a method
• Figure 6 illustrates a combination of two threads
• Figure 8 illustrates a further embodiment of the mobile communication apparatus.
• the mobile communication apparatus may also be a user terminal which is a piece of equipment or a device configured to associate the user terminal and its user with a subscription and allows a user to interact with a communications system.
• the user terminal presents information to the user and allows the user to input information.
• the user terminal may be any terminal capable of receiving information from and/or transmitting information to the network, connectable to the network wirelessly.
• FIG. 1 discloses an embodiment of a mobile communication apparatus (MCA) 100.
• the mobile communication apparatus 100 may refer to a portable communication device.
• Such communication devices include wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: mobile phone, smartphone, personal digital assistant (PDA), other portable communication devices possibly including computer functionalities or functionalities of other data processing devices.
• SIM subscriber identification module
• PDA personal digital assistant
• the mobile communication apparatus 100 comprises a telecommunications interface 106 configured to establish wireless local ad hoc data transfer connections to other mobile communication apparatuses 1 10, 1 12, 1 14, 1 16.
• the wireless connection may be implemented with a wireless transceiver operating according to the GSM (Global System for Mobile Communications), WCDMA (Wideband Code Division Multiple Access), WLAN (Wireless Local Area Network) or Bluetooth® standard, or any other suitable standard/non-standard wireless communication means.
• the mobile communication apparatus 100 also comprises a processor 104.
• the processor 104 may be implemented as an electronic digital computer, which may comprise a working memory (RAM), a central processing unit (CPU), and a system clock.
• the CPU may comprise a set of registers, an arithmetic logic unit, and a control unit.
• the control unit is controlled by a sequence of program instructions transferred to the CPU from the RAM.
• the control unit may contain a number of microinstructions for basic operations. The implementation of such microinstructions may vary, depending on the CPU design.
• the program instructions may be coded by a programming language, which may be a high-level programming language, such as C, Java, etc., or a low-level programming language, such as a machine language, or an assembler.
• the electronic digital computer may also have an operating system, which may provide system services to a computer program written with the program instructions.
• the processor 104 may also be implemented as one or more integrated circuits, such as application-specific integrated circuits ASIC. Other hardware embodiments are also feasible, such as a circuit built of separate logic components. A hybrid of these different implementations is also feasible.
• a thread comprises messages (old/new), and the (old/new) message may comprise textual data, multimedia data, visual data, audio data, and/or metadata.
• the thread thus constitutes a multimedia collage of the performance.
• Metadata may be created automatically. Metadata may be location data created by a GPS (Global Positioning System) receiver, for example. Metadata may also be other context data, and it may be created by various sensors (a temperature sensor, for example) of the mobile communication apparatus 100.
• GPS Global Positioning System
• Metadata may also be other context data, and it may be created by various sensors (a temperature sensor, for example) of the mobile communication apparatus 100.
• Thread processing may be used for other recreational uses as well.
• People may use it for various types of communication, as it enables storage and presentation of information in the form of threads, even without a network infrastructure.
• Threads may freely spread among the users. Threads may evolve in an organic fashion, i.e. there may exist numerous different versions of one thread, as they may have spread over a large geographical area or to varying demographic groups of people, for example.
• thread processing Another use case of thread processing is to use it for information distribution in crisis areas, where no communication network infrastructure may exist or it has been destroyed. Relief action personnel may use the threads in disaster areas for communication, in an earthquake area, for example.
• the processor 104 is configured to request in a user-initiated fashion through the telecommunications interface 106 an old thread 120 from a first mobile communication apparatus 1 10.
• the processor 104 is configured to request through the telecommunications interface 106 an old message 122 belonging to the old thread 120 from a second mobile communication apparatus 1 12.
• the processor 104 is configured to compile a new thread 126 dynamically and cumulatively from the old thread 120, and a new message 124.
• the processor 104 is configured to transmit through the telecommunications interface 106 the new thread 126 to a third mobile communication apparatus 1 14 on the basis of a request 132 received from the third mobile communication apparatus 1 14.
• the processor 104 is configured to transmit through the telecommunications interface 106 the new message 124 to a fourth mobile communication apparatus 1 16 on the basis of a request 134 received from the fourth mobile communication apparatus 1 16.
• the mobile communication apparatus 100 also comprises a generator 102 configured to create the new message 124, and a memory 107 configured to store the new thread 126 and the new message 124.
• the described thread processing starts with an old thread 120 obtained from the first and second mobile communication apparatus 1 10, 1 12.
• the new thread 126 is distributed to the third mobile communication apparatus 1 14.
• the third mobile communication apparatus 1 14 has passed the new thread 126 to the fourth mobile communication apparatus 1 16, which requests the new message 124 belonging to the new thread 126 from the mobile communication apparatus 100 that created the new message 124.
• the generator 102 further comprises a user interface 200 configured to create the new message 124.
• a user 202 may use the user interface 200 to view the old thread 120 and the old message 122, and to manipulate the new thread
• the memory 108 is further configured to store other data 130
• the generator 102 is further configured to recognize a predetermined feature from the old message 122, and to create the new message 124 from a portion of the other data 130 having a feature similar to the predetermined feature.
• the predetermined feature may be a feature relating to metadata of the old message 122, and/or a feature relating to the contents of the old message 122, for example.
• Figure 7 illustrates combination of messages. Two family members, a daughter and a boy, have each prepared a shopping list 700, 702: the daughter wants one kilogram of apples, and the boy wants a new bicycle. Each of these messages 700, 702 also comprises other data, in this case metadata.
• the metadata relates to a context that these members of the family have defined for the shopping list.
• the context is defined as "after work” and "when at the mall".
• the metadata may be defined automatically or by a user operation.
• a third family member, father arrives at the mall after his work, and his mobile communication apparatus automatically creates a new message/thread 704, from the messages 700, 702 of his children.
• the mobile communication apparatus of the father may automatically detect that the metadata requirements set by the children for their messages 700, 702 are met before the new message/thread 704 is created.
• the shopping list of the father 704 is the combination of the shopping lists 700, 702 of his children.
• Figure 8 illustrates a further embodiment of the mobile communication apparatus.
• the other data 130 stored in the memory 108 may be data 800 from the user, data 802 from an old message/thread, data 804 from the other mobile communication apparatus(es), or other data already mentioned such as metadata, location data, etc.
• the generator 102 utilizes the other data 130, inter alia, in order to generate the new message 124 and/or the new thread 126.
• a feature recognizer 806 may recognize a feature or features from the other data 130.
• a similarity indicator 808 may evaluate similarity of a feature between two different instances of the other data 130. If the similarity exceeds a similarity threshold 810, a new message 124 or a new thread 126 may be created based on the other data 130 in a creation block 812.
• An embodiment provides a computer program provided on a carrier and comprising computer executable instructions for causing a mobile communication apparatus 100 to request in a user-initiated fashion through a wireless local ad hoc data transfer connection an old thread from a first mobile communication apparatus; request through a wireless local ad hoc data transfer connection an old message belonging to the old thread from a second mobile communication apparatus; create a new message; compile a new thread dynamically and cumulatively from the old thread and the new message; store the new thread and the new message; transmit through a wireless local ad hoc data transfer connection the new thread to a third mobile communication apparatus on the basis of a request received from the third mobile communication apparatus; and transmit through a wireless local ad hoc data transfer connection the new message to a fourth mobile communication apparatus on the basis of a request received from the fourth mobile communication apparatus.
• the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
• carrier include a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example.
• the computer program may be executed on a single electronic digital computer or it may be distributed amongst a number of computers.
• the telecommunications interface 106 comprises a short-range wireless transceiver 300 operating without a fixed network infrastructure with the other mobile communication apparatus.
• the short-range wireless transceiver may operate according to the Bluetooth standard, for example.
• the short-range wireless transceiver 300 may be used to receive the old thread 120 and the old message 122 from the other mobile communication apparatus, and to transmit the new thread 126 and the new message 124 to the other mobile communication apparatus.
• the embodiments of the mobile communication apparatus 100 may be implemented on a platform provided by a normal mobile telephone, as it includes all the necessary structural parts, the telecommunications interface 106, the processor 105 and the memory 108.
• the additional features/parts may easily be implemented on top of the platform with suitable software and hardware components. All modifications and configurations required for implementing a functionality of an embodiment may be performed as routines, which may be implemented as added or updated software routines, application circuits (ASIC) and/or programmable circuits, for example.
• software routines may be downloaded into an apparatus.
• the apparatus may be configured as a computer or a microprocessor, such as a single-chip computer element, including at least a memory for providing a storage area to be used for arithmetic operation and an operations processor for executing the arithmetic operation.
• Figure 6 illustrates how different versions of the thread, each having evolved differently, may be combined.
• Thread 600 there are two different versions of the thread, 600 and 602.
• T# ⁇ num> defines the terminal that created the contents. Both threads contain a startup message 610 and a first reply message 612. After that, the threads have evolved differently: thread 600 also contains messages 614, 616, and 618, whereas thread 602 also contains messages 620, 622, and 624.
• the two branches may be combined into one uniform thread. When a new part (a start-up message or a reply, for example) is added to a thread, a marker containing the contributor's address and the time of contribution is stored into the thread. By using this information, the thread branches are combined so that the replies of the threads are put into order according to the time of contribution. The combined thread is displayed to the user as a single entity and the mobile communication apparatus that performed the combination distributes this combined version of the thread further.
• the combined thread 604 thus contains the messages 610, 612, 620, 614, 616, 622, 618, and 624, ordered according to their time of contribution.
• the messages 610, 612, 620, 614, 616, 622, 618, and 624 ordered according to their time of contribution.
• other rules besides the time of the contribution may be used instead or additionally.
• Every new thread may be given a unique identifier, UID, which is generated at random.
• the identifier may be a 32-bit identifier, for example.
• Threads may be organized based on the identifier by creating a directory c: ⁇ data ⁇ others ⁇ threads ⁇ UID in hexadecimal> where all files belonging to the thread are stored.
• the possibility that two threads are given the same UID at random is about 0.0000000002 when using the 32-bit identifier, i.e. the possibility that two threads could have the same identifier in any given mobile communication apparatus is minimal.
• the threads are stored as a straightforward directory structure, managing them does not require any complex functionality.
• the thread contents may be created by an editor launched from the mobile terminal browser. A thread may be removed using simple file system operations. When a message is contributed into a thread, several pieces of information are stored. Naturally, the contents created by the user constitutes one piece of such information, but, in addition to this, a time stamp and the Bluetooth device address of the message creator may be written into the thread as well. Both of these additional items may be hidden from the user.
• the contents may also require formatting, and since the contents may be displayed as an XHTML-page, some HTML-tags may be added to the thread as well.
• the thread processing functionality may be based on client/server requests and replies. The following description gives an example as to how the message flow turns into an XHTML-page that is displayed to the user.
• the user selects a device from a list of devices shown on the web browser of her/his mobile terminal. This issues a "GET THREADLIST" request to the destination device.
• the destination device receives the request and generates a list of thread UIDs stored in its memory. It sends the list back to the requesting device. 3.
• the requesting device receives the reply containing the list of stored thread UIDs.
• An XHTML-page is generated from the list. After this, a "GET FILELIST" request is performed on each thread and a list of files in a thread is received. This information is used to generate links for the XHTML- page for fetching the files stored in a thread. 4.
• the XHTML-page containing the list of threads is shown to the user and (s)he selects the one to be examined. The selection issues a "GET ⁇ filename>" request to the destination device, and the destination device sends the file contents as a reply. This request can be issued multiple times, depending on the number of files stored in the thread.
• the file(s) is received and displayed to the user. These contents are not modified at all, the thread contents are already in XHTML-format upon reception.
• the thread processing may be implemented as three applications: a server listening for incoming requests (GET THREADLIST, GET FILELIST, GET ⁇ filename>), a client making the requests for the server and receiving responses from the server, and an editor creating new threads and adding messages to the threads.
• these three applications may be wrapped to a single application to avoid multiple installations.
• the method relates to thread processing.
• the method starts in 500 and ends in 516.
• an old thread is requested in a user-initiated fashion through a wireless local ad hoc data transfer connection from a first mobile communication apparatus.
• an old message belonging to the old thread is requested through a wireless local ad hoc data transfer connection from a second mobile communication apparatus.
• a new message is created.
• a new thread is dynamically and cumulatively compiled from the old thread and the new message.
• the new thread and the new message are stored.
• the new thread is transmitted through a wireless local ad hoc data transfer connection to a third mobile communication apparatus on the basis of a request received from the third mobile communication apparatus.
• the new message is transmitted through a wireless local ad hoc data transfer connection to a fourth mobile communication apparatus on the basis of a request received from the fourth mobile communication apparatus.
• Figure 4 illustrates the embodiments from the point of view of the user interface.
• the DTServer application is run in the background.
• a web browser is started and a web page is opened by using a predetermined bookmark.
• the web page 402 includes three different items: "New thread”, "Discovery” and "My threads”.
• the user may create a new thread by entering in a thread title and message contents in a window 404.
• the thread title is "Free coffee” and the message contents "Downstairs at noon!”.
• the threads stored in the user's own apparatus may be browsed by selecting the "My threads” link, whereupon a web page 408 is shown with the following threads: “Car for sale”, “Comics”, “Free coffee”, and “Stolen wallet”.
• Other apparatuses may be browsed by selecting the "Discovery” link, whereupon a web page 406 is shown.
• there are four other devices “D600”, “DDTEddie”, “DDTGame” and "OULKV1 K738”.
• a list of threads stored in the selected apparatus is shown on a web page 410: "Winter tyres", “Bridge construction”, and “Fishing spot”.
• the user may select a thread to view, whereupon that thread 412 is shown.
• “DDTEddie” started a new thread “Bridge construction” with the start-up message "There's a construction ongoing at highway E4 near Tampere. Traffic jams expected.”.
• "DDTVincent” has fetched this thread, and adds a reply "Actually it's already done” on a web page 414.
• the whole thread is shown on a web page 416.

Landscapes

• Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Human Resources & Organizations (AREA)
• Strategic Management (AREA)
• Entrepreneurship & Innovation (AREA)
• Computer Hardware Design (AREA)
• Quality & Reliability (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Economics (AREA)
• Marketing (AREA)
• Operations Research (AREA)
• Data Mining & Analysis (AREA)
• Tourism & Hospitality (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=39589301

Family Applications (1)

Country Status (2)

Cited By (2)

Citations (6)

• 2008
  • 2008-06-02 FI FI20085535A patent/FI20085535A0/fi not_active Application Discontinuation
• 2009
  • 2009-06-01 WO PCT/FI2009/050462 patent/WO2009147295A1/en active Application Filing

Patent Citations (6)

Also Published As

Similar Documents

Legal Events