Parameter determination method and apparatus, and terminal device

CN118891901APending Publication Date: 2024-11-01GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280090072.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-07
Publication Date
2024-11-01

AI Technical Summary

Technical Problem

The existing DRX configuration method is based on UE granularity and has poor flexibility. It cannot dynamically adjust DRX parameters according to the QoS requirements of different data, which affects the power consumption and service performance of the terminal equipment.

Method used

By determining the DRX parameters related to the HARQ process, configuring them according to the data granularity, and dynamically adjusting the parameters of the DRX mechanism to improve the flexibility of DRX.

Benefits of technology

It realizes dynamic adjustment of DRX parameters according to different business needs, meets delay-sensitive and energy-saving needs, and improves the performance and efficiency of terminal equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118891901A_ABST
    Figure CN118891901A_ABST
Patent Text Reader

Abstract

Provided in an embodiment of the present application are a parameter determination method and apparatus, and a terminal device, the method comprising: a terminal device determining a first discontinuous reception (DRX) parameter, the first DRX parameter being a DRX parameter related to a hybrid automatic repeat request (HARQ) process, and the first DRX parameter being also related to data; and the terminal equipment executes a corresponding DRX operation based on the first DRX parameter.
Need to check novelty before this filing date? Find Prior Art

Description

Parameter determination method and device, and terminal equipment Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a parameter determination method and apparatus, and terminal equipment. Background Art

[0002] To save energy on terminal devices, a discontinuous reception (DRX) mechanism is introduced. Network equipment configures a DRX configuration for the terminal device, which then uses the DRX configuration to monitor the physical downlink control channel (PDCCH).

[0003] However, the current DRX configuration is configured according to the UE granularity (per UE), and the terminal device will use the same set of DRX configuration for any transmission situation. The current DRX configuration method has poor flexibility.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a parameter determination method and apparatus, terminal equipment, chip, computer-readable storage medium, computer program product, and computer program.

[0006] The parameter determination method provided in the embodiment of the present application includes:

[0007] The terminal device determines a first DRX parameter, where the first DRX parameter is a DRX parameter related to a Hybrid Automatic Repeat Request (HARQ) process, and the first DRX parameter is further related to data;

[0008] The terminal device performs corresponding DRX operations based on the first DRX parameters.

[0009] The parameter determination device provided in the embodiment of the present application includes:

[0010] a determining unit, configured to determine a first DRX parameter, where the first DRX parameter is a DRX parameter related to the HARQ process and is also related to data;

[0011] A processing unit is configured to perform corresponding DRX operations based on the first DRX parameters.

[0012] The terminal device provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned parameter determination method.

[0013] The chip provided in the embodiment of the present application is used to implement the above-mentioned parameter determination method.

[0014] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned parameter determination method.

[0015] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned parameter determination method.

[0016] The computer program product provided in the embodiments of the present application includes computer program instructions, which enable a computer to execute the above-mentioned parameter determination method.

[0017] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned parameter determination method.

[0018] Through the above technical solution, the first DRX parameter is a DRX parameter related to the HARQ process, and the first DRX parameter is also related to the data, that is, the first DRX parameter is configured according to the data granularity (per data or per TB), so that the DRX parameter at the HARQ process level can be adjusted according to the data granularity, thereby improving the flexibility of the DRX mechanism. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0020] FIG1 is a schematic diagram of an application scenario;

[0021] Figure 2 is a diagram of a 5G network system architecture;

[0022] FIG3 is a schematic diagram of a QoS mechanism;

[0023] FIG4 is a schematic diagram of a DRX cycle;

[0024] FIG5 is a flow chart of a parameter determination method according to an embodiment of the present application;

[0025] FIG6 is a second flow chart of a parameter determination method according to an embodiment of the present application;

[0026] FIG7 is a schematic diagram of candidate start times of a fixed DRX state timer provided in an embodiment of the present application;

[0027] FIG8 is a third flow chart of a parameter determination method according to an embodiment of the present application;

[0028] FIG9 is a schematic diagram of the time slot length corresponding to the SCS provided in an embodiment of the present application;

[0029] FIG10 is a fourth flow chart of a parameter determination method according to an embodiment of the present application;

[0030] FIG11 is a schematic diagram of the structure of a parameter determination device provided in an embodiment of the present application;

[0031] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0032] FIG13 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0033] FIG14 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0035] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0036] As shown in Figure 1, a communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0037] It should be understood that the embodiments of the present application are only illustrative of the communication system 100, but the embodiments of the present application are not limited thereto. That is, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems.

[0038] In the communication system 100 shown in Figure 1, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area and may communicate with the terminal device 110 (eg, UE) located within the coverage area.

[0039] The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0040] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0041] For example, the terminal device 110 may refer to an access terminal, user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. An access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), 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 5G network, or a terminal device in a future evolution network, etc.

[0042] The terminal device 110 can be used for device-to-device (D2D) communication.

[0043] The wireless communication system 100 may further include a core network device 130 for communicating with the base station. The core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions that can be implemented by SMF and PGW-C. During the network evolution process, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in the embodiments of the present application.

[0044] The functional units in the communication system 100 may also establish connections and implement communication via next generation (NG) network interfaces.

[0045] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (referred to as N1); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (referred to as N3); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (referred to as N2); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (referred to as N4); the UPF can exchange user plane data with the data network through the NG interface 6 (referred to as N6); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (referred to as N11); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (referred to as N7).

[0046] Figure 1 exemplarily shows a base station, a core network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminal devices within its coverage area, which is not limited in this embodiment of the present application.

[0047] It should be noted that Figure 1 is merely an example of a system applicable to this application. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the associated objects are in an "or" relationship. It should also 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 relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; or it can mean that A and B have an association relationship. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between two objects, or that there is an association relationship between the two objects, or a relationship between an indicator and the indicated, a configuration and the configured, and so on. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit its specific implementation method. For example, predefined can refer to a definition in a protocol. It should also be understood that in the embodiments of the present application, the “protocol” can refer to a standard protocol in the field of communications, such as an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0048] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0049] 5G Network Architecture

[0050] Figure 2 is a diagram of the 5G network system architecture. As shown in Figure 2, the network elements involved in the 5G network system include: User Equipment (UE), Radio Access Network (RAN), User Plane Function (UPF), Data Network (DN), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Application Function (AF), Authentication Server Function (AUSF), and Unified Data Management (UDM).

[0051] As shown in Figure 2, the UE establishes an access stratum (AS) connection with the RAN via the Uu interface, exchanging access stratum messages and wireless data transmission. The UE establishes a non-access stratum (NAS) connection with the AMF via the N1 interface, exchanging NAS messages. The AMF is the mobility management function in the core network, and the SMF is the session management function in the core network. In addition to managing UE mobility, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The PCF is the policy management function in the core network, responsible for formulating policies related to UE mobility management, session management, and billing. The UPF is a user plane function in the core network, communicating data with the DN via the N6 interface and with the RAN via the N3 interface.

[0052] Qos mechanism

[0053] In a mobile communication network, one or more QoS flows need to be established to transmit user-plane data. QoS parameters are often used to indicate the characteristics of a QoS flow, as an important measure of communication quality. Different QoS flows correspond to different QoS parameters. QoS parameters may include but are not limited to: 5G QoS Identifier (5QI), Allocation Retension Priority (ARP), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), Uplink / Downlink Maximum Packet Loss Rate (UL / DL Maximum Packet Loss Rate, UL / DL MPLR), End-to-end Packet Delay Budget (PDB), AN-PDB, Packet Error Rate (PER), Priority Level, Averaging Window, Resource Type, Maximum Data Burst Volume, UE Aggregate Maximum Bit Rate (UE-AMBR), Session Aggregate Maximum Bit Rate (Session-AMBR), etc.

[0054] Filters contain characteristic parameters that describe data packets (such as some relevant parameters of IP packets and some relevant parameters of Ethernet packets) and are used to filter out specific data packets to bind to specific QoS flows. The most commonly used filter here is the IP quintuple, namely the source IP address, destination IP address, source port number, destination port number, and protocol type.

[0055] Referring to Figure 3, the UPF and UE will form a filter based on the characteristic parameter combination of the data packet (the trapezoid on the far left and the parallelogram on the far right in Figure 3 represent the filter). The uplink or downlink data packets that meet the characteristic parameters of the data packet transmitted on the user plane are filtered through the filter and bound to a certain QoS flow. The uplink QoS flow is bound by the UE, and the downlink QoS flow is bound by the UPF. In the QoS mechanism, one or more QoS flows can be mapped to a data radio bearer (DRB) for transmission. For a QoS flow, corresponding to a set of QoS parameters, the base station will establish a DRB based on the QoS parameters and bind the QoS flow to a specific DRB.

[0056] QoS flows are established by the SMF. When QoS needs to be adjusted, both the UE and the network can trigger the PDU Session Modification process to change the QoS. For example, the UE can modify the QoS parameters of a QoS flow or establish a new QoS flow by sending a PDU Session Modification Request message. This means that when the UE adjusts its QoS, it must execute a session modification process and obtain network approval. Because the PDU Session Modification process takes a long time and is not guaranteed to succeed, it can affect application behavior. Applications cannot accurately determine whether and when they can achieve their desired QoS. This can have a significant impact on many real-time services, such as machine learning and neural network analysis. QoS changes can occur in a variety of situations. For example, the following can all cause QoS changes: 1) base station handover; 2) network congestion (e.g., a sudden increase in the number of users); and 3) the UE moves into or out of a specific range (e.g., the service area of ​​an edge server).

[0057] URLLC / XR

