A method and system for simulating wireless device signaling

Abstract

The application relates to the communication technical field, discloses a method and system for simulating generation of wireless device signaling, the method comprises the following steps: analyzing the debugging parameter information into a fault type; presetting a simulation device to process a signaling list corresponding to different simulation terminal operation services under different fault types; presetting a signal element text corresponding to the signaling list; reading the debugging parameter information specified by the simulation device; replacing the signal element value in the preset signal element text with the debugging parameter information specified by the simulation device read, to form a new signal element text, so that the device connection topology, the relationship between the debugging parameter information and the connection state, the relationship between the service operation and the signaling under different connection states, and the relationship between the signal element value and the device debugging parameter information can be simulated and presented, the signaling generation process and result are highly restored, the learners are facilitated to learn and analyze the wireless network connection state and locate the connection fault, and the cost is greatly reduced.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and system for simulating and generating wireless device signaling. Background Art

[0002] When learning wireless network connection status analysis, especially connection failure analysis, communications engineers and university students need to obtain, understand, and analyze device signaling and cells. In a real-world device environment, generating these signals requires building a device topology, configuring device parameters for operation, and implementing wireless connection services. This is time-consuming, labor-intensive, and expensive. Building a basic device environment typically costs over a million yuan and requires maintenance by multiple professional communications engineers. This imposes significant costs on learners, and for university students in particular, constructing a real-world device environment to capture authentic signaling and cells is nearly impossible.

[0003] In the related art, the simulation generates signaling and cell, and only presents the signaling list and cell text, but does not simulate the logical relationship between the device connection topology, debugging parameter information, connection status, service operation type, signaling list, and cell text. Summary of the Invention

[0004] The purpose of this application is to overcome the shortcomings of the existing technology and provide a method and system for simulating and generating wireless device signaling, which highly restores the signaling generation process and results, provides convenience for learners to learn, analyze wireless network connection status, and locate connection failures, and greatly reduces costs.

[0005] In a first aspect, a method for simulating and generating wireless device signaling is provided, comprising:

[0006] Obtain the connection topology between the simulation device and the simulation terminal, the debugging parameter information of the simulation device, and the business operation type of the simulation terminal;

[0007] Parsing the debugging parameter information into a fault type;

[0008] Pre-set simulation equipment to process signaling lists corresponding to different simulation terminal operation services under different fault types;

[0009] The cell text corresponding to the preset signaling list, wherein the cell text includes a hexadecimal code, a cell name, and a cell value;

[0010] Read the debugging parameter information specified by the simulation device;

[0011] Replacing the cell value in the preset cell text with the debug parameter information specified by the simulated device to form a new cell text;

[0012] The signaling list and cell text are read out according to the fault type and the service operation type of the simulated terminal, and the read signaling list and cell text are output.

[0013] Furthermore, the simulated device includes a simulated wireless base station, a bearer network element and a core network element, the simulated terminal includes a simulated mobile terminal and an Internet of Things terminal, and the connection topology is: the wireless base station is connected to the bearer network element, the bearer network element is connected to the core network element, and the wireless base station is connected to the simulated terminal.

[0014] Furthermore, the debugging parameter information includes simulation device function operation parameters and MML command execution results, wherein the simulation device function operation parameters include network element name, cabinet, frame, slot, port and operating status, and the MML command execution result is presented in an MML command execution message, the operating status is normal or abnormal, and the MML command execution message includes the network element name, command name, parameter name and parameter value.

[0015] Furthermore, parsing the debugging parameter information into a fault type includes the following steps:

[0016] Preset equipment fault list corresponding to the functional operation parameters of simulated equipment;

[0017] Preset the debugging fault list corresponding to the MML command execution results;

[0018] According to the simulated equipment function operating parameters, find the corresponding fault type in the equipment fault list;

[0019] According to the MML command execution results, find the corresponding fault type in the debugging fault list;

[0020] Fault analysis is performed based on the fault type corresponding to the simulation device function operation parameter and the fault type corresponding to the MML command execution result to obtain the fault type corresponding to the debugging parameter information.

