Data transmission method and apparatus, and device and storage medium

Abstract

A data transmission method and apparatus, and a device and a storage medium, which relate to the technical field of communications. The method is executed by a terminal device. The method comprises: when a first condition is met, executing a first behavior, wherein the first behavior comprises at least one of the following: stopping or disabling or pausing a first timer, refraining from transmitting data, clearing a buffer, and clearing an HARQ process (210). By means of implementing the method, when a first condition is met, a terminal device executes a first behavior and does not transmit data anymore, such that resources can be effectively prevented from being wasted by transmitting data that does not meet the condition, thereby improving system capacity.

Description

Data transmission method, device, equipment and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a data transmission method, apparatus, device, and storage medium. Background Art

[0002] With the advancement of wireless transmission technology, people are pursuing higher speeds, latency, high-speed mobility, and energy efficiency, coupled with the increasing diversity and complexity of future services. Since data transmission must meet corresponding latency requirements, further research is needed to determine how to ensure both data transmission latency and overall system throughput during scheduling.

[0003] Summary of the Invention

[0004] The present invention provides a data transmission method, apparatus, device, and storage medium. The technical solution is as follows:

[0005] According to one aspect of an embodiment of the present application, a data transmission method is provided, the method being performed by a terminal device, the method comprising:

[0006] When the first condition is met, perform a first behavior; wherein the first behavior includes at least one of the following: stopping the first timer, not enabling the first timer, pausing the first timer, not transmitting data, clearing the buffer, and clearing the HARQ (Hybrid Automatic Repeat reQuest) process.

[0007] According to one aspect of an embodiment of the present application, a data transmission apparatus is provided, the apparatus being executed by a terminal device, the apparatus including:

[0008] A processing module is used to perform a first behavior when a first condition is met; wherein the first behavior includes at least one of the following: stopping the first timer, not enabling the first timer, pausing the first timer, not transmitting data, clearing the buffer, and clearing the HARQ process.

[0009] According to one aspect of an embodiment of the present application, a terminal device is provided, comprising a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the above-mentioned data transmission method.

[0010] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to be executed by a processor to implement the above-mentioned data transmission method.

[0011] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement the above-mentioned data transmission method.

[0012] According to one aspect of an embodiment of the present application, a computer program product is provided, which includes computer instructions stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned data transmission method.

[0013] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0014] The technical solution provided in the embodiment of the present application is that when the first condition is met, the terminal device executes the first behavior and no longer transmits data, which can effectively avoid wasting resources to transmit data that does not meet the conditions and improve system capacity. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0016] FIG2 is a flow chart of a data transmission method provided by an embodiment of the present application;

[0017] FIG3 is a block diagram of a data transmission device provided by an embodiment of the present application;

[0018] FIG4 is a schematic diagram of the structure of a terminal device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0019] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0020] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0021] Please refer to FIG1 , which shows a schematic diagram of a network architecture 100 provided by an embodiment of the present application. The network architecture 100 may include: a terminal device 10 , an access network device 20 , and a core network element 30 .

[0022] The terminal device 10 may refer to a UE (User Equipment), a STA (Station), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user apparatus. In some embodiments, the terminal device 10 may also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5GS (5th Generation System) or a terminal device in a future evolved PLMN (Public Land Mobile Network), etc., and the embodiments of the present application are not limited thereto. For ease of description, the above-mentioned devices are collectively referred to as terminal devices. The number of terminal devices 10 is generally multiple, and one or more terminal devices 10 may be distributed in each cell managed by an access network device 20. The terminal device may also be referred to as a terminal or UE for short, and those skilled in the art may understand its meaning.

[0023] The access network device 20 is a device deployed in the access network to provide wireless communication functions for the terminal device 10. The access network device 20 may include various forms of macro base stations, micro base stations, relay stations, APs (Access Points), etc. In systems using different wireless access technologies, the names of devices with access network device functions may be different. For example, in the 5G NR (New Radio) system, it is called gNodeB or gNB (Next Generation Node B). With the evolution of communication technology, the name "access network device" may change. For the convenience of description, in the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal device 10 are collectively referred to as access network devices. In some embodiments, a communication relationship can be established between the terminal device 10 and the core network network element 30 through the access network device 20. For example, in an LTE (Long Term Evolution) system, the access network device 20 may be an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or one or more eNodeBs in the EUTRAN. In a 5G NR system, the access network device 20 may be a Radio Access Network (RAN) or one or more gNBs in the RAN. In the embodiments of the present application, unless otherwise specified, the "network device" referred to refers to the access network device 20, such as a base station.

[0024] The core network element 30 is a network element deployed in the core network. The functions of the core network element 30 are mainly to provide user connection, user management, and service bearer, and to provide an interface to the external network as a bearer network. For example, the core network elements in the 5G NR system may include network elements such as the AMF (Access and Mobility Management Function) entity, the UPF (User Plane Function) entity, and the SMF (Session Management Function) entity.

[0025] In some embodiments, the access network device 20 and the core network element 30 communicate with each other via an air interface technology, such as the NG interface in the 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via an air interface technology, such as the Uu interface.

[0026] The "5G NR system" in the embodiments of the present application may also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in the embodiments of the present application may be applicable to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems (e.g., B5G (Beyond 5G) systems, 6G systems (6th Generation System, sixth generation mobile communication systems)), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems, which are not limited in this application.

[0027] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0028] Before introducing the technical solutions of this application, we first introduce and explain some of the relevant technical knowledge involved in this application. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least part of the following contents.

[0029] Currently, with people's pursuit of speed, latency, high-speed mobility, and energy efficiency, coupled with the increasing diversity and complexity of future services, the 3GPP (3rd Generation Partnership Project) international standards organization has begun developing 5G. The main application scenarios of 5G are: Enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communication (URLLC), and Massive Machine Type Communication (mMTC).

[0030] eMBB still aims to provide users with multimedia content, services, and data, and demand for this technology is growing rapidly. However, since eMBB can be deployed in diverse scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary significantly. Therefore, it cannot be generalized and requires detailed analysis based on specific deployment scenarios. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety. Typical characteristics of mMTC include high connection density, small data volumes, latency-insensitive services, low module costs, and long service life.

[0031] NR can also be deployed independently. In the 5G network environment, in order to reduce air interface signaling and quickly restore wireless connections and data services, a new RRC (Radio Resource Control) state is defined, namely RRC_INACTIVE (RRC inactive state). This state is different from RRC_IDLE (RRC idle state) and RRC_ACTIVE (RRC active state).

[0032] RRC_IDLE: Mobility is based on UE cell reselection. Paging is initiated by the CN (Core Network), and the paging area is configured by the CN. There is no UE AS (Access Stratum) context on the base station side. No RRC connection exists.

[0033] RRC_CONNECTED (RRC connected state): An RRC connection exists, and a UE AS context exists between the base station and the UE. The network knows the UE's location at the cell level. Mobility is controlled by the network. Unicast data can be transmitted between the UE and the base station.

[0034] RRC_INACTIVE: Mobility is UE-based cell selection and reselection, a CN-NR connection exists, the UE AS context exists on a certain base station, paging is triggered by the RAN, the RAN-based paging area is managed by the RAN, and the network side knows the UE location at the RAN-based paging area level.

[0035] Among the related technologies, a research project titled "eXtended Reality (XR) and cloud game (CG) evaluations for NR" has been approved. The services studied in this project include AR (Augmented Reality) / VR (Virtual Reality) / Cloud gaming, etc. A major service of XR / CG is video streaming, and its arrival rate (measured in fps, i.e., frame per second) can be 30fps, 60fps, 90fps, and 120fps. The corresponding video stream period is {33.33ms, 16.67ms, 11.11ms, 8.33ms}.

[0036] XR data features variable packet sizes with a large average. For example, for AR / VR with a 100Mbps data rate, the average uplink packet size is 20,833 bytes, the maximum is 31,250 bytes, and the minimum is 10,417 bytes. This means that the size of the packet to be transmitted in each cycle is between [10,417 bytes and 31,250 bytes]. In a real-world system with 100Mbps bandwidth, transmitting a 20,833-byte packet requires approximately four time slots of transmission resources.

[0037] Currently, 3GPP supports configuring multiple PUSCH occasions within a CG cycle for transmitting XR large data packets. Furthermore, multiple CGs can be configured to transmit XR large data packets. When the amount of data transmitted is relatively small and does not require the use of multiple pre-configured PUSCH (physical uplink shared channel) occasions, the UE can notify the base station of the unused PUSCH occasions. The base station can then reallocate the unused PUSCH occasions to other UEs for data transmission, thereby improving system efficiency.

