TW201528799A - An information concentrating center capable of making P2P connections with remote client devices - Google Patents

Abstract

The present invention discloses an information concentrating center such as a set top box, wherein the information concentrating center comprises: at least one module for concentrating information from at least one information source; and at least one module coupling to the Internet, for establishing a P2P connection with a remote client device through the Internet, wherein at least one portion of the information is delivered to the remote client device through the P2P connection.

Description

Information aggregation center capable of establishing a point-to-point connection with a remote client device

The present invention relates to a communication system, and more particularly to a communication system using a P2P (Peer-to-Peer) connection.

Typically, a Set Top Box is used to connect to a television to view television programs transmitted via satellite or cable. The set-top box can be thought of as an Information Concentration Center for aggregating various information such as video and audio, which can then be passed to a device, such as a television, for viewing. However, conventional set-top boxes are primarily used to provide information to televisions, limiting their use. There is therefore a need for an efficient way to use the more capabilities of the set-top box.

It is an object of the present invention to provide an integrated solution for establishing a P2P connection for an information aggregation center.

In an example, an information aggregation center is disclosed, including: at least one first module for collecting information from at least one information source; and at least one second module coupled to the Internet for a distance The end client device establishes a point-to-point (P2P) connection over the Internet, wherein at least a portion of the information is transmitted by the P2P connection to the remote client device.

In one example, the information gathering center is a Set Top Box.

In an example, the information aggregation center has a first unique identification code (UID), and the first unique identification code (UID) is registered in at least one connection server to associate connection information of the aggregation center, where The remote client device communicates with the at least one connection server and establishes the P2P connection according to the connection information provided by the at least one connection server, wherein the remote client is established when the P2P is established The device is not registered in the at least one connection server.

In an example, the remote client device does not have a connection information for being registered in the at least one connection server to associate the remote client device when contacting the at least one connection server. Unique identification number (UID).

In one example, the source of information is a satellite feed containing television programming.

In one example, the information gathering center is connected to an electrical appliance via a router through which the remote client device controls the home appliance.

In one example, the information aggregation center further includes a formatting module to convert the information into a format suitable for viewing by the remote client device.

In an example, a home appliance includes: at least one module coupled to an information gathering center, wherein a P2P connection is established between the information gathering center and a remote client device, wherein the far The end client device is connected to the information aggregation center via the P2P connection to control the home appliance.

In an example, the information aggregation center has a first unique identification code (UID), and the first unique identification code (UID) is registered in at least one connection server to associate connection information of the aggregation center. The remote client device communicates with the at least one connection server and establishes the P2P connection according to the connection information provided by the at least one connection server, wherein when the P2P is established, the far The end client device is not registered in the at least one connection server. [Simplified illustration]

Fig. 1 is a schematic view showing the state of the first embodiment (1). Fig. 2 is a schematic view showing the state of the first embodiment (2). Fig. 3 is a schematic view showing the state of the first embodiment (3). Fig. 4 is a schematic view showing the state of the first embodiment (4). Fig. 5 is a schematic view showing the state of the first embodiment (5). Fig. 6 is a schematic view showing the state of the first embodiment (6). Fig. 7 is a schematic view showing the state of the first embodiment (7). FIG. 8 is a schematic diagram of a plurality of connection server groups for a remote device to log in. FIG. 9 is a connection flowchart of a connection server and a management server. Figure 10 is a flow chart showing the connection between the remote device and the connection server. Figure 11 is a flow chart showing the connection of the near-end device requesting connection with the remote device. FIG. 12 is an IoT cross-platform architecture of an example of the present invention. 13A-D are block diagrams showing an integrated circuit in an example of the present invention. 14A-B are block diagrams of two devices connected by a P2P. Figure 15 is a schematic diagram of the integrated identification code (UID) on the processor. Figure 16 is a schematic diagram of the integrated identification code (UID) and serial number on the processor. FIG. 17 is a schematic diagram showing a system of an information aggregation center connected to a remote client device using a P2P connection according to an embodiment of the present invention. FIG. 18 is a schematic diagram showing the system of a set-top box connected to a remote client device using a P2P connection according to an embodiment of the present invention. FIG. 19 is a diagram showing a unique identification code associated with a set-top box and a connection server to establish a P2P connection according to an embodiment of the present invention.

This case is a remote message communication system and its connection method. The following describes the technology of the present invention in conjunction with the drawings.

First, the present disclosure defines a remote message communication system including at least one remote device, a management server, and at least one connection server, and the remote message communication system accepts a request from at least one near-end device to make the near-end A method for establishing a connection between the device and the remote device, and a method for connecting the remote message communication system, the method comprising the following steps: A. at least one remote device requests at least one support by the management server via the Internet The address of the connection server of the remote device; B. the remote device logs the information of the remote device to the connection server according to the address provided by the management server; C. a near-end device transmits The Internet sends a request to the management server to find the designated remote device; D. The management server responds to the near-end device by the address of the connection server to which the specified remote device is logged; The near-end device submits a request to the connection server to connect to the designated remote device according to the responded address; F. the connection server establishes the near-end device and the quilt according to the request of the near-end device Designated far Connection equipment. The technical focus of this method is to make the connection server and the remote device do not need to directly disclose their IP address or Domain name. All the near-end devices can only request the management server to find the designated remote device first. The address of the connection server provided by the management server is requested by the near-end device to establish a connection. Therefore, the connection server and the remote device can be reduced to reduce the risk of being invaded by the hacker. From the perspective of the near-end device, the near-end device does not need to have a fixed IP, nor does it need to memorize a fixed IP address or a domain name, which can save a lot of technical problems of connection settings for users of the near-end device. .

