Digital program control dispatching system

Abstract

This invention relates to the field of digital communication technology and discloses a digital program-controlled scheduling system, comprising the following steps: defining the start and end times and core participants of scheduling events through a multi-functional dispatch console; receiving and standardizing call details from the scheduling exchange host, operation logs from the multi-functional dispatch console, and recording metadata from the digital recording subsystem in real time via an event log and correlation engine; and automatically determining whether each communication record belongs to the current active event in terms of time and participants through a correlation function. This invention includes an event log and correlation engine that executes the above method, and a system maintenance terminal that can retrieve and centrally present all correlated records within a communication scenario on a unified timeline. This invention achieves automated, real-time correlation and aggregation of multi-source heterogeneous communication data related to scheduling events, improving the efficiency and completeness of event backtracking, and providing an intuitive and accurate global view for post-event analysis.

Description

Technical Field

[0001] This invention relates to the field of digital communication technology, and in particular to a digital program-controlled scheduling system. Background Technology

[0002] Currently, digital program-controlled dispatching systems, as a key communication platform for modern command, production, and management, are widely used in important fields such as public safety, transportation, energy and power, and aerospace. The core function of these systems is to provide efficient and reliable voice dispatching services to specific user groups, such as individual calls, group calls, conferencing, and broadcasting. To ensure operational traceability and meet the needs of accident analysis and liability determination, dispatching systems typically generate and store various communication records during operation.

[0003] However, in existing technologies, these critical communication records are often generated and managed by functionally independent subsystems. For example, the dispatching switch host is responsible for generating call details that record information such as the caller, the called party, and the call time; the digital recording subsystem captures the audio stream of the call through listening or bridging, generating recording files and corresponding recording metadata; and the specific operations performed by the dispatcher on the multi-functional dispatch console are also recorded in the behavior log.

[0004] Regarding the aforementioned technologies, this multi-source, heterogeneous data generation model leads to a significant technical drawback: various records are physically and logically separated, forming individual data sets. When a complete retrospective analysis of a specific scheduling event is required, management or investigators must manually perform tedious searches in databases or log files across different systems. They need to first filter relevant calls in the call detail record system based on approximate time, then search for corresponding audio files in the recording system based on the call information, and simultaneously compare the dispatch console's operation logs to understand the context of the call. This process is not only time-consuming, labor-intensive, and inefficient, but also highly susceptible to errors or omissions of key information due to human negligence, making it difficult to quickly and intuitively reconstruct the full picture of the event and the causal relationships between various operations, especially in complex and intensive scheduling scenarios. Summary of the Invention

[0005] The purpose of this invention is to provide a digital programmable scheduling system that solves the problem that various communication records are generated and stored separately by independent systems, forming individual data sets. This makes it necessary to rely on manual retrieval and comparison between different systems for the retrospective work of specific events. This is not only time-consuming and laborious, but also prone to errors and omissions, and makes it difficult to quickly and intuitively reconstruct the full picture of the event.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a digital program-controlled scheduling system, characterized in that it comprises:

[0007] The scheduling switching host is used to handle call setup and generate call details;

[0008] A multi-functional dispatch console is used by dispatchers to perform dispatching operations and create event tags to define a dispatching event;

[0009] A digital recording subsystem, connected to the scheduling and switching host, is used to record calls and generate recording metadata;

[0010] An event log and association engine is used to respond to the creation of event tags for the scheduling event, receive the call details and the recording metadata, and associate the received call details and the recording metadata with the event tags of the scheduling event, thereby generating a communication scenario corresponding to the scheduling event.

[0011] The system maintenance terminal is connected to the event log and association engine and is used to retrieve and trace the communication scenario based on the event tags of the scheduling event.

[0012] Through the above technical solutions, a complete closed-loop system is constructed, which organically integrates the originally scattered and heterogeneous communication record sources through a core association engine. It realizes the automatic aggregation from scattered raw communication records to structured communication scenarios with scheduling events as the core, fundamentally solving the problems of data isolation and difficulty in backtracking in existing technologies, and realizing one-click complete reproduction of specific events.

[0013] Preferably, the event log and association engine are specifically used for:

