Method and apparatus for configuring discontinuous reception cycle

Abstract

Provided in the embodiments of the present application are a method and apparatus for configuring a discontinuous reception (DRX) cycle. The method comprises: a network device sending a first message to a terminal device, wherein the first message is configured with a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle, and the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle. According to the embodiments of the present application, DRX-related enhancement is performed in an RRC and / or MAC layer, so as to solve the problems of DRX configuration and operation in the case of different XR service cycles and multiple XR service flows, thereby better supporting UE energy saving for XR services and streaming media services.

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 3GPP Release 18 introduced non-integer long DRX (Discontinuous Reception) cycles and non-integer short DRX cycles, and defined some non-integer cycle values. However, the current non-integer cycle values ​​do not fully match the requirements of all XR and streaming services. For example, non-integer long DRX cycles and non-integer short DRX cycles do not fully match, resulting in not all XR and streaming services supporting UE energy saving.

[0008] 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 DRX cycle.

[0009] According to one aspect of an embodiment of the present application, a DRX cycle configuration apparatus is provided, configured in a network device, the apparatus including:

[0010] A sending unit sends a first message to a terminal device, wherein the first message configures a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle; the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle.

[0011] According to another aspect of an embodiment of the present application, a DRX cycle configuration device is provided, configured in a network device, the device including:

[0012] A sending unit sends a first message to a terminal device, wherein the first message configures a short DRX cycle and a long DRX cycle corresponding to the short DRX cycle. If the short DRX cycle is a non-integer, the long DRX cycle is a non-integer.

[0013] 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 DRX configuration and operation problems in different XR service cycles and multiple XR service flows are solved, and UE energy saving for XR services and streaming services is better supported.

[0014] 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.

[0015] 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.

[0016] 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

[0017] 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.

[0018] 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:

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

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

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

[0022] FIG4 is a schematic diagram of a method for determining a DRX cycle according to an embodiment of the first aspect of the present application;

[0023] FIG5 is a schematic diagram of a method for configuring a DRX cycle according to an embodiment of the second aspect of the present application;

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

[0025] FIG7 is a schematic diagram of a DRX cycle configuration device according to an embodiment of the third aspect of the present application;

[0026] FIG8 is a schematic diagram of a device for determining a DRX cycle according to an embodiment of the third aspect of the present application;

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

[0028] FIG10 is another schematic diagram of a device for determining a DRX cycle according to an embodiment of the third aspect of the present application;

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

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

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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, pico, etc.). The term "base station" may include some or all of their 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 the term is used.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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:

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

[0043] - 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).

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

[0045] - 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.

[0046] - 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).

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

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

[0049] - 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.

[0050] - 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.

[0051] - 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).

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

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] The inventors have found 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, 24, 30, 45, 60, 72, 75, 80, 90, and 120 frames per second correspond to non-integer data periods (66.66, 41.66, 33.33, 22.22, 16.66, 13.88, 13.33, 12.5, 11.11, and 8.33 milliseconds, respectively).

[0058] The current DRX cycle is defined as a different integer value in milliseconds. To reduce power consumption when the UE is using XR services, the DRX cycle can be matched to the data arrival cycle (e.g., the data cycle of the XR service), and the wake-up period and the data arrival time can be roughly aligned. In this way, when 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 not an 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.

[0059] 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.

[0060] The inventors discovered that 3GPP Rel-18 introduced non-integer long and short DRX cycles and defined some non-integer cycle values. However, the current non-integer cycle values ​​do not fully meet the requirements of all XR and streaming services. For example, non-integer long and non-integer short DRX cycles do not fully match, resulting in not all XR and streaming services supporting UE energy saving.

[0061] Therefore, considering the periodic characteristics of XR service traffic, how to solve the mismatch between the DRX cycle and the data arrival cycle requires further standardization and technical implementation.

[0062] Currently, long and short DRX cycles can flexibly support service changes. For XR services, due to their high latency requirements, if a short DRX cycle is configured, the long DRX cycle will not be too long to avoid failing to meet the latency budget. For example, the long DRX cycle can be set to 2 or 3 times the short DRX cycle. If the short DRX cycle is a non-integer (fraction, decimal, or rational number), the long DRX cycle (2 or 3 times the short DRX cycle) can be either a non-integer or an integer.

