WO2016046902A1 - System, method, and program for sharing handwritten information - Google Patents

Abstract

According to an embodiment, this method comprises: detecting a first operation of entering handwritten input on the screen of an electronic device using a first pen corresponding to a first terminal; and performing settings so that when the first operation is detected, first stroke data input by hand on the electronic device can be transmitted to the first terminal and second stroke data input by hand on the first terminal can be received from the first terminal.

Description

System, method and program for sharing handwritten information

The embodiment of the present invention relates to a technique for sharing handwritten information.

In recent years, various electronic devices such as tablets, PDAs, and smartphones have been developed. Many electronic devices of this type are equipped with a touch screen display to facilitate an input operation by a user.

Recently, a system for sharing handwritten information such as characters or figures written by hand among a plurality of terminals has also been developed.

JP-A-6-161537

Incidentally, as described above, in order to share handwritten information between a plurality of terminals, it is necessary to start a session between the plurality of terminals.

However, when starting a session in this way, various settings (procedures) must be made between the terminals. This procedure is complicated for the user who uses the terminal.

An object of one embodiment of the present invention is to provide a system, method, and program capable of easily sharing handwritten information.

According to the embodiment, the method detects, on the screen of the electronic device, a first operation input by handwriting using a first pen corresponding to the first terminal, and the first operation is detected. The first stroke data input by handwriting in the electronic device can be transmitted to the first terminal, and the second stroke data input by handwriting in the first terminal can be received from the first terminal. Setting to be performed.

FIG. 1 is an exemplary perspective view illustrating an external appearance of an electronic apparatus according to an embodiment. FIG. 2 is an exemplary diagram illustrating a connection between terminals logged into the handwriting sharing service. FIG. 3 is a diagram illustrating an example of a data flow between the host terminal and the guest terminal in the handwriting sharing service. FIG. 4 is a diagram illustrating an example of a handwriting sharing screen. FIG. 5 is a diagram illustrating an example of a handwritten document handwritten on the touch screen display of the tablet terminal illustrated in FIG. 1. FIG. 6 is a diagram illustrating an example of time-series information corresponding to the handwritten document illustrated in FIG. FIG. 7 is a diagram illustrating an example of a system configuration of the tablet terminal. FIG. 8 is a diagram mainly illustrating an example of a functional configuration of the tablet terminal. FIG. 9 is a diagram illustrating an example of the data structure of the stroke database. FIG. 10 is a diagram illustrating an example of the data structure of the stroke database when managed in units of point data. FIG. 11 is a diagram for explaining an outline of operations of a plurality of terminals and the authentication server device. FIG. 12 is a sequence chart showing processing procedures of the plurality of terminals and the authentication server device during the operation shown in FIG. FIG. 13 is a diagram for explaining an outline of operations of a plurality of terminals and an authentication server device different from those in FIG. 11. FIG. 14 is a sequence chart showing processing procedures of the plurality of terminals and the authentication server device during the operation shown in FIG. FIG. 15 is a diagram for explaining an outline of operations of the host terminal and the guest terminal when using the handwriting sharing service. FIG. 16 is a diagram for explaining an outline of operations of the host terminal and the guest terminal when the handwriting sharing service is used.

Hereinafter, embodiments will be described with reference to the drawings.
FIG. 1 is a perspective view illustrating an external appearance of an electronic apparatus according to an embodiment. This electronic device is, for example, a pen-based portable electronic device that can be input by handwriting with a pen (stylus) or a finger. This electronic device can be realized as a tablet terminal, a notebook personal computer, a smartphone, a PDA, or the like. FIG. 1 shows an example in which this electronic device is realized as a tablet terminal. In the following description, the electronic device according to the present embodiment is described as being realized as a tablet terminal. A tablet terminal is a portable electronic device also called a tablet or a slate computer.

The tablet terminal 10 shown in FIG. 1 includes a main body 11 and a touch screen display 12. The main body 11 has a thin box-shaped housing, and the touch screen display 12 is attached so as to overlap the upper surface of the main body 11.

The touch screen display 12 incorporates a flat panel display and a sensor. The sensor is configured to detect a contact position of a pen or a finger on the screen of the flat panel display. The flat panel display may be a liquid crystal display (LCD), for example. As the sensor, for example, a capacitive touch panel, an electromagnetic induction digitizer, or the like can be used. In the following, it is assumed that both the touch panel display 12 and the digitizer sensor are incorporated in the touch screen display 12.

The touch screen display 12 can detect not only a touch operation on the screen using a finger but also a touch operation on the screen using the pen 100. The pen 100 may be, for example, an electromagnetic induction pen (digitizer pen). The user can perform a handwriting input operation on the touch screen display 12 using the pen 100. During the handwriting input operation, the trajectory of the movement of the pen 100 on the screen, that is, the stroke trajectory (handwriting) handwritten by the handwriting input operation is drawn in real time, whereby the trajectory of each stroke is displayed on the screen. . The locus of movement of the pen 100 while the pen 100 is in contact with the screen corresponds to one stroke. A set of many strokes corresponding to handwritten characters or figures, that is, a set of many trajectories (handwriting) constitutes a handwritten document.

In this embodiment, the handwritten document is stored in the storage medium as time series information indicating the coordinate sequence of the trajectory of each stroke and the order relationship between the strokes, not image data. Although details of this time-series information will be described later, the time-series information indicates the order in which a plurality of strokes are handwritten, and includes a plurality of stroke data respectively corresponding to the plurality of strokes. In other words, the time series information means a set of time series stroke data respectively corresponding to a plurality of strokes. Each stroke data corresponds to a certain stroke, and includes a coordinate data series (time series coordinates) corresponding to each point on the locus of this stroke. The order of arrangement of the stroke data corresponds to the order in which the strokes are handwritten, that is, the stroke order.

Furthermore, the tablet terminal 10 has an editing function. This editing function deletes or deletes arbitrary strokes or arbitrary handwritten characters in the displayed handwritten document according to the editing operation by the user using the “eraser” tool, the range specification tool, and other various tools. Can move. Further, this editing function includes a function for canceling a history of some handwriting operations.

In this embodiment, the time series information can be managed as one or a plurality of pages. In this case, a group of time-series information that fits on one screen may be recorded as one page by dividing the time-series information into area units that fit on one screen. Alternatively, the page size may be variable. In this case, since the page size can be expanded to an area larger than the size of one screen, a handwritten document having an area larger than the screen size can be handled as one page. When one entire page cannot be simultaneously displayed on the display, the page may be reduced and displayed, or the display target portion in the page may be moved by vertical and horizontal scrolling.

As described above, since the time series information can be managed as page data, hereinafter, the time series information is also referred to as handwritten page data or simply handwritten data.

Moreover, the tablet terminal 10 has a network communication function, and can cooperate with other tablet terminals and server devices.

The server device capable of cooperating with the tablet terminal 10 includes a large-capacity storage medium such as a hard disk drive (HDD). The tablet terminal 10 can transmit the time-series information (handwritten page data) to the server apparatus via the network and store the time-series information in a storage medium of the server apparatus (upload). In order to ensure secure communication between the tablet terminal 10 and the server device, the server device may authenticate the tablet terminal 10 at the start of communication. In this case, a dialog for prompting the user to input an ID or password may be displayed on the screen of the tablet terminal 10, or the ID of the tablet terminal 10 may be automatically transmitted from the tablet terminal 10 to the server device. Also good.

