Discontinuous reception (DRX) parameter determination methods, terminal and network device

Abstract

The present disclosure relates to discontinuous reception (DRX) parameter determination methods, a terminal, and a network device. A method comprises: the terminal sends first information. Thus, the problem of how terminals specifically report the expected discontinuous reception (DRX) can be solved to a certain extent.

Description

Method for determining DRX parameters for discontinuous reception, terminal, and network equipment Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method for determining discontinuous reception (DRX) parameters, a terminal, and a network device. Background Art

[0002] In the field of communication technology, a discontinuous reception (DRX) mechanism has been introduced. Currently, a user equipment (UE) can report its desired DRX parameters.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a method for determining DRX parameters for discontinuous reception, a terminal, and a network device, which to a certain extent solve the problem of how to report DRX parameters in a UE.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for determining a discontinuous reception (DRX) parameter is provided, which is executed by a terminal. The method includes:

[0006] Sending first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0007] According to a second aspect of an embodiment of the present disclosure, a method for determining a discontinuous reception (DRX) parameter is provided, which is performed by a network device. The method includes:

[0008] Receive first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0009] According to a third aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0010] A transceiver module is used to receive first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0011] According to a fourth aspect of an embodiment of the present disclosure, a network device is provided, including:

[0012] A transceiver module is used to receive first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0013] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0014] one or more processors;

[0015] The processor is used to call instructions to enable the communication device to execute the processing method described in any one of the first aspect and the second aspect.

[0016] According to the sixth aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a terminal and a network device, wherein the terminal is configured to implement the method for determining the discontinuous reception DRX parameters described in the first aspect, and the network device is configured to implement the method for determining the discontinuous reception DRX parameters described in the second aspect.

[0017] According to the seventh aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes the method for determining discontinuous reception DRX parameters as described in any one of the first and second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0019] FIG1A is a schematic diagram illustrating an architecture of a communication system according to an embodiment of the present disclosure;

[0020] FIG1B is a schematic diagram of a discontinuous reception (DRX) mechanism according to an embodiment of the present disclosure;

[0021] 2A-2B are interactive diagrams illustrating a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure;

[0022] 3A-3E are flowcharts of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure;

[0023] 4A-4C are flowcharts of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure;

[0024] FIG5A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure;

[0025] FIG5B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure;

[0026] FIG6A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0027] FIG6B is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] The embodiments of the present disclosure provide a method for determining DRX parameters, a terminal, and a network device.

[0029] In a first aspect, an embodiment of the present disclosure provides a method for determining a discontinuous reception (DRX) parameter, which is performed by a terminal. The method includes:

[0030] Sending first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0031] In the above embodiment, the terminal reports the expected first type of DRX cycle and / or second type of DRX cycle by sending the first information to the network device, so that the network device's understanding of the terminal's expected DRX cycle is consistent with the terminal's understanding, thereby improving the accuracy and efficiency of determining the expected DRX parameters.

[0032] In combination with some embodiments of the first aspect, in some embodiments, the expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, and the expected long cycle is X times the expected short cycle, where X is an integer.

[0033] In the above embodiment, the transmission delay between the terminal and the network device is reduced by reporting the expected long period and the expected short period that have a multiple relationship.

[0034] With reference to some embodiments of the first aspect, in some embodiments, the expected long cycle and the expected short cycle are both DRX cycles of the second type;

[0035] or,

[0036] The expected long cycle and the expected short cycle are both DRX cycles of the first type;

[0037] or,

[0038] The desired long cycle is a first type of DRX cycle, and the desired short cycle is a second type of DRX cycle;

[0039] The first type of DRX cycle is an integer cycle.

[0040] In the above embodiment, the terminal improves the flexibility of reporting the DRX cycle by reporting long cycles and short cycles of the same or different types, thereby providing conditions for further reducing transmission delay and ensuring accuracy and reliability of data transmission.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0042] receiving second information, where the second information is used to configure a DRX cycle;

[0043] According to the configured DRX cycle, a type of the expected DRX cycle reported in the first information is determined.

[0044] In the above embodiment, the type of the expected DRX cycle reported in the first information is determined based on the second information of the network device, thereby reducing the amount of resources occupied by the terminal when reporting the expected DRX cycle and improving the transmission efficiency of the communication system.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, determining, according to the configured DRX cycle, the type of the expected DRX cycle reported in the first information includes:

[0046] The configured DRX cycle is a first type of DRX cycle, and determining that the expected DRX cycle reported in the first information is a first type of DRX cycle; or,

[0047] The configured DRX cycle is a second type of DRX cycle, and it is determined that the expected DRX cycle reported in the first information is a second type of DRX cycle.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0049] receiving third information, where the third information is used to indicate a reported desired DRX cycle type;

[0050] Determine, according to the third information, the type of the expected DRX cycle reported in the first information.

[0051] In the above embodiment, the terminal reports only the DRX cycle of the DRX cycle type indicated by the network device in the first information, thereby reducing the amount of resources occupied by the terminal when reporting the desired DRX cycle and improving the transmission efficiency of the communication system.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the expected DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, and the second type of DRX cycle and the first type of DRX cycle are associated with the same prohibition timer.

[0053] In the above embodiment, by associating the second type of DRX cycle and the first type of DRX cycle with the same prohibition timer, the reporting of two types of DRX cycles can be achieved through one message, thereby reducing the amount of resources when the terminal reports different types of expected DRX cycles and improving the transmission efficiency of the communication system.

[0054] In a second aspect, an embodiment of the present disclosure provides a method for determining a discontinuous reception (DRX) parameter, which is performed by a network device. The method includes:

[0055] Receive first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0056] In combination with some embodiments of the second aspect, in some embodiments, the expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, and the expected long cycle is X times the expected short cycle, where X is an integer.

[0057] With reference to some embodiments of the second aspect, in some embodiments, the expected long cycle and the expected short cycle are both DRX cycles of the second type;

[0058] or,

[0059] The expected long cycle and the expected short cycle are both DRX cycles of the first type;

[0060] or,

