GPRS (General Packet Radio Service) data retransmission method of special mobile terminal for railway

Abstract

The invention discloses a GPRS (General Packet Radio Service) data retransmission method of a special mobile terminal for a railway, which enhances the reliability of railway communication. The method comprises the following steps that: an LLC entity receives and stores user data, and initializes retransmission times and validity period parameters at the same time; the RLC / MAC entity applies to establish an uplink TBF connection to send data; if the TBF connection fails, the RLC / MAC entity informs the LLC entity of the result; and the LLC entity determines whether to retransmit the data according to the sending result of the user data, the retransmission times and the validity period parameter. If the data transmission fails and is in the validity period, the LLC entity increases the retransmission times and retransmits the data; otherwise, clearing the data and resetting the parameters. According to the method, the sending failure is responded in time, so that the reset of the mobile terminal caused by continuous data loss is avoided, the safety and on-time arrival of a train are ensured, and the efficiency and reliability of railway special mobile communication are remarkably improved.

Description

Technical Field

[0001] The invention relates to GSM-R railway dedicated mobile communication, in particular to a GPRS data retransmission method for a railway dedicated mobile terminal. Background Art

[0002] GSM-R is a railway-specific mobile communication system widely used in countries around the world. GPRS, as a mobile packet data service developed on the basis of the GSM mobile communication system, is also widely used in railway mobile communications. Compared with the CSD data transmission method in the circuit domain, the GPRS data transmission method has a certain delay, but it has the highest resource utilization efficiency. It only needs to occupy resources when sending data, and only occupies one or limited channel resources, so it basically does not affect the normal operation of voice services in railway mobile communications.

[0003] At present, GPRS services are mainly used in China's railway-specific mobile communications to transmit information such as train numbers, dispatching commands, and route notices. Due to the high-speed operation of railways and the complex communication environment along the railway, there are data loss problems during GPRS data transmission, such as no response to the application channel, the application channel receives an Immediate Assignment Reject signaling, and contention resolution fails. If data loss occurs continuously, the locomotive integrated wireless communication equipment will reset the mobile terminal, further affecting the sending and receiving of data, and even affecting the safety and on-time arrival of the train. In some cases, whether the data is sent successfully is known to the mobile terminal. If the channel application fails, the data cannot be sent normally.

[0004] It should be noted that the information disclosed in the above background technology section is only used for understanding the background of the present application, and therefore may include information that does not constitute prior art known to ordinary technicians in the field. Summary of the invention

[0005] The main purpose of the present invention is to overcome the defects existing in the above-mentioned background technology and provide a GPRS data retransmission method for a railway dedicated mobile terminal.

[0006] To achieve the above object, the present invention adopts the following technical solutions:

[0007] A GPRS data retransmission method for a railway dedicated mobile terminal comprises the following steps:

[0008] S1. Data storage and parameter initialization: The LLC entity receives user data, saves the user data, and initializes the number of retransmissions and validity period parameters associated with the user data;

[0009] S2. Uplink TBF connection application: RLC / MAC entity applies to establish an uplink TBF connection to send user data;

[0010] S3 uplink TBF connection result processing: RLC / MAC entity determines whether the uplink TBF connection is successfully established based on the network response; if the connection fails, the failure result is notified to the LLC entity;

[0011] S4. Data sending and retransmission decision:

[0012] If the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF;

[0013] If the sent user data is not confirmed by the network within the expected time, the RLC / MAC entity notifies the LLC entity of the sending failure result;

[0014] The LLC entity determines whether to retransmit based on the transmission failure result, the number of retransmissions, and the data validity period parameters;

[0015] If the judgment result is retransmission, the LLC entity increases the number of retransmissions and retransmits the saved user data;

[0016] If the judgment result is not retransmission, the LLC entity clears the saved user data and resets related parameters.

[0017] Further, the method includes an LLC entity data retransmission process, wherein:

[0018] In step S1, the LLC entity distinguishes between user data and signaling data, saves only the user data, and initializes the number of retransmissions and validity period parameters;

