Communication method and apparatus, and readable storage medium

Abstract

Embodiments of the present application provide a communication method and apparatus, and a readable storage medium. The method mainly comprises: receiving configuration information, wherein the configuration information comprises a plurality of data scheduling index values, and the data scheduling index values are used for associating with corresponding downlink scheduling intervals; sending first information to a second communication apparatus, wherein the first information indicates a downlink scheduling interval of data, and the downlink scheduling interval of the data is determined on the basis of the configuration information; and receiving the data sent by the second communication apparatus on the basis of the downlink scheduling interval. By implementing the embodiments of the present application, energy-saving scheduling in RANs can be implemented without relying on AFs to provide operations and maintenance feature information, thereby improving the flexibility of energy-saving scheduling in RANs.

Description

A communication method, apparatus and readable storage medium

[0001] This application claims priority to Chinese Patent Application No. 202410700451.X, filed on May 30, 2024, entitled "A Communication Method, Apparatus and Readable Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a communication method, apparatus and readable storage medium. Background Technology

[0003] As base station energy consumption continues to rise, operators' operating costs are increasing. To reduce base station energy consumption, a common approach is to employ different levels of shutdown techniques during periods of no data transmission in the time domain. For example, symbol shutdown can be used when there are no data transmission symbols, or the network can use scheduling methods to aggregate data transmissions that were originally scattered in the time domain, increasing the time without data transmission and thus increasing the shutdown probability, thereby achieving network energy saving. Cell discontinuous transmission (DTX) technology allows the network to perform downlink transmission with terminals only during specified time periods, while not performing downlink transmission during other time periods, thus allowing for corresponding shutdown techniques and further achieving network energy saving.

[0004] Quality of Service (QoS) refers to the network services that provide differentiated service quality to businesses under limited resources. It mainly involves two aspects: one is the specific indicators (parameters) characterizing QoS, and the other is how to guarantee these indicators, i.e., the mechanisms for implementing QoS. Fifth generation (5G) introduced QoS streams. All data streams within the same QoS stream will receive the same QoS guarantees (e.g., scheduling policies, buffer queue management). Different QoS guarantees require different QoS streams. Currently, the configuration and rule formulation of dedicated QoS streams rely on the cooperation of over-the-top (OTT) applications. That is, OTT application vendors provide data transmission requirements to the network. OTT applications interact with network elements such as network exposure function (NEF), policy control function (PCF), and session management function (SMF) through application functions (AF) or application servers (AS), enabling the SMF to generate matching dedicated QoS stream configurations and rules. This approach requires the radio access network (RAN) element to know the QoS configuration of all arriving data. Furthermore, when the AF (Automatic Access Parameter) is not enabled, the RAN element can only perform energy-saving scheduling based on a single QoS parameter, which greatly limits its scheduling flexibility.

[0005] Therefore, how to break free from dependence on the service characteristic information provided by AF, improve the flexibility of RAN network element energy-saving scheduling, and realize RAN network element energy-saving scheduling is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method, apparatus, and readable storage medium that pre-configures DRB or scheduling policy for multiple different downlink scheduling intervals and transmits data according to the reported selected DRB or scheduling policy. This can achieve RAN energy-saving scheduling without the need for OTT applications or relying on AF to provide service characteristic information, thereby improving the flexibility of RAN energy-saving scheduling.

[0007] In a first aspect, a communication method is provided, which is applied to a first communication device. The method includes: receiving configuration information, which includes multiple data scheduling index values, the data scheduling index values ​​being used to associate corresponding downlink scheduling intervals; sending first information (or data scheduling information) to a second communication device, the first information indicating the downlink scheduling interval of data, the first information being determined based on the configuration information; and receiving the data sent by the second communication device based on the downlink scheduling interval.

[0008] In implementing the embodiments of this application, the second communication device pre-configures multiple data scheduling index values ​​and associates them with downlink scheduling intervals. The first communication device determines the downlink scheduling interval that meets the service requirements based on AT commands and configuration information and notifies it to the second communication device. The second communication device uses the downlink scheduling interval to send data. In this way, the dependence on OTT applications and AS is eliminated, the interaction with core network elements is reduced, the flexibility of RAN energy-saving scheduling is improved, the occupation of core network resources is reduced, and the efficiency of RAN energy-saving scheduling is improved.

[0009] In one alternative implementation, the data scheduling index value includes a DRB index value, and the first communication device determines the DRB corresponding to carry the data based on the attention AT command and multiple DRB index values.

[0010] By implementing the embodiments of this application, the second communication device can pre-configure multiple DRBs to achieve flexible energy-saving scheduling. Compared with configuring only one DRB, it can reduce the time spent on subsequent RRC reconfiguration and adding DRBs. Furthermore, the first communication device can determine the DRB that best meets the requirements for carrying data based on AT commands and DRB index values.

[0011] In one alternative implementation, the first communication device adds a first indication (e.g., a Reflective Communication Quality (QoS) tag RQI) to the SDAP packet header and sends the SDAP packet to the second communication device via the determined DRB for carrying data.

[0012] By implementing the embodiments of this application, the RQI mechanism can be used to instruct the second communication device to update the SDAP mapping rules. RQI only occupies 1 bit, which can reduce the occupation of resources in the SDAP packet header.

[0013] In one alternative implementation, the data scheduling index value includes a DRB index value, and the first communication device determines the DRB index value corresponding to the data carrier based on AT commands and multiple DRB index values.

[0014] By implementing the embodiments of this application, the second communication device can pre-configure multiple DRBs to achieve flexible energy-saving scheduling. Compared with configuring only one DRB, it can reduce the time spent on subsequent RRC reconfiguration and adding DRBs. Furthermore, the first communication device can determine the most suitable DRB index value for carrying data based on AT commands and DRB index values.

[0015] In one optional implementation, the data scheduling index value includes a scheduling policy index value, and the first communication device determines the scheduling policy index value corresponding to the data based on the AT command and the scheduling policy index value.

[0016] By implementing the embodiments of this application, the second communication device can pre-configure multiple scheduling strategies to achieve flexible energy-saving scheduling, and the first communication device can determine the scheduling strategy index value that best meets the requirements for carrying data based on AT commands and scheduling strategy index values.

[0017] In one alternative implementation, the first communication device sends data scheduling information to the second communication device via a MAC CE, the MAC CE including a scheduling policy index value.

[0018] By implementing the embodiments of this application, the scheduling policy index value can be carried through the MAC CE, enabling the second communication device to achieve flexible energy-saving scheduling at the MAC layer.

[0019] In one alternative implementation, before the first communication device receives configuration information, an RRC connection is established with the second communication device, and the first communication device receives RRC signaling sent by the second communication device, the RRC signaling including configuration information.

[0020] By implementing the embodiments of this application, the first communication device and the second communication device can interact with RRC signaling through a pre-established RRC connection, without having to occupy additional communication resources to send configuration information, which can improve resource utilization.

[0021] In one alternative implementation, the maximum downlink scheduling interval is less than or equal to the packet delay budget value (PDB) of the default QoS.

[0022] By implementing the embodiments of this application, the setting value of the downlink scheduling interval is referenced to the PDB of the default QoS. This ensures that the maximum value of the configured downlink scheduling interval does not exceed the PDB of the default QoS, thereby ensuring that the configured downlink scheduling interval can meet the latency requirements of the service and prevent extreme situations from affecting the user experience.

[0023] Secondly, a communication method is provided. This method can be applied to a second communication device, a chip within the second communication device, or a logic module or software capable of implementing all or part of the functions of the second communication device. The method includes: generating configuration information, which includes multiple data scheduling index values ​​used to associate corresponding downlink scheduling intervals; sending the configuration information to a first communication device; receiving data scheduling information sent by the first communication device, which indicates the downlink scheduling interval for data; and sending data to the first communication device according to the data scheduling information.

[0024] In one optional implementation, the data scheduling index value includes a DRB index value. The first communication device receives an SDAP packet, and the header of the SDAP packet includes a first indication (e.g., a Reflection Communication Quality (QoS) tag, RQI). The DRB corresponding to the data can be determined based on the first indication. Data is then sent to the first communication device using the DRB corresponding to the SDAP packet.

[0025] In one optional implementation, the data scheduling index value includes a DRB index value, and the header of the SDAP packet sent by the first communication device includes the DRB index value; data is sent to the first communication device through the DRB corresponding to the DRB index value.

[0026] In one optional implementation, the data scheduling index value includes a scheduling policy index value; the system receives a MAC CE sent by the first communication device, the MAC CE including the scheduling policy index value; and sends data to the first communication device through the scheduling policy corresponding to the scheduling policy index value.

[0027] In one alternative implementation, before sending the configuration information to the first communication device, an RRC connection is established with the first communication device; and an RRC signaling message including the configuration information is sent to the first communication device.

[0028] In one alternative implementation, the maximum downlink scheduling interval is less than or equal to the default QoS PDB.

[0029] Thirdly, a communication device is provided. This communication device can be a first communication device, or a module or unit (e.g., a chip, chip system, or circuit) within the first communication device that performs each of the methods / operations / steps / actions described in the first aspect, or a device compatible with the first communication device. This communication device has the functionality to implement some or all of the embodiments described in the first aspect. Alternatively, the communication device can be a second communication device, or a module or unit (e.g., a chip, chip system, or circuit) within the second communication device that performs each of the methods / operations / steps / actions described in the second aspect, or a device compatible with the second communication device. This communication device has the functionality to implement some or all of the embodiments described in the second aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above-described functionality.