[0063] For example, for a service with an 80 fps (frames per second) frame rate, the data arrival period is 12.5 milliseconds, or 25 / 2 milliseconds. A short DRX cycle of 25 / 2 milliseconds can be defined, and then a long DRX cycle can be used that is twice and / or three times the short DRX cycle. Twice 25 / 2 milliseconds is 25 milliseconds, an integer period; three times 25 / 2 milliseconds is 75 / 2 milliseconds, still a non-integer period. Similar examples include services with frame rates of 24 fps, 60 fps, and 75 fps.

[0064] The current standard only supports configuring both long and short DRX cycles as integers or fractions. It does not support configuring both a non-integer short DRX cycle and an integer long DRX cycle. To support the DRX cycles corresponding to the frame rates in the above example, DRX configuration needs to be enhanced.

[0065] 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.

[0066] Embodiments of the first aspect

[0067] 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:

[0068] 310: The network device sends a first message to the terminal device, where the first message configures a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle, where the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle.

[0069] It is worth noting that FIG3 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.

[0070] According to the above embodiment, both a non-integer short DRX cycle (drx-NonIntegerShortCycle) and an integer long DRX cycle (drx-LongCycle / drx-LongCycleStartOffset) can be configured. This means that the terminal can use both a non-integer short DRX cycle and an integer long DRX cycle simultaneously. This solves the mismatch between the DRX cycle and the XR service cycle, and achieves UE energy conservation.

[0071] In some embodiments, the first message includes a first IE (Information Element), the first IE including a first field, the first field including an integer long DRX cycle and its corresponding starting offset. The integer long DRX cycle and its corresponding starting offset are both in milliseconds.

[0072] In the above embodiment, the first message is, for example, an RRCReconfiguration message, the first IE is, for example, a DRX-Config IE, and the first field is, for example, drx-LongCycleStartOffset-r18. In this embodiment, a first field is added to the first IE to indicate an integer long DRX cycle (drx-LongCycle) and its corresponding start offset (drx-StartOffset).

[0073] In some embodiments, the integer long DRX cycle in the first field is an integer multiple of some (part of) non-integer short DRX cycles, which can ensure that the DRX cycle matches the XR service cycle.

[0074] For example, the integer long DRX cycle in the first field includes at least one of the following: 25 milliseconds, 50 milliseconds, and 125 milliseconds; the starting offset corresponding to the integer long DRX cycle is an integer, and the value range of the starting offset is 0 to the integer long DRX cycle minus 1. For example, the starting offset corresponding to the 25 millisecond long DRX cycle is an integer between 0 and 24; the starting offset corresponding to the 50 millisecond long DRX cycle is an integer between 0 and 49; and the starting offset corresponding to the 125 millisecond long DRX cycle is an integer between 0 and 124.

[0075] In the above embodiment, in addition to using the existing integer long DRX cycle, the existing integer long DRX cycle is enhanced by adding some integer long DRX cycles and their corresponding starting offsets to support certain non-integer short DRX cycles. For example, an integer long DRX cycle of 25 milliseconds is added to support a non-integer short DRX cycle of 25 / 2 milliseconds. Similarly, integer long DRX cycles of 50 milliseconds and 125 milliseconds can also be added to support non-integer short DRX cycles such as 50 / 3ms and 125 / 3ms. The starting offset corresponding to each integer long DRX cycle ranges from 0 to [integer long DRX cycle - 1].

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

[0077] In some embodiments, if the non-integer short DRX cycle is configured and the non-integer long DRX cycle is not configured, the integer long DRX cycle (drx-LongCycle) is an integer multiple of the non-integer short DRX cycle. This ensures that the DRX cycle matches the XR service cycle.

[0078] In the above embodiment, the integer long DRX cycle (drx-LongCycle) can be in the above-mentioned first field (for example, the above-mentioned drx-LongCycleStartOffset-r18), or in a traditional field, such as drx-LongCycleStartOffset (referred to as the second field), and this application does not impose any restrictions on this.

[0079] In some embodiments, if the first field is configured, the integer long DRX cycle (drx-LongCycle) in the first field must be an integer multiple of the non-integer short DRX cycle, thereby ensuring that the DRX cycle and the XR service cycle match each other.

