Communication methods and devices

By sending service requirement information and configuration information into service groups in the communication system, the problem of high energy consumption of terminal equipment is solved, and energy saving and network performance optimization of terminal equipment and network equipment are achieved.

CN123124106APending Publication Date: 2026-11-17HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510629457.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-15
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

With the development of communication technology, the power consumption of terminal devices has increased, and how to reduce the energy consumption of terminal devices has become an urgent problem to be solved.

Method used

By sending service demand information for services to be scheduled, network devices can perceive the service information of terminal devices, group services according to grouping rules, send configuration information to schedule data for each service group, and optimize network performance and terminal device power consumption.

Benefits of technology

This reduces the frequency of terminal devices opening and closing the transmit and receive channels, lowers the energy consumption of terminal devices, optimizes network resource utilization, and improves transmission efficiency and service quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124106A_ABST
    Figure CN123124106A_ABST
Patent Text Reader

Abstract

This application provides a communication method and apparatus. The method includes: sending service requirement information for at least one service to be scheduled; receiving first configuration information, the first configuration information being used to schedule data corresponding to the service to be scheduled included in each of at least one service group, wherein the at least one service group is determined by grouping the at least one service to be scheduled based on a grouping rule, the grouping rule being related to the service requirement information. Using this application can reduce the power consumption of terminal devices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Currently, with the continuous development of communication technology, the specifications of terminals are also constantly improving. For example, the antenna size, system bandwidth and transmission power have been greatly improved, and the power consumption of terminals will also increase accordingly. Therefore, with the further development of communication technology, how to reduce the power consumption of terminal devices is a technical problem that needs to be solved by people in this field. Summary of the Invention

[0003] This application proposes a communication method and apparatus that can reduce the energy consumption of terminal devices.

[0004] In a first aspect, embodiments of this application provide a communication method applicable to a terminal-side device, which may be a terminal device, a component within the terminal device (e.g., a processor, chip, circuit, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The method includes: sending service requirement information for at least one scheduled service; and receiving first configuration information, wherein the first configuration information is used to schedule data corresponding to the scheduled service included in each of at least one service group, wherein the at least one service group is determined based on a grouping rule related to the service requirement information.

[0005] In the above method, by sending service requirement information for at least one service to be scheduled, the network device can perceive the relevant information of the terminal device's service, which is beneficial for grouping. By receiving first configuration information, which is used to schedule the data corresponding to the services to be scheduled in each service group, the energy consumption of the terminal device can be reduced, and the energy consumption of the network device can be saved. For example, if a service group includes three consecutive services to be scheduled, the terminal device only needs to open and close the transceiver channel once. Compared with the prior art, where the three services to be scheduled are not consecutive and the terminal device needs to open and close the transceiver channel three times, this application can reduce the number of times the terminal device frequently opens and closes the transceiver channel, thereby reducing the energy consumption of the terminal device and achieving the purpose of energy saving.

[0006] In one possible implementation, the business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

[0007] In another possible implementation, the grouping rule is related to the business requirement information, and the grouping rule includes one or more of the following: the service package size of the services to be scheduled in the same business group falls within the same range; the service type of the services to be scheduled in the same business group is the same; the service latency requirements of the services to be scheduled in the same business group fall within the same range; the service priority of the services to be scheduled in the same business group falls within the same range; or the service traffic requirements of the services to be scheduled in the same business group fall within the same range.

[0008] In the above methods, optimizing network performance and improving transmission efficiency by grouping the service packets of scheduled services within the same service group into the same size range. For example, scheduling services with larger packet sizes are grouped together, and those with smaller packet sizes are grouped together. Grouping scheduling services with similar or identical packet sizes avoids frequent fragmentation when transmitting mixed large and small packets, reducing processing latency and improving network transmission efficiency. Since scheduling services of the same service type have similar or identical packet sizes and latency requirements, grouping them by service type within the same service group facilitates centralized scheduling. Grouping the latency requirements of scheduling services within the same service group within the same range ensures low grouping difficulty and does not affect user experience. Grouping the service priorities of scheduling services within the same service group within the same range ensures that high-priority scheduling services are transmitted first, while low-priority scheduling services are transmitted later, thereby improving service quality. By grouping the traffic demands of services to be scheduled within the same service group into the same range, network resource utilization can be improved. For example, services to be scheduled with the same or similar peak rates can be grouped together, and resource allocation can be dynamically adjusted to avoid congestion or resource idleness.

[0009] In another possible implementation, the method further includes: receiving second configuration information for configuring at least one discontinuous reception DRX cycle corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX cycle.

[0010] The above methods can significantly reduce the power consumption of terminal devices and optimize network resource utilization.

[0011] In another possible implementation, the DRX cycles associated with different business groups within the at least one business group are different.

[0012] In the above method, different DRX cycles can be configured based on the business requirements of different business groups, which helps to reduce the energy consumption of terminal devices.

[0013] In another possible implementation, the at least one service group includes a first service group and a second service group, the first service group being associated with a first DRX cycle and the second service group being associated with a second DRX cycle, the service latency requirement of the first service group being higher than that of the second service group, and the first DRX cycle being shorter than that of the second DRX cycle.

[0014] Optionally, the first DRX cycle being shorter than the second DRX cycle includes situations where the onduration of the first DRX cycle and the onduration of the second DRX cycle are equal, but the dormancy period of the first DRX cycle is shorter than the dormancy period of the second DRX cycle.

[0015] In the above method, the data corresponding to the scheduled services included in the first service group can be transmitted faster than the data corresponding to the scheduled services included in the second service group, thereby ensuring the transmission latency of the scheduled services included in the first service group.

[0016] In another possible implementation, the method further includes: receiving first indication information, the service requirement information for sending at least one scheduled service is sent based on the first indication information.

[0017] In another possible implementation, the at least one service group includes a third service group associated with a third DRX cycle. The method further includes receiving third configuration information for configuring time-frequency resources for data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle. The first service does not belong to the at least one service to be scheduled.

[0018] In the above method, a conflict handling mechanism is defined when the scheduled services included in the third service group and the first service conflict, thereby ensuring the normal transmission of the scheduled services included in the third service group and the first service.

[0019] Secondly, embodiments of this application provide a communication method applicable to a network-side device, which may be a network device, a component within the network device (e.g., a processor, chip, circuit, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. The method includes: receiving service requirement information for at least one service to be scheduled; grouping the at least one service to be scheduled based on a grouping rule to determine at least one service group, each service group including at least one service to be scheduled, the grouping rule being related to the service requirement information; and sending first configuration information for scheduling data corresponding to the services to be scheduled included in each service group.

[0020] In the above method, by receiving service requirement information of at least one service to be scheduled, the network device can perceive the relevant information of the terminal device's service, which is beneficial for service grouping. By grouping the at least one service to be scheduled based on grouping rules to determine at least one service group, services to be scheduled with the same or similar service requirement information can be grouped together, which is more conducive to centralized processing of the services to be scheduled included in the service group. By sending first configuration information, which is used to schedule the data corresponding to the services to be scheduled included in each service group, the energy consumption of the terminal device can be reduced, and the energy consumption of the network device can be saved, thereby achieving the effect of energy saving at both ends. For example, if a service group includes three consecutive services to be scheduled, the terminal device only needs to open and close the transceiver channel once. Compared with the prior art, where the three services to be scheduled are not consecutive and the terminal device needs to open and close the transceiver channel three times, this application can reduce the number of times the terminal device frequently opens and closes the transceiver channel, thereby reducing the energy consumption of the terminal device and achieving the purpose of energy saving. For example, if a service group includes three consecutive services to be scheduled, the network device only needs to send configuration information once. In contrast, in the existing technology, the three services to be scheduled are not consecutive, and the network device needs to send configuration information three times, thus saving signaling overhead and network device energy consumption.

[0021] In one possible implementation, the business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

[0022] In another possible implementation, the grouping rule is related to the business requirement information, and the grouping rule includes one or more of the following: the service package size of the services to be scheduled in the same business group falls within the same range; the service type of the services to be scheduled in the same business group is the same; the service latency requirements of the services to be scheduled in the same business group fall within the same range; the service priority of the services to be scheduled in the same business group falls within the same range; or the service traffic requirements of the services to be scheduled in the same business group fall within the same range.

[0023] In the above methods, optimizing network performance and improving transmission efficiency by grouping the service packets of scheduled services within the same service group into the same size range. For example, scheduling services with larger packet sizes are grouped together, and those with smaller packet sizes are grouped together. Grouping scheduling services with similar or identical packet sizes avoids frequent fragmentation when transmitting mixed large and small packets, reducing processing latency and improving network transmission efficiency. Since scheduling services of the same service type have similar or identical packet sizes and latency requirements, grouping them by service type within the same service group facilitates centralized scheduling. Grouping the latency requirements of scheduling services within the same service group within the same range ensures low grouping difficulty and does not affect user experience. Grouping the service priorities of scheduling services within the same service group within the same range ensures that high-priority scheduling services are transmitted first, while low-priority scheduling services are transmitted later, thereby improving service quality. By grouping the traffic demands of services to be scheduled within the same service group into the same range, network resource utilization can be improved. For example, services to be scheduled with the same or similar peak rates can be grouped together, and resource allocation can be dynamically adjusted to avoid congestion or resource idleness.

[0024] In another possible implementation, the method further includes: sending second configuration information for configuring at least one discontinuous reception DRX cycle corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX cycle.

[0025] The above methods can significantly reduce the power consumption of terminal devices and optimize network resource utilization.

[0026] In another possible implementation, the DRX cycles associated with different business groups within the at least one business group are different.

[0027] In the above method, different DRX cycles can be configured based on the business requirements of different business groups, which helps to reduce the energy consumption of terminal devices.

[0028] In another possible implementation, the at least one service group includes a first service group and a second service group, the first service group being associated with a first DRX cycle and the second service group being associated with a second DRX cycle, the service latency requirement of the first service group being higher than that of the second service group, and the first DRX cycle being shorter than that of the second DRX cycle.

[0029] Optionally, the first DRX cycle being shorter than the second DRX cycle includes situations where the onduration of the first DRX cycle and the onduration of the second DRX cycle are equal, but the dormancy period of the first DRX cycle is shorter than the dormancy period of the second DRX cycle.

[0030] In the above method, the data corresponding to the scheduled services included in the first service group can be transmitted faster than the data corresponding to the scheduled services included in the second service group, thereby ensuring the transmission latency of the scheduled services included in the first service group.

[0031] In another possible implementation, the method further includes: sending first indication information, which instructs the terminal device to send service requirement information for the at least one scheduled service.

[0032] In another possible implementation, the at least one service group includes a third service group associated with a third DRX cycle. The method further includes sending third configuration information for configuring the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle. The first service does not belong to the at least one service to be scheduled.

[0033] In the above method, a conflict handling mechanism is defined when the scheduled services included in the third service group and the first service conflict in transmission, thereby ensuring the normal transmission of the scheduled services included in the third service group and the first service.

[0034] Thirdly, embodiments of this application provide a communication device, which can be a terminal device, a component in the terminal device (e.g., a processor, chip, circuit, or chip system), or a logic module or software that can implement all or part of the functions of the terminal device.

[0035] In one possible implementation, the communication device may include modules, units, or means that correspond one-to-one with the methods / operations / steps / actions described in the first aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0036] In one possible implementation, the communication device includes: a processing unit and a transceiver unit. The processing unit is configured to transmit service requirement information of at least one service to be scheduled through the transceiver unit. The transceiver unit is configured to receive first configuration information, which is used to schedule data corresponding to the service to be scheduled included in each of at least one service group. The at least one service group is determined based on a grouping rule that is related to the service requirement information.

[0037] In one possible implementation, the business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

[0038] In another possible implementation, the grouping rule is related to the business requirement information, and the grouping rule includes one or more of the following: the service package size of the services to be scheduled in the same business group falls within the same range; the service type of the services to be scheduled in the same business group is the same; the service latency requirements of the services to be scheduled in the same business group fall within the same range; the service priority of the services to be scheduled in the same business group falls within the same range; or the service traffic requirements of the services to be scheduled in the same business group fall within the same range.

[0039] In another possible implementation, the transceiver unit is further configured to receive second configuration information, which is used to configure at least one discontinuous reception DRX cycle corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX cycle.

[0040] In another possible implementation, the DRX cycles associated with different business groups within the at least one business group are different.

[0041] In another possible implementation, the at least one service group includes a first service group and a second service group, the first service group being associated with a first DRX cycle and the second service group being associated with a second DRX cycle, the service latency requirement of the first service group being higher than that of the second service group, and the first DRX cycle being shorter than that of the second DRX cycle.

[0042] In another possible implementation, the transceiver unit is further configured to receive first indication information, which is used to send service requirement information for sending at least one scheduled service.

[0043] In another possible implementation, the at least one service group includes a third service group associated with a third DRX cycle. The transceiver unit is also configured to receive third configuration information for configuring the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle. The first service does not belong to the at least one service to be scheduled.

[0044] For the technical effects of the third aspect or possible implementation, please refer to the introduction of the technical effects of the first aspect or corresponding implementation.

[0045] Fourthly, embodiments of this application provide a communication device, which may be a network device, a component of a network device (e.g., a processor, chip, circuit, or chip system), or a logic module or software capable of implementing all or part of the functions of a network device.

[0046] In one possible implementation, the communication device may include modules, units, or means that correspond one-to-one with the methods / operations / steps / actions described in the second aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0047] In one possible implementation, the communication device includes: a processing unit and a transceiver unit. The transceiver unit is configured to receive service requirement information for at least one service to be scheduled; the processing unit is configured to group the at least one service to be scheduled based on a grouping rule to determine at least one service group, each service group including at least one service to be scheduled, the grouping rule being related to the service requirement information; and the transceiver unit is configured to send first configuration information for scheduling data corresponding to the services to be scheduled included in each service group.

