Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

SOBOT

Service Robot

Services →

SOBOT is a 3GPP use case category for 5G-enabled robotic services, covering communication requirements and architecture for robots performing tasks in commercial, industrial, and domestic environments.

Introduced
Rel-19
Where
Services
Specifications
1 specs
SOBOT Description Purpose Neighbours Specifications

Description

SOBOT (Service Robot) is a term introduced in 3GPP Release 19 within the context of study on service robot communications, documented in TR 22.916. It refers to robots that perform useful tasks for humans or equipment, excluding industrial automation applications (which are covered separately under industrial robotics). Service robots encompass a wide range of applications, including domestic robots (vacuuming, lawn mowing), professional service robots (medical, logistics, cleaning, agriculture), and collaborative robots in public spaces. The 3GPP study aims to identify communication requirements and potential enhancements to 5G systems to support these robots efficiently.

Service robots typically require wireless connectivity for remote control, teleoperation, data offloading (e.g., sensor data, video), software updates, and coordination with other robots or cloud services. The communication needs vary widely: some robots require high reliability and low latency for real-time control, while others need high bandwidth for video streaming or large data transfers. The SOBOT study in TR 22.916 analyzes use cases such as robot teleoperation, autonomous navigation, fleet management, and human-robot interaction, and derives requirements for 5G networks.

Architecturally, service robots can connect to the 5G network either directly via embedded 5G modules or indirectly via gateways (e.g., Wi-Fi or proprietary radio to 5G). The study considers both scenarios and evaluates how 5G features such as network slicing, edge computing, and QoS frameworks can be applied. For example, a robot performing teleoperation may require a dedicated network slice with ultra-reliable low-latency communication (URLLC) characteristics, while a robot uploading sensor data may use enhanced mobile broadband (eMBB) or massive machine-type communication (mMTC) services.

The SOBOT study also examines the role of edge computing to reduce latency by hosting robot control functions at the network edge. It considers the need for seamless mobility as robots move across different coverage areas, and the potential for group communication among robot fleets. Security and privacy are also addressed, particularly for robots operating in sensitive environments such as hospitals or homes.

How it works: a service robot establishes a connection to the 5G network, either via a direct 5G modem or through a gateway. The network assigns appropriate QoS flows based on the robot's communication needs, which may be signaled by the robot application or configured by the operator. The robot can communicate with a remote controller, cloud service, or other robots. The 5G system provides the necessary reliability, latency, and throughput, potentially leveraging network slicing to isolate robot traffic from other services. The SOBOT study identifies gaps in current 5G specifications and proposes enhancements for future releases.

The SOBOT term is part of 3GPP's broader effort to expand 5G into new vertical domains beyond traditional mobile broadband. It reflects the growing interest in robotics and the need for standardized communication solutions to support the diverse requirements of service robots.

Purpose & Motivation

The SOBOT study and term exist to address the communication needs of the rapidly growing service robot market. Service robots are increasingly deployed in homes, hospitals, warehouses, and public spaces, and they require reliable, low-latency, and often high-bandwidth connectivity. Existing 5G specifications were primarily designed for human-centric communication and may not fully optimize for robot-specific requirements such as deterministic latency, high reliability, and efficient group communication.

The motivation for SOBOT comes from the recognition that robots have unique communication patterns: they may need to send periodic sensor data, receive real-time control commands, and coordinate with other robots. These patterns differ from those of smartphones or IoT devices. Without a dedicated study, 3GPP risked missing opportunities to tailor 5G features for robotics, leading to suboptimal performance and fragmented solutions.

SOBOT also addresses the need for interoperability and scalability. As robots become more prevalent, networks must handle large numbers of robots efficiently. The study explores how 5G features like network slicing, edge computing, and advanced QoS can be leveraged to support robot fleets. By identifying requirements and gaps, SOBOT paves the way for future 3GPP releases to enhance 5G for service robots, ensuring that the technology can meet the demands of this emerging vertical.

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-19 Initial

Initial study of service robot communications in TR 22.916, defining use cases, requirements, and potential 5G enhancements for service robots.

Defining Specifications

3GPP specifications that define or reference SOBOT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 22.916 vj00 Study on Network of Service Robots with Ambient Intelligence Rel-19 read