A dialing driving method and device, electronic equipment and storage medium

Abstract

The application discloses a dialing driving method and device, electronic equipment and a storage medium. The method comprises the following steps: registering a virtual mobile broadband interface model device, exposing a mobile broadband interface model interface to an operating system of a host through the virtual mobile broadband interface model device; receiving a mobile broadband interface model control instruction sent by the operating system of the host through the mobile broadband interface model interface; converting the mobile broadband interface model control instruction into an AT instruction sequence according to a preset mapping relationship between a mobile broadband interface model command and an AT instruction; sending the AT instruction sequence to a baseband processor through a control channel, so that the baseband processor performs a dialing control operation corresponding to the AT instruction sequence; and transmitting an Internet protocol data packet between the host and the baseband processor through a data channel based on a remote network driving interface specification protocol. The application realizes the compatibility of the mobile broadband interface model protocol on a chip platform which does not support the mobile broadband interface model protocol stack.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a dial-up driving method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] In related technologies, driver schemes based on the Mobile Broadband Interface Model (MBIM) protocol require the baseband processor to natively support the MBIM protocol stack. The host operating system interacts with the baseband processor through the MBIM interface to complete dial-up control and the transmission and reception of Internet Protocol (IP) data packets. For chip platforms that do not have the MBIM protocol stack, a remote network driver interface specification (RWIP) protocol scheme is typically used to transmit IP packets through the RWIP channel.

[0003] However, when the baseband processor does not support the Mobile Broadband Interface Model (MBIM) protocol stack, it cannot directly receive and respond to standard MBIM control commands from the operating system. This prevents the driver module from providing dial-up control services to the operating system through the standard MBIM interface, thus limiting the functional integrity of such devices. Furthermore, while relying solely on the remote network driver interface specification protocol scheme can achieve the transmission of Internet protocol data, its control plane lacks MBIM command semantics and cannot support the standard MBIM control flow of the operating system. Consequently, control commands from the operating system side cannot be effectively transmitted to the baseband processor.

[0004] Therefore, how to achieve compatibility of the Mobile Broadband Interface Model (MBIM) protocol on chip platforms that do not support the MBIM protocol stack, so that the operating system can complete dial-up control and data communication through the standard MBIM protocol, is a technical problem that needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a dial-up driver method, apparatus, electronic device, and computer-readable storage medium, which achieves compatibility with the Mobile Broadband Interface Model (MBIM) protocol on chip platforms that do not support the MBIM protocol stack, enabling the operating system to complete dial-up control and data communication through the standard MBIM interface.

[0006] To achieve the above objectives, this application provides a dial-up driver method applied to a dial-up driver module of a host computer, wherein the host computer is connected to a baseband processor, and the method includes: Register a virtual mobile broadband interface model device and expose the mobile broadband interface model interface to the operating system of the host through the virtual mobile broadband interface model device; The mobile broadband interface model receives control commands from the host's operating system via the mobile broadband interface model interface. According to the preset mapping relationship between mobile broadband interface model commands and AT commands, the mobile broadband interface model control commands are converted into AT command sequences. The AT command sequence is sent to the baseband processor through the control channel, so that the baseband processor executes the dialing control operation corresponding to the AT command sequence; Internet Protocol (IP) data packets are transmitted between the host and the baseband processor via a data channel based on the Remote Network Driver Interface Specification (RNCI) protocol; wherein the control channel and the data channel are independent of each other.

[0007] Optionally, the registered virtual mobile broadband interface model device includes: Initialize the protocol conversion engine; The protocol conversion engine sends an initialization AT command to the baseband processor to request the mobile broadband interface model capability set from the baseband processor. Register the virtual mobile broadband interface model device according to the mobile broadband interface model capability set.

[0008] Optionally, the step of converting the mobile broadband interface model control commands into an AT command sequence according to a preset mapping relationship between mobile broadband interface model commands and AT commands includes: The target AT command corresponding to the mobile broadband interface model control command is determined according to a preset mapping table; wherein, the preset mapping table records the mapping relationship between mobile broadband interface model commands and AT commands; The target AT command is dynamically replaced to generate the AT command sequence; wherein, the dynamic parameter replacement includes automatically filling the access point name into the target AT command.

[0009] Optionally, the mobile broadband interface model control commands include network configuration commands; correspondingly, the step of converting the mobile broadband interface model control commands into an AT command sequence according to a preset mapping relationship between mobile broadband interface model commands and AT commands includes: The network configuration command is converted into Packet Data Protocol (PaDT) configuration instructions based on the mapping relationship.

[0010] Optionally, it also includes: Monitor the load of the control channel and adjust the bandwidth allocation between the control channel and the data channel according to the load; wherein the bandwidth of the control channel is positively correlated with the load, and the bandwidth of the data channel is negatively correlated with the load.

[0011] Optionally, it also includes: Obtain the priority of the control commands for the mobile broadband interface model; If the priority meets the preset priority condition, the AT command sequence is sent through the control channel first, before transmitting the Internet Protocol data packet through the data channel.

[0012] Optionally, the method further includes fault tolerance processing, which includes at least one of the following: If the target AT command in the AT command sequence times out, the target AT command is retransmitted. If the control channel fails, it will switch to the backup channel; If it is detected that the baseband processor does not support the mobile broadband interface model protocol, it will fall back to the pure remote network driver interface specification mode.