[0080] In some embodiments, the first IE further includes a second field, which includes an integer long DRX cycle and its corresponding starting offset. The second field is, for example, a traditional drx-LongCycleStartOffset. For details about the traditional drx-LongCycleStartOffset, please refer to the relevant art and will not be repeated here.

[0081] In the above embodiment, if the first field is configured, the terminal device ignores the configuration of the second field. That is, if the first field is configured, and the integer long DRX cycle in the first field is an integer multiple of the configured non-integer short DRX cycle, the terminal device ignores the traditional integer long DRX cycle configuration. This ensures that the DRX cycle matches the XR service cycle.

[0082] In some embodiments, if a non-integer long DRX cycle is configured, the non-integer long DRX cycle is an integer multiple of the non-integer short DRX cycle, thereby ensuring the matching of the DRX cycle and the XR service cycle.

[0083] According to the above embodiment, the description of the drx-LongCycleStartOffset field in the DRX-Config IE in the RRCReconfiguration message may be modified as follows.

[0084] In the embodiment of the present application, in order to support the mixed configuration (use) of non-integer short DRX cycles and corresponding integer long DRX cycles, corresponding enhancements can also be made to the behavior of non-integer DRX cycles at the MAC layer.

[0085] In some embodiments, when the non-integer long DRX cycle (referred to as drx-NonIntegerLongCycleStartOffset) and / or the non-integer short DRX cycle is configured, the UE variable DRX_SFN_COUNTER is used for DRX operation. This UE variable is a counter that increments by 1 each time the system frame number (SFN) changes to 0.

[0086] In the above embodiment, the purpose of this counter is to solve the problem of misalignment between the DRX cycle and the system frame boundary when the system frame number flips. Since the DRX cycle may not be evenly divisible by the duration of the system frame number flip cycle when it is a non-integer, the DRX cycle may straddle a system frame boundary, causing the next system frame cycle and the system frame boundary to be misaligned, thereby causing an error in the calculation of the DRX wake-up period. According to the above embodiment, this counter is introduced, and the duration of the counter is also taken into account when calculating the DRX wake-up period, which is equivalent to extending the time for the system frame flip, thereby solving the problem of misalignment between the DRX cycle and the system frame boundary when the system frame number flips.

[0087] In the above embodiment, conditions for initializing and configuring the counter may also be defined.

[0088] For example, if the non-integer long DRX cycle and / or the non-integer short DRX cycle is configured, the UE variable DRX_SFN_COUNTER is increased by 1 at the first symbol time of the time slot where the system frame number becomes 0.

[0089] For another example, if DRX is configured or reconfigured, for example, DRX is configured or reconfigured by an RRC message, then the UE variable DRX_SFN_COUNTER is set to 0 at the first symbol time of the timestamp after the configuration or reconfiguration is completed.

[0090] In some embodiments, the above-mentioned first message also configures a short cycle timer, and the value of the short cycle timer is the time of the short DRX cycle that the terminal device needs to follow, for example, called drx-ShortCycleTimer, and the value of the short cycle timer indicates an integer short DRX cycle, or, when a non-integer short DRX cycle is configured, the value of the short cycle timer indicates a multiple of the non-integer short DRX cycle.

[0091] For example, if the value of the short cycle timer is 1, it indicates an integer short DRX cycle duration or a non-integer short DRX cycle duration (if a non-integer short DRX cycle is configured).

[0092] For another example, if the value of the short cycle timer is 2, it represents 2 times the short DRX cycle duration of an integer or 2 times the short DRX cycle duration of a non-integer.

[0093] In the above embodiment, if a non-integer short DRX cycle is configured, the short cycle timer may be configured to indicate a multiple of the non-integer short DRX cycle.

[0094] In the above embodiment, the short cycle timer can be indicated by adding a new field in the above first message. For example, the above first message can also include a fourth field, which is called drx-ShortCycleTimer-r18, and its value range is 1 to 16.

[0095] In the above embodiment, when the short cycle timing corresponding to a certain DRX group times out, the terminal device may use a long DRX cycle for the DRX group.

[0096] 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.

[0097] 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.