In order to more specifically describe the foregoing method, the present disclosure further discloses a remote message communication system that specifically implements the method, the remote message communication system including at least one management server, at least one connection server, and at least one remote device. . Please refer to FIG. 1. FIG. 1 is a schematic diagram showing the architecture of the remote message communication system. In Figure 1, it can be seen that the two management servers 11, 12 form a management server group 1 for mutual backup. The management server 11, 12 stores a device list and a server list, and the device list stores information of a plurality of remote devices that are allowed to log in. The server list stores information about the multiple connection servers. In a specific implementation manner, the server list may include multiple connection servers operated by different service providers, or multiple connection servers with different supported device types, or multiple locations. A different connection server. Further, there is a correspondence between the device list and the server list, which will be described in detail later. It is further seen in FIG. 1 that the remote message communication system further has a connection server 201 and a connection server 211. In this embodiment, the connection server 201 and the connection server 202 can be classified into different ones. The service provider operates. Moreover, it can be seen in FIG. 1 that the connection server 201 can form a connection server group A 20 with another connection server 202 for mutual backup; similarly, the connection server 211 is connected to another connection. The server 212 constitutes a connection server group B 21 to be mutually redundant. In order to facilitate the description of the technology of the present invention, the following connection objects will directly represent the server to which the server group 1 and the connection server group A 20 and the connection server group B 21 belong. The remote messaging system further includes a remote device A 31, a remote device B 32, and a remote device C 33. As described above, the device list has information of a plurality of remote devices, and the remote devices A~C 31, 32, and 33 each have their unique identification code (Unique ID), and the remote devices A~C The service provider's messages belonging to 31, 32, and 33 have been pre-stored in the device list stored in the management server group 1. When the connection server group A 20, the connection server group B 21, and the remote device A 31, a remote device B 32, and a remote device C 33 are connected to the Internet. The connection server group A 20 and the connection server group B 21 transmit a server login information 92 to the management server group 1 via the Internet to log in the address and configuration information (model, connection) Status and other information). The management server group 1 verifies whether the connection server group A 20 and the connection server group B 21 are legitimate devices that are pre-stored in the server list, and if the connection server group A 20 is replied to The connection server group B 21 has been successfully logged in. In order to find a server that can be supported, the remote device A 31 to the remote device C 33 respectively send a server query information 91 to the management server group 1 through the Internet. The management server group 1 After verifying whether the remote device A 31 to the remote device C 33 are pre-stored in the device list, the remote device A 31 to the remote device C 33 respectively reply to the connected target.

In a specific implementation manner, the connection server group A 20 and the connection server group B 21 may be operated by different service providers respectively. Therefore, the management server group 1 will be remotely located. Device A 31 is assigned to connect to the connection server group A 20 operated by the service provider supporting remote device A 31. Similarly, based on the service provider, the remote device B 32 and the remote device C 33 are assigned by the management server group 1 to the service provider supporting the remote device B 32 and the remote device C 33. The connected server group B 21 that is operated. However, the remote messaging system also includes different implementations, and the management server group 1 may also assign the remote device separately because the remote device A 31 to the remote device C 33 are different product types. A 31 to remote device C 33 log in to connection server group A 20 or connection server group B 20. Another different implementation manner is that the management server group 1 can also be assigned to connect to the closer connection server group A 20 according to the geographical location of the remote device A 31 to the remote device C 33 itself. Connect to server group B 21.

Referring to FIG. 2, based on the connection address that the management server group 1 responds, the remote device A 31 is connected to the connection server group A 20 and logs in the information of the remote device A 31. Connect to server group A 20. Similarly, according to the connection address that the management server group 1 responds, the remote device B 32 and the remote device C 33 are connected to the connection server group B 21, and log in their own information to the connection. In server group B 21 . Let the connection server group A 20 know the network address of the remote device A 31; the connection server group B 21 knows the network of the remote device B 32 and the remote device C 33 Address.

