WO2025065798A1 - 非连续接收周期的配置方法和装置 - Google Patents

非连续接收周期的配置方法和装置 Download PDF

Info

Publication number
WO2025065798A1
WO2025065798A1 PCT/CN2023/129183 CN2023129183W WO2025065798A1 WO 2025065798 A1 WO2025065798 A1 WO 2025065798A1 CN 2023129183 W CN2023129183 W CN 2023129183W WO 2025065798 A1 WO2025065798 A1 WO 2025065798A1
Authority
WO
WIPO (PCT)
Prior art keywords
integer
drx cycle
terminal device
drx
configuration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/129183
Other languages
English (en)
French (fr)
Inventor
易粟
李国荣
韩超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to CN202380102331.3A priority Critical patent/CN121909676A/zh
Publication of WO2025065798A1 publication Critical patent/WO2025065798A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the field of communications.
  • XR Support extended reality
  • 3GPP 3rd Generation Partnership Project
  • XR services refer to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices. Its application areas include but are not limited to entertainment, medical care, education, etc.
  • XR services can include virtual reality (VR) services, augmented reality (AR) services, mixed reality (MR) services and other representative forms and mixed and cross-cutting fields.
  • VR virtual reality
  • AR augmented reality
  • MR mixed reality
  • Virtual reality is a rendered version of a published visual and audio scene, where the rendering is intended to simulate the visual and auditory sensory stimulation of the real world as naturally as possible when the observer 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 with the aim of providing an illusion that these elements are part of the real scene.
  • a PDU Set consists of one or more PDUs (Protocol Data Units) 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.
  • PDUs Protocol Data Units
  • 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.
  • DRX discontinuous reception
  • the terminal device does not need to continuously monitor the physical downlink.
  • the data transmission control channel (PDCCH) is used to achieve energy saving.
  • the DRX cycle can be matched with the data arrival cycle, and the wake-up period and data arrival time can be roughly aligned.
  • the UE can monitor the PDCCH sent by the base station, obtain scheduling information from it, and schedule the data in a timely manner.
  • the current DRX cycle is defined as different integer values in milliseconds. If the data arrival cycle is a non-integer, 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 delays.
  • an embodiment of the present application provides a method and apparatus for configuring a discontinuous reception (DRX) cycle.
  • DRX discontinuous reception
  • a DRX cycle configuration device which is applied to a network device, and the device includes:
  • 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, 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.
  • a DRX cycle configuration device which is applied to a network device, and the device includes:
  • a sending unit which sends a second configuration message to a terminal device, wherein the second configuration message configures disabling of CG retransmission monitoring for configuration authorization;
  • the second configuration message contains a second information unit, wherein the second information unit includes a sixth field, and the sixth field indicates disabling of CG retransmission monitoring for configuration authorization.
  • 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.
  • FIG1 is a schematic diagram of a DRX cycle
  • FIG2 is a schematic diagram showing a mismatch between the DRX cycle and the XR traffic cycle
  • FIG3 is a schematic diagram of a method for configuring a DRX cycle according to an embodiment of the present application
  • FIG4 is a schematic diagram of an example of a DRX configuration
  • FIG5 is a schematic diagram showing that the continuous monitoring time of the long DRX cycle and the short DRX cycle are not aligned
  • FIG6 is a schematic diagram of a method for determining a DRX cycle according to an embodiment of the present application.
  • FIG7 is another schematic diagram of a DRX configuration method according to an embodiment of the present application.
  • FIG8 is another schematic diagram of a method for implementing DRX configuration according to an embodiment of the present application.
  • FIG9 is a schematic diagram of a DRX cycle configuration device according to an embodiment of the present application.
  • FIG10 is another schematic diagram of a DRX configuration device according to an embodiment of the present application.
  • FIG11 is a schematic diagram of a device for determining a DRX cycle according to an embodiment of the present application.
  • FIG12 is another schematic diagram of an implementation device of a DRX configuration according to an embodiment of the present application.
  • FIG13 is a schematic diagram of a network device according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of title, but do not indicate the spatial arrangement or temporal order of these elements, etc., 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.
  • 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), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.
  • LTE Long Term Evolution
  • LTE-A enhanced Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • communication between devices in the communication system may be carried out according to communication protocols of any stage, such as 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 communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G and future 5G
  • NR New Radio
  • the term "network device” refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • the network device may include, but is 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.
  • Base stations may include but are not limited to: NodeB (NB), evolved NodeB (eNodeB or eNB) And 5G base station (gNB), etc., in addition to remote radio head (RRH, Remote Radio Head), remote radio unit (RRU, Remote Radio Unit), relay or low-power node (such as femto, pico, etc.).
  • NB NodeB
  • eNodeB or eNB evolved NodeB
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay or low-power node such as femto, pico, etc.
  • base station can include some or all of their functions, and each base station can provide communication coverage for a specific geographical area.
  • the term “cell” can refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” 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).
  • the terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a user, a subscriber station (SS), an access terminal (AT), a station, and the like.
  • Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDA), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, and IAB-MT, etc.
  • PDA personal digital assistants
  • wireless modems wireless communication devices
  • handheld devices machine-type communication devices
  • machine-type communication devices laptop computers
  • cordless phones smart phones
  • smart watches smart watches
  • digital cameras digital cameras
  • IAB-MT IAB-MT
  • the terminal device can also be a machine or device for monitoring or measuring, such as 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.
  • MTC machine type communication
  • D2D device to device
  • M2M machine to machine
  • HDRLL High Data Rate Low Latency
  • AR/VR/XR AR/VR/XR services
  • tactile/multimodal communication services The goals include:
  • Enhanced features to support multi-mode services including:
  • DRX 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.
  • DRX in the connected state Connected DRX, C-DRX
  • DRX refers to the DRX used when the UE is in the connected state, that is, C-DRX.
  • the UE When the UE is configured with DRX, the UE does not need to continuously monitor the PDCCH (Physical Downlink Control Channel), thereby achieving energy saving.
  • the UE's MAC entity can be configured with the DRX function by RRC signaling to control the UE's PDCCH monitoring activities for certain RNTIs (Radio Network Temporary Identifiers) of the MAC entity.
  • RNTIs Radio Network Temporary Identifiers
  • the basic mechanism of DRX is to configure a DRX cycle for the UE in RRC CONNECTED state.
  • the DRX cycle consists of On Duration (wake-up period) and Opportunity for DRX (sleep period).
  • On Duration the UE monitors and receives PDCCH; during the "Opportunity for DRX" time During the DRX period, the UE does not receive PDCCH to reduce power consumption.
  • the DRX cycle defines a periodic repetition of wake-up periods followed by possible inactivity periods, as shown in Figure 1.
  • NR supports two types of DRX cycles: long DRX cycle and short DRX cycle, depending on the length of time the UE monitors a specific scheduling channel after waking up. If it is predicted that UE data arrives frequently or the service is sensitive to latency, the network side can configure the UE to use a short DRX cycle; if it is predicted that UE data is sparse and insensitive to latency, the network side can configure the UE to use only a long DRX cycle. In order to facilitate the UE to switch between long and short DRX cycles, the long DRX cycle is required to be an integer multiple of the short DRX cycle, so that the continuous monitoring time (onDuration) of the two can be aligned.
  • XR traffic period the arrival period of XR service traffic
  • XR traffic period or data transmission period may be a non-integer (rational number).
  • XR services with frame rates of 15, 30, 45, 60, 72, 90 and 120 frames per second correspond to non-integer (respectively 66.66, 33.33, 22.22, 16.66, 13.88, 11.11 and 8.33 milliseconds) data periods.
  • the current DRX cycle is defined as different integer values in milliseconds.
  • 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.
  • 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 a non-integer, it will cause the data arrival cycle and the DRX cycle to 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 delays.
  • FIG2 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 period is set to 16 milliseconds, after several DRX periods, the DRX wake-up period and the data arrival time (66.67 ms in FIG2 ) will not be aligned.
  • FIG3 is a schematic diagram of a method for configuring a DRX cycle in an embodiment of the present application. As shown in FIG3, the method includes:
  • 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 message 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.
  • FIG. 1 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • 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 the above FIG. 3.
  • the problem that the DRX cycle does not support non-integer data arrival cycles is solved, and UE energy saving is achieved.
  • the first configuration message is an RRCReconfiguration message
  • the first information unit is a DRX-Config IE.
  • 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 cycles.
  • the DRX-Config IE in the RRCReconfiguration message is enhanced to add support for the configuration of the DRX cycle being a rational number, but the present application is not limited thereto.
  • Other information units 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.
  • the following takes the enhancement of the DRX-Config IE in the RRCReconfiguration message as an example.
  • non-integer long DRX cycles and start offsets are uniformly defined.
  • the first information unit includes a first field, which includes a combination of a non-integer (fractional) long DRX cycle corresponding to a frame rate and its corresponding starting offset, for example, which may be called drx-NonIntegerLongCycleStartOffset.
  • a non-integer (fractional) long DRX cycle corresponding to a frame rate and its corresponding starting offset, for example, which may be called drx-NonIntegerLongCycleStartOffset.
  • the present application is not limited to this, and the first field may also have other names.
  • the first field is, for example, 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.
  • the first field is a CHOICE structure, indicating that a selection is made from predefined non-integer long DRX cycles corresponding to a certain frame rate and their corresponding starting offsets in milliseconds during configuration.
  • 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.
  • 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.
  • the first field drx-NonIntegerLongCycleStartOffset contains the fractional value drx-NonIntegerLongCycle (non-integer long DRX cycle) in milliseconds and drx-StartOffset (starting offset) in milliseconds.
  • "ms200/3" is just a method of using two integers (numerator and denominator, usually coprime integers) to represent a fraction.
  • 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.
  • the terminal device may ignore the configuration of drx-LongCycleStartOffset (that is, the integer long DRX cycle and the corresponding start offset), thereby avoiding ambiguity in terminal behavior.
  • drx-LongCycleStartOffset that is, the integer long DRX cycle and the corresponding start offset
  • 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.
  • a new second field may be defined in the DRX-Config IE, where the second field is a non-integer (fraction) short DRX cycle corresponding to a certain frame rate.
  • the second field may be called, for example, drx-NonIntegerShortCycle, but the present application is not limited thereto, and the second field may also have other names.
  • 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.
  • the value "ms200/3" in the second field corresponds to 200/3 milliseconds, and so on.
  • the terminal device may ignore the configuration of drx-ShortCycle (that is, the integer short DRX cycle), thereby avoiding ambiguity in terminal behavior.
  • the non-integer long DRX cycle value in the first field must be an integer multiple of the value of the second field.
  • the non-integer long DRX cycle in the first field can be configured as ms200/3. In this way, the onDuration of the two can be aligned.
  • non-integer long DRX cycles and start offsets are defined separately.
  • the first information unit 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
  • the fourth field includes a starting offset for the non-integer long DRX cycle.
  • 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, wherein 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.
  • drx-NonIntegerLongCycle two integers (a first integer and a second integer), such as N1 and N2
  • N1 represents the numerator in the fractional expression N1/N2 of the above non-integer long DRX cycle
  • N2 represents the denominator in the fractional expression N1/N2 of the above non-integer long DRX cycle.
  • N1 and N2 can be integers, and the value ranges are the ranges of the numerator and denominator in the fractional expression of the supported non-integer long DRX cycle. In this way, N1 and N2 can take any value within their respective ranges, which has strong scalability and can support more services with different data rates.
  • N1 and N2 are both integer types:
  • N1 and N2 may also be enumerated types, and the value ranges include fixed values of the numerator and denominator in the fractional expression of the supported non-integer long DRX cycle, and may also include reserved spare bits. In this way, the signaling overhead is smaller, and a certain scalability is maintained, so that more services with different data rates can be supported.
  • N1 and N2 are enumeration types:
  • the third field may also include only one integer, namely, a second integer, such as N2, to represent a non-integer long DRX cycle.
  • 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.
  • the fourth field defines the starting offset for a non-integer long DRX cycle, such as drx-StartOffsetForNonIntCycle.
  • the fourth field may be an integer type, and the value range may be 0 to Nmax.
  • Nmax is the maximum supported non-integer long DRX cycle rounded down, such as 66 milliseconds.
  • the fourth field when the third field is configured, the fourth field must be configured. Thus, the integrity of the configuration of the non-integer long DRX cycle can be guaranteed.
  • 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.
  • drx-LongCycleStartOffset ie, the integer long DRX cycle and its corresponding start offset
  • 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.
  • a new fifth field may be defined in the DRX-Config IE, and the fifth field defines a non-integer (fraction) short DRX cycle corresponding to a certain frame rate.
  • the fifth field may be called drx-NonIntegerShortCycle, represented by two integers, and the field design is the same as the third field, and may also be represented by the above two examples.
  • 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.
  • the third integer and the fourth integer are respectively of integer type, and the value range of the third integer is the range of variation of 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 variation of the denominator in the fractional expression of the supported non-integer short DRX cycle.
  • the third integer and the fourth integer are respectively of enumeration type; 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.
  • the terminal device uses the quotient of 1000 milliseconds and the fourth integer as a fraction to represent the non-integer short DRX cycle.
  • 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.
  • the value of the third field must be an integer multiple of the value of the fifth field.
  • the terminal device can ignore the configuration of drx-ShortCycle (ie, the integer short DRX cycle), thereby avoiding ambiguity in terminal behavior.
  • the calculation formula for 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 the non-integer DRX cycle, it is necessary to calculate by a formula.
  • a counter (first counter) can be added, such as DRX_SFN_COUNTER.
  • the 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.
  • 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.
  • 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.
  • DRX_SFN_COUNTER system frame number (SFN) and subframe number satisfy the following formula:
  • the terminal device starts a wake-up timer (drx-onDurationTimer) for the above DRX group after the time slot offset (drx-SlotOffset) length after the start of the subframe corresponding to the above subframe number.
  • DRX_SFN_COUNTER current first counter
  • SFN system frame number
  • the terminal device without configuring the downlink control information (DCP, DCI with CRC scrambled by PS_RNTI) monitoring with cyclic redundancy check scrambled by energy-saving radio network temporary identification for the activated downlink bandwidth part (BWP, BandWidth Part), starts the subframe corresponding to the above subframe number for the above DRX group.
  • the wake-up timer is started after the time slot offset (drx-SlotOffset) from the start.
  • the specific order refers to the order from left to right in the formula during calculation.
  • a DRX group refers to a group of service cells with the same DRX activation time configured by RRC.
  • 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 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.
  • the meanings of the above parameters have been explained above, and their contents are incorporated here and will not be repeated here.
  • the first counter needs to be synchronized on the network side and the terminal side, that is, to keep the same value.
  • the terminal device can initialize the counter to 0 when receiving the RRC configuration of the non-integer DRX cycle (such as the RRC configuration of the non-integer long DRX cycle, that is, the above-mentioned first configuration message), and add 1 to the first character time of the time slot when the SFN changes to 0.
  • 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).
  • DRX_SFN_COUNTER 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).
  • a terminal device when a terminal device receives an RRC configuration regarding a non-integer DRX cycle from the network, if the time reference SFN value is 0, it means that the SFN when the network sends the configuration 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.
  • the network side 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 a SFN rollover has occurred, so the terminal device can set DRX_SFN_COUNTER to 1.
  • the terminal device initializes the above DRX_SFN_COUNTER according to the time reference SFN carried by the RRC configuration of the received non-integer DRX cycle, which can ensure the network side and the UE side.
  • the non-integer DRX cycle may be a non-integer long DRX cycle or a non-integer short DRX cycle.
  • the time reference SFN may be omitted in the above related formulas of the non-integer DRX cycle.
  • the MAC entity of the terminal device determines the time to start the wake-up period of the non-integer DRX cycle by the following method:
  • a short DRX cycle is used for a certain 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:
  • the terminal device starts a wake-up timer (drx-onDurationTimer) for the above-mentioned DRX group after the drx-SlotOffset (time slot offset) duration after the start of the subframe corresponding to the above-mentioned subframe number.
  • drx-onDurationTimer a wake-up timer for the above-mentioned DRX group after the drx-SlotOffset (time slot offset) duration after the start of the subframe corresponding to the above-mentioned subframe number.
  • 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, subframe number Satisfies the following formula:
  • the terminal device If the terminal device is not configured with 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.
  • DCP DCI with CRC scrambled by PS_RNTI
  • the problem that the DRX cycle does not support non-integer data arrival cycles is further solved.
  • 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.
  • FIG4 is a schematic diagram of an example of DRX configuration.
  • 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.
  • the starting offset is configured to 16ms, there may be a problem that a certain DRX period has no wake-up period, such as the third period in FIG4. In this way, the terminal device will not be able to monitor the downlink control information, and thus cannot send and receive data, resulting in transmission delays.
  • the embodiments of the present application further provide solutions.
  • the maximum value of the start offset is configured as floor(non-integer long DRX cycle)-1.
  • the first information unit includes the first field
  • the first field is a CHOICE structure, and includes a non-integer long DRX cycle and a starting offset corresponding to the frame rate
  • the maximum value of the starting offset is no longer a value obtained by rounding down the non-integer long DRX cycle, but a value -1 obtained by rounding down the non-integer long DRX cycle, as follows:
  • the method according to the above embodiment solves the problem that the DRX cycle has no wake-up period.
  • 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 offset is configured to be 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. Thereby, the problem that the terminal device may start the wake-up period in advance due to the aforementioned configuration, thereby missing the services that arrive later, is avoided.
  • the terminal device 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.
  • the maximum value of the starting offset is still configured as floor (non-integer long DRX cycle), and enhancement is performed on the UE side.
  • 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.
  • the inventor further discovered that if the short DRX cycle is configured and is a non-integer, and the long DRX cycle is also a 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 be aligned.
  • the long DRX cycle is configured as 50/3ms
  • the short DRX cycle is configured as 25/3ms
  • the starting offset is configured as 15ms.
  • the situation shown in FIG. 5 may occur, that is, at moments 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. Since this situation does not conform to the traditional protocol standard, this may cause unknown operations of some terminal devices and increase the complexity of device development.
  • the embodiments of the present application further provide solutions.
  • a short DRX cycle when a non-integer long DRX cycle is configured, a short DRX cycle is not configured. That is, in view of the above problem, a non-integer short DRX cycle is not defined. That is, when supporting non-integer data cycle XR services, only the long DRX cycle can be configured as a non-integer. When a non-integer long DRX cycle is configured, a short DRX cycle is not configured. This method is simple to implement and reduces design complexity.
  • the long DRX cycle when a non-integer short DRX cycle is configured, the long DRX cycle is an integer. That is, for the above problem, when a non-integer short DRX cycle is configured, the long DRX cycle must be an integer, that is, the (existing) drx-LongCycleStartOffset must be used. This method retains the short DRX cycle, improves the flexibility of UE energy saving, and can better support data bursts.
  • the uplink HARQ (hybrid automatic repeat request) RTT (round-trip time) timer may not be started for the uplink scheduled transmission of the configured grant (CG), thereby not starting retransmission, which is especially important for short-cycle, delay-sensitive XR services.
  • the network device may also send a second configuration information to the terminal device, wherein the second configuration information configures the disabling of CG retransmission monitoring for configuration authorization.
  • the second configuration information may include a second information unit, wherein the second information unit includes a sixth field, and the sixth field indicates the disabling of CG retransmission monitoring for configuration authorization.
  • the second configuration message may be, for example, an RRCReconfiguration message
  • the second information unit may be, for example, a ConfiguredGrantConfig IE
  • the sixth field may be, for example, called disableCG-RetransmissionMonitoring, but the present application is not limited thereto.
  • a configuration may be added to each configuration grant to disable CG retransmission monitoring, that is, to disable uplink configuration grant transmission. Stop starting the drx-HARQ-RTT-TimerUL timer. This solves the problem that CG does not support free uplink retransmission and enhances UE energy saving for delay-sensitive services such as XR services.
  • 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 a period
  • the configuration of the sixth field applies to all configuration uplink grants in the configuration grant, that is, all PUSCH transmission occasions (occasion).
  • the drx-HARQ-RTT-TimerUL timer is prohibited from being started for all configuration uplink grants in the CG.
  • the serving cell of the terminal device is not configured with an uplink HARQ mode (uplinkHARQ-Mode)
  • uplinkHARQ-Mode uplink HARQ-Mode
  • 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;
  • 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.
  • 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 is used alone.
  • the present application is not limited to this.
  • the embodiment of the present application also provides a method for determining a DRX cycle, which is described from the side 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.
  • FIG. 6 is a schematic diagram of a method for determining a DRX cycle according to an embodiment of the present application. As shown in FIG. 6 , the method includes:
  • 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.
  • the terminal device ignores the configuration of the integer long DRX cycle and its corresponding starting offset.
  • 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.
  • the terminal device ignores the configuration of the integer long DRX cycle and its corresponding starting offset.
  • the method may further include:
  • 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.
  • the terminal device can start the wake-up timer.
  • the problem that the DRX cycle does not support non-integer data reaching the cycle is solved, and uplink retransmission-free transmission of multiple PUSCH configuration authorizations is supported, thereby achieving UE energy saving.
  • 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 described again.
  • FIG. 7 is a schematic diagram of a DRX configuration method according to an embodiment of the present application. Referring to FIG. 7 , the method includes:
  • the network device sends a second configuration message to the terminal device, wherein the second configuration message configures disabling of CG retransmission monitoring for configuration authorization;
  • the second configuration message includes a second information unit, wherein the second information unit includes a sixth field, and the sixth field indicates disabling of CG retransmission monitoring for configuration authorization.
  • FIG. 7 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • 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 the above FIG. 7.
  • 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 the uplink configuration authorization transmission.
  • the second configuration information is an RRCReconfiguration message; the second information unit is a ConfiguredGrantConfig IE.
  • the present application is not limited thereto.
  • all configured uplink grants in the above-mentioned configured grants are prohibited from starting the drx-HARQ-RTT-TimerUL timer.
  • the configuration grant is a configuration grant including multi-PUSCH (Physical Uplink Shared CHannel), that is, the CG configuration includes multiple consecutive configured uplink grants (configured uplink grant) within one cycle, and the configuration of the sixth field is applicable to all configured uplink grants in the configuration grant, that is, all PUSCH transmission occasions.
  • multi-PUSCH Physical Uplink Shared CHannel
  • the configuration of the sixth field is applicable to all configured uplink grants in the configuration grant, that is, all PUSCH transmission occasions.
  • the terminal device serving cell 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:
  • the drx-HARQ-RT-TimerUL timer is started for the corresponding HARQ process in the first symbol after the last transmission of the corresponding PUSCH transmission;
  • 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.
  • the embodiment of the present application also provides a method for implementing DRX configuration, which is described from the side of the terminal device. It should be noted that this method is the processing on the UE side corresponding to the DRX configuration method of the above embodiment, and the same contents as the above embodiment will not be repeated.
  • 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:
  • 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.
  • 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:
  • the terminal device 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;
  • 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.
  • the problem of not supporting free uplink retransmission 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.
  • An embodiment of the present application provides a DRX cycle configuration device.
  • FIG9 is a schematic diagram of a DRX cycle configuration device according to an embodiment of the present application, and the device may be, for example, a network device, or may be one or more components or assemblies configured in the network device. Since the principle of solving the problem by the device is the same as 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 contents will not be repeated.
  • the DRX cycle configuration device 900 includes:
  • 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, 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.
  • the first configuration message is a RRCReconfiguration message.
  • the first information unit is the DRX-Config IE.
  • the first information unit includes a first field including a combination of a non-integer long DRX cycle and a start offset corresponding to a frame rate.
  • the first field may be a CHOICE structure
  • 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.
  • 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 the value rounded down to the non-integer long DRX cycle.
  • 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 respectively.
  • the terminal device may ignore the configuration of the integer long DRX cycle and its corresponding starting offset.
  • 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.
  • the second field may be of enumeration type.
  • the non-integer short DRX cycle may be expressed by a fraction in milliseconds.
  • 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.
  • the terminal device can ignore the configuration of the integer short DRX cycle.
  • 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
  • the fourth field includes a starting offset for the non-integer long DRX cycle.
  • 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.
  • 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.
  • the third field may only include a 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.
  • the fourth field may be of integer type, and the value range is 0 to a value rounded down to the maximum non-integer long DRX cycle supported.
  • the fourth field when the third field is configured, the fourth field must be configured.
  • the terminal device may ignore the configuration of the integer long DRX cycle and its corresponding starting offset.
  • the first information unit may further include a fifth field, and the fifth field includes a non-integer short DRX cycle corresponding to the frame rate.
  • the fifth field may include a third integer and a fourth integer; the third integer is the non-integer
  • the fourth integer is the numerator in the fractional expression of the short DRX cycle of the non-integer, and the fourth integer is the denominator in the fractional expression of the short DRX cycle of the non-integer.
  • the third integer and the fourth integer may be enumerated types respectively; 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.
  • the fifth field may also include only 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.
  • 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.
  • the terminal device determines a time to start a wake-up period of said non-integer DRX cycle.
  • 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:
  • the terminal device then starts a wake-up timer for the DRX group after a time slot offset length after the start of the subframe corresponding to the subframe number.
  • the terminal device starts the wake-up timer for the DRX group after the time slot offset length after the start of the subframe corresponding to the subframe number.
  • DCP downlink control information
  • each of 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.
  • the terminal device may also initialize the first counter, for example, initialize the first counter to 0 when receiving the first configuration message; and add 1 to the first character time of the time slot when the SFN changes to 0.
  • the terminal device may initialize the first counter according to the time reference SFN included in the received first configuration message.
  • the terminal device initializes the first counter to 0 when receiving the first configuration message.
  • 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.
  • the synchronization of the first counter between the network side and the terminal side can be achieved.
  • the time reference SFN in the above formula can be omitted.
  • 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 certain DRX group, and a non-integer short DRX cycle is configured, and the current first counter, SFN, and subframe number satisfy the following formula:
  • 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.
  • 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:
  • the terminal device 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.
  • the maximum value of the above-mentioned starting offset is configured to be a value obtained by rounding down a non-integer DRX cycle minus 1.
  • the duration of the wake-up period of the non-integer DRX cycle may be longer than the duration of the wake-up period of the DRX cycle corresponding to other values of the maximum value of the start offset.
  • the terminal device 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.
  • the maximum value of the above-mentioned starting offset is configured as a value obtained by rounding down a non-integer DRX cycle.
  • the terminal device starts the wake-up timer 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 non-integer DRX cycle may be a non-integer long DRX cycle and/or a non-integer short DRX cycle.
  • the short DRX cycle when a non-integer long DRX cycle is configured, the short DRX cycle is not configured; or, when a non-integer short DRX cycle is configured, the long DRX cycle is an integer.
  • the apparatus 900 further includes:
  • 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.
  • the second configuration information may be an RRCReconfiguration message; the second information unit may be a ConfiguredGrantConfig IE.
  • 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:
  • the terminal device 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;
  • 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.
  • An embodiment of the present application also provides a DRX configuration device.
  • FIG10 is a schematic diagram of a DRX configuration device of an embodiment of the present application, and the device may be, for example, a network device, or one or more components or assemblies configured in the network device. Since the principle of solving the problem by the device is the same as the method shown in FIG7 of the embodiment of the second aspect, its specific implementation may refer to the implementation of the method shown in FIG7 of the embodiment of the second aspect, and the same contents will not be repeated.
  • the DRX configuration device 1000 includes:
  • the sending unit 1010 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 includes a second information unit, wherein the second information unit includes a sixth field, and the sixth field indicates the disabling of CG retransmission monitoring for configuration authorization.
  • the second configuration information is an RRCReconfiguration message; the second information unit is a ConfiguredGrantConfig IE.
  • all configured uplink grants in the above-mentioned configured grants are prohibited from starting the drx-HARQ-RTT-TimerUL timer.
  • 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:
  • the terminal device 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;
  • 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.
  • An embodiment of the present application also provides a device for determining a DRX cycle.
  • 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 may be one or more components or assemblies configured in the terminal device.
  • the principle of the problem is the same as the method shown in Figure 6 of the embodiment of the first aspect, and corresponds to the device shown in Figure 9 of the above embodiment. Therefore, its specific implementation can refer to the implementation of the method shown in Figure 6 of the embodiment of the first aspect and the implementation of the device shown in Figure 9 of the above embodiment, and the same contents will not be repeated.
  • the DRX cycle determination device 1100 includes:
  • a receiving unit 1110 receives first configuration information sent by a network 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.
  • the device 1100 further includes: a processing unit 1120 .
  • the processing unit 1120 ignores the configuration of the integer long DRX cycle and its corresponding starting offset.
  • 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.
  • the processing unit 1120 ignores the configuration of the integer long DRX cycle and its corresponding starting offset.
  • the apparatus 1100 may further include:
  • the determining unit 1130 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.
  • the determination unit 1130 can start the wake-up timer.
  • An embodiment of the present application also provides a device for implementing DRX configuration.
  • FIG12 is a schematic diagram of a device for implementing the DRX configuration of an embodiment of the present application, and the device may be, for example, a terminal device, or may be 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 the method shown in FIG8 of the embodiment of the second aspect, and corresponds to the device shown in FIG10 of the above embodiment, its specific implementation may refer to the implementation of the method shown in FIG8 of the embodiment of the second aspect and the implementation of the device shown in FIG10 of the above embodiment, and the same contents will not be repeated.
  • the DRX configuration implementation device 1200 includes:
  • the receiving unit 1210 receives a second configuration message sent by the network device, wherein the second configuration message configures
  • 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.
  • the apparatus 1200 may further include: a processing unit 1220 .
  • 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:
  • the processing unit 1220 starts the drx-HARQ-RT-TimerUL timer for the corresponding HARQ process at the first symbol after the last transmission of the corresponding PUSCH transmission;
  • 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.
  • the devices 900, 1000, 1100, 1200 of the embodiments of the present application may also include other components or modules, and the specific contents of these components or modules may refer to the relevant technology.
  • FIG9 to FIG12 only exemplarily illustrate the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned various 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.
  • the UE energy saving effect is achieved.
  • the 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 described in the embodiment of the first aspect or the second aspect.
  • the behavior of the network device has been described in detail in the embodiments of the first aspect to the third aspect, and its contents are incorporated herein and will not be repeated here.
  • An embodiment of the present application further 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 FIG. 3 of the embodiment of the first aspect or the method described in FIG. 7 of the embodiment of the second aspect.
  • FIG13 is a schematic diagram of a network device according to an embodiment of the present application.
  • the network device 1300 may include: a central processing unit (CPU) 1310 and a memory 1320; the memory 1320 is coupled to the CPU 1310.
  • the memory 1320 may store various data; in addition, it may store information processing programs, and execute the programs under the control of the CPU 1310 to receive various information sent by the terminal device and send the information to the terminal device. Devices send various information.
  • 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.
  • the 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 of the prior art and are not described in detail here. It is worth noting that the network device 1300 does not necessarily include all the components shown in FIG3 ; in addition, the network device 1300 may also include components not shown in FIG13 , which may refer to the prior art.
  • 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 FIG. 6 of the embodiment of the first aspect or the method described in FIG. 8 of the embodiment of the second aspect.
  • FIG14 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 1400 may include a processor 1410 and a memory 1420; the memory 1420 stores data and programs and is coupled to the processor 1410. It is worth noting that the figure is exemplary; other types of structures may also be used to supplement or replace the structure to implement telecommunication functions or other functions.
  • 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.
  • 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 the above 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 the components shown in FIG14 , and the above components are not necessary; in addition, the terminal device 1400 may also include components not shown in FIG14 , and reference may be made to the prior art.
  • 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. 7 of the embodiment of the second aspect in the network device.
  • 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. 7 of the embodiment of the second aspect in a network device.
  • the embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program causes the computer to execute the method described in FIG. 6 or the method described in FIG. 7 of the embodiment of the first aspect in the terminal device. The method described in FIG. 8 of the embodiment of the second aspect.
  • 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. 6 of the embodiment of the first aspect or the method described in FIG. 8 of the embodiment of the second aspect in a terminal device.
  • the above devices and methods of the present application can be implemented by hardware, or by hardware combined with software.
  • the present application relates to such a computer-readable program, which, when executed by a logic component, enables the logic component to implement the above-mentioned devices or components, 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.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams shown in the figure and/or one or more combinations of the functional block diagrams may correspond to various software modules of the computer program flow or to various hardware modules.
  • These software modules may correspond to the various steps shown in the figure, respectively.
  • These hardware modules may be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).
  • FPGA field programmable gate array
  • the software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, 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 a memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • the functional blocks described in the drawings and/or one or more combinations of functional blocks it can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in the present application.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • it can 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.
  • a method for configuring a DRX cycle comprising:
  • 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;
  • 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.
  • 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;
  • the fifth field includes a third integer and a fourth integer
  • the third integer is a numerator in a fractional expression of the non-integer short DRX cycle
  • the fourth integer is a denominator in a fractional expression of the non-integer short DRX cycle.
  • the third integer and the fourth integer are respectively of enumeration type
  • 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;
  • 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.
  • 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;
  • the fifth field includes a fourth integer
  • 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.
  • the terminal device determines the time to start the wake-up period of the non-integer DRX cycle, wherein:
  • the terminal device then starts a wake-up timer for the DRX group after a time slot offset length after the start of the subframe corresponding to the subframe number.
  • the terminal device determines the time to start the wake-up period of the non-integer DRX cycle, wherein:
  • 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.
  • DCP downlink control information
  • a module B in the above formula is replaced by A-floor(A*N2/N1)*N1/N2;
  • B N1/N2
  • the calculation is performed according to the order of the operators in A-floor (A*N2/N1)*N1/N2 from left to right.
  • 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.
  • the short DRX cycle is not configured; or when the non-integer short DRX cycle is configured, the long DRX cycle is an integer.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种非连续接收周期的配置方法和装置，所述方法包括：网络设备向终端设备发送第一配置消息，所述第一配置消息配置了由一个或多个分数表示的非整数的DRX周期；所述第一配置信息包括第一信息单元，所述第一信息单元包括指示非整数的长DRX周期及其起始偏移量和/或指示非整数的短DRX周期的字段。根据本申请实施例，通过在RRC和/或MAC层进行DRX相关的增强，来解决不同XR业务流量的到达周期以及多XR业务流量的情况下的DRX配置和操作问题，更好地支持针对XR业务以及媒体业务的UE节能。

