Method and device for configuring discontinuous reception period

Abstract

The embodiment of the invention provides a discontinuous reception (DRX) period configuration method and device, and the method comprises the steps that a network device sends a first configuration message to a terminal device, and the first configuration message configures a non-integer DRX period represented by one or more scores; the first configuration information comprises a first information unit, and the first information unit comprises a field indicating a non-integer long DRX period and an initial offset thereof and / or indicating a non-integer short DRX period. According to the embodiment of the invention, the DRX-related enhancement is carried out on the RRC and / or MAC layer, so that the problems of DRX configuration and operation under the conditions of arrival periods of different XR service flows and multiple XR service flows are solved, and UE energy conservation for XR services and media services is better supported.

Description

Method and device for configuring discontinuous reception cycle Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] Support for extended reality (XR) services within 3GPP (3rd Generation Partnership Project) services and networks. XR services refer to all combined real and virtual environments and human-computer interactions enabled by computing technology and wearable devices. Application areas include, but are not limited to, entertainment, healthcare, and education. XR services can encompass representative forms such as virtual reality (VR), augmented reality (AR), and mixed reality (MR), as well as hybrid and interdisciplinary areas.

[0003] Virtual reality is a rendered version of a visual and audio scene that is presented to the viewer or user, designed to simulate the visual and auditory sensory stimulation of the real world as naturally as possible as the viewer or user moves within the limitations defined by the application. Augmented reality refers to the provision of additional information or artificially generated items or content overlaid on the user's current environment. Mixed reality is an advanced form of AR, in which some virtual elements are inserted into the physical scene to provide the illusion that these elements are part of the real scene.

[0004] A PDU Set consists of one or more Protocol Data Units (PDUs) that carry the payload of an information unit generated at the application layer, such as a frame or video slice for XR and media services. In some embodiments, the application layer requires all PDUs in a PDU Set to use the corresponding information unit. In other embodiments, when some PDUs are lost, the application layer can still recover all or part of the information unit.

[0005] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0006] Summary of the Invention

[0007] The inventors discovered that to reduce power consumption in terminal devices, 3GPP has been using discontinuous reception (DRX) technology since the 3G era. When a terminal device is configured with DRX, it does not need to continuously monitor the physical downlink control channel (PDCCH), thereby achieving energy conservation.

[0008] To reduce power consumption when using XR services, the DRX cycle can be matched to the data arrival cycle, and the wake-up period can be roughly aligned with the data arrival time. This allows the UE to monitor the PDCCH sent by the base station when data arrives, obtain scheduling information, and schedule the data in a timely manner. However, the current DRX cycle is defined as different integer values ​​in milliseconds. If the data arrival cycle is non-integer, the data arrival cycle and the DRX cycle will not match. After a period of time, the data arrival time may fall into the sleep period. The UE will not be able to monitor the PDCCH, which will affect the timely scheduling of data and increase data transmission delays.

[0009] In response to at least one of the above problems or other similar problems, an embodiment of the present application provides a method and apparatus for configuring a discontinuous reception (DRX) cycle.

[0010] According to one aspect of an embodiment of the present application, a DRX cycle configuration apparatus is provided, which is applied to a network device, and the apparatus includes:

[0011] A sending unit, which sends a first configuration message to a terminal device, wherein the first configuration message configures a non-integer DRX cycle represented by one or more fractions; the first configuration information includes a first information unit, which includes a field indicating a non-integer long DRX cycle and its starting offset and / or indicating a non-integer short DRX cycle.

[0012] According to another aspect of an embodiment of the present application, a DRX cycle configuration device is provided, which is applied to a network device, and the device includes:

[0013] A sending unit, which sends a second configuration message to the terminal device, wherein the second configuration message configures the disabling of CG retransmission monitoring for configuration authorization; the second configuration message contains a second information unit, and the second information unit includes a sixth field, and the sixth field indicates the disabling of CG retransmission monitoring for configuration authorization.

[0014] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, by performing DRX-related enhancements at the RRC and / or MAC layer, the arrival period of different XR service flows and the DRX configuration and operation problems in the case of multiple XR service flows are solved, thereby better supporting UE energy saving for XR services and media services.

[0015] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0016] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0017] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0019] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0020] FIG1 is a schematic diagram of a DRX cycle;

[0021] FIG2 is a schematic diagram showing a mismatch between the DRX cycle and the XR traffic cycle;

[0022] FIG3 is a schematic diagram of a method for configuring a DRX cycle according to an embodiment of the present application;

[0023] FIG4 is a schematic diagram of an example of a DRX configuration;

[0024] FIG5 is a schematic diagram showing that the continuous monitoring time of the long DRX cycle and the short DRX cycle are not aligned;

[0025] FIG6 is a schematic diagram of a method for determining a DRX cycle according to an embodiment of the present application;

[0026] FIG7 is another schematic diagram of a DRX configuration method according to an embodiment of the present application;

[0027] FIG8 is another schematic diagram of a method for implementing DRX configuration according to an embodiment of the present application;

[0028] FIG9 is a schematic diagram of a DRX cycle configuration apparatus according to an embodiment of the present application;

[0029] FIG10 is another schematic diagram of a DRX configuration apparatus according to an embodiment of the present application;

[0030] FIG11 is a schematic diagram of a device for determining a DRX cycle according to an embodiment of the present application;

[0031] FIG12 is another schematic diagram of an implementation apparatus for DRX configuration according to an embodiment of the present application;

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

[0033] FIG14 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0034] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0035] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0036] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0037] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0038] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and / or other currently known or future communication protocols to be developed.

[0039] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0040] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto and pico). The term "base station" may include some or all of these functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which it is used.

[0041] In the embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE). Terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, etc.

[0042] Terminal devices may include, but are not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, and IAB-MT, etc.

[0043] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0044] Currently, 5G technology is researching key issues, solutions, and conclusions to support advanced media services, such as High Data Rate Low Latency (HDRLL) services, AR / VR / XR services, and tactile / multimodal communication services. The goals include:

[0045] 1. Enhancements to support multi-mode services, including:

[0046] - Investigate whether and how to enable applications to provide relevant tactile and multimodal data to users at similar times (e.g., audio, video, and tactile data associated with a specific time), focusing on the need for enhanced policy control (e.g., QoS policy coordination).

[0047] 2. Enhanced network exposure to support interaction between 5GS (5G system) and applications, including:

[0048] - Study whether and how to perform application synchronization and QoS (Quality of Service) policy coordination between multiple UEs or multiple QoS flows per UE, and how to interact between AF and 5GS.

[0049] - Study the exposure of 5GS QoS information (e.g., QoS capabilities) and network conditions to applications to enable fast codec / rate adaptation that helps deliver the desired QoE (e.g., helping alleviate 5GS congestion).

[0050] 3. Study whether and how to implement the following QoS and policy enhancements for XR service and media service transport, including:

[0051] -Study the traffic characteristics of media services that can improve network resource utilization and QoE (Quality of Experience).

[0052] - Enhance the QoS framework to support PDU Set granularity (e.g. video / audio frame / tile, application data unit, control information), where a PDU Set consists of PDUs with the same QoS requirements.

[0053] - Considering the different importance of PDU Sets, it supports differentiated QoS processing. For example, packets belonging to less important PDU Sets can be legally discarded to reduce resource waste.

[0054] - Whether and how to support uplink-downlink transmission coordination to meet the RTT (Round Trip Time) delay requirement between the UE and the N6 termination point of the UPF (User Plane Function).

[0055] - Potential policy enhancements to minimize jitter, focusing on demand provisioning from AF (Application Function) and extensions of PCC (policy and charging control) rules.

[0056] In order to reduce the power consumption of UE, 3GPP has been using DRX technology since the 3G era. The full name of DRX is Discontinuous Reception. The mechanism of DRX in RRC IDLE and RRC CONNECTED is different. The DRX mechanism in the idle state is the paging mechanism, which means that the network side wakes up the UE by sending a paging message. In the embodiment of this application, DRX in the connected state (Connected DRX, C-DRX) is used as an example for explanation. In the following description, unless otherwise specified, DRX refers to the DRX used when the UE is in the connected state, that is, C-DRX.

[0057] When a UE is configured with DRX, it does not need to continuously monitor the PDCCH (Physical Downlink Control Channel), thereby achieving energy conservation. The UE's MAC entity can be configured with DRX via RRC signaling to control the UE's PDCCH monitoring activity for certain RNTIs (Radio Network Temporary Identifiers) associated with the MAC entity.

[0058] The basic DRX mechanism configures a DRX cycle for a UE in the RRC Connected state. The DRX cycle consists of an On Duration (wake-up period) and an Opportunity for DRX (sleep period). During the On Duration, the UE monitors and receives the PDCCH; during the Opportunity for DRX, the UE does not receive PDCCH to reduce power consumption. The DRX cycle defines a recurring cycle of wake-up periods followed by possible periods of inactivity, as shown in Figure 1.

[0059] To balance power conservation and latency, NR supports two DRX cycles: long and short, depending on the length of time the UE monitors specific scheduling channels after waking up. If UE data is predicted to arrive frequently or the service is latency-sensitive, the network can configure the UE to use the short DRX cycle. If UE data is predicted to arrive sparsely and the service is latency-insensitive, the network can configure the UE to use only the long DRX cycle. To facilitate UE switching between long and short DRX cycles, the long DRX cycle must be an integer multiple of the short DRX cycle to ensure alignment of the onDurations of the two cycles.