[0019] In step S2, when the RLC / MAC entity sends user data, if the uplink TBF connection is successfully established, the data is sent; if the connection fails, the LLC entity is notified of the sending result;

[0020] In step S3, after receiving the notification from the RLC / MAC entity, the LLC entity performs the following operations according to the transmission result:

[0021] If the user data is sent successfully, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters;

[0022] If the user data fails to be sent, the LLC entity determines whether the saved user data is within the validity period and whether the number of retransmissions is not greater than the maximum number of retransmissions;

[0023] In step S4, the LLC entity performs the following operations:

[0024] If the user data is within the validity period and the number of retransmissions is less than the maximum number of retransmissions, the LLC entity increases the number of retransmissions by one and re-adds the saved user data to the sending queue for retransmission;

[0025] If the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters to prepare for receiving new user data.

[0026] Further, the method includes starting a data retransmission process upon failure of uplink TBF establishment, wherein:

[0027] In step S2, when the RLC / MAC entity applies for an uplink TBF connection, if it receives an immediate assignment rejection message or the channel request timeout timer times out due to no response received, the LLC entity performs the following operations:

[0028] Increase the number of retransmissions by one;

[0029] If the number of retransmissions does not exceed the preset maximum number of retransmissions, the retransmission mechanism is started to prepare to retransmit LLCPDU data;

[0030] In step S3, after receiving the result of the uplink TBF connection establishment failure notified by the RLC / MAC entity, the LLC entity will perform the following operations:

[0031] Determine whether the user data is still within the validity period;

[0032] If the user data is within the validity period and the number of retransmissions does not exceed the preset maximum number of retransmissions, the LLC entity increases the number of retransmissions by one and starts the retransmission mechanism;

[0033] If the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters;

[0034] In step S4, if the LLC entity starts the retransmission mechanism after the uplink TBF connection establishment fails, the following operations will be performed:

[0035] Retransmit LLCPDU data request;

[0036] If the retransmission is successful, the saved user data is cleared, and the number of retransmissions and validity period parameters are reset;

[0037] If the retransmission fails, the retransmission is continued based on the number of retransmissions and the data validity period until the retransmission condition is no longer met or the retransmission is successful.

[0038] Further, the method includes starting a data retransmission process when conflict resolution fails, in step S4:

[0039] If the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF;

[0040] Monitor the network's confirmation message for sending data. If no confirmation message is received from the network within a certain period of time, that is, the data sending confirmation waiting counter reaches the maximum value, the RLC / MAC entity considers that the data sending has failed;

[0041] The RLC / MAC entity notifies the LLC entity of the result of data transmission failure;

[0042] After receiving the result of the RLC / MAC entity sending failure, the LLC entity checks whether the user data is within the set validity period and whether the number of retransmissions has not reached the preset maximum number of retransmissions;

[0043] If the user data is within the validity period and the number of retransmissions has not reached the maximum number of retransmissions, the LLC entity increases the number of retransmissions by one and starts the retransmission mechanism to prepare to retransmit the LLCPDU data;

[0044] If the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters;

[0045] If the LLC entity starts the retransmission mechanism, it sends a request to retransmit LLCPDU;

[0046] If the retransmission is successful, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters;

[0047] If the retransmission fails again, the LLC entity continues to determine whether to continue retransmission based on the number of retransmissions and the data validity period until the retransmission condition is no longer met or the retransmission is successful.

[0048] A GPRS data retransmission device for a railway dedicated mobile terminal, comprising:

[0049] Data storage and parameter initialization module: The LLC entity receives user data, stores the user data, and initializes the number of retransmissions and validity period parameters related to the user data;

[0050] Uplink TBF connection application module: RLC / MAC entity applies to establish an uplink TBF connection to send user data;

[0051] Uplink TBF connection result processing module: The RLC / MAC entity determines whether the uplink TBF connection is successfully established based on the network response; if the connection fails, the failure result is notified to the LLC entity;

[0052] Data sending and retransmission decision module:

[0053] If the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF;

[0054] If the sent user data is not confirmed by the network within the expected time, the RLC / MAC entity notifies the LLC entity of the sending failure result;

