Data monitoring method and device, data sending end and readable storage medium

Abstract

The application discloses a data monitoring method and device, a data sending end and a readable storage medium, and belongs to the technical field of communication. The data monitoring method of the application comprises the following steps: a data sending end acquires a counter; and based on the counter, a data transmission fault is monitored.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a data monitoring method, device, data transmitting end, and readable storage medium. Background Technology

[0002] For services with lifespan requirements, it's essential to prevent consecutive data transmission failures. Multiple consecutive failures can render the receiving application unusable, disrupting normal communication. However, currently, there's no method to monitor for consecutive data transmission failures at the sending end. Therefore, how to monitor data transmission failures is a pressing issue that needs to be addressed. Summary of the Invention

[0003] This application provides a data monitoring method, apparatus, and data transmitting end, which can solve the problem of how to monitor data transmission failures.

[0004] Firstly, a data monitoring method is provided, including:

[0005] The data sender obtains the counter;

[0006] The data sending end monitors data transmission failures based on the counter.

[0007] Secondly, a data monitoring device is provided, comprising:

[0008] The acquisition module is used to acquire the counter;

[0009] A monitoring module is used to monitor data transmission failures based on the counter.

[0010] Thirdly, a data transmitting end is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0011] Fourthly, a data transmitting end is provided, including a processor and a communication interface, wherein the processor is used to acquire a counter and, based on the counter, monitor data transmission failures.

[0012] Fifthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0013] In a sixth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the steps of the method described in the first aspect.

[0014] In a seventh aspect, a computer program / program product is provided, the computer program / program product being stored in a non-transient storage medium, the program / program product being executed by at least one processor to perform the steps of the method as described in the first aspect.

[0015] In this embodiment, the data sending end can acquire a counter and monitor data transmission failures based on the counter. Therefore, a fault monitoring mechanism can be introduced during data transmission to detect data transmission failures, thereby preventing multiple consecutive data transmission failures and ensuring normal communication. Attached Figure Description

[0016] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0017] Figure 2 This is a flowchart of a data monitoring method provided in an embodiment of this application;

[0018] Figure 3 This is a schematic diagram of the structure of a data monitoring device provided in an embodiment of this application;

[0019] Figure 4 This is a schematic diagram of the structure of a data sending end provided in an embodiment of this application;

[0020] Figure 5 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0021] Figure 6 This is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0023] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0024] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0025] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. In this context, terminal 11 can also be referred to as terminal equipment or user equipment (UE). Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms.

[0026] Optionally, the scenarios applicable to the embodiments of this application include, but are not limited to, services with survival time requirements. For services with higher reliability requirements, data packets sent by the sender have an expected arrival time. If the receiver does not receive the data packet within the expected arrival time, it enters the survival time. If the receiver still cannot successfully receive the data packet within the survival time, the communication service will enter an unavailable state, requiring a longer time to restore normal communication service. Simply put, for this type of service, multiple consecutive data packet losses are not allowed; otherwise, the corresponding communication service will enter an unavailable state.

[0027] Optionally, in this application embodiment, the data sending end (which may be simply referred to as the sending end) can be a terminal or a network-side device, and the corresponding data receiving end (which may be simply referred to as the receiving end) can be a network-side device or a terminal.

[0028] Optionally, in the embodiments of this application, both the data sender and receiver can be terminals or network-side devices. For example, in a sidelink scenario, both the data sender and receiver are terminals.

[0029] The data monitoring method, apparatus, data sending end, and readable storage medium provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0030] Please see Figure 2 , Figure 2 This is a flowchart of a data monitoring method provided in an embodiment of this application. The method is executed by a data sending end, which can be a terminal or a network-side device. Figure 2 As shown, the method includes the following steps:

[0031] Step 21: The data sending end obtains the counter.