[0013] To achieve the above objectives, this application provides a dial-up driver device deployed on a host computer, the host computer being connected to a baseband processor, the device comprising: The registration unit is used to register a virtual mobile broadband interface model device and expose the mobile broadband interface model interface to the operating system of the host through the virtual mobile broadband interface model device. The receiving unit is used to receive mobile broadband interface model control commands sent by the operating system of the host through the mobile broadband interface model interface. The conversion unit is used to convert the mobile broadband interface model control commands into AT command sequences according to a preset mapping relationship between mobile broadband interface model commands and AT commands. The transmitting unit is used to send the AT command sequence to the baseband processor through the control channel, so that the baseband processor executes the dialing control operation corresponding to the AT command sequence; A transmission unit is used to transmit Internet Protocol (IP) data packets between the host and the baseband processor via a data channel based on the Remote Network Driver Interface Specification (RNTI) protocol; wherein the control channel and the data channel are independent of each other.

[0014] To achieve the above objectives, this application provides an electronic device, comprising: Memory, used to store computer programs; A processor is used to implement the steps of the dial-up driver method described above when executing the computer program.

[0015] To achieve the above objectives, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the dial-up driver method described above.

[0016] The dial-up driver method provided in this application registers a virtual mobile broadband interface model (MBIM) device and exposes the MBIM interface to the host operating system. This allows the operating system to send standard MBIM control commands to the driver module through the MBIM interface without needing to know whether the underlying baseband processor natively supports the MBIM protocol stack, thus shielding the protocol differences of the underlying hardware. After receiving the MBIM control commands, the method converts them into an AT command sequence according to a preset mapping relationship between MBIM commands and AT commands. Since AT commands are a standard instruction set commonly supported by baseband processors, this conversion mechanism accurately maps the MBIM semantics on the operating system side to control commands that the baseband processor can recognize, achieving transparent connection of the control plane protocol. Based on this, the AT command sequence is sent to the baseband processor through the control channel, while simultaneously transmitting Internet Protocol (IP) data packets through an independent data channel based on the Remote Network Driver Interface Specification (RNK) protocol. The control channel and data channel are independent of each other, ensuring that the transmission of control commands and IPR data packets do not interfere with each other. This preserves the high-speed data communication capabilities of the RNK protocol while filling the gap in the semantics of the control plane MBIM. Therefore, this application achieves compatibility with the Mobile Broadband Interface Model (MBIM) protocol on chip platforms that do not support the MBIM protocol stack, enabling the operating system to complete dial-up control and data communication through the standard MBIM interface. This application also discloses a dial-up driver, an electronic device, and a computer-readable storage medium, which can achieve the same technical effects.

[0017] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this application. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. The drawings are used to provide a further understanding of this disclosure and constitute a part of the specification. They are used together with the following detailed description to explain this disclosure, but do not constitute a limitation of this disclosure. In the drawings: Figure 1 This is a flowchart illustrating a dialing driving method according to an exemplary embodiment; Figure 2 A flowchart illustrating another dialing driving method according to an exemplary embodiment; Figure 3 This is a schematic diagram of a hybrid protocol dialing driver architecture in an application embodiment of this application; Figure 4 This is a timing diagram for the initialization of a dialer driver in an application embodiment of this application; Figure 5 This is a data transmission flowchart of an application embodiment of this application; Figure 6 This is a flowchart illustrating an error recovery process in an application embodiment of this application; Figure 7 This is a structural diagram of a dialing drive device according to an exemplary embodiment; Figure 8 This is a structural diagram of an electronic device according to an exemplary embodiment. Detailed Implementation

[0019] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0020] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0021] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0022] In related technologies, domestically produced Internet of Things (IoT) chip platforms generally do not support the Mobile Broadband Interface Model (MBIM) protocol stack, preventing the host operating system from completing dial-up control through the standard MBIM interface. While the Remote Network Driver Interface Specification (RNDIS) scheme can transmit Internet Protocol (IP) data packets, its control plane lacks MBIM command semantics. This application constructs a protocol conversion engine at the driver layer to convert the operating system's MBIM control instructions into AT (Attention) instruction sequences recognizable by the baseband processor, while preserving the high-speed data channel of the RNDIS protocol. This achieves full compatibility with the MBIM protocol without modifying the chip hardware.

[0023] This embodiment discloses a dial-up driver method applied to the dial-up driver module of a host, wherein the host is connected to a baseband processor.

[0024] The host can connect to the baseband processor via a Universal Serial Bus (USB) interface. The host can be implemented using a layered hybrid protocol driver architecture: the bottom layer uses the RNDIS protocol for the data channel, transmitting IP packets via USB bulk transfer endpoints; the control channel uses AT command set extensions to MBIM commands, with an MBIM message parser implemented at the driver layer; a protocol conversion engine converts the operating system's MBIM control commands into AT command sequences; and a dual-channel communication mechanism is designed to ensure high-speed RNDIS transmission for the data channel, while the control channel uses a virtual serial port for AT command interaction.

[0025] See Figure 1 A flowchart illustrating a dialing driving method according to an exemplary embodiment is shown below. Figure 1 As shown, it includes: S101: Register the virtual mobile broadband interface model device and expose the mobile broadband interface model interface to the operating system of the host through the virtual mobile broadband interface model device; The Virtual Mobile Broadband Interface Model (MBIM) device refers to a logical device instance registered in the host's driver layer. At the operating system level, this device appears as a standard MBIM network adapter, but its underlying implementation does not rely on the baseband processor's native MBIM protocol stack. The Mobile Broadband Interface Model (MBIM) interface refers to a set of standard MBIM control interfaces invoked by the operating system through this virtual device, including MBIM command sets for device enumeration, connection management, and network configuration.

[0026] In this step, the dial-up driver module registers a virtual MBIM device object with the operating system's device management layer during the initialization phase. Once the operating system recognizes this virtual device as a standard MBIM network adapter, application layers, such as the Windows Local Profile Assistant (LPA) service, can issue control commands through this MBIM interface without needing to know whether the underlying baseband processor natively supports the MBIM protocol stack. This virtual device layer shields the underlying hardware protocol differences, enabling the dial-up driver module to accept the operating system's MBIM control flow through a unified standard interface.