[0021] Furthermore, the signaling list includes a signaling message type, a standard signaling interface type, a message direction, and a cell text. The signaling message type is used to describe the purpose of the device sending the instruction, the standard signaling interface type is used to describe the type of device sending the instruction, the message direction is used to describe the device interface for sending the instruction, and the cell text is used to describe the detailed content of the instruction.

[0022] Furthermore, reading the debugging parameter information specified by the simulation device also includes: a one-to-one correspondence between the preset cell name and the specified debugging parameter information, the specified debugging parameter information is a part of the debugging parameter information, and the specified debugging parameter information includes machine language information consistent with the cell value.

[0023] In a second aspect, a system for simulating and generating wireless device signaling is provided, comprising an information acquisition module and a signaling generation module;

[0024] An information acquisition module is used to obtain the connection topology between the simulation device and the simulation terminal, the debugging parameter information of the simulation device, and the business operation type of the simulation terminal;

[0025] Signaling generation module, including:

[0026] A parsing submodule, configured to parse the debugging parameter information into a fault type;

[0027] The signaling list presetting submodule is used to presetting the signaling lists corresponding to the simulated equipment processing different simulated terminal operation services under different fault types;

[0028] A cell text presetting submodule, configured to presetting a cell text corresponding to a signaling list, wherein the cell text includes a hexadecimal code, a cell name, and a cell value;

[0029] An information reading module is used to read the debugging parameter information specified by the simulation device;

[0030] The cell value replacement module is used to replace the cell value in the preset cell text with the debug parameter information specified by the simulated device to form a new cell text;

[0031] The output module is used to read out the signaling list and cell text according to the fault type and the service operation type of the simulated terminal, and output the read signaling list and cell text.

[0032] Furthermore, the parsing submodule includes:

[0033] Equipment fault list presetting unit, used to presetting equipment fault list corresponding to the functional operation parameters of simulated equipment;

[0034] A debugging fault list presetting unit is used to preset a debugging fault list corresponding to the MML command execution result;

[0035] Search unit 1, used to search for the corresponding fault type in the device fault list according to the simulated device function operation parameters;

[0036] Search unit 2 is used to search for the corresponding fault type in the debugging fault list according to the MML command execution result;

[0037] The fault type parsing unit is used to perform fault parsing based on the fault type corresponding to the functional operating parameters of the simulation device and the fault type corresponding to the MML command execution result, so as to obtain the fault type corresponding to the debugging parameter information.

[0038] In a third aspect, a computer-readable storage medium is provided, wherein the computer-readable medium stores program code for execution by a device, the program code including steps for executing the method in any one of the implementations in the first aspect.

[0039] In a fourth aspect, an electronic device is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements a method as in any one of the implementations in the first aspect.

[0040] The present application has the following beneficial effects: the message direction in the signaling list feeds back the connection topology of the simulated device, the signaling list feeds back the connection status of the simulated device and the operating services of the simulated terminal, and the cell document feeds back the debugging parameter information of the simulated device, the connection status of the simulated device, and the operating services of the simulated terminal, thereby being able to simulate and present the device connection topology, the relationship between the debugging parameter information and the connection status, the relationship between the business operations and signaling in different connection states, and the relationship between the cell value and the device debugging parameter information, highly restoring the signaling generation process and results, providing convenience for learners to learn, analyze the wireless network connection status, and locate connection failures, and greatly reducing costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The drawings that constitute a part of this application are used to provide a further understanding of this application. The illustrative embodiments of this application and their descriptions are used to explain this application and do not constitute an improper limitation on this application.

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0043] Figure 1 This is the process of the method for simulating and generating wireless device signaling in embodiment 1 of the present application. Figure 1 ;

[0044] Figure 2 This is the process of the method for simulating and generating wireless device signaling in embodiment 1 of the present application. Figure 2 ;

[0045] Figure 3 This is a block diagram of the system structure for simulating and generating wireless device signaling according to the second embodiment of the present application;

[0046] Figure 4 This is a connection topology diagram in the method for simulating and generating wireless device signaling in the first embodiment of the present application;

[0047] Figure 5 This is an example of an MML command execution message in the method for simulating and generating wireless device signaling in the first embodiment of the present application. Figure 1 ;

