WO2014045623A1

WO2014045623A1 - Electronic apparatus and account creation program

Info

Publication number: WO2014045623A1
Application number: PCT/JP2013/058475
Authority: WO
Inventors: Mitsuru Shimbayashi
Original assignee: Toshiba Corp
Current assignee: Toshiba Corp
Priority date: 2012-09-20
Filing date: 2013-03-18
Publication date: 2014-03-27
Anticipated expiration: 2015-03-20
Also published as: JP2014063321A

Description

D E S C R I P T I O N ELECTRONIC APPARATUS AND ACCOUNT CREATION PROGRAM

Field

Embodiments described herein relate generally to an electronic apparatus and account creation.

Background

Television receivers (electronic apparatus) which can be connected to the Internet have become

widespread.

When the user accesses the Internet by using a television receiver, the user is required to input information which is necessary for creating an account from a user interface (UI) displayed by the television receiver, by operating a remote controller.

Inputting information in accordance with the UI of the television receiver, however, has the problem that the user is required to get skilled in operation of the remote controller and get used to transition of display of the UI, which is large burden on the user who wishes to create the account. It can be considered that the size of the screen of the television receiver has an influence on creation of the account.

An object of the invention is to provide an electronic apparatus and an account creation program. Brief Description of the Drawings

A general architecture that implements the various features of the embodiments will now be described with reference to the drawings. The drawings and the associated descriptions are provided to illustrate the embodiments and not to limit the scope of the

invention .

FIG. 1 is an exemplary diagram showing an example of connection between electronic apparatuses according to an embodiment;

FIG. 2 is an exemplary diagram showing an example of flow of signals between a television receiver, a portable terminal device and a server device according to an embodiment;

FIG. 3 is an exemplary diagram showing an example of flow of signals between the television receiver, the portable terminal device and the server device

according to an embodiment;

FIG. 4 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment;

FIG. 5 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an embodiment ;

FIG. 6 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment;

FIG. 7 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment ;

FIG. 8 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment ;

FIG. 9 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment ;

FIG. 10 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment ;

FIG. 11 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment ;

FIG. 12 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment ;

FIG. 13 is an exemplary diagram showing an example of transmission and reception of control commands between the television receiver, the portable terminal device, and the server device according to an

embodiment ;

FIG. 14 is an exemplary diagram showing an example of the television receiver (electronic apparatus) according to an embodiment;

FIG. 15 is an exemplary diagram showing an example of the portable terminal device (electronic apparatus) according to an embodiment; and

FIG. 16 is an exemplary diagram showing an example of flow of signals between the television receiver, the portable terminal device, and the server device

according to an embodiment .

Detailed Description

Various embodiments will be described hereinafter with reference to the accompanying drawings. In general, according to one embodiment, an electronic device which is capable of communicating with another electronic device through a network and communicating with a server device through an external network characterized by comprising: a communication module (51) configured to transmit information unique to the electronic device and information to access the server device to said other electronic device, an account of the electronic device managed by the server device, and a control module configured to connect to the server device, after the control module receives notification that login to the account of the

electronic device has been completed from said other electronic device.

Embodiments will now be described hereinafter in detail with reference to the accompanying drawings.

FIG. 1 illustrates an example of connection between a television receiver (electronic apparatus) according to an embodiment and a portable terminal device (tablet device/electronic apparatus), which can be used for creating an account necessary for

performing connection to the Internet by the television receiver, on a home network. Constituent

elements/structures explained hereinafter may be realized by hardware, or software by using a

microcomputer (processing device, central processing unit [CPU] ) . In FIG. 1, a home network 1, such as one

conforming to the Digital Living Network Alliance

(DLNA) standard, connects electronic apparatuses, such as a television 5 and at least one tablet device (A) 7 or tablet device (b) 9, which plays back programs (also referred to as content /titles/information/streams ) that can be obtained as television broadcasting through radio wave (frequency) signals or a communication network, through a broadband router 3, such that the electronic apparatuses can mutually transmit and receive image data, sound data, and/or control signals.