[0058] In the future, the 3rd Generation Partnership Project (3 rdThe 3GPP (3rd Generation Partnership Project) system will provide increasingly broad and in-depth support for vertical industries. For example, Ultra-Reliable Low-Latency Communications (URLLC) supports the transmission of services such as factory automation, transport industry, and smart electrical power distribution over 5G systems. Extended Reality (XR) supports the transmission of services such as augmented reality (AR), virtual reality (VR), mixed reality (MR), and cloud gaming. These services generally have reliability and latency requirements, and resource scheduling for terminal devices must meet data transmission Quality of Service (QoS) requirements. For terminal devices, power consumption must also be addressed to avoid unnecessary power consumption. Furthermore, given the large number of terminal devices supporting these services, resource allocation must ensure network capacity.

[0059] Typically, URLLC / XR services must support a minimum latency of 0.5ms and 99.999% reliability. Services can be pseudo-periodic, meaning that service arrival times exhibit jitter. In other words, services arrive not at a specific time but at any time within a time range. Furthermore, service periods can be non-integer, such as 16.67ms. Furthermore, the arrival times of different service flows within the same service can vary significantly.

[0060] DRX mechanism in 5G NR

[0061] In 5G NR, network devices can configure DRX configuration for terminal devices through RRC dedicated signaling, so that the terminal devices can monitor PDCCH discontinuously to achieve the purpose of terminal device power saving. Each Media Access Control (MAC) entity has a DRX configuration. As an example, the parameters configured in the DRX configuration are:

[0062] -DRX-onDurationTimer: used to determine the period of time after the start of the DRX cycle;

[0063] -DRX slot offset (drx-SlotOffset): used to determine the delay before starting the DRX state timer;

[0064] -DRX Inactivity Timer: used to determine the period of time after a PDCCH occasion in which a PDCCH is detected and indicates a new uplink or downlink transmission;

[0065] - Downlink DRX retransmission timer (drx-RetransmissionTimerDL): used to determine the maximum time before receiving a downlink retransmission;

[0066] - Uplink DRX retransmission timer (drx-RetransmissionTimerUL): used to determine the maximum time before receiving an uplink retransmission grant;

[0067] -DRX long cycle start offset (drx-LongCycleStartOffset): used to determine the DRX long cycle and the DRX start time offset (drx-StartOffset). drx-StartOffset is used to determine the start time of the DRX long cycle and DRX short cycle (e.g., the subframe corresponding to the start time);

[0068] -DRX short cycle (drx-ShortCycle): This is an optional configuration used to determine the DRX short cycle;

[0069] -DRX Short Cycle Timer (drx-ShortCycleTimer): This is an optional configuration used to determine the duration of the DRX short cycle. Its value refers to the multiple of the DRX short cycle;

[0070] - Downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL): the minimum duration expected by the MAC entity before a downlink allocation for HARQ retransmission;

[0071] - Uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL): The minimum duration before an uplink grant for HARQ retransmission expected by the MAC entity.

[0072] In the above solution, the unit of the DRX parameter is millisecond (ms), which is applicable to services whose DRX cycle is an integer multiple of the ms cycle.

[0073] In the above solution, the downlink DRX retransmission timer, the uplink DRX retransmission timer, the downlink DRX HARQ RTT timer, and the uplink DRX HARQ RTT timer are related to HARQ.

[0074] If the terminal device is configured with DRX, the terminal device needs to monitor the PDCCH during the DRX active time. The DRX active time includes the following situations:

[0075] 1) The running period of any one of the five timers, drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, and ra-ContentionResolutionTimer, belongs to the DRX activation time.

[0076] 2) After the terminal device sends a scheduling request (SR) on the physical uplink control channel (PUCCH), the period when the SR is in a pending state belongs to the DRX activation time.

[0077] 3) In the contention-based random access process, the period during which the terminal device has not received an initial transmission indicated by the C-RNTI-scrambled PDCCH after successfully receiving the random access response belongs to the DRX activation time.

[0078] The terminal device determines the start time of drx-onDurationTimer based on whether the current DRX cycle is a short DRX cycle or a long DRX cycle. The specific regulations are as follows:

[0079] 1.1> If the DRX short cycle is used, the SFN and subframe number of the start time of drx-onDurationTimer satisfy the following equation: [(SFN × 10) + subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle);

[0080] 1.2> If DRX long cycle is used, then the SFN and subframe number of the start time of drx-onDurationTimer satisfy the following: [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset;

[0081] 2> Start drx-onDurationTimer at the moment when the start time of the subframe determined by the above formula is offset by drx-SlotOffset time slots.

[0082] The conditions for the terminal device to start or restart drx-InactivityTimer are:

[0083] If the terminal device receives a PDCCH indicating an initial downlink or uplink transmission, the terminal device starts or restarts the drx-InactivityTimer.

[0084] The conditions for the terminal device to start and stop drx-RetransmissionTimerDL are:

[0085] When the terminal device receives a PDCCH indicating a downlink transmission, or when the terminal device receives a MAC PDU on the configured downlink grant resources, the terminal device stops the drx-RetransmissionTimerDL corresponding to the HARQ process. The terminal device starts the drx-HARQ-RTT-TimerDL corresponding to the HARQ process after completing the transmission of the HARQ process feedback for this downlink transmission.

[0086] If the drx-HARQ-RTT-TimerDL corresponding to a HARQ process of the terminal device times out and the decoding of the downlink data transmitted using this HARQ process is unsuccessful, the terminal device starts the drx-RetransmissionTimerDL corresponding to this HARQ process.

[0087] The conditions for the terminal device to start and stop drx-RetransmissionTimerUL are:

[0088] When the terminal device receives a PDCCH indicating an uplink transmission, or when the terminal device sends a MAC PDU on the configured uplink grant resource, the terminal device stops the drx-RetransmissionTimerUL corresponding to the HARQ process. The terminal device starts the drx-HARQ-RTT-TimerUL corresponding to the HARQ process after completing the first repetition of the PUSCH.

[0089] If the drx-HARQ-RTT-TimerUL corresponding to a HARQ process of the terminal device times out, the terminal device starts the drx-RetransmissionTimerUL corresponding to this HARQ process.

[0090] It can be seen from the above DRX mechanism that after completing uplink transmission or completing ACK / NACK feedback for downlink transmission, the terminal device will first start a DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL for uplink transmission and drx-HARQ-RTT-TimerDL for downlink transmission). The terminal device is in sleep state during the operation of the DRX HARQ RTT timer and does not monitor the PDCCH. The terminal device will start monitoring the uplink retransmission scheduling after the timer expires, or determine whether to start monitoring the downlink retransmission scheduling based on the feedback.

[0091] As shown in Figure 4, the DRX cycle consists of "On Duration" and "DRX opportunity (Opportunity for DRX)". During the On Duration time, the terminal device is in the DRX active time; if the terminal does not receive PDCCH within the On Duration time, it will stop monitoring and switch to DRX inactive time (DRX inactive time) during the "Opportunity for DRX" time. The terminal device does not receive PDCCH to reduce power consumption (that is, the terminal device is in a dormant period).

[0092] Currently, the DRX configuration configured by network equipment for terminal devices is configured at the UE granularity (per UE). The terminal device will use the same set of DRX configurations for any transmission situation. That is, regardless of the service, the data carried, and the data in the bearer, the terminal device will use a set of DRX configurations. The same DRX parameters are also used for HARQ-related DRX parameters. Because different data has different QoS requirements, dynamically adjusting the DRX parameters used according to the data is beneficial for data with strict QoS requirements. To this end, the following technical solutions are proposed in the embodiments of the present application.

[0093] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0094] FIG5 is a flow chart of a parameter determination method according to an embodiment of the present application. As shown in FIG5 , the parameter determination method includes the following steps:

[0095] Step 501: The terminal device determines a first DRX parameter, where the first DRX parameter is a DRX parameter related to the HARQ process and is also related to data.

[0096] Step 502: The terminal device performs corresponding DRX operations based on the first DRX parameters.

[0097] In an embodiment of the present application, the first DRX parameter is a DRX parameter related to the HARQ process, and the first DRX parameter includes a downlink DRX parameter related to the HARQ process and / or an uplink DRX parameter related to the HARQ process, wherein the downlink DRX parameter related to the HARQ process can be set according to data granularity, and the uplink DRX parameter related to the HARQ process can also be set according to data granularity, which is explained below.

[0098] Solution 1: Downlink DRX parameters related to the HARQ process

[0099] The first DRX parameter includes a first round-trip time (RTT) timer and / or a first retransmission timer, and the first RTT timer and / or the first retransmission timer are timers used by the downlink HARQ process. Here, the first RTT timer may also be referred to as a downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL), and the first retransmission timer may also be referred to as a downlink DRX retransmission timer (drx-RetransmissionTimerDL). Their functions may refer to the description of the aforementioned related solutions. It should be noted that this application does not limit the names of the first RTT timer and the first retransmission timer.

[0100] In the embodiment of the present application, the terminal device determines the first RTT timer and / or the first retransmission timer in the following manners, but is not limited to:

[0101] Method 1-1

[0102] In some optional embodiments, the terminal device receives first downlink control information (Downlink Control Information, DCI) sent by a network device, where the first DCI is used to schedule downlink transmission of data, and the first DCI is also used to indicate a first RTT timer and / or a first retransmission timer used for the data in a HARQ process associated with the data; the terminal device determines the first RTT timer and / or the first retransmission timer based on the first DCI.

[0103] In some optional embodiments, the first DCI carries an index of the first RTT timer and / or the first retransmission timer; the terminal device determines the first RTT timer and / or the first retransmission timer based on the index of the first RTT timer and / or the first retransmission timer, and first configuration information, the first configuration information including at least one RTT timer configuration and / or at least one retransmission timer configuration, wherein each RTT timer configuration is associated with an index, each retransmission timer configuration is associated with an index, or each RTT timer configuration and retransmission timer configuration are associated with a shared index. Here, the first configuration information is configured through Radio Resource Control (RRC) signaling.

[0104] In some optional implementations, the first DCI carries a logical channel identifier (Logical Channel ID, LCID) list, where the LCID list is used to indicate a list of logical channels for data scheduled by the first DCI and authorized to be transmitted.

[0105] Method 1-2

[0106] In some optional embodiments, the terminal device determines the first RTT timer and / or the first retransmission timer based on a semi-persistent scheduling (SPS) in which the received data is located and second configuration information, wherein the second configuration information includes an RTT timer configuration and / or a retransmission timer configuration corresponding to at least one SPS. Here, the second configuration information is configured through RRC signaling.

[0107] Methods 1-3

[0108] In some optional embodiments, the terminal device determines the first RTT timer and / or the first retransmission timer based on the LCID corresponding to the received data and third configuration information, wherein the third configuration information includes an RTT timer configuration and / or a retransmission timer configuration corresponding to at least one LCID. Here, the third configuration information is configured through RRC signaling.

[0109] In one case, the data received by the terminal corresponds to an LCID. In this case, the terminal device determines the RTT timer configuration and / or retransmission timer configuration corresponding to the LCID based on the third configuration information, and uses it as the first RTT timer and / or first retransmission timer.

[0110] In another case, the data received by the terminal corresponds to multiple LCIDs. In this case, the following options are available:

[0111] Option 1) If the data received by the terminal corresponds to multiple LCIDs, the terminal selects the LCID with the highest priority from the multiple LCIDs, and determines the RTT timer configuration and / or retransmission timer configuration corresponding to the LCID with the highest priority based on the third configuration information, and uses it as the first RTT timer and / or first retransmission timer.

[0112] Option 2) If the data received by the terminal corresponds to multiple LCIDs, the terminal device determines the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs based on the third configuration information, selects the shortest RTT timer configuration and / or retransmission timer from the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs, and uses it as the first RTT timer and / or first retransmission timer.