[0030] In one possible design, the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing the corresponding functions described in the above-described method. The communication unit supports communication between the communication device and other communication devices. The communication device may also include a storage unit coupled to the processing unit and the communication unit, which stores necessary program instructions and data for the communication device. Additionally, the processing unit may be used to control the communication unit to transmit and receive data / signaling.

[0031] In one embodiment, a communication unit is configured to receive configuration information, which includes multiple data scheduling index values, which are used to associate corresponding downlink scheduling intervals.

[0032] The processing unit is used to generate data scheduling information, which indicates the downlink scheduling interval of data and is determined based on configuration information.

[0033] The communication unit is also used to send data scheduling information.

[0034] The communication unit is also used to receive data.

[0035] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0036] In one embodiment, a processing unit is configured to generate configuration information, which includes multiple data scheduling index values, the data scheduling index values ​​being used to associate with corresponding downlink scheduling intervals.

[0037] The communication unit is used to send configuration information.

[0038] The communication unit is also used to receive data scheduling information.

[0039] The communication unit is also used to send data.

[0040] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0041] As an example, the communication unit can be a transceiver or a communication interface, the storage unit can be a memory, and the processing unit can be a processor. The processor is coupled to the memory, which stores programs or instructions for the processor. The processor can be used to cause the communication device to perform the method described in the first aspect above when the program or instructions are executed by the processor. The transceiver or communication interface can be used to send and receive signals and / or data.

[0042] In one embodiment, a transceiver is used to receive configuration information, which includes multiple data scheduling index values, and the data scheduling index values ​​are used to associate corresponding downlink scheduling intervals.

[0043] The processor generates data scheduling information that indicates the downlink scheduling interval for application layer business data, and this data scheduling information is determined based on configuration information.

[0044] The transceiver is also used to send data scheduling information.

[0045] A transceiver is also used to receive data.

[0046] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0047] In one embodiment, a processor is used to generate configuration information, which includes multiple data scheduling index values, which are used to associate corresponding downlink scheduling intervals.

[0048] A transceiver is used to send configuration information.

[0049] The transceiver is also used to receive data scheduling information.

[0050] Transceivers are also used to send data.

[0051] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0052] In another embodiment, the communication device is a chip or chip system. The processing unit may also be a processing circuit or logic circuit; the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system.

[0053] In implementation, the processor can be used for, but is not limited to, baseband-related processing, and the transceiver or communication interface can be used for, but is not limited to, radio frequency transceiver. These devices can be disposed on separate chips, or at least partially or entirely on the same chip. For example, the processor can be further divided into analog baseband processors and digital baseband processors. The analog baseband processor can be integrated with the transceiver (or communication interface) on the same chip, while the digital baseband processor can be disposed on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (e.g., but not limited to graphics processors, multimedia processors, etc.) on the same chip. Such a chip can be called a System on a Chip (SoC). Whether the devices are disposed independently on different chips or integrated on one or more chips often depends on the needs of the product design. This application does not limit the implementation form of the above-mentioned devices.

[0054] Fourthly, a processor is provided for executing the various methods described above. In executing these methods, the processes of sending and receiving the signals described above can be understood as the process of the processor outputting the signals and the process of the processor inputting the signals. When outputting the signals, the processor outputs the signals to a transceiver for transmission by the transceiver (or communication interface). After being output by the processor, the signals may require further processing before reaching the transceiver (or communication interface). Similarly, when the processor receives the input signals, the transceiver (or communication interface) receives the signals and inputs them to the processor. Furthermore, after the transceiver (or communication interface) receives the signals, the signals may require further processing before being input to the processor.

[0055] Unless otherwise specified, or unless it contradicts its actual function or internal logic in the relevant description, the transmission and reception operations involved by the processor can be more generally understood as processor output and reception, input and other operations, rather than transmission and reception operations directly performed by radio frequency circuits and antennas.

[0056] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0057] Fifthly, a wireless communication system is provided, comprising a first communication device and / or a second communication device as described above. The first communication device is configured to perform the method described in the first aspect or any possible implementation thereof, and the second communication device is configured to perform the method described in the second aspect or any possible implementation thereof. In another possible design, the system may further include other devices that interact with the first communication device and / or the second communication device as provided in this application.

[0058] Sixthly, this application provides a computer-readable storage medium storing a computer program that, when run, causes the method described in the first aspect, or the second aspect, or any possible implementation thereof, to be executed.

[0059] In a seventh aspect, this application also provides a computer program product including instructions, the computer program product comprising: computer program code, which, when executed, causes the method described in the first aspect, or the second aspect, or any possible implementation thereof, to be performed.

[0060] Eighthly, this application provides a chip system including a processor and an interface. The interface is used to acquire programs or instructions, and the processor is used to invoke the programs or instructions to implement the functions involved in the first or second aspect. In one possible design, the chip system further includes a memory for storing necessary program instructions and data for the terminal. This chip system may be composed of chips or may include chips and other discrete devices. Attached Figure Description

[0061] Figure 1 is a schematic diagram of a communication system provided in an embodiment of this application;

[0062] Figure 2 is a schematic diagram showing the relationship between the NR protocol stack and network element modules on the access network device side according to an embodiment of this application;

[0063] Figure 3 is a schematic diagram of the architecture of a 5G network provided in an embodiment of this application;

[0064] Figure 4 is a schematic diagram of an ORAN network architecture provided in an embodiment of this application;

[0065] Figure 5 is a schematic diagram of a cell DTX provided in an embodiment of this application;

[0066] Figure 6 is a schematic diagram of QoS flow configuration and rule generation provided in an embodiment of this application;

[0067] Figure 7 is a schematic diagram of a multi-level QoS support mechanism provided in an embodiment of this application;

[0068] Figure 8 is a schematic diagram of another communication system provided in an embodiment of this application;

[0069] Figure 9 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0070] Figure 10 is a schematic diagram of a downlink reflection QoS mechanism provided in an embodiment of this application;

[0071] Figure 11 is a schematic diagram of a downlink reflection QoS process provided in an embodiment of this application;

[0072] Figure 12 is a schematic diagram of a downlink SDAP protocol data cell with an SDAP header provided in an embodiment of this application;

[0073] Figure 13 is a schematic diagram of on-demand selection of multiple DRBs provided in an embodiment of this application;

[0074] Figure 14 is a schematic diagram of on-demand selection of multiple scheduling strategies provided in an embodiment of this application;

[0075] Figure 15 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0076] Figure 16 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0077] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0078] In the description of this application, terms such as "first" and "second" are used only to distinguish different objects, not to describe a specific order. Furthermore, 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. Additionally, "at least one" refers to one or more, and "multiple" refers to two or more. "One or more 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.

[0079] The terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0080] In this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0081] It is understood that in this application, "when," "if," and "if" all refer to the device performing a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action when it is implemented, nor do they imply any other limitations. The device performing a corresponding action under certain objective circumstances includes: satisfying the objective circumstances, i.e., being able to perform the corresponding action; or satisfying both the objective circumstances and other circumstances, in order to perform the corresponding action.

[0082] In this application, "simultaneous" can be understood as "parallel", or at the same point in time, or within a period of time, or within the same cycle. The specific meaning can be understood in conjunction with the context.

[0083] In this application, the use of singular designations for elements is intended to represent "one or more" rather than "one and only one," unless otherwise specified.

[0084] It is understood that in the embodiments of this application, "B corresponding to A", "A and B correspond" or similar expressions indicate that B is associated with A, and B can be determined based on A. Determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0085] The technical solutions of this application embodiment can be applied to various wireless communication systems that can simultaneously support both communication and sensing functions. Examples include: wireless local area network (WLAN) systems using the 802.11 series protocols; long term evolution (LTE) systems; 5th generation (5G) systems, such as new radio access technology (NR); networks integrating multiple systems; IoT systems; vehicle-to-everything (V2X) systems; open-radio access network (O-RAN) systems; and future communication systems, such as 6th generation (6G) systems. The 802.11 series protocols include, but are not limited to: 802.11ax, 802.11be, Wi-Fi 7 or next-generation protocols such as Wi-Fi 8, ultra-high reliability (UHR), 802.11bn, Wi-Fi AI, or millimeter wave, etc., which are not listed here. Here, supporting sensing functionality can be understood as supporting, but is not limited to, one or more of the following sensing protocols: the 802.11bf protocol, or the next-generation sensing protocol of the 802.11bf protocol, or a future generation of WLAN sensing protocol, etc.

[0086] In one possible implementation, the communication system includes communication devices that can wirelessly communicate with each other using air interface resources. These communication devices may include network devices and terminal devices; the network devices may also be called base station devices, access network devices, or access point (AP) devices. Air interface resources may include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources. In this application, "at least one" may also be described as one or more, and "multiple" may be two, three, four, or more; this application does not impose any limitations.

[0087] It should be understood that the system architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, as the system architecture or application scenarios evolve, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0088] Referring to Figure 1, which is a simplified schematic diagram of the communication system provided in an embodiment of this application, the communication system includes a radio access network (RAN) 100, a core network (CN) 200, and an Internet 300. RAN 100 can be a next-generation (e.g., 6G or higher) radio access network or a traditional (e.g., 5G, 4G, 3G, or 2G) radio access network. One or more terminal devices (120a-120j, collectively referred to as 120) can be interconnected or connected to one or more network devices in RAN 100 (e.g., 110a and 110b in Figure 1, collectively referred to as 110). RAN 100 may also include other devices, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). RAN node 110 is connected to the core network 200 wirelessly or via wired means. The core network devices in the core network 200 and the RAN node 110 in the RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0089] In practical applications, this communication system can include multiple network devices (also known as access network devices or AP devices) and multiple terminal devices simultaneously. One network device can serve one or more terminal devices simultaneously. A terminal device can also access one or more network devices simultaneously. This application embodiment does not limit the number of terminal devices and network devices included in the communication system.