[0098] FIG4 is a schematic diagram of a method for determining a DRX cycle according to an embodiment of the present application. This method is a UE-side process corresponding to the previous DRX cycle configuration method. The same contents as the previous embodiment will not be repeated. As shown in FIG4 , the method includes:

[0099] 410: The terminal device receives first information sent by the network device, where the first message configures a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle, where the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle.

[0100] In some embodiments, as described above, if a non-integer short DRX cycle is configured and a non-integer long DRX cycle is not configured, the integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

[0101] In some embodiments, as described above, the first message includes a first IE, the first IE includes a first field, and the first field includes an integer long DRX cycle and its corresponding starting offset.

[0102] In the above embodiment, the value of the integer long DRX cycle may be an integer multiple of some non-integer short DRX cycles.

[0103] In the above embodiment, as mentioned above, the integer long DRX cycle may, for example, include at least one of the following: 25 milliseconds, 50 milliseconds, and 125 milliseconds; the starting offset corresponding to the integer long DRX cycle is an integer, and the value range of the starting offset is 0 to the integer long DRX cycle minus 1.

[0104] For example, the starting offset corresponding to a 25 millisecond long DRX cycle is an integer between 0 and 24; the starting offset corresponding to a 50 millisecond long DRX cycle is an integer between 0 and 49; and the starting offset corresponding to a 125 millisecond long DRX cycle is an integer between 0 and 124.

[0105] In some embodiments, if the first field is configured, the integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

[0106] In some embodiments, the first IE further includes a second field, the second field including an integer long DRX cycle and its corresponding starting offset; if the first field is configured, the terminal device ignores the configuration of the second field.

[0107] In some embodiments, if a non-integer long DRX cycle is configured, the non-integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

[0108] In some embodiments, when a non-integer long DRX cycle and / or a non-integer short DRX cycle is configured, the UE variable DRX_SFN_COUNTER is used for DRX operation.

[0109] In the above embodiment, if a non-integer long DRX cycle and / or a non-integer short DRX cycle is configured, the DRX_SFN_COUNTER is increased by 1 at the first symbol time of the time slot where the system frame number becomes 0.

[0110] In the above embodiment, if DRX is configured or reconfigured, DRX_SFN_COUNTER is set to 0 at the first symbol time of the timestamp after the configuration or reconfiguration is completed.

[0111] According to the method of the embodiment of the present application, the configuration of integer and non-integer DRX long and short cycles can be more flexibly supported, and UE energy saving for more XR services can be supported.

[0112] Embodiments of the second aspect

[0113] 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.

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

[0115] 510: The network device sends a first message to the terminal device, where the first message configures a short DRX cycle and a long DRX cycle corresponding to the short DRX cycle; if the short DRX cycle is a non-integer, the long DRX cycle is also a non-integer.

[0116] It is worth noting that FIG5 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 FIG5 above.

[0117] According to the above embodiment, if the short DRX cycle is a non-integer, the long DRX cycle must also be a non-integer, thereby solving the problem of mismatch between the DRX cycle and the XR service cycle and achieving UE energy saving.

[0118] In some embodiments, if the short DRX cycle is a non-integer, the long DRX cycle is an integer multiple of the short DRX cycle, such as 2 times or 3 times.

[0119] According to the above embodiment, to resolve the issue where some non-integer short DRX cycles do not have corresponding long DRX cycles, a non-integer value of 2 or 3 times the non-integer short DRX cycle can be defined as a non-integer long DRX cycle. In other words, if a value of 2 or 3 times the non-integer short DRX cycle is still a non-integer, it can be included in the value range of the non-integer long DRX cycle.

[0120] In some embodiments, the first message includes a first IE, the first IE includes a third field, and the third field includes a non-integer long DRX cycle and its corresponding starting offset.

[0121] In the above embodiment, the non-integer long DRX cycle may include, for example, at least one of the following: 80 / 3 milliseconds, 75 / 2 milliseconds; the starting offset corresponding to the non-integer long DRX cycle is an integer, and the value of the starting offset ranges from 0 to the value of the non-integer long DRX cycle rounded down minus 1. For example, the starting offset corresponding to the non-integer long DRX cycle of 80 / 3 milliseconds is an integer between 0 and 25; and the starting offset corresponding to the non-integer long DRX cycle of 75 / 2 milliseconds is an integer between 0 and 36.