The broadband router 3 connects the home network 1 to the Internet 101. The Internet 101 provides the television 5 and the tablet device 7 (9) with Web service 111 by connecting them to the server device 121.

The television (electronic apparatus) 5, an outline of which is illustrated in FIG. 14, includes at least an interface 51 which manages input and output of content, a recording and playback processor 52 which writes (records) content in a recording region 56 that is, for example, a hard disk drive (HDD) and Secure Digital (SD) storage, and reads content from the recording region 56, and a main control module 53 which controls writing of content in the recording and playback processor 52 and playback of content from the recording and playback processor 52, and controls constituent elements/structures explained hereinafter. The television 5 also includes at least an encoder 54 which is used for recording content, and a decoder 55 which is used for playing back content.

The television 5 decodes content

(programs/titles/information), which is received by a receiving module (not shown) and selected by a tuner

(not shown), by the encoder 54, and records the content on the recording region 56 through the recording and playback processor 52. The same is applicable to content (information/programs/titles) input as external inputs.

When playback of the content (program/title) is instructed, the television 5 decodes the content, which has been read from the recording region 56 by the recording and playback processor 52, by the decoder 55 to convert it to image output (video or still image) and sound output (audio, sound/music) , and outputs the image output to a display device (display module) 57. The sound output is output to an output module (not shown) such as speakers.

The tablet device (portable terminal device) 7 (9), an outline of which is illustrated in FIG. 15, at least includes an interface 71 which manages input and output of content, a recording and playback processor 72 which writes (records) content in a recording region 56 that is, for example, a hard disk drive (HDD) and Secure Digital (SD) storage, and reads content from the recording region 56, and a main control module 73 which controls writing of content in the recording and playback processor 72 and playback of content from the recording and playback processor 72, and controls constituent elements/structures explained hereinafter. The tablet device 7 (9) also includes at least an encoder 74 which is used for recording content, and a decoder 75 which is used for playing back content.

The tablet device 7 (9) encodes the input content (programs/titles/information) by the encoder 74, and records the content on the recording region 76 through the recording and playback processor 72.

When playback of the content (programs/titles) is instructed, the tablet device 7 (9) decodes the

content, which has been read from the recording region 76 by the recording and playback processor 72, by the decoder 75 to convert it to image output (video or still image) and sound output (audio, sound/music) , and outputs the image output to a display device (display module) 77. The sound output is output to an output module (not shown) such as an external output terminal.

The tablet device 7 (9) includes a touchpanel 77 which enables input of control signals or the like, a display module 78 which is prepared as one unitary piece with the touchpanel 77, and a communication controller 79 which enables communication with a communication line (wireless communication network) .

An outline of the embodiment will be explained with reference to FIG. 1.

The home network 1, which connects with the

Internet 101 (server device 121) through the broadband router 3, is connected with the television 5, and the tablet device A(7) or tablet device B(9).

The television 5 and the tablet terminal A (7) or tablet terminal B (9) can access the Web service 111 via the broadband router 3. The Web service is

available at the server device 121 on the Internet 101.

The television 5 and the tablet device A (7) or tablet device B (9) are correlated with each other, and can mutually transmit and receive desired messages and events. In addition, the television 5 can be operated by remote control from the tablet device A (7) or tablet device B (9) .

FIG. 2 shows an embodiment of creating an account necessary for connecting the television to the

Internet, from the tablet device. In the following explanation, the tablet device 7 is representatively explained with respect to the any one of the tablet devices .

When user interface (UI) operation for the UI displayed on the display module (display device) 57 by the television 5 from the remote controller or remote operation by the tablet device 7 is performed, the television 5 performs PUSH transmission to transmit an account creation uniform resource locater (URL) (221) and a television ID (222) to the tablet device 7 [201]. The account creation URL (221) is a URL of the Web service 111 which operates on the server device 121.