[0055] The LLC entity determines whether to retransmit based on the transmission failure result, the number of retransmissions, and the data validity period parameters;

[0056] If the judgment result is retransmission, the LLC entity increases the number of retransmissions and retransmits the saved user data;

[0057] If the judgment result is not retransmission, the LLC entity clears the saved user data and resets related parameters.

[0058] A computer-readable storage medium stores a computer program, characterized in that the computer program, when executed by a processor, implements the GPRS data retransmission method for a railway-specific mobile terminal.

[0059] A computer program product comprises a computer program, wherein when the computer program is executed by a processor, the GPRS data retransmission method of a railway dedicated mobile terminal is implemented.

[0060] The present invention has the following beneficial effects:

[0061] The present invention provides a GPRS data retransmission method for a railway-specific mobile terminal, which effectively solves the problem of data loss in a complex communication environment along the railway. By distinguishing user data from signaling data in the LLC entity and adding retransmission times and validity period parameters for user data storage, the present invention can promptly start the retransmission mechanism when user data fails to send, avoiding the situation where the locomotive integrated wireless communication device resets the mobile terminal due to continuous data loss, thereby reducing the impact on data sending and receiving, and ensuring the safety and punctual arrival of the train. In addition, the present invention can promptly detect the success or failure of user data transmission through the added retransmission mechanism, solving the problem of retransmission mechanism lag and unsuitability for one-way data in the prior art, and improving the reliability and efficiency of railway-specific mobile communications.

[0062] Other beneficial effects of the embodiments of the present invention will be further described below. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 This is a flowchart of LLC entity data retransmission according to an embodiment of the present invention.

[0064] Figure 2 This is a flow chart of starting data retransmission when uplink TBF establishment fails according to an embodiment of the present invention.

[0065] Figure 3 This is a flow chart of initiating data retransmission when conflict resolution fails according to an embodiment of the present invention. DETAILED DESCRIPTION

[0066] The following is a detailed description of the embodiments of the present invention. It should be emphasized that the following description is only exemplary and is not intended to limit the scope and application of the present invention.

[0067] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present invention, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0068] The embodiment of the present invention provides a GPRS data retransmission method for a railway dedicated mobile terminal, comprising the following steps:

[0069] Step S1. Data preservation and parameter initialization: The LLC entity receives user data, preserves the user data, and initializes the number of retransmissions and validity period parameters related to the user data;

[0070] Step S2. Uplink TBF connection application: The RLC / MAC entity applies to establish an uplink TBF connection to send user data;

[0071] Step S3. Uplink TBF connection result processing: The RLC / MAC entity determines whether the uplink TBF connection is successfully established based on the network response; if the connection fails, the failure result is notified to the LLC entity;

[0072] Step S4. Data sending and retransmission decision:

[0073] If the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF;

[0074] If the sent user data is not confirmed by the network within the expected time, the RLC / MAC entity notifies the LLC entity of the failure to send the data;

[0075] The LLC entity determines whether to retransmit based on the transmission failure result, the number of retransmissions, and the data validity period parameters;

[0076] If the judgment result is retransmission, the LLC entity increases the number of retransmissions and retransmits the saved user data;

[0077] If the judgment result is not retransmission, the LLC entity clears the saved user data and resets related parameters.

[0078] See also Figure 1 In a preferred embodiment, the method includes an LLC entity data retransmission process, wherein: in step S1, the LLC entity distinguishes between user data and signaling data, saves only the user data, and initializes the number of retransmissions and validity period parameters; in step S2, when the RLC / MAC entity sends user data, if an uplink TBF connection is successfully established, the data is sent, and if the connection fails, the LLC entity is notified of the sending result; in step S3, after receiving the notification from the RLC / MAC entity, the LLC entity performs the following operations according to the sending result: if the user data is sent successfully, the LLC entity clears the saved user data. data, and reset the number of retransmissions and validity period parameters; if the user data fails to be sent, the LLC entity determines whether the saved user data is within the validity period and whether the number of retransmissions is not greater than the maximum number of retransmissions; in step S4, the LLC entity performs the following operations: if the user data is within the validity period and the number of retransmissions is less than the maximum number of retransmissions, the LLC entity increases the number of retransmissions by one, and re-adds the saved user data to the sending queue for retransmission; if the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data, and resets the number of retransmissions and validity period parameters to prepare for receiving new user data.