[0038] Application-layer data exchanged between a UE and an application server or peer UE, such as in AR / VR / cloud gaming / live streaming, typically includes data streams in multiple modes, including voice, video, text, and control information. These data streams typically require synchronization, for example, so that voice, video, subtitles, and other data can be displayed synchronously to the user. Currently, video playback synchronizes multiple data streams at the application layer. This involves caching multiple received data streams, extracting corresponding data frames from the multiple data streams based on the timestamps of the playback data streams, and displaying them synchronously to the user.

[0039] In addition, since service transmission, such as XR services, has latency requirements, it is necessary to consider how to take latency into account in scheduling to ensure service transmission latency while also ensuring the overall system throughput.

[0040] Please refer to FIG2 , which shows a flow chart of a data transmission method provided by an embodiment of the present application. The method is executed by a terminal device and includes the following step 210 .

[0041] Step 210, when the first condition is met, the terminal device performs a first behavior; wherein the first behavior includes at least one of the following: stopping the first timer, not enabling the first timer, pausing the first timer, not transmitting data, clearing the buffer, and clearing the HARQ process.

[0042] In some embodiments, the first condition is related to the latency of the data. In some embodiments, the first condition is determined based on the latency of the data. In some embodiments, the first condition can be predefined or preconfigured, which is not limited in this application.

[0043] In some embodiments, the first timer is associated with data transmission. In some embodiments, the first timer is associated with data retransmission. In some embodiments, stopping or pausing the first timer prevents data transmission. In some embodiments, stopping or pausing the first timer prevents data retransmission. In some embodiments, disabling the first timer prevents data transmission. In some embodiments, disabling the first timer prevents data retransmission.

[0044] In some embodiments, if a paused first timer is restarted, it may be run based on the configured duration of the first timer or based on the paused state of the first timer, which is not limited in this application. In some embodiments, the paused state of the first timer refers to the remaining duration of the first timer when the first timer is paused. For example, if the configured duration of the first timer is 10s, and the first timer is paused at 4s, if the first timer is restarted, it may be run based on the configured duration of 10s of the first timer or based on the remaining duration of 6s of the first timer.

[0045] In some embodiments, not transmitting data may mean deleting the data, or may mean not deleting the data but not transmitting the data either, which is not limited in this application. In some embodiments, clearing the buffer means clearing the data stored by the terminal device. For example, clearing the HARQ buffer means clearing the HARQ process used to transmit data. In some embodiments, the terminal device performing any one or more of the first behaviors will cause the terminal device to no longer transmit data.

[0046] In some embodiments, the data may be a MAC PDU (Media Access Control Protocol Data Unit), a MAC sub-PDU, an SDU (Service Data Unit), a packet, or other forms, which is not limited in this application.

[0047] In some embodiments, the first timer includes at least one of the following: CGT (Configured Grant Timer), CGRT (Configured Grant Retransmission Timer), HARQ RTT (Round-Trip Time) timer, and HARQ retransmission timer.

[0048] In some embodiments, the HARQ RTT timer includes a UL (UpLink) HARQ RTT timer and / or a DL (DownLink) HARQ RTT timer.

[0049] In some embodiments, the HARQ retransmission timer includes a UL HARQ retransmission timer and / or a DL HARQ retransmission timer.

[0050] In some embodiments, the CGT is used to protect the HARQ buffer from being overwritten by new data. If the CGT is not running at the time of the configuration grant, the new data indication is switched and the HARQ buffer is overwritten by the new data. The CGT is started when an uplink grant addressed to the Cell-Radio Network Temporary Identifier (C-RNTI) or the configured scheduling RNTI (CS-RNTI) is received for a HARQ process configured for the configuration grant, or when an uplink transmission is performed for a HARQ process configured for the configuration grant. The CGT is stopped when the second type of configuration grant is activated to enable the HARQ buffer to be updated before the new configuration is applied.

[0051] In some embodiments, CGRT is used to trigger autonomous retransmission using the configured grant. When the timer expires, the UE will assume that a negative acknowledgment has been received for the corresponding HARQ process and start retransmission on the next available configured grant opportunity. The timer is started when a transport block is transmitted on a configured grant and the new timer is stopped when HARQ feedback (e.g., DFI (Downlink Feedback Information)) or a dynamic grant for the HARQ process is received. The traditional configured grant timer and behavior are retained to prevent the configured grant from overwriting the transport blocks scheduled by the dynamic grant, i.e., for the HARQ process configured for the configured grant, it is started when a PDCCH (Physical Downlink Control Channel) for an uplink grant addressed to the cell radio network temporary identifier or the configured scheduling-RNTI is received and when a transmission on the dynamically granted PUSCH is received. However, since CGT and CGRT can coexist, the interaction and behavior between these two timers needs to be specified.

[0052] In some embodiments, the HARQ RTT timer indicates the shortest duration before the MAC entity expects a DL allocation of a HARQ retransmission, which is used for UE energy saving and defines the minimum retransmission start time.

[0053] In some embodiments, for each DL HARQ process, excluding the broadcast process, the HARQ retransmission timer indicates the maximum duration before receiving a DL retransmission. For each UL HARQ process, the HARQ retransmission timer indicates the maximum duration before receiving an UL retransmission grant. In some embodiments, the HARQ retransmission timer is used by the UE to monitor retransmission scheduling and perform PDCCH monitoring.

[0054] In some embodiments, the first condition is determined based on at least one of the following: a first duration, a second timer, first information, data transmission status, and data delay, wherein the second timer is used to control the data transmission time or the data storage time; the first information is used to configure or indicate whether the terminal device is allowed to perform the first behavior.

[0055] In some embodiments, when the first condition is determined based on a first duration or a first timer, the first condition is that the first duration has been exceeded, or that the second timer has timed out, is not running, or is stopped. In some embodiments, the duration of the second timer is the first duration. In some embodiments, the first duration is represented by the first timer.

[0056] In some embodiments, when the first condition is determined based on the first information, the method further includes the following step 220.

[0057] Step 220: The terminal device receives the first information sent by the network device.

[0058] Correspondingly, the network device sends the first information to the terminal device.

[0059] In some embodiments, the first information is configured or indicated by the network device to the terminal device.

[0060] In some embodiments, the data transmission situation includes at least one of the following: the data or PDU or SDU reports DSR (Delay Status Report) information, the DSR information includes data or PDU or SDU, the MAC PDU has been packaged, the data or PDU or SDU is packaged or sent, the MAC PDU includes data or PDU or SDU that meets the delay condition or situation, and the data or PDU or SDU included in the MAC PDU are all data or SDUs that meet the delay condition or situation.

[0061] In some embodiments, when the first condition is determined based on the latency of the data, the first condition is that the latency of the data is less than or equal to a first threshold; or, the first condition is that the data has a specific latency requirement.

[0062] In some embodiments, after the terminal device executes the first action, it no longer sends data. At this time, if the network device has received the data, it can inform the terminal device that the data has been successfully received. The method can also include the following step 230.

[0063] Step 230: The terminal device receives second information sent by the network device, where the second information is used to indicate that the network device has successfully received the data.

[0064] Accordingly, the network device sends the second information to the terminal device.

[0065] In some embodiments, the first information may be feedback information for a MAC PDU, feedback information for a HARQ process, feedback information for data, or feedback information for a PUSCH. For example, the first information may be feedback information for an RLC SDU / PDU, or feedback information for a PDCP PDU / SDU.

[0066] In some embodiments, the first information may be ACK (Acknowledge Character) information.

[0067] In some embodiments, the first information may be NACK information, or rescheduling information, or DFI (Downlink Feedback Indication) information.

[0068] In some embodiments, the first information may be carried through a status report, or may be carried through HARQ ACK / NACK, or may be carried through PDCCH, or may be carried through DFI, which is not limited in this application.

[0069] In some embodiments, if the network device fails to receive the data, the terminal device may be instructed to retransmit the data to ensure that the network device can successfully obtain the data. The method may further include the following step 240.

[0070] Step 240: The terminal device receives third information sent by the network device, where the third information is used to instruct the terminal device to retransmit data.

[0071] Accordingly, the network device sends the third information to the terminal device.

[0072] In some embodiments, the terminal device retransmits the data after receiving the third information.

[0073] In some embodiments, the third information may be rescheduling information for a MAC PDU, feedback information for a HARQ process, feedback information for data, or rescheduling information for a PUSCH. For example, the third information may be feedback information for an RLC SDU / PDU, or feedback information for a PDCP PDU / SDU.