[0060] The inventors have discovered that there are many different frame rates for existing XR services, most of which correspond to non-integer data arrival periods. If expressed in milliseconds, the arrival period of XR service traffic (abbreviated as XR traffic period or data transmission period, etc.) may be a non-integer (rational number). For example, XR services with frame rates of 15, 30, 45, 60, 72, 90, and 120 frames per second correspond to non-integer data periods (66.66, 33.33, 22.22, 16.66, 13.88, 11.11, and 8.33 milliseconds, respectively).

[0061] The current DRX cycle is defined as a different integer value in milliseconds. In order to reduce power consumption when the UE uses XR services, the DRX cycle can be matched with the data (such as XR service traffic) arrival cycle, and the wake-up period and data arrival time can be roughly aligned. In this way, when the data arrives, the UE can monitor the PDCCH sent by the base station, obtain scheduling information from it, and schedule the data in a timely manner. If the data arrival cycle is non-integer, then the data arrival cycle and the DRX cycle will not match. After a period of time, the data arrival time will fall into the sleep period. In this way, the UE will not be able to monitor the PDCCH, which will affect the timely scheduling of data and increase data transmission delay.

[0062] Figure 2 takes a frame rate of 60 frames per second (corresponding to a data arrival period of approximately 16.67 milliseconds) as an example. If the DRX cycle is set to 16 milliseconds, after several DRX cycles, the DRX wake-up period and the data arrival time (at 66.67 ms in Figure 2) will not be aligned.

[0063] Considering the arrival cycle characteristics of XR service traffic, how to solve the mismatch between the DRX cycle and the arrival cycle of XR service traffic requires further standardization and technical implementation.

[0064] Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely illustrative and are not intended to limit the present application. In the following description, expressions such as "if...", "in the case of...", and "when..." have the same meaning and are interchangeable.

[0065] Embodiments of the first aspect

[0066] The present application embodiment provides a method for configuring a DRX cycle, which is described from the perspective of a network device. FIG3 is a schematic diagram of the method for configuring a DRX cycle according to an embodiment of the present application. As shown in FIG3 , the method includes:

[0067] 310: The network device sends a first configuration message to the terminal device, wherein the first configuration message configures a non-integer DRX cycle represented by one or more fractions; the first configuration information includes a first information unit, wherein the first information unit includes a field indicating a non-integer long DRX cycle and its starting offset and / or indicating a non-integer short DRX cycle.

[0068] It is worth noting that FIG1 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG3 above.

[0069] According to the above embodiment, the problem that the DRX cycle does not support non-integer data arrival periods is solved, and UE energy saving is achieved.

[0070] In some embodiments, the first configuration message is an RRCReconfiguration message, and the first information element is a DRX-Config IE. According to the above embodiment, by enhancing the RRC configuration, the RRC can configure the DRX cycle as a rational number (i.e., a fraction), thereby solving the problem that the DRX cycle does not support non-integer data arrival periods.

[0071] In the above embodiment, the DRX-Config IE in the RRCReconfiguration message is enhanced to support configuration of a rational number DRX cycle, but the present application is not limited thereto. Other information elements in other configuration messages may also be enhanced, or new IEs may be added to the RRCReconfiguration message or other configuration messages to perform the above configuration.

[0072] For the convenience of explanation, the following takes the enhancement of the DRX-Config IE in the RRCReconfiguration message as an example.

[0073] In some embodiments, non-integer long DRX cycles and start offsets are uniformly defined.

[0074] In the above embodiment, the first information unit includes a first field, which includes a combination of a non-integer (fractional) long DRX cycle corresponding to the frame rate and its corresponding starting offset, for example, which can be called drx-NonIntegerLongCycleStartOffset. The present application is not limited to this, and the first field may also have other names.

[0075] In the above embodiment, the first field is, for example, a CHOICE structure, in which each element is a combination of a predefined non-integer long DRX cycle corresponding to a certain frame rate and its corresponding starting offset in milliseconds. The first field is a CHOICE structure, indicating that a selection is made from among the predefined non-integer long DRX cycles corresponding to a certain frame rate and their corresponding starting offsets in milliseconds during configuration.

[0076] In the above embodiment, a non-integer long DRX cycle can be expressed by a fraction in milliseconds, which is expressed by an integer numerator and denominator, such as 200 / 3ms. In addition, the starting offset corresponding to each non-integer long DRX cycle ranges from 0 to a value rounded down to the non-integer long DRX cycle, such as 0 to 66.

[0077] Here is an example of the first field:

[0078] In the above example, the first field drx-NonIntegerLongCycleStartOffset contains the fractional value drx-NonIntegerLongCycle (non-integer long DRX cycle) in milliseconds and drx-StartOffset (start offset) in milliseconds. The value "ms200 / 3" corresponds to 200 / 3 milliseconds, that is, the frame rate is 15 frames per second (1000ms / 15fps=200 / 3ms), and other fractional values ​​are similar. In addition, in the above example, "ms200 / 3" is just a method of using two integers (numerator and denominator, usually coprime integers) to represent a fraction. This application does not limit this and can also be expressed as "ms200by3", "ms200over3", etc. The non-integer long DRX cycles defined in the above example correspond to frame rates of 15fps, 30fps, 45fps, 60fps, 72fps, 90fps, and 120fps respectively.

[0079] In the above embodiment, if the first field is configured, the terminal device may ignore the configuration of drx-LongCycleStartOffset (ie, the integer long DRX cycle and the corresponding start offset), thereby avoiding ambiguity in terminal behavior.

[0080] In the above embodiment, the first information unit may further include a second field, where the second field includes a non-integer short DRX cycle corresponding to the frame rate.

[0081] In the above embodiment, for non-integer short DRX cycles, a new second field can be defined in the DRX-Config IE. This second field is the non-integer (fraction) short DRX cycle corresponding to a certain frame rate. This second field can be called, for example, drx-NonIntegerShortCycle, but the present application is not limited thereto, and this second field can also have other names.

[0082] In the above embodiment, the second field may be of an enumeration type, and when used, is selected from pre-defined short DRX cycles expressed by fractions in milliseconds.

[0083] Here is an example of the second field:

[0084] In the above example, the value "ms200 / 3" in the second field corresponds to 200 / 3 milliseconds, and so on.

[0085] In the above embodiment, if the second field is configured, the terminal device may ignore the configuration of drx-ShortCycle (ie, an integer short DRX cycle), thereby avoiding ambiguity in terminal behavior.

[0086] In the above embodiment, if the second field is configured, the non-integer long DRX cycle value in the first field must be an integer multiple of the value in the second field. For example, if the second field is configured as ms100 / 3, the non-integer long DRX cycle in the first field can be configured as ms200 / 3. This ensures that the onDuration of the two devices is aligned.

[0087] In some other embodiments, non-integer long DRX cycles and starting offsets are defined separately.

[0088] In the above embodiment, the first information element includes a third field and a fourth field, for example, a new third field and a fourth field are defined in the DRX-Config IE. The third field includes a non-integer long DRX cycle corresponding to the frame rate, and the fourth field includes a starting offset for the non-integer long DRX cycle.

[0089] In the above embodiment, the third field defines a non-integer (fractional) long DRX cycle, such as drx-NonIntegerLongCycle, which is represented by two integers (a first integer and a second integer), such as N1 and N2, where N1 represents the numerator in the fractional expression N1 / N2 of the above non-integer long DRX cycle, and N2 represents the denominator in the fractional expression N1 / N2 of the above non-integer long DRX cycle.

[0090] In the above embodiment, N1 and N2 can be integers, with the value ranges corresponding to the numerator and denominator of the fractional representation of a supported non-integer long DRX cycle. This allows N1 and N2 to take arbitrary values ​​within their respective ranges, providing strong scalability and supporting a wider range of services with different data rates.

[0091] The following is an example of the third field, showing the case where N1 and N2 are both integer types:

[0092] In the above embodiment, N1 and N2 may also be enumerated types, with the value ranges including the fixed values ​​of the numerator and denominator in the fractional expression of supported non-integer long DRX cycles, and may also include reserved spare bits. This reduces signaling overhead while maintaining a certain degree of scalability, allowing support for more services with different data rates.

[0093] Here is another example of the third field, showing the case where N1 and N2 are enumeration types:

[0094] In the above embodiment, the third field includes two integers, N1 and N2. Since N1 and N2 are used to indicate the non-integer period of the XR video service as fractions, they are actually obtained by dividing 1000 milliseconds by the frame rate and performing a reduction. In some implementations, this reduction can be omitted, meaning that N1 = 1000 ms and N2 = frame rate. In this case, N1 need not be indicated, and only the frame rate needs to be indicated.

[0095] That is, the third field may also include only one integer, namely, a second integer, such as N2, to represent a non-integer long DRX cycle. After receiving the third field, the terminal device may use the quotient of 1000 milliseconds and the second integer, namely, 1000 / N2, ​​as a fraction to represent the non-integer long DRX cycle.

[0096] In the above embodiment, the fourth field defines the starting offset for non-integer long DRX cycles, for example, drx-StartOffsetForNonIntCycle. This fourth field can be an integer, with a value range of 0 to Nmax. Nmax is the maximum supported non-integer long DRX cycle, rounded down to the nearest integer, for example, 66 milliseconds.

