Method, device, data sending end and storage medium for exiting survival time state
By acquiring information and adjusting the transmission strategy at the data sending end, the resource overhead problem of the sending end being in a long-term live state is solved, and efficient resource utilization is achieved.
Patent Information
- Application Number
- CN202111229247.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-10-21
- Publication Date
- 2026-02-17
- Estimated Expiration
- 2041-10-21
AI Technical Summary
How to make the sender exit the time-to-live state to avoid the resource overhead caused by long-term use of high-reliability transmission strategies.
The data sender obtains the first information and, based on this information, removes the target bearer from the liveness time state. It reduces resource consumption by adjusting the transmission path or deactivating the data replication function.
This effectively avoids the resource overhead caused by using a high-reliability transmission strategy while maintaining the lifespan state for an extended period, thus reducing resource consumption.
Smart Images

Figure CN116017494B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application belongs to the technical field of communication, and particularly relates to a method and device for exiting a survival time state, a data sending end and a readable storage medium. BACKGROUND
[0002] For a service with a survival time requirement, it is necessary to ensure that there is no continuous N times of data transmission failure, otherwise the receiving end application will enter a service unavailable state. In the case of continuous M (M < N) times of data transmission failure, the sending end will enter a survival time (ST) state. In the survival time state, the sending end will use a high-reliability transmission strategy to transmit data in the hope that subsequent data packets can be successfully transmitted. However, if the sending end is always in the survival time state, it will bring great resource overhead due to the use of the high-reliability transmission strategy. Therefore, how to make the sending end exit the survival time state is a problem that needs to be solved at present. SUMMARY
[0003] The embodiments of the present application provide a method and device for exiting a survival time state, a data sending end and a readable storage medium, which can solve the problem of how to make the sending end exit the survival time state.
[0004] In a first aspect, a method for exiting a survival time state is provided, comprising:
[0005] The data sending end acquires first information;
[0006] Based on the first information, a target bearer of the data sending end exits a survival time state.
[0007] In a second aspect, a device for exiting a survival time state is provided, comprising:
[0008] An acquisition module is configured to acquire first information;
[0009] An exit module is configured to exit a target bearer from a survival time state based on the first information.
[0010] In a third aspect, a data sending end is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction is executed by the processor to implement the steps of the method according to the first aspect.
[0011] In a fourth aspect, a data sending end is provided, comprising a processor and a communication interface, wherein the processor is configured to acquire first information, and exit a target bearer from a survival time state based on the first information.
[0012] In a fifth aspect, a readable storage medium is provided, and the readable storage medium stores a program or instructions, and the program or instructions are executed by a processor to implement the steps of the method in the first aspect.
[0013] In a sixth aspect, a chip is provided, and the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run a program or instructions to implement the method in the first aspect.
[0014] In a seventh aspect, a computer program / program product is provided, and the computer program / program product is stored in a non-transitory storage medium, and the computer program / program product is executed by at least one processor to implement the steps of the method in the first aspect.
[0015] In the embodiments of the present application, the data sending end can obtain first information, and based on the first information, the target bearer exits the alive time state. Thus, the data sending end can exit the alive time state, thereby avoiding a large resource consumption caused by using a high reliability transmission strategy in the case of long-term maintenance in the alive time state, and thus the resource consumption can be reduced. BRIEF DESCRIPTION OF DRAWINGS
[0016] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;
[0017] Figure 2 is a flowchart of a method for exiting an alive time state provided by the embodiments of the present application;
[0018] Figure 3 is a structural schematic diagram of an apparatus for exiting an alive time state provided by the embodiments of the present application;
[0019] Figure 4 is a structural schematic diagram of a data sending end provided by the embodiments of the present application;
[0020] Figure 5 is a structural schematic diagram of a terminal provided by the embodiments of the present application;
[0021] Figure 6 is a structural schematic diagram of a network side device provided by the embodiments of the present application. DETAILED DESCRIPTION
[0022] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present 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. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.
[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, the receiving end has an expected arrival time for data packets. When the receiving end does not receive a data packet within the expected arrival time, it enters the survival time. If the receiving end still fails to successfully receive any data packet within the survival time, the communication service will enter an unavailable state, requiring a longer time for the recovery process of normal communication service. Simply put, for this type of service, multiple consecutive data packets cannot be lost; otherwise, the receiving end's communication will enter an unavailable state.
[0027] Optionally, in the embodiments of this application, 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 following description, in conjunction with the accompanying drawings, details the method, apparatus, data transmitter, and readable storage medium for exiting the liveness time state provided in this application, through some embodiments and application scenarios.
[0030] Please see Figure 2 , Figure 2 This is a flowchart illustrating a method for exiting a liveness time state according to 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 first information.
[0032] In this embodiment, the first information is used to assist in determining whether to remove the target bearer from the liveness time state. The first information is related to the target bearer at the data sending end.
[0033] Optionally, when acquiring the first information, it may be acquired by the Radio Resource Control (RRC) entity of the data transmitter or by the Medium Access Control (MAC) entity of the data transmitter; there is no limitation on which one is acquired.
[0034] Step 22: Based on the first information, the target bearer of the data sending end exits the liveness time status.
[0035] In some embodiments, the service corresponding to the target bearer has a time-to-live requirement. For example, this time-to-live requirement means that two data packets cannot be lost consecutively. Therefore, if one data packet is lost, the target bearer can enter a time-to-live state. In the time-to-live state, the data sender can use a transmission strategy with higher reliability to transmit the service data corresponding to the target bearer.
[0036] Optionally, after obtaining the first information, the data sender can remove the target bearer from its lifetime state based on that first information. In some embodiments, the target bearer is located in a Packet Data Convergence Protocol (PDCP) entity, which removes the target bearer from its lifetime state based on the obtained first information. In other embodiments, the target bearer can correspond to other entities, and the data sender can also remove the target bearer from its lifetime state through other entities corresponding to the target bearer, based on the obtained first information.
[0037] In some embodiments, the target bearer may have PDCP replication functionality. The network may configure at least two transmission paths for the target bearer, which may correspond to a single network node or multiple different network nodes. When sending data, the PDCP layer of the target bearer can transmit a replicated copy of the data through each transmission path to improve data transmission reliability.
[0038] In the method for exiting the time-to-live state according to the embodiments of this application, the data sending end can obtain first information and, based on the first information, exit the time-to-live state of the target bearer. This allows the data sending end to exit the time-to-live state, thereby avoiding the resource overhead caused by using a high-reliability transmission strategy while maintaining the time-to-live state for an extended period, and reducing resource consumption.
[0039] Optionally, when the RRC entity of the data sender obtains the first information, the target bearer of the data sender may exit the time-to-live state if at least one of the following conditions is met:
[0040] 1) The first information includes first indication information, which is used to indicate that the target bearer needs to exit the lifetime state. For example, the first indication information can be a one-bit indication. One scenario is that when the network-side device sends this first indication information to the data sender (such as the UE), the data sender determines that the target bearer needs to exit the lifetime state. Another scenario is that when the first indication information is set to a preset value, the data sender determines that the target bearer needs to exit the lifetime state.
[0041] 2) The first information includes the second indication information, which is used to indicate the deactivation of the data replication function of the target bearer. For example, if the protocol stipulates or the network configuration specifies that the data replication function of at least two transmission paths is used when the target bearer enters the lifetime state, then when the network-side device instructs the data replication function of the target bearer to be deactivated, the data sending end (such as the terminal UE) believes that the target bearer needs to exit the lifetime state.
[0042] 3) The first information includes first configuration information, wherein the transmission path status corresponding to the target bearer configured by the first configuration information satisfies a first preset condition. For example, the first configuration information is used to reconfigure the transmission path status corresponding to the target bearer.
[0043] Optionally, the first preset condition described above may include at least one of the following:
[0044] ① Any currently active transmission path is deactivated, meaning that any currently active transmission path of the target bearer configured in the first configuration information is deactivated. For example, if the target bearer's currently active transmission paths include leg1, leg2, and leg3, and if the first configuration information configures the target bearer's transmission paths leg1 and leg2 to be active while leg3 is deactivated, then the data sender considers that the target bearer needs to exit the lifetime state.
[0045] Based on ① above, the first preset condition mentioned above can also be: any N currently active transmission paths are deactivated, where N is an integer greater than 1, and N can be agreed upon by the protocol or set according to actual needs.
[0046] ② The number of active transmission paths is less than or equal to a first preset value, meaning the number of active transmission paths of the target bearer configured in the first configuration information is less than or equal to the first preset value. For example, if the number of active transmission paths of the target bearer configured in the first configuration information is 2, which is less than the preset value of 3, then the target bearer at the data sending end needs to exit the lifetime state.
[0047] ③ The number of transmission paths in the deactivated state is greater than or equal to the second preset value, that is, the number of transmission paths in the deactivated state of the target bearer configured in the first configuration information is greater than or equal to the second preset value. For example, the number of transmission paths in the deactivated state of the target bearer configured in the first configuration information is 2, which is greater than the preset value of 1. In this case, the target bearer of the data sending end needs to exit the liveness time state.
[0048] Understandably, the first and second preset values mentioned above may be agreed upon in the agreement or set according to actual needs, and there are no restrictions on this.
[0049] Optionally, when the MAC entity of the data sender obtains the first information, the target bearer of the data sender may exit the time-to-live state if at least one of the following conditions is met:
[0050] 1) The first information includes a first Medium Access Control Control Element (MAC CE), which indicates that the target bearer needs to exit the time-to-live state. As an example, the first MAC CE can be identified by a dedicated Logical Channel Identifier (LCID), which identifies the first MAC CE as an exiting time-to-live state MAC CE. For instance, a currently reserved LCID value is used, specifically to indicate the first MAC CE. When the MAC entity at the data sender acquires the first MAC CE, it determines that the target bearer needs to exit the time-to-live state based on this first MAC CE. In one case, the first MAC CE can be zero bits, meaning only the MAC header. In this case, when the data sender acquires the first MAC CE on the target bearer's dedicated resources (such as dedicated Dynamic Grant (DG) resources), it considers the target bearer to need to exit the time-to-live state. In another scenario, the first MAC CE can carry the bearer identifier of the target bearer. Upon acquiring this first MAC CE, the data sender can assume that the target bearer corresponding to the bearer identifier carried by the first MAC CE needs to exit the time-to-live state. Yet another scenario is that the first MAC CE indicates the bit corresponding to the target bearer; setting this bit to a preset value (e.g., 1) indicates that the corresponding target bearer needs to exit the time-to-live state.
[0051] 2) The first information includes a second MAC CE, which is used to indicate the deactivation of the data replication function of the target bearer. For example, when the data sender obtains a second MAC CE indicating the deactivation of the data replication function of the target bearer, the data sender believes that the target bearer needs to exit the lifetime state. This second MAC CE is, for example, a traditional data replication function activation / deactivation MAC CE.
[0052] 3) The first information includes a third MAC CE, which indicates that the transmission path status corresponding to the target bearer meets the second preset condition. For example, the third MAC CE is used to indicate the deactivation or deactivation of the transmission path corresponding to the target bearer.
[0053] Optionally, the second preset condition described above may include at least one of the following:
[0054] ① Any currently active transmission path is deactivated, meaning the third MAC CE indicates that any currently active transmission path of the target bearer is deactivated. For example, if the target bearer's currently active transmission paths include leg1, leg2, and leg3, and the third MAC CE indicates that transmission paths leg1 and leg2 of the target bearer are active while leg3 is deactivated, then the data sender considers that the target bearer needs to exit the time-to-live state.
[0055] Based on ① above, the second preset condition mentioned above can also be: any N currently active transmission paths are deactivated, where N is an integer greater than 1, and N can be agreed upon by the protocol or set according to actual needs.
[0056] ② The number of active transmission paths is less than or equal to a third preset value, meaning the number of active transmission paths of the target bearer indicated by the third MAC CE is less than or equal to the third preset value. For example, if the number of active transmission paths of the target bearer indicated by the third MAC CE is 2, which is less than the preset value of 3, then the target bearer at the data sending end needs to exit the time-to-live state.
[0057] ③ The number of transmission paths in the deactivated state is greater than or equal to the fourth preset value, that is, the number of transmission paths in the deactivated state of the target bearer indicated by the third MAC CE is greater than or equal to the fourth preset value. For example, the number of transmission paths in the deactivated state of the target bearer indicated by the third MAC CE is 2, which is greater than the preset value of 1. In this case, the target bearer of the data sender needs to exit the time-to-live state.
[0058] Understandably, the aforementioned third and fourth preset values may be agreed upon in the agreement or set according to actual needs, and there are no restrictions on this.
[0059] ④ Only one transmission path is active, meaning the third MAC CE indicates that only one transmission path of the target bearer is active. In this case, the data sender considers the target bearer to need to exit the time-to-live state.
[0060] In this embodiment of the application, when a target bearer exits its time-to-live (TTL) state, the data sending end can perform TTL-related operations on the target bearer. These TTL-related operations can be performed simultaneously with or after the target bearer exits its TTL state.
[0061] Optionally, the first protocol entity at the data sender may perform exit time-to-live status related operations on the target bearer.
[0062] It should be noted that before the first protocol entity at the data sending end performs operations related to exiting the time-to-live (TTL) state for the target bearer, the first protocol entity can receive third indication information from the second protocol entity at the data sending end. This third indication information indicates that the target bearer is exiting the TTL state. The second protocol entity is the protocol entity that obtained the first information. For example, the second protocol entity can be an RRC entity, and the first protocol entity can be a MAC entity or a PDCP entity. Furthermore, the second protocol entity can provide the third indication information to multiple first protocol entities. For instance, if the target bearer corresponds to two MAC entities, when the RRC entity at the data sending end obtains the first information, it can provide the third indication information to these two MAC entities, which will then perform the TTL state exit operations on the target bearer. As another example, the second protocol entity can be a MAC entity, and the first protocol entity can be an RRC entity or a PDCP entity. For example, if the target bearer corresponds to two MAC entities, when any MAC entity obtains the first information, it provides the third indication information to the PDCP entity corresponding to the target bearer, which will then perform the TTL state exit operations on the target bearer. As yet another example, both the first and second protocol entities can be MAC entities.
[0063] Optionally, the exit time-to-live status related operations performed by the data sender on the target bearer may include at least one of the following:
[0064] (1) Reset the first counter, which is used to monitor data transmission failures on the transmission paths of the target bearer. For example, the first protocol entity (e.g., a MAC entity) at the data sending end maintains a first counter for each transmission path and monitors the transmission status of the corresponding transmission path based on the first counter. If the count value of the first counter reaches a preset value, a transmission failure is considered to have occurred on the corresponding transmission path. When the target bearer exits its lifetime state, the first protocol entity at the data sending end performs a reset operation on the first counter corresponding to each transmission path. As an example, in the case of exiting the lifetime operation, the first protocol entity (e.g., the MAC entity) initiates the provision of transmission failure indication information to the third protocol entity (e.g., the MAC entity). For example, after exiting the lifetime, if the first counter value reaches a preset value, the first protocol entity (e.g., the MAC entity) provides transmission failure indication information to the third protocol entity (e.g., the MAC entity).
[0065] (2) Reset the second counter, which is used to monitor data transmission failures in the cell group where the transmission path of the target bearer is located. For example, the first protocol entity (e.g., MAC entity) of the data sender maintains a second counter for each cell group where the transmission path of the target bearer is located, and monitors the transmission status of the corresponding cell group based on the second counter. If the count value of the second counter reaches a preset value, it is considered that a transmission failure has occurred in the corresponding cell group. When the corresponding target bearer exits its lifetime status, the first protocol entity of the data sender performs a reset operation on the second counter corresponding to the cell group. As an example, in the case of exiting the lifetime operation, the first protocol entity (e.g., MAC entity) initiates the provision of transmission failure indication information to the third protocol entity (e.g., MAC entity). For example, after exiting the lifetime, if the value of the first counter reaches a preset value, the first protocol entity (e.g., MAC entity) provides transmission failure indication information to the third protocol entity (e.g., MAC entity).
[0066] (3) Reset the third counter, which is used to monitor data transmission failures of the target bearer. For example, the first protocol entity (such as the PDCP entity) of the data sending end maintains a third counter for the target bearer and monitors the transmission status of the corresponding target bearer based on the third counter. If the count value of the third counter reaches a preset value, it is considered that the target bearer has experienced a transmission failure. If the target bearer exits the liveness time state, the first protocol entity of the data sending end performs a reset operation on the third counter corresponding to the target bearer.
[0067] In this embodiment of the application, when the target bearer exits its time-to-live state, the data sending end can transmit data corresponding to the target bearer based on second configuration information. This second configuration information indicates the available transmission path after the target bearer exits its time-to-live state. Transmitting data corresponding to the target bearer based on the second configuration information can be performed either simultaneously with or after the target bearer exits its time-to-live state.
[0068] Optionally, the second configuration information may satisfy at least one of the following:
[0069] 1) The second configuration information is pre-configured. For example, an exit time-of-life field is introduced, which indicates the available transmission path after the target bearer exits its life-of-life period. For instance, this exit time-of-life field is pre-configured to the data sender via an RRC message. When it is determined based on the acquired first information that the target bearer needs to exit its life-of-life period, the data of the target bearer is transmitted using the pre-configured transmission path available after the exit time-of-life period.
[0070] 2) The second configuration information is carried through the first information. As an example, the first MACCE included in the first information may additionally carry transmission path indication information to indicate the available transmission path after the target bearer exits its time-to-live state. As another example, when the third MACCE included in the first information indicates an exit from the time-to-live state, the active transmission path indicated by the third MACCE is used to transmit the target bearer's data.
[0071] 3) The second configuration information is agreed upon by the protocol. For example, if it is determined that the target bearer has exited the liveness state, the protocol stipulates that the primary transmission path will always be used to transmit the target bearer's data. As an example, if the target bearer's data replication function is deactivated by instructing it via an RRC message or a second MAC CE, the primary transmission path will always be used to transmit the target bearer's data after the target bearer exits the liveness state.
[0072] It should be noted that the method for exiting the lifespan state provided in this application embodiment can be executed by an apparatus for exiting the lifespan state, or by a control module within that apparatus for executing the method for exiting the lifespan state. This application embodiment uses an apparatus for exiting the lifespan state executing the method for exiting the lifespan state as an example to illustrate the apparatus for exiting the lifespan state provided in this application embodiment.
[0073] Please see Figure 3 , Figure 3 This is a schematic diagram of a device for exiting a liveness time state provided in an embodiment of this application. This device is applied to a data sending end, which can be a terminal or a network-side device. Figure 3 As shown, the device 30 for exiting the survival time state includes:
[0074] Module 31 is used to acquire the first information;
[0075] The exit module 32 is used to, based on the first information, assign the target a liveness time exit status.
[0076] In this embodiment, first information can be obtained, and based on this first information, the target bearer can be removed from the time-to-live state. This allows the data sender to exit the time-to-live state, thereby avoiding the resource overhead associated with using high-reliability transmission strategies while maintaining the time-to-live state for an extended period, and reducing resource consumption.
[0077] Optionally, the acquisition module 31 is set in the RRC entity, and the RRC entity acquires the first information; or, the acquisition module 31 is set in the MAC entity, and the MAC entity acquires the first information.
[0078] Optionally, when the RRC entity obtains the first information, the exit module 32 is specifically configured to: exit the target bearer's liveness state when at least one of the following conditions is met:
[0079] The first information includes first indication information, which is used to indicate the target bearer's exit survival time status;
[0080] The first information includes second instruction information, which is used to instruct the deactivation of the data replication function of the target bearer;
[0081] The first information includes first configuration information, wherein the transmission path status corresponding to the target bearer configured by the first configuration information satisfies a first preset condition.
[0082] Optionally, the first preset condition includes at least one of the following:
[0083] Any currently active transmission path is deactivated;
[0084] Any N currently active transmission paths are deactivated, where N is an integer greater than 1;
[0085] The number of active transmission paths is less than or equal to a first preset value;
[0086] The number of transmission paths in the deactivated state is greater than or equal to the second preset value.
[0087] Optionally, when the MAC entity obtains the first information, the exit module 32 is specifically configured to: exit the target bearer's liveness state when at least one of the following conditions is met:
[0088] The first information includes a first MAC CE, which is used to indicate the target bearer's exit time-to-live status;
[0089] The first information includes a second MAC CE, which is used to instruct the deactivation of the data replication function of the target bearer;
[0090] The first information includes a third MAC CE, which indicates that the transmission path status corresponding to the target bearer meets a second preset condition.
[0091] Optionally, the second preset condition includes at least one of the following:
[0092] Any currently active transmission path is deactivated;
[0093] Any N currently active transmission paths are deactivated, where N is an integer greater than 1;
[0094] The number of active transmission paths is less than or equal to the third preset value;
[0095] The number of transmission paths in the deactivated state is greater than or equal to the fourth preset value;
[0096] Only one transmission path is active.
[0097] Optionally, the device 30 for exiting the liveness state also includes:
[0098] The execution module is used to perform operations related to the exiting the lifetime state of the target bearer when the target bearer exits the lifetime state.
[0099] Optionally, the execution module is placed in the first protocol entity, which is used to perform operations related to the exit from the time-to-live state of the target bearer when the target bearer exits the time-to-live state.
[0100] Optionally, the first protocol entity is further configured to:
[0101] Before performing operations related to exiting the lifetime status of the target bearer, a third indication information is received from a second protocol entity; wherein the third indication information indicates that the target bearer exits the lifetime status, and the second protocol entity is the protocol entity that obtained the first information.
[0102] Optionally, the exit survival time status related operations include at least one of the following:
[0103] Reset the first counter, which is used to monitor data transmission failures in the transmission path carried by the target;
[0104] Reset the second counter, which is used to monitor data transmission failures in the cell group where the transmission path carried by the target is located;
[0105] Reset the third counter, which is used to monitor data transmission failures carried by the target.
[0106] Optionally, the device 30 for exiting the liveness state also includes:
[0107] The transmission module is configured to transmit data corresponding to the target bearer based on second configuration information when the target bearer exits the liveness time state; wherein the second configuration information is used to indicate the transmission path available after exiting the liveness time state.
[0108] The device for exiting the liveness time state in this application embodiment can be a device, a device with an operating system, or an electronic device, or it can be 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 application embodiment does not specifically limit the specific type of terminal.
[0109] The device 30 for exiting the liveness time state 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.
[0110] 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, a program or instruction stored in the memory 42 and executable on the processor 41. When the program or instruction is executed by the processor 41, it implements the various processes of the above-described method embodiment for exiting the life-time state and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0111] This application also provides a terminal, including a processor and a communication interface. The processor is used to acquire first information and, based on the first information, to exit the life-time state of a target bearer. When this terminal is a data sending end, it can implement the various processes of the above-described method embodiments for exiting the life-time state and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0112] Specifically, Figure 5 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.
[0113] 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.
[0114] 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 5 The 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.
[0115] 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.
[0116] 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.
[0117] 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.
[0118] 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.
[0119] The processor 510 is used to acquire first information and, based on the first information, to determine the target bearer's exit from the lifespan state.
[0120] In this embodiment, terminal 500 can obtain first information and, based on the first information, remove the target bearer from the time-liveness state. This allows terminal 500 to exit the time-liveness state, thereby avoiding the resource overhead associated with using a high-reliability transmission strategy while maintaining the time-liveness state for an extended period, and reducing resource consumption.
[0121] Understandably, the terminal 500 provided in this application embodiment is capable of achieving... 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.
[0122] This application also provides a network-side device, including a processor and a communication interface. The processor is used to acquire first information and, based on the first information, to exit the target bearer's lifetime state. When this network-side device is a data sending end, it can implement the various processes of the above-described method embodiments for exiting the lifetime state and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0123] 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.
[0124] The aforementioned frequency band processing device can be located in the baseband device 63. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 63, which includes a processor 64 and a memory 65.
[0125] Baseband device 63 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 6As 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.
[0126] 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).
[0127] Specifically, the network-side device in this application embodiment further includes: instructions or programs stored in memory 65 and executable on processor 64. Processor 64 can call the instructions or programs in memory 65 to implement the various processes of the above-described method embodiment for exiting the liveness time state and achieve the same technical effect. To avoid repetition, they will not be described in detail here.
[0128] This application also provides a readable storage medium, which can be volatile or non-volatile. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described method embodiment for exiting the time-to-live state and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0129] 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.
[0130] 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 method embodiment for exiting the life-time state, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0131] 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.
[0132] This application also provides a computer program / program product, which is stored in a non-transient storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-described method embodiment for exiting the life-time state, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0133] 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.
[0134] 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.
[0135] 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 method for exiting a lifespan state, characterized in that, include: The data sender obtains the first information; Based on the first information, the target bearer of the data sending end exits the liveness time status; In the case where the target bearer exits the liveness time state, the method further includes: The data sending end performs operations related to the exit liveness time status of the target bearer; The operation related to exiting the survival time status includes at least one of the following: Reset the first counter, which is used to monitor data transmission failures in the transmission path carried by the target; Reset the second counter, which is used to monitor data transmission failures in the cell group where the transmission path carried by the target is located; Reset the third counter, which is used to monitor data transmission failures carried by the target.
2. The method according to claim 1, characterized in that, The acquisition of the first information includes any one of the following: The Radio Resource Control (RRC) entity at the data transmitting end acquires the first information; The Media Access Control (MAC) entity at the data sending end acquires the first information.
3. The method according to claim 2, characterized in that, When the RRC entity obtains the first information, the step of determining the target bearer's time-to-live status based on the first information includes: The target bearer of the data transmitter exits the time-to-live state when at least one of the following conditions is met: The first information includes first indication information, which is used to indicate the target bearer's exit survival time status; The first information includes second instruction information, which is used to instruct the deactivation of the data replication function of the target bearer; The first information includes first configuration information, wherein the transmission path status corresponding to the target bearer configured by the first configuration information satisfies a first preset condition.
4. The method according to claim 3, characterized in that, The first preset condition includes at least one of the following: Any currently active transmission path is deactivated; Any N currently active transmission paths are deactivated, where N is an integer greater than 1; The number of active transmission paths is less than or equal to a first preset value; The number of transmission paths in the deactivated state is greater than or equal to the second preset value.
5. The method according to claim 2, characterized in that, When the MAC entity obtains the first information, the step of determining the target bearer's time-to-live status based on the first information includes: The target bearer of the data transmitter exits the time-to-live state when at least one of the following conditions is met: The first information includes a first media access control unit (MAC CE), which is used to indicate the target bearer's out-of-life time status. The first information includes a second MAC CE, which is used to instruct the deactivation of the data replication function of the target bearer; The first information includes a third MAC CE, which indicates that the transmission path status corresponding to the target bearer meets a second preset condition.
6. The method according to claim 5, characterized in that, The second preset condition includes at least one of the following: Any currently active transmission path is deactivated; Any N currently active transmission paths are deactivated, where N is an integer greater than 1; The number of active transmission paths is less than or equal to the third preset value; The number of transmission paths in the deactivated state is greater than or equal to the fourth preset value; Only one transmission path is active.
7. The method according to claim 1, characterized in that, The operation related to exiting the liveness time status of the target bearer includes: The first protocol entity at the data sending end performs exit liveness time status related operations on the target bearer.
8. The method according to claim 7, characterized in that, Before the first protocol entity performs operations related to the exit liveness status of the target bearer, the method further includes: The first protocol entity receives third indication information from the second protocol entity; wherein the third indication information is used to indicate the target bearer's exit liveness time status, and the second protocol entity is the protocol entity that obtained the first information.
9. The method according to claim 1, characterized in that, In the case that the target bearer exits the time-to-live state, the method further includes: The data sending end transmits the data corresponding to the target bearer based on the second configuration information; The second configuration information is used to indicate the available transmission path after exiting the liveness time state.
10. The method according to claim 9, characterized in that, The second configuration information satisfies at least one of the following: The second configuration information is pre-configured; The second configuration information is carried through the first information; The second configuration information is as agreed upon in the protocol.
11. A device for exiting a lifespan state, characterized in that, include: The acquisition module is used to acquire the initial information. The exit module is used to assign the target's exit survival time status based on the first information; The device further includes: The execution module is used to perform operations related to the exiting the lifetime state of the target bearer when the target bearer exits the lifetime state. The operation related to exiting the survival time status includes at least one of the following: Reset the first counter, which is used to monitor data transmission failures in the transmission path carried by the target; Reset the second counter, which is used to monitor data transmission failures in the cell group where the transmission path carried by the target is located; Reset the third counter, which is used to monitor data transmission failures carried by the target.
12. The apparatus according to claim 11, characterized in that, The acquisition module is set in the RRC entity, and the RRC entity acquires the first information; or, The acquisition module is set in the MAC entity, and the MAC entity acquires the first information.
13. The apparatus according to claim 12, characterized in that, When the RRC entity obtains the first information, the exit module is specifically configured to: exit the target bearer's liveness state when at least one of the following conditions is met: The first information includes first indication information, which indicates the target bearer's exit survival time status; The first information includes a second instruction, which instructs the activation of the data replication function of the target bearer. The first information includes first configuration information, wherein the transmission path status corresponding to the target bearer configured by the first configuration information satisfies a first preset condition.
14. The apparatus according to claim 13, characterized in that, The first preset condition includes at least one of the following: Any currently active transmission path is deactivated; Any N currently active transmission paths are deactivated, where N is an integer greater than 1; The number of active transmission paths is less than or equal to a first preset value; The number of transmission paths in the deactivated state is greater than or equal to the second preset value.
15. The apparatus according to claim 12, characterized in that, When the MAC entity obtains the first information, the exit module is specifically configured to: exit the target bearer's liveness state when at least one of the following conditions is met: The first information includes a first MAC CE, which indicates the target bearer's exit time-to-live status; The first information includes a second MAC CE, which indicates the deactivation of the data replication function of the target bearer; The first information includes a third MAC CE, and the transmission path status corresponding to the target bearer indicated by the third MAC CE satisfies a second preset condition.
16. The apparatus according to claim 15, characterized in that, The second preset condition includes at least one of the following: Any currently active transmission path is deactivated; Any N currently active transmission paths are deactivated, where N is an integer greater than 1; The number of active transmission paths is less than or equal to the third preset value; The number of transmission paths in the deactivated state is greater than or equal to the fourth preset value; Only one transmission path is active.
17. The apparatus according to claim 11, characterized in that, The execution module is located in the first protocol entity, which is used to perform operations related to the exiting the lifetime state of the target bearer when the target bearer exits the lifetime state.
18. The apparatus according to claim 17, characterized in that, The first protocol entity is also used for: Before performing operations related to exiting the lifetime status of the target bearer, a third indication information is received from a second protocol entity; wherein the third indication information indicates that the target bearer exits the lifetime status, and the second protocol entity is the protocol entity that obtained the first information.
19. The apparatus according to claim 11, characterized in that, The device further includes: The transmission module is configured to transmit data corresponding to the target bearer based on second configuration information when the target bearer exits the liveness time state; wherein the second configuration information is used to indicate the transmission path available after exiting the liveness time state.
20. A data transmitting end, 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 method for exiting the time-to-live state as described in any one of claims 1 to 10.
21. 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 method for exiting the time-to-live state as described in any one of claims 1 to 10.