[0079] See also Figure 2 In a preferred embodiment, the method includes starting a data retransmission process when an uplink TBF establishment fails, wherein: in step S2, when the RLC / MAC entity applies for an uplink TBF connection, if it receives an immediate assignment rejection message or the channel request timeout timer times out due to no response, the LLC entity will perform the following operations: increase the number of retransmissions by one; if the number of retransmissions does not exceed the preset maximum number of retransmissions, start the retransmission mechanism and prepare to retransmit LLCPDU data; in step S3, after receiving the result of the uplink TBF connection establishment failure notified by the RLC / MAC entity, the LLC entity will perform the following operations: determine whether the user data is still within the validity period; if the user data Within the validity period, and the number of retransmissions does not exceed the preset maximum number of retransmissions, the LLC entity increases the number of retransmissions by one and starts the retransmission mechanism; if the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data and resets the number of retransmissions and the validity period parameters; in step S4, if the LLC entity starts the retransmission mechanism after the uplink TBF connection establishment fails, the following operations will be performed: retransmit the LLCPDU data request; if the retransmission is successful, clear the saved user data, and reset the number of retransmissions and the validity period parameters; if the retransmission fails, continue to determine whether to continue retransmission based on the number of retransmissions and the data validity period until the retransmission conditions are not met or the retransmission is successful.

[0080] See also Figure 3In a preferred embodiment, the method includes starting a data retransmission process when conflict resolution fails. In step S4: if the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF; monitor the network's confirmation message for sending data, if no confirmation message from the network is received within a certain period of time, that is, the data sending confirmation waiting counter reaches the maximum value, the RLC / MAC entity considers that the data sending fails; the RLC / MAC entity notifies the LLC entity of the result of the data sending failure; after receiving the result of the RLC / MAC entity sending failure, the LLC entity checks whether the user data is within the set validity period and whether the number of retransmissions has not reached the preset maximum number of retransmissions; if the user data is within the validity period and the number of retransmissions has not reached the maximum number of retransmissions, the LLC entity increases the number of retransmissions by one, and starts the retransmission mechanism to prepare to retransmit the LLC PDU data; if the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters; if the LLC entity starts the retransmission mechanism, it sends a retransmission LLC PDU data. PDU request; if the retransmission is successful, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters; if the retransmission fails again, the LLC entity continues to determine whether to continue retransmission based on the number of retransmissions and data validity period until the retransmission conditions are not met or the retransmission is successful.

[0081] The embodiment of the present invention further provides a GPRS data retransmission device for a railway dedicated mobile terminal, comprising:

[0082] Data storage and parameter initialization module: The LLC entity receives user data, stores the user data, and initializes the number of retransmissions and validity period parameters related to the user data;

[0083] Uplink TBF connection application module: RLC / MAC entity applies to establish an uplink TBF connection to send user data;

[0084] Uplink TBF connection result processing module: The RLC / MAC entity determines whether the uplink TBF connection is successfully established based on the network response; if the connection fails, the failure result is notified to the LLC entity;

[0085] Data sending and retransmission decision module:

[0086] If the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF;

[0087] If the sent user data is not confirmed by the network within the expected time, the RLC / MAC entity notifies the LLC entity of the sending failure result;

[0088] The LLC entity determines whether to retransmit based on the transmission failure result, the number of retransmissions, and the data validity period parameters;

[0089] If the judgment result is retransmission, the LLC entity increases the number of retransmissions and retransmits the saved user data;

[0090] If the judgment result is not retransmission, the LLC entity clears the saved user data and resets related parameters.