Referring to FIG. 3 again, the remote message communication system can connect one or more near-end devices 4, and the near-end device 4 needs to have an application interface program (API) that supports connection with the management server group 1. Application Programming Interface), the near-end device 4 can select a designated remote device through the application interface program. It is assumed that the near-end device 4 is connected to the remote device A 31 through the application interface program, and the near-end device 4 sends a link query information 94 to the management server group 1 through the application interface program to query the management server. What is the connection server group that can be connected to the remote device A 31? The management server group 1 provides the location of the connection server group A 20 registered by the designated remote device (the remote device A 31). Therefore, the application interface program of the near-end device 4 is further connected to the connection server group A 20 according to the address of the management server group 1, and the near-end device 4 issues a desire to connect with the remote device A 31. A connection to the connection request information 95. Referring to FIG. 5, the connection server group A 20 preferentially uses a hole punching technique to transmit a dozen holes connection messages 960 and 961 to the near-end device 4 and the remote device A 31, respectively. Having the near-end device 4 establish a point-to-point transmission connection 97 with the designated remote device A 31, the near-end device 4 can obtain information of the remote device A 31 through the point-to-point transmission technology, or the remote device A 31 controls. The aforementioned hole punching technique can be referred to the patents of US Patent Publication No. 2009/0100309, and the German Patent No. 2475279. Since the hole punching technique is not a technical feature claimed in the present case, its technical content will not be described again. Alternatively, as shown in FIG. 6, if the connection server group A 20 does not complete the hole punching procedure for both, the near-end device 4 and the designated one are mutually forwarded through the connection server group A 20 The data packet of the remote device A 31.

Since the near-end device 4 needs to obtain the connection address of the connection server group A 20 and the connection server group B 21 through the management server group 1, the connection server group A 20 The address and mechanical specification change of the connection server group B 21 does not prevent the near-end device 4 from inquiring about the connection object. Based on this feature, the architecture (quantity, specification, category, etc.) of the connection server group B 21 can be changed according to the needs of the market. For example, when the number of online products of a certain type of products increases, the support for such products can be increased. The number of connected servers to match the device load. You only need to update the server list when adding a connection server group or changing the connection information of the connection server group (such as IP address change) or changing the number of machines in the connection server group. Let the connection server group send the server login information 92 to the management server group 1 again to log in. Similarly, when the number and type of remote devices change, or when the connection server group to which the remote device is logged changes, the device list is also updated, and the remote device again provides the provided connection servo. The group asks for the connection server group information for the connection.

Please refer to FIG. 7. FIG. 7 is an embodiment of the extension of the remote message communication system. The embodiment adds a remote device D 34, which can update the management server group 1 even if the number of addresses or the address changes. Increase the number of supported remote devices (or specifications) for the device list. Both the remote device A 31 and the remote device D 34 can re-query the connectable connection server group by the management server group 1 through the process of transmitting the server query information 91. Similarly, in FIG. 7, it can be seen that the connection server group B 21 adds a connection server 213, and a new connection server group C composed of connection servers 221, 222, and 223 is added. 22. Similarly, the number of connection servers entering the remote messaging system is amplified by updating the server list of the management server group 1. Therefore, the remote message communication system allows the number, specifications, and categories of the remote device and the connection server group to be expanded and changed according to requirements, and only needs to update the server list, device list, and again to the management server group. Group 1 login is sufficient, so that the manufacturer of the connection server group or the remote device can be changed according to the load of the device.

The remote messaging system allows multiple connection servers to accept the same remote device login. Please refer to FIG. 8. FIG. 8 discloses that the remote messaging system includes connection server groups A, D, and E20. 23, 24, the connection server group D 23 is constituted by the connection servers 231, 232, and the connection server group E 24 is constituted by the connection servers 241, 242. After the remote device A 31 queries the management server group 1 by issuing the server query information 91, the management server group 1 replies to the remote device A 31 and the connection server groups A and D. , E 20, 23, 24 to log in. Through this feature, the different connection server groups A, D, E 20, 23, 24 can support the remote device A 31 together. The remote device A 31 can still log in to one of the connection server group D 23 or the connection server group E 24 assuming that the connection server group A 20 is faulty or other reasons are offline. It is also assumed that the remote device A 31 is a mobile device, and the remote device A 31 can be connected to any of the connected server groups whose physical distance is closest through the allocation of the management server group 1.

The correspondence between the plurality of remote devices and the connection server group is as shown in Table 1:

Taking Table 1 as an example, the server list of the management server may store the connection servers Ser01 to Ser05 operated by the service provider A and the connection servers Ser11 to Ser12 operated by the service provider B. The connection servers Ser01 to Ser03 are allocated for the remote devices D01 to D05 to log in, and D01 to D05 are the identification codes of the remote devices. As described earlier, each remote device has its unique identification code. Used to authenticate and identify the identity of the remote device for the management server or connection server. The connection servers Ser01 to Ser03 receive a request from the near-end device to establish a connection with the remote devices D01 to D05. Since the connection server Ser01 to Ser03 can perform the same function, the connection servers Ser01 to Ser03 can be mutually redundant, and the connection servers Ser01 to Ser03 can be respectively set to different positions, such as connection. The servers Ser01 to Ser03 are located in Shanghai, Tokyo, and Los Angeles, and the remote devices D01 to D05 can be registered in a connection server that is closer to the geographic location. Similarly, the remote devices ser04 to ser05 are registered by the remote devices D06 to D09. The connection servers Ser11 to Ser12 operated by the service provider B are registered by the remote devices D11 to D14. Therefore, for the management server, as long as the remote device D01 goes online to query the connection server, the management server can simultaneously provide the location of the connection server Ser01 to Ser05 to the remote device D01, so that the remote device D01 can be used at any time. You can find a connection server that is working properly.