[0061] The desired long cycle is a first type of DRX cycle, and the desired short cycle is a second type of DRX cycle;

[0062] The first type of DRX cycle is an integer cycle.

[0063] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0064] Send second information, where the second information is used to configure a DRX cycle.

[0065] In combination with some embodiments of the second aspect, in some embodiments, the configured DRX cycle is a first type of DRX cycle, and the expected DRX cycle reported in the first information is a first type of DRX cycle; or,

[0066] The configured DRX cycle is a second type of DRX cycle, and the expected DRX cycle reported in the first information is a second type of DRX cycle.

[0067] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0068] Send third information, where the third information is used to indicate the type of the reported expected DRX cycle.

[0069] In combination with some embodiments of the second aspect, in some embodiments, the expected DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, and the second type of DRX cycle and the first type of DRX cycle are associated with the same prohibition timer.

[0070] In a third aspect, an embodiment of the present disclosure provides a terminal, comprising:

[0071] A transceiver module is used to receive first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0072] In combination with some embodiments of the third aspect, in some embodiments, the expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, and the expected long cycle is X times the expected short cycle, where X is an integer.

[0073] With reference to some embodiments of the third aspect, in some embodiments, the expected long cycle and the expected short cycle are both second-type DRX cycles;

[0074] or,

[0075] The expected long cycle and the expected short cycle are both DRX cycles of the first type;

[0076] or,

[0077] The desired long cycle is a first type of DRX cycle, and the desired short cycle is a second type of DRX cycle;

[0078] The first type of DRX cycle is an integer cycle.

[0079] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0080] The transceiver module is configured to receive second information, wherein the second information is used to configure a DRX cycle;

[0081] A processing module is used to determine the type of the expected DRX cycle reported in the first information according to the configured DRX cycle.

[0082] In conjunction with some embodiments of the third aspect, in some embodiments, the processing module is further configured to:

[0083] The configured DRX cycle is a first type of DRX cycle, and determining that the expected DRX cycle reported in the first information is a first type of DRX cycle; or,

[0084] The configured DRX cycle is a second type of DRX cycle, and it is determined that the expected DRX cycle reported in the first information is a second type of DRX cycle.

[0085] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0086] The transceiver module is configured to receive third information, wherein the third information is used to indicate a type of a reported expected DRX cycle;

[0087] The processing module is configured to determine, based on the third information, a type of the expected DRX cycle reported in the first information.

[0088] In combination with some embodiments of the third aspect, in some embodiments, the expected DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, and the second type of DRX cycle and the first type of DRX cycle are associated with the same prohibition timer.

[0089] In a fourth aspect, an embodiment of the present disclosure provides a network device, wherein the network device includes:

[0090] A transceiver module is used to receive first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0091] In combination with some embodiments of the fourth aspect, in some embodiments, the expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, and the expected long cycle is X times the expected short cycle, where X is an integer.

[0092] With reference to some embodiments of the fourth aspect, in some embodiments, the expected long cycle and the expected short cycle are both second-type DRX cycles;

[0093] or,

[0094] The expected long cycle and the expected short cycle are both DRX cycles of the first type;

[0095] or,

[0096] The desired long cycle is a first type of DRX cycle, and the desired short cycle is a second type of DRX cycle;

[0097] The first type of DRX cycle is an integer cycle.

[0098] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to:

[0099] Send second information, where the second information is used to configure a DRX cycle.

[0100] In conjunction with some embodiments of the fourth aspect, in some embodiments, the configured DRX cycle is a first type of DRX cycle, and the expected DRX cycle reported in the first information is a first type of DRX cycle; or,

[0101] The configured DRX cycle is a second type of DRX cycle, and the expected DRX cycle reported in the first information is a second type of DRX cycle.

[0102] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to:

[0103] Send third information, where the third information is used to indicate the type of the reported expected DRX cycle.

[0104] In combination with some embodiments of the fourth aspect, in some embodiments, the expected DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, and the second type of DRX cycle and the first type of DRX cycle are associated with the same prohibition timer.

[0105] In a fifth aspect, an embodiment of the present disclosure proposes a terminal, which includes: one or more processors; wherein the processors are used to execute an optional implementation of the method for determining discontinuous reception DRX parameters proposed in the first aspect.

[0106] In a sixth aspect, an embodiment of the present disclosure proposes a network device, which includes: one or more processors; wherein the processors are used to execute an optional implementation of the method for determining discontinuous reception DRX parameters proposed in the second aspect.

[0107] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the method described in the optional implementation manner of the first aspect, and the network device is configured to execute the method described in the optional implementation manner of the second aspect.

[0108] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0109] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0110] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0111] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0112] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0113] The present disclosure provides a method for determining DRX parameters for discontinuous reception. In some embodiments, the terms "method for determining DRX parameters for discontinuous reception," "measurement configuration method," "configuration method," and "communication method" are interchangeable; the terms "device for determining DRX parameters for discontinuous reception," "measurement configuration device," and "communication device" are interchangeable; and the terms "system for determining DRX parameters for discontinuous reception," "measurement configuration system," and "communication system" are interchangeable.

[0114] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0115] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0116] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0117] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0118] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0119] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0120] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0121] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0122] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0123] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0124] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0125] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0126] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0127] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0128] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macrocell", "smallcell", "femtocell", "picocell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0129] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station (subscriber station), mobile unit (mobile unit), subscriber unit (subscribe runit), wireless unit (wireless unit), remote unit (remote unit), mobile device (mobile device), wireless device (wireless device), wireless communication device (wireless communication device), remote device (remoted device), mobile subscriber station (mobile subscriber station), access terminal (access terminal), mobile terminal (mobile terminal), wireless terminal (wireless terminal), remote terminal (remote terminal), handset (handset), user agent (user agent), mobile client (mobile client), client (client), etc.

[0130] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0131] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0132] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0133] As shown in FIG. 1A , a communication system 1100 includes a terminal 1101 and a network device 1102 .

[0134] In some embodiments, the terminal 1101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0135] In some embodiments, the network device 1102 may include at least one of an access network device and a core network device.

