> For the complete documentation index, see [llms.txt](https://docs.v-nova.com/technologies/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v-nova.com/technologies/mpeg-5.lcevc/carriage/getting-started.md).

# Getting started

In video streaming, *"carriage"* refers to the method by which encoded video data is packaged on the server side and transmitted for playback on the client side. This process involves structuring the video data into compatible formats, applying necessary protocols, and organizing metadata so that the client can decode and render the video smoothly.

This section covers LCEVC carriage solutions and examines their impact on components across end-to-end video systems. It explores how LCEVC integrates with existing streaming ecosystems, from encoding and packaging to playback, and addresses the impacts on each stage of the video delivery pipeline.

{% content-ref url="/pages/k3CjgehtYGN3NAVAOSWs" %}
[Overview of LCEVC carriages](/technologies/mpeg-5.lcevc/carriage/overview-of-lcevc-carriages.md)
{% endcontent-ref %}

{% content-ref url="/pages/UgOs2ARMqlNHtk5bYUVv" %}
[Carriage implementations](/technologies/mpeg-5.lcevc/carriage/carriage-implementations.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.v-nova.com/technologies/mpeg-5.lcevc/carriage/getting-started.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.