Communication method, communication apparatus, device, communication system, and storage medium

Abstract

Embodiments of the present disclosure provide a communication method, a communication apparatus, a device, a communication system, and a storage medium. The communication method comprises: sending a DRX parameter, wherein the DRX parameter is used for indicating a first DRX cycle of a terminal, and the value of the first DRX cycle is a fraction. According to the technical solution provided by the embodiments of the present disclosure, the DRX cycle is more flexible, so that a downlink service with a fractional cycle is supported, and power consumption of the terminal is reduced.

Description

Communication method, communication device, equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to communication methods, communication devices, equipment, communication systems, and storage media. Background Art

[0002] In a communication system, network equipment can configure discontinuous reception (DRX) for terminals, allowing them to enter DRX operation when there are no scheduled transmissions for a period of time. Under the DRX mechanism, terminals periodically wake up to monitor the physical downlink control channel (PDCCH), thereby saving power.

[0003] Summary of the Invention

[0004] In DRX operation, the terminal sends a fractional DRX cycle to the network to make the DRX cycle more flexible, thereby supporting downlink services with a fractional cycle and saving power consumption of the terminal.

[0005] Embodiments of the present disclosure provide a communication method, a communication apparatus, a device, a communication system, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a terminal. The method includes: sending a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a network device. The method includes: receiving a DRX parameter, the DRX parameter being used to indicate a first DRX cycle of a terminal, wherein the first DRX cycle value is a fraction.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a communication system. The method includes: a terminal sending a DRX parameter to a network device, where the DRX parameter is used to indicate a first DRX cycle of the terminal, where the first DRX cycle value is a fraction; and the network device sending downlink information to the terminal according to the DRX parameter and the first DRX cycle.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a terminal is provided, comprising: a sending module, configured to send a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a network device is provided, comprising: a receiving module configured to receive a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of a terminal, wherein the first DRX cycle value is a fraction.

[0011] According to a sixth aspect of the embodiments of the present disclosure, a communication device is provided. The communication device includes one or more processors, wherein the processor is configured to execute the communication method as described in any one of the first aspect and its embodiments by calling instructions.

[0012] According to a seventh aspect of the embodiments of the present disclosure, a communication device is provided. The communication device includes one or more processors, wherein the processor is configured to execute the communication method as described in any one of the second aspect and its embodiments by calling instructions.

[0013] According to an eighth aspect of the embodiments of the present disclosure, a communication system is provided. The communication system includes a terminal and a network device; the terminal is configured to implement the communication method as described in any one of the first aspect and its embodiments; and the network device is configured to implement the communication method as described in any one of the second aspect and its embodiments.

[0014] According to a ninth aspect of the embodiments of the present disclosure, a storage medium is provided, wherein instructions are stored in the storage medium; when the instructions are executed on a processor, the processor executes the communication method as described in any one of the first aspect, the second aspect, and the embodiments thereof.

[0015] According to a tenth aspect of the embodiments of the present disclosure, a computer program or computer program product is provided. The computer program or computer program product includes code. When the instructions are executed by a processor, the communication method as described in any one of the first aspect, the second aspect, and the embodiments thereof is performed.

[0016] The technical solution provided by the embodiments of the present disclosure makes the DRX cycle more flexible, thereby supporting downlink services with fractional cycles and saving power consumption of the terminal.

[0017] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not constitute limitations on the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0019] FIG1 is a schematic diagram of an architecture of a communication system provided according to an embodiment of the present disclosure.

[0020] FIG2 is a schematic diagram of a DRX cycle provided according to an embodiment of the present disclosure.

[0021] FIG3 is a schematic diagram of XR service arrival according to an embodiment of the present disclosure.

[0022] FIG4 is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.

[0023] FIG5 is a flow chart of a method for executing communication on a terminal side according to an embodiment of the present disclosure.

[0024] FIG6 is a flow chart of a communication method executed on a network device side according to an embodiment of the present disclosure.

[0025] FIG7 is another interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.

[0026] FIG8 is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0027] FIG9 is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] Embodiments of the present disclosure provide a communication method, a communication apparatus, a device, a communication system, and a storage medium.

[0029] In a first aspect, an embodiment of the present disclosure provides a communication method, which is executed by a terminal. The method includes: sending a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

[0030] In the disclosed embodiments, the terminal sends DRX parameters to indicate to the network that the DRX cycle value is a fractional DRX cycle, allowing the network to perform downlink transmissions based on the DRX cycle reported by the terminal. This makes the DRX cycle more flexible, supporting downlink services with fractional cycles and saving power consumption in the terminal.

[0031] In combination with some embodiments of the first aspect, the first DRX cycle value is a fraction, and the DRX parameter includes at least one of a first field and a second field, wherein the first field is the numerator of the first DRX cycle value and the second field is the denominator of the first DRX cycle value.

[0032] In the embodiment of the present disclosure, the terminal indicates the numerator and denominator of the DRX cycle value respectively through two fields in the DRX parameter, so as to indicate the DRX cycle whose DRX cycle value is a fraction.

[0033] In combination with some embodiments of the first aspect, the numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration.

[0034] With reference to some embodiments of the first aspect, the first DRX cycle is a DRX long cycle or a DRX short cycle.

[0035] In combination with some embodiments of the first aspect, the DRX parameter is further used to indicate a second DRX cycle of the terminal, where the second DRX cycle value is a fraction.

[0036] In the disclosed embodiments, the terminal sends DRX parameters to indicate to the network that the DRX cycle value is a fractional number of DRX cycles, allowing the network to perform downlink transmissions based on the multiple DRX cycles reported by the terminal. This makes the DRX cycle more flexible, supporting downlink services with fractional cycles and saving power consumption in the terminal.

[0037] In combination with some embodiments of the first aspect, the DRX parameter further includes at least one of a third field and a fourth field, the third field is the numerator of the second DRX cycle value, and the fourth field is the denominator of the second DRX cycle value.

[0038] In combination with some embodiments of the first aspect, the first DRX cycle is a DRX long cycle, the DRX parameter is further used to indicate a DRX short cycle of the terminal, and the DRX long cycle value is an integer multiple of the DRX short cycle value.

[0039] In combination with some embodiments of the first aspect, the above method includes: sending first information, where the first information is used to indicate whether the terminal supports sending a DRX cycle with a DRX cycle value as a fraction.

[0040] In the embodiment of the present disclosure, the terminal reports to the network device whether it supports a DRX cycle indicating a fractional DRX cycle value, so that the network device can allocate reasonable resources to the terminal according to the terminal's capabilities, thereby avoiding waste of system resources.

[0041] In combination with some embodiments of the first aspect, the above method includes: determining that the terminal supports sending a DRX cycle with a DRX cycle value as a fraction under at least one of the following conditions: supporting sending expected DRX parameters; supporting a DRX cycle with a DRX cycle value as a fraction.

[0042] In a second aspect, an embodiment of the present disclosure provides a communication method, which is executed by a network device. The method includes: receiving a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of a terminal, wherein the first DRX cycle value is a fraction.

[0043] In combination with some embodiments of the second aspect, the DRX parameter includes at least one of a first field and a second field, wherein the first field is a numerator of the first DRX cycle value and the second field is a denominator of the first DRX cycle value.

[0044] In combination with some embodiments of the second aspect, the numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration.

[0045] In combination with some embodiments of the second aspect, the first DRX cycle is a DRX long cycle or a DRX short cycle.

