SONY's Proposal for
FIMS NAB Demo
FIMS Demo Overall Scenario [Idea]
one slot (30 Min)
5min.
General
Presentation
(PowerPoint)
10min.
Workflow
Demonstration
(Proto System)
10min.
Q&A
Margin
FIMS Workflow Demonstration [Plan A] (Idea)
Primary Capture Service
Cinegy
Capture
Loudness Optimization
Service
Ingest Service
Cube Tec
Transform
Avid
Ingest
Protocol?
MXF AS-02
VC-3/PCM
Secondary Capture Service
Protocol?
Sony
Capture
[TBA]
Transform
MXF AS-02
VC-3/PCM'
Playback two files
FTP
MXF OP1a
MPEG2/PCM
System A
Cinegy
Cube Tec
Avid
System B
Sony
Transform
Cube Tec
Avid
time
FIMS Workflow Demonstration [Plan A]
1.
Assign one Capture service as the primary service, the other as the
secondary service
–
i.e. Cinegy Capture as the primary, Sony Capture as the secondary
2.
IBM and Sony Orchestration systems use exactly the same workflow.
3.
IBM (or Sony) orchestration system starts operation first, Sony (or IBM)
orchestration system starts 5-10 seconds later.
4.
IBM (or Sony) system chooses Cinegy service for Capture service, and
Sony (or IBM) system chooses Sony service as Cinegy service is not
available.
5.
[TBA] service transforms from output of Sony service "MPEG-2 long
GOP/OP1a" to "VC-3/AS-02" format.
Cube-Tec service optimizes audio loudness in files created by both Cinegy
service and [TBA] transfer service in turn.
Avid service ingests files created by Cube-Tec in turn.
Avid service plays back two files manually for confirmation.
6.
7.
8.
Constraints of FIMS Workflow Demonstration
1.
Polling approach
–
2.
3.
4.
One Input
One Output
No Queuing
–
5.
NB Stop message not used. Also, it will be easy to obtain “Progress”
percentage if the duration is known beforehand.
Progress report
–
7.
When a service is not available, it simply returns error as ACK rather than
entering into queue.
Combination of “NoWait” and “Duration” to be used as the way to specify
IN/OUT in the case of capture service.
–
6.
Response message not in use
Regardless of its precision.
Structure of Profile
– format ID
– techMetadata (EBU Tech. 3293)
– destination
FIMS Workflow Demo Sequence Chart [Plan A]
IBM
Webspher
SONY
MBB
Cinegy
Capture
CaptureRequest
CaptureAck (status = running)
CaptureRequest
CaptureFault (code = ?)
CaptureRequest
CaptureAck (status = running)
QueryJobRequest
QueryJobResponse (status = completed)
TransformRequest
TransformResponse (status = running)
QueryJobRequest
QueryJobResponse (status = completed)
TransformRequest
TransformAck (status = running)
QueryJobRequest
QueryJobResponse (status = completed)
TransformRequest
TransformResponse (status = running)
QueryJobRequest
QueryJobResponse (status = completed)
TransformRequest
TransformAck (status = running)
QueryJobRequest
QueryJobResponse (status = completed)
QueryJobRequest
QueryJobResponse (status = completed)
TransformRequest
TransformAck (status = running)
QueryJobRequest
QueryJobResponse (status = completed)
SONY
Capture
[TBA]
Transform
CubeTeck
Transform
Avid
Ingest
- IBM/Sony Orchestration system keeps polling operation until status is complete using
QueryJobRequest/Response.
- IBM/Sony Orchestration system starts operation (send CaptureRequest) manually.
- Once operation is started, moving next job is processed automatically when a job is
completed.
- IBM/Sony Orchestration system keeps sending Request if a service is not available
(receive Fault) until it is available.
Outstanding issues on Plan A
• Transform Service (TBA)
– Must retrieve MXF file from Sony Capture service as FTP client
– Must support MPEG-2 Long GOP/RDD9 as an input file
– Must support VC-3/AS-02 as an output file
• Ingest Service (Avid)
– In addition to VC-3/AS-02, can MPEG-2 Long GOP (RDD9)/AS-02 be
supported as an input file?
• In order to avoid any risks in essence compatibility, a backup
plan should be implemented from the beginning. (See next slide)
– In this case, MPEG-2 Long GOP (RDD9)/OP1a also needs to be
supported as an input file by Avid
FIMS Workflow Demo Scenario [Backup Plan] (Idea)
Avid Ingest Service directly ingests files from output files of both Cinegy and Sony Capture services.
Transform Services ([TBA]/Cube Tec) do not perform any service but accept request messages and
return the appropriate messages as it they were actually performed.
These special messages should be defined for the backup plan.
Primary Capture Service
FTP?
Cinegy
Capture
Loudness Optimization
Service
Ingest Service
Cube Tec
Transform
Avid
Ingest
Protocol?
MXF AS-02
VC-3/PCM
Secondary Capture Service
Protocol?
Sony
Capture
MXF OP1a
MPEG2/PCM
MXF AS-02
VC-3/PCM'
[TBA]
Transform
Playback two files
FTP
Proposed Plan for providing Pre-Defined Messages
• Pre-defined Message (WSDL, SOAP) will be created based on
the v03 WSDL released by IBM.
• Sony to provide tentative release of WSDL, SOAP messages
three business days after obtaining v03 WSDL.
• IBM to check WSDL, SOAP messages (?) business days after
tentative release.
After three business days
IBM to release
v03 WSDL
After (?) business days
Sony to provide
tentative release
of WSDL, SOAP
for IBM checking
IBM to provide
official release of
WSDL, SOAP
Other issues to be discussed
• Date and Place for starting connection test at the NAB venue.
– At least four days before NAB show starts, i.e. 7th Apr.
• Complete equipments list
– Including Ethernet Switch, cables, Power extension etc.
– Total size, power are important.
• Network Setting
– IP address
• Pre-defined static IP address is preferred, i.e. 172.16.12.xx
– IBM ESB and Sony ESB share same Ethernet?
• Same Ethernet is preferred.
– ESBs and Media Bus share same Ethernet (or other bus)?
• Same Ethernet is preferred.