[0014] Obtain the start time, end time, and core participant set of the scheduling event defined by the event label of the scheduling event;

[0015] Define a communication record that includes call details and recording metadata.

[0016] When the occurrence time of the communication record is between the start time and the end time, and the participants in the communication record have an intersection with the core participant set, the communication record is associated with the event tag of the scheduling event, and the communication record is classified into the communication scenario.

[0017] The above technical solution clarifies the core of the association logic, namely, by setting a time window and a set of participants as dual filtering conditions, the automation and accuracy of the association process are ensured. It can accurately filter and collect relevant communication records into the correct event scenarios, avoiding oversights and errors in human judgment.

[0018] Preferably, the multi-functional dispatch console is also used to generate a dispatch operation log that records the dispatcher's operations;

[0019] The event log and association engine is also used to receive the scheduling operation log, associate the scheduling operation log with the event tag of the scheduling event, and classify it into the communication scenario.

[0020] By employing the aforementioned technical solutions, the dispatcher's subjective operational behavior is incorporated into the data dimension of the communication scenario. This allows the retrospective analysis to not only see what happened during the call but also understand why such a call occurred, providing crucial contextual information for comprehensive event analysis and making the scenario reconstruction more complete and in-depth.

[0021] Preferably, the multi-functional dispatch console is equipped with a dedicated event management interface, which is used for dispatchers to activate or terminate the event tags of the dispatch events and input descriptive information for the event tags of the dispatch events.

[0022] The above technical solution provides dispatchers with a clear and convenient human-computer interaction interface, enabling precise control of the event lifecycle and the addition of necessary textual descriptions, which greatly improves the operability and flexibility of the event definition process.

[0023] Preferably, the event log and association engine includes a structured storage unit, which persistently stores the communication scenario by establishing an event table, a communication record table, and an association table between events and records.

[0024] The above technical solution, employing relational database design principles, ensures the structured, standardized, and efficient storage of data. By separating entity tables and dedicated relational tables, not only is data integrity and consistency guaranteed, but subsequent query and retrieval speeds are also significantly optimized, providing a solid data structure foundation for rapid backtracking.

[0025] Preferably, the scheduling and switching host includes a main control unit and a power supply unit. Both the main control unit and the power supply unit adopt a dual hot backup mechanism to ensure that the generation of call details is not interrupted when the main unit fails.

[0026] The above technical solutions, through redundant backup design, improve the reliability and business continuity of the system, ensuring that the call processing and detailed billing functions of the system are not affected when a single point of failure occurs in the core hardware, thereby guaranteeing the integrity and uninterrupted recording of the original communication data.

[0027] Preferably, when the system maintenance terminal traces back the communication scenario, it will associate and present all communication records associated with the event tag of the same scheduling event on a unified timeline.

[0028] The above technical solution provides an intuitive and easy-to-understand data visualization method. By presenting multi-source, heterogeneous records in a unified chronological order, it helps those conducting background checks to grasp the complete timeline of events and the temporal relationships between various records at a glance, greatly reducing the complexity of information interpretation.

[0029] Preferably, the set of core participants is determined by at least one method, wherein the method is:

[0030] The event label is specified in advance by the scheduler when creating the scheduled event;

[0031] The event log and association engine automatically identify the participants in the initial call associated with the scheduling event.

[0032] The above technical solution provides a flexible and intelligent mechanism for determining participants. Manual assignment is suitable for pre-planned scheduling tasks, while automatic identification can adapt to unexpected events. The system can autonomously capture key roles from initial communications, reducing reliance on scheduler operations and enhancing the system's automation level.

[0033] Preferably, the digital recording subsystem is used to push the generated recording metadata to the event log and association engine in real time, supporting dynamic association during the scheduling event.

[0034] The above technical solution ensures that recorded data can be incorporated into the event context for correlation in near real-time. Compared to the engine's timed pull mode, this push mode has lower latency, allowing the entire correlation process to dynamically synchronize with the event's progress, laying the foundation for near real-time event monitoring and backtracking.

[0035] Preferably, the scheduling operation log generated by the multi-functional scheduling console includes: operation records of forced insertion, forced disconnection, or meeting convening.