[0046] In combination with some embodiments of the second aspect, the DRX parameter is further used to indicate a second DRX cycle of the terminal, where the second DRX cycle value is a fraction.

[0047] In combination with some embodiments of the second aspect, the DRX parameter further includes at least one of a third field and a fourth field, the third field is the numerator of the second DRX cycle value, and the fourth field is the denominator of the second DRX cycle value.

[0048] In combination with some embodiments of the second aspect, the first DRX cycle is a DRX long cycle, the DRX parameter is further used to indicate a DRX short cycle of the terminal, and the DRX long cycle value is an integer multiple of the DRX short cycle value.

[0049] In combination with some embodiments of the second aspect, the method further includes: receiving first information, where the first information is used to indicate whether the terminal supports sending a DRX cycle with a DRX cycle value being a fraction.

[0050] In a third aspect, an embodiment of the present disclosure provides a communication method, which is executed by a communication system, and the method includes: the terminal sends a DRX parameter to a network device, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction; the network device sends downlink information to the terminal according to the DRX parameter and the first DRX cycle.

[0051] In a fourth aspect, an embodiment of the present disclosure provides a terminal, including: a sending module, configured to send a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

[0052] In combination with some embodiments of the fourth aspect, the sending module is used to send a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

[0053] In combination with some embodiments of the fourth aspect, the first DRX cycle value is a fraction, and the DRX parameter includes at least one of a first field and a second field, wherein the first field is the numerator of the first DRX cycle value and the second field is the denominator of the first DRX cycle value.

[0054] In combination with some embodiments of the fourth aspect, the numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration.

[0055] In combination with some embodiments of the fourth aspect, the first DRX cycle is a DRX long cycle or a DRX short cycle.

[0056] In combination with some embodiments of the fourth aspect, the DRX parameter is further used to indicate a second DRX cycle of the terminal, where the second DRX cycle value is a fraction.

[0057] In combination with some embodiments of the fourth aspect, the DRX parameter further includes at least one of a third field and a fourth field, the third field is the numerator of the second DRX cycle value, and the fourth field is the denominator of the second DRX cycle value.

[0058] In combination with some embodiments of the fourth aspect, the first DRX cycle is a DRX long cycle, the DRX parameter is further used to indicate a DRX short cycle of the terminal, and the DRX long cycle value is an integer multiple of the DRX short cycle value.

[0059] In combination with some embodiments of the fourth aspect, the sending module is further used to send first information, where the first information is used to indicate whether the terminal supports sending a DRX cycle with a DRX cycle value being a fraction.

[0060] In combination with some embodiments of the fourth aspect, the processing module is used to determine that the terminal supports sending a DRX cycle with a DRX cycle value as a fraction when at least one of the following is met: supporting sending expected DRX parameters; supporting a DRX cycle with a DRX cycle value as a fraction.

[0061] In a fifth aspect, an embodiment of the present disclosure provides a network device, including: a receiving module, configured to receive a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of a terminal, wherein the first DRX cycle value is a fraction.

[0062] In combination with some embodiments of the fifth aspect, the receiving module is used to receive a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

[0063] In combination with some embodiments of the fifth aspect, the DRX parameter includes at least one of a first field and a second field, wherein the first field is the numerator of the first DRX cycle value and the second field is the denominator of the first DRX cycle value.

[0064] In combination with some embodiments of the fifth aspect, the numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration.

[0065] In combination with some embodiments of the fifth aspect, the first DRX cycle is a DRX long cycle or a DRX short cycle.

[0066] In combination with some embodiments of the fifth aspect, the DRX parameter is further used to indicate a second DRX cycle of the terminal, where the second DRX cycle value is a fraction.

[0067] In combination with some embodiments of the fifth aspect, the DRX parameter also includes at least one of a third field and a fourth field, the third field is the numerator of the second DRX cycle value, and the fourth field is the denominator of the second DRX cycle value.

[0068] In combination with some embodiments of the fifth aspect, the first DRX cycle is a DRX long cycle, the DRX parameter is also used to indicate a DRX short cycle of the terminal, and the DRX long cycle value is an integer multiple of the DRX short cycle value.

[0069] In combination with some embodiments of the fifth aspect, the receiving module is further used to receive first information, where the first information is used to indicate whether the terminal supports sending a DRX cycle with a DRX cycle value as a fraction.

[0070] In a sixth aspect, an embodiment of the present disclosure provides a communication device, comprising: one or more processors; the processor is configured to execute the communication method as described in any one of the first aspect and its embodiments by calling instructions.

[0071] In a seventh aspect, an embodiment of the present disclosure provides a communication device, comprising: one or more processors; the processor is configured to execute the communication method as described in any one of the second aspect and its embodiments by calling instructions.

[0072] In the eighth aspect, an embodiment of the present disclosure provides a communication system, comprising: a terminal and a network device; the terminal is configured to implement the communication method as described in any one of the first aspect and its embodiments; the network device is configured to implement the communication method as described in any one of the second aspect and its embodiments.

[0073] In a ninth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions; when the instructions are executed on a processor, the processor executes the communication method as described in any one of the first aspect, the second aspect and their embodiments.

[0074] In a tenth aspect, embodiments of the present disclosure provide a computer program or computer program product. The computer program or computer program product includes code. When executed by a processor, the instructions perform the communication method as described in any one of the first aspect, the second aspect, and the embodiments thereof.

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

[0076] The present disclosure provides a communication method, communication device, equipment, communication system, and storage medium. In some embodiments, the terms "communication method" and "information processing method" and "information transmission method" are interchangeable; the terms "communication device" and "information processing device" and "information transmission device" are interchangeable; and the terms "communication system" and "information processing system" are interchangeable.

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

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

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

[0080] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the",

[0081] "Above", "said", "the aforementioned", "this", etc. can mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article can be understood as a singular expression or a plural expression.

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

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

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

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

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

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

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

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

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

[0091] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0092] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", "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)" and the like may be used interchangeably.

[0093] In some embodiments, the terms “terminal,” “terminal device,” “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,” and the like may be used interchangeably.

[0094] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0095] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

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

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

[0098] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0099] As shown in FIG1 , FIG1 is a schematic diagram of an architecture of a communication system provided according to an embodiment of the present disclosure. A communication system 100 includes a terminal 101 and a network device 102 .

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

[0101] In some embodiments, the network device 102 may include an access network device and / or a core network device. In some embodiments, the network device 102 may be, 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), a next generation evolved NodeB (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.

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

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

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

[0105] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0106] 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, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), 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) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0107] First, concepts involved in the implementation of the present disclosure are explained.

[0108] 1. DRX

[0109] DRX (discontinuous reception) allows the terminal to periodically enter sleep mode and not monitor the control channel (i.e., downlink control channel) sent by the network (such as the base station). When monitoring is needed, the terminal wakes up from sleep mode, which saves power.

[0110] In some embodiments, in the above-mentioned communication system, to save power consumption of the terminal, a DRX mechanism is introduced. That is, when the terminal is in a connected state, it does not need to continuously monitor the control channel (i.e., the downlink control channel) sent by the network (e.g., a base station), but instead monitors the downlink control channel intermittently. In a DRX cycle, the on duration represents the time period during which the terminal monitors the control channel, during which the radio frequency channel is turned on and continuously monitors the control channel. Except for the on duration, the terminal is in a power-saving state during which the radio frequency channel is turned off. The on duration occurs periodically, and the specific period is implemented by network configuration. While achieving terminal power saving, to avoid excessive transmission delay between the network and the terminal, the DRX cycle introduces the concepts of long cycles and short cycles. During the long or short cycles, the terminal enters an inactive state and does not need to continuously monitor the downlink control channel. As shown in FIG2 , FIG2 is a schematic diagram of a DRX cycle provided according to an embodiment of the present disclosure, wherein (a) represents a long DRX cycle and (b) represents a short DRX cycle. In a short cycle, the on duration occurs more frequently than in a long cycle. In some embodiments, if the terminal is configured with both a long cycle and a short cycle, then after the short cycle ends, the terminal monitors according to the long cycle.