[0097] In the above embodiment, when the third field is configured, the fourth field must be configured, thereby ensuring the integrity of the configuration of non-integer long DRX cycles.

[0098] In the above embodiment, when the third field is configured, the terminal device may ignore the configuration of drx-LongCycleStartOffset (ie, the integer long DRX cycle and its corresponding start offset), thereby avoiding ambiguity in terminal behavior.

[0099] In the above embodiment, the first information unit further includes a fifth field, and the fifth field includes a non-integer short DRX cycle corresponding to the frame rate.

[0100] In the above embodiment, for non-integer short DRX cycles, a new fifth field can be defined in the DRX-Config IE. The fifth field defines a non-integer (fractional) short DRX cycle corresponding to a certain frame rate. This fifth field can be called, for example, drx-NonIntegerShortCycle and represented by two integers. The field design is the same as the third field and can also be represented by the two examples described above.

[0101] For example, the fifth field includes a third integer and a fourth integer, the third integer being the numerator in the fractional expression of the non-integer short DRX cycle, and the fourth integer being the denominator in the fractional expression of the non-integer short DRX cycle.

[0102] In an example, the third integer and the fourth integer are both integer types, and the value range of the third integer is the range of changes in the numerator in the fractional expression of the supported non-integer short DRX cycle; the value range of the fourth integer is the range of changes in the denominator in the fractional expression of the supported non-integer short DRX cycle.

[0103] In another example, the third integer and the fourth integer are respectively enumerated types; the value range of the third integer includes a fixed value of the numerator in the fractional expression of the supported non-integer short DRX cycle, and may also include reserved spare bits; the value range of the fourth integer includes a fixed value of the denominator in the fractional expression of the supported non-integer short DRX cycle, and may also include reserved spare bits.

[0104] In the above embodiment, taking the fifth field including the third integer and the fourth integer as an example, similar to the third field, without reducing the fraction, the third integer may be indicated instead of the fourth integer, that is, the fifth field only includes the fourth integer, and the fourth integer represents a non-integer short DRX cycle. The terminal device uses the quotient of 1000 milliseconds and the fourth integer as a fraction to represent the non-integer short DRX cycle.

[0105] In the above embodiment, the third field and the fifth field are both rational numbers in milliseconds, indicating that a non-integer DRX cycle is defined as N1 / N2 milliseconds.

[0106] In the above embodiment, if the fifth field is configured, the value of the third field must be an integer multiple of the value of the fifth field.

[0107] In the above embodiment, similar to the third field, if the fifth field is configured, the terminal device may ignore the configuration of drx-ShortCycle (ie, an integer short DRX cycle), thereby avoiding ambiguity in terminal behavior.

[0108] The above describes the implementation of a non-integer long DRX cycle, a starting offset, and a non-integer short DRX cycle. In the embodiments of the present application, the formula for calculating the start time of the DRX wake-up period can be further enhanced. That is, when determining when to start the wake-up period of a non-integer DRX cycle, a formula is required for calculation.

[0109] In addition, in order to solve the problem of misalignment between the DRX cycle and the SFN boundary when the SFN (system frame number) flips, a counter (first counter) can be added, such as DRX_SFN_COUNTER. This counter increases by 1 every time the SFN flips, that is, the first counter is increased by 1 at the first character time of the time slot when the SFN changes to 0. The initial value of the counter is 0 and the maximum value is 65535. In addition, a time reference system frame number (SFN) for determining the starting offset can be defined, such as drx-TimeReferenceSFN, with a value of 0 or 512, which is used to determine the start time of the DRX wake-up period. The terminal device uses the SFN closest to the indicated reference SFN before receiving the DRX configuration with the time reference SFN.

[0110] In some embodiments, the terminal device determines the time to start the wake-up period of the non-integer DRX cycle. For example, when the DRX cycle is configured, the MAC entity of the terminal device determines the time to start the wake-up period of the non-integer DRX cycle.

[0111] In one example,

[0112] If a short DRX cycle is used for a DRX group, and a non-integer short DRX cycle is configured (for example, the second field or the fifth field is configured), and the current first counter (DRX_SFN_COUNTER), system frame number (SFN), and subframe number satisfy the following formula:

[0113] floor([(first counter×10240)+(system frame number×10)+subframe number]modulo(non-integer short DRX cycle))=floor([(time reference system frame number×10)+start offset)]modulo(non-integer short DRX cycle)),

[0114] The terminal device starts a wake-up timer (drx-onDurationTimer) for the above DRX group after the time slot offset (drx-SlotOffset) duration after the start of the subframe corresponding to the above subframe number.

[0115] In another example,

[0116] If a long DRX cycle is used for a DRX group, and a non-integer long DRX cycle is configured (for example, the first field or the third field is configured), and the current first counter (DRX_SFN_COUNTER), system frame number (SFN), and subframe number satisfy the following formula:

[0117] floor([(first counter×10240)+(system frame number×10)+subframe number]modulo(non-integer long DRX cycle))=floor([(time reference system frame number×10)+start offset)]modulo(non-integer long DRX cycle)),

[0118] The terminal device starts the wake-up timer for the above-mentioned DRX group after the time slot offset (drx-SlotOffset) duration after the start of the subframe corresponding to the above-mentioned subframe number, when the downlink control information (DCP, DCI with CRC scrambled by PS_RNTI) with cyclic redundancy check scrambled by the energy-saving radio network temporary identifier (PS_RNTI) is not configured for the activated downlink bandwidth part (BWP, BandWidth Part) to be monitored.

[0119] In the above formula, modulo represents the modulo (remainder) calculation. Since this is performed on a rational number (i.e., a non-integer DRX cycle, represented by N1 / N2), to avoid roundoff errors, A modulo B (B = N1 / N2) in the formula can be replaced with A-floor(A*N2 / N1)*N1 / N2. The calculation must be performed in the order of the operators in this replacement formula to avoid roundoff errors. The specific order refers to performing the operations from left to right in the formula.

[0120] The following is an example of enhancing the DRX process of TS 38.321 according to the above embodiment:

[0121] In the above embodiment, a DRX group refers to a group of service cells configured by RRC with the same DRX activation time. In order to align the DRX cycles of different DRX groups, the following parameters can be set to be common to all DRX groups: a non-integer long DRX cycle, a starting offset, a non-integer short DRX cycle, and drx-TimeReferenceSFN. That is, in the embodiment of the present application, each DRX group can share the following parameters: a non-integer long DRX cycle, a starting offset corresponding to the non-integer long DRX cycle, a non-integer short DRX cycle, and a time reference frame number. The meanings of the above parameters have been explained above, and their contents are incorporated here and will not be repeated here.

[0122] In some embodiments, considering that a first counter (DRX_SFN_COUNTER) is used in the above formula, the first counter needs to be synchronized on the network side and the terminal side, that is, to maintain the same value. The terminal device can initialize the counter to 0 when receiving an RRC configuration for a non-integer DRX cycle (such as an RRC configuration for a non-integer long DRX cycle, that is, the above-mentioned first configuration message), and add 1 to the first counter at the first character time of the time slot when the SFN changes to 0. Since the first counter increases by 1 every time the SFN wraps around, if the terminal device receives an RRC configuration for a non-integer DRX cycle when the SFN has just wrapped around (for example, SFN=0 or a very small value), due to network delay, the terminal device cannot determine whether the SFN has wrapped when the network side sends the configuration, so the DRX_SFN_COUNTER cannot be initialized correctly, that is, the DRX_SFN_COUNTER cannot be synchronized with the network.

[0123] In the above embodiment, the terminal device can initialize the above first counter (DRX_SFN_COUNTER) according to the time reference SFN (drx-TimeReferenceSFN) carried by the above RRC configuration (for example, the RRC configuration of the non-integer DRX cycle, that is, the above first configuration message).

[0124] For example, when the terminal device receives the RRC configuration of a non-integer DRX cycle sent by the network side, if the time reference SFN value is 0, it means that when the network side sends the configuration, the SFN is the first half of the entire SFN cycle (that is, SFN 0-511). When the terminal device receives the configuration, SFN flipping will definitely not occur, so the terminal device can set DRX_SFN_COUNTER to 0.

[0125] For another example, when the network side sends an RRC configuration about a non-integer DRX cycle, if the time reference SFN value is 512, it means that the current SFN is the second half of the entire SFN cycle (that is, SFN 512-1023). If the SFN is still in the second half of the SFN cycle when the terminal device receives the configuration, it means that no SFN rollover has occurred, so the terminal device can set DRX_SFN_COUNTER to 0; if the SFN is in the first half of the SFN cycle when the terminal device receives the configuration, it means that an SFN rollover has occurred, so the terminal device can set DRX_SFN_COUNTER to 1.

[0126] Therefore, the terminal device initializes the above-mentioned DRX_SFN_COUNTER according to the time reference SFN carried by the received RRC configuration of the non-integer DRX cycle, which can ensure the synchronization of DRX_SFN_COUNTER on the network side and the UE side.

[0127] In the above embodiment, the non-integer DRX cycle may be a non-integer long DRX cycle or a non-integer short DRX cycle.

[0128] The following is another example of enhancing the DRX process of TS 38.321 according to the above embodiment, to achieve correct initialization of DRX_SFN_COUNTER:

[0129] In the above embodiment, after the DRX_SFN_COUNTER is synchronized on the network side and the terminal side, the time reference SFN may be omitted in the above formula related to the non-integer DRX cycle.

[0130] For example, when a DRX cycle is configured, the MAC entity of the terminal device determines the time to start the wake-up period of a non-integer DRX cycle by the following method:

[0131] If a short DRX cycle is used for a DRX group, and a non-integer short DRX cycle is configured (for example, the second field or the fifth field is configured), and the current DRX_SFN_COUNTER, SFN, and subframe number satisfy the following formula:

[0132] floor([(DRX_SFN_COUNTER×10240)+(SFN×10)+subframe number]modulo(non-integer short DRX cycle))=floor((start offset)modulo(non-integer short DRX cycle)),

[0133] The terminal device starts a wake-up timer (drx-onDurationTimer) for the above DRX group after the drx-SlotOffset (time slot offset) duration after the start of the subframe corresponding to the above subframe number.

[0134] If a long DRX cycle is used for a DRX group, and a non-integer long DRX cycle is configured (for example, the first field or the third field is configured), and the current DRX_SFN_COUNTER, SFN, and subframe number satisfy the following formula:

[0135] floor([(DRX_SFN_COUNTER×10240)+(SFN×10)+subframe number]modulo(non-integer long DRX cycle))=start offset,

[0136] If the terminal device does not configure DCP (DCI with CRC scrambled by PS_RNTI) monitoring for the activated downlink bandwidth part (BWP), it will start the wake-up timer for the above-mentioned DRX group after the drx-SlotOffset duration after the start of the subframe corresponding to the above-mentioned subframe number.

[0137] It is worth noting that the modulo calculation of the fraction in the above formula can refer to the previous method to avoid rounding errors.

[0138] According to the above embodiment, the problem that the DRX cycle does not support non-integer data arrival cycles is further solved.

[0139] In the embodiments of the present application, the inventors further discovered that for non-integer DRX cycles, since a rounding operation is used in the calculation formula for the start time of the DRX wake-up period, the DRX cycle is a rational number on average, but a single DRX cycle is actually an integer, and each DRX cycle is not necessarily exactly the same, and there may be a difference of 1 millisecond.

[0140] Figure 4 is a schematic diagram of an example of DRX configuration. In the example of Figure 4, taking the XR service frame rate of 60fps (corresponding to a period of 50 / 3ms) as an example, the DRX period (which can be a long DRX period or a short DRX period) is configured to 50 / 3 milliseconds, referring to the previous configuration method. When the starting offset is configured to 16ms, a problem may occur where a certain DRX period does not have a wake-up period, such as the third period in Figure 4. In this case, the terminal device will not be able to monitor the downlink control information, and thus cannot send or receive data, resulting in transmission delays.

[0141] In response to the above problems, the embodiments of the present application further provide solutions.

[0142] In some embodiments, the maximum value of the start offset is configured as floor(non-integer long DRX cycle)-1.

[0143] Still taking the example of the first information unit including the first field, which is a CHOICE structure and includes a non-integer long DRX cycle and a start offset corresponding to the frame rate, the difference from the previous embodiment is that the maximum value of the start offset is no longer a value obtained by rounding down the non-integer long DRX cycle, but a value obtained by rounding down the non-integer long DRX cycle -1, as follows:

[0144] The method according to the above embodiment solves the problem that the DRX cycle has no wake-up period.

[0145] In the above embodiment, the duration of the wake-up period of a non-integer DRX cycle can be set to be longer than the duration of the wake-up period of the DRX cycle corresponding to other values ​​of the maximum value of the starting offset. That is, the network side can configure a longer wake-up period (that is, a longer onDurationTimer) when the configuration offset is floor (non-integer long DRX cycle) - 1. In particular, the network side configures a longer wake-up period after the offset floor (non-integer long DRX cycle) corresponding to the expected arrival time of the periodic traffic, such as a value 1 millisecond larger than the usual configuration. Thus, the problem that the terminal device may start the wake-up period in advance due to the aforementioned configuration and thus miss the later arriving services is avoided.

[0146] In the above embodiment, when a non-integer DRX cycle is configured and the actual cycle length of the previous DRX cycle is equal to the value obtained by rounding down the non-integer DRX cycle plus 1, the terminal device extends the wake-up period of the current DRX cycle. That is, if the starting offset is configured as floor(non-integer long DRX cycle)-1, and the previous DRX cycle length is equal to floor(non-integer long DRX cycle)+1, the terminal device automatically extends the wake-up period of the current DRX cycle, for example, by 1 millisecond. Floor(non-integer long DRX cycle)+1 is also equal to ceil(non-integer long DRX cycle). Ceil(x) means rounding up x. The actual length of the previous DRX cycle can be determined by subtracting the start time of the wake-up period of the previous DRX cycle from the start time of the wake-up period of the current DRX cycle. Thus, the problem that the terminal device may start the wake-up period in advance due to the above configuration and miss the services that arrive later is avoided.

[0147] In some other embodiments, the maximum value of the start offset is still configured as floor (a non-integer long DRX cycle), and enhancement is performed on the UE side.

[0148] For example, if the wake-up period timer has not run after a DRX cycle has elapsed since the start of the last wake-up period timer, the terminal device starts the wake-up timer. That is, when the starting offset is configured as floor (a non-integer long DRX cycle), if the wake-up period timer has not run after a DRX cycle has elapsed since the start of the last wake-up period timer, the terminal device autonomously starts the wake-up period timer, that is, starts the wake-up period. The DRX cycle here can be floor (a non-integer long DRX cycle) + 1 millisecond. Thus, the problem of no wake-up period in the DRX cycle is also solved.

[0149] The above takes a non-integer long DRX cycle as an example, but the present application is not limited thereto, and a non-integer short DRX cycle can be deduced by analogy.

[0150] In the embodiments of the present application, the inventors further discovered that if the short DRX cycle is configured and is non-integer, and the long DRX cycle is also non-integer (still an integer multiple of the short DRX cycle), in certain configurations, the wake-up periods of the long and short DRX cycles may not align. For example, if the long DRX cycle is configured as 50 / 3ms, the short DRX cycle is configured as 25 / 3ms, and the start offset is configured as 15ms, the situation shown in Figure 5 may occur at certain moments. That is, at around 31ms and 48ms, the wake-up period of the short DRX cycle and the wake-up period of the long DRX cycle are not started at the same time. Because this situation does not comply with traditional protocol standards, it may cause unknown operations of some terminal devices and increase the complexity of device development.

[0151] In response to the above problems, the embodiments of the present application further provide solutions.

[0152] In some embodiments, when a non-integer long DRX cycle is configured, a short DRX cycle is not configured. That is, to address the aforementioned issue, non-integer short DRX cycles are not defined. Specifically, when supporting non-integer data cycle XR services, only a non-integer long DRX cycle can be configured. When a non-integer long DRX cycle is configured, a short DRX cycle is not configured. This approach simplifies implementation and reduces design complexity.

[0153] In other embodiments, when a non-integer short DRX cycle is configured, the long DRX cycle is an integer. That is, to address the aforementioned issue, when a non-integer short DRX cycle is configured, the long DRX cycle must be an integer, meaning the (existing) drx-LongCycleStartOffset must be used. This approach preserves the short DRX cycle, improves UE energy-saving flexibility, and better supports data bursts.

[0154] In an embodiment of the present application, in order to support better UE energy saving, the uplink HARQ (hybrid automatic repeat request) RTT (round-trip time) timer (drx-HARQ-RTT-TimerUL) may not be started for the uplink scheduled transmission of the configured grant (CG), thereby not starting retransmission, which is particularly important for short-cycle, delay-sensitive XR services.

[0155] In some embodiments, the network device may further send second configuration information to the terminal device, wherein the second configuration information configures disabling CG retransmission monitoring for configuration authorization. The second configuration information may include a second information unit, the second information unit including a sixth field, and the sixth field indicates disabling CG retransmission monitoring for configuration authorization.

[0156] In the above embodiment, the second configuration message may be, for example, an RRCReconfiguration message, the second information unit may be, for example, a ConfiguredGrantConfig IE, and the sixth field may be, for example, called disableCG-RetransmissionMonitoring, but the present application is not limited thereto. According to an embodiment of the present application, a configuration may be added to each configuration authorization to disable CG retransmission monitoring, that is, to prohibit starting the drx-HARQ-RTT-TimerUL timer for uplink configuration authorization transmission. Thus, the problem that CG does not support uplink retransmission-free is solved, and the energy saving of UEs containing delay-sensitive services, such as XR services, is enhanced.

[0157] In the above embodiment, if the configuration grant is a configuration grant containing multiple (multi-) PUSCH (Physical Uplink Shared CHannel), that is, the CG configuration contains multiple consecutive configuration uplink grants (configured uplink grant) within one period, then the configuration of the sixth field applies to all configuration uplink grants in the configuration grant, that is, all PUSCH transmission occasions (occasion). In some embodiments, when the sixth field is configured, the drx-HARQ-RTT-TimerUL timer is prohibited from being started for all configuration uplink grants in the CG. Thus, the problem that the CG with multiple PUSCHs does not support free uplink retransmission is solved, and the energy saving of UEs containing delay-sensitive services, such as XR services, is enhanced.