[0036] The above technical solution clarifies the key dispatching operation types that need to be recorded. These operations are often high-level authority actions by dispatchers to intervene in and control the communication situation. Recording them is of irreplaceable value for understanding the dispatcher's decision-making intentions at critical moments and reconstructing the command process.

[0037] In summary, the present invention has at least one of the following beneficial technical effects:

[0038] 1. This invention establishes an event log and an association engine. This engine responds to event tags created by the dispatcher on the multi-functional dispatch console, automatically associating communication records from multiple sources, including call details from the dispatch switching host, recording metadata from the digital recording subsystem, and dispatch operation logs, to form a structured communication scenario. This design solves the technical problem in existing technologies where various communication records are stored independently and in a scattered manner, making effective post-event association difficult.

[0039] 2. Based on the generated communication scenario, this invention allows for the retrieval and backtracking of the complete communication process of a specific scheduling event through a system maintenance terminal, using a unique event tag for each scheduling event. This method can present all records related to a single event in a unified view with contextual association, improving the efficiency, accuracy, and completeness of event review compared to the traditional method of manually comparing time points across different systems to piece together information.

[0040] 3. This invention transforms the originally discrete and unstructured communication data streams into structured data archives centered on specific business events. This structured communication scenario provides an objective, complete, and easily analyzable data foundation for subsequent management activities such as scheduling process optimization, emergency plan evaluation, or responsibility definition, making data-driven management decisions possible. Attached Figure Description

[0041] Figure 1 This is a schematic diagram of the overall process of the digital program-controlled scheduling system of the present invention;

[0042] Figure 2 This is a flowchart illustrating the generation and backtracking of the scheduling event communication scenario according to the present invention;

[0043] Figure 3 This is a schematic diagram of the scheduling and switching host of the present invention;

[0044] Figure 4 This is a flowchart illustrating the multi-functional dispatch console of the present invention;

[0045] Figure 5 This is a flowchart illustrating the digital recording subsystem of the present invention;

[0046] Figure 6 This is a flowchart of the event log and association engine of the present invention;

[0047] Figure 7 This is a schematic diagram of the system maintenance terminal function flow of the present invention;

[0048] Figure 8 This is a schematic diagram of the communication scenario process of the present invention. Detailed Implementation

[0049] The following is in conjunction with the appendix Figure 1 -Appendix Figure 8 The present invention will be further described in detail below.

[0050] This invention provides a digital program-controlled scheduling system comprising the following modules:

[0051] The dispatching and switching host includes: an interface unit, a digital switching network unit, and a call control and signaling processing unit.

[0052] An interface unit provides the physical connection and signal conversion between the dispatching switch host and external communication equipment. In one embodiment, this interface unit consists of various pluggable service boards, such as a subscriber line interface circuit for connecting analog telephone terminals. This circuit provides functions such as power supply, overvoltage protection, ringing signals, on / off status monitoring, analog-to-digital and digital-to-analog conversion, and two-to-four-wire conversion for the analog telephone. A digital trunk interface circuit connects to the public switched telephone network or other dedicated switching networks via E1 or T1 lines. This circuit is responsible for frame synchronization, time slot extraction, and physical layer code conversion of 2.048Mbps or 1.544Mbps signals.

[0053] A digital switching network unit, connected to an interface unit, is used to establish a real-time bidirectional communication channel between ports within the system. In one embodiment, the digital switching network unit is a non-blocking time-division multiplexing switching matrix. When a call needs to be established between two ports, the call control and signaling processing unit controls the switching matrix to switch the 8-bit data sample of the pulse code modulation (PCM) data stream input to one port to the target time slot of the PCM data stream output to the other port in the next frame period, and vice versa, thereby constructing a 64kbit / s full-duplex voice channel.

[0054] The call control and signaling processing unit is connected to both the interface unit and the digital switching network unit via a control bus. This unit is the control core of the scheduling switching host, responsible for executing all call processing logic. Internally, this unit maintains an independent finite state machine for each port in the system. The finite state machine defines all possible port states, such as idle, off-hook, dialed, ringback, and talk states. Transitions between states are driven by line events or signaling messages reported by the interface unit.