[0111] The starting position of the on duration in the DRX long cycle or short cycle is as follows:

[0112] 1> If the DRX short cycle is used for the DRX group, the DRX short cycle satisfies the following formula:

[0113] [(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle);

[0114] SFN (system frame number) is the system frame number, subframe number is the subframe number, drx-ShortCycle is the DRX short cycle, drx-StartOffset is the subframe at which the DRX long cycle and DRX short cycle start, and "modulo" is the modulo operation.

[0115] (1>if the Short DRX cycle is used for a DRX group,and[(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle)).

[0116] 2> After a time delay (drx SlotOffset) of starting the duration timer (drx onDurationTimer) from the start of the subframe, start the drx onDurationTimer of the DRX group.

[0117] (2>start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.)

[0118] 1> If the DRX long cycle is used for the DRX group, the DRX long cycle satisfies the following formula:

[0119] [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset;

[0120] Among them, drx-LongCycle is the DRX long cycle.

[0121] (1>if the Long DRX cycle is used for a DRX group,and[(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset).

[0122] 2> After drx SlotOffset from the start of the subframe, start drx onDurationTimer for this DRX group.

[0123] (2>start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe).

[0124] In some embodiments, DRX may include the following timers (see general DRX configuration parameters):

[0125] drx-onDurationTimer: duration at the start of the DRX cycle;

[0126] drx-SlotOffset: Delay before starting drx-onDurationTimer;

[0127] drx-InactivityTimer: For the current multimedia access control (MAC) entity, the duration after the PDCCH indicates a new uplink or downlink transmission;

[0128] drx-RetransmissionTimerDL (for each downlink hybrid automatic repeat request process except broadcast): the maximum duration until a downlink retransmission is received;

[0129] drx-RetHARQransmissionTimerUL (for each uplink HARQ process): the maximum duration until an uplink grant for uplink retransmission is received;

[0130] drx-LongCycleStartOffset: includes the DRX long cycle (drx-LongCycle) and drx-StartOffset. drx-StartOffset is the subframe where the DRX long cycle and short cycle start.

[0131] drx-ShortCycle (optional): DRX short cycle;

[0132] drx-ShortCycleTimer (optional): The duration of the DRX short cycle used by the terminal;

[0133] drx-HARQ-RTT-TimerDL (for each downlink HARQ except broadcast): the minimum duration before the MAC entity expects to receive downlink resource allocation control signaling for downlink HARQ retransmission;

[0134] drx-HARQ-RTT-TimerUL (for each uplink HARQ process): the minimum duration that the MAC entity expects to receive uplink grant signaling for uplink HARQ retransmission;

[0135] The value range of drx-LongCycle is: 10ms, 20ms, 32ms, 40ms, 60ms, 64ms, 70ms, 80ms, 128ms, 160ms, 256ms, 320ms, 512ms, 640ms, 1024ms, 1280ms, 2048ms, 2560ms, 5120ms, and 10240ms, where "ms" stands for milliseconds.

[0136] The value range of drx-ShortCycle is 2ms, 3ms, 4ms, 5ms, 6ms, 7ms, 8ms, 10ms, 14ms, 16ms, 20ms, 30ms, 32ms, 35ms, 40ms, 64ms, 80ms, 128ms, 160ms, 256ms, 320ms, 512ms, and 640ms.

[0137] Currently, the 3GPP standard only supports DRX cycles that are integers. This means that DRX cycles (including DRX long and DRX short cycles) are integer cycles, i.e., DRX cycle values ​​are integers. Here, "integer" can be interchangeably used with "integer value" or "integer milliseconds."

[0138] 2. Extended Reality (XR) Business

[0139] In wireless communication networks, XR technology offers advantages such as multi-perspective and strong interactivity, providing users with a brand-new visual experience and possessing enormous application value and commercial potential. XR encompasses virtual reality (VR), augmented reality (AR), and cloud gaming (CG). Typical XR services are characterized by fixed frame rates, with services arriving at terminals at fixed intervals. For example, AR / VR: 60 frames per second (fps), meaning one video frame appears every 16.66 milliseconds (ms), at rates of 20 Mbps, 45 Mbps, etc.; 120 fps, meaning one video frame appears every 8.33 ms. The air interface transmission delay budget for a complete video frame is 10 ms. CG: 60 or 120 fps, at rates of 8 Mbps, 30 Mbps, etc., meaning one video frame appears every 15 ms. However, there will be additional delay jitter beyond this fixed period, causing the actual data service to arrive at the terminal earlier or later. Figure 3 shows a schematic diagram of XR service arrival according to an embodiment of the present disclosure. For example, a frame rate of 60 fps, with a period of 16.67 ms and a jitter range of [4, -4] ms, is shown.

[0140] In the embodiments of the present disclosure, for services with non-integer periods, such as XR services, a fraction is introduced to represent the period of the XR service. In this case, when the network configures the terminal, 50 / 3 can be used to express 16.67ms, that is, 3 frames in 50ms, and the frame rate is 60fps. In some embodiments, 100 / 3, 200 / 9, 125 / 9, 100 / 9, and 25 / 3 can be used to indicate frame rates such as 30fps, 45fps, 72fps, 90fps, and 120fps, respectively.

[0141] In some embodiments, "non-integer" can be interchanged with "fraction", "fractional value", "non-integer milliseconds", etc.

[0142] In some embodiments, "non-integer period" can be replaced with "non-integer value period", "fractional period", "fractional value period", "non-integer millisecond period", "period with non-integer period value", "period with fractional period value", "period with non-integer millisecond period value", "period with non-integer length value", "period with fractional length value", "period with non-integer millisecond length value", etc.

[0143] In some embodiments, since the period of the XR service can be an integer or a non-integer, the period of the XR service can be understood as a rational number.

[0144] In some embodiments, the DRX cycle may be configured based on rational numbers.

[0145] However, for the terminal, currently the terminal can autonomously send its desired DRX parameters (ie, DRX-Preference) to the base station. However, the DRX parameters sent by the terminal do not take non-integer periodic reporting into consideration, so a new solution is needed.

[0146] As shown in Figure 4, Figure 4 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a method that can be applied to a communication system 100, wherein the network device 102 can be an access network device. The method can include steps S410 to S440.

[0147] In step S410 , the terminal 101 sends first information to the network device 102 .

[0148] In some embodiments, network device 102 may receive first information.

[0149] In some embodiments, terminal 101 is in a radio resource control (RRC) connected state.

[0150] In some embodiments, the first information is used to indicate whether the terminal 101 supports the capability of sending a DRX cycle with a DRX cycle value being a fraction.

[0151] In some embodiments, a DRX cycle with a fractional DRX cycle value may be described as a second type of DRX cycle to distinguish it from a first type of DRX cycle, i.e., a DRX cycle with an integer DRX cycle value. In some embodiments, the first information is used to indicate whether the terminal 101 has the capability to send a DRX cycle with a fractional DRX cycle value.

[0152] In some embodiments, the DRX cycle with a fractional DRX cycle value may be described as a DRX cycle with a fractional period value, a DRX cycle with a fractional length value, and the like.

[0153] In some embodiments, the first information is used to indicate the terminal 101's ability to support a DRX cycle with a fractional transmission cycle value.

[0154] In some embodiments, the first information is used to indicate that the terminal 101 supports the ability to send a DRX cycle with a fractional cycle value or an expected DRX cycle; or, the first information is used to indicate that the terminal 101 does not support the ability to send a DRX cycle with a fractional cycle value or an expected DRX cycle.

[0155] In some embodiments, the DRX cycle with a fractional cycle value is the DRX cycle expected by the terminal 101 .

[0156] In some embodiments, a DRX cycle with a fractional cycle value may be described as a desired DRX cycle with a fractional cycle value.

[0157] In some embodiments, the first information is used to indicate whether the terminal 101 supports the capability of sending a desired DRX cycle with a cycle value being a fraction.

[0158] In some embodiments, the first information is used to indicate the terminal 101's ability to support an expected DRX cycle with a fractional transmission cycle value.

[0159] In some embodiments, the first information is used to indicate whether the terminal 101 has the capability of sending a desired DRX cycle with a cycle value being a fraction.

[0160] In some embodiments, the first information is used to indicate that the terminal 101 supports the expected DRX cycle with a sending cycle value of a fraction; or, the first information is used to indicate that the terminal 101 does not support the expected DRX cycle with a sending cycle value of a fraction.

[0161] In some embodiments, a DRX cycle with a fractional cycle value may also be described as a DRX cycle with a rational length value or an expected DRX cycle with a rational length value.

[0162] In some embodiments, the DRX cycle whose length value is a rational number or the expected DRX cycle whose length value is a rational number is an expected rational number DRX parameter of the terminal 101 (such as drx-Preference-rational).

[0163] In some embodiments, the first information is used to indicate whether the terminal 101 supports sending a DRX cycle whose length value is a rational number, or is used to indicate an expected DRX cycle whose length value is a rational number.

[0164] In some embodiments, the first information is used to indicate the terminal 101's ability to support a DRX cycle whose length value is a rational number, or to indicate the terminal 101's ability to support an expected DRX cycle whose length value is a rational number.

[0165] In some embodiments, the first information is used to indicate whether the terminal 101 has the capability to send a DRX cycle whose length value is a rational number, or to indicate whether the terminal 101 has the capability to send an expected DRX cycle whose length value is a rational number.

[0166] In some embodiments, if the terminal has the capability to send drx-Preference-rational to the network device, it indicates that the terminal supports sending the desired DRX cycle with a fractional cycle value. If the terminal does not have the capability to send drx-Preference-rational to the network device, it indicates that the terminal does not support sending the desired DRX cycle with a fractional cycle value.

[0167] In some embodiments, the first information may be carried in terminal capability information (eg, UECapabilityinformation).

[0168] In some embodiments, before step S410, terminal 101 receives third information sent by network device 102, where the third information is used to instruct terminal 101 to report its own capabilities. Exemplarily, the third information is terminal capability query (eg, UECapabilityEnquiry) information.

[0169] In some embodiments, the terminal capability information may be sent to the network device in response to a terminal capability query (eg, UECapabilityEnquiry) message sent by the network device.

[0170] In some embodiments, before step S410 , the terminal 101 determines whether to support sending a DRX cycle with a fractional cycle value or an expected DRX cycle with a fractional cycle value.

[0171] In some embodiments, the terminal 101 determines whether to support sending a DRX cycle with a fractional cycle value or an expected DRX cycle with a fractional cycle value when at least one of the following conditions is met: the terminal 101 supports sending expected DRX parameters, and the terminal 101 supports a DRX cycle with a fractional cycle value.

[0172] In some embodiments, the terminal 101 supports sending the expected DRX parameters, which means that the terminal 101 supports sending the expected DRX parameters (such as drx-Preference) to the network device 102, that is, the terminal 101 supports reporting the expected DRX parameters.

[0173] In some embodiments, the terminal 101 supports a DRX cycle with a cycle value of a fraction, which means that the terminal 101 supports working using a DRX cycle with a cycle value of a fraction.

[0174] In some embodiments, a precondition for the terminal 101 to determine that it supports sending a DRX cycle with a fractional cycle value or a desired DRX cycle with a fractional cycle value may be that the terminal 101 supports sending a desired DRX parameter (such as drx-Preference). Exemplarily, the terminal 101 determines that it supports sending the desired DRX parameter, and the terminal 101 determines that it supports sending a DRX cycle with a fractional cycle value or a desired DRX cycle with a fractional cycle value.

[0175] In some embodiments, terminal 101 may optionally report support for DRX cycles with fractional transmission cycle values ​​or expected DRX cycles with fractional transmission cycle values. It is understandable that some terminals support reporting the expected DRX cycle, but may not necessarily support DRX cycles with fractional transmission cycle values ​​or expected DRX cycles with fractional transmission cycle values, as this depends on the implementation of terminal 101. Therefore, only if terminal 101 reports the capability to support DRX cycles with fractional transmission cycle values ​​or expected DRX cycles with fractional transmission cycle values ​​can network device 102 configure it to report DRX cycles with fractional transmission cycle values ​​or expected DRX cycles with fractional transmission cycle values. For terminals 101 that do not report the capability to support DRX cycles with fractional transmission cycle values ​​or expected DRX cycles with fractional transmission cycle values, network device 102 may not configure it to report DRX cycles with fractional transmission cycle values ​​or expected DRX cycles with fractional transmission cycle values.

[0176] In some embodiments, terminal 101 supports sending a drx-Preference, which can indicate the terminal 101's desired DRX cycle. Under this premise, the terminal determines whether it supports sending a drx-Preference-rational. For example, the drx-Preference-rational can indicate the desired DRX cycle with a cycle value of a fraction. If supported, the drx-Preference-rational can be sent to the network device. If not supported, the drx-Preference-rational is not sent to the network device.

[0177] In some embodiments, a precondition for the terminal 101 to determine that it supports a DRX cycle with a fractional transmission cycle value or an expected DRX cycle with a fractional cycle value may be: supporting a DRX cycle with a fractional cycle value. Exemplarily, the terminal 101 determines that it supports a DRX cycle with a fractional transmission cycle value, and the terminal 101 determines that it supports a DRX cycle with a fractional transmission cycle value or an expected DRX cycle with a fractional cycle value.

[0178] In some embodiments, only terminals that originally support a DRX cycle with a cycle value of fractions can choose to report their expected DRX cycle with a supported transmission cycle value of fractions.

[0179] In some embodiments, terminal 101 supports a DRX cycle with a fractional cycle value or an expected DRX cycle with a fractional cycle value. Under this premise, the terminal determines whether it supports sending a drx-preference-rational. If supported, the drx-preference-rational may be sent to the network device. If not supported, the drx-preference-rational is not sent to the network device.

[0180] In some embodiments, a precondition for the terminal 101 to determine that it supports sending a DRX cycle with a fractional cycle value may be that the terminal 101 supports sending desired DRX parameters (such as drx-Preference) and that the terminal 101 supports DRX cycles with fractional cycle values. Exemplarily, the terminal 101 first determines that it supports sending the desired DRX parameters and that it supports DRX cycles with fractional cycle values, and then the terminal 101 determines whether it supports sending a DRX cycle with a fractional cycle value or an expected DRX cycle with a fractional cycle value.

[0181] In some embodiments, only terminals that originally support the DRX parameters expected by the transmitting terminal and also support DRX cycles with fractional cycle values ​​can choose to report their expected DRX cycles with fractional transmission cycle values.

[0182] In some embodiments, if terminal 101 supports sending drx-preferences and supports fractional DRX cycles, the terminal determines whether it supports sending drx-preference-rational. If so, the terminal may send the drx-preference-rational to the network device. If not, the terminal does not send the drx-preference-rational to the network device.

[0183] For example, referring to the following table, the UECapabilityInformation IE may include two fields: drx-Preference and drx-Preference-rational.

[0184] Table 1

[0185] Wherein, drx-Preference-r16 is the desired DRX parameter, which is used to indicate whether the UE supports providing its desired DRX parameters for the cell group for energy saving in the RRC connected state (RRC_CONNECTED), as specified in TS 38.331[9].

[0186] drx-Preference-rational-r18 is a rational number of desired DRX parameters used to indicate whether the UE supports providing its preference for rational number DRX parameters for the cell group for energy saving in RRC_CONNECTED, as specified in TS 38.331 [9]. The UE can indicate support for drx-Preference-rational-r18 only if the UE supports drx-Preference-r16.

[0187] Per indicates the configuration granularity of drx-Preference-r16 and drx-Preference-rational-r18. "UE" indicates that drx-Preference-r16 and drx-Preference-rational-r18 are applied to each UE, that is, they are configured per UE.

[0188] M stands for mandatory, indicating whether a field is required. "NO" indicates that the field is optional.

[0189] FDD-TDD DIFF indicates whether there is a difference between time division multiplexing and frequency division multiplexing. "No" indicates no difference.

[0190] FR1-FR2DIFF indicates whether there is a difference in frequency division between frequency bands FR1 and FR2. "No" indicates no difference.

[0191] In step S420 , the network device 102 sends second information to the terminal 101 .

[0192] In some embodiments, terminal 101 may receive second information.

[0193] In some embodiments, the second information is configuration information of desired DRX parameters sent by the terminal 101 to the network device 102 .

[0194] In some embodiments, the second information is configured by the network device 102 for the terminal 101 according to the first information.

[0195] In some embodiments, the second information is used to instruct the terminal 101 to send the DRX parameters expected by the terminal to the network device 102 .

[0196] In step S430 , the terminal 101 sends DRX parameters to the network device 102 .

[0197] In some embodiments, network device 102 may receive DRX parameters.

[0198] In some embodiments, the DRX parameters sent by the terminal 101 may also be described as expected DRX parameters.

[0199] In some embodiments, the DRX parameters are carried in terminal assistance information, such as UEAssistanceInformation.

[0200] In some embodiments, the DRX parameter is used to indicate a DRX cycle of the terminal 101 , where the DRX cycle includes at least one of a DRX long cycle and a DRX short cycle.

[0201] In some embodiments, the DRX parameter is used to indicate a DRX cycle desired by the terminal 101 , where the desired DRX cycle includes at least one of a desired DRX long cycle and a desired DRX short cycle.

[0202] In some embodiments, the DRX parameter is used to indicate at least one of a DRX long cycle (or an expected DRX long cycle) and a DRX short cycle (or an expected DRX short cycle) of the terminal 101 .

[0203] In some embodiments, the DRX parameter is used to indicate the DRX long cycle (or the expected DRX long cycle) or the DRX short cycle (or the expected DRX short cycle) of the terminal 101. In this case, the DRX parameter is used to indicate the first DRX cycle of the terminal 101, and the first DRX cycle is the DRX long cycle or the DRX short cycle; or, the first DRX cycle is the expected DRX long cycle or the expected DRX short cycle.

[0204] In some embodiments, the DRX parameter is used to indicate the DRX long cycle (or the expected DRX long cycle) of the terminal 101. In this case, the DRX short cycle (or the expected DRX short cycle) is an optional configuration.

[0205] In some embodiments, the DRX parameter is used to indicate the DRX long cycle and DRX short cycle of the terminal 101. In this case, the DRX parameter is used to indicate the first DRX cycle and the second DRX cycle of the terminal 101. The first DRX cycle is one of the DRX long cycle and the DRX short cycle, and the second DRX cycle is the other of the DRX long cycle and the DRX short cycle. Exemplarily, the first DRX cycle may be the DRX long cycle, and the second DRX cycle may be the DRX short cycle; or, the first DRX cycle is the DRX short cycle, and the second DRX cycle is the DRX long cycle.

[0206] In some embodiments, the DRX parameter is used to indicate the desired DRX long cycle and the desired DRX short cycle of the terminal 101. In this case, the DRX parameter is used to indicate the first DRX cycle and the second DRX cycle of the terminal 101. The first DRX cycle is one of the desired DRX long cycle and the desired DRX short cycle, and the second DRX cycle is the other of the desired DRX long cycle and the desired DRX short cycle. Exemplarily, the first DRX cycle may be the desired DRX long cycle, and the second DRX cycle may be the desired DRX short cycle; or, the first DRX cycle may be the desired DRX short cycle, and the second DRX cycle may be the desired DRX long cycle.

[0207] In some embodiments, the DRX long cycle may be the preferredDRX-LongCycle in the DRX-Preference-rational, or the DRX short cycle may be the preferredDRX-ShortCycle in the DRX-Preference-rational.

[0208] In some embodiments, the DRX parameter is used to indicate a first DRX cycle of the terminal 101 , and the first DRX cycle value is different from the DRX cycle value of the last transmission.

[0209] In some embodiments, the period value of the DRX cycle can be interchanged with terms such as value of DRX cycle, DRX cycle value, DRX cycle length, and DRX cycle length value.

[0210] For example, the period value of the first DRX cycle can be described as a first DRX cycle value, a first DRX cycle length, a first DRX cycle length value, etc. The period value of the second DRX cycle can be described as a second DRX cycle value, a second DRX cycle length, a second DRX cycle length value, etc. The period value of the long DRX cycle can be described as a DRX long cycle value, a long DRX cycle length, a DRX cycle length value, etc. The period value of the short DRX cycle can be described as a DRX short cycle value, a short DRX cycle length, a short DRX cycle length value, etc.

[0211] In some embodiments, the first DRX cycle value may be a fraction, a decimal, etc., as long as the cycle value is a non-integer rational number. This embodiment of the present disclosure does not specifically limit this.

[0212] In some embodiments, the first DRX cycle value may be a fraction, in which case the first DRX cycle may be a non-integer cycle, a fractional cycle, a non-integer millisecond cycle, etc. For example, the first DRX cycle value may be 100 / 3, 200 / 9, 125 / 9, 100 / 9, 25 / 3, etc.

[0213] In some embodiments, the first DRX cycle value is a fraction. The DRX parameter may include a first field and a second field, wherein the first field is the numerator of the first DRX cycle value and the second field is the denominator of the first DRX cycle value. For example, if the first DRX cycle value is 100 / 3, the first field is 100 and the second field is 3.

[0214] In some embodiments, if the first DRX cycle value is a decimal, the DRX parameter may include a first field and a second field, wherein the first field is the integer portion of the first DRX cycle value and the second field is the decimal portion of the first DRX cycle value. For example, if the first DRX cycle value is 16.67, the first field is 16 and the second field is 67.

[0215] In some embodiments, since the terminal 101 can also report only a value different from the DRX cycle of the last transmission when reporting the DRX cycle to the network device 102, the DRX parameter may include the first field or the second field. For example, the DRX long cycle value of the last transmission is 200 / 3, and the current DRX long cycle value is 100 / 3 this time, then the DRX parameter may include only the first field, and the first field is 100, so as to inform the network device of the current DRX long cycle. Alternatively, if the DRX long cycle value of the last transmission is 200 / 3, and the current DRX long cycle value is 200 / 9 this time, then the DRX parameter may include only the second field, and the second field is 9, so as to inform the network device of the current DRX long cycle.

[0216] In some embodiments, the first DRX cycle value is a fraction, the numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration. For example, the numerator of the first DRX cycle value (i.e., the integer duration) may be in the range of {200, 125, 100, 50, 25}, in ms; the denominator of the first DRX cycle value (the number of frames sent within the integer duration) may be in the range of {3, 9}.

[0217] In some embodiments, the unit of the integer duration may also be other natural units of time, such as seconds (s), minutes (min), etc.

[0218] In some embodiments, the DRX parameter is used to indicate a first DRX cycle and a second DRX cycle of the terminal 101. The description of the second DRX cycle can refer to the description of the first DRX cycle, which is not repeated here.

[0219] In some embodiments, the DRX long cycle and the DRX short cycle have a multiple relationship. Exemplarily, the DRX long cycle may be an integer multiple of the DRX short cycle.

[0220] In some embodiments, the relationship between the multiples of the DRX long cycle and the DRX short cycle may not be limited. The DRX long cycle may be an integer multiple of the DRX short cycle, or a non-integer multiple (e.g., a fractional multiple) of the DRX short cycle. In this case, at least one of the DRX long cycle value and the DRX short cycle value is a fraction.

[0221] In some embodiments, the DRX long cycle is an integer multiple of the DRX short cycle. In this case, the DRX short cycle value is a fraction, and the DRX long cycle value can be a fraction or an integer.

[0222] In some embodiments, the DRX parameter is used to indicate a first DRX cycle of the terminal 101 , where the first DRX cycle is a long DRX cycle, and the long DRX cycle is an integer multiple of a short DRX cycle of the last transmission.

[0223] In some embodiments, the DRX parameter is used to indicate a first DRX cycle of the terminal 101 , the first DRX cycle is a DRX short cycle, and the DRX long cycle of the last transmission is an integer multiple of the DRX short cycle.

[0224] In some embodiments, the DRX long cycle is a non-integer multiple (eg, a multiple is a fraction) of the DRX short cycle. In this case, the DRX short cycle value is a fraction, and the DRX long cycle value can be a fraction or an integer.

[0225] In some embodiments, the DRX parameter is used to indicate the first DRX cycle of the terminal 101, where the first DRX cycle is a long DRX cycle, and the long DRX cycle is a non-integer multiple (eg, a fractional multiple) of the last transmitted short DRX cycle.

[0226] In some embodiments, the DRX parameter is used to indicate the first DRX cycle of the terminal 101, the first DRX cycle is a DRX short cycle, and the DRX long cycle of the last transmission is a non-integer multiple (such as a multiple is a fraction) of the DRX short cycle.

[0227] Exemplarily, the terminal 101 sends a DRX parameter to the network device 102 , where the DRX parameter includes a first field and a second field, where the first field and the second field together indicate a DRX long cycle or a DRX short cycle.

[0228] Exemplarily, the terminal 101 sends a DRX parameter to the network device 102 , where the DRX parameter includes a first field, and the first field is a numerator of a DRX long cycle value or a DRX short cycle value.

[0229] Exemplarily, the terminal 101 sends a DRX parameter to the network device 102 , where the DRX parameter includes a second field, and the second field is a denominator of a DRX long cycle value or a DRX short cycle value.

[0230] Exemplarily, the terminal 101 sends DRX parameters to the network device 102. The DRX parameters include a first field, a second field, a third field, and a fourth field. The first field and the second field together indicate a DRX long cycle, and the third field and the fourth field together indicate a DRX short cycle.

[0231] Exemplarily, the terminal 101 sends DRX parameters to the network device 102, and the DRX parameters include a first field, a second field, a third field and a fourth field. The first field is the numerator of the DRX long cycle value, the second field is the denominator of the DRX long cycle value, the third field is the numerator of the DRX short cycle value, and the fourth field is the denominator of the DRX short cycle value.

[0232] Exemplarily, the terminal 101 sends DRX parameters to the network device 102, where the DRX parameters include one of the first field and the second field and one of the third field and the fourth field, where the first field or the second field indicates a DRX long cycle, and the third field or the fourth field indicates a DRX short cycle.

[0233] In step S440 , the network device 102 sends downlink information to the terminal 101 .

[0234] In some embodiments, the network device 101 sends downlink information to the terminal 102 according to the DRX parameters and at least one of the DRX long cycle and the DRX short cycle.

[0235] In some embodiments, the downlink information may be sent via a downlink control channel, such as downlink control information (DCI).

[0236] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0237] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0238] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0239] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0240] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0241] The communication method involved in the embodiments of the present disclosure may include at least one of steps S410 to S440. For example, steps S410 and S420 may be implemented as independent embodiments. For example, the combination of steps S430 and S440 may be implemented as an independent embodiment. For example, the combination of steps S410, S420, S430, and S440 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S410 to S440 are not limited to this.