[0090] RAN100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, non-terrestrial network (NTN) systems, or future-oriented evolution systems (e.g., 6G mobile communication systems). RAN100 can also be an open-RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or a communication system integrating two or more of the above systems. The RAN100 involved in this application is preferably an NTN system, and RAN100 can be in transparent transmission mode or regenerative mode.

[0091] Terminal device 120 can also be referred to as terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the device form of the terminal.

[0092] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal devices 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal device 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0093] Communication between access network devices and terminal devices follows a specific protocol layer structure. This protocol layer may include a control plane protocol layer and a user plane protocol layer. The control plane protocol layer may include at least one of the following: radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, or physical (PHY) layer, etc. The user plane protocol layer may include at least one of the following: service data adaptation protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or physical layer, etc.

[0094] In one possible scenario, RAN node 110 can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a 6th-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. RAN node 110 can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, RAN node 110 can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).

[0095] In another possible scenario, multiple RAN nodes 110 collaborate to assist the terminal in achieving wireless access, with each RAN node 110 implementing a portion of the base station's functions. For example, a RAN node 110 can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). The CU and DU nodes separate the gNB's protocol layers; some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. As one implementation, the CU deploys the Radio Resource Control (RRC) layer, PDCP layer, and SDAP layer from the protocol stack; the DU deploys the RLC layer, MAC layer, and physical layer (PHY) from the protocol stack. Thus, the CU has the processing capabilities for RRC, PDCP, and SDAP. The DU has RLC, MAC, and PHY processing capabilities. It is understood that the above functional division is merely an example and does not constitute a limitation on the CU and DU. The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). See Figure 2, which is a schematic diagram of the relationship between the NR protocol stack and network element modules on the access network equipment side provided in an embodiment of this application. As shown in Figure 2, when the CU is not split, the CU is connected to the DU through the F1 interface, and the CU deploys the RRC layer, SDAP layer, and PDCP layer of the protocol stack, while the DU deploys the RLC layer, MAC layer, and PHY layer of the protocol stack. When the CU is split into CU-CP and CU-UP, the two are connected to each other through the E1 interface and connected to the DU through the F1-C and F1-U interfaces, respectively. The CU-CP deploys the RRC layer and PDCP control plane (PDCP-C) layer of the protocol stack, the CU-UP deploys the SDAP layer and PDCP user plane (PDCP-U) layer of the protocol stack, and the DU deploys the RLC layer, MAC layer, and PHY layer of the protocol stack.

[0096] Core network equipment refers to equipment in the core network that provides service support to terminals, such as access and mobility management function (AMF) entities, session management function (SMF) entities, and user plane function (UPF) entities. See Figure 3, which is a schematic diagram of the 5G network architecture provided in an embodiment of this application. As shown in Figure 3, the core network equipment includes network data analytics function (NWDAF) entities, network exposure function (NEF), network repository function (NRF), authentication server function (AUSF) entities, AMF entities, SMF entities, policy control function (PCF) entities, unified data management (UDM) entities, and application function (AF) entities. The various network elements are connected through service-based interfaces, represented in the form of Nxxx, such as Nnef and Nsmf in the figure. In addition, the architecture also includes UE, (R)AN, user plane function (UPF) entities, and data network (DN). They are connected and interact with each other and with the core network elements through NG interfaces (such as N1 and N2 in the figure).The main functions of the AMF include managing user registration, reachability detection, SMF node selection, and mobility state transition management; the main functions of the SMF include controlling session establishment, modification, and deletion, and user plane node selection; the main functions of the UPF include packet routing and forwarding, mobility anchors, uplink classifiers to support routing service flows to the data network, and branch points to support multi-homed PDU sessions; the main function of the PCF is the policy decision point, providing rules based on service data flow and application detection, gating, QoS, and flow-based charging control; the main function of the UDM is to store user subscription data; AU The primary function of the SF (Secure Element) is to provide authentication services; the primary function of the NEF (Network Element) is to securely open services and capabilities provided by 3GPP network functions, such as third parties, edge computing, and AF (Automatic Element). The primary function of the NWDAF (Network Window AF) is to provide network data collection and analysis functions based on technologies such as big data and artificial intelligence; the primary function of the NRF (Network RF) is to maintain the characteristics of available network element instances and their supported service capabilities; the primary function of the AF (Automatic Element) is to interact with the 3GPP core network to provide services, influencing service flow routing, access network capability opening, policy control, etc.; and the primary function of the (R)AN (Radio Access Network) is to provide radio connectivity, located between the UE and the core network node. It should be noted that entities in this application can also be referred to as network elements or functional entities. For example, an AMF (Active Network Function) entity can also be referred to as an AMF network element or an AMF functional entity; these can be used equivalently, and no further distinction will be made thereafter.

[0097] RAN100 can be an ORAN (Access Network RAN) designed to achieve intelligence and openness. The main features of the ORAN architecture are hardware and software separation, which realizes the virtualization of network functions and the standardization of hardware. In addition, ORAN also introduces artificial intelligence (AI). See Figure 4, which is a schematic diagram of the ORAN network architecture provided in the embodiment of this application. As shown in Figure 4, the architecture includes a service management and orchestration framework (SMO) network element, which is mainly responsible for RAN management. It connects to O-RAN internal network elements (such as O-eNB, O-DU, etc.) through the O1 interface and performs intelligent configuration and management; it connects to the Open Cloud Infrastructure Platform (O-Cloud) through the O2 interface and manages the various O-RAN network service nodes running on the O-Cloud, performing intelligent configuration and management; it connects to and manages the ORAN radio unit (O-RU) through the Open fronthaul M-Plane (Open FH M-Plane). The O1 interface can also control the O-RU, that is, the O-RU has two sets of management interfaces. When both sets of interfaces are enabled, it is called hybrid mode. The SMO includes a non-real-time RAN intelligent controller (Non-Real Time RIC), which provides policies, ML model management, and a large amount of information to the near-real-time RAN intelligent controller (Near-Real Time RIC) via the A1 interface, thereby achieving intelligent RAN optimization. The Near-Real Time RIC connects to the O-Enb, Open DU (O-DU), Open CU-Control Plane (O-CU-UP), and Open CU-User Plane (O-CU-UP) via the E2 interface. The O-CU-CP connects to the O-CU-UP via the E1 interface and to the O-DU via the F1-c interface, providing the control plane X2 interface (X2-c), control plane Xn interface (Xn-c), and control plane NG interface (NG-c). The O-CU-UP connects to the O-DU via the F1-U interface, providing the user plane X2 interface (X2-u), user plane Xn interface (Xn-u), and user plane NG interface (NG-u).The O-DU connects to the O-RU via the Open fronthaul control user synchronization-Plane (Open FH CUS-Plane) and the Open FH M-Plane. The NG interface is the interface between NR RAN equipment (e.g., base stations, CUs, CU-CPs, or CU-UPs) and the NR core network, while the Xn interface is the interface between LTE RAN equipment. In NR, the X2 interface is primarily used in E-UTRA-NR dual connectivity (EN-DC) scenarios, where the master station is an LTE RAN device connected to the LTE core network via the X2 interface.

[0098] O-Cloud mainly includes physical infrastructure nodes (providing physical resources to meet the functional requirements of O-RAN), software components (such as operating systems, virtual machines, real-time containers, etc.), and management and orchestration functions (such as O-RAN infrastructure node management, hardware acceleration card management, O-Cloud notification management, etc.).

[0099] O-CU, also known as O-RAN aggregation unit or O-RAN control unit, is primarily used to implement the RRC layer, PDCP layer, SDAP layer, and other control functions in the 3GPP standard. O-CU-CP, similar to CU-CP in NR systems, implements the functions of the RRC layer and the control plane functions of the PDCP layer. O-CU-UP, similar to CU-UP in NR systems, implements the functions of the SDAP layer and the user plane functions of the PDCP layer. O-DU, based on low-layer function partitioning, is mainly used to implement the higher layers (closer to the MAC layer) of the RLC layer, MAC layer, and PHY in the 3GPP standard. The higher-layer functions of the PHY layer include one or more of the following: forward error correction (FEC), encoding / decoding, scrambling / descrambling, modulation / demodulation. O-RU, also based on low-layer function partitioning, implements the lower-layer (closer to RF) functions of the PHY in the 3GPP standard, as well as RF functions. The lower-layer functions of the PHY layer include one or more of the following: fast fourier transform (FFT) / inverse fast fourier transform (Inverse Fast Fourier Transform). The process includes Fourier transform (iFFT), digital beamforming, extraction and filtering of the physical random access channel (PRACH), which is similar to the transmission reception point (TRP) or remote radio head (RRH) in 3GPP, but includes the low-level functions of the PHY. Non-Real Time RIC, also known as non-RT RIC or NRT RIC, is mainly used to implement non-real-time intelligent management of RAN functions. It can realize AI / ML workflows including model training and model updates, and guide applications / functions in the nRT RIC based on policies. Near-Real Time RIC, also known as near-RT RIC or nRT RIC, is used to realize near real-time intelligent management of RAN. Through data collection and related operations on the E2 interface, it realizes near real-time control and optimization of O-RAN modules and resources.