[0113] In the embodiment of the present application, after the terminal device determines the first RTT timer and / or the first retransmission timer, the terminal device performs the following DRX operation: after receiving the data and completing the positive acknowledgement (ACK) / negative acknowledgement (NACK) for the data

[0114] After the feedback, the first RTT timer is started; if the first RTT timer times out, the terminal device starts the first retransmission timer.

[0115] Solution 2: Uplink DRX parameters related to HARQ processes

[0116] The first DRX parameter includes a second RTT timer and / or a second retransmission timer, which are timers used by the uplink HARQ process. Here, the second RTT timer may also be referred to as an uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL), and the second retransmission timer may also be referred to as an uplink DRX retransmission timer (drx-RetransmissionTimerUL). Their functions may refer to the description of the aforementioned related solutions. It should be noted that this application does not limit the names of the second RTT timer and the second retransmission timer.

[0117] In the embodiment of the present application, the terminal device determines the second RTT timer and / or the second retransmission timer in the following manners, but is not limited to:

[0118] Method 2-1

[0119] In some optional embodiments, the terminal device receives a second DCI sent by a network device, where the second DCI is used to schedule uplink transmission of data, and the second DCI is also used to indicate a second RTT timer and / or a second retransmission timer used for the data in a HARQ process associated with the data; the terminal device determines the second RTT timer and / or the second retransmission timer based on the DCI.

[0120] In some optional embodiments, the second DCI carries an index of the second RTT timer and / or the second retransmission timer; the terminal device determines the second RTT timer and / or the second retransmission timer based on the index of the second RTT timer and / or the second retransmission timer, and fourth configuration information, wherein the fourth configuration information includes at least one RTT timer configuration and / or at least one retransmission timer configuration, wherein each RTT timer configuration is associated with an index, each retransmission timer configuration is associated with an index, or each RTT timer configuration and retransmission timer configuration are associated with a shared index. Here, the fourth configuration information is configured through RRC signaling.

[0121] In some optional implementations, the second DCI carries an LCID list, and the logical channel identifier list is used to indicate a list of logical channels for data scheduled by the second DCI and authorized to be transmitted.

[0122] Method 2-2

[0123] In some optional implementations, the terminal device uses the RTT timer and / or retransmission timer selected by it as the second RTT timer and / or second retransmission timer.

[0124] Further, optionally, the terminal device indicates to the network device an index of the second RTT timer and / or the second retransmission timer selected by the terminal device through the first indication information. In this way, the network device can determine the second RTT timer and / or the second retransmission timer based on the index of the second RTT timer and / or the second retransmission timer and the fourth configuration information.

[0125] Here, optionally, the first indication information is carried in a MAC control element (CE) or a header of a MAC packet data unit (PDU) or a header of a packet data convergence protocol (PDCP) PDU.

[0126] Method 2-3

[0127] In some optional embodiments, the terminal device determines the second RTT timer and / or the second retransmission timer based on a configured grant (CG) containing data to be sent and fifth configuration information, wherein the fifth configuration information includes an RTT timer configuration and / or a retransmission timer configuration corresponding to at least one CG. Here, the fifth configuration information is configured through RRC signaling.

[0128] Methods 2-4

[0129] In some optional implementations, the terminal device determines the second RTT timer and / or the second retransmission timer based on the LCID corresponding to the data to be sent and sixth configuration information, wherein the sixth configuration information includes an RTT timer configuration and / or a retransmission timer configuration corresponding to at least one LCID. Here, the sixth configuration information is configured through RRC signaling.

[0130] In one case, the data that the terminal needs to send corresponds to an LCID. In this case, the terminal device determines the RTT timer configuration and / or retransmission timer configuration corresponding to the LCID based on the sixth configuration information, and uses it as the second RTT timer and / or second retransmission timer.

[0131] In another case, the data that the terminal needs to send corresponds to multiple LCIDs. For this case, there are the following options:

[0132] Option 1) If the data that the terminal device needs to send corresponds to multiple LCIDs, the terminal selects the LCID with the highest priority from the multiple LCIDs, and determines the RTT timer configuration and / or retransmission timer configuration corresponding to the LCID with the highest priority based on the sixth configuration information, and uses it as the second RTT timer and / or second retransmission timer.

[0133] Option 2) If the data that the terminal device needs to send corresponds to multiple LCIDs, the terminal device determines the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs based on the sixth configuration information, and selects the shortest RTT timer configuration and / or retransmission timer from the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs, and uses it as the second RTT timer and / or second retransmission timer.

[0134] In an embodiment of the present application, after the terminal device determines the second RTT timer and / or the second retransmission timer, it performs the following DRX operation: after transmitting the data, the terminal device starts the second RTT timer; if the second RTT timer times out, the terminal device starts the second retransmission timer.

[0135] As an example: for downlink data, if the downlink data is transmitted based on DCI dynamic scheduling, the DCI indicates the DL DRX RTT timer and / or DL ​​DRX retansmission timer used for the data in the HARQ corresponding to the downlink data. After receiving the downlink data and completing the ACK / NACK feedback for the downlink data, the terminal device starts the DL DRX RTT timer indicated in the DCI; after the DL DRX RTT timer times out, the terminal device starts the DL DRX retansmission timer indicated in the DCI. The DCI may indicate the index of the DL DRX RTT timer and / or the DL DRX retansmission timer, at least one DL DRX RTT timer and / or at least one DL DRX retansmission timer is pre-configured through RRC signaling, each DL DRX RTT timer configuration is associated with an index, each DL DRX retansmission timer configuration is associated with an index, or each DL DRX RTT timer configuration and the DL DRX retansmission timer configuration are associated with a shared index.

[0136] As an example: for downlink data, if the downlink data is transmitted based on SPS, the terminal device starts the DL DRX RTT timer associated with the SPS after receiving the downlink data on the SPS and completing the ACK / NACK feedback for the downlink data; after the DL DRX RTT timer times out, the terminal device starts the DL DRX retansmission timer associated with the SPS. Among them, the network side configures the DL DRX RTT timer and / or DL ​​DRX retansmission timer per SPS through RRC signaling, that is, each SPS configuration corresponds to a DL DRX RTT timer configuration and / or DL ​​DRX retansmission tiemr configuration. Alternatively, after the terminal device receives the downlink data on the SPS and completes the ACK / NACK feedback for the downlink data, it starts the DL DRX RTT timer associated with the LCID corresponding to the downlink data; after the DL DRX RTT timer times out, the terminal device starts the DL DRX retansmission timer associated with the LCID corresponding to the downlink data. The network side configures the DL DRX RTT timer and / or DL ​​DRX retransmission timer per LCID through RRC signaling, that is, each LCID corresponds to a DL DRX RTT timer configuration and / or DL ​​DRX retransmission timer configuration.

[0137] As an example: for uplink data, if the uplink data is transmitted based on DCI dynamic scheduling, the DCI indicates the UL DRX RTT timer and / or UL DRX retansmission timer used for the data in the HARQ corresponding to the uplink data. After transmitting the uplink data, the terminal device starts the UL DRX RTT timer indicated in the DCI; after the UL DRX RTT timer times out, the terminal device starts the UL DRX retansmission timer indicated in the DCI. The DCI may indicate the index of the UL DRX RTT timer and / or the UL DRX retansmission timer, at least one UL DRX RTT timer and / or at least one UL DRX retansmission timer is pre-configured through RRC signaling, each UL DRX RTT timer configuration is associated with an index, each UL DRX retansmission timer configuration is associated with an index, or each UL DRX RTT timer configuration and the UL DRX retansmission timer configuration are associated with a shared index.

[0138] As an example: for uplink data, if the uplink data is transmitted based on CG, the terminal device starts the UL DRX RTT timer associated with the CG after transmitting the uplink data on the CG; after the UL DRX RTT timer times out, the terminal device starts the UL DRX retansmission timer associated with the CG. The network side configures the UL DRX RTT timer and / or UL DRX retansmission timer per CG through RRC signaling, that is, each CG configuration corresponds to a UL DRX RTT timer configuration and / or UL DRX retansmission tiemr configuration. Alternatively, after the terminal device transmits the uplink data on the CG, it starts the UL DRX RTT timer associated with the LCID corresponding to the uplink data; after the UL DRX RTT timer times out, the terminal device starts the UL DRX retansmission timer associated with the LCID corresponding to the uplink data. The network side configures the UL DRX RTT timer and / or UL DRX retransmission timer per LCID through RRC signaling, that is, each LCID corresponds to a UL DRX RTT timer configuration and / or UL DRX retransmission timer configuration.

[0139] As an example: for uplink data, the terminal device autonomously selects UL DRX RTT timer and / or UL DRX retansmission timer. After transmitting the uplink data, the terminal device starts the selected UL DRX RTT timer; after the UL DRX RTT timer times out, the terminal device starts the selected UL DRX retansmission timer. Furthermore, the terminal device can send an indication message to the network side while sending the uplink data. The indication message is used to indicate the index of the UL DRX RTT timer and / or UL DRX retansmission timer selected by the terminal device. Here, at least one UL DRX RTT timer and / or at least one UL DRX retansmission timer is pre-configured through RRC signaling, each UL DRX RTT timer configuration is associated with an index, each UL DRX retansmission timer configuration is associated with an index, or each UL DRX RTT timer configuration and UL DRX retansmission timer configuration are associated with a shared index. Here, the indication information can be carried in the MAC CE.

[0140] In the above scheme, the length of the RTT timer and / or retransmission timer can be dynamically adjusted according to the service QoS attributes of the data (such as delay), so that the running time of the retransmission timer and the on duration time overlap to the maximum extent, thereby achieving the purpose of energy saving of the terminal device while meeting the service QoS requirements. For example: a longer RTT timer and / or retransmission timer can be configured for a delay-insensitive service, thereby achieving the purpose of energy saving of the terminal device without affecting the service delay requirements. For example: a shorter RTT timer and / or retransmission timer can be configured for a delay-sensitive service, thereby meeting the service delay requirements.

[0141] In the above scheme, before the terminal device determines the above-mentioned first DRX parameter, optionally, the network device can configure a set of DRX parameters for the terminal device through RRC dedicated signaling, where the set of DRX parameters is configured per UE, including at least one of the following: DRX state timer (drx-onDurationTimer); DRX time slot offset (drx-SlotOffset); DRX inactivity timer (drx-InactivityTimer); downlink DRX retransmission timer (drx-RetransmissionTimerDL); uplink DRX retransmission timer (drx-RetransmissionTimerUL); DRX long cycle start offset (drx-LongCycleStartOffset); DRX short cycle (drx-ShortCycle); DRX short cycle cycle timer (drx-ShortCycleTimer); downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL); uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL).