[0242] In some embodiments, steps S410 and S420 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0243] Figure 5 is a flow chart of a communication method performed by a terminal according to an embodiment of the present disclosure. The present disclosure relates to a communication method that can be applied to a terminal 101. As shown in Figure 5, the method includes steps S510 to S520.

[0244] In step S510, terminal 101 sends first information.

[0245] The optional implementation of step S510 can refer to the optional implementation of step S410 in Figure 4 and other related parts in the embodiment involved in Figure 4, which will not be repeated here.

[0246] In some embodiments, the terminal 101 sends the first information to the network device 102 (such as an access network device), but is not limited thereto and the first information may also be sent to other entities.

[0247] In some embodiments, the first information is used by the network device 102 to send the second information. Optional implementations thereof may refer to the optional implementations of step S420 in FIG4 and other related parts of the embodiment involved in FIG4 , which will not be described in detail here.

[0248] In step S520, the terminal 101 sends DRX parameters.

[0249] The optional implementation of step S520 can refer to the optional implementation of step S430 in Figure 4 and other related parts in the embodiment involved in Figure 4, which will not be repeated here.

[0250] In some embodiments, the terminal 101 sends DRX parameters to the network device 102 (such as an access network device), but is not limited thereto and may also send DRX parameters to other entities.

[0251] In some embodiments, the DRX parameters are used by the network device 102 to send downlink information according to the DRX cycle indicated by the DRX parameters. Optional implementations thereof can be found in the optional implementations of step S440 of FIG4 and other related parts of the embodiment involved in FIG4 , which will not be described in detail here.