[0100] Terminal equipment 120 can be a UE, access terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, terminal, wireless communication equipment, multimedia equipment, streaming media equipment, UE agent, or UE device, etc. Access terminals can be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle equipment, wearable devices, terminals in future 5G networks, or terminals in future evolved public land mobile networks (PLMNs), etc.

[0101] In this application embodiment, the device for implementing the terminal's functions can be a terminal itself; it can also be a device capable of supporting the terminal in implementing these functions, such as a chip system, a communication module, or a modem, etc., which can be installed in the terminal. In this application embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. The embodiments of this application do not limit the specific technology or specific device form used in the terminal device.

[0102] Network equipment refers to devices in RAN100 that can communicate with terminal equipment 120. These devices can be base stations, relay stations, or access points. Base stations can be base transceiver stations (BTS) in Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA) networks, node base stations (NBs) in Wideband Code Division Multiple Access (WCDMA) networks, evolved NBs (eNBs or eNodeBs) in Long Term Evolution (LTE) networks, radio controllers in cloud radio access network (CRAN) scenarios, base station equipment in future 5G networks, access network equipment in future evolved PLMN networks, wearable devices, or vehicle-mounted devices.

[0103] In the embodiments of this application, the device used to implement the functions of the network device can be the network device itself; it can also be a device capable of supporting the network device in implementing the functions, such as a chip system, a communication module, or a modem, etc., and the device can be installed in the network device. The network device can support networks with the same or different access technologies, and the embodiments of this application do not limit the specific technology or specific device form adopted by the network device.

[0104] It is understood that when the network device is an access point (as shown in Figure 1, 110b) and the terminal device is a non-access point site (as shown in Figure 1, 120f or 120g), the network formed by the network device and the terminal device can be a wireless local area network (WLAN). In other words, the communication system shown in Figure 1 can include, but is not limited to, WLAN.

[0105] Secondly, some terms and related technologies involved in the embodiments of this application will be explained to facilitate understanding by those skilled in the art.

[0106] Discontinuous transmission (DTX) in cells refers to shutting down transmission during voice intermittent periods and transmitting only silence indication frames. Its main function is to extend equipment standby time, improve network utilization, and reduce interference. It can be divided into uplink DTX and downlink DTX. Uplink DTX can save terminal equipment battery power and reduce intra-system interference, while downlink DTX can reduce network equipment power consumption and reduce inter-base station crosstalk. When used together, they can improve the co-channel interference ratio of the system. DTX allows the network to perform downlink transmission with the terminal only during specified time periods, and not during other time periods, thus enabling the use of corresponding shutdown techniques to achieve network energy saving. See Figure 5, which is a schematic diagram of cell DTX provided in an embodiment of this application. As shown in Figure 5, the cell adopts a periodic cell DTX configuration. During the cell DTX on period, the network transmits downlink data (including downlink service transmission with the terminal); during the cell DTX off period, the network at least stops downlink service transmission with the terminal, and may also stop certain periodic signals, such as at least one of the following: synchronization signal block (SSB), channel state information-reference signal (CSI-RS), and semi-persistent scheduling (SPS). The longer the cell DTX off period, the longer and deeper the shutdown can be on the network side, thus achieving better energy-saving effects. However, correspondingly, the transmission latency of service data and the impact on the terminal will also increase.

[0107] Cell discontinuous reception (DRX) is a concept relative to DTX, meaning that the network only performs uplink transmissions with the terminal during specified time periods, and does not perform uplink transmissions during other time periods. DRX and DTX configurations are independent; they can be configured simultaneously or only one can be configured.

[0108] QoS (Quality of Service) refers to a network's ability to provide better service for specified network communications using various underlying technologies. It is a network security mechanism used to address network latency and congestion issues. QoS guarantees are crucial for networks with limited capacity, especially for streaming multimedia applications such as VoIP and IPTV, as these applications often require fixed transmission rates and are sensitive to latency. Devices supporting QoS can provide quality of service, assigning transmission priorities to specific types of data streams to indicate their relative importance. They utilize various priority forwarding policies and congestion avoidance mechanisms provided by the device to offer specialized transmission services to these data streams. A QoS-configured network environment increases the predictability of network performance, effectively allocates network bandwidth, and utilizes network resources more rationally.

[0109] AT commands are used for connection and communication between terminal devices and PC applications. Each AT command line can contain only one AT command. For AT command transmission, in addition to the two characters "AT", a maximum length of 1056 characters (including the final null character) can be received. AT command sets are sent from terminal devices or data terminal equipment to terminal adapters (TA) or data circuit terminal equipment (DCE). For URC instructions or responses proactively reported by the terminal device to the PC, only one instruction or response is allowed per line; multiple instructions or responses are not permitted on a single line. AT commands end with a carriage return, and responses or reports end with a carriage return and line feed.

[0110] The radio bearer (RB) is the collective term for the different layer protocol entities and configurations allocated by the base station to the UE, including PDCP protocol entities, RLC protocol entities, MAC protocol entities, and a series of resources allocated by the PHY. The RB is the channel connecting the eNB and the UE via the Uu interface. All data transmitted on the Uu interface must pass through the RB. The RB includes the signalalling radio bearer (SRB) and the data radio bearer (DRB). The SRB is the channel for the actual transmission of system signaling messages, while the DRB is the channel for the actual transmission of user data. It carries not RRC messages at the RRC layer, but rather IP data packets between the terminal and the core network data gateway. In 5G, end-to-end QoS Flow replaces end-to-end Evolved Packet System (EPS) bearers. QoS Flow can be dynamically created without end-to-end signaling. It is divided into DRB bearers on the radio interface side and QoS Flow on the core network side. QoS Flow and DRB bearers can be dynamically mapped through the SDAP protocol, which improves the efficiency of QoS Flow creation.

[0111] Packet data in a QoS flow are classified and labeled using a QoS flow identifier (QFI), which can include the following types: GBR QoS flow requiring guaranteed traffic bit rate, Non-GBR QoS flow not requiring guaranteed traffic bit rate, and latency-critical QoS flow. The 5G network can provide the UE with one or more QoS flow descriptions associated with the PDU session during PDU session establishment or modification. Each QoS flow includes: 5G QoS identifier (5QI), Allocation and Reservation Priority (ARP), Guaranteed Traffic Bit Rate for Uplink and Downlink (GFBR), Maximum Traffic Bit Rate for Uplink and Downlink (MFBR), Maximum Packet Loss Rate for Uplink and Downlink, Latency-Critical Resource Type, Notification Control, and Reflection QoS Attribute (RQA). QoS flow characteristics include: resource type, priority, packet latency budget, packet error rate, average window, and maximum data burst size.

[0112] Currently, to achieve network energy saving, data scattered in the time domain is aggregated to increase the time without data transmission, thereby increasing the probability of network shutdown and achieving energy saving. Specifically, the UE obtains the RRC configuration information sent by the cell, obtaining the Cell DTX period length and on-duration duration. In the RRC configuration information, the cell DTX of the cell may be configured as inactive. When the cell decides to activate DTX, it sends DCI2-9 signaling. The UE obtains this indication signaling through blind detection and learns that the cell DTX of the cell is activated. Therefore, based on the Cell DTX period length and on-duration duration, it monitors the downlink control information from the network device to transmit downlink data. Furthermore, the cell DTX on period can be called the activation period, and the base station or cell being in this period can be called the active state. The cell DTX off period can be called the deactivation period, and the base station or cell being in this period can be called the deactivation state. In the deactivation state, the transmission and reception state of the first signal can be any one of the following: not transmitting or not receiving; correspondingly, in the active state, the transmission and reception state of the first signal can be any one of the following: transmitting or receiving. The first signal may include at least one set of signals from a first group of signals, a second group of signals, a third group of signals, and a fourth group of signals. The first group of signals includes any one or more of the following signals: a PDCCH scrambled with a cell radio network temporary identifier (C-RNIT), a PDCCH scrambled with a configured scheduling radio network temporary identifier (CS-RNTI), a PDCCH scrambled with slot format indicators (SFI)-RNTI, a PDCCH scrambled with INT (Interruption)-RNTI, a PDCCH scrambled with cancellation indication (CI)-RNTI, a PDCCH scrambled with uplink power control information of the physical uplink control channel (TPC-PUCCH)-RNTI, a PDCCH scrambled with uplink power control information of the physical uplink shared channel (TPC-PUSCH)-RNTI, a PDCCH scrambled with uplink power control information of the dynamically scheduled physical downlink shared channel and channel sounding reference signal (TPC-SRS)-RNTI, and an availability indicator. indication, AI)-RNTI scrambled PDCCH;The second group of signals includes any one or more of the following: Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) for dynamically scheduled Physical Downlink Shared Channel (PDSCH), Aperiodic Sounding Reference Signal (A-SRS), Periodic Sounding Reference Signal (P-SRS), Semi-static Sounding Reference Signal (SP-SRS), Aperiodic Channel State Information (A-SRS), Periodic Channel State Information (P-SRS), Semi-static Channel State Information (SP-SRS), and Dynamic Grant (DG) PUSCH; the third group of signals includes any one or more of the following: SSB, BFR, Semi-static Scheduled Physical Downlink Data Channel (SPS PDSCH), and PDCCH scrambled with System Information (SI) / Random Access (RA) / Temporary Cell (TC) / Paging / Power Saving (PS)-RNTI; the fourth group of signals includes any one or more of the following: Granted Physical Uplink Shared Channel (CG). PUSCH), Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) for the semi-statically scheduled Physical Downlink Shared Channel (SPS PDSCH), Scheduling Request (SR), and Physical Random Access Channel (PRACH).