Furthermore, the tablet terminal 10 reads (downloads) any one or more time-series information (handwritten page data) stored in the storage medium of the server device, and each of the strokes indicated by the read time-series information. The locus can be displayed on the screen of the touch screen display 12 of the tablet terminal 10. In this case, a list of thumbnails (thumbnail images) obtained by reducing each page of a plurality of time-series information (handwritten page data) may be displayed on the screen of the touch screen display 12 or selected from these thumbnails. One page may be displayed in a normal size on the screen of the touch screen display 12.

Thereby, even when the storage capacity in the tablet terminal 10 is small, the tablet terminal 10 can handle a large number or a large amount of time-series information (handwritten page data).

Thus, in the present embodiment, the time series information can be stored in either the storage medium (storage) in the tablet terminal 10 or the storage medium (storage) in the server device. In other words, the user using the tablet terminal 10 can store arbitrary time-series information in an arbitrary storage medium selected from the storage medium in the tablet terminal 10 and the storage medium in the server device.

Furthermore, the tablet terminal 10 can also hand-write objects such as characters and figures on web pages, texts, images, and other various contents. In this case, the handwritten stroke can be drawn on the transparent layer set on the displayed content. Thereby, this handwritten stroke can be displayed over the above-mentioned content.

Furthermore, the tablet terminal 10 has a handwriting collaboration function. The handwriting collaboration function executes a handwriting sharing service capable of sharing handwritten information (characters and graphics written in handwriting) between a plurality of terminals including the tablet terminal 10 described above. This handwriting sharing service allows users who use each terminal to browse handwritten information shared and edits handwritten information through collaborative work with users who use other terminals.

In this handwriting sharing service, stroke data input by handwriting in any of a plurality of terminals participating (logged in) in the handwriting sharing service is transmitted to each other terminal in real time. As a result, the contents of the display screens of the plurality of terminals can be synchronized. In this case, strokes input by handwriting by different users may be displayed in different forms (for example, different colors, different pen types, etc.).

The handwriting sharing service is used by a group of multiple people. A group of a plurality of persons using the handwriting sharing service uses, for example, a user (organizer) who uses the tablet terminal 10 serving as a host terminal and a tablet terminal 10 which is a terminal other than the host terminal (hereinafter referred to as a guest terminal). User (participant).

FIG. 2 shows an example of connection between terminals logged in to the handwriting sharing service described above.
A terminal 10A illustrated in FIG. 2 is a tablet terminal 10 used by a user A, for example. The terminal 10B is the tablet terminal 10 used by the user B, for example. The terminal 10C is a tablet terminal 10 used by the user C. That is, each of the terminals 10A to 10C has a handwriting collaboration function equivalent to that of the tablet terminal 10 according to the present embodiment.

When using the handwriting sharing service, the terminals 10A to 10C are wirelessly connected to each other. As this wireless connection, any wireless connection standard capable of wirelessly connecting a plurality of terminals to each other is used. Specifically, for example, Bluetooth (registered trademark) or Wi-Fi Direct (registered trademark) may be used.

Any one of the terminals 10A to 10C can function as a host terminal (handwriting collaboration server system) configured to manage the handwriting sharing service. Specifically, for example, the tablet terminal 10 used by the user who becomes the organizer operates as the host terminal.

Suppose that this host terminal (user who uses it) has the authority of whether or not to allow other terminals (users who use it) to participate in the handwriting sharing service. In the present embodiment, processing when a terminal other than the host terminal logs in (participates) in the handwriting sharing service and the terminal starts a session with the host terminal (establishes connection) will be described later.

Here, it is assumed that the terminals 10A to 10C are logged in (participated) in the handwriting sharing service, that is, a session is started between the terminals 10A to 10C. Thus, when logged in to the same handwriting sharing service, the contents of the display screens of the terminals 10A to 10C are synchronized.

That is, the stroke data handwritten input by each of the users A to C at his / her terminals 10A to 10C is not only displayed on the screen of his / her terminal but also reflected in real time on the screens of other users' terminals ( Is displayed. Specifically, for example, stroke data input by handwriting on the terminal 10A by the user A using his / her pen 100A is also displayed on the screens of the terminals 10B and 10C. Similarly, for example, stroke data handwritten by the user B using his / her pen 100B at the terminal 10B is also displayed on the screens of the terminals 10A and 10C. Further, for example, stroke data input by the user C using the pen 100C of his / her handwriting on the terminal 10C is also displayed on the screens of the terminals 10A and 10B. Thereby, handwritten information (handwritten characters, handwritten figures, etc.) can be exchanged and shared between the users A to C who are logged in to the handwriting sharing service.

Furthermore, the terminals 10A to 10C logged in to the handwriting sharing service can display the same content such as conference materials on the screen. In this case, stroke data input by handwriting in each of the terminals 10A to 10C is displayed on this content. Thus, the users A to C can exchange and share handwritten information (handwritten characters, handwritten figures, etc.) handwritten on the content while browsing the same content among the users A to C.

In the present embodiment, for example, each of the terminals 100A to 10C logged in to the handwriting sharing service has an identification for identifying the pen in each of the pens 100A to 100C used for handwriting input of stroke data. Information (hereinafter referred to as pen ID) is held. According to this, for example, when stroke data is input by handwriting in any of the terminals 10A to 10C using the pen 100A, a pen ID for identifying the pen 100A is transmitted to the terminal. Here, the pen 100A has been described, but the same applies to the case where the pens 100B and 100C are used. In the present embodiment, it is assumed that users A to C who use the handwriting sharing service use their own pens 100A to 100C, respectively.

FIG. 3 shows a data flow between the host terminal and the guest terminal in the handwriting sharing service. In FIG. 3, it is assumed that the terminal 10A operates as a host terminal, and the terminals 10B and 10C operate as guest terminals. That is, the user A who uses the terminal 10A is the organizer of the handwriting sharing service, and the users B and C who use the terminals 10B and 10C are participants of the handwriting sharing service.

In this case, the terminal 10A (host terminal) receives stroke data (handwritten data) input by handwriting in the terminal 10B (guest terminal) from the terminal 10B. In addition, the terminal 10A receives stroke data input by handwriting on the terminal 10C (guest terminal) from the terminal 10C.

Furthermore, the terminal 10A transmits the stroke data input by handwriting in the terminal 10A and the stroke data received from the terminal 10C to the terminal 10B. Furthermore, the terminal 10A transmits stroke data input by handwriting on the terminal 10A and stroke data received from the terminal 10B to the terminal 10C.

Therefore, on the touch screen display 12 of the terminal 10A, not only the stroke data input by handwriting by the user A is displayed, but also stroke data input by handwriting by the user B, and further stroke data input by handwriting by the user C. Is also displayed.

Similarly, not only the stroke data input by handwriting by the user B is displayed on the touch screen display 12 of the terminal 10B, but also stroke data input by handwriting by the user A, and further strokes input by handwriting by the user C. Data is also displayed.

Similarly, not only the stroke data input by handwriting by the user C but also the stroke data input by handwriting by the user A and the stroke input by handwriting by the user B are displayed on the touch screen display 12 of the terminal 10C. Data is also displayed.