[0048] Figure 6 This is an example of a signaling list in the method for simulating and generating wireless device signaling in the first embodiment of the present application. Figure 1 ;

[0049] Figure 7 This is an example of the cell text in the method for simulating and generating wireless device signaling in embodiment 1 of the present application. Figure 1 ;

[0050] Figure 8 This is an example of an MML command execution message in the method for simulating and generating wireless device signaling in the first embodiment of the present application. Figure 2 ;

[0051] Figure 9 This is an example of an MML command execution message in the method for simulating and generating wireless device signaling in the first embodiment of the present application. Figure 3 ;

[0052] Figure 10 This is an example of a signaling list in the method for simulating and generating wireless device signaling in the first embodiment of the present application. Figure 2 ;

[0053] Figure 11 This is an example of the cell text in the method for simulating and generating wireless device signaling in embodiment 1 of the present application. Figure 2 . DETAILED DESCRIPTION

[0054] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0055] To better understand the present method and system, some of the terms involved in the present method and system are defined as follows:

[0056] Simulated equipment, as opposed to real communication equipment, is simulated by computers and has the ability to simulate interconnections, input and store software debugging parameters. Specifically, it includes simulated communication base stations, bearer networks, and core network equipment;

[0057] A simulated terminal, as opposed to a real terminal, is a computer simulation that has the ability to simulate connections with simulated devices and simulate operations. These operations include, but are not limited to, powering on and off, turning airplane mode on and off, positioning the mobile terminal on a simulated map, making calls, sending text messages, uploading and downloading files, playing videos, roaming, and other conventional mobile terminal and IoT terminal services.

[0058] Device debugging parameters refer to the MML command execution results and device function operation parameters entered to enable the simulated device to simulate connections and simulate terminal operation services.

[0059] MML commands, also known as Man-Machine Language (MML), are the primary mode for operating and maintaining network elements. Network administrators can operate network elements by issuing MML commands. Operators can use commands or command procedures to instruct computers to perform tasks. During these conversations, computers may ask for answers, set parameters, or select options. Through these conversations, humans can guide or limit computer operations and oversee the execution of tasks.

[0060] Signaling: A series of data fed back by wireless base stations to observe whether simulated terminals are experiencing network anomalies. This data includes real-time dynamic tracking and monitoring of protocol messages, port signaling link connection processes, and business processes, providing insights for troubleshooting.

[0061] A cell is a special data structure that is different from the frames or packets transmitted on ordinary networks. This is because frames and packets are variable length, while cells are fixed length and very small, with a length of only 53 bytes, of which 5 bytes are the cell header and 48 bytes are the information segment. The information segment can be user data of various services, and the cell header contains various control information. The cell includes a CRC checksum, and its generation formula is X^8+X^2+X+1. The checksum only verifies the cell header.

[0062] Example 1

[0063] A method for simulating and generating wireless device signaling involved in a first embodiment of the present application includes: obtaining a connection topology between a simulated device and a simulated terminal, debugging parameter information of the simulated device, and a service operation type of the simulated terminal; parsing the debugging parameter information into a fault type; presetting a signaling list corresponding to the simulated device processing different simulated terminal operation services under different fault types; presetting a cell text corresponding to the signaling list, wherein the cell text includes a hexadecimal code, a cell name, and a cell value; reading debugging parameter information specified by the simulated device; replacing the cell value in the preset cell text with the debug parameter information specified by the read simulated device to form a new cell text; reading a signaling list and cell text according to the fault type and the service operation type of the simulated terminal, and outputting the read signaling list and cell text. This method can simulate and present the device connection topology, the relationship between debugging parameter information and connection status, the relationship between service operations and signaling under different connection states, and the relationship between cell values ​​and device debugging parameter information, highly restoring the signaling generation process and results, providing convenience for learners to learn and analyze wireless network connection status and locate connection faults, and greatly reducing costs.

[0064] Specifically, Figure 1 A flowchart of a method for simulating and generating wireless device signaling in the first embodiment of the application is shown, including:

[0065] S101. Generate a fault type;