[0113] It should be understood that among the four groups of signals mentioned above, the first and third groups are downlink signals, while the second and fourth groups are uplink signals. Both the first and second groups are affected by DRX configuration. For ease of signal differentiation, in this application, the first group is also referred to as a first-type downlink signal, the second group as a first-type uplink signal, the third group as a second-type downlink signal, and the fourth group as a second-type uplink signal. The first-type signal is affected by connected DRX (C-DRX) configuration; that is, it can be assumed that the access network equipment and terminal equipment will only transmit the first-type signal during the active period indicated by the C-DRX configuration, and will not transmit the first-type signal during the deactivation period. The second-type signal is considered unaffected by C-DRX configuration but is affected by cell DTX / DRX configuration. Therefore, cell DTX / DRX can achieve greater energy-saving gains than C-DRX by shutting down more signals. In summary, under the inactive state of cell DTX, the following downlink signals are not transmitted: SPS PDSCH, UE-specific PDCCH, periodic / semi-static CSI-RS, and group PDCCH (e.g., DCI2-0 / 1 / 2 / 3 / 4 / 5); under the inactive state of cell DRX, the following uplink signals are not received: CG PUSCH, SR, periodic / semi-static CSI reporting, and periodic / semi-static SRS; of course, it is not excluded that other downlink signals may not be transmitted or uplink signals may not be received.

[0114] Another way to save network energy is for OTT application providers to provide data transmission requirements to the network. After a series of interactions within the network, the SMF generates a matching dedicated QoS flow configuration and rules, which are then distributed to the RAN and UE, instructing them on how to process data packets. The RAN can then perform energy-saving scheduling while ensuring service experience. For example, the network can perform delay scheduling within the QoS-defined PDB limit to achieve time-domain converged data transmission, thereby achieving network energy saving. See Figure 6, which is a schematic diagram of the generation of QoS flow configuration and rules provided in an embodiment of this application. As shown in Figure 6, when a user goes online, they obtain subscription data from the UDM. This subscription data carries the session aggregate maximum bit rate (Session-AMBR), address resolution protocol (ARP), 5QI, etc. The request message is sent to the PCF after passing through the SMF. The PCF makes a decision based on the slice information, location information, etc., carried by the user upon going online, and generates a QoS policy. The generation of the QoS policy is entirely decided by the PCF, without any negotiation process with the UDM or SMF. The PCF sends the generated QoS policy to the SMF through a response message, and the SMF installs the policy locally. If the Policy and Charging Control (PCC) function is not enabled in the network or if the N7 session is unreachable due to PCF malfunction, the SMF configures the QoS policy locally. However, the policy configured locally by the SMF is inconsistent with the policy generated by the PCF. The PCF generates a more granular policy control, which can flexibly customize the QoS policy according to user location, level, time period, quota status, holidays, etc. It should be noted that the PCF has the highest decision-making authority over QoS parameters. If the PCF does not issue the corresponding QoS parameters, the SMF will decide whether to authorize the user to use the requested QoS based on its local configuration. The SMF stores the QoS parameters of the final decision.Furthermore, after determining the final QoS parameters to be used, the SMF will determine the QoS Flow information (such as QFI, packet filter set (PFS), QoS parameters, etc.) based on the QoS parameters and service information, and then control the establishment, modification, and deletion of the QoS Flow. That is, the SMF will distribute the generated QoS policies to the UPF, RAN, and UE respectively (the QoS information distributed to the RAN and UE needs to be transparently transmitted through the AMF), instructing them on how to process data packets. Specifically, the SMF sends the QFI, QoS parameters, and PFS to the UPF, so that the UPF can map data packets to the corresponding QoS flow. The SMF sends the QFI and QoS parameters to the RAN, guiding the RAN to map the QoS flow to radio bearers and resources. The SMF sends the QFI and PFS to the UE, guiding the UE to map data packets to the corresponding QoS flow. It can be seen that in the specific execution of the QoS policy, the UDM is mainly responsible for user data subscription, that is, allocating the default QoS Flow ARP and 5QI when the user comes online, and providing Session-AMBR and UE-AMBR; the AMF mainly provides channels for signaling establishment so as to carry out information transparent transmission; the UPF marks and controls the downlink QFI and verifies the uplink QFI; the RAN processes the QoS policy transmitted from the signaling plane, maps the QoS parameters of the signaling plane to usernames, and realizes the control of the quality of service of user services.

[0115] To further understand the impact of PCF and AF / AS on SMF's generation of dedicated QoS policies, the following explanation is based on V2X. Refer to Figure 7, which is a schematic diagram of the multi-level QoS support mechanism provided in this embodiment. As shown in Figure 7, to enable different levels of autonomous driving in V2X, the V2X AS provides QoS level-related information to the PCF; then, the PCF maps the QoS level to multiple QoS parameter sets, generates PCC rules, and identifies the preferred QoS parameter set; next, the PCF sends the generated information to the SMF, which establishes multiple QoS profiles and binds them to a new QoS Flow, identifying the preferred QoS profile; the SMF sends the generated information to the NG-RAN; the NG-RAN completes the QoS notification control process and PDU session modification process with the PCF based on the information sent by the SMF. It's worth noting that the multi-level QoS support mechanism shown in Figure 7 differs from a single QoS flow having a single QoS profile in that the NG-RAN supports configuring multiple levels of QoS profiles for a specific application. When it detects that the current QoS cannot satisfy the QoS flow, it will use other QoS profiles bound to this QoS flow and notify the core network using the QoS notification control mechanism. The notification message from NG-RAN to the 5GC (5G core network element) can include the currently supported QoS profile information. The PCF can initiate the corresponding PDU session modification process based on the information provided by NG-RAN to adjust the QoS policy of the service flow. It should also be noted that the QoS flow here is different from the default QoS flow, which has customized QoS configuration and is therefore generally called a dedicated QoS flow. The default QoS flow, on the other hand, is the QoS flow with the default QoS rules established for the PDU session in the 5G system. It has the lowest priority and is used to carry application data when no dedicated QoS flow is matched.

[0116] It can be seen that in scenarios with multi-level QoS support, in order to generate dedicated QoS policies so that the RAN can flexibly achieve energy-saving scheduling, it is necessary to rely on OTT applications to provide data transmission requirements through AS / AF, and through a series of interactions between core network elements, so that the RAN can know the QoS flow configuration of all arriving data. This is inefficient and cannot quickly enable the RAN to perform energy-saving scheduling. At the same time, the UE side corresponding to the RAN also needs to maintain multiple dedicated QoS flows, which also increases the UE's energy consumption. In addition, the diversity of OTT applications may lead to an excessive number of dedicated QoS flows that the UE needs to establish and maintain, exceeding its capacity limit.

[0117] Based on the above, this application provides a communication method, apparatus, and readable storage medium to address the problems that the configuration and rule formulation of existing dedicated QoS flows rely on the cooperation of OTT applications, resulting in low configuration efficiency and insufficient flexibility in RAN energy-saving scheduling. This eliminates the dependence on OTT applications and enables RAN energy-saving scheduling quickly, thereby improving the flexibility of RAN energy-saving scheduling.

[0118] In a specific embodiment, as shown in Figure 8, the communication system 200 includes a UE 210, a RAN 220, and a 5GC 230. The UE 210 includes a message transmission middleware (MT) 2110, which deploys an RRC protocol stack 21110 and a UP protocol stack 21120. The RAN 220 deploys corresponding RRC protocol stacks 2210 and UP protocol stacks 2220. The UE 210 and RAN 220 first establish an RRC connection based on the RRC protocol stacks. Then, the UE 210 establishes an initial context and PDU session with the 5GC 230 through the RAN 220. Next, the RAN 220 completes relevant configurations for different downlink scheduling intervals. The configuration information may include multiple data scheduling index values, with different scheduling index values ​​associated with different downlink scheduling intervals. Optionally, the data scheduling index values ​​include DRB index values ​​or scheduling policy index values. The RAN 220 sends the generated configuration information to the UE 210. After receiving the configuration information, UE210 learns the service requirements of the application (e.g., acceptable scheduling latency) based on AT commands. Then, UE210 determines the downlink scheduling interval of the application's service data and reports the selection result to RAN220. RAN220 forwards the application service data in 5GC230 to UE210 based on the downlink scheduling interval selected by UE210, thereby realizing flexible energy-saving scheduling of RAN220.

[0119] The technical solution provided in this application will be described in detail below with reference to more accompanying drawings.

[0120] To facilitate a clear description of the technical solutions of this application, multiple embodiments are used for illustration, as detailed in the following descriptions of the various embodiments. Unless otherwise specified, the same or similar parts between different embodiments or implementations can be referenced interchangeably. In the various embodiments and implementation methods / methods within those embodiments, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between different implementation methods / methods within those embodiments are consistent and can be mutually referenced. The technical features in different embodiments and between different implementation methods / methods within those embodiments can be combined to form new embodiments, implementation methods, or methods of implementation based on their inherent logical relationships. The embodiments described below do not constitute a limitation on the scope of protection of this application. It is understood that the order of the embodiments below does not represent their importance.

[0121] It should be understood that in this application, the indication includes direct indication (also known as explicit indication) and implicit indication. Direct indication information A refers to information A being included; implicit indication information A refers to information A being indicated through the correspondence between information A and information B, and through direct indication information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.

