Method for determining discontinuous reception (DRX) parameters, terminal, and network device

Abstract

The present disclosure relates to a method for determining discontinuous reception (DRX) parameters, a terminal, and a network device. The method includes: the terminal sends first information. Thus, to a certain extent, the problem of how the terminal specifically reports the desired discontinuous reception (DRX) is solved.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, 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 technologies, a discontinuous reception (DRX) mechanism has been introduced. Currently, a user equipment (UE) can report its desired DRX parameters. Summary of the Invention

[0003] Embodiments of the present disclosure provide a method for determining discontinuous reception (DRX) parameters, a terminal, and a network device, which to a certain extent solve the problem of how a UE specifically reports DRX parameters.

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

[0005] Sending a first message, where the first message is used to report a DRX cycle desired by the terminal, and 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.

[0006] According to a second aspect of the embodiments of the present disclosure, a method for determining discontinuous reception (DRX) parameters is provided, which is executed by a network device. The method includes:

[0007] Receiving a first message, where the first message is used to report a DRX cycle desired by a terminal, and 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.

[0008] According to a third aspect of the embodiments of the present disclosure, a terminal is provided, including:

[0009] A transceiver module, configured to receive a first message, where the first message is used to report a DRX cycle desired by a terminal, and 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.

[0010] According to a fourth aspect of the embodiments of the present disclosure, a network device is provided, including:

[0011] A transceiver module, configured to receive a first piece of information, where the first piece of information is used to report a DRX cycle expected by a terminal, and 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 being an integer cycle, and the second type of DRX cycle being a non-integer cycle.

[0012] According to a fifth aspect of the embodiments of the present disclosure, a communication device is provided, including:

[0013] One or more processors;

[0014] Wherein, the processor is configured to call instructions to cause the communication device to execute the processing method described in any one of the first aspect and the second aspect.

[0015] According to a sixth aspect of the embodiments of the present disclosure, a communication system is provided, characterized by including a terminal and a network device, where the terminal is configured to implement the method for determining non-continuous reception DRX parameters described in the first aspect, and the network device is configured to implement the method for determining non-continuous reception DRX parameters described in the second aspect.

[0016] According to a seventh aspect of the embodiments of the present disclosure, a storage medium is provided, the storage medium stores instructions, and is characterized in that when the instructions run on a communication device, the communication device is caused to execute the method for determining non-continuous reception DRX parameters described in any one of the first aspect and the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following introduces the drawings required for describing the embodiments. The following drawings are only some embodiments of the present disclosure and do not specifically limit the protection scope of the present disclosure.

[0018] Figure 1A is a schematic diagram of the architecture of a communication system shown according to an embodiment of the present disclosure;

[0019] Figure 1B is a schematic diagram of a non-continuous reception DRX mechanism shown in an embodiment of the present disclosure;

[0020] Figures 2A - 2B is an interaction schematic diagram of the method for determining non-continuous reception DRX parameters shown according to an embodiment of the present disclosure;

[0021] Figures 3A - 3E is a flowchart of the method for determining non-continuous reception DRX parameters provided according to an embodiment of the present disclosure;

[0022] Figures 4A - 4C is a flowchart of the method for determining non-continuous reception DRX parameters provided according to an embodiment of the present disclosure;

[0023] Figure 5A is a schematic structural diagram of a terminal proposed by an embodiment of the present disclosure;

[0024] Figure 5B is a schematic structural diagram of a network device proposed by an embodiment of the present disclosure;

[0025] Figure 6A is a schematic structural diagram of a communication device proposed by an embodiment of the present disclosure;

[0026] Figure 6B is a schematic structural diagram of a chip proposed by an embodiment of the present disclosure. Detailed implementation manners

[0027] An embodiment of the present disclosure proposes a method for determining discontinuous reception (DRX) parameters, a terminal, and a network device.

[0028] In a first aspect, an embodiment of the present disclosure proposes a method for determining DRX parameters, which is executed by a terminal. The method includes:

[0029] Sending first information, where the first information is used to report a DRX cycle desired by the terminal. 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.

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

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

[0032] In the above embodiment, by reporting the desired long cycle and the desired short cycle with a multiple relationship, the transmission delay between the terminal and the network device is reduced.

[0033] In combination with some embodiments of the first aspect, in some embodiments, both the desired long cycle and the desired short cycle are the second type of DRX cycle;

[0034] Or,

[0035] both the desired long cycle and the desired short cycle are the first type of DRX cycle;

[0036] Or,

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

[0038] Wherein, the DRX period of the first type is an integer period.

[0039] In the above embodiments, the terminal reports long periods and short periods of the same type or different types, thereby improving the flexibility of the terminal to report DRX periods, and providing conditions for further reducing the transmission delay, ensuring the accuracy and reliability of data transmission.

[0040] Combined with some embodiments of the first aspect, in some embodiments, the method further includes:

[0041] Receiving second information, wherein the second information is used to configure the DRX period;

[0042] Determining the type of the desired DRX period reported in the first information according to the configured DRX period.

[0043] In the above embodiments, by determining the type of the desired DRX period reported in the first information based on the second information of the network device, the resource amount occupied when the terminal reports the desired DRX period is reduced, and the transmission efficiency of the communication system is improved.

[0044] Combined with some embodiments of the first aspect, in some embodiments, the determining the type of the desired DRX period reported in the first information according to the configured DRX period includes:

[0045] If the configured DRX period is a DRX period of the first type, determining that the desired DRX period reported in the first information is a DRX period of the first type; or,

[0046] If the configured DRX period is a DRX period of the second type, determining that the desired DRX period reported in the first information is a DRX period of the second type.

[0047] Combined with some embodiments of the first aspect, in some embodiments, the method further includes:

[0048] Receiving third information, wherein the third information is used to indicate the type of the desired DRX period reported;

[0049] Determining the type of the desired DRX period reported in the first information according to the third information.

[0050] In the above embodiments, 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 when the terminal reports the desired DRX cycle and improving the transmission efficiency of the communication system.

[0051] In combination with some embodiments of the first aspect, in some embodiments, 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 is associated with the same prohibition timer as the first type of DRX cycle.