[0074] Through the above steps 230 or 240, the terminal device can know whether the network device has received the data. In the case that the network device has not received the data, the terminal device can also retransmit the data to ensure data transmission.

[0075] The technical solution provided in the embodiment of the present application is that when the first condition is met, the terminal device executes the first behavior and no longer transmits data, which can effectively avoid wasting resources to transmit data that does not meet the conditions and improve system capacity.

[0076] The embodiments of this application provide exemplary explanations for several situations of the first condition.

[0077] 1. Determine a first condition based on a first duration or a first timer

[0078] In some embodiments, the first duration or the second timer may be configured for a terminal device or for an object used to transmit data, and this application does not limit this.

[0079] In some embodiments, the first duration or the second timer is configured for at least one of the following objects: DRB (Data Radio Bearer), terminal equipment, HARQ process, CG (Configured Grant), DG (Dynamic Grant), LCH (Logical Channel), LCG (Logic Channel Group), and MAC entity.

[0080] In some embodiments, the first duration or the second timer may be maintained for a terminal device or for an object used to transmit data, and this application does not limit this.

[0081] In some embodiments, the maintenance of the first duration or the second timer can be understood as the actual application of the first duration or the second timer. In some embodiments, the granularity of configuration and maintenance can be the same or different, and this application does not limit this.

[0082] In some embodiments, the first duration or the second timer is maintained for at least one of the following objects: DRB, terminal device, HARQ process, CG, DG, LCH, LCG, MAC entity, MAC PDU, triggered or pending DSR, DSR MAC CE (MAC Control Element, MAC control unit).

[0083] In some embodiments, the object that configures the first duration or the second timer and the object that maintains the first duration or the second timer may be the same or different, and this application does not limit this. Exemplarily, the first duration or the second timer is configured for a terminal device, and the first duration or the second timer is maintained for the terminal device. Exemplarily, the first duration or the second timer is configured for a terminal device, and the first duration or the second timer is maintained for a HARQ process.

[0084] In some embodiments, the first duration or second timer configured for different objects may be the same or different, and this application does not limit this. For example, the first duration configured for a DRB is 5 seconds, and the first duration configured for a HARQ process is 8 seconds. For example, the first durations configured for both the DRB and the HARQ process are 5 seconds.

[0085] In some embodiments, if a first duration or a second timer is configured for an object, the first duration or the second timer may be maintained for the object. For example, if the first duration or the second timer is configured for a terminal device, the first duration or the second timer may be maintained for the terminal device.

[0086] In some embodiments, if a certain object is not configured with the first duration or the second timer, the first duration or the second timer is not maintained for the object. Exemplarily, if the first duration or the second timer is not configured for a terminal device, the first duration or the second timer is not maintained for the terminal device.

[0087] In some embodiments, if an object is configured with a first duration or a second timer, then when maintaining the first duration or the second timer for different objects, the first duration or the second timer configured for the object may be used. Exemplarily, the first duration or the second timer is configured for a terminal device, and when maintaining the first duration or the second timer for a HARQ process, the first duration or the second timer configured for the terminal device may also be used.

[0088] In some embodiments, if there are multiple objects configured with the first duration or the second timer, if an object is configured with the first duration or the second timer, the first duration or the second timer can be maintained for the object; if an object is not configured with the first duration or the second timer, the first duration or the second timer is not maintained for the object.

[0089] In some embodiments, if there are multiple objects configured with the first duration or the second timer, if a certain object is configured with the first duration or the second timer, the first duration or the second timer can be maintained for the object; if a certain object is not configured with the first duration or the second timer, the first duration or the second timer configured for other objects can be used for maintenance.

[0090] In some embodiments, if a first duration or second timer is not configured for an object, the first duration or second timer configured for any object may be used for maintenance. In some embodiments, if a first duration or second timer is not configured for an object, the first duration or second timer configured for an object associated with the object may be used for configuration. In some embodiments, the association may be predefined or preconfigured, and this application does not limit this.

[0091] The above method provides a method for determining the maintenance object of the first duration or the second timer based on the configuration object of the first duration or the second timer in actual applications.

[0092] In some embodiments, the first duration is related to the length or running status of a PDCP (Packet Data Convergence Protocol) discard timer.

[0093] It should be noted that the timer lengths mentioned in the embodiments of this application refer to the duration of the timer. For example, the length of the PDCP discard timer refers to the duration of the PDCP discard timer. It should be understood that if similar descriptions appear in subsequent embodiments, the same understanding should be maintained here, and this application will not elaborate on them one by one.

[0094] In some embodiments, if a PDCP PDU has no chance of being scheduled after being generated, then after the PDCP discard timer expires, the PDCP PDU and the corresponding PDCP SDU will be discarded.

[0095] In some embodiments, the first duration is less than or equal to a length of a PDCP discard timer.

[0096] In some embodiments, the first duration may be related to the configured length of the PDCP discard timer, or may be related to the remaining length of the PDCP discard timer.

[0097] In some embodiments, the first duration is less than or equal to a configured length of the PDCP discard timer.

[0098] In some embodiments, the first duration is less than or equal to a remaining length of a PDCP discard timer.

[0099] In some embodiments, the first duration is related to a PDB (Packet Delay Budget) and / or a PSDB (PDU Set Delay Budget).

[0100] In some embodiments, the PDB includes AN-PDB (Access Network-PDB), which is used to indicate the PDB of the access network, or the upper limit of the time during which packet transmission of the access network is delayed.

[0101] In some embodiments, the PDB defines an upper limit on the time that a packet can be delayed between the UE and the UPF terminating the N6 interface.

[0102] In some embodiments, an application may have certain latency requirements for a PDU set that do not adequately translate into a packet latency budget requirement. For example, if the PSDB is 10ms, then the PDB can be set to 10ms only if all packets of the PDU set arrive at the 5G system at the same time. If the packets are spread out, the PSDB is measured based on the arrival of the first packet of the PDU set or the last packet of the PDU set. In either case, a given PSDB will result in different PDB requirements for different packets of the PDU set. It has been observed that specifying the PSDB to the 5G system may be beneficial. Therefore, it is useful to send new 5G QoS (Quality of Service) identifier attributes (latency budget, error rate, etc.) based on the PDU set on the control plane. On the user plane, application servers can mark IP (Internet Protocol) packets to distinguish packets belonging to the same set and / or burst.

[0103] In some embodiments, the first duration is less than or equal to the length of the PDB.

[0104] In some embodiments, the first duration is less than or equal to the length of the PSDB.

[0105] In some embodiments, the starting time of the first duration or the second timer is one of the following times: the time when data arrives at the AS layer of the terminal device, the time when data arrives at PDCP, the time when PDCP receives data, the start time of the PDCP discard timer, the triggering time of DSR, the time when DSR MAC CE is generated, the time when MAC PDU containing data is generated, the time when MAC PDU containing data is transmitted, the time when authorization containing data is transmitted, the time when authorization corresponding to data is transmitted, the time when MAC PDU containing DSR MAC CE is generated, the time when MAC PDU containing DSR MAC CE is transmitted, the time when a data packet or authorization containing DSR MAC CE is transmitted, and the time when a data packet or authorization containing DSR MAC CE is sent.

[0106] It should be noted that the "data to xxx" time mentioned in the embodiments of this application refers to the time when the data arrives at xxx. For example, the "data to the AS layer time" of the terminal device refers to the time when the data arrives at the AS layer of the terminal device; the "data to PDCP time" refers to the time when the data arrives at the PDCP. It should be understood that if similar descriptions appear in subsequent embodiments, the same understanding should be maintained here, and this application will not elaborate on them one by one.

[0107] Regarding the above content, the embodiment of the present application is exemplified by taking the example of the terminal device stopping or pausing or not enabling the second timer when the first condition is met.

[0108] In some embodiments, the network device is configured with a second timer. When the PDCP receives data, the terminal device starts the second timer. When the second timer expires, the terminal device stops, suspends, or disables the CGT and / or CGRT. The CGT and / or CGRT that is stopped, suspended, or disabled is maintained for a UL grant that includes the data.

[0109] In some embodiments, the network device is configured with a second timer. When the PDCP receives data, the terminal device starts the second timer. When the second timer times out, the terminal device stops, suspends, or disables the HARQ RTT timer. The stopped, suspended, or disabled HARQ RTT timer is maintained for a HARQ process that includes the data.