[0122] It should be understood that in this application, information D is determined based on information C, which includes both situations where information D is determined solely based on information C and situations where information D is determined based on information C and other information. Furthermore, the use of information C to determine information D can also include indirect determination, such as when information D is determined based on information E, and information E is determined based on information C.

[0123] Furthermore, in the embodiments of this application, "network element A sends information A to network element B" can be understood as network element B being the destination of information A or an intermediate network element in the transmission path between the destination and network element B, which may include sending information directly or indirectly to network element B. "Network element B receives information A from network element A" can be understood as network element A being the source of information A or an intermediate network element in the transmission path between the source and network element A, which may include receiving information directly or indirectly from network element A. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way and will not be elaborated further here.

[0124] Please refer to Figure 9, which is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes, but is not limited to, the following steps:

[0125] S101: The first communication device establishes an RRC connection with the second communication device.

[0126] Specifically, the first communication device can be a UE, and the second communication device can be a base station in the RAN. For ease of description, this will not be further explained later. The first communication device first needs to access the network, and the process of accessing the network is the process of establishing an RRC connection.

[0127] For example, the first communication device first sends a random access preamble. After receiving the random access preamble, the second communication device sends a random access response message to the first communication device. Then, the first communication device sends an RRC connection request. After resolving the conflict, the second communication device returns an RRC connection establishment success message to the first communication device. It should be understood that after the RRC connection is established, wireless network signaling can be transmitted, such as allocating wireless resources.

[0128] S102: The first communication device establishes an initial context and PDU session with the core network element through the second communication device.

[0129] Specifically, the second communication device sends an initial UE message to the 5GC. The 5GC then sends an initial context setup request to the second communication device, requesting the establishment of a default bearer. Upon receiving the request, the second communication device sends an RRC connection reconfiguration message to the first communication device. The second device then sends a security mode command to the first communication device on the DCCH. After successfully applying the new encryption method, the first communication device sends the security mode command to the second communication device on the uplink DCCH. The first communication device replies with an RRC connection reconfiguration complete message. The second communication device then sends an initial context setup response message to the 5GC, indicating successful establishment of the default bearer. The 5GC then sends an E-RAB setup request message to the second communication device, requesting the establishment of an S1 bearer. This message may carry the E-RAB ID, E-RAB level QoS, and transport layer. The second communication device sends an RRC connection reconfiguration message to the first communication device, requesting the establishment of the radio bearer for this bearer, and the first communication device sends an RRC connection reconfiguration complete message to the second communication device. After the radio resources and S1 resources are allocated, the second communication device sends a successful E-RAB setup response message to 5GC.

[0130] It is understandable that all necessary initial UE context establishment can be completed through initial context establishment, including SAE bearer context, security context, handover restriction list, UE capability information, NAS PDU, etc.

[0131] Furthermore, the first communication device sends a request message to the 5GC to establish a PDU session. This message may include the first communication device's authentication information and other necessary parameters (such as PDU session ID, PTI, DN-specific identity, SSC mode, PDU session type, QoS parameters, etc.). After receiving the request message, the 5GC replies with an acknowledgment message, indicating that it has received the request and can proceed with further processing. After confirmation by both parties, the connection is successfully established, and the session can begin transmitting data. It should be noted that the PDU session process may differ in different protocols. In practical applications, this process may be enhanced with encryption and authentication functions to ensure the security and reliability of communication.

[0132] S103: The second communication device generates configuration information, which includes multiple data scheduling index values.

[0133] Specifically, in order to achieve energy-saving scheduling and improve scheduling flexibility, the second communication device sets different downlink scheduling intervals, that is, how often the second communication device sends downlink data. For example, three different time lengths can be set, namely 10 milliseconds (ms), 100ms and 300ms, and corresponding configuration information is generated based on different time lengths.

[0134] It is worth noting that the setting of different downlink scheduling intervals here is similar to DTX, that is, the second communication device only performs downlink transmission with the first communication device during a specified time period, and does not perform downlink transmission during other time periods, thereby achieving energy-saving scheduling. It should be understood that, similar to the DTX setting, the second communication device may not perform any data or signal transmission during other time periods (e.g., service data, CS-RNTI scrambled PDCCH, AI scrambled PDCCH, etc.), or it may still allow the transmission of some signals during these time periods (e.g., SPS PDSCH, CSI-RS, group PDCCH, etc.). In addition, for ease of description, the downlink scheduling interval is used here to indicate how often the second communication device performs downlink transmission. Of course, other terms or expressions can also be used to indicate this, such as downlink scheduling cycle, downlink scheduling period, downlink scheduling interval, base station sleep period, etc., and this application does not limit this.

[0135] Specifically, for each downlink scheduling interval, a data scheduling index value is set. Optionally, the data scheduling index value can be represented using binary. For example, 00 represents a 10ms downlink scheduling interval, 01 represents a 100ms downlink scheduling interval, and 10 represents a 300ms downlink scheduling interval.

[0136] In one optional implementation, the maximum value of the downlink scheduling interval is less than or equal to the QoS PDB, and optionally the QoS is the default QoS.

[0137] Specifically, when the second communication device is pre-configured, it does not blindly and arbitrarily configure the downlink scheduling interval. Instead, it needs to refer to the PDB of the default QoS to ensure that the maximum value of the configured downlink scheduling interval does not exceed the PDB of the default QoS. This ensures that the configured downlink scheduling interval can meet the latency requirements of the service and avoids extreme situations.

[0138] In one alternative implementation, the data scheduling index value includes a DRB index value or a scheduling policy index value.

[0139] Specifically, the second communication device can pre-configure multiple DRBs, with different DRBs used to carry service data for different downlink scheduling intervals. Each DRB corresponds to a unique index value. This approach reduces the RRC reconfiguration process and saves time spent adding DRBs, thus improving communication efficiency, compared to configuring only one DRB and adding them on demand. Alternatively, the second communication device can pre-configure multiple scheduling strategies, with different scheduling strategies corresponding to different downlink scheduling intervals, and each strategy corresponding to a unique index value.

[0140] S104: The second communication device sends the configuration information to the first communication device.

[0141] Specifically, after completing the pre-configuration, the second communication device needs to send the generated configuration information to the first communication device, that is, send the data scheduling index value to the first communication device.

[0142] Optionally, the second communication device sends the configuration information to the first communication device via RRC signaling; or, the second communication device sends the configuration information to the first communication device via system messages; or, the second communication device sends the configuration information to the first communication device via other messages.

[0143] S105: The first communication device determines the downlink scheduling interval of data based on AT commands and configuration information.

[0144] Specifically, the first communication device can determine the downlink scheduling interval of the data based on AT commands and configuration information. This data can be application layer service data. That is, the first communication device can determine the downlink scheduling interval of the application layer service data based on AT commands and configuration information. For ease of understanding and explanation, the following description will use application layer service data as an example and will not make any further distinction.

[0145] Optionally, the first communication device enables the operating system (OS) to inform the modem of the acceptable downlink scheduling interval for application layer service data via AT commands and provides it to the AS user plane (UP). The acceptable downlink scheduling interval for application layer service data can be obtained through standardized operations (i.e., the OS obtains this data when installing applications), or the OS can obtain it through lower-layer perception and further analysis.

[0146] Furthermore, based on the acceptable downlink scheduling interval for application layer service data and the configuration information obtained from the second communication device, the first communication device can determine the final downlink scheduling interval for the application layer service data. Subsequent application layer service data will be scheduled using this downlink scheduling interval. For example, assuming the maximum acceptable downlink scheduling interval for application layer service data is 110ms (exceeding this interval will affect user experience), and the configuration information includes three different downlink scheduling intervals: 10ms, 100ms, and 300ms, the first communication device will select 100ms as the scheduling interval for the service data. This satisfies the service data latency requirements, ensures user experience, and minimizes power consumption.

[0147] In one alternative implementation, the first communication device determines the DRB corresponding to the application layer service data it is used to carry based on AT commands and multiple DRB index values.

[0148] Specifically, when the second communication device performs multiple DRB configuration, each DRB corresponds to an index value, which is associated with a downlink scheduling interval. Therefore, the first communication device can determine the downlink scheduling interval of the service data according to the application layer service data transmission requirements, and then determine the corresponding DRB, which can then be used to carry the service data.

[0149] In one alternative implementation, the first communication device determines the DRB index value corresponding to the application layer service data to be carried by the first communication device based on AT commands and multiple DRB index values.

[0150] Specifically, when the second communication device performs multiple DRB configuration, each DRB corresponds to an index value, which is associated with a downlink scheduling interval. Therefore, the first communication device can determine the downlink scheduling interval of the service data according to the application layer service data transmission requirements, and then determine the corresponding DRB index value.

[0151] In one optional implementation, the first communication device determines the scheduling policy index value corresponding to the application layer service data of the first communication device based on AT commands and multiple scheduling policy index values.

[0152] Specifically, when the second communication device configures multiple scheduling strategies, each scheduling strategy corresponds to an index value, which is associated with a downlink scheduling interval. Therefore, the first communication device can determine the downlink scheduling interval of the service data according to the application layer service data transmission requirements, and thus determine the corresponding scheduling strategy.

[0153] S106: The first communication device sends data scheduling information to the second communication device, which indicates the downlink scheduling interval of application layer service data.

[0154] Specifically, after the first communication device determines the downlink scheduling interval for application layer service data, it needs to report the result so that the second communication device can subsequently send service data according to the downlink scheduling interval.

[0155] In one alternative implementation, the first communication device adds an RQI to the SDAP packet header and sends the SDAP packet to the second communication device via the determined DRB for carrying application layer service data.