[0052] In the above embodiments, by associating the second type of DRX cycle with the same prohibition timer as the first type of DRX cycle, the reporting of two types of DRX cycles can be achieved through one piece of information, reducing the amount of resources when the terminal reports different types of desired DRX cycles and improving the transmission efficiency of the communication system.

[0053] In a second aspect, embodiments of the present disclosure propose a method for determining discontinuous reception (DRX) parameters, which is executed by a network device. The method includes:

[0054] Receiving a first piece of information, where the first piece of information is used to report the DRX cycle desired by the terminal. 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.

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

[0056] In combination with some embodiments of the second aspect, in some embodiments, both the desired long cycle and the desired short cycle are of the second type of DRX cycle;

[0057] Or,

[0058] Both the desired long cycle and the desired short cycle are of the first type of DRX cycle;

[0059] Or,

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

[0061] where the first type of DRX cycle is an integer cycle.

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

[0063] Sending a second piece of information, where the second piece of information is used to configure a DRX cycle.

[0064] In some embodiments 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 desired DRX cycle reported in the first piece of information is a first type of DRX cycle; or,

[0065] The configured DRX cycle is a second type of DRX cycle, and the desired DRX cycle reported in the first piece of information is a second type of DRX cycle.

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

[0067] Sending a third piece of information, where the third piece of information is used to indicate the type of the desired DRX cycle reported.

[0068] In some embodiments in combination with some embodiments of the second aspect, in some embodiments, 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 is associated with the same prohibited timer as the first type of DRX cycle.

[0069] In a third aspect, an embodiment of the present disclosure provides a terminal, where the terminal includes:

[0070] A transceiver module, configured to receive a first piece of information, where the first piece of information is used to report a desired DRX cycle of the terminal, where 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.

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

[0072] In some embodiments in combination with some embodiments of the third aspect, in some embodiments, both the desired long cycle and the desired short cycle are second type of DRX cycles;

[0073] Or,

[0074] Both the desired long cycle and the desired short cycle are first type of DRX cycles;

[0075] Or,

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

[0077] Wherein, the DRX period of the first type is an integer period.

[0078] In combination with some embodiments of the third aspect, in some embodiments, it further includes:

[0079] The transceiver module is configured to receive second information, wherein the second information is used to configure the DRX period;

[0080] The processing module is configured to determine the type of the desired DRX period reported in the first information according to the configured DRX period.

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

[0082] When the configured DRX period is a DRX period of the first type, determine that the desired DRX period reported in the first information is a DRX period of the first type; or,

[0083] When the configured DRX period is a DRX period of the second type, determine that the desired DRX period reported in the first information is a DRX period of the second type.

[0084] In combination with some embodiments of the third aspect, in some embodiments, it further includes:

[0085] The transceiver module is configured to receive third information, wherein the third information is used to indicate the type of the desired DRX period reported;

[0086] The processing module is configured to determine the type of the desired DRX period reported in the first information according to the third information.

[0087] In combination with some embodiments of the third aspect, in some embodiments, the desired DRX period includes a DRX period of a first type and a DRX period of a second type, and the DRX period of the second type is associated with the same prohibition timer as the DRX period of the first type.

[0088] Fourth aspect, an embodiment of the present disclosure provides a network device, the network device includes:

[0089] A transceiver module, configured to receive a first piece of information, where the first piece of information is used to report a DRX cycle desired by a terminal, and 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 being an integer cycle, and the second type of DRX cycle being a non-integer cycle.

[0090] Combined with some embodiments of the fourth aspect, in some embodiments, the desired DRX cycle includes at least one of the following: a desired long cycle, a desired short cycle, the desired long cycle being X times the desired short cycle, where X is an integer.

[0091] Combined with some embodiments of the fourth aspect, in some embodiments, both the desired long cycle and the desired short cycle are of the second type of DRX cycle;

[0092] Or,

[0093] both the desired long cycle and the desired short cycle are of the first type of DRX cycle;

[0094] Or,

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

[0096] where the first type of DRX cycle is an integer cycle.

[0097] Combined with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to:

[0098] send a second piece of information, where the second piece of information is used to configure a DRX cycle.

[0099] Combined with some embodiments of the fourth aspect, in some embodiments, the configured DRX cycle is of the first type of DRX cycle, and the desired DRX cycle reported in the first piece of information is of the first type of DRX cycle; or,

[0100] the configured DRX cycle is of the second type of DRX cycle, and the desired DRX cycle reported in the first piece of information is of the second type of DRX cycle.

[0101] Combined with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to:

[0102] send a third piece of information, where the third piece of information is used to indicate the type of the desired DRX cycle reported.

[0103] In some embodiments in combination with some embodiments of the fourth aspect, 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 is associated with the same prohibition timer as the first type of DRX cycle.

[0104] Fifth aspect, embodiments of the present disclosure propose a terminal, the terminal includes: one or more processors; wherein, the processor is used to execute an optional implementation manner of the method for determining discontinuous reception DRX parameters proposed in the first aspect.

[0105] Sixth aspect, embodiments of the present disclosure propose a network device, the network device includes: one or more processors; wherein, the processor is used to execute an optional implementation manner of the method for determining discontinuous reception DRX parameters proposed in the second aspect.

[0106] Seventh aspect, embodiments of the present disclosure propose a communication system, the communication system includes: a terminal, 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.

[0107] Eighth aspect, embodiments of the present disclosure propose a storage medium, the storage medium stores instructions, when the instructions run on a communication device, the communication device is caused to execute the methods described in the optional implementation manners of the first aspect and the second aspect.

[0108] Ninth aspect, embodiments of the present disclosure propose a program product, when the program product is executed by a communication device, the communication device is caused to execute the methods described in the optional implementation manners of the first aspect and the second aspect.

[0109] Tenth aspect, embodiments of the present disclosure propose a computer program, when it runs on a computer, the computer is caused to execute the methods described in the optional implementation manners of the first aspect and the second aspect.

[0110] Eleventh aspect, embodiments of the present disclosure provide a chip or a chip system. The chip or the chip system includes a processing circuit configured to execute the methods described in the optional implementation manners of the first aspect and the second aspect above.

[0111] It can be understood that the above terminal, network device, communication system, storage medium, program product, computer program, chip or chip system are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods, which will not be elaborated here.