Description

非连续接收周期的配置方法和装置 技术领域
本申请涉及通信领域。
背景技术
在3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)服务和网络中支持扩展现实(eXtended Reality，XR)业务，XR业务指的是计算机技术和可穿戴设备产生的所有现实和虚拟组合的环境和人机交互。其应用领域包括但不限于娱乐、医疗、教育等。XR业务可以包括虚拟现实(Virtual reality，VR)业务、增强现实(Augmented reality，AR)业务和混合现实(Mixed reality，MR)业务等代表形式及混合交叉的领域。
虚拟现实是发布的视觉和音频场景的渲染版本，当观察者或用户在应用程序定义的限制内移动时，渲染旨在尽可能自然地模拟现实世界的视觉和听觉感官刺激。增强现实是指向用户提供附加信息或人工生成的项目或覆盖在其当前环境上的内容。混合现实是AR的一种高级形式，其中一些虚拟元素被插入到物理场景中，目的是提供一种错觉，让人感觉这些元素是真实场景一部分。
PDU Set(PDU集)由一个或多个PDU(Protocol Data Unit，协议数据单元)组成，这些PDU携带了在应用层生成的一个信息单元的有效载荷，例如，用于XR和媒体服务的帧或视频切片。在一些实施方式中，应用层需要PDU Set中的所有PDU来使用相应的信息单元。在其他实施方式中，当某些PDU丢失时，应用层仍然可以恢复全部或部分信息单元。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，为了降低终端设备的功耗，3GPP从3G时代就开始使用非连续接收(DRX)技术。当终端设备被配置了DRX时，终端设备不需要连续地监听物理下 行控制信道(PDCCH)，从而达到节能的目的。
为了使终端设备在使用XR业务时降低功耗，可以将DRX周期和数据到达周期匹配，并将唤醒期和数据到达时间大致对齐，这样，在数据到达时，UE可以监听基站发送的PDCCH，从中得到调度信息，对数据进行及时的调度。然而，目前的DRX周期定义为单位为毫秒的不同的整数值，如果数据到达周期为非整数，那么就会导致该数据到达周期和DRX的周期不匹配，在一段时间后，会发生数据到达时间落在休眠期的情况，这样UE将监听不到PDCCH，从而会影响对数据的及时调度，增加数据传输延迟。
针对上述问题至少之一或者其他类似问题，本申请实施例提供了一种非连续接收(DRX)周期的配置方法和装置。
根据本申请实施例的一方面，提供一种DRX周期的配置装置，应用于网络设备，所述装置包括：
发送单元，其向终端设备发送第一配置消息，所述第一配置消息配置了由一个或多个分数表示的非整数的DRX周期；所述第一配置信息包括第一信息单元，所述第一信息单元包括指示非整数的长DRX周期及其起始偏移量和/或指示非整数的短DRX周期的字段。
根据本申请实施例的另一方面，提供一种DRX周期的配置装置，应用于网络设备，所述装置包括：
发送单元，其向终端设备发送第二配置消息，所述第二配置消息配置了针对配置授权的禁用CG重传监听；所述第二配置消息包含第二信息单元，所述第二信息单元包括第六字段，所述第六字段指示了针对配置授权的禁用CG重传监听。
本申请实施例的有益效果之一在于：根据本申请实施例，通过在RRC和/或MAC层进行DRX相关的增强，来解决不同XR业务流量的到达周期以及多XR业务流量的情况下的DRX配置和操作问题，更好地支持针对XR业务以及媒体业务的UE节能。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多 个其它实施方式中使用，与其它实施方式中的特征相组合或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是DRX周期的一示意图；
图2是DRX周期和XR流量周期不匹配的一示意图；
图3是本申请实施例的DRX周期的配置方法的一示意图；
图4是DRX配置的一个示例的示意图；
图5是长DRX周期和短DRX周期的持续监听时间没有对齐的一示意图；
图6是本申请实施例的DRX周期的确定方法的一示意图；
图7是本申请实施例的DRX的配置方法的另一示意图；
图8是本申请实施例的DRX配置的实施方法的另一示意图；
图9是本申请实施例的DRX周期的配置装置的一示意图；
图10是本申请实施例的DRX的配置装置的另一示意图；
图11是本申请实施例的DRX周期的确定装置的一示意图；
图12是本申请实施例的DRX配置的实施装置的另一示意图；
图13是本申请实施例的网络设备的一示意图；
图14是本申请实施例的终端设备的一示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、收发节点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB) 以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，还可以是IAB-MT，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
目前，5G技术正在研究支持先进媒体服务的关键问题、解决方案和结论，例如高数据速率低延迟(HDRLL，High Data Rate Low Latency)服务、AR/VR/XR服务和触觉/多模态通信服务。目标包括：
1.支持多模式服务的增强功能，包括：
-研究是否以及如何启用应用程序在类似时间向用户提供相关的触觉和多模式数据(例如，与特定时间相关的音频、视频和触觉数据)，重点关注增强策略控制的需求(例如QoS策略协调)。
2.增强网络暴露以支持5GS(5G系统)与应用程序之间的交互，包括：
-研究是否以及如何在多个UE之间或每个UE的多个QoS流之间进行应用同步和QoS(Quality of Service，服务质量)策略协调，以及如何在AF和5GS之间进行交互。
-研究5GS QoS信息(例如QoS能力)和网络条件对应用程序的暴露，以实现快速编解码器/速率自适应，有助于提供所需的QoE(例如帮助缓解5GS拥塞)。
3.研究是否以及如何针对XR服务和媒体服务传输执行以下QoS和策略增强，包括：
-研究能够提高网络资源使用率和QoE(Quality of Experience，体验质量)的媒体服务的流量特性。
-增强QoS框架以支持PDU Set粒度(例如视频/音频帧/tile、应用数据单元、控制信息)，其中，PDU Set由具有相同QoS要求的PDU组成。
-考虑到PDU Set的不同重要性，支持差异化的QoS处理。例如，合法丢弃属于不太重要的PDU Set的数据包，以减少资源浪费。
-是否以及如何支持上行链路-下行链路传输协调以满足UE到UPF(User Plane Function，用户面功能)的N6终结点之间的RTT(Round Trip Time，往返时间)延迟要求。
-潜在的策略增强以最大限度地减少抖动，重点是来自AF(Application Function，应用功能)的需求供应、PCC(policy and charging control，策略和计费控制)规则的扩展。
为了降低UE的功耗，3GPP从3G时代就开始使用DRX技术。DRX的全称是Discontinuous Reception(非连续接收)，DRX在RRC IDLE(空闲态)和RRC CONNECTED(连接态)下的机制是不同的。空闲态下的DRX机制即寻呼机制，就是网络侧通过下发paging消息唤醒UE，在本申请实施例中，以连接态下的DRX(Connected DRX，C-DRX)为例进行说明。在以下的说明中，如无特别说明，DRX是指UE处于连接态时所使用的DRX，也就是C-DRX。
当UE被配置了DRX时，UE不需要连续地监听PDCCH(Physical Downlink Control Channel，物理下行控制信道)，从而达到节能的目的。UE的MAC实体可以被RRC信令配置DRX功能，用于控制UE的关于MAC实体的某些RNTI(Radio Network Temporary Identifier，无线网临时标识)的PDCCH监听活动。
DRX的基本机制是为处于RRC CONNECTED态的UE配置一个DRX cycle(DRX周期)。DRX cycle由On Duration(唤醒期)和Opportunity for DRX(休眠期)组成。在“On Duration”时间内，UE监听并接收PDCCH；在“Opportunity for DRX”时间 内，UE不接收PDCCH以减少功耗。DRX周期定义了唤醒期跟随着可能的非活动时期的周期重复，如图1所示。
为了兼顾省电和时延，根据UE醒来以后监听特定调度信道的时间的长度，NR支持两种DRX周期：长DRX周期和短DRX周期。如果预测到UE数据到达比较频繁或者业务对时延比较敏感，网络侧可以配置UE使用短DRX周期；如果预测到UE数据比较稀疏且对时延不敏感，网络侧可以配置UE仅使用长DRX周期。为了便于UE进行长短DRX周期的切换，要求长DRX周期是短DRX周期的整数倍，这样可以保证两者的持续监听时间(onDuration)对齐。
发明人发现，现有的XR业务的帧速率有很多种，其中大多数帧速率对应了非整数的数据到达周期。如果以毫秒为单位，XR业务流量的到达周期(简称为XR流量周期或者数据发送周期，等等)可能会是非整数(有理数)。比如说帧速率为15,30,45,60,72,90和120帧每秒的XR业务分别对应了非整数(分别为66.66,33.33,22.22,16.66,13.88,11.11和8.33毫秒)的数据周期。
目前的DRX周期定义为单位为毫秒的不同的整数值。为了使UE在使用XR业务时降低功耗，可以将DRX周期和数据(例如XR业务流量)到达周期匹配，并将唤醒期和数据到达时间大致对齐，这样，在数据到达时，UE可以监听基站发送的PDCCH，从中得到调度信息，对数据进行及时的调度。如果数据到达周期为非整数，那么就会导致该数据到达周期和DRX的周期不匹配，在一段时间后，会发生数据到达时间落在休眠期的情况，这样UE将监听不到PDCCH，从而会影响对数据的及时调度，增加数据传输延迟。
图2以帧速率为60帧每秒(对应数据到达周期约为16.67毫秒)为例，如果将DRX周期设为16毫秒，经过几个DRX周期之后，会导致DRX唤醒期和数据到达时间(图2中66.67ms处)不对齐的问题。
在考虑XR业务流量的到达周期特点情况下，如何解决DRX周期和XR业务流量的到达周期的不匹配的问题需要进行进一步标准化和技术实现。
下面结合附图对本申请的各种实施方式进行说明。这些实施方式只是示例性的，不是对本申请的限制。在下面的说明中，“如果…”、“在…的情况下”、“当…时”等说法含义相同，可以互换。
第一方面的实施例
本申请实施例提供一种DRX周期的配置方法，从网络设备的一侧进行说明。图3是本申请实施例的DRX周期的配置方法的一示意图。如图3示，该方法包括：
310：网络设备向终端设备发送第一配置消息，所述第一配置消息配置了由一个或多个分数表示的非整数的DRX周期；所述第一配置信息包括第一信息单元，所述第一信息单元包括指示非整数的长DRX周期及其起始偏移量和/或指示非整数的短DRX周期的字段。
值得注意的是，以上附图1仅示意性地对本申请实施例进行了说明，但本申请不限于此。例如还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图3的记载。
根据上述实施例，解决了DRX周期不支持非整数数据到达周期的问题，实现了UE节能。
在一些实施例中，第一配置消息为RRCReconfiguration消息，第一信息单元为DRX-Config IE。根据上述实施例，通过对RRC配置进行增强，使RRC能够配置DRX周期为有理数(也即分数)，解决了DRX周期不支持非整数数据到达周期的问题。
在上述实施例中，以针对RRCReconfiguration消息中的DRX-Config IE进行增强，增加支持DRX周期为有理数的配置为例，但本申请不限于此。也可以对其他配置消息中的其他信息单元进行增强，或者在RRCReconfiguration消息或其他配置消息中增加新的IE来进行上述配置。
为了方便说明，下面以针对RRCReconfiguration消息中的DRX-Config IE进行增强为例。
在一些实施例中，对非整数的长DRX周期和起始偏移量进行统一定义。
在上述实施例中，第一信息单元包括第一字段，该第一字段包括与帧率对应的非整数(分数)的长DRX周期及其对应的起始偏移量的组合，例如可以称为drx-NonIntegerLongCycleStartOffset，本申请不限于此，该第一字段也可以有其他名字。
在上述实施例中，第一字段例如为CHOICE结构，该CHOICE结构中的每个元素为预定义的对应某帧率的非整数的长DRX周期和其对应的以毫秒为单位的起始偏移量的组合。第一字段为CHOICE结构，表明了配置时从事先定义好的对应某个帧率的非整数的长DRX周期和对应的以毫秒为单位的起始偏移量中进行选择。
在上述实施例中，非整数的长DRX周期可以由以毫秒为单位的分数表达，该分数由整数的分子和分母表达，例如200/3ms，此外，每个非整数的长DRX周期对应的起始偏移量的取值范围是0到对该非整数的长DRX周期向下取整的值，例如0～66。
下面是第一字段的一个示例：
在上面的示例中，第一字段drx-NonIntegerLongCycleStartOffset包含了以毫秒为单位的分数值drx-NonIntegerLongCycle(非整数的长DRX周期)和以毫秒为单位的drx-StartOffset(起始偏移量)。其中值“ms200/3”对应的是200/3毫秒，也就是帧率为15帧每秒(1000ms/15fps＝200/3ms)，其他分数值以此类推。此外，上述示例中，“ms200/3”只是一种用两个整数(分子和分母，通常为互质的整数)来表示一个分数的方法，本申请对此不做限制，还可以表示为“ms200by3”，“ms200over3”等等。上面的示例中定义的非整数的长DRX周期分别对应了15fps,30fps,45fps,60fps,72fps,90fps,120fps的帧率。
在上述实施例中，如果第一字段被配置，终端设备可以忽略drx-LongCycleStartOffset(也就是整数的长DRX周期和对应的起始偏移量)的配置。由此，避免了终端行为的模糊。
在上述实施例中，第一信息单元还可以包括第二字段，该第二字段包括与帧率对应的非整数的短DRX周期。
在上述实施例中，针对非整数的短DRX周期，可以在DRX-Config IE中定义新的第二字段，该第二字段为对应某个帧率的非整数(分数)的短DRX周期。该第二字段例如可以称为drx-NonIntegerShortCycle，本申请不限于此，该第二字段也可以有其他名字。
在上述实施例中，该第二字段可以是枚举类型，使用时从事先定义好的由分数表达的以毫秒为单位的短DRX周期中进行选择。
下面是第二字段的一个示例：
在上面的示例中，第二字段中的值“ms200/3”对应的是200/3毫秒，以此类推。
在上述实施例中，如果第二字段被配置，终端设备可以忽略drx-ShortCycle(也就是整数的短DRX周期)的配置。由此，避免了终端行为的模糊。
在上述实施例中，如果第二字段被配置，第一字段中的非整数的长DRX周期的值必须是第二字段的值的整数倍。比如第二字段被配置为ms100/3，第一字段中的非整数的长DRX周期可以配置为ms200/3。由此，可以保证两者的持续监听时间(onDuration)对齐。
在另一些实施例中，对非整数的长DRX周期和起始偏移量分别定义。
在上述实施例中，第一信息单元包括第三字段和第四字段，例如在DRX-Config IE中定义新的第三字段和第四字段。第三字段包括与帧率对应的非整数的长DRX周期，第四字段包括针对上述非整数的长DRX周期的起始偏移量。
在上述实施例中，第三字段定义了非整数(分数)的长DRX周期，比如叫做drx-NonIntegerLongCycle，由两个整数(第一整数和第二整数)来表示，比如叫做N1和N2，其中N1表示上述非整数的长DRX周期的分数表达形式N1/N2中的分子，N2表示上述非整数的长DRX周期的分数表达形式N1/N2中的分母。
在上述实施例中，N1和N2可以为整数型，取值范围分别为支持的非整数的长DRX周期的分数表达形式中的分子和分母的变化范围。这样，N1和N2可以在各自的范围内任意取值，扩展性强，并且可以支持更多的不同数据速率的业务。
下面是第三字段的一个示例，示出了N1和N2分别为整数型的情况：