For example, the terminal 10A operating as a host terminal stores stroke data (handwritten data) input by handwriting in each terminal (here, the terminals 10A to 10C) logged in to the handwriting sharing service in a stroke database described later. . This stroke database is used to manage handwritten data created and edited by collaborative work.

FIG. 4 shows an example of the handwriting sharing screen of the terminal 10A (that is, the screen of the terminal 10A when logged in to the handwriting sharing service). In the display area of the handwriting sharing screen 21 of the terminal 10A, a transparent layer (handwriting layer) 22 capable of handwriting input is set. The stroke data of each user is displayed on the handwriting layer 22.

In the example illustrated in FIG. 4, stroke data (handwritten stroke of user A) 31 input by the user A using the pen 100 </ b> A on the handwriting sharing screen 21 of the terminal 10 </ b> A is displayed on the handwriting sharing screen 21 of the terminal 10 </ b> A. Is done. Furthermore, stroke data received from another terminal is displayed on the handwriting sharing screen 21 of the terminal 10A. The stroke data received from other terminals include, for example, stroke data input by handwriting by user B (handwriting stroke of user B) 32, stroke data input by handwriting by user C (handwriting stroke of user C) 33, Is included.

Next, the relationship between stroke data (handwritten characters, handwritten marks, handwritten figures, handwritten tables, etc.) input by handwriting and time-series information will be described with reference to FIGS.

FIG. 5 shows an example of a handwritten document (handwritten character string) handwritten on the touch screen display 12 using the pen 100 or the like.

In FIG. 5, the handwritten character string “ABC” is handwritten in the order of “A”, “B”, and “C”, and then a handwritten arrow is handwritten near the handwritten character “A”. Is assumed.

The handwritten character “A” is expressed by two strokes (“∧” shape trajectory, “−” shape trajectory) handwritten using the pen 100 or the like. The trajectory of the first “∧” -shaped pen 100 handwritten is sampled in real time, for example, at equal time intervals, thereby obtaining the time-series coordinates SD11, SD12,. Similarly, the trajectory of the “−” shaped pen 100 described next is also sampled in real time at equal time intervals, thereby obtaining the time series coordinates SD21, SD22,..., SD2n of the “−” shaped stroke.

The handwritten character “B” is expressed by two strokes handwritten using the pen 100 or the like. The handwritten character “C” is expressed by one stroke handwritten using the pen 100 or the like. The handwritten “arrow” is expressed by two strokes handwritten using the pen 100 or the like.

FIG. 6 shows time-series information corresponding to the handwritten document shown in FIG. The time series information 200 shown in FIG. 6 includes a plurality of stroke data SD1, SD2,. In the time series information 200, these stroke data SD1, SD2,..., SD7 are arranged in time series in the order of handwriting, that is, the order in which a plurality of strokes are handwritten.

In the time series information 200, the first two stroke data SD1 and SD2 indicate two strokes of the handwritten character “A”, respectively. The third and fourth stroke data SD3 and SD4 indicate two strokes constituting the handwritten character “B”, respectively. The fifth stroke data SD5 indicates one stroke constituting the handwritten character “C”. The sixth and seventh stroke data SD6 and SD7 indicate two strokes constituting the handwritten “arrow”, respectively.

Each stroke data includes a coordinate data series (time series coordinates) corresponding to one stroke, that is, a plurality of coordinates corresponding to each of a plurality of points on the trajectory of one stroke. In each stroke data, a plurality of coordinates are arranged in time series in the order in which the strokes are written. For example, for the handwritten character “A”, the stroke data SD1 includes coordinate data series (time series coordinates) corresponding to each point on the locus of the stroke of the “∧” shape of the handwritten character “A”, that is, n pieces of data. Coordinate data SD11, SD12,..., SD1n are included. The stroke data SD2 includes a coordinate data series corresponding to each point on the trajectory of the stroke of the “−” shape of the handwritten character “A”, that is, n coordinate data SD21, SD22,. Note that the number of coordinate data may be different for each stroke data.

Each coordinate data (point data) indicates an X coordinate and a Y coordinate corresponding to a certain point in the corresponding locus. For example, the coordinate data SD11 indicates the X coordinate (X11) and the Y coordinate (Y11) of the start point of the “∧” -shaped stroke. SD1n indicates the X coordinate (X1n) and Y coordinate (Y1n) of the end point of the “∧” -shaped stroke. Further, for example, information (Z) indicating writing pressure may be added to each coordinate data.

FIG. 7 shows a system configuration of the tablet terminal 10 (terminals 10A to 10C). As shown in FIG. 7, the tablet terminal 10 includes a CPU 101, a nonvolatile memory 102, a main memory 103, a BIOS-ROM 104, a system controller 105, a GPU (graphics processing unit) 106, a wireless communication device 107, an EC 108, and the like. In the tablet terminal 10, the touch screen display 12 shown in FIG. 1 includes an LCD 12A, a touch panel 12B, and a digitizer 12C.

The CPU 101 is a processor that controls the operation of various modules in the tablet terminal 10. The CPU 101 executes various programs (software) loaded into the main memory 103 from the nonvolatile memory 102 that is a storage device. These programs include an operating system (OS) 103a and various application programs. The application program includes a handwriting sharing application program 103b. This handwriting sharing application program 103b is configured to realize the above-described handwriting collaboration function for sharing handwritten information among a plurality of terminals.

The CPU 101 also executes a basic input / output system (BIOS) stored in the BIOS-ROM 104. The BIOS is a program for hardware control.

The system controller 105 is a device that connects between the local bus of the CPU 101 and various components. The system controller 105 also includes a memory controller that controls access to the main memory 103. The system controller 105 also has a function of executing communication with the GPU 106 via a PCI EXPRESS serial bus or the like.

The GPU 106 is a display processor that controls the LCD 12A used as a display monitor of the tablet terminal 10. A display signal generated by the GPU 106 is sent to the LCD 12A. The LCD 12A displays a screen image based on the display signal. A touch panel 12B is disposed on the upper surface side of the LCD 12A. A digitizer 12C is disposed on the lower surface side of the LCD 12A. The touch panel 12B is a capacitance-type pointing device for inputting on the screen of the LCD 12A. The touch position on the screen where the finger is touched and the movement of the touch position are detected by the touch panel 12B. The digitizer 12C is an electromagnetic induction type pointing device for inputting on the screen of the LCD 12A. The contact position on the screen with which the pen 100 is touched, the movement of the contact position, and the like are detected by the digitizer 12C.

The wireless communication device 107 is a device configured to execute wireless communication such as the above-described Bluetooth or Wi-Fi Direct.

EC108 is a one-chip microcomputer including an embedded controller for power management. The EC 108 has a function of powering on or off the tablet terminal 10 in accordance with a power button operation by the user.

Next, mainly the functional configuration of the tablet terminal 10 (terminals 10A to 10C) will be described with reference to FIG.