[0158] In some embodiments, if the serving cell of the terminal device is not configured with an uplink HARQ mode (uplink HARQ-Mode), and if the sixth field is not configured for the multiple PUSCH CGs to which the configured uplink grant belongs, then:

[0159] If drx-LastTransmissionUL is configured, the drx-HARQ-RT-TimerUL timer is started for the corresponding HARQ process at the first symbol after the last transmission (within the bundle) of the corresponding PUSCH transmission;

[0160] Otherwise, the drx-HARQ-RT-TimerUL timer is started for the corresponding HARQ process in the first symbol after the first transmission (within the bundle) of the corresponding PUSCH transmission.

[0161] The following is an example of enhancing the DRX process of TS 38.321 according to the method of the above embodiment:

[0162] The method of the above embodiment can be used when the DRX cycle is a non-integer, for example, it can be used in combination with the method of configuring a non-integer DRX cycle through the first configuration information in the previous embodiment, or it can be used when the DRX cycle is an integer, for example, it is not bound to the method of configuring a non-integer DRX cycle through the first configuration information in the previous embodiment and can be used alone. The present application is not limited to this.

[0163] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0164] The present application also provides a method for determining a DRX cycle, which is described from the perspective of a terminal device. It should be noted that this method is a UE-side process corresponding to the DRX cycle configuration method of the aforementioned embodiment, and the same contents as the aforementioned embodiment will not be repeated.

[0165] FIG6 is a schematic diagram of a method for determining a DRX cycle according to an embodiment of the present application. As shown in FIG6 , the method includes:

[0166] 610: The terminal device receives first configuration information sent by the network device, and the first configuration message configures a non-integer DRX cycle represented by one or more fractions; the first configuration information includes a first information unit, and the first information unit includes a field indicating a non-integer long DRX cycle and its starting offset and / or indicating a non-integer short DRX cycle.

[0167] In some embodiments, as described above, if the first field is configured, the terminal device ignores the configuration of the integer long DRX cycle and its corresponding starting offset.

[0168] In some embodiments, as described above, when the third field includes only the second integer, the terminal device may use the quotient of 1000 milliseconds and the second integer as a fraction to represent a non-integer long DRX cycle.

[0169] In some embodiments, as described above, if the third field is configured, the terminal device ignores the configuration of the integer long DRX cycle and its corresponding starting offset.

[0170] In some embodiments, as shown in FIG6 , the method may further include:

[0171] 620: The terminal device determines the time for starting the wake-up period of the non-integer DRX cycle. The method for determining the time for the wake-up period of the non-integer DRX cycle has been described above and will not be repeated here.

[0172] In the above embodiment, as mentioned above, if the maximum value of the starting offset is the value obtained by rounding down a non-integer DRX cycle minus 1, then if the wake-up period timer has not run after the length of a DRX cycle has passed since the start of the last wake-up period timer, the terminal device can start the wake-up timer.

[0173] The method according to the embodiment of the present application solves the problem that the DRX cycle does not support non-integer data reaching the cycle, and supports uplink retransmission-free transmission of multiple PUSCH configuration authorizations, thereby achieving UE energy saving.

[0174] Embodiments of the second aspect

[0175] The embodiment of the present application provides a DRX configuration method, which is described from the perspective of a network device. The same contents as those in the embodiment of the first aspect will not be repeated.

[0176] FIG7 is a schematic diagram of a DRX configuration method according to an embodiment of the present application. Referring to FIG7 , the method includes:

[0177] 710: The network device sends a second configuration message to the terminal device, and the second configuration message configures the disabling of CG retransmission monitoring for configuration authorization; the second configuration message includes a second information unit, and the second information unit includes a sixth field, and the sixth field indicates the disabling of CG retransmission monitoring for configuration authorization.

[0178] It is worth noting that FIG7 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG7 above.

[0179] According to the above embodiment, a configuration is added to each configuration authorization to disable CG retransmission monitoring, that is, the drx-HARQ-RTT-TimerUL timer is prohibited from being started for uplink configuration authorization transmission. This solves the problem of not supporting uplink retransmission-free when the CG includes a CG with multiple PUSCHs, and enhances UE energy saving for delay-sensitive services such as XR services.

[0180] In some embodiments, the second configuration information is an RRCReconfiguration message; and the second information unit is a ConfiguredGrantConfig IE. The present application is not limited thereto.

[0181] In some embodiments, when the sixth field is configured, all configured uplink grants in the above configured grants are prohibited from starting the drx-HARQ-RTT-TimerUL timer.

[0182] In the above embodiment, the configuration grant is a configuration grant containing multiple (multi-)PUSCH (Physical Uplink Shared CHannel), that is, the CG configuration contains multiple consecutive configured uplink grants (configured uplink grant) within one period, and the configuration of the sixth field is applicable to all configured uplink grants in the configuration grant, that is, all PUSCH transmission occasions (occasion).

[0183] In some embodiments, if the terminal device serving cell is not configured with an uplink HARQ mode, and if the sixth field is not configured for the multiple PUSCH CGs to which the configured uplink grant belongs, then:

[0184] If drx-LastTransmissionUL is configured, the drx-HARQ-RT-TimerUL timer is started for the corresponding HARQ process on the first symbol after the last transmission of the corresponding PUSCH transmission;

[0185] Otherwise, the drx-HARQ-RT-TimerUL timer is started for the corresponding HARQ process in the first symbol after the first transmission of the corresponding PUSCH transmission.

[0186] The present application also provides a method for implementing DRX configuration, which is described from the perspective of a terminal device. It should be noted that this method is a UE-side process corresponding to the DRX configuration method of the aforementioned embodiment, and the same contents as the aforementioned embodiment will not be repeated.

[0187] FIG8 is a schematic diagram of a method for implementing DRX configuration according to an embodiment of the present application. As shown in FIG8 , the method includes:

[0188] 810: The terminal device receives a second configuration message sent by the network device, and the second configuration message configures the disabling of CG retransmission monitoring for configuration authorization; the second configuration message includes a second information unit, and the second information unit includes a sixth field, and the sixth field indicates the disabling of CG retransmission monitoring for configuration authorization.

[0189] In some embodiments, as described above, if the serving cell of the terminal device is not configured with an uplink HARQ mode, and if the sixth field is not configured for the multiple PUSCH CGs to which the configured uplink grant belongs, then:

[0190] If drx-LastTransmissionUL is configured, the terminal device starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process on the first symbol after the last transmission of the corresponding PUSCH transmission;

[0191] Otherwise, the terminal device starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process in the first symbol after the first transmission of the corresponding PUSCH transmission.

[0192] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0193] According to the method of the embodiment of the present application, the problem of not supporting uplink retransmission-free when the CG includes a CG with multiple PUSCHs is solved, and the UE energy saving of delay-sensitive services such as XR services is enhanced.

[0194] Embodiments of the third aspect

[0195] An embodiment of the present application provides a device for configuring a DRX cycle.

[0196] FIG9 is a schematic diagram of a DRX cycle configuration apparatus according to an embodiment of the present application. The apparatus may be, for example, a network device or one or more components or assemblies configured within the network device. Because the principle underlying the problem solved by the apparatus is the same as that of the method shown in FIG3 of the embodiment of the first aspect, its specific implementation may refer to the implementation of the method shown in FIG3 of the embodiment of the first aspect, and the same details will not be repeated here.

[0197] As shown in FIG9 , the DRX cycle configuration apparatus 900 includes:

[0198] A first sending unit 910 sends a first configuration message to a terminal device, wherein the first configuration message configures a non-integer DRX cycle represented by one or more fractions; the first configuration information includes a first information unit, which includes a field indicating a non-integer long DRX cycle and its starting offset and / or indicating a non-integer short DRX cycle.

[0199] In some embodiments, the first configuration message is an RRCReconfiguration message.

[0200] In some embodiments, the first information unit is a DRX-Config IE.

[0201] In some embodiments, the first information unit includes a first field including a combination of a non-integer long DRX cycle corresponding to a frame rate and a start offset.

[0202] In the above embodiment, the first field may be a CHOICE structure, and each element in the CHOICE structure is a combination of a predefined non-integer long DRX cycle corresponding to a certain frame rate and its corresponding starting offset in milliseconds.

[0203] In the above embodiment, a non-integer long DRX cycle can be expressed by a fraction in milliseconds, which is expressed by an integer numerator and denominator; the starting offset corresponding to each non-integer long DRX cycle ranges from 0 to a value rounded down to the non-integer long DRX cycle.

[0204] In the above embodiment, the non-integer long DRX cycle may include multiple fractional values, which correspond to the following frame rates: 15fps, 30fps, 45fps, 60fps, 72fps, 90fps, and 120fps.

[0205] In the above embodiment, if the first field is configured, the terminal device may ignore the configuration of the integer long DRX cycle and its corresponding starting offset.

[0206] In the above embodiment, the first information unit may further include a second field, where the second field includes a non-integer short DRX cycle corresponding to the frame rate.

[0207] In the above embodiment, the second field may be of enumeration type.

[0208] In the above embodiment, the non-integer short DRX cycle may be expressed by a fraction in milliseconds.

[0209] In the above embodiment, if the second field is configured, the value of the non-integer long DRX cycle in the first field is an integer multiple of the value of the non-integer short DRX cycle in the second field.