在上述实施例中，N1和N2也可以是枚举型，取值范围分别包括支持的非整数的长DRX周期的分数表达形式中的分子和分母的固定值，还可以分别包括保留的备用位。这样信令开销要小一些，也保持了一定扩展性，可以支持更多的不同数据速率的业务。
下面是第三字段的另一个示例，示出了N1和N2分别为枚举型的情况：
在上述实施例中，以第三字段包括N1和N2两个整数为例，由于N1和N2是为了用分数表明XR视频业务的非整数周期，实际就是由1000毫秒除以帧率并进行约分所得。在一些实施方式中，也可以不进行约分，也就是直接使用N1＝1000ms，N2＝帧率，则这种情况下，不需要指示N1，只需要指示帧率即可。
也即，上述第三字段也可以仅包括一个整数，也即第二整数，例如N2，来表示非整数的长DRX周期。终端设备在收到该第三字段后，可以将1000毫秒与该第二整数的商，也即1000/N2作为分数表示的非整数的长DRX周期。
在上述实施例中，第四字段定义了针对非整数的长DRX周期的起始偏移量，比如叫做drx-StartOffsetForNonIntCycle。该第四字段可以为整数类型，取值范围可以是0到Nmax。Nmax为支持的最大非整数的长DRX周期向下取整的值，比如66毫秒。
在上述实施例中，当第三字段被配置时，第四字段必须被配置。由此，能够保证非整数的长DRX周期的配置的完整性。
在上述实施例中，当第三字段被配置时，终端设备可以忽略drx-LongCycleStartOffset(也即整数的长DRX周期及其对应的起始偏移量)的配置。由此，避免了终端行为的模糊。
在上述实施例中，第一信息单元还包括第五字段，该第五字段包括与帧率对应的非整数的短DRX周期。
在上述实施例中，针对非整数的短DRX周期，可以在DRX-Config IE中定义新的第五字段，第五字段定义了对应某个帧率的非整数(分数)的短DRX周期。该第五字段例如可以称为drx-NonIntegerShortCycle，由两个整数来表示，字段设计和第三字段一样，也可以由上述两种示例来表示。
例如，第五字段包括第三整数和第四整数，第三整数为非整数的短DRX周期的分数表达形式中的分子，第四整数为非整数的短DRX周期的分数表达形式中的分母。
在一个示例中，第三整数和第四整数分别为整数型，第三整数的取值范围为支持的非整数的短DRX周期的分数表达形式中的分子的变化范围；第四整数的取值范围为支持的非整数的短DRX周期的分数表达形式中的分母的变化范围。
在另一个示例中，第三整数和第四整数分别为枚举型；第三整数的取值范围包含支持的非整数的短DRX周期的分数表达形式中的分子的固定值，还可以包含保留的备用位；第四整数的取值范围包含支持的非整数的短DRX周期的分数表达形式中的分母的固定值，还可以包含保留的备用位。
在上述实施例中，以第五字段包括第三整数和第四整数为例，与第三字段类似，在不进行约分的情况下，也可以不指示第三整数而只指示第四整数，也即，第五字段仅包括第四整数，该第四整数表示非整数的短DRX周期，终端设备将1000毫秒与该第四整数的商作为分数表示的非整数的短DRX周期。
在上述实施例中，第三字段和第五字段都是以毫秒为单位的有理数，表明非整数的DRX周期定义为N1/N2毫秒。
在上述实施例中，如果第五字段被配置，则第三字段的值必须是第五字段的值的整数倍。
在上述实施例中，与第三字段类似，如果第五字段被配置，终端设备可以忽略drx-ShortCycle(也即整数的短DRX周期)的配置。由此，避免了终端行为的模糊。
以上对非整数的长DRX周期、起始偏移量、非整数的短DRX周期的实施方式进行了说明，在本申请实施例中，还可以进一步对DRX唤醒期的起始时间的计算公式进行增强。也即在判断何时开始非整数的DRX周期的唤醒期时，需要通过公式进行计算。
另外，为了解决SFN(系统帧号)翻转时，DRX周期和SFN边界对不齐的问题，可以增加一个计数器(第一计数器)，比如叫做DRX_SFN_COUNTER，该计数器在每SFN翻转时增加1，也即在SFN变化为0时的时隙的第一个字符时间将该第一计数器加1。该计数器初始值为0，最大值为65535。此外，还可以定义一个用于确定起始偏移量的时间参考系统帧号(SFN)，比如叫做drx-TimeReferenceSFN，取值为0或者512，用于确定DRX的唤醒期的开始时间。终端设备使用在收到带有该时间参考SFN的DRX配置之前离指示的参考SFN最近的SFN。
在一些实施例中，终端设备确定启动上述非整数的DRX周期的唤醒期的时间。例如，当DRX周期被配置时，终端设备的MAC实体确定启动非整数的DRX周期的唤醒期的时间。
在一个示例中，
如果为某个DRX组使用了短DRX周期，且非整数的短DRX周期被配置(例如前述第二字段或第五字段被配置)，且当前的第一计数器(DRX_SFN_COUNTER)、系统帧号(SFN)以及子帧号满足如下公式：
floor([(第一计数器×10240)+(系统帧号×10)+子帧号]modulo(非整数的短DRX周期))＝floor([(时间参考系统帧号×10)+起始偏移量)]modulo(非整数的短DRX周期))，
则终端设备为上述DRX组在上述子帧号对应的子帧开始之后的时隙偏移量(drx-SlotOffset)时长之后开启唤醒定时器(drx-onDurationTimer)。
在另一个示例中，
如果为某个DRX组使用了长DRX周期，且非整数的长DRX周期被配置(例如前述第一字段或第三字段被配置)，且当前的第一计数器(DRX_SFN_COUNTER)、系统帧号(SFN)以及子帧号满足如下公式：
floor([(第一计数器×10240)+(系统帧号×10)+子帧号]modulo(非整数的长DRX周期))＝floor([(时间参考系统帧号×10)+起始偏移量)]modulo(非整数的长DRX周期))，
则终端设备在没有为激活的下行带宽部分(BWP，BandWidth Part)配置带有通过节能无线网临时标识加扰的循环冗余校验的下行控制信息(DCP，DCI with CRC scrambled by PS_RNTI)监听的情况下，为上述DRX组在上述子帧号对应的子帧开 始之后的时隙偏移量(drx-SlotOffset)时长之后开启唤醒定时器。
上述公式中modulo为取模(求余)计算，由于是对有理数(即非整数的DRX周期，由N1/N2表示)进行取模，为了在计算中不产生舍入误差，公式中的A modulo B(B＝N1/N2)可以使用A-floor(A*N2/N1)*N1/N2来替代，且需要按照该替代公式中的操作符顺序来进行计算，从而不产生舍入误差。具体顺序指在计算时按照公式中从左到右的顺序进行操作运算。
下面是根据上述实施例对TS 38.321的DRX过程进行增强的一个示例：
在上述实施例中，DRX组(group)是指RRC配置的具有相同DRX激活时间(Active Time)的服务小区组。为了使不同DRX组的DRX周期对齐，可以将下面参数设为各DRX组公用：非整数的长DRX周期，起始偏移量，非整数的短DRX周期，以及 drx-TimeReferenceSFN。也即，在本申请实施例中，各DRX组可以公用以下参数：非整数的长DRX周期，所述非整数的长DRX周期对应的起始偏移量，非整数的短DRX周期，以及时间参考帧号。关于上述各参数的含义，已经在前面做了说明，其内容被合并于此，此处不再赘述。
在一些实施例中，考虑到上述公式中使用了第一计数器(DRX_SFN_COUNTER)，该第一计数器需要在网络侧和终端侧同步，也就是保持同样的数值。终端设备可以在收到关于非整数的DRX周期的RRC配置(比如非整数的长DRX周期的RRC配置，也即上述第一配置消息)时，将该计数器初始化为0，并且在SFN变化为0时的时隙的第一个字符时间将该第一计数器加1。由于该第一计数器在每SFN翻转(wrap around)时增加1，如果在SFN刚刚翻转时(例如SFN＝0或者是很小的值)，终端设备收到关于非整数的DRX周期的RRC配置，由于有网络时延，终端设备不能判断网络侧发出该配置时SFN是否已经翻转，所以无法正确初始化DRX_SFN_COUNTER，也即无法和网络同步DRX_SFN_COUNTER。
在上述实施例中，终端设备可以根据上述RRC配置(例如上述非整数的DRX周期的RRC配置，也即上述第一配置消息)所携带的时间参考SFN(drx-TimeReferenceSFN)来进行上述第一计数器(DRX_SFN_COUNTER)的初始化。
例如，当终端设备收到网络侧发送的关于非整数的DRX周期的RRC配置时，如果时间参考SFN取值为0，那么说明网络侧发送该配置时SFN为整个SFN周期的前半部分(也即SFN 0-511)，终端设备收到该配置时肯定不会发生SFN翻转，所以终端设备可以将DRX_SFN_COUNTER设为0。
再例如，当网络侧发送关于非整数的DRX周期的RRC配置时，如果时间参考SFN取值为512，那么说明当前SFN为整个SFN周期的后半部分(也即SFN 512-1023)，如果终端设备收到该配置时SFN仍然为SFN周期的后半部分，那么说明没有发生SFN翻转，所以终端设备可以将DRX_SFN_COUNTER设为0；如果终端设备收到该配置时SFN处于SFN周期的前半部分，那么说明发生了SFN翻转，所以终端设备可以将DRX_SFN_COUNTER设为1。
由此，终端设备根据接收到的非整数的DRX周期的RRC配置所携带的时间参考SFN来进行上述DRX_SFN_COUNTER的初始化，可以保证网络侧和UE侧的 DRX_SFN_COUNTER同步。
在上述实施例中，非整数的DRX周期可以是非整数的长DRX周期，也可以是非整数的短DRX周期。
下面是根据上述实施例对TS 38.321的DRX过程进行增强的另一个示例，用于实现DRX_SFN_COUNTER的正确初始化：
在上述实施例中，在网络侧和终端侧实现了上述DRX_SFN_COUNTER的同步后，在上述非整数的DRX周期的相关公式中，可以省略时间参考SFN。
例如，当DRX周期被配置时，终端设备的MAC实体通过如下方法来确定启动非整数的DRX周期的唤醒期的时间：
如果为某个DRX组使用了短DRX周期，且非整数的短DRX周期被配置(例如前述第二字段或第五字段被配置)，且当前的DRX_SFN_COUNTER、SFN、子帧号满足如下公式：
floor([(DRX_SFN_COUNTER×10240)+(SFN×10)+subframe number]modulo(非整数的短DRX周期))＝floor((起始偏移量)modulo(非整数的短DRX周期))，
则终端设备为上述DRX组在上述subframe number对应的子帧开始之后的drx-SlotOffset(时隙偏移量)时长之后开启唤醒定时器(drx-onDurationTimer)。
如果为某个DRX组使用了长DRX周期，且非整数的长DRX周期被配置(例如前述第一字段或第三字段被配置)，且当前的DRX_SFN_COUNTER、SFN、子帧号 满足如下公式：
floor([(DRX_SFN_COUNTER×10240)+(SFN×10)+subframe number]modulo(非整数的长DRX周期))＝起始偏移量，
则终端设备在没有为激活的下行带宽部分(BWP，BandWidth Part)配置DCP(DCI with CRC scrambled by PS_RNTI)监听的情况下，为上述DRX组在上述subframe number对应的子帧开始之后的drx-SlotOffset时长之后开启唤醒定时器。
值得注意的是，上述公式中对分数进行modulo计算可以参考前面方法，以避免舍入误差。
根据上述实施例，进一步解决了DRX周期不支持非整数数据达到周期的问题。
在本申请实施例中，发明人进一步发现，对于非整数的DRX周期，由于在DRX唤醒期的起始时间的计算公式中使用了取整操作，从而导致DRX周期平均来讲是个有理数，但是单个DRX周期实际为整数，且每个DRX周期不一定完全相同，可能会有1毫秒的差别。
图4是DRX配置的一个示例的示意图。在图4的示例中，以XR业务帧率60fps(对应周期50/3ms)为例，将DRX周期(可以是长DRX周期，也可以是短DRX周期)配置为50/3毫秒，参考前面的配置方法。当起始偏移量配置为16ms的时候，可能会出现某个DRX周期没有唤醒期的问题，如图4中第三个周期。这样终端设备会监听不到下行控制信息，从而不能收发数据，导致传输时延。
针对上述问题，本申请实施例进一步提供了解决方案。
在一些实施例中，将起始偏移量的最大值配置为floor(非整数的长DRX周期)-1。
仍以第一信息单元包括第一字段，该第一字段为CHOICE结构，且包括与帧率对应的非整数的长DRX周期和起始偏移量为例，与前面实施例不同的是，该起始偏移量的最大值不再是对非整数的长DRX周期向下取整后得到的值，而是对非整数的长DRX周期向下取整后得到的值-1，如下：