The tablet terminal 10 includes a handwriting input unit 301, a display processing unit 302, a stroke data generation unit 303, a stroke database 304, a communication processing unit 305, a processing unit 306, and the like. In the present embodiment, the handwriting input unit 301, the display processing unit 302, the stroke data generation unit 303, the communication processing unit 305, and the processing unit 306 illustrated in FIG. 8 are realized by the CPU 101 executing the handwriting sharing application program 103b. A function execution module for sharing handwritten data. The stroke database 304 is stored in the nonvolatile memory 102 that is a storage device.

Here, the handwriting sharing application program 103b creates, displays, and edits handwritten page data by using stroke data input using the touch screen display 12. The digitizer 12 </ b> C provided in the touch screen display 12 is configured to detect occurrence of events such as “touch”, “move (slide)”, and “release”. “Touch” is an event indicating that the pen 100 has touched the screen of the tablet terminal 10. “Move (slide)” is an event indicating that the contact position has been moved while the pen 100 is in contact with the screen of the tablet terminal 10. “Release” is an event indicating that the pen 100 has been released from the screen of the tablet terminal 10. According to such a digitizer 12 </ b> C, an operation (handwriting input operation) input by handwriting on the screen of the tablet terminal 10 using the pen 100 can be detected.

The handwriting input unit 301 is an interface configured to perform handwriting input in cooperation with the digitizer 12C. The handwriting input unit 301 inputs (receives) a “touch” or “move (slide)” event from the digitizer 12 </ b> C, and thereby detects a handwriting input operation. The “touch” event includes the coordinates of the contact position. The “move (slide)” event also includes the coordinates of the contact position of the movement destination. Therefore, the handwriting input unit 301 can input a coordinate sequence (stroke data) corresponding to the movement locus of the contact position from the touch screen display 12.

The display processing unit 302 acquires a coordinate string from the handwriting input unit 301, and displays each stroke data input by handwriting by a handwriting input operation using the pen 100 on the screen of the LCD 12A based on the coordinate string. Furthermore, the display processing unit 302 displays the stroke data received from another terminal on the screen of the LCD 12A under the control of the processing unit 306.

The stroke data generation unit 303 acquires the above-described coordinate sequence from the handwriting input unit 301, and generates time series information (stroke data) having a structure as described in detail in FIG. 6 based on the coordinate sequence. The stroke data generated in this way is stored in the stroke database 304, for example.

The communication processing unit 305 executes processing for transmitting each stroke data in the stroke database 304 to another terminal using the wireless communication device 107 under the control of the processing unit 306. Also, the communication processing unit 305 executes processing for receiving stroke data from another terminal using the wireless communication device 107 under the control of the processing unit 306.

The processing unit 306 executes processing for sharing handwritten information (stroke data) among a plurality of terminals. The processing unit 306 includes a pen ID acquisition unit 306a, a connection management unit 306b, a stroke management unit 306c, and the like.

The pen ID acquisition unit 306a acquires a pen ID from the pen 100 used for handwritten input of stroke data. In this way, according to the pen ID acquired by the pen ID acquisition unit 306a, it is possible to identify the pen used when a handwriting input operation (or touch operation or the like) is performed on the tablet terminal 10.

The connection management unit 306b manages a user (a terminal used by the handwriting sharing service) and executes a process for starting a session between the tablet terminal 10 and another terminal.

Specifically, the connection management unit 306b, for example, when another user using a terminal other than the tablet terminal 10 performs a handwriting input operation or the like on the screen of the tablet terminal 10 using his / her pen 100 Then, a session between the tablet terminal 10 and the other terminal is started. Details of the processing of the connection management unit 306b will be described later.

The stroke management unit 306c manages stroke data received from each terminal logged into the handwriting sharing service using the stroke database 304. Note that the processing by the stroke management unit 306c may be executed only in the terminal operating as the host terminal described above.

FIG. 9 shows an example of the data structure of the stroke database 304. The stroke database 304 includes a large number of records (a large number of storage areas) each assigned a record ID. One stroke data (one stroke) is assigned to one record. In each record, a terminal ID (device ID), stroke data (coordinate sequence), and the like are stored. Further, a user ID corresponding to the stroke data (that is, an identifier for identifying a user who has input the stroke data by handwriting), a pen ID, and the like may be stored in each record.

In the example shown in FIG. 9, the record ID “1”, the record ID “2”, and the record ID “102” are recorded in the tablet terminal 10 (that is, the terminal 10A) identified by the terminal ID “A”. The stroke data input by handwriting is stored. The record with the record ID “3” stores stroke data input by handwriting on the tablet terminal 10 (that is, the terminal 10B) identified by the terminal ID “B”. Furthermore, in the records with the record ID “4”, the record ID “100”, and the record ID “101”, the stroke data input by handwriting on the tablet terminal 10 (that is, the terminal 10C) identified by the terminal ID “C” is stored. Stored.

In the example shown in FIG. 9, one stroke data is assigned to one record (that is, managed in units of stroke data). However, the stroke data is a plurality of point data (coordinate data) described above. For example, as shown in FIG. 10, one point data may be assigned to one record (that is, managed in units of point data corresponding to stroke data). When data is managed in units of point data in this way, stroke data can be transmitted / received in units of point data when using the handwriting sharing service described above. In the case of such a configuration, it is possible to reproduce in more detail how the stroke is described.

Hereinafter, operations of a plurality of terminals including the tablet terminal 10 according to the present embodiment and the above-described authentication server device will be described.

In the following description, it is assumed that the plurality of terminals include terminals 10A to 10C used by users A to C, respectively. The users A to C use their own pens 100A to 100C, respectively.

Here, it is assumed that the terminal 10A (user A who uses the terminal) is logged in to the handwriting sharing service, and the terminal 10A operates as the host terminal described above. The terminal 10A can operate as the host terminal by setting a mode in which the terminal 10A operates as a host terminal. The host terminal is preferably a terminal having handwritten data (handwritten page data) desired to be shared, a terminal desired to be used for sharing work, or the like. On the other hand, it is assumed that the terminal 10B and the terminal 10C are not logged in to the handwriting sharing service.

Further, it is assumed that the terminal 10A is connected to the authentication server device so as to be communicable. The authentication server device includes a pen ID for identifying the pen 100 (here, the pens 100A to 100C) used by each user who uses the handwriting sharing service and a terminal (here, the terminal) used by the user. 10A to 10C) are stored in association with each other. The authentication information may be registered in advance in the authentication server device when each of the users A to C starts using the terminals 10A to 10C and the pens 100A to 100C, for example.

First, with reference to FIG. 11, an outline of operations of the plurality of terminals 10A to 10C and the authentication server device when the users B and C try to use the handwriting sharing service in such a case will be described.

In the present embodiment, when the users B and C who use (own) the terminals 10B and 10C are going to use the handwriting sharing service, the users B and C have the user B on the screen of the terminal 10A that is the host terminal. And C are brought into contact with unique pens 100B and 100C, respectively, and a handwriting input operation using the pens 100B and 100C is performed (A1).

In this case, the terminal 10A acquires a pen ID for identifying each of the pens 100B and 100C from the pens 100B and 100C, and makes an inquiry to the authentication server device (directory server device) 400 using the pen ID as a key. (A2). By referring to the authentication information in the authentication server device 400, the terminals 10B and 10C corresponding to the pens 100B and 100C are specified as terminals to be connected to the terminal 10A.

