TWCSDVCCMIS212Word文档格式.docx

TWCSDVCCMIS212Word文档格式.docx

《TWCSDVCCMIS212Word文档格式.docx》由会员分享，可在线阅读，更多相关《TWCSDVCCMIS212Word文档格式.docx（28页珍藏版）》请在冰豆网上搜索。

May20,2003

Version0.5,Update,April7,2005

Version1.0,IssuedApril8,2005

Version1.1,IssuedMay10,2005

Version1.2,DRAFTJune14,2005

Version1.3,DRAFTJune30,2005

Version1.4,Issued,July12005

Version1.5,Issued,July14,2005

Version2.0,IssuedJuly20,2005

Filenamechange,resetversionto1.0,August9,2005

Version1.0,Re-issuedAugust26,2005

Version1.1,IssuedSeptember30,2005

Version1.11,IssuedOctober4,2005

Version1.12,IssuedOctober4,2005

Version2.12IssuedOctober12,2005

StatusCode:

WorkinProgress

Draft

Issued

Closed

StatusCodeLegend

WorkinProgressindicatesthatthisisanincompletedocumentdesignedtoguidediscussionandgeneratefeedback,whichmayincludeseveralalternativeproposalsforconsideration.

Draftindicatesthatthisdocumentisinproposalformatandconsideredlargelycomplete,butlackingformalreviewbyteammembers.Draftsaresusceptibletosubstantialchangesduringthereviewprocess.

Issuedindicatesthatthisisastabledocument,whichhasundergonerigorousreviewandissuitableforresponse.

Closedindicatesthatthisdocumenthasbeenreviewed,tested,validated,andclosedtofurtherchangerequests.

RevisionsBlock

Sectionor

proposalrequirement

RevisionDescription

Date

All

InitialdraftbyJH

2/13/2003

Fixedsometypos,JH

RewrotetouseDSMCCmsgs,CM

4/29/2003

AddedServiceGroupIdtoincomingmessagefromclient

5/20/2003

AddactiveTimeandtunerID

2/16/2005

4

DescribedOperationofMiniCarousel,GS

4/8/2005

4.1.2.2

ChangedtunerIDtobeacomponentofsessionID,GS

Released,PDB

5Addendum

AddedCCMISdonatedbyparticipatingvendor

6/1/2005

MergedTWC-SACCMISwiththird-partyproposedCCMIS.ReflectedcommentscanvassedduringreviewwithPDBon6/6/2005.NeedfurtherdiscussiononSDBProgramInitIndicationmessage.RK

6/14/2005

4.3

ChangetoreflectthefacttheClientshallsendtheexactSourceIDforeverychannelchange.TheSourceIDisonlysetto0whentheset-topisturnedofforrecordingends.RK

6/17/2005

4.5,4.6,4.9,4.10

IncorporatedcommentsfromTWC.ModifiedSDBProgramSelectIndication（）toincludecurrentsourceIDaswellasnewsourceIDtotuneto.RK

6/30/2005

Various

ChangedallreferencestobroadcastprogramIDtoSourceID;

Changednamesofvariousmessagestoeliminateunnecessaryinclusionoftheword“program.”-PDB

7/1/2005

4.9,4.9.1

AddedbarkerMessageID0x0000andfixedthetagandlenfieldsofthegenericSDBEventIndicationtobe1byteeach.-RK

7/14/2005

4.9,4.11

AddedsourceIdtoSDBEventIndicationmessagetoallowClienttoproperlyhandleevents.HighlightedthefactthattheClientneednotreinitializewiththesecondarySDVServeruponfailureoforprotectionswitchtotheprimary.-RK

7/18/2005

BaselineReleaseforclientdevelopment

7/20/2005

Nameonly

ChangedfilenamefromTWCSDBMCPtoTWCSDVMCMIS.ResetVersionto1.0

8/9/2005

ChangedallfulltextreferencesfromSwitchedDigitalBroadcasttoSwitchedDigitalVideo;

changedassociatedacronymreferencesfromSDBtoSDV.ChangedreferencesfromMiniCarouselProtocoltoMiniCarouselMessageInterfaceSpecification;

changedassociatedacronymsfromMCPtoMCMIS.Thesechangesareforclarificationofintenttoexternalentities,andnomodificationofscopeormeaningisintended.Notethatforcontinuity,theactualmessagenamesandreferencesretaintheformerusage.Originallyissuedas1.1,nowre-numberedto1.0becausetheversion1.1changes（nextentry）werenotincluded.

8/26/2005

4.1.2.1,4.6,4.9

Removedthefollowingstatementwhichisnolongervalidfromsection4.1.2.1:

“Avalueof0indicatesachanneloutsideoftheSwitchedDigitalVideo.”

Substitutedthefollowingstatement:

“Avalueof0indicatesaninvalidsourceID.”

Forexample,iftheSDVServersendsanSDBSelectIndicationmessagetotheclientindicatingProgNotAvailable,thevalueofthesourceIDwouldbezerointhiscase. 

Likewise,whentheServersendstheSDBQueryRequestmessagetotheclient,buttheclientiscurrentlyonanon-videochannelforwhichthereisnosourceID,theclientwouldneedtoreportavalueofzeroforthesourceIDintheresponse.

_____________________________________

Insection10.2.1oftheDSM-CCspecification,theSDVPrivateDataisdefinedtoalwaysstartwithprivateDataLength（2bytes）.IntheCCMISspecification（2.0）:

Insection4.6SDBProgramSelectResponse,thePrivateDatastructurewasempty.Ithasnowbeensettoa2-byteprivateDataLengthfieldwithvalue0.Likewise,insection4.9SDBEventIndication,thefirstfieldofthePrivateDatawassourceId（4bytes）.TheprivateDataLengthhasbeenplacedbeforethesourceIdforconsistencywiththeDSM-CCspecification.

9/30/2005

Addedclarificationtosection4.1.2.2abouttheformatofthesessionIDfieldofCCMISmessages.–RK

Correctedversionnumberingofinitial1.1release,-PDB

10/4/2005

4.3,4.5

HarmonizedformatofsessionIDinsection4.3andthatofsection4.1.2.2.ItisimportanttoformatthesessionIDasdescribedinsection4.1.1.2and4.3toensurecompatibilitybetweenSDVClientandServer.

____________________________________

UpdatedprivateDataLengthfieldto0x0Einsection4.5.-RK

NameOnly

Duetosimultaneousupdateissue,filenameandreferenceswereinadvertentlyresetbacktoSDB.Thisreleasecorrectsthisissue,andchangesversionnumberfrom1.12to2.12.Otherwise,theseversionsaretechnicallyidentical.

10/12/2005

Contents

TimeWarnerCableSwitchedDigitalVideoi

ChannelChangeMessageInterfaceSpecificationi

1USINGTHISDOCUMENT8

1.1AddingContent8

1.2CommentingorResponding8

1.3ChangesandRevisions8

2INTRODUCTION9

2.1PurposeOfDocument9

2.2ScopeOfDocument9

2.3Audience9

2.4DocumentConventions9

2.5References9

3NetworkConnection10

4MessageSpecifications11

4.1DSMCCStandardMessageandStandardFields11

4.1.1.Header11

4.1.1.1.MessageID12

4.1.2.StandardFields13

4.1.2.1.SourceId13

4.1.2.2.SessionId13

4.1.2.3.ReasonandResponse13

4.2MessageFlow14

4.3SDBProgramSelectRequest15

4.4SDBProgramSelectConfirm17

4.5SDBProgramSelectIndication21

4.6SDBProgramSelectResponse23

4.7SDBQueryRequest26

4.8SDBQueryConfirm26

4.9SDBEventIndication28

4.9.1.BarkerMessageDescriptor29

4.9.2.TunerUseChangedDescriptor30

4.10SDBEventResponse31

4.11SDBInitRequest31

4.12SDBInitConfirm34

4.13SDBUserActivityReport35

1USINGTHISDOCUMENT

ThisdocumentisintendedtobeaworkingdocumentinwhichreviewersmakecommentsviaE-mail,additionalsourcedocuments,orVisio/rose/etc.diagrams.

Pleaseaddcommentsandcontentaccordingtothefollowingdirections:

1.1AddingContent

YoucanaddcontenttothisdocumentbysendingPaulBrooksE-mail（Paul.Brooks@TWC）,worddocuments,orcopiesofthisdocumentwithcommentsintheareasofconcern.PaulwillreviewthecommentsattempttoaddthechangesASAPandmaketheupdatesavailableonatimelybasis.

1.2CommentingorResponding

ThisdocumentcanbeusedinsomeinstancesasacommunicationmediumbetweenTimeWarnerCableteammembersanddevelopmentpartners.Commentsandresponsescanbeincludedinthetext.Comments/responsesshouldconcernunresolvedissuesortheyshouldcontainalternativeproposalsfordiscussion.Pleasebegineachcommentandresponse（paragraph）withyourinitials（e.g.,PB）.

1.3ChangesandRevisions

ChangesarelistedintheRevisionsBlock,locatedbeforetheTableofContents.Documentnumberwillbeincrementeduponrelease.Changessincelastissuewillbeindicatedbychangebarsonleft.

2

INTRODUCTION

2.1PurposeOfDocument

ThepurposeofthisdocumentistospecifytheSwitchedDigitalVideoChannelChangeMessageInterfaceSpecification.ThisinterfaceoperatesbetweentheSwitchedDigitalVideo（SDV）ServerandtheSDVClientrunningonasettopbox.ThisinterfaceprovidesamechanismforchangingchannelsintheSwitchedDigitalVideoService.

2.2ScopeOfDocument

ThisscopeofspecificationislimitedtothechannelchangeoperationperformedinaSwitchedDigitalVideosystem.

2.3Audience

Thefollowinggroupsaretheprimaryaudiencesforthisdocument:

vVendorssupplyingcomponentsoftheSwitchedDigitalVideoSystem

vImplementersoftheSwitchedDigitalVideoServerandclient

vEngineerstestingtheSwitchedDigitalVideoSystem

2.4DocumentConventions

Thisspecificationusesthefollowingconventionstoalertyoutospecificinformation:

Note:

　Thiscontainsimportantinformationaboutthetopicitisassociatedwith.

SeeAlso:

　Thisisacrossreferencetorelatedinformation.

2.5References

1.ISO/IEC13818-6MPEG-2DigitalStorageMediaCommandandControl（DSM-CC）

3

NetworkConnection

TheSDVCCMISisaclient-serverbased,connectionless,messagingprotocolintendedforchannelchangeoperationsinaSwitchedDigitalVideosystem.TheserverisimplementedinaSDVServer.Theclientisimplementedinasettopbox（STB）.

TheCCMISiscarriedoverUDP/IP,whichisconnectionlessand