[0112] Embodiments of the present disclosure propose a method for determining discontinuous reception (DRX) parameters. In some embodiments, terms such as the method for determining DRX parameters, the method for measurement configuration, the configuration method, and the communication method can be used interchangeably; terms such as the apparatus for determining DRX parameters, the measurement configuration apparatus, the configuration apparatus, and the communication apparatus can be used interchangeably; terms such as the system for determining DRX parameters, the measurement configuration system, and the communication system can be used interchangeably.

[0113] The embodiments of the present disclosure are not exhaustive, but are only illustrations of some embodiments and do not constitute specific limitations on the protection scope of the present disclosure. Without contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily. For example, a solution obtained by removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be arbitrarily exchanged. Additionally, optional implementation manners in an embodiment can be combined arbitrarily; moreover, the embodiments can be combined arbitrarily. For example, some or all steps of different embodiments can be combined arbitrarily, and an embodiment can be combined arbitrarily with the optional implementation manners of other embodiments.

[0114] In the embodiments of the present disclosure, unless otherwise specified and there is no logical conflict, the terms and / or descriptions among the embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0115] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and do not constitute a limitation on the present disclosure.

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

[0117] In the embodiments of the present disclosure, "a plurality of" means two or more.

[0118] In some embodiments, terms such as "at least one of", "one or more", "a plurality of", "multiple", etc. can be used interchangeably.

[0119] In some embodiments, notations such as "at least one of A and B", "A and / or B", "in one case A, in another case B", "in response to one case A, in response to another case B", etc. may, depending on the circumstances, include the following technical solutions: in some embodiments, A (performing A independently of B); in some embodiments, B (performing B independently of A); in some embodiments, selecting to perform from A and B (A and B are selectively performed); in some embodiments, A and B (both A and B are performed). The same applies when there are more branches such as A, B, C, etc.

[0120] In some embodiments, notations such as "A or B" may, depending on the circumstances, include the following technical solutions: in some embodiments, A (performing A independently of B); in some embodiments, B (performing B independently of A); in some embodiments, selecting to perform from A and B (A and B are selectively performed). The same applies when there are more branches such as A, B, C, etc.

[0121] Prefix words such as "first", "second", etc. in the embodiments of the present disclosure are only used to distinguish different described objects and do not impose limitations on the position, order, priority, quantity, or content of the described objects. For the statements of the described objects, refer to the description in the claims or the context of the embodiments. There should be no redundant limitations due to the use of prefix words. For example, if the described object is "field", the ordinal numbers before "field" in "first field" and "second field" do not limit the position or order between the "fields", and "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of "first field" and "second field". Another example, if the described object is "level", the ordinal numbers before "level" in "first level" and "second level" do not limit the priority between the "levels". Another example, the quantity of the described object is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the quantity of "device" can be one or more. In addition, the objects modified by different prefix words can be the same or different. For example, if the described object is "device", "first device" and "second device" can be the same device or different devices, and their types can be the same or different; another example, if the described object is "information", "first information" and "second information" can be the same information or different information, and their contents can be the same or different.

[0122] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A or as indirectly indicating A.

[0123] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "when...", "when...", "if...", "if..." can be replaced with each other.

[0124] 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 lower than", "above", etc. may be interchangeable 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", "below", etc. may be interchangeable with each other.

[0125] In some embodiments, a device and an apparatus may be interpreted as physical or virtual, and their names are not limited to the names described in the embodiments, and in some cases may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0126] In some embodiments, a "network" may be interpreted as the devices included in the network. For example, access network devices, core network devices, etc.

[0127] In some embodiments, an "access network device (AN device)" may also be referred to as a "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as a "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

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

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

[0130] In some embodiments, data, information, etc. may be obtained after obtaining the consent of the user.

[0131] Figure 1A It is a schematic diagram of the architecture of a communication system shown according to an embodiment of the present disclosure.

[0132] As Figure 1A shown, the communication system 1100 includes a terminal 1101 and a network device 1102.

[0133] In some embodiments, the terminal 1101 includes, for example, at least one of a mobile phone, a wearable device, an Internet of Things device, a vehicle with communication function, a smart vehicle, a tablet computer (Pad), 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 smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, and a wireless terminal device in smart home, but is not limited thereto.

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

[0135] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of an evolved NodeB (eNB) in a 5G communication system, a next-generation eNB (ng-eNB), a next-generation NodeB (gNB), a NodeB (NB), a home NodeB (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 RAN, a Cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.

[0136] In some embodiments, the technical solutions of the present disclosure can be applied to the Open RAN architecture. At this time, the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure can become the internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0137] In some embodiments, an access network device may be composed of a central unit (CU) and a distributed unit (DU). Among them, the CU can also be referred to as a control unit. Adopting the CU-DU structure can split the protocol layer of the access network device. The functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all protocol layers are distributed in the DU. The CU centrally controls the DU, but it is not limited to this.

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

[0139] It can be understood that the communication system described in the embodiments of the present disclosure is to more clearly illustrate the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of the present disclosure. Those of ordinary skill in the art know that with the evolution of the system architecture and the emergence of new service scenarios, the technical solutions proposed in the embodiments of the present disclosure are equally applicable to similar technical problems.

[0140] The following embodiments of the present disclosure can be applied to Figure 1A the communication system 1100 shown, or part of the main body, but it is not limited to this. Figure 1A The main bodies shown are examples. The communication system can include Figure 1A all or part of the main bodies, or can include Figure 1A other main bodies outside. The number and form of each main body are arbitrary. Each main body can be physical or virtual. The connection relationships between the main bodies are examples. The main bodies can be not connected or connected, and their connections can be in any way, either directly connected or indirectly connected, either wired or wireless.

[0141] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, the 4th generation mobile communication system (4G), the 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), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.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, next-generation systems extended based on them, etc. In addition, multiple systems can be combined (for example, a combination of LTE or LTE-A and 5G, etc.) and applied.