[0252] The communication method involved in the embodiments of the present disclosure may include at least one of steps S510 to S520. For example, step S510 may be implemented as an independent embodiment. For example, step S520 may be implemented as an independent embodiment. For example, a combination of steps S510 and S520 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S510 to S520 are not limited to this.

[0253] In some embodiments, step S510 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0254] In some embodiments, step S520 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0255] FIG6 is a flow chart of a communication method performed by a network device according to an embodiment of the present disclosure. The present disclosure relates to a communication method applied to a network device 102, such as an access network device. As shown in FIG6 , the method includes steps S610 to S620.

[0256] In step S610 , the network device 102 sends second information.

[0257] The optional implementation of step S610 can refer to the optional implementation of step S420 in Figure 4 and other related parts in the embodiment involved in Figure 4, which will not be repeated here.

[0258] In some embodiments, the network device 102 sends the second information to the terminal 101, but is not limited thereto and may also send the second information to other entities.

[0259] In some embodiments, the second information is used by the terminal 101 to send DRX parameters. Optional implementations thereof can be found in the optional implementations of step S430 in FIG4 and other related parts of the embodiment involved in FIG4 , which will not be described in detail here.

[0260] In step S620 , the network device 102 sends downlink information.

[0261] The optional implementation of step S620 can refer to the optional implementation of step S440 in Figure 4 and other related parts in the embodiment involved in Figure 4, which will not be repeated here.