[0055] The call control and signaling processing unit also includes a call detail record generation module. This module is triggered at specific points in the call flow to generate a detailed record of the call. The call detail record generation module is activated when a port's finite state machine transitions from a call state to any call termination state.

[0056] Call details generated by the call details generation module It is a piece of structured data, and its data structure can be defined as:

[0057] ;

[0058] The symbols are defined as follows: The caller's number; The number of the called party; The timestamp for establishing the call. The timestamp for establishing the call is in the call status.

[0059] The moment the device first enters call mode is accurately recorded; This is the timestamp when the call ended. This timestamp is precisely recorded when the call state machine leaves the call state. The duration of the call, its value is determined by... - The calculation yielded the result.

[0060] The call detail record generation module generates a complete call detail record. Then, the data record is sent to the event log and correlation engine in real time and reliably through a preset TCP or IP interface.

[0061] The multi-functional dispatch console includes: a human-computer interaction module, a local processing and control module, and a communication interface module.

[0062] The human-computer interaction module serves as the medium for dispatchers to perform physical operations and obtain information. In one embodiment, the physical part of this module includes a programmable key array, where each key is a direct dispatch selection key and integrates a dual-color or tri-color LED to indicate different states such as idle, ringing, and talking on the corresponding user line. The human-computer interaction module also includes an LCD screen or touch screen for displaying a graphical user interface, and microphone and speaker interfaces for voice communication.

[0063] The local processing and control module, connected to the human-machine interface module, interprets the dispatcher's operational intentions and generates corresponding instructions and logs. The local processing and control module consists of an embedded microprocessor and the firmware running on it. When the dispatcher performs a dispatching operation through the human-machine interface module, such as forcibly inserting or disconnecting a call, the local processing and control module generates a dispatching operation log. .

[0064] The scheduling operation log It is a structured data record, and its data structure can be defined as:

[0065] ;

[0066] The symbols are defined as follows: This is the precise timestamp of the operation. The identifier of the dispatcher who performed the operation. The number or identifier of the target user to whom the operation is performed. The type code for the operation.

[0067] The local processing and control module is also responsible for handling the creation and management logic of event tags for scheduled events. The human-computer interaction module has a dedicated event management interface, such as a physical button labeled EVENT. When the dispatcher presses this button, the local processing and control module responds by displaying an input interface on the screen, allowing the dispatcher to enter a text description of the scheduled event.

[0068] After the dispatcher confirms the input, the local processing and control module generates an event management instruction. This instruction The data structure can be defined as:

[0069] ;

[0070] The symbols are defined as follows: This is an instruction type. This is a globally unique event identifier. In one embodiment, this identifier is generated by concatenating the device ID of the dispatch console with the current high-precision timestamp to ensure its uniqueness. The timestamp generated for the instruction is used to mark the start or end time of the event. This field contains textual descriptions associated with the event, entered by the dispatcher. It can be empty when an event termination command is sent.

[0071] The communication interface module, connected to the local processing and control module, is responsible for encapsulating locally generated instructions and logs and sending them via the physical network to the scheduling exchange host or directly to the event log and correlation engine. In one embodiment, the communication interface module is an Ethernet interface that receives scheduling operation logs generated by the local processing and control module. and event management commands The data packets are packaged according to predefined TCP or IP application layer protocols and reliably transmitted over IP networks. The data packets consist of a frame header, command word, data length, data payload, and checksum. or Transmitted as data payload;

[0072] To ensure scheduling operation logs and event management commands To ensure reliable transmission to the event log and correlation engine, this embodiment employs a communication protocol with an acknowledgment mechanism between the communication interface module and the event log and correlation engine. When the communication interface module sends data, if no acknowledgment is received from the engine within a preset timeout period, the data is stored in a local temporary storage queue and retried according to a preset retransmission strategy until acknowledgment is received. This mechanism ensures that critical log and instruction data are not lost in the event of a network outage or temporary engine unavailability.

[0073] The digital recording subsystem includes: an audio stream capture module, an audio processing and storage module, and a metadata generation and transmission module.