[0142] In the 5G system, in order to save the power consumption of the UE, a Discontinuous Reception (DRX) mechanism is introduced. That is, when the UE is in the connected state, it does not need to continuously monitor the control channel sent by the gNB, but intermittently monitors the control channel, as Figure 1B shown. Figure 1BIt is a schematic diagram of the discontinuous reception (DRX) mechanism shown in an embodiment of the present disclosure. Among them, OnDuration represents the time period during which the UE listens to the control channel. During this period, the radio frequency channel is turned on, and the control channel is continuously listened to. At other times except for OnDuration, the UE is in a power-saving state, and its radio frequency link is turned off. On Duration appears periodically, and the specific period is implemented by the gNB configuration. While achieving power saving for the UE, in order to avoid excessive transmission delay between the gNB and the UE, the concepts of long cycle and short cycle are introduced. During this cycle, the UE enters the inactive state and does not need to continuously listen to the control channel of the gNB. In the Short Cycle, On Duration appears more frequently than in the long cycle. If the UE is configured with both long and short cycles, after the short cycle starts, after the timer (drx-ShortCycleTimer) of the short cycle times out, the UE listens according to the long cycle.

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

[0144] Figure 2A It is an interactive schematic diagram of the method for determining discontinuous reception (DRX) parameters shown in an embodiment of the present disclosure. As Figure 2A shown, the embodiment of the present disclosure relates to a method for determining discontinuous reception (DRX) parameters. The above method includes:

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

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

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

[0148] In some embodiments, when the DRX cycle configured by the network device 1102 for the terminal 1101 is the first type of DRX cycle, the desired DRX cycle reported in the first information can be the first type of DRX cycle.

[0149] In some embodiments, the first type of DRX cycle is an integer-cycle DRX cycle. For example, the first type of DRX cycle can be any integer-cycle DRX cycle such as 30 milliseconds, 80 milliseconds, 256 milliseconds, 1024 milliseconds, etc. The present disclosure does not limit this.

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

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

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

[0153] In some embodiments, the second type of DRX cycle is a non-integer cycle DRX cycle. For example, the second type of DRX cycle may be a DRX cycle with any non-integer cycle such as 50 / 3 milliseconds, 200 / 9 milliseconds, 400 / 3 milliseconds, 125 / 9 milliseconds, etc., and the present disclosure does not limit this.

[0154] In some embodiments, when the DRX cycle configured by the network device 1102 for 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 the first type of DRX cycle and the second type of DRX cycle. At this time, the second type of DRX cycle reported in the first information is associated with the same prohibited timer as the first type of DRX cycle.

[0155] In some embodiments, when the network device 1102 configures both the first type of DRX cycle and the second type of DRX cycle for the terminal 1101, when the expectation reported in the first information includes the first type of DRX cycle and the second type of DRX cycle, since different types of DRX cycles cannot be reported simultaneously, at this time, these two types of DRX cycles reported in the first information can be associated with a prohibited timer. When the first DRX cycle is reported, the prohibited timer is started, and after the prohibited timer times out, the second DRX cycle is reported.

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

[0157] Step S2102, when the configured DRX cycle is the first type of DRX cycle, the terminal 1101 determines that the expected DRX cycle reported in the first information is the first type of DRX cycle.

[0158] In some embodiments, when the DRX cycle configured by the network device 1102 for the terminal 1101 is the 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.

[0159] Step S2103, when the configured DRX cycle is a second type of DRX cycle, the terminal 1101 determines that the expected DRX cycle reported in the first information is a second type of DRX cycle.

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

[0161] Among them, after step S2101, step S2102 may be executed, or step S2103 may also be executed. When the configured DRX cycle is a first type of DRX cycle, step S2102 may be executed, and when the configured DRX cycle is a second type of DRX cycle, step S2103 may be executed.

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

[0163] In some embodiments, after the terminal 1101 determines the type of the expected DRX cycle reported in the first information, it may send the first information to the network device 1102.

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

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

[0166] In some embodiments, the name of the expected long cycle is not limited, for example, it is "preferredDRX-LongCycle", etc.

[0167] In some embodiments, the name of the expected short cycle is not limited, for example, it is "preferredDRX-ShortCycle", etc.

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

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

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

[0171] In some embodiments, when the DRX cycle configured by the network device 1102 for the terminal 1101 is a DRX cycle of the second type, since the expected DRX cycles reported in the first information determined by the terminal 1101 may include the expected long cycle and the 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 for the terminal 1101 is a DRX cycle of the second type, the expected long cycle reported in the first information determined by the terminal 1101 may be a DRX cycle of the first type, and the expected short cycle reported may be a DRX cycle of the second type.

[0172] For example, the DRX cycle parameters of the second type configured by the network device 1102 for the terminal 1101 are: 50 / 3 ms, 200 / 9 ms, 400 / 3 ms, 125 / 9 ms, 600 / 3 ms. The expected short cycle of the terminal 1101 is 50 / 3 ms, and the expected long cycle can be 600 / 3 ms, that is, 200 ms. At this time, the terminal 1101 can report the expected DRX cycles 50 / 3 ms and 200 ms through the first information. The expected DRX cycles reported by the terminal 1101 include the DRX cycle of the first type, 200 ms, and the DRX cycle of the second type, 50 / 3 ms. The terminal can first report the expected short cycle 50 / 3 ms and start the prohibition timer at the same time. When the prohibition timer expires, it continues to report the expected long cycle 200 ms.

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

[0174] For example, the DRX cycle parameters of the first type configured by the network device 1102 for the terminal 1101 are: 30 milliseconds, 80 milliseconds, 256 milliseconds, and 1024 milliseconds. If the DRX cycle expected by the terminal 1101 is 256 milliseconds, the terminal 1101 can report the expected DRX cycle of 256 milliseconds through the first information.

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

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

[0177] In this embodiment or implementation, without contradiction, each step can be independent, combined arbitrarily or the order can be exchanged. Optional methods or optional examples can be combined arbitrarily, and can be combined arbitrarily with any steps of other embodiments or other implementations.

[0178] In this embodiment, first, the network device 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 expected DRX cycle of the terminal is consistent with the terminal's understanding, improving the accuracy and efficiency of determining the expected DRX parameters.

[0179] Figure 2B It is an interaction schematic diagram of the method for determining the discontinuous reception (DRX) parameters shown in the embodiments of the present disclosure. As Figure 2B shown, the embodiments of the present disclosure relate to a method for determining the discontinuous reception (DRX) parameters. The above method includes:

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

