CN116963104A

CN116963104A - DRX parameter configuration method, device, communication equipment and storage medium

Info

Publication number: CN116963104A
Application number: CN202210399923.3A
Authority: CN
Inventors: 应祚龙; 孙晓东; 曾超君; 李东儒; 陈晓航; 尤花征; 李娜; 蒋露
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-04-15
Filing date: 2022-04-15
Publication date: 2023-10-27

Abstract

The application discloses a DRX parameter configuration method, a device, communication equipment and a storage medium, which belong to the technical field of wireless communication, and the DRX parameter configuration method of the embodiment of the application comprises the following steps: the terminal receives first information sent by network side equipment; the terminal determines DRX parameters based on the first information; the DRX parameters include non-integer DRX cycle parameters and/or DRX cycle sequences. By configuring the non-integer DRX cycle parameter and/or the DRX cycle sequence for the terminal, the time difference between the arrival time of the service frame and the starting time of the DRX activation period can be reduced, so that the service transmission delay is reduced, the redundant monitoring time of the terminal before the service frame arrives can be shortened, and the power consumption of the terminal is reduced.

Description

DRX parameter configuration method, device, communication equipment and storage medium

Technical Field

The application belongs to the technical field of wireless communication, and particularly relates to a DRX parameter configuration method, a device, communication equipment and a storage medium.

Background

Discontinuous reception (Discontinuous Reception, DRX), which is an operation mode that a terminal (also called User Equipment, UE) turns on the receiver to enter an active state only for necessary time to receive downlink data and signaling, and turns off the receiver to enter a sleep state at other times to stop receiving downlink data and signaling, saves power consumption of the terminal.

Currently, configurable Connected mode DRX (CDRX) long period values are 10, 20, 32, 40ms, etc., and short period values are 2, 3, 5, 6, 7, 8, 10, 14, 16, 20, 30, 32, 35ms, etc., whichever CDRX period value only supports an integer multiple of 1 ms. For Extended real (XR) traffic, typical XR Downlink (DL) frame rates are 30FPS, 60FPS, 90FPS, 120FPS (FPS refers to frames per second), and corresponding frame periods are 33.33ms, 16.67ms, 11.11ms, 8.33ms, respectively. Thus, whichever period is selected from the currently available period values of the CDRX, it cannot be exactly the same as the XR DL frame arrival time, and such mismatch will result in loss of XR capacity, increased latency and increased terminal power consumption.

Disclosure of Invention

The embodiment of the application provides a DRX parameter configuration method, a device, communication equipment and a storage medium, which can solve the problem that the DRX period is not matched with the XR DL frame arrival time.

In a first aspect, an embodiment of the present application provides a method for configuring DRX parameters, including:

the terminal receives first information sent by network side equipment;

the terminal determines DRX parameters based on the first information; the DRX parameters include non-integer DRX cycle parameters and/or DRX cycle sequences.

In a second aspect, an embodiment of the present application provides a DRX parameter configuration method, including:

the network side equipment determines DRX parameters of a terminal, wherein the DRX parameters comprise non-integer DRX cycle parameters and/or DRX cycle sequences;

and the network side equipment sends first information to the terminal, wherein the first information is used for indicating the DRX parameter.

In a third aspect, an embodiment of the present application provides a DRX parameter configuration apparatus, applied to a terminal, including:

the first receiving module is used for receiving first information sent by the network side equipment;

a first determining module, configured to determine a DRX parameter based on the first information; the DRX parameters include non-integer DRX cycle parameters and/or DRX cycle sequences.

In a fourth aspect, an embodiment of the present application provides a DRX parameter configuration apparatus, which is applied to a network side device, including:

a second determining module, configured to determine a DRX parameter of the terminal, where the DRX parameter includes a non-integer DRX cycle parameter and/or a DRX cycle sequence;

and the second sending module is used for sending first information to the terminal, wherein the first information is used for indicating the DRX parameter.

In a fifth aspect, an embodiment of the present application provides a terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implements the method according to the first aspect.

In a sixth aspect, an embodiment of the present application provides a terminal, including a processor and a communication interface, where the communication interface is configured to: receiving first information sent by network side equipment; the processor is configured to: determining a DRX parameter based on the first information; the DRX parameters include non-integer DRX cycle parameters and/or DRX cycle sequences.

In a seventh aspect, an embodiment of the present application provides a network side device, where the network side device includes a processor and a memory, where the memory stores a program or an instruction executable on the processor, and where the program or the instruction is executed by the processor to implement the method according to the second aspect.

In an eighth aspect, an embodiment of the present application provides a network side device, including a processor and a communication interface, where the processor is configured to: determining DRX parameters of a terminal, wherein the DRX parameters comprise non-integer DRX cycle parameters and/or DRX cycle sequences; the communication interface is used for: and sending first information to the terminal, wherein the first information is used for indicating the DRX parameter.

In a ninth aspect, an embodiment of the present application provides a DRX parameter configuration system, including: a terminal and a network side device, wherein the terminal is used for executing the DRX parameter configuration method according to the first aspect, and the network side device is used for executing the DRX parameter configuration method according to the second aspect.

In a tenth aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement a method as described in the first aspect, or implement a method as described in the second aspect.

In an eleventh aspect, embodiments of the present application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to execute a program or instructions to implement a method according to the first aspect, or to implement a method according to the second aspect.

In a twelfth aspect, embodiments of the present application provide a computer program/program product stored in a storage medium, the computer program/program product being executable by at least one processor to implement a method as described in the first aspect, or to implement a method as described in the second aspect.

In the embodiment of the application, the time difference between the arrival time of the service frame and the starting time of the DRX activation period can be reduced by configuring the non-integer DRX cycle parameter and/or the DRX cycle sequence for the terminal, so that the service transmission delay is reduced, the redundant monitoring time of the terminal before the service frame arrives can be shortened, and the power consumption of the terminal is reduced.

Drawings

Fig. 1 is a block diagram of a wireless communication system provided by an embodiment of the present application;

fig. 2 is a schematic diagram of a DRX cycle provided by an embodiment of the present application;

fig. 3 is a schematic diagram of a DRX cycle configuring an inactivity timer according to an embodiment of the present application;