根据上述实施例的方法，解决了DRX周期没有唤醒期的问题。
在上述实施例中，非整数的DRX周期的唤醒期的时长可以设置为比起始偏移量的最大值为其他值时对应的DRX周期的唤醒期的时长更长。也即，网络侧可以在配置偏移量为floor(非整数的长DRX周期)-1时，配置一个较长的唤醒期(也即较长的onDurationTimer)。尤其是网络侧在周期流量期望的到达时间对应的偏移量floor(非整数的长DRX周期)之后时，配置一个较长的唤醒期，比如比平常的配置大1毫秒的值。由此，避免了由于前述配置导致终端设备可能提前开启唤醒期从而错过较晚到达的业务的问题。
在上述实施例中，当配置了非整数的DRX周期且前一个DRX周期的实际周期长度等于对该非整数的DRX周期进行向下取整得到的值加1时，终端设备将当前的DRX周期的唤醒期延长。也即，如果起始偏移量被配置为floor(非整数的长DRX周期)-1，且前一个DRX周期长度等于floor(非整数的长DRX周期)+1时，终端设备自行将当前DRX周期的唤醒期延长，比如增加1毫秒。floor(非整数的长DRX周期)+1也等于ceil(非整数的长DRX周期)。Ceil(x)指对x向上取整。判断前一个DRX周期的实际长度可以由当前DRX周期的唤醒期的起始时间减去前一个DRX周期的唤醒期的起始时间得到。由此，避免了由于前述配置导致终端设备可能提前开启唤醒期从而错过较晚到达的业务的问题。
在另一些实施例中，起始偏移量的最大值仍然配置为floor(非整数的长DRX周期)，而对UE侧进行增强。
例如，如果从上一个唤醒期定时器开始的时间过了一个DRX周期的长度之后唤醒期定时器没有运行过，则终端设备启动唤醒定时器。也即，当起始偏移量被配置为floor(非整数的长DRX周期)时，如果从上一个唤醒期定时器开始的时间过了一个DRX周期之后，唤醒期定时器没有运行过，则终端设备自主启动唤醒期定时器，也即开启唤醒期。此处的DRX周期可以是floor(非整数的长DRX周期)+1毫秒。由此，也解决了DRX周期没有唤醒期的问题。
前面以非整数的长DRX周期为例，本申请不限于此，非整数的短DRX周期以 此类推。
在本申请实施例中，发明人进一步发现，如果短DRX周期被配置且为非整数，且长DRX周期也为非整数(仍然为短DRX周期的整数倍)，在某些配置的情况下会出现长短DRX周期的唤醒期没有对齐的情况。例如，长DRX周期配置为50/3ms，短DRX周期配置为25/3ms，起始偏移量配置为15ms，在某些时刻可能会出现图5所示的情况，也即，在31ms和48ms左右的时刻，短DRX周期的唤醒期和长DRX周期的唤醒期不在同时启动，由于该情况不符合传统协议标准，这样会造成一些终端设备的未知操作，增加设备开发的复杂度。
针对上述问题，本申请实施例进一步提供了解决方案。
在一些实施例中，当非整数的长DRX周期被配置时，短DRX周期不被配置。也即，针对上述问题，不定义非整数的短DRX周期。也就是支持非整数数据周期XR业务时，只能配置长DRX周期为非整数，配置了非整数的长DRX周期时，不配置短DRX周期。这种方法实现简单，减少设计复杂度。
在另一些实施例中，当非整数的短DRX周期被配置时，长DRX周期为整数。也即，针对上述问题，当配置了非整数的短DRX周期时，长DRX周期必须是整数，也即必须使用(现有的)drx-LongCycleStartOffset。这种方法保留了短DRX周期，提高了UE节能的灵活性，能够更好地支持数据突发。
在本申请实施例中，为了支持更好的UE节能，对配置授权(configured grant，CG)的上行调度传输，可以不启动上行HARQ(hybrid automatic repeat request)RTT(round-trip time)定时器(drx-HARQ-RTT-TimerUL)，从而不启动重传，这对短周期的、时延敏感的XR业务尤其重要。
在一些实施例中，网络设备还可以向终端设备发送第二配置信息，该第二配置信息配置了针对配置授权的禁用CG重传监听。其中，该第二配置信息可以包括第二信息单元，该第二信息单元包括第六字段，该第六字段指示了针对配置授权的禁用CG重传监听。
在上述实施例中，第二配置消息例如可以是RRCReconfiguration消息，第二信息单元例如可以是ConfiguredGrantConfig IE，第六字段例如可以称为disableCG-RetransmissionMonitoring，本申请不限于此。根据本申请实施例，可以对每个配置授权增加一个配置，用于禁用CG重传监听，也就是对上行配置授权传输禁 止启动drx-HARQ-RTT-TimerUL定时器。由此，解决了CG不支持免上行重传的问题，增强了含有时延敏感业务，比如XR业务的UE节能。
在上述实施例中，如果配置授权是一个包含多(multi-)PUSCH(Physical Uplink Shared CHannel)的配置授权，也就是CG配置中在一个周期内包含了多个连续的配置上行授权(configured uplink grant)，那么第六字段的配置适用于该配置授权中的所有配置上行授权，也就是所有的PUSCH传输时机(occasion)。在一些实施例中，当第六字段被配置时，对CG中的所有配置上行授权都禁止启动drx-HARQ-RTT-TimerUL定时器。由此，解决了多PUSCH的CG不支持免上行重传的问题，增强了含有时延敏感业务，比如XR业务的UE节能。
在一些实施例中，如果终端设备的服务小区没有被配置上行HARQ模式(uplinkHARQ-Mode)，且如果没有为配置的上行授权所属的多PUSCH CG配置所述第六字段，则：
如果配置了drx-LastTransmissionUL，则在对应的PUSCH传输的(bundle内的)最后传输之后的第一个符号(symbol)为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器；
反之，则在对应的PUSCH传输的(bundle内的)第一个传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器。
下面是根据上述实施例的方法对TS 38.321的DRX过程进行增强的一个示例：

