Description
Time-Independent Invocation (TII) is a sophisticated mechanism defined within the 3GPP Network Management framework, particularly for the Integration Reference Point (IRP) between a Network Manager (NM) and Element Manager (EM) or Network Element (NE). It allows a management system to issue a command or operation request whose execution is deferred to a specified future time or contingent upon the occurrence of a defined network condition. This decouples the issuance of the management instruction from its actual execution, enabling advanced automation, maintenance window scheduling, and coordinated network changes.
Architecturally, TII operates within the context of the 3GPP Common Object Request Broker Architecture (CORBA)-based or later Web Services-based IRP solutions. A manager (e.g., an OSS) sends an invocation request that includes TII-specific parameters, such as a scheduled start time, an expiration time, or a triggering event condition. This request is received by an agent (e.g., on an EM or NE), which acknowledges the request and stores it as a pending operation. The agent's TII scheduler component then monitors the system clock or subscribed event streams. When the specified time arrives or the triggering condition is met (e.g., a certain alarm clears, or load drops below a threshold), the agent automatically executes the originally requested operation, such as a software upgrade, configuration change, or diagnostic test.
Key components include the TII-capable IRP interface, the scheduler within the agent, and the information model objects representing the scheduled invocations (often managed as "Schedule" objects). The operation execution is transactional; if conditions are not met before expiration, the request may be discarded or trigger a failure notification. TII supports both absolute time scheduling (e.g., "execute at 02:00 AM") and relative time scheduling (e.g., "execute 30 minutes after receipt"). Its role is critical for implementing zero-touch automation, allowing operators to pre-provision massive network changes (e.g., during 5G network slicing rollout) to occur simultaneously during a maintenance window without manual intervention, thereby reducing operational errors and enabling large-scale, synchronized network management.
Purpose & Motivation
TII was created to address significant limitations in traditional, immediate-invocation network management models, which required real-time human intervention or complex external scripting to execute time-sensitive or conditional operations. Prior to TII, scheduling a network-wide configuration update for a low-traffic period required operators to manually initiate jobs at the appointed hour, which was error-prone, not scalable, and impossible for truly synchronized actions across thousands of elements. TII solves this by embedding scheduling and conditional logic directly into the standardized management interface, enabling the network to autonomously execute management actions at precise times or in response to specific network states.
The historical context includes the increasing complexity of 3GPP networks from Release 8 onwards, with the introduction of LTE, Self-Organizing Networks (SON), and later 5G. These networks demanded higher levels of automation for efficiency and reliability. TII provides the foundational capability for advanced SON functions like scheduled optimization, automated healing, and coordinated configuration. For example, a cell parameter change intended to optimize handover performance can be scheduled overnight, or a recovery script can be triggered automatically when a hardware fault is detected.
Moreover, TII supports regulatory and business requirements for maintenance windows and change management processes. It allows operators to plan and approve changes in advance, with the system executing them precisely as scheduled, improving compliance and audit trails. By moving from reactive, manual operations to proactive, scheduled automation, TII reduces operational expenditure (OPEX), minimizes service disruption, and enables the scalable management required for dense, heterogeneous 5G and IoT networks. It is a key enabler for intent-based management and closed-loop automation in modern telecom networks.
Key Features
- Enables deferred execution of management operations at a specified absolute or relative time
- Supports conditional execution based on network event triggers or state changes
- Integrated into 3GPP IRP framework (CORBA/Web Services) for standardized northbound interfaces
- Allows scheduling with start time, expiration time, and recurrence patterns
- Facilitates large-scale, synchronized network changes (e.g., mass configuration updates)
- Provides transactional handling with success/failure notifications for scheduled jobs
Evolution Across Releases
Time-Independent Invocation was initially introduced in the 3GPP Network Management specifications, defining the core architecture, IRP information model, and interfaces for scheduling management operations. The initial capabilities included basic absolute and relative time scheduling, with operations stored as pending invocations on the agent until the scheduled time for execution.
Defining Specifications
| Specification | Title |
|---|---|
| TS 32.373 | 3GPP TR 32.373 |
| TS 32.376 | 3GPP TR 32.376 |