fig. 4 is a schematic flow chart of a DRX parameter configuration method according to an embodiment of the present application;

fig. 5 is a second flowchart of a DRX parameter configuration method according to an embodiment of the present application;

fig. 6 is one implementation schematic diagram of a DRX parameter configuration method according to an embodiment of the present application;

fig. 7 is a second schematic implementation diagram of a DRX parameter configuration method according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a DRX parameter configuration apparatus according to an embodiment of the present application;

fig. 9 is a second schematic structural diagram of a DRX parameter configuration apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 11 is a schematic diagram of a hardware structure of a terminal according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a network side device according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the "first" and "second" distinguishing between objects generally are not limited in number to the extent that the first object may, for example, be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 is a block diagram of a wireless communication system according to an embodiment of the present application, and as shown in fig. 1, the wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include a base station, a WLAN access point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiment of the present application, only a base station in the NR system is described as an example, and the specific type of the base station is not limited.

In order to better understand the technical solutions of the embodiments of the present application, the following describes technical contents related to the embodiments of the present application.

1. XR traffic.

XR traffic belongs to quasi-periodic traffic, that is, traffic packets arrive at equal intervals, and the intervals are small floating point numbers (non-positive integers). Typical XR DL frame rates are 30FPS, 60FPS, 90FPS, 120FPS (FPS refers to frames per second) with corresponding frame periods of 33.33ms, 16.67ms, 11.11ms, 8.33ms, respectively.

2. RRC Connected DRX (CDRX).

Fig. 2 is a schematic diagram of a DRX cycle provided in an embodiment of the present application, as shown in fig. 2, one basic DRX cycle (DRX cycle) is composed of an active period (On Duration) and a sleep period (DRX off or opportunity for DRX), and in the time of "On Duration", the terminal listens to a target channel/signal; during the "DRX off" time, the terminal does not monitor the target channel/signal to save power consumption.

Fig. 3 is a schematic DRX cycle diagram of configuring an inactivity timer according to an embodiment of the present application, where, as shown in fig. 3, the network configures an inactivity timer, and if a new physical downlink control channel (Physical Downlink Control Channel, PDCCH) is received in an on duration, the inactivity timer is started or restarted to extend the duration of the terminal listening to the PDCCH.

3. DRX parameters.

Typical DRX timer and cycle configuration parameters are shown in table 1 below.

Table 1 DRX timer and period configuration parameters

The DRX parameter configuration method provided by the embodiment of the present application is described in detail below by referring to the accompanying drawings through some embodiments and application scenarios thereof.

Fig. 4 is a flowchart of a method for configuring DRX parameters according to an embodiment of the present application, as shown in fig. 4, where the method includes the following steps:

step 400, the terminal receives first information sent by the network side device.

Step 401, the terminal determines a DRX parameter based on first information; the DRX parameters include non-integer DRX cycle parameters and/or DRX cycle sequences.

Optionally, the DRX cycle parameter may include a DRX cycle value (DRX cycle) and/or a DRX start offset value (DRX start offset). For example, the non-integer DRX cycle parameter may include a non-integer DRX cycle value and/or a non-integer DRX start position offset value; the integer DRX cycle parameter may include an integer DRX cycle value and/or an integer DRX start position offset value.

Optionally, in the embodiment of the present application, the non-integer DRX cycle parameter configured by the network side device (e.g., the base station) to the terminal may be a non-integer DRX cycle value, or may also be a non-integer DRX start position offset value, or may also be a non-integer DRX cycle value and a non-integer DRX start position offset value. For example, the network side device may configure the terminal with a non-integer DRX cycle value of any non-integer value, such as 8.5ms, 16.5ms, 16.67ms, 9.5ms, etc.

Optionally, at least 2 DRX cycle values may be included in one DRX cycle sequence. For example, a certain DRX cycle sequence may be denoted as {16ms,17ms }.

It should be noted that, in each embodiment of the present application, for convenience of description, any DRX cycle sequence written not only represents a specific certain DRX cycle value arrangement sequence, but also includes a combination of all the arrangement sequences, which is not described in detail later. For example, a certain DRX cycle sequence {16ms,17ms }, which may represent a cycle sequence of three different DRX cycle value arrangements of {16ms,17ms }, {17ms,16ms }, is written.

Optionally, the network side device may send first information to the terminal after determining the DRX parameter configured for the terminal, where the first information may be used to indicate the DRX parameter of the terminal, so that the terminal may determine the DRX parameter based on the first information after receiving the first information. For example, the first information indicates that the non-integer DRX cycle value configured by the network side device to the terminal is 16.5ms, and the terminal may use the DRX cycle value of 16.5ms for discontinuous reception.

Optionally, in case the DRX parameter comprises a DRX cycle sequence, after determining the DRX parameter, the method may further comprise: the terminal sequentially and circularly applies each DRX cycle value in the determined DRX cycle sequence on a time axis. For example, if the DRX cycle sequence determined by the terminal based on the first information is {16ms,17ms }, the terminal may sequentially apply three DRX cycle values of 16ms,17ms, and 17ms in a cyclic manner on the time axis, for example, the first DRX cycle uses a DRX cycle value of 16ms, the second DRX cycle uses a DRX cycle value of 17ms, the third DRX cycle uses a DRX cycle value of 17ms, the fourth DRX cycle uses a DRX cycle value of 16ms, and so on, which will not be described herein.

Optionally, the first information may include at least one of:

(1) One or more non-integer DRX cycle parameters.

Optionally, the first information sent by the network side device to the terminal may include one or more non-integer DRX cycle parameters, so that the terminal adapts to different service periods. For example, the first information may include a plurality of non-integer DRX cycle values corresponding to different XR service periods, and the terminal may select an appropriate non-integer DRX cycle value according to the different XR service periods, so as to reduce delay and power consumption of the terminal as much as possible.

(2) One or more DRX cycle sequences.

Optionally, the first information sent by the network side device to the terminal may include one or more DRX cycle sequences, so that the terminal adapts to different service periods. For example, the first information may include a plurality of DRX cycle sequences corresponding to different XR service periods, and the terminal may select an appropriate DRX cycle sequence according to the different XR service periods, so as to reduce delay and power consumption of the terminal as much as possible.