[0066] Among them, generating fault types requires obtaining the connection topology of the simulated device and the simulated terminal, the debugging parameter information of the simulated device, and presetting the device fault list corresponding to the functional operation parameters of the simulated device and the debugging fault list corresponding to the MML command execution results;

[0067] The simulated devices include simulated wireless base stations, bearer network elements, and core network elements. The wireless base stations, bearer network elements, and core network elements mentioned below are all simulated devices, not real devices. The simulated terminals include mobile terminals and Internet of Things terminals. The mobile terminals and Internet of Things terminals mentioned below are all simulated terminals, not real terminals. For example, simulated wireless base stations, bearer network elements, and core network elements are used as simulated devices, and mobile phones are used as simulated terminals.

[0068] The connection topology is that the wireless base station is connected to the bearer network element, the bearer network element is connected to the core network element, and the wireless base station is connected to the analog terminal. For example, the connection topology is that the wireless base station is connected to the bearer network element, the bearer network element is connected to the core network element, and the wireless base station is connected to the mobile phone;

[0069] The debugging parameter information includes an MML command execution message and simulation device function operation parameters. The MML command execution result is usually presented in an MML command execution message;

[0070] The simulated device function operation parameters include network element name, cabinet, frame, slot, port, and operation status, where the operation status is normal or abnormal, for example, Table 1:

[0071] Network element name cabinet box groove port Running status gNodeB101 0 0 0 101 normal PTN7900-1 bearer network 1 1 1 1 / 0 / 1 normal PTN7900-2 bearer network 1 1 2 2 / 0 / 1 normal Bearer Network PTN780-1 1 1 3 1 / 0 / 1 normal Bearer Network PTN780-2 1 1 4 2 / 0 / 1 normal PTN780-3 bearer network 1 1 5 3 / 0 / 1 normal Bearer Network PTN780-4 1 1 6 4 / 0 / 1 normal Core Network AMF 2 2 2 2022 normal Core Network SMF 2 2 2 2024 normal Core Network UPF 2 2 2 2025 normal Core Network UDM 2 2 2 2026 normal

[0072] The MML command execution message includes the network element name, command name, parameter n name, parameter n value, and fault type, where parameter n refers to multiple different parameters, for example, network element name = gNodeB101, command name = DSP NRCELL, parameter 1 name = NR cell identifier, parameter 1 value = 101&102&103, parameter 2 name = cell availability status, parameter 2 value = normal&normal&normal, where & represents an "and" relationship, and further examples are as follows Figure 5 As shown;

[0073] Parse the debugging parameter information into fault types and preset the device fault list corresponding to the simulated device function operation parameters, for example, Table 2:

[0074]

[0075]

[0076] Preset the debugging fault list corresponding to the MML command execution results;

[0077] The debugging fault list includes the network element name, command name, parameter n, and fault type, wherein the parameter includes the parameter name and parameter value, and the parameter n refers to multiple different parameters, for example, Table 3:

[0078]

[0079] According to the functional operating parameters of the simulated equipment, the corresponding fault type is found in the equipment fault list, and the fault type is obtained as no fault;

[0080] According to the MML command execution result, the corresponding fault type is found in the debugging fault list, and the fault type is obtained as no fault;

[0081] According to the corresponding relationship, the fault result is no fault, and the corresponding relationship is shown in Table 4:

[0082]

[0083]

[0084] X device failure refers to other device failures except the normal one, and X debugging failure refers to other debugging failures except the normal one.

[0085] S102, obtaining the simulated terminal service operation type;

[0086] The service operation types include, but are not limited to, powering on, powering off, turning on / off airplane mode, switching between sites, making calls, sending text messages, uploading / downloading files, playing videos, roaming, and other conventional mobile terminal and IoT terminal services. For example, the service operation type is powering on;

[0087] S103, generating a signaling list and cell text;

[0088] The signaling list includes signaling message type, standard signaling interface type, message direction, and cell text. For example, if fault type = no fault and service operation type = power on, the signaling list is as shown in Table 5:

[0089]

[0090]

[0091]

[0092]

[0093] The cell text corresponding to the preset signaling list, wherein the cell text includes a hexadecimal code, a cell name, and a cell value;