上述实施例的方法可以在DRX周期为非整数时使用，例如可以与前面实施例的通过第一配置信息配置非整数的DRX周期的方法结合使用，也可以在DRX周期为整数时使用，例如不与前面实施例的通过第一配置信息配置非整数的DRX周期的方法绑定而单独使用，本申请不限于此。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
本申请实施例还提供一种DRX周期的确定方法，从终端设备的一侧进行说明。需要说明的是，该方法是与前述实施例的DRX周期的配置方法对应的UE侧的处理，其中与前述实施例相同的内容不再重复说明。
图6是本申请实施例的DRX周期的确定方法的一示意图，如图6所示，该方法包括：
610：终端设备接收网络设备发送的第一配置信息，该第一配置消息配置了由一个或多个分数表示的非整数的DRX周期；该第一配置信息包括第一信息单元，该第一信息单元包括指示非整数的长DRX周期及其起始偏移量和/或指示非整数的短DRX周期的字段。
在一些实施例中，如前所述，如果第一字段被配置，则终端设备忽略整数的长DRX周期及其对应的起始偏移量的配置。
在一些实施例中，如前所述，在第三字段仅包括第二整数的情况下，终端设备可以将1000毫秒与所述第二整数的商作为分数表示的非整数的长DRX周期。
在一些实施例中，如前所述，如果第三字段被配置，则终端设备忽略整数的长DRX周期及其对应的起始偏移量的配置。
在一些实施例中，如图6所示，该方法还可以包括：
620：终端设备确定启动所述非整数的DRX周期的唤醒期的时间。关于确定该非整数的DRX周期的唤醒期的时间的方法，已经在前面做了说明，此处不再赘述。
在上述实施例中，如前所述，如果起始偏移量的最大值为对非整数的DRX周期进行向下取整得到的值减1，则如果从上一个唤醒期定时器开始的时间过了一个DRX周期的长度之后唤醒期定时器没有运行过，终端设备可以启动唤醒定时器。
根据本申请实施例的方法，解决了DRX周期不支持非整数数据达到周期的问题，并支持多个PUSCH的配置授权的免上行重传传输，从而实现UE节能。
第二方面的实施例
本申请实施例提供一种DRX的配置方法，从网络设备的一侧进行说明。与第一方面的实施例相同的内容不再重复说明。
图7是本申请实施例的DRX的配置方法的一示意图，请参照图7，该方法包括：
710：网络设备向终端设备发送第二配置消息，所述第二配置消息配置了针对配置授权的禁用CG重传监听；所述第二配置消息包含第二信息单元，所述第二信息单元包括第六字段，所述第六字段指示了针对配置授权的禁用CG重传监听。
值得注意的是，以上附图7仅示意性地对本申请实施例进行了说明，但本申请不限于此。例如可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图7的记载。
根据上述实施例，通过对每个配置授权增加一个配置，用于禁用CG重传监听，也就是对上行配置授权传输禁止启动drx-HARQ-RTT-TimerUL定时器，解决了在CG包括多PUSCH的CG的情况下不支持免上行重传的问题，增强了含有时延敏感业务，比如XR业务的UE节能。
在一些实施例中，第二配置信息为RRCReconfiguration消息；第二信息单元为ConfiguredGrantConfig IE。本申请不限于此。
在一些实施例中，当第六字段被配置时，对上述配置授权中的所有配置上行授权都禁止启动drx-HARQ-RTT-TimerUL定时器。
在上述实施例中，配置授权是一个包含多(multi-)PUSCH(Physical Uplink Shared CHannel)的配置授权，也就是CG配置中在一个周期内包含了多个连续的配置上行授权(configured uplink grant)，第六字段的配置适用于该配置授权中的所有配置上行授权，也就是所有的PUSCH传输时机(occasion)。
在一些实施例中，如果终端设备服务小区没有被配置上行HARQ模式，且如果没有为配置的上行授权所属的多PUSCH CG配置所述第六字段，则：
如果配置了drx-LastTransmissionUL，则在对应的PUSCH传输的最后传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器；
反之，则在对应的PUSCH传输的第一个传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器。
本申请实施例还提供一种DRX配置的实施方法，从终端设备的一侧进行说明。需要说明的是，该方法是与前述实施例的DRX的配置方法对应的UE侧的处理，其中与前述实施例相同的内容不再重复说明。
图8是本申请实施例的DRX配置的实施方法的一示意图，如图8所示，该方法包括：
810：终端设备接收网络设备发送的第二配置消息，所述第二配置消息配置了针对配置授权的禁用CG重传监听；所述第二配置消息包含第二信息单元，所述第二信息单元包括第六字段，所述第六字段指示了针对配置授权的禁用CG重传监听。
在一些实施例中，如前所述，如果终端设备的服务小区没有被配置上行HARQ模式，且如果没有为配置的上行授权所属的多PUSCH CG配置所述第六字段，则：
如果配置了drx-LastTransmissionUL，则终端设备在对应的PUSCH传输的最后传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器；
反之，则终端设备在对应的PUSCH传输的第一个传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
根据本申请实施例的方法，解决了在CG包括多PUSCH的CG的情况下不支持免上行重传的问题，增强了含有时延敏感业务，比如XR业务的UE节能。
第三方面的实施例
本申请实施例提供一种DRX周期的配置装置。
图9是本申请实施例的DRX周期的配置装置的一示意图，该装置例如可以是网络设备，也可以是配置于该网络设备中的某个或某些部件或者组件。由于该装置解决问题的原理与第一方面的实施例的图3所示的方法相同，因此其具体的实施可以参照第一方面的实施例的图3所示的方法的实施，内容相同之处不再重复说明。
如图9所示，该DRX周期的配置装置900包括：
第一发送单元910，其向终端设备发送第一配置消息，所述第一配置消息配置了由一个或多个分数表示的非整数的DRX周期；所述第一配置信息包括第一信息单元，所述第一信息单元包括指示非整数的长DRX周期及其起始偏移量和/或指示非整数的短DRX周期的字段。
在一些实施例中，第一配置消息为RRCReconfiguration消息。
在一些实施例中，第一信息单元为DRX-Config IE。
在一些实施例中，第一信息单元包括第一字段，第一字段包括与帧率对应的非整数的长DRX周期和起始偏移量的组合。
在上述实施例中，第一字段可以为CHOICE结构，CHOICE结构中的每个元素为预定义的对应某帧率的非整数的长DRX周期和其对应的以毫秒为单位的起始偏移量的组合。
在上述实施例中，非整数的长DRX周期可以由以毫秒为单位的分数表达，该分数由整数的分子和分母表达；每个非整数的长DRX周期对应的起始偏移量的取值范围是0到对该非整数的长DRX周期向下取整的值。
在上述实施例中，非整数的长DRX周期可以包括多个分数值，该多个分数值分别对应以下帧率：15fps,30fps,45fps,60fps,72fps,90fps,120fps。
在上述实施例中，如果第一字段被配置，则终端设备可以忽略整数的长DRX周期及其对应的起始偏移量的配置。
在上述实施例中，第一信息单元还可以包括第二字段，该第二字段包括与帧率对应的非整数的短DRX周期。
在上述实施例中，第二字段可以为枚举型。
在上述实施例中，非整数的短DRX周期可以由以毫秒为单位的分数表达。
在上述实施例中，如果第二字段被配置，则第一字段中的非整数的长DRX周期的值为第二字段中的非整数的短DRX周期的值的整数倍。
在上述实施例中，如果第二字段被配置，则终端设备可以忽略整数的短DRX周期的配置。
在另一些实施例中，第一信息单元包括第三字段和第四字段，第三字段包括与帧率对应的非整数的长DRX周期，第四字段包括针对所述非整数的长DRX周期的起始偏移量。
在上述实施例中，所述第三字段可以包括第一整数和第二整数；第一整数为非整数的长DRX周期的分数表达形式中的分子，第二整数为非整数的长DRX周期的分数表达形式中的分母。
在上述实施例中，第一整数的取值范围可以为支持的非整数的长DRX周期的分数表达形式中的分子的变化范围；第二整数的取值范围可以为支持的非整数的长DRX周期的分数表达形式中的分母的变化范围。
在上述实施例中，第一整数和第二整数可以分别为枚举型；第一整数的取值范围包含支持的非整数的长DRX周期的分数表达形式中的分子的固定值，还可以包含保留的备用位；第二整数的取值范围包含支持的非整数的长DRX周期的分数表达形式中的分母的固定值，还可以包含保留的备用位。
在上述实施例中，所述第三字段可以仅包括第二整数；该第二整数表示非整数的长DRX周期，终端设备将1000毫秒与该第二整数的商作为分数表示的非整数的长DRX周期。
在上述实施例中，第四字段可以为整数类型，取值范围为0到对支持的最大非整数的长DRX周期向下取整的值。
在上述实施例中，当第三字段被配置时，第四字段必须被配置。
在上述实施例中，当第三字段被配置时，终端设备可以忽略整数的长DRX周期及其对应的起始偏移量的配置。
在上述实施例中，第一信息单元还可以包括第五字段，第五字段包括与帧率对应的非整数的短DRX周期。
在上述实施例中，第五字段可以包括第三整数和第四整数；第三整数为所述非整 数的短DRX周期的分数表达形式中的分子，第四整数为所述非整数的短DRX周期的分数表达形式中的分母。
在上述实施例中，第三整数的取值范围可以为支持的非整数的短DRX周期的分数表达形式中的分子的变化范围；第四整数的取值范围可以为支持的非整数的短DRX周期的分数表达形式中的分母的变化范围。
在上述实施例中，第三整数和所述第四整数可以分别为枚举型；第三整数的取值范围包含支持的非整数的短DRX周期的分数表达形式中的分子的固定值，还可以包含保留的备用位；第四整数的取值范围包含支持的非整数的短DRX周期的分数表达形式中的分母的固定值，还可以包含保留的备用位。
在上述实施例中，第五字段也可以仅包括第四整数；第四整数表示非整数的短DRX周期，终端设备将1000毫秒与该第四整数的商作为分数表示的非整数的短DRX周期。
在上述实施例中，如果第五字段被配置，则第三字段中的非整数的长DRX周期的值是第五字段中的非整数的短DRX周期的值的整数倍。
在一些实施例中，终端设备确定启动所述非整数的DRX周期的唤醒期的时间。
在上述实施例中，在一些实施方式中，如果为某个DRX组使用了短DRX周期，且非整数的短DRX周期被配置，且当前的第一计数器、系统帧号以及子帧号满足如下公式：
floor([(第一计数器×10240)+(系统帧号×10)+子帧号]modulo(非整数的短DRX周期))＝floor([(时间参考系统帧号×10)+起始偏移量)]modulo(非整数的短DRX周期))，
则终端设备为所述DRX组在所述子帧号对应的子帧开始之后的时隙偏移量时长之后开启唤醒定时器。
在上述实施例中，在另一些实施方式中，如果为某个DRX组使用了长DRX周期，且非整数的长DRX周期被配置，且当前的第一计数器、系统帧号以及子帧号满足如下公式：
floor([(第一计数器×10240)+(系统帧号×10)+子帧号]modulo(非整数的长DRX周期))＝floor([(时间参考系统帧号×10)+起始偏移量)]modulo(非整数的长DRX周期))，
则终端设备在没有为激活的下行带宽部分配置带有通过节能无线网临时标识加扰的循环冗余校验的下行控制信息(DCP)监听的情况下，为所述DRX组在所述子帧号对应的子帧开始之后的时隙偏移量时长之后开启唤醒定时器。
在前述实施例中，上述公式中的A module B可以使用A-floor(A*N2/N1)*N1/N2来替代；其中，B＝N1/N2，并且，按照A-floor(A*N2/N1)*N1/N2中的操作符的从左到右顺序来进行计算。
在前述实施例中，各所述DRX组可以公用以下参数：非整数的长DRX周期，所述非整数的长DRX周期对应的起始偏移量，非整数的短DRX周期，以及时间参考帧号。
在一些实施例中，终端设备还可以对上述第一计数器进行初始化，例如，在收到第一配置消息时将第一计数器初始化为0；在SFN变化为0时的时隙的第一个字符时间将第一计数器加1。
在一些实施例中，终端设备可以根据接收到的第一配置消息所包含的时间参考SFN来初始化上述第一计数器。
例如，如果该时间参考SFN为0，则所述终端设备在收到第一配置消息时将第一计数器初始化为0。
再例如，如果该时间参考SFN为512，则终端设备在收到第一配置消息时的SFN为SFN周期的后半部分的情况下，将第一计数器初始化为0，在收到第一配置消息时的SFN为SFN周期的前半部分的情况下，将第一计数器初始化为1。
根据上述方法，能够实现网络侧和终端侧对第一计数器的同步。
在上述实施例中，由于网络侧和终端侧已经实现了对第一计数器的同步，则上述公式中的时间参考SFN可以省略。
例如，在终端设备确定启动非整数的DRX周期的唤醒期的时间时，如果为某个DRX组使用了短DRX周期，且非整数的短DRX周期被配置，且当前的第一计数器、SFN、子帧号满足如下公式：
floor([(第一计数器×10240)+(SFN×10)+子帧号]modulo(非整数的短DRX周期))＝floor((起始偏移量)modulo(非整数的短DRX周期))，
则终端设备为上述DRX组在上述子帧号对应的子帧开始之后的时隙偏移量时长之后开启唤醒定时器。
再例如，在终端设备确定启动非整数的DRX周期的唤醒期的时间时，如果为某个DRX组使用了长DRX周期，且非整数的长DRX周期被配置，且当前的第一计数器、SFN、子帧号满足如下公式：
floor([(第一计数器×10240)+(SFN×10)+子帧号]modulo(非整数的长DRX周期))＝起始偏移量，
则终端设备在没有为激活的下行带宽部分配置DCP监听的情况下，为上述DRX组在上述子帧号对应的子帧开始之后的时隙偏移量时长之后开启唤醒定时器。
在一些实施例中，上述起始偏移量的最大值被配置为对非整数的DRX周期进行向下取整得到的值减1。
在上述实施例中，非整数的DRX周期的唤醒期的时长可以比起始偏移量的最大值为其他值时对应的DRX周期的唤醒期的时长大。
在上述实施例中，当配置了非整数的DRX周期，且前一个DRX周期的实际周期长度等于对该非整数的DRX周期进行向下取整得到的值加1时，终端设备可以将当前的DRX周期的唤醒期延长。
在另外一些实施例中，上述起始偏移量的最大值被配置为对非整数的DRX周期进行向下取整得到的值。
在上述实施例中，如果从上一个唤醒期定时器开始的时间过了一个DRX周期的长度之后唤醒期定时器没有运行过，则终端设备启动唤醒定时器。
在前述各实施例中，非整数的DRX周期可以为非整数的长DRX周期，和/或，非整数的短DRX周期。
在一些实施例中，当非整数的长DRX周期被配置时，短DRX周期不被配置；或者，当非整数的短DRX周期被配置时，长DRX周期为整数。
在一些实施例中，如图9所示，该装置900还包括：
第二发送单元920，其向终端设备发送第二配置消息，所述第二配置消息配置了针对配置授权的禁用CG重传监听；所述第二配置消息包含第二信息单元，所述第二信息单元包括第六字段，所述第六字段指示了针对配置授权的禁用CG重传监听。
在上述实施例中，第二配置信息可以为RRCReconfiguration消息；第二信息单元可以为ConfiguredGrantConfig IE。
在上述实施例中，当第六字段被配置时，对配置授权中的所有配置上行授权都禁 止启动drx-HARQ-RTT-TimerUL定时器。
在上述实施例中，如果终端设备的服务小区没有被配置上行HARQ模式，且如果没有为配置的上行授权所属的多PUSCH CG配置所述第六字段，则：
如果配置了drx-LastTransmissionUL，则终端设备在对应的PUSCH传输的最后传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器；
反之，则终端设备在对应的PUSCH传输的第一个传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器。
本申请实施例还提供一种DRX的配置装置。
图10是本申请实施例的DRX的配置装置的一示意图，该装置例如可以是网络设备，也可以是配置于该网络设备中的某个或某些部件或者组件。由于该装置解决问题的原理与第二方面的实施例的图7所示的方法相同，因此其具体的实施可以参照第二方面的实施例的图7所示的方法的实施，内容相同之处不再重复说明。
如图10所示，该DRX的配置装置1000包括：
发送单元1010，其向终端设备发送第二配置消息，所述第二配置消息配置了针对配置授权的禁用CG重传监听；所述第二配置消息包含第二信息单元，所述第二信息单元包括第六字段，所述第六字段指示了针对配置授权的禁用CG重传监听。
在一些实施例中，第二配置信息为RRCReconfiguration消息；第二信息单元为ConfiguredGrantConfig IE。
在一些实施例中，当第六字段被配置时，对上述配置授权中的所有配置上行授权都禁止启动drx-HARQ-RTT-TimerUL定时器。
在一些实施例中，如果终端设备的服务小区没有被配置上行HARQ模式，且如果没有为配置的上行授权所属的多PUSCH CG配置所述第六字段，则：
如果配置了drx-LastTransmissionUL，则终端设备在对应的PUSCH传输的最后传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器；
反之，则终端设备在对应的PUSCH传输的第一个传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器。
本申请实施例还提供了一种DRX周期的确定装置。
图11是本申请实施例的DRX周期的确定装置的一示意图，该装置例如可以是终端设备，也可以是配置于该终端设备中的某个或某些部件或者组件。由于该装置解决 问题的原理与第一方面的实施例的图6所示的方法相同，并且与上述实施例的图9所示的装置对应，因此其具体的实施可以参照第一方面的实施例的图6所示的方法的实施以及上述实施例的图9所示的装置的实施，内容相同之处不再重复说明。
如图11所示，该DRX周期的确定装置1100包括：
接收单元1110，其接收网络设备发送的第一配置信息，该第一配置消息配置了由一个或多个分数表示的非整数的DRX周期；该第一配置信息包括第一信息单元，该第一信息单元包括指示非整数的长DRX周期及其起始偏移量和/或指示非整数的短DRX周期的字段。
在一些实施例中，如图11所示，该装置1100还包括：处理单元1120。
在一些实施例中，如前所述，如果第一字段被配置，则处理单元1120忽略整数的长DRX周期及其对应的起始偏移量的配置。
在一些实施例中，如前所述，在第三字段仅包括第二整数的情况下，处理单元1120可以将1000毫秒与所述第二整数的商作为分数表示的非整数的长DRX周期。
在一些实施例中，如前所述，如果第三字段被配置，则处理单元1120忽略整数的长DRX周期及其对应的起始偏移量的配置。
在一些实施例中，如图11所示，该装置1100还可以包括：
确定单元1130，其确定启动所述非整数的DRX周期的唤醒期的时间。关于确定该非整数的DRX周期的唤醒期的时间的方法，已经在前面做了说明，此处不再赘述。
在上述实施例中，如前所述，如果起始偏移量的最大值为对非整数的DRX周期进行向下取整得到的值减1，则如果从上一个唤醒期定时器开始的时间过了一个DRX周期的长度之后唤醒期定时器没有运行过，确定单元1130可以启动唤醒定时器。
本申请实施例还提供一种DRX配置的实施装置。
图12是本申请实施例的DRX配置的实施装置的一示意图，该装置例如可以是终端设备，也可以是配置于该终端设备中的某个或某些部件或者组件。由于该装置解决问题的原理与第二方面的实施例的图8所示的方法相同，并且与上述实施例的图10所示的装置对应，因此其具体的实施可以参照第二方面的实施例的图8所示的方法的实施以及上述实施例的图10所示的装置的实施，内容相同之处不再重复说明。
如图12所示，该DRX配置的实施装置1200包括：
接收单元1210，其接收网络设备发送的第二配置消息，所述第二配置消息配置 了针对配置授权的禁用CG重传监听；所述第二配置消息包含第二信息单元，所述第二信息单元包括第六字段，所述第六字段指示了针对配置授权的禁用CG重传监听。
在一些实施例中，如图12所示，该装置1200还可以包括：处理单元1220。
在一些实施例中，如前所述，如果终端设备的服务小区没有被配置上行HARQ模式，且如果没有为配置的上行授权所属的多PUSCH CG配置所述第六字段，则：
如果配置了drx-LastTransmissionUL，则处理单元1220在对应的PUSCH传输的最后传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器；
反之，则处理单元1220在对应的PUSCH传输的第一个传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的装置900、1000、1100、1200还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图9至图12中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
根据本申请实施例的装置，达到了UE节能的效果。
第四方面的实施例
本申请实施例提供一种通信系统，包括终端设备和网络设备，该网络设备被配置为执行第一方面或第二方面的实施例所述的方法。关于该网络设备的行为已经在第一方面至第三方面的实施例中做了详细说明，其内容被合并于此，此处不再赘述。
本申请实施例还提供了一种网络设备，该网络设备包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如第一方面的实施例中图3所述的方法或者第二方面的实施例中图7所述的方法。
图13是本申请实施例的网络设备的一示意图。如图13所示，网络设备1300可以包括：中央处理器(CPU)1310和存储器1320；存储器1320耦合到中央处理器1310。其中该存储器1320可存储各种数据；此外还存储信息处理的程序，并且在中央处理器1310的控制下执行该程序，以接收终端设备发送的各种信息、并且向终端 设备发送各种信息。
例如，处理器1310可以被配置为执行程序而实现如第一方面的实施例中图3所述的方法或第二方面的实施例中图7所述的方法。
此外，如图13所示，网络设备1300还可以包括：收发机1330和天线1340等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1300也并不是必须要包括图3中所示的所有部件；此外，网络设备1300还可以包括图13中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种终端设备，该终端设备包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如第一方面的实施例中图6所述的方法或者第二方面的实施例中图8所述的方法。
图14是本申请实施例的终端设备的一示意图。如图14所示，该终端设备1400可以包括处理器1410和存储器1420；存储器1420存储有数据和程序，并耦合到处理器1410。值得注意的是，该图是示例性的；还可以使用其它类型的结构，来补充或代替该结构，以实现电信功能或其它功能。
例如，处理器1410可以被配置为执行程序而实现如第一方面的实施例中图6所述的方法或者第二方面的实施例中图8所述的方法。
如图14所示，该终端设备1400还可以包括：通信模块1430、输入单元1440、显示器1450、电源1460。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1400也并不是必须要包括图14中所示的所有部件，上述部件并不是必需的；此外，终端设备1400还可以包括图14中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在网络设备中执行所述程序时，所述程序使得计算机在所述网络设备中执行第一方面的实施例的图3所述的方法或者第二方面的实施例的图7所述的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在网络设备中执行第一方面的实施例的图3所述的方法或者第二方面的实施例的图7所述的方法。
本申请实施例还提供一种计算机可读程序，其中当在终端设备中执行所述程序时，所述程序使得计算机在所终端设备中执行第一方面的实施例的图6所述的方法或第 二方面的实施例的图8所述的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在终端设备中执行第一方面的实施例的图6所述的方法或第二方面的实施例的图8所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
1.一种DRX周期的配置方法，其中，所述方法包括：
网络设备向终端设备发送第一配置消息，所述第一配置消息配置了由一个或多个分数表示的非整数的DRX周期；
所述第一配置信息包括第一信息单元，所述第一信息单元包括指示非整数的长DRX周期及其起始偏移量和/或指示非整数的短DRX周期的字段。
2.根据附记1所述的方法，其中，
所述第一信息单元还包括第五字段，所述第五字段包括与帧率对应的非整数的短DRX周期；
所述第五字段包括第三整数和第四整数；
所述第三整数为所述非整数的短DRX周期的分数表达形式中的分子，所述第四整数为所述非整数的短DRX周期的分数表达形式中的分母。
3.根据附记2所述的方法，其中，
所述第三整数和所述第四整数分别为枚举型；
所述第三整数的取值范围包含支持的非整数的短DRX周期的分数表达形式中的分子的固定值；
所述第四整数的取值范围包含支持的非整数的短DRX周期的分数表达形式中的分母的固定值。
4.根据附记1所述的方法，其中，
所述第一信息单元还包括第五字段，所述第五字段包括与帧率对应的非整数的短DRX周期；
所述第五字段包括第四整数；
所述第四整数表示非整数的短DRX周期，所述终端设备将1000毫秒与所述第四整数的商作为分数表示的非整数的短DRX周期。
5.根据附记1所述的方法，其中，
所述终端设备确定启动所述非整数的DRX周期的唤醒期的时间，其中，
如果为某个DRX组使用了短DRX周期，且非整数的短DRX周期被配置，且当前的第一计数器、系统帧号以及子帧号满足如下公式：
floor([(第一计数器×10240)+(系统帧号×10)+子帧号]modulo(非整数的短DRX周期))＝floor([(时间参考系统帧号×10)+起始偏移量)]modulo(非整数的短DRX周期))，
则终端设备为所述DRX组在所述子帧号对应的子帧开始之后的时隙偏移量时长之后开启唤醒定时器。
6.根据附记1所述的方法，其中，
所述终端设备确定启动所述非整数的DRX周期的唤醒期的时间，其中，
如果为某个DRX组使用了长DRX周期，且非整数的长DRX周期被配置，且当前的第一计数器、系统帧号以及子帧号满足如下公式：
floor([(第一计数器×10240)+(系统帧号×10)+子帧号]modulo(非整数的长DRX周期))＝floor([(时间参考系统帧号×10)+起始偏移量)]modulo(非整数的长DRX周期))，
则所述终端设备在没有为激活的下行带宽部分配置带有通过节能无线网临时标识加扰的循环冗余校验的下行控制信息(DCP)监听的情况下，为所述DRX组在所述子帧号对应的子帧开始之后的时隙偏移量时长之后开启唤醒定时器。
7.根据附记5或6所述的方法，其中，
所述公式中的A module B使用A-floor(A*N2/N1)*N1/N2来替代；
其中，B＝N1/N2，并且，按照所述A-floor(A*N2/N1)*N1/N2中的操作符的从左到右顺序来进行计算。
8.根据附记5或6所述的方法，其中，
各所述DRX组公用以下参数：非整数的长DRX周期，所述非整数的长DRX周期对应的起始偏移量，非整数的短DRX周期，以及时间参考帧号。
9.根据附记1所述的方法，其中，
当所述非整数的长DRX周期被配置时，短DRX周期不被配置；或者，当所述非整数的短DRX周期被配置时，长DRX周期为整数。
10.根据附记5或6所述的方法，其中，
所述终端设备在收到所述第一配置消息时将所述第一计数器初始化为0；所述终端设备在SFN变化为0时的时隙的第一个字符时间将所述第一计数器加1。