(3) And the first indication information is used for determining the parameter adjustment quantity, and the non-integer DRX cycle parameter is determined according to the sum of the integer DRX cycle parameter and the parameter adjustment quantity.

Optionally, the first information sent by the network side device to the terminal may indicate a parameter adjustment amount, where a value of the parameter adjustment amount may be any value greater than 0 and less than 1, and the terminal may determine the actually applied non-integer DRX cycle parameter according to a sum of the configured integer DRX cycle parameter and the parameter adjustment amount. For example, actually applied DRX cycle value=configured DRX cycle value (legacy parameter, integer) +parameter adjustment amount.

Alternatively, the integer-type DRX cycle parameter may be preconfigured, or may be indicated in the first information, or may be otherwise configured, without limitation.

Optionally, the first indication information may include at least one of: a candidate set of parameter adjustment amounts; and a candidate set of second scaling factors, wherein the parameter adjustment amount is determined according to the inverse of the second scaling factors. That is, there may be various ways to indicate the parameter adjustment amount, for example, the first information may directly indicate a candidate set of the parameter adjustment amount, or the first information may also indicate a candidate set of a scaling factor (i.e., the second scaling factor may be any integer greater than 1) where the parameter adjustment amount is determined according to the reciprocal of the scaling factor. For example, assuming that the second scaling factor is 3, the amount of parameter adjustment actually applied may be 1/3.

Alternatively, the candidate set of parameter adjustment amounts may comprise parameter adjustment amounts of one or more candidates.

Alternatively, the candidate set of parameter adjustment amounts may include one or more of 0.11ms, 0.125ms, 0.25ms, 0.33ms, 0.5ms, 0.67 ms. For example, the terminal may select a suitable value from the candidate set of parameter adjustment amounts according to different XR service periods, so as to reduce delay and terminal power consumption as much as possible.

Optionally, the candidate set of second scaling factors may comprise one or more candidate second scaling factors.

Alternatively, the candidate set of second scaling factors may comprise one or more of 3, 6, 9. For example, the terminal may select an appropriate value from the candidate set of the second scaling factor according to different XR service periods, so as to reduce the delay and the power consumption of the terminal as much as possible.

Alternatively, the parameter adjustment amount may be associated with a subcarrier spacing (SCS). For example, the first information may indicate the subcarrier interval associated with the parameter adjustment amount while indicating the parameter adjustment amount, and the terminal may determine which parameter adjustment amount is used to obtain the non-integer DRX cycle parameter in which subcarrier interval according to the association relationship between the parameter adjustment amount and the subcarrier interval.

Optionally, the network side device may determine the parameter adjustment amount configured for the terminal according to the subcarrier spacing. For example, a plurality of different parameter adjustment amounts are configured for a plurality of different subcarrier spacings.

Alternatively, in the case where the subcarrier spacing is equal to 30kHz, the parameter adjustment amount may be 0.5ms.

Alternatively, in the case where the subcarrier spacing is equal to 60kHz, the parameter adjustment amount may be 0.25ms.

Alternatively, in the case where the subcarrier spacing is equal to 120kHz, the parameter adjustment amount may be 0.125ms.

(4) And second indication information for determining the first scaling factor, wherein the non-integer DRX cycle parameter is determined according to a ratio between the integer DRX cycle parameter and the first scaling factor.

Optionally, the first information sent by the network side device to the terminal may indicate a first scaling factor, where the value of the first scaling factor may be any integer greater than 1, and the terminal may determine the actually applied non-integer DRX cycle parameter according to a ratio between the configured integer DRX cycle parameter and the first scaling factor.

For example, actually applied DRX cycle value = configured DRX cycle value/first scaling factor.

For example, the DRX start position offset value of actual application = configured DRX start position offset value/first scaling factor.

(5) The first m-1 DRX period values in the target DRX period sequence and the sum of all the DRX period values in the target DRX period sequence, wherein m is the number of the DRX period values in the target DRX period sequence.

Alternatively, the target DRX cycle sequence may refer to any one of the DRX cycle sequences indicated in the first information.

For example, when indicating a certain DRX cycle sequence, the network side device may assume that the number of DRX cycle values in the DRX cycle sequence is m, the first m-1 DRX cycle values in the DRX cycle sequence may be explicitly configured in the first information, and the sum X of each DRX cycle value in the DRX cycle sequence, and the terminal may subtract, according to the indication in the first information, the sum of the first m-1 DRX cycle values in the DRX cycle sequence from X, to obtain the last DRX cycle value in the DRX cycle sequence, thereby obtaining the complete DRX cycle sequence.

(6) One or more indexes for indicating a target DRX cycle sequence, each index for indicating one DRX cycle sequence.

Optionally, the first information may include one or more indexes for indicating the target DRX cycle sequence, each index may be used to indicate one DRX cycle sequence, for example, the DRX cycle sequence associated with each index may be predefined, and then, when indicating a certain DRX cycle sequence, the network side device may configure the one or more indexes in the first information to indicate.

Optionally, when multiple indexes are configured to indicate a target DRX cycle sequence, the terminal may cascade-combine multiple DRX cycle sequences corresponding to the multiple indexes according to a certain order to obtain the complete target DRX cycle sequence.

For example, the first information indicates a target DRX cycle sequence by using 3 indexes index1, index2, and index3, where the DRX cycle sequence corresponding to index1 is { a, a, c }, the DRX cycle sequence corresponding to index2 is { d, e, f }, and the DRX cycle sequence corresponding to index3 is { g, h, i, j }, and the terminal may concatenate the three DRX cycle sequences in order to obtain the target DRX cycle sequence indicated by the first information as { a, a, c, d, e, f, g, h, i, j }.

Optionally, a DRX cycle sequence pattern (pattern) may be predefined, where each DRX cycle sequence pattern is used to indicate one DRX cycle sequence, each DRX cycle sequence pattern corresponds to an index, and when indicating a certain DRX cycle sequence, the network side device may configure one or more indexes in the first information to indicate the DRX cycle sequence pattern, and further indicate the DRX cycle sequence.