[0262] In some embodiments, the network device 102 sends downlink information to the terminal 101 according to at least one of the DRX long cycle and the DRX short cycle indicated by the DRX parameter, but is not limited thereto and may also send downlink information to other entities.

[0263] The communication method involved in the embodiments of the present disclosure may include at least one of step S610 and step S620. For example, step S610 may be implemented as an independent embodiment. For example, step S620 may be implemented as an independent embodiment. For example, a combination of steps S610 and S620 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more of steps S610 and S620 are not limited to this.

[0264] In some embodiments, step S610 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0265] In some embodiments, step S620 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0266] FIG7 is another interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG7 , the communication method includes steps S710 and S720.

[0267] In step S710 , the terminal 101 sends DRX parameters to the network device 102 .

[0268] Optional implementations of step S710 may refer to step S430 of FIG. 4 , step S520 of FIG. 5 , and other related parts of the embodiments involved in FIG. 4 and FIG. 5 , which will not be described in detail here.

[0269] In step S720 , the network device 102 receives DRX parameters.

[0270] Optional implementations of step S720 may refer to step S440 of FIG. 4 , step S620 of FIG. 6 , and other related parts of the embodiments involved in FIG. 4 and FIG. 6 , which will not be described in detail here.

[0271] In some embodiments, the above method may include the method described in the above terminal side and network device side embodiments, which will not be repeated here.

