text
stringlengths 537
1.44k
|
---|
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: Generate business development indicator analysis data table. Functional process: business development index analysis data table generation (GP business library). Sub-process description: Timely trigger the task of generating business development indicator analysis data tables. Data movement type: E. Data group: system time. Data attribute: 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: multi-dimensional cluster analysis of 5G message service indicators, drill-down of 5G message indicators. Trigger event: 5G message group sending detailed list data download. Functional process: 5G message group sending detailed list data download. Sub-process description: Enter the 5G message group sending detailed list data download request. Data movement type: E. Data group: download operation instruction. Data attributes: download time, download format. |
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: generation of on-delay index data table. Functional process: generation of connection delay index data table (GP business library). Sub-process description: generate the on-delay index data table. Data movement type: W. Data group: data table of connection delay index. Data attributes: wireless delay (VoNR), total wireless delay (VNR2VNR), wireless delay (VNR2VNR), connection delay (VoNR), total connection delay measurement times (VNR2VNR), connection delay index, Total connection delay (VoNR), total connection delay measurement times (VoNR), connection delay (VNR2VNR), wireless total delay measurement times (VNR2VNR). |
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. Triggering event: poor-quality bulk business data query. Functional process: Query the list of bad-quality mass-sending business data. Sub-process description: read the list information of poor-quality mass-sending business data. Data movement type: R. Data group: list information of poor-quality mass-sending business data. Data attributes: poor-quality group sending business, large (average delay in sending messages in mode (group sending)), large (number of successful messages received in mode (group sending)), date, large (number of sending messages in mode (group sending)), conclusion of poor quality group sending , large (mode message sending success rate (group sending)), city, large (mode message receiving times (group sending)), mass sending quality city factors, large (mode message sending average delay (group sending)). |
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: NE fallback aggregation dimension data export. Functional process: Network element fallback aggregation dimension data export. Sub-process description: Read the template for exporting the NE fallback aggregation dimension. Data movement type: R. Data group: Export template of NE fallback aggregation dimension. Data attribute: NE fallback aggregation dimension 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 forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice EPSFB user number prediction analysis data export. Functional process: 5G voice EPSFB user number prediction analysis data export. Sub-process description: read 5G voice EPSFB user number prediction and analysis data. Data movement type: R. Data group: 5G voice EPSFB user number prediction and analysis data. Data attributes: Number of active EPSFB users in the peak hour of month n-2, predicted number of active EPSFB users in the peak hour of month n+2, prediction and analysis of the number of EPSFB users for 5G voice, forecast number of active EPSFB users in the peak hour of month n+1, month n-4 Number of active EPSFB users in peak hour, n-number of active EPSFB users in peak hour in May, number of active EPSFB users in peak hour of this month, number of active EPSFB users in peak hour of this month, n-number of active EPSFB users in peak hour in March, forecast n+ The number of EPSFB active users in the peak hour in March, n-the number of EPSFB active users in the peak hour in January. |
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: generation of on-delay index data table. Functional process: generation of connection delay index data table (GP business library). Sub-process description: Read the verification rules to verify the connection delay index data. Data movement type: R. Data group: verification rules for connection delay index data. Data attributes: wireless delay (VoNR), total wireless delay (VNR2VNR), wireless delay (VNR2VNR), connection delay (VoNR), total connection delay measurement times (VNR2VNR), connection delay index, Total connection delay (VoNR), total connection delay measurement times (VoNR), connection delay (VNR2VNR), wireless total delay measurement times (VNR2VNR). |
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: Export of EPSFB voice demand forecast configuration data. Functional process: EPSFB voice demand forecast configuration data export. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not. |
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 P2P SMS prediction rule configuration data display. Functional process: UP2.4 terminal P2P SMS prediction rule configuration data display. Sub-process description: read the configuration data of UP2.4 terminal P2P SMS prediction rules. Data movement type: R. Data group: UP2.4 terminal P2P SMS prediction rule configuration data. Data attribute: UP2.4 terminal P2P SMS prediction rule configuration, n+9 month UP2.4 terminal P2P message number growth rate, n+4 month UP2.4 terminal P2P message number growth rate, n+8 month UP2.4 terminal P2P message number growth rate The growth rate of the number of messages, the growth rate of the number of P2P messages of UP2.4 terminals in n+5 months, the growth rate of the number of P2P messages of UP2.4 terminals in July, the growth rate of the number of P2P messages of UP2.4 terminals in n+2 months, n+3 The monthly growth rate of UP2.4 terminal P2P messages, the number of UP2.4 terminal P2P messages this month, and the number of months of historical data forecasted by 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: The core network latency index data table is generated. Functional process: Generation of core network delay index data table (GP service library). Sub-process description: Save the core network delay index data table to the GP table library. Data movement type: W. Data group: core network latency index data table. Data attributes: 5G core network total delay 1 measurement times (VNR2VNR), core network delay index, 5G core network total delay 1 (VoNR), 5G core network delay 2 (VNR2VNR), 5G core network total delay 1 (VNR2VNR), 5G core network total delay 2 (VNR2VNR), 5G core network delay 1 (VNR2VNR), 5G core network total delay 2 (VoNR), 5G core network total delay 2 measurement times (VNR2VNR). |
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: Chatbot service quality indicator data download. Functional process: Chatbot business quality index data download. Sub-process description: Read Chatbot business quality indicator data. Data movement type: R. Data set: Chatbot service quality index data. Data attributes: the success rate of messages uplinked by users to Chatbot, the total delay of messages uplinked by UP2.4 terminal users to Chatbot, the total delay of messages uplinked by users to Chatbot, the total number of messages downlinked by Chatbot to users, and the number of messages downlinked by Chatbot to users The number of successful messages, the total number of messages uploaded by users to Chatbot, the poor service quality index of Chatbot, date, and the success rate of messages uploaded by UP2.4 terminal users to Chatbot. |
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: Input the new request of VONR voice demand forecast configuration data. Data movement type: E. Data group: add operation instructions. Data attribute: add person, add 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 business demand, 5G message demand and forecasted city rankings and trends. Trigger event: UP2.4 terminal user number forecast data query. Functional process: UP2.4 terminal user number forecast data list query. Sub-process description: read UP2.4 terminal user number prediction data list information. Data movement type: R. Data group: UP2.4 terminal user number prediction data list information. Data attribute: n-the number of 5G message users of UP2.4 terminals in February, n-the number of 5G message users of UP2.4 terminals in January, n-the number of 5G message users of UP2.4 terminals in May, n-the number of UP2.4 terminals in April The number of 5G message users, the number of 5G message users of UP2.4 terminals in n+1 month, districts and counties, the forecast of the number of UP2.4 terminal users, the number of 5G message users of UP2.4 terminals this month. |
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: business development indicator analysis data query. Functional process: detailed query of business development indicators analysis data. Sub-process description: read the detailed data of business development indicator analysis. Data movement type: R. Data group: business development indicators analysis details data. Data attributes: the number of successful authentications initiated by the terminal to the storage server, the number of TCP establishment requests, the number of successful TCP establishments, the total delay of TCP establishments (wireless side), the number of successful TCP establishments (core network), the total delay of HTTP responses, and the total delay of TCP establishments initiated by terminals. The total number of authentications of the storage server, the number of successful TCP establishments (on the wireless side), the total number of HTTP business requests, and the analysis of business development 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: IMS domain latency indicator data upload. Functional process: IMS domain delay index data upload. Sub-process description: return the upload result. Data movement type: X. Data group: IMS domain latency index data upload results. Data attributes: whether the upload is successful, upload address. |
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: The core network latency index data table is generated. Functional process: core network latency index data statistics (HBASE library). Sub-process description: Save the statistical results of the core network latency index data to the HBASE library. Data movement type: W. Data group: Statistical results of core network latency index data. Data attributes: 5G core network delay 1 (VoNR), 5G core network total delay 2 (VoNR), 5G core network total delay 2 (VNR2VNR), core network delay index, 5G core network total delay 2 measurement times (VoNR), 5G core network delay 1 (VNR2VNR), 5G core network delay 2 (VoNR), 5G core network total delay 1 measurement times (VNR2VNR), 5G core network total delay 1 (VoNR). |
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 query. Functional process: Query the details of 5G voice VOLTE user number analysis data. Sub-process description: Output the detailed query results of 5G voice VOLTE user number analysis data. Data movement type: X. Data group: 5G voice VOLTE user number analysis data detailed query results. Data attributes: VOLTE initial call voice connection rate, VOLTE voice connection average delay, VOLTE final call voice connection average delay, VOLTE voice connection rate, date, VOLTE re-registration success rate, 5G voice VOLTE user number analysis, VOLTE network voice connection rate, VOLTE registration average delay, VOLTE initial call voice response rate, VOLTE initial registration success rate. |
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 latency index data analysis. Sub-process description: Input core network latency index data analysis request. Data movement type: E. Data group: system time. Data attribute: 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: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: Generate registration index analysis data table. Functional process: registration index analysis data statistics (HBASE library). Sub-process description: Input the statistics request of the registration index analysis data. Data movement type: E. Data group: data statistics operation instructions. Data attributes: statistical date, statistical method, dimension. |
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: export of business development indicator monitoring rule configuration data. Functional process: business development indicator monitoring rule configuration data export. Sub-process description: read the configuration data of business development indicator monitoring rules. Data movement type: R. Data group: business development indicator monitoring rule configuration data. Data attributes: effective or not, indicator Chinese name, KPI proportion, comparison condition, business development indicator, indicator English name, business development indicator monitoring rule configuration, poor quality threshold. |
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: Chatbot business indicator reason value data query. Functional process: query the details of the cause value data of Chatbot business indicators. Sub-process description: Read the detailed data of the reason value of the Chatbot business indicator. Data movement type: R. Data group: Chatbot business indicator cause value detail data. Data attributes: reason value, reason value of Chatbot business indicators, MSRP (REPORT (Req (Status (Code)))), Chatbot indicators, last SIP status code, process failure reason, first teardown message. |
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: VOLTE poor voice quality delay rule configuration data query. Function process: VOLTE poor voice quality delay rule configuration data list query. Sub-process description: Read the configuration data list information of VOLTE voice quality delay rule. Data movement type: R. Data group: VOLTE poor voice quality delay rule configuration data list information. Data attributes: quality factors of core network indicators (proportion of poor quality core network), quality factors of individual user indicators (according to the number of attempts), number of community users, quality factors of prefectural and city indicators (proportion of poor quality prefectures and cities), community The proportion of poor quality indicators, the average delay of VOLTE re-registration, the average delay of VOLTE initial registration, the configuration of VOLTE voice quality delay rules, the delay of successful third-party registration, the proportion of network element quality indicators, and VOLTE voice connection average latency. |
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 messaging service requirements, analysis and forecasting of 5G messaging terminal numbers. Trigger event: 5G message terminal analysis data query. Functional process: Detailed query of 5G message terminal analysis data. Sub-process description: Enter a request for querying the details of the 5G message terminal analysis data. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type. |
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: Deletion of VONR voice quality delay rule configuration data. Functional process: Delete the configuration data of VONR voice quality delay rule. Sub-process description: Input VONR poor voice quality delay rule configuration data deletion request. Data movement type: E. Data group: delete operation instruction. Data attributes: delete person, delete time. |
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 export. Functional process: terminal EPSFB delay data export. Sub-process description: Read the terminal EPSFB delay export template. Data movement type: R. Data group: terminal EPSFB delay export template. Data attribute: terminal EPSFB delay export template. |
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 fallback quality closed-loop data query. Functional process: EPSFB fallback quality closed-loop data list query. Sub-process description: Enter the query request for the EPSFB fallback quality closed-loop data list. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type. |
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, monitoring of 5G message indicators. Trigger event: Registration indicator monitoring data export. Functional process: export registration indicator monitoring data. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not. |
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: The business development indicator monitoring rule configuration data is added. Functional process: Added configuration data for business development indicator monitoring rules. Sub-process description: read rule verification business development indicator monitoring rule configuration data. Data movement type: R. Data group: business development indicator monitoring rules configure data verification rules. Data attributes: business development indicator monitoring rule configuration data non-null check, data format check. |
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: EPSFB voice service quality monitoring indicator data export. Functional process: EPSFB voice service quality monitoring index data export. Sub-process description: read the EPSFB voice service quality monitoring index export template. Data movement type: R. Data group: EPSFB voice service quality monitoring index export template. Data attribute: EPSFB voice service quality monitoring index 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 demand, early warning of 5G voice indicators. Trigger event: VONR voice indicator warning data is added. Functional process: VONR voice index early warning data is added. Sub-process description: return the newly added result of VONR voice index early warning data. Data movement type: X. Data group: newly added results of VONR voice index early warning data. Data attributes: whether the new result is successful, and the new time. |
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: Timing trigger VONR connection quality closed-loop data table generation task. Data movement type: E. Data group: system time. Data attribute: 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, analysis of key factors of poor quality business indicators. Trigger event: data query of key business factors of poor registration quality. Functional process: query the data list of key factors of poor registration quality business. Sub-process description: read the data list information of the key factors of poor registration quality business. Data movement type: R. Data group: data list information of key factors of poor registration quality business. Data attributes: core network indicators poor quality factors, UP2.4 terminal initial registration success times, initial registration success times, wireless indicators poor quality factors, poor quality factors proportion, registration poor business key factors, initial registration total delay, users Index quality factors, the number of initial registration requests, the total delay of re-registration, and the number of re-registration requests of UP2.4 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. 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: Save the statistical results of the group sending failure cause value data to the HBASE library. Data movement type: W. Data group: statistical results of group sending failure cause value data. Data attributes: last SIP status code, first demolition reason, MSRP (REPORT (Req (Status (Code)))), Reason (Protocol), mass sending index, index value, reason value, index name, mass sending failure reason value, process Failure reason, the first demolition message. |
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: Generate business development indicator analysis data table. Functional process: business development index analysis data table generation (GP business library). Sub-process description: Save the business development index analysis data table to the GP table library. Data movement type: W. Data group: business development indicator analysis data table. Data attributes: analysis of business development indicators, number of HTTP business successes, total TCP establishment delay (core network), total TCP establishment delay (wireless side), number of successful TCP establishments (core network), number of successful TCP establishments, HTTP response Total delay, the total number of authentications initiated by the terminal to the storage server. |
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 table is generated. Functional process: 5G voice EPSFB user number analysis data table generation (GP service library). Sub-process description: generate 5G voice EPSFB user number analysis abnormal data log write. Data movement type: W. Data group: 5G voice EPSFB user number analysis abnormal data log. Data attributes: error code, error description, 5G voice EPSFB user number analysis exception source data information. |
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: EPSFB fallback delay analysis data query. Functional process: EPSFB fallback delay analysis data list query. Sub-process description: Read the EPSFB fallback delay analysis data list information. Data movement type: R. Data group: EPSFB fallback delay analysis data list information. Data attributes: name of deterioration index, number of days of index deterioration, success rate of EPSFB initial call fall, recovery time of deterioration index, number of index deterioration periods, success rate of EPSFB final call fallback, proportion of index deterioration period of this month, number of normal index periods, EPSFB fallback Time delay analysis, description of deterioration indicators, and normal days of 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 voice quality perception analysis, poor quality analysis data export. Trigger event: display of poor quality terminal analysis data. Functional process: Display of poor quality terminal analysis data. Sub-process description: read the poor-quality terminal analysis data. Data movement type: R. Data set: Poor quality terminal analysis data. Data attributes: initial registration average delay, core network factors, proportion of poor quality indicators, poor quality terminal analysis, user factors, VoNR (voice) drop rate, initial registration success rate, terminal model. |
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 network element analysis. Trigger event: Export of call quality index data of poor-quality NEs. Functional process: Export call quality index data of poor quality network elements. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not. |
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 modification. Functional process: Modify the configuration data of P2P short message number demand prediction rules. 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. Data attributes: growth rate of P2P messages in n+3 months, growth rate of P2P messages in n+2 months, P2P SMS demand forecast rule configuration, growth rate of P2P messages in n+4 months, growth rate of P2P messages in n+1 months , the number of P2P messages this month, the growth rate of the number of P2P messages in n+8 months, and the number of months for which the indicator predicts historical 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 export. Functional process: registration class poor quality rule configuration data export. Sub-process description: read the configuration export template of registration class poor quality rules. Data movement type: R. Data group: Registration class poor quality rule configuration export template. Data attribute: Registration class poor quality rule configuration export template. |
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: registration latency indicator data collection. Functional process: register the latency index data collection interface. Sub-process description: read registration delay indicator data. Data movement type: R. Data group: register latency indicator data. Data attributes: average initial registration delay, average registration delay, total number of initial registrations, registration delay index, total number of re-registrations, number of successful initial registrations, and number of successful third-party registrations. |
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 end user forecast data export. Functional process: UP2.4 end user number forecast data export. Sub-process description: Input UP2.4 terminal user number forecast export request. Data movement type: E. Data group: UP2.4 terminal user number forecast export operation instruction. Data attributes: data time, city, equipment manufacturer. |
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 file transfer business data table. Functional process: poor quality file transfer business data statistics (HBASE library). Sub-process description: read statistical rules to perform statistical calculations on poor-quality file transfer business data. Data movement type: R. Data group: Statistical rules for poor quality file transfer business data. Data attributes: summary conditions, summary dimensions. |
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 details of the 5G message user number indicator data. Sub-process description: Enter a request for querying the details of the 5G message user number indicator data. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type. |
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 call quality indicator data in poor quality cells. Functional process: Query the call quality index data list of poor quality cells. Sub-process description: Read the call quality index data list information of poor quality cells. Data movement type: R. Data group: list information of call quality index data in poor quality cells. Data attributes: prefecture, city, number of poor quality indicators, cell, VoNR (voice) downlink average MOS, EPSFB (RTP uplink packet loss rate), EPSFB (RTP uplink MOS), EPSFB call drop rate, EPSFB (RTP downlink packet loss rate) , Call quality indicators in poor quality cells, VoNR (voice) drop rate, VoNR (voice) uplink average MOS. |
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: Read and convert the 5G voice EPSFB call duration analysis data. Data movement type: R. Data group: 5G voice EPSFB call duration analysis data. Data attributes: 5G voice EPSFB call duration analysis, EPSFB total connection delay measurement times (5T5), EPSFB total call connection delay (redirection mode), EPSFB total connection delay (5T4), EPSFB call duration growth rate , EPSFB connection total delay measurement times (5T4), EPSFB caller voice call times, EPSFB call connection total delay measurement times (redirection mode), date. |
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: Query the overall VONR delay data of the cell. Functional process: Query the details of the overall VONR delay data of the cell. Sub-process description: Read the detailed data of the overall VONR delay of the cell. Data movement type: R. Data group: Detailed data of the overall VONR delay of the cell. Data attributes: overall cell VONR delay, 5G core network total delay 1 measurement times (VoNR), IMS forwarding and called paging total delay (VoNR), called response total delay (VoNR), 5G core network time Delay 2 (VoNR), IMS domain total delay measurement times (VoNR), wireless total delay measurement times (VoNR). |
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, monitoring of 5G message indicators. Trigger event: business indicator monitoring data query. Functional process: query the details of business indicator monitoring data. Sub-process description: Enter a request for querying the business indicator monitoring data details. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type. |
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 details of P2P message index data of poor quality terminals. Sub-process description: Read the detailed data of P2P message indicators of poor quality terminals. Data movement type: R. Data group: detailed data of poor quality terminal P2P message indicators. Data attributes: tac, core network factor, terminal brand, wireless network factor, p2p message receiving success rate, conclusion, p2p message sending success rate, p2p message sending average delay, p2p message receiving average delay, poor quality terminal P2P message category index. |
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: The core network latency index data table is generated. Functional process: core network latency index data statistics (HBASE library). Sub-process description: read the core network delay index data. Data movement type: R. Data group: core network latency index data. Data attributes: 5G core network delay 1 (VoNR), 5G core network total delay 2 (VoNR), 5G core network total delay 2 (VNR2VNR), core network delay index, 5G core network total delay 2 measurement times (VoNR), 5G core network delay 1 (VNR2VNR), 5G core network delay 2 (VoNR), 5G core network total delay 1 measurement times (VNR2VNR), 5G core network total delay 1 (VoNR). |
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: VOLTE voice indicators early warning data query. Functional process: VOLTE voice indicator warning data list query. Sub-process description: read VOLTE voice index warning data list information. Data movement type: R. Data group: VOLTE voice indicator warning data list information. Data attributes: VOLTE initial registration average delay, VOLTE voice connection rate, VOLTE voice index warning, VOLTE final call voice network connection rate, VOLTE re-registration success rate, VOLTE registration average delay, VOLTE re-registration average delay. |
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: Export of poor-quality terminal business indicator data. Functional process: export of bad-quality terminal business index data. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not. |
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 indicator data upload. Functional process: core network latency index data upload. Sub-process description: Input the core network latency index data upload request. Data movement type: E. Data group: upload operation instructions. Data attributes: upload time, upload address. |
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: P2P poor quality terminal rule configuration data export. Functional process: P2P poor quality terminal rule configuration data export. Sub-process description: Input the P2P poor quality terminal rule configuration export request. Data movement type: E. Data group: P2P poor quality terminal rule configuration export operation instruction. Data attributes: data time, city, equipment manufacturer. |
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. Description of the sub-process: Input the request for exporting the prediction of the number of group text messages sent by UP2.4 terminals. Data movement type: E. Data group: UP2.4 terminal group text message number prediction export operation command. Data attributes: data time, city, equipment manufacturer. |
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: Read the account information of the 5G voice VOLTE user number analysis data server. Data movement type: R. Data group: 5G voice VOLTE user number analysis data server account information. Data attributes: 5G voice VOLTE user number analysis data server IP, account number, password. |
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 registration rule configuration data deletion. Functional process: EPSFB poor voice quality registration rule configuration data deletion. Sub-process description: Input the EPSFB poor voice quality registration rule configuration data deletion request. Data movement type: E. Data group: delete operation instruction. Data attributes: delete person, delete 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 messaging service requirements, analysis and forecasting of 5G messaging terminal numbers. Trigger event: 5G message terminal analysis data query. Functional process: 5G message terminal analysis data list query. Sub-process description: Enter a query request for the 5G message terminal analysis data list. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type. |
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 statistics (HBASE library). Sub-process description: Input VONR connection quality closed-loop data statistics request. Data movement type: E. Data group: data statistics operation instructions. Data attributes: statistical date, statistical method, dimension. |
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 export. Functional process: 5G voice VOLTE call duration analysis data export. Sub-process description: read the 5G voice VOLTE call duration analysis and export template. Data movement type: R. Data group: 5G voice VOLTE call duration analysis export template. Data attribute: 5G voice VOLTE call duration analysis 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 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: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not. |
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 P2P SMS prediction rule configuration data modification. Functional process: UP2.4 terminal P2P SMS prediction rule configuration data modification. Sub-process description: Input UP2.4 terminal P2P short message prediction rule configuration data modification request. Data movement type: E. Data group: modify the operation instruction. Data attributes: modification person, modification time. |
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: display of poor-quality cell analysis data. Functional process: display of poor-quality community analysis data. Sub-process description: Input the poor-quality cell analysis display request. Data movement type: E. Data group: display operation instructions. Data attributes: request time, requester, request type. |
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 registration class quality closed-loop data table generation. Functional process: VONR registration quality closed-loop data statistics (HBASE library). Sub-process description: Read VONR registration class quality closed-loop data. Data movement type: R. Data set: VONR registered quality closed-loop data. Data attributes: index normal value (1 point), VONR registration quality closed loop, index deterioration value (14 points), index normal value (13 points), index deterioration value (19 points), index deterioration value (21 points), index Normal value (18 points), index normal value (23 points), index normal value (11 points), index deterioration value (7 points). |
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 EPSFB delay data export. Functional process: Cell EPSFB delay data export. Sub-process description: export cell EPSFB delay data. Data movement type: X. Data group: cell EPSFB delay data. Data attributes: EPSFB initial call connection times, EPSFB average delay, cell EPSFB delay, total number of EPSFB final call fallbacks, total EPSFB initial call fallback times, date, cell. |
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 download. Functional process: P2P failure reason value data download. Sub-process description: input P2P failure cause value data download request. Data movement type: E. Data group: download operation instruction. Data attributes: download time, download format. |
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 statistics (HBASE library). Sub-process description: read statistical rules to perform statistical calculations on VONR connection-type quality closed-loop data. Data movement type: R. Data group: VONR connected quality closed-loop data statistical rules. Data attributes: summary conditions, summary dimensions. |
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: Return the modification result. Data movement type: X. Data group: UP2.4 end user number prediction rule configuration data modification results. Data attributes: modification time, change record. |
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, city ranking and trend of VoNR calling delay. Trigger event: VONR time delay ranking and trend data export. Functional process: Ranking and trend data export of VONR delay. Sub-process description: Export ranking and trend data of VONR delay. Data movement type: X. Dataset: Ranking and trending data for VONR latency. Data attributes: total called response delay (VoNR), ranking and trend of VONR delay, total wireless delay measurement times (VoNR), total wireless delay (VoNR), IMS domain total delay measurement times (VoNR), Called response total delay measurement times (VoNR), called response total delay (VoNR), IMS forwarding and called paging total delay measurement times (VoNR). |
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 the overall VONR delay data of the cell. Functional process: export the overall VONR delay data of the cell. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not. |
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 EPSFB delay data query. Functional process: Query the details of cell EPSFB delay data. Sub-process description: Input cell EPSFB delay data query request. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type. |
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: mass query of index prefecture and city ranking data. Functional process: query the ranking data list of cities and towns with mass distribution indicators. Description of the sub-process: Input the query request for the ranking data list of cities and towns with mass distribution indicators. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type. |
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: Read the VONR connection class quality closed-loop export template. Data movement type: R. Data group: VONR connected quality closed-loop export template. Data attribute: VONR connected quality closed-loop 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: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Triggering event: querying aggregated indicator data for message group sending. Functional process: Query the details of aggregated indicator data for group message sending. Sub-process description: output the detailed query results of aggregated indicator data of message group sending. Data movement type: X. Data group: the result of querying the details of aggregated indicator data for message group sending. Data attributes: Pager Mode message sending times (group sending), Pager Mode message receiving times (group sending), Large Mode message sending total delay (group sending), Pager Mode message sending total delay (group sending), Large Mode message sending times (group sending ), Large Mode message receiving delay (group sending), Large Mode MRSP message sending total delay (group sending), Large Mode MRSP message receiving delay (group sending), message group sending category aggregation 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: 5G message terminal number demand forecasting rule configuration data display. Functional process: 5G message terminal number demand forecasting rule configuration data display. Sub-process description: Input the 5G message terminal number demand prediction rule configuration display request. Data movement type: E. Data group: display operation instructions. Data attributes: request time, requester, request type. |
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: File transfer indicator monitoring rule configuration data export. Functional process: file transfer indicator monitoring rule configuration data export. Sub-process description: Read the configuration data of file transfer indicator monitoring rules. Data movement type: R. Data group: file transfer indicator monitoring rule configuration data. Data attributes: dynamic threshold position, KPI proportion, threshold type, indicator English name, comparison condition, file transfer indicator monitoring rule configuration, file transfer indicator, indicator Chinese name, indicator unit, poor quality threshold. |
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 delay rule configuration data modification. Functional process: VONR poor voice quality delay rule configuration data modification. Sub-process description: Input VONR poor voice quality delay rule configuration data modification request. Data movement type: E. Data group: modify the operation instruction. Data attributes: modification person, modification 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 monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: business failure reason value data query. Functional process: Query the details of the cause value data of business failure. Sub-process description: Enter a request for querying the business failure cause value data details. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type. |
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: save 5G voice VOLTE call time analysis and collection data. Data movement type: W. Data group: 5G voice VOLTE call duration analysis data. Data attributes: VOLTE initial call voice network connection rate, VOLTE initial registration success rate, VOLTE re-registration success rate, VOLTE initial call voice response rate, VOLTE voice connection average delay, VOLTE final call voice network connection rate, city , VOLTE initial registration average delay, VOLTE re-registration average delay, 5G voice VOLTE call duration analysis. |
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 call quality indicator data in poor quality cells. Functional process: Query the details of call quality index data in poor quality cells. Sub-process description: Enter a query request for details of call quality index data in poor-quality cells. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type. |
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 registration class quality closed-loop data export. Functional process: VONR registration class quality closed-loop data export. Sub-process description: Read the VONR registration class quality closed-loop export template. Data movement type: R. Data group: VONR registration class quality closed-loop export template. Data attribute: VONR registration class quality closed-loop 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: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: EPSFB voice demand forecast configuration data is added. Functional process: EPSFB voice demand forecasting configuration data is added. Sub-process description: Return the new result of EPSFB voice demand forecast configuration data. Data movement type: X. Data group: EPSFB voice demand forecasting configuration data newly added results. Data attributes: whether the new result is successful, and the new time. |
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: EPSFB voice demand forecast configuration data deletion. Functional process: EPSFB voice demand forecast configuration data deletion. Sub-process description: Delete EPSFB voice demand forecast configuration data. Data movement type: W. Data group: EPSFB voice demand forecast configuration data to be deleted. Data attribute: EPSFB network voice connection rate poor quality threshold, EPSFB user voice response rate poor quality threshold, EPSFB initial call voice network connection rate poor quality threshold, EPSFB voice demand forecast configuration, EPSFB voice connection rate poor quality threshold, EPSFB The poor quality threshold of the voice response rate of the final call, the poor quality threshold of the voice response rate of the EPSFB initial call, the poor quality threshold of the voice completion rate of the EPSFB final call, and the poor quality threshold of the voice connection rate of the EPSFB initial call. |
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 registration class quality closed-loop data table generation. Functional process: VONR registration quality closed-loop data statistics (HBASE library). Sub-process description: read the statistical rules to perform statistical calculations on the closed-loop data of VONR registration quality. Data movement type: R. Data group: VONR registration class quality closed-loop data statistical rules. Data attributes: summary conditions, summary dimensions. |
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 the overall VONR delay data of the cell. Functional process: export the overall VONR delay data of the cell. Sub-process description: Input the overall VONR delay derivation request of the cell. Data movement type: E. Data group: operation command for deriving the overall VONR delay of the cell. Data attributes: data time, city, equipment manufacturer. |
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 call quality indicator data in poor quality cells. Functional process: Query the details of call quality index data in poor quality cells. Sub-process description: Output query results of call quality index data details of poor-quality cells. Data movement type: X. Data group: detailed query results of call quality index data in poor quality cells. Data attributes: cell, number of poor quality indicators, EPSFB (RTP downlink MOS), VoNR (voice) drop rate, proportion of poor quality indicators, EPSFB (RTP uplink MOS), poor quality cell call quality indicators, EPSFB (RTP uplink packet loss rate), VoNR (voice) uplink average MOS. |
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. Triggering event: NE fallback aggregation dimension data query. Functional process: Query the details of NE fallback aggregation dimension data. Sub-process description: output the detailed query results of network element fallback aggregation dimension data. Data movement type: X. Data group: NE fallback aggregation dimension data details query results. Data attributes: the success rate of message received by the message center from the mobile phone, date, initial registration success rate of the UP2.4 terminal, the success rate of the message sent by the message center to the mobile phone, the success rate of the large mode message sent by the UP2.4 terminal (P2P), network The dimension of meta-fallback convergence, UP2.4 terminal re-registration success rate, UP2.4 terminal Pager Mode message sending success rate (P2P). |
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: EPSFB network connection analysis data query. Functional process: EPSFB network access analysis data details query. Sub-process description: input EPSFB network access analysis data details query request. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type. |
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 user number prediction analysis data export. Functional process: 5G voice VONR user number prediction analysis data export. Sub-process description: read 5G voice VONR user number prediction and analysis data. Data movement type: R. Data group: 5G voice VONR user number prediction and analysis data. Data attributes: number of VoNR active users in peak hour of month n-February, predicted number of VoNR registered users in peak hour of month n+2, number of active VoNR users in peak hour of month n-April, prediction and analysis of 5G voice VONR user numbers, peak value in month n-April The number of VoNR registered users per hour, the number of VoNR registered users at peak hour in forecast n+3 month, the number of VoNR active users at peak hour this month, date. |
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, city ranking and trend of VoNR calling delay. Trigger event: EPSFB time-lapse ranking and trend data export. Functional process: EPSFB latency ranking and trend data export. Sub-process description: Input the ranking and trend export request of EPSFB delay. Data movement type: E. Data group: EPSFB delay ranking and trend export operation instructions. Data attributes: data time, city, equipment manufacturer. |
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 fallback class quality closed-loop data table is generated. Functional process: EPSFB fallback quality closed-loop data table generation (GP business library). Sub-process description: save the EPSFB fallback quality closed-loop data table to the GP table library. Data movement type: W. Data group: EPSFB fallback quality closed-loop data table. Data attribute: index deterioration value (19 points), index deterioration value (17 points), index deterioration value (20 points), index normal value (8 points), index deterioration value (12 points), index deterioration value (23 points) , Index normal value (5 points), EPSFB fallback quality closed loop, index deterioration value (1 point), index deterioration value (13 points), index normal value (10 points). |
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: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not. |
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 network element analysis. Triggering event: Query for registration index data of poor quality NEs. Functional process: Query the details of registration index data of poor-quality NEs. Sub-process description: output the detailed query results of registration index data of poor quality network elements. Data movement type: X. Data group: query result of the detailed index data of poor-quality network element registration. Data attributes: number of calling initial registration delay measurements, poor quality network element registration indicators, called initial registration delay measurement times, total calling initial registration delay, initial registration request times, non-registration return times, initial registration total Delay, the number of called initial registration failures, the calling number of initial registration requests, the calling number of non-registered returns, and the number of initial registration delay measurements. |
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, monitoring of 5G message indicators. Trigger event: register indicator monitoring data query. Functional process: Query the details of registration indicator monitoring data. Sub-process description: output the query result of registration indicator monitoring data details. Data movement type: X. Data group: the query result of registration indicator monitoring data details. Data attributes: success rate of mobility registration, total delay of normal UE registration, total delay of UE shutdown registration, total delay of normal network side registration, number of attempts, success rate of normal network side registration, total mobility registration time Delay, registration indicator monitoring. |
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: EPSFB fallback delay analysis data query. Functional process: EPSFB fallback delay analysis data list query. Sub-process description: Input EPSFB fallback delay analysis data list query request. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type. |
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 mass-sending business data table. Functional process: Generation of poor-quality mass-sending business data tables (GP business library). Sub-process description: read poor-quality mass-sending business data. Data movement type: R. Data group: poor quality bulk business data. Data attributes: poor-quality group sending business, large (mode message reception success rate (group sending)), large (mode message receiving success times (group sending)), large (mode message sending times (group sending)), large (mode message receiving times ( Group sending)), conclusion of poor quality of group sending, prefecture and city, factor of poor quality of group sending, large (number of successful mode message sending (group sending)), large (mode message sending success rate (group sending)), large (mode message sending average time extension (mass)). |
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: N11 interface delay data download. Functional process: N11 interface delay data download. Sub-process description: download the delay data of the N11 interface. Data movement type: W. Data group: N11 interface delay data. Data attributes: N11 interface delay, ReleaseSMContext success total delay, N1N2MessageTransfer success times, UpdateSMContext request times, CreateSMContext success times, UpdateSMContext success total delay, N1N2MessageTransfer request times. |
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: VOLTE voice indicator warning data deletion. Functional process: VOLTE voice indicator warning data deletion. Sub-process description: read VOLTE voice indicator warning data. Data movement type: R. Data group: VOLTE voice indicators early warning data. Data attributes: VOLTE initial call voice connection rate, VOLTE final call voice network connection rate, VOLTE re-registration success rate, VOLTE voice connection rate, VOLTE voice indicator warning, VOLTE final call voice response rate, VOLTE initial call voice connection Average delay, average delay of VOLTE final call voice connection, VOLTE initial call voice network connection rate, VOLTE initial registration success rate, VOLTE initial call voice response rate. |
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 P2P service data tables. Functional process: Generation of poor-quality P2P business data tables (GP business library). Sub-process description: Save the poor-quality P2P business data table to the GP table library. Data movement type: W. Data set: poor quality P2P business data table. Data attributes: cities, core network factors of poor p2p service quality, large (number of mode message sending (p2p)), large (mode message sending success times (p2p)), page (mode message sending average delay (p2p)), page (mode message sending times (p2p)), poor quality P2P business, page (mode message sending success times (p2p)), page (mode message sending success rate (p2p)), date, p2p business quality conclusion. |
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: Display of business development indicator monitoring rule configuration data. Functional process: business development indicator monitoring rule configuration data display. Sub-process description: output and display the configuration data of business development indicator monitoring rules. Data movement type: X. Data group: business development indicator monitoring rule configuration data. Data attributes: comparison conditions, business development indicator monitoring rule configuration, whether it is effective, indicator unit, indicator Chinese name, business development indicator, KPI proportion, dynamic threshold position, indicator English name, threshold type. |