Next, the tablet device 7 displays a Web page of the received account creation URL (221) on the display module 78, and prompts the user to input information necessary for creating an account [202].

The user inputs account information (223) from the touchpanel 77, in accordance with the account creation Web page displayed on the display module 78 of the tablet device 7 [203] .

When input of account information (223) by the user with the tablet device 7 is finished, the tablet device 7 transmits the ID (222) of the television 5 and the account information (223) to the server device 121 [204] .

The server device 121 creates an account which is associated with the ID (222) of the television 5, by using the received account information (223) [205] .

The tablet device 7 performs PUSH notification (automatically transmit information in accordance with a predetermined process) to notify the television 5 that the account has been created [206] .

When the television 5 receives notification of completion of account creation, the television 5 transmits the ID (222) to the server device 121, and receives login information (224) of the account

associated with the ID (222) from the server device 121 [207] . The login information may be any information as long as it is information to log in to the account.

For example, the login information may be a combination of the user ID and a password, or only a password.

The received login information (224) of the account is registered (recorded) by the television 5 in the recording region 56 or firmware of the main control module 53. Thereby, the television 5 can log in to the Web service 111 which operates on the server device 121 by using the registered login information (224)

thereafter [208] .

FIG. 3 illustrates another embodiment of creating an account necessary for connecting the television to the Internet from the tablet device.

When UI operation for the UI displayed on the television 5 from the remote controller or remote operation by the tablet device 7 is performed, the television 5 transmits an ID (321) of the television 5 to the server device 121. Thereby, the television 5 obtains an encoded television ID (323) which is encoded by using a secret key (322) held by the server device 121 [301].

Next, the television 5 performs PUSH transmission of an account creation URL (324) and the encoded television ID (323) to the tablet device 7 [302]. The account creation URL (324) is the URL of the Web service 111 which operates on the server device 121.

Next, the tablet device 7 displays a Web page of the received account creation URL (324) on the display module 78, and prompts the user to input information necessary for creating an account [303].

The user inputs account information (325) from the touchpanel 77, in accordance with the account creation Web page displayed on the tablet device 7 [304].

When input of account information (325) by the user with the tablet device 7 is finished, the tablet device 7 transmits the encoded television ID (323) and the account information (325) to the server device 121 [305] .

The server device 121 decodes the received encoded television ID (323) by a secret key (322) held by the server device 121 to generate a television ID (326) , and checks (compares) whether the decoded ID (326) is the same as the television ID (321) [306].

Next, the server device 121 creates an account which is associated with the television ID (321), by using the received account information (325) [307].

The tablet device 7 performs PUSH notification (automatically transmit information in accordance with a predetermined process) to notify the television 5 that the account has been created [308] . When the television 5 receives notification of completion of account creation, the television 5 transmits the ID (321) to the server device 121, and receives login information (327) of the account

associated with the ID (321) from the server device 121 [309] .

The login information (327) of the received account is registered (recorded) by the television 5 in the recording region 56 or firmware of the main control module 53. Thereby, the television 5 can log in to the Web service 111 which operates on the server device 121 by using the registered login information (327)

thereafter. .

FIG. 4 to FIG. 13 illustrate transmission and reception of control commands between the television receiver, the portable terminal device and the server device, to create an account necessary for connecting the television to the Internet from the tablet device explained with reference to FIG. 2 or FIG. 3. FIG. 4 to FIG. 11 illustrate communication between tablet device A(7) or tablet device B(9) and an http server of the television 5, and access to an outer server by the television 5. FIG. 12 and FIG. 13 illustrate

communication between tablet device A(7) or tablet device B(9) and an http server of the television 5, and access to an outer server by the television 5.

As illustrated in FIG. 4, for example, a command "401: GET remote message request"

is transmitted from tablet device A to the television 5, that is, the http server. Specifically, tablet device A changes to a state of waiting for reception of a message from the http server. In the case where tablet device B accesses the http server (television 5) , a command

"421: GET remote message request"

is transmitted. Thereafter, tablet device B changes to a state of waiting for reception of a message from the http server.