[0110] In some embodiments, the network device is configured with a second timer, and the terminal device starts the second timer when reporting a MAC PDU or UL grant transmission. When the second timer expires, the terminal device stops, suspends, or disables the CGT and / or CGRT. The CGT and / or CGRT that is stopped, suspended, or disabled is maintained for the UL grant.

[0111] In some embodiments, the network device is configured with a second timer, and the terminal device starts the second timer when reporting a MAC PDU or UL grant transmission. When the second timer expires, the terminal device stops, suspends, or disables the HARQ RTT timer. The stopped, suspended, or disabled HARQ RTT timer is maintained for the HARQ process of the MAC PDU or UL grant.

[0112] In some embodiments, for a paused timer, when it is restarted, the timer is run according to the initial value of the timer, or the timer continues to run according to the value when the timer was paused.

[0113] Through the above method, the first condition is determined based on the first duration or the second timer. When the first condition is met, the terminal device does not transmit data, which can avoid wasting resources to transmit data whose transmission delay no longer meets the conditions and improve system capacity.

[0114] 2. Determine the first condition based on the first information

[0115] In some embodiments, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior. In some embodiments, the first information is used to configure a first behavior among multiple behaviors. In some embodiments, the multiple behaviors include stopping, not enabling, or pausing the first timer, not transmitting data, clearing a buffer, and clearing a HARQ process.

[0116] In some embodiments, the first information may be configured or indicated in an explicit indication manner to configure or indicate whether the terminal device is allowed or enabled to perform the first behavior, or may be configured or indicated in an implicit indication manner to configure or indicate whether the terminal device is allowed or enabled to perform the first behavior, which is not limited in this application. For example, if the terminal device receives the first information, it is considered that the terminal device is allowed to perform the first behavior. For example, the first information includes a first information field, and the first information field is used to configure or indicate whether the terminal device is allowed or enabled to perform the first behavior. For example, the value of the first information field is a first numerical value, indicating that the terminal device is allowed to perform the first behavior; the value of the first information field is a second numerical value, indicating that the terminal device is not allowed to perform the first behavior. For example, the value of the first information field is 1, indicating that the terminal device is allowed to perform the first behavior, and the value of the first information field is 0, indicating that the terminal device is not allowed to perform the first behavior. In some embodiments, the first information field may be represented by 1 bit or by multiple bits, which is not limited in this application.

[0117] In some embodiments, if the terminal device has the capability to perform the first behavior, the first condition is determined based on the first information. For example, if the terminal device has the capability to perform the first behavior, the first condition is determined based on the first information if the terminal device receives the first information. For example, if the terminal device does not have the capability to perform the first behavior, even if the terminal device receives the first information, there is no need to determine the first condition.

[0118] In some embodiments, when the terminal device does not have the ability to perform the first behavior, the first condition may also be determined based on the first information. For example, when the terminal device does not have the ability to perform the first behavior, if the terminal device receives the first information, the first condition is determined based on the first information.

[0119] In some embodiments, the first information is used to configure or instruct a first object to perform a first behavior.

[0120] In some embodiments, the first information is used to configure or indicate whether the terminal device is allowed or enabled to perform the first behavior.

[0121] In some embodiments, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior on the first object.

[0122] In some embodiments, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior within the first time period.

[0123] In some embodiments, the first information is used to configure or indicate whether to allow or enable the terminal device to perform a first behavior on the first object within a first time period.

[0124] In some embodiments, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior at the first moment.

[0125] In some embodiments, the first information is used to configure or indicate whether to allow or enable the terminal device to perform a first behavior on the first object at a first moment.

[0126] In some embodiments, the first object includes at least one of the following: DRB, terminal device, HARQ process, CG, DG, LCH, LCG, MAC PDU, triggered DSR, pending DSR, DSR MAC CE.

[0127] In some embodiments, the first time period may be a time period during which the terminal device transmits data. For example, the first time period may be a time period during which a HARQ process including data is transmitted. For example, the first time period may be a time period during which a grant including data is transmitted.

[0128] In some embodiments, the first time period may be a time period configured by the first information.

[0129] In some embodiments, the first information is further used to configure or indicate at least one of the following: the duration of the first time period, the start time of the first time period, and the end time of the first time period.

[0130] In some embodiments, if the first information does not indicate the first time period or the first time, the terminal device performs the first behavior when receiving the first information.

[0131] In some embodiments, the first information may be dynamically configured or statically configured, which is not limited in this application.

[0132] In some embodiments, the first condition is determined based on the first information and / or the first duration (second timer). Exemplarily, the first information is used to configure or indicate that the terminal device is allowed to perform the first behavior, and the terminal device performs the first behavior based on the first duration. For example, when the terminal device receives the first information, it performs the first behavior when the first duration (second timer) times out. In this case, the starting time of the first duration (second timer) can be configured by the network device or the time when the first information is received, and this application does not limit this. Exemplarily, the network device sends first configuration information to the terminal device, and the first configuration information is used to configure the first duration (second timer).

[0133] Through the above method, the first information is used to indicate or configure whether to allow or enable the terminal device to perform the first behavior, so that the terminal device can avoid wasting resources to transmit data whose delay no longer meets the conditions, thereby improving system capacity.

[0134] 3. Determine the first condition based on data transmission conditions

[0135] In some embodiments, the data transmission situation includes at least one of the following: the data or PDU or SDU reports DSR information, the DSR information includes data or PDU or SDU, the MAC PDU has been packaged, at least part of the data or PDU or SDU has been transmitted, the data or PDU or SDU has not been deleted, the data or PDU or SDU has been packaged or sent, the MAC PDU includes data or PDU or SDU that meets the delay condition, and the data or PDU or SDU included in the MAC PDU are all data or SDU that meet the delay condition.

[0136] In some embodiments, the delay situation may also be referred to as a delay condition or a delay state, which is not limited in this application.

[0137] In some embodiments, the first condition is determined based on a data transmission situation and a first duration (a first timer). Exemplarily, when the above data transmission situation exists, if the first duration (the first timer) times out, the first action is executed.

[0138] Regarding the above content, the embodiment of the present application is exemplified by taking the example of the terminal device stopping or pausing or not enabling the second timer when the first condition is met.

[0139] In some embodiments, the data reports DSR information, or the DSR information includes data, and the MAC PDU carrying the data is not allowed to be retransmitted. Furthermore, the terminal device stops or suspends or does not enable the relevant second timer.

[0140] In some embodiments, if the information of the data carried in the MAC PDU is reported in the DSR MAC CE, the HARQ RTT timer of the HARQ for the MAC PDU is stopped, suspended or not enabled.

[0141] In some embodiments, if the information of the data carried in the MAC PDU is reported in the DSR MAC CE, the CGT and / or CGRT for the MAC PDU is stopped, suspended or not enabled.

[0142] In some embodiments, if the data carried in the MAC PDU has information reported in the DSR MAC CE and the second timer times out, the HARQ RTT timer for the HARQ of the MAC PDU is stopped or suspended or not enabled.

[0143] In some embodiments, if the data carried in the MAC PDU has information reported in the DSR MAC CE and the second timer expires, the CGT and / or CGRT for the MAC PDU is stopped or suspended or not enabled.

[0144] In some embodiments, if the data is carried in the MAC PDU and the second timer expires, the HARQ RTT timer for the HARQ of the MAC PDU is stopped or suspended or not enabled.

[0145] In some embodiments, if the data is carried in the MAC PDU and the second timer expires, the CGT and / or CGRT of the HARQ for the MAC PDU is stopped or suspended or not enabled.

[0146] In some embodiments, if the data is carried in the MAC PDU and the data meets the delay condition (for example, the remaining time is less than or equal to the Xth threshold, or the data is service data with delay-sensitive requirements, or the HARQ process or the LCH where the data is located is indicated as being able to execute the first behavior, etc.), the HARQ RTT timer for the HARQ of the MAC PDU is stopped or suspended or not enabled.

[0147] In some embodiments, if the data is carried in the MAC PDU and the data meets the delay condition (for example, the remaining time is less than or equal to the Xth threshold, or the data is service data with delay-sensitive requirements, or the HARQ process or the LCH where the data is located is indicated as being able to execute the first behavior, etc.), the CGT and / or CGRT of the HARQ for the MAC PDU is stopped or suspended or not enabled.