[0091] The GPRS data retransmission method for a railway-specific mobile terminal of the present invention distinguishes user data from signaling data in the LLC entity, and increases the number of retransmissions and saves data validity period parameters for user data storage, so that the LLC entity can effectively manage user data. The RLC / MAC entity adds a process for reporting the user data transmission results to the LLC entity, so that the LLC entity can timely judge and decide whether to retransmit data based on the transmission failure results, the number of retransmissions and the data validity period parameters. This mechanism effectively avoids the problem of the locomotive integrated wireless communication equipment resetting the mobile terminal due to continuous data loss, reduces the impact on data transmission and reception, and ensures the safety and punctual arrival of the train. At the same time, the present invention can timely discover the success or failure of user data transmission through the retransmission mechanism added to the mobile terminal, solves the lag of the locomotive integrated wireless communication equipment retransmission mechanism, and the limitation of not being suitable for one-way data, and improves the reliability and efficiency of railway-specific mobile communications.

[0092] The specific embodiments of the present invention are further described below.

[0093] A GPRS data retransmission method for a railway-dedicated mobile terminal, the method mainly involves an LLC (Logical Link Control) entity, an RLC (Radio Link Control) entity, and a MAC (Medium Access Control) entity. In the LLC entity, the user data sent by the SNDCP (Subnetwork Dependent Convergence Protocol) entity is saved, and the signaling data sent by the GMM (GPRS Mobility Management) entity is not saved. In addition, the number of retransmissions and the validity period parameters are increased. When RLC / MAC sends user data, a process for reporting the data transmission result to the LLC entity is added. When user data transmission fails, if the saved data is within the validity period and the number of retransmissions is not greater than the maximum number of retransmissions, the LLC entity increases the number of retransmissions by 1 and retransmits the saved data. Otherwise, the LLC entity clears the saved data and resets the number of retransmissions and the validity period parameters. Figure 1 FIG. 4 shows the LLC entity data retransmission process according to an embodiment of the present invention.

[0094] Before the mobile terminal sends user PDU data, the RLC / MAC entity applies to establish an uplink TBF (Temporary BlockFlow) connection by sending a channel request (ChannelRequest / PacketChannelRequest). During this process, if an immediate assignment (Immediate Assignment / PacketUplinkAssignment) message is received from the network, it indicates that the uplink TBF connection can be established normally; if an immediate assignment rejection (ImmediateAssignmentReject / PacketAccessReject) message is received, or no response is received, resulting in the T3146 timer timing out, it indicates that the uplink TBF establishment has failed, that is, the PDU data cannot be sent normally. When the uplink TBF establishment fails, the RLC / MAC entity sends the TBF establishment result to the LLC entity. When the LLC entity receives the notification of TBF establishment failure, if the saved data is within the validity period and the number of retransmissions is not greater than the maximum number of retransmissions, the number of retransmissions is increased by 1, and the retransmission mechanism is started. Figure 2 FIG. 4 is a flowchart of starting data retransmission when uplink TBF establishment fails according to an embodiment of the present invention.

[0095] After the uplink TBF is successfully established, the mobile terminal will send uplink data on the uplink TBF. If the counter N3104 reaches the maximum value and the network still has not received the confirmation message (Packet UplinkAck / Nack) for the sent data, the conflict resolution fails, indicating that the user data is not received normally. The RLC / MAC entity sends the result of the user PDU data sending failure to the LLC entity. When the LLC entity determines that the saved data is within the validity period and the number of retransmissions is not greater than the maximum number of retransmissions, it will increase the number of retransmissions by 1 and start the retransmission mechanism. Figure 3 As shown, a data retransmission process is initiated when conflict resolution fails according to an embodiment of the present invention.

[0096] Due to the complex communication environment along the railway, there is a problem of data loss during the transmission of GPRS data. In China Railway Special Mobile Communications, if the locomotive integrated wireless communication equipment does not receive response data for two-way data such as activity detection data within 30 seconds, it will be considered that the data transmission has failed and retransmission will be started. If no response data is received after three retransmissions, the GPRS mobile terminal will be reset.