In addition, for example, a command

"441: GET internal message request"

is transmitted from the Javascript of the outer server to the http server. Thereafter, the Javascript of the outer server changes to a state of waiting for a message from the http server.

When each of tablet device A (tablet device B) and the Javascript of the outer server is in the state of waiting for reception of a message from the http server, for example, the Javascript of the outer server requests the http server to input characters. For example, when a command

"461: PUT internal message request"

is transmitted, the http server transmits a request (message) from the Javascript of the outer server to tablet device A (tablet device B) . Specifically, a command

"411: Show Software Keyboard"

"431: Show Software Keyboard (for tablet B) " is transmitted to respond to the request 401 (421) .

Thereafter, for example, a command

"404: PUT remote message (Notify Input Changed:

A) "

is returned to the http server, as a response to the request (message) from the Javascript of the outer server by tablet device A <<in the state of waiting for reception of a message from the http server>>.

When the http server receives a response from tablet device A, the http server transmits, for

example, a command

"451: Update Text Input to Text-A"

to the Javascript of the outer server.

In addition, tablet device A returns a command

"405: Put remote message (Notify Input Changed:

B) "

to the http server, as a response to the request (message) from the Javascript of the outer server «in the state of waiting for reception of a message from the http server>>. The http server returns, for example., a command

"452: Update Text Input to Text-B"

to the Javascript of the outer server <<which is in the state of waiting for reception of a message from the http server».

Next, tablet device A notifies the http server of, for example, a command

"406: PUT remote message request (Notify Input

Validated: B)".

The http server returns, for example, a command "453: Validate Text-B of Text Input"

to the Javascript of the outer server <<which is in the state of waiting for reception of a message from the http server>>, in response to the command 406 from tablet device A.

Thereafter, at predetermined timing, for example, a command

"446: PUT internal message (hide keyboard)" is transmitted from the Javascript of the outer server <<which is in the state of waiting for reception of a message from the http server by the command 444>> to the http server, and a command

"412: Hide Software Keyboard"

is transmitted from the http server to tablet device A.

FIG. 5 illustrates another example of the example illustrated in FIG. 4. In FIG. 5, control which is substantially the same as the control illustrated in

FIG. 4 is denoted by a reference numeral which is obtained by changing the number of the thousand' s place of the reference numeral of FIG. 4, and part or all of the explanation is omitted (the same is applicable to FIG. 6 to FIG. 13) .

FIG. 5 illustrates an example of the case where a command

"523: PUT remote message (Notify Input Changed:

B) "

is transmitted from tablet device B to the http server, instead of the command

"PUT remote message request"

same as "405" in FIG. 4.

Specifically, the http server notifies the

Javascript of the outer server <<which is in the state of waiting for reception of a message from the http server by the command 541>> of a command

"551: Validate Text-A of Text input",

and notifies the Javascript of the outer server <<which is in the state of waiting for reception of a message from the http server by the command 542>> of a command

"552: Validate Text-B of Text input".

Thereafter, when tablet device A notifies the http server of a command

"505: PUT remote message request (Notify input Validated A) ",

the http server notifies the Javascript of the outer server <<which is in the state of waiting for reception of a message from the http server by the command 543>> of a command

"553: Validate Text-A of Text Input".

On the other hand, when cancel is instructed, for example, in FIG. 8, the http server notifies the

Javascript of the outer server of a command

"853: Cancel Text Input",

which corresponds to, for example, a command "806: PUT remote message request (Push Cancel Button) "

from tablet device A.

In response to the command, the Javascript of the outer server transmits a command

"846: PUT internal message request (hide

Keyboard) "

to the http server. This state is changed to a command

"812: Ignore hide Keyboard"

in tablet device A.

As illustrated in FIG. 9, when cancel is

instructed by tablet device B with a command such as a command

"923: PUT remote message (Push Cancel Button)", the http server transmits a command

"953: Cancel Text Input"

to the Javascript of the outer server.

"946: PUT internal message request (hide