[0210] In the above embodiment, if the second field is configured, the terminal device can ignore the configuration of the integer short DRX cycle.

[0211] In some other embodiments, the first information unit includes a third field and a fourth field, the third field includes a non-integer long DRX cycle corresponding to the frame rate, and the fourth field includes a starting offset for the non-integer long DRX cycle.

[0212] In the above embodiment, the third field may include a first integer and a second integer; the first integer is the numerator in the fractional expression of the non-integer long DRX cycle, and the second integer is the denominator in the fractional expression of the non-integer long DRX cycle.

[0213] In the above embodiment, the value range of the first integer can be the range of changes in the numerator in the fractional expression of the supported non-integer long DRX cycle; the value range of the second integer can be the range of changes in the denominator in the fractional expression of the supported non-integer long DRX cycle.

[0214] In the above embodiment, the first integer and the second integer can be enumeration types respectively; the value range of the first integer includes the fixed value of the numerator in the fractional expression of the supported non-integer long DRX cycle, and may also include reserved spare bits; the value range of the second integer includes the fixed value of the denominator in the fractional expression of the supported non-integer long DRX cycle, and may also include reserved spare bits.

[0215] In the above embodiment, the third field may only include the second integer; the second integer represents a non-integer long DRX cycle, and the terminal device uses the quotient of 1000 milliseconds and the second integer as a fraction to represent the non-integer long DRX cycle.

[0216] In the above embodiment, the fourth field may be of integer type, with a value ranging from 0 to a value rounded down to the maximum non-integer long DRX cycle supported.

[0217] In the above embodiment, when the third field is configured, the fourth field must be configured.

[0218] In the above embodiment, when the third field is configured, the terminal device may ignore the configuration of the integer long DRX cycle and its corresponding starting offset.

[0219] In the above embodiment, the first information unit may further include a fifth field, where the fifth field includes a non-integer short DRX cycle corresponding to the frame rate.

[0220] In the above embodiment, the fifth field may include a third integer and a fourth integer; the third integer is the numerator in the fractional expression of the non-integer short DRX cycle, and the fourth integer is the denominator in the fractional expression of the non-integer short DRX cycle.

[0221] In the above embodiment, the value range of the third integer can be the range of changes in the numerator in the fractional expression of the supported non-integer short DRX cycle; the value range of the fourth integer can be the range of changes in the denominator in the fractional expression of the supported non-integer short DRX cycle.

[0222] In the above embodiment, the third integer and the fourth integer can be enumerated types respectively; the value range of the third integer includes the fixed value of the numerator in the fractional expression of the supported non-integer short DRX cycle, and may also include reserved spare bits; the value range of the fourth integer includes the fixed value of the denominator in the fractional expression of the supported non-integer short DRX cycle, and may also include reserved spare bits.

[0223] In the above embodiment, the fifth field may also only include the fourth integer; the fourth integer represents a non-integer short DRX cycle, and the terminal device uses the quotient of 1000 milliseconds and the fourth integer as a fraction to represent the non-integer short DRX cycle.

[0224] In the above embodiment, if the fifth field is configured, the value of the non-integer long DRX cycle in the third field is an integer multiple of the value of the non-integer short DRX cycle in the fifth field.

[0225] In some embodiments, the terminal device determines a time to start a wake-up period of said non-integer DRX cycle.

[0226] In the above embodiment, in some implementations, if a short DRX cycle is used for a certain DRX group, and a non-integer short DRX cycle is configured, and the current first counter, system frame number, and subframe number satisfy the following formula:

[0227] floor([(first counter×10240)+(system frame number×10)+subframe number]modulo(non-integer short DRX cycle))=floor([(time reference system frame number×10)+start offset)]modulo(non-integer short DRX cycle)),

[0228] The terminal device then starts a wake-up timer for the DRX group after the time slot offset length after the start of the subframe corresponding to the subframe number.

[0229] In the above embodiment, in other implementations, if a long DRX cycle is used for a certain DRX group, and a non-integer long DRX cycle is configured, and the current first counter, system frame number, and subframe number satisfy the following formula:

[0230] floor([(first counter×10240)+(system frame number×10)+subframe number]modulo(non-integer long DRX cycle))=floor([(time reference system frame number×10)+start offset)]modulo(non-integer long DRX cycle)),

[0231] The terminal device starts a wake-up timer for the DRX group after the time slot offset length after the start of the subframe corresponding to the subframe number, without configuring downlink control information (DCP) monitoring with cyclic redundancy check encrypted by the energy-saving wireless network temporary identifier for the activated downlink bandwidth part.

[0232] In the aforementioned embodiment, A module B in the above formula can be replaced by A-floor(A*N2 / N1)*N1 / N2; where B=N1 / N2, and the calculation is performed in the order of the operators in A-floor(A*N2 / N1)*N1 / N2 from left to right.

[0233] In the aforementioned embodiment, the DRX groups may share the following parameters: a non-integer long DRX cycle, a starting offset corresponding to the non-integer long DRX cycle, a non-integer short DRX cycle, and a time reference frame number.

[0234] In some embodiments, the terminal device may also initialize the first counter, for example, initialize the first counter to 0 upon receiving the first configuration message; and add 1 to the first counter at the first character time of the time slot when the SFN changes to 0.

[0235] In some embodiments, the terminal device may initialize the first counter according to the time reference SFN included in the received first configuration message.

[0236] For example, if the time reference SFN is 0, the terminal device initializes the first counter to 0 when receiving the first configuration message.

[0237] For another example, if the time reference SFN is 512, the terminal device initializes the first counter to 0 when the SFN when receiving the first configuration message is the second half of the SFN cycle, and initializes the first counter to 1 when the SFN when receiving the first configuration message is the first half of the SFN cycle.

[0238] According to the above method, synchronization of the first counter between the network side and the terminal side can be achieved.

[0239] In the above embodiment, since the network side and the terminal side have already achieved synchronization of the first counter, the time reference SFN in the above formula can be omitted.

[0240] For example, when the terminal device determines the time to start the wake-up period of a non-integer DRX cycle, if a short DRX cycle is used for a DRX group, and a non-integer short DRX cycle is configured, and the current first counter, SFN, and subframe number satisfy the following formula:

[0241] floor([(first counter×10240)+(SFN×10)+subframe number]modulo(non-integer short DRX cycle))=floor((start offset)modulo(non-integer short DRX cycle)),

[0242] The terminal device starts the wake-up timer for the above-mentioned DRX group after the time slot offset length after the start of the subframe corresponding to the above-mentioned subframe number.

[0243] For another example, when the terminal device determines the time to start the wake-up period of a non-integer DRX cycle, if a long DRX cycle is used for a certain DRX group, and a non-integer long DRX cycle is configured, and the current first counter, SFN, and subframe number satisfy the following formula:

[0244] floor([(first counter×10240)+(SFN×10)+subframe number]modulo(non-integer long DRX cycle))=start offset,

[0245] If the terminal device does not configure DCP monitoring for the activated downlink bandwidth part, it starts the wake-up timer for the above-mentioned DRX group after the time slot offset length after the start of the subframe corresponding to the above-mentioned subframe number.

[0246] In some embodiments, the maximum value of the start offset is configured to be a value obtained by rounding down a non-integer DRX cycle minus 1.

[0247] In the above embodiment, the duration of the wake-up period of a non-integer DRX cycle may be longer than the duration of the wake-up period of a DRX cycle corresponding to other values ​​of the maximum value of the start offset.

[0248] In the above embodiment, when a non-integer DRX cycle is configured and the actual cycle length of the previous DRX cycle is equal to the value obtained by rounding down the non-integer DRX cycle plus 1, the terminal device can extend the wake-up period of the current DRX cycle.

[0249] In some other embodiments, the maximum value of the above-mentioned starting offset is configured as a value obtained by rounding down a non-integer DRX cycle.

[0250] In the above embodiment, if the wake-up period timer has not run after the length of a DRX cycle has elapsed since the start of the last wake-up period timer, the terminal device starts the wake-up timer.

[0251] In the aforementioned embodiments, the non-integer DRX cycle may be a non-integer long DRX cycle and / or a non-integer short DRX cycle.

[0252] In some embodiments, when a non-integer long DRX cycle is configured, a short DRX cycle is not configured; or, when a non-integer short DRX cycle is configured, the long DRX cycle is an integer.

[0253] In some embodiments, as shown in FIG9 , the apparatus 900 further includes:

[0254] The second sending unit 920 sends a second configuration message to the terminal device, and the second configuration message configures the disabling of CG retransmission monitoring for configuration authorization; the second configuration message contains a second information unit, and the second information unit includes a sixth field, and the sixth field indicates the disabling of CG retransmission monitoring for configuration authorization.

[0255] In the above embodiment, the second configuration information may be an RRCReconfiguration message; and the second information unit may be a ConfiguredGrantConfig IE.

[0256] In the above embodiment, when the sixth field is configured, starting the drx-HARQ-RTT-TimerUL timer is prohibited for all configuration uplink grants in the configuration grant.

[0257] In the above embodiment, if the serving cell of the terminal device is not configured with an uplink HARQ mode, and if the sixth field is not configured for the multiple PUSCH CGs to which the configured uplink grant belongs, then:

[0258] If drx-LastTransmissionUL is configured, the terminal device starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process on the first symbol after the last transmission of the corresponding PUSCH transmission;

