Skip to content
  • Tools
    • ARFCN-Frequency Converter
  • Contact Us
  • Foreword
  • 1 Scope
  • 2 References
  • 3 Definitions and abbreviations
  • 4 Open Service Architecture
  • 5 Methodology
  • 6 Class diagrams
    • 6 Class diagrams
    • 6.1 Class diagrams common across OSA
    • 6.2 Class diagrams for the Framework
    • 6.3 Generic Call Control
    • 6.4 Generic User Interaction and Call User Interaction
    • 6.5 Data Session Control
    • 6.6 Network User Location
    • 6.7 User Status
    • 6.8 Terminal Capabilities
  • 7 State Transition Diagrams
    • 7 State Transition Diagrams
    • 7.1 Framework
      • 7.1.1 IpAuthentication
      • 7.1.2 IpAccess
      • 7.1.3 IpServiceDiscovery
      • 7.1.4 IpLoadManager
      • 7.1.5 IPFaultManager
      • 7.1.6 IpHeartbeatmgmt
      • 7.1.7 IpHeartBeat
      • 7.1.8 IpOAM
      • 7.1.9. IpServiceRegistration
    • 7.2 Generic Call Control
    • 7.3 User Interaction
    • 7.4 Data Session
    • 7.5 Network User Location
    • 7.6 User Status
  • 8 Data Definitions
  • 9 IDL Interface Definitions

7.1.7 IpHeartBeat

29.1983GPPOpen Service Architecture (OSA) Application Programming Interface (API) - Part 1Release 1999TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

Figure 7-8: State Transition Diagram for HeartBeat

7.1.7.1 FW Supervised by Application state

In this state the Framework has requested the application for heartbeat supervision on itself. Periodically the application calls the send() method and the Framework returns it’s heartbeat result.