[0094] The cell value is composed of the network element name, cabinet, frame, slot, port, operating status, MML command parameter name, MML command parameter value, etc. For example, the cell text of the first cell MIB in Table 5 (cell list) is as follows:

[0095] C0 25

[0096] RRC-MSG

[0097] *msg

[0098] **struBCCH-BCH-Message

[0099] ***struBCCH-BCH-Message

[0100] ****message

[0101] *****mib

[0102] ******systemFrameNumber---'000001'B

[0103] ******subCarrierSpacingCommon---scs30or120(1)

[0104] ******ssb-SubcarrierOffset---0xc(12)

[0105] ******dmrs-TypeA-Position---pos2(0)

[0106] pdcch-ConfigSIB1

[0107] *******controlResourceSetZero---0x0(0)

[0108] *******searchSpaceZero---0x4(4)

[0109] ******cellBarred---notBarred(0)

[0110] ******intraFreqReselection---allowed(0)

[0111] ******spare---'1'B

[0112] C0 25 is a hexadecimal code. Taking "******cellBarred---notBarred(0)" as an example, cellBarred is the cell name, and notBarred(0) is the cell value.

[0113] S104, replace the cell value;

[0114] It is necessary to first read the debugging parameter information specified by the simulation device and preset a one-to-one correspondence between the cell name and the specified debugging parameter information. For example, cellBarred corresponds to the cell availability status of the DSP NRCELL command in gNodeB101. When the cell availability status = normal, cellBarred = notBarred(1); when the cell availability status = abnormal, cellBarred = notBarred(0).

[0115] According to the cell name cellBarred, the three records of the DSP NRCELL command of the analog device are read, and the cell availability status = normal, and the corresponding cellBarred = notBarred (1);

[0116] Replace the cell value in the preset cell text with the debug parameter information specified by the simulated device to form a new cell text. For example, replace notBarred(0) in cellBarred with notBarred(1) to form a new cell text. The new cell text is as follows:

[0117] C0 25

[0118] RRC-MSG

[0119] *msg

[0120] **struBCCH-BCH-Message

[0121] ***struBCCH-BCH-Message

[0122] ****message

[0123] *****mib

[0124] ******systemFrameNumber---'000001'B

[0125] ******subCarrierSpacingCommon---scs30or120(1)

[0126] ******ssb-SubcarrierOffset---0xc(12)

[0127] ******dmrs-TypeA-Position---pos2(0)

[0128] pdcch-ConfigSIB1

[0129] *******controlResourceSetZero---0x0(0)

[0130] *******searchSpaceZero---0x4(4)

[0131] ******cellBarred---notBarred(1)

[0132] ******intraFreqReselection---allowed(0)

[0133] ******spare---'1'B

[0134] Based on the fault type parsed in the above steps and the service operation type of the simulated terminal obtained, the preset signaling list and cell text are read and the signaling list and cell text are presented. The signaling list example is as follows: Figure 6 As shown, the sample screenshot of the cell text is as follows Figure 7 shown.

[0135] like Figure 2 FIG. 1 is a flow chart of another method for simulating and generating wireless device signaling according to an embodiment of the present application, the method comprising:

[0136] S201, generating a fault type;

[0137] For example, device fault type = no fault, MML command execution message, network element name = core network UDM, command name = LST SNSSAI, parameter 1 name = IMSI, parameter 1 value = 460888888880001, parameter 2 name = slice, parameter 2 value = 1-010101, parameter name 3 = default, parameter 3 value = yes, for example Figure 8 shown.

[0138] At the same time, the network element name = core network UDM, command name = LST SMDATA, parameter 1 name = IMSI, parameter 1 value = 460888888880001, parameter 2 name = slice, parameter 2 value = no corresponding result, parameter name 3 = default, parameter 3 value = no corresponding result, for example Figure 9 As shown;

[0139] A debugging fault list corresponding to the execution result of the preset MML command includes the network element name, command name, parameter n, and fault type, wherein the parameter includes a parameter name and a parameter value, and parameter n refers to multiple different parameters, for example, Table 6:

[0140]

[0141] According to the MML command execution result, the corresponding fault type is found in the debugging fault list, and the fault type is found to be UDM not configured with SMDATA;

[0142] According to the corresponding relationship, the fault result is that UDM is not configured with SMDATA. The corresponding relationship is shown in Table 7:

[0143] Simulate device functional operating parameters MML command execution results Fault analysis results No trouble No trouble No trouble X device failure No trouble X device failure No trouble X debug failure X debug failure X device failure X debug failure X device failure

[0144] X device failure refers to other device failures except the normal one, and X debugging failure refers to other debugging failures except the normal one.

[0145] S202, obtaining the simulated terminal service operation type;

[0146] The service operation types include but are not limited to conventional mobile terminal and IoT terminal services such as powering on, powering off, turning on / off airplane mode, inter-station switching, making calls, sending text messages, uploading / downloading files, playing videos, and roaming. For example, the service operation type is inter-station switching, which means moving the terminal from the signal coverage area of ​​one base station to the signal coverage area of ​​another base station.

[0147] S203, generate a signaling list and cell text;

[0148] The preset simulation equipment processes the signaling list corresponding to different simulation terminal operation services under different fault types. The signaling list includes the signaling message type, standard signaling interface type, message direction, and cell text. For example, if the fault type = UDM is not configured with SMDATA and the service operation type = inter-station switching, the signaling list is as shown in Table 8:

[0149]

[0150]

[0151]

[0152] The cell text corresponding to the preset signaling list includes a hexadecimal code, a cell name, and a cell value. The cell value is composed of a network element name, cabinet, frame, slot, port, running status, MML command parameter name, MML command parameter value, etc. For example, the cell text of the 34th cell Nudm_SDM_GetUESubscribedNSSAIResponse in the cell list is as follows:

[0153]

[0154]

[0155] In the cell text, "sst":0 and "sd":0 are used as examples for description, where sst and sd are cell names, and 0 is the cell value.

[0156] S204, replace the cell value;

[0157] Read the debugging parameter information specified by the analog device and preset a one-to-one correspondence between the cell name and the specified debugging parameter information. For example, the cell value of sst is the value before the "-" in the LST SNSSAI command slice parameter value in the core UDM, and the cell value of sd is the value after the "-" in the LST SNSSAI command slice parameter value in the core UDM. When the LST SNSSAI command slice parameter value changes, the cell values ​​of sst and sd change accordingly.

[0158] According to the cell names sst and sd, the LST SNSSAI command slice parameter values ​​intercepted to the analog device are 1 and 010101 respectively;

[0159] Replace the cell values ​​in the preset cell text with the debug parameter information specified by the simulated device to form a new cell text. For example, replace the 0 in "sst":0 with 1 and the 0 in "sd":0 with 010101 to form the following new cell text:

[0160]

[0161]

[0162] Based on the fault type parsed in the above steps and the service operation type of the simulated terminal obtained, the preset signaling list and cell text are read and the signaling list and cell text are presented. For example, the signaling list example is intercepted as follows: Figure 10 As shown, the cell text example is intercepted as Figure 11 As shown;

[0163] At this time, the message direction in the signaling list feedbacks the connection topology of the simulated device, the signaling list feedbacks the connection status of the simulated device and the operating services of the simulated terminal, and the cell document feedbacks the debugging parameter information of the simulated device, the connection status of the simulated device, and the operating services of the simulated terminal.

[0164] Example 2

[0165] A system for simulating and generating wireless device signaling according to the second embodiment of the present application includes an information acquisition module 301 and a signaling generation module 302;

[0166] The information acquisition module 301 is used to obtain the connection topology between the simulation device and the simulation terminal, the debugging parameter information of the simulation device, and the service operation type of the simulation terminal;

[0167] The signaling generation module 302 includes:

[0168] A parsing submodule, configured to parse the debugging parameter information into a fault type;

[0169] The signaling list presetting submodule is used to presetting the signaling lists corresponding to the simulated equipment processing different simulated terminal operation services under different fault types;

[0170] A cell text presetting submodule, configured to presetting a cell text corresponding to a signaling list, wherein the cell text includes a hexadecimal code, a cell name, and a cell value;