Keyboard) "

to the http server. This state is changed to a command

"932: Ignore hide Keyboard"

in tablet device B.

When the process is proceeded to creation of an account by the tablet device, input of the television 5 by the remote controller may be cancelled, by a command such as a command

"1145: PUT internal message (Cancel Text Input by TV side) "

illustrated in FIG. 11.

FIG. 6, FIG. 7, and FIG. 10 illustrate examples of transmission and reception of commands under conditions which are different from the conditions of the examples illustrated in FIG. 4 (5), FIG. 8 (9) and FIG. 11.

For example, in FIG. 6, when the commands "Update Text Input to Text-A" and "Update Text Input to Text-B" are transmitted from tablet device A as illustrated in FIG. 4, the Javascript of the outer server adopts the command "Update Text Input to Text-B" which was

transmitted later, that is, the Javascript of the outer server is notified of a command "Notify Input Changed: B (606: PUT remote message request)" from tablet device A while the Javascript of the outer server is not in the state of waiting for reception of a message.

Thereby, a command

"642: Notify Input Changed: B is discarded", which indicates that the command "Update Text Input to Text-A" was discarded, is transmitted to the http server.

In response to the command 642, the Javascript of the outer server is notified of a command

"652: Validated Text-B of Text input"

from the http server.

Thereafter, a command

"645: PUT internal message (hide Keyboard)" is transmitted from the Javascript of the outer server to the http server, and thereby tablet device A is notified of a command

"612: Hide software Keyboard"

from the http server.

FIG. 7 illustrates an example in which the

Javascript of the outer server returns a command

"747: PUT internal message request (hide

Keyboard) ",

in response to a command

"707: PUT remote message request (Notify Input Validated: B) "

transmitted from tablet device A, when one tablet

(tablet device A) transmits commands "Update Text Input to Text-A" and "Update Text Input to Text-B" to the http server as illustrated in FIG. 4 and tablet device B transmits a command

"724: Notify Input Changed: C".

FIG. 10 illustrates an example in which the Javascript of the outer server transmits a command

"1046: PUT internal message request (Push OK Button of TV s Remote controller) "

and commands "Cancel Text Input", when tablet A transmits commands "Update Text Input to Text-A" and "Update Text Input to Text-B" to the http server and tablet device B transmits a command

"1023: Notify Input Changed: C".

FIG. 12 and FIG. 13 illustrate transmission and reception of control signals (commands) between tablet device A(7) or tablet device B(9) and the http server of the television 5, and between the television 5 and the outer server.

As illustrated in FIG. 12, for example, a command "1201: GET remote message request"

is transmitted from the tablet device (A) to the http server.

The Javascript of the outer server returns, for example, a command

"1241: GET internal message"

to the http server.

In addition, the Javascript of the outer server transmits a command "1261: get token: tl from the server"

to the (connected) outer server, and changes to a state of waiting for reception of a message.

In response to the command "get token: tl

from the server (1261)", the outer server returns a command

"1246: PUT v2 internal/message (Show ExternalView : url = a, token = tl) request (Make tablets show their Web View) "

to the http server.

The http server which has received the command 1246 returns, for example, a command

"1211: Show ExternalView: url = a, token = tl" to tablet device A.

Thereafter, in response to the command "1211: Show ExternalView: url = a, token = tl", tablet device A transmits, for example, a command

"1204: PUT remote message request (Notify URL Changed: url = a, token = tl)"

to the http server.

The http server which has received the command 1204 transmits, for example, a command

"1251: Notify URL Changed: url = a, token = tl" to the Javascript of the outer server.

When there is a request to change the url to [b] from tablet device A, tablet device A transmits, for example, a command "1205: PUT remote message request (Notify URL Changed: url = b, token = tl)".

The http server which has received the command 1205 transmits, for example, a command

"1252: Notify URL Changed: url = b, token = tl" to the Javascript of the outer server.

In response to the command 1252, the outer server transmits, for example, a command