Optionally, when multiple indexes are configured to indicate a target DRX cycle sequence, the terminal may concatenate and combine multiple DRX cycle sequence patterns corresponding to the multiple indexes according to a certain order to obtain the complete target DRX cycle sequence.

For example, the first information indicates a DRX cycle sequence by using 3 indexes index1, index2, and index3, where the DRX cycle sequence pattern 1= { a, a, c } corresponding to index1, the DRX cycle sequence pattern 2= { d, e, f } corresponding to index2, and the DRX cycle sequence pattern 3= { g, h, i, j } corresponding to index3, and the terminal may concatenate the three patterns in order to obtain the DRX cycle sequence { a, a, c, d, e, f, g, h, i, j } indicated by the first information.

Optionally, each DRX cycle sequence pattern is used to indicate a DRX cycle sequence, each pattern may include a size of an i-th DRX cycle value in the pattern, and/or each pattern may indicate a number of times or a position where the i-th DRX cycle value in the pattern occurs, where i is a total number of DRX cycle values from 1 to the pattern.

For example, if a pattern indicates that the 1 st DRX cycle value is 16ms, the 2 nd DRX cycle value is 17ms, and the 3 rd DRX cycle value is 17ms in the pattern, the terminal may determine the pattern= {16ms,17ms }.

For example, if a pattern indicates that the 1 st DRX cycle value in the pattern is 16ms, the 2 nd DRX cycle value is 17ms, and occurs 2 times, the terminal may determine that the pattern= {16ms,17ms }.

Optionally, the DRX cycle sequence may include a first DRX cycle sequence and/or a second DRX cycle sequence;

the DRX cycle values in the first DRX cycle sequence are all positive integer values, and at least two DRX cycle values are different;

at least one DRX cycle value in the second DRX cycle sequence is a non-integer number, and at least two DRX cycle values are different.

Optionally, the first information sent by the network side device to the terminal may indicate one or more DRX cycle sequences, where the DRX cycle sequences may include different types, for example, the first DRX cycle sequence and/or the second DRX cycle sequence.

Alternatively, there may be one or more first DRX cycle sequences, where each DRX cycle value in the first DRX cycle sequence is a positive integer value, and at least two DRX cycle values are different. For example, the first DRX cycle sequence may be {16ms,17ms }, {16ms,18 ms }, etc.

Alternatively, there may be one or more second DRX cycle sequences, where at least one DRX cycle value in each second DRX cycle sequence is a non-integer value, and at least two DRX cycle values are different. For example, the second DRX cycle sequence may be {16.5ms, 17ms }, {16ms,16.5ms,17.5ms }, etc.

Optionally, the DRX cycle sequence is associated with a traffic downlink frame rate.

For example, typical XR traffic downstream frame rates are 30FPS, 60FPS, 90FPS, 120FPS (FPS refers to how many frames per second), with corresponding frame periods of 33.33ms, 16.67ms, 11.11ms, 8.33ms, respectively.

Alternatively, the DRX cycle sequence may be associated with an XR traffic downlink frame rate. For example, the first information may indicate the DRX cycle sequence and indicate the XR service downlink frame rate associated with the DRX cycle sequence, and the terminal may determine which DRX cycle sequence is used in which case of the XR service downlink frame rate according to the association relationship between the DRX cycle sequence and the XR service downlink frame rate.

Optionally, the network side device may determine the DRX cycle sequence configured for the terminal according to the XR service downlink frame rate. For example, a plurality of different DRX cycle sequences are configured for a plurality of different XR traffic downlink frame rates.

Optionally, the number of DRX cycle values in the DRX cycle sequence is associated with the traffic downlink frame rate, i.e. the number of DRX cycle values may be different in different DRX cycle sequences corresponding to different traffic downlink frame rates.

For example, in case of a traffic downlink frame rate of 30FPS or 60FPS or 120FPS, the number of DRX cycle values in the DRX cycle sequence may be an integer multiple of 3.

For example, in the case of a traffic downlink frame rate of 90FPS, the number of DRX cycle values in the DRX cycle sequence may be an integer multiple of 9.

Alternatively, the sum of the individual DRX cycle values in the DRX cycle sequence may be a specified value associated with the traffic downlink frame rate.

For example, the DRX cycle sequence is { x } ₁ ,…,x _m }，x ₁ +…+x _m X, where m is the number of DRX cycle values in the DRX cycle sequence, and the value of X is related to the traffic downlink frame rate. For example, the traffic downlink frame rate is 60fps, and x is 50ms; the traffic downlink frame rate is 90fps, x is 100ms, etc.

Alternatively, the DRX cycle values in the DRX cycle sequence may includeOne or more of the following; wherein (1)>Indicating a rounding down of the first value L, +.>The first value L is represented by rounding up, and is determined according to the traffic downlink frame rate.

For example, the DRX cycle value in the DRX cycle sequence is denoted as W, where W satisfies:or-> Wherein L is a value related to XR service downlink frame rate, e.g. XR service downlink frame rate is 60FPS, L can be 16.67%>16->The DRX cycle value in the DRX cycle sequence may take the value of 14ms, 15ms, 16ms, 17ms, 18ms, 19ms, etc. for 17.

Alternatively, the first value L may comprise one or more of 16.67, 8.33, 33.33, 11.11.

Optionally, the network side device may determine DRX cycle values in the DRX cycle sequence configured for the terminal according to the service downlink frame rate, for example, calculate different L values according to different XR service downlink frame rates, and then calculate the L values according to the XR service downlink frame ratesOr (b) Respective DRX cycle values in the DRX cycle sequence are determined. For example, for a frame rate of 60FPS, the DRX cycle sequence may be {16ms,17ms } or {16ms,18 ms }, etc.

Fig. 5 is a second flowchart of a DRX parameter configuration method according to an embodiment of the present application, as shown in fig. 5, where the method includes the following steps:

step 500, the network side device determines a DRX parameter of the terminal, where the DRX parameter includes a non-integer DRX cycle parameter and/or a DRX cycle sequence.

In step 501, the network side device sends first information to the terminal, where the first information is used to indicate the DRX parameter.