[0032] In this embodiment, the counter is used to monitor data transmission failures. One implementation is that the timer is used to monitor data transmission failures at the Packet Data Convergence Protocol (PDCP) layer. For example, the counter records the number of data packets that failed to transmit, such as the number of consecutively failed data packets. When a data packet transmission failure is confirmed, the corresponding counter increments by 1. It should be noted that the aforementioned data packets can be PDCP layer data packets, such as PDCP Service Data Units (SDUs). Alternatively, the counter can record the number of transmission failures, such as the number of consecutive transmission failures. When a transmission failure is confirmed, the corresponding counter increments by 1. It should be noted that the aforementioned transmission failure can be a PDCP layer data packet transmission failure, or a failure of the Medium Access Control (MAC) Protocol Data Unit (PDU) or Transport Block (TB) transmission carrying the PDCP layer data packets.

[0033] One way to determine if a data packet transmission has failed is by receiving a retransmission scheduling signaling for the data packet. Correspondingly, when a scheduling signaling is received and used to schedule data packet retransmission, the corresponding counter is incremented by 1. Alternatively, in an unauthorized scenario, a HARQ-NACK feedback message is received. Correspondingly, when a HARQ-NACK feedback message is received, this feedback message indicates data transmission failure, and the corresponding counter is incremented by 1.

[0034] In some embodiments, a data transmission failure can be understood as N consecutive data transmission failures, where N is an integer greater than 1 and can be set based on actual needs.

[0035] Step 22: The data sending end monitors data transmission failures based on a counter.

[0036] For example, a data transmission failure is considered to have occurred when the counter's count reaches a predetermined threshold. In this case, a reset operation can be performed on the counter. It should be noted that the aforementioned threshold can be configured on the network side or determined by the terminal. For example, in a sideline scenario, the threshold can be determined by the data receiving terminal and indicated to the data sending terminal, or it can be determined by the data sending terminal itself.

[0037] For example, the PDCP entity at the aforementioned data sending end can monitor data transmission failures based on a counter.

[0038] In some embodiments, for services with time-to-live requirements, in the event of a data transmission failure, such as M consecutive (M less than N) data transmission failures, the data sender can change the transmission strategy to ensure that subsequent data packets can be transmitted with higher reliability, thereby preventing the receiving application from entering a communication unavailable state.

[0039] In the data monitoring method of this application embodiment, the data sending end can acquire a counter and monitor data transmission faults based on the counter. Therefore, a fault monitoring mechanism can be introduced during data transmission to detect data transmission faults, thereby avoiding continuous data transmission failures and ensuring normal communication.

[0040] In this embodiment of the application, when monitoring data transmission failures based on a counter, it is necessary to ensure that the counter is accurately reset in order to accurately detect data transmission failures. If the counter cannot be accurately reset, the data sending end may incorrectly determine that a data transmission failure has occurred, thereby affecting normal communication. For example, if the counter cannot be accurately reset, the sending end may incorrectly determine that a data transmission failure has occurred, and then use a transmission strategy with higher resource consumption for subsequent data transmission in the hope that subsequent data packets will be transmitted successfully, which will lead to unnecessary waste of resources.

[0041] Optionally, the data transmitter may perform a reset operation on the counter under preset conditions to avoid data transmission failures caused by the transmitter's incorrect judgment due to the counter's inaccurate reset. The preset conditions include, but are not limited to, at least one of the following:

[0042] 1) A data transmission failure occurs. For example, when the counter's count value reaches a predetermined threshold, the data sender considers a data transmission failure to have occurred. In this case, a reset operation is performed on the counter.

[0043] 2) A change in transmission strategy occurs. For example, if a data transmission failure is detected, or if data transmission is detected to have recovered from a failure, the data sender may change the transmission strategy and reset the counter.

[0044] 3) Recovering from data transmission failure. For example, after confirming a data transmission failure but learning that the data packet was successfully transmitted, the data sender considers the data transmission failure recovered and can perform a reset operation on the counter. As another example, upon receiving a transmission policy change indication and considering the data transmission failure recovered, a reset operation can be performed on the counter.

[0045] 4) Data transmission successful.