"1247: PUT remote message request (Receive url = b and make tablet close their Web Views)"

to the http server at a predetermined timing.

The http server receives the command "1247", and transmits, for example, a command

"1212: hide ExternalView"

to tablet device A.

On the other hand, tablet device A transmits, for example, a command

"1206: PUT remote message request (Notify

ExternalView Hidden: token = tl)"

to the http server. In the same manner, tablet device B transmits, for example, a command

"1224: PUT remote message request (Notify

ExternalView Hidden: token = tl)"

to the http server.

The http server notifies the Javascript of the outer server «which is in the state of waiting for reception of a message from the http server (with the command "1243") >> of, for example, a command

"1253: do nothing (Notify ExternalView Hidden, token = tl) ".

When the command "do nothing" is returned from the Javascript of the outer server to the http server in response to the command "1253", the http server

notifies the Javascript of the outer server <<which is in the state of waiting for reception of a message from the http server by the message "1244">> of, for

example, a command

"1254: Notify ExternalView Hidden, token = tl".

On the other hand, the Javascript of the outer server transmits, for example, a command

"1262: get new information by token: tl from the server"

to the outer server, to obtain various information items associated with the identification information tl (token = 1) from the outer server.

The example illustrated in FIG. 13 is different in that the Javascript of the outer server executes

"processing for url = a, token = tl (if needed) ", if necessary, when the Javascript of the outer server receives, for example, a command

"1351: Notify URL Changed: url = a, token = tl", which is transmitted to the Javascript of the outer server from the http server that has received a command "1304: PUT remote message request (Notify URL

Changed: url = a, token = tl)".

In the same manner, the example illustrated in

FIG. 13 is different in that the Javascript of the outer server executes

"processing for url = b, token = tl (if needed)", if necessary, when the Javascript of the outer server receives, for example, a command

"1352: Notify URL Changed: url = b, token = tl", which is transmitted to the Javascript of the outer server from the http server that has received a command

"1305: Notify URL Changed: url = b, token = tl (PUT remote message request)".

Specifically, the Javascript of the outer server provides a trigger for closing the External . view in the example illustrated in FIG. 12, and a trigger for closing the External view is a UI action (for example, tapping the close button) of tablet device A in the example illustrated in FIG. 13.

Transmission and reception of control signals (commands) between tablet device A (7) or tablet device B (9) and the http server of the television 5, and between the television 5 and the outer server, which are performed thereafter in the example of FIG. 13 are similar to those in FIG. 12, and thus explanation thereof is omitted. As described above, using the embodiment enables reduction of the user's burden required for creating an account to the minimum, and the user' s convenience can be improved. In addition, the user's convenience is improved, in comparison with the method of using another terminal of high usability such as a personal computer and registering only information necessary for login by using the UI of the television.

FIG. 16 discloses a modification of an embodiment.

An electronic apparatus (television) which is capable of communicating with another electronic apparatus (tablet device) through a network, and communicating with a server device (account server) through an external network, comprising:

a communication module [A] which transmits

identification information of the electronic apparatus (television) and information to access the server device (account server) that manages an account of the electronic apparatus (television) to said other

electronic apparatus (tablet device) , characterized in that

the electronic apparatus can connect [E] with the server device (account server) after the electronic apparatus receives notification that login to the account of the electronic apparatus (television) has been completed, from said other electronic apparatus (tablet device) . <A> The television apparatus transmits an ID (unique identification information) of the television and information (URL) to access the account server to the tablet device. The identification information of the television may be any information as long as it identifies the television, such as a number which is uniquely assigned to the television, an existing number (such as MAC address), and a number which is obtained by converting an existing number.

Next, after the tablet device receives the ID of the television and information to access the account server from the television, login information which corresponds to the ID of the television is input. In the embodiment, suppose that the login information is input by the user to the tablet device <B> . The login information may be stored in the tablet device, or may be input by the user each time through the user

interface of the tablet device.