[0122] In the above embodiment, the first message is, for example, an RRCReconfiguration message, the first IE is, for example, DRX-Config, and the third field is, for example, called drx-NonIntegerLongCycleStartOffset-r18.

[0123] According to the above embodiment, new long DRX cycle values, such as 80 / 3 milliseconds and 75 / 2 milliseconds, are added to the drx-NonIntegerLongCycleStartOffset-r18 field in the drx-Config IE to support short DRX cycles of 40 / 3 ms and 25 / 2 ms, respectively. In addition, the corresponding long DRX cycle start offset value ranges are added to the above field, such as 0 to 25 and 0 to 36, respectively. This solves the problem of mismatch between the DRX cycle and the XR service cycle, and achieves UE energy saving.

[0124] Here is an example of the third field:

[0125] In some embodiments, the above-mentioned first message may also be configured with a short cycle timer. The relevant content about the short cycle timer has been explained in the above embodiment of the first aspect and will not be repeated here.

[0126] 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.

[0127] 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.

[0128] FIG6 is a schematic diagram of a method for determining a DRX cycle according to an embodiment of the present application. This method is a UE-side process corresponding to the previous DRX cycle configuration method. The same contents as the previous embodiment will not be repeated. As shown in FIG6 , the method includes:

[0129] 610: The terminal device receives a first message sent by the network device, where the first message configures a short DRX cycle and a long DRX cycle corresponding to the short DRX cycle; if the short DRX cycle is a non-integer, the long DRX cycle is a non-integer.

[0130] In some embodiments, if the short DRX cycle is a non-integer, the long DRX cycle is an integer multiple of the short DRX cycle.

[0131] In some embodiments, the first message includes a first IE, the first IE includes a third field, and the third field includes a non-integer long DRX cycle and its corresponding starting offset.

[0132] In the above embodiment, the non-integer long DRX cycle includes at least one of the following: 80 / 3 milliseconds, 75 / 2 milliseconds; the starting offset corresponding to the non-integer long DRX cycle is an integer, and the value range of the starting offset is 0 to the value rounded down of the non-integer long DRX cycle minus 1.

[0133] For example, the starting offset corresponding to a non-integer long DRX cycle of 80 / 3 milliseconds is an integer between 0 and 25; the starting offset corresponding to a non-integer long DRX cycle of 75 / 2 milliseconds is an integer between 0 and 36.

[0134] 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.

[0135] According to the method of the embodiment of the present application, it is only necessary to modify the value of the non-integer long DRX cycle to achieve matching between the DRX cycle and the XR data cycle, which has a smaller standardization impact and is simpler to implement.

[0136] Embodiments of the third aspect

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

[0138] FIG7 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.

[0139] As shown in FIG7 , the DRX cycle configuration apparatus 700 includes:

[0140] The sending unit 710 sends a first message to the terminal device, which configures a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle; the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle.

[0141] In some embodiments, if the non-integer short DRX cycle is configured and the non-integer long DRX cycle is not configured, the integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

[0142] In some embodiments, the first message includes a first IE, the first IE includes a first field, and the first field includes the long DRX cycle of the integer and its corresponding starting offset.

[0143] In the above embodiment, the first message is, for example, an RRCReconfiguration message, the first IE is, for example, DRX-Config, and the first field is, for example, drx-LongCycleStartOffset-r18.

[0144] In the above embodiment, the integer long DRX cycle may be an integer multiple of a portion of non-integer short DRX cycles. For example, the integer long DRX cycle includes at least one of the following: 25 milliseconds, 50 milliseconds, and 125 milliseconds. The starting offset corresponding to the integer long DRX cycle is an integer, and the starting offset ranges from 0 to the integer long DRX cycle minus 1.

[0145] For example, the starting offset corresponding to a 25 millisecond long DRX cycle is an integer between 0 and 24; the starting offset corresponding to a 50 millisecond long DRX cycle is an integer between 0 and 49; and the starting offset corresponding to a 125 millisecond long DRX cycle is an integer between 0 and 124.

[0146] In some embodiments, if the first field is configured, the integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