Thereby, the plurality of connection server groups in the remote message communication system can be mutually supported, and the connection server group includes a plurality of connection servers that can be mutually redundant. The multiple backup architecture makes the remote messaging system very stable and does not affect operation due to a few mechanical failures.

Referring to FIG. 9, the operation between the foregoing connection server and the management server is as shown in FIG. 9. First, when one or more connection servers are online (step S01) or one or more connections. When the IP or Port of the line server is changed (step S02), the connection server needs to connect to the management server via the Internet, and sends the server login information to the management server (step S03). The management server verifies whether the content of the server login information is legal in the server list (step S04). If the verification is successful, it means that the connection server is indeed a legitimate server in the server list, according to the servo. The server login information updates the server list (step S05), and the management server replies with the login success message (step S06), the connection server receives the reply message (step S07), and in order to ensure that the management server can store the connection The latest state of the line server group will repeat the step S03 to resend the server login information every time a predetermined time elapses (step S09). If it is verified in step S04 that the server login information is failed, it means that the connection server is not in the server list, and is an illegal connection server, and also replies with the login failure message (step S08), and the connection server is connected. The reply message is received (step S07).

Next, FIG. 10 shows a process in which the remote device and the management server are connected to request to reply to the connection server. First, the remote device sends a message asking the server address (step S11), the management server verifies whether the message sent by the remote device is valid (step S12), and if the verification is successful, the management server replies with a connection. The address of the server is given to the remote device (step S13); if the verification fails, the management server replies with a reject request message to the remote device (step S14). Then, the remote device needs to be connected to the connection server that the management server replies. The remote device sends the login message of the remote device (step S15), the connection server group receives the login message (step S16), and then the connection server replies with a response message to the remote device (step S17). ). Therefore, the connection server can know the IP address of the remote device to contact the necessary information of the remote device. In order to ensure that the connection server can find the remote device, after each predetermined time (which can be preset every 10 minutes), the remote device needs to return to step S11 to re-send its own information message (step S18). So that the connection server can obtain the update status of the remote device from time to time. Moreover, the remote device can re-interrogate the management server every time (for example, every 24 hours can be preset) (step S19), so that the management server provides the latest connection server address setting information.

Finally, the process of requesting the near-end device to connect to the remote device can be seen in FIG. 11. The user specifies a remote device through an application interface program (API) of the near-end device, and the near-end device passes the application interface program ( The API) submits a request for finding the designated remote device to the management server (step S21), and the management server returns the address of the connection server that the remote device logs in to the near-end device (step S22), so The near-end device can obtain a connection to which connection server to find the designated remote device. Then, the near-end device requests the connection server to connect to the remote device (step S23), and the connection server preferentially selects a hole punching process for the near-end device and the remote device (step S24), if If successful, the near-end device and the remote device may perform point-to-point transmission (step S25); if it fails, the data packet of the near-end device and the remote device is forwarded through the connection server (step S26).

Through the foregoing technology, the remote device and the connection server do not need to directly expose their IP address or Domain name to reduce the risk of being invaded by the hacker. Similarly, the near-end device does not need to have a fixed IP, nor does it need to memorize a fixed IP address or a domain name. The management server can be used to query the connection server to which the specific remote device belongs. Therefore, the near-end device only needs to have an application programming interface (API) supported by the management server to request the management server to query the connection address, and the user only needs to select one of the remote devices. The program that communicates with the management server and the connection server can be automatically processed by the application interface program to greatly simplify the complexity of the user operation. Moreover, the system allows the number, specifications, and categories of the remote device and the connection server to be expanded and changed according to requirements, and only needs to log in to the management server to update the server list and device list. The manufacturer of the connection server or remote device can vary depending on the amount of equipment load. The aforementioned remote device may be a security alarm system, such as a surveillance photographic equipment, an alarm, a smoke fire alarm, etc.; or an electrical appliance such as a refrigerator, an air conditioner, or the like. Furthermore, the near-end device should have audio and video playback functions, such as a mobile phone with audio and video playback capabilities, a computer, a personal digital assistant (PDA), and the like.

In one example, a communication system for establishing a P2P connection is disclosed, the communication system includes a network device or a service device having an identification code, and at least one connection server provides connection information to enable the terminal device or the client device. Establishing a P2P connection with the network device or the service device, the identification code of the service device is at least logged into a connection server, and the client device and the at least one according to the connection information provided by the at least one connection server The connection server communicates to establish a P2P connection with the service device, and when the P2P connection is established, the client device does not log in to the connection server.

Please note that at the first P2P connection establishment, the client device does not need an identification code. It is different from the existing technology in that the existing technology has to log in to the server in order to establish a P2P connection client device.

In one example, the functions of the management server and the connection server can be integrated into a single connection server, and the service device can log in its UID to the connection server, and the client device can connect to the server. Communication establishes a P2P connection between the client device and the service device. As long as the client device has the UID identification code of the service device, the client device can connect with the server to enable the server and the client device to complete the P2P connection by themselves, wherein the client device does not need to have its own UID. The number of servers required depends on the network size of the service client and the service device.