[0148] In some embodiments, the network device configures a second timer, and when the terminal device reports a DSR MAC CE or sends a MAC PDU with a DSR MAC CE, the second timer is started. When the second timer times out, the terminal device stops or suspends or does not enable the CGT and / or CGRT. The CGT and / or CGRT that is stopped, suspended or not enabled is maintained for UL grant, and the UL grant carries data involved in or reported information in the DSR, or the UL grant carries data involved in or reported information in the DSR.

[0149] In some embodiments, the network device configures a second timer, and when the terminal device reports a DSR MAC CE or sends a MAC PDU with a DSR MAC CE, the second timer is started. When the second timer times out, the terminal device stops, suspends, or disables the HARQ RTT timer. The stopped, suspended, or disabled HARQ RTT timer is maintained for a HARQ process that carries data involved in or reported information in the DSR, or the data carried in the UL grant are all involved in or reported information in the DSR.

[0150] Through the above method, the first condition is determined by the data transmission situation. When the first condition is met, the terminal device executes the first behavior and no longer transmits data. This can effectively avoid wasting resources to transmit data that does not meet the conditions and improve system capacity.

[0151] 4. Determine the first condition based on data latency

[0152] In some embodiments, the first condition is that the delay of the data is less than or equal to a first threshold.

[0153] In some embodiments, the first threshold is configured by a network device. Exemplarily, the network device sends second configuration information to the terminal device, where the second configuration information is used to configure the first threshold.

[0154] In some embodiments, the first threshold is less than a triggering threshold of the DSR MAC CE.

[0155] In some embodiments, the first threshold may also be determined by the terminal device based on its own implementation. For example, the terminal device determines a first threshold that is smaller than a triggering threshold of the DSR MAC CE based on its own implementation.

[0156] In some embodiments, the first threshold is configured for at least one of the following objects: DRB, terminal device, HARQ process, CG, DG, LCH, LCG, MAC entity.

[0157] In some embodiments, the first condition is that the data has a specific latency requirement.

[0158] In some embodiments, the delay is a residual delay. In some embodiments, the residual delay refers to the remaining time length of the delay preconfigured for the data.

[0159] In some embodiments, the delay is a delay determined based on a PDCP discard timer.

[0160] In some embodiments, the delay is determined based on the configured duration or the remaining duration of the PDCP discard timer, which is not limited in this application. In some embodiments, the delay is determined based on the configured duration of the PDCP discard timer. In some embodiments, the delay is determined based on the remaining duration of the PDCP discard timer.

[0161] In some embodiments, the delay may be a delay inferred based on a PDCP discard timer.

[0162] In some embodiments, the delay is a delay determined based on the PDB or PSDB.

[0163] In some embodiments, the latency is the remaining time required for data to reach the PDB or PSDB.

[0164] In some embodiments, the first condition is determined based on the data's latency and a first duration (a second timer). Exemplarily, the first condition is that the data's latency is less than or equal to a first threshold and exceeds the first duration. Exemplarily, the first condition is that the data has a specific latency requirement and the second timer has expired.

[0165] In some embodiments, the first condition is determined based on the data delay and the data transmission condition. For example, the first condition is that the data delay is less than or equal to a first threshold and the terminal device reports DSR information for the data.

[0166] Regarding the above content, the embodiment of the present application is exemplified by taking the example of the terminal device stopping or pausing or not enabling the second timer when the first condition is met.

[0167] In some embodiments, the network device configures a first threshold. If the remaining delay of the data is less than the first threshold, the terminal device stops, suspends, or disables CGT and / or CGRT. The stopped, suspended, or disabled CGT and / or CGRT is maintained for an UL grant that includes the data.

[0168] In some embodiments, the network device configures a first threshold, and if the remaining delay of the data is less than the first threshold, the terminal device stops, suspends, or disables the HARQ RTT timer. The stopped, suspended, or disabled HARQ RTT timer is maintained for the HARQ process that includes the data.

[0169] In some embodiments, the network device configures a first threshold. If the remaining delay of the data is less than the first threshold and the terminal device reports DSR information for the data, the terminal device stops, suspends, or disables CGT and / or CGRT. The stopped, suspended, or disabled CGT and / or CGRT is maintained for an UL grant that includes the data.

[0170] In some embodiments, the network device configures a first threshold. If the remaining delay of the data is less than the first threshold and the terminal device reports DSR information for the data, the terminal device stops, suspends, or disables the HARQ RTT timer. The stopped, suspended, or disabled HARQ RTT timer is maintained for the HARQ process that includes the data.

[0171] In some embodiments, in the case of MAC PDU packetization, if the delay of the data it carries is less than a first threshold value, CGT and / or CGRT is stopped or suspended or not enabled.

[0172] In some embodiments, if the delay of the data carried in the MAC PDU is less than a first threshold, the HARQ RTT timer for the MAC PDU is stopped, suspended, or disabled.

[0173] Through the above method, the first condition is determined by the data delay. When the first condition is met, the terminal device executes the first behavior and no longer transmits data. This can effectively avoid wasting resources to transmit data that does not meet the conditions and improve system capacity.

[0174] For the methods described in the above embodiments, this application also supplements the terms or schemes that may be involved in the above embodiments. It should be noted that the following content can be used as a separate method or combined with the methods in the above embodiments. The combined method should also fall within the scope of protection of the embodiments of this application.

[0175] 1. First, explain the data or SDU related to DSR

[0176] In some embodiments, the data or SDU related to the DSR may exist in the following two ways.

[0177] Mode 1: An SDU is considered to be associated with a DSR if it is associated with the LCG which triggered the DSR and if it is associated as Delay-critical UL data as defined in TS 38.323 and TS 38.322.

[0178] Mode 2: An SDU is considered to be associated with a DSR if it is associated with the LCG which triggered the DSR and if it is associated with a PDU set in which at least one PDCP SDU has the remaining value of its PDCP discardTimer below remainingTimeThreshold (If the SDU is associated with the LCG that triggers the DSR and it is associated with a PDU set, in which at least one PDCP SDU has the remaining value of its PDCP discard timer below the remaining time threshold, then the SDU is considered to be associated with the DSR).

[0179] 2. In the case of SFN (System Frame Number) periodic changes, how to set DRX or DRX_SFN_COUNTER (counter) or NSFN in the DRX formula when the terminal device receives a DRX configuration with a reference SFN indication of 512 within the SFN value range of 0-512?

[0180] In some embodiments, if the received reference SFN indication is 512 when the SFN is between 0 and 512, the SFN is initialized to obtain the NSFN, and the NSFN is incremented by 1.

[0181] Illustratively, I increment NSFN by 1 after the NSFN initialization operation, if the DRX configuration with "drx-ReferenceSFN=512" is received during the first half of a hyper frame (ie, SFN is between 0 and 512).

[0182] In some embodiments, when a DRX non-integer long cycle start offset is configured, if RRC reconfigures DRX, DRX_SFN_COUNTER is set to 0 in the first symbol of the time slot after the RRC reconfiguration is successfully completed; if DRX reconfiguration information with a reference SFN indication of 512 is received when the SFN is between 0-512, DRX_SFN_COUNTER is incremented by 1.

[0183] In some embodiments, the configuration method of DRX_SFN_COUNTER or NSFN is as follows:

[0184] 1>if the drx-NonIntegerLongCycleStartOffset is configured (if drx-NonIntegerLongCycleStartOffset is configured):

[0185] 2>if DRX is (re-)configured by RRC (if RRC (re)configure DRX):

[0186] 3>set DRX_SFN_COUNTER to 0 in the first symbol of the slot immediately after the successful completion of the RRC(re-)configuration (after successful completion of RRC(re)configuration, immediately set DRX_SFN_COUNTER to 0 in the first symbol of the time slot);

[0187] 3>increment DRX_SFN_COUNTER by 1 if the DRX(re)-configraution containing drx-TimeReferenceSFN equals 512 is received between SFN 0 and SFN 512 (if a DRX(re)-configuration containing drx-TimeReferenceSFN equals 512 is received between SFN 0 and SFN 512, DRX_SFN_COUNTER is incremented by 1).

[0188] 2>increment DRX_SFN_COUNTER by 1 in the first symbol of a slot in which SFN changes to 0 (in the first symbol of the time slot where SFN changes to 0, DRX_SFN_COUNTER increases by 1).

[0189] In some embodiments, when a DRX non-integer long cycle start offset is configured, if RRC reconfigures DRX, DRX_SFN_COUNTER is set to 0 in the first symbol of the time slot after the RRC reconfiguration is successfully completed; in the first symbol of the time slot where the SFN is changed to 0, DRX_SFN_COUNTER is incremented by 1.