Optionally, the network side device may send first information to the terminal after determining the DRX parameter configured for the terminal, where the first information may be used to indicate the DRX parameter of the terminal, so that the terminal may determine the DRX parameter based on the first information after receiving the first information.

For example, the first information indicates that the non-integer DRX cycle value configured by the network side device to the terminal is 16.5ms, and the terminal may use the DRX cycle value of 16.5ms for discontinuous reception.

For example, the first information indicates that the DRX cycle sequence configured by the network side device to the terminal is {16ms,17ms }, and the terminal may sequentially apply each DRX cycle value in the DRX cycle sequence in a cyclic manner on a time axis to perform discontinuous reception, which is specifically referred to the method embodiment on the terminal side and will not be described herein.

Optionally, the first information may include at least one of:

(1) One or more non-integer DRX cycle parameters.

Optionally, the first information sent by the network side device to the terminal may include one or more non-integer DRX cycle parameters, so that the terminal adapts to different service periods. For example, the first information may include a plurality of non-integer DRX cycle values corresponding to different XR service periods, so that the terminal may select an appropriate non-integer DRX cycle value according to the different XR service periods, so as to reduce delay and power consumption of the terminal as much as possible.

(2) One or more DRX cycle sequences.

Optionally, the first information sent by the network side device to the terminal may include one or more DRX cycle sequences, so that the terminal adapts to different service periods. For example, the first information may include a plurality of DRX cycle sequences corresponding to different XR service periods, so that the terminal may select an appropriate DRX cycle sequence according to the different XR service periods, so as to reduce delay and power consumption of the terminal as much as possible.

Alternatively, the candidate set of parameter adjustment amounts may include one or more of 0.11ms, 0.125ms, 0.25ms, 0.33ms, 0.5ms, 0.67 ms.

Alternatively, the candidate set of second scaling factors may comprise one or more of 3, 6, 9.

Alternatively, the parameter adjustment amount may be associated with the subcarrier spacing. For example, the network side device may determine the parameter adjustment amount configured for the terminal according to the subcarrier interval, for example, configure a plurality of different parameter adjustment amounts for a plurality of different subcarrier intervals, so that the terminal may determine which parameter adjustment amount to use to obtain the non-integer DRX cycle parameter in which subcarrier interval according to the association relationship between the parameter adjustment amount and the subcarrier interval.

For example, a pattern may indicate that the 1 st DRX cycle value in the pattern is 16ms, the 2 nd DRX cycle value is 17ms, and the 3 rd DRX cycle value is 17ms, so that the terminal may determine the pattern= {16ms,17ms }.

For example, a pattern may indicate that the 1 st DRX cycle value in the pattern is 16ms, the 2 nd DRX cycle value is 17ms, and occurs 2 times, so that the terminal may determine the pattern= {16ms,17ms }.

Alternatively, the DRX cycle sequence may be associated with an XR traffic downlink frame rate. For example, the network side device may determine a DRX cycle sequence configured for the terminal according to the XR service downlink frame rate, for example, configure a plurality of different DRX cycle sequences for a plurality of different XR service downlink frame rates, so that the terminal may determine which DRX cycle sequence is used in which case of which XR service downlink frame rate according to the association relationship between the DRX cycle sequence and the XR service downlink frame rate.

Optionally, the number of DRX cycle values in the DRX cycle sequence is associated with the service downlink frame rate, i.e. the network side device may determine, according to the service downlink frame rate, the number of DRX cycle values in the DRX cycle sequence configured for the terminal.

For example, the DRX cycle sequence is { x } ₁ ,…,x _m }，x ₁ +…+x _m X, where m is the number of DRX cycle values in the DRX cycle sequence, and the value of X may be determined according to the traffic downlink frame rate. For example, the traffic downlink frame rate is 60fps, and x is 50ms; the traffic downlink frame rate is 90fps, x is 100ms, etc.

For example, the DRX cycle value in the DRX cycle sequence is denoted as W, where W satisfies:or-> Wherein L is a value related to XR service downlink frame rate, e.g. XR service downlink frame rate is 60FPS, L can be 16.67%>16->The DRX period value in the DRX period sequence can be 14ms, 15ms, 16ms,17ms,18 ms, 19ms, etc.

The methods provided by the embodiments of the present application are based on the same application conception, so that the implementation of each method can be referred to each other, and the repetition is not repeated.

The following illustrates the method provided by each of the above embodiments of the present application by way of examples of specific application scenarios.

Embodiment one: a non-integer DRX cycle value is configured.

Fig. 6 is a schematic implementation diagram of a DRX parameter configuration method according to an embodiment of the present application, as shown in fig. 6, the CDRX period value only supports an integer multiple of 1ms, and when the service downlink frame rate is 60FPS, if the DRX period value is configured to be 16ms, the frame arrival time and the DRX on duration start time differ by 0.67×m ms, where M is a positive integer. It can be seen that in this case, the time difference between the frame arrival time and the DRX on duration start time becomes larger.

If the DRX cycle value is configured to be 16.5ms, the frame arrival time and the DRX on duration start time differ by 0.17×mms, where M is a positive integer. It can be found that the DRX cycle value is configured to be 16.5ms, effectively reducing the degree of mismatch between the traffic downlink frame rate and the DRX cycle compared to the 16ms configuration.

Embodiment two: a DRX cycle sequence is configured.

Fig. 7 is a second implementation schematic diagram of a DRX parameter configuration method according to an embodiment of the present application, as shown in fig. 7, when the service downlink frame rate is 60FPS, the frame period is 16.67ms. According to the frame period characteristic, it is indicated that the fourth frame arrives at the 50ms, if the DRX cycle value is 16ms, the on time of the fourth DRX on duration will be 2ms earlier than the fourth frame arrival time, resulting in an increase of the power consumption of the terminal.

If different DRX cycle combinations are used, such as configuring the DRX cycle sequence {16ms,18 ms }, the on time of the fourth DRX on duration will be consistent with the fourth frame arrival time, so that matching with the service downlink frame rate can be achieved, and the delay and the terminal power consumption are reduced.

Embodiment III: a DRX cycle sequence list.