[0136] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0137] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0138] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0139] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0140] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0141] The following embodiments of the present disclosure may be applied to the communication system 1100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary. The entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0142] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi (registered trademark)), IEEE802.16 (WiMAX (registered trademark)), IEEE802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine-to-Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, and next-generation systems based on these methods. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A with 5G, etc.) for application.

[0143] In 5G systems, a discontinuous reception (DRX) mechanism is introduced to save UE power. This mechanism requires that when in connected state, the UE does not continuously monitor the control channel sent by the gNB, but instead monitors the control channel intermittently. Figure 1B is a schematic diagram of the DRX mechanism, shown in an embodiment of the present disclosure. The "On Duration" represents the time period during which the UE monitors the control channel, during which the RF channel is open and continuously monitors the control channel. During other times outside the "On Duration," the UE is in a power-saving state, with its RF link shut down. The "On Duration" occurs periodically, with the specific period configured by the gNB. To achieve UE power savings while minimizing transmission latency between the gNB and the UE, the concepts of long cycles and short cycles are introduced. During these cycles, the UE enters an inactive state and does not continuously monitor the gNB's control channel. In a short cycle, "On Duration" occurs more frequently than in a long cycle. If the UE is configured with both a long and short cycle, after the short cycle is started and the short cycle timer (drx-ShortCycleTimer) times out, the UE will monitor according to the long cycle.

[0144] For the UE, currently the UE can report its desired DRX parameters, that is, it can report both DRX parameters of integer cycles and DRX parameters of non-integer cycles.

[0145] FIG2A is an interactive diagram illustrating a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG2A , an embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, the method comprising:

[0146] Step S2101 , the network device 1102 sends second information to the terminal 1101 .

[0147] In some embodiments, the second information is used to configure a DRX cycle.

[0148] In some embodiments, terms such as "DRX", "Discontinuous Reception", and "Discontinuous Reception" can be used interchangeably.

[0149] In some embodiments, when the DRX cycle configured by the network device 1102 to the terminal 1101 is a first type of DRX cycle, the expected DRX cycle reported in the first information may be the first type of DRX cycle.

[0150] In some embodiments, the first type of DRX cycle is an integer DRX cycle, for example, the first type of DRX cycle can be any integer DRX cycle such as 30 milliseconds, 80 milliseconds, 256 milliseconds, or 1024 milliseconds, which is not limited in the present disclosure.

[0151] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0152] In some embodiments, the expected DRX cycle is used to represent the DRX cycle reported by the terminal 1101.

[0153] In some embodiments, when the DRX cycle configured by the network device 1102 to the terminal 1101 is a second-type DRX cycle, the expected DRX cycle reported in the first information may be a second-type DRX cycle.

[0154] In some embodiments, the second type of DRX cycle is a non-integer DRX cycle. For example, the second type of DRX cycle can be any non-integer DRX cycle such as 50 / 3 milliseconds, 200 / 9 milliseconds, 400 / 3 milliseconds, or 125 / 9 milliseconds, which is not limited in this disclosure.

[0155] In some embodiments, when the DRX cycle configured by the network device 1102 to the terminal 1101 includes a first type of DRX cycle and a second type of DRX cycle, the expected DRX cycle reported in the first information may include a first type of DRX cycle and a second type of DRX cycle. At this time, the second type of DRX cycle reported in the first information and the first type of DRX cycle are associated with the same prohibition timer.

[0156] In some embodiments, when the network device 1102 configures the first type of DRX cycle and the second type of DRX cycle to the terminal 1101 at the same time, when the expectations reported in the first information include the first type of DRX cycle and the second type of DRX cycle, since different types of DRX cycles cannot be reported at the same time, at this time, the two types of DRX cycles reported in the first information can be associated with the prohibition timer. When the first DRX cycle is reported, the prohibition timer is started. After the prohibition timer times out, the second DRX cycle is reported.

[0157] In some embodiments, terminal 1101 receives second information sent by network device 1102 .

[0158] Step S2102: When the configured DRX cycle is a first type of DRX cycle, the terminal 1101 determines that the expected DRX cycle reported in the first information is a first type of DRX cycle.

[0159] In some embodiments, when the DRX cycle configured by the network device 1102 to the terminal 1101 is a first type of DRX cycle, the terminal 1101 may determine that the expected DRX cycle reported in the first information is the first type of DRX cycle.

[0160] Step S2103: When the configured DRX cycle is the second type of DRX cycle, the terminal 1101 determines that the expected DRX cycle reported in the first information is the second type of DRX cycle.

[0161] In some embodiments, when the DRX cycle configured by the network device 1102 to the terminal 1101 is the second type of DRX cycle, the terminal 1101 may determine that the expected DRX cycle reported in the first information is the second type of DRX cycle.

[0162] After step S2101, step S2102 or step S2103 may be performed. When the configured DRX cycle is a first type DRX cycle, step S2102 may be performed, and when the configured DRX cycle is a second type DRX cycle, step S2103 may be performed.

[0163] Step S2104 , terminal 1101 sends first information to network device 1102 .

[0164] In some embodiments, after determining the type of the desired DRX cycle reported in the first information, the terminal 1101 may send the first information to the network device 1102 .

[0165] In some embodiments, after determining the type of the expected DRX cycle reported in the first information, the terminal 1101 may select the expected DRX cycle to be reported from the DRX cycle parameters configured by the network device 1102 for reporting.

[0166] In some embodiments, the desired DRX cycle may include at least one of the following: a desired long cycle, a desired short cycle, and the desired long cycle is X times the desired short cycle, where X is an integer.

[0167] In some embodiments, the name of the desired long cycle is not limited, and it can be, for example, "preferredDRX-LongCycle".

[0168] In some embodiments, the name of the desired short cycle is not limited, and it can be, for example, "preferredDRX-ShortCycle" or the like.

[0169] In some embodiments, when terminal 1101 reports a desired DRX cycle, if the reported desired DRX cycle includes a desired long cycle and a desired short cycle, then the desired long cycle is an integer multiple of the desired short cycle. For example, if the desired short cycle is 30 milliseconds, the desired long cycle may be 300 milliseconds, which is 10 times the desired short cycle.