[0259] Otherwise, the terminal device starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process in the first symbol after the first transmission of the corresponding PUSCH transmission.

[0260] An embodiment of the present application also provides a DRX configuration device.

[0261] Figure 10 is a schematic diagram of a DRX configuration apparatus according to an embodiment of the present application. This apparatus may be, for example, a network device or one or more components or assemblies configured within the network device. Because the principle underlying the problem solved by this apparatus is the same as the method illustrated in Figure 7 of the embodiment of the second aspect, its specific implementation may refer to the implementation of the method illustrated in Figure 7 of the embodiment of the second aspect, and the details of the commonality will not be repeated.

[0262] As shown in FIG10 , the DRX configuration apparatus 1000 includes:

[0263] Sending unit 1010, which sends a second configuration message to the terminal device, wherein the second configuration message configures the disabling of CG retransmission monitoring for configuration authorization; the second configuration message contains a second information unit, and the second information unit includes a sixth field, and the sixth field indicates the disabling of CG retransmission monitoring for configuration authorization.

[0264] In some embodiments, the second configuration information is an RRCReconfiguration message; the second information unit is a ConfiguredGrantConfig IE.

[0265] In some embodiments, when the sixth field is configured, all configured uplink grants in the above configured grants are prohibited from starting the drx-HARQ-RTT-TimerUL timer.

[0266] In some embodiments, if the serving cell of the terminal device is not configured with an uplink HARQ mode, and if the sixth field is not configured for the multiple PUSCH CGs to which the configured uplink grant belongs, then:

[0267] If drx-LastTransmissionUL is configured, the terminal device starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process on the first symbol after the last transmission of the corresponding PUSCH transmission;

[0268] Otherwise, the terminal device starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process in the first symbol after the first transmission of the corresponding PUSCH transmission.

[0269] An embodiment of the present application also provides a device for determining a DRX cycle.

[0270] FIG11 is a schematic diagram of a device for determining a DRX cycle according to an embodiment of the present application. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. Since the principle of solving the problem by the device is the same as that of the method shown in FIG6 of the embodiment of the first aspect, and corresponds to the device shown in FIG9 of the above embodiment, its specific implementation may refer to the implementation of the method shown in FIG6 of the embodiment of the first aspect and the implementation of the device shown in FIG9 of the above embodiment, and the same contents will not be repeated here.

[0271] As shown in FIG11 , the DRX cycle determination device 1100 includes:

[0272] A receiving unit 1110 receives first configuration information sent by a network device, where the first configuration message configures a non-integer DRX cycle represented by one or more fractions; the first configuration information includes a first information unit, where the first information unit includes a field indicating a non-integer long DRX cycle and its starting offset and / or indicating a non-integer short DRX cycle.

[0273] In some embodiments, as shown in FIG11 , the apparatus 1100 further includes: a processing unit 1120 .

[0274] In some embodiments, as described above, if the first field is configured, the processing unit 1120 ignores the configuration of the integer long DRX cycle and its corresponding starting offset.

[0275] In some embodiments, as described above, when the third field includes only the second integer, the processing unit 1120 may use the quotient of 1000 milliseconds and the second integer as a fraction to represent a non-integer long DRX cycle.

[0276] In some embodiments, as described above, if the third field is configured, the processing unit 1120 ignores the configuration of the integer long DRX cycle and its corresponding starting offset.

[0277] In some embodiments, as shown in FIG11 , the apparatus 1100 may further include:

[0278] The determining unit 1130 is configured to determine the time for starting the wake-up period of the non-integer DRX cycle. The method for determining the time for the wake-up period of the non-integer DRX cycle has been described above and will not be repeated here.

[0279] In the above embodiment, as described above, if the maximum value of the starting offset is a value obtained by rounding down a non-integer DRX cycle minus 1, then if the wake-up period timer has not run after the length of a DRX cycle has passed since the start of the previous wake-up period timer, the determination unit 1130 can start the wake-up timer.

[0280] An embodiment of the present application also provides a device for implementing DRX configuration.

[0281] Figure 12 is a schematic diagram of an apparatus for implementing a DRX configuration according to an embodiment of the present application. This apparatus may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. Because the principle of solving the problem of this apparatus is the same as that of the method shown in Figure 8 of the embodiment of the second aspect, and corresponds to the apparatus shown in Figure 10 of the aforementioned embodiment, its specific implementation may refer to the implementation of the method shown in Figure 8 of the embodiment of the second aspect and the implementation of the apparatus shown in Figure 10 of the aforementioned embodiment, and the details of the same content will not be repeated here.

[0282] As shown in FIG12 , the DRX configuration implementation apparatus 1200 includes:

[0283] Receiving unit 1210 receives a second configuration message sent by the network device, and the second configuration message configures the disabling of CG retransmission monitoring for configuration authorization; the second configuration message contains a second information unit, and the second information unit includes a sixth field, and the sixth field indicates the disabling of CG retransmission monitoring for configuration authorization.

[0284] In some embodiments, as shown in FIG12 , the apparatus 1200 may further include: a processing unit 1220 .

[0285] In some embodiments, as described above, if the serving cell of the terminal device is not configured with an uplink HARQ mode, and if the sixth field is not configured for the multiple PUSCH CGs to which the configured uplink grant belongs, then:

[0286] If drx-LastTransmissionUL is configured, the processing unit 1220 starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process on the first symbol after the last transmission of the corresponding PUSCH transmission;

[0287] Otherwise, the processing unit 1220 starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process in the first symbol after the first transmission of the corresponding PUSCH transmission.

[0288] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The devices 900, 1000, 1100, and 1200 of the embodiments of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0289] In addition, for the sake of simplicity, Figures 9 to 12 only illustrate the connection relationships or signal paths between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0290] According to the device of the embodiment of the present application, the UE energy saving effect is achieved.

[0291] Embodiments of the fourth aspect

[0292] The present application provides a communication system including a terminal device and a network device, wherein the network device is configured to perform the method described in the first or second aspect. The behavior of the network device has been described in detail in the first to third aspects, and the details are incorporated herein and will not be repeated here.

[0293] An embodiment of the present application also provides a network device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method described in Figure 3 of the embodiment of the first aspect or the method described in Figure 7 of the embodiment of the second aspect.

[0294] Figure 13 is a schematic diagram of a network device according to an embodiment of the present application. As shown in Figure 13, network device 1300 may include a central processing unit (CPU) 1310 and a memory 1320; memory 1320 is coupled to CPU 1310. Memory 1320 can store various data and information processing programs, which are executed under the control of CPU 1310 to receive various information from terminal devices and send various information to terminal devices.

[0295] For example, the processor 1310 may be configured to execute a program to implement the method described in FIG. 3 in the embodiment of the first aspect or the method described in FIG. 7 in the embodiment of the second aspect.

[0296] In addition, as shown in FIG13 , network device 1300 may further include: a transceiver 1330 and an antenna 1340, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 1300 does not necessarily include all the components shown in FIG3 ; in addition, network device 1300 may also include components not shown in FIG13 , and reference may be made to the prior art for details.

[0297] An embodiment of the present application also provides a terminal device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method described in Figure 6 of the embodiment of the first aspect or the method described in Figure 8 of the embodiment of the second aspect.

[0298] Figure 14 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 14 , terminal device 1400 may include a processor 1410 and a memory 1420. Memory 1420 stores data and programs and is coupled to processor 1410. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0299] For example, the processor 1410 may be configured to execute a program to implement the method described in FIG. 6 in the embodiment of the first aspect or the method described in FIG. 8 in the embodiment of the second aspect.

[0300] As shown in Figure 14 , the terminal device 1400 may further include: a communication module 1430, an input unit 1440, a display 1450, and a power supply 1460. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1400 does not necessarily include all of the components shown in Figure 14 , and these components are not essential. Furthermore, the terminal device 1400 may also include components not shown in Figure 14 , for which reference may be made to the prior art.

[0301] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a network device, the program enables the computer to execute the method described in Figure 3 of the embodiment of the first aspect or the method described in Figure 7 of the embodiment of the second aspect in the network device.

[0302] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in FIG3 of the embodiment of the first aspect or the method described in FIG7 of the embodiment of the second aspect in a network device.

[0303] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program enables the computer to execute the method described in Figure 6 of the embodiment of the first aspect or the method described in Figure 8 of the embodiment of the second aspect in the terminal device.

[0304] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in FIG6 of the embodiment of the first aspect or the method described in FIG8 of the embodiment of the second aspect in a terminal device.

[0305] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0306] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0307] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0308] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as 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 device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0309] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0310] Regarding the above implementation methods disclosed in this embodiment, the following additional notes are also disclosed:

[0311] 1. A method for configuring a DRX cycle, wherein the method comprises:

[0312] The network device sends a first configuration message to the terminal device, where the first configuration message configures a non-integer DRX cycle represented by one or more fractions;

[0313] The first configuration information includes a first information unit, which includes a field indicating a non-integer long DRX cycle and a starting offset thereof and / or a field indicating a non-integer short DRX cycle.

[0314] 2. The method according to Supplement 1, wherein:

[0315] The first information unit further includes a fifth field, wherein the fifth field includes a non-integer short DRX cycle corresponding to the frame rate;

[0316] The fifth field includes a third integer and a fourth integer;

