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; 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; 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; 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. 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; 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; 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; 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. 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; 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. 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.