[0027] As one possible implementation, the registration of the virtual mobile broadband interface model device includes: initializing a protocol conversion engine; sending an initialization AT command to the baseband processor through the protocol conversion engine to request the mobile broadband interface model capability set from the baseband processor; and registering the virtual mobile broadband interface model device according to the mobile broadband interface model capability set.

[0028] The protocol conversion engine is the core conversion component within the dial-up driver module, responsible for establishing the mapping relationship between MBIM commands and AT instructions, managing the command queue, and performing parameter replacement. Initialization AT instructions are a set of AT commands used to query the baseband processor's MBIM capability set, such as the AT+MBIMINIT command. The mobile broadband interface model capability set refers to the set of MBIM functions supported by the baseband processor, returned by the baseband processor, such as a list of supported MBIM commands, maximum message length, and supported message types.

[0029] In practical implementation, the dial-up driver module first initializes the data structure of the protocol conversion engine upon startup, including loading the preset MBIM command and AT command mapping table and allocating command buffers and timeout management resources. Subsequently, the protocol conversion engine sends an initialization AT command to the baseband processor via the control channel to query the MBIM capability set. Upon response, the baseband processor returns MBIM capability set information, which the protocol conversion engine uses to determine the range of MBIM functions available to the upper layer. For example, if the capability set returned by the baseband processor indicates that it does not support the MBIM protocol stack but supports the complete AT command set, the protocol conversion engine configures all MBIM commands to be executed via AT command conversion. Finally, the driver module registers the virtual MBIM device with the operating system based on this capability set, reporting the supported functional characteristics of the device to the operating system during registration, ensuring that the operating system only initiates control operations that the baseband processor can actually support. Therefore, this implementation, through a capability negotiation mechanism, enables the driver module to adapt to the capability differences of different baseband processors, avoiding control failures caused by blindly registering unsupported functions.

[0030] S102: Receive the mobile broadband interface model control command sent by the operating system of the host through the mobile broadband interface model interface; Among them, the Mobile Broadband Interface Model (MBIM) control commands refer to the control commands sent by the operating system to the virtual MBIM device through the standard MBIM interface. Typical MBIM control commands include connection request (MBIM_CID_CONNECT), disconnection request (MBIM_CID_DISCONNECT), network registration status query (MBIM_CID_REGISTER_STATE), network configuration (MBIM_CID_IP_CONFIGURATION), signal status query (MBIM_CID_SIGNAL_STATE), and packet service query (MBIM_CID_PACKET_SERVICE), etc.

[0031] In this step, when application-layer components in the operating system (such as the Windows LPA service) need to perform dial-up or network management operations, the MBIM control commands are encapsulated into standard MBIM messages by the MBIM driver framework of the operating system kernel and sent to the virtual MBIM device registered by the dial-up driver module. After receiving the message at the MBIM interface layer, the dial-up driver module extracts it and passes it to its internal protocol conversion engine for processing. It should be noted that from the operating system's perspective, this process is no different from sending commands to a baseband processor that natively supports the MBIM protocol stack; the operating system does not need to concern itself with the underlying protocol conversion details.

[0032] S103: Based on the preset mapping relationship between mobile broadband interface model commands and AT commands, convert the mobile broadband interface model control commands into an AT command sequence; The predefined mapping relationship between Mobile Broadband Interface (MBIM) model commands and AT commands refers to a predefined set of conversion rules where one MBIM command corresponds to one or more AT commands. This mapping relationship records the correspondence between MBIM command identifiers and target AT command templates. An AT command sequence is a set of ordered AT commands generated after mapping and parameter filling, sent to the baseband processor in a specific order to complete the corresponding MBIM control operation. This mapping relationship is deterministic; that is, the same MBIM command input always produces the same AT command sequence output, ensuring the consistency and predictability of protocol conversion behavior.

[0033] In this step, after receiving the MBIM control command, the protocol conversion engine first parses the command identifier and parameter payload of the command, and then queries the preset mapping relationship to determine the corresponding target AT command template. Since an MBIM command may correspond to multiple sub-operations, such as a connection operation requiring sequential execution of PDP (Packet Data Protocol) context activation and dialing, the protocol conversion engine breaks down the MBIM command into multiple AT commands and arranges them into an AT command sequence according to execution dependencies. For example, for the MBIM_CID_CONNECT command, its corresponding AT command template is AT+CGACT. After extracting parameters such as the PDP context identifier from the MBIM_CID_CONNECT command, the protocol conversion engine generates a command sequence such as AT+CGACT=1,1.

[0034] As a feasible implementation, the mobile broadband interface model control command includes a network configuration command; correspondingly, the step of converting the mobile broadband interface model control command into an AT command sequence according to a preset mapping relationship between mobile broadband interface model commands and AT commands includes: converting the network configuration command into a packet data protocol configuration AT command according to the mapping relationship.

[0035] Among them, network configuration commands refer to the instructions in the MBIM protocol used to configure network connection parameters, mainly including Access Point Name (APN) settings, IP type selection, and authentication method configuration. Packet Data Protocol (Packet Data Protocol) configuration AT commands refer to the AT commands used to configure the PDP context on the baseband processor side. The typical command is AT+CGDCONT, which is used to set network parameters such as APN and PDP type.

[0036] In practical implementation, when the operating system issues a network configuration command (e.g., MBIM_CID_PDP_CONTEXT), the protocol conversion engine parses the network configuration parameters in the command, including APN (e.g., CMNET), IP type (e.g., IPv4 or IPv4v6), authentication protocol, etc., and then converts them into AT+CGDCONT instructions according to the mapping relationship. For example, for a configuration request with APN of CMNET and IP type of IPv4v6, the protocol conversion engine generates AT instructions in the format AT+CGDCONT=1,"IPV4V6","CMNET". This conversion process accurately expresses the network configuration information in MBIM semantics into PDP configuration instructions that the baseband processor can directly execute, realizing lossless transmission of network parameters between the two protocol domains.