[0156] Specifically, the first communication device adds an indication field to the SDAP packet header. This indication field can be a redefined field, a reused extended field in the SDAP packet header, or a reinterpretation of an existing field. Optionally, this indication field is a 1-bit field used to add indication information such as RQI. If it is necessary to switch the DRB to carry application layer service data, the first communication device will no longer use the previous DRB. Assuming the previous DRB is the first DRB, the SDAP packet with added RQI will no longer be sent to the second communication device through the first DRB. Instead, the newly determined DRB corresponding to carrying application layer service data will be used. The second DRB is used to send SDAP packets with added RQI to the second communication device, instructing the second communication device to use the DRB to send the data to the first communication device after the data in the subsequent QoS stream arrives. If it is not necessary to switch DRBs to carry application layer service data, the first communication device can still use the previous DRB to send SDAP packets with added RQI to the second communication device, or the first communication device can still use the previous DRB to send SDAP packets to the second communication device, instructing the second communication device to use the DRB to send the data to the first communication device after the data in the subsequent QoS stream arrives.

[0157] It should be noted that the counterpart to RQI is the reflection QoS mechanism, as shown in Figure 10, which is a schematic diagram of the downlink reflection QoS mechanism provided in the embodiment of this application. As shown in Figure 10, when a UE initiates a specific service, if no signaling plane filter is matched, it will use the default QoS flow (e.g., default QoS Flow1) to send uplink data. The QoS Flow signaling plane is triggered to establish, which can realize the UPF downlink flow mapping, that is, send downlink data through QoS Flow2. After the UE receives the downlink data flow, it generates the mapping of the uplink data flow to the QoS Flow according to the indication in the downlink data flow. That is, the UE will no longer use default QoS Flow1 to send uplink data, but will use QoS Flow2 to send uplink data.

[0158] Specifically, when adding a PFS (e.g., adding a new application) to an existing QoS Flow, the SMF does not inform the UE of the new PFS via signaling. Instead, the UE infers the PFS itself based on the information carried in the header of the received data packets. See Figure 11, which is a schematic diagram of the downlink reflection QoS process provided in an embodiment of this application. As shown in Figure 11, the SMF sends a message to the UPF / RAN carrying QoS Flow information, including a reflected QoS flag, instructing the UPF / RAN to add an RQI to the header of data packets that meet the specified PCF. The UPF adds an RQI identifier to the DL GTP-U header for specific service flows. Correspondingly, after receiving the GTP-U packet sent by the UPF, the RAN adds an RQI indication to the header of the corresponding downlink SDAP data packet based on the RQI identifier in the header and sends it to the UE in the downlink data. The UE updates the QoS rules based on the RQI and QFI carried in the data packet sent by the RAN, that is, to include the specified service in the current QoS Flow. The UE-derived QoS rule includes an uplink packet filter (UL packet filter), QFI, and a priority value, that is, to update the UL SDF of the specified QoS Flow. Optionally, a reflected QoS timer is also configured, which comes from a pre-configured one or the SMF / PCF. After the timeout, the UE deletes the corresponding UE-derived QoS rule.

[0159] Furthermore, in addition to the methods described above for updating the QoS rules at the NAS layer, the RQI mechanism is also associated with updating the QoS flow-DRB mapping rules at the AS layer. See Figure 12, which is a cell-based schematic diagram of downlink SDAP protocol data with an SDAP header provided in this embodiment. As shown in Figure 12, the UE receives DL data with an SDAP header at the AS layer SDAP entity. RQI is used to indicate whether to notify the NAS layer of the SDF-to-QoS flow mapping rule update, and the Reflected DRB Indication (RDI) is used to indicate the update of the QoS flow-to-DRB mapping rule. Specifically, before time T0, the data of QoS flow A is carried by DRB2, and the UE also receives the downlink data of QoS flow A from DRB2. The QFI in the SDAP header is A. At time T0, the downlink data of QoS flow A is carried by DRB1. The UE receives the data of QoS flow A from DRB1. At this time, it finds that the QFI in the SDAP header received from DRB1 is A, and at the same time, RDI is set to 1. Then, when the UE sends uplink data, it sends an end-marker control protocol data unit (PDU) to DRB2, indicating that it stops mapping the SDAP SDU of the QoS flow indicated by QFI (i.e., QFI A above) to the DRB (i.e., DRB2 above) that sent the end-marker control PDU, and updates the original mapping rule (QoS flow A-DRB2) to QoS flow A-DRB1. The uplink data of QoS flow A of the UE is then delivered from DRB1.

[0160] It should be understood that the RQI used in this application embodiment is not exactly the same as the existing reflection QoS mechanism. The existing reflection QoS mechanism is for downlink, that is, the first communication device (e.g., UE) performs its own deduction based on the information carried in the header of the received data packet to update the mapping rules. However, the embodiment of this application is for uplink, that is, the second communication device (e.g., RAN) performs the deduction based on the information (e.g., RQI) carried in the header of the received SDAP packet to update the mapping rules.

[0161] In one alternative implementation, the first communication device adds a DRB index value to the SDAP packet header and sends the SDAP packet to the second communication device.

[0162] Specifically, the first communication device adds an indication field to the SDAP packet header. This indication field can be a redefined field, a reused extended field in the SDAP packet header, or a reinterpretation of an existing field. Optionally, this indication field is an N-bit field used to add a DRB index value, where N is an integer greater than 1. If it is necessary to switch the DRB to carry application layer service data, the first communication device sends an SDAP packet with the added DRB index value to the second communication device using the previous DRB. Upon receiving the SDAP packet, the second communication device determines the corresponding DRB based on the DRB index value. Subsequent data transmission and reception are carried using the newly determined DRB.

[0163] For example, see Figure 13, which is a schematic diagram of on-demand selection of multiple DRBs provided in an embodiment of this application. As shown in Figure 13, the RAN pre-configures two DRBs, DRB0 and DRB1, with an index value of 00 for DRB0 and an index value of 01 for DRB1. Their corresponding downlink scheduling intervals are 10ms and 100ms, respectively. Multiple applications are deployed in the UE, such as APP1, APP2, and APP3. Assuming that the UE initially carries service data with the RAN through DRB0, APP2 enables the OS to inform the modem through an AT command that the acceptable downlink scheduling latency is 110ms. Then, the UE adds the index value 01 to the header of the SDAP packet and sends the SDAP packet to the RAN through DRB0. After receiving the SDAP packet, the RAN updates the SDAP mapping rules and switches the data in the subsequent QoS flow to DRB1 with an index value of 01.

[0164] In one alternative implementation, the first communication device sends the downlink scheduling interval of application layer service data to the second communication device via a MAC CE, the MAC CE including a scheduling policy index value.

[0165] Specifically, the parsing of scheduling policies is completed and implemented at the MAC protocol layer. Therefore, when only one DRB is configured, all QoS flow data will be carried through this DRB, but it can correspond to different MAC scheduling policies. If multiple scheduling policies are configured and it is necessary to update the scheduling policy to schedule application layer service data, the first communication device can add the scheduling policy index value to the MAC CE and send the MAC CE to the second communication device. The MAC layer of the second communication device will parse it and determine the corresponding scheduling policy based on the scheduling policy index value. Subsequent service data will be scheduled according to the newly determined scheduling policy.

[0166] For example, refer to Figure 14, which is a schematic diagram of on-demand selection of multiple scheduling strategies provided in an embodiment of this application. As shown in Figure 14, the RAN pre-configures two scheduling strategies, namely scheduling strategy 1 and scheduling strategy 2. The index value of scheduling strategy 1 is 00, and the index value of scheduling strategy 2 is 01. Their corresponding downlink scheduling intervals are 10ms and 100ms, respectively. Multiple applications are deployed in the UE, such as APP1, APP2, and APP3. Assuming that the UE and RAN initially use scheduling strategy 1 to schedule service data, APP2 enables the OS to inform the modem through an AT command that the acceptable downlink scheduling latency is 110ms. Then, the UE adds the index value 01 to the MAC CE and sends the MAC CE to the RAN. After receiving the MAC CE, the RAN updates the scheduling strategy and schedules subsequent service data using scheduling strategy 2.

[0167] S107: The second communication device sends application layer service data to the first communication device.

[0168] Specifically, the second communication device receives application layer service data from the core network element and forwards the received data to the UE according to the determined downlink scheduling interval.

[0169] In summary, this communication method pre-configures multiple data scheduling index values ​​with downlink scheduling intervals via the RAN. Then, based on AT commands, it enables the UE communication module to perceive the tolerable scheduling intervals of the service. Thus, the UE can determine the downlink scheduling interval for service data and inform the RAN. Finally, the RAN distributes service data according to the determined downlink scheduling interval. This approach does not rely on AF to provide service characteristic information, improving the flexibility of RAN energy-saving scheduling. Furthermore, it avoids complex interactions with core network elements, reducing the occupation of core network resources and improving RAN energy-saving scheduling efficiency.

[0170] The methods of the embodiments of this application have been described in detail above. In order to facilitate better implementation of the above solutions of the embodiments of this application, correspondingly, related devices for cooperating in implementing the above solutions are also provided below.