[0170] In some embodiments, when the DRX cycle configured by the network device 1102 for the terminal 1101 is the second type of DRX cycle, it can be determined that the expected long cycle and / or the expected short cycle reported in the first information are both the second type of DRX cycle.

[0171] For example, the second type of DRX cycle parameters configured by the network device 1102 to the terminal 1101 are: 50 / 3 milliseconds, 200 / 9 milliseconds, 400 / 3 milliseconds, and 125 / 9 milliseconds. The short DRX cycle expected by the terminal 1101 is 50 / 3 milliseconds, and the long DRX cycle expected by the terminal 1101 is 400 / 3 milliseconds. At this time, the expected DRX cycles that the terminal 1101 can report through the first information are 50 / 3 milliseconds and 400 / 3 milliseconds.

[0172] In some embodiments, when the DRX cycle configured by the network device 1102 to the terminal 1101 is a second type of DRX cycle, since the expected DRX cycle reported in the first information determined by the terminal 1101 may include an expected long cycle and an expected short cycle, and the expected long cycle reported by the terminal 1101 is an integer multiple of the expected short cycle, when the DRX cycle configured by the network device 1102 to the terminal 1101 is a second type of DRX cycle, the expected long cycle reported in the first information determined by the terminal 1101 may be the first type of DRX cycle, and the reported expected short cycle may be the second type of DRX cycle.

[0173] For example, the second type of DRX cycle parameters configured by network device 1102 to terminal 1101 are: 50 / 3 milliseconds, 200 / 9 milliseconds, 400 / 3 milliseconds, 125 / 9 milliseconds, and 600 / 3 milliseconds. Terminal 1101 expects a short cycle of 50 / 3 milliseconds, and an expected long cycle of 600 / 3 milliseconds, i.e., 200 milliseconds. In this case, terminal 1101 can report the expected DRX cycles of 50 / 3 milliseconds and 200 milliseconds through the first information. The expected DRX cycles reported by terminal 1101 include the first type DRX cycle of 200 milliseconds and the second type DRX cycle of 50 / 3 milliseconds. The terminal can first report the expected short cycle of 50 / 3 milliseconds and simultaneously start a prohibition timer. When the prohibition timer times out, the terminal can continue to report the expected long cycle of 200 milliseconds.

[0174] In some embodiments, when the DRX cycle configured by network device 1102 to terminal 1101 is a first type of DRX cycle, terminal 1101 can determine that the expected long cycle and / or expected short cycle reported in the first information are both first type of DRX cycles, and then terminal 1101 can send the first information to network device 1102.

[0175] For example, the first type of DRX cycle parameters configured by network device 1102 to terminal 1101 are: 30 milliseconds, 80 milliseconds, 256 milliseconds, and 1024 milliseconds. The DRX cycle expected by terminal 1101 is 256 milliseconds. At this time, terminal 1101 can report the expected DRX cycle of 256 milliseconds through the first information.

[0176] In some embodiments, the network device 1102 receives the first information sent by the terminal 1101 .

[0177] The method for determining DRX parameters for discontinuous reception involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2104. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, and steps S2101+S2103 may be implemented as independent embodiments, but are not limited thereto.

[0178] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0179] In this embodiment, the network device first configures the DRX cycle for the terminal, and then the terminal determines and reports the expected DRX cycle based on the configured DRX cycle, so that the network device's understanding of the terminal's expected DRX cycle is consistent with that of the terminal, thereby improving the accuracy and efficiency of determining the expected DRX parameters.

[0180] FIG2B is an interactive diagram illustrating a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG2B , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, the method comprising:

[0181] Step S2201 , the network device 1102 sends second information to the terminal 1101 .

[0182] For a detailed introduction to step S2201, please refer to the above step S2101.

[0183] Step S2202 , the network device 1102 sends third information to the terminal 1101 .

[0184] In some embodiments, the third information is used to indicate the type of the reported desired DRX cycle.

[0185] In some embodiments, when the network device 1102 configures the first type of DRX cycle and the second type of DRX cycle for the terminal 1101, the network device 1102 may send third information to the terminal 1101 to indicate the type of desired DRX to be reported by the terminal 1101.

[0186] In some embodiments, based on protocol agreement, when the terminal 1101 optionally expects a DRX cycle including a first type of DRX cycle and a second type of DRX cycle, the network device 1102 may indicate the type of expected DRX to be reported by the terminal 1101 by sending a third information to the terminal 1101.

[0187] In some embodiments, the terminal 1101 receives third information sent by the network device 1102 .

[0188] In step S2203, the terminal 1101 determines the type of the expected DRX cycle reported in the first information according to the third information.

[0189] In some embodiments, after receiving the third information sent by the network device 1102 , the terminal 1101 may determine the type of the desired DRX cycle reported in the first information based on the third information.

[0190] For example, when the third information sent by network device 1102 to terminal 1101 indicates that the type of the expected DRX cycle reported by terminal 1101 is the first type, terminal 1101 can determine that the type of the expected DRX cycle reported in the first information is the first type based on the third information.

[0191] Step S2204 , the terminal 1101 sends the first information to the network device 1102 .

[0192] For a detailed description of step S2204, please refer to the above step S2104.

[0193] The method for determining DRX parameters for discontinuous reception involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2204. For example, step S2201 may be implemented as an independent embodiment, step S2202 may be implemented as an independent embodiment, and steps S2201+S2203 may be implemented as independent embodiments, but are not limited thereto.

[0194] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0195] In this embodiment, based on the indication of the expected DRX cycle to be reported sent by the network device, the terminal only determines and reports the DRX cycle of the DRX cycle type indicated by the network device, thereby reducing the amount of resources occupied by the terminal when reporting the expected DRX cycle and improving the transmission efficiency of the communication system.

[0196] FIG3A is a flow chart of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, which is used for terminal 1101. The method includes:

[0197] Step S3101, receiving the second information sent by the network device 1102.

[0198] In some embodiments, the second information is used to configure a DRX cycle.