[0190] In some embodiments, the configuration method of DRX_SFN_COUNTER or NSFN is as follows:

[0191] 1>if the drx-NonIntegerLongCycleStartOffset is configured (if drx-NonIntegerLongCycleStartOffset is configured):

[0192] 2>if DRX is (re-)configured by RRC (if RRC (re)configure DRX):

[0193] 3>set DRX_SFN_COUNTER to 0 in the first symbol of the slot immediately after the successful completion of the RRC(re-)configuration (after successful completion of RRC(re)configuration, immediately set DRX_SFN_COUNTER to 0 in the first symbol of the time slot);

[0194] 2>increment DRX_SFN_COUNTER by 1 in the first symbol of a slot in which SFN changes to 0 (in the first symbol of the time slot where SFN changes to 0, DRX_SFN_COUNTER increases by 1).

[0195] The above method provides a method for the terminal device to set DRX_SFN_COUNTER or NSFN when the SFN cycle changes, thereby avoiding errors in the terminal device when changing the SFN cycle.

[0196] 3. When DSR triggers SR (Status Report)

[0197] In some embodiments, for the case where DSR triggers SR, an SR transmission delay mechanism may be introduced or may not be introduced.

[0198] Method 1: For SRs triggered by DSRs, no SR transmission delay mechanism is introduced. In some embodiments, the SR corresponding to the DSR is triggered without waiting for the delay timer to expire. In other words, the SR corresponding to the DSR can be triggered without waiting for the delay timer to expire.

[0199] Method 2: For SRs triggered by DSRs, an SR transmission delay mechanism is introduced. This means that the SR corresponding to the DSR is triggered only when the delay timer expires.

[0200] In some embodiments, the delay timer is a dedicated timer for DSR, or the delay timer is the same as the delay timer for SR triggered by BSR. In some embodiments, if the delay timer is a dedicated timer for DSR, the delay timer is included in the DSR configuration. Exemplarily, the delay timer is included in LCG-DSR-Config.

[0201] In some embodiments, the delay timer is configured when logicalChannelSR-DelayTimerApplied is set or present, or when logicalChannelSR-DelayTimerApplied is set to a first value. In some embodiments, the first value is true, indicating that the delay timer can be configured.

[0202] In some embodiments, when logicalChannelSR-DelayTimerApplied is set to the first value and DSR is triggered, the delay timer is started. In some embodiments, when logicalChannelSR-DelayTimerApplied is set to the first value and DSR is triggered, if the delay timer for the same LCH has not been started (or the delay timer for the same LCH has not been allowed), the delay timer is started (or the delay timer for the LCH).

[0203] In some embodiments, when a DSR is triggered and its delay timer is not running, an SR is triggered. In some embodiments, when a DSR is triggered and its delay timer is not running, and if there is no available UL-SCH (Uplink Shared Channel) to carry the new transmission, an SR is triggered.

[0204] In some embodiments, when a DSR is triggered and its delay timer for an LCH is not running, an SR for this LCH is triggered. In some embodiments, when a DSR is triggered and its delay timer for an LCH is not running, and if there is no available UL-SCH to carry the new transmission, an SR for this LCH is triggered.

[0205] In some embodiments, if DSR is triggered and logicalChannelSR-Mask is set to a second value, SR may be triggered. In some embodiments, the second value is false.

[0206] In some embodiments, if DSR is triggered, the MAC entity is configured with CG and / or logicalChannelSR-Mask is set to the second value, and in combination with the delay timer, SR may be triggered. Exemplarily, if DSR is triggered, the MAC entity is configured with CG and / or logicalChannelSR-Mask is set to false, and the delay timer times out, SR may be triggered. Exemplarily, if DSR is triggered, the MAC entity is configured with CG and / or the logicalChannelSR-Mask of the LCH is set to false, and the delay timer of the LCH times out, SR of the LCH may be triggered.

[0207] The above method provides a method for triggering the SR corresponding to the DSR, ensuring that the SR can be triggered normally.

[0208] 4. Trigger an emergency call in case of cell DRX (cell discontinuous reception)

[0209] In some embodiments, if the terminal device is not allowed to transmit uplink authorization on any serving cell based on the cell DRX mechanism, the terminal device triggers an emergency call on an SPCell (Special Cell). In some embodiments, the SPCell includes a PCell (Primary Cell) and a PSCell (Primary Secondary Cell). In some embodiments, the terminal device triggers a RACH (Random Access Channel) on the SPCell to make an emergency call.

[0210] In some embodiments, UE triggers RACH on the SpCell for an emergency call if no serving cell configured for the UE has the uplink grant that is allowed to transmitted based on the cell DRX mechanism.

[0211] In some embodiments, the UE triggers RACH on the SpCell for an emergency call if no available uplink grant transmission is allowed on any serving cell of the UE based on the cell DRX mechanism.

[0212] In some embodiments, if the cell DRX is activated and the serving cell is not in an active cycle (or the serving cell is in a dormant cycle), the terminal device performs at least one of the following steps.

[0213] 1>if cell DRX is activated and the Serving Cell is not in the cell DRX Active Period (if cell DRX is activated and the serving cell is not in the cell DRX active period):

[0214] 2>not instruct the physical layer to signal a SR on a PUCCH resource for SR (not just the physical layer sends an SR signal to the SR on the PUCCH resource);

[0215] 2>not increment the SR_COUNTER for a SR (do not increase the SR_COUNTER of SR);

[0216] 2>not start the sr-ProhibitTimer for a SR (do not start the sr-ProhibitTimer for SR);

[0217] 2> not deliver any configured uplink grant and the associated HARQ information to the HARQ entity (not providing any configured uplink grant and related HARQ information to the HARQ entity);

[0218] 2>not instruct a HARQ process associated with a configured uplink grant to trigger a new transmission or a retransmission (do not instruct the HARQ process associated with the configured uplink grant to trigger a new transmission or a retransmission);

[0219] 2>not report periodic CSI on PUCCH and semi-persistent CSI configured on PUSCH (do not report periodic CSI on PUCCH and semi-persistent CSI configured on PUSCH);

[0220] 2>if an emergency service is initiated by upper layers and this Serving Cell is the SpCell (if the emergency service is initiated by the upper layer and the service unit is SpCell); and

[0221] 2>if there is no available UL-SCH resource on any other serving cell,if any,on which cell DRX is deconfigured,or deactivated,or in the Active Period (if there is no available UL-SCH resource on any other serving cell (if any), or in the active period):

[0222] 3>initiate a Random Access procedure.

[0223] Through the above method, when the terminal device is in the DRX sleep cycle, it can also make an emergency call, thereby avoiding affecting the services of the terminal device and ensuring the stability of the communication services.

[0224] It should be noted that the first behavior includes at least one of the following: stopping, disabling, or pausing the first timer, not transmitting data, clearing the buffer, or clearing the HARQ process. The above embodiment is merely illustrative of the first behavior of stopping, pausing, or disabling the second timer. The content of the above embodiment is also applicable to behaviors other than stopping, pausing, or disabling the second timer.

[0225] It should be noted that the above embodiments illustrate possible combinations 1 to 4. The methods provided in the embodiments of the present application can also be combined to obtain other methods, and the combined methods should also fall within the protection scope of the embodiments of the present application.

[0226] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0227] Please refer to Figure 3, which shows a block diagram of a data transmission device provided by one embodiment of the present application. This device has the functions of implementing the above-mentioned example of the data transmission method. The functions can be implemented by hardware or by hardware executing corresponding software. This device can be the terminal device described above, or it can be provided in a terminal device. As shown in Figure 3, the device 300 may include: a processing module 310.

[0228] The processing module 310 is used to perform a first behavior when a first condition is met; wherein the first behavior includes at least one of the following: stopping the first timer, not enabling the first timer, pausing the first timer, not transmitting data, clearing the buffer, and clearing the hybrid automatic repeat request HARQ process.

[0229] In some embodiments, the first timer is related to the transmission of the data, and / or the first condition is related to the delay of the data.

[0230] In some embodiments, the first timer includes at least one of the following: a configuration grant timer CGT, a configuration grant retransmission timer CGRT, a HARQ round trip time RTT timer, and a HARQ retransmission timer.

[0231] In some embodiments, the first condition is determined based on at least one of the following: a first duration, a second timer, first information, the transmission status of the data, and the delay of the data, wherein the second timer is used to control the transmission time of the data or the storage time of the data; the first information is used to configure or indicate whether the terminal device is allowed to perform the first behavior.