[0037] S104: The AT command sequence is sent to the baseband processor through the control channel, so that the baseband processor executes the dialing control operation corresponding to the AT command sequence; The control channel refers to the dedicated communication path between the dial-up driver module and the baseband processor for transmitting control commands. In this embodiment, the control channel is implemented based on a USB virtual serial port, using a USB control transmission endpoint to send and receive AT commands. This virtual serial port is created during driver initialization and exposes the serial device to the host through the communication interface in the USB device descriptor.

[0038] In this step, after the protocol conversion engine generates the AT command sequence, it sends the AT commands in the sequence sequentially to the baseband processor through the control channel. After each AT command is sent, the driver module waits for the baseband processor to return a response code (e.g., OK or ERROR), and decides whether to continue sending the next command or retry based on the response result. Upon receiving the AT command, the baseband processor parses and executes the corresponding dialing control operation according to the AT command set specification, such as activating the PDP context, initiating dialing, and querying network registration status, and returns the execution result to the driver module through the control channel. The driver module converts the baseband processor's response result into the corresponding MBIM response message and sends it back to the operating system.

[0039] S105: Transmit Internet Protocol data packets between the host and the baseband processor via a data channel based on the Remote Network Driver Interface Specification protocol; wherein the control channel and the data channel are independent of each other.

[0040] The data channel refers to the communication path between the dial-up driver module and the baseband processor used to transmit IP data packets. In this embodiment, the data channel is implemented based on the RNDIS protocol and uses a USB bulk transfer endpoint for sending and receiving IP data packets. The control channel and data channel are independent of each other, meaning they use different USB endpoints, different protocol stacks, and different data buffers, and do not interfere with each other at the physical transmission level.

[0041] In this step, after the dial-up connection is established, IP data packets between the host and the baseband processor are transmitted through the RNDIS protocol data channel. The RNDIS protocol is based on a USB bulk transfer endpoint, employs a large-capacity data buffer, supports bulk data transmission, and has high throughput. The process of transmitting IP data packets on the data channel and transmitting AT commands on the control channel proceeds in parallel, with no resource contention or mutual blocking between the two channels. Taking actual test data as an example, while the RNDIS data channel is transmitting IP data packets, the control channel can still respond to the operating system's signal strength query command (MBIM_CID_SIGNAL_STATE) in real time, and the response latency is not affected by the data channel load. This independent dual-channel design ensures that the interaction of control commands does not affect the transmission performance of the data channel, and that the data channel maintains stable data transmission even when the control channel is performing command interactions.

[0042] The dial-up driver method provided in this application registers a virtual mobile broadband interface model (MBIM) device and exposes the MBIM interface to the host operating system. This allows the operating system to send standard MBIM control commands to the driver module through the MBIM interface without needing to know whether the underlying baseband processor natively supports the MBIM protocol stack, thus shielding the protocol differences of the underlying hardware. After receiving the MBIM control command, the method converts the control command into an AT command sequence according to a preset mapping relationship between MBIM commands and AT commands. Since AT commands are a standard instruction set commonly supported by baseband processors, this conversion mechanism accurately maps the MBIM semantics on the operating system side to control commands that the baseband processor can recognize, achieving transparent connection of the control plane protocol. Based on this, the AT command sequence is sent to the baseband processor through the control channel, while simultaneously transmitting Internet Protocol (IP) data packets through an independent data channel based on the Remote Network Driver Interface Specification (RNK) protocol. The control channel and data channel are independent of each other, ensuring that the transmission of control commands and the transmission of IP packets do not interfere with each other. This retains the high-speed data communication capabilities of the RNK protocol while filling the gap in the semantics of the control plane MBIM. Therefore, this application embodiment achieves compatibility with the Mobile Broadband Interface Model (MBIM) protocol on a chip platform that does not support the MBIM protocol stack, enabling the operating system to complete dial-up control and data communication through the standard MBIM interface.

[0043] This application discloses a dialing driver method, which, compared to the previous embodiment, further explains and optimizes the technical solution. Specifically: See Figure 2 A flowchart illustrating another dialing driving method according to an exemplary embodiment, such as... Figure 2 As shown, it includes: S201: Register the virtual mobile broadband interface model device and expose the mobile broadband interface model interface to the operating system of the host through the virtual mobile broadband interface model device; S202: Receive the mobile broadband interface model control command sent by the operating system of the host through the mobile broadband interface model interface; S203: Determine the target AT command corresponding to the mobile broadband interface model control command according to the preset mapping table; wherein, the preset mapping table records the mapping relationship between mobile broadband interface model commands and AT commands; The preset mapping table is a pre-configured data table in the dial-up driver module, used to record the deterministic mapping relationship between each MBIM command identifier and its corresponding AT command template. For example, the preset mapping table may contain the following mapping relationships: MBIM_CID_CONNECT corresponds to AT+CGACT, MBIM_CID_IP_CONFIGURATION corresponds to AT+CGDCONT, MBIM_CID_REGISTER_STATE corresponds to AT+COPS, and MBIM_CID_PACKET_SERVICE corresponds to AT+CGREG. The target AT command refers to the AT command template string obtained through table lookup matching, which has not yet been populated with specific parameters.

[0044] In this step, after receiving the MBIM control command, the protocol conversion engine first extracts the command identifier of the command, and then searches for a record that matches the command identifier in a preset mapping table. If a match is found, the corresponding AT command template is obtained as the target AT command; if a match fails, it is determined that the MBIM command is not supported on the current baseband processor, and the corresponding error code is returned to the operating system. This mapping table lookup process is deterministic, meaning that the same MBIM command input always produces the same AT command template output, ensuring the consistency of protocol conversion.