Illustratively, the present embodiment provides a DRX cycle sequence corresponding to different traffic downlink frame rates, as shown in table 2 below.

Table 2 DRX cycle sequences corresponding to different service downlink frame rates

In this embodiment, for convenience of description, any DRX cycle sequence written not only represents a specific certain DRX cycle value permutation sequence, but also includes a combination of all the permutation sequences. For example, a certain DRX cycle sequence {16ms,18ms }, written in table 2, may represent a cycle sequence of three different DRX cycle value arrangements of {16ms,18ms }, {16ms,18ms,16ms }, and {18ms,16ms }.

Illustratively, the present embodiment provides a predefined DRX cycle sequence pattern, as shown in table 3 below.

Table 3 predefined DRX cycle sequence pattern

Index	DRX cycle sequence Pattern
		1	{x ₁ ,x ₂ ,x ₃ }＝{a,a,c}
2	{x ₁ ,x ₂ ,x ₃ }＝{d,e,f}
		3	{x ₁ ,x ₂ ,x ₃ ,x ₄ }＝{g,h,I,j}
…	…

Illustratively, the present embodiment provides a DRX cycle sequence corresponding to different traffic downlink frame rates, where a sum of respective DRX cycle values in the DRX cycle sequence is as follows.

For example, the traffic downlink frame rate is 30fps, drx cycle sequence { x ] ₁ ,x ₂ ,x ₃ }，x ₁ +x ₂ +x ₃ ＝100ms。

For example, the traffic downlink frame rate is 60FPS, the DRX cycle sequence { x } ₁ ,x ₂ ,x ₃ }，x ₁ +x ₂ +x ₃ ＝50ms。

For example, the traffic downlink frame rate is 90fps, drx cycle sequence { x ] ₁ ,…,x ₉ }，x ₁ +…+x ₉ ＝100ms。

For example, the traffic downlink frame rate is 120FPS, the DRX cycle sequence { x } ₁ ,x ₂ ,x ₃ }，x ₁ +x ₂ +x ₃ ＝25ms。

Embodiment four: illustratively, the present embodiment provides for a semi-persistent scheduling (Semipersistent Scheduling) Grant (CG) period, a channel state information Reference Signal (CSI-RS) period, and a period value of a search space.

For example, the period value of the SPS CG period may include 16ms, 17ms, 18ms, and so on.

For example, the periodicity value of the CSI-RS periodicity may include 16ms, 17ms, 18ms, etc.

For example, the periodic value of the search space may include 16ms, 17ms, 18ms, etc.

According to the DRX parameter configuration method provided by the embodiment of the application, the execution main body can be the DRX parameter configuration device. In the embodiment of the present application, a method for executing DRX parameter configuration by using a DRX parameter configuration device is taken as an example, and the DRX parameter configuration device provided by the embodiment of the present application is described.

Fig. 8 is one of schematic structural diagrams of a DRX parameter configuration apparatus according to an embodiment of the present application, as shown in fig. 8, and an embodiment of the present application provides a DRX parameter configuration apparatus 800, which is applicable to a terminal, and includes:

a first receiving module 810, configured to receive first information sent by a network side device;

a first determining module 820, configured to determine a DRX parameter based on the first information; the DRX parameters include non-integer DRX cycle parameters and/or DRX cycle sequences.

Optionally, the first information includes at least one of:

one or more non-integer DRX cycle parameters;

one or more DRX cycle sequences;

the first indication information is used for determining parameter adjustment quantity, and the non-integer DRX cycle parameter is determined according to the sum of the integer DRX cycle parameter and the parameter adjustment quantity;

Second indication information for determining a first scaling factor, the non-integer DRX cycle parameter being determined according to a ratio between the integer DRX cycle parameter and the first scaling factor;

the first m-1 DRX cycle values in the target DRX cycle sequence and the sum of all DRX cycle values in the target DRX cycle sequence, wherein m is the number of the DRX cycle values in the target DRX cycle sequence;

one or more indexes for indicating a target DRX cycle sequence, each index for indicating one DRX cycle sequence.

Optionally, the first indication information includes at least one of:

a candidate set of parameter adjustment amounts;

and a candidate set of second scaling factors, wherein the parameter adjustment amount is determined according to the inverse of the second scaling factors.

Optionally, the candidate set of parameter adjustment amounts includes one or more of 0.11ms, 0.125ms, 0.25ms, 0.33ms, 0.5ms, 0.67 ms; alternatively, the candidate set of second scaling factors comprises one or more of 3, 6, 9.

Alternatively, in the case where the subcarrier spacing is equal to 30kHz, the parameter adjustment amount is 0.5ms; or,

in the case where the subcarrier spacing is equal to 60kHz, the parameter adjustment amount is 0.25ms; or,

in the case where the subcarrier spacing is equal to 120kHz, the parameter adjustment amount is 0.125ms.

Optionally, the non-integer DRX cycle parameter includes a non-integer DRX cycle value and/or a non-integer DRX start position offset value.

Optionally, the DRX cycle sequence includes a first DRX cycle sequence and/or a second DRX cycle sequence;

Optionally, the number of DRX cycle values in the DRX cycle sequence is associated with a traffic downlink frame rate.

Optionally, in the case that the traffic downlink frame rate is 30FPS or 60FPS or 120FPS, the number of DRX cycle values in the DRX cycle sequence is an integer multiple of 3; alternatively, in the case where the traffic downlink frame rate is 90FPS, the number of DRX cycle values in the DRX cycle sequence is an integer multiple of 9.

Optionally, the sum of the DRX cycle values in the DRX cycle sequence is a specified value associated with the traffic downlink frame rate.

Optionally, the DRX cycle value in the DRX cycle sequence includesOne or more of the following;

wherein ,indicating a rounding down of the first value L, +. >The first value L is represented by rounding up, and is determined according to the traffic downlink frame rate.

Optionally, the first value L comprises one or more of 16.67, 8.33, 33.33, 11.11.

Optionally, in case the DRX parameter comprises a DRX cycle sequence, the apparatus further comprises:

and the first application module is used for sequentially and circularly applying each DRX cycle value in the determined DRX cycle sequence on a time axis.

