Method for implementing real-time soft bus oriented to intelligent rail transit system

A method for implementing a real-time soft bus oriented to an intelligent rail transit system, wherein the intelligent rail transit system comprises at least one professional subsystem, each professional subsystem accesses a soft bus via at least one control center and/or at least one station;

• a communication front-end processor of each station is configured to interact with a server of the station via different nodes of the soft bus;
• and a communication front-end processor of the control center is configured to interact with a server of the control center via other nodes of the soft bus;
• the soft bus includes a soft bus resource interface, a QoS (quality of service) module and a shared memory;
• the soft bus resource interface includes a transmission plug-in interface, a thread pool container, and an entity creation interface;
• the method comprising:
• defining a data type for interaction between the servers and the communication front-end processors, wherein the data type is a message structure body comprising a message header and a message body;
• structure information of the message header comprises an interface version number, a message sending time, a data check code, source address information, destination address information, and/or a message type;
• the source address information comprises a domain number wherein the source address is located and/or a serial number of the communication front-end processor located at the source address;
• and/or the destination address information comprises a domain number wherein the destination address is located and/or a serial number of the communication front-end processor located at the destination address;
• enabling professional subsystems to construct at least one publisher entity and/or at least one subscriber entity respectively on the soft bus via the entity creation interface, where the publisher entity communicates with its corresponding subscriber entity, and the message structure body is a most basic data transmission unit between the publisher entity and its corresponding subscriber entity;
• the enabling professional subsystems to construct at least one publisher entity and/or at least one subscriber entity comprises:
• registering, by the professional subsystems, entity information to the soft bus when the publisher entity and/or the subscriber entity are/is created on a node of the soft bus;
• publishing the entity information by the soft bus, and enabling other nodes of the soft bus to perform parameter matching after the entity information is received, recording the entity information by the soft bus and returning match information to the corresponding nodes only after match rules are met;
• data isolation of the soft bus is achieved via domains;
• a domain number is specified when the publisher entity or the subscriber entity is created on a node of the soft bus by the professional subsystems, and a unicast or multicast port is calculated by the soft bus according to the domain number;
• after the unicast or multicast port is determined, the publisher entity or the subscriber entity on each node send and receive data on the unicast or multicast port;
• the domain number is set to d (0≤ d≤200);
• when the publisher entity and the subscriber entity match for communication, the multicast port is calculated in the following formula:
• port 1=7720+d×250, where the port 1 is the multicast port, and wherein d is the domain number;
• after the matching, responsive to determining that the publisher entity and the subscriber entity communicate data, the unicast port is calculated in the following formula:
• port 2=7720+d×250+hostId×2, where the port 2 is the unicast port, and wherein d is the domain number, and where the hostId is a serial number of the communication front-end processor where the subscriber entity is located;
• and the multicast port is calculated in the following formula:
• port 3=7720+d×250+1, where the port 3 is the multicast port, and wherein d is the domain number.