[0199] In some embodiments, terminal 1101 receives second information sent by network device 1102 .

[0200] Step S3102: When the configured DRX cycle is a first type of DRX cycle, determine that the expected DRX cycle reported in the first information is a first type of DRX cycle.

[0201] Step S3103: When the configured DRX cycle is the second type of DRX cycle, determine that the expected DRX cycle reported in the first information is the second type of DRX cycle.

[0202] Step S3104: Send first information to network device 1102.

[0203] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0204] In some embodiments, terminal 1101 sends first information to network device 1102 .

[0205] For a detailed description of steps S3101 - S3104 , please refer to steps S2101 - S2104 in the embodiment shown in FIG2A , which will not be repeated here.

[0206] The method for determining DRX parameters involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3104. For example, steps S3101+S3102 may be implemented as independent embodiments, and step S3103 may be implemented as an independent embodiment, etc., but is not limited thereto.

[0207] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0208] In this embodiment, the terminal determines the type of the expected DRX cycle to be reported based on the DRX cycle configured by the network device, and reports the expected DRX cycle, thereby improving the transmission efficiency of the communication system.

[0209] FIG3B is a flow chart of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, which is used for terminal 1101 and includes:

[0210] Step S3201: Receive the second information sent by the network device 1102.

[0211] In some embodiments, the second information is used to configure a DRX cycle.

[0212] In some embodiments, terminal 1101 receives second information sent by network device 1102 .

[0213] Step S3202, receiving the third information sent by the network device 1102.

[0214] In some embodiments, the third information is used to indicate the type of the reported desired DRX cycle.

[0215] In some embodiments, the terminal 1101 receives third information sent by the network device 1102 .

[0216] Step S3203: Determine the type of the expected DRX cycle reported in the first information according to the third information.

[0217] Step S3204: Send first information to the network device 1102.

[0218] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0219] In some embodiments, terminal 1101 sends first information to network device 1102 .

[0220] For a detailed description of steps S3201 to S3204, reference may be made to steps S2201 to S2204 in the embodiment shown in FIG2B , which will not be repeated here.

[0221] The method for determining DRX parameters for discontinuous reception involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3204. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, and steps S3201+S3202 may be implemented as independent embodiments, but are not limited thereto.

[0222] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0223] In this embodiment, the terminal reports only the DRX cycle of the DRX cycle type indicated by the network device in the first information, thereby reducing the amount of resources occupied by the terminal when reporting the desired DRX cycle and improving the transmission efficiency of the communication system.

[0224] FIG3C is a flow chart of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, which is used for terminal 1101. The method includes:

[0225] Step S3301, receiving the second information sent by the network device 1102.

[0226] In some embodiments, the second information is used to configure a DRX cycle.

[0227] In some embodiments, terminal 1101 receives second information sent by network device 1102 .

[0228] Step S3302: When the configured DRX cycle is a first type of DRX cycle, determine that the expected DRX cycle reported in the first information is a first type of DRX cycle.

[0229] For a detailed description of steps S3301-S3302, please refer to steps S2101-S2102 in the embodiment shown in FIG2A, which will not be repeated here.

[0230] Step S3303: Send first information to network device 1102.

[0231] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0232] In some embodiments, terminal 1101 sends first information to network device 1102 .

[0233] For a detailed description of step S3303, please refer to step S2104 in the embodiment shown in FIG2A , which will not be repeated here.

[0234] The method for determining DRX parameters involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3303. For example, steps S3301+S3302 may be implemented as independent embodiments, and step S3303 may be implemented as an independent embodiment, etc., but is not limited thereto.

[0235] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0236] In this embodiment, when the DRX cycle configured by the network device is a first type of DRX cycle, the terminal reports the first type of DRX cycle in the first information, thereby improving the accuracy and efficiency of determining the expected DRX parameters.

[0237] FIG3D is a flow chart of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, which is used for terminal 1101. The method includes:

[0238] Step S3401: Receive the second information sent by the network device 1102.

[0239] In some embodiments, the second information is used to configure a DRX cycle.

[0240] In some embodiments, terminal 1101 receives second information sent by network device 1102 .

[0241] For a detailed description of step S3401, please refer to step S2101 in the embodiment shown in FIG2A , which will not be repeated here.

[0242] Step S3402: When the configured DRX cycle is the second type of DRX cycle, determine that the expected DRX cycle reported in the first information is the second type of DRX cycle.

[0243] Step S3403: Send first information to the network device 1102.

[0244] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0245] In some embodiments, terminal 1101 sends first information to network device 1102 .

[0246] For a detailed description of steps S3402-S3403, please refer to steps S2103-S2104 in the embodiment shown in FIG2A, which will not be repeated here.

[0247] The method for determining DRX parameters involved in the embodiments of the present disclosure may include at least one of steps S3401 to S3403. For example, steps S3401+S3402 may be implemented as independent embodiments, and step S3403 may be implemented as an independent embodiment, etc., but is not limited thereto.

[0248] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0249] In this embodiment, when the DRX cycle configured by the network device is the second type of DRX cycle, the terminal reports the second type of DRX cycle in the first information, thereby improving the accuracy and efficiency of determining the expected DRX parameters.

[0250] FIG3E is a flow chart of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG3E , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, which is used for terminal 1101 and includes:

[0251] Step S3501: Send first information to the network device 1102.

[0252] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0253] In some embodiments, terminal 1101 sends first information to network device 1102 .

[0254] In some embodiments, the desired DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0255] In some embodiments, the desired DRX cycle includes at least one of the following: a desired long cycle, a desired short cycle, and the desired long cycle is X times the desired short cycle, where X is an integer.

[0256] In some embodiments, the desired long cycle and the desired short cycle are both DRX cycles of the second type;

[0257] or,

[0258] The expected long cycle and the expected short cycle are both first-type DRX cycles;

[0259] or,

[0260] The desired long cycle is a first type of DRX cycle, and the desired short cycle is a second type of DRX cycle;

[0261] The first type of DRX cycle is an integer cycle.

[0262] In some embodiments, the method further comprises:

[0263] receiving second information, where the second information is used to configure a DRX cycle;

[0264] According to the configured DRX cycle, the type of the expected DRX cycle reported in the first information is determined.

[0265] In some embodiments, determining, based on the configured DRX cycle, the type of the expected DRX cycle reported in the first information includes:

[0266] The configured DRX cycle is a first type of DRX cycle, and the expected DRX cycle reported in the first information is determined to be the first type of DRX cycle; or,

[0267] The configured DRX cycle is a second type of DRX cycle, and it is determined that the expected DRX cycle reported in the first information is a second type of DRX cycle.

[0268] In some embodiments, the method further comprises:

[0269] receiving third information, where the third information is used to indicate a reported desired DRX cycle type;

[0270] The type of the expected DRX cycle reported in the first information is determined according to the third information.

[0271] In some embodiments, the desired DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, the second type of DRX cycle being associated with the same inhibit timer as the first type of DRX cycle.

[0272] For a detailed description of step S3501, please refer to the above embodiment description, which will not be repeated here.

[0273] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0274] In this embodiment, the terminal reports the expected first type of DRX cycle and / or second type of DRX cycle by sending the first information to the network device, so that the network device's understanding of the terminal's expected DRX cycle is consistent with the terminal's understanding, thereby improving the accuracy and efficiency of determining the expected DRX parameters.

[0275] FIG4A is a flow chart of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, which is used in a network device 1102 and includes:

[0276] Step S4101, sending second information to terminal 1101.

[0277] In some embodiments, the second information is used to configure a DRX cycle.

[0278] In some embodiments, the network device 1102 sends second information to the terminal 1101 .

[0279] For a detailed description of step S4101, please refer to step S2101 in the embodiment shown in FIG2A , which will not be repeated here.

[0280] Step S4102: Receive the first information sent by terminal 1101.

[0281] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0282] In some embodiments, the network device 1102 receives the first information sent by the terminal 1101 .

[0283] For a detailed description of step S4102, please refer to step S2104 in the embodiment shown in FIG2A, which will not be repeated here.

[0284] The method for determining DRX parameters for discontinuous reception involved in the embodiments of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, and steps S4101+S4102 may be implemented as independent embodiments, but are not limited thereto.

[0285] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0286] In this embodiment, the network device configures the DRX cycle for the terminal and then receives the expected DRX cycle reported by the terminal, thereby providing conditions for improving the efficiency of the terminal in determining the expected DRX cycle and improving the transmission efficiency of the communication system.

[0287] FIG4B is a flow chart of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, which is used in a network device 1102 and includes:

[0288] Step S4201: Send second information to terminal 1101.

[0289] In some embodiments, the second information is used to configure a DRX cycle.

[0290] In some embodiments, the network device 1102 sends second information to the terminal 1101 .

[0291] For a detailed description of step S4201, please refer to step S2201 in the embodiment shown in FIG2B , which will not be repeated here.

[0292] Step S4202: Send third information to terminal 1101.

[0293] In some embodiments, the third information is used to indicate the type of the reported desired DRX cycle.

[0294] In some embodiments, the network device 1102 sends third information to the terminal 1101 .

[0295] For a detailed description of step S4202, please refer to step S2202 in the embodiment shown in FIG2B , which will not be repeated here.

[0296] Step S4203: Receive the first information sent by terminal 1101.

[0297] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0298] In some embodiments, the network device 1102 receives the first information sent by the terminal 1101 .

[0299] For a detailed description of step S4203, please refer to step S2204 in the embodiment shown in FIG2B , which will not be repeated here.

[0300] The method for determining DRX parameters for discontinuous reception involved in the embodiments of the present disclosure may include at least one of steps S4201 to S4203. For example, step S4201 may be implemented as an independent embodiment, step S4202 may be implemented as an independent embodiment, and steps S4201+S4202 may be implemented as independent embodiments, but are not limited thereto.

[0301] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0302] In this embodiment, the network device configures the DRX cycle for the terminal and indicates the type of the expected DRX cycle reported by the terminal, and then receives the expected DRX cycle reported by the terminal, thereby reducing the amount of resources occupied by the terminal when reporting the expected DRX cycle and ensuring the accuracy and reliability of data transmission.

[0303] FIG4C is a flow chart of a method for determining DRX parameters for discontinuous reception according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to a method for determining DRX parameters for discontinuous reception, which is used in a network device 1102 and includes:

[0304] Step S4301: receiving the first information sent by terminal 1101.

[0305] In some embodiments, the first information is used to report the DRX cycle expected by the terminal.

[0306] In some embodiments, the network device 1102 receives the first information sent by the terminal 1101 .

[0307] In some embodiments, the desired DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0308] In some embodiments, the desired DRX cycle includes at least one of the following: a desired long cycle, a desired short cycle, and the desired long cycle is X times the desired short cycle, where X is an integer.

[0309] In some embodiments, the desired long cycle and the desired short cycle are both DRX cycles of the second type;

[0310] or,

[0311] The expected long cycle and the expected short cycle are both first-type DRX cycles;

[0312] or,

[0313] The desired long cycle is a first type of DRX cycle, and the desired short cycle is a second type of DRX cycle;

[0314] The first type of DRX cycle is an integer cycle.

[0315] In some embodiments, the method further comprises:

[0316] Send second information, where the second information is used to configure the DRX cycle.

[0317] In some embodiments, the configured DRX cycle is a first type of DRX cycle, and the expected DRX cycle reported in the first information is a first type of DRX cycle; or,

[0318] The configured DRX cycle is a second type of DRX cycle, and the expected DRX cycle reported in the first information is a second type of DRX cycle.

[0319] In some embodiments, the method further comprises:

[0320] Send third information, where the third information is used to indicate the type of the reported expected DRX cycle.

[0321] In some embodiments, the desired DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, the second type of DRX cycle being associated with the same inhibit timer as the first type of DRX cycle.

[0322] For a detailed description of step S4301, please refer to the detailed description of the above embodiments, which will not be repeated here.