[0097] In summary, the present invention proposes a GPRS data retransmission method for a railway-specific mobile terminal, which realizes effective management of GPRS data by distinguishing user data from signaling data in the LLC entity, saving user data, and introducing the number of retransmissions and the validity period parameters of the saved data. The RLC / MAC entity is responsible for reporting the user data sending results to the LLC entity, so that the LLC entity can judge whether the saved data needs to be retransmitted or cleared based on this information and the number of retransmissions and the validity period parameters of the data. This method mechanism not only responds to the failure of user data transmission in a timely manner, avoids the resetting of the mobile terminal by the locomotive integrated wireless communication device due to continuous data loss, reduces the impact on data transmission and reception, and effectively ensures the safety and punctual arrival of the train. In addition, by adding a retransmission mechanism in the mobile terminal, the present invention can timely discover the success or failure of user data transmission, solves the hysteresis problem of the retransmission mechanism of the locomotive integrated wireless communication device, and breaks through the limitation of not being applicable to one-way data, thereby improving the reliability and efficiency of railway-specific mobile communications.

[0098] An embodiment of the present invention further provides a storage medium for storing a computer program, which at least performs the above method when executed.

[0099] An embodiment of the present invention further provides a control device, comprising a processor and a storage medium for storing a computer program; wherein the processor is configured to execute at least the method described above when executing the computer program.

[0100] An embodiment of the present invention further provides a processor, wherein the processor executes a computer program and at least executes the method described above.

[0101] The storage medium can be implemented by any type of non-volatile storage device, or a combination thereof. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a ferromagnetic random access memory, a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The storage medium described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0102] In the several embodiments provided by the present invention, it should be understood that the disclosed systems and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0103] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0104] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0105] Those skilled in the art can understand that: all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiments; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), disks or optical disks, etc. Various media that can store program codes.

[0106] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

[0107] The methods disclosed in the several method embodiments provided by the present invention can be arbitrarily combined without conflict to obtain new method embodiments.

[0108] The features disclosed in several product embodiments provided by the present invention can be arbitrarily combined without conflict to obtain new product embodiments.

[0109] The features disclosed in several method or device embodiments provided by the present invention can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

[0110] The above contents are further detailed descriptions of the present invention in combination with specific preferred embodiments, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For those skilled in the art of the present invention, several equivalent substitutions or obvious variations can be made without departing from the concept of the present invention, and the performance or use is the same, which should be regarded as belonging to the protection scope of the present invention.

Claims

1. A GPRS data retransmission method for a railway dedicated mobile terminal, characterized in that: The following steps are involved: S1. Data storage and parameter initialization: The LLC entity receives user data, saves the user data, and initializes the number of retransmissions and validity period parameters associated with the user data; S2. Uplink TBF connection application: RLC / MAC entity applies to establish an uplink TBF connection to send user data; S3 uplink TBF connection result processing: RLC / MAC entity determines whether the uplink TBF connection is successfully established based on the network response; if the connection fails, the failure result is notified to the LLC entity; S4. Data sending and retransmission decision: If the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF; If the sent user data is not confirmed by the network within the expected time, the RLC / MAC entity notifies the LLC entity of the sending failure result; The LLC entity determines whether to retransmit based on the transmission failure result, the number of retransmissions, and the data validity period parameters; If the judgment result is retransmission, the LLC entity increases the number of retransmissions and retransmits the saved user data; If the judgment result is not retransmission, the LLC entity clears the saved user data and resets related parameters.

2. The GPRS data retransmission method for a railway dedicated mobile terminal as claimed in claim 1, characterized in that: Includes LLC entity data retransmission process, including: In step S1, the LLC entity distinguishes between user data and signaling data, saves only the user data, and initializes the number of retransmissions and validity period parameters; In step S2, when the RLC / MAC entity sends user data, if the uplink TBF connection is successfully established, the data is sent; if the connection fails, the LLC entity is notified of the sending result; In step S3, after receiving the notification from the RLC / MAC entity, the LLC entity performs the following operations according to the transmission result: If the user data is sent successfully, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters; If the user data fails to be sent, the LLC entity determines whether the saved user data is within the validity period and whether the number of retransmissions is not greater than the maximum number of retransmissions; In step S4, the LLC entity performs the following operations: If the user data is within the validity period and the number of retransmissions is less than the maximum number of retransmissions, the LLC entity increases the number of retransmissions by one and re-adds the saved user data to the sending queue for retransmission; If the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters to prepare for receiving new user data.