[0048] In one possible implementation, the business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

[0049] In another possible implementation, the grouping rule is related to the business requirement information, and the grouping rule includes one or more of the following: the service package size of the services to be scheduled in the same business group falls within the same range; the service type of the services to be scheduled in the same business group is the same; the service latency requirements of the services to be scheduled in the same business group fall within the same range; the service priority of the services to be scheduled in the same business group falls within the same range; or the service traffic requirements of the services to be scheduled in the same business group fall within the same range.

[0050] In another possible implementation, the transceiver unit is further configured to send second configuration information, which is used to configure at least one discontinuous reception DRX cycle corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX cycle.

[0051] In another possible implementation, the DRX cycles associated with different business groups within the at least one business group are different.

[0052] In another possible implementation, the at least one service group includes a first service group and a second service group, the first service group being associated with a first DRX cycle and the second service group being associated with a second DRX cycle, the service latency requirement of the first service group being higher than that of the second service group, and the first DRX cycle being shorter than that of the second DRX cycle.

[0053] In another possible implementation, the transceiver unit is further configured to send first indication information, which instructs the terminal device to send service requirement information for the at least one scheduled service.

[0054] In another possible implementation, the at least one service group includes a third service group associated with a third DRX cycle. The transceiver unit is also used to send third configuration information, which is used to configure the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle. The first service does not belong to the at least one service to be scheduled.

[0055] For the technical effects of the fourth aspect or possible implementation, please refer to the introduction of the technical effects of the second aspect or corresponding implementation.

[0056] Fifthly, embodiments of this application provide a communication device including at least one processor, which invokes a computer program or instructions stored in a memory to execute the method described in the first aspect or a possible implementation thereof.

[0057] In one possible implementation, the communication device also includes a memory and a communication interface. Optionally, the memory and processor are integrated together.

[0058] In one possible implementation, the memory is located outside the communication device.

[0059] In a sixth aspect, embodiments of this application provide a communication device including at least one processor, which invokes a computer program or instructions stored in a memory to execute the method described in the second aspect or a possible implementation thereof.

[0060] In one possible implementation, the communication device also includes a memory and a communication interface. Optionally, the memory and processor are integrated together.

[0061] In one possible implementation, the memory is located outside the communication device.

[0062] In a seventh aspect, embodiments of this application provide a chip device including at least one processor, the at least one processor being configured to execute computer programs or instructions to implement any of the above aspects or possible implementations of any of the above aspects.

[0063] In one possible implementation, the input of the chip device corresponds to the receiving operation in any of the above-mentioned aspects or possible implementations, and the output of the chip device corresponds to the transmitting operation in any of the above-mentioned aspects or possible implementations.

[0064] Optionally, the processor is coupled to the memory via an interface.

[0065] Optionally, the chip device may also include a memory storing computer program instructions.

[0066] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a processor, implement the methods described above.

[0067] Ninthly, embodiments of this application provide a computer program product that includes a computer program or instructions that, when executed on a processor, implement the method described in any of the above aspects.

[0068] In a tenth aspect, embodiments of this application provide a communication system comprising: the apparatus as described in the fifth aspect and the apparatus as described in the sixth aspect. Attached Figure Description

[0069] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0070] Figure 2 This is a schematic diagram of a decentralized scheduling method;

[0071] Figure 3 This is a schematic diagram of a centralized scheduling method provided in an embodiment of this application;

[0072] Figure 4 This is a diagram illustrating the network element function division and protocol layer structure of an ORAN device provided in an embodiment of this application;

[0073] Figure 5This is a schematic diagram of terminal equipment specifications in 4G and 5G.

[0074] Figure 6 This is a schematic diagram illustrating the presence and absence of data transmission;

[0075] Figure 7 This is a schematic diagram of a PDCCH Skipping method;

[0076] Figure 8 This is a schematic diagram of a low-power wake-up receiver and a main receiver completing PDCCH monitoring;

[0077] Figure 9 This is a schematic diagram of a communication method provided in an embodiment of this application;

[0078] Figure 10 This is a schematic diagram of a service group provided in an embodiment of this application;

[0079] Figure 11 This is a schematic diagram illustrating different DRX cycles associated with different service groups, provided in an embodiment of this application.

[0080] Figure 12 This is a schematic diagram of a third service group and a first service scheduling provided in an embodiment of this application;

[0081] Figure 13 This is another schematic diagram of a third service group and a first service scheduling provided in the embodiments of this application;

[0082] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0083] Figure 15 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application;

[0084] Figure 16 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application. Detailed Implementation

[0085] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0086] References to "one embodiment" or "some embodiments" as described in this application mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0087] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, and c can be single or multiple.

[0088] It is understood that in this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0089] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index; indirectly instructing the information to be instructed by instructing other information, where there is a relationship between the other information and the information to be instructed; or instructing only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent.

[0090] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0091] It is understood that "send" and "receive" in this application refer to the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which can include direct transmission via the air interface or indirect transmission via the air interface from other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which can include direct reception from YY via the air interface or indirect reception from YY via the air interface from other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0092] In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via buses, wiring, or interfaces.