[0147] In some embodiments, the first IE further includes a second field, which includes an integer long DRX cycle and its corresponding starting offset; if the above-mentioned first field is configured, the terminal device ignores the configuration of the second field.

[0148] In the above embodiment, the second field is a traditional integer long DRX cycle field, for example, called drx-LongCycleStartOffset.

[0149] In some embodiments, if a non-integer long DRX cycle is configured, the non-integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

[0150] In some embodiments, when the non-integer long DRX cycle and / or the non-integer short DRX cycle is configured, the UE variable DRX_SFN_COUNTER is used for DRX operation.

[0151] In the above embodiment, if a non-integer long DRX cycle and / or a non-integer short DRX cycle is configured, the DRX_SFN_COUNTER is increased by 1 at the first symbol time of the time slot where the system frame number becomes 0.

[0152] In the above embodiment, if DRX is configured or reconfigured, the DRX_SFN_COUNTER is set to 0 at the first symbol time of the timestamp after the configuration or reconfiguration is completed.

[0153] In some embodiments, the first message further configures a short cycle timer, the value of the short cycle timer indicating an integer short DRX cycle or a multiple of a non-integer short DRX cycle when a non-integer short DRX cycle is configured.

[0154] In an example, if the value of the short cycle timer is 1, it indicates the integer short DRX cycle duration or the non-integer short DRX cycle duration.

[0155] In another example, if the value of the short cycle timer is 2, it represents 2 times the integer short DRX cycle duration or 2 times the non-integer short DRX cycle duration.

[0156] An embodiment of the present application also provides a DRX determination device.

[0157] Figure 8 is a schematic diagram of a DRX determination device according to an embodiment of the present application. This device 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 device is the same as that of the method shown in Figure 4 of the embodiment of the first aspect, and corresponds to the device shown in Figure 7 of the aforementioned embodiment, its specific implementation can refer to the method shown in Figure 4 of the embodiment of the first aspect and the implementation of the device shown in Figure 7 of the aforementioned embodiment, and the details of the same content will not be repeated here.

[0158] As shown in FIG8 , the DRX determination device 800 includes:

[0159] The receiving unit 810 receives first information sent by the network device, where the first message configures a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle, where the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle.

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

[0161] 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 illustrated in FIG5 of the embodiment of the second aspect, its specific implementation may refer to the implementation of the method illustrated in FIG5 of the embodiment of the second aspect, and the same details will not be repeated here.

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

[0163] The sending unit 910 sends a first message to the terminal device, where the first message configures a short DRX cycle and a long DRX cycle corresponding to the short DRX cycle; if the short DRX cycle is a non-integer, the long DRX cycle is also a non-integer.

[0164] In some embodiments, if the short DRX cycle is a non-integer, the long DRX cycle is an integer multiple of the short DRX cycle.

[0165] In some embodiments, the first message includes a first IE, the first IE includes a third field, and the third field includes a non-integer long DRX cycle and its corresponding starting offset.

[0166] In the above embodiment, the first message is, for example, an RRCReconfiguration message, the first IE is, for example, DRX-Config, and the third field is, for example, drx-NonIntegerLongCycleStartOffset-r18.

[0167] In the above embodiment, the non-integer long DRX cycle may include, for example, at least one of the following: 80 / 3 milliseconds, 75 / 2 milliseconds. The starting offset corresponding to the non-integer long DRX cycle is an integer, and the value of the starting offset ranges from 0 to the value of the non-integer long DRX cycle rounded down minus 1. For example, the starting offset corresponding to the non-integer long DRX cycle of 80 / 3 milliseconds is an integer between 0 and 25; and the starting offset corresponding to the non-integer long DRX cycle of 75 / 2 milliseconds is an integer between 0 and 36.

[0168] In some embodiments, the first message further configures a short cycle timer, the value of the short cycle timer indicating an integer short DRX cycle or a multiple of a non-integer short DRX cycle when a non-integer short DRX cycle is configured.

[0169] In an example, if the value of the short cycle timer is 1, it indicates the integer short DRX cycle duration or the non-integer short DRX cycle duration.

[0170] In another example, if the value of the short cycle timer is 2, it represents 2 times the integer short DRX cycle duration or 2 times the non-integer short DRX cycle duration.

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