In one example, in addition to managing the server group and the connection server group, adding a rear management server group to detect any failed management server and/or connection server and executing the management server And / or load balancing of the connection server. For example, if one management server fails, the latter server can detect such a condition and forward the request to the failed management server to another management server. Similarly, if a management server or connection server is overloaded, the rear server can detect such a condition and forward a portion of the request to the overloaded server to another server to complete the balance.

In one example, API modules can be integrated on different platforms. FIG. 12 shows an Internet of Things Cross-platform (IOTC) 1200 in an example of the present invention. Through the IOTC platform 1210, different APIs (Application Programming Interfaces) 1201, 1202, 1203, 1204, 1205, 1206 can request P2P services to establish P2P connections, thereby providing use of different processors such as: ARM, X86, MIPS, etc. A unified integration plan across platforms. A cross-platform unified integration solution can use different operating systems, such as: Windows, Linux, IOS, Android, etc. In addition, the IOTC platform 1210 can have a network layer 1220 to communicate with another IOTC platform, and a sensing layer or device layer 1230 to connect to other devices, such as IP cam, RFID, and the like.

With the rapid advancement of integrated circuit technology, more and more designs can be integrated into one IC. By doing so, not only can the cost be saved, but also the plug-and-play can be achieved through the P2P connection. Fig. 13A shows a block diagram 1300 of an integrated circuit in an example of the present invention. The integrated circuit 1300 includes a CPU 1301 or a processor, and an IOTC API module 1303 for establishing a connection with a predetermined remote device. The IOTC API module 1303 includes a plurality of instructions. When the processor executes a plurality of instructions, the management server is requested to provide address information of a connection server that has logged into a predetermined remote device. Based on the address information of the connection server provided by the management server, the IOTC module 1303 requests the connection server to establish a P2P connection between the integrated circuit and the predetermined remote device.

In an example, as shown in FIG. 13B, the integrated circuit 1350 has an IOTC API module 1303, an operating system module 1304, and a network working module 1305.

In one example, as shown in FIG. 13C, the integrated circuit 1360 has a UID module 1302, an IOTC API module 1303, an operating system module 1304, and a network working module 1305. The UID module 1302 performs a login procedure to log an electronic device including the integrated circuit 1360 to the management server and the connection server to enable other electronic devices to establish a P2P connection with the electronic device.

In one example, as shown in FIG. 13D, the integrated circuit 1370 has a browser or application module 1306, an IOTC API module 1303, an operating system module 1304, and a network working module 1305. The browser or application module 1306 can establish a P2P connection with the remote device through the API module.

Please note that the API module, operating system module and network working module or CPU can be packaged in the same electronic device, such as IP camera, mobile device or storage device. The CPU and API modules can also be packaged into two or more integrated circuits. The description of the previous integrated circuit can also be used for electronic devices and will not be further described.

Figure 14A is a block diagram showing two connected devices of a P2P connection established by a management server and a connection server, one of which is a client device 1400 and the other is a remote service device 1410. The client device 1400 can be integrated in an integrated circuit or packaged in an electronic device, and the remote service device 1410 can be integrated in an integrated circuit or packaged in an electronic device. As shown in FIG. 14A, the remote service device 1410 has a CPU 1411, a UID module 1412, an IOTC API module 1413, an operating system module 1414, and a network working module 1415. The UID module 1412 performs a login procedure to log the remote service device 1410 into the management server and the connection server to enable the client device 1400 to establish a P2P connection with the remote service device 1410. The client device 1400 has a CPU 1401, a browser or application module 1402, an IOTC API module 1403, an operating system module 1404, and a network working module 1405. The browser or application module 1402 can establish a P2P connection with the remote service device 1410 through the API module.

As described in U.S. Application Serial No. 61/812,262, an image sensor can read a pattern such as a one-dimensional bar code or QR code for identification of an input terminal device, a client device, a network device, or an electronic device. Code information, the input identification code information can be used to establish a P2P connection. Please note that a mobile device can also input identification code information through the input device of the mobile device, such as an image sensor, a keyboard, a touch panel, etc., and transmit it to other terminal devices or electronic devices.

In one example, a block diagram of two connected devices of a P2P connection established by a management server and a connection server is shown in FIG. 14B, one of which is a client device 1400 and the other is a service device 1410. As shown in FIG. 14B, the service device 1410 has a CPU 1411, a UID module 1412, an IOTC API module 1413, an operating system module 1414, and a network working module 1415. The UID module 1412 executes a login procedure to cause the service device 1410 to log into the management server and the connection server to establish a P2P connection between the client device 1400 and the service device 1410. The UID module 1412 inputs, for example, a one-dimensional barcode or QR code pattern to input the identification code information of the service device 1410, so that the login program can use the input identification code information to log the service device 1410 to the management server and the connection servo. Device. The client device 1400 has a CPU 1401, a UID input module 1406 for inputting service device identification code information, an IOTC API module 1403, an operating system module 1404, and a network working module 1405. For example, the UID input module 1406 inputs the identification code information of the service device 1410 in order to establish a P2P connection with the service device 1410 through the IOTC API module 1403.