[0093] It is understandable that information may undergo necessary processing, such as encoding and modulation, between the source and destination, but the destination can understand the valid information from the source. Similar statements in this application can be interpreted in a similar way and will not be elaborated further.

[0094] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system 100 provided in an embodiment of this application, to... Figure 1The application scenario used in this application is illustrated using the communication system 100 architecture shown as an example. The communication system 100 includes a network device 101 and a terminal device 102. It should be understood that the communication system 100 to which the methods of the embodiments of this application can be applied may include more or fewer network devices or terminal devices. Network devices and terminal devices can be hardware, functionally separated software, or a combination of both. Network devices and terminal devices can communicate with each other through other devices or network elements. In this system, network device 101 can transmit data with multiple terminal devices; that is, network device 101 sends downlink data to terminal device 102, and of course, terminal device 102 can also send uplink data to network device 101. The apparatus provided in the embodiments of this application can be applied to network device 101 or to terminal device 102. The network device 101 can be any of the network devices described below, and the terminal device 102 can be any of the terminal devices described below. It is understood that... Figure 1 This application only illustrates one possible communication system architecture to which this embodiment can be applied. In other possible scenarios, the communication system architecture may also include other devices. It should be noted that the methods described in this application embodiment can be applied to... Figure 1 The communication system shown.

[0095] In existing technologies, network devices are unaware of the service needs of terminal devices and schedule terminal devices based on the principle of optimal experience. This often results in terminal devices frequently performing blind checks of the physical downlink control channel (PDCCH) or keeping the transmit and receive channels open for extended periods. This is detrimental to the energy efficiency of terminal devices and thus affects the energy consumption of network devices. Please refer to [link to details]. Figure 2 , Figure 2This is a schematic diagram of a decentralized scheduling mechanism. The network device schedules UE#1 in the first time slot, meaning data transmission occurs between the network device and UE#1 in the first time slot. No data transmission occurs in the second time slot. UE#2 is scheduled in the third time slot, meaning data transmission occurs between the network device and UE#2 in the third time slot. UE#1 is scheduled in the fourth time slot, meaning data transmission occurs between the network device and UE#1 in the fourth time slot. It can be seen that UE#1 completes data transmission in multiple non-contiguous time slots and needs to be prepared for scheduling in other time slots. Therefore, it generally maintains micro-sleep. For example, even though there is no data transmission in the second time slot, UE#1 still needs to perform PDCCH blind detection, open the transmit / receive channel, decode, confirm that there is no data transmission, and close the transmit / receive channel to enter micro-sleep. The processes of PDCCH blind detection, opening the transmit / receive channel, decoding, and closing the transmit / receive channel by UE#1 generate energy consumption. The energy consumption of each channel opening is much greater than the energy consumption of a single transmission (with the same amount of data), which is detrimental to the energy saving of terminal equipment. In addition, network devices need to frequently send downlink control information (DCI) to schedule multiple terminal devices, which leads to high power consumption of network devices.

[0096] This application's network equipment senses the service needs of terminal devices and schedules terminal devices on demand based on the principle of optimal energy consumption. This facilitates energy saving at both the network and terminal ends and minimizes the impact on service experience. Please refer to [link / reference] for details. Figure 3 , Figure 3 This is a schematic diagram of centralized scheduling provided in an embodiment of this application. The network device sends a DCI (Distributed Control Interface), which can simultaneously schedule UE#1 and UE#2. UE#1 can complete data reception or transmission in two consecutive time slots. Specifically, it can achieve full-specification data reception or transmission, which means high-speed transmission based on large bandwidth or full antenna, reducing transmission time and achieving energy saving. Through this centralized scheduling method, UE#1 can complete data reception or transmission in two consecutive time slots by opening and closing the transceiver channel only once, reducing the number of times the transceiver channel is opened and closed. This reduces the energy consumption generated by UE#1 in performing PDCCH blind detection, decoding, opening and closing the transceiver channel, etc., thus achieving energy saving. In addition, the network device can schedule multiple terminal devices through DCI in one time slot, reducing the number of DCI transmissions, saving signaling overhead, and thus saving network device energy consumption.

[0097] (1) Terminal equipment, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device that provides voice or data connectivity to a user. Specifically, it includes devices that provide voice connectivity to a user, devices that provide data connectivity to a user, or devices that provide both voice and data connectivity to a user. For example, it may include handheld devices with wireless connectivity or processing devices connected to a wireless modem. This terminal equipment can communicate with the core network via a radio access network (RAN), exchanging voice or data with the RAN, or interacting with the RAN to exchange voice and data. Currently, terminal devices can include: mobile phones, tablets, laptops, smartphones, wireless data cards, wireless modems, handsets, laptop computers, handheld computers, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminals in autonomous driving, wireless terminals in remote surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. Terminal devices can also be other devices with terminal functions. For example, a terminal device can also be a device that plays a terminal function in device-to-device (D2D) communication.Terminal devices can also include vehicle-to-everything (V2X) terminal devices, machine-to-machine / machine-type communications (M2M / MTC) terminal devices, Internet of Things (IoT) terminal devices, light UEs, reduced capability UEs (REDCAP UEs), subscriber units, subscriber stations, mobile stations, remote stations, access points (APs), remote terminals, access terminals, user terminals, user agents, or user devices, and drone equipment. For example, they can include mobile phones (or cellular phones), computers with mobile terminal devices, portable, pocket-sized, handheld, and computer-embedded mobile devices, etc. Examples include personal communication service (PCS) telephones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). It also includes limited devices, such as devices with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners. In this application, terminal devices with wireless transceiver capabilities and chips that can be installed in the aforementioned terminal devices are collectively referred to as terminal devices.

[0098] It should be noted that the terminal device may be a device or apparatus with a chip, or a device or apparatus with integrated circuitry, or a chip, module or control unit in the device or apparatus shown above. This application does not limit the specific device.

[0099] (2) A network device is a device deployed in a wireless access network to provide wireless communication functions for terminal devices. A network device may also be called a wireless access network (RAN) entity, access node, network node, or communication device, etc.

[0100] Specifically, the network equipment can be access network equipment for cellular systems related to the 3rd Generation Partnership Project (3GPP). For example, fourth-generation (4G) mobile communication systems or fifth-generation (5G) mobile communication systems. The network equipment can also be access network equipment in open RAN (O-RAN or ORAN) or cloud radio access network (CRAN). Alternatively, the network equipment can also be access network equipment in a communication system formed by the integration of two or more of the above communication systems.

[0101] Network equipment includes, but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS) in Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA) networks, home base station (e.g., home evolved Node B, or home Node B, HNB), baseband unit (BBU), access point (AP) in Wi-Fi systems, macro base station, micro base station (also known as small cell), relay station, donor node, radio controller in CRAN scenarios, radio backhaul node, transmission point (TP), or transmission reception point (TRP). Network equipment can also be access network equipment in 5G mobile communication systems. For example, a next-generation NodeB (gNB), TRP, TP in a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) in a base station in a 5G mobile communication system. Alternatively, network equipment can also be network nodes that constitute a gNB or transmission point. For example, a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. CU and DU can be set up separately or included in the same network element. For example, a BBU. RU can be included in radio equipment or radio units. For example, in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). Alternatively, network equipment can also be a server, wearable device, vehicle, or in-vehicle equipment, etc. For example, in V2X technology, network equipment can be a roadside unit (RSU).

[0102] Please see Figure 4 , Figure 4 This is a diagram illustrating the network element function division and protocol layer structure of an ORAN device provided in an embodiment of this application.

[0103] In some examples, the CU is a logical node carrying the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which can be interfaces such as E2 interfaces. Optionally, the CU may possess some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces, which can be interfaces such as the F1 interface. In some examples, these interfaces (e.g., the F1 interface) can provide control plane and user plane functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0104] In some examples, the CU can be split into CU-CP (control unit-control plane) and CU-UP (control unit-user plane). CU-CP is a logical node carrying the RRC layer and PDCP-C (control plane part of PDCP) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function (AMF) network elements, such as the access and mobility management function (AMF) in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the SDAP layer and PDCP-U (user plane part of PDCP) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the user plane function (UPF) network element in a 5G system, are responsible for data forwarding and receiving in terminal devices. The above CU and DU configurations are merely examples; the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as latency. Functions requiring low latency can be placed in the DU, while functions not requiring this latency can be placed in the CU. It is understood that network devices can be CU nodes, DU nodes, or devices including both CU and DU nodes. Moreover, the CU can be classified as a network device in the access network (RAN) or a network device in the core network (CN); there are no restrictions here.

[0105] In some examples, a DU is a logical node that carries the RLC layer, medium / media access control (MAC) layer, higher physical layer (Higher PHY) layer, and other functions. In some examples, a DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0106] In some examples, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a 3GPP TRP or RRH or other similar entity. In some examples, the Low-PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0107] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a lower-layer split cus-plane (LLS-CUS) interface through a fronthaul link. LLS-CUS may include LLS-C and LLS-U interfaces that provide the control plane (C-Plane) and user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0108] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0109] It should be noted that CU (or CU-CP and CU-UP), DU, or RU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open central unit (O-CU) or an open CU, DU can also be called an open distributed unit (O-DU), central unit control plane (CU-CP) can also be called an open central unit control plane (O-CU-CP) or an open CU-CP, central unit user plane (CU-UP) can also be called an open central unit user plane (O-CU-UP) or an open CU-UP, and RU can also be called an open radio unit (O-RU). This application does not impose any specific limitations. Any of the units CU, CU-CP, CU-UP, DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0110] In some deployments, the CU and DU implement some of the functions of the gNB. For example, the CU implements Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) layer functions, while the DU implements Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layer functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC or PDCP layer signaling, can also be considered as being sent by the DU, or by the DU+RU. It is understood that network devices can be CU nodes, DU nodes, or devices including both CU and DU nodes. Furthermore, the CU can be classified as a network device in the Access Network (RAN) or the Core Network (CN); no restrictions are placed here.