[0172] Figure 10 is a schematic diagram of a device for determining a DRX configuration 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 of this device is the same as that of the method shown in Figure 6 of the embodiment of the second aspect, and corresponds to the device shown in Figure 9 of the above embodiment, its specific implementation can refer to the implementation of the method shown in Figure 6 of the embodiment of the second aspect and the implementation of the device shown in Figure 9 of the above embodiment, and the same content will not be repeated here.

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

[0174] The receiving unit 1010 receives a first message sent by a network device, where the first message configures a short DRX cycle and a long DRX cycle corresponding to the short DRX cycle; if the short DRX cycle is a non-integer, the long DRX cycle is a non-integer.

[0175] 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 700, 800, 900, and 1000 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.

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

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

[0178] Embodiments of the fourth aspect

[0179] An embodiment of the present application provides a communication system, including a terminal device and a network device, wherein the network device is configured to execute the method shown in FIG3 of the embodiment of the first aspect or the method shown in FIG5 of the embodiment of the second aspect. The behavior of the network device has been described in detail in the embodiments of the first aspect and the second aspect, and the contents thereof are incorporated herein and will not be repeated here. Accordingly, the terminal device is configured to execute the method shown in FIG4 of the embodiment of the first aspect or the method shown in FIG5 of the embodiment of the second aspect. The behavior of the terminal device has been described in detail in the embodiments of the first aspect and the second aspect, and the contents thereof are incorporated herein and will not be repeated here.

[0180] 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 5 of the embodiment of the second aspect.

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

[0182] For example, the processor 1110 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. 5 in the embodiment of the second aspect.

[0183] In addition, as shown in FIG11 , network device 1100 may further include: a transceiver 1130 and an antenna 1140, 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 1100 does not necessarily include all the components shown in FIG3 ; in addition, network device 1100 may also include components not shown in FIG11 , which may be referred to in the prior art.

[0184] 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 4 of the embodiment of the first aspect or the method described in Figure 6 of the embodiment of the second aspect.

[0185] Figure 12 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 12, terminal device 1200 may include a processor 1210 and a memory 1220. Memory 1220 stores data and programs and is coupled to processor 1210. 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.

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

[0187] As shown in Figure 12 , the terminal device 1200 may further include: a communication module 1230, an input unit 1240, a display 1250, and a power supply 1260. 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 1200 does not necessarily include all of the components shown in Figure 12 , and these components are not essential. Furthermore, the terminal device 1200 may also include components not shown in Figure 12 , for which reference may be made to the prior art.

[0188] 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 a computer to execute the method described in FIG. 3 of the embodiment of the first aspect or the method described in FIG. 5 of the embodiment of the second aspect in the network device.

[0189] 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 FIG. 3 of the embodiment of the first aspect or the method described in FIG. 5 of the embodiment of the second aspect in a network device.

[0190] 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 4 of the embodiment of the first aspect or the method described in Figure 6 of the embodiment of the second aspect in the terminal device.

[0191] 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 FIG. 4 of the embodiment of the first aspect or the method described in FIG. 6 of the embodiment of the second aspect in a terminal device.

[0192] 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.

[0193] 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).

[0194] 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.

[0195] 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.

[0196] 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.

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

[0198] 1. A network device comprising 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 following method:

[0199] A first message is sent to a terminal device, wherein the first message configures a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle; the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle.

[0200] 2. A network device comprising 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 following method:

[0201] A first message is sent to a terminal device, where the first message configures a short DRX cycle and a long DRX cycle corresponding to the short DRX cycle; if the short DRX cycle is a non-integer, the long DRX cycle is a non-integer.

[0202] 3. A communication system comprising a network device and a terminal device, wherein the network device is configured to send a first message to the terminal device, and the terminal device is configured to receive the first message, wherein:

[0203] The first message configures a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle; the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle; or,

[0204] The first message configures a short DRX cycle and a long DRX cycle corresponding to the short DRX cycle; if the short DRX cycle is a non-integer, the long DRX cycle is a non-integer.

Claims