3. The GPRS data retransmission method for a railway dedicated mobile terminal as claimed in claim 1 or 2, characterized in that: It includes the process of starting data retransmission upon failure of uplink TBF establishment, in which: In step S2, when the RLC / MAC entity applies for an uplink TBF connection, if it receives an immediate assignment rejection message or the channel request timeout timer times out due to no response received, the LLC entity performs the following operations: Increase the number of retransmissions by one; If the number of retransmissions does not exceed the preset maximum number of retransmissions, the retransmission mechanism is started to prepare to retransmit LLC PDU data; In step S3, after receiving the result of the uplink TBF connection establishment failure notified by the RLC / MAC entity, the LLC entity will perform the following operations: Determine whether the user data is still within the validity period; If the user data is within the validity period and the number of retransmissions does not exceed the preset maximum number of retransmissions, the LLC entity increases the number of retransmissions by one and starts the retransmission mechanism; If the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters; In step S4, if the LLC entity starts the retransmission mechanism after the uplink TBF connection establishment fails, the following operations will be performed: Retransmission of LLC PDU data request; If the retransmission is successful, the saved user data is cleared, and the number of retransmissions and validity period parameters are reset; If the retransmission fails, continue to determine whether to retransmit based on the number of retransmissions and the data validity period until the retransmission conditions are no longer met or the retransmission is successful.

4. The GPRS data retransmission method for a railway dedicated mobile terminal as claimed in claim 1, characterized in that: Including starting the data retransmission process when the conflict resolution fails, in step S4: If the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF; Monitor the network's confirmation message for sending data. If no confirmation message is received from the network within a certain period of time, that is, the data sending confirmation waiting counter reaches the maximum value, the RLC / MAC entity considers that the data sending has failed; The RLC / MAC entity notifies the LLC entity of the result of data transmission failure; After receiving the result of the RLC / MAC entity sending failure, the LLC entity checks whether the user data is within the set validity period and whether the number of retransmissions has not reached the preset maximum number of retransmissions; If the user data is within the validity period and the number of retransmissions has not reached the maximum number of retransmissions, the LLC entity increases the number of retransmissions by one and starts the retransmission mechanism to prepare to retransmit the LLC PDU data; If the user data is not within the validity period or the number of retransmissions has reached the maximum number of retransmissions, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters; If the LLC entity starts the retransmission mechanism, it sends a request to retransmit LLC PDU; If the retransmission is successful, the LLC entity clears the saved user data and resets the number of retransmissions and validity period parameters; If the retransmission fails again, the LLC entity continues to determine whether to continue retransmission based on the number of retransmissions and the data validity period until the retransmission condition is no longer met or the retransmission is successful.

5. A GPRS data retransmission device for a railway dedicated mobile terminal, characterized in that: include: Data storage and parameter initialization module: The LLC entity receives user data, stores the user data, and initializes the number of retransmissions and validity period parameters related to the user data; Uplink TBF connection application module: RLC / MAC entity applies to establish an uplink TBF connection to send user data; Uplink TBF connection result processing module: The RLC / MAC entity determines whether the uplink TBF connection is successfully established based on the network response; if the connection fails, the failure result is notified to the LLC entity; Data sending and retransmission decision module: If the uplink TBF connection is successfully established, the mobile terminal sends user data on the uplink TBF; If the sent user data is not confirmed by the network within the expected time, the RLC / MAC entity notifies the LLC entity of the sending failure result; The LLC entity determines whether to retransmit based on the transmission failure result, the number of retransmissions, and the data validity period parameters; If the judgment result is retransmission, the LLC entity increases the number of retransmissions and retransmits the saved user data; If the judgment result is not retransmission, the LLC entity clears the saved user data and resets related parameters.

6. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the GPRS data retransmission method for a railway dedicated mobile terminal as described in any one of claims 1 to 4 is implemented.

7. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the GPRS data retransmission method for a railway dedicated mobile terminal as described in any one of claims 1 to 4 is implemented.

Images