[0111] Optionally, network equipment can also be core network equipment. Core network equipment is responsible for access control, registration management, service management, mobility management, etc., of terminal equipment accessing the network. For example, core network equipment can be access and mobility management function (AMF) network elements, user plane function (UPF) network elements, session management function (SMF) network elements, or policy control function (PCF) network elements.

[0112] It should be noted that the network device can be the device or apparatus shown above, or a component (e.g., a chip), module, or unit in the device or apparatus shown above; this application does not limit the specifics.

[0113] To better understand the solutions provided in the embodiments of this application, some terms, concepts or processes involved in the embodiments of this application will be introduced below.

[0114] I. Power Consumption of Terminal Equipment

[0115] Please see Figure 5 , Figure 5This diagram illustrates the specifications of terminal devices in 4G and 5G. In the Long Term Evolution (LTE) system, the terminal device has a 1-transmit, 2-receive (1T2R) antenna, a transmit power of 23 dBm, and supports a bandwidth of 1.6 Mbps or 20 Mbps. In the NR system, the terminal device has a 2-transmit, 4-receive (2T4R) antenna, a transmit power of 26 dBm, and supports a bandwidth of 100 Mbps. As can be seen, the specifications of terminal devices in the NR system are significantly improved compared to those in the LTE system, and the power consumption of the terminal devices will also increase accordingly.

[0116] However, in the communication module, the largest portion of power consumption in downlink connected state terminal devices is the Physical Downlink Control Channel (PDCCH-only), which accounts for approximately 60% to 70% of the total downlink connected state power consumption. PDCCH-only refers to scenarios where the terminal device performs PDCCH detection and decoding within a specific time slot or search space, but no actual data transmission occurs. See also... Figure 6 , Figure 6 This diagram illustrates the presence and absence of data transmission. The gray boxes represent PDCCH + Physical Downlink Shared Channel (PDSCH), indicating data transmission, while the white boxes represent PDCCH-only, meaning no data transmission. Therefore, it can be seen that PDCCH-only consumes a significant portion of the total power consumption in the downlink connection state.

[0117] II. PDCCH Skipping Mechanism and LP-WUS Mechanism

[0118] To reduce the power consumption of terminal devices, a Physical Downlink Control Channel Skipping (PDCCH Skipping) mechanism and a Low-Power Wake-up Signal (LP-WUS) mechanism are proposed. Details are as follows:

[0119] The PDCCH Skipping mechanism refers to a network device instructing terminal devices to skip certain PDCCH detection cycles, thereby reducing the power consumption of these PDCCH-only invalid detections. See also... Figure 7 , Figure 7 This is a diagram illustrating PDCCH Skipping, where the terminal device skips some PDCCH checks after receiving instructions from the network device.

[0120] LP-WUS mechanism: The terminal device adopts a two-level PDCCH detection architecture, as detailed below: Please refer to Figure 8 , Figure 8This diagram illustrates how a low-power wake-up receiver (LP-WUR) and a main radio (MR) perform PDCCH monitoring. The LP-WUR on the terminal device monitors the wake-up signal (WUS) sent by the network device. When the monitoring is successful, i.e., WUS is detected, the MR is activated to complete PDCCH monitoring. At other times, the MR goes to sleep, thereby significantly reducing the power consumption of PDCCH-only invalid detection.

[0121] As can be seen from the above, with the continuous development of communication technology, the specifications of terminal devices are also constantly improving. For example, antenna size, system bandwidth, and transmission power have increased significantly, and the power consumption of terminal devices will also increase accordingly. Therefore, with the further development of communication technology, how to reduce the power consumption of terminal devices is a technical problem that urgently needs to be solved by those skilled in the art. In order to solve the above problem, the embodiments of this application propose the following solutions.