Fig. 9 is a second schematic structural diagram of a DRX parameter configuration apparatus according to an embodiment of the present application, as shown in fig. 9, and in an embodiment of the present application, a DRX parameter configuration apparatus 900 is provided, which may be applied to a network side device, and includes:

a second determining module 910, configured to determine a DRX parameter of the terminal, where the DRX parameter includes a non-integer DRX cycle parameter and/or a DRX cycle sequence;

the second sending module 920 is configured to send first information to the terminal, where the first information is used to indicate the DRX parameter.

Optionally, the first information includes at least one of:

one or more non-integer DRX cycle parameters;

one or more DRX cycle sequences;

Optionally, the first indication information includes at least one of:

a candidate set of parameter adjustment amounts;

wherein ,indicating a rounding down of the first value L, +.>The first value L is represented by rounding up, and is determined according to the traffic downlink frame rate.

The DRX parameter configuration device in the embodiment of the present application may be an electronic device, for example, an electronic device with an operating system, or may be a component in an electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

The DRX parameter configuration device provided by the embodiment of the present application can implement each process implemented by the foregoing method embodiments, and achieve the same technical effects, so that repetition is avoided, and details are not repeated here.

Fig. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application, and as shown in fig. 10, the embodiment of the present application further provides a communication device 1000, which includes a processor 1001 and a memory 1002, where a program or an instruction that can run on the processor 1001 is stored in the memory 1002, for example, when the communication device 1000 is a terminal, the program or the instruction is executed by the processor 1001 to implement each step of the embodiment of the DRX parameter configuration method corresponding to the terminal, and the same technical effects can be achieved. When the communication device 1000 is a network side device, the program or the instruction, when executed by the processor 1001, implements the steps of the embodiment of the DRX parameter configuration method corresponding to the network side device, and can achieve the same technical effects. In order to avoid repetition, a description thereof is omitted.

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the communication interface is used for receiving the first information sent by the network side equipment; the processor is used for determining DRX parameters based on the first information; the DRX parameters include non-integer DRX cycle parameters and/or DRX cycle sequences.

The terminal embodiment corresponds to the terminal-side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the terminal embodiment, and the same technical effects can be achieved.

Specifically, fig. 11 is a schematic hardware structure of a terminal according to an embodiment of the present application. The terminal 1100 includes, but is not limited to: at least part of the components of the radio frequency unit 1101, the network module 1102, the audio output unit 1103, the input unit 1104, the sensor 1105, the display unit 1106, the user input unit 1107, the interface unit 1108, the memory 1109, and the processor 1110, etc.

Those skilled in the art will appreciate that the terminal 1100 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 1110 by a power management system so as to perform functions such as managing charging, discharging, and power consumption by the power management system. The terminal structure shown in fig. 11 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine some components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 1104 may include a graphics processing unit (Graphics Processing Unit, GPU) 11041 and a microphone 11042, the graphics processor 11041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1107 includes at least one of a touch panel 11071 and other input devices 11072. The touch panel 11071 is also referred to as a touch screen. The touch panel 11071 may include two parts, a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 1101 may transmit the downlink data to the processor 1110 for processing; in addition, the radio frequency unit 1101 may send uplink data to the network side device. Typically, the radio frequency unit 1101 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

Memory 1109 may be used to store software programs or instructions and various data. The memory 1109 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 1109 may include volatile memory or nonvolatile memory, or the memory 1109 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 1109 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

Processor 1110 may include one or more processing units; optionally, the processor 1110 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, and the like, and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 1110.

The radio frequency unit 1101 is configured to receive first information sent by a network side device.

A processor 1110 for determining a DRX parameter based on the first information; the DRX parameters include non-integer DRX cycle parameters and/or DRX cycle sequences.

Optionally, the first information includes at least one of:

one or more non-integer DRX cycle parameters;

one or more DRX cycle sequences;

Optionally, the first indication information includes at least one of:

a candidate set of parameter adjustment amounts;

Optionally, in case the DRX parameter comprises a DRX cycle sequence, the processor 1110 is further configured to:

And sequentially and circularly applying each DRX cycle value in the determined DRX cycle sequence on a time axis.

The embodiment of the application also provides network side equipment, which comprises a processor and a communication interface, wherein the processor is used for determining the DRX parameter of the terminal, and the DRX parameter comprises a non-integer DRX period parameter and/or a DRX period sequence; the communication interface is configured to send first information to the terminal, where the first information is used to indicate the DRX parameter. The network side device embodiment corresponds to the network side device method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

Specifically, the embodiment of the application also provides network side equipment. Fig. 12 is a schematic structural diagram of a network side device according to an embodiment of the present application, as shown in fig. 12, where the network side device 1200 includes: an antenna 121, a radio frequency device 122, a baseband device 123, a processor 124, and a memory 125. The antenna 121 is connected to a radio frequency device 122. In the uplink direction, the radio frequency device 122 receives information via the antenna 121, and transmits the received information to the baseband device 123 for processing. In the downlink direction, the baseband device 123 processes information to be transmitted, and transmits the processed information to the radio frequency device 122, and the radio frequency device 122 processes the received information and transmits the processed information through the antenna 121.

The method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 123, where the baseband apparatus 123 includes a baseband processor.

The baseband apparatus 123 may, for example, include at least one baseband board, where a plurality of chips are disposed, as shown in fig. 12, where one chip, for example, a baseband processor, is connected to the memory 125 through a bus interface, so as to invoke a program in the memory 125 to perform the network device operation shown in the above method embodiment.

The network-side device may also include a network interface 126, such as a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 1200 of the embodiment of the present application further includes: instructions or programs stored in the memory 125 and executable on the processor 124, the processor 124 invokes the instructions or programs in the memory 125 to perform the methods performed by the modules shown in fig. 9 and achieve the same technical effects, and are not repeated here.

The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the above embodiment of the DRX parameter configuration method, and can achieve the same technical effects, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, the chip comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running a program or instructions, the processes of the embodiment of the DRX parameter configuration method can be realized, the same technical effects can be achieved, and the repetition is avoided, and the description is omitted here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product stored in a storage medium, where the computer program/program product is executed by at least one processor to implement each process of the above embodiment of the DRX parameter configuration method, and achieve the same technical effects, and are not repeated herein.