[0045] S204: Perform dynamic parameter replacement on the target AT command to generate the AT command sequence; wherein, the dynamic parameter replacement includes automatically filling the access point name into the target AT command.

[0046] In this step, after obtaining the target AT command template, the protocol conversion engine dynamically replaces the placeholder parameters in the AT command template according to the parameter payload carried in the MBIM control command. Taking PDP context configuration as an example, the parameters of the MBIM_CID_IP_CONFIGURATION command include configuration parameters such as APN, IP type, and authentication information. The protocol conversion engine extracts the values ​​of these parameters and fills them into the corresponding parameter positions in the AT+CGDCONT command template, generating a complete AT command that can be directly sent to the baseband processor. This dynamic parameter replacement process is automatically completed by the protocol conversion engine, without requiring the upper-layer application to pay attention to the specific format and parameter positions of the AT command, achieving transparent conversion at the parameter level. For example, when the MBIM network configuration command issued by the operating system specifies the APN as CMNET and the IP type as IPv4, the protocol conversion engine replaces the APN placeholder parameter in the AT+CGDCONT template with CMNET and the PDP type placeholder parameter with IP, ultimately generating a complete AT command AT+CGDCONT=1,"IP","CMNET".

[0047] S205: The AT command sequence is sent to the baseband processor through the control channel, so that the baseband processor executes the dialing control operation corresponding to the AT command sequence; S206: Internet Protocol data packets are transmitted between the host and the baseband processor via a data channel based on the Remote Network Driver Interface Specification protocol; wherein the control channel and the data channel are independent of each other.

[0048] Therefore, this embodiment determines the target AT command corresponding to the MBIM control command through a preset mapping table, and generates an AT command sequence by dynamically replacing parameters (including APN auto-fill) of the target AT command, thus achieving a deterministic, parameter-level transparent conversion between MBIM commands and AT commands. The design of the preset mapping table allows the protocol conversion engine to quickly match the target AT command template without complex semantic reasoning, improving command conversion efficiency; the dynamic parameter replacement mechanism enables the driver module to automatically extract network configuration parameters from the MBIM control command and fill them into the AT command template, without the upper-layer application needing to concern itself with the specific format and parameter position of the AT command. In other words, this embodiment achieves lightweight command conversion through a mapping table and parameter replacement.

[0049] Based on the above embodiments, as a preferred embodiment, it further includes: monitoring the load of the control channel and adjusting the bandwidth allocation between the control channel and the data channel according to the load; wherein the bandwidth of the control channel is positively correlated with the load, and the bandwidth of the data channel is negatively correlated with the load.

[0050] The control channel load refers to the number of AT commands sent through the control channel per unit time and the occupancy rate of the control channel transmit buffer. The control channel bandwidth is positively correlated with the load, meaning that when the control channel load increases, the USB bus bandwidth allocated to the control channel increases accordingly. Conversely, the data channel bandwidth is negatively correlated with the load, meaning that when the control channel occupies more bandwidth, the available USB bus bandwidth for the data channel decreases accordingly.

[0051] In practical implementation, the command queue depth and transmit buffer occupancy of the control channel are periodically sampled at preset time intervals (e.g., 500 milliseconds) to calculate the current control channel load indicators. When the control channel load increases (e.g., during the initial connection establishment phase when multiple configuration AT commands need to be sent intensively), the USB endpoint polling priority of the control channel is increased, while the batch transmission endpoint scheduling frequency of the data channel is appropriately reduced, thereby allocating more USB bus bandwidth to the control channel to ensure that the AT command sequence can be sent quickly. Conversely, when the control channel load decreases below a preset threshold (e.g., after the connection stabilizes and only periodic status queries are needed), the original bandwidth allocation of the data channel is restored to maximize the throughput of the data channel. This dynamic bandwidth allocation strategy balances the control plane response speed and data plane transmission efficiency, avoiding command delays during the connection establishment phase while not affecting data transmission performance during the steady-state phase. Therefore, this implementation method, through dynamic bandwidth coordination, automatically optimizes the USB bus resource allocation between the two channels under fluctuating control channel load, improving the overall driver response capability and data transmission efficiency.

[0052] Based on the above embodiments, as a preferred implementation, it further includes: obtaining the priority of the mobile broadband interface model control command; if the priority meets a preset priority condition, then before transmitting the Internet Protocol data packet through the data channel, the AT command sequence is sent preferentially through the control channel.

[0053] The priority of MBIM control commands can be determined based on the function type of the command. For example, commands that are sensitive to timing, such as network configuration commands and session establishment commands, are given higher priority, while commands that are not sensitive to timing, such as status query commands, are given lower priority.

[0054] In practical implementation, the driver module can maintain independent scheduling strategies for instructions of different priorities in the instruction queue. A preset priority condition can refer to the MBIM control instruction having a priority higher than a preset level; for example, the condition is met when the instruction has a high priority. When the preset priority condition is met, the driver module prioritizes the transmission of the AT instruction sequence corresponding to that instruction at the scheduling level, ensuring that the AT instruction sequence is sent before IP data packets are transmitted through the data channel.

[0055] As can be seen, this implementation method ensures the timely transmission of critical control commands through an instruction priority scheduling mechanism, avoiding control plane signaling delays caused by busy data channels.

[0056] Based on the above embodiments, as a preferred implementation, the method further includes fault tolerance processing, which includes at least one of the following: if the transmission of the target AT command in the AT command sequence times out, the target AT command is retransmitted; if the control channel fails, the switch is made to the backup channel; if the baseband processor is detected to not support the Mobile Broadband Interface Model Protocol, the fallback is made to the Pure Remote Network Driver Interface Specification mode.