Claims (20)

  1. 一种DRX周期的配置装置，配置于网络设备，其中，所述装置包括：
    第一发送单元，其向终端设备发送第一配置消息，所述第一配置消息配置了由一个或多个分数表示的非整数的DRX周期；
    所述第一配置信息包括第一信息单元，所述第一信息单元包括指示非整数的长DRX周期及其起始偏移量和/或指示非整数的短DRX周期的字段。
  2. 根据权利要求1所述的装置，其中，
    所述第一信息单元为DRX-Config IE。
  3. 根据权利要求1所述的装置，其中，
    所述第一信息单元包括第一字段和第二字段；
    所述第一字段包括与帧率对应的非整数的长DRX周期和起始偏移量的组合；
    所述第二字段包括与帧率对应的非整数的短DRX周期。
  4. 根据权利要求3所述的装置，其中，
    所述第一字段为CHOICE结构，所述CHOICE结构中的每个元素为预定义的对应某帧率的非整数的长DRX周期和其对应的以毫秒为单位的起始偏移量的组合。
  5. 根据权利要求4所述的装置，其中，
    所述非整数的长DRX周期由以毫秒为单位的分数表达，所述分数由整数的分子和分母表达；
    每个非整数的长DRX周期对应的起始偏移量的取值范围是0到对所述非整数的长DRX周期向下取整的值。
  6. 根据权利要求4所述的装置，其中，
    如果所述第一字段被配置，则所述终端设备忽略整数的长DRX周期及其对应的起始偏移量的配置。
  7. 根据权利要求3所述的装置，其中，
    所述非整数的短DRX周期由以毫秒为单位的分数表达。
  8. 根据权利要求3所述的装置，其中，
    如果所述第二字段被配置，则所述第一字段中的非整数的长DRX周期的值为所述第二字段中的非整数的短DRX周期的值的整数倍；和/或，
    如果所述第二字段被配置，则所述终端设备忽略整数的短DRX周期的配置。
  9. 根据权利要求1所述的装置，其中，
    所述终端设备确定启动所述非整数的DRX周期的唤醒期的时间，其中，
    如果为某个DRX组使用了短DRX周期，且非整数的短DRX周期被配置，且当前的第一计数器、系统帧号以及子帧号满足如下公式：
    floor([(第一计数器×10240)+(系统帧号×10)+子帧号]modulo(非整数的短
    DRX周期))＝floor([(时间参考系统帧号×10)+起始偏移量)]modulo(非整数的短DRX周期))，
    则所述终端设备为所述DRX组在所述子帧号对应的子帧开始之后的时隙偏移量时长之后开启唤醒定时器。
  10. 根据权利要求9所述的装置，其中，
    所述第一配置消息包括时间参考系统帧号；所述终端设备根据所述时间参考系统帧号对所述第一计数器进行初始化；
    如果所述时间参考系统帧号为0，则所述终端设备在收到所述第一配置消息时将所述第一计数器初始化为0；
    如果所述时间参考系统帧号为512，则所述终端设备在收到所述第一配置消息时的SFN为SFN周期的后半部分的情况下，将所述第一计数器初始化为0，在收到所述第一配置消息时的SFN为SFN周期的前半部分的情况下，将所述第一计数器初始化为1。
  11. 根据权利要求10所述的装置，其中，
    所述公式变形为如下：
    floor([(第一计数器×10240)+(SFN×10)+子帧号]modulo(非整数的短DRX
    周期))＝floor((起始偏移量)modulo(非整数的短DRX周期))。
  12. 根据权利要求1所述的装置，其中，
    所述终端设备确定启动所述非整数的DRX周期的唤醒期的时间，其中，
    如果为某个DRX组使用了长DRX周期，且非整数的长DRX周期被配置，且当前的第一计数器、系统帧号以及子帧号满足如下公式：
    floor([(第一计数器×10240)+(系统帧号×10)+子帧号]modulo(非整数的长
    DRX周期))＝floor([(时间参考系统帧号×10)+起始偏移量)]modulo(非整数的长 DRX周期))，
    则所述终端设备在没有为激活的下行带宽部分配置带有通过节能无线网临时标识加扰的循环冗余校验的下行控制信息(DCP)监听的情况下，为所述DRX组在所述子帧号对应的子帧开始之后的时隙偏移量时长之后开启唤醒定时器。
  13. 根据权利要求12所述的装置，其中，
    所述第一配置消息包括时间参考系统帧号；所述终端设备根据所述时间参考系统帧号对所述第一计数器进行初始化；
    如果所述时间参考系统帧号为0，则所述终端设备在收到所述第一配置消息时将所述第一计数器初始化为0；
    如果所述时间参考系统帧号为512，则所述终端设备在收到所述第一配置消息时的SFN为SFN周期的后半部分的情况下，将所述第一计数器初始化为0，在收到所述第一配置消息时的SFN为SFN周期的前半部分的情况下，将所述第一计数器初始化为1。
  14. 根据权利要求13所述的装置，其中，
    所述公式变形为如下：
    floor([(第一计数器×10240)+(SFN×10)+子帧号]modulo(非整数的长DRX周
    期))＝起始偏移量。
  15. 根据权利要求12所述的装置，其中，
    各所述DRX组公用以下参数：非整数的长DRX周期，所述非整数的长DRX周期对应的起始偏移量，非整数的短DRX周期，以及时间参考帧号。
  16. 根据权利要求1所述的装置，其中，
    所述起始偏移量的最大值为对非整数的DRX周期进行向下取整得到的值减1。
  17. 根据权利要求16所述的装置，其中，
    如果从上一个唤醒期定时器开始的时间过了一个DRX周期的长度之后唤醒期定时器没有运行过，则所述终端设备启动唤醒定时器。
  18. 一种DRX周期的配置装置，配置于网络设备，其中，所述装置包括：
    发送单元，其向终端设备发送第二配置消息，所述第二配置消息配置了针对配置授权的禁用CG重传监听；
    所述第二配置消息包含第二信息单元，所述第二信息单元包括第六字段，所述第 六字段指示了针对配置授权的禁用CG重传监听。
  19. 根据权利要求18所述的装置，其中，
    所述第二配置信息为RRCReconfiguration消息；
    所述第二信息单元为ConfiguredGrantConfig IE。
  20. 根据权利要求18所述的装置，其中，
    如果所述终端设备的服务小区没有被配置上行HARQ模式，且如果没有为配置的上行授权所属的多PUSCH CG配置所述第六字段，则：
    如果配置了drx-LastTransmissionUL，则所述终端设备在对应的PUSCH传输的最后传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器；
    反之，则所述终端设备在对应的PUSCH传输的第一个传输之后的第一个符号为对应的HARQ进程启动drx-HARQ-RT-TimerUL定时器。
