Please enable JavaScript.
Coggle requires JavaScript to display documents.
Ku Comm Unit:
OPERATIONS (INTERNET PROTOCOL (IP) RECORDING PROFILES…
Ku Comm Unit:
OPERATIONS
-
INPUT CONFIGURATION:
A). First "stop" for all data entering the Ku Comm Unit is the input channel
- The following settings are required for each input channel and is uniquely configured for each source:
- Bandwidth: How many Mbps the channel is allowed to use. This bandwidth will be reserved for this channel and will always be available.
- Overrun: How many Mbps the channel will be allowed to use if extra bandwidth is available. This bandwidth is not guaranteed.
- Data Type: What kind of data is on this channel? (CCSDS, Video, Audio, IP Encap, Bitstream)
- Record Mode: Determines if and how the Ku Comm Unit will record the data. (Manual, Auto_Record, Auto_Ops)
B). The input channel must be configured before anything else can be done of the Ku Comm Unit with the data on the channel.
BANDWIDTH:
- Total Usable Bandwidth of 259.6 Mbps
- Amount is split between the 103 input channels and the six dump channels
- If attempt to exceed this limit, the command will be rejected
- Overrun does not count against the 259.6 Mbps limit
- Dumping from the MMU, the software will use up all available bandwidth even if that bandwidth has been reserved.
-
RECORD MODE
-
- Manual
- Manual recording is controlled solely by operator command
- Auto Record
- Auto Record causes all source channels to automatically be recorded when an LOS event occurs if the channel is mapped to a non-zero Record Chanel ID.
- Auto Ops
- In Auto Ops mode, the channels set to Auto Ops begin recording when an LOS event occurs if the channel is mapped to a non-zero Record Channel ID and stops recording once the Ku-band signal is reacquired and the LOS period ends.
B). Auto Record and Auto Ops recording is based on the Modem SBC detecting AOS/LOS.
- The Ku Comm Unit determines AOS/LOS by the status of the Ku Forward link.
STORAGE MANAGEMENT
- In order to record data on an input channel, the input channel must be mapped to a Record Channel ID
- Each Record Channel ID with record data must be mapped to a Dump Channel before the data can be dumped
- There are six dump channels that can be individually configured and operated simultaneously.
- Minimum Dump Rate: This is the amount of bandwidth reserved for this dump channel.
- Data Type: Each dump channel can only be configured to a single data type at a time.
- A dump channel configured to IP Encap can be used to dump Video, Audio, and IP Ecap data
- Virtual Channel: This sets the virtual channel the dump channel will use to down-link its data
- REMEMBER when dumping data or video from the MMU, the Ku Comm Unit will automatically use available bandwidth in the Ku return link. This allows the MMU to dump as much data as possible without wasting any bandwidth or requiring extra configuration
-
-
DATA/VIDEO DUMPS
- Each Record Channel ID can only be in a single record/dump/delete state at a time
A).The Ku Comm Unit can be commanded to begin recording a given Record Channel ID while a dump for that channel is in progress.
B).The Ku Comm Unit can be commanded to begin dumping data or video from a Record Channel ID while that channel is in record mode.
C).NOTE: The Ku Comm Unit Record Channel ID must not be recording or dumping in order for a delete command to be successful on the channel.
D). For individual Record Channels, data/video can be dumped for a specified time range.
-
-