[0057] In practical implementation, for command-level retries, the driver module sets a timeout for each AT command, for example, 3 seconds. If no response code is received from the baseband processor within this timeout period, the AT command is automatically retransmitted, with a maximum of 3 retries. A backoff period is waited before each retry, increasing with the number of retries: 500 milliseconds for the first retry, 1000 milliseconds for the second, and 2000 milliseconds for the third, to avoid consecutive failures due to temporary baseband processor overload. If no successful response is received after 3 retries, the operating system is reported that the MBIM command execution failed, along with a failure reason code. For channel-level switching, the driver module continuously monitors the communication status of the control channel, including metrics such as the USB endpoint's data integrity error rate and link timeout count. When a control channel failure is detected (e.g., 3 consecutive AT command timeouts or the USB endpoint continuously returning transmission errors), if a backup USB interrupt transmission endpoint exists in the system, the control channel is automatically switched to the backup endpoint, and the connection status of the protocol conversion engine is reinitialized to restore the normal transmission and reception process of control commands. The switching process is transparent to the operating system, requiring no re-initiation of a control session by upper-layer applications. For protocol-level degradation, during the driver module initialization phase, if the baseband processor returns an initialization AT command indicating complete lack of support for MBIM command-related functions (i.e., an empty MBIM capability set), or if it continuously fails to execute critical MBIM commands, the driver module automatically reverts to pure RNDIS mode. In pure RNDIS mode, the driver module no longer registers virtual MBIM devices, only exposing the RNDIS network adapter to the operating system. The operating system directly communicates with the baseband processor via the RNDIS protocol to send and receive IP packets, achieving basic network connectivity. While this mode cannot provide MBIM control plane functionality, it ensures that the device can still perform normal network communication even with the simplest configuration.

[0058] The following describes one application embodiment provided by this application. See also... Figure 3 , Figure 3 This is a schematic diagram of a hybrid protocol dial-up driver architecture in an application embodiment of this application. Figure 3As shown, this layered driver architecture, from top to bottom, includes: user space, the application layer components of the deployment host; the Windows LPA module, located to the right of user space, used to initiate MBIM control commands and eSIM (embedded Subscriber Identity Module) configuration commands; and the virtual MBIM device layer, which receives MBIM control commands from user space and commands from Windows LPA. The LPA module's eSIM configuration commands; the protocol conversion engine, located below the virtual MBIM device layer, is the core of the driver architecture, responsible for converting MBIM control commands into AT commands and managing the forwarding of IP packets. It branches down into two paths: the left side generates AT commands, and the right side forwards IP packets; the AT command parser, located to the lower left of the protocol conversion engine, receives the AT commands generated by the protocol conversion engine and connects to the chip's baseband processor; the RNDIS data channel, located to the lower right of the protocol conversion engine, receives the IP packets forwarded by the protocol conversion engine and connects to the USB bulk transfer endpoint; the chip's baseband processor, located at the lower left of the architecture, receives AT commands from the AT command parser and executes the corresponding dialing control operations; the USB bulk transfer endpoint, located at the lower right of the architecture, serves as the underlying transmission medium for the RNDIS data channel. The AT command parser and the RNDIS data channel are independent of each other, interfacing with the baseband processor and the USB physical layer respectively through control and data channels. The two channels operate in parallel without interference.

[0059] See Figure 4 , Figure 4 This is a timing diagram for dial-up driver initialization in an application embodiment of this application. The diagram contains four objects, from left to right: Windows, virtual MBIM driver, protocol conversion engine, and baseband processor. Figure 4As shown, the initialization process includes the following message interactions in sequence: 1) Windows sends a message to the virtual MBIM driver to load the MBIM device driver, triggering the loading of the virtual MBIM driver; 2) After the virtual MBIM driver is loaded, it sends a message to the protocol conversion engine to initialize the protocol conversion engine, enabling the protocol conversion engine to enter a working ready state; 3) The protocol conversion engine sends an AT+MBIMINIT message to the baseband processor to request the MBIM capability set; 4) After receiving the AT+MBIMINIT, the baseband processor returns the supported MBIM capability information to the protocol conversion engine by returning an MBIM capability set message (dashed return); 5) Based on the obtained capability set, the protocol conversion engine sends a message to the virtual MBIM driver to register the virtual MBIM device (dashed line), and the virtual MBIM driver completes the instantiation of the virtual MBIM device; 6) After the virtual MBIM driver completes the registration, it sends a message to Windows to expose the MBIM interface (dashed line), enabling the Windows operating system to issue subsequent control commands to the virtual MBIM driver through the standard MBIM interface. This initialization sequence diagram illustrates the complete process from the operating system loading the driver to the full exposure of the virtual MBIM interface, demonstrating the operating mechanism of the protocol conversion engine negotiating capabilities with the baseband processor via AT+MBIMINIT before registering the virtual MBIM device.

[0060] See Figure 5 , Figure 5 This is a data transmission flowchart of an application embodiment of this application. For example... Figure 5 As shown, the data transmission process starts with a data transmission request and proceeds sequentially through the following steps: 1) Windows LPA sends the MBIM_SET_IP command, distributing the IP configuration request to the protocol conversion engine; 2) After receiving the MBIM_SET_IP command, the protocol conversion engine converts it into an AT+CGDCONT command (i.e., a packet data protocol configuration AT command) according to a preset mapping table, completing the protocol conversion from MBIM command to AT command; 3) Subsequently, it enters the control channel priority judgment node to determine whether the control channel priority of the AT+CGDCONT command meets the preset priority conditions. If it does, the AT command is sent through the control channel before data channel transmission; if it does not, it is executed in parallel with the data channel; 4) Regardless of whether it is a priority path or a parallel path, the IP data packet is ultimately transmitted through the RNDIS channel; 5) After the RNDIS channel completes the transmission of the IP data packet, it enters the transmission completion node, ending the data transmission process. This flowchart illustrates the complete link from the upper-layer application initiating a data transmission request to the completion of IP data packet transmission through the RNDIS channel, demonstrating the collaborative working method of control plane protocol conversion and high-speed data plane transmission.