[0142] It should be noted that the priority of the first RTT timer, the first retransmission timer, the second RTT timer, and the second retransmission timer determined by the terminal device in the above manner is higher than the priority of the first RTT timer, the first retransmission timer, the second RTT timer, and the second retransmission timer configured by the above RRC dedicated signaling, or in other words, the first RTT timer, the first retransmission timer, the second RTT timer, and the second retransmission timer determined by the terminal device in the above manner override the first RTT timer, the first retransmission timer, the second RTT timer, and the second retransmission timer configured by the RRC dedicated signaling.

[0143] In some optional embodiments, the method further includes: the terminal device receives RRC dedicated signaling sent by the network device, the RRC dedicated signaling is used to configure multiple sets of DRX parameters, each set of DRX parameters includes at least one of the following: DRX state timer (drx-onDurationTimer); DRX time slot offset (drx-SlotOffset); DRX inactivity timer (drx-InactivityTimer); downlink DRX retransmission timer (drx-RetransmissionTimerDL); uplink DRX retransmission timer (drx-RetransmissionTimerUL); DRX long cycle start offset (drx-LongCycleStartOffset); DRX short cycle (drx-ShortCycle); DRX short cycle cycle timer (drx-ShortCycleTimer); downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL); uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL). Further, the terminal device receives second indication information sent by the network device, where the second indication information is used to indicate the use of the set of DRX parameters from the multiple sets of DRX parameters. Here, optionally, the second indication information is carried in the DCI or the MAC CE.

[0144] FIG6 is a second flow chart of a parameter determination method provided in an embodiment of the present application. As shown in FIG6 , the parameter determination method includes the following steps:

[0145] Step 601: The terminal device receives third indication information sent by the network device, where the third indication information is used to indicate the DRX time slot offset to be used.

[0146] Here, the DRX timeslot offset may also be referred to as drx-SlotOffset, and its meaning may refer to the description of the aforementioned related solutions. It should be noted that the value of the DRX timeslot offset may be positive or negative.

[0147] Here, the third indication information is carried in the DCI or the MAC CE.

[0148] The DRX time slot offset can be configured in a set of DRX parameters through RRC dedicated signaling. Further, the DRX time slot offset can be dynamically changed through DCI or MAC CE, that is, the DCI or MAC CE carries third indication information, and the DRX time slot offset is dynamically changed through the third indication information.

[0149] Step 602: The terminal device determines the start time of the DRX state timer based on the third indication information.

[0150] In the embodiment of the present application, the terminal device determines the start time of the DRX state timer based on the third indication information, which can be achieved in the following manner:

[0151] Method A

[0152] In some optional embodiments, the terminal device determines the target SFN and the target subframe based on the DRX cycle and the DRX start offset; the terminal device determines the start time of the DRX state timer based on the third indication information as the start time of the target subframe in the target SFN offset backward or forward by N time slots, where N is determined based on the value of the DRX time slot offset. As one case, N is a positive value, and the terminal device determines the start time of the DRX state timer as the start time of the target subframe in the target SFN offset backward by N time slots. As another case, N is a negative value, and the terminal device determines the start time of the DRX state timer as the absolute value of N time slots offset forward from the start time of the target subframe in the target SFN.

[0153] Here, the DRX cycle may also be referred to as a drxCycle, which is divided into a DRX short cycle (drx-ShortCycle) and a DRX long cycle (drx-LongCycle). The meanings thereof may refer to the description of the aforementioned related solutions.

[0154] Here, the DRX start offset may be referred to as drx-StartOffset, and its meaning may refer to the description of the aforementioned related solutions.

[0155] Here, the terminal device may determine the target SFN and target subframe using the following formula:

[0156] For the case of DRX short cycle: [(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle); or,

[0157] For the case of DRX long cycle: [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset;

[0158] Among them, SFN is the target SFN, subframe number is the target subframe number, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, and modulo represents the remainder operation.

[0159] In the above solution, the value range of the DRX timeslot offset can be expanded, so that the start time of the DRX state timer can be determined according to the subframe granularity or the radio frame granularity.

[0160] Method B

[0161] In some optional embodiments, the terminal device determines a first candidate start time of the DRX state timer based on the DRX cycle and the DRX start offset, and determines a second candidate start time and / or a third candidate start time based on the first candidate start time and the DRX cycle; the terminal device receives fourth indication information sent by the network device, and the fourth indication information is used to indicate the start time to be used from the first candidate start time, the second candidate start time and / or the third candidate start time; the terminal device determines the start time of the DRX state timer based on the fourth indication information. Here, optionally, the second candidate start time is equal to the first candidate start time minus the duration of the DRX state timer, and the third candidate start time is equal to the first candidate start time plus the duration of the DRX state timer, as shown in Figure 7.

[0162] Here, the terminal device determines the target SFN and target subframe based on the DRX cycle and the DRX start offset, and determines the start time of the target subframe within the target SFN as the first candidate start time of the DRX state timer, or determines the moment when the start time of the target subframe within the target SFN is offset backward or forward by N time slots as the first candidate start time of the DRX state timer, where N is determined based on the value of the DRX time slot offset (such as drx-SlotOffset).

[0163] Here, the DRX cycle may also be referred to as a drxCycle, which is divided into a DRX short cycle (drx-ShortCycle) and a DRX long cycle (drx-LongCycle). The meanings thereof may refer to the description of the aforementioned related solutions.

[0164] Here, the DRX start offset may be referred to as drx-StartOffset, and its meaning may refer to the description of the aforementioned related solutions.

[0165] Here, the terminal device may determine the target SFN and target subframe using the following formula:

[0166] For the case of DRX short cycle: [(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle); or,

[0167] For the case of DRX long cycle: [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset;

[0168] Among them, SFN is the target SFN, subframe number is the target subframe number, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, and modulo represents the remainder operation.

[0169] For example, for quasi-periodic services, which may experience latency jitter, to align the start time of drx-onDurationTimer with the start time of the service period as closely as possible, drx-SlotOffset can be dynamically changed using method A above. The value of drx-SlotOffset can be positive or negative. Furthermore, the value range of drx-SlotOffset can be expanded, and the start time of drx-onDurationTimer can be determined based on subframe or radio frame granularity.

[0170] As an example: For quasi-periodic services, there may be delay jitter. In order to align the start time of drx-onDurationTimer with the start time of the service cycle as much as possible, multiple candidate start times of drx-onDurationTimer can be determined through the above method B, and the final start time to be used can be determined through dynamic indication on the network side.

[0171] The above-mentioned solution of the embodiment of the present application can meet the energy-saving requirements of the terminal equipment while meeting the service requirements of non-integer ms periods and the requirements of delay-sensitive services.

[0172] FIG8 is a flow chart of a parameter determination method according to an embodiment of the present application. As shown in FIG8 , the parameter determination method includes the following steps:

[0173] Step 801: The terminal device determines the start time of the DRX state timer based on the DRX cycle and the DRX start offset, where the units of the DRX cycle and the DRX start offset are time slots, half time slots, or symbols.

[0174] Here, the DRX cycle may also be referred to as a drxCycle, which is divided into a DRX short cycle (drx-ShortCycle) and a DRX long cycle (drx-LongCycle). The meanings thereof may refer to the description of the aforementioned related solutions.

[0175] Here, the DRX start offset may be referred to as drx-StartOffset, and its meaning may refer to the description of the aforementioned related solutions.

[0176] In the embodiment of the present application, the units of the DRX cycle and the DRX start offset can be extended to slots, half slots, or symbols, which are described below in combination with different situations.

[0177] Case 1

[0178] In some optional embodiments, the unit of the DRX cycle and the DRX start offset is a time slot; the terminal device determines the target SFN, the target subframe and the target time slot based on the DRX cycle and the DRX start offset; the terminal device determines, based on the DRX time slot offset and / or the DRX symbol offset, that the start time of the DRX state timer is the start time of the target time slot in the target subframe within the target SFN, offset backward or forward by N time slots and / or M symbols; or, the terminal device determines, based on the DRX symbol offset, that the start time of the DRX state timer is the start time of the target half time slot in the target time slot in the target subframe within the target SFN, offset backward or forward by N time slots and / or M symbols, the target half time slot is indicated by RRC signaling, N is determined based on the value of the DRX time slot offset, and M is determined based on the value of the DRX symbol offset.

[0179] Here, the DRX timeslot offset may also be referred to as drx-SlotOffset, and its meaning may refer to the description of the aforementioned related solutions. It should be noted that the value of the DRX timeslot offset may be positive or negative.

[0180] Here, the DRX symbol offset may also be referred to as drx-SymbolOffset, which means a symbol offset. It should be noted that the value of the DRX symbol offset may be a positive value or a negative value.

[0181] In the above solution, specifically, the terminal device determines the target SFN, target subframe, and target time slot based on the following formula:

[0182] For the case of DRX short cycle: [(SFN×10)×k+subframe number×k+slot number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle); or,

[0183] For the case of a long DRX cycle: [(SFN×10)×k+subframe number×k+slot number]modulo(drx-LongCycle)=drx-StartOffset;

[0184] Among them, SFN is the target SFN, subframe number is the target subframe number, slot number is the target time slot number, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

[0185] Case 2

[0186] In some optional embodiments, the unit of the DRX cycle and the DRX start offset is half a time slot; the terminal device determines the target SFN, target subframe, target time slot and target half time slot based on the DRX cycle and the DRX start offset; the terminal device determines the start time of the DRX state timer based on the DRX symbol offset, which is the start time of the target half time slot in the target time slot in the target subframe within the target SFN, offset backward or forward by M symbols, where M is determined based on the value of the DRX symbol offset.

[0187] Here, the DRX symbol offset may also be referred to as drx-SymbolOffset, which means a symbol offset. It should be noted that the value of the DRX symbol offset may be a positive value or a negative value.

[0188] In the above solution, specifically, the terminal device determines the target SFN, target subframe, target time slot and target half time slot based on the following formula:

[0189] For the case of a short DRX cycle: [(SFN×10)×k×2+subframe number×k×2+slot number×2+half slot number]modulo(drxCycle)=(drx-StartOffset)modulo(drxCycle); or,

[0190] For the case of a long DRX cycle: [(SFN×10)×k×2+subframe number×k×2+slot number×2+half slot number]modulo(drx-LongCycle)=drx-StartOffset;

[0191] Where SFN is the target SFN, subframe number is the target subframe number, slot number is the target slot number, half slot number is the target half slot number, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

[0192] Case 3

[0193] In some optional embodiments, the units of the DRX cycle and the DRX start offset are symbols; the terminal device determines the target SFN, target subframe, target time slot, target half time slot and target symbol based on the DRX cycle and the DRX start offset; the terminal device determines, based on the DRX symbol offset, that the start time of the DRX state timer is M symbols offset backward or forward from the start time of the target symbol in the target time slot in the target subframe within the target SFN, where M is determined based on the value of the DRX symbol offset.

[0194] Here, the DRX symbol offset may also be referred to as drx-SymbolOffset, which means a symbol offset. It should be noted that the value of the DRX symbol offset may be a positive value or a negative value.

[0195] In the above solution, specifically, the terminal device determines the target SFN, target subframe, target time slot, target half time slot and target symbol based on the following formula:

[0196] For the case of a short DRX cycle: [(SFN×10)×k×14+subframe number×k×14+slot number×14+symbol number]modulo(drxCycle)=(drx-StartOffset)modulo(drxCycle); or,

[0197] For the case of a long DRX cycle: [(SFN×10)×k×14+subframe number×k×14+slot number×14+symbol number]modulo(drx-LongCycle)=drx-StartOffset;

[0198] Among them, SFN is the target SFN, subframe number is the target subframe number, slot number is the target time slot number, symbol number is the target symbol, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

[0199] In the embodiment of the present application, the length of the unit (such as a time slot or a half time slot or a symbol) in the above scheme is related to the reference subcarrier spacing (SCS) or is determined based on the reference SCS. In some optional implementations, the reference SCS can be determined by:

[0200] Method I) Refer to SCS and display the configuration through RRC signaling.

[0201] Mode II) The reference SCS is the SCS configured for the currently activated DL BWP.

[0202] Method III) The reference SCS is the SCS configured for the currently activated UL BWP.

[0203] Mode IV) The reference SCS is the minimum SCS or the maximum SCS among the following SCSs: the SCS configured by the currently activated DL BWP and the SCS configured by the currently activated UL BWP.