[0171] This application divides the communication device into functional modules according to the above method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0172] As shown in Figure 15, this application embodiment provides a communication device 300. The communication device 300 can be a first communication device or a second communication device, and can also be a component of the first communication device (e.g., an integrated circuit, a chip, etc.) or a component of the second communication device (e.g., an integrated circuit, a chip, etc.). The communication device 300 can also be other communication units used to implement the methods in the method embodiments of this application. The communication device 300 may include a processing unit 310. Optionally, the communication device 300 may further include a communication unit 320, where the processing unit 310 controls the communication unit 320 to perform data / signaling transmission and reception. The communication unit 320 may also be called a transceiver unit. Optionally, the communication unit 320 may include a sending unit and a receiving unit. The sending unit can be used to send data / signaling, and the receiving unit can be used to receive data / signaling. Optionally, the communication device 300 may further include a storage unit 330, which can be used to store information and / or data and / or instructions, etc. The storage unit 330 can interact with the processing unit 310 and also with the communication unit 320.

[0173] In one possible design, regarding the case where the communication device 300 is used to implement the function of the first communication device in the above method embodiment:

[0174] The communication unit 320 is used to receive configuration information, which includes multiple data scheduling index values, and the data scheduling index values ​​are used to associate the corresponding downlink scheduling intervals.

[0175] The processing unit 310 is used to generate data scheduling information, which indicates the downlink scheduling interval of application layer business data, and the data scheduling information is determined based on configuration information.

[0176] The communication unit 320 is also used to send data scheduling information.

[0177] The communication unit 320 is also used to receive application layer service data.

[0178] In another possible design, regarding the case where the communication device 300 is used to implement the function of the second communication device in the above method embodiment:

[0179] The processing unit 310 is used to generate configuration information, which includes multiple data scheduling index values, and the data scheduling index values ​​are used to associate the corresponding downlink scheduling intervals.

[0180] Communication unit 320 is used to send configuration information.

[0181] The communication unit 320 is also used to receive data scheduling information.

[0182] The communication unit 320 is also used to send application layer service data.

[0183] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0184] As shown in Figure 16, this application embodiment also provides a communication device 400. The communication device 400 can be a UE or a RAN, or it can be a chip, chip system, or processor that supports the UE in implementing the above methods, or it can be a chip, chip system, or processor that supports the RAN in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0185] The communication device 400 may include one or more processors 401. The processor 401 can be used to implement some or all of the functions of the UE or RAN through logic circuits or by running computer programs. The processor 401 may be a general-purpose processor or a dedicated processor, such as a baseband processor, digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or CPU. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs. The communication device may be, for example, a base station, a baseband chip, a terminal, a terminal chip, a distributed unit (DU), or a centralized unit (CU).

[0186] Optionally, the communication device 400 may include one or more memories 402, which may store instructions 404 that can be executed on the processor 401, causing the communication device 400 to perform the methods described in the above method embodiments. Optionally, the memories 402 may also store data. The processor 401 and the memories 402 may be provided separately or integrated together.

[0187] The memory 402 may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), ROM or compact disc read-only memory (CD-ROM), etc.

[0188] Optionally, the communication device 400 may further include a transceiver 405 and an antenna 406. The transceiver 405 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 405 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0189] In one possible design, regarding the case where the communication device 400 is used to implement the functions of the UE in the above method embodiments:

[0190] Transceiver 405 is used to receive configuration information, which includes multiple data scheduling index values, and these data scheduling index values ​​are used to associate the corresponding downlink scheduling intervals.

[0191] Processor 401 is used to generate data scheduling information that indicates the downlink scheduling interval of application layer business data, and the data scheduling information is determined based on configuration information.

[0192] The transceiver 405 is also used to send data scheduling information.

[0193] The transceiver 405 is also used to receive application layer business data.

[0194] In another possible design, regarding the case where the communication device 400 is used to implement the RAN function in the above method embodiments:

[0195] Processor 401 is used to generate configuration information, which includes multiple data scheduling index values, which are used to associate the corresponding downlink scheduling intervals.

[0196] Transceiver 405 is used to send configuration information.

[0197] Transceiver 405 is also used to receive data scheduling information.

[0198] The transceiver 405 is also used to send application layer business data.

[0199] In another possible design, the processor 401 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0200] In another possible design, the processor 401 may optionally store instructions 403, which, when executed on the processor 401, cause the communication device 400 to perform the methods described in the above method embodiments. Instructions 403 may be embedded in the processor 401; in this case, the processor 401 may be implemented in hardware.

[0201] In another possible design, the communication device 400 may include circuitry that performs the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application embodiment can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0202] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0203] The embodiments of this application and the above-described method embodiments are based on the same concept and have the same technical effects. For the specific principles, please refer to the description in the above-described method embodiments, which will not be repeated here.

[0204] This application also provides a computer-readable storage medium for storing computer software instructions that, when executed by a communication device, implement the functions of any of the above method embodiments.

[0205] This application also provides a computer program product for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0206] This application also provides a computer program that, when run on a computer, implements the functions of any of the above method embodiments.

[0207] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., SSDs), etc.

[0208] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a first communication device, comprising: Receive configuration information, which includes multiple data scheduling index values, and the data scheduling index values ​​are used to associate the corresponding downlink scheduling intervals; Send a first message to the second communication device, the first message indicating the downlink scheduling interval of the data, the first message being determined based on the configuration information; Receive the data sent by the second communication device based on the downlink scheduling interval.

2. The method as described in claim 1, characterized in that, The data scheduling index value includes the data radio bearer (DRB) index value, and the first information determined based on the configuration information includes: Based on the attention AT command and multiple DRB index values, the DRB corresponding to the data is determined.

3. The method as described in claim 1, characterized in that, Sending the first information to the second communication device includes: Add a first indication to the Business Data Adaptation Protocol (SDAP) header; the first indication is used to determine the DRB corresponding to the data to be carried. The SDAP packet is sent to the second communication device via the DRB that carries the data.

4. The method as described in claim 1, characterized in that, The data scheduling index value includes the data radio bearer (DRB) index value, and the first information determined based on the configuration information includes: Based on the attention AT command and multiple DRB index values, the DRB index value corresponding to the data is determined.

5. The method as described in claim 1, characterized in that, Sending the first information to the second communication device includes: Add the DRB index value to the SDAP packet header; The SDAP packet is sent to the second communication device.

6. The method as described in claim 1, characterized in that, The data scheduling index value includes a scheduling policy index value, and the first information, determined based on the configuration information, includes: Based on the attention AT command and multiple scheduling policy index values, the scheduling policy index value corresponding to the data is determined.

7. The method as described in claim 1, characterized in that, Sending the first information to the second communication device includes: The first information is sent to the second device via the Media Access Control Unit (MAC CE), wherein the MAC CE includes a scheduling policy index value.

8. The method according to any one of claims 1-7, characterized in that, Before receiving configuration information, the method further includes: Establish a Radio Resource Control (RRC) connection with the second communication device; The received configuration information includes: Receive RRC signaling sent by the second communication device, wherein the RRC signaling includes the configuration information.

9. The method according to any one of claims 1-8, characterized in that, The maximum value of the downlink scheduling interval is less than or equal to the delay budget value (PDB) of the default QoS packet.

10. A communication method, characterized in that, Applied to a second communication device, including: Generate configuration information, which includes multiple data scheduling index values, and the data scheduling index values ​​are used to associate the corresponding downlink scheduling intervals; The configuration information is sent to the first communication device; Receive first information sent by the first communication device, wherein the first information indicates the downlink scheduling interval of the data; Based on the first information, the data is sent to the first communication device.

11. The method as described in claim 10, characterized in that, The data scheduling index value includes a DRB index value, and the first information received from the first communication device includes: Receive an SDAP packet sent by the first communication device, wherein the header of the SDAP packet includes a first indication; Based on the first instruction, determine the DRB corresponding to the data carrier; Sending the data to the first communication device based on the first information includes: The data is sent to the first communication device by carrying the DRB corresponding to the SDAP packet.

12. The method as described in claim 10, characterized in that, The data scheduling index value includes a DRB index value, and the first information received from the first communication device includes: Receive SDAP packets sent by the first communication device, wherein the header of the SDAP packets includes a DRB index value; Sending the data to the first communication device based on the first information includes: The data is sent to the first communication device through the DRB corresponding to the DRB index value.

13. The method as described in claim 10, characterized in that, The data scheduling index value includes a scheduling policy index value, and receiving the first information sent by the first communication device includes: Receive the MAC CE sent by the first communication device, wherein the MAC CE includes a scheduling policy index value; Sending the data to the first communication device based on the first information includes: The data is sent to the first communication device according to the scheduling policy corresponding to the scheduling policy index value.

14. The method according to any one of claims 10-13, characterized in that, Before sending the configuration information to the first communication device, the method further includes: Establish an RRC connection with the first communication device; Sending the configuration information to the first communication device includes: Send RRC signaling to the first communication device, the RRC signaling including the configuration information.

15. The method according to any one of claims 10-14, characterized in that, The maximum value of the downlink scheduling interval is less than or equal to the PDB of the default QoS.

16. A communication device, characterized in that, Includes units or modules for performing the method according to any one of claims 1 to 15.

17. A communication device, characterized in that, Including memory and processor; The memory is used to store instructions or computer programs; The processor is configured to execute the computer program or instructions stored in the memory to cause the communication device to perform the method of any one of claims 1 to 15.

18. A wireless communication system, characterized in that, include: A first communication device for performing the method according to any one of claims 1 to 9, and / or a second communication device for performing the method according to any one of claims 10 to 15.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes a communication device including the processor to perform the method as described in any one of claims 1 to 15.

20. A computer program product, the computer program product comprising: Computer program code, when executed by a processor, causes a communication device including the processor to perform the method as described in any one of claims 1 to 15.

Images