[0272] The embodiment of the present disclosure relates to a communication method, which is executed by terminal 101 and includes the following steps A.

[0273] Step A: Terminal 101 sends DRX parameters.

[0274] Optional implementations of step A can be found in step S430 of FIG. 4 , step S520 of FIG. 5 , and other related parts of the embodiments involved in FIG. 4 and FIG. 5 , which will not be described in detail here.

[0275] In some embodiments, the above method may include the method described in the above terminal side embodiment, which will not be repeated here.

[0276] The embodiment of the present disclosure relates to a communication method, which is performed by the network device 102 and includes the following steps B.

[0277] In step B, the network device 102 receives DRX parameters.

[0278] Optional implementations of step B may refer to step S440 of FIG. 4 , step S620 of FIG. 6 , and other related parts of the embodiments involved in FIG. 4 and FIG. 6 , which will not be described in detail here.

[0279] In some embodiments, the above method may include the method described in the above embodiment on the network device side, which will not be repeated here.

[0280] The present disclosure relates to a communication method, which is executed by terminal 101 and includes:

[0281] 1. A method for protecting a terminal in a connected state from reporting a second type of DRX cycle, wherein the second type of DRX cycle is a DRX parameter having a non-integer cycle, a fractional cycle, or a rational number cycle, which is different from the original first type of DRX cycle, which is an integer cycle; or the second type of DRX cycle is considered to have characteristics of a non-integer cycle, a fractional cycle, or a rational number cycle, which is different from the integer DRX cycle supported in the existing protocol;

[0282] As an embodiment, the second type of DRX cycle reported by the terminal is its expected second type of DRX cycle, that is, an expected non-integer cycle or a fractional cycle or a rational number cycle.

[0283] 2. Based on 1, the terminal reports the first field and / or the second field to indicate the second type of DRX cycle it desires:

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

[0285] b) As a preferred embodiment, it is limited that the terminal needs to report the first field and the second field at the same time (ie, the two fields exist at the same time);

[0286] c) wherein: one of the first field and / or the second field is used for the numerator part, and the other one of the first field and / or the second field is used for the denominator part, together expressing the period.

[0287] As an example:

[0288] One of the first field and / or the second field is used to express time, such as X ms or minutes;

[0289] The first field and / or the second field is used to express the number of frames sent within Xms, such as Y frames;

[0290] In this case, X / Y is used to express non-integer periods;

[0291] As an example:

[0292] The parameter range used as the numerator is: {200, 125, 100, 50, 25;}

[0293] The range of the parameter used as the denominator is: {3, 9}

[0294] 3. Based on 2, the protocol stipulates that the preferredDRX-LongCycle reported by the terminal must meet the integer multiple relationship with the preferredDRX-ShortCycle.

[0295] a) As an example:

[0296] For example, (100 / 3) is reported as the long cycle, and 50 / 3 is reported as the short cycle; in this case, the two satisfy the multiple relationship;

[0297] For example, if (100 / 3) is configured as the long cycle and 200 / 9 is configured as the short cycle, the two do not satisfy the multiple relationship, which is an unreasonable reporting configuration.

[0298] 4. Based on 2, the protocol stipulates that the preferredDRX-LongCycle reported by the terminal needs to meet the relationship with the preferredDRX-ShortCycle, which does not necessarily need to meet the integer multiple relationship.

[0299] a) As an example:

[0300] For example, (100 / 3) is reported as the long cycle, and 10ms is reported as the short cycle. In this case, only the long cycle reported is a non-integer cycle.

[0301] 5. Based on 1 or 2, define a terminal reporting capability indication, that is, it can notify the network of its ability to support reporting of the expected second type DRX cycle.

[0302] As an embodiment, the precondition for supporting this capability may be defined in a protocol agreement as at least one of the following:

[0303] a) As a preferred embodiment, a prerequisite for the terminal's ability to support reporting of the desired second type of DRX cycle is its ability to support the desired DRX reporting. (Embodiment 1) See Table 1 in the above book. That is, the terminal can optionally report its ability to support reporting of the desired second type of DRX cycle only if it supports the desired DRX reporting capability.

[0304] b) As a preferred embodiment, a prerequisite for the terminal to support the capability of reporting the second type of DRX cycle is its capability of supporting non-integer DRX cycles; that is, the terminal can optionally report its capability of supporting reporting the desired second type of DRX cycle only if it supports non-integer DRX cycles;

[0305] c) As a preferred embodiment, a and b can be used in combination. That is, the prerequisite for supporting the capability of reporting the second type of DRX cycle is that both a and b are supported. That is, the terminal must support both the desired DRX reporting capability and the capability of supporting non-integer DRX cycles before it can optionally report its capability of supporting the desired second type of DRX cycle.

[0306] The embodiments of the present disclosure also provide communication devices, such as terminal 101 and network device 102, for implementing any of the above methods. For example, the embodiments of the present disclosure provide a communication device including units or modules for implementing each step performed by the terminal in any of the above methods. For another example, another communication device is also provided, including units or modules for implementing each step performed by a network device (e.g., an access network device or a core network device) in any of the above methods.

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

[0308] 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). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0309] FIG8 is a schematic diagram of a structure of a communication device according to an embodiment of the present disclosure. As shown in FIG8 , the communication device 800 may include at least one of a sending module 810 , a processing module 820 , and a receiving module 830 .

[0310] In some embodiments, the communication device 800 may be a terminal, and executes the method described in the embodiment on the terminal 101 side. In this case, the communication device 800 may include a sending module 810 and a processing module 820.

