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: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: Export of prefecture-city registration aggregation dimension data. Functional process: Export of prefecture-city registration aggregation dimension data. Sub-process description: Input the export request of prefecture-city registration aggregation dimension. Data movement type: E. Data group: the command to export the aggregation dimension of prefecture-city registration. 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 service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 terminal user number prediction rule configuration data is added. Function process: UP2.4 terminal user number prediction rule configuration data is added. Sub-process description: Return the new result of UP2.4 terminal user number prediction rule configuration data. Data movement type: X. Data group: UP2.4 end user number prediction rule configuration data newly added results. Data attributes: whether the new result is successful, and the new 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, 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: Query the list of prefecture-level and poor-quality terminal indicator data. Sub-process description: Read the list information of the terminal indicator data list with poor quality at prefecture-level granularity. Data movement type: R. Data group: data list information of prefecture-level and poor-quality terminal indicators. Data attributes: terminal brand, average download delay of 5GM02 interface files, average initial registration delay, initial registration success rate, prefecture-level and poor quality terminal indicators, average http response delay, 5GM02 interface file upload success rate, http business success rate , 5GM02 interface file download success 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: 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: update the configuration data of the 5G message terminal number demand prediction rule. Data movement type: W. Data group: newly added 5G message terminal number demand forecasting rule configuration data. Data attributes: growth rate of the number of 5G message terminals in n+9, growth rate of the number of 5G message terminals in n+August, number of months of historical data forecast by indicators, growth rate of 5G message terminals in n+April, 5G message terminals in n+1 month Number growth rate, 5G message terminal number demand forecast rule configuration, n+2 month 5G message terminal number growth rate, n+7 month 5G message terminal number growth rate, n+3 month 5G message terminal number growth rate, n+6 month The growth rate of the number of 5G messaging terminals, n+the growth rate of the number of 5G messaging terminals in May. |
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: VOLTE voice demand forecast configuration data query. Functional process: VOLTE voice demand forecast configuration data list query. Sub-process description: output the query result of VOLTE voice demand forecast configuration data list. Data movement type: X. Data group: query result of VOLTE voice demand forecast configuration data list. Data attributes: VOLTE initial call voice connection rate poor quality threshold, VOLTE user voice response rate poor quality threshold, VOLTE initial call voice response rate poor quality threshold, VOLTE final call voice network connection rate poor quality threshold, VOLTE third-party registration success Poor rate threshold, VOLTE registration success rate poor quality threshold, VOLTE final call voice connection rate poor quality threshold, VOLTE voice connection rate poor quality threshold, VOLTE voice uplink RTP packet loss rate poor quality threshold, index forecast historical data months , VOLTE voice demand forecast configuration. |
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: Input the request for analyzing and exporting network elements with poor quality. Data movement type: E. Data group: operation instructions for analyzing and exporting poor-quality network elements. 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: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: generation of on-delay index data table. Functional process: connect delay indicator data statistics (HBASE library). Sub-process description: Save the statistical results of connection delay index data to the HBASE library. Data movement type: W. Data group: Statistical results of connection delay index data. Data attributes: total connection delay (VNR2VNR), total wireless delay measurement times (VoNR), total connection delay (VoNR), total connection delay measurement times (VNR2VNR), wireless delay (VoNR), wireless Delay (VNR2VNR), total wireless delay (VNR2VNR), total connection delay measurement times (VoNR), connection delay index. |
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 voice quality is poor and the connection rule configuration data is deleted. Functional process: Delete the connection rule configuration data for poor VOLTE voice quality. Sub-process description: read the configuration data of connection rules for poor voice quality of VOLTE. Data movement type: R. Data group: VOLTE poor voice quality connection rule configuration data. Data attributes: the number of users in the community, the proportion of poor network element quality indicators, the 4G network connection rate of VOLTE call fallback, the quality factor of individual user indicators (according to the number of attempts), the configuration of VOLTE voice quality poor connection rules, and the success rate of EPS fallback , Factors of poor quality of core network indicators (proportion of core network with poor quality), proportion of poor quality indicators of 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 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 query. Sub-process description: output the detailed query results of 5G voice VONR call duration prediction analysis data. Data movement type: X. Data group: 5G voice VONR call duration prediction analysis data detailed query results. Data attributes: VoNR call drop rate in n+3 months, VoNR voice connection rate in this month, VoNR voice connection rate in n-2 months, prefecture and city, 5G voice VONR call duration prediction analysis, VoNR voice connection rate in n+1 month , n-4 month VoNR drop rate, n+2 month VoNR drop rate, n-1 month VoNR voice connection rate, n-4 month VoNR voice connection rate. |
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 export. Functional process: VONR voice demand forecast configuration data export. Sub-process description: Read the VONR voice demand forecast configuration export template. Data movement type: R. Data group: VONR voice demand forecast configuration export template. Data attribute: VONR voice demand forecast configuration 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: 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 list of key factors of P2P poor quality business. Sub-process description: Input the query request for the data list of key factors of P2P poor quality business. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, 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 latency index data of poor-quality cells. Functional process: Inquire about the details of the time delay index data of poor-quality cells. Sub-process description: Read the detailed data of delay indicators in poor-quality cells. Data movement type: R. Data group: Detailed data of time delay indicators of poor quality cells. Data attributes: average voice connection delay for final calls, average re-registration delay, poor-quality cell delay indicators, average uplink voice delay (RTCP), average voice connection delay for initial calls, and average voice connection delay , Third-party registration success delay, cell, voice downlink average delay (RTCP). |
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 of terminal information and data with poor core network quality. Functional process: Query the details of terminal information and data with poor core network quality. Sub-process description: Output the detailed query results of terminal information data with poor core network quality. Data movement type: X. Data group: query results of detailed information and data of terminals with poor core network quality. Data attributes: http average response delay, 5GM02 interface file download average delay, 5GM02 interface file upload average delay, date, 5GM02 interface file download success rate, tac, core network quality terminal information, UP2.4 terminal initial registration success rate, initial registration success 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 quality perception analysis, poor quality terminal rule configuration. Trigger event: display of terminal rule configuration data with poor business development quality. Functional process: Display of terminal rule configuration data with poor business development quality. Description of the sub-process: Input the display request of the terminal rule configuration with poor service development quality. 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: 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 the statistical rules to perform statistical calculations on the poor quality indicator data of the file transfer category. Data movement type: R. Data group: Statistical rules for poor quality indicators of file transfers. 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 monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: Chatbot business index cause value data table generation. Functional process: Chatbot business indicator cause value data table generation (GP business library). Sub-process description: Save the Chatbot business indicator cause value data table to the GP table library. Data movement type: W. Data group: Chatbot business indicator cause value data table. Data attributes: last SIP status code, MSRP (REPORT (Req (Status (Code)))), index value, first teardown message, first teardown SIP status code, Chatbot service index reason value, first teardown reason. |
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: export of on-delay indicator data. Functional process: Data export of on-time delay indicators. Sub-process description: read the on-delay index data. Data movement type: R. Data group: on-delay index data. Data attributes: total connection delay measurement times (VNR2VNR), connection total delay (VNR2VNR), wireless total delay measurement times (VNR2VNR), connection delay (VoNR), wireless delay (VoNR), connection Total delay measurement times (VoNR), wireless delay (VNR2VNR), connection delay 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: uploading of on-delay indicator data. Functional process: upload the connection delay index data. Sub-process description: read the on-delay index data. Data movement type: R. Data group: on-delay index data. Data attributes: connection delay index, wireless delay (VoNR), total wireless delay (VoNR), total connection delay (VoNR), connection delay (VNR2VNR), total connection delay measurement times (VNR2VNR ), wireless delay (VNR2VNR), and total connection 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: intelligent analysis of VONR calling delay, city ranking and trend of VoNR calling delay. Trigger event: VONR time delay ranking and trend data query. Functional process: Query the ranking and trend data details of VONR delay. Sub-process description: Output the ranking and trend data query results of VONR delay. Data movement type: X. Data group: detailed query results of ranking and trend data of VONR delay. Data attributes: VONR delay ranking and trend, IMS forwarding and called paging total delay measurement times (VoNR), cities, 5G core network total delay 1 (VoNR), date, connection delay (VoNR) , 5G core network total delay 2 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 news indicators, city ranking and trend analysis. Trigger event: Export of file transfer indicator city trend analysis data. Functional process: file transfer indicators, city trend analysis data export. Sub-process description: Read the file transfer indicator city trend analysis data. Data movement type: R. Data group: file transfer indicators city trend analysis data. Data attributes: date, file transfer index city trend analysis, 5GM02 interface file upload success rate, 5GM02 interface file download total delay, 5GM02 interface file upload total delay, 5GM02 interface file upload total times, 5GM02 interface file download success times. |
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 overall VONR delay data list of the cell. Sub-process description: Read the overall VONR delay data list information of the cell. Data movement type: R. Data group: the overall VONR delay data list information of the cell. Data attributes: total called response delay (VoNR), overall cell VONR delay, date, connection delay (VoNR), total connection delay (VoNR), total wireless delay (VoNR), total called response delay Latency 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: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: EPSFB fallback delay analysis data export. Functional process: EPSFB fallback delay analysis data export. Sub-process description: Input EPSFB fallback delay analysis export request. Data movement type: E. Data group: EPSFB fallback delay analysis and export operation instructions. 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 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: generation of data table of cause value of mass sending failure (GP business library). Sub-process description: Read the verification rules to verify the data of the cause value of the mass sending failure. Data movement type: R. Data group: data verification rules for group sending failure cause values. Data attributes: first demolition SIP status code, reason value, MSRP (REPORT (Req (Status (Code)))), group sending indicators, group sending failure reason value, last SIP status code, indicator name, Reason (Protocol), process failure reason. |
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: Save the time-delayed download data of the N26 interface. Data movement type: W. Data group: N26 interface delay download data. Data attribute: FWD (RELOC (CMP (NOTIF success times))), CONTEXT (REQ total delay), FWD (RELOC (REQ total delay)), N26 interface delay, CONTEXT (REQ success times), FWD (RELOC (CMP (NOTIF request times))), FWD (RELOC (REQ success 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: 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: update EPSFB poor voice quality registration rule configuration data. Data movement type: W. Data group: the deleted EPSFB poor voice quality registration rule configuration data. Data attributes: initial registration success rate of EPSFB callers, proportion of poor terminal quality indicators, quality factors of core network indicators (proportion of poor quality core network), EPSFB voice quality poor registration rule configuration, number of community users, EPSFB initial registration success rate, EPSFB called initial registration success rate, and the proportion of poor quality indicators in the community. |
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: Query the details of VoNR delay data of VoNR calls in the community. Sub-process description: read the detailed data of the VoNR call delay of the cell VoNR. Data movement type: R. Data group: Detailed data of the VoNR call delay of the cell VoNR. Data attributes: IMS domain total delay (VNR2VNR), cell VoNR call VoNR delay, 5G core network total delay 1 measurement times (VNR2VNR), date, wireless total delay (VNR2VNR), called response total delay (VNR2VNR ), the total response delay of the called party (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: 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: update UP2.4 terminal user number prediction rule configuration data. Data movement type: W. Data group: modified UP2.4 terminal user number prediction rule configuration data. Data attribute: growth rate of UP2.4 terminal 5G message users in n+May, growth rate of UP2.4 terminal 5G message users in n+August, n+April growth rate of UP2.4 terminal 5G message users, n+ January UP2.4 terminal 5G message user growth rate, UP2.4 terminal user number forecast rule configuration, n+7 UP2.4 terminal 5G message user number growth rate, n+3 UP2.4 terminal 5G message user number Growth rate, the number of 5G message users of UP2.4 terminals this month, n+the growth rate of the number of 5G message users of UP2.4 terminals in September. |
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: input new request for configuration data of business development indicator monitoring rules. 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: 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: Generate and write abnormal data logs of poor-quality P2P services. Data movement type: W. Data group: abnormal data logs of poor-quality P2P services. Data attributes: error code, error description, abnormal source data information of poor-quality P2P business. |
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 query. Functional process: Query the details of EPSFB voice service quality monitoring index data. Sub-process description: Input the query request for EPSFB voice service quality monitoring index 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: 5G voice quality perception analysis, poor quality cell analysis. Triggering event: Query of registration index data of poor-quality communities. Functional process: Query the details of registration index data of poor-quality communities. Sub-process description: Enter a query request for the details of registration index data of poor-quality communities. 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, poor quality terminal rule configuration. Trigger event: export of chatbot terminal rule configuration data with poor quality. Functional process: Chatbot poor quality terminal rule configuration data export. Sub-process description: export chatbot poor quality terminal rule configuration data. Data movement type: X. Data group: chatbot poor quality terminal rule configuration data. Data attributes: rule name, user uplink to chatbot establishment success rate index threshold, operator, unit, whether it takes effect, proportion of poor quality cities, chatbot downlink to user establishment average delay index threshold, number, chatbot poor quality terminal rule configuration , chatbot downlink to user establishment success rate index threshold, user uplink to chatbot establishment average delay index threshold. |
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: generate VONR connection quality closed-loop data table. Data movement type: W. Data set: VONR connected quality closed-loop data table. Data attributes: index normal value (20 points), index normal value (9 points), index degradation value (5 points), VoNR origination (voice) connection average delay, VONR connection quality closed loop, degradation index description, Index normal value (4 points), index deterioration value (4 points), index normal value (0 point). |
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: export of P2P & group message warning data. Functional process: P2P & group message early warning 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: 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 analysis. Sub-process description: Input 5G voice VOLTE call duration analysis 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: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: Chatbot business index cause value data table generation. Functional process: Chatbot business indicator cause value data table generation (GP business library). Sub-process description: Generate Chatbot business indicator reason value abnormal data log write. Data movement type: W. Data group: Chatbot business indicator cause value abnormal data log. Data attributes: error code, error description, abnormal source data information of Chatbot business indicator cause 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: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Data query of poor quality indicators for business development. Functional process: Inquiry about the details of business development quality indicator data. Sub-process description: Read the detailed data of business development category poor quality indicators. Data movement type: R. Data group: detailed data of poor quality indicators for business development. Data attributes: the number of first TCP transaction responses, poor quality indicators for business development, total TCP establishment delay, number of HTTP service establishment failures (client rejection), average HTTP response delay, total number of HTTP business requests, TCP link establishment The number of successful requests to the first transaction, the total delay of HTTP responses, the number of abnormal terminations of HTTP services (client RST), and the total delay of TCP establishment (wireless side). |
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 collection interface. Sub-process description: read 5G voice VONR user number analysis data. Data movement type: R. Data group: 5G voice VONR user number analysis data. Data attributes: prefectures and cities, number of successful establishment of VoNR dedicated load (called), number of times of establishment of VoNR dedicated load (calling), number of successful establishment of VoNR dedicated load (calling), number of failed establishment of VoNR dedicated load (called), VoNR The number of dedicated load establishment failures, the growth rate of the number of active VONR users, the analysis of the number of 5G voice VONR users, the number of failed VoNR dedicated load establishments (calling), and the number of VoNR untriggered dedicated load establishments (called). |
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: Return the modification result. Data movement type: X. Data group: P2P short message quantity demand prediction rule configuration data modification result. Data attributes: modification time, change record. |
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: Poor quality terminal group message index data query. Functional process: Query the index data list of group messages sent by poor-quality terminals. Sub-process description: Input the query request for the index data list of group messages sent by poor-quality terminals. 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: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: registration latency indicator data query. Functional process: query the registration delay index data list. Sub-process description: Read the registration delay index data list information. Data movement type: R. Data group: Register the latency indicator data list information. Data attributes: average initial registration delay, registration delay index, average registration delay, successful third-party registration delay, successful re-registration times, total third-party registration times, successful third-party registration times, average re-registration delay, initial Number of successful 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: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: UP2.4 terminal 5G message indicator data download. Function process: UP2.4 terminal 5G message indicator data download. Sub-process description: read UP2.4 terminal 5G message indicator data. Data movement type: R. Data group: UP2.4 terminal 5G message index data. Data attributes: UP2.4 terminal Pager Mode message receiving delay (P2P), UP2.4 terminal 5G message indicators, UP2.4 terminal Large Mode message receiving delay (P2P), UP2.4 terminal 5G message drop-down times of MMS, UP2.4 terminal Pager Mode message sending total delay (P2P), UP2.4 terminal Pager Mode message sending times (P2P), UP2.4 terminal Pager Mode message reception success times (P2P), UP2.4 terminal Pager Mode message reception Times (P2P), UP2.4 terminal Large Mode message sending success times (P2P), UP2.4 terminal Pager Mode message sending average delay (P2P), UP2.4 terminal Large Mode message sending success rate (P2P). |
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 query. Function process: 5G voice VONR call duration analysis data details query. Sub-process description: output the detailed query results of 5G voice VONR call duration analysis data. Data movement type: X. Data group: 5G voice VONR call duration analysis data details query results. Data attributes: VoNR call fallback 4G network connection times (called), VoNR call fallback 4G network connection times (called), 5G voice VONR call duration analysis, VoNR call fallback 4G network connection times (calling), Number of times VoNR calls fall back to the 4G network and are not connected, prefectures and cities, times of 4G normal release after VoNR calls are connected (called), times of VoNR calls fallback to 4G network connections, growth rate of VONR call duration, normal release after VoNR calls are connected times (called). |
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 latency index data of poor-quality cells. Functional process: Query the data list of time delay indicators of poor quality cells. Sub-process description: output the list query results of the time delay index data of poor quality cells. Data movement type: X. Data group: the query result of the time delay index data list of poor quality cells. Data attributes: average video connection delay, average voice downlink delay (RTCP), re-registration average delay, voice uplink average delay (RTCP), registration average delay, voice average delay (RTCP), poor quality cell Latency indicators, voice downlink average delay (V2V (RTCP)), cell. |
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: 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: 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 5G voice VOLTE call duration analysis data. Data movement type: R. Data group: 5G voice VOLTE call duration analysis data. Data attributes: VOLTE initial-call voice connection rate, VOLTE initial-call voice connection average delay, 5G voice VOLTE call duration analysis, VOLTE re-registration success rate, VOLTE initial-call voice network completion rate, VOLTE final-call voice connection average Time delay, prefecture and city. |
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: Query the list of prefecture-level and poor-quality terminal indicator data. Sub-process description: Output the list query results of the city-level poor-quality terminal indicator data list. Data movement type: X. Data group: query results of the data list of prefecture-level and poor-quality terminal indicators. Data attributes: terminal brand, average download delay of 5GM02 interface files, average initial registration delay, initial registration success rate, prefecture-level and poor quality terminal indicators, average http response delay, 5GM02 interface file upload success rate, http business success rate , 5GM02 interface file download success 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 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: Output the query results of the poor-quality terminal file transfer index data list. Data movement type: X. Data group: the query result of the poor quality terminal file transfer index data list. Data attributes: poor-quality terminal file transfer indicators, wireless network factors, 5GM02 interface file upload success rate, 5GM02 interface file upload average delay, city factors, user factors, terminal model, 5GM02 interface file download average delay, 5GM02 interface File download success rate, terminal brand, and core network factors. |
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: read the core network delay index data. Data movement type: R. Data group: core network latency index data. 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: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: Export of aggregated dimension data with poor terminal quality. Functional process: Export of aggregated dimension data with poor terminal quality. Sub-process description: Input the request for exporting the aggregated dimension of poor quality of the input terminal. Data movement type: E. Data group: the export operation command of the aggregation dimension with poor terminal quality. 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 requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data collection. Functional process: 5G voice VONR call duration analysis data analysis. Sub-process description: Input 5G voice VONR call duration analysis 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: export of registered indicator analysis data. Functional process: export of registration index analysis data. Sub-process description: Read the registration index analysis export template. Data movement type: R. Data group: registration class index analysis export template. Data attribute: registration class indicator 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: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: EPSFB poor voice quality registration rule configuration data modification. Functional process: Modify the configuration data of EPSFB poor voice quality registration rules. Sub-process description: Modify the configuration data of EPSFB poor voice quality registration rules. Data movement type: W. Data group: EPSFB poor voice quality registration rule configuration data to be modified. Data attributes: the proportion of poor quality indicators of network elements, the quality factors of individual user indicators (according to the number of attempts), the quality factors of prefectural and city indicators (proportion of poor quality prefectures and cities), the initial registration success rate of EPSFB callers, and the poor quality of terminals Index ratio, EPSFB initial registration success rate, EPSFB poor voice quality registration rule configuration. |
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 details query. Sub-process description: Enter the query request for P2P failure reason value 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: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: user perception aggregated dimension data display. Functional process: user perception aggregation dimension data display. Sub-process description: Read user-perceived aggregation dimension data. Data movement type: R. Data group: User-perceived aggregation dimension data. Data attributes: success rate of HTTP business, average delay of message downlinking from Chatbot to user, success rate of message uplinking from user to Chatbot, success rate of TCP establishment (core network), average delay of message downlinking from UP2.4 terminal Chatbot to user, The success rate of TCP establishment, the success rate of uplink messages from UP2.4 terminal users to Chatbot, the success rate of downlink messages from UP2.4 terminal Chatbot to users, and the aggregation dimension of user perception. |
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 deletion. Functional process: VONR voice demand forecast configuration data deletion. Sub-process description: delete VONR voice demand forecast configuration data. Data movement type: W. Data group: VONR voice demand forecast configuration data to be deleted. Data attribute: VONR initial call voice network connection rate poor quality threshold, VONR initial call voice response rate poor quality threshold, VONR registration success rate poor quality threshold, VONR user voice response rate poor quality threshold, VONR network voice connection rate poor quality Threshold, VONR initial call voice completion rate poor quality threshold, VONR re-registration success rate poor quality threshold, VONR voice demand forecast configuration, VONR final call voice completion rate 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: 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: Inquiry about the data details of the key factors of poor registration quality business. Sub-process description: read the detailed data of the key factors of poor registration quality business. Data movement type: R. Data group: detailed data of key factors of poor registration quality business. Data attributes: total delay of re-registration, number of successful initial registrations, total delay of UP2.4 terminal re-registration, key factors of poor registration quality business, factors of poor quality of wireless indicators, proportion of poor quality factors, factors of poor quality of core network indicators, The number of re-registration requests of UP2.4 terminals, the poor quality factors of prefectural and city indicators, and the number of successful initial registrations 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: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message terminal number indicator data query. Functional process: Query the list of 5G message terminal number index data. Sub-process description: output the query result of the 5G message terminal number index data list. Data movement type: X. Data group: 5G message terminal number index data list query result. Data attributes: UP2.4 terminal Pager Mode message reception times (P2P), UP2.4 terminal Large Mode message sending average delay (P2P), UP2.4 terminal Large Mode message receiving delay (P2P), UP2.4 terminal Pager Mode message sending success times (P2P), UP2.4 terminal initial registration success times, UP2.4 terminal Pager Mode message sending total delay (P2P), UP2.4 terminal Pager Mode message receiving success times (P2P), UP2.4 Terminal Large Mode message sending success rate (P2P), 5G message terminal number 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, call auxiliary delay statistics. Trigger event: N11 interface delay data query. Function process: N11 interface delay data list query. Sub-process description: read the N11 interface delay data list information. Data movement type: R. Data group: N11 interface delay data list information. Data attributes: the total delay of ReleaseSMContext success, the number of successful UpdateSMContext, the number of N1N2MessageTransfer requests, the total delay of CreateSMContext success, the number of successful ReleaseSMContext, the number of successful N1N2MessageTransfer, and the delay of N11 interface. |
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: Read the data list information of the cause value of the business failure. Data movement type: R. Data group: business failure reason value data list information. Data attributes: reason value, cause value of business failure, indicator name, last SIP status code, business development indicators, first dismantling SIP status code, first dismantling message, first dismantling reason, indicator value, MSRP(REPORT(Req(Status(Code )))). |
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: Inquiry about the details of registration index data of poor-quality terminals. Sub-process description: Read the detailed data of registration indicators of poor-quality terminals. Data movement type: R. Data group: detailed data of poor-quality terminal registration indicators. Data attributes: user factors, poor quality terminal registration indicators, wireless network factors, tac, city factors, average registration delay, conclusion, registration success rate. |
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: update VONR voice demand forecast configuration data. Data movement type: W. Data group: newly added VONR voice demand forecast configuration data. Data attributes: VONR re-registration success rate poor quality threshold, VONR final call voice response rate poor quality threshold, index forecast historical data months, VONR voice demand forecast configuration, VONR initial call voice response rate poor quality threshold, VONR user voice response rate Poor quality threshold, VONR voice connection rate poor quality threshold, VONR final call voice network connection rate poor quality threshold, VONR initial call voice connection rate poor quality threshold, VONR initial call voice network connection rate (V2V poor quality threshold) , VONR initial registration success rate 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, multi-dimensional aggregation and presentation. Trigger event: display of aggregated dimension data with poor terminal quality. Functional process: Display of aggregated dimensional data with poor terminal quality. Sub-process description: Read terminal poor-quality aggregation dimension data. Data movement type: R. Data group: Aggregate dimensional data with poor terminal quality. Data attributes: UP2.4 terminal Pager Mode message receiving success rate (group sending), UP2.4 terminal Chatbot downlink message success rate to users, UP2.4 terminal Large Mode message receiving success rate (group sending), time period, UP2.4 terminal Pager Mode message sending success rate (group sending), UP2.4 terminal Large Mode message sending success rate (group sending), terminal poor quality aggregation dimension, UP2.4 terminal 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, call auxiliary delay statistics. Trigger event: N26 interface delay data download. Functional process: N26 interface delay data download. Sub-process description: Input N26 interface delay data download request. Data movement type: E. Data group: download operation instruction. Data attributes: download time, download format. |
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 export. Functional process: P2P poor quality rule configuration data export. Sub-process description: input P2P class poor quality rule configuration export request. Data movement type: E. Data group: P2P poor quality 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: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: poor quality P2P service data query. Functional process: Query the details of poor-quality P2P business data. Sub-process description: output the detailed query results of poor-quality P2P business data. Data movement type: X. Data group: query results of poor quality P2P business data details. Data attributes: large (average message sending delay in mode (p2p)), poor quality P2P services, factors of poor p2p service cities, cities, page (average message sending delay in mode (p2p)), large (mode message sending success rate (p2p)), large (number of successful mode message sending (p2p)). |
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: modification of analysis data for poor-quality terminals. Functional process: modify the analysis data of poor-quality terminals. Sub-process description: update the poor-quality terminal analysis data. Data movement type: W. Data set: Modified poor quality terminal analysis data. Data attributes: initial registration average delay, city factors, EPS fallback success rate, VoNR (voice) drop rate, terminal model, initial registration success rate, poor quality terminal analysis, user factors, terminal brand, proportion of poor quality indicators , After the VoNR call is connected, the success rate of the 4G network drops. |
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: Export VONR call drop solution data. Data movement type: X. Data group: VONR drop call solution data. Data attributes: days of index degradation, VONR call drop solution, index compliance rate, VoNR (voice) upstream RTP packet loss rate, VoNR (voice) downstream RTP packet loss rate, percentage of index degradation days this month, and description of degradation 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: 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: Timing triggers the generation task of 5G voice EPSFB user number analysis data table. 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 messaging service indicators, key indicators and trends of business development. Trigger event: 5G message sending key indicator data query. Functional process: Query the details of key indicator data for 5G message sending. Sub-process description: Input 5G message to send query request for key indicator 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: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: display of aggregated dimension data with poor terminal quality. Functional process: Display of aggregated dimensional data with poor terminal quality. Sub-process description: Input terminal poor quality aggregation dimension 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: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: the collection of registered index analysis data. Functional process: registration index analysis data collection. Sub-process description: Input the registration class index analysis data collection request. Data movement type: E. Data group: system time. Data attribute: system 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: update EPSFB voice demand forecast configuration data. Data movement type: W. Data group: the deleted EPSFB voice demand forecast configuration data. 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: 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: 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: registration latency indicator data collection. Functional process: registration delay index data collection. Sub-process description: Read the verification rules to verify the registration delay indicator data server account information. Data movement type: R. Data group: registration delay index data server IP verification rules. Data attributes: verification rules for registration delay indicator data server IP, account number, and password. |
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: Export of configuration data for business development class poor quality rules. Functional process: business development class poor quality rule 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: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: Export of terminal rule configuration data with poor service development quality. Functional process: export of terminal rule configuration data with poor business development quality. Sub-process description: read the configuration export template of the terminal rule configuration with poor business development quality. Data movement type: R. Data group: Export template for rule configuration of terminals with poor business development quality. Data attribute: Export template for rule configuration of terminals with 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: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: registration class indicator analysis data query. Functional process: query the registration index analysis data list. Sub-process description: Enter the query request for the list of registration index analysis data. 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 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: The output shows the configuration data of UP2.4 terminal P2P SMS prediction rules. Data movement type: X. 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: 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: The display of aggregated dimension data reported by the community. Functional process: display of aggregated dimension data reported by the community. Description of the sub-process: Input the display request of the aggregation dimension reported by the community. 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: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: The configuration data of the poor quality rule of the business development category is added. Functional process: Added new configuration data for business development category poor quality rules. Sub-process description: read rule verification business development class poor quality rule configuration data. Data movement type: R. Data group: Configure data verification rules for poor quality rules of business development. Data attributes: business development class poor quality 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: intelligent analysis of VONR calling delay, call auxiliary delay statistics. Trigger event: N11 interface delay data query. Functional process: Query the details of the delay data of the N11 interface. Sub-process description: Read the detailed data of the N11 interface delay. Data movement type: R. Data group: N11 interface delay details data. Data attributes: ReleaseSMContext request times, ReleaseSMContext success total delay, N1N2MessageTransfer success times, N1N2MessageTransfer success total delay, UpdateSMContext success times, N11 interface delay, UpdateSMContext success total delay, N1N2MessageTransfer request times, CreateSMContext success times, ReleaseSMContext success times, CreateSMContext request times. |
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: save the connection delay index data table to the GP table library. 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: 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 overall VONR delay data query. Functional process: query the terminal overall VONR delay data list. Sub-process description: read the overall VONR delay data list information of the terminal. Data movement type: R. Data group: the overall VONR delay data list information of the terminal. Data attributes: total wireless delay (VoNR), 5G core network total delay 2 measurement times (VoNR), connection total delay measurement times (VoNR), wireless delay (VoNR), 5G core network total delay 1 measurement Number of times (VoNR), overall terminal VONR delay, IMS forwarding and called paging delay (VoNR), tac, total called response delay measurement times (VoNR), 5G core network delay 2 (VoNR), IMS forwarding And called paging total delay (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: 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: Read and analyze the rules to analyze the core network delay index data. Data movement type: R. Data group: core network latency index data analysis rules. Data attributes: file conversion specification, abnormal character processing 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: 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: download the time-delay index data of poor-quality cells. Data movement type: W. Data group: Delay index data of poor quality cells. Data attributes: average voice delay (RTCP), poor-quality cell delay indicators, average voice delay (V2V (RTCP)), average initial registration delay, average voice connection delay, average registration delay, final call The average video connection delay. |
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: Delete the VONR poor voice quality delay rule configuration data. Data movement type: W. Data group: configuration data of VONR poor voice quality delay rule to be deleted. Data attributes: VONR voice connection average delay, VONR initial registration average delay, VONR poor voice quality delay rule configuration, core network indicators poor quality factors (proportion of poor quality core network), individual user indicators poor quality factors (according to number of attempts), quality factors of prefecture-city indicators (proportion of poor-quality prefectures and cities), the number of indicators participating in the judgment of poor-quality communities, the number of community users, the proportion of network element quality indicators, the average registration delay of VONR, and the third-party VONR Delay for successful registration. |
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 poor-quality network elements is added. Functional process: The analysis data of poor quality network elements is added. Sub-process description: read the analysis data of poor-quality network elements. Data movement type: R. Data group: poor quality network element analysis data. Data attributes: prefecture, city, poor quality NE analysis, poor quality NE, VoNR (voice) downlink average MOS, VoNR (voice) uplink average MOS, initial registration success rate, EPSFB (RTP downlink packet loss rate), initial registration average delay. |
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. Triggering event: Analysis data query of low-quality terminal delay index factors. Functional process: Query the data list of the analysis data list of the delay index factor of the poor quality terminal. Sub-process description: Input a list query request for analyzing data list of delay index factors of poor-quality terminals. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, 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 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: Input the request for modifying the analysis data of the poor quality cell. 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: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Export of poor quality load indicator data. Functional process: data export of poor quality load indicators. Sub-process description: read the poor quality load indicator data. Data movement type: R. Data group: poor quality load index data. Data attributes: UP2.4 terminal 5G message terminal growth rate, poor quality load index, 5G message user load threshold, 5G message user growth rate, city, date, UP2.4 terminal 5G message terminal number, current 5G message user number, Growth rate of UP2.4 terminal 5G message users. |
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: output the query result of EPSFB fallback quality closed-loop data list. Data movement type: X. Data group: EPSFB fallback quality closed-loop data list query result. Data attributes: index deterioration value (17 points), index deterioration value (6 points), EPSFB fallback success rate, index normal value (0 points), EPSFB final call fallback success rate, EPSFB fallback quality closed loop, index deterioration value (8 points), indicator degradation value (21 points), EPSFB average delay, and index normal value (13 points). |
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 list of registered index data of poor-quality network elements. Sub-process description: Input a query request for the list of index data of registration class of poor-quality network elements. 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: 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: 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: The core network latency index data table is generated. Functional process: core network latency index data statistics (HBASE library). Sub-process description: Input the core network latency index data statistics request. Data movement type: E. Data group: data statistics operation instructions. Data attributes: statistical date, statistical method, dimension. |
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 closed-loop data query. Functional process: query the EPSFB call quality closed-loop data list. Sub-process description: Input the EPSFB call quality class quality closed-loop 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: 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: input P2P short message number demand prediction rule configuration export request. Data movement type: E. Data group: P2P short message number demand prediction 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: 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: 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: P2P indicator monitoring rule configuration data display. Functional process: P2P indicator monitoring rule configuration data display. Sub-process description: read the P2P indicator monitoring rule configuration data. Data movement type: R. Data group: P2P indicator monitoring rule configuration data. Data attributes: threshold type, p2p business indicators, indicator unit, indicator English name, indicator Chinese name, whether it is effective, KPI proportion, P2P indicator monitoring rule configuration, comparison conditions, dynamic threshold position. |
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 query. Functional process: query the details of 5G voice VONR user number prediction and analysis data. Sub-process description: Output the detailed query results of 5G voice VONR user number prediction and analysis data. Data movement type: X. Data group: 5G voice VONR user number prediction and analysis data detailed query results. Data attributes: number of VoNR registered users in peak hours of month n-1, prefectures and cities, number of VoNR registered users in peak hours of months n-2, forecast analysis of 5G voice VoNR users, forecast number of VoNR active users in peak hours of month n+3, this month Number of VoNR active users in peak hour, predicted number of active VoNR users in peak hour in month n+2, number of active VoNR users in peak hour in this month, number of registered VoNR users in peak hour in this month, number of active VoNR users in peak hour in month n-4, n- The number of VoNR registered users at the peak hour in April. |
End of preview. Expand
in Dataset Viewer.
README.md exists but content is empty.
- Downloads last month
- 46