[0122] Please see Figure 9 , Figure 9 This is a schematic diagram of a communication method provided in an embodiment of this application. Figure 9 The method shown can be applied to terminal-side devices and network-side devices. The terminal-side device can be a terminal device, a component applied within the terminal device (e.g., a processor, chip, circuit, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The network-side device can be a network device, a component applied within the network device (e.g., a processor, chip, circuit, or chip system), or a logic module or software capable of implementing all or part of the network device's functions. The following... Figure 9 The embodiments shown are described using terminal-side devices as terminal equipment and network-side devices as network equipment as examples. The method includes, but is not limited to, the following steps:

[0123] Step S901: The terminal device sends service requirement information for at least one service to be scheduled.

[0124] In this process, the terminal device sends service request information for at least one service to be scheduled to the network device, and correspondingly, the network device receives service request information for at least one service to be scheduled from the terminal device. It should be noted that this can be done by one terminal device or multiple terminal devices sending such information.

[0125] The business requirement information includes at least one of the following: business packet size, business type, business latency requirement, business priority, or business traffic requirement. The business packet size can refer to the volume of the business-related data set transmitted or processed between systems; for example, the business packet size can be measured in bits or bytes. The business packet size can also be called the business data packet size, which is not limited in this embodiment. The business type can include one or more of the following: live streaming, gaming, voice, video, uplink, or downlink. The business latency requirement can refer to the specific latency requirements in different business scenarios. For example, when browsing a webpage, the latency requirement is relatively lenient, usually higher than 200 milliseconds. As another example, when conducting video conferencing, the latency requirement is relatively high, usually lower than 10 milliseconds, to ensure a real-time communication experience. For example, the business latency requirement can be measured in milliseconds (ms). The business latency requirement can also be called the business latency requirement, which is not limited in this embodiment. The business priority is used to measure the importance or urgency of the business to be scheduled. Priority services are processed first, while lower priority services are processed later. For example, service 1 has a priority of 1 and is a critical voice call; service 2 has a priority of 8 and is a video call. Since service 1 has a higher priority than service 2, service 1 is processed first, and service 2 is processed later. Service traffic requirements refer to the quantitative requirements for data transmission, processing, and network resources in a specific business scenario. Service traffic requirements can include one or more of the following: peak rate or average rate. Peak rate refers to the maximum instantaneous transmission rate required by the service (such as burst traffic). Average rate refers to the long-term average data throughput of the service.

[0126] In one possible implementation, the method further includes: the network device sending fourth configuration information to the terminal device, and correspondingly, the terminal device receiving the fourth configuration information from the network device.

[0127] Optionally, the network device receives service requirement information for at least one scheduled service from the terminal device, the service requirement information including service latency requirements. The method further includes: the network device sending fourth configuration information to the terminal device.

[0128] The fourth configuration information is used to configure the search space. The starting orthogonal frequency division multiplexing (OFDM) symbol number of the PDCCH, the PDCCH monitoring period, and the associated control resource set (CORESET) are encapsulated in the search space. Information such as the frequency domain resources occupied by the PDCCH in the frequency domain and the number of OFDM symbols occupied in the time domain are encapsulated in the CORESET. The aforementioned PDCCH is used to carry the data corresponding to the scheduled service. For example, if the service latency requirement of scheduled service 1 is lower than that of scheduled service 2, the period of the search space corresponding to scheduled service 1 is shorter than the period of the search space corresponding to scheduled service 2.

[0129] In other words, if a terminal device reports at least one service latency requirement for a service to be scheduled, the network device configures the search space as needed. For example, the period of the search space corresponding to the service to be scheduled with low service latency requirement is shorter than the period of the search space corresponding to the service to be scheduled with high service latency requirement.

[0130] In another possible implementation, the method further includes: the network device sending fifth configuration information to the terminal device, and correspondingly, the terminal device receiving the fifth configuration information from the network device.

[0131] Optionally, the network device receives service requirement information for at least one scheduled service from the terminal device, the service requirement information including service priority. The method further includes: the network device sending fifth configuration information to the terminal device.

[0132] The fifth configuration information is used to configure the bandwidth part (BWP), which is used to transmit the data corresponding to the scheduled service. For example, the service priority of scheduled service 1 is higher than that of scheduled service 2, and the BWP corresponding to scheduled service 1 is greater than that of scheduled service 2. This ensures that the data corresponding to the higher-priority scheduled service is transmitted quickly.

[0133] In another possible implementation, the method further includes: the network device sending first indication information to the terminal device, and correspondingly, the terminal device receiving the first indication information from the network device.

[0134] In this implementation, the terminal device may send service request information for at least one scheduled service based on a first indication message. The first indication message also indicates that centralized scheduling is enabled. Centralized scheduling may include scheduled services within a centralized processing service group. In one possible implementation, after receiving the first indication message from the network device, the terminal device sends service request information for at least one scheduled service to the network device. In another possible implementation, the protocol pre-configures a centralized scheduling mechanism, and the terminal device sends service request information for at least one scheduled service to the network device.

[0135] Optionally, the first indication information can be carried in RRC signaling, MAC control element, or dedicated signaling. For example, the first indication information can be k. 0min ≠0, terminal device receives k 0min Following ≠0, on the one hand, it confirms that centralized scheduling is enabled, and the terminal device sends service request information for at least one service to be scheduled. On the other hand, it indicates that the terminal device is allowed to perform cross-slot scheduling, that is, the PDSCH (downlink data) or PUSCH (uplink data) scheduled by PDCCH can be transmitted in a different time slot than in the same time slot, but delayed to a later time slot. For example, the first indication information can be indicated in the form of bits, such as the first indication information being 0 indicating that centralized scheduling is enabled ('ON'), and the first indication information being 1 indicating that centralized scheduling is disabled ('OFF').

[0136] Step S902: The network device groups at least one service to be scheduled based on the grouping rules to determine at least one service group.

[0137] Each of the at least one service group includes at least one service to be scheduled. The at least one service to be scheduled within each service group is continuous, for example, continuous in time slots. For example, the service to be scheduled within a service group can be represented by k, where k = 0, 1, 2, ..., K-1, and K represents that a service group includes K services to be scheduled. The grouping rules are related to service requirement information. When the service requirement information includes service packet size, the grouping rules include a range of service packet sizes. When the service requirement information includes service type, the grouping rules include the service type. When the service requirement information includes service latency requirements, the grouping rules include a range of service latency requirements. When the service requirement information includes service priority, the grouping rules include a range of service priority. When the service requirement information includes service traffic requirements, the grouping rules include a range of service traffic requirements. It should be noted that when the business requirement information includes at least two items, the grouping rule can be a combination of these two items. For example, if the business requirement information includes the business package size and the business latency requirement, the grouping rule could include the range of the business package size and the range of the business latency requirement. In other words, the grouping rule considers both the business package size and the business latency requirement. One possible implementation is to predefine priorities in the protocol; for example, the priority of the business package size is lower than that of the business latency requirement. Therefore, when grouping based on the business package size and the business latency requirement, if a conflict occurs, the business grouping based on the business latency requirement can take precedence. For an example, please refer to [link to example]. Figure 10 , Figure 10 This is a schematic diagram of a service group provided in an embodiment of this application. Service group 1 is determined based on the range of service packet size. Service group 1 includes service 1 to be scheduled, service 2 to be scheduled, and service 3 to be scheduled. The service latency requirement of service 1 to be scheduled is 50ms, the service latency requirement of service 2 to be scheduled is 80ms, and the service latency requirement of service 3 to be scheduled is 100ms. Since service 3 to be scheduled has the highest service latency requirement in service group 1, and the service latency requirements of service 1 and service 2 to be scheduled are lower than those of service 3 to be scheduled, service 1 and service 2 to be scheduled need to be scheduled first. Optionally, if service 3 to be scheduled in service group 1 exceeds the latency limit, which is determined based on the capabilities of the terminal device and / or the network device, then the network device and the terminal device can choose to schedule service 3 to be scheduled later.

[0138] The grouping rules include one or more of the following: the service packet sizes of services to be scheduled within the same service group fall within the same range; the service types of services to be scheduled within the same service group are the same; the service latency requirements of services to be scheduled within the same service group fall within the same range; the service priorities of services to be scheduled within the same service group fall within the same range; or the service traffic requirements of services to be scheduled within the same service group fall within the same range. Optionally, when multiple terminal devices send service requirement information for at least one service to be scheduled, the grouping rules may further include: the services to be scheduled within the same service group belong to the same terminal device.

[0139] Specifically, the situation where the package sizes of two pending services within the same business group fall within the same range can be defined as follows: if the package sizes of two pending services fall within the same range, then these two pending services belong to the same business group; conversely, if the package sizes of two pending services fall within different ranges, then these two pending services belong to different business groups. In one example, the business requirement information includes the package size, and the grouping rule includes the range of package sizes, for example, it could be: P k <10 Mbps, 10 Mbps ≤ P k <30 trillion, 30 trillion≤P k Among them, P k This represents the size of the service packets to be scheduled. Service packet size 1 is 6 MB, service packet size 2 is 15 MB, service packet size 3 is 5 MB, and service packet size 4 is 21 MB. Based on the above grouping rules, the network device determines service group 1 and service group 2. Service group 1 includes services 1 and 3 to be scheduled, and service group 2 includes services 2 and 4 to be scheduled. It should be noted that the sum of the service packet sizes of the services to be scheduled in a service group does not exceed a first threshold, which is determined based on the processing capabilities of the terminal device and / or the network device. The constraints on the processing capabilities of the terminal device include one or more of the following: temperature limits, continuous load, memory pressure, or battery consumption. In one example, Where, p k P represents the size of the service package to be scheduled in a service group. max This represents the first threshold. The first threshold can also be called the upper limit of centralized scheduling. The above method optimizes network performance and improves transmission efficiency. For example, scheduling services with larger packet sizes are grouped together, and scheduling services with smaller packet sizes are grouped together. By grouping scheduling services with similar or identical packet sizes together, frequent fragmentation when transmitting mixed large and small packets can be avoided, reducing processing latency and thus improving network transmission efficiency.

[0140] The requirement that services to be scheduled within the same service group have the same service type can be defined as follows: if two services to be scheduled have the same service type, then they belong to the same service group; conversely, if two services to be scheduled have different service types, then they belong to different service groups. In one example, service requirement information includes service type, and grouping rules also include service type. Service types include: live streaming, gaming, voice, video, uplink, or downlink. Specifically, if service 1, service 2, service 3, and service 4 to be scheduled are all live streaming services, then the network device determines service group 1 based on the aforementioned grouping rules. Service group 1 includes services to be scheduled 1, 2, 3, and 4. In the above method, since the service packages of the same service type to be scheduled are of similar size and have similar service latency requirements, the above grouping method, that is, grouping according to service type, is more conducive to completing centralized scheduling.

[0141] Specifically, the condition that the latency requirements of two services to be scheduled within the same service group fall within the same range can be defined as follows: if the latency requirements of two services to be scheduled fall within the same range, then these two services belong to the same service group; conversely, if the latency requirements of two services to be scheduled fall within different ranges, then these two services belong to different service groups. In one example, the service requirement information includes the latency requirement, and the grouping rule includes the range of the latency requirement, for example, d. k ≤100ms, 100ms≤d k ≤300ms,d k >300ms; where d k This represents the latency requirements of the services to be scheduled. Service 1 has a latency requirement of 50ms, Service 2 has a latency requirement of 30ms, Service 3 has a latency requirement of 150ms, and Service 4 has a latency requirement of 130ms. Based on the above grouping rules, the network device determines Service Group 1 and Service Group 2. Service Group 1 includes Services 1 and 2, and Service Group 2 includes Services 3 and 4. This method ensures that the latency requirements of services to be scheduled within the same service group fall within the same range, reducing grouping difficulty and not impacting user experience.

[0142] Specifically, the requirement that the service priorities of two pending services within the same service group fall within the same range can be interpreted as follows: if the service priorities of two pending services fall within the same range, then these two pending services belong to the same service group; conversely, if the service priorities of two pending services fall within different ranges, then these two pending services belong to different service groups. In one example, the service requirement information includes the service priority, and the grouping rule includes the range of the service priority, for example, 1 ≤ m. k ≤10,11≤m k ≤30, 31≤m k ≤70, 71≤m k ≤80, 81≤m k ≤255, where m k Indicates the service priority of the service to be scheduled, m k The smaller the value of m, the higher the priority of the service to be scheduled. k The larger the value of , the lower the priority of the service to be scheduled. Specifically, service 1 has a priority of 1, service 2 has a priority of 2, service 3 has a priority of 13, and service 4 has a priority of 14. Based on these grouping rules, the network device determines service group 1 and service group 2. Service group 1 includes services 1 and 2, and service group 2 includes services 3 and 4. This method, by grouping services according to their priority, ensures that high-priority services are transmitted first, while low-priority services are transmitted later, thereby improving service quality.

[0143] Specifically, the condition that the traffic demands of two pending services within the same business group fall within the same range can be defined as follows: if the traffic demands of two pending services fall within the same range, then these two pending services belong to the same business group; conversely, if the traffic demands of two pending services fall within different ranges, then these two pending services belong to different business groups. In one example, the business demand information includes the traffic demand, and the grouping rule includes the range of the traffic demand, which could be, for example: v k ≤50Mbps, 50Mbps<v k ≤1Gbps,v k >1Gbps; where v kThis represents the peak rate of the traffic demand for the services to be scheduled, where Mbps is the number of bits transmitted per second and Gbps is the number of gigabits transmitted per second. If the peak rate of service 1 to be scheduled is 50 Mbps and the peak rate of service 2 to be scheduled is 48 Mbps, then the network device determines service group 1 based on the above grouping rules. Service group 1 includes both services to be scheduled and service 2. This method can improve network resource utilization. For example, by grouping services with similar or identical peak rates, resource allocation can be dynamically adjusted to avoid congestion or resource idleness.

[0144] In one possible implementation, the method further includes: the network device sending second configuration information to the terminal device, and correspondingly, the terminal device receiving the second configuration information from the network device.

[0145] Optionally, after the network device determines at least one service group by grouping at least one service to be scheduled based on the grouping rules, the method further includes: the network device sending second configuration information to the terminal device.

[0146] The second configuration information is used to configure at least one discontinuous reception (DRX) cycle corresponding to at least one service group, with each service group associated with one DRX cycle. That is, after determining at least one service group, the network device can send the second configuration information to the terminal device. This second configuration information is used to configure at least one DRX cycle for the at least one service group, with each service group associated with one DRX cycle. It should be noted that "associated" can also be described as "bound" or "corresponding." A DRX cycle includes an onDuration period and a sleep period (Opportunity for DRX). During the onDuration period, the terminal device wakes up and monitors the PDCCH to check for scheduled data. If data is detected, it remains active; otherwise, it starts a sleep timer. During the sleep period, the terminal device shuts down its RF module and enters a low-power state, receiving no data. In one example, the network device determines two service groups based on packet rules: service group 1 and service group 2. Service group 1 is associated with DRX cycle 1, and service group 2 is associated with DRC cycle 2. The above methods can significantly reduce the power consumption of terminal devices and optimize the utilization of network resources.

[0147] In some possible embodiments, different service groups within at least one service group are associated with different DRX periods. For example, at least one service group includes a first service group and a second service group. The first service group is associated with a first DRX period, and the second service group is associated with a second DRX period. The latency requirement of the first service group is higher than that of the second service group, and the first DRX period is shorter than the second DRX period. The higher latency requirement of the first service group means that the latency requirement range of the scheduled services included in the first service group is smaller than that of the scheduled services included in the second service group. For example, the latency requirement range of the scheduled services included in the first service group is d. k ≤100ms, the latency requirement range for the services to be scheduled in the second service group is 100ms ≤ d. k ≤300ms. Optionally, the first DRX cycle being shorter than the second DRX cycle includes situations where the on-duration of the first DRX cycle and the on-duration of the second DRX cycle are equal, but the sleep period of the first DRX cycle is shorter than the sleep period of the second DRX cycle. Optionally, the first DRX cycle can be a short cycle, and the second DRX cycle can be a long cycle. See one example. Figure 11 , Figure 11 This is a schematic diagram illustrating different DRX cycles associated with different service groups, provided in an embodiment of this application. The network device determines two service groups based on grouping rules: service group 1 and service group 2. Service group 1 is associated with DRX cycle 1, and service group 2 is associated with DRC cycle 2. The service latency requirement of service group 1 is higher than that of service group 2. The on-duration period in DRX cycle 1 and DRX cycle 2 is the same, while the sleep period in DRX cycle 1 is shorter than that in DRX cycle 2. Optionally, when the service latency requirement of one service group in at least one service group is very high, the terminal device can disable the DRX mechanism corresponding to that service group. Consequently, the terminal device does not need to enter a sleep period and continues to transmit the data corresponding to that service group until the data transmission for that service group is complete.

[0148] In the above method, the data corresponding to the scheduled services included in the first service group can be transmitted faster than the data corresponding to the scheduled services included in the second service group, thereby ensuring the transmission latency of the scheduled services included in the first service group.

[0149] In some other possible embodiments, different service groups within at least one service group are associated with different DRX cycles. For example, at least one service group includes a first service group and a second service group. The first service group is associated with a first DRX cycle, and the second service group is associated with a second DRX cycle. The sum of the service packet sizes of the scheduled services included in the first service group is greater than the sum of the service packet sizes of the scheduled services included in the second service group, and the first DRX cycle is greater than the second DRX cycle. Optionally, the first DRX cycle can be a long cycle, and the second DRX cycle can be a short cycle. Optionally, the first DRX cycle being greater than the second DRX cycle includes situations where the on-duration of the first DRX cycle and the on-duration of the second DRX cycle are equal, but the dormancy period of the first DRX cycle is greater than the dormancy period of the second DRX cycle. In one example, the network device determines two service groups based on packet rules, namely service group 1 and service group 2. Service group 1 is associated with DRXcycle 1, and service group 2 is associated with DRC cycle 2. The sum of the service packet sizes of the services to be scheduled in service group 1 is 50 Mbps, and the sum of the service packet sizes of the services to be scheduled in service group 2 is 30 Mbps. 50 Mbps is greater than 30 Mbps. The on-duration period in DRXcycle 1 is the same as that in DRXcycle 2, and the dormancy period in DRXcycle 1 is greater than that in DRXcycle 2.

[0150] In the above method, the data corresponding to the scheduled services included in the second service group can be transmitted faster than the data corresponding to the scheduled services included in the first service group, which is more conducive to data transmission.

[0151] Step S903: The network device sends the first configuration information.

[0152] In this process, the network device sends first configuration information to the terminal device, and the terminal device receives the first configuration information from the network device.

[0153] The first configuration information is used to schedule the data corresponding to the scheduled services included in each service group. Optionally, the first configuration information can be a DCI, which may include the first indication information in step S901.

[0154] In another possible implementation, the method further includes: the network device sending second indication information to the terminal device, and correspondingly, the terminal device receiving the second indication information from the network device.

[0155] The second indication information is used to indicate one of the following: switching from centralized scheduling to decentralized scheduling, or switching from decentralized scheduling to centralized scheduling. The second indication information is also used to indicate one of the following: switching from cross-timeslot scheduling to simultaneous-timeslot scheduling, or switching from simultaneous-timeslot scheduling to cross-timeslot scheduling. Simultaneous-timeslot scheduling includes the transmission of PDSCH (downlink data) or PUSCH (uplink data) scheduled by PDCCH within the same time slot.

[0156] Optionally, the second indication information can be carried in the first configuration information. Optionally, the network device can dynamically adjust k based on the implicit indication configured for the bandwidth part (BWP). 0min This allows for switching between centralized and decentralized scheduling. For example, different k can be configured for different BWPs. 0min Values, such as BWP1:k 0min =0, applicable to ultra-reliable low-latency communication (URLLC) services, BWP2:k 0min =1, applicable to enhanced mobile broadband (eMBB) services. When a terminal device switches from URLLC services to eMBB services, the network device instructs the terminal device to perform BWP handover through DCI, for example, from BWP1 to BWP2, implicitly indicating a switch from decentralized scheduling to centralized scheduling; when a terminal device switches from eMBB services to URLLC services, the network device instructs the terminal device to perform BWP handover through DCI, for example, from BWP2 to BWP1, implicitly indicating a switch from centralized scheduling to decentralized scheduling.

[0157] In another possible implementation, the network device will not send configuration information to the terminal device until the data transmission corresponding to the scheduled service included in the centralized scheduling service group is completed. This configuration information is used to activate unauthorized scheduling. In this way, the transmission of scheduled services during the centralized scheduling process can be prioritized.

[0158] During centralized scheduling, some services with higher priority or lower latency requirements need to be processed. The network or protocol needs to define a conflict handling mechanism, as follows:

[0159] In another possible implementation, at least one service group includes a third service group associated with a third DRX cycle. The method further includes: the network device sending third configuration information to the terminal device, and the terminal device receiving the third configuration information from the network device.

[0160] In some possible embodiments, the third configuration information is used to configure the time-frequency resources for the data corresponding to the first service, which includes part or all of the sleep period of the third DRX cycle. The first service does not belong to at least one scheduled service. Optionally, when the first service is an ultra-high priority service, such as a mission-critical voice call (e.g., emergency service), the time-frequency resources may include the entire sleep period of the third DRX cycle, that is, the entire sleep period of the third DRX cycle is used to transmit the data corresponding to the first service.

[0161] In some possible embodiments, the third configuration information is used to configure the fourth DRX cycle. During the dormant period of the third DRX cycle, the fourth DRX cycle is used to transmit the first service, which does not belong to at least one scheduled service. That is, during the third DRX cycle, when the network device centrally schedules the scheduled services included in the third service group, if a first service needs to be scheduled, the network device sends the third configuration information to the terminal device. This third configuration information is used to configure the fourth DRX cycle, and during the dormant period of the third DRX cycle, the fourth DRX cycle is used to transmit the first service. Optionally, this fourth DRX cycle expires in the next cycle of the third DRX cycle. Optionally, the fourth DRX cycle can also be called a temporary DRX cycle. See details below. Figure 12 , Figure 12 This is a schematic diagram of a third service group and a first service scheduling according to an embodiment of this application. The third service group includes a service to be scheduled, 1, and a service to be scheduled, 2. The third service group is associated with DRX cycle 1, and the first service corresponds to DRX cycle 2. DRX cycle 2 is within the sleep period of DRX cycle 1. In the above method, a conflict handling mechanism is defined when the service to be scheduled and the first service included in the third service group conflict, thereby ensuring the normal transmission of the service to be scheduled and the first service included in the third service group.

[0162] In another possible implementation, at least one service group includes a third service group associated with a third DRX cycle. The method further includes: the terminal device starting an inactivity timer, the extended wake-up time of which is used to transmit data corresponding to the first service. Optionally, the sum of the extended wake-up time of the inactivity timer and the active period in the third DRX cycle does not exceed the sum of the times of one cycle in the third DRX cycle; otherwise, the terminal device prioritizes transmitting the first service or disables the centralized scheduling mechanism by default. See details below. Figure 13 , Figure 13This is another schematic diagram of scheduling a third service group and a first service provided in an embodiment of this application. The third service group is associated with DRX cycle 1. The sum of the extended wake-up time of the inactive timer and the active period (onduration) in DRX cycle 1 does not exceed the sum of the time of one cycle in DRX cycle 1. That is, the extended wake-up time of the inactive timer is at most equal to the sleep period in DRX cycle 1. In the above method, a conflict handling mechanism is defined when the scheduled services included in the third service group and the first service conflict, thereby ensuring the normal transmission of the scheduled services included in the third service group and the first service.

[0163] exist Figure 9 In the method described, by having the terminal device send service requirement information for at least one scheduled service, the network device can perceive the relevant information of the terminal device's services, which is beneficial for service grouping. By having the network device group the at least one scheduled service based on grouping rules to determine at least one service group, scheduled services with similar or identical service requirement information can be grouped together, which is more conducive to centralized processing of the scheduled services included in the service group. By having the network device send first configuration information, which is used to schedule the data corresponding to the scheduled services included in each service group, the energy consumption of the terminal device can be reduced, and the energy consumption of the network device can also be saved, thus achieving energy saving at both ends. For example, if a service group includes three consecutive scheduled services, the terminal device only needs to open and close the transceiver channel once. Compared to the prior art, where the three scheduled services are not consecutive and the terminal device needs to open and close the transceiver channel three times, this application can reduce the number of times the terminal device frequently opens and closes the transceiver channel, thereby reducing the terminal device's energy consumption and achieving energy saving. For example, if a service group includes three consecutive services to be scheduled, the network device only needs to send configuration information once. In contrast, in the existing technology, the three services to be scheduled are not consecutive, and the network device needs to send configuration information three times, thus saving signaling overhead and network device energy consumption.

[0164] It should be noted that when the embodiments of this application are applied to an open RAN architecture, for example, the network device may include a CU, DU, or RU, and the interaction between the CU, DU, or RU and the terminal device can be referred to Figure 9 ,Will Figure 9The network devices in the diagram are replaced by CU, DU, or RU. In one possible implementation, the network devices include CU and DU. The terminal device sending service requirement information for at least one scheduled service may include the terminal device sending this information to the CU in the network device; alternatively, the CU in the network device sends this information to the DU. The DU in the network device groups the at least one scheduled service based on packet rules to determine at least one service group. The DU in the network device then sends first configuration information to the CU. The CU in the network device then sends the first configuration information to the terminal device.

[0165] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below.

[0166] Please see Figure 14 , Figure 14 This is a schematic diagram of the structure of a communication device 1400 provided in an embodiment of this application. The communication device 1400 may include modules, units or means corresponding to the methods / operations / steps / actions performed by the terminal device or network device in the above method embodiments. The modules, units or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0167] In one possible implementation, the communication device 1400 may include a processing unit 1401 and a transceiver unit 1402, the specific details of which are as follows:

[0168] The processing unit 1401 is used for data processing. The transceiver unit 1402 can implement corresponding communication functions. The transceiver unit 1402 can also be called a communication interface or a communication module.

[0169] Optionally, the communication device 1400 may further include a storage unit, which can be used to store instructions and / or data. The processing unit 1401 can read the instructions and / or data in the storage module to enable the implementation of the aforementioned method embodiments.

[0170] Optionally, the transceiver unit 1402 may include a sending unit and a receiving unit. The sending unit is used to perform the sending operation in the above method embodiments. The receiving unit is used to perform the receiving operation in the above method embodiments.

[0171] It should be noted that the communication device 1400 may include a transmitting unit but not a receiving unit. Alternatively, the communication device 1400 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described scheme executed by the communication device 1400 includes both transmitting and receiving actions.

[0172] Optionally, the communication device 1400 is used to perform the above. Figure 9 The actions performed by the terminal device in the illustrated embodiment are shown above. For details, please refer to the above. Figure 9 The relevant descriptions in the illustrated embodiments are not elaborated here. For example, the communication device 1400 is used to execute the following scheme:

[0173] The processing unit 1401 is used to send service requirement information of at least one service to be scheduled through the transceiver unit 1402; the transceiver unit 1402 is used to receive first configuration information, which is used to schedule the data corresponding to the service to be scheduled included in each of the at least one service groups, wherein the at least one service group is determined by grouping the at least one service to be scheduled based on a grouping rule, and the grouping rule is related to the service requirement information.