[0204] Mode V) The reference SCS is the minimum SCS or maximum SCS among the following SCSs: the SCSs configured by all DL BWPs.

[0205] Method VI) The reference SCS is the minimum SCS or maximum SCS among the following SCSs: the SCSs configured for all UL BWPs.

[0206] Mode VII) The reference SCS is the minimum SCS or the maximum SCS among the following SCSs: the SCSs of all DL BWP configurations and the SCSs of all UL BWP configurations.

[0207] As an example: the unit of the DRX parameter can be a time slot, a half time slot or a symbol. The DRX parameters here are, for example: DRX state timer (drx-onDurationTimer); DRX time slot offset (drx-SlotOffset); DRX inactivity timer (drx-InactivityTimer); downlink DRX retransmission timer (drx-RetransmissionTimerDL); uplink DRX retransmission timer (drx-RetransmissionTimerUL); DRX long cycle start offset (drx-LongCycleStartOffset); DRX short cycle (drx-ShortCycle); DRX short cycle cycle timer (drx-ShortCycleTimer); downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL); uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL). The unit length of the DRX parameter is determined according to the reference SCS. As shown in Figure 9, the reference SCS can be 15KHz, 30KHz, 60KHz, 120KHz, or 240KHz. The time slot length corresponding to 15KHz is 1ms, the time slot length corresponding to 30KHz is 0.5ms, the time slot length corresponding to 60KHz is 0.25ms, the time slot length corresponding to 120KHz is 0.125ms, and the time slot length corresponding to 240KHz is 0.0625ms. Regardless of the reference SCS, a time slot includes 14 symbols. The reference SCS can be determined in the following ways: 1) The reference SCS is configured through RRC signaling; 2) The reference SCS is determined based on the SCS configured for the currently activated DL BWP or the SCS configured for the currently activated UL BWP; 3) The minimum SCS (or maximum SCS) of the SCS configured for the currently activated DL BWP and the SCS configured for the currently activated UL BWP is the reference SCS. 4) The minimum SCS (or maximum SCS) among the SCSs configured for all DL BWPs is used as the reference SCS, or the minimum SCS (or maximum SCS) among the SCSs configured for all UL BWPs is used as the reference SCS, or the minimum SCS (or maximum SCS) among the SCSs configured for all DL BWPs and the SCSs configured for all UL BWPs is used as the reference SCS. For different units, the scheme described in Case 1, Case 2, or Case 3 can be used to determine the start time of the DRX state timer.

[0208] The above-mentioned solution of the embodiment of the present application can meet the energy-saving requirements of the terminal equipment while meeting the service requirements of non-integer ms periods and the requirements of delay-sensitive services.

[0209] FIG10 is a fourth flow chart of a parameter determination method provided in an embodiment of the present application. As shown in FIG10 , the parameter determination method includes the following steps:

[0210] Step 1001: The terminal device receives seventh configuration information, and the seventh configuration information includes at least one SPS configuration and / or at least one CG configuration; wherein, at least part of the SPS configurations in the at least one SPS configuration includes fifth indication information; and at least part of the CG configurations in the at least one CG configuration includes sixth indication information.

[0211] Here, the seventh configuration information is carried in RRC dedicated signaling.

[0212] Here, the fifth indication information is used to indicate whether data reception on SPS is allowed during the DRX non-activation time, or to indicate that data reception on SPS is not allowed during the DRX non-activation time, or to indicate whether data reception on SPS needs to be performed during the DRX activation time, or to indicate that data reception on SPS needs to be performed during the DRX activation time.

[0213] Here, the sixth indication information is used to indicate whether data sending on the CG is allowed within the DRX non-activation time, or to indicate that data sending on the CG is not allowed within the DRX non-activation time, or to indicate whether data sending on the CG needs to be performed within the DRX activation time, or to indicate that data sending on the CG needs to be performed within the DRX activation time.

[0214] As a case, if some of the SPS configurations in the at least one SPS configuration do not include the fifth indication information, then for the SPS configured by the partial SPS configuration, the terminal device allows data reception on the SPS during the DRX non-activation time and / or the terminal device does not need to perform data reception on the SPS during the DRX activation time; if some of the CG configurations in the at least one CG configuration do not include the sixth indication information, then for the CG configured by the partial CG configuration, the terminal device allows data sending on the CG during the DRX non-activation time and / or the terminal device does not need to perform data sending on the CG during the DRX activation time.

[0215] As another case, if part of the SPS configurations in the at least one SPS configuration includes the fifth indication information, then for the SPS configured by the part of the SPS configuration, the terminal device determines based on the fifth indication information whether data reception on the SPS is allowed to be performed during the DRX non-activation time, or whether data reception on the SPS needs to be performed during the DRX activation time, or determines that data reception on the SPS is not allowed to be performed during the DRX non-activation time, or determines that data reception on the SPS needs to be performed during the DRX activation time; if part of the CG configuration in the at least one CG configuration includes the sixth indication information, then for the CG configured by the part of the CG configuration, the terminal device determines based on the sixth indication information whether data sending on the CG is allowed to be performed during the DRX non-activation time, or whether data sending on the CG needs to be performed during the DRX activation time, or determines that data sending on the CG is not allowed to be performed during the DRX non-activation time, or determines that data sending on the CG needs to be performed during the DRX activation time.

[0216] In the above-mentioned solution of the embodiment of the present application, if the network side configures a certain SPS or CG to not allow data sending or receiving during the DRX non-activation time, the purpose of energy saving of terminal equipment can be achieved for services that are not sensitive to delay.

[0217] It should be noted that the solutions related to Figures 6 to 10 of the embodiments of the present application can be implemented separately or in any combination.

[0218] The technical solution of the embodiment of the present application stipulates a method for dynamic change of DRX, so that the DRX activation time can meet the requirements of the quasi-periodicity of multimedia services and the non-integer periodicity of service cycles, while also meeting the service reception and transmission caused by service jitter.

[0219] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0220] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0221] FIG11 is a schematic diagram of the structure of a parameter determination device provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG11 , the parameter determination device includes:

[0222] The determining unit 1101 is configured to determine a first DRX parameter, where the first DRX parameter is a DRX parameter related to the HARQ process and is also related to data;

[0223] The processing unit 1102 is configured to perform corresponding DRX operations based on the first DRX parameters.

[0224] In some optional implementations, the first DRX parameter includes a first RTT timer and / or a first retransmission timer, where the first RTT timer and / or the first retransmission timer are timers used by a downlink HARQ process.

[0225] In some optional implementations, the apparatus further includes: a receiving unit 1103, configured to receive a first DCI sent by a network device, where the first DCI is used to schedule downlink transmission of data, and the first DCI is further used to indicate a first RTT timer and / or a first retransmission timer used for the data in a HARQ process associated with the data;

[0226] The determining unit 1101 is configured to determine the first RTT timer and / or the first retransmission timer based on the first DCI.

[0227] In some optional implementations, the first DCI carries an index of the first RTT timer and / or the first retransmission timer;

[0228] The determination unit 1101 is used to determine the first RTT timer and / or the first retransmission timer based on the index of the first RTT timer and / or the first retransmission timer, and first configuration information, wherein the first configuration information includes at least one RTT timer configuration and / or at least one retransmission timer configuration, wherein each RTT timer configuration is associated with an index, each retransmission timer configuration is associated with an index, or each RTT timer configuration and retransmission timer configuration are associated with a shared index.

[0229] In some optional implementations, the first configuration information is configured through RRC signaling.

[0230] In some optional implementations, the first DCI carries an LCID list, where the LCID list is used to indicate a list of logical channels for data scheduled by the first DCI and authorized to be transmitted.

[0231] In some optional embodiments, the determination unit 1101 is used to determine the first RTT timer and / or first retransmission timer based on the SPS where the received data is located and second configuration information, wherein the second configuration information includes an RTT timer configuration and / or retransmission timer configuration corresponding to at least one SPS.

[0232] In some optional implementations, the second configuration information is configured through RRC signaling.

[0233] In some optional embodiments, the determination unit 1101 is used to determine the first RTT timer and / or first retransmission timer based on the LCID corresponding to the received data and third configuration information, wherein the third configuration information includes an RTT timer configuration and / or retransmission timer configuration corresponding to at least one LCID.

[0234] In some optional embodiments, the determination unit 1101 is used to select the LCID with the highest priority from the multiple LCIDs if the received data corresponds to multiple LCIDs, and determine the RTT timer configuration and / or retransmission timer configuration corresponding to the LCID with the highest priority based on the third configuration information, and use it as the first RTT timer and / or first retransmission timer; or, if the received data corresponds to multiple LCIDs, determine the RTT timer configuration and / or retransmission timer corresponding to the multiple LCIDs based on the third configuration information, select the shortest RTT timer configuration and / or retransmission timer from the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs, and use it as the first RTT timer and / or first retransmission timer.

