> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/core-concepts.md). # 核心概念了解 Convai Unity SDK 在运行时如何工作——连接、会话、具身化、对话状态以及事件驱动响应。 “核心概念”部分解释了你场景中每个 Convai 角色底层运行的系统——管理连接的运行时层、管控每个角色生命周期的会话状态机、驱动凝视和情绪等模块的按角色具象层、控制谁在何时发言的轮流发言系统，以及让你的场景对运行时发生的事情做出反应的事件组件。先从 **运行时架构** 如果你刚接触 SDK 内部实现。需要配置某个特定系统，或想了解 SDK 为什么会以某种方式运行时，请阅读其他页面。


运行时架构运行时层、接口清单，以及你可以替换的内容。	运行时架构
会话生命周期状态机、按角色的会话、持久化和重新连接。	会话生命周期
角色 Embodiment 每个角色的组合根、确定性 tick，以及 Animator 和面部混合形状的单写入者规则。	角色具身化
对话状态每个具象化模块都会读取的八值对话状态模型。	对话状态
资源所有权与写时复制为什么编辑随包提供的配置文件会创建项目副本，而不是直接原地编辑。	资产所有权与写时复制
轮流发言模式免提模式与按键发言模式——逐项解释每个字段和策略。	轮流发言模式
语音活动检测服务器默认阈值与自定义检测阈值在连接时确定。	语音活动检测
事件系统中继组件、负载类型和订阅模式。	事件系统

--- # 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.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/core-concepts.md?ask=&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.