[0074] An audio stream capture module is used to acquire voice data of a specified call from the dispatch switching host. In one embodiment, the audio stream capture module is physically connected in parallel to the TDM bus of the digital switching network unit inside the dispatch switching host via a high-impedance probe. This connection allows the audio stream capture module to passively listen and copy the PCM data stream in a specific time slot on the bus without affecting the transmission of the original call signal. The specific time slots to be listened to are specified by the call control and signaling processing unit of the dispatch switching host when the call is established, thereby achieving accurate recording of a specific call.

[0075] An audio processing and storage module, connected to the audio stream capture module, is used to process and persistently store the captured raw voice data. The audio processing and storage module first digitally mixes the two captured unidirectional PCM data streams belonging to the two parties in the call, merging them into a single unidirectional mixed voice stream. Subsequently, this mixed voice stream is processed by an audio encoder; in one embodiment, the encoder uses the G.711A-law standard to compress and encode the PCM data. The encoded audio data is then encapsulated into a standard audio file format and stored in the storage medium managed by the audio processing and storage module.

[0076] When the scheduling switch is a softswitch platform based on a network interconnection protocol IP architecture, the audio stream capture module can be implemented in different ways. For example, by configuring port mirroring on the core switch, a copy of the Real-Time Transport Protocol (RTP) packet stream carrying VoIP calls can be made to the listening port of the audio stream capture module. Alternatively, if the scheduling switch supports standard protocols such as Session Initiation Protocol (SIPREC) recording, the audio stream capture module will act as a recording server, and the scheduling switch will actively copy and send the session media stream to this recording server when a call is established.

[0077] The metadata generation and sending module works in conjunction with the audio processing and storage module, and creates a recording metadata record corresponding to the recording file at the same time as the call recording ends and the audio file is generated. The recording metadata It is a structured data record, and its data structure can be defined as:

[0078] ;

[0079] The symbols are defined as follows: The number of the calling party. This is the number of the called party. This is the timestamp for the start of the recording, which is consistent with the start time of the corresponding call. This is the timestamp indicating the end of the recording, which is consistent with the end time of the corresponding call. The complete storage path on the storage medium for the audio recording file generated for this call.

[0080] In generating the recording metadata Subsequently, the metadata generation and sending module immediately establishes a Transmission Control Protocol (TCP) connection with the event log and correlation engine through its network interface, and sends the record... Data records are serialized and then sent to the event log and correlation engine via this TCP connection. This real-time push mechanism ensures that the event log and correlation engine can dynamically obtain the latest recording information and perform correlation operations during the event scheduling process;

[0081] To ensure the recording metadata The metadata can be reliably transmitted to the event log and correlation engine. In this embodiment, the metadata generation and sending module also adopts a transmission mechanism with acknowledgment. If the metadata transmission fails or no acknowledgment is received within a timeout period, the recording metadata... It will be cached in local non-volatile storage and periodically resent by a background task until successful.

[0082] The event log and correlation engine includes: a data receiving and standardization module, an event status management module, a correlation logic module, and a structured storage module.

[0083] The data receiving and standardization module receives heterogeneous data from other modules in the system and converts it into a unified internal data format. In one embodiment, the data receiving and standardization module internally operates multiple independent listening service ports; for example, one port is used to receive call details from the scheduling and switching host. The other port is used to receive scheduling operation logs from the multi-function dispatch console. and event management commands The third port is used to receive recording metadata from the digital recording subsystem. The data receiving and standardization module parses the received data in different formats and encapsulates it into a standardized internal communication record object for subsequent processing.

[0084] The event state management module, connected to the data receiving and standardization module, is responsible for managing the lifecycle of scheduled events. The event state management module maintains a list of active events in memory to store all currently active scheduled events. When the data receiving and standardization module receives an event management command of type "event activation,"... At that time, the event state management module creates a new event instance in the active event list. and record its unique event identifier. Start timestamp and description information .

[0085] Meanwhile, the event status management module determines the event Related core stakeholders In one embodiment, this set is determined by: if the event management instruction... If the event status management module contains a list of participants pre-specified by the scheduler, then that list will be used directly; otherwise, the module will wait for and retrieve the first communication record that arrives immediately after the event activation command, and automatically set the participants in that record as the core participant set. When a command of type "Event Termination" is received, the event state management module finds the corresponding event instance in the list of active events. Record the end timestamp for it. And remove it from the list of active events;