[0323] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0324] In this embodiment, the network device receives the expected DRX cycle reported by the terminal through the first information sent by the terminal, so that the network device's understanding of the terminal's expected DRX cycle is consistent with that of the terminal, thereby improving the accuracy and efficiency of determining the expected DRX parameters.

[0325] The following is an exemplary introduction to the above method.

[0326] The present disclosure is used to implement a method for a terminal to report desired DRX parameters. Optional implementation solutions are as follows:

[0327] The present disclosure relates to a method for determining DRX parameters for discontinuous reception. Taking a base station as an example, the method includes:

[0328] 1. A working method for protecting a terminal in a connected state to report an expected second type of DRX cycle (the second type of DRX cycle is a non-integer cycle or a DRX parameter of a rational number cycle, which is different from the original first type of DRX cycle, which is an integer cycle):

[0329] a) The desired DRX cycles include: preferredDRX-LongCycle and preferredDRX-ShortCycle;

[0330] 2. Based on 1, for the desired second type of DRX cycle, the preferredDRX-LongCycle reported by the terminal needs to be an integer multiple of the preferredDRX-ShortCycle;

[0331] 3. Based on 1, the expected long cycle parameters and short cycle parameters reported by the terminal are of the same type, either the first type (integer cycle) or the second type (non-integer cycle); or they are of different types. For example, the long cycle is of the first type and the short cycle is of the second type (but the long cycle will not be of the second type and the short cycle of the first type);

[0332] 4. Based on 1, the first type of DRX cycle and the second type of DRX cycle cannot be reported at the same time:

[0333] a) As an embodiment, the desired first type DRX long cycle and the desired second type DRX long cycle cannot be reported simultaneously;

[0334] b) The terminal decides whether to report the first type of DRX cycle or the second type of DRX cycle according to implementation (i.e., two different types of DRX cycles cannot be reported at the same time);

[0335] 5. Based on 1, the protocol stipulates that the terminal determines how to report the expected DRX cycle based on the DRX cycle configured by the base station:

[0336] c) As an embodiment, if the base station sends a periodic DRX parameter configuration (i.e., a first type of DRX cycle, i.e., an integer cycle DRX parameter, is configured), the terminal only reports the desired first type of DRX cycle, i.e., reports the integer cycle DRX parameter;

[0337] d) As an embodiment, if the base station sends a non-periodic DRX parameter configuration (i.e., the second type of DRX cycle, i.e., a non-integer cycle DRX parameter is configured), the terminal only reports the desired second type of DRX cycle, i.e., reports the non-integer cycle DRX parameter;

[0338] e) As an embodiment, if the base station has not yet sent down the DRX parameter configuration, that is, if the auxiliary information has not been obtained, it can be carried out through 4.

[0339] 6. Based on 1, the network sends configuration information to instruct the terminal to report the expected first type of DRX cycle or the expected second type of DRX cycle:

[0340] a) The base station may instruct the terminal to report only one type of expected value (either one or the other).

[0341] 7. Based on 1, the terminal may report the expected first type of DRX cycle and / or report the expected second type of DRX cycle, depending on which type of reporting is used by the network implementation.

[0342] Example 1:

[0343] Use the reserved bit of the existing IE to report the DRX parameters of the second cycle (that is, use the same prohibit timer as the first DRX cycle reporting):

[0344] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., a RAN) in any of the above methods.

[0345] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0346] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0347] FIG5A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG5A , the terminal 5100 may include at least one of a transceiver module 5101 and a processing module 5102. The terminal 5100 may include:

[0348] The transceiver module 5101 is used to receive the first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0349] Optionally, the expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, and the expected long cycle is X times the expected short cycle, where X is an integer.

[0350] Optionally, the expected long cycle and the expected short cycle are both DRX cycles of the second type;

[0351] or,

[0352] The expected long cycle and the expected short cycle are both first-type DRX cycles;

[0353] or,

[0354] The desired long cycle is a first type of DRX cycle, and the desired short cycle is a second type of DRX cycle;

[0355] The first type of DRX cycle is an integer cycle.

[0356] Optionally, it also includes:

[0357] The transceiver module 5101 is configured to receive second information, where the second information is used to configure a DRX cycle;

[0358] The processing module 5102 is configured to determine the type of the expected DRX cycle reported in the first information according to the configured DRX cycle.

[0359] Optionally, the processing module 5102 is further configured to:

[0360] The configured DRX cycle is a first type of DRX cycle, and the expected DRX cycle reported in the first information is determined to be the first type of DRX cycle; or,

[0361] The configured DRX cycle is a second type of DRX cycle, and it is determined that the expected DRX cycle reported in the first information is a second type of DRX cycle.

[0362] Optionally, it also includes:

[0363] The transceiver module 5101 is configured to receive third information, where the third information is used to indicate a type of a reported desired DRX cycle;

[0364] The processing module 5102 is configured to determine the type of the expected DRX cycle reported in the first information according to the third information.

[0365] Optionally, the desired DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, and the second type of DRX cycle and the first type of DRX cycle are associated with the same prohibit timer.

[0366] FIG5B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure. As shown in FIG5B , the network device 5200 may include: at least one of a transceiver module 5201 and a processing module 5202. The network device 5200 may include:

[0367] The transceiver module 5201 is used to receive the first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

[0368] Optionally, the expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, and the expected long cycle is X times the expected short cycle, where X is an integer.

[0369] Optionally, the expected long cycle and the expected short cycle are both DRX cycles of the second type;

[0370] or,

[0371] The expected long cycle and the expected short cycle are both first-type DRX cycles;

[0372] or,

[0373] The desired long cycle is a first type of DRX cycle, and the desired short cycle is a second type of DRX cycle;

[0374] The first type of DRX cycle is an integer cycle.

[0375] Optionally, the transceiver module 5201 is further configured to:

[0376] Send second information, where the second information is used to configure the DRX cycle.

[0377] Optionally, the configured DRX cycle is a first type of DRX cycle, and the expected DRX cycle reported in the first information is a first type of DRX cycle; or,

[0378] The configured DRX cycle is a second type of DRX cycle, and the expected DRX cycle reported in the first information is a second type of DRX cycle.

