text
stringlengths 463
768
|
|---|
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data collection. Functional process: core network delay index data collection. Sub-process description: Read the account information of the core network latency indicator data server. Data movement type: R. Data group: account information of the core network latency index data server. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: The registration class poor quality rule configuration data is added. Functional process: The configuration data of the registration class poor quality rule is added. Sub-process description: update the configuration data of registration class poor quality rules. Data movement type: W. Data group: newly added registration class poor quality rule configuration data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Triggering event: downloading of the ranking data of prefectures and cities for mass distribution of indicators. Functional process: download the ranking data of prefectures and cities by group sending. Sub-process description: Save the downloaded data of the ranking of cities and towns for mass distribution indicators. Data movement type: W. Data group: download data of rankings of prefectures and cities for mass distribution of indicators. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data query. Functional process: query the core network latency index data list. Sub-process description: Input the query request for the core network latency index data list. Data movement type: E. Data group: list query operation instructions. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service quality closed-loop management, voice service quality monitoring closed-loop presentation. Trigger event: VOLTE voice service quality monitoring indicator data export. Functional process: export VOLTE voice service quality monitoring index data. Sub-process description: input the VOLTE voice service quality monitoring index export request. Data movement type: E. Data group: VOLTE voice service quality monitoring indicator export operation instruction. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: Export of poor-quality NE analysis data. Functional process: export the analysis data of poor quality network elements. Sub-process description: read the export template of poor quality network element analysis. Data movement type: R. Data group: Export template for poor quality NE analysis. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: P2P poor quality rule configuration data modification. Functional process: modify the configuration data of P2P poor quality rules. Sub-process description: modify the configuration data of P2P poor quality rules. Data movement type: W. Data group: configuration data of the P2P poor quality rules to be modified. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data query of key factors of P2P poor quality business. Functional process: query the data details of the key factors of P2P poor quality business. Sub-process description: read the detailed data of the key factors of P2P poor quality business. Data movement type: R. Data group: detailed data of key factors of P2P poor quality business. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Triggering event: downloading of connection index data for poor quality cells. Functional process: downloading of connection index data for poor quality cells. Sub-process description: read the access index data of poor quality cells. Data movement type: R. Data group: poor-quality community connection index data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: 5G message terminal number demand forecast rule configuration data export. Functional process: 5G message terminal number demand forecast rule configuration data export. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: Business development indicator monitoring rule configuration data modification. Functional process: business development indicator monitoring rule configuration data modification. Sub-process description: Input the service development indicator monitoring rule configuration data modification request. Data movement type: E. Data group: modify the operation instruction. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Triggering event: VONR connected quality closed-loop data export. Functional process: VONR connected quality closed-loop data export. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: export of VoNR delay data for VoNR calls in the cell. Functional process: export of VoNR delay data for cell VoNR calls. Sub-process description: read VoNR delay data of cell VoNR calls. Data movement type: R. Data group: Cell VoNR call VoNR delay data. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VONR voice demand forecast configuration data is added. Function process: VONR voice demand forecast configuration data is added. Sub-process description: read VONR voice demand forecast configuration data. Data movement type: R. Data group: VONR voice demand forecast configuration data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message business demand, 5G message demand and forecasted city rankings and trends. Triggering event: UP2.4 export of prediction data on the number of group text messages sent by terminals. Functional process: UP2.4 terminal group text message number prediction data export. Sub-process description: export the prediction data of UP2.4 terminal group text messages. Data movement type: X. Data group: UP2.4 terminal group text message number forecast data. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data collection. Functional process: core network delay index data collection. Sub-process description: Read the verification rules to verify the account information of the core network latency index data server. Data movement type: R. Data group: core network latency index data server IP verification rules. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data collection. Functional process: 5G voice VONR user number analysis data conversion interface. Sub-process description: read 5G voice VONR user number analysis data for conversion. Data movement type: R. Data group: 5G voice VONR user number analysis data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: registration failure reason value data query. Functional process: Query the details of the reason value data of the registration failure. Sub-process description: Enter the query request for registration failure reason value data details. Data movement type: E. Data group: query operation instructions for details. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: Query data of terminal indicators with poor granularity in prefectures and cities. Functional process: Inquiry about the details of terminal index data with poor granularity and quality in prefectures and cities. Sub-process description: Output the detailed query results of the terminal index data with poor granularity and quality in cities. Data movement type: X. Data group: Detailed query results of prefecture-level and poor-quality terminal indicator data. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data collection. Functional process: 5G voice VOLTE call duration analysis data collection interface. Sub-process description: return 5G voice VOLTE call duration analysis data. Data movement type: X. Data group: 5G voice VOLTE call duration analysis and collection data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Triggering event: The data export of terminal business aggregation indicators. Functional process: export the aggregation indicator data of terminal business class. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data table is generated. Functional process: 5G voice VONR user number analysis data table generation (GP service library). Sub-process description: Read the verification rules to verify the 5G voice VONR user number analysis data. Data movement type: R. Data group: 5G voice VONR user number analysis data verification rules. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: Inquiry of connection index data of poor quality cells. Functional process: Query the data list of connection indicators of poor quality cells. Sub-process description: output query results of poor-quality cell connection index data list. Data movement type: X. Data group: Query results of the data list of connectivity indicators for poor-quality communities. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: VONR voice indicators early warning data query. Functional process: Query the details of VONR voice index early warning data. Sub-process description: Read the detailed data of VONR voice indicator warning. Data movement type: R. Data group: VONR voice indicator warning details data. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data conversion. Sub-process description: Save the 5G voice VOLTE user number analysis data conversion data. Data movement type: W. Data group: the converted 5G voice VOLTE user number analysis data. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data collection. Sub-process description: Input the 5G voice VOLTE user number analysis data collection request. Data movement type: E. Data group: system time. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Triggering event: The configuration data of the registration poor quality terminal rule is added. Functional process: The configuration data for the registration of poor-quality terminal rules is added. Sub-process description: Enter a new request for configuration data of poor registered terminal rules. Data movement type: E. Data group: add operation instructions. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of terminal delay. Trigger event: terminal EPSFB delay data query. Function process: terminal EPSFB delay data list query. Sub-process description: Input terminal EPSFB delay data list query request. Data movement type: E. Data group: list query operation instructions. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice VONR call duration prediction analysis data query. Functional process: 5G voice VONR call duration prediction analysis data list query. Sub-process description: read 5G voice VONR call duration prediction analysis data list information. Data movement type: R. Data group: 5G voice VONR call duration prediction analysis data list information. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice EPSFB call duration prediction analysis data query. Functional process: 5G voice EPSFB call duration prediction analysis data query. Sub-process description: Read the detailed data of 5G voice EPSFB call duration prediction analysis. Data movement type: R. Data group: 5G voice EPSFB call duration prediction analysis detailed data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: P2P message index data query of poor quality terminals. Functional process: Query the P2P message index data list of poor quality terminals. Sub-process description: Output the query result of the P2P message index data list of poor quality terminals. Data movement type: X. Data group: the query result of the P2P message index data list of poor quality terminals. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: P2P failure reason value data query. Functional process: P2P failure reason value data list query. Sub-process description: read P2P failure cause value data list information. Data movement type: R. Data group: P2P failure cause value data list information. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 terminal user number prediction rule configuration data display. Functional process: UP2.4 terminal user number prediction rule configuration data display. Sub-process description: The output shows the UP2.4 terminal user number prediction rule configuration data. Data movement type: X. Data group: UP2.4 terminal user number prediction rule configuration data. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: The analysis data of the poor quality cell is modified. Functional process: modify the analysis data of poor quality plots. Sub-process description: Update the analysis data of the poor-quality plots. Data movement type: W. Data set: modified analysis data of poor quality plots. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: download of ranking data of prefectures and cities of registration indicators. Functional process: download the ranking data of registration index cities. Sub-process description: read the ranking data of registered index prefectures and cities. Data movement type: R. Data set: the ranking data of registered index prefectures and cities. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VONR poor voice quality registration rule configuration data deletion. Functional process: Delete the registration rule configuration data for VONR poor voice quality. Sub-process description: Delete the registration rule configuration data of VONR poor voice quality. Data movement type: W. Data group: configuration data of VONR poor voice quality registration rules to be deleted. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G messaging service requirements, early warning of 5G messaging performance indicators. Trigger event: P2P & group message warning data query. Functional process: P2P & group message early warning data details query. Sub-process description: read P2P & group message warning details data. Data movement type: R. Data group: P2P & group message warning details data. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR connected quality closed-loop data query. Functional process: VONR connected quality closed-loop data list query. Sub-process description: Input VONR access quality closed-loop data list query request. Data movement type: E. Data group: list query operation instructions. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Triggering event: downloading of connection index data for poor quality cells. Functional process: downloading of connection index data for poor quality cells. Sub-process description: Save the download data of connection indicators of poor-quality cells. Data movement type: W. Data group: download data of connectivity indicators for poor quality communities. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB call quality quality closed-loop data table generation. Functional process: EPSFB call quality closed-loop data statistics (HBASE library). Sub-process description: Input EPSFB call quality closed-loop data statistics request. Data movement type: E. Data group: data statistics operation instructions. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: Modification of the configuration data of the group sending poor quality terminal rules. Functional process: Modify the configuration data of group sending poor quality terminal rules. Sub-process description: Update the configuration data of the group sending poor quality terminal rules. Data movement type: W. Data group: the modified configuration data of the group sending poor quality terminal rules. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: business failure reason value data query. Functional process: query the data list of business failure reasons. Sub-process description: Output the query result of the data list of the cause of business failure. Data movement type: X. Data group: the query result of the data list of the cause of business failure. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor quality load indicator data table. Functional process: Statistics of poor quality load indicators (HBASE library). Sub-process description: Save the statistical results of poor quality load index data to the HBASE library. Data movement type: W. Data group: statistical results of poor quality load index data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: Registration class poor quality rule configuration data modification. Functional process: modify the configuration data of registration class poor quality rules. Sub-process description: Return the modification result. Data movement type: X. Data group: the result of modifying configuration data of registration class poor quality rules. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data export. Functional process: 5G voice VONR user number analysis data export. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR connected quality closed-loop data table is generated. Functional process: VONR connection quality closed-loop data table generation (GP business library). Sub-process description: read VONR connection quality closed-loop data. Data movement type: R. Data group: VONR connected quality closed-loop data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message business demand, 5G message demand and forecasted city rankings and trends. Trigger event: UP2.4 terminal mass SMS number prediction data query. Functional process: UP2.4 query the details of the prediction data of the number of group text messages sent by the terminal. Sub-process description: output the detailed query results of UP2.4 terminal group SMS number prediction data. Data movement type: X. Data group: UP2.4 terminal mass SMS number prediction data detailed query results. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: P2P SMS demand forecasting rule configuration data is added. Functional process: The configuration data of the P2P short message number demand prediction rule is added. Sub-process description: update the configuration data of the P2P short message number demand prediction rule. Data movement type: W. Data group: newly added P2P SMS demand forecasting rule configuration data. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: Core network latency index data export. Functional process: export core network latency index data. Sub-process description: Input the core network delay index export request. Data movement type: E. Data group: core network latency index export operation instruction. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: modification of terminal rule configuration data with poor service development quality. Functional process: modification of terminal rule configuration data for poor business development. Sub-process description: input a request for modifying configuration data of terminal rules with poor service development quality. Data movement type: E. Data group: modify the operation instruction. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of terminal delay. Trigger event: terminal EPSFB delay data query. Functional process: Query the details of the terminal EPSFB delay data. Sub-process description: Input terminal EPSFB delay data query request. Data movement type: E. Data group: query operation instructions for details. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB call quality quality closed-loop data table generation. Functional process: EPSFB call quality closed-loop data table generation (GP service library). Sub-process description: Trigger the generation task of EPSFB call quality closed-loop data table at regular intervals. Data movement type: E. Data group: system time. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: File transfer class poor quality rule configuration data export. Functional process: file transfer class poor quality rule configuration data export. Sub-process description: Input file transfer class poor quality rule configuration export request. Data movement type: E. Data group: file transfer class poor quality rule configuration export operation instruction. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: upload of business development indicator analysis data. Functional process: business development indicators analysis data upload. Sub-process description: read the analysis data of business development indicators. Data movement type: R. Data group: analysis data of business development indicators. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: EPSFB poor voice quality connection rule configuration data is added. Functional process: The EPSFB poor voice quality connection rule configuration data is added. Sub-process description: return the newly added result of EPSFB poor voice quality connection rule configuration data. Data movement type: X. Data group: The newly added result of EPSFB voice quality connection rule configuration data. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data conversion interface. Sub-process description: return 5G voice VOLTE user number analysis data conversion data. Data movement type: X. Data group: the converted 5G voice VOLTE user number analysis data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: Data query of key factors of poor business development. Functional process: query the data list of key factors of poor business development quality. Sub-process description: read the data list information of key factors of poor business development quality. Data movement type: R. Data group: data list information of key factors of poor business development quality. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: P2P short message number demand prediction rule configuration data export. Functional process: P2P SMS number demand prediction rule configuration data export. Sub-process description: read the configuration data of P2P short message number demand prediction rules. Data movement type: R. Data group: configuration data of P2P SMS demand forecasting rules. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: The configuration data of the chatbot poor quality terminal rule is added. Functional process: Added chatbot terminal rule configuration data with poor quality. Sub-process description: update chatbot poor-quality terminal rule configuration data. Data movement type: W. Data group: newly added chatbot poor quality terminal rule configuration data. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB call quality quality closed-loop data table generation. Functional process: EPSFB call quality closed-loop data table generation (GP service library). Sub-process description: Read the verification rules to verify the quality closed-loop data of EPSFB call quality. Data movement type: R. Data group: EPSFB call quality quality closed-loop data verification rules. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: Poor quality terminal file transfer index data query. Functional process: Query the data list of poor-quality terminal file transfer indicators. Sub-process description: Read the index data list information of poor-quality terminal file transfers. Data movement type: R. Data group: data list information of poor-quality terminal file transfer indicators. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 terminal user number prediction rule configuration data modification. Functional process: UP2.4 Modification of the configuration data of the prediction rules for the number of end users. Sub-process description: Input UP2.4 terminal user number prediction rule configuration data modification request. Data movement type: E. Data group: modify the operation instruction. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: data query of connection delay index. Functional process: Query the details of connection delay index data. Description of the sub-process: Input the request for querying the details of the on-delay index data. Data movement type: E. Data group: query operation instructions for details. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data export. Functional process: 5G voice VONR call duration analysis data export. Sub-process description: Input 5G voice VONR call duration analysis and export request. Data movement type: E. Data group: 5G voice VONR call duration analysis and export operation instructions. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: Export of EPSFB voice index warning data. Functional process: EPSFB voice indicator early warning data export. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: 5G message terminal number demand forecast rule configuration data export. Functional process: 5G message terminal number demand forecast rule configuration data export. Sub-process description: Input the export request of the 5G message terminal quantity demand forecasting rule configuration. Data movement type: E. Data group: 5G message terminal number demand forecast rule configuration export operation instruction. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VONR poor voice quality registration rule configuration data query. Functional process: Query the configuration data list of VONR poor voice quality registration rules. Sub-process description: input VONR poor voice quality registration rule configuration data list query request. Data movement type: E. Data group: list query operation instructions. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G messaging service requirements, early warning of 5G messaging performance indicators. Trigger event: P2P & group message warning data query. Functional process: P2P & group message early warning data details query. Sub-process description: Input P2P & group message early warning data details query request. Data movement type: E. Data group: query operation instructions for details. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: The generation of data table of poor quality indicators of file transfer class. Functional process: Statistics of poor quality indicators for file transfers (HBASE library). Sub-process description: read file transfer class poor quality indicator data. Data movement type: R. Data group: file transfer class poor quality indicator data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, drill-down of 5G message indicators. Trigger event: 5G message group sending detailed list data query. Functional process: 5G message group sending detailed list data detailed query. Sub-process description: Enter a request for querying the details of the 5G message group sending detailed list data. Data movement type: E. Data group: query operation instructions for details. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: On-time delay indicator data collection. Functional process: data analysis of connection delay index. Sub-process description: Input the data analysis request of the on-delay index. Data movement type: E. Data group: system time. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: 5G message terminal number demand forecasting rule configuration data is added. Functional process: 5G message terminal number demand forecasting rule configuration data is added. Sub-process description: Read the configuration data of the 5G message terminal number demand prediction rule. Data movement type: R. Data group: 5G message terminal number demand forecasting rule configuration data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: Business development indicator monitoring rule configuration data modification. Functional process: business development indicator monitoring rule configuration data modification. Sub-process description: modify the configuration data of the business development indicator monitoring rules. Data movement type: W. Data group: configuration data of business development indicator monitoring rules to be modified. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, call auxiliary delay statistics. Trigger event: N26 interface delay data download. Functional process: N26 interface delay data download. Sub-process description: download the delay data of the N26 interface. Data movement type: W. Data group: N26 interface delay data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Trigger event: Chatbot class aggregation indicator data export. Functional process: Chatbot class aggregation indicator data export. Sub-process description: read the export template of Chatbot class aggregation indicators. Data movement type: R. Data group: Chatbot class aggregation indicator export template. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: Data export of key indicators of 5G message business. Functional process: export key indicator data of 5G message business. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data collection. Functional process: 5G voice EPSFB call duration analysis data conversion interface. Sub-process description: Receive 5G voice EPSFB call duration analysis data conversion request. Data movement type: E. Data group: 5G voice EPSFB call duration analysis data conversion request. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Data export of poor quality indicators for business development. Functional process: Data export of poor quality indicators for business development. Sub-process description: read the poor quality indicator data of business development category. Data movement type: R. Data group: business development category poor quality indicator data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Triggering event: Query of poor-quality terminal registration indicator data. Functional process: Query the data list of poor-quality terminal registration indicators. Sub-process description: Read the information of the poor-quality terminal registration index data list. Data movement type: R. Data group: the list information of poor-quality terminal registration index data list. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: bad-quality terminal chatbot business data query. Functional process: query the chatbot business data list of poor-quality terminals. Sub-process description: Output the query result of chatbot business data list of poor-quality terminals. Data movement type: X. Data group: query result of chatbot business data list of poor quality terminals. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data query. Functional process: 5G voice EPSFB call duration analysis data list query. Sub-process description: Input the 5G voice EPSFB call duration analysis data list query request. Data movement type: E. Data group: list query operation instruction. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality terminal analysis. Trigger event: Analysis data query of call quality index factors of poor-quality terminals. Functional process: Query the list query of the call quality index factor analysis data of poor quality terminals. Sub-process description: output the query results of the call quality index factor analysis data list of the terminal with poor quality. Data movement type: X. Data group: the query result of the analysis data list of call quality index factors of poor quality terminals. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message user number indicator data query. Functional process: Query the list of 5G message user number index data. Sub-process description: Read the 5G message user number index data list information. Data movement type: R. Data group: 5G news user number index data list information. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: Export of prefecture-level and poor-quality terminal indicator data. Functional process: Data export of prefecture-level and poor-quality terminal indicators. Sub-process description: Read the template for exporting city-level poor-quality terminal indicators. Data movement type: R. Data group: Export template of prefecture-level and poor-quality terminal indicators. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data export of key factors of P2P poor quality business. Functional process: Data export of key factors of P2P poor quality business. Sub-process description: read the data of key factors of P2P poor quality business. Data movement type: R. Data set: data on key factors of P2P poor quality business. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: download of ranking data of prefectures and cities of registration indicators. Functional process: download the ranking data of registration index cities. Sub-process description: Save the downloaded data of the registered index prefecture and city ranking. Data movement type: W. Data group: download data of registered index prefecture and city rankings. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, analysis and forecast of 5G message user numbers. Trigger event: UP2.4 user analysis data query. Functional process: UP2.4 user analysis data details query. Sub-process description: output the query result of UP2.4 user analysis data details. Data movement type: X. Data group: UP2.4 user analysis data details query results. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: Cell VoNR call VoNR delay data query. Functional process: VoNR calling VoNR delay data list query in the cell. Sub-process description: Input the cell VoNR call VoNR delay data list query request. Data movement type: E. Data group: list query operation instructions. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: The configuration data of the group sending poor quality terminal rule is added. Functional process: The configuration data of the group sending poor quality terminal rules is added. Sub-process description: Return the new result of configuration data of group sending poor quality terminal rules. Data movement type: X. Data group: The newly added results of group sending poor quality terminal rule configuration data. |
Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: VONR drop call solution data export. Functional process: VONR dropped call solution data export. Sub-process description: read VONR dropped call solution data. Data movement type: R. Data group: VONR drop call solution data. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, analysis and forecast of 5G message user numbers. Trigger event: UP2.4 user analysis data export. Functional process: UP2.4 user analysis data export. Sub-process description: read UP2.4 user analysis export template. Data movement type: R. Data group: UP2.4 user analysis export template. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data collection. Functional process: 5G voice EPSFB call duration analysis data collection interface. Sub-process description: Receive 5G voice EPSFB call duration analysis data collection request. Data movement type: E. Data group: 5G voice EPSFB call duration analysis data collection request. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: downloading of time delay index data for poor quality cells. Functional process: Download the time-delay index data of poor-quality cells. Sub-process description: Read the time-delay index data of poor-quality cells. Data movement type: R. Data group: Delay index data of poor quality cells. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Triggering event: The data table of the cause value of mass sending failure is generated. Functional process: Statistics of the cause value of mass sending failure (HBASE library). Sub-process description: read the data of the cause value of the mass sending failure. Data movement type: R. Data group: data of group sending failure reason value. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: P2P message index data export of poor quality terminals. Functional process: Export the P2P message index data of poor quality terminals. Sub-process description: Export P2P message index data of poor quality terminals. Data movement type: X. Data group: P2P message index data of poor quality terminals. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: UP2.4 terminal 5G message index data query. Functional process: Query the list of UP2.4 terminal 5G message index data. Sub-process description: Read the UP2.4 terminal 5G message indicator data list information. Data movement type: R. Data group: UP2.4 terminal 5G message indicator data list information. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data collection. Functional process: 5G voice VOLTE call duration analysis data collection. Sub-process description: Read the account information of the 5G voice VOLTE call time analysis data server. Data movement type: R. Data group: 5G voice VOLTE call duration analysis data server account information. |
Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: prefecture-city registration aggregation dimension data query. Functional process: Query the details of the aggregation dimension data of prefecture-city registration. Description of the sub-process: Input the query request for the details of the aggregation dimension data of prefecture-city registration. Data movement type: E. Data group: query operation instructions for details. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: downloading of call quality indicator data in poor quality cells. Functional process: Download call quality indicator data for poor quality cells. Sub-process description: Save the downloaded data of call quality indicators in poor quality cells. Data movement type: W. Data group: download data of call quality indicators in poor quality cells. |
Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice EPSFB user number analysis data collection. Functional process: 5G voice EPSFB user number analysis data conversion interface. Sub-process description: return 5G voice EPSFB user number analysis data conversion data. Data movement type: X. Data group: converted 5G voice EPSFB user number analysis data. |