[0171] An information reading module is used to read the debugging parameter information specified by the simulation device;

[0172] The cell value replacement module is used to replace the cell value in the preset cell text with the debug parameter information specified by the simulated device to form a new cell text;

[0173] The output module is used to read out the signaling list and cell text according to the fault type and the service operation type of the simulated terminal, and output the read signaling list and cell text.

[0174] In a further embodiment, the parsing submodule includes:

[0175] Equipment fault list presetting unit, used to presetting equipment fault list corresponding to the functional operation parameters of simulated equipment;

[0176] A debugging fault list presetting unit is used to preset a debugging fault list corresponding to the MML command execution result;

[0177] Search unit 1, used to search for the corresponding fault type in the device fault list according to the simulated device function operation parameters;

[0178] Search unit 2 is used to search for the corresponding fault type in the debugging fault list according to the MML command execution result;

[0179] The fault type parsing unit is used to perform fault parsing based on the fault type corresponding to the functional operating parameters of the simulation device and the fault type corresponding to the MML command execution result, so as to obtain the fault type corresponding to the debugging parameter information.

[0180] For descriptions of the processing flow of each module in the system and the interaction flow between modules, please refer to the relevant descriptions in the above method embodiments, which will not be described in detail here.

[0181] Example 3

[0182] A computer-readable storage medium according to the third embodiment of the present application stores program code for execution by a device, the program code including steps for executing the method in any one of the implementations of the first embodiment of the present application;

[0183] Among them, the computer-readable storage medium can be a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM); the computer-readable storage medium can store program code, and when the program stored in the computer-readable storage medium is executed by the processor, the processor is used to execute the steps of the method in any one of the implementation methods in Example 1 of the present application.

[0184] Example 4

[0185] An electronic device according to the fourth embodiment of the present application includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method in any one of the implementations of the first embodiment of the present application.

[0186] Among them, the processor can adopt a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the method in any one of the implementation methods in Example 1 of the present application.

[0187] The processor may also be an integrated circuit electronic device with signal processing capabilities. In the implementation process, each step of the method in any one of the implementation methods in the first embodiment of the present application may be completed by hardware integrated logic circuits in the processor or software instructions.

[0188] The above-mentioned processor can also be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in combination with its hardware, completes the functions required to be executed by the units included in the data processing system of the embodiment of the present application, or executes the method in any one of the implementation methods in the first embodiment of the present application.

[0189] In the several embodiments provided in the present application, it should be understood that in order to better restore the process and results of signaling generated by a real device, the fault naming, signaling message type, standard signaling interface type, message direction, cell text, specified debugging parameter information, etc. described in the present application are consistent with the real device, and do not mean to limit the scope. In other words, the fault naming, signaling message type, standard signaling interface type, message direction, cell text, specified debugging parameter information, etc. are modified to make them deviate from the real device, and their essence does not deviate from the spirit and scope of the technical solution disclosed herein.

[0190] The methods and systems disclosed in this application can be implemented in other ways. The embodiments described above are merely illustrative. For example, the module division of the system is merely a logical function division. In actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be through some communication interface, indirect coupling or communication connection of the system or unit, which may be electrical, mechanical or other forms.

[0191] The modules of the system may or may not be physically separate, may or may not be physical units, that is, may be located in one place, or may be distributed across multiple network units. The purpose of the present embodiment can be achieved by selecting some or all of the modules according to actual needs.