[0174] In one possible implementation, the business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

[0175] In another possible implementation, the grouping rule is related to the business requirement information, and the grouping rule includes one or more of the following: the service package size of the services to be scheduled in the same business group falls within the same range; the service type of the services to be scheduled in the same business group is the same; the service latency requirements of the services to be scheduled in the same business group fall within the same range; the service priority of the services to be scheduled in the same business group falls within the same range; or the service traffic requirements of the services to be scheduled in the same business group fall within the same range.

[0176] In another possible implementation, the transceiver unit 1402 is further configured to receive second configuration information, which is used to configure at least one discontinuous reception DRX cycle corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX cycle.

[0177] In another possible implementation, the DRX cycles associated with different business groups within the at least one business group are different.

[0178] In another possible implementation, the at least one service group includes a first service group and a second service group, the first service group being associated with a first DRX cycle and the second service group being associated with a second DRX cycle, the service latency requirement of the first service group being higher than that of the second service group, and the first DRX cycle being shorter than that of the second DRX cycle.

[0179] In another possible implementation, the transceiver unit 1402 is also configured to receive first indication information, the service requirement information for sending at least one scheduled service is sent based on the first indication information.

[0180] In another possible implementation, the at least one service group includes a third service group associated with a third DRX cycle. The transceiver unit 1402 is also used to receive third configuration information, which is used to configure the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle. The first service does not belong to the at least one service to be scheduled.

[0181] It should be noted that the implementation and beneficial effects of each module can be found by referring to [the relevant documentation / reference]. Figure 9 The corresponding description of the method embodiments shown.

[0182] Optionally, the communication device 1400 is used to perform the above. Figure 9 The actions performed by the network device in the illustrated embodiment are shown above. For details, please refer to the above. Figure 9 The relevant descriptions in the illustrated embodiments are not elaborated here. For example, the communication device 1400 is used to execute the following scheme:

[0183] The transceiver unit 1402 is used to receive service requirement information of at least one service to be scheduled; the processing unit 1401 is used to group the at least one service to be scheduled based on a grouping rule to determine at least one service group, each service group including at least one service to be scheduled, the grouping rule being related to the service requirement information; the transceiver unit 1402 is used to send first configuration information, the first configuration information being used to schedule the data corresponding to the service to be scheduled included in each service group.

[0184] In one possible implementation, the business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

[0185] In another possible implementation, the grouping rule is related to the business requirement information, and the grouping rule includes one or more of the following: the service package size of the services to be scheduled in the same business group falls within the same range; the service type of the services to be scheduled in the same business group is the same; the service latency requirements of the services to be scheduled in the same business group fall within the same range; the service priority of the services to be scheduled in the same business group falls within the same range; or the service traffic requirements of the services to be scheduled in the same business group fall within the same range.

[0186] In another possible implementation, the transceiver unit 1402 is further configured to send second configuration information, which is used to configure at least one discontinuous reception DRX cycle corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX cycle.

[0187] In another possible implementation, the DRX cycles associated with different business groups within the at least one business group are different.

[0188] In another possible implementation, the at least one service group includes a first service group and a second service group, the first service group being associated with a first DRX cycle and the second service group being associated with a second DRX cycle, the service latency requirement of the first service group being higher than that of the second service group, and the first DRX cycle being shorter than that of the second DRX cycle.

[0189] In another possible implementation, the transceiver unit 1402 is further configured to send first indication information, which instructs the terminal device to send service requirement information for the at least one scheduled service.

[0190] In another possible implementation, the at least one service group includes a third service group associated with a third DRX cycle. The transceiver unit 1402 is also used to send third configuration information, which is used to configure the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle. The first service does not belong to the at least one service to be scheduled.

[0191] It should be noted that the implementation and beneficial effects of each module can be found by referring to [the relevant documentation / reference]. Figure 9 The corresponding description of the method embodiments shown is provided below. The module division in the embodiments of this application is illustrative and is merely a logical functional division; other division methods may be used in actual implementation.

[0192] The processing unit 1401 in the above embodiments can be implemented by at least one processor or processor-related circuitry. The transceiver unit 1402 can be implemented by a transceiver or transceiver-related circuitry. The transceiver unit 1402 can also be referred to as a communication module or communication interface. The storage module can be implemented by at least one memory.

[0193] Please see Figure 15 , Figure 15 This is a schematic diagram of the structure of a communication device 1500 provided in an embodiment of this application. The communication device 1500 may include modules, units, or means that correspond one-to-one with the methods / operations / steps / actions performed by the terminal device in the above method embodiments. The modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0194] The communication device 1500 includes a processor 1501. Optionally, the communication device 1500 also includes a memory 1502. Optionally, the communication device 1500 also includes a transceiver 1503, which includes a transmitter 15031, a receiver 15032, and an antenna 15033. The receiver 15032 can be used to receive transmission control information through the antenna 15033, and the transmitter 15031 can be used to send transmission feedback information to network devices through the antenna 15033. Optionally, the processor 1501 can be integrated with the memory 1502.

[0195] The memory 1502 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), which is used to store computer programs or instructions.

[0196] Processor 1501 can be one or more central processing units (CPUs). When processor 1501 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0197] The processor 1501 in the communication device 1500 is used to read computer programs or instructions stored in the memory 1502 to implement the functions of the processing unit, and the transceiver 1503 in the communication device 1500 is used to implement the functions of the transceiver unit.

[0198] Please see Figure 16 , Figure 16 This is a schematic diagram of the structure of another communication device 1600 provided in the embodiments of this application. The communication device 1600 may include modules, units or means corresponding to the methods / operations / steps / actions performed by the network device in the above method embodiments. The modules, units or means may be hardware circuits or software, or hardware circuits combined with software.

[0199] The communication device 1600 includes a processor 1601. Optionally, the communication device 1600 also includes a memory 1602. Optionally, the communication device 1600 also includes a transceiver 1603, which includes a transmitter 16031, a receiver 16032, and an antenna 16033. The receiver 16032 can be used to receive transmission control information through the antenna 16033, and the transmitter 16031 can be used to send transmission feedback information to network devices through the antenna 16033. Optionally, the processor 1601 can be integrated with the memory 1602.

[0200] The memory 1602 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), which is used to store computer programs or instructions.