[0061] See Figure 6 , Figure 6 This is a flowchart illustrating an error recovery process in an application embodiment of this application. For example... Figure 6 As shown, the error recovery process uses normal mode as the main operating state. The driver module enters the error recovery process under the following abnormal conditions: 1) AT command timeout triggers entry into control channel fault state; 2) In control channel fault state, the target AT command is automatically retransmitted 3 times, entering retry mechanism state; 3) The retry mechanism state has the following branches: if the retry is successful (i.e., a response is received from the baseband processor), it returns to normal mode; if it fails 5 times consecutively, it enters channel switching state; 4) The channel switching state has two branches: if the interrupt endpoint is enabled, it switches to the backup channel, communication is restored by the backup channel, and it returns to normal mode; if the baseband does not support it, it enters protocol degradation state; 5) In protocol degradation state, the rollback mechanism is activated, causing the driver module to enter pure RNDIS mode. In pure RNDIS mode, the driver module no longer receives MBIM control commands from the operating system through the virtual MBIM device, but only maintains the basic network connection function of the RNDIS data channel; this state supports sub-state definition, i.e., selectable: if this state has internal behavior, it can be defined here. The error recovery process employs a three-tiered progressive mechanism: automatic retransmission at the command level (3 times), switching to a backup channel at the channel level, and falling back to pure RNDIS mode at the protocol level, ensuring the reliability of the driver module layer by layer.

[0062] The following describes a dialing driver device provided in an embodiment of this application. The dialing driver device described below and the dialing driver method described above can be referred to each other.

[0063] See Figure 7 A structural diagram of a dialing drive device is shown according to an exemplary embodiment, as follows: Figure 7 As shown, the dialing driver is deployed on a host computer, which is connected to a baseband processor. The device includes: Registration unit 100 is used to register a virtual mobile broadband interface model device and expose the mobile broadband interface model interface to the operating system of the host through the virtual mobile broadband interface model device. The receiving unit 200 is used to receive mobile broadband interface model control commands sent by the operating system of the host through the mobile broadband interface model interface. The conversion unit 300 is used to convert the mobile broadband interface model control command into an AT command sequence according to a preset mapping relationship between mobile broadband interface model commands and AT commands. The transmitting unit 400 is used to transmit the AT command sequence to the baseband processor through the control channel, so that the baseband processor executes the dialing control operation corresponding to the AT command sequence; The transmission unit 500 is used to transmit Internet Protocol data packets between the host and the baseband processor through a data channel based on the Remote Network Driver Interface Specification protocol; wherein the control channel and the data channel are independent of each other.

[0064] The dial-up driver device provided in this application registers a virtual mobile broadband interface model (MBIM) device and exposes the MBIM interface to the host operating system. This allows the operating system to send standard MBIM control commands to the driver module through the MBIM interface without needing to know whether the underlying baseband processor natively supports the MBIM protocol stack, thus shielding the protocol differences of the underlying hardware. After receiving the MBIM control command, the device converts the control command into an AT command sequence according to a preset mapping relationship between MBIM commands and AT commands. Since AT commands are a standard instruction set commonly supported by baseband processors, this conversion mechanism accurately maps the MBIM semantics on the operating system side to control commands that the baseband processor can recognize, achieving transparent connection of the control plane protocol. Based on this, the AT command sequence is sent to the baseband processor through the control channel, while simultaneously transmitting Internet Protocol (IP) data packets through an independent data channel based on the Remote Network Driver Interface (RNTI) specification protocol. The control channel and data channel are independent of each other, ensuring that the transmission of control commands and the transmission of IP packets do not interfere with each other. This retains the high-speed data communication capabilities of the RTI specification protocol while filling the gap in the semantics of the control plane MBIM. Therefore, this application embodiment achieves compatibility with the Mobile Broadband Interface Model (MBIM) protocol on a chip platform that does not support the MBIM protocol stack, enabling the operating system to complete dial-up control and data communication through the standard MBIM interface.

[0065] Based on the above embodiments, as a preferred implementation, the registration unit 100 is specifically used for: initializing the protocol conversion engine; sending an initialization AT command to the baseband processor through the protocol conversion engine to request the mobile broadband interface model capability set from the baseband processor; and registering the virtual mobile broadband interface model device according to the mobile broadband interface model capability set.

[0066] Based on the above embodiments, as a preferred implementation, the conversion unit 300 is specifically used to: determine the target AT command corresponding to the mobile broadband interface model control command according to a preset mapping table; wherein, the preset mapping table records the mapping relationship between mobile broadband interface model commands and AT commands; perform dynamic parameter replacement on the target AT command to generate the AT command sequence; wherein, the dynamic parameter replacement includes automatically filling the access point name into the target AT command.

[0067] Based on the above embodiments, as a preferred implementation, the mobile broadband interface model control command includes a network configuration command; correspondingly, the conversion unit 300 is specifically used to: convert the network configuration command into a packet data protocol configuration (AT) command according to the mapping relationship.

[0068] Based on the above embodiments, as a preferred embodiment, it further includes: An adjustment module is used to monitor the load of the control channel and adjust the bandwidth allocation between the control channel and the data channel according to the load; wherein the bandwidth of the control channel is positively correlated with the load, and the bandwidth of the data channel is negatively correlated with the load.

[0069] Based on the above embodiments, as a preferred embodiment, it further includes: The acquisition module is used to acquire the priority of the control command of the mobile broadband interface model; if the priority meets the preset priority condition, the AT command sequence is sent through the control channel first before transmitting the Internet Protocol data packet through the data channel.