[0181] For a detailed introduction to step S2201, reference can be made to the above step S2101.

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

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

[0184] In some embodiments, when the network device 1102 configures a first type of DRX cycle and a 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 the desired DRX that the terminal 1101 is to report.

[0185] In some embodiments, based on protocol agreements, when the optional desired DRX cycles of the terminal 1101 include a first type of DRX cycle and a second type of DRX cycle, the network device 1102 may send third information to the terminal 1101 to indicate the type of the desired DRX that the terminal 1101 is to report.

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

[0187] Step S2203. The terminal 1101 determines the type of the desired DRX cycle reported in the first information according to the third information.

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

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

[0190] Step S2204. The terminal 1101 sends the first information to the network device 1102.

[0191] For a detailed introduction to step S2204, reference may be made to step S2104 above.

[0192] The method for determining discontinuous reception (DRX) parameters according to 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 step S2201 + S2203 may be implemented as an independent embodiment, but is not limited thereto.

[0193] In this embodiment or implementation manner, without contradiction, each step may be independent, combined arbitrarily or the order may be exchanged, optional manners or optional examples may be combined arbitrarily, and any combination may be made with any step of other embodiments or other implementation manners.

[0194] In this embodiment, based on the indication of the desired DRX cycle reported 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 when the terminal reports the desired DRX cycle and improving the transmission efficiency of the communication system.

[0195] Figure 3A It is a flowchart of a method for determining discontinuous reception (DRX) parameters according to an embodiment of the present disclosure. As Figure 3A shown, the embodiment of the present disclosure relates to a method for determining DRX parameters, which is used for the terminal 1101. The method includes:

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

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

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

[0199] Step S3102, when the configured DRX cycle is the DRX cycle of the first type, determining that the desired DRX cycle reported in the first information is the DRX cycle of the first type.

[0200] Step S3103, when the configured DRX cycle is the DRX cycle of the second type, determining that the desired DRX cycle reported in the first information is the DRX cycle of the second type.

[0201] Step S3104, sending the first information to the network device 1102.

[0202] In some embodiments, the first information is used to report the desired DRX cycle of the terminal.

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

[0204] For a detailed introduction to steps S3101 - S3104, reference can be made to Figure 2A Steps S2101 - S2104 in the embodiments shown, which will not be elaborated here.

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

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

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

[0208] Figure 3B It is a flowchart showing a method for determining discontinuous reception (DRX) parameters according to an embodiment of the present disclosure. As Figure 3B shown, the embodiments of the present disclosure relate to a method for determining discontinuous reception (DRX) parameters for a terminal 1101. The method includes:

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

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

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

[0212] Step S3202: Receive third information sent by the network device 1102.

[0213] In some embodiments, the third information is used to indicate the type of the expected DRX cycle to be reported.

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

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

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

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

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

[0219] For a detailed introduction to steps S3201 - S3204, reference can be made to steps S2201 - S2204 in the embodiment shown in Figure 2B which will not be elaborated here.

[0220] The method for determining discontinuous reception (DRX) parameters according to 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 step S3201 + S3202 may be implemented as an independent embodiment, but not limited thereto.

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

[0222] 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 when the terminal reports the desired DRX cycle and improving the transmission efficiency of the communication system.

[0223] Figure 3C It is a flowchart of the method for determining discontinuous reception (DRX) parameters according to the embodiments of the present disclosure. As Figure 3C shown, the embodiments of the present disclosure relate to a method for determining discontinuous reception (DRX) parameters for a terminal 1101. The method includes:

[0224] Step S3301: Receive a second piece of information sent by a network device 1102.

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

[0226] In some embodiments, the terminal 1101 receives the second piece of information sent by the network device 1102.

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

[0228] For a detailed introduction to steps S3301 - S3302, reference may be made to Figure 2A steps S2101 - S2102 in the embodiments shown, which will not be elaborated here.

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

[0230] In some embodiments, the first information is used to report the desired DRX cycle of the terminal.

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

[0232] For a detailed introduction to step S3303, reference may be made toFigure 2A Step S2104 in the illustrated embodiment will not be elaborated herein.

[0233] The method for determining discontinuous reception (DRX) parameters according to 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 an independent embodiment, step S3303 may be implemented as an independent embodiment, etc., but not limited thereto.

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

[0235] 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 desired DRX parameters.

[0236] Figure 3D It is a flowchart showing the method for determining discontinuous reception (DRX) parameters according to the embodiments of the present disclosure. As Figure 3D shown, the embodiments of the present disclosure relate to a method for determining discontinuous reception (DRX) parameters for a terminal 1101. The above method includes:

[0237] Step S3401, receiving second information sent by a network device 1102.

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

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

[0240] For a detailed introduction to step S3401, reference may be made to Figure 2A step S2101 in the illustrated embodiment, which will not be elaborated herein.

[0241] Step S3402, when the configured DRX cycle is a second type of DRX cycle, determining that the desired DRX cycle reported in the first information is the second type of DRX cycle.

[0242] Step S3403, sending the first information to the network device 1102.

[0243] In some embodiments, the first information is used to report the desired DRX cycle of the terminal.

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

[0245] For a detailed introduction to steps S3402 - S3403, reference can be made to Figure 2A steps S2103 - S2104 in the illustrated embodiment, which will not be elaborated here.

[0246] The method for determining discontinuous reception (DRX) parameters according to the embodiments of the present disclosure may include at least one of steps S3401 to S3403. For example, steps S3401 + S3402 can be implemented as an independent embodiment, step S3403 can be implemented as an independent embodiment, and so on, but not limited thereto.

[0247] In the embodiments of the present disclosure, some or all of the steps and their optional implementation manners can be arbitrarily combined with some or all of the steps in other embodiments, and can also be arbitrarily combined with the optional implementation manners in other embodiments.

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

[0249] Figure 3E is a flowchart showing the method for determining discontinuous reception (DRX) parameters according to the embodiments of the present disclosure. As Figure 3E shown, the embodiments of the present disclosure relate to a method for determining discontinuous reception (DRX) parameters for a terminal 1101. The method includes:

[0250] Step S3501, sending a first information to a network device 1102.

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

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

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

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

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

[0256] Or,

[0257] Both the desired long cycle and the desired short cycle are DRX cycles of the first type;

[0258] Or,

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

[0260] Among them, the DRX cycle of the first type is an integer cycle.

[0261] In some embodiments, the method further includes:

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

[0263] determining the type of the desired DRX cycle reported in the first information according to the configured DRX cycle.

[0264] In some embodiments, determining the type of the desired DRX cycle reported in the first information according to the configured DRX cycle includes:

[0265] if the configured DRX cycle is a DRX cycle of the first type, determining that the desired DRX cycle reported in the first information is a DRX cycle of the first type; or,

[0266] if the configured DRX cycle is a DRX cycle of the second type, determining that the desired DRX cycle reported in the first information is a DRX cycle of the second type.

[0267] In some embodiments, the method further includes:

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

[0269] determining the type of the desired DRX cycle reported in the first information according to the third information.

[0270] In some embodiments, the desired DRX cycle includes a DRX cycle of the first type and a DRX cycle of the second type, and the DRX cycle of the second type is associated with the same prohibited timer as the DRX cycle of the first type.

[0271] For the detailed introduction of step S3501, reference can be made to the description of the above embodiments, and details are not described herein again.

[0272] In the embodiments of the present disclosure, some or all of the steps and their optional implementation manners can be arbitrarily combined with some or all of the steps in other embodiments, or can be arbitrarily combined with the optional implementation manners in other embodiments.

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

[0274] Figure 4A It is a flowchart showing a method for determining discontinuous reception (DRX) parameters according to an embodiment of the present disclosure. As Figure 4A shown, the embodiment of the present disclosure relates to a method for determining DRX parameters, which is used for the network device 1102. The method includes:

[0275] Step S4101: Send the second information to the terminal 1101.

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

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

[0278] For a detailed introduction to step S4101, reference can be made to Figure 2A step S2101 in the embodiment shown, which will not be elaborated here.

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

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

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

[0282] For a detailed introduction to step S4102, reference can be made to Figure 2A step S2104 in the embodiment shown, which will not be elaborated here.

[0283] The method for determining DRX parameters according to the embodiment of the present disclosure may include at least one of step S4101 to step S4102. For example, step S4101 can be implemented as an independent embodiment, step S4102 can be implemented as an independent embodiment, and step S4101 + S4102 can be implemented as an independent embodiment, but not limited thereto.

[0284] In the embodiment of the present disclosure, some or all of the steps and their optional implementation manners can be arbitrarily combined with some or all of the steps in other embodiments, and can also be arbitrarily combined with the optional implementation manners in other embodiments.

[0285] In this embodiment, after the network device configures the DRX cycle for the terminal, it receives the desired DRX cycle reported by the terminal, thereby providing conditions for improving the efficiency of the terminal to determine the desired DRX cycle and improving the transmission efficiency of the communication system.

[0286] Figure 4B It is a flowchart showing a method for determining discontinuous reception (DRX) parameters according to an embodiment of the present disclosure. As Figure 4B shown, the embodiment of the present disclosure relates to a method for determining DRX parameters, which is used for a network device 1102. The method includes:

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

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

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

[0290] For a detailed introduction to step S4201, reference can be made to Figure 2B step S2201 in the embodiment shown, which will not be elaborated here.

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

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

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

[0294] For a detailed introduction to step S4202, reference can be made to Figure 2B step S2202 in the embodiment shown, which will not be elaborated here.

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

[0296] In some embodiments, the first information is used to report the desired DRX cycle of the terminal.

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

[0298] For a detailed introduction to step S4203, reference can be made to Figure 2B step S2204 in the embodiment shown, which will not be elaborated here.

[0299] The method for determining discontinuous reception (DRX) parameters 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 step S4201 + S4202 may be implemented as an independent embodiment, but it is not limited thereto.

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

[0301] 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 resource amount occupied when the terminal reports the expected DRX cycle, and ensuring the accuracy and reliability of data transmission.

[0302] Figure 4C It is a flowchart of the method for determining discontinuous reception (DRX) parameters shown according to the embodiments of the present disclosure. As Figure 4C shown, the embodiments of the present disclosure relate to a method for determining discontinuous reception (DRX) parameters, which is used for a network device 1102. The method includes:

[0303] Step S4301, receiving first information sent by a terminal 1101.

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

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

[0306] In some embodiments, 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.

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

[0308] In some embodiments, both the expected long cycle and the expected short cycle are the second type of DRX cycle;

[0309] Or,

[0310] both the expected long cycle and the expected short cycle are the first type of DRX cycle;

[0311] Alternatively,

[0312] the desired long period is a DRX period of a first type, and the desired short period is a DRX period of a second type;

[0313] wherein, the DRX period of the first type is an integer period.

[0314] In some embodiments, the method further includes:

[0315] sending second information, wherein the second information is used to configure the DRX period.

[0316] In some embodiments, the configured DRX period is a DRX period of the first type, and the desired DRX period reported in the first information is a DRX period of the first type; or,

[0317] the configured DRX period is a DRX period of the second type, and the desired DRX period reported in the first information is a DRX period of the second type.

[0318] In some embodiments, the method further includes:

[0319] sending third information, wherein the third information is used to indicate the type of the desired DRX period reported.

[0320] In some embodiments, the desired DRX period includes a DRX period of the first type and a DRX period of the second type, and the DRX period of the second type is associated with the same prohibition timer as the DRX period of the first type.

[0321] For a detailed introduction to step S4301, reference may be made to the detailed descriptions of the above embodiments, which will not be elaborated here.

[0322] In the embodiments of the present disclosure, some or all of the steps, and their optional implementation manners, can be arbitrarily combined with some or all of the steps in other embodiments, and can also be arbitrarily combined with the optional implementation manners in other embodiments.

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

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

[0325] The method for implementing how the terminal specifically reports the desired DRX parameters in the present disclosure has the following optional implementation solutions:

[0326] Embodiments of the present disclosure relate to a method for determining discontinuous reception (DRX) parameters. Taking the network device as a base station as an example, the method includes:

[0327] 1. Protect the working mode in which the terminal reports the desired DRX cycle of the second type (the DRX cycle of the second type is a non-integer cycle or a rational number cycle DRX parameter, which is different from the original first type of DRX cycle, that is, an integer cycle) in the connected state:

[0328] a) Among them, the desired DRX cycle includes: preferredDRX-LongCycle, preferredDRX-ShortCycle;

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

[0330] 3. Based on 1, the reported desired long cycle parameter and short cycle parameter of the terminal are of the same type, either the first type (integer cycle) or the second type (non-integer cycle); or of different types. For example, the long cycle is of the first type and the short cycle is of the second type (but it will not occur that the long cycle is of the second type and the short cycle is of the first type);

[0331] 4. Based on 1, the DRX cycles of the first type and the second type cannot be reported simultaneously:

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

[0333] b) The terminal decides whether to report the DRX cycle of the first type or the DRX cycle of the second type according to the implementation (that is, the two different types of DRX cycles cannot be reported simultaneously);

[0334] 5. Based on 1, the protocol stipulates that the terminal determines how to report the desired DRX cycle according to the DRX cycle situation configured by the base station:

[0335] c) As an embodiment, if the base station issues a periodic DRX parameter configuration (that is, configures the DRX cycle of the first type, that is, the integer cycle DRX parameter), the terminal only reports the desired DRX cycle of the first type, that is, reports the integer cycle DRX parameter;

[0336] d) As an example, if the base station sends down an aperiodic DRX parameter configuration (i.e., configures a DRX cycle of the second type, which is a non-integer cycle DRX parameter), the terminal only reports the expected DRX cycle of the second type, that is, reports the DRX parameter with a non-integer cycle;

[0337] e) As an example, if the base station has not sent down a DRX parameter configuration, that is, has not obtained auxiliary information, it can be done through 4.

[0338] 6. Based on 1, the network sends down configuration information to indicate whether the terminal reports the expected DRX cycle of the first type or the expected DRX cycle of the second type:

[0339] a) The base station can indicate that the terminal only reports one type of expected value (either one of the two).

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

[0341] Embodiment 1:

[0342] Use the reserved bit of the existing IE to report the DRX parameter of the second cycle (i.e., use the same prohibited timer as the reporting of the first DRX cycle):

[0343]

[0344] The embodiments of the present disclosure also propose a device for implementing any of the above methods. For example, a device is proposed. The above device includes units or modules for implementing each step executed by the terminal in any of the above methods. Again, another device is proposed, including units or modules for implementing each step executed by a network device (such as RAN, etc.) in any of the above methods.

[0345] It should be understood that the division of each unit or module in the above device is only a division of logical functions. In actual implementation, it can be fully or partially integrated into a physical entity, or physically separated. In addition, the units or modules in the device can 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 instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or the functions of each unit or module of the above device. 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 inside or outside the device. Alternatively, the units or modules in the device can be implemented in the form of a hardware circuit, and the functions of some or all of the units or modules can be implemented by designing the hardware circuit. The above hardware circuit can be understood as one or more processors. For example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are implemented by designing the logical relationship of the components in the circuit. Again, for example, in another implementation, the above hardware circuit can be implemented 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 through a configuration file to implement the functions of some or all of the above units or modules. All units or modules of the above device can be fully implemented in the form of a processor calling software, or fully implemented in the form of a hardware circuit, or partially implemented in the form of a processor calling software, and the remaining part is implemented in the form of a hardware circuit.

[0346] In the embodiments of the present disclosure, a 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), etc.; in another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the above-mentioned hardware circuit is fixed or can be reconfigured. 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 to implement the configuration of the hardware circuit 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] Figure 5A is a schematic structural diagram of a terminal proposed in the embodiments of the present disclosure. As Figure 5A shown, the terminal 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. Among them, the terminal 5100 may include:

[0348] The transceiver module 5101 is configured to receive first information, where the first information is used to report the DRX cycle expected by the terminal, and 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, both the expected long cycle and the expected short cycle are the second type of DRX cycle;

[0351] Alternatively,

[0352] both the desired long cycle and the desired short cycle are DRX cycles of the first type;

[0353] Alternatively,

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

[0355] wherein, the DRX cycle of the first type is an integer cycle.

[0356] Optionally, it further includes:

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

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

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

[0360] when the configured DRX cycle is a DRX cycle of the first type, determine that the desired DRX cycle reported in the first information is a DRX cycle of the first type; or,

[0361] when the configured DRX cycle is a DRX cycle of the second type, determine that the desired DRX cycle reported in the first information is a DRX cycle of the second type.

[0362] Optionally, it further includes:

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

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

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

[0366] Figure 5B It is a schematic structural diagram of a network device proposed by an embodiment of the present disclosure. As Figure 5B shown, the network device 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. Among them, the network device 5200 may include:

[0367] A transceiver module 5201, configured to receive a first piece of information, where the first piece of information is used to report a DRX cycle desired by a terminal, and 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.

[0368] Optionally, 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.

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

[0370] Or,

[0371] both the desired long cycle and the desired short cycle are of the first type of DRX cycle;

[0372] Or,

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

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

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

[0376] send a second piece of information, where the second piece of information is used to configure a DRX cycle.

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

[0378] the configured DRX cycle is of the second type of DRX cycle, and the desired DRX cycle reported in the first piece of information is of the second type of DRX cycle.

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

[0380] send a third piece of information, where the third piece of information is used to indicate the type of the desired DRX cycle reported.

[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 is associated with the same forbidden timer as the first type of DRX cycle.

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

[0383] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the above-mentioned multiple sub-modules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0384] Figure 6A It is a schematic structural diagram of a communication device 6100 proposed in an embodiment of the present disclosure. The communication device 6100 may be a terminal, a network device, a chip, a chip system, or a processor, etc. that supports a terminal to implement any of the above methods, or may also be a chip, a chip system, or a processor, etc. that supports a network device to implement any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments, and specific reference can be made to the descriptions in the above method embodiments.

[0385] As Figure 6A shown, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a dedicated processor, etc. For example, it may be 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 a communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 6100 is used to execute 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 also be 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 executes at least one of the communication steps such as sending and / or receiving in the above methods (such as step S2101, step S2104, step S2201, step S2202, step S2204, but not limited thereto), and the processor 6101 executes other steps (such as step S2102, step S2103, step S2203).