[0086] In a further embodiment, the event state management module also supports a set of core stakeholders. Dynamic expansion. In this mode, when the associated logic module discovers a communication record... timestamp Within the event window, and its participants With the current core stakeholders When there is an intersection, in addition to recording the record With the event In addition to association, the event state management module will also China does not belong to New participants are also dynamically joining. This mechanism allows the scope of association to expand naturally along the event's communication network, thereby capturing communications initiated by core personnel and between their associated secondary personnel.

[0087] The association logic module, connected to the data receiving and standardization module and the event state management module, is used to execute the core association judgment logic. For each standardized communication record received by the data receiving and standardization module... The association logic module will iterate through each active event in the list of active events maintained by the event state management module. .

[0088] For each activity event The associated logic module extracts communication records. timestamp of occurrence and participating parties and from event instances Extract its start time End time and the core participants Then, the preset correlation function is applied. Perform the calculation:

[0089] ;

[0090] The definitions of each symbol have been explained above. If and only if When the calculation result is 1, the associated logic module in the communication record Add a field to the data structure to store the corresponding event. event identifier This completes the logical binding between the record and the event; When the above conditions are not met, The value is .

[0091] The structured storage module, connected to the association logic module and the event state management module, is used to persistently store event information, communication records, and their relationships. In one embodiment, the structured storage module is a database interface responsible for interacting with a relational database. This database contains the following tables: an event table with fields including event identifier, start time, end time, and description information, used to store the attributes of each scheduled event; a communication record table with fields including record identifier, record type, occurrence timestamp, participant list, and specific content or file path, used to store all received communication records; and an event-record association table containing two fields: event identifier and record identifier, used to specify all communication records included in each event and establish a many-to-many mapping relationship between them.

[0092] After the association logic module processes a communication record, or when the event status management module marks an event as completed, the structured storage module is responsible for generating the corresponding structured query language (SQL) instructions and writing these data into the corresponding tables mentioned above, thereby completing the solidified storage of the entire communication scenario.

[0093] In one embodiment, the system maintenance terminal is a software application deployed on a workstation or a web application accessed through a browser, which includes: a query interface and processing module, a data retrieval and organization module, and a scene presentation module.

[0094] The query interface and processing module provides administrators with a search interface and generates structured query requests based on input criteria. The graphical user interface provided by the query interface and processing module includes multiple query input fields, such as a text box for entering event descriptions, a date or time selector for specifying the time range of the event, and an input box for entering the numbers of specific participants.

[0095] When an administrator enters query criteria and initiates a search, the query interface and processing module convert these input criteria into a formalized query request. In one embodiment, this query request is constructed as a Structured Query Language (SQL) statement used to query the structured storage module of the event log and the correlation engine. This SQL statement, by joining the event table, communication record table, and correlation table, filters out events that meet all input criteria and all their associated communication records.

[0096] The data retrieval and organization module, connected to the query interface and processing module, is responsible for executing queries and preprocessing the returned results. The data retrieval and organization module sends the query requests generated by the query interface and processing module to the event log and association engine. Upon receiving the data set returned by the query, the data retrieval and organization module first processes all communication records within the set. Process it.

[0097] The processing includes: First, based on each communication record... timestamps within For sets Sort the records in ascending order to obtain a sequence of communication records arranged chronologically. Secondly, the data retrieval and organization module parses the content of each record in the sequence to prepare the data for subsequent presentation.

[0098] The scene presentation module, connected to the data retrieval and organization module, is used to present the sorted sequence of communication records. The scene is presented graphically. In one embodiment, the scene presentation module generates a unified timeline view on the user interface. This timeline is a horizontal line with scales representing time.

[0099] For sequences Each communication record The scene presentation module is based on its timestamp. Calculate its horizontal position coordinates on the time axis. This calculation process can be defined by the following function:

[0100] ;