[0046] It should be noted that resetting the counter upon successful data transmission can include: directly resetting the counter's count value to its initial value (e.g., 0); alternatively, resetting the counter if data transmission is successful but the counter's count value is not the initial value (e.g., 0). For example, if the counter's count value is not equal to the initial value (e.g., 0) upon successful data transmission, the timer is reset; or, if the timer's count value is equal to the initial value (e.g., 0), the timer reset operation is not performed. The aforementioned data can be PDCP layer data, where the PDCP layer learns of successful data transmission based on an indication from the RadioLink Control (RLC) layer, or it can learn of successful data transmission directly based on an indication from the MAC layer. Specifically, the aforementioned data can be PDCP layer data, where the PDCP entity can learn of successful PDCP layer data transmission based on an indication from its associated RLC entity, or it can learn of successful PDCP layer data transmission based on an indication from its associated MAC entity.

[0047] One method to determine successful data transmission is as follows: the `configuredGrantTimer` associated with the Hybrid Automatic Repeat reQuest (HARQ) process that transmits data times out. This `configuredGrantTimer` is started or restarted upon receiving scheduling signaling for its associated HARQ process and upon data transmission using its associated HARQ process. In this example, the MAC layer can determine whether data transmission was successful based on the `configuredGrantTimer` associated with the HARQ process carrying PDCP layer data. Specifically, when the timer times out, the MAC layer's determination that the HARQ process carrying PDCP layer data has successfully transmitted data is equivalent to the PDCP layer data transmission being successful. Another method to stop the `configuredGrantTimer` is as follows: the data sender (e.g., UE) stops the `configuredGrantTimer` after receiving signaling containing a specific identifier. It should be noted that when the data sender receives the aforementioned signaling, it can be considered that the HARQ process associated with this timer has successfully transmitted data. In this example, the MAC layer's determination that the HARQ process carrying PDCP layer data has successfully transmitted data is equivalent to the aforementioned successful transmission of PDCP layer data.

[0048] Another way to achieve successful data transmission is by receiving a new transmission scheduling signaling. Specifically, this occurs when a scheduling signaling is received and used to schedule the new transmission of data packets. Alternatively, in an unauthorized scenario, this occurs by receiving a HARQ-ACK feedback message. Specifically, when a HARQ-ACK feedback message is received, this feedback message indicates that the data transmission was successful.

[0049] 5) Receive the first indication information, which is used to indicate the reset of the corresponding counter.

[0050] Optionally, the first indication information may also indicate the identifier of the data radio bearer (DRB) corresponding to the counter that needs to be reset, such as the DRB ID. Alternatively, the first indication information may also indicate the identifier of the QoS stream corresponding to the counter that needs to be reset, such as QFI.

[0051] In some embodiments, the data sender is the UE, and the UE can reset the corresponding counter after receiving the indication information sent by the NW to indicate that the corresponding counter should be reset.

[0052] Optionally, the data sender can adjust the transmission strategy in real time based on data transmission status to ensure normal data transmission. The aforementioned changes to the transmission strategy may include at least one of the following:

[0053] (1) Change from the first transmission strategy to the second transmission strategy.

[0054] The first transmission strategy is the strategy used when no data transmission failure occurs, i.e., the strategy used before a data transmission failure occurs, which can also be understood as the transmission strategy used under normal data transmission conditions. The second transmission strategy is the strategy used after a data transmission failure occurs, which can also be understood as the transmission strategy used to handle data transmission failures. For example, the first transmission strategy provides a low reliability guarantee and is used when no data transmission failure occurs; the second transmission strategy provides a high reliability guarantee and is used after a data transmission failure occurs. When a data transmission failure is detected based on a counter, the first transmission strategy can be changed to the second transmission strategy, at which point the counter is reset. For example, the counter can be reset to its initial value, such as 0.

[0055] For example, one potential implementation method for a data transmitter (such as a UE) to determine that a transmission policy change has occurred is as follows: when the data transmitter (such as a UE) receives a resource indication corresponding to activating the second transmission policy, the data transmitter (such as a UE) changes its transmission policy from the first transmission policy to the second transmission policy. Alternatively, when the data transmitter (such as a UE) receives a transmission path indication corresponding to activating the second transmission policy, the data transmitter (such as a UE) changes its transmission policy from the first transmission policy to the second transmission policy.

[0056] (2) Change from the second transmission strategy to the first transmission strategy.