[0388] In some embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver machine, transceiver circuit, etc. may be used interchangeably, terms such as transmitter, transmitter unit, transmitter machine, transmitter circuit, etc. may be used interchangeably, and terms such as receiver, receiver unit, receiver machine, receiver circuit, etc. 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 can be used to receive signals from the memory 6102 or other devices and can be used to send signals to the memory 6102 or other devices. For example, the interface circuit 6104 can read the instructions stored in the memory 6102 and send the instructions to the processor 6101.

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

[0391] Figure 6B is a schematic structural diagram of the chip 6200 proposed in the embodiments of the present disclosure. For the case where the communication device 6100 can be a chip or a chip system, reference can be made to Figure 6B the schematic structural diagram of the chip 6200 shown, but not limited thereto.

[0392] The chip 6200 includes one or more processors 6201, and the chip 6200 is used 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 the interface circuit 6202 can be used to send signals to the memory 6203 or other devices. For example, the interface circuit 6202 can read the instructions stored in the memory 6203 and send the instructions to the processor 6201.

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

[0395] In some embodiments, terms such as interface circuit, interface, transceiver pin, transceiver, etc. can be replaced with each other.

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

[0397] The present disclosure also provides a storage medium. Instructions are stored on the above storage medium. When the above instructions run on the communication device 6100, the communication device 6100 is caused to execute any of the above methods. Optionally, the above storage medium is an electronic storage medium. Optionally, the above storage medium is a computer-readable storage medium, but not limited thereto, and it can also be a storage medium readable by other devices. Optionally, the above storage medium can be a non-transitory storage medium, but not limited thereto, and it can also be a transitory storage medium.

[0398] The present disclosure also provides a program product. When the above program product is executed by the communication device 6100, the communication device 6100 is caused to execute any of the above methods. Optionally, the above program product is a computer program product.

[0399] The present disclosure also provides a computer program. When it runs on a computer, the computer is caused to execute any of the above methods.

Claims

1. A method for determining discontinuous reception (DRX) parameters, characterized in that, the method is executed by a terminal, and the method includes: sending a first message, wherein the first message is used to report the DRX cycle expected by the terminal, and 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; the expected DRX cycle includes at least one of the following: an expected long cycle, an expected short cycle, the expected long cycle is X times the expected short cycle, where X is an integer.

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

3. The method according to claim 1, characterized in that, the method further includes: receiving a second message, wherein the second message is used to configure the DRX cycle; determining the type of the DRX cycle expected reported in the first message according to the configured DRX cycle.

4. The method according to claim 3, characterized in that, the determining the type of the DRX cycle expected reported in the first message according to the configured DRX cycle includes: when the configured DRX cycle is the first type of DRX cycle, determining that the DRX cycle expected reported in the first message is the first type of DRX cycle; or, when the configured DRX cycle is the second type of DRX cycle, determining that the DRX cycle expected reported in the first message is the second type of DRX cycle.

5. The method according to any one of claims 1-4, characterized in that, the method further includes: receiving a third message, wherein the third message is used to indicate the type of the DRX cycle expected reported; determining the type of the DRX cycle expected reported in the first message according to the third message.

6. The method according to any one of claims 1-4, characterized in that, 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 is associated with the same prohibited timer as the first type of DRX cycle.

7. A method for determining discontinuous reception (DRX) parameters, characterized in that, the method is executed by a network device, and the method includes: receiving a first message, wherein the first message is used to report the DRX cycle expected by a terminal, and 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; The desired DRX cycle includes at least one of the following: a desired long cycle, a desired short cycle, where the desired long cycle is X times the desired short cycle, and X is an integer.

8. The method according to claim 7, wherein, both the desired long cycle and the desired short cycle are DRX cycles of a second type; or, both the desired long cycle and the desired short cycle are DRX cycles of a first type; or, the desired long cycle is a DRX cycle of a first type, and the desired short cycle is a DRX cycle of a second type; wherein, the DRX cycle of the first type is an integer cycle.

9. The method according to claim 7, wherein, the method further includes: sending second information, where the second information is used to configure the DRX cycle.

10. The method according to claim 9, wherein, the configured DRX cycle is a DRX cycle of a first type, and the desired DRX cycle reported in the first information is a DRX cycle of a first type; or, the configured DRX cycle is a DRX cycle of a second type, and the desired DRX cycle reported in the first information is a DRX cycle of a second type.

11. The method according to any one of claims 7-10, wherein, the method further includes: sending third information, where the third information is used to indicate the type of the desired DRX cycle reported.

12. The method according to any one of claims 7-10, wherein, the desired DRX cycle includes a DRX cycle of a first type and a DRX cycle of a second type, and the DRX cycle of the second type is associated with the same prohibition timer as the DRX cycle of the first type.

13. A terminal, wherein, the terminal includes: a transceiver module, configured to receive first information, where the first information is used to report a desired DRX cycle of the terminal, where the desired DRX cycle includes a DRX cycle of a first type and / or a DRX cycle of a second type, the DRX cycle of the first type is an integer cycle, and the DRX cycle of the second type is a non-integer cycle; The desired DRX cycle includes at least one of the following: a desired long cycle, a desired short cycle, where the desired long cycle is X times the desired short cycle, and X is an integer.

14. A network device, wherein, the network device includes: a transceiver module, configured to receive first information, where the first information is used to report a desired DRX cycle of the terminal, where the desired DRX cycle includes a DRX cycle of a first type and / or a DRX cycle of a second type, the DRX cycle of the first type is an integer cycle, and the DRX cycle of the second type is a non-integer cycle; The desired DRX cycle includes at least one of the following: a desired long cycle, a desired short cycle, where the desired long cycle is X times the desired short cycle, and X is an integer.

15. A communication device, wherein, includes: one or more processors; Among them, the processor is used to execute the method for determining discontinuous reception (DRX) parameters according to any one of claims 1-12.

16. A storage medium storing instructions, characterized in that when the instructions run on a communication device, the communication device is caused to execute the method for determining discontinuous reception (DRX) parameters according to any one of claims 1-12.

Images