The embodiment of the application also provides a DRX parameter configuration system, which comprises: the terminal can be used for executing the DRX parameter configuration method corresponding to the terminal, and the network side device can be used for executing the DRX parameter configuration method corresponding to the network side device.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims

1. A DRX parameter configuration method, comprising:

the terminal receives first information sent by network side equipment;

2. The DRX parameter configuration method of claim 1, wherein the first information comprises at least one of:

one or more non-integer DRX cycle parameters;

one or more DRX cycle sequences;

The method comprises the steps that m is the number of DRX cycle values in a target DRX cycle sequence, wherein m is the number of the DRX cycle values in the target DRX cycle sequence, and the sum of all DRX cycle values in the target DRX cycle sequence;

one or more indices for indicating a target DRX cycle sequence, each index for indicating one DRX cycle sequence.

3. The DRX parameter configuration method of claim 2, wherein the first indication information comprises at least one of:

a candidate set of the parameter adjustment amounts;

4. A DRX parameter configuration method according to claim 3, characterized in that the candidate set of parameter adjustment amounts comprises one or more of 0.11ms, 0.125ms, 0.25ms, 0.33ms, 0.5ms, 0.67 ms; or,

the candidate set of second scaling factors includes one or more of 3, 6, 9.

5. The method for configuring DRX parameters according to any one of claims 2 to 4,

in case the subcarrier spacing is equal to 30kHz, the parameter adjustment amount is 0.5ms; or,

In case the subcarrier spacing is equal to 120kHz, the parameter adjustment amount is 0.125ms.

6. The DRX parameter configuration method according to any one of claims 1 to 5, wherein the non-integer DRX cycle parameter comprises a non-integer DRX cycle value and/or a non-integer DRX start position offset value.

7. The DRX parameter configuration method according to claim 2, wherein the DRX cycle sequence comprises a first DRX cycle sequence and/or a second DRX cycle sequence;

8. The DRX parameter configuration method according to claim 2 or 7, wherein the DRX cycle sequence is associated with a traffic downlink frame rate.

9. The DRX parameter configuration method of claim 8, wherein the number of DRX cycle values in the DRX cycle sequence is associated with a traffic downlink frame rate.

10. The DRX parameter configuration method according to claim 9, wherein:

under the condition that the service downlink frame rate is 30FPS or 60FPS or 120FPS, the number of DRX cycle values in the DRX cycle sequence is an integer multiple of 3; or,

And under the condition that the service downlink frame rate is 90FPS, the number of DRX cycle values in the DRX cycle sequence is an integer multiple of 9.

11. The DRX parameter configuration method according to any one of claims 8 to 10, wherein a sum of respective DRX cycle values in the DRX cycle sequence is a specified value associated with a traffic downlink frame rate.

12. The DRX parameter configuration method according to any one of claims 8 to 11, wherein the DRX cycle value in the DRX cycle sequence comprisesOne or more of the following;

13. The DRX parameter configuration method according to claim 12, wherein the first value L comprises one or more of 16.67, 8.33, 33.33, 11.11.

14. The DRX parameter configuration method according to claim 1, wherein, in case the DRX parameter comprises a DRX cycle sequence, after the determining the DRX parameter, the method further comprises:

the terminal sequentially and circularly applies each DRX period value in the determined DRX period sequence on a time axis.

15. A DRX parameter configuration method, comprising:

16. The DRX parameter configuration method of claim 15, wherein the first information comprises at least one of:

one or more non-integer DRX cycle parameters;

one or more DRX cycle sequences;

17. The DRX parameter configuration method of claim 16, wherein the first indication information comprises at least one of:

a candidate set of the parameter adjustment amounts;

18. The DRX parameter configuration method of claim 17, wherein the candidate set of parameter adjustment amounts comprises one or more of 0.11ms, 0.125ms, 0.25ms, 0.33ms, 0.5ms, 0.67 ms; or,

the candidate set of second scaling factors includes one or more of 3, 6, 9.

19. The DRX parameter configuration method according to any one of claims 16 to 18,

20. The DRX parameter configuration method according to any one of claims 15 to 19, wherein the non-integer DRX cycle parameter comprises a non-integer DRX cycle value and/or a non-integer DRX start position offset value.

21. The DRX parameter configuration method according to claim 16, wherein the DRX cycle sequence comprises a first DRX cycle sequence and/or a second DRX cycle sequence;

22. The DRX parameter configuration method according to claim 16 or 21, wherein the DRX cycle sequence is associated with a traffic downlink frame rate.

23. The DRX parameter configuration method of claim 22, wherein the number of DRX cycle values in the DRX cycle sequence is associated with a traffic downlink frame rate.

24. The DRX parameter configuration method according to claim 23, wherein:

25. The DRX parameter configuration method according to any one of claims 22 to 24, wherein a sum of respective DRX cycle values in the DRX cycle sequence is a specified value associated with a traffic downlink frame rate.

26. The DRX parameter configuration method according to any one of claims 22 to 25, wherein the DRX cycle value in the DRX cycle sequence comprisesOne or more of the following;

27. The DRX parameter configuration method of claim 26, wherein the first value L comprises one or more of 16.67, 8.33, 33.33, 11.11.

28. A DRX parameter configuration apparatus, applied to a terminal, comprising:

29. The DRX parameter configuration apparatus of claim 28, wherein the first information comprises at least one of:

one or more non-integer DRX cycle parameters;

one or more DRX cycle sequences;

30. A DRX parameter configuration apparatus, which is applied to a network side device, includes:

31. The DRX parameter configuration apparatus of claim 30, wherein the first information comprises at least one of:

one or more non-integer DRX cycle parameters;

one or more DRX cycle sequences;

32. A communication device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implements the DRX parameter configuration method of any of claims 1 to 14, or implements the DRX parameter configuration method of any of claims 15 to 27.

33. A readable storage medium, wherein a program or instructions is stored on the readable storage medium, which when executed by a processor, implements the DRX parameter configuration method according to any of claims 1 to 14, or implements the DRX parameter configuration method according to any of claims 15 to 27.