Finally, the terminal 10A starts a session with the terminals 10B and 10C identified as described above by transmission from the terminal 10A side which is the host terminal (A3). Thereby, sharing of handwritten information (handwritten notes) in the terminals 10A to 10C is started.

Next, with reference to the sequence chart of FIG. 12, the processing procedure of the plurality of terminals 10A to 10C and the authentication server device 400 during the operation described in FIG. 11 will be described in detail.

First, the case where user B intends to use the handwriting sharing service will be described. In this case, the user B performs a handwriting input operation such as a touch operation on the screen of the terminal 10A using the pen 100B unique to the user B.

When such an operation is performed, the digitizer 12C of the touch screen display 12 provided in the terminal 10A causes an event such as “touch” and “movement (slide)” (that is, contact with the pen 100B on the screen of the terminal 10A). ) Is detected. In this case, the handwriting input unit 301 inputs a “touch” or “move (slide)” event from the digitizer 12C, and detects a handwriting input operation by the user B (block B1).

On the other hand, when a handwriting input operation using the pen 100B by the user B is detected on the screen of the terminal 10A, the pen ID acquisition unit 306a of the processing unit 306 included in the terminal 10A is a pen for identifying the pen 100B. An ID is acquired (received) from the pen 100B (block B2).

Here, the pen ID acquired by the pen ID acquisition unit 306a is not a pen ID for identifying the pen 100A used by the user A who uses the terminal 10A. In this case, the connection management unit 306b transmits an authentication request including the pen ID acquired by the pen ID acquisition unit 306a to the authentication server device 400 (block B3). When the pen ID acquired by the pen ID acquisition unit 306a is a pen ID for identifying the pen 100A (that is, for example, the user A performs a handwriting input operation using the pen 100A), the block B3 And the processing of blocks B4 to B6, which will be described later, is not executed, and processing for displaying the stroke data input by handwriting by the user A on the screen of the LCD 12A is executed.

Next, the authentication server device 400 receives the authentication request transmitted by the terminal 10A (the connection management unit 306b). The authentication server device 400 acquires the terminal ID included in the authentication information described above in association with the pen ID included in the received authentication request (block B4). Here, the terminal ID acquired by the authentication server device 400 is used by a user (here, user B) using the pen 100 (here, pen 100B) identified by the pen ID included in the received authentication information. This is an identifier for identifying the tablet terminal 10 (here, the terminal 10B).

If the authentication information including the pen ID included in the authentication request transmitted by the terminal 10A is not stored (registered) in the authentication server device 400, the terminal corresponding to the pen 100 identified by the pen ID is selected. It cannot be specified. In this case, the authentication server device 400 returns a response that the user using the pen 100 identified by the pen ID included in the authentication request cannot use the handwriting sharing service to the terminal 10A, for example, and a block B6 described later This processing is not executed.

The authentication server device 400 transmits the acquired terminal ID to the terminal 10A as a response to the authentication request transmitted from the terminal 10A in the block B3 described above (block B5).

The connection management unit 306b of the terminal 10A receives the terminal ID transmitted by the authentication server device 400. When the terminal ID is received in this way, the connection management unit 306b executes a process of starting a session between the terminal 10A and the terminal 10B identified by the received terminal ID. (Block B6).

In this case, the terminal 10A, for example, the terminal 10B logs in to the handwriting sharing service, and transmits information (hereinafter referred to as connection information) necessary for starting a session between the terminal 10A and the terminal 10B to the terminal 10B. According to this, the terminal 10B can log in to the handwriting sharing service using the connection information transmitted by the terminal 10A, and a session between the terminal 10A and the terminal 10B is started. In this case, the terminal 10A can transmit stroke data input by handwriting on the terminal 10A to the terminal 10B, and can perform setting so that stroke data input by handwriting on the terminal 10B can be received from the terminal 10B. Do. Similarly, the terminal 10B can transmit stroke data input by handwriting in the terminal 10B to the terminal 10A, and can perform setting so that stroke data input by handwriting in the terminal 10A can be received from the terminal 10A. Do. When the processing of block B6 is executed in this way, the terminal 10B operates as the guest terminal described above, and the user B can use the handwriting sharing service using the terminal 10B.

Next, a case where user C intends to use the handwriting sharing service will be described. In this case, the user C performs a handwriting input operation such as a touch operation on the screen of the terminal 10A using the pen 100C unique to the user C.

When such an operation is performed, the digitizer 12C of the touch screen display 12 provided in the terminal 10A causes an event such as “touch” and “move (slide)” (that is, contact with the pen 100C on the screen of the terminal 10A). ) Is detected. In this case, the handwriting input unit 301 inputs a “touch” or “move (slide)” event from the digitizer 12C, and detects a handwriting input operation by the user B (block B7).

On the other hand, when a handwriting input operation using the pen 100C by the user C is detected on the screen of the terminal 10A, the pen ID acquisition unit 306a of the processing unit 306 included in the terminal 10A is a pen for identifying the pen 100C. The ID is acquired (received) from the pen 100C (block B8).

Here, the pen ID acquired by the pen ID acquisition unit 306a is not a pen ID for identifying the pen 100A used by the user A who uses the terminal 10B. In this case, the connection management unit 306b transmits an authentication request including the pen ID acquired by the pen ID acquisition unit 306a to the authentication server device 400 (block B9).

Next, the authentication server device 400 receives the authentication request transmitted by the terminal 10A (the connection management unit 306b). The authentication server device 400 acquires the terminal ID included in the authentication information described above in association with the pen ID included in the received authentication request (block B10). Here, the terminal ID acquired by the authentication server device 400 is used by a user (here, user C) who uses the pen 100 (here, the pen 100C) identified by the pen ID included in the received authentication information. This is an identifier for identifying the tablet terminal 10 (here, the terminal 10C).

The authentication server device 400 transmits the acquired terminal ID to the terminal 10A as a response to the authentication request transmitted from the terminal 10A in the above block B9 (block B11).

The connection management unit 306b of the terminal 10A receives the terminal ID transmitted by the authentication server device 400. When the terminal ID is received in this way, the connection management unit 306b executes a process of starting a session between the terminal 10A and the terminal 10C identified by the received terminal ID (block B12).

In this case, the terminal 10A, for example, the terminal 10C logs in to the handwriting sharing service, and transmits connection information necessary for starting a session between the terminal 10A and the terminal 10C to the terminal 10C. According to this, the terminal 10C can log in to the handwriting sharing service using the connection information transmitted by the terminal 10A, and a session between the terminal 10A and the terminal 10C is started. In this case, the terminal 10A can transmit stroke data input by handwriting at the terminal 10A to the terminal 10C, and can perform setting so that stroke data input by handwriting at the terminal 10C can be received from the terminal 10C. Do. Similarly, the terminal 10C can transmit stroke data input by handwriting at the terminal 10C to the terminal 10A, and can perform setting so that stroke data input by handwriting at the terminal 10A can be received from the terminal 10A. Do. When the processing of block B12 is executed in this way, the terminal 10C operates as the guest terminal described above, and the user C can use the handwriting sharing service using the terminal 10C.