1. A configuration device for a discontinuous reception (DRX) cycle, configured in a network device, wherein, The device includes: A sending unit, which sends a first message to a terminal device, where the first message configures a non-integer short DRX cycle and a long DRX cycle corresponding to the non-integer short DRX cycle; the long DRX cycle is an integer long DRX cycle or a non-integer long DRX cycle.

2. The device according to claim 1, wherein If the non-integer short DRX cycle is configured and the non-integer long DRX cycle is not configured, the integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

3. The device according to claim 1, wherein The first message includes a first information element (IE), the first IE includes a first field, and the first field includes the integer long DRX cycle and its corresponding starting offset.

4. The device according to claim 3, wherein The value of the integer long DRX cycle is an integer multiple of a part of the non-integer short DRX cycles.

5. The device according to claim 4, wherein The integer long DRX cycle includes at least one of the following: 25 milliseconds, 50 milliseconds, 125 milliseconds; The starting offset corresponding to the integer long DRX cycle is an integer, and the value range of the starting offset is from 0 to the integer long DRX cycle minus 1.

6. The device according to claim 5, wherein The starting offset corresponding to the 25-millisecond long DRX cycle is an integer between 0 and 24; The starting offset corresponding to the 50-millisecond long DRX cycle is an integer between 0 and 49; The starting offset corresponding to the 125-millisecond long DRX cycle is an integer between 0 and 124.

7. The device according to claim 3, wherein If the first field is configured, the integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

8. The device according to claim 3, wherein The first IE further includes a second field, and the second field includes an integer long DRX cycle and its corresponding starting offset; if the first field is configured, the terminal device ignores the configuration of the second field.

9. The device according to claim 1, wherein If the non-integer long DRX cycle is configured, the non-integer long DRX cycle is an integer multiple of the non-integer short DRX cycle.

10. The device according to claim 1, wherein When the non-integer long DRX cycle and / or the non-integer short DRX cycle are configured, the UE variable DRX_SFN_COUNTER is used for DRX operations.

11. The device according to claim 10, wherein If the non-integer long DRX cycle and / or the non-integer short DRX cycle are configured, at the first symbol time of the time slot when the system frame number becomes 0, the DRX_SFN_COUNTER is incremented by 1.

12. The device according to claim 10, wherein If DRX is configured or reconfigured, at the first symbol time of the time slot after the completion of the configuration or reconfiguration, the DRX_SFN_COUNTER is set to 0.

13. A DRX cycle configuration device, wherein, The apparatus includes: The network device sends a first message to the terminal device, and the first message configures a short DRX cycle and a long DRX cycle corresponding to the short DRX cycle; If the short DRX cycle is non-integer, the long DRX cycle is non-integer.

14. The apparatus according to claim 13, wherein, If the short DRX cycle is non-integer, the long DRX cycle is an integer multiple of the short DRX cycle.

15. The apparatus according to claim 13, wherein, The first message includes a first IE, the first IE includes a third field, and the third field includes a non-integer long DRX cycle and its corresponding start offset.

16. The apparatus according to claim 15, wherein, The non-integer long DRX cycle includes at least one of the following: 80 / 3 milliseconds, 75 / 2 milliseconds; The start offset corresponding to the non-integer long DRX cycle is an integer, and the value range of the start offset is from 0 to the value obtained by rounding down the non-integer long DRX cycle minus 1.

17. The apparatus according to claim 16, wherein, The start offset corresponding to the non-integer long DRX cycle of 80 / 3 milliseconds is an integer between 0 and 25; The start offset corresponding to the non-integer long DRX cycle of 75 / 2 milliseconds is an integer between 0 and 36.

18. The apparatus according to claim 13, wherein, The first message also configures a short cycle timer, and the value of the short cycle timer indicates an integer short DRX cycle or a multiple of the non-integer short DRX cycle when a non-integer short DRX cycle is configured.

19. The apparatus according to claim 18, wherein, If the value of the short cycle timer is 1, it represents the duration of the integer short DRX cycle or the duration of the non-integer short DRX cycle; If the value of the short cycle timer is 2, it represents 2 times the duration of the integer short DRX cycle or 2 times the duration of the non-integer short DRX cycle.

20. The apparatus according to claim 15, wherein, The first message is an RRCReconfiguration message, and the first IE is a DRX-Config.

Images