[0235] In some optional implementations, the third configuration information is configured through RRC signaling.

[0236] In some optional implementations, the processing unit 1102 is configured to start the first RTT timer after receiving the data and completing ACK / NACK feedback for the data; and start the first retransmission timer if the first RTT timer times out.

[0237] In some optional implementations, the first DRX parameter includes a second RTT timer and / or a second retransmission timer, and the second RTT timer and / or the second retransmission timer are timers used by an uplink HARQ process.

[0238] In some optional implementations, the apparatus further includes: a receiving unit 1103, configured to receive a second DCI sent by a network device, where the second DCI is used to schedule uplink transmission of the data, and the second DCI is further used to indicate a second RTT timer and / or a second retransmission timer used for the data in a HARQ process associated with the data;

[0239] The determining unit 1101 is configured to determine the second RTT timer and / or the second retransmission timer based on the DCI.

[0240] In some optional implementations, the second DCI carries an index of the second RTT timer and / or the second retransmission timer;

[0241] The determination unit 1101 is used to determine the second RTT timer and / or the second retransmission timer based on the index of the second RTT timer and / or the second retransmission timer, and fourth configuration information, wherein the fourth configuration information includes at least one RTT timer configuration and / or at least one retransmission timer configuration, wherein each RTT timer configuration is associated with an index, each retransmission timer configuration is associated with an index, or each RTT timer configuration and retransmission timer configuration are associated with a shared index.

[0242] In some optional implementations, the fourth configuration information is configured through RRC signaling.

[0243] In some optional implementations, the second DCI carries an LCID list, and the logical channel identifier list is used to indicate a list of logical channels for data scheduled by the second DCI and authorized to be transmitted.

[0244] In some optional implementations, the determining unit 1101 is configured to use the RTT timer and / or retransmission timer selected by it as the second RTT timer and / or second retransmission timer.

[0245] In some optional implementations, the apparatus further includes: a sending unit 1104, configured to indicate the index of the second RTT timer and / or the second retransmission timer selected by the terminal device to the network device through first indication information.

[0246] In some optional implementations, the first indication information is carried in a MAC CE or a header of a MAC PDU or a header of a PDCP PDU.

[0247] In some optional embodiments, the determination unit 1101 is used to determine the second RTT timer and / or second retransmission timer based on the configuration authorization CG where the data to be sent is located and the fifth configuration information, wherein the fifth configuration information includes at least one RTT timer configuration and / or retransmission timer configuration corresponding to the CG.

[0248] In some optional implementations, the fifth configuration information is configured through RRC signaling.

[0249] In some optional embodiments, the determination unit 1101 is used to determine the second RTT timer and / or second retransmission timer based on the LCID corresponding to the data to be sent and sixth configuration information, wherein the sixth configuration information includes an RTT timer configuration and / or retransmission timer configuration corresponding to at least one LCID.

[0250] In some optional embodiments, the determination unit 1101 is used to select the LCID with the highest priority from the multiple LCIDs if the data to be sent corresponds to multiple LCIDs, and determine the RTT timer configuration and / or retransmission timer configuration corresponding to the LCID with the highest priority based on the sixth configuration information, and use it as the second RTT timer and / or second retransmission timer; or, if the data to be sent corresponds to multiple LCIDs, determine the RTT timer configuration and / or retransmission timer corresponding to the multiple LCIDs based on the sixth configuration information, select the shortest RTT timer configuration and / or retransmission timer from the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs, and use it as the second RTT timer and / or second retransmission timer.

[0251] In some optional implementations, the sixth configuration information is configured through RRC signaling.

[0252] In some optional implementations, the processing unit 1102 is configured to start the second RTT timer after transmitting the data; and start the second retransmission timer if the second RTT timer times out.

[0253] In some optional embodiments, the apparatus further includes: a receiving unit 1103, configured to receive RRC dedicated signaling sent by a network device, wherein the RRC dedicated signaling is used to configure multiple sets of DRX parameters, each set of DRX parameters including at least one of the following: a DRX state timer (drx-onDurationTimer); a DRX slot offset (drx-SlotOffset); a DRX inactivity timer (drx-InactivityTimer); a downlink DRX retransmission timer (drx-RetransmissionTimerDL); an uplink DRX retransmission timer (drx-RetransmissionTimerUL); a DRX long cycle start offset (drx-LongCycleStartOffset); a DRX short cycle (drx-ShortCycle); a DRX short cycle cycle timer (drx-ShortCycleTimer); a downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL); an uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL).

[0254] In some optional implementations, the receiving unit 1103 is configured to receive second indication information sent by the network device, where the second indication information is used to indicate the use of the set of DRX parameters from the multiple sets of DRX parameters.

[0255] In some optional implementations, the second indication information is carried in DCI or MAC CE.

[0256] In some optional embodiments, the receiving unit 1103 is used to receive third indication information sent by the network device, where the third indication information is used to indicate the DRX time slot offset to be used; the determining unit 1101 is also used to determine the start time of the DRX state timer based on the third indication information.

[0257] In some optional embodiments, the determination unit 1101 is used to determine the target SFN and target subframe based on the DRX cycle and the DRX start offset; and determine, based on the third indication information, that the start time of the DRX state timer is N time slots shifted backward or forward from the start time of the target subframe within the target SFN, where N is determined based on the value of the DRX time slot offset.

[0258] In some optional implementations, the third indication information is carried in the DCI or the MAC CE.

[0259] In some optional implementations, the determining unit 1101 is configured to determine a first candidate start time of the DRX state timer based on the DRX cycle and the DRX start offset, and determine a second candidate start time and / or a third candidate start time based on the first candidate start time and the DRX cycle;

[0260] The receiving unit 1103 is configured to receive fourth indication information sent by the network device, where the fourth indication information is used to indicate a start time to be used from among the first candidate start time, the second candidate start time, and / or the third candidate start time;

[0261] The determining unit 1101 is configured to determine a start time of a DRX state timer based on the fourth indication information.

[0262] In some optional implementations, the second candidate start time is equal to the first candidate start time minus the duration of the DRX state timer, and the third candidate start time is equal to the first candidate start time plus the duration of the DRX state timer.

[0263] In some optional implementations, the determining unit 1101 is configured to determine a start time of the DRX state timer based on a DRX cycle and a DRX start offset, where the units of the DRX cycle and the DRX start offset are time slots, half time slots, or symbols.

[0264] In some optional embodiments, the unit of the DRX cycle and the DRX start offset is a time slot; the determination unit 1101 is used to determine the target SFN, the target subframe and the target time slot based on the DRX cycle and the DRX start offset; based on the DRX time slot offset and / or the DRX symbol offset, determine that the start time of the DRX state timer is the start time of the target time slot in the target subframe within the target SFN, offset backward or forward by N time slots and / or M symbols; or, based on the DRX symbol offset, the terminal device determines that the start time of the DRX state timer is the start time of the target half time slot in the target time slot in the target subframe within the target SFN, offset backward or forward by N time slots and / or M symbols, the target half time slot is indicated by RRC signaling, N is determined based on the value of the DRX time slot offset, and M is determined based on the value of the DRX symbol offset.

[0265] In some optional implementations, the determining unit 1101 is configured to determine the target SFN, target subframe, and target time slot based on the following formula:

[0266] For the case of DRX short cycle: [(SFN×10)×k+subframe number×k+slot number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle); or,

[0267] For the case of a long DRX cycle: [(SFN×10)×k+subframe number×k+slot number]modulo(drx-LongCycle)=drx-StartOffset;

[0268] Among them, SFN is the target SFN, subframe number is the target subframe number, slot number is the target time slot number, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

[0269] In some optional embodiments, the unit of the DRX cycle and the DRX start offset is half a time slot; the determination unit 1101 is used to determine the target SFN, target subframe, target time slot and target half time slot based on the DRX cycle and the DRX start offset; based on the DRX symbol offset, determine that the start time of the DRX state timer is M symbols offset backward or forward from the start time of the target half time slot in the target subframe within the target SFN, where M is determined based on the value of the DRX symbol offset.

[0270] In some optional implementations, the determining unit 1101 is configured to determine the target SFN, the target subframe, the target time slot, and the target half time slot based on the following formula:

[0271] For the case of a short DRX cycle: [(SFN×10)×k×2+subframe number×k×2+slot number×2+half slot number]modulo(drxCycle)=(drx-StartOffset)modulo(drxCycle); or,

[0272] For the case of a long DRX cycle: [(SFN×10)×k×2+subframe number×k×2+slot number×2+half slot number]modulo(drx-LongCycle)=drx-StartOffset;

[0273] Where SFN is the target SFN, subframe number is the target subframe number, slot number is the target slot number, half slot number is the target half slot number, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

[0274] In some optional embodiments, the units of the DRX cycle and the DRX start offset are symbols; the determination unit 1101 is used to determine the target SFN, target subframe, target time slot, target half time slot and target symbol based on the DRX cycle and the DRX start offset; based on the DRX symbol offset, determine that the start time of the DRX state timer is M symbols offset backward or forward from the start time of the target symbol in the target time slot in the target subframe within the target SFN, where M is determined based on the value of the DRX symbol offset.

[0275] In some optional implementations, the determining unit 1101 is configured to determine a target SFN, a target subframe, a target time slot, a target half time slot, and a target symbol based on the following formula:

[0276] For the case of a short DRX cycle: [(SFN×10)×k×14+subframe number×k×14+slot number×14+symbol number]modulo(drxCycle)=(drx-StartOffset)modulo(drxCycle); or,

[0277] For the case of a long DRX cycle: [(SFN×10)×k×14+subframe number×k×14+slot number×14+symbol number]modulo(drx-LongCycle)=drx-StartOffset;

[0278] Among them, SFN is the target SFN, subframe number is the target subframe number, slot number is the target time slot number, symbol number is the target symbol, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

[0279] In some optional embodiments, the receiving unit 1103 is used to receive seventh configuration information, and the seventh configuration information includes at least one SPS configuration and / or at least one CG configuration; wherein, at least part of the SPS configurations in the at least one SPS configuration includes fifth indication information, and the fifth indication information is used to indicate whether data reception on the SPS is allowed to be performed during the DRX non-activation time, or to indicate that data reception on the SPS is not allowed to be performed during the DRX non-activation time, or to indicate whether data reception on the SPS needs to be performed during the DRX activation time, or to indicate that data reception on the SPS needs to be performed during the DRX activation time; at least part of the CG configurations in the at least one CG configuration includes sixth indication information, and the sixth indication information is used to indicate whether data sending on the CG is allowed to be performed during the DRX non-activation time, or to indicate that data sending on the CG is not allowed to be performed during the DRX non-activation time, or to indicate whether data sending on the CG needs to be performed during the DRX activation time, or to indicate that data sending on the CG needs to be performed during the DRX activation time.