Here, as described above, when the session between the terminal 10A and the terminal 10B has already been started, the connection information transmitted from the terminal 10A to the terminal 10C includes the connection information between the terminal 10A and the terminal 10B. Information indicating that the session has already started (that is, the terminal 10B is logged in to the handwriting sharing service as a guest terminal). In this case, not only the connection between the terminal 10A and the terminal 10C but also a session between the terminal 10B and the terminal 10C may be started.

In addition, although the case where the users B and C intend to use the handwriting sharing service has been described here, the same processing is executed when a user other than the users B and C tries to use the handwriting sharing service. Is done.

In other words, in the present embodiment, by executing the processing shown in FIG. 12, the tablet terminal 10 (here, the terminal 10A) that operates as the host terminal and the other tablet terminal 10 that operates as the guest terminal (here) Then, a session between the terminals 10B and 10C) is started, and the handwriting sharing service is used by the user (group) using the host terminal and at least one or more guest terminals.

11 and 12, the authentication server device 400 that has received the authentication request (inquiry query) from the terminal 10A responds to the authentication request (a terminal for identifying the terminals 10B and 10C to be connected to the terminal 10A). ID) is transmitted to the terminal 10A, and the session is started from the terminal 10A side. However, the authentication server device 400 is a terminal for the terminals 10B and 10C specified from the pen ID included in the authentication request. It may be configured to issue a command to start a session with 10A (that is, a host terminal) and start a session from the terminals 10B and 10C (that is, guest terminals).

Moreover, although demonstrated here that a session is started between the said terminal 10A and the terminal 10C when the handwriting input operation using the pen 100C is performed on the screen of the host terminal (terminal 10A), for example. For example, when a session has already been started between the terminal 10A operating as a host terminal and the terminal 10B, the handwriting input operation using the pen 100C may be performed on the screen of the terminal 10B. That is, even when a handwriting input operation using the pen 100C is performed on the screen of the terminal 10B that is already operating as a guest terminal, by transmitting an authentication request from the terminal 10B to the authentication server device 400 It is also possible to start a session between the terminal 10A (or the terminal 10B) and the terminal 10C.

Further, unlike FIG. 11 and FIG. 12 described above, for example, the user A (that is, the owner of the host terminal) using the terminal 10A operating as the host terminal should connect to the terminal 10A using his / her pen 100A. When a handwriting input operation is performed on the screens of the terminals 10B and 10C, a configuration may be adopted in which a session is started between the terminal 10A and the terminals 10B and 10C.

Here, with reference to FIG. 13, an outline of operations of the plurality of terminals 10A to 10C and the authentication server device 400 in this case will be described.

In this embodiment, when the user A who uses (owns) the terminal 10A operating as the host terminal wants the users B and C to use the handwriting sharing service, the user A uses the terminals 10B and C used by the users B and C. A pen 100A unique to the user A is brought into contact with the screen of 10C, and a handwriting input operation using the pen 100A is performed (A11).

In this case, the terminals 10B and 10C obtain a pen ID for identifying the pen 100A from the pen 100A, and make an inquiry to the authentication server device 400 using the pen ID as a key (A12). By referring to the authentication information in the authentication server device 400, the terminal 10A corresponding to the pen 100A is specified as a terminal (host terminal) to be connected to the terminals 10B and 10C.

Finally, the terminals 10B and 10C start a session with the terminal 10A specified as described above by transmission from the terminals 10B and 10C (A13). Thereby, sharing of handwritten information (handwritten notes) in the terminals 10A to 10C is started.

Next, with reference to the sequence chart of FIG. 14, the processing procedure of the plurality of terminals 10A to 10C and the authentication server device 400 during the operation described in FIG. 13 will be described.

First, a case where the user A wants the user B to use the handwriting sharing service will be described. In this case, the user A performs a handwriting input operation such as a touch operation on the screen of the terminal 10B using the pen 100A unique to the user A.

When such an operation is performed, the digitizer 12C of the touch screen display 12 provided in the terminal 10B causes an event such as “touch” and “move (slide)” (ie, contact with the pen 100A on the screen of the terminal 10B). ) Is detected. In this case, the handwriting input unit 301 inputs a “touch” or “move (slide)” event from the digitizer 12C, and detects a handwriting input operation by the user A (block B21).

On the other hand, when a handwriting input operation using the pen 100A by the user A is detected on the screen of the terminal 10B, the pen ID acquisition unit 306a of the processing unit 306 included in the terminal 10B is a pen for identifying the pen 100A. The ID is acquired (received) from the pen 100A (block B22).

Here, the pen ID acquired by the pen ID acquisition unit 306a is not a pen ID for identifying the pen 100B used by the user B who uses the terminal 10B. In this case, the connection management unit 306b transmits an authentication request including the pen ID acquired by the pen ID acquisition unit 306a to the authentication server device 400 (block B23).

Next, the authentication server device 400 receives the authentication request transmitted by the terminal 10B (the connection management unit 306b). The authentication server device 400 acquires the terminal ID included in the authentication information described above in association with the pen ID included in the received authentication request (block B24). Here, the terminal ID acquired by the authentication server device 400 is used by a user (here, user A) who uses the pen 100 (here, the pen 100A) identified by the pen ID included in the received authentication request. This is an identifier for identifying the tablet terminal 10 (here, the terminal 10A).

The authentication server device 400 transmits the acquired terminal ID to the terminal 10B as a response to the authentication request transmitted from the terminal 10B in the block B23 described above (block B25).

The connection management unit 306b of the terminal 10B receives the terminal ID transmitted by the authentication server device 400. When the terminal ID is received in this way, the connection management unit 306b executes a process of starting a session between the terminal 10A and the terminal 10B identified by the received terminal ID (block B26).

In this case, for example, the terminal 10B logs in to the handwriting sharing service and requests the terminal 10A for connection information necessary for starting a session between the terminal 10A operating as the host terminal and the terminal 10B. To do. When connection information is returned from the terminal 10A to the terminal 10B as a response to this request, the terminal 10B can log in to the handwriting sharing service using the connection information, and a session between the terminal 10A and the terminal 10B is started. . In this case, the terminal 10B can transmit stroke data input by handwriting in the terminal 10B to the terminal 10A, and can perform setting so that stroke data input by handwriting in the terminal 10A can be received from the terminal 10A. Do. Similarly, the terminal 10A can transmit stroke data input by handwriting on the terminal 10A to the terminal 10B, and can perform setting so that stroke data input by handwriting on the terminal 10B can be received from the terminal 10B. Do. When the process of block B26 is executed in this way, the terminal 10B operates as the guest terminal described above, and the user A can use the terminal 10B to allow the user B to use the handwriting sharing service. become.

Next, a case where user A wants user C to use the handwriting sharing service will be described. In this case, the user A performs a handwriting input operation such as a touch operation on the screen of the terminal 10C using the pen 100A unique to the user A.

When such an operation is performed, the digitizer 12C of the touch screen display 12 provided in the terminal 10C, for example, touches the pen 100A on the screen of the terminal 10C (for example, “touch” and “movement (slide)”). ) Is detected. In this case, the handwriting input unit 301 inputs a “touch” or “move (slide)” event from the digitizer 12C, and detects a handwriting input operation by the user A (block B27).

On the other hand, the pen ID acquisition unit 306a of the processing unit 306 included in the terminal 10C is a pen for identifying the pen 100A when a handwriting input operation using the pen 100A by the user A is detected on the screen of the terminal 10C. The ID is acquired (received) from the pen 100A (block B28).