[0057] The first transmission strategy is the strategy used when no data transmission failure occurs; that is, the strategy used before a data transmission failure occurs, which can also be understood as the transmission strategy used under normal data transmission conditions. The second transmission strategy is the strategy used after a data transmission failure occurs; it can also be understood as the transmission strategy used to handle data transmission failures. For example, if it is known that the data transmission failure has been resolved, the second transmission strategy is changed back to the first transmission strategy, and the counter is reset. For example, the counter can be reset to its initial value, such as 0.

[0058] For example, one potential implementation method for a data sender (such as a UE) to determine that a transmission policy change has occurred is as follows: when the data sender (such as a UE) receives a resource indication corresponding to deactivating the second transmission policy, the data sender (such as a UE) changes its transmission policy from the second transmission policy to the first transmission policy. Alternatively, when the data sender (such as a UE) receives a transmission path indication corresponding to deactivating the second transmission policy, the data sender (such as a UE) changes its transmission policy from the second transmission policy to the first transmission policy.

[0059] As an optional embodiment, when data transmission is detected to have recovered from a transmission failure, a reset operation is performed on the counter when the second transmission strategy is changed back to the first transmission strategy.

[0060] As another optional embodiment, when the second transmission strategy meets preset conditions, a counter is reset when the second transmission strategy is changed to the first transmission strategy. For example, the preset conditions may be reaching a preset time, reaching a preset number of transmissions, or reaching a preset number of data packets transmitted. Specifically, for instances where the preset time is reached, it can be implemented using a timer. The timer is started when the second transmission strategy is used, and when the timer expires, a counter is reset when the second transmission strategy is changed to the first transmission strategy. For instances where the preset number of transmissions or the preset number of data packets is reached, it can be implemented using a counter (different from the counter used to monitor data transmission failures in this application). When the number of data packets transmitted using the first transmission strategy (e.g., the number of successfully transmitted data packets) or the number of transmissions (e.g., the number of successful transmissions) reaches a preset value, a counter is reset when the second transmission strategy is changed to the first transmission strategy.

[0061] (3) Change from the second transmission strategy to the third transmission strategy.

[0062] The second transmission strategy is the one used after a data transmission failure occurs; it can also be understood as the transmission strategy used to handle transmission failures. The third transmission strategy is the one used after the data transmission failure has been resolved. For example, upon learning that the data transmission failure has been resolved, the second transmission strategy is changed to the third transmission strategy, and the counter is reset. For instance, the counter can be reset to its initial value, such as 0.

[0063] It should be noted that the first and third transmission strategies mentioned above can be different transmission strategies. For example, if a bearer is configured with a data replication function, the first transmission strategy corresponds to the transmission strategy when the data replication function is deactivated, the second transmission strategy may correspond to the transmission strategy when all transmission paths are activated, and the third transmission strategy may correspond to the transmission strategy when only two transmission paths are activated for data replication.

[0064] It should also be noted that the third transmission strategy can be configured by the network layer for the terminal. When configuring the third transmission strategy, additional indication information can be provided to indicate that the data transmission failure has been recovered. In this case, the terminal needs to perform operations based on counter-based monitoring of data transmission failures.

[0065] In this embodiment, the data sending end can stop monitoring data transmission failures. For example, when the first transmission strategy is changed to the second transmission strategy, monitoring for data transmission failures is stopped. The second transmission strategy is the transmission strategy used after a data transmission failure occurs.

[0066] Optionally, the aforementioned actions to stop monitoring data transmission failures may include at least one of the following:

[0067] Stop sending auxiliary information, which is used to update or reset the counter;

[0068] Stop updating the counter's count value.

[0069] Optionally, the data sending end may include a first protocol entity and a second protocol entity. The aforementioned cessation of sending auxiliary information may include: the second protocol entity ceasing to send auxiliary information to the first protocol entity, which is used to assist the first protocol entity in updating or resetting the counter.

[0070] Optionally, before stopping the transmission of auxiliary information, the first protocol entity may send a second indication message to the second protocol entity, which instructs the second protocol entity to stop sending auxiliary information to the first protocol entity. Afterwards, the second protocol entity stops sending auxiliary information to the first protocol entity, which was used to assist the first protocol entity in updating or resetting a counter.