PCT/CN2023/129183 2023-09-28 2023-11-01 非连续接收周期的配置方法和装置 Pending WO2025065798A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202380102331.3A CN121909676A (zh) 2023-09-28 2023-11-01 非连续接收周期的配置方法和装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/122924 WO2025065631A1 (zh) 2023-09-28 2023-09-28 非连续接收周期的配置方法和装置
CNPCT/CN2023/122924 2023-09-28

Publications (1)

Publication Number Publication Date
WO2025065798A1 true WO2025065798A1 (zh) 2025-04-03

Family

ID=95204271

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2023/122924 Pending WO2025065631A1 (zh) 2023-09-28 2023-09-28 非连续接收周期的配置方法和装置
PCT/CN2023/129183 Pending WO2025065798A1 (zh) 2023-09-28 2023-11-01 非连续接收周期的配置方法和装置

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/122924 Pending WO2025065631A1 (zh) 2023-09-28 2023-09-28 非连续接收周期的配置方法和装置

Country Status (2)

Country Link
CN (1) CN121909676A (zh)
WO (2) WO2025065631A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021088015A1 (en) * 2019-11-08 2021-05-14 Nokia Shanghai Bell Co., Ltd. Discontinuous reception mechanism supporting blind retransmission
WO2022203264A1 (ko) * 2021-03-22 2022-09-29 삼성전자 주식회사 자동전송과 cg 재전송의 공존을 위한 방법 및 장치
CN115334696A (zh) * 2021-05-10 2022-11-11 华为技术有限公司 一种非连续接收的通信方法及装置
CN115515236A (zh) * 2021-06-07 2022-12-23 苹果公司 处置配置有非整数周期的新空口（nr）流量

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114451064A (zh) * 2019-10-09 2022-05-06 Oppo广东移动通信有限公司 非连续接收的方法、终端设备及存储介质
CN117397310A (zh) * 2021-07-21 2024-01-12 Oppo广东移动通信有限公司 一种drx配置方法及装置、终端设备、网络设备
WO2023008900A1 (ko) * 2021-07-27 2023-02-02 엘지전자 주식회사 무선 통신 시스템에서 무선 신호 송수신 방법 및 장치
US20240224376A1 (en) * 2021-09-24 2024-07-04 Apple Inc. Simultaneous drx configurations and harq timer enhancements for xr traffic
WO2023133691A1 (zh) * 2022-01-11 2023-07-20 Oppo广东移动通信有限公司 Drx配置方法、装置、设备及介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021088015A1 (en) * 2019-11-08 2021-05-14 Nokia Shanghai Bell Co., Ltd. Discontinuous reception mechanism supporting blind retransmission
WO2022203264A1 (ko) * 2021-03-22 2022-09-29 삼성전자 주식회사 자동전송과 cg 재전송의 공존을 위한 방법 및 장치
CN115334696A (zh) * 2021-05-10 2022-11-11 华为技术有限公司 一种非连续接收的通信方法及装置
CN115515236A (zh) * 2021-06-07 2022-12-23 苹果公司 处置配置有非整数周期的新空口（nr）流量