[0317] The third integer is a numerator in a fractional expression of the non-integer short DRX cycle, and the fourth integer is a denominator in the fractional expression of the non-integer short DRX cycle.

[0318] 3. The method according to Supplementary Note 2, wherein:

[0319] The third integer and the fourth integer are respectively of enumeration type;

[0320] The value range of the third integer includes a fixed value of the numerator in the fractional expression of the supported non-integer short DRX cycle;

[0321] The value range of the fourth integer includes a fixed value of the denominator in the fractional expression of the supported non-integer short DRX cycle.

[0322] 4. The method according to Supplement 1, wherein:

[0323] The first information unit further includes a fifth field, wherein the fifth field includes a non-integer short DRX cycle corresponding to the frame rate;

[0324] The fifth field includes a fourth integer;

[0325] The fourth integer represents a non-integer short DRX cycle, and the terminal device uses the quotient of 1000 milliseconds and the fourth integer as a fraction to represent the non-integer short DRX cycle.

[0326] 5. The method according to Supplement 1, wherein:

[0327] The terminal device determines a time to start a wake-up period of the non-integer DRX cycle, wherein:

[0328] If a short DRX cycle is used for a DRX group, and a non-integer short DRX cycle is configured, and the current first counter, system frame number, and subframe number satisfy the following formula:

[0329] floor([(first counter×10240)+(system frame number×10)+subframe number]modulo(non-integer short DRX cycle))=floor([(time reference system frame number×10)+start offset)]modulo(non-integer short DRX cycle)),

[0330] The terminal device then starts a wake-up timer for the DRX group after the time slot offset length after the start of the subframe corresponding to the subframe number.

[0331] 6. The method according to Supplement 1, wherein:

[0332] The terminal device determines a time to start a wake-up period of the non-integer DRX cycle, wherein:

[0333] If a long DRX cycle is used for a DRX group, and a non-integer long DRX cycle is configured, and the current first counter, system frame number, and subframe number satisfy the following formula:

[0334] floor([(first counter×10240)+(system frame number×10)+subframe number]modulo(non-integer long DRX cycle))=floor([(time reference system frame number×10)+start offset)]modulo(non-integer long DRX cycle)),

[0335] The terminal device starts a wake-up timer for the DRX group after the time slot offset length after the start of the subframe corresponding to the subframe number, without configuring downlink control information (DCP) monitoring with cyclic redundancy check encrypted by the energy-saving wireless network temporary identifier for the activated downlink bandwidth part.

[0336] 7. The method according to Supplement 5 or 6, wherein:

[0337] A module B in the formula is replaced by A-floor(A*N2 / N1)*N1 / N2;

[0338] Wherein, B=N1 / N2, and the calculation is performed according to the order of the operators in A-floor(A*N2 / N1)*N1 / N2 from left to right.

[0339] 8. The method according to Supplement 5 or 6, wherein:

[0340] The DRX groups share the following parameters: a non-integer long DRX cycle, a starting offset corresponding to the non-integer long DRX cycle, a non-integer short DRX cycle, and a time reference frame number.

[0341] 9. The method according to Supplement 1, wherein:

[0342] When the non-integer long DRX cycle is configured, the short DRX cycle is not configured; or when the non-integer short DRX cycle is configured, the long DRX cycle is an integer.

[0343] 10. The method according to Supplement 5 or 6, wherein:

[0344] The terminal device initializes the first counter to 0 when receiving the first configuration message; the terminal device adds 1 to the first counter at the first character time of the time slot when the SFN changes to 0.

Claims

1. A DRX cycle configuration device, configured in a network device, wherein: The device comprises: A first sending unit, which sends a first configuration message to a terminal device, where the first configuration message configures a non-integer DRX cycle represented by one or more fractions; The first configuration information includes a first information unit, which includes a field indicating a non-integer long DRX cycle and a starting offset thereof and / or indicating a non-integer short DRX cycle.

2. The device according to claim 1, wherein: The first information unit is DRX-Config IE.

3. The device according to claim 1, wherein: The first information unit includes a first field and a second field; The first field includes a combination of a non-integer long DRX cycle and a start offset corresponding to a frame rate; The second field includes a non-integer short DRX cycle corresponding to a frame rate.

4. The device according to claim 3, wherein: The first field is a CHOICE structure, and each element in the CHOICE structure is a combination of a predefined non-integer long DRX cycle corresponding to a certain frame rate and its corresponding starting offset in milliseconds.

5. The device according to claim 4, wherein: The non-integer long DRX cycle is expressed by a fraction in milliseconds, wherein the fraction is expressed by an integer numerator and a denominator; The value range of the starting offset corresponding to each non-integer long DRX cycle is 0 to a value obtained by rounding down the non-integer long DRX cycle.

6. The device according to claim 4, wherein: If the first field is configured, the terminal device ignores the configuration of an integer long DRX cycle and its corresponding starting offset.

7. The device according to claim 3, wherein: The non-integer short DRX cycle is expressed by a fraction in milliseconds.

8. The device according to claim 3, wherein: If the second field is configured, the value of the non-integer long DRX cycle in the first field is an integer multiple of the value of the non-integer short DRX cycle in the second field; and / or, If the second field is configured, the terminal device ignores the configuration of an integer short DRX cycle.

9. The device according to claim 1, wherein: The terminal device determines the time to start the wake-up period of the non-integer DRX cycle, wherein: If a short DRX cycle is used for a DRX group, and a non-integer short DRX cycle is configured, and the current first counter, system frame number, and subframe number satisfy the following formula: floor([(first counter × 10240) + (system frame number × 10) + subframe number] modulo(non-integer short DRX cycle)) = floor([(time reference system frame number × 10) + start offset)] modulo(non-integer short DRX cycle)), The terminal device then starts a wake-up timer for the DRX group after a time slot offset duration after the start of the subframe corresponding to the subframe number.

10. The device according to claim 9, wherein: The first configuration message includes a time reference system frame number; the terminal device initializes the first counter according to the time reference system frame number; If the time reference system frame number is 0, the terminal device initializes the first counter to 0 upon receiving the first configuration message; If the time reference system frame number is 512, the terminal device initializes the first counter to 0 when the SFN when the first configuration message is received is the second half of the SFN cycle, and initializes the first counter to 1 when the SFN when the first configuration message is received is the first half of the SFN cycle.

11. The device according to claim 10, wherein: The formula is transformed into the following: floor([(first counter×10240)+(SFN×10)+subframe number]modulo(non-integer short DRX cycle)) = floor((start offset) modulo(non-integer short DRX cycle)).

12. The device according to claim 1, wherein: The terminal device determines the time to start the wake-up period of the non-integer DRX cycle, wherein: If a long DRX cycle is used for a certain DRX group, and a non-integer long DRX cycle is configured, and the current first counter, system frame number, and subframe number satisfy the following formula: floor([(first counter × 10240) + (system frame number × 10) + subframe number] modulo(non-integer length DRX cycle)) = floor([(time reference system frame number × 10) + start offset)] modulo(non-integer length DRX cycle)), Then, the terminal device starts a wake-up timer for the DRX group after the time slot offset length after the start of the subframe corresponding to the subframe number, without configuring downlink control information (DCP) monitoring with cyclic redundancy check encrypted by the energy-saving wireless network temporary identifier for the activated downlink bandwidth part.

13. The device according to claim 12, wherein: The first configuration message includes a time reference system frame number; the terminal device initializes the first counter according to the time reference system frame number; If the time reference system frame number is 0, the terminal device initializes the first counter to 0 upon receiving the first configuration message; If the time reference system frame number is 512, the terminal device initializes the first counter to 0 when the SFN when the first configuration message is received is the second half of the SFN cycle, and initializes the first counter to 1 when the SFN when the first configuration message is received is the first half of the SFN cycle.

14. The device according to claim 13, wherein: The formula is transformed into the following: floor([(first counter×10240)+(SFN×10)+subframe number]modulo(non-integer long DRX cycle Period)) = starting offset.

15. The device according to claim 12, wherein: The DRX groups share the following parameters: a non-integer long DRX cycle, a starting offset corresponding to the non-integer long DRX cycle, a non-integer short DRX cycle, and a time reference frame number.

16. The device according to claim 1, wherein The maximum value of the starting offset is a value obtained by rounding down a non-integer DRX cycle minus 1.

17. The device according to claim 16, wherein: If the wake-up period timer has not run after the length of a DRX cycle has passed since the start of the last wake-up period timer, the terminal device starts the wake-up timer.

18. A DRX cycle configuration device, configured in a network device, wherein: The device comprises: A sending unit, which sends a second configuration message to the terminal device, wherein the second configuration message configures disabling CG retransmission monitoring for configuration authorization; The second configuration message includes a second information unit, the second information unit includes a sixth field, the Field six indicates disabling CG retransmission monitoring for configuration authorization.

19. The device according to claim 18, wherein: The second configuration information is an RRCReconfiguration message; The second information unit is ConfiguredGrantConfig IE.

20. The device according to claim 18, wherein If the serving cell of the terminal device is not configured with an uplink HARQ mode, and if the sixth field is not configured for the multiple PUSCH CGs to which the configured uplink grant belongs, then: If drx-LastTransmissionUL is configured, the terminal device starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process in the first symbol after the last transmission of the corresponding PUSCH transmission; Otherwise, the terminal device starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process in the first symbol after the first transmission of the corresponding PUSCH transmission.

Images