[0071] Optionally, after the data transmission failure is recovered, the first protocol entity may send a third indication message to the second protocol entity. The third indication message is used to instruct the second protocol entity to resume sending auxiliary information to the first protocol entity, so that the first protocol entity can update or reset the counter based on the auxiliary information.

[0072] In some embodiments, the first protocol entity is a PDCP entity, and the auxiliary information includes indications of data transmission failure and / or success. The cessation of providing auxiliary information is performed by a second protocol entity. For example, the second protocol entity can be an RLC entity, in which case the RLC entity associated with the PDCP entity stops providing auxiliary information to the PDCP entity. Alternatively, the second protocol entity can also be a MAC entity, in which case the MAC entity associated with the PDCP entity stops providing auxiliary information to the PDCP entity. It should be noted that the second protocol entity's action of stopping the provision of auxiliary information can be determined by the second protocol entity based on data monitoring. For example, if the second protocol entity detects data transmission on (all) transmission paths corresponding to the second transmission strategy, it can determine that the current transmission strategy has changed from the first transmission strategy to the second transmission strategy, and thus stops providing auxiliary information to the first protocol entity.

[0073] In some embodiments, a second protocol entity (such as an RLC entity) provides auxiliary information to a first protocol entity (such as a PDCP entity). This auxiliary information is an indication of data transmission failure. In this case, the first protocol entity can stop updating the counter value based on the auxiliary information. Alternatively, the first protocol entity can ignore or discard the auxiliary information.

[0074] Optionally, stopping the transmission of auxiliary information to the first protocol entity can be achieved by stopping the transmission of first auxiliary information, stopping the transmission of both first and second auxiliary information, or stopping the transmission of second auxiliary information. The first auxiliary information indicates data transmission failure, and the second auxiliary information indicates data transmission success.

[0075] In this embodiment of the application, after stopping the monitoring of data transmission failure, the data sender can restart the monitoring of data transmission failure if at least one of the following conditions is met:

[0076] 1) Data is successfully transmitted while using the second transmission strategy, which is a transmission strategy used after a data transmission failure occurs. This can also be understood as a transmission strategy used to handle data transmission failures. For example, if data is successfully transmitted during the use of the second transmission strategy, the data sender considers the data transmission failure to have been recovered. In this case, the data sender restarts the counter-based data transmission failure monitoring operation.

[0077] 2) The conditions for changing the transmission strategy are met during the use of the second transmission strategy.

[0078] Optionally, the condition for satisfying the transmission policy change may include at least one of the following:

[0079] ① A transmission policy change indication is obtained, indicating that the data transmission failure has been recovered. For example, this transmission policy change indication may be provided by the data receiver to the data sender. Specifically, the aforementioned transmission policy change indication may be an indication to deactivate the transmission path corresponding to the second transmission policy. Alternatively, the aforementioned transmission policy change indication may be an indication to deactivate the resource corresponding to the second transmission policy.

[0080] ② The second transmission strategy is used to meet preset conditions. These preset conditions can be reaching a preset time, a preset number of transmissions, or a preset number of data packets transmitted. Specifically, for the use case of reaching the preset time, a timer can be used, which starts when the second transmission strategy is used. If the timer expires, the second transmission strategy is changed back to the first transmission strategy, and the data sender restarts the counter-based data transmission fault monitoring operation. For the use case of reaching the preset number of transmissions or the preset number of data packets transmitted, a counter can be used (different from the counter used to monitor data transmission faults in this application). If the number of data packets transmitted using the first transmission strategy (e.g., the number of successfully transmitted data packets) or the number of transmissions (e.g., the number of successful transmissions) reaches a preset value, the second transmission strategy is changed back to the first transmission strategy, and the data sender restarts the counter-based data transmission fault monitoring operation. It should be noted that the preset time, preset number of transmissions, and preset number of data packets transmitted can all be configured on the network side or determined by the data sender itself. As an application scenario, such as in a sidelink scenario, the preset time, preset number of transmissions, and preset number of data packets can all be determined by the data receiving terminal and indicated to the data sending terminal, or they can be determined by the data sending terminal itself.