Here, the pen ID acquired by the pen ID acquisition unit 306a is not a pen ID for identifying the pen 100C used by the user C using the terminal 10C. In this case, the connection management unit 306b transmits an authentication request including the pen ID acquired by the pen ID acquisition unit 306a to the authentication server device 400 described above (block B29).

Next, the authentication server device 400 receives the authentication request transmitted by the terminal 10C (the connection management unit 306b). The authentication server device 400 acquires the terminal ID included in the authentication information described above in association with the pen ID included in the received authentication request (block B30). Here, the terminal ID acquired by the authentication server device 400 is used by a user (here, user A) who uses the pen 100 (here, the pen 100A) identified by the pen ID included in the received authentication request. Tablet terminal 10 (here, an identifier for identifying terminal 10A.

The authentication server device 400 transmits the acquired terminal ID to the terminal 10C as a response to the authentication request transmitted from the terminal 10C in the block B29 described above (block B31).

The connection management unit 306b of the terminal 10C receives the terminal ID transmitted by the authentication server device 400. When the terminal ID is received in this way, the connection management unit 306b executes a process of starting a session between the terminal 10A and the terminal 10C identified by the received terminal ID (block B32).

In this case, for example, the terminal 10C logs in to the handwriting sharing service and requests the terminal 10A for connection information necessary for starting a session between the terminal 10A operating as the host terminal and the terminal 10C. To do. When connection information is returned from the terminal 10A to the terminal 10C as a response to this request, the terminal 10C can log in to the handwriting sharing service using the connection information, and a session between the terminals 10A and 10C is started. In this case, the terminal 10C can transmit stroke data input by handwriting at the terminal 10C to the terminal 10A, and can perform setting so that stroke data input by handwriting at the terminal 10A can be received from the terminal 10A. Do. Similarly, the terminal 10A can transmit stroke data input by handwriting in the terminal 10A to the terminal 10C, and can perform setting so that stroke data input by handwriting in the terminal 10B can be received from the terminal 10C. Do. When the process of block B32 is executed in this way, the terminal 10C operates as the guest terminal described above, and the user A can use the terminal 10C to allow the user C to use the handwriting sharing service. It becomes like this.

13 and 14, the authentication server device 400 that has received the authentication request (inquiry query) from the terminals 10B and 10C responds to the authentication request (a terminal ID for identifying the terminal 10A operating as the host terminal). ) Is transmitted to the terminals 10B and 10C, and the session is started from the terminals 10B and 10C. May be configured to issue a command to start a session with the terminals 10B and 10C and start the session from the terminal 10A (that is, the host terminal) side.

Next, an overview of operations of the host terminal (terminal 10A) and the guest terminals ( terminals 10B and 10C) when using the handwriting sharing service described above will be described with reference to FIGS. When the handwriting sharing service is used, wireless communication using, for example, Bluetooth or WiFi-Direct is possible between the terminal 10A and the terminals 10B and 10C.

Here, as illustrated in FIG. 15, when stroke data (for example, a handwritten character string “TABLET”) is input by hand using the pen 100 </ b> B in the terminal 10 </ b> B, the stroke data of the user B is transmitted from the terminal 10 </ b> B. It is transmitted to the terminal 10A. The terminal 10A displays the stroke data transmitted by the terminal 10B on the screen of the terminal 10A and transmits the stroke data to a guest terminal (here, the terminal 10C) other than the terminal 10B. The terminal 10C displays the stroke data transmitted by the terminal 10A on the screen of the terminal 10C. When the handwriting sharing service is used in this way, for example, the handwritten character string “TABLET” (stroke data) input by handwriting on the terminal 10B is displayed on the screens of the terminals 10A to 10C as shown in FIG. Is done.

On the other hand, as illustrated in FIG. 15, when stroke data (for example, handwritten character string “ABC”) is input by hand using the pen 100 </ b> C in the terminal 10 </ b> C, the stroke data of the user C is transmitted from the terminal 10 </ b> C to the terminal. 10A. The terminal 10A displays the stroke data transmitted by the terminal 10C on the screen of the terminal 10A and transmits the stroke data to a guest terminal (here, the terminal 10B) other than the terminal 10C. The terminal 10B displays the stroke data transmitted by the terminal 10A on the screen of the terminal 10C. When the handwriting sharing service is used in this way, for example, the handwritten character string “ABC” (stroke data) input by handwriting on the terminal 10C is displayed on the screens of the terminals 10A to 10C as shown in FIG. Is done.

In addition, as illustrated in FIG. 16, when stroke data (for example, a handwritten character string “STROKE123”) is input by handwriting using the pen 100 </ b> A in the terminal 10 </ b> A, the stroke data of the user A is transmitted from the terminal 10 </ b> A to the terminal. 10B and 10C. The terminal 10B displays the stroke data transmitted by the terminal 10A on the screen of the terminal 10B. Similarly, the terminal 10C displays the stroke data transmitted by the terminal 10A on the screen of the terminal 10C. When the handwriting sharing service is used in this way, for example, the handwritten character string “STROKE123” (stroke data) input by handwriting on the terminal 10A is displayed on the screens of the terminals 10A to 10C as shown in FIG. Is done.

15 and FIG. 16, it is described that wireless communication is performed only between the terminal 10A and the terminal 10B and between the terminal 10A and the terminal 10C. However, for example, the terminal 10A operating as a host terminal In the connection management unit 306b, users B and C ( terminals 10B and 10C used by the users B and C) who use the handwriting sharing service are managed. It is.

Further, when using the handwriting sharing service, the stroke data is not transmitted individually to each of a plurality of terminals, but the stroke data is transmitted by broadcast to all terminals connected to the network (segment), for example. It is also possible to adopt such a configuration. In this case, it is assumed that key information for using (that is, displaying) stroke data is managed in a plurality of terminals logged into the handwriting sharing service. According to this, even when the stroke data is transmitted by broadcast, it is possible to use the stroke data only at the terminal logged into the handwriting sharing service.

Further, here, the terminal 10A and the terminals 10B and 10C have been described as transmitting and receiving stroke data directly. The stroke data may be transmitted and received.

As described above, in the present embodiment, an operation (first operation) input by handwriting using the pen 100B (first pen) corresponding to the terminal 10B (first terminal) is detected on the screen of the terminal 10A. The stroke data (first stroke data) input by handwriting at the terminal 10A can be transmitted to the terminal 10B, and the stroke data (second stroke data) input by handwriting at the terminal 10B is transmitted to the terminal 10B. Set to be able to receive from.

Further, in the present embodiment, an operation (second operation) input by handwriting on the screen of the terminal 10A using the pen 100C (second pen) corresponding to the terminal 10C (second terminal) different from the terminal 10B. Is detected, the stroke data input by handwriting in the terminal 10A can be transmitted to the terminal 10C, and the stroke data input by handwriting in the terminal 10C (third stroke data) is received from the terminal 10C. Make the settings that are possible.

