An Inter-Working Petri Net Model between SIMPLE and IMPS for XDM Service

Jianxin Liao, Yuting Zhang, Xiaomin ZhuOpenalex Unknown 2008 · DOI · OpenAlex

Abstract

The XML Document Management (XDM) service is increasingly critical as communication becomes more user-centric. Originally emerging alongside Instant Messaging (IM) as Group Management (GM), XDM handles essential personal data like contact lists and user profiles. However, the industry is currently fragmented between two primary standards: SIMPLE (SIP-based) and IMPS (widely deployed but older). While the Open Mobile Alliance (OMA) proposed basic inter-working models, they lack the depth to handle complex XDM data exchange. This paper proposes an enhanced architectural model and a bi-directional protocol mapping to enable inter-working between SIMPLE and IMPS. By applying formal Petri Net modeling, we identify and resolve potential deadlocks, proving the proposed bridge is mathematically sound for real-world implementation.

The Challenge of XDM Inter-Working

In modern messaging ecosystems, XDM acts as a supporting service for IM and Presence, managing the data that allows users to find and interact with one another. The incompatibility between SIMPLE and IMPS creates silos; for instance, a user on a SIMPLE-based network cannot natively view the profile of a user on an IMPS-based network.

Existing OMA models provide a starting point but do not fully address the nuances of XDM service exchange. To solve this, we developed an Inter-Working Function (IWF) that translates between the Extensible Markup Language Configuration Access Protocol (XCAP) used by SIMPLE and the Server-to-Server Protocol (SSP) used by IMPS.

Enhanced Architectural Model

To facilitate this exchange, we introduced an enhanced architecture that adds specific reference points to the standard OMA model. These points, such as IWF-4 and IWF-5, are designed to handle XDM data and search queries specifically.

Enhanced architectural model for inter-working between SIMPLE and IMPS, featuring the Inter-Working Function (IWF).

As shown in the architecture, the IWF serves as the central bridge, communicating with the SIP/IP Core on the SIMPLE side and the IMPS 1.3 Server on the other. This setup allows for the seamless flow of group management and presence data across protocol boundaries.

Protocol Mapping and Formal Verification

A core contribution of this work is the bi-directional mapping of protocol functions. Because a simple 1:1 mapping is not always possible—a phenomenon we call a "soft mismatch"—we defined specific translations for atomic functions like joining groups, retrieving profiles, and searching for users.

Mapping of atomic protocol functions to XCAP request methods used in the SIMPLE standard.

To ensure these mappings do not lead to system failures, we employed Petri Net modeling. Unlike standard flowcharts, Petri Nets allow for the mathematical simulation of concurrent processes. Our initial models revealed "race conditions"—for example, a system hang could occur if a server sends a notification at the exact moment a user unsubscribes.

We resolved these issues by introducing specific transitions, such as the SIP 487 "Request Terminated" response, which allows the system to fail gracefully and reset. Formal analysis using tools like Visual Object Net++ confirmed that the final model is "1-bounded" (safe) and "live," meaning it will never enter an illegal state and will always remain functional.

Key Results and Future Work

The mathematical validation through S-invariant analysis proved that the system state remains consistent during protocol conversion. By resolving deadlocks and livelocks, we have established a robust framework for XDM inter-working.

While this model focuses on SIMPLE and IMPS, the methodology serves as a blueprint for other standards like XMPP. Future research will look toward "Timed Petri Nets" to simulate real-world network latency and jitter, further refining the reliability of these inter-working functions in high-traffic environments.

Summary updated

Abstract

The XDM (XML Document Management) (Open Mobile Alliance, 2006a ; Open Mobile Alliance, 2006c; Open Mobile Alliance, 2006h ; Open Mobile Alliance, 2006l) service is more and more attractive in the age of regarding the user as the communication center. XDM which was ever named GM (Group Management) comes out with the Instant Messaging (IM) service, and manages the personal information, such as contact list, which is the necessary information that IM service needs With the development of XDM service, the information which the XDM server stores will be richer and richer, for example, the personal profile and group information are added to the XDM service. Then the XDM service turns into one of the supporting services from a simple service which just provides the contact for the user. As one of the supporting services, the XDM provides the personal information for the other services which need them, for example, providing the user's personal information for the IM service or Presence service. At present, there are many different appellations of XDM in different standards. Many research institutes and companies have presented their implementations for the XDM service, but the implementations are different and incompatible, so it is hard to inter-work between them. However the inter-working for the services based on XDM service is desired intensively, such as IM, Presence service. There are three main international standards for the XDM service and its relative services: SIMPLE (Session Initiation Protocol for Instant Message and Presence Leveraging Extensions) {1}, IMPS (Instant Messaging and Presence Services) {2} and XMPP (Extensible Messaging and Presence Protocol) (P. Saint-Andre, 2004a ; IMPS has been deployed in many systems for its better maturity, but SIMPLE is more suitable for being deployed in IMS (Internet Protocol Multimedia Subsystem) network, so inter-working between them is becoming a research hotspot in the value-added service field, but recently the research on the topic is just in the initial stage. OMA (Open Mobile Alliance) just proposed a simple Architectural Model (Open Mobile Alliance, 2005a; Open Mobile Alliance, 2005b) for the inter-working between SIMPLE and IMPS, but the architecture can not perform the inter-working for the XDM service. Based on the research on the difference between SIMPLE and IMPS and the OMA's inter-working Architectural Model, we (with the State Key Lab of Networking and Switching Technology of Beijing University of Posts and Telecommunications, and Research Institute of China Mobile) have proposed a bi-directional protocol mapping for use to enable the exchange of XDM
BibTeX
@inproceedings{liao2008inter,
  author = {Jianxin Liao and Yuting Zhang and Xiaomin Zhu},
  title = {{An Inter-Working Petri Net Model between SIMPLE and IMPS for XDM Service}},
  booktitle = {Openalex Unknown},
  year = {2008},
  doi = {10.5772/5313},
}

Loading related content...

Figure