[0232] In some embodiments, when the first condition is determined based on the first duration or the second timer, the first condition is: exceeding the first duration, or the second timer times out or does not run or stops.

[0233] In some embodiments, the duration of the second timer is the same as the first duration.

[0234] In some embodiments, the first duration or the second timer is configured for at least one of the following objects: a data radio bearer DRB, the terminal device, a HARQ process, a CG, a DG, a LCH, a LCG, or a MAC entity.

[0235] In some embodiments, the first duration or the second timer is maintained for at least one of the following objects: DRB, the terminal device, HARQ process, CG, DG, LCH, LCG, MAC entity, MAC PDU, triggered DSR, pending DSR, DSR MAC CE.

[0236] In some embodiments, the first duration is related to the length or running state of a Packet Data Convergence Protocol (PDCP) discard timer; or

[0237] The first duration is related to the PDB and / or PSDB.

[0238] In some embodiments, the starting time of the first duration or the second timer is one of the following times: the time when the data reaches the AS layer of the terminal device, the time when the data reaches PDCP, the time when PDCP receives the data, the start time of the PDCP discard timer, the triggering time of DSR, the time when DSR MAC CE is generated, the time when MAC PDU containing the data is generated, the time when MAC PDU containing the data is transmitted, the time when the authorization containing the data is transmitted, the time when the authorization corresponding to the data is transmitted, the time when MAC PDU containing DSR MAC CE is generated, the time when MAC PDU containing DSR MAC CE is transmitted, the time when a data packet or authorization containing DSR MAC CE is transmitted, and the time when a data packet or authorization containing DSR MAC CE is sent.

[0239] In some embodiments, the first information is used to configure or instruct a first object to perform the first behavior; or

[0240] The first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior; or,

[0241] The first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior on the first object; or

[0242] The first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior within a first time period; or,

[0243] The first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior on the first object within a first time period; or

[0244] The first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior at a first moment; or

[0245] The first information is used to configure or indicate whether to allow or enable the terminal device to perform the first behavior on the first object at a first moment;

[0246] The first object includes at least one of the following: DRB, the terminal device, HARQ process, CG, DG, LCH, LCG, media access control MAC PDU, triggered DSR, pending DSR, DSR MAC CE.

[0247] In some embodiments, the transmission condition of the data includes at least one of the following: the data or PDU or service data unit SDU reports DSR information, the DSR information includes the data or PDU or SDU, the MAC PDU has been packaged, at least part of the data or PDU or SDU is transmitted, the data or PDU or SDU is not deleted, the data or PDU or SDU is packaged or sent, the MAC PDU includes the data or PDU or SDU that meets the delay condition, and the data or PDU or SDU included in the MAC PDU are all data or SDUs that meet the delay condition.

[0248] In some embodiments, the first condition is that the delay of the data is less than or equal to a first threshold; or, the first condition is that the data has a specific delay requirement.

[0249] In some embodiments, the delay is a residual delay; or,

[0250] The delay is a delay determined based on a PDCP discard timer; or,

[0251] The delay is a delay determined based on the PDB or PSDB; or,

[0252] The delay is the remaining time for the data to reach the PDB or PSDB requirements.

[0253] In some embodiments, the first threshold is configured by a network device.

[0254] In some embodiments, the first threshold is less than a triggering threshold of a DSR MAC CE.

[0255] In some embodiments, the first threshold is configured for at least one of the following objects: DRB, the terminal device, HARQ process, CG, DG, LCH, LCG, MAC entity.

[0256] In some embodiments, the apparatus 300 further includes a receiving module (not shown).

[0257] a receiving module, configured to receive second information sent by a network device, wherein the second information is used to indicate that the network device has successfully received the data; or

[0258] The receiving module is used to receive third information sent by the network device, where the third information is used to instruct the terminal device to retransmit the data.

[0259] The technical solution provided in the embodiment of the present application is that when the first condition is met, the terminal device executes the first behavior and no longer transmits data, which can effectively avoid wasting resources to transmit data that does not meet the conditions and improve system capacity.

[0260] It should be noted that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0261] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0262] Please refer to Figure 4, which shows a schematic diagram of the structure of a terminal device provided in one embodiment of the present application. The terminal device 400 may include: a processor 401, a transceiver 402, and a memory 403. The transceiver 402 is used to implement a transmission or reception function, and the processor 401 may be used to implement other processing functions or control transmission and / or reception, such as implementing the functions of the processing module 310 described above.

[0263] The processor 401 includes one or more processing cores. The processor 401 executes various functional applications and information processing by running software programs and modules.

[0264] The transceiver 402 may include a receiver and a transmitter. For example, the receiver and the transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0265] The memory 403 may be connected to the processor 401 and the transceiver 402 .

[0266] The memory 403 may be used to store a computer program executed by the processor, and the processor 401 is used to execute the computer program to implement each step in the above method embodiment.

[0267] In some embodiments, the processor 401 is used to perform a first behavior when a first condition is met; wherein the first behavior includes at least one of the following: stopping or not enabling or pausing a first timer, not transmitting data, clearing a buffer, and clearing a hybrid automatic repeat request HARQ process.

[0268] For details not described in detail in this embodiment, please refer to the above embodiments and will not be described in detail here.

[0269] In addition, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0270] The embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored, and the computer program is used to be executed by a processor to implement the above-mentioned data transmission method on the terminal device side. Optionally, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives) or optical disks, etc. Among them, random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0271] An embodiment of the present application further provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the above-mentioned data transmission method on the terminal device side.

[0272] An embodiment of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor reads and executes the computer program from the computer-readable storage medium to implement the above-mentioned data transmission method on the terminal device side.

[0273] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0274] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0275] In some embodiments of the present application, "predefined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, predefined may refer to information defined in a protocol.

[0276] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, for example, it may include an LTE protocol, a NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0277] In this document, "plurality" refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates an "or" relationship between the associated objects.

[0278] The term “greater than or equal to” mentioned herein may mean greater than or equal to, or greater than, and the term “less than or equal to” may mean less than or equal to, or less than.

[0279] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order of the diagram. The embodiments of the present application are not limited to this.

[0280] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0281] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A data transmission method, characterized in that, The method is executed by a terminal device, and the method includes: Performing a first action when a first condition is met; wherein, the first action includes at least one of the following: stopping a first timer, not enabling the first timer, pausing the first timer, not transmitting data, clearing a buffer, and clearing a Hybrid Automatic Repeat reQuest (HARQ) process.

2. The method according to claim 1, characterized in that, The first timer is related to the transmission of the data, and / or, the first condition is related to the latency of the data.

3. The method according to claim 1 or 2, characterized in that The first timer includes at least one of the following: a Configured Grant Timer (CGT), a Configured Grant Retransmission Timer (CGRT), a HARQ Round-Trip Time (RTT) timer, and a HARQ retransmission timer.

4. The method according to any one of claims 1 to 3, characterized in that The first condition is determined based on at least one of the following: a first duration, a second timer, first information, the transmission situation of the data, and the latency of the data, where the second timer is used to control the transmission time or the storage time of the data; and the first information is used to configure or indicate whether to allow the terminal device to perform the first action.

5. The method according to claim 4, wherein When the first condition is determined based on the first duration or the second timer, the first condition is: exceeding the first duration, or the second timer timing out or not running or stopping.

6. The method according to claim 5, wherein The duration of the second timer is the first duration.

7. The method according to claim 5 or 6, characterized in that, The first duration or the second timer is configured for at least one of the following objects: a Data Radio Bearer (DRB), the terminal device, a HARQ process, a Configured Grant (CG), a Dynamic Grant (DG), a Logical Channel (LCH), a Logical Channel Group (LCG), and a Medium Access Control (MAC) entity.

8. The method according to any one of claims 5 to 7, characterized in that The first duration or the second timer is maintained for at least one of the following objects: a DRB, the terminal device, a HARQ process, a CG, a DG, an LCH, an LCG, a MAC entity, a MAC Protocol Data Unit (PDU), a triggered Delayed Status Report (DSR), a pending DSR, and a DSR MAC Control Element (MAC CE).

9. The method according to any one of claims 5 to 8, characterized in that The first duration is related to the length or running state of a Packet Data Convergence Protocol (PDCP) discard timer; or The first duration is related to a Packet Delay Budget (PDB) and / or a PDU Set Delay Budget (PSDB).