[0081] It should be noted that the data monitoring method provided in this application embodiment can be executed by a data monitoring device, or by a control module within the data monitoring device for executing the data monitoring method. This application embodiment uses the execution of the data monitoring method by a data monitoring device as an example to illustrate the data monitoring device provided in this application embodiment.

[0082] Please see Figure 3 , Figure 3 This is a schematic diagram of a data monitoring device provided in an embodiment of this application. The device is applied to a data transmitting end, which can be a terminal or a network-side device. Figure 3As shown, the data monitoring device 30 includes:

[0083] Module 31 is used to acquire the counter;

[0084] Monitoring module 32 is used to monitor data transmission failures based on the counter.

[0085] Optionally, the counter is used to record the number of data packets that failed to transmit; or, the counter is used to record the number of transmission failures.

[0086] Optionally, the data monitoring device 30 may also include:

[0087] An execution module is used to perform a reset operation on the counter when preset conditions are met;

[0088] The preset conditions include at least one of the following:

[0089] Data transmission failure occurred;

[0090] A change in transmission strategy has occurred;

[0091] Recover from data transmission failure;

[0092] Data successfully transmitted;

[0093] Upon receiving a first indication message, the first indication message is used to instruct the corresponding counter to be reset.

[0094] Optionally, the transmission strategy change includes at least one of the following:

[0095] The transmission strategy was changed from the first transmission strategy to the second transmission strategy.

[0096] The transmission strategy was changed from the second transmission strategy to the first transmission strategy.

[0097] The transmission strategy was changed from the second to the third.

[0098] The first transmission strategy is the transmission strategy used when no data transmission failure occurs, the second transmission strategy is the transmission strategy used to handle data transmission failure, and the third transmission strategy is the transmission strategy used after the data transmission failure is recovered.

[0099] Optionally, the monitoring module 32 is also used to: stop monitoring for data transmission failures.

[0100] Optionally, the action of stopping monitoring data transmission failures includes at least one of the following:

[0101] Stop sending auxiliary information, which is used to update or reset the counter;

[0102] Stop updating the counter's count value.

[0103] Optionally, the monitoring module 32 includes a first protocol entity and a second protocol entity; the second protocol entity is used to: stop sending the auxiliary information to the first protocol entity, the auxiliary information being used to assist the first protocol entity in updating or resetting the counter.

[0104] Furthermore, before ceasing to send auxiliary information, the first protocol entity is configured to: send a second indication message to the second protocol entity, the second indication message being configured to instruct the second protocol entity to cease sending the auxiliary information to the first protocol entity.

[0105] Optionally, after the data transmission failure is recovered, the first protocol entity is further configured to: send a third indication message to the second protocol entity, the third indication message being used to instruct the second protocol entity to resume sending the auxiliary information to the first protocol entity.

[0106] Optionally, the monitoring module 32 is also configured to: restart monitoring for data transmission failures if at least one of the following conditions is met:

[0107] Data was successfully transmitted while using the second transmission strategy; wherein, the second transmission strategy is the transmission strategy used after a data transmission failure occurs.

[0108] The conditions for changing the transmission strategy are met during the use of the second transmission strategy.

[0109] Optionally, satisfying the transmission strategy change conditions during the use of the second transmission strategy includes at least one of the following:

[0110] The transmission strategy change indication information is obtained, which indicates that the data transmission failure has been recovered;

[0111] The second transmission strategy is used to meet preset conditions, which may be reaching a preset time, reaching a preset number of transmissions, or reaching a preset number of data packets transmitted.

[0112] The data monitoring device 30 in this embodiment can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. This device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This embodiment does not impose specific limitations.

[0113] The data monitoring device 30 provided in this embodiment can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0114] Optional, such as Figure 4 As shown, this application embodiment also provides a data sending end 40, which is a terminal or network-side device, including a processor 41, a memory 42, and a program or instruction stored in the memory 42 that can run on the processor 41. When the program or instruction is executed by the processor 41, it implements the various processes of the above-described data monitoring method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0115] This application also provides a terminal, including a processor and a communication interface. The processor is used to acquire a counter and, based on the counter, monitor data transmission faults. When this terminal is a data sending end, it can implement the various processes of the above-described data monitoring method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0116] Specifically, Figure 5 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0117] The terminal 500 includes, but is not limited to, at least some of the following components: radio frequency unit 501, network module 502, audio output unit 503, input unit 504, sensor 505, display unit 506, user input unit 507, interface unit 508, memory 509, and processor 510.