In one example, the UID is embedded in a processor and the UID can be stored in a non-volatile memory embedded in the processor, such as a flash memory or EEPROM. The UID is programmed into a non-volatile memory embedded in the processor after the processor is tested and used to establish a point-to-point connection.

As shown in FIG. 15, a processor 1500 is integrated with the UID, which is programmed into the processor when the processor 1500 is manufactured and then tested. This approach is simpler and less time consuming than programming the UID into the processor after the processor has been integrated into a board or system, since complex programming is not required to program the UID on the board or system. This approach also does not require additional flash memory or EEPROM to store the UID to save space. In addition, a portion of the pins of processor 1500 can be shared to program the UID into processor 1500 such that once the identification code is programmed into processor 1500, the shared pins will be dedicated to other uses. For example, the processor 1500 has a multiplexer. When the identification code is programmed to the processor 1500, the multiplexer connects a set of pins to the flash memory; the processor 1500 performs normal In operation, the multiplexer connects the set of pins to another portion of the circuitry of the processor 1500 for normal operation.

In one example, as shown in FIG. 16, each processor 1600 has a plurality of pins 1601, a CPU 1602, and a sequence number 1603 to identify the processor 1600 and an identification code 1604 for establishing a P2P connection. In an example, the serial number of the CPU is used as an identification code to establish a P2P connection. In an example, the serial number and the identification code are simultaneously programmed into the CPU.

In one embodiment, the present invention relates to an integration of an information concentrating center and P2P technology such that a remote client device can establish a P2P connection with an information aggregation center to obtain services provided by the information aggregation center.

Traditionally, when a remote client device attempts to connect to an information concentrating center located at home via the Internet, it needs to include very complex procedures such as DDNS (Dynamic DNS) and port mapping to establish distance from the Internet. The connection of the client device to the information aggregation center. Today, UPnP's port forwarding technology simplifies the setup process from remote client devices to information aggregation. However, when a multi-layer router exists in a path from a remote client device to an information aggregation center, the UPnP port forwarding technology has security and operational problems.

Traditionally, Video On Demand (VOD) technology uses a centralized server for storing content such as video/audio information so that users can view the content in different places over the Internet. However, video on demand technology has some drawbacks, such as the high cost of the central server and the bandwidth limitations associated with the central server. In addition, video on demand operators need to pay a substantial license fee to obtain such content. By using a P2P connection between the remote client device and the information aggregation center, users in different locations can view various content over the Internet in a distributed manner to address the bandwidth issues associated with the central server. In addition, by using P2P to connect remote client devices and information aggregation centers, bandwidth and hardware requirements are significantly lower than video on demand technology, while bandwidth and hardware costs are paid by each user.

In order to solve the above problem of establishing a connection between a remote client device through an internetwork and an information aggregation center, the present invention discloses a peer-to-peer (P2P) connection method through the Internet to establish a remote client device to information. The connection to the aggregation center. By using a point-to-point (P2P) connection between the remote client device and the information aggregation center, it is possible to establish a service such as a video streaming conference or check the status of the home appliance provided by the information aggregation center, or from a remote client. The device transmits, for example, two-way communication of switching control information of the television channel to the information aggregation center.

Please refer to FIG. 17, which illustrates a system diagram of an information aggregation center connected to a remote client device using a point-to-point connection according to an embodiment of the present invention. An information source 1701 is coupled to the information aggregation center 1702 to provide any source of information. For example, the information source 1701 can be a television program that is fed via satellite or cable. A first local client device 1703, such as a TV, can be connected to the information aggregation center 1702. Additionally, digital information, such as high definition television programming, may be transmitted from the information aggregation center 1702 to a second local client device 1705, such as a TV, mobile phone, tablet, notebook, or personal computer, via router 1704 or home network. For example, users can use a mobile phone to receive TV shows via a router and wireless signals, such as WIFI, even in a home's backyard. Moreover, when the user leaves home, such as when the user is on vacation, the user can establish a peer-to-peer (P2P) connection 1708 with the information aggregation center 1702 via the router 1704 and the Internet 1707 using the remote client device 1706, such as a mobile phone.

In one embodiment, the information source 1701 includes at least one source of information that is desirably used by the Internet to provide information to the information gathering center 1702, such as a television program or other information fed through a satellite feed or cable. In one embodiment, the information aggregation center 1702 includes a formatting module to convert the information format into a format suitable for viewing by the remote client device 1706.

In one embodiment, FIG. 18 illustrates a plurality of devices for connecting to an information gathering center, for example, a set-top box 1730 is used as a service device for providing information to a client device such as a television set 1731, wherein A source of information, such as satellite and/or cable feed 1732, is coupled to set-top box 1730 to provide television programming or other information. A remote client device 1706, such as a mobile phone, PAD, laptop or other electronic device, can be connected to the set-top box 1730 using a point-to-point (P2P) connection 1708 through router 1704 and the Internet 1707. At home, some home appliances 1733 can be connected to the set-top box 1730 through the router 1704, so that the remote client device 1706, such as a mobile phone, PAD, notebook computer or other electronic device, can check the home appliance 1733 through the set-top box 1730. Or send a command to the set-top box 1730 to control the home appliance 1733. Additionally, a local client device 1705, such as a mobile phone, PAD, laptop, or other electronic device, can view television programming via router 1704 using wired or wireless transmission.