[0311] In some embodiments, the sending module 810 is configured to send a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

[0312] In some embodiments, the first DRX cycle value is a fraction, and the DRX parameter includes at least one of a first field and a second field, wherein the first field is a numerator of the first DRX cycle value and the second field is a denominator of the first DRX cycle value.

[0313] In some embodiments, the numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration.

[0314] In some embodiments, the first DRX cycle is a DRX long cycle or a DRX short cycle.

[0315] In some embodiments, the DRX parameter is further used to indicate a second DRX cycle of the terminal, wherein the second DRX cycle value is a fraction.

[0316] In some embodiments, the DRX parameter further includes at least one of a third field and a fourth field, the third field is a numerator of the second DRX cycle value, and the fourth field is a denominator of the second DRX cycle value.

[0317] In some embodiments, the first DRX cycle is a DRX long cycle, the DRX parameter is further used to indicate a DRX short cycle of the terminal, and the DRX long cycle value is an integer multiple of the DRX short cycle value.

[0318] In some embodiments, the sending module 810 is further configured to send first information, where the first information is configured to indicate whether the terminal supports sending a DRX cycle with a fractional DRX cycle value.

[0319] In some embodiments, the processing module 820 is configured to determine that the terminal supports sending a DRX cycle with a fractional DRX cycle value when at least one of the following conditions is met: supporting sending expected DRX parameters; supporting a DRX cycle with a fractional DRX cycle value.

[0320] In some embodiments, the communication device 800 may be a network device that executes the method described in the embodiment on the network device 102 side. In this case, the communication device 800 may include a receiving module 830.

[0321] In some embodiments, the receiving module 830 is configured to receive a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

[0322] In some embodiments, the DRX parameter includes at least one of a first field and a second field, wherein the first field is a numerator of the first DRX cycle value and the second field is a denominator of the first DRX cycle value.

[0323] In some embodiments, the numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration.

[0324] In some embodiments, the first DRX cycle is a DRX long cycle or a DRX short cycle.

[0325] In some embodiments, the DRX parameter is further used to indicate a second DRX cycle of the terminal, wherein the second DRX cycle value is a fraction.

[0326] In some embodiments, the DRX parameter further includes at least one of a third field and a fourth field, the third field is a numerator of the second DRX cycle value, and the fourth field is a denominator of the second DRX cycle value.

[0327] In some embodiments, the first DRX cycle is a DRX long cycle, the DRX parameter is further used to indicate a DRX short cycle of the terminal, and the DRX long cycle value is an integer multiple of the DRX short cycle value.

[0328] In some embodiments, the receiving module 830 is further configured to receive first information, where the first information is configured to indicate whether the terminal supports sending a DRX cycle with a fractional DRX cycle value.

[0329] Figure 9 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. Communication device 900 can be terminal 101, network device 102, or a chip, chip system, or processor that supports terminal 101 or network device 102 in implementing any of the above methods. Communication device 900 can be used to implement the communication methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

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

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

[0332] In some embodiments, the communication device 900 further includes one or more transceivers 903. When the communication device 900 includes one or more transceivers 903, the communication steps such as sending and receiving in the above method are performed by the transceiver 903, and the other steps are performed by the processor 901.

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

[0334] Optionally, the communication device 900 further includes one or more interface circuits 904, which are connected to the memory 902. The interface circuits 904 can be used to receive signals from the memory 902 or other devices, and can be used to send signals to the memory 902 or other devices. For example, the interface circuits 904 can read instructions stored in the memory 902 and send the instructions to the processor 901.

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

[0336] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed by a processor, causes the processor to execute any of the above communication methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a temporary storage medium.

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

[0338] The embodiment of the present disclosure also provides a computer program, which, when executed on a processor, enables the processor to execute any one of the above communication methods.

[0339] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the embodiments disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow from the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0340] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A communication method, performed by a terminal, the method comprising: A DRX parameter is sent, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

2. The method according to claim 1, wherein: The DRX parameter includes at least one of a first field and a second field, the first field is a numerator of the first DRX cycle value, and the second field is a denominator of the first DRX cycle value.

3. The method according to claim 1 or 2, wherein: The numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration.

4. The method according to any one of claims 1 to 3, wherein: The first DRX cycle is a DRX long cycle or a DRX short cycle.

5. The method according to any one of claims 1 to 4, wherein: The DRX parameter is also used to indicate a second DRX cycle of the terminal, wherein the second DRX cycle value is a fraction.

6. The method according to claim 5, wherein: The DRX parameter further includes at least one of a third field and a fourth field, the third field is a numerator of the second DRX cycle value, and the fourth field is a denominator of the second DRX cycle value.

7. The method according to any one of claims 1 to 3, wherein: The first DRX cycle is a DRX long cycle, the DRX parameter is further used to indicate a DRX short cycle of the terminal, and a DRX long cycle value is an integer multiple of a DRX short cycle value.

8. The method according to any one of claims 1 to 7, wherein: The method further comprises: Sending first information, where the first information is used to indicate whether the terminal supports sending a DRX cycle whose DRX cycle value is a fraction.

9. The method according to claim 8, wherein: The method comprises: When at least one of the following conditions is met, it is determined that the terminal supports a DRX cycle with a fractional sending cycle value: Support sending expected DRX parameters; Supports DRX cycle values ​​that are fractional DRX cycles.

10. A communication method, performed by a network device, the method comprising: A DRX parameter is received, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

11. The method according to claim 10, wherein: The DRX parameter includes at least one of a first field and a second field, wherein the first field is a numerator of the first DRX cycle value, and the second field is a denominator of the first DRX cycle value.

12. The method according to claim 10 or 11, wherein: The numerator of the first DRX cycle value is an integer duration, and the denominator of the first DRX cycle value is the number of frames sent within the integer duration.

13. The method according to any one of claims 10 to 12, wherein: The first DRX cycle is a DRX long cycle or a DRX short cycle.

14. The method according to any one of claims 10 to 13, wherein: The DRX parameter is also used to indicate a second DRX cycle of the terminal, wherein the second DRX cycle value is a fraction.

15. The method according to claim 14, wherein: The DRX parameter further includes at least one of a third field and a fourth field, the third field is a numerator of the second DRX cycle value, and the fourth field is a denominator of the second DRX cycle value.

16. The method according to any one of claims 10 to 12, wherein: The first DRX cycle is a DRX long cycle, the DRX parameter is further used to indicate a DRX short cycle of the terminal, and the DRX long cycle value is an integer multiple of the DRX short cycle value.

17. The method according to any one of claims 10 to 16, wherein: The method further comprises: First information is received, where the first information is used to indicate whether the terminal supports sending a DRX cycle whose DRX cycle value is a fraction.

18. A terminal, comprising: The sending module is used to send a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

19. A network device comprising: The receiving module is used to receive a DRX parameter, where the DRX parameter is used to indicate a first DRX cycle of the terminal, wherein the first DRX cycle value is a fraction.

20. A communication device, comprising: One or more processors; The processor is configured to execute the communication method according to any one of claims 1 to 9 by calling instructions.

21. A communication device, comprising: One or more processors; The processor is configured to execute the communication method according to any one of claims 10 to 17 by calling instructions.

22. A communication system comprising: A terminal, configured to implement the communication method according to any one of claims 1 to 9; A network device, configured to implement the communication method according to any one of claims 10 to 17.

23. A storage medium storing instructions; when the instructions are executed on a processor, the processor executes the communication method according to any one of claims 1 to 9 and claims 10 to 17.

Images