[0101] The symbols are defined as follows: The coordinates of the starting point of the timeline on the screen. This is the scaling factor for the time axis, representing the pixel width on the screen corresponding to each unit time interval. For communication records The timestamp of the occurrence. The start time displayed in the current timeline view.

[0102] The scene presentation module provides different graphical icons for different types of communication records. For example, call details. Represented by a telephone icon, recording metadata The scheduling operation log is represented by an earphone icon. Represented by a gear icon. Each icon is precisely drawn on its own... The calculated position.

[0103] The scene presentation module also provides interactive functionality. When a user clicks any icon on the timeline, a window pops up displaying all the details of that communication record. If the clicked icon corresponds to a recording metadata entry... The interface will then provide a play button. When the user clicks this button, the system can play the file based on the file path in the metadata. The system retrieves the corresponding audio file from the storage medium of the digital recording subsystem and plays it. This method enables context-based backtracking of all communication records related to the scheduling event.

[0104] To facilitate the analysis of complex communication scenarios, the scenario presentation module also provides filtering functionality for the timeline view. The user interface offers filtering controls, allowing users to select to display only specific types of communication records, or only records related to specific participants. Furthermore, the scenario presentation module provides a communication relationship graph view. All participants are displayed as nodes, and past calls or communications are shown as edges connecting the nodes, thus allowing for a visual analysis of the communication topology among the parties involved in the event.

Claims

1. A digital program-controlled dispatching system, characterized in that, include: The scheduling switching host is used to handle call setup and generate call details; A multi-functional dispatch console is used by dispatchers to perform dispatching operations and create event tags to define a dispatching event; A digital recording subsystem, connected to the scheduling and switching host, is used to record calls and generate recording metadata; An event log and association engine is used to respond to the creation of event tags for the scheduling event, receive the call details and the recording metadata, and associate the received call details and the recording metadata with the event tags of the scheduling event, thereby generating a communication scenario corresponding to the scheduling event. The system maintenance terminal is connected to the event log and association engine and is used to retrieve and trace the communication scenario based on the event tags of the scheduling event. The event log and association engine are specifically used for: Obtain the start time, end time, and core participant set of the scheduling event defined by the event label of the scheduling event; Define a communication record that includes call details and recording metadata. When the occurrence time of the communication record is between the start time and the end time, and the participants of the communication record have an intersection with the core participant set, the communication record is associated with the event tag of the scheduling event, and the communication record is classified into the communication scenario. The set of core participants is determined through at least one method, wherein the method is: The event label is specified in advance by the scheduler when creating the scheduled event; The event log and association engine automatically identify the participants in the initial call associated with the scheduling event.

2. The digital program-controlled scheduling system according to claim 1, characterized in that, The multi-functional dispatch console is also used to generate dispatch operation logs that record the dispatcher's operations; The event log and association engine is also used to receive the scheduling operation log, associate the scheduling operation log with the event tag of the scheduling event, and classify it into the communication scenario.

3. The digital program-controlled scheduling system according to claim 1, characterized in that, The multi-functional dispatch console is equipped with a dedicated event management interface, which is used by dispatchers to activate and terminate event tags of dispatch events and input descriptive information for the event tags of dispatch events.

4. The digital program-controlled scheduling system according to claim 1, characterized in that, The event log and association engine includes a structured storage unit, which persistently stores the communication scenario by establishing an event table, a communication record table, and an association table between events and records.

5. The digital program-controlled scheduling system according to claim 1, characterized in that, The scheduling and switching host includes a main control unit and a power supply unit. Both the main control unit and the power supply unit adopt a dual hot backup mechanism to ensure that the generation of call details is not interrupted when the main unit fails.

6. The digital program-controlled scheduling system according to claim 1, characterized in that, When the system maintenance terminal traces back the communication scenario, it will associate all communication records related to the event tag of the same scheduling event and present them on a unified timeline.

7. The digital program-controlled scheduling system according to claim 1, characterized in that, The digital recording subsystem is used to push the generated recording metadata to the event log and association engine in real time, and supports dynamic association during the scheduling event.

8. The digital program-controlled scheduling system according to claim 2, characterized in that, The scheduling operation log generated by the multi-functional scheduling console includes operation records of forced insertion, forced disconnection, and meeting convening.

Images