10. The method according to any one of claims 5 to 9, characterized in that, The start time of the first duration or the second timer is one of the following times: the time when the data reaches the AS layer of the terminal device, the time when the data reaches the PDCP, the time when the PDCP receives the data, the start time of the PDCP discard timer, the triggering time of DSR, the time when the DSR MAC CE is generated, the time when the MAC PDU containing the data is generated, the time when the MAC PDU containing the data is transmitted, the time when the authorization containing the data is transmitted, the time when the authorization corresponding to the data is transmitted, the time when the MAC PDU containing the DSR MAC CE is generated, the time when the MAC PDU containing the DSR MAC CE is transmitted, the time when the packet containing the DSR MAC CE is transmitted, the time when the authorization containing the DSR MAC CE is transmitted, the time when the packet or authorization containing the DSR MAC CE is sent.

11. The method according to claim 4, wherein the first information is used to configure or indicate a first object for performing the first action; or, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action; or, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action for a first object; or, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action within a first time period; or, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action for a first object within a first time period; or, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action at a first moment; or, the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action for a first object at a first moment; wherein the first object includes at least one of the following: DRB, the terminal device, HARQ process, CG, DG, LCH, LCG, MAC PDU, triggered DSR, pending DSR, DSR MAC CE.

12. The method according to claim 4, wherein The transmission situation of the data includes at least one of the following: the data or PDU or service data unit SDU reports DSR information, the DSR information includes the data or PDU or SDU, the MAC PDU has been packetized, at least part of the data or PDU or SDU has been transmitted, the data or PDU or SDU has not been deleted, the data or PDU or SDU has been packetized or sent, the MAC PDU includes the data or PDU or SDU that meets the delay situation, and the data or PDU or SDU included in the MAC PDU are all data or SDUs that meet the delay situation.

13. The method according to claim 4, characterized in that, The first condition is that the delay of the data is less than or equal to a first threshold; or, the first condition is that the data has a specific delay requirement.

14. The method according to claim 13, wherein The delay is the remaining delay; or, The delay is the delay determined based on the PDCP discard timer; or, The time delay is a time delay determined based on PDB or PSDB; or, The time delay is the remaining time for the data to meet the PDB or PSDB requirements.

15. The method according to claim 13 or 14, characterized in that, The first threshold is configured by the network device.

16. The method according to any one of claims 13 to 15, characterized in that The first threshold is less than the trigger threshold of the DSR MAC CE.

17. The method according to any one of claims 13 to 16, characterized in that, The first threshold is configured for at least one of the following objects: DRB, the terminal device, HARQ process, CG, DG, LCH, LCG, MAC entity.

18. The method according to any one of claims 1 to 17, characterized in that, The method further includes: Receiving second information sent by the network device, where the second information is used to indicate that the network device has successfully received the data; or, Receiving third information sent by the network device, where the third information is used to indicate that the terminal device re-transmits the data.

19. A data transmission device, characterized in that, The apparatus includes: A processing module, configured to perform a first action when a first condition is met; where the first action includes at least one of the following: stopping a first timer, not enabling the first timer, pausing the first timer, not transmitting data, clearing a buffer, and clearing a Hybrid Automatic Repeat reQuest (HARQ) process.

20. The device according to claim 19, characterized in that, The first timer is related to the transmission of the data, and / or the first condition is related to the time delay of the data.

21. The device according to claim 19 or 20, characterized in that, The first timer includes at least one of the following: a Configuration Grant Timer (CGT), a Configuration Grant Retransmission Timer (CGRT), a HARQ Round-Trip Time (RTT) Timer, and a HARQ Retransmission Timer.

22. The device according to any one of claims 19 to 21, characterized in that, The first condition is determined based on at least one of the following: a first duration, a second timer, first information, the transmission situation of the data, and the time delay of the data, where the second timer is used to control the transmission time or the storage time of the data; the first information is used to configure or indicate whether to allow the terminal device to perform the first action.

23. The device according to claim 22, characterized in that, When the first condition is determined based on the first duration or the second timer, the first condition is: exceeding the first duration, or the second timer timing out or not running or stopping.

24. The device according to claim 23, characterized in that, The duration of the second timer is the first duration.

25. The device according to claim 23 or 24, characterized in that, The first duration or the second timer is configured for at least one of the following objects: Data Radio Bearer (DRB), the terminal device, HARQ process, Configuration Grant (CG), Dynamic Grant (DG), Logical Channel (LCH), Logical Channel Group (LCG), Media Access Control (MAC) entity.

26. The device according to any one of claims 23 to 25, characterized in that, The first duration or the second timer is maintained for at least one of the following objects: DRB, the terminal device, HARQ process, CG, DG, LCH, LCG, MAC entity, MAC Protocol Data Unit (PDU), Triggered or Pending Delay Status Report (DSR), DSR Media Access Control Element (MAC CE).

27. The device according to any one of claims 23 to 26, characterized in that, The first duration is related to the length or running state of the Packet Data Convergence Protocol (PDCP) discard timer; or, The first duration is related to the Packet Delay Budget (PDB) and / or the PDU Set Delay Budget (PSDB).

28. The device according to any one of claims 23 to 27, characterized in that, The start time of the first duration or the second timer is one of the following times: the time when the data arrives at the AS layer of the terminal device, the time when the data arrives at the PDCP, the time when the PDCP receives the data, the start time of the PDCP discard timer, the triggering moment of DSR, the moment of generating the DSR MAC CE, the moment of generating the MAC PDU containing the data, the moment of transmitting the MAC PDU containing the data, the moment of transmitting the authorization containing the data, the moment of transmitting the authorization corresponding to the data, the moment of generating the MAC PDU containing the DSR MAC CE, the moment of transmitting the MAC PDU containing the DSR MAC CE, the moment of transmitting the data packet or authorization containing the DSR MAC CE, and the moment of sending the data packet or authorization containing the DSR MAC CE.

29. The device according to claim 22, wherein the first information is used to configure or indicate a first object for performing the first action; or the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action; or the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action on a first object; or the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action within a first period; or the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action on a first object within a first period; or the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action at a first moment; or the first information is used to configure or indicate whether to allow or enable the terminal device to perform the first action on a first object at a first moment; wherein the first object includes at least one of the following: DRB, the terminal device, HARQ process, CG, DG, LCH, LCG, MAC PDU, triggered DSR, pending DSR, DSR MAC CE.

30. The device according to claim 22, wherein, The transmission situation of the data includes at least one of the following: the data or PDU or service data unit SDU reports DSR information, the DSR information includes the data or PDU or SDU, the MAC PDU has been packetized, at least a part of the data or PDU or SDU has been transmitted, the data or PDU or SDU has not been deleted, the data or PDU or SDU has been packetized or sent, the data or PDU or SDU that meets the latency situation is included in the MAC PDU, and the data or PDU or SDU included in the MAC PDU are all data or SDUs that meet the latency situation.

31. The device according to claim 22, wherein, The first condition is that the latency of the data is less than or equal to a first threshold; or the first condition is that the data has a specific latency requirement.

32. The device according to claim 31, characterized in that, The latency is the remaining latency; or The latency is the latency determined based on the PDCP discard timer; or The time delay is a time delay determined based on PDB or PSDB; or, The time delay is the remaining time for the data to meet the PDB or PSDB requirement.

33. The device according to claim 31 or 32, characterized in that, The first threshold is configured by the network device.

34. The device according to any one of claims 31 to 33, characterized in that, The first threshold is less than the triggering threshold of the DSR MAC CE.

35. The device according to any one of claims 31 to 34, characterized in that, The first threshold is configured for at least one of the following objects: DRB, the terminal device, HARQ process, CG, DG, LCH, LCG, MAC entity.

36. The device according to any one of claims 19 to 35, characterized in that The apparatus further includes: a receiving module, configured to receive second information sent by the network device, where the second information is used to indicate that the network device has successfully received the data; or, a receiving module, configured to receive third information sent by the network device, where the third information is used to indicate that the terminal device re-transmits the data.

37. A terminal device, characterized in that, The terminal device includes a processor and a memory, where a computer program is stored in the memory, and the processor executes the computer program to implement the method according to any one of claims 1 to 18.

38. A computer-readable storage medium, characterized in that, A computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the method according to any one of claims 1 to 18.

39. A chip, characterized in that, The chip includes programmable logic circuits and / or program instructions, and when the chip runs, it is used to implement the method according to any one of claims 1 to 18.

40. A computer program product, characterized in that, The computer program product includes computer instructions, where the computer instructions are stored in a computer-readable storage medium, and the processor reads and executes the computer instructions from the computer-readable storage medium to implement the method according to any one of claims 1 to 18.

Images