CN111031370A - 一种融合网关部分和机顶盒部分相互通讯的方法 - Google Patents
一种融合网关部分和机顶盒部分相互通讯的方法 Download PDFInfo
- Publication number
- CN111031370A CN111031370A CN201911276978.XA CN201911276978A CN111031370A CN 111031370 A CN111031370 A CN 111031370A CN 201911276978 A CN201911276978 A CN 201911276978A CN 111031370 A CN111031370 A CN 111031370A
- Authority
- CN
- China
- Prior art keywords
- top box
- status
- communication system
- cmdtype
- parameter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/4104—Peripherals receiving signals from specially adapted client devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/426—Internal components of the client ; Characteristics thereof
- H04N21/42607—Internal components of the client ; Characteristics thereof for processing the incoming bitstream
- H04N21/42623—Internal components of the client ; Characteristics thereof for processing the incoming bitstream involving specific decryption arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/81—Monomedia components thereof
- H04N21/8166—Monomedia components thereof involving executable data, e.g. software
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Software Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明公开了一种融合网关部分和机顶盒部分相互通讯的方法,包括以下步骤:融合网关通信系统可对接收的信息进行解密操作,且所述融合网关通信系统可对发送的信息进行加密操作;机顶盒通信系统可对接收的信息进行解密操作,且所述机顶盒通信系统可对发送的信息进行加密操作;提供一供所述融合网关通信系统和所述机顶盒通信系统进行信息交互的通信规范;所述融合网关通信系统与所述机顶盒通信系统通过该通信协议进行数据交互。本发明通过自定义的二层管理协议和报文处理方式,为融合网关开发提供技术规范,在不改变现有软件架构的条件下,使后期的功能扩展开发更加方便容易,提高了设计开发的灵活性。
Description
技术领域
本发明属于融合网关技术领域,具体涉及一种融合网关部分和机顶盒部分相互通讯的方法。
背景技术
为了满足酒店,商铺和政府公共服务机构等场所用户高速上网,移动终端接入和视频点播的需求,经常会要求部署多个接入终端,由此会带来布线困难,故障点多,成本高的问题。融合网关准确定位于酒店类需要接入多个终端用户,将网关和机顶盒融合,实现了维护架构上实行管道和业务隔离维护的机制,上层设备无需变动,平滑部署。通过零配置、预部署,安装环节自动化,提升装机效率,避免二次上门,实现维护智能化、诊断远程化和一站式开通。一定程度上降低运维复杂度和难度,以及设备成本。
然而,在现今的技术条件和实现方面,还难以做到真正的融合。目前市面上的融合网关芯片供应商,基本没有将几个功能集成到一个SOC。所以,推出融合网关设备时,往往是将网关模块和机顶盒通信系统通过硬件接口相连接,而每个模块依然是各自独立的软件系统。这样,机顶盒不能设置查看网关运行状况,也不能对网关进行设置,网关对于机顶盒也同样如此。但是,在进行装机开通以及日常使用时,我们往往希望他们是一个“整体”,不必采用复杂的方式对他们进行查看与设置。另外,从机顶盒管理平台及网关管理平台管理融合设备也希望能够整体管理。
因此,现阶段需要提供一种融合网关部分和机顶盒部分相互通讯的方法。
发明内容
本发明目的在于提供一种融合网关部分和机顶盒部分相互通讯的方法,用于解决现有技术中存在的技术问题,比如:在现今的技术条件和实现方面,还难以做到真正的融合。目前市面上的融合网关芯片供应商,基本没有将几个功能集成到一个SOC。所以,推出融合网关设备时,往往是将网关模块和机顶盒通信系统通过硬件接口相连接,而每个模块依然是各自独立的软件系统。这样,机顶盒不能设置查看网关运行状况,也不能对网关进行设置,网关对于机顶盒也同样如此。但是,在进行装机开通以及日常使用时,我们往往希望他们是一个“整体”,不必采用复杂的方式对他们进行查看与设置。另外,从机顶盒管理平台及网关管理平台管理融合设备也希望能够整体管理。
为实现上述目的,本发明所采用的技术方案是:
一种融合网关部分和机顶盒部分相互通讯的方法,包括以下步骤:
S1:提供一融合网关通信系统,所述融合网关通信系统可对接收的信息进行解密操作,且所述融合网关通信系统可对发送的信息进行加密操作;提供一机顶盒通信系统,所述机顶盒通信系统可对接收的信息进行解密操作,且所述机顶盒通信系统可对发送的信息进行加密操作;
S2:在步骤S1的基础上,提供一供所述融合网关通信系统和所述机顶盒通信系统进行信息交互的通信规范;
S3:在步骤S2的基础上,当所述融合网关通信系统接收到所述机顶盒通信系统发送来的经过加密操作的信息时,所述融合网关通信系统可通过所述通信规范对该加密信息进行解密操作,待所述融合网关通信系统完成对该加密信息的读取后,所述融合网关通信系统生成一加密反馈信息并将该加密反馈信息发送至所述机顶盒通信系统,当所述机顶盒通信系统接收到所述融合网关通信系统发送来的加密反馈信息时,所述机顶盒通信系统通过所述通信规范对该加密反馈信息进行解密操作,从而完成对该加密反馈信息的读取;同理,当所述机顶盒通信系统接收到所述融合网关通信系统发送来的经过加密操作的信息时,所述机顶盒通信系统可通过所述通信规范对该加密信息进行解密操作,待所述机顶盒通信系统完成对该加密信息的读取后,所述机顶盒通信系统生成一加密反馈信息并将该加密反馈信息发送至所述融合网关通信系统,当所述融合网关通信系统接收到所述机顶盒通信系统发送来的加密反馈信息时,所述融合网关通信系统通过所述通信规范对该加密反馈信息进行解密操作,从而完成对该加密反馈信息的读取。
优选的,在步骤S3中,当所述机顶盒通信系统向所述融合网关通信系统主动发送信息时,所述通信规范的具体方式为:
融合网关通信系统主动发起协议类型为0x9212;
voidgetIPTVVersion():
获取机顶盒通信系统版本信息:操作系统版本、系统软件版本、各应用软件版本;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"IPTVVERSION"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"IPTVVERSION","Status":"0","OSVersion":"xxxx","SoftwareVersion":"xxxx","appinfo":[{"name":"xxxx","version":"xxxx"},{"name":"xxxx","version":"xxxx"}]}}
Status:调用成功/失败,0成功,1失败;OSVersion:操作系统版本;SoftwareVersion:系统软件版本;appinfo:应用软件信息,name为应用软件名称,version为其对应版本;
voidgetNetInfo():
获取网络信息:机顶盒通信系统的MAC、IP、子网掩码、默认网关、DNS服务器;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"NETINFO"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"NETINFO","Status":"0","DevMac":"xxxx","A4InetAddr":"xxxx","A4Mask":"xxxx","A4DefGateway":"xxxx","A4DNS":"xxxx","A4ALTDNS":"xxxx","A6InetAddr":"xxxx","A6Mask":"xxxx","A6DefGateway":"xxxx","A6DNS":"xxxx","A6ALTDNS":"xxxx",B4InetAddr":"xxxx","B4Mask":"xxxx","B4DefGateway":"xxxx","B4DNS":"xxxx","B4ALTDNS":"xxxx","B6InetAddr":"xxxx","B6Mask":"xxxx","B6DefGateway":"xxxx","B6DNS":"xxxx","B6ALTDNS":"xxxx"}}
Status:调用成功/失败,0成功,1失败;DevMac:机顶盒通信系统MAC;InetAddr:机顶盒通信系统IP;Mask:机顶盒通信系统子网掩码;DefGateway:机顶盒通信系统默认网关;DNS:机顶盒通信系统DNS服务器;ALTDNS:机顶盒通信系统备用DNS服务器;
A4表示A平面Ipv4,A6表示A平面Ipv6,如A4InetAddr表示机顶盒A平面ipv4地址,A6InetAddr表示机顶盒A平面ipv6地址;
B4表示B平面Ipv4,B6表示B平面Ipv6,如B4InetAddr表示机顶盒B平面ipv4地址,B6InetAddr表示机顶盒B平面ipv6地址;
voidgetServerInfo():
获取机顶盒服务器信息:可查看机顶盒终端管理平台地址、NTP地址等;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"SERVERINFO"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"SERVERINFO","Status":"0","PlatformAddr":"xxxx","NTPAddr":"xxxx"}}
Status:调用成功/失败,0成功,1失败;PlatformAddr:机顶盒终端管理平台地址;NTPAddr;NTP地址;
voidHibernateState(int state):
网关主动发送休眠状态,当网关模块休眠时,向机顶盒通信系统发送网关休眠消息,机顶盒接收到后也应进入休眠状态;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"HIBERNATESTATE","STATE":"1"}}
State:表示休眠状态,1休眠,2未休眠;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"HIBERNATESTATE","Status":"0"}}
Status:0机顶盒休眠成功,1机顶盒休眠失败;
voidClearAccount():
网关首次注册成功后,通过本地界面等方式修改宽带识别码且新的宽带识别码在OLT或ITMS+上注册成功,发送此消息,机顶盒通信系统收到消息清空接入账号和业务账号;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"CLEARACCOUNT"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"CLEARACCOUNT","Status":"0"}}
Status:0清空成功,1清空失败;
voidrepAlarmInfo():
□告警状态:包括CPU负载告警、CPU温度告警等;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"ALARMINFO","Info":"SysCPUTempAlarm(x)"}}
SysCPUTempAlarm(x):CPU温度告警,当前温度为x,收到此消息表示连续5分钟CPU温度高于阀值;
SysCPULoadAlarm(x):CPU负载告警,当前占用率为x(如80表示占用率%80),收到此消息表示连续5分钟CPU负载高于阀值;
voidrepwanlinkstate():
网关为lan上行设备时,当上行口状态发生改变时,主动发送上行口连接状态;格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"WANLINKSTATE","STATE":"1"}}
STATE:1:up,连接上;0:down,断开;
voidrepbootinfo():
网关上电启动完成,交互进程启动后,主动发送启动完成消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"BOOTCOMPLETE"}}
voidotherwanupinfo():
OTHER wan connect时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"OTHERWANUP"}}
voidinternetwanupinfo()
Internet wan connect时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"INTERNETWANUP"}}
void OltLinkSuccessInfo():
OLT认证成功时时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"OLTLINKSUCCESS"}}
void devrepwaninfo():
主动上报是否建立OTHER WAN和INTERNET WAN;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"WANINFO","OTHERFLAG":"1","INTERNETFLAG":"1"}}
OTHERFLAG:是否建立OTHER WAN,0:未建立1:已建立;
INTERNETFLAG:是否建立OTHER WAN,0:未建立1:已建立;
void linkstatus():
光纤连接状态变更时,主动上报连接状态;格式
{"RPCMethod":"GET","Parameter":{"CmdType":"PONSTATE","linkDown":"true"}}
linkDown:连接断开:true连接成功:false;
void devRrebootinfo():
网关重启时,主动上报重启消息;格式
{ID:"","RPCMethod":"GET","Parameter":{"CmdType":"DEVREBOOT"}}。
优选的,在步骤S3中,当所述融合网关通信系统向所述机顶盒通信系统主动发送信息时,所述通信规范的具体方式为:
机顶盒通信系统主动发起协议类型为0x9211;
voidHibernateState(int state):
机顶盒主动发送休眠状态,当机顶盒模块休眠和从休眠状态恢复时,向网关模块发送网关休眠消息,网关在机顶盒唤醒时应该唤醒;请求格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"HIBERNATESTATE","STATE":"1"}}
State:表示休眠状态,1休眠,2未休眠;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"HIBERNATESTATE","Status":"0"}}
Status:0操作成功,1操作失败;
voidgetNetConStatus():
网络连接状态:光纤(如:连通、断开、光信号低等)、OLT认证状态、IPTV WAN连接状态(如:未配置、断开、正常等);请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"NETCONSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"NETCONSTATUS","Status":"0","PonStatus":"0","LoidStatus":"0","IPTVRegStatusIPV4":"0","IPTVRegStatusIPV6":"0"}}
Status:0操作成功,1操作失败;
PonStatus:光纤连接状态,0:未连接;1:已连接;2:光信号弱
LoidStatus:OLT认证状态,0:初始状态;1:认证成功;2:LOID无效;3:密码错误;4:LOID冲突;5:光纤未连接;6:认证失败;7:LOID未认证;8:未知状态
IPTVRegStatusIPV4:IPV4 IPTV WAN连接状态;IPTVRegStatusIPV6:IPV4 IPTVWAN连接状态
IPTV WAN状态值,0:未连接;1:连接中;2:已连接;3:未配置
voidgetServiceStatus():
□业务状态:上网业务状态(如:未配置、断开、正常等)、语音业务状态(如:未配置、注册失败、正常等);请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"SERVICESTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"SERVICESTATUS","Status":"0","IPv4info":[{"servicetype":"internet","regstatus":"xxxx"},{"servicetype":"voip","regstatus":"xxxx"}],"IPv6info":[{"servicetype":"internet","regstatus":"xxxx"},{"servicetype":"voip","regstatus":"xxxx"}]}}
Status:0操作成功,1操作失败;
IPv4info:IPv4信息;IPv6info:IPv6信息;
Servicetype:连接类型;internet:上网连接;voip:语音连接;
RegStatus状态值,0:未连接;1:连接中;2:已连接;3:未配置
voidgetPlatformStatus():
平台连接状态:包括ITMS连接状态、智能网关平台连接状态等;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"PLATFORMSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"PLATFORMSTATUS","Status":"0","ITMSRegStatus":"0","SmartGwstatus":[{"platformname":"bss_platform","server":"xxxx","status":"xxxx"},{"platformname":"main_platform","server":"xxxx","status":"xxxx"},{"platformname":"dist_platform","server":"xxxx","status":"xxx"}]}}
Status:0操作成功,1操作失败;
ITMSRegStatus:0:注册成功;1:注册失败;2:未注册;
SmartGwstatus:智能网关平台连接状态;platformname:平台名字,bss_platform:BSS平台;main_platform:主能力平台;dist_platform:分发平台;server:平台地址;status:连接状态;
status:与平台连接状态;返回为GB2132编码中文字符;
voidsetLoidRegisterInfo():
设置逻辑ID账号和密码;请求格式:
{"ID":"","RPCMethod":"SET","Parameter":{"CmdType":"REGISTER","userName":"xxxx","pwd":"xxxx"}}
userName:逻辑ID,当为空或者只设置密码时,userName值为字符串”NULL”;不能缺少该字段;
Pwd:密码,当为空或者只设置逻辑ID时,pwd值为字符串”NULL”;不能缺少该字段;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"REGISTER","Status":"0"}
Status:0操作成功,1操作失败;
voidgetRegisterStat():
按照速影规范;获取注册认证过程和业务开通过程;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"REGISTERINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"REGISTERINFO","Status":"0","registerstat":"xxxxx"}}
Status:0操作成功,1操作失败;
registerstat:注册开通进度;其取值如下:
REGISTER_DEFAULT:初始设备未注册状态;
REGISTER_REGISTED:设备为已注册状态;
REGISTER_TIMEOUT:注册超时失败;
REGISTER_NOMATCH_NOLIMITED STATE=%s:逻辑ID与密码不匹配,剩余尝试次数:%s;
REGISTER_NOMATCH_LIMITED:逻辑ID与密码不匹配,注册失败;
REGISTER_NOACCOUNT_NOLIMITED STATE=%s:密码不存在,剩余尝试次数:%s;
REGISTER_NOUSER_LIMITED:逻辑ID不存在,注册失败;
REGISTER_OLT PROGRESS=%s:正在注册OLT(%s表示百分比,可取20表示正在注册OLT30表示在OLT授权成功,40表示TR069的WAN连接获得IP地址;
REGISTER_OLT_FAIL:在OLT上注册失败;
REGISTER_OK_DOWN_BUSINESS PROGRESS=%s和REGISTER_OK_DOWN_BUSINESSPROGRESS=%s BUSSNAME=%s:注册成功,正在下发业务(进度为%s),%s可取60,99;%s如果为50,表示注册ITMS平台成功,等待下发业务,%s如果为60,表示平台开使下发业务下发的业务名称为(BUSSNAME=%S),可以取”INTERNET”,”VOIP”,”IPTV””OTHER”的组合;
REGISTER_OK SERVICENAME=%s:注册成功,下发业务成功,共下发了XX业务(下发几个业务就提示几个业务);
REGISTER_OK_NOW_REBOOT:注册成功,下发业务成功,网关需要重启,请等待;
REGISTER_POK:注册成功,下发业务失败;
REGISTER_FAIL:注册失败;
voidgetCpuinfo():
获取CPU温度和负载信息,请求格式
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETCPUINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETCPUINFO","Status":"0","CPUTemp":"ON(x)","CPULoad":"ON(x)"}}
Status:0操作成功,1操作失败;
CPUTemp:CPU温度信息,ON表示温度过高,OFF表示关闭报警,x为温度;
CPULoad:CPU负载信息,ON表示负载过高,OFF表示关闭报警,x为负载情况,若80,占用率%80
voidgetBootinfo():
获取网关是否已经开机,请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETBOOTINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETBOOTINFO","State":"BOOTCOMPLETE"}}
回复此消息表示已经开机;
voidgetWanlinkState():
网关为lan上行设备时,获取上行口是否连接;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETWANLINKSTATE"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETWANLINKSTATE","Status":"0","State":"Up"}}
Status:0操作成功,1操作失败;
State:上行口连接状态,Up为已连接,其余未连接;
void getUploaddataIP():
机顶盒需要对网关进行升级时,通过此接口获取网关给定机顶盒IP:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETUPLOADDATAIP"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETUPLOADDATAIP","Status":"0","Ip":"xxxxxx","gatewayIp":"xxxxxx"}}
Status:0操作成功,1操作失败;
ip:网关返回可用升级ip;
gatewayIp:网关地址;
void getwanreginfo():
机顶盒查询网关OTHER和INTERNET WAN连接状态;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETWANREGINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETWANREGINFO","Status":"0","IPTVRegStatusIPV4":"0","IPTVRegStatusIPV6":"0","INTRegStatusIPV4":"0","INTRegStatusIPV6":"0"}}
Status:0操作成功,1操作失败;
IPTVRegStatusIPV4:IPV4 IPTV WAN连接状态;IPTVRegStatusIPV6:IPV4 IPTVWAN连接状态
INTRegStatusIPV4:IPV4 INTERNET WAN连接状态;INTRegStatusIPV6:IPV4INTERNET WAN连接状态
WAN状态值,0:未连接;1:连接中;2:已连接;3:未配置
void getdevbasicinfo():
机顶盒主动查询型号序列号等信息;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETDEVBASICINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETDEVBASICINFO","Status":"0","ProductClass":"xxxx","SerialNumber":"xxxx","ManufacturerOUI":"xxxxx"}}
Status:0操作成功,1操作失败;
void queryWlanInfo():
机顶盒主动查询PPPoE上网络连接信息:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"QUERY_WAN_INFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"QUERY_WAN_INFO","Status":"0","ADDRESSTYPE":"xxxx","CONNECTIONTYPE":"xxxx","CONNECTIONSTATUS":"xxxxx","PPPOE_USR_NAME":"xxxxx","PPPOE_PASSWORD":"xxxxx"}}
Status:0操作成功,1操作失败;
ADDRESSTYPE:下层设备网络连接方式DHCP/PPPoE/Static;
CONNECTIONTYPE:连接类型,取值IP_Routed:路由IP_Bridged:桥;当值为IP_Routed时,PPPoE账号密码有效;
PPPOE_USR_NAME:PPPoE账号
PPPOE_PASSWORD:PPPoE密码
CONNECTIONSTATUS:连接状态;取值如下
Unconfigured:未配置
Connecting:连接中
Authenticating:认证中
Connected:已连接
PendingDisconnect:正在等待断开
Disconnecting:正在断开
Disconnected:连接已断开
void setMixType():
机顶盒主动设置切换公客政企版;请求格式:
{"ID":"","RPCMethod":"SET","Parameter":{"CmdType":"SETMIXTYPE","type":"xxxx"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"SETMIXTYPE","Status":"0"}}
Status:0操作成功,1操作失败;
Type:GNE:政企版PUB:公客版
void getItmsregsiterStatus():
机顶盒主动查询ITMS注册信息;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"ITMSREGISTERSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"ITMSREGISTERSTATUS","Status":"0","ITMSRegStatus":"0"}}
Status:0:成功1:失败;
ITMSRegStatus:0:注册成功;1:注册失败;2:未注册。
优选的,所述通信协议包括一个类型为RAW的Socket,所述Socket绑定在融合网关通信系统和机顶盒通信系统之间的网口上,用来收发自定义的二层数据包;当从RAWSocket上接收到二层数据包时,按二层协议的报文格式消息格式解析消息内容,然后传送到本通信系统上对应的软件功能模块;当本通信系统有向对方系统发送管理消息需求时,由该通信系统上的监控进程按二层协议的报文格式组装消息包,并通过RAW Socket发送出去。
优选的,所述二层协议的报文格式遵循Ethernet II。
优选的,所述二层协议的报文格式遵循以下报文处理方法:a网关和机顶盒能接收Type=9211和Type=9212的二层广播或单播报文,不得对收到的报文进行转发;不得对WAN侧报文进行响应,没有学习到对侧MAC时发送广播报文。
b.所述步骤a中,若收到的是广播报文,将报文SA作为响应报文DA,将融合网关通信系统自身LAN侧MAC地址作为响应报文SA,从收到报文的LAN侧端口单播原路发送响应;
c.所述步骤a中,若收到的是单播报文,则将报文SA作为响应报文DA,将融合网关通信系统自身LAN侧MAC地址作为响应报文SA,数据长度和数据(数据需加密)修改为相应的操作结果长度和结果从收到报文的LAN侧端口单播原路发送响应。
本发明的有益技术效果是:(1)网关模块和机顶盒模块通过软件通信协议进行数据交互,每个模块不再是各自独立的软件系统;这样,机顶盒能设置查看网关运行状况,也能对网关进行设置,网关对于机顶盒也同样如此;并且在进行装机开通以及日常使用时,网关和机顶盒是一个“整体”,不必采用复杂的方式对他们进行查看与设置;另外,从机顶盒管理平台及网关管理平台在管理融合网关和机顶盒时也能够整体管理。
(2)通过自定义的二层管理协议和报文处理方式,为融合网关开发提供技术规范,在不改变现有软件架构的条件下,使后期的功能扩展开发更加方便容易,提高了设计开发的灵活性。
附图说明
图1显示为本发明的实施例的步骤流程示意图。
图2显示为本发明的实施例的报文格式示意图。
图3显示为本发明的实施例的网关主动发送信息时的流程示意图。
具体实施方式
下面结合本发明的附图1-3,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
实施例:
如图1所示,一种融合网关部分和机顶盒部分相互通讯的方法,包括以下步骤:
S1:提供一融合网关通信系统,所述融合网关通信系统可对接收的信息进行解密操作,且所述融合网关通信系统可对发送的信息进行加密操作;提供一机顶盒通信系统,所述机顶盒通信系统可对接收的信息进行解密操作,且所述机顶盒通信系统可对发送的信息进行加密操作;
S2:在步骤S1的基础上,提供一供所述融合网关通信系统和所述机顶盒通信系统进行信息交互的通信规范;
S3:在步骤S2的基础上,当所述融合网关通信系统接收到所述机顶盒通信系统发送来的经过加密操作的信息时,所述融合网关通信系统可通过所述通信规范对该加密信息进行解密操作,待所述融合网关通信系统完成对该加密信息的读取后,所述融合网关通信系统生成一加密反馈信息并将该加密反馈信息发送至所述机顶盒通信系统,当所述机顶盒通信系统接收到所述融合网关通信系统发送来的加密反馈信息时,所述机顶盒通信系统通过所述通信规范对该加密反馈信息进行解密操作,从而完成对该加密反馈信息的读取;同理,当所述机顶盒通信系统接收到所述融合网关通信系统发送来的经过加密操作的信息时,所述机顶盒通信系统可通过所述通信规范对该加密信息进行解密操作,待所述机顶盒通信系统完成对该加密信息的读取后,所述机顶盒通信系统生成一加密反馈信息并将该加密反馈信息发送至所述融合网关通信系统,当所述融合网关通信系统接收到所述机顶盒通信系统发送来的加密反馈信息时,所述融合网关通信系统通过所述通信规范对该加密反馈信息进行解密操作,从而完成对该加密反馈信息的读取。
通过上述方案,网关模块和机顶盒模块通过软件通信协议进行数据交互,每个模块不再是各自独立的软件系统;这样,机顶盒能设置查看网关运行状况,也能对网关进行设置,网关对于机顶盒也同样如此;并且在进行装机开通以及日常使用时,网关和机顶盒是一个“整体”,不必采用复杂的方式对他们进行查看与设置;另外,从机顶盒管理平台及网关管理平台在管理融合网关和机顶盒时也能够整体管理。
优选的,在步骤S3中,当所述机顶盒通信系统向所述融合网关通信系统主动发送信息时,所述通信规范的具体方式为:
融合网关通信系统主动发起协议类型为0x9212;
voidgetIPTVVersion():
获取机顶盒通信系统版本信息:操作系统版本、系统软件版本、各应用软件版本;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"IPTVVERSION"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"IPTVVERSION","Status":"0","OSVersion":"xxxx","SoftwareVersion":"xxxx","appinfo":[{"name":"xxxx","version":"xxxx"},{"name":"xxxx","version":"xxxx"}]}}
Status:调用成功/失败,0成功,1失败;OSVersion:操作系统版本;SoftwareVersion:系统软件版本;appinfo:应用软件信息,name为应用软件名称,version为其对应版本;
voidgetNetInfo():
获取网络信息:机顶盒通信系统的MAC、IP、子网掩码、默认网关、DNS服务器;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"NETINFO"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"NETINFO","Status":"0","DevMac":"xxxx","A4InetAddr":"xxxx","A4Mask":"xxxx","A4DefGateway":"xxxx","A4DNS":"xxxx","A4ALTDNS":"xxxx","A6InetAddr":"xxxx","A6Mask":"xxxx","A6DefGateway":"xxxx","A6DNS":"xxxx","A6ALTDNS":"xxxx",B4InetAddr":"xxxx","B4Mask":"xxxx","B4DefGateway":"xxxx","B4DNS":"xxxx","B4ALTDNS":"xxxx","B6InetAddr":"xxxx","B6Mask":"xxxx","B6DefGateway":"xxxx","B6DNS":"xxxx","B6ALTDNS":"xxxx"}}
Status:调用成功/失败,0成功,1失败;DevMac:机顶盒通信系统MAC;InetAddr:机顶盒通信系统IP;Mask:机顶盒通信系统子网掩码;DefGateway:机顶盒通信系统默认网关;DNS:机顶盒通信系统DNS服务器;ALTDNS:机顶盒通信系统备用DNS服务器;
A4表示A平面Ipv4,A6表示A平面Ipv6,如A4InetAddr表示机顶盒A平面ipv4地址,A6InetAddr表示机顶盒A平面ipv6地址;
B4表示B平面Ipv4,B6表示B平面Ipv6,如B4InetAddr表示机顶盒B平面ipv4地址,B6InetAddr表示机顶盒B平面ipv6地址;
voidgetServerInfo():
获取机顶盒服务器信息:可查看机顶盒终端管理平台地址、NTP地址等;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"SERVERINFO"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"SERVERINFO","Status":"0","PlatformAddr":"xxxx","NTPAddr":"xxxx"}}
Status:调用成功/失败,0成功,1失败;PlatformAddr:机顶盒终端管理平台地址;NTPAddr;NTP地址;
voidHibernateState(int state):
网关主动发送休眠状态,当网关模块休眠时,向机顶盒通信系统发送网关休眠消息,机顶盒接收到后也应进入休眠状态;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"HIBERNATESTATE","STATE":"1"}}
State:表示休眠状态,1休眠,2未休眠;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"HIBERNATESTATE","Status":"0"}}
Status:0机顶盒休眠成功,1机顶盒休眠失败;
voidClearAccount():
网关首次注册成功后,通过本地界面等方式修改宽带识别码且新的宽带识别码在OLT或ITMS+上注册成功,发送此消息,机顶盒通信系统收到消息清空接入账号和业务账号;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"CLEARACCOUNT"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"CLEARACCOUNT","Status":"0"}}
Status:0清空成功,1清空失败;
voidrepAlarmInfo():
□告警状态:包括CPU负载告警、CPU温度告警等;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"ALARMINFO","Info":"SysCPUTempAlarm(x)"}}
SysCPUTempAlarm(x):CPU温度告警,当前温度为x,收到此消息表示连续5分钟CPU温度高于阀值;
SysCPULoadAlarm(x):CPU负载告警,当前占用率为x(如80表示占用率%80),收到此消息表示连续5分钟CPU负载高于阀值;
voidrepwanlinkstate():
网关为lan上行设备时,当上行口状态发生改变时,主动发送上行口连接状态;格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"WANLINKSTATE","STATE":"1"}}
STATE:1:up,连接上;0:down,断开;
voidrepbootinfo():
网关上电启动完成,交互进程启动后,主动发送启动完成消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"BOOTCOMPLETE"}}
voidotherwanupinfo():
OTHER wan connect时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"OTHERWANUP"}}
voidinternetwanupinfo()
Internet wan connect时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"INTERNETWANUP"}}
void OltLinkSuccessInfo():
OLT认证成功时时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"OLTLINKSUCCESS"}}
void devrepwaninfo():
主动上报是否建立OTHER WAN和INTERNET WAN;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"WANINFO","OTHERFLAG":"1","INTERNETFLAG":"1"}}
OTHERFLAG:是否建立OTHER WAN,0:未建立1:已建立;
INTERNETFLAG:是否建立OTHER WAN,0:未建立1:已建立;
void linkstatus():
光纤连接状态变更时,主动上报连接状态;格式
{"RPCMethod":"GET","Parameter":{"CmdType":"PONSTATE","linkDown":"true"}}
linkDown:连接断开:true连接成功:false;
void devRrebootinfo():
网关重启时,主动上报重启消息;格式
{ID:"","RPCMethod":"GET","Parameter":{"CmdType":"DEVREBOOT"}}。
优选的,在步骤S3中,当所述融合网关通信系统向所述机顶盒通信系统主动发送信息时,所述通信规范的具体方式为:
机顶盒通信系统主动发起协议类型为0x9211;
voidHibernateState(int state):
机顶盒主动发送休眠状态,当机顶盒模块休眠和从休眠状态恢复时,向网关模块发送网关休眠消息,网关在机顶盒唤醒时应该唤醒;请求格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"HIBERNATESTATE","STATE":"1"}}
State:表示休眠状态,1休眠,2未休眠;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"HIBERNATESTATE","Status":"0"}}
Status:0操作成功,1操作失败;
voidgetNetConStatus():
网络连接状态:光纤(如:连通、断开、光信号低等)、OLT认证状态、IPTV WAN连接状态(如:未配置、断开、正常等);请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"NETCONSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"NETCONSTATUS","Status":"0","PonStatus":"0","LoidStatus":"0","IPTVRegStatusIPV4":"0","IPTVRegStatusIPV6":"0"}}
Status:0操作成功,1操作失败;
PonStatus:光纤连接状态,0:未连接;1:已连接;2:光信号弱
LoidStatus:OLT认证状态,0:初始状态;1:认证成功;2:LOID无效;3:密码错误;4:LOID冲突;5:光纤未连接;6:认证失败;7:LOID未认证;8:未知状态
IPTVRegStatusIPV4:IPV4 IPTV WAN连接状态;IPTVRegStatusIPV6:IPV4 IPTVWAN连接状态
IPTV WAN状态值,0:未连接;1:连接中;2:已连接;3:未配置
voidgetServiceStatus():
□业务状态:上网业务状态(如:未配置、断开、正常等)、语音业务状态(如:未配置、注册失败、正常等);请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"SERVICESTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"SERVICESTATUS","Status":"0","IPv4info":[{"servicetype":"internet","regstatus":"xxxx"},{"servicetype":"voip","regstatus":"xxxx"}],"IPv6info":[{"servicetype":"internet","regstatus":"xxxx"},{"servicetype":"voip","regstatus":"xxxx"}]}}
Status:0操作成功,1操作失败;
IPv4info:IPv4信息;IPv6info:IPv6信息;
Servicetype:连接类型;internet:上网连接;voip:语音连接;
RegStatus状态值,0:未连接;1:连接中;2:已连接;3:未配置
voidgetPlatformStatus():
平台连接状态:包括ITMS连接状态、智能网关平台连接状态等;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"PLATFORMSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"PLATFORMSTATUS","Status":"0","ITMSRegStatus":"0","SmartGwstatus":[{"platformname":"bss_platform","server":"xxxx","status":"xxxx"},{"platformname":"main_platform","server":"xxxx","status":"xxxx"},{"platformname":"dist_platform","server":"xxxx","status":"xxx"}]}}
Status:0操作成功,1操作失败;
ITMSRegStatus:0:注册成功;1:注册失败;2:未注册;
SmartGwstatus:智能网关平台连接状态;platformname:平台名字,bss_platform:BSS平台;main_platform:主能力平台;dist_platform:分发平台;server:平台地址;status:连接状态;
status:与平台连接状态;返回为GB2132编码中文字符;
voidsetLoidRegisterInfo():
设置逻辑ID账号和密码;请求格式:
{"ID":"","RPCMethod":"SET","Parameter":{"CmdType":"REGISTER","userName":"xxxx","pwd":"xxxx"}}
userName:逻辑ID,当为空或者只设置密码时,userName值为字符串”NULL”;不能缺少该字段;
Pwd:密码,当为空或者只设置逻辑ID时,pwd值为字符串”NULL”;不能缺少该字段;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"REGISTER","Status":"0"}
Status:0操作成功,1操作失败;
voidgetRegisterStat():
按照速影规范;获取注册认证过程和业务开通过程;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"REGISTERINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"REGISTERINFO","Status":"0","registerstat":"xxxxx"}}
Status:0操作成功,1操作失败;
registerstat:注册开通进度;其取值如下:
REGISTER_DEFAULT:初始设备未注册状态;
REGISTER_REGISTED:设备为已注册状态;
REGISTER_TIMEOUT:注册超时失败;
REGISTER_NOMATCH_NOLIMITED STATE=%s:逻辑ID与密码不匹配,剩余尝试次数:%s;
REGISTER_NOMATCH_LIMITED:逻辑ID与密码不匹配,注册失败;
REGISTER_NOACCOUNT_NOLIMITED STATE=%s:密码不存在,剩余尝试次数:%s;
REGISTER_NOUSER_LIMITED:逻辑ID不存在,注册失败;
REGISTER_OLT PROGRESS=%s:正在注册OLT(%s表示百分比,可取20表示正在注册OLT30表示在OLT授权成功,40表示TR069的WAN连接获得IP地址;
REGISTER_OLT_FAIL:在OLT上注册失败;
REGISTER_OK_DOWN_BUSINESS PROGRESS=%s和REGISTER_OK_DOWN_BUSINESSPROGRESS=%s BUSSNAME=%s:注册成功,正在下发业务(进度为%s),%s可取60,99;%s如果为50,表示注册ITMS平台成功,等待下发业务,%s如果为60,表示平台开使下发业务下发的业务名称为(BUSSNAME=%S),可以取”INTERNET”,”VOIP”,”IPTV””OTHER”的组合;
REGISTER_OK SERVICENAME=%s:注册成功,下发业务成功,共下发了XX业务(下发几个业务就提示几个业务);
REGISTER_OK_NOW_REBOOT:注册成功,下发业务成功,网关需要重启,请等待;
REGISTER_POK:注册成功,下发业务失败;
REGISTER_FAIL:注册失败;
voidgetCpuinfo():
获取CPU温度和负载信息,请求格式
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETCPUINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETCPUINFO","Status":"0","CPUTemp":"ON(x)","CPULoad":"ON(x)"}}
Status:0操作成功,1操作失败;
CPUTemp:CPU温度信息,ON表示温度过高,OFF表示关闭报警,x为温度;
CPULoad:CPU负载信息,ON表示负载过高,OFF表示关闭报警,x为负载情况,若80,占用率%80
voidgetBootinfo():
获取网关是否已经开机,请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETBOOTINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETBOOTINFO","State":"BOOTCOMPLETE"}}
回复此消息表示已经开机;
voidgetWanlinkState():
网关为lan上行设备时,获取上行口是否连接;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETWANLINKSTATE"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETWANLINKSTATE","Status":"0","State":"Up"}}
Status:0操作成功,1操作失败;
State:上行口连接状态,Up为已连接,其余未连接;
void getUploaddataIP():
机顶盒需要对网关进行升级时,通过此接口获取网关给定机顶盒IP:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETUPLOADDATAIP"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETUPLOADDATAIP","Status":"0","Ip":"xxxxxx","gatewayIp":"xxxxxx"}}
Status:0操作成功,1操作失败;
ip:网关返回可用升级ip;
gatewayIp:网关地址;
void getwanreginfo():
机顶盒查询网关OTHER和INTERNET WAN连接状态;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETWANREGINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETWANREGINFO","Status":"0","IPTVRegStatusIPV4":"0","IPTVRegStatusIPV6":"0","INTRegStatusIPV4":"0","INTRegStatusIPV6":"0"}}
Status:0操作成功,1操作失败;
IPTVRegStatusIPV4:IPV4 IPTV WAN连接状态;IPTVRegStatusIPV6:IPV4 IPTVWAN连接状态
INTRegStatusIPV4:IPV4 INTERNET WAN连接状态;INTRegStatusIPV6:IPV4INTERNETWAN连接状态
WAN状态值,0:未连接;1:连接中;2:已连接;3:未配置
void getdevbasicinfo():
机顶盒主动查询型号序列号等信息;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETDEVBASICINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETDEVBASICINFO","Status":"0","ProductClass":"xxxx","SerialNumber":"xxxx","ManufacturerOUI":"xxxxx"}}
Status:0操作成功,1操作失败;
void queryWlanInfo():
机顶盒主动查询PPPoE上网络连接信息:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"QUERY_WAN_INFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"QUERY_WAN_INFO","Status":"0","ADDRESSTYPE":"xxxx","CONNECTIONTYPE":"xxxx","CONNECTIONSTATUS":"xxxxx","PPPOE_USR_NAME":"xxxxx","PPPOE_PASSWORD":"xxxxx"}}
Status:0操作成功,1操作失败;
ADDRESSTYPE:下层设备网络连接方式DHCP/PPPoE/Static;
CONNECTIONTYPE:连接类型,取值IP_Routed:路由IP_Bridged:桥;当值为IP_Routed时,PPPoE账号密码有效;
PPPOE_USR_NAME:PPPoE账号
PPPOE_PASSWORD:PPPoE密码
CONNECTIONSTATUS:连接状态;取值如下
Unconfigured:未配置
Connecting:连接中
Authenticating:认证中
Connected:已连接
PendingDisconnect:正在等待断开
Disconnecting:正在断开
Disconnected:连接已断开
void setMixType():
机顶盒主动设置切换公客政企版;请求格式:
{"ID":"","RPCMethod":"SET","Parameter":{"CmdType":"SETMIXTYPE","type":"xxxx"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"SETMIXTYPE","Status":"0"}}
Status:0操作成功,1操作失败;
Type:GNE:政企版PUB:公客版
void getItmsregsiterStatus():
机顶盒主动查询ITMS注册信息;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"ITMSREGISTERSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"ITMSREGISTERSTATUS","Status":"0","ITMSRegStatus":"0"}}
Status:0:成功1:失败;
ITMSRegStatus:0:注册成功;1:注册失败;2:未注册。
如图2和图3所示,通过上述方案,当所述融合网关通信系统接收到所述机顶盒通信系统发送来的经过加密操作的信息时,所述融合网关通信系统可通过所述通信规范对该加密信息进行解密操作,待所述融合网关通信系统完成对该加密信息的读取后,所述融合网关通信系统生成一加密反馈信息并将该加密反馈信息发送至所述机顶盒通信系统,当所述机顶盒通信系统接收到所述融合网关通信系统发送来的加密反馈信息时,所述机顶盒通信系统通过所述通信规范对该加密反馈信息进行解密操作,从而完成对该加密反馈信息的读取;同理,当所述机顶盒通信系统接收到所述融合网关通信系统发送来的经过加密操作的信息时,所述机顶盒通信系统可通过所述通信规范对该加密信息进行解密操作,待所述机顶盒通信系统完成对该加密信息的读取后,所述机顶盒通信系统生成一加密反馈信息并将该加密反馈信息发送至所述融合网关通信系统,当所述融合网关通信系统接收到所述机顶盒通信系统发送来的加密反馈信息时,所述融合网关通信系统通过所述通信规范对该加密反馈信息进行解密操作,从而完成对该加密反馈信息的读取。从而实现融合网关通信系统与所述机顶盒通信系统之间的数据交互。
优选的,所述通信协议包括一个类型为RAW的Socket,所述Socket绑定在融合网关通信系统和机顶盒通信系统之间的网口上,用来收发自定义的二层数据包;当从RAWSocket上接收到二层数据包时,按二层协议的报文格式消息格式解析消息内容,然后传送到本通信系统上对应的软件功能模块;当本通信系统有向对方系统发送管理消息需求时,由该通信系统上的监控进程按二层协议的报文格式组装消息包,并通过RAW Socket发送出去。
优选的,所述二层协议的报文格式遵循Ethernet II。
优选的,所述二层协议的报文格式遵循以下报文处理方法:a.网关和机顶盒能接收Type=9211和Type=9212的二层广播或单播报文,不得对收到的报文进行转发;不得对WAN侧报文进行响应,没有学习到对侧MAC时发送广播报文。
b.所述步骤a中,若收到的是广播报文,将报文SA作为响应报文DA,将融合网关通信系统自身LAN侧MAC地址作为响应报文SA,从收到报文的LAN侧端口单播原路发送响应;
c.所述步骤a中,若收到的是单播报文,则将报文SA作为响应报文DA,将融合网关通信系统自身LAN侧MAC地址作为响应报文SA,数据长度和数据(数据需加密)修改为相应的操作结果长度和结果从收到报文的LAN侧端口单播原路发送响应。
通过上述方案,通过自定义的二层管理协议和报文处理方式,为融合网关开发提供技术规范,在不改变现有软件架构的条件下,使后期的功能扩展开发更加方便容易,提高了设计开发的灵活性。
在本发明的描述中,需要理解的是,术语“逆时针”、“顺时针”“纵向”、“横向”、“上”、“下”、“前”、“后”、“左”、“右”、“竖直”、“水平”、“顶”、“底”、“内”、“外”等指示的方位或位置关系为基于附图所示的方位或位置关系,仅是为了便于描述本发明,而不是指示或暗示所指的装置或元件必须具有特定的方位、以特定的方位构造和操作,因此不能理解为对本发明的限制。
Claims (6)
1.一种融合网关部分和机顶盒部分相互通讯的方法,其特征在于,包括以下步骤:
S1:提供一种融合网关通信系统,所述融合网关通信系统可对接收的信息进行解密操作,且所述融合网关通信系统可对发送的信息进行加密操作;提供一机顶盒通信系统,所述机顶盒通信系统可对接收的信息进行解密操作,且所述机顶盒通信系统可对发送的信息进行加密操作;
S2:在步骤S1的基础上,提供一供所述融合网关通信系统和所述机顶盒通信系统进行信息交互的通信规范;
S3:在步骤S2的基础上,当所述融合网关通信系统接收到所述机顶盒通信系统发送来的经过加密操作的信息时,所述融合网关通信系统可通过所述通信规范对该加密信息进行解密操作,待所述融合网关通信系统完成对该加密信息的读取后,所述融合网关通信系统生成一加密反馈信息并将该加密反馈信息发送至所述机顶盒通信系统,当所述机顶盒通信系统接收到所述融合网关通信系统发送来的加密反馈信息时,所述机顶盒通信系统通过所述通信规范对该加密反馈信息进行解密操作,从而完成对该加密反馈信息的读取;同理,当所述机顶盒通信系统接收到所述融合网关通信系统发送来的经过加密操作的信息时,所述机顶盒通信系统可通过所述通信规范对该加密信息进行解密操作,待所述机顶盒通信系统完成对该加密信息的读取后,所述机顶盒通信系统生成一加密反馈信息并将该加密反馈信息发送至所述融合网关通信系统,当所述融合网关通信系统接收到所述机顶盒通信系统发送来的加密反馈信息时,所述融合网关通信系统通过所述通信规范对该加密反馈信息进行解密操作,从而完成对该加密反馈信息的读取。
2.根据权利要求1所述的一种融合网关部分和机顶盒部分相互通讯的方法,其特征在于,在步骤S3中,当所述机顶盒通信系统向所述融合网关通信系统主动发送信息时,所述通信规范的具体方式为:
融合网关通信系统主动发起协议类型为0x9212;
voidgetIPTVVersion():
获取机顶盒通信系统版本信息:操作系统版本、系统软件版本、各应用软件版本;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"IPTVVERSION"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"IPTVVERSION","Status":"0","OSVersion":"xxxx","SoftwareVersion":"xxxx","appinfo":[{"name":"xxxx","version":"xxxx"},{"name":"xxxx","version":"xxxx"}]}}
Status:调用成功/失败,0成功,1失败;OSVersion:操作系统版本;SoftwareVersion:系统软件版本;appinfo:应用软件信息,name为应用软件名称,version为其对应版本;
voidgetNetInfo():
获取网络信息:机顶盒通信系统的MAC、IP、子网掩码、默认网关、DNS服务器;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"NETINFO"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"NETINFO","Status":"0","DevMac":"xxxx","A4InetAddr":"xxxx","A4Mask":"xxxx","A4DefGateway":"xxxx","A4DNS":"xxxx","A4ALTDNS":"xxxx","A6InetAddr":"xxxx","A6Mask":"xxxx","A6DefGateway":"xxxx","A6DNS":"xxxx","A6ALTDNS":"xxxx",B4InetAddr":"xxxx","B4Mask":"xxxx","B4DefGateway":"xxxx","B4DNS":"xxxx","B4ALTDNS":"xxxx","B6InetAddr":"xxxx","B6Mask":"xxxx","B6DefGateway":"xxxx","B6DNS":"xxxx","B6ALTDNS":"xxxx"}}
Status:调用成功/失败,0成功,1失败;DevMac:机顶盒通信系统MAC;InetAddr:机顶盒通信系统IP;Mask:机顶盒通信系统子网掩码;DefGateway:机顶盒通信系统默认网关;DNS:机顶盒通信系统DNS服务器;ALTDNS:机顶盒通信系统备用DNS服务器;
A4表示A平面Ipv4,A6表示A平面Ipv6,如A4InetAddr表示机顶盒A平面ipv4地址,A6InetAddr表示机顶盒A平面ipv6地址;
B4表示B平面Ipv4,B6表示B平面Ipv6,如B4InetAddr表示机顶盒B平面ipv4地址,B6InetAddr表示机顶盒B平面ipv6地址;
voidgetServerInfo():
获取机顶盒服务器信息:可查看机顶盒终端管理平台地址、NTP地址等;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"SERVERINFO"}}
回复格式:
{"ID":"","return_Parameter":{"CmdType":"SERVERINFO","Status":"0","PlatformAddr":"xxxx","NTPAddr":"xxxx"}}
Status:调用成功/失败,0成功,1失败;PlatformAddr:机顶盒终端管理平台地址;NTPAddr;NTP地址;
voidHibernateState(int state):
网关主动发送休眠状态,当网关模块休眠时,向机顶盒通信系统发送网关休眠消息,机顶盒接收到后也应进入休眠状态;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"HIBERNATESTATE","STATE":"1"}}
State:表示休眠状态,1休眠,2未休眠;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"HIBERNATESTATE","Status":"0"}}
Status:0机顶盒休眠成功,1机顶盒休眠失败;
voidClearAccount():
网关首次注册成功后,通过本地界面等方式修改宽带识别码且新的宽带识别码在OLT或ITMS+上注册成功,发送此消息,机顶盒通信系统收到消息清空接入账号和业务账号;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"CLEARACCOUNT"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"CLEARACCOUNT","Status":"0"}}
Status:0清空成功,1清空失败;
voidrepAlarmInfo():
□告警状态:包括CPU负载告警、CPU温度告警;请求格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"ALARMINFO","Info":"SysCPUTempAlarm(x)"}}
SysCPUTempAlarm(x):CPU温度告警,当前温度为x,收到此消息表示连续5分钟CPU温度高于阀值;
SysCPULoadAlarm(x):CPU负载告警,当前占用率为x(如80表示占用率%80),收到此消息表示连续5分钟CPU负载高于阀值;
voidrepwanlinkstate():
网关为lan上行设备时,当上行口状态发生改变时,主动发送上行口连接状态;格式:
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"WANLINKSTATE","STATE":"1"}}
STATE:1:up,连接上;0:down,断开;
voidrepbootinfo():
网关上电启动完成,交互进程启动后,主动发送启动完成消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"BOOTCOMPLETE"}}
voidotherwanupinfo():
OTHER wan connect时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"OTHERWANUP"}}
voidinternetwanupinfo()
Internet wan connect时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"INTERNETWANUP"}}
void OltLinkSuccessInfo():
OLT认证成功时时发送此消息;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"OLTLINKSUCCESS"}}
void devrepwaninfo():
主动上报是否建立OTHER WAN和INTERNET WAN;格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"WANINFO","OTHERFLAG":"1","INTERNETFLAG":"1"}}
OTHERFLAG:是否建立OTHER WAN,0:未建立1:已建立;
INTERNETFLAG:是否建立OTHER WAN,0:未建立1:已建立;
void linkstatus():
光纤连接状态变更时,主动上报连接状态;格式
{"RPCMethod":"GET","Parameter":{"CmdType":"PONSTATE","linkDown":"true"}}
linkDown:连接断开:true连接成功:false;
void devRrebootinfo():
网关重启时,主动上报重启消息;格式
{ID:"","RPCMethod":"GET","Parameter":{"CmdType":"DEVREBOOT"}}。
3.根据权利要求1或2所述的一种融合网关部分和机顶盒部分相互通讯的方法,其特征在于,在步骤S3中,当所述融合网关通信系统向所述机顶盒通信系统主动发送信息时,所述通信规范的具体方式为:
机顶盒通信系统主动发起协议类型为0x9211;
voidHibernateState(int state):
机顶盒主动发送休眠状态,当机顶盒模块休眠和从休眠状态恢复时,向网关模块发送网关休眠消息,网关在机顶盒唤醒时应该唤醒;请求格式
{"ID":"","RPCMethod":"REP","Parameter":{"CmdType":"HIBERNATESTATE","STATE":"1"}}
State:表示休眠状态,1休眠,2未休眠;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"HIBERNATESTATE","Status":"0"}}
Status:0操作成功,1操作失败;
voidgetNetConStatus():
网络连接状态:光纤、OLT认证状态、IPTV WAN连接状态;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"NETCONSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"NETCONSTATUS","Status":"0","PonStatus":"0","LoidStatus":"0","IPTVRegStatusIPV4":"0","IPTVRegStatusIPV6":"0"}}
Status:0操作成功,1操作失败;
PonStatus:光纤连接状态,0:未连接;1:已连接;2:光信号弱
LoidStatus:OLT认证状态,0:初始状态;1:认证成功;2:LOID无效;3:密码错误;4:LOID冲突;5:光纤未连接;6:认证失败;7:LOID未认证;8:未知状态
IPTVRegStatusIPV4:IPV4 IPTV WAN连接状态;IPTVRegStatusIPV6:IPV4 IPTV WAN连接状态
IPTV WAN状态值,0:未连接;1:连接中;2:已连接;3:未配置
voidgetServiceStatus():
□业务状态:上网业务状态(如:未配置、断开、正常等)、语音业务状态(如:未配置、注册失败、正常等);请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"SERVICESTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"SERVICESTATUS","Status":"0","IPv4info":[{"servicetype":"internet","regstatus":"xxxx"},{"servicetype":"voip","regstatus":"xxxx"}],"IPv6info":[{"servicetype":"internet","regstatus":"xxxx"},{"servicetype":"voip","regstatus":"xxxx"}]}}
Status:0操作成功,1操作失败;
IPv4info:IPv4信息;IPv6info:IPv6信息;
Servicetype:连接类型;internet:上网连接;voip:语音连接;
RegStatus状态值,0:未连接;1:连接中;2:已连接;3:未配置
voidgetPlatformStatus():
平台连接状态:包括ITMS连接状态、智能网关平台连接状态等;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"PLATFORMSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"PLATFORMSTATUS","Status":"0","ITMSRegStatus":"0","SmartGwstatus":[{"platformname":"bss_platform","server":"xxxx","status":"xxxx"},{"platformname":"main_platform","server":"xxxx","status":"xxxx"},{"platformname":"dist_platform","server":"xxxx","status":"xxx"}]}}
Status:0操作成功,1操作失败;
ITMSRegStatus:0:注册成功;1:注册失败;2:未注册;
SmartGwstatus:智能网关平台连接状态;platformname:平台名字,bss_platform:BSS平台;main_platform:主能力平台;dist_platform:分发平台;server:平台地址;status:连接状态;
status:与平台连接状态;返回为GB2132编码中文字符;
voidsetLoidRegisterInfo():
设置逻辑ID账号和密码;请求格式:
{"ID":"","RPCMethod":"SET","Parameter":{"CmdType":"REGISTER","userName":"xxxx","pwd":"xxxx"}}
userName:逻辑ID,当为空或者只设置密码时,userName值为字符串”NULL”;不能缺少该字段;
Pwd:密码,当为空或者只设置逻辑ID时,pwd值为字符串”NULL”;不能缺少该字段;
应答格式:
{"ID":"","return_Parameter":{"CmdType":"REGISTER","Status":"0"}
Status:0操作成功,1操作失败;
voidgetRegisterStat():
获取注册认证过程和业务开通过程;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"REGISTERINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"REGISTERINFO","Status":"0","registerstat":"xxxxx"}}
Status:0操作成功,1操作失败;
registerstat:注册开通进度;其取值如下:
REGISTER_DEFAULT:初始设备未注册状态;
REGISTER_REGISTED:设备为已注册状态;
REGISTER_TIMEOUT:注册超时失败;
REGISTER_NOMATCH_NOLIMITED STATE=%s:逻辑ID与密码不匹配,剩余尝试次数:%s;
REGISTER_NOMATCH_LIMITED:逻辑ID与密码不匹配,注册失败;
REGISTER_NOACCOUNT_NOLIMITED STATE=%s:密码不存在,剩余尝试次数:%s;
REGISTER_NOUSER_LIMITED:逻辑ID不存在,注册失败;
REGISTER_OLT PROGRESS=%s:正在注册OLT(%s表示百分比,可取20表示正在注册OLT30表示在OLT授权成功,40表示TR069的WAN连接获得IP地址;
REGISTER_OLT_FAIL:在OLT上注册失败;
REGISTER_OK_DOWN_BUSINESS PROGRESS=%s和REGISTER_OK_DOWN_BUSINESSPROGRESS=%s BUSSNAME=%s:注册成功,正在下发业务,进度为%s,%s可取60,99;%s如果为50,表示注册ITMS平台成功,等待下发业务,%s如果为60,表示平台开使下发业务下发的业务名称为BUSSNAME=%S,可以取”INTERNET”,”VOIP”,”IPTV””OTHER”的组合;
REGISTER_OK SERVICENAME=%s:注册成功,下发业务成功,共下发了XX业务,即下发几个业务就提示几个业务;
REGISTER_OK_NOW_REBOOT:注册成功,下发业务成功,网关需要重启,请等待;
REGISTER_POK:注册成功,下发业务失败;
REGISTER_FAIL:注册失败;
voidgetCpuinfo():
获取CPU温度和负载信息,请求格式
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETCPUINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETCPUINFO","Status":"0","CPUTemp":"ON(x)","CPULoad":"ON(x)"}}
Status:0操作成功,1操作失败;
CPUTemp:CPU温度信息,ON表示温度过高,OFF表示关闭报警,x为温度;
CPULoad:CPU负载信息,ON表示负载过高,OFF表示关闭报警,x为负载情况,若80,占用率%80
voidgetBootinfo():
获取网关是否已经开机,请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETBOOTINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETBOOTINFO","State":"BOOTCOMPLETE"}}
回复此消息表示已经开机;
voidgetWanlinkState():
网关为lan上行设备时,获取上行口是否连接;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETWANLINKSTATE"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETWANLINKSTATE","Status":"0","State":"Up"}}
Status:0操作成功,1操作失败;
State:上行口连接状态,Up为已连接,其余未连接;
void getUploaddataIP():
机顶盒需要对网关进行升级时,通过此接口获取网关给定机顶盒IP:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETUPLOADDATAIP"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETUPLOADDATAIP","Status":"0","Ip":"xxxxxx","gatewayIp":"xxxxxx"}}
Status:0操作成功,1操作失败;
ip:网关返回可用升级ip;
gatewayIp:网关地址;
void getwanreginfo():
机顶盒查询网关OTHER和INTERNET WAN连接状态;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETWANREGINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETWANREGINFO","Status":"0","IPTVRegStatusIPV4":"0","IPTVRegStatusIPV6":"0","INTRegStatusIPV4":"0","INTRegStatusIPV6":"0"}}
Status:0操作成功,1操作失败;
IPTVRegStatusIPV4:IPV4 IPTV WAN连接状态;IPTVRegStatusIPV6:IPV4 IPTV WAN连接状态
INTRegStatusIPV4:IPV4 INTERNET WAN连接状态;INTRegStatusIPV6:IPV4 INTERNETWAN连接状态
WAN状态值,0:未连接;1:连接中;2:已连接;3:未配置
void getdevbasicinfo():
机顶盒主动查询型号序列号等信息;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"GETDEVBASICINFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"GETDEVBASICINFO","Status":"0","ProductClass":"xxxx","SerialNumber":"xxxx","ManufacturerOUI":"xxxxx"}}
Status:0操作成功,1操作失败;
void queryWlanInfo():
机顶盒主动查询PPPoE上网络连接信息:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"QUERY_WAN_INFO"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"QUERY_WAN_INFO","Status":"0","ADDRESSTYPE":"xxxx","CONNECTIONTYPE":"xxxx","CONNECTIONSTATUS":"xxxxx","PPPOE_USR_NAME":"xxxxx","PPPOE_PASSWORD":"xxxxx"}}
Status:0操作成功,1操作失败;
ADDRESSTYPE:下层设备网络连接方式DHCP/PPPoE/Static;
CONNECTIONTYPE:连接类型,取值IP_Routed:路由IP_Bridged:桥;当值为IP_Routed时,PPPoE账号密码有效;
PPPOE_USR_NAME:PPPoE账号
PPPOE_PASSWORD:PPPoE密码
CONNECTIONSTATUS:连接状态;取值如下
Unconfigured:未配置
Connecting:连接中
Authenticating:认证中
Connected:已连接
PendingDisconnect:正在等待断开
Disconnecting:正在断开
Disconnected:连接已断开
void setMixType():
机顶盒主动设置切换公客政企版;请求格式:
{"ID":"","RPCMethod":"SET","Parameter":{"CmdType":"SETMIXTYPE","type":"xxxx"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"SETMIXTYPE","Status":"0"}}
Status:0操作成功,1操作失败;
Type:GNE:政企版PUB:公客版
void getItmsregsiterStatus():
机顶盒主动查询ITMS注册信息;请求格式:
{"ID":"","RPCMethod":"GET","Parameter":{"CmdType":"ITMSREGISTERSTATUS"}}
应答格式:
{"ID":"","return_Parameter":{"CmdType":"ITMSREGISTERSTATUS","Status":"0","ITMSRegStatus":"0"}}
Status:0:成功1:失败;
ITMSRegStatus:0:注册成功;1:注册失败;2:未注册。
4.根据权利要求1所述的一种融合网关部分和机顶盒部分相互通讯的方法,其特征在于,所述通信协议包括一个类型为RAW的Socket,所述Socket绑定在融合网关通信系统和机顶盒通信系统之间的网口上,用来收发自定义的二层数据包;当从RAW Socket上接收到二层数据包时,按二层协议的报文格式消息格式解析消息内容,然后传送到本通信系统上对应的软件功能模块;当本通信系统有向对方系统发送管理消息需求时,由该通信系统上的监控进程按二层协议的报文格式组装消息包,并通过RAW Socket发送出去。
5.根据权利要求4所述的一种融合网关部分和机顶盒部分相互通讯的方法,其特征在于,所述二层协议的报文格式遵循Ethernet II。
6.根据权利要求4-5任意一项所述的一种融合网关部分和机顶盒部分相互通讯的方法,其特征在于,所述二层协议的报文格式遵循以下报文处理方法:a网关和机顶盒能接收Type=9211和Type=9212的二层广播或单播报文,不得对收到的报文进行转发;不得对WAN侧报文进行响应,没有学习到对侧MAC时发送广播报文。
b.若收到的是广播报文,将报文SA作为响应报文DA,将融合网关通信系统自身LAN侧MAC地址作为响应报文SA,从收到报文的LAN侧端口单播原路发送响应;
c.所述步骤a中,若收到的是单播报文,则将报文SA作为响应报文DA,将融合网关通信系统自身LAN侧MAC地址作为响应报文SA,数据长度和加密的数据修改为相应的操作结果长度和结果从收到报文的LAN侧端口单播原路发送响应。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201911276978.XA CN111031370A (zh) | 2019-12-12 | 2019-12-12 | 一种融合网关部分和机顶盒部分相互通讯的方法 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201911276978.XA CN111031370A (zh) | 2019-12-12 | 2019-12-12 | 一种融合网关部分和机顶盒部分相互通讯的方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
CN111031370A true CN111031370A (zh) | 2020-04-17 |
Family
ID=70208877
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201911276978.XA Pending CN111031370A (zh) | 2019-12-12 | 2019-12-12 | 一种融合网关部分和机顶盒部分相互通讯的方法 |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111031370A (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115334358A (zh) * | 2022-08-18 | 2022-11-11 | 武汉烽火技术服务有限公司 | 融合网关自动化软件改制方法与存储介质 |
CN115460030A (zh) * | 2022-08-03 | 2022-12-09 | 深圳市华迅光通信有限公司 | 融合网关及其数据处理方法、设备及可读存储介质 |
CN115766687A (zh) * | 2022-11-15 | 2023-03-07 | 四川天邑康和通信股份有限公司 | 一种家庭网关ipv6文件系统及其交互方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102377633A (zh) * | 2010-08-06 | 2012-03-14 | 北京乾唐视联网络科技有限公司 | 一种接入网设备的通信连接方法及系统 |
US20160112448A1 (en) * | 2007-08-30 | 2016-04-21 | Ashbourne Technologies, Llc | System for tracking media content transactions |
CN109104343A (zh) * | 2018-09-30 | 2018-12-28 | 四川长虹电器股份有限公司 | Pon融合型网关stb设备业务建立的优化方法 |
CN109861989A (zh) * | 2019-01-07 | 2019-06-07 | 四川天邑康和通信股份有限公司 | 一种融合网关中pon网关与机顶盒通信的方法 |
-
2019
- 2019-12-12 CN CN201911276978.XA patent/CN111031370A/zh active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160112448A1 (en) * | 2007-08-30 | 2016-04-21 | Ashbourne Technologies, Llc | System for tracking media content transactions |
CN102377633A (zh) * | 2010-08-06 | 2012-03-14 | 北京乾唐视联网络科技有限公司 | 一种接入网设备的通信连接方法及系统 |
CN109104343A (zh) * | 2018-09-30 | 2018-12-28 | 四川长虹电器股份有限公司 | Pon融合型网关stb设备业务建立的优化方法 |
CN109861989A (zh) * | 2019-01-07 | 2019-06-07 | 四川天邑康和通信股份有限公司 | 一种融合网关中pon网关与机顶盒通信的方法 |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115460030A (zh) * | 2022-08-03 | 2022-12-09 | 深圳市华迅光通信有限公司 | 融合网关及其数据处理方法、设备及可读存储介质 |
CN115460030B (zh) * | 2022-08-03 | 2024-01-26 | 深圳市华迅光通信有限公司 | 融合网关及其数据处理方法、设备及可读存储介质 |
CN115334358A (zh) * | 2022-08-18 | 2022-11-11 | 武汉烽火技术服务有限公司 | 融合网关自动化软件改制方法与存储介质 |
CN115334358B (zh) * | 2022-08-18 | 2023-08-22 | 烽火通信科技股份有限公司 | 融合网关自动化软件改制方法与存储介质 |
CN115766687A (zh) * | 2022-11-15 | 2023-03-07 | 四川天邑康和通信股份有限公司 | 一种家庭网关ipv6文件系统及其交互方法 |
CN115766687B (zh) * | 2022-11-15 | 2024-05-28 | 四川天邑康和通信股份有限公司 | 一种家庭网关ipv6文件系统及其交互方法 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6907470B2 (en) | Communication apparatus for routing or discarding a packet sent from a user terminal | |
US8856290B2 (en) | Method and apparatus for exchanging configuration information in a wireless local area network | |
US7808994B1 (en) | Forwarding traffic to VLAN interfaces built based on subscriber information strings | |
US7944918B2 (en) | Dynamic building of VLAN interfaces based on subscriber information strings | |
US7720057B2 (en) | Packet relay apparatus and control method for data relay apparatus | |
US11917399B2 (en) | Zero-touch deployment (ZTD) of cellular IoT devices and associated trust model | |
CN111031370A (zh) | 一种融合网关部分和机顶盒部分相互通讯的方法 | |
CN101179603B (zh) | IPv6网络中用于控制用户网络接入的方法和装置 | |
US20070195804A1 (en) | Ppp gateway apparatus for connecting ppp clients to l2sw | |
EP1670188A2 (en) | Methods and systems for connection determination in a multi-point virtual private network | |
CN101212294A (zh) | 上网认证的实现方法和系统 | |
CN101146051A (zh) | 一种企业级即时通信互联系统及其实现企业互联的方法 | |
US9667483B2 (en) | Method, gateway device and network system for configuring a device in a local area network | |
KR20040080011A (ko) | Epon에서의 인증 방법과 인증 장치과 인증 장치 및상기 방법을 실현시키기 위한 프로그램을 기록한 컴퓨터로읽을 수 있는 기록매체 | |
EP1014628B1 (en) | Packet transfer method and packet transfer system in mobile communication network system | |
WO2011116598A1 (zh) | 一种对网关实现管理的方法及系统 | |
WO2019237683A1 (zh) | 一种协议报文以及虚拟客户终端设备的管理方法 | |
US20050157722A1 (en) | Access user management system and access user management apparatus | |
US20060209723A1 (en) | Network device and management technique of the same | |
US20040255166A1 (en) | Network access system | |
JP2001144812A (ja) | ワイヤレスip端末の認証処理方式 | |
JP2002084306A (ja) | パケット通信装置及びネットワークシステム | |
WO2011153731A1 (zh) | 有线终端的管理控制方法及系统、以及接入服务器 | |
CN100449989C (zh) | 一种触发802.1x认证过程的方法 | |
Cisco | Protocol Translator Manual |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200417 |
|
RJ01 | Rejection of invention patent application after publication |