[0192] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The scope of protection of the present application is not limited thereto. Although the present application has been described in detail with reference to the above-described embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-described embodiments within the technical scope disclosed in the present application, or perform equivalent replacements for some of the technical features thereof. These modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. A method for simulating and generating wireless device signaling, characterized in that: include: Obtain the connection topology between the simulation device and the simulation terminal, the debugging parameter information of the simulation device, and the business operation type of the simulation terminal; Parsing the debugging parameter information into a fault type specifically includes the following steps: presetting a device fault list corresponding to the simulated device function operation parameters; presetting a debugging fault list corresponding to the MML command execution result; searching for a corresponding fault type in the device fault list based on the simulated device function operation parameters; searching for a corresponding fault type in the debugging fault list based on the MML command execution result; performing fault parsing based on the fault type corresponding to the simulated device function operation parameters and the fault type corresponding to the MML command execution result to obtain a fault type corresponding to the debugging parameter information; Pre-set simulation equipment to process signaling lists corresponding to different simulation terminal operation services under different fault types; The cell text corresponding to the preset signaling list, wherein the cell text includes a hexadecimal code, a cell name, and a cell value; Read the debugging parameter information specified by the simulation device; Replacing the cell value in the preset cell text with the debug parameter information specified by the simulated device to form a new cell text; The signaling list and cell text are read out according to the fault type and the service operation type of the simulated terminal, and the read signaling list and cell text are output.

2. The method for simulating and generating wireless device signaling according to claim 1, wherein: The simulated equipment includes simulated wireless base stations, bearer network elements and core network elements; the simulated terminals include simulated mobile terminals and Internet of Things terminals; the connection topology is: the wireless base station is connected to the bearer network element, the bearer network element is connected to the core network element, and the wireless base station is connected to the simulated terminal.

3. The method for simulating and generating wireless device signaling according to claim 1, wherein: The debugging parameter information includes simulated device function operation parameters and MML command execution results, wherein the simulated device function operation parameters include network element name, cabinet, frame, slot, port and operating status, and the MML command execution result is presented in an MML command execution message. The operating status is normal or abnormal, and the MML command execution message includes the network element name, command name, parameter name and parameter value.

4. The method for simulating and generating wireless device signaling according to claim 1, wherein: The signaling list includes a signaling message type, a standard signaling interface type, a message direction, and a cell text. The signaling message type is used to describe the purpose of the device sending the instruction, the standard signaling interface type is used to describe the device type sending the instruction, the message direction is used to describe the device interface sending the instruction, and the cell text is used to describe the detailed content of the instruction.

5. The method for simulating and generating wireless device signaling according to claim 1, wherein: Reading the debugging parameter information specified by the simulation device also includes: presetting a one-to-one correspondence between the cell name and the specified debugging parameter information, the specified debugging parameter information is a part of the debugging parameter information, and the specified debugging parameter information includes machine language information consistent with the cell value.

6. A system for simulating and generating wireless device signaling, characterized in that: Including information acquisition module and signaling generation module; An information acquisition module is used to obtain the connection topology between the simulation device and the simulation terminal, the debugging parameter information of the simulation device, and the business operation type of the simulation terminal; Signaling generation module, including: A parsing submodule, configured to parse the debugging parameter information into a fault type; The signaling list presetting submodule is used to presetting the signaling lists corresponding to the simulated equipment processing different simulated terminal operation services under different fault types; A cell text presetting submodule, configured to presetting a cell text corresponding to a signaling list, wherein the cell text includes a hexadecimal code, a cell name, and a cell value; An information reading module is used to read the debugging parameter information specified by the simulation device; The cell value replacement module is used to replace the cell value in the preset cell text with the debug parameter information specified by the simulated device to form a new cell text; An output module, configured to read a signaling list and a cell text according to the fault type and the service operation type of the simulated terminal, and output the read signaling list and cell text; Wherein, the parsing submodule includes: Equipment fault list presetting unit, used to presetting equipment fault list corresponding to the functional operation parameters of simulated equipment; A debugging fault list presetting unit is used to preset a debugging fault list corresponding to the MML command execution result; Search unit 1, used to search for the corresponding fault type in the device fault list according to the simulated device function operation parameters; Search unit 2 is used to search for the corresponding fault type in the debugging fault list according to the MML command execution result; The fault type parsing unit is used to perform fault parsing based on the fault type corresponding to the functional operating parameters of the simulation device and the fault type corresponding to the MML command execution result, so as to obtain the fault type corresponding to the debugging parameter information.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium is used for program code executed by a device, and the program code includes steps for executing the method according to any one of claims 1 to 5.

8. An electronic device, characterized in that: The electronic device includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction implements the method according to any one of claims 1 to 5 when executed by the processor.

Images