<C> The tablet device accesses the account server by using the information (URL) to access the account server. The tablet device logs in to the account which corresponds to the user or the television, by using the ID of the television and the ID and the password of the user. The information to access the account server is not limited to URL, but may be an IP address or

information which identifies the account server, or part of the information. The ID of the television may be the same as, or different from, the ID of the user.

<D> Next, the account server determines whether login to the account is possible or not, by using the ID of the television and the login information. When it is determined that login is impossible <NO (NG) of D>, the account server notifies the tablet device that login ended in failure. When login ended in failure, the tablet device may attempt login by transmitting the login information to the account server again, notify the television that login ended in failure, or end the processing.

When it is determined that login is possible <YES (OK) of D>, the account server notifies the tablet device that login has been completed.

<E> Next, the tablet device notifies the

television that login to the account has been

completed. The notification from the tablet device to the television is performed (by PUSH method) without waiting for another request from the television.

<F> Next, after the television has received notification that login to the account has been

completed from the tablet device, the television accesses the server device. Since login processing to the account has already been completed by the tablet device, no separate login processing is required when the television accesses the server device.

By logging in to the account as described above, the user can log in to the server (account) by using the user interface of the tablet device, not the user interface of the television. Thereby, the user's convenience is improved.

<A'> The following method can be adopted as a method of transmitting the ID of the television from the television to the tablet device. Before processing <A>, the television accesses the account server by using the ID of the television, and obtains encoded television ID which is encoded by a secret key held by the account server. Next, the television transmits the encoded television ID to the tablet device. Thereby, it is possible to prevent unrelated tablet devices other than the tablet that is connected to the

television, to which the account server has transmitted the encoded television ID, from creating an account.

It is possible to set the term of validity for the ID of the television. When login to the server

(account) cannot be completed within the validity term of the ID of the television, the ID of the television expires. Thereby, login by an unauthorized person can be prevented.

To prevent creation of overlapping login accounts by a plurality of tablet devices that are associated with the television, the tablet device can transmit a tablet ID which identifies the tablet device to the account server together, when the tablet device accesses the account server in processing <B>.

Thereby, creation of overlapping login accounts can be prevented .

Claims

C L A I M S

. 1. An electronic device (5) which is capable of communicating with another electronic device (7(9)) through a network (3) and communicating with a server device (121) through an external network (111(101)), characterized by comprising:

a communication module (51) configured to transmit information unique to the electronic device and

information to access the server device to said other electronic device, an account of the electronic device managed by the server device; and

a control module (53) configured to connect to the server device, after the control module receives notification that login to the account of the

electronic device has been completed from said other electronic device.

2. The electronic device of claim 1,

characterized in that

the communication module (51) configured to transmit identification information of the electronic device, the identification information encoded by a key in the server device.

3. An electronic device (7(9)) which is capable of communicating with other electronic device (5) through a network (3) and communicating with a server device (121) through an external network (111(101)), characterized by comprising: a communication module (71(91)) configured to receive identification information of said other electronic device and information to access the server device, from said other electronic device, an account of the electronic device managed by the server device; and

an input module (77(97)), to which login

information of an account of said other electronic device is input by the user,

characterized in that

the communication module (71(91)) configured to transmit the identification information of said other electronic device and the login information of the account of said other electronic device to the server device, and

said other electronic device is notified that login to the account of said other electronic device has been completed, after login to the account of said other electronic device has been completed.

. A system configured to allow a computer to execute characterized by comprising:

a function of causing an electronic apparatus, which is capable of communicating with another

electronic apparatus through, a network and

communicating with a server device through an external network, to receive identification information of said other electronic apparatus and information to access the server device from said other electronic apparatus, an account of the electronic device managed by the server device;

a function of enabling the user to input login information of an account of said other electronic apparatus ;

a function of transmitting the identification information of said other electronic apparatus and the login information of the account of said other

electronic apparatus to the server device; and

a function of transmitting, to said other

electronic apparatus, notification that login to the account of said other electronic apparatus has been completed, after login to the account of said other electronic apparatus has been completed.