Also Published As

Publication number Publication date
WO2025065631A1 (zh) 2025-04-03
CN121909676A (zh) 2026-04-21

Similar Documents

Publication Publication Date Title
US20220303902A1 (en) User equipment involved in monitoring the downlink control channel
WO2023000201A1 (zh) 一种drx配置方法及装置、终端设备、网络设备
KR102240644B1 (ko) 데이터 전송/수신 장치 및 방법, 및 통신 시스템
US20240015840A1 (en) Method and apparatus for triggering a sidelink discontinuous reception command and system
WO2023217250A1 (en) Method for enabling wireless communication device to access services provided by radio access network and related devices
EP3689071B1 (en) Corresponding configuration for simultaneous physical uplink control channel pucch and physical uplink shared channel pusch transmission
WO2023226022A9 (en) Methods and apparatuses of a power saving mechanism for xr traffic
JP2024512055A (ja) データ送信方法、装置及びシステム
WO2024067107A1 (zh) 一种网络配置方法、装置及设备
EP4668842A1 (en) Data processing method and apparatus
WO2025065798A1 (zh) 非连续接收周期的配置方法和装置
WO2025065632A1 (zh) 一种信息发送、接收和处理方法、装置、通信系统
WO2023011240A1 (zh) 数据传输方法、装置、网络侧设备及终端
WO2024229846A1 (zh) 监听信道的方法、装置和通信系统
CN118975308A (zh) 无线通信方法及相关设备
JP7787994B2 (ja) 無線通信方法およびその装置
WO2025156296A1 (zh) 非连续接收周期的配置方法和装置
CN119014058B (zh) 无线通信方法、无线终端及无线网络节点
WO2025020164A1 (zh) 用于指示上行数据突发结束的方法和装置
WO2025065648A1 (zh) 未使用的传输时机的指示方法和装置
WO2025156115A1 (zh) 针对sdu丢弃的配置方法和装置
WO2024164312A1 (zh) 上行数据发送、上行数据接收装置以及方法
WO2023028784A1 (en) Methods and apparatuses for discontinuous reception (drx)
WO2025025213A1 (zh) 不被使用的发送时机的指示方法和装置
KR20260052171A (ko) 정보 송신, 수신, 및 처리 방법 및 장치, 및 통신 시스템

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23953933

Country of ref document: EP

Kind code of ref document: A1