[0070] Based on the above embodiments, as a preferred embodiment, the device further includes a fault-tolerant module, which is used to perform fault-tolerant processing, the fault-tolerant processing including at least one of the following: if the transmission of the target AT command in the AT command sequence times out, the target AT command is automatically retransmitted; if the control channel fails, the switch is made to the backup channel; if the baseband processor is detected to not support the Mobile Broadband Interface Model Protocol, the fallback is made to the Pure Remote Network Driver Interface Specification mode.

[0071] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0072] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, the embodiments of this application also provide an electronic device. Figure 8 This is a structural diagram of an electronic device according to an exemplary embodiment, such as... Figure 8 As shown, the electronic device includes: Communication interface 1 enables information exchange with other devices, such as network devices; Processor 2 is connected to communication interface 1 to enable information interaction with other devices. When running a computer program, it executes the dial-up driver method provided by one or more of the above-mentioned technical solutions. The computer program is stored in memory 3.

[0073] Of course, in practical applications, the various components in an electronic device are coupled together through bus system 4. It can be understood that bus system 4 is used to achieve communication and connection between these components. In addition to the data bus, bus system 4 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 8 The general will label all buses as Bus System 4.

[0074] The memory 3 in this embodiment is used to store various types of data to support the operation of the electronic device. Examples of such data include any computer program used to operate on the electronic device.

[0075] It is understood that memory 3 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 3 described in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0076] The methods disclosed in the embodiments of this application can be applied to processor 2, or implemented by processor 2. Processor 2 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 2 or by instructions in the form of software. The processor 2 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 2 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested 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 modules may be located in a storage medium, which is located in memory 3. Processor 2 reads the program in memory 3 and completes the steps of the aforementioned method in combination with its hardware.

[0077] When processor 2 executes the program, it implements the corresponding processes in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0078] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a memory 3 that stores a computer program, which can be executed by a processor 2 to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0079] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0080] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer, server, network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0081] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A dialing driving method, characterized in that, A dial-up driver module applied to a host computer, the host computer being connected to a baseband processor, the method comprising: Register a virtual mobile broadband interface model device and expose the mobile broadband interface model interface to the operating system of the host through the virtual mobile broadband interface model device; The mobile broadband interface model receives control commands from the host's operating system via the mobile broadband interface model interface. According to the preset mapping relationship between mobile broadband interface model commands and AT commands, the mobile broadband interface model control commands are converted into AT command sequences. The AT command sequence is sent to the baseband processor through the control channel, so that the baseband processor executes the dialing control operation corresponding to the AT command sequence; Internet Protocol (IP) data packets are transmitted between the host and the baseband processor via a data channel based on the Remote Network Driver Interface Specification (RNCI) protocol; wherein the control channel and the data channel are independent of each other.

2. The dialing driving method according to claim 1, characterized in that, The registered virtual mobile broadband interface model device includes: Initialize the protocol conversion engine; The protocol conversion engine sends an initialization AT command to the baseband processor to request the mobile broadband interface model capability set from the baseband processor. Register the virtual mobile broadband interface model device according to the mobile broadband interface model capability set.

3. The dialing driving method according to claim 1, characterized in that, The step of converting the mobile broadband interface model control commands into AT command sequences based on a preset mapping relationship between mobile broadband interface model commands and AT commands includes: The target AT command corresponding to the mobile broadband interface model control command is determined according to a preset mapping table; wherein, the preset mapping table records the mapping relationship between mobile broadband interface model commands and AT commands; The target AT command is dynamically replaced to generate the AT command sequence; wherein, the dynamic parameter replacement includes automatically filling the access point name into the target AT command.

4. The dialing driving method according to claim 1, characterized in that, The mobile broadband interface model control commands include network configuration commands; correspondingly, the step of converting the mobile broadband interface model control commands into an AT command sequence according to a preset mapping relationship between mobile broadband interface model commands and AT commands includes: The network configuration command is converted into Packet Data Protocol (PaDT) configuration instructions based on the mapping relationship.

5. The dialing driving method according to claim 1, characterized in that, Also includes: Monitor the load of the control channel and adjust the bandwidth allocation between the control channel and the data channel according to the load; wherein the bandwidth of the control channel is positively correlated with the load, and the bandwidth of the data channel is negatively correlated with the load.

6. The dialing driving method according to claim 1, characterized in that, Also includes: Obtain the priority of the control commands for the mobile broadband interface model; If the priority meets the preset priority condition, the AT command sequence is sent through the control channel first, before transmitting the Internet Protocol data packet through the data channel.

7. The dialing driving method according to claim 1, characterized in that, The method further includes fault tolerance processing, which includes at least one of the following: If the target AT command in the AT command sequence times out, the target AT command is retransmitted. If the control channel fails, it will switch to the backup channel; If it is detected that the baseband processor does not support the mobile broadband interface model protocol, it will fall back to the pure remote network driver interface specification mode.

8. A dialing drive device, characterized in that, Deployed in a host computer, the host computer being connected to a baseband processor, the device includes: The registration unit is used to register a virtual mobile broadband interface model device and expose the mobile broadband interface model interface to the operating system of the host through the virtual mobile broadband interface model device. The receiving unit is used to receive mobile broadband interface model control commands sent by the operating system of the host through the mobile broadband interface model interface. The conversion unit is used to convert the mobile broadband interface model control commands into AT command sequences according to a preset mapping relationship between mobile broadband interface model commands and AT commands. The transmitting unit is used to send the AT command sequence to the baseband processor through the control channel, so that the baseband processor executes the dialing control operation corresponding to the AT command sequence; A transmission unit is used to transmit Internet Protocol (IP) data packets between the host and the baseband processor via a data channel based on the Remote Network Driver Interface Specification (RNTI) protocol; wherein the control channel and the data channel are independent of each other.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the dialing driver method as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the dialing driving method as described in any one of claims 1 to 7.

Images