[0280] In some optional embodiments, if some of the SPS configurations in the at least one SPS configuration do not include the fifth indication information, then for the SPS configured by the partial SPS configuration, the terminal device allows data reception on the SPS during the DRX non-activation time and / or the terminal device does not need to perform data reception on the SPS during the DRX activation time; if some of the CG configurations in the at least one CG configuration do not include the sixth indication information, then for the CG configured by the partial CG configuration, the terminal device allows data sending on the CG during the DRX non-activation time and / or the terminal device does not need to perform data sending on the CG during the DRX activation time.

[0281] In some optional embodiments, if part of the SPS configurations in the at least one SPS configuration includes the fifth indication information, then for the SPS configured by the part of the SPS configuration, the terminal device determines based on the fifth indication information whether data reception on the SPS is allowed to be performed during the DRX non-activation time, or whether data reception on the SPS needs to be performed during the DRX activation time, or determines that data reception on the SPS is not allowed to be performed during the DRX non-activation time, or determines that data reception on the SPS needs to be performed during the DRX activation time; if part of the CG configuration in the at least one CG configuration includes the sixth indication information, then for the CG configured by the part of the CG configuration, the terminal device determines based on the sixth indication information whether data sending on the CG is allowed to be performed during the DRX non-activation time, or whether data sending on the CG needs to be performed during the DRX activation time, or determines that data sending on the CG is not allowed to be performed during the DRX non-activation time, or determines that data sending on the CG needs to be performed during the DRX activation time.

[0282] Those skilled in the art should understand that the relevant description of the above-mentioned parameter determination device in the embodiment of the present application can be understood with reference to the relevant description of the parameter determination method in the embodiment of the present application.

[0283] Figure 12 is a schematic diagram of a communication device 1200 provided in an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 1200 shown in Figure 12 includes a processor 1210, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0284] Optionally, as shown in FIG12 , the communication device 1200 may further include a memory 1220. The processor 1210 may call and execute a computer program from the memory 1220 to implement the method in the embodiment of the present application.

[0285] The memory 1220 may be a separate device independent of the processor 1210 , or may be integrated into the processor 1210 .

[0286] Optionally, as shown in FIG12 , the communication device 1200 may further include a transceiver 1230 , and the processor 1210 may control the transceiver 1230 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0287] The transceiver 1230 may include a transmitter and a receiver. The transceiver 1230 may further include an antenna, and the number of antennas may be one or more.

[0288] Optionally, the communication device 1200 may specifically be a network device in an embodiment of the present application, and the communication device 1200 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0289] Optionally, the communication device 1200 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 1200 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0290] Figure 13 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1300 shown in Figure 13 includes a processor 1310, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0291] Optionally, as shown in FIG13 , the chip 1300 may further include a memory 1320 , wherein the processor 1310 may call and execute a computer program from the memory 1320 to implement the method in the embodiment of the present application.

[0292] The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

[0293] Optionally, the chip 1300 may further include an input interface 1330. The processor 1310 may control the input interface 1330 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0294] Optionally, the chip 1300 may further include an output interface 1340. The processor 1310 may control the output interface 1340 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0295] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0296] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0297] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0298] FIG14 is a schematic block diagram of a communication system 1400 provided in an embodiment of the present application. As shown in FIG14 , the communication system 1400 includes a terminal device 1410 and a network device 1420 .

[0299] Among them, the terminal device 1410 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1420 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0300] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0301] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0302] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0303] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0304] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0305] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0306] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0307] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0308] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0309] The embodiment of the present application also provides a computer program.

[0310] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0311] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0312] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0313] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0314] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0315] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0316] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0317] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0318] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A parameter determination method, the method comprising: The terminal device determines a first discontinuous reception (DRX) parameter, where the first DRX parameter is a DRX parameter related to a hybrid automatic repeat request (HARQ) process, and the first DRX parameter is also related to data; The terminal device performs corresponding DRX operations based on the first DRX parameters.

2. The method according to claim 1, wherein The first DRX parameter includes a first round trip time (RTT) timer and / or a first retransmission timer, and the first RTT timer and / or the first retransmission timer are timers used by a downlink HARQ process.

3. The method according to claim 2, wherein: The terminal device determining the first DRX parameter includes: The terminal device receives first downlink control information DCI sent by the network device, where the first DCI is used to schedule downlink transmission of data, and the first DCI is further used to indicate a first RTT timer and / or a first retransmission timer used for the data in a HARQ process associated with the data; The terminal device determines the first RTT timer and / or the first retransmission timer based on the first DCI.

4. The method according to claim 3, wherein: The first DCI carries an index of the first RTT timer and / or the first retransmission timer; The terminal device determining the first RTT timer and / or the first retransmission timer based on the first DCI includes: The terminal device determines the first RTT timer and / or the first retransmission timer based on the index of the first RTT timer and / or the first retransmission timer, and first configuration information, wherein the first configuration information includes at least one RTT timer configuration and / or at least one retransmission timer configuration, wherein each RTT timer configuration is associated with an index, each retransmission timer configuration is associated with an index, or each RTT timer configuration and retransmission timer configuration are associated with a shared index.

5. The method according to claim 4, wherein The first configuration information is configured through radio resource control RRC signaling.

6. The method according to any one of claims 3 to 5, wherein The first DCI carries a logical channel identifier LCID list, where the LCID list is used to indicate a logical channel list of data scheduled by the first DCI and authorized to be transmitted.

7. The method according to claim 2, wherein: The terminal device determining the first DRX parameter includes: The terminal device determines the first RTT timer and / or first retransmission timer based on the semi-persistent scheduling SPS where the received data is located and the second configuration information, wherein the second configuration information includes the RTT timer configuration and / or retransmission timer configuration corresponding to at least one SPS.

8. The method according to claim 7, wherein: The second configuration information is configured through RRC signaling.

9. The method according to claim 2, wherein: The terminal device determining the first DRX parameter includes: The terminal device determines the first RTT timer and / or first retransmission timer based on the LCID corresponding to the received data and third configuration information, wherein the third configuration information includes an RTT timer configuration and / or a retransmission timer configuration corresponding to at least one LCID.

10. The method according to claim 9, wherein: The terminal device determines the first RTT timer and / or the first retransmission timer based on the LCID corresponding to the received data and the third configuration information, including: If the data received by the terminal corresponds to multiple LCIDs, the terminal selects the LCID with the highest priority from the multiple LCIDs, and determines the RTT timer configuration and / or retransmission timer configuration corresponding to the LCID with the highest priority based on the third configuration information, and uses it as the first RTT timer and / or first retransmission timer; or, If the data received by the terminal corresponds to multiple LCIDs, the terminal device determines the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs based on the third configuration information, and selects the shortest RTT timer configuration and / or retransmission timer from the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs, and uses it as the first RTT timer and / or first retransmission timer.

11. The method according to claim 9 or 10, wherein: The third configuration information is configured through RRC signaling.

12. The method according to any one of claims 2 to 11, wherein The terminal device performs a corresponding DRX operation based on the first DRX parameter, including: After receiving the data and completing positive acknowledgment ACK / negative acknowledgment NACK feedback for the data, the terminal device starts the first RTT timer; If the first RTT timer times out, the terminal device starts the first retransmission timer.

13. The method according to claim 1, wherein The first DRX parameter includes a second RTT timer and / or a second retransmission timer, and the second RTT timer and / or the second retransmission timer are timers used by an uplink HARQ process.

14. The method according to claim 13, wherein The terminal device determining the first DRX parameter includes: The terminal device receives a second DCI sent by the network device, where the second DCI is used to schedule uplink transmission of the data, and the second DCI is further used to indicate a second RTT timer and / or a second retransmission timer used for the data in a HARQ process associated with the data; The terminal device determines the second RTT timer and / or the second retransmission timer based on the DCI.

15. The method according to claim 14, wherein The second DCI carries an index of the second RTT timer and / or the second retransmission timer; The terminal device determining the second RTT timer and / or the second retransmission timer based on the second DCI includes: The terminal device determines the second RTT timer and / or the second retransmission timer based on the index of the second RTT timer and / or the second retransmission timer, and fourth configuration information, wherein the fourth configuration information includes at least one RTT timer configuration and / or at least one retransmission timer configuration, wherein each RTT timer configuration is associated with an index, each retransmission timer configuration is associated with an index, or each RTT timer configuration and retransmission timer configuration are associated with a shared index.

16. The method according to claim 15, wherein The fourth configuration information is configured through RRC signaling.

17. The method according to any one of claims 14 to 16, wherein The second DCI carries an LCID list, and the logical channel identifier list is used to indicate a list of logical channels for data scheduled by the second DCI and authorized to be transmitted.

18. The method according to claim 13, wherein The terminal device determining the first DRX parameter includes: The terminal device uses the RTT timer and / or retransmission timer selected by it as the second RTT timer and / or second retransmission timer.

19. The method according to claim 18, wherein The method further comprises: The terminal device indicates the index of the second RTT timer and / or the second retransmission timer selected by the terminal device to the network device through the first indication information.

20. The method according to claim 19, wherein The first indication information is carried in a media access control MAC control element CE or in a header of a MAC packet data unit PDU or in a header of a packet data convergence protocol PDCP PDU.

21. The method according to claim 13, wherein The terminal device determining the first DRX parameter includes: The terminal device determines the second RTT timer and / or second retransmission timer based on the configuration authorization CG where the data to be sent is located and the fifth configuration information, wherein the fifth configuration information includes at least one RTT timer configuration and / or retransmission timer configuration corresponding to the CG.

22. The method according to claim 21, wherein The fifth configuration information is configured through RRC signaling.

23. The method according to claim 13, wherein The terminal device determining the first DRX parameter includes: The terminal device determines the second RTT timer and / or second retransmission timer based on the LCID corresponding to the data to be sent and the sixth configuration information, wherein the sixth configuration information includes the RTT timer configuration and / or retransmission timer configuration corresponding to at least one LCID.

24. The method according to claim 23, wherein The terminal device determines the second RTT timer and / or the second retransmission timer based on the LCID corresponding to the data to be sent and the sixth configuration information, including: If the data that the terminal device needs to send corresponds to multiple LCIDs, the terminal selects the LCID with the highest priority from the multiple LCIDs, and determines the RTT timer configuration and / or retransmission timer configuration corresponding to the LCID with the highest priority based on the sixth configuration information, and uses it as the second RTT timer and / or second retransmission timer; or, If the data that the terminal device needs to send corresponds to multiple LCIDs, the terminal device determines the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs based on the sixth configuration information, and selects the shortest RTT timer configuration and / or retransmission timer from the RTT timer configurations and / or retransmission timers corresponding to the multiple LCIDs, and uses it as the second RTT timer and / or second retransmission timer.