[0379] Optionally, the transceiver module 5201 is further configured to:

[0380] Send third information, where the third information is used to indicate the type of the reported expected DRX cycle.

[0381] Optionally, the desired DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, and the second type of DRX cycle and the first type of DRX cycle are associated with the same prohibit timer.

[0382] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0383] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0384] Figure 6A is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 can be a terminal, a network device, a chip, a chip system, or a processor that supports a terminal implementing any of the above methods, or a chip, a chip system, or a processor that supports a network device implementing any of the above methods. Communication device 6100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0385] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. Processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. The communication device 6100 is used to perform any of the above methods.

[0386] In some embodiments, the communication device 6100 further includes one or more memories 6102 for storing instructions. Optionally, all or part of the memories 6102 may be located outside the communication device 6100.

[0387] In some embodiments, the communication device 6100 further includes one or more transceivers 6103. When the communication device 6100 includes one or more transceivers 6103, the transceiver 6103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2104, step S2201, step S2202, and step S2204, but not limited thereto), and the processor 6101 performs the other steps (for example, step S2102, step S2103, and step S2203).

[0388] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0389] In some embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6102. The interface circuit 6104 may be configured to receive signals from the memory 6102 or other devices, and may be configured to send signals to the memory 6102 or other devices. For example, the interface circuit 6104 may read instructions stored in the memory 6102 and send the instructions to the processor 6101.

[0390] The communication device 6100 described in the above embodiments may be a terminal, a network device, or a third entity, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0391] 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.

[0392] The chip 6200 includes one or more processors 6201 , and the chip 6200 is configured to execute any of the above methods.

[0393] In some embodiments, the chip 6200 further includes one or more interface circuits 6202. Optionally, the interface circuit 6202 is connected to the memory 6203. The interface circuit 6202 can be used to receive signals from the memory 6203 or other devices, and can be used to send signals to the memory 6203 or other devices. For example, the interface circuit 6202 can read instructions stored in the memory 6203 and send the instructions to the processor 6201.

[0394] In some embodiments, the interface circuit 6202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2104, step S2201, step S2202, step S2204, but not limited to these), and the processor 6201 executes other steps (for example, step S2102, step S2103, step S2203).

[0395] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0396] In some embodiments, the chip 6200 further includes one or more memories 6203 for storing instructions. Alternatively, all or part of the memories 6203 may be located outside the chip 6200.

[0397] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0398] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0399] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A method for determining DRX parameters of discontinuous reception, characterized in that: The method is executed by a terminal, and includes: Sending first information, wherein the first information is used to report the DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

2. The method according to claim 1, characterized in that The expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, and the expected long cycle is X times the expected short cycle, where X is an integer.

3. The method according to claim 2, characterized in that The expected long cycle and the expected short cycle are both DRX cycles of the second type; or, The expected long cycle and the expected short cycle are both DRX cycles of the first type; or, The expected long cycle is a first type of DRX cycle, and the expected short cycle is a second type of DRX cycle; The first type of DRX cycle is an integer cycle.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: receiving second information, wherein the second information is used to configure a DRX cycle; According to the configured DRX cycle, a type of the expected DRX cycle reported in the first information is determined.

5. The method according to claim 4, characterized in that The determining, according to the configured DRX cycle, a type of the expected DRX cycle reported in the first information includes: The configured DRX cycle is a first type of DRX cycle, and determining that the expected DRX cycle reported in the first information is a first type of DRX cycle; or, The configured DRX cycle is a second type of DRX cycle, and it is determined that the expected DRX cycle reported in the first information is a second type of DRX cycle.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: receiving third information, wherein the third information is used to indicate a type of the reported expected DRX cycle; The type of the expected DRX cycle reported in the first information is determined according to the third information.

7. The method according to any one of claims 1 to 6, characterized in that: The expected DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, wherein the second type of DRX cycle and the first type of DRX cycle are associated with a same prohibit timer.

8. A method for determining DRX parameters of discontinuous reception, characterized in that: The method is performed by a network device, and the method includes: Receive first information, wherein the first information is used to report a DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

9. The method according to claim 8, characterized in that The expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, and the expected long cycle is X times the expected short cycle, where X is an integer.

10. The method according to claim 9, characterized in that The expected long cycle and the expected short cycle are both DRX cycles of the second type; or, The expected long cycle and the expected short cycle are both DRX cycles of the first type; or, The expected long cycle is a first type of DRX cycle, and the expected short cycle is a second type of DRX cycle; The first type of DRX cycle is an integer cycle.

11. The method according to any one of claims 8 to 10, characterized in that: The method further comprises: Send second information, where the second information is used to configure the DRX cycle.

12. The method according to claim 11, characterized in that The configured DRX cycle is a first type of DRX cycle, and the expected DRX cycle reported in the first information is a first type of DRX cycle; or, The configured DRX cycle is a second type of DRX cycle, and the expected DRX cycle reported in the first information is a second type of DRX cycle.

13. The method according to any one of claims 8 to 12, characterized in that: The method further comprises: Send third information, where the third information is used to indicate the type of the reported expected DRX cycle.

14. The method according to any one of claims 8 to 13, characterized in that: The expected DRX cycle includes a first type of DRX cycle and a second type of DRX cycle, wherein the second type of DRX cycle and the first type of DRX cycle are associated with a same prohibit timer.

15. A terminal, characterized in that: The terminal comprises: A transceiver module is used to receive first information, wherein the first information is used to report a DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

16. A network device, characterized in that: The network equipment includes: A transceiver module is used to receive first information, wherein the first information is used to report a DRX cycle expected by the terminal, wherein the expected DRX cycle includes a first type of DRX cycle and / or a second type of DRX cycle, the first type of DRX cycle is an integer cycle, and the second type of DRX cycle is a non-integer cycle.

17. A communication device, characterized in that: include: one or more processors; The processor is used to execute the method for determining the discontinuous reception DRX parameters according to any one of claims 1-14.

18. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is enabled to execute the method for determining a discontinuous reception (DRX) parameter according to any one of claims 1 to 14.

Images