In the present embodiment, with such a configuration, when handwritten information (stroke data) is shared between a plurality of terminals, for example, the users B and C, for example, themselves on the screen of the terminal 10A operating as a host terminal A session between the terminal 10A, the terminal 10B, and the terminal 10C can be started only by performing a handwriting input operation using the pens 100B and 100C. That is, in the present embodiment, using the fact that the pen 100 used by each user has a unique pen ID, an operation related to connection between terminals when using the handwriting sharing service is intuitively called a handwriting input operation on the host terminal. Since it is replaced with an easy-to-understand user interface (UI), handwritten information can be easily shared.

Further, in the present embodiment, an operation (third handwriting input operation) input by handwriting using, for example, the pen 100A (third pen) corresponding to the terminal 10A is detected on the screen of the terminal 10B (or 10C). The stroke data input by handwriting at the terminal 10A can be transmitted to the terminal 10B (or 10C), and the stroke data input by handwriting at the terminal 10B (or 10C) is transmitted to the terminal 10B (or 10C). Set to be able to receive from. In the present embodiment, with such a configuration, the user A who uses the terminal 10A operating as the host terminal simply performs a handwriting input operation using the pen 100A on the screen of the terminal 10B or the terminal 10C. And the terminal 10B or 10C is started, and the user B or C who uses the terminal 10B or 10C can use the handwriting sharing service.

In the present embodiment, for example, it is assumed that a session between the terminal 10A and the terminal 10B or 10C is started when a handwriting input operation with the pen 100B or 100C is simply performed on the screen of the terminal 10A. However, it is also possible to adopt a configuration in which the session is started only when a predetermined handwriting input operation (gesture) for starting sharing of handwritten information is performed. In this case, for example, the session may be started only when the handwriting input operation is continuously detected for a predetermined time (for example, 5 seconds), or the handwriting input operation is predetermined. The session may be started only when a predetermined operation such as drawing a figure or touching a predetermined position is detected. According to such a configuration, for example, it is possible to prevent a situation in which handwritten information is erroneously shared by an operation not intended to share handwritten information.

Further, in the present embodiment, the authentication server device 400 that stores the authentication information is described as being present. However, a configuration in which the authentication server device 400 does not exist is also possible. In this case, for example, the terminal 10A on which the handwriting input operation with the pen 100B has been performed uses the pen ID for identifying the pen 100B and the terminal ID for identifying the terminal 10A (including packet data, etc.) It transmits (broadcast / multicast) to all terminals connected to the network (segment) in which the terminal 10A exists. In this case, it is assumed that each terminal used by a user who uses the handwriting sharing service holds a pen ID for identifying the pen 100 used by the user.

The terminal 10B that has received such packet data recognizes that the user B who owns the terminal 10B has performed a handwriting input operation on the host terminal using the pen 100B, based on the pen ID included in the packet data. The host ID can be recognized from the terminal ID included in the packet data. Thereby, the terminal 10B can start a session with the terminal 10A, for example, by executing the process of the block B26 shown in FIG. 14 described above.

Since the processing of the present embodiment can be realized by a computer program, the computer program is installed and executed on a computer through a computer-readable storage medium that stores the computer program, as in the present embodiment. The effect of can be easily realized.

Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalents thereof. *

DESCRIPTION OF SYMBOLS 10,10A, 10B, 10C ... Tablet terminal, 11 ... Main body, 12 ... Touch screen display, 12A ... LCD, 12B ... Touch panel, 12C ... Digitizer, 100, 100A, 100B, 100C ... Pen, 101 ... CPU, 102 ... Nonvolatile 103, main memory, 103a ... operating system, 103b ... handwriting sharing application program, 104 ... BIOS-ROM, 105 ... system controller, 106 ... GPU, 107 ... wireless communication device, 108 ... EC, 301 ... handwriting input unit , 302 ... Display processing unit, 303 ... Stroke data generation unit, 304 ... Stroke database, 305 ... Communication processing unit, 306 ... Processing unit, 306a ... Pen ID acquisition unit, 306b ... Connection management unit, 306c ... Stroke management , 400 ... authentication server device.

Claims (15)

1. A method performed using an electronic device,
   Detecting a first operation input by hand using a first pen corresponding to the first terminal on the screen of the electronic device;
   When the first operation is detected, the first stroke data input by handwriting in the electronic device can be transmitted to the first terminal, and the second stroke data input by handwriting in the first terminal is Setting to enable reception from the first terminal.
2. Detecting a second operation input by hand using a second pen corresponding to a second terminal different from the first terminal on the screen of the electronic device;
   When the second operation is detected, the first stroke data can be transmitted to the second terminal, and the third stroke data input by handwriting at the second terminal can be received from the second terminal. The method according to claim 1, further comprising: setting to perform.
3. When a third operation input by handwriting using a third pen corresponding to the electronic device is detected on the screen of the first terminal, the first stroke data can be transmitted to the first terminal. The method according to claim 1, further comprising: setting so that the second stroke data can be received from the first terminal.
4. The method according to claim 1, wherein the setting is performed when the first operation is detected continuously for a predetermined time.
5. The method according to claim 1, wherein the setting is performed when a predetermined operation is detected as the first operation.
6. A system including electronic equipment,
   Detecting means for detecting a first operation input by handwriting on a screen of the electronic device using a first pen corresponding to the first terminal;
   When the first operation is detected, the first stroke data input by handwriting in the electronic device can be transmitted to the first terminal, and the second stroke data input by handwriting in the first terminal is A connection management means for performing a setting to enable reception from the first terminal.
7. The detection means further detects a second operation input by hand using a second pen corresponding to a second terminal different from the first terminal on the screen of the electronic device,
   The connection management means is capable of transmitting the first stroke data to the second terminal when the second operation is detected, and receiving third stroke data input by handwriting in the second terminal. The system according to claim 6, wherein setting is made to enable reception from two terminals.
8. When a third operation input by handwriting using a third pen corresponding to the electronic device is detected on the screen of the first terminal, the first stroke data can be transmitted to the first terminal. The system according to claim 6, wherein the second stroke data is set to be received from the first terminal.
9. The system according to claim 6, wherein the connection management means performs the setting when the first operation is detected continuously for a predetermined time.
10. The system according to claim 6, wherein the connection management means performs the setting when an operation predetermined as the first operation is detected.
11. A program executed by a computer of an electronic device,
    In the computer,
    Detecting a first operation input by hand using a first pen corresponding to the first terminal on the screen of the electronic device;
    When the first operation is detected, the first stroke data input by handwriting in the electronic device can be transmitted to the first terminal, and the second stroke data input by handwriting in the first terminal is A program for executing the setting to enable reception from the first terminal.
12. In the computer,
    Detecting a second operation input by hand using a second pen corresponding to a second terminal different from the first terminal on the screen of the electronic device;
    When the second operation is detected, the first stroke data can be transmitted to the second terminal, and the third stroke data input by handwriting at the second terminal can be received from the second terminal. The program according to claim 11, further comprising: setting to perform.
13. When the computer detects a third operation input by handwriting using a second pen corresponding to the electronic device on the screen of the first terminal, the first stroke data is transferred to the first terminal. The program according to claim 11, further configured to perform a setting that enables transmission of the second stroke data from the first terminal.
14. 12. The program according to claim 11, wherein the setting is performed when the first operation is detected continuously for a predetermined time.
15. The program according to claim 11, wherein the setting is performed when a predetermined operation is detected as the first operation.

Images