A home device such as an information aggregation center can register its UID (Unique Identification Code) to a linking server as described in U.S. Patent Application Serial No. 13/293,506 and U.S. Patent Application Serial No. 13/950,281. The remote client device can then communicate with the connection server to establish a P2P connection from the remote client device to the information aggregation center. As long as the client device has the UID of the information aggregation center, the remote client device can contact the connection server to establish a P2P connection from the remote client device to the information aggregation center.

19 shows a connection server 1750 connected to the Internet 1704 for establishing a P2P connection 1708 from the remote client device 1706 to an information aggregation center such as the set-top box 1730. The set-top box 1730 has a unique identification code (UID) module 1760 that can communicate directly with the connection server 1750, or indirectly through the management server to obtain the address of the connection server 1750, and then communicate with the connection server 1750. So that the set-top box 1730 can register the unique identification code (UID) in the connection server 1750. Thereafter, the remote client device 1706, such as a mobile phone, PAD, laptop or other electronic device, can communicate directly with the connection server 1750, or indirectly through the management server to obtain the address of the connection server 1750. The connection server 1750 communicates to establish a P2P connection 1708 from the remote client device 1706 to the set-top box 1730.

This approach is fast and requires complex procedures to establish P2P connections. In addition, the bandwidth used for P2P connections is Scalable, because each home user can establish a P2P connection to a set-top box in his/her own home in a distributed manner. Such as the video bandwidth (VoD) technology bandwidth (Bandwidth) problem.

In one embodiment, the image sensor can capture a pattern such as a one-dimensional barcode or QR code to produce an image for input, as described in US Patent Application No. 13/293,506 and U.S. Patent Application Serial No. 13/950,281. The UID of the information aggregation center establishes a P2P connection from the remote client device to the information aggregation center.

It is noted that all descriptions of U.S. Patent Application No. 13/293,506 and U.S. Patent Application Serial No. 13/950,281, may be incorporated in whole or in part with an information gathering center for establishing and remote client devices, such as mobile phones, notebook computers, P2P connection between personal computer, PAD or other suitable electronic device.

In one embodiment, the information aggregation center has a first unique identification code (UID) registered in the at least one connection server, wherein the remote client device aggregates the first unique identification code according to the information aggregation center (UID), contact the at least one connection server to establish a P2P connection with the information aggregation center.

In one embodiment, when the remote client device contacts the at least one connection server to establish a connection with the P2P in the information set, the remote client device does not register a second in the at least one connection server. Unique identification number (UID).

In one embodiment, when the remote client device sends a first message to establish a P2P connection with the information aggregation center to the connection server, the remote client device does not have a registration to the connection. One of the unique identification codes (UIDs) of the server.

In one embodiment, the connection server sends a hole punch message to the information aggregation center and the remote client device to establish a P2P connection.

In an embodiment, a unique identifier (UID) is embedded in the manufactured information aggregation center when the information aggregation is manufactured, wherein the unique identification code (UID) of the information aggregation center is generated, and the network is not used. Road address information, such as an IP address. Similarly, the second unique identification code (UID) described above does not include network address information, such as an IP address.

Note that there are many ways to establish a P2P connection from a remote client device to an information aggregation center over the Internet. The present invention is not limited to the manner of establishing a P2P connection, as long as the P2P connection is used to connect the information aggregation center and the remote client device are the scope of protection of the present invention.

Although the present invention has been disclosed above in the preferred embodiment, it is not intended to limit the present invention. Anyone who is familiar with this skill and does not deviate from the spirit and scope of this case, and some of the changes and refinements should be covered in this case. Therefore, the scope of protection of this case shall be subject to the definition of the scope of the patent application attached. In summary, this case enhances the above-mentioned effects compared with the well-known creations. It should fully comply with the novelty and progressive statutory innovation patent requirements. If you apply in accordance with the law, you are requested to approve the invention patent application. Feeling the virtues.