[0201] Processor 1601 can be one or more central processing units (CPUs). When processor 1601 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0202] The processor 1601 in the communication device 1600 is used to read computer programs or instructions stored in the memory 1602 to implement the functions of the aforementioned processing unit, and the transceiver 1603 in the communication device 1600 is used to implement the functions of the aforementioned transceiver unit.

[0203] This application also provides a chip device including at least one processor for executing computer programs or instructions to cause the processor to perform the methods provided in the above embodiments.

[0204] In one possible implementation, the input of the chip device corresponds to the receiving operation in any of the above embodiments, and the output of the chip device corresponds to the sending operation in any of the above embodiments.

[0205] Optionally, the processor is coupled to the memory via an interface.

[0206] Optionally, the chip device may also include a memory storing computer program instructions.

[0207] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed on a processor, implement the method performed by a terminal device or network device in the above method embodiments.

[0208] This application also provides a computer program product, which includes a computer program or instructions that, when run on a processor, implement the method executed by a terminal device or network device in the above method embodiments.

[0209] This application also provides a communication system, which includes the terminal device and the network device described in the above embodiments. The terminal device is used to perform some or all of the operations performed by the terminal device in the above method embodiments, and the network device is used to perform some or all of the operations performed by the network device in the above method embodiments.

[0210] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0211] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0212] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0213] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0214] In the description of this application, terms such as "first", "second", "S901" or "S902" are used only for the purpose of distinguishing descriptions and for the convenience of context. Different sequence numbers do not have specific technical meanings themselves and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying the order of execution of operations. The order of execution of each process should be determined by its function and internal logic.

Claims

1. A communication method characterized by comprising: include: Send service requirement information for at least one service to be scheduled; Receive first configuration information, which is used to schedule data corresponding to the scheduled services included in each of at least one service group. The at least one service group is determined by grouping the at least one scheduled services based on grouping rules, and the grouping rules are related to the service requirement information.

2. The method of claim 1, wherein, The business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

3. The method according to claim 1 or 2, wherein the grouping rule is related to the business requirement information, and the grouping rule includes one or more of the following: The size of the service packets of services to be scheduled in the same service group falls within the same range. The business types of the services to be scheduled within the same business group are the same; The latency requirements of services to be scheduled within the same business group fall within the same range. The service priorities of services to be scheduled within the same service group fall into the same range. or The traffic demands of services to be scheduled within the same business group fall into the same range.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Receive second configuration information, which is used to configure at least one discontinuous reception DRX period corresponding to the at least one service group, and each service group in the at least one service group is associated with one DRX period.

5. The method according to claim 4, characterized in that, The DRX cycles associated with different business groups in at least one business group are different.

6. The method of claim 5, wherein, The at least one service group includes a first service group and a second service group, wherein the first service group is associated with a first DRX period and the second service group is associated with a second DRX period. The latency requirement of the first service group is higher than that of the second service group, and the first DRX period is shorter than the second DRX period.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The first instruction information is received, and the service requirement information for sending at least one service to be scheduled is sent based on the first instruction information.

8. The method according to any one of claims 1-7, characterized in that, The at least one service group includes a third service group, the third service group being associated with a third DRX cycle, and the method further includes: Receive third configuration information, which is used to configure the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle. The first service does not belong to the at least one service to be scheduled.

9. A communication method characterized by comprising: include: Receive service request information for at least one service to be scheduled; Based on the grouping rules, the at least one service to be scheduled is grouped to determine at least one service group. Each service group includes at least one service to be scheduled. The grouping rules are related to the service requirement information. Send first configuration information, which is used to schedule the data corresponding to the scheduled services included in each service group.

10. The method of claim 9, wherein, The business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

11. The method according to claim 9 or 10, wherein the grouping rule is related to the business requirement information, and the grouping rule includes one or more of the following: The size of the service packets of services to be scheduled in the same service group falls within the same range. The business types of the services to be scheduled within the same business group are the same; The latency requirements of services to be scheduled within the same business group fall within the same range. The service priorities of services to be scheduled within the same service group fall into the same range. or The traffic demands of services to be scheduled within the same business group fall into the same range.

12. The method according to any one of claims 9-11, characterized in that, The method further includes: Send second configuration information, which is used to configure at least one discontinuous reception DRX period corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX period.

13. The method according to claim 12, characterized in that, The DRX cycles associated with different business groups in at least one business group are different.

14. The method of claim 13, wherein, The at least one service group includes a first service group and a second service group, wherein the first service group is associated with a first DRX period and the second service group is associated with a second DRX period. The latency requirement of the first service group is higher than that of the second service group, and the first DRX period is shorter than the second DRX period.

15. The method according to any one of claims 9-14, characterized in that, The method further includes: Send a first instruction message, which is used to instruct the terminal device to send the service requirement information of the at least one service to be scheduled.

16. The method according to any one of claims 9-15, characterized in that, The at least one service group includes a third service group, the third service group being associated with a third DRX cycle, and the method further includes: Send third configuration information, which is used to configure the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle. The first service does not belong to the at least one service to be scheduled.

17. A communications device, characterized by The communication device includes a transceiver unit and a processing unit. The processing unit is used to send service requirement information of at least one service to be scheduled through the transceiver unit. Receive first configuration information, which is used to schedule data corresponding to the scheduled services included in each of at least one service group. The at least one service group is determined by grouping the at least one scheduled services based on grouping rules, and the grouping rules are related to the service requirement information.

18. The apparatus of claim 17, wherein, The business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

19. The apparatus according to claim 17 or 18, wherein the grouping rule is related to the service requirement information, and the grouping rule includes one or more of the following: The size of the service packets of services to be scheduled in the same service group falls within the same range. The business types of the services to be scheduled within the same business group are the same; The latency requirements of services to be scheduled within the same business group fall within the same range. The service priorities of services to be scheduled within the same service group fall into the same range. or The traffic demands of services to be scheduled within the same business group fall into the same range.

20. The apparatus according to any one of claims 17-19, characterized in that, The transceiver unit is further configured to receive second configuration information, which is used to configure at least one discontinuous reception DRX period corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX period.

21. The apparatus according to claim 20, characterized in that, The DRX cycles associated with different business groups in at least one business group are different.

22. The apparatus according to claim 21, characterized in that, The at least one service group includes a first service group and a second service group, wherein the first service group is associated with a first DRX period and the second service group is associated with a second DRX period. The latency requirement of the first service group is higher than that of the second service group, and the first DRX period is shorter than the second DRX period.

23. The apparatus according to any one of claims 17-22, characterized in that, The transceiver unit is also configured to receive first indication information, wherein the service requirement information for sending at least one scheduled service is sent based on the first indication information.

24. The apparatus according to any one of claims 17-23, characterized in that, The at least one service group includes a third service group, which is associated with a third DRX cycle. The transceiver unit is further configured to receive third configuration information, which is used to configure the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle, and the first service does not belong to the at least one scheduled service.

25. A communication device, characterized in that, The communication device includes a transceiver unit and a processing unit. The transceiver unit is used to receive service requirement information for at least one service to be scheduled. The processing unit is configured to group the at least one service to be scheduled based on a grouping rule to determine at least one service group, wherein each service group includes at least one service to be scheduled, and the grouping rule is related to the service requirement information. The transceiver unit is used to send first configuration information, which is used to schedule the data corresponding to the scheduled services included in each service group.

26. The apparatus according to claim 25, characterized in that, The business requirement information includes at least one of the following: business package size, business type, business latency requirement, business priority, or business traffic requirement.

27. The apparatus according to claim 25 or 26, wherein the grouping rule is related to the service requirement information, and the grouping rule includes one or more of the following: The size of the service packets of services to be scheduled in the same service group falls within the same range. The business types of the services to be scheduled within the same business group are the same; The latency requirements of services to be scheduled within the same business group fall within the same range. The service priorities of services to be scheduled within the same service group fall into the same range. or The traffic demands of services to be scheduled within the same business group fall into the same range.

28. The apparatus according to any one of claims 25-27, characterized in that, The transceiver unit is further configured to send second configuration information, which is used to configure at least one discontinuous reception DRX period corresponding to the at least one service group, wherein each service group in the at least one service group is associated with one DRX period.

29. The apparatus according to claim 28, characterized in that, The DRX cycles associated with different business groups in at least one business group are different.

30. The apparatus according to claim 29, characterized in that, The at least one service group includes a first service group and a second service group, wherein the first service group is associated with a first DRX period and the second service group is associated with a second DRX period. The latency requirement of the first service group is higher than that of the second service group, and the first DRX period is shorter than the second DRX period.

31. The apparatus according to any one of claims 25-30, characterized in that, The transceiver unit is further configured to send first indication information, which instructs the terminal device to send service requirement information for the at least one scheduled service.

32. The apparatus according to any one of claims 25-31, characterized in that, The at least one service group includes a third service group, which is associated with a third DRX cycle. The transceiver unit is further configured to send third configuration information, which is used to configure the time-frequency resources of the data corresponding to the first service. The time-frequency resources include part or all of the sleep period of the third DRX cycle, and the first service does not belong to the at least one scheduled service.

33. A communication device, characterized in that, The apparatus includes at least one processor, which is configured to invoke a computer program or instructions stored in a memory to perform the method as described in any one of claims 1-8.

34. A communication device, characterized in that, The apparatus includes at least one processor, which is configured to invoke a computer program or instructions stored in a memory to perform the method as described in any one of claims 9-16.

35. A communication system, characterized in that, The communication system includes: the apparatus as described in claim 33 and the apparatus as described in claim 34.

36. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a processor, implement the method as described in any one of claims 1-16.

37. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when run on a processor, implement the method as described in any one of claims 1-16.