25. The method according to claim 23 or 24, wherein The sixth configuration information is configured through RRC signaling.

26. The method according to any one of claims 13 to 25, wherein The terminal device performs a corresponding DRX operation based on the first DRX parameter, including: After the terminal device completes transmitting the data, starting the second RTT timer; If the second RTT timer times out, the terminal device starts the second retransmission timer.

27. The method according to any one of claims 1 to 26, wherein The method further comprises: The terminal device receives RRC dedicated signaling sent by the network device, where the RRC dedicated signaling is used to configure multiple sets of DRX parameters, each set of DRX parameters including at least one of the following: DRX state timer drx-onDurationTimer; DRX slot offset drx-SlotOffset; DRX inactivity timer drx-InactivityTimer; Downlink DRX retransmission timer drx-RetransmissionTimerDL; Uplink DRX retransmission timer drx-RetransmissionTimerUL; DRX long cycle start offset drx-LongCycleStartOffset; DRX short cycle drx-ShortCycle; DRX short cycle timer drx-ShortCycleTimer; Downlink DRX HARQ RTT timer drx-HARQ-RTT-TimerDL; Uplink DRX HARQ RTT timer drx-HARQ-RTT-TimerUL.

28. The method according to claim 27, wherein The method further comprises: The terminal device receives second indication information sent by the network device, where the second indication information is used to indicate the use of the set of DRX parameters from the multiple sets of DRX parameters.

29. The method according to claim 28, wherein The second indication information is carried in the DCI or the MAC CE.

30. The method according to any one of claims 1 to 29, wherein The method further comprises: The terminal device receives third indication information sent by the network device, where the third indication information is used to indicate a used DRX time slot offset; The terminal device determines the start time of the DRX state timer based on the third indication information.

31. The method according to claim 30, wherein The terminal device determines, based on the third indication information, a start time of the DRX state timer, including: The terminal device determines a target SFN and a target subframe based on a DRX cycle and a DRX start offset; The terminal device determines, based on the third indication information, that the start time of the DRX state timer is N time slots shifted backward or forward from the start time of the target subframe within the target SFN, where N is determined based on the value of the DRX time slot offset.

32. The method according to claim 30 or 31, wherein The third indication information is carried in the DCI or the MAC CE.

33. The method according to any one of claims 1 to 29, wherein The method further comprises: The terminal device determines a first candidate start time of the DRX state timer based on the DRX cycle and the DRX start offset, and determining a second candidate start time and / or a third candidate start time based on the first candidate start time and the DRX cycle; The terminal device receives fourth indication information sent by the network device, where the fourth indication information is used to indicate a start time to be used from the first candidate start time, the second candidate start time, and / or the third candidate start time; The terminal device determines the start time of the DRX state timer based on the fourth indication information.

34. The method according to claim 33, wherein The second candidate start time is equal to the first candidate start time minus the duration of the DRX state timer, and the third candidate start time is equal to the first candidate start time plus the duration of the DRX state timer.

35. The method according to any one of claims 1 to 34, wherein The method further comprises: The terminal device determines the start time of the DRX state timer based on the DRX cycle and the DRX start offset, and the units of the DRX cycle and the DRX start offset are time slots, half time slots or symbols.

36. The method according to claim 35, wherein The units of the DRX cycle and the DRX start offset are time slots; The terminal device determines a start time of a DRX state timer based on a DRX cycle and a DRX start offset, including: The terminal device determines a target SFN, a target subframe, and a target time slot based on a DRX cycle and a DRX start offset; The terminal device determines, based on the DRX slot offset and / or DRX symbol offset, that the start time of the DRX state timer is a start time of the target slot in the target subframe in the target SFN, which is offset backward or forward by N slots and / or M symbols; or, based on the DRX symbol offset, the terminal device determines that the start time of the DRX state timer is a start time of the target half slot in the target slot in the target subframe in the target SFN, which is offset backward or forward by N slots and / or M symbols, the target half slot being indicated by RRC signaling, N being determined based on the value of the DRX slot offset, and M being determined based on the value of the DRX symbol offset.

37. The method according to claim 36, wherein The terminal device determines a target SFN, a target subframe, and a target time slot based on a DRX cycle and a DRX start offset, including: The terminal device determines the target SFN, target subframe, and target time slot based on the following formula: For the case of DRX short cycle: [(SFN×10)×k+subframe number×k+slot number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle); or, For the case of a long DRX cycle: [(SFN×10)×k+subframe number×k+slot number]modulo(drx-LongCycle)=drx-StartOffset; Among them, SFN is the target SFN, subframe number is the target subframe number, slot number is the target time slot number, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

38. The method of claim 35, wherein: The unit of the DRX cycle and the DRX start offset is half a time slot; The terminal device determines a start time of a DRX state timer based on a DRX cycle and a DRX start offset, including: The terminal device determines a target SFN, a target subframe, a target time slot, and a target half time slot based on a DRX cycle and a DRX start offset; Based on the DRX symbol offset, the terminal device determines that the start time of the DRX state timer is M symbols offset backward or forward from the start time of the target half time slot in the target time slot in the target subframe within the target SFN, where M is determined based on the value of the DRX symbol offset.

39. The method according to claim 38, wherein The terminal device determines a target SFN, a target subframe, a target time slot, and a target half time slot based on a DRX cycle and a DRX start offset, including: The terminal device determines the target SFN, target subframe, target time slot, and target half time slot based on the following formula: For the case of a short DRX cycle: [(SFN×10)×k×2+subframe number×k×2+slot number×2+half slot number]modulo(drxCycle)=(drx-StartOffset)modulo(drxCycle); or, For the case of a long DRX cycle: [(SFN×10)×k×2+subframe number×k×2+slot number×2+half slot number]modulo(drx-LongCycle)=drx-StartOffset; Where SFN is the target SFN, subframe number is the target subframe number, slot number is the target time slot number, half slot number is the target half time slot number, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

40. The method of claim 35, wherein The units of the DRX cycle and the DRX start offset are symbols; The terminal device determines a start time of a DRX state timer based on a DRX cycle and a DRX start offset, including: The terminal device determines a target SFN, a target subframe, a target time slot, a target half time slot, and a target symbol based on a DRX cycle and a DRX start offset; Based on the DRX symbol offset, the terminal device determines that the start time of the DRX state timer is M symbols offset backward or forward from the start time of the target symbol in the target time slot in the target subframe in the target SFN, where M is determined based on the value of the DRX symbol offset.

41. The method according to claim 40, wherein The terminal device determines a target SFN, a target subframe, a target time slot, a target half time slot, and a target symbol based on a DRX cycle and a DRX start offset, including: The terminal device determines the target SFN, target subframe, target time slot, target half time slot, and target symbol based on the following formula: For the case of a short DRX cycle: [(SFN×10)×k×14+subframe number×k×14+slot number×14+symbol number]modulo(drxCycle)=(drx-StartOffset)modulo(drxCycle); or, For the case of a long DRX cycle: [(SFN×10)×k×14+subframe number×k×14+slot number×14+symbol number]modulo(drx-LongCycle)=drx-StartOffset; Among them, SFN is the target SFN, subframe number is the target subframe number, slot number is the target time slot number, symbol number is the target symbol, drx-ShortCycle is the DRX short cycle, drx-LongCycle is the DRX long cycle, drx-StartOffset is the DRX start offset, modulo represents the remainder operation, and k is an integer.

42. The method according to any one of claims 1 to 41, wherein The method further comprises: The terminal device receives seventh configuration information, where the seventh configuration information includes at least one SPS configuration and / or at least one CG configuration; wherein, At least some of the at least one SPS configurations include fifth indication information, where the fifth indication information is used to indicate whether data reception on the SPS is allowed during the DRX inactive time, or to indicate that data reception on the SPS is not allowed during the DRX inactive time, or to indicate whether data reception on the SPS needs to be performed during the DRX active time, or to indicate that data reception on the SPS needs to be performed during the DRX active time; At least part of the CG configurations in the at least one CG configuration includes sixth indication information, and the sixth indication information is used to indicate whether data sending on the CG is allowed within the DRX non-activation time, or to indicate that data sending on the CG is not allowed within the DRX non-activation time, or to indicate whether data sending on the CG needs to be performed within the DRX activation time, or to indicate that data sending on the CG needs to be performed within the DRX activation time.

43. The method according to claim 42, wherein If some SPS configurations in the at least one SPS configuration do not include the fifth indication information, then, for the SPS configured by the part of the SPS configuration, the terminal device is allowed to perform data reception on the SPS during the DRX inactive time and / or the terminal device does not need to perform data reception on the SPS during the DRX active time; If some of the CG configurations in the at least one CG configuration do not include the sixth indication information, then for the CG configured by the partial CG configuration, the terminal device is allowed to perform data sending on the CG during the DRX non-activation time and / or the terminal device does not need to perform data sending on the CG during the DRX activation time.

44. The method of claim 42, wherein: If some SPS configurations in the at least one SPS configuration include the fifth indication information, then, for the SPS configured by the part of the SPS configuration, the terminal device determines, based on the fifth indication information, whether data reception on the SPS is allowed to be performed during the DRX inactive time, or whether data reception on the SPS needs to be performed during the DRX active time, or determines that data reception on the SPS is not allowed to be performed during the DRX inactive time, or determines that data reception on the SPS needs to be performed during the DRX active time; If part of the CG configurations in the at least one CG configuration includes the sixth indication information, then for the CG configured by the part of the CG configuration, the terminal device determines based on the sixth indication information whether data sending on the CG is allowed to be performed within the DRX non-activation time, or whether data sending on the CG needs to be performed within the DRX activation time, or determines that data sending on the CG is not allowed to be performed within the DRX non-activation time, or determines that data sending on the CG needs to be performed within the DRX activation time.

45. A parameter determination device, applied to a terminal device, comprising: a determining unit, configured to determine a first DRX parameter, where the first DRX parameter is a DRX parameter related to the HARQ process and is also related to data; A processing unit is configured to perform corresponding DRX operations based on the first DRX parameters.

46. ​​A terminal device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 44.

47. A chip comprising: A processor, configured to call and execute a computer program from a memory, so that a device equipped with the chip executes a method according to any one of claims 1 to 44.

48. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 44.

49. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 44.

50. A computer program causing a computer to perform the method of any one of claims 1 to 44.