1‧‧‧Manage server group
4‧‧‧ Near-end equipment
11, 12, 13‧‧‧Management Server
20‧‧‧Connection Server Group A
21‧‧‧Connection Server Group B
22‧‧‧Connected Server Group C
23‧‧‧Connected Server Group D
24‧‧‧Connection Server Group E
31‧‧‧ Remote Device A
32‧‧‧Remote device B
33‧‧‧Remote device C
34‧‧‧Remote device D
91‧‧‧Query information
92‧‧‧ Login Information
93‧‧‧ Remote Device A Connection Request Information Connection Server Group A
94‧‧‧Contact information
95‧‧‧Connection request information
97‧‧‧ Point-to-point transmission connection
98‧‧‧ Near-end device connection request information connection server group A
99‧‧‧ Remote Device A Connection Request Information Connection Server Group A
201, 202, 211, 212, 213, 221, 222, 223, 231, 232, 241, 242‧‧ ‧ connection server
960, 961‧‧‧ hole connection message
1200‧‧‧Internet of Things Cross-Platform Architecture (IOTC)
1201, 1202, 1203, 1204, 1205, 1206‧‧‧ application interface
1210‧‧‧IoT Cross-Platform Architecture (IOTC) Platform
1220‧‧‧Network layer
1230‧‧‧Sensor or device layer
1300, 1350, 1360, 1370‧‧‧ integrated circuits
1301, 1401, 1411, 1602‧‧‧ CPU
1303, 1403, 1413‧‧‧IoT Cross-Platform Architecture (IOTC) Application Interface Module
1304, 1404, 1414‧‧‧ operating system modules
1305, 1405, 1415‧‧‧ network working modules
1302, 1412 UID‧‧‧ modules
1306, 1402‧‧‧ browser or application module
1400‧‧‧ client device
1410‧‧‧ Remote service unit
1406‧‧‧UID input module for inputting service device identification code information
1500, 1600, 1703‧‧ ‧ processors
1601‧‧‧ pins
1603‧‧‧Ordinary number
1604‧‧‧ID
1701‧‧‧Information source
1702‧‧‧Information gathering center
1703‧‧‧First local client device
1704‧‧‧ router
1705‧‧‧Second local client device
1706‧‧‧Remote client device
1707‧‧‧Internet
1708‧‧‧Peer-to-Peer (P2P) connection
1730‧‧‧Set-top box
1731‧‧‧TV
1732‧‧‧ Satellite or cable feed
1733‧‧‧Home Appliances
1750‧‧‧Connected server,
1760‧‧‧UID module

1701‧‧‧Information source

1702‧‧‧Information gathering center

1703‧‧‧First local client device

1704‧‧‧ router

1705‧‧‧Second local client device

1706‧‧‧Remote client device

1707‧‧‧Internet

1708‧‧‧ Point-to-point (P2P) connection

Claims (20)

An information aggregation center includes: at least one first module for collecting information from at least one information source; and at least one second module coupled to the Internet for establishing a pass with a remote client device A point-to-point (P2P) connection of the Internet, wherein at least a portion of the information is transmitted by the P2P connection to the remote client device. The information aggregation center described in item 1 of the patent application scope is a Set Top Box. The information gathering center of claim 1, wherein the remote client device is a portable electronic device. The information aggregation center of claim 1, wherein the remote client device is a mobile phone. The information aggregation center according to claim 1, wherein the information aggregation center has a first unique identification code (UID), and the first unique identification code (UID) is registered in at least one connection server. Correlating the connection information of the aggregation center, wherein the remote client device communicates with the at least one connection server and establishes the P2P connection according to the connection information provided by the at least one connection server, wherein When the P2P is established, the remote client device is not registered in the at least one connection server. The information aggregation center according to claim 1, wherein the at least one second module is connected to the Internet through an external router or an internal router. The information gathering center of claim 1, wherein the information source is a satellite feed containing a television program. The information gathering center of claim 1, wherein the information source is a cable feed containing a television program. The information aggregation center of claim 7, wherein the remote client device sends a command to the information aggregation center to switch the television channel of the television program. The information aggregation center of claim 8, wherein the remote client device sends a command to the information aggregation center to switch the television channel of the television program. The information gathering center of claim 1, wherein the at least one information source comprises a satellite feed and a cable feed. For example, the information aggregation center described in claim 6 wherein the router is an IP router. The information gathering center according to claim 6, wherein the information gathering center is connected to an electric appliance through a router, and the remote client device controls the home appliance through the information gathering center. The information aggregation center of claim 6, wherein the router has a wireless access point for connecting to a portable electronic device to transmit the information to the portable electronic device. The information aggregation center as described in claim 1 further includes: a formatting module to convert the information into a format suitable for viewing by a remote client device. The information aggregation center according to claim 1, wherein the information aggregation center has a first unique identification code (UID), and the first unique identification code (UID) is registered in at least one connection server. To associate the connection information of the aggregation center, wherein the remote client device contacts the at least one connection server according to the first unique identification code (UID) of the information aggregation center to indicate the connection information of the information aggregation center. The information aggregation center of claim 16, wherein the remote client device does not have a register for the at least one connection server when contacting the at least one connection server. A unique identification number (UID) associated with the connection information of the remote client device. The information aggregation center of claim 5, wherein the at least one connection server transmits hole-punching messages to the information aggregation center and the remote client device to establish the P2P connection. A home appliance includes: at least one module coupled to an information gathering center, wherein a P2P connection is established between the information gathering center and a remote client device, wherein the remote client device passes the P2P Wired to connect to the information gathering center to control the home appliance. The home appliance of claim 19, wherein the information gathering center has a first unique identification code (UID), and the first unique identification code (UID) is registered in at least one connection server. Correlating connection information of the aggregation center, wherein the remote client device communicates with the at least one connection server and establishes the P2P connection according to the connection information provided by the at least one connection server, where When the P2P is established, the remote client device is not registered in the at least one connection server.