[0118] Those skilled in the art will understand that the terminal 500 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 510 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 5The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0119] It should be understood that, in this embodiment, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042. The GPU 5041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 506 may include a display panel 5061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 507 includes a touch panel 5071 and other input devices 5072. The touch panel 5071 is also called a touch screen. The touch panel 5071 may include a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0120] In this embodiment, the radio frequency unit 501 receives downlink data from the network-side device and processes it for the processor 510; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0121] The memory 509 can be used to store software programs or instructions and various data. The memory 509 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 509 may include high-speed random access memory and non-volatile memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0122] Processor 510 may include one or more processing units; optionally, processor 510 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 510.

[0123] The processor 510 is used to acquire the counter and, based on the counter, monitor data transmission failures.

[0124] In this embodiment, terminal 500 can acquire a counter and monitor data transmission failures based on the counter. Therefore, a fault monitoring mechanism can be introduced during data transmission to detect data transmission failures, thereby avoiding continuous data transmission failures and ensuring normal communication.

[0125] Optionally, the processor 510 is further configured to perform a reset operation on the counter when preset conditions are met; the preset conditions include at least one of the following: a data transmission failure occurs; a transmission strategy change occurs; the data transmission failure is recovered; data is successfully transmitted; or a first indication is received, wherein the first indication is used to indicate that the corresponding counter is reset.

[0126] This allows for accurate reset of the counter, preventing data transmission failures caused by incorrect judgments at the transmitting end due to inaccurate counter reset, thus ensuring normal communication.

[0127] Optionally, the transmission strategy change includes at least one of the following:

[0128] The transmission strategy was changed from the first transmission strategy to the second transmission strategy.

[0129] The transmission strategy was changed from the second transmission strategy to the first transmission strategy.

[0130] The transmission strategy was changed from the second to the third.

[0131] The first transmission strategy is the transmission strategy used when no data transmission failure occurs, the second transmission strategy is the transmission strategy used after a data transmission failure occurs, and the third transmission strategy is the transmission strategy used after the data transmission failure is recovered.

[0132] The terminal 500 provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0133] This application also provides a network-side device, including a processor and a communication interface. The processor is used to acquire a counter and, based on the counter, monitor data transmission faults. When this network-side device is a data sender, it can implement all the processes of the above-described data monitoring method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0134] Specifically, embodiments of this application also provide a network-side device. For example... Figure 6 As shown, the network-side device 60 includes an antenna 61, a radio frequency (RF) device 62, and a baseband device 63. The antenna 61 is connected to the RF device 62. In the uplink direction, the RF device 62 receives information through the antenna 61 and transmits the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes the information to be transmitted and sends it to the RF device 62. The RF device 62 processes the received information and then transmits it through the antenna 61.

[0135] The aforementioned frequency band processing device can be located in the baseband device 63, and the aforementioned data monitoring can be implemented in the baseband device 63, which includes a processor 64 and a memory 65.

[0136] Baseband device 63 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 6 As shown, one of the chips, for example, is a processor 64, which is connected to a memory 65 to call the program in the memory 65 and execute the network-side device operations shown in the above method embodiments.

[0137] The baseband device 63 may also include a network interface 66 for exchanging information with the radio frequency device 62, such as a common public radio interface (CPRI).

[0138] Specifically, the network-side device 60 in this application embodiment further includes instructions or programs stored in the memory 65 and executable on the processor 64. When the network-side device 60 is a data transmitter, the processor 64 can call the instructions or programs in the memory 65 to implement the various processes of the above-described data monitoring method embodiment and achieve the same technical effect. To avoid repetition, these will not be described in detail here.

[0139] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described data monitoring method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0140] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0141] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described data monitoring method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0142] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0143] This application also provides a computer program / program product, which is stored in a non-transient storage medium. The program / program product is executed by at least one processor to implement the various processes of the above-described data monitoring method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0144] It should be noted that, in this document, 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. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0145] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network-side device, etc.) to execute the methods described in the various embodiments of this application.

[0146] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A data monitoring method, characterized in that, include: The data sender obtains the counter; The data sending end monitors data transmission failures based on the counter; The method further includes: Under certain preset conditions, the data sending end performs a reset operation on the counter; wherein, the preset conditions include: a change in transmission strategy occurs.

2. The method according to claim 1, characterized in that, The counter is used to record the number of data packets that failed to be transmitted; or, The counter is used to record the number of transmission failures.

3. The method according to claim 1, characterized in that, The preset conditions also include at least one of the following: Data transmission failure occurred; Recover from data transmission failure; Data successfully transmitted; Upon receiving a first indication message, the first indication message is used to instruct the corresponding counter to be reset.

4. The method according to claim 1, characterized in that, The change in transmission strategy includes at least one of the following: The transmission strategy was changed from the first transmission strategy to the second transmission strategy. The transmission strategy was changed from the second transmission strategy to the first transmission strategy. The transmission strategy was changed from the second to the third. The first transmission strategy is the transmission strategy used when no data transmission failure occurs, the second transmission strategy is the transmission strategy used to handle data transmission failure, and the third transmission strategy is the transmission strategy used after the data transmission failure is recovered.

5. The method according to claim 1, characterized in that, The method further includes: The data sending end stops monitoring for data transmission failures.

6. The method according to claim 5, characterized in that, The action of stopping monitoring data transmission failure includes at least one of the following: Stop sending auxiliary information, which is used to update or reset the counter; Stop updating the counter's count value.

7. The method according to claim 6, characterized in that, The data sending end includes a first protocol entity and a second protocol entity; the stopping of sending auxiliary information includes: The second protocol entity stops sending the auxiliary information to the first protocol entity, the auxiliary information being used to assist the first protocol entity in updating or resetting the counter.

8. The method according to claim 7, characterized in that, Before ceasing the transmission of auxiliary information, the method further includes: The first protocol entity sends a second instruction message to the second protocol entity, the second instruction message being used to instruct the second protocol entity to stop sending the auxiliary information to the first protocol entity.

9. The method according to claim 7, characterized in that, The method further includes: After the data transmission failure is recovered, the first protocol entity sends a third indication message to the second protocol entity, which instructs the second protocol entity to resume sending the auxiliary information to the first protocol entity.

10. The method according to claim 5, characterized in that, After stopping monitoring for data transmission failures, the method further includes: The data transmitter will resume monitoring for data transmission failures if at least one of the following conditions is met: Data was successfully transmitted while using the second transmission strategy; wherein, the second transmission strategy is the transmission strategy used after a data transmission failure occurs. The conditions for changing the transmission strategy are met during the use of the second transmission strategy.

11. The method according to claim 10, characterized in that, The conditions for satisfying the transmission strategy change include at least one of the following: The transmission strategy change indication information is obtained, which indicates that the data transmission failure has been recovered; The second transmission strategy is used to meet the preset conditions.

12. A data monitoring device, characterized in that, include: The acquisition module is used to acquire the counter; The monitoring module is used to monitor data transmission failures based on the counter. The device further includes: An execution module is used to perform a reset operation on the counter when preset conditions are met; wherein the preset conditions include: a change in transmission strategy has occurred.

13. The apparatus according to claim 12, characterized in that, The preset conditions also include at least one of the following: Data transmission failure occurred; Recover from data transmission failure; Data successfully transmitted; Upon receiving a first indication message, the first indication message is used to instruct the corresponding counter to be reset.

14. The apparatus according to claim 12, characterized in that, The change in transmission strategy includes at least one of the following: The transmission strategy was changed from the first transmission strategy to the second transmission strategy. The transmission strategy was changed from the second transmission strategy to the first transmission strategy. The transmission strategy was changed from the second to the third. The first transmission strategy is the transmission strategy used when no data transmission failure occurs, the second transmission strategy is the transmission strategy used after a data transmission failure occurs, and the third transmission strategy is the transmission strategy used after the data transmission failure is recovered.

15. A data transmitter, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the data monitoring method as described in any one of claims 1 to 11.

16. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the data monitoring method as described in any one of claims 1 to 11.

Images