> For the complete documentation index, see [llms.txt](https://lillius.gitbook.io/lillius-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lillius.gitbook.io/lillius-white-paper/english/11.-technical-overview/11.1-service-architecture.md).
# 11.1 Service Architecture
This is the comprehensive server configuration (architecture) of the LILLIUS service. The public network includes the training API and the training content section, catering to users' needs. Meanwhile, the private network establishes a link to the blockchain for the data of players who offer training programs.
Phase 1 of the LILLIUS service focuses on supporting the Android/IOS smartphone environment. Phase 2 expands its support to include smart TVs and smartwatches. Phase 3 encompasses multiple devices, including AR and VR devices.
As the above phases progress, the system will also receive updates. Firstly, the exercise evaluation score extraction technology and reward service will be updated. Next, the reward service (T2E) linkage will be adjusted based on exercise results, taking into account the number of exercise participants and user feedback. Lastly, VR sports content and AR exercise lecture services, along with motion analysis technology, will be gradually updated.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://lillius.gitbook.io/lillius-white-paper/english/11.-technical-overview/11.1-service-architecture.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.