METHODS AND DEVICES FOR PROCESSING MESSAGES OF IPTV

• US 20170055037A1
• Filed: 08/05/2014
• Published: 02/23/2017
• Est. Priority Date: 04/22/2014
• Status: Abandoned Application

• Current Assignee: ZTE Corporation
• Original Assignee: ZTE Corporation
• Inventors: FEI, Lihua, XIE, Shizhao
• Application Number:
  US15/305,297
• Publication Number:
  US 20170055037A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04N 21/26291 for providing content or additional data updates, e.g. updating software modules, stored at the client deployment, distribution, installation, update of software G06F8/65; error detection or correction during software upgrading G06F11/1433; arrangements for updating broadcast information or broadcast-related information H04H60/25
• CPC Class Codes: H04N 21/431 Generation of visual interfaces for content selection or interaction; Content or additional data rendering
• CPC Class Codes: H04N 21/435 Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
• CPC Class Codes: H04N 21/4586 Content update operation triggered locally, e.g. by comparing the version of software modules in a DVB carousel to the version stored locally deployment, distribution, installation, update of software G06F8/65; error detection or correction of the data by redundancy during software upgrading G06F11/1433; arrangements for updating broadcast information or broadcast-related information H04H60/25
• CPC Class Codes: H04N 21/4622 Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet web site content organization and management for information retrieval from the Internet G06F16/958; transmission by internet of broadcast information H04H60/82; stock exchange data over packet-switching network H04L12/1804; push services including data channel over packet-switching network H04L12/1859
• CPC Class Codes: H04N 21/4821 using a grid, e.g. sorted out by channel and broadcast time
• CPC Class Codes: H04N 21/64322 IP
• CPC Class Codes: H04N 21/8543 using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML] information retrieval of semistructured data, the underlying structure being taken into account, e.g. mark-up language structure data G06F16/80

Abstract

Provided are a method and device for processing messages of IPTV. The method includes: acquiring multiple EPG versions which simultaneously exist; acquiring one or more corresponding view types according to the multiple EPG versions, wherein a group of EPG versions to be processed in a same manner are set to collectively correspond to one view type; and processing request messages of the multiple EPG versions according to the one or more view types. By means of the solution, the problem in the relevant art that services cannot be processed normally due to the service upgrade in batches of the IPTV is solved, thereby providing a technical basis for achieving the service upgrade of an IPTV system in batches, so that the losses of benefits and operation of an operator caused by the upgrade can be decreased and reduced to the maximum extent, and a favorable service experiences are ensured for users.

Claims

1. A method for processing messages of Internet Protocol Television or Interactive Personal Television (IPTV), comprising:

acquiring multiple Electronic Program Guide (EPG) versions which simultaneously exist;

acquiring one or more corresponding view types according to the multiple EPG versions, wherein a group of EPG versions to be processed in a same manner are set to collectively correspond to one view type; and

processing request messages of the multiple EPG versions according to the one or more corresponding view types.

2. The method of claim 1, before acquiring the one or more corresponding view types according to the multiple EPG versions, further comprising:

setting one or more EPG versions, which have a same number of table fields and have table structures in which a same field has a same length, to collectively correspond to one view type.

3. The method of claim 2, after setting the one or more EPG versions, which have the same number of table fields and have the table structures in which the same field has the same length, to collectively correspond to one view type, further comprising:

storing, into a control point, a corresponding relation between the one or more EPG versions, which have the same number of table fields and have the table structures in which the same field has the same length, and the view type corresponding to the one or more EPG versions.

4. The method of claim 1, wherein acquiring the one or more corresponding view types according to the multiple EPG versions comprises:

determining the one or more corresponding view types according to the multiple EPG versions;

reading the one or more corresponding view types from a service database.

5. The method of claim 1, before processing the request messages of the multiple EPG versions according to the one or more corresponding view types, further comprising:

acquiring a corresponding interface type of current request messages;

judging, based on the interface type, whether to process request messages of the multiple EPG versions according to the one or more corresponding view types.

6. The method of claim 5, wherein judging, based on the interface type, whether to process request messages of the multiple EPG versions according to the one or more corresponding view types comprises at least one of:

in the case that the interface type is a File Transfer Protocol (FTP) interface, processing the request messages of the multiple EPG versions according to the one or more corresponding view types;

in the case that the interface type is a Transmission Control Protocol (TCP) interface and/or a JavaScript Object Notation (JSON) interface, processing the request messages of the multiple EPG versions directly;

in the case that the interface type is a Hypertext Transfer Protocol (HTTP) and/or an Extensible Markup Language (XML) interface, converting a type of the request messages into JSON type and process the request messages of the multiple EPG versions directly.

13. The method of claim 2, wherein acquiring the one or more corresponding view types according to the multiple EPG versions comprises:

determining the one or more corresponding view types according to the multiple EPG versions;

reading the one or more corresponding view types from a service database.

14. The method of claim 3, wherein acquiring the one or more corresponding view types according to the multiple EPG versions comprises:

determining the one or more corresponding view types according to the multiple EPG versions;

reading the one or more corresponding view types from a service database.

15. The method of claim 2, before processing the request messages of the multiple EPG versions according to the one or more corresponding view types, further comprising:

acquiring a corresponding interface type of current request messages;

judging, based on the interface type, whether to process request messages of the multiple EPG versions according to the one or more corresponding view types.

16. The method of claim 3, before processing the request messages of the multiple EPG versions according to the one or more corresponding view types, further comprising:

acquiring a corresponding interface type of current request messages;

judging, based on the interface type, whether to process request messages of the multiple EPG versions according to the one or more corresponding view types.

17. The method of claim 15, wherein judging, based on the interface type, whether to process request messages of the multiple EPG versions according to the one or more corresponding view types comprises at least one of:

in the case that the interface type is a File Transfer Protocol (FTP) interface, processing the request messages of the multiple EPG versions according to the one or more corresponding view types;

in the case that the interface type is a Transmission Control Protocol (TCP) interface and/or a JavaScript Object Notation (JSON) interface, processing the request messages of the multiple EPG versions directly;

in the case that the interface type is a Hypertext Transfer Protocol (HTTP) and/or an Extensible Markup Language (XML) interface, converting a type of the request messages into JSON type and process the request messages of the multiple EPG versions directly.

18. The method of claim 16, wherein judging, based on the interface type, whether to process request messages of the multiple EPG versions according to the one or more corresponding view types comprises at least one of:

in the case that the interface type is a File Transfer Protocol (FTP) interface, processing the request messages of the multiple EPG versions according to the one or more corresponding view types;

in the case that the interface type is a Transmission Control Protocol (TCP) interface and/or a JavaScript Object Notation (JSON) interface, processing the request messages of the multiple EPG versions directly;

in the case that the interface type is a Hypertext Transfer Protocol (HTTP) and/or an Extensible Markup Language (XML) interface, converting a type of the request messages into JSON type and process the request messages of the multiple EPG versions directly.

7. A device for processing messages of Internet Protocol Television or Interactive Personal Television (IPTV), comprising:

a first acquiring component, configured to acquire multiple Electronic Program Guide (EPG) versions which simultaneously exist;

a second acquiring component, configured to acquire one or more corresponding view types according to the multiple EPG versions, wherein a group of EPG versions to be processed in a same manner are set to collectively correspond to one view type;

a processing component, configured to process request messages of the multiple EPG versions according to the one or more corresponding view types.

8. The device of claim 7, the device further comprising:

a classifying component, configured to set one or more EPG versions, which have a same number of table fields and have table structures in which a same field has a same length, to collectively correspond to one view type.

9. The device of claim 8, the device further comprising:

a storing component, configured to store, into a control point, a corresponding relation between the one or more EPG versions, which have the same number of table fields and have the table structures in which the same field has the same length, and the view type corresponding to the one or more EPG versions.

10. The device of claim 7, wherein the second acquiring component comprises:

a determining element, configured to determine the one or more corresponding view types according to the multiple EPG versions;

a reading element, configured to read the one or more corresponding view types from a service database.

11. The device of claim 7, the device further comprising:

a third acquiring component, configured to acquire a corresponding interface type of current request messages;

a judging component, configured to judge, based on the interface type, whether to process request messages of the multiple EPG versions according to the one or more corresponding view types.

12. The device of claim 11, wherein the judging component comprises at least one of the following elements:

a first processing element, configured to, in the case that the interface type is a File Transfer Protocol (FTP) interface, process the request messages of the multiple EPG versions according to the one or more corresponding view types;

a second processing element, configured to, in the case that the interface type is a Transmission Control Protocol (TCP) interface and/or a JavaScript Object Notation (JSON) interface, process the request messages of the multiple EPG versions directly;

a third processing element, configured to, in the case that the interface type is a Hypertext Transfer Protocol (HTTP) and/or an Extensible Markup Language (XML) interface, convert a type of the request messages into JSON type and process the request messages of the multiple EPG versions directly.

19. The device of claim 8, the device further comprising:

a third acquiring component, configured to acquire a corresponding interface type of current request messages;

a judging component, configured to judge, based on the interface type, whether to process request messages of the multiple EPG versions according to the one or more corresponding view types.

20. The device of claim 19, wherein the judging component comprises at least one of the following elements:

a first processing element, configured to, in the case that the interface type is a File Transfer Protocol (FTP) interface, process the request messages of the multiple EPG versions according to the one or more corresponding view types;

a second processing element, configured to, in the case that the interface type is a Transmission Control Protocol (TCP) interface and/or a JavaScript Object Notation (JSON) interface, process the request messages of the multiple EPG versions directly;

a third processing element, configured to, in the case that the interface type is a Hypertext Transfer Protocol (HTTP) and/or an Extensible Markup Language (XML) interface, convert a type of the request messages into JSON type and process the request messages of the multiple EPG versions directly.