Information configuration method and device, related equipment and storage medium

Abstract

The invention discloses an information configuration method and device, a terminal, network equipment and a storage medium. The method comprises: a terminal receiving configuration information associated with at least one discontinuous reception (DRX), each DRX in the at least one DRX being capable of supporting different configuration grants (CG) or semi-persistent scheduling (SPS), and a configuration parameter of each DRX being associated with a property of a service flow supported by the corresponding CG or SPS.

Description

Technical Field

[0001] This application relates to the field of wireless communications, and in particular, to an information configuration method, apparatus, related device, and storage medium. Background Art

[0002] In the related art, in order to achieve energy saving of a terminal, the discontinuous reception (DRX) mechanism can be used to reduce power consumption.

[0003] However, in multiple service scenarios with different cycles, the DRX mechanism in the related art may be difficult to meet the energy saving requirements of the terminal. Summary of the Invention

[0004] To solve the problems in the related art, embodiments of this application provide an information configuration method, apparatus, related device, and storage medium.

[0005] The technical solution of the embodiments of this application is implemented as follows:

[0006] Embodiments of this application provide an information configuration method applied to a terminal, including:

[0007] Receiving configuration information associated with at least one DRX, where each DRX in the at least one DRX can support different configured grants (CGs) or semi-persistent schedulings (SPSs), and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

[0008] In the above solution, the configuration information includes at least one of the following:

[0009] First information, where the first information is used to identify a DRX;

[0010] Second information, where the second information is used to indicate at least one CG supported by the DRX;

[0011] Third information, where the third information is used to indicate at least one SPS supported by the DRX;

[0012] Fourth information, where the fourth information is used to indicate at least one logical channel (LC) supported by the DRX;

[0013] Fifth information, where the fifth information is used to indicate at least one data radio bearer (DRB) supported by the DRX;

[0014] Sixth information, where the sixth information is used to indicate at least one LC group supported by the DRX.

[0015] In the above solution, the configuration information includes:

[0016] The seventh information, where the seventh information is used to indicate at least one DRX that the LC is allowed to use.

[0017] In the above solution, the method further includes:

[0018] Receiving the eighth information, where the eighth information is used to indicate the activation and / or deactivation of the DRX in the at least one DRX.

[0019] In the above solution, the activation and / or deactivation of the DRX is indicated by means of a bitmap.

[0020] In the above solution, the method further includes:

[0021] Sending the ninth information to the network side, where the ninth information is used to indicate that the terminal supports multi-DRX configuration.

[0022] An embodiment of the present application further provides an information configuration method, which is applied to a network device and includes:

[0023] Sending configuration information associated with at least one DRX to a terminal, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the service flow supported by the corresponding CG or SPS.

[0024] In the above solution, the configuration information includes at least one of the following:

[0025] The first information, where the first information is used to identify a DRX;

[0026] The second information, where the second information is used to indicate at least one CG supported by the DRX;

[0027] The third information, where the third information is used to indicate at least one SPS supported by the DRX;

[0028] The fourth information, where the fourth information is used to indicate at least one LC supported by the DRX;

[0029] The fifth information, where the fifth information is used to indicate at least one DRB supported by the DRX;

[0030] The sixth information, where the sixth information is used to indicate at least one LC group supported by the DRX;

[0031] In the above solution, the configuration information includes:

[0032] The seventh information, where the seventh information is used to indicate at least one DRX that the LC is allowed to use.

[0033] In the above solution, the method further includes:

[0034] Sending an eighth piece of information to the terminal, where the eighth piece of information is used to indicate activation and / or deactivation of DRX in the at least one DRX.

[0035] In the above solution, activation and / or deactivation of DRX is indicated by means of a bitmap.

[0036] In the above solution, the method further includes:

[0037] Receiving a ninth piece of information sent by the terminal, where the ninth piece of information is used to indicate that the terminal supports multi-DRX configuration.

[0038] An embodiment of the present application further provides an information configuration device, including:

[0039] A first receiving unit, configured to receive configuration information associated with at least one DRX, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the service flow supported by the corresponding CG or SPS.

[0040] An embodiment of the present application further provides an information configuration device, including:

[0041] A first sending unit, configured to send configuration information associated with at least one DRX to a terminal, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the service flow supported by the corresponding CG or SPS.

[0042] An embodiment of the present application further provides a terminal, including: a first processor and a first communication interface; wherein,

[0043] The first communication interface is configured to receive configuration information associated with at least one DRX, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the service flow supported by the corresponding CG or SPS.

[0044] An embodiment of the present application further provides a network device, including: a second processor and a second communication interface; wherein,

[0045] The second communication interface is configured to send configuration information associated with at least one DRX to a terminal, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the service flow supported by the corresponding CG or SPS.

[0046] An embodiment of the present application further provides a terminal, including: a first processor and a first memory for storing a computer program that can run on the processor,

[0047] Wherein, when the first processor is used to run the computer program, it executes the steps of any of the above methods on the terminal side.

[0048] An embodiment of the present application further provides a network device, including: a second processor and a second memory for storing a computer program that can run on the processor,

[0049] Wherein, when the second processor is used to run the computer program, it executes the steps of any of the above methods on the network device side.

[0050] An embodiment of the present application further provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of any of the above methods on the terminal side, or implements the steps of any of the above methods on the network device side.

[0051] In the information configuration method, device, related device, and storage medium provided by the embodiments of the present application, the terminal receives configuration information associated with at least one DRX sent by the network side. Each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the service flow supported by the corresponding CG or SPS. In the solution provided by the embodiments of the present application, the network device configures DRX configuration parameters for the terminal such that each DRX can support different CGs or SPSs. In this way, in a scenario where there are multiple services with different periods, the terminal can select (or equivalently, use) the corresponding DRX configuration parameters according to different services, enabling the terminal to be in a sleep state during other times except when transmitting data according to the periods of each service, thereby meeting the energy-saving requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 It is a schematic diagram of the state change of the terminal when a DRX is activated;

[0053] Figure 2 It is a flowchart of an information configuration method according to an embodiment of the present application

[0054] Figure 3 It is a flowchart of another information configuration method according to an embodiment of the present application;

[0055] Figure 4 It is a flowchart of an information configuration method for an application example of the present application;

[0056] Figure 5 It is a schematic diagram of the state change of the terminal when a DRX is activated for an application example of the present application;

[0057] Figure 6 Schematic structural diagram of an information configuration device according to an embodiment of the present application;

[0058] Figure 7 Schematic structural diagram of another information configuration device according to an embodiment of the present application;

[0059] Figure 8 Schematic structural diagram of a terminal according to an embodiment of the present application;

[0060] Figure 9 Schematic structural diagram of a network device according to an embodiment of the present application;

[0061] Figure 10 Schematic structural diagram of an information configuration system according to an embodiment of the present application. Detailed implementation manners

[0062] The present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0063] In the related art, in the DRX technology, for each terminal, the DRX mechanism is configured for each terminal, that is, each terminal has its own exclusive DRX configuration parameters, and the DRX configuration is periodic. The DRX configuration for each terminal is a common DRX configuration, that is to say, all services use this DRX configuration.

[0064] Exemplarily, as Figure 1 shown, when the terminal is DRX-activated, it does not perform scheduling information detection and data transmission during the sleep state period, and can detect possible scheduling information during the non-sleep state period (i.e., the wake-up period), so as to transmit data based on the detected scheduling information. In this way, the terminal can achieve terminal energy saving by periodically entering the low-power sleep state.

[0065] In the related art, for the energy-saving scheme related to the extended reality (XR) technology, currently it only includes a single periodic traffic flow such as an I-frame (which can also be called an intra-coded frame or an intra picture) model or a P-frame (which can also be called a forward prediction coded frame) model. By configuring DRX for the single periodic traffic flow, the terminal can enter the power-saving mode corresponding to the configured DRX. Specifically, the DRX configuration scheme for the single periodic traffic flow can configure a non-integer period DRX, and can also ensure the periodicity of DRX when the system frame number (SFN) cycles.

[0066] However, applications such as XR and the metaverse may include multiple service flows, such as video service flows, audio service flows, haptic service flows, etc. The natures of different service flows (which can also be referred to as the characteristics of service flows) may be different. For example, different service flows may have different periods, different packet sizes, and different packet delay budgets (PDBs), etc. Therefore, the terminal needs to support the natures of multiple different service flows simultaneously and transmit data within the period corresponding to each service flow. In this case, a single DRX configuration will cause the terminal to stay in a non-sleep state for a long time in order to meet the different periods of multiple services, making it difficult to achieve the energy-saving effect;

[0067] In the related art, for a service flow that requires the terminal to periodically send uplink data, the network side can configure the corresponding CG for the terminal to schedule the terminal to periodically send uplink data; correspondingly, for a service flow that requires the terminal to periodically receive downlink data, the network side can configure the corresponding SPS for the terminal to schedule the terminal to periodically receive downlink data. Among them, the uplink refers to the direction in which the terminal sends data to the network side, and the downlink refers to the direction in which the network side sends data to the terminal.

[0068] However, in the case where the terminal needs to support multiple different periodic service flows simultaneously, a single DRX configuration cannot support different CGs or SPSs, which will cause the terminal to stay in a non-sleep state for a long time in order to meet the different periods of multiple services, making it difficult to achieve the energy-saving effect.

[0069] Exemplarily, assume that the terminal supports service A and service B simultaneously. Among them, the period of service A is 3s, and data needs to be transmitted during the period from 0s to 1s within the period, and the period of service B is 6s, and data needs to be transmitted during the period from 4s to 5s within the period. If the DRX configuration method in the related art is used, the DRX period can be configured as the common period of the two services (i.e., 6s). At the same time, the wake-up time period of DRX is configured as the start time of the first data transmission (i.e., 0s) to the end time of the last data transmission (i.e., 5s) within the period. That is to say, using the DRX configuration scheme in the related art, the terminal needs to stay in a non-sleep state during the period from 0s to 5s within a 6s period, making it difficult to achieve effective energy saving.

[0070] Based on this, in various embodiments of the present application, the network device configures DRX for the terminal with DRX configuration parameters that can support different CGs or SPSs. In this way, in the scenario of multiple services with different periods (i.e., the periods of multiple services are different), the terminal can use the corresponding DRX configuration parameters according to different services, so that the terminal can be in a sleep state at other times except when meeting the data transmission of each service period, thereby meeting the energy-saving requirements.

[0071] An embodiment of the present application provides an information configuration method, which is applied to a terminal, such as Figure 2 As shown, the method includes:

[0072] Step 201: Receive configuration information associated with at least one DRX, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

[0073] Wherein, in actual application, the terminal may be referred to as a user equipment (UE, User Equipment), a terminal device, a device, or a user, etc., and the embodiments of the present application do not limit this.

[0074] In actual application, the terminal may use the configuration parameters of one or more DRXs in the at least one DRX according to the services that the terminal actually needs to support, so that the terminal can be in a sleep state at other times except when transmitting data in each service cycle, thereby meeting the energy-saving requirements.

[0075] Exemplarily, based on the above example, the terminal receives the configuration information of DRX-A for service A and the configuration information of DRX-B for service B respectively. When the terminal needs to support both service A and service B at the same time, the terminal can use DRX-A and DRX-B at the same time. In this way, the terminal can remain in a non-sleep state only during the time periods of 0s-1s and 3s-5s when data transmission is required within a 6s cycle, and can enter the sleep state at other times. Compared with the DRX configuration scheme in the related art, it can effectively achieve energy saving of the terminal.

[0076] In actual application, the terminal may report to the network side that the terminal supports multi-DRX configuration, so that the network side can send the configuration information associated with at least one DRX to the terminal that supports multi-DRX configuration.

[0077] Based on this, in an embodiment, before step 201, the method may further include:

[0078] Step 200: Send a ninth piece of information to the network side, where the ninth piece of information is used to indicate that the terminal supports multi-DRX configuration.

[0079] Here, in actual application, the terminal may send the ninth piece of information to the network side through a radio resource control (RRC, Radio Resource Control) signaling or a media access control control element (MAC CE, Media Access Control Control Element), etc.

[0080] In actual application, the network side can configure corresponding CG or SPS for the terminal by using the nature of the service flow corresponding to each service among multiple services. Wherein, each CG or SPS supports the nature of at least one service flow. In this way, after the network side configures CG or SPS for the terminal, at least one DRX can be configured for the terminal, and the configuration parameters of each DRX in the at least one DRX are associated with the nature of the service flow supported by the corresponding CG or SPS.

[0081] Specifically, in one embodiment, the configuration information includes at least one of the following:

[0082] The first information, which is used to identify a DRX;

[0083] The second information, which is used to indicate at least one CG supported by the DRX;

[0084] The third information, which is used to indicate at least one SPS supported by the DRX;

[0085] The fourth information, which is used to indicate at least one LC supported by the DRX;

[0086] The fifth information, which is used to indicate at least one DRB supported by the DRX;

[0087] The sixth information, which is used to indicate at least one LC group supported by the DRX.

[0088] Here, in actual application, the network side can send the configuration information to the terminal through RRC signaling or the like, and the embodiments of the present application do not limit this.

[0089] In actual application, the first information may specifically be a DRX ID, and a specific DRX is identified by the DRX ID.

[0090] In actual application, the presentation form of the second information may be a list of CG IDs supported by the DRX (which can be expressed in English as allowedCG-List), and the CG ID list includes at least one CG ID, and each CG ID is used to identify a CG. When the configuration information includes the second information, the DRX corresponding to the configuration information is associated with the nature of the service flow supported by at least one CG identified by the CG ID list corresponding to the second information.

[0091] In actual application, the presentation form of the third information may be a list of SPS IDs supported by DRX (which can be expressed in English as allowedSPS-List). The SPS ID list contains at least one SPS ID, and each SPS ID is used to identify an SPS. When the configuration information contains the third information, the DRX corresponding to the configuration information is associated with the nature of the service flows supported by at least one SPS identified by the SPS ID list corresponding to the third information.

[0092] In actual application, when the configuration information of a DRX contains the second information, the terminal can use the second information to determine at least one CG indicated by the second information. The terminal can use at least one CG to determine the non-sleep state period and the sleep state period corresponding to this DRX. In this way, the terminal can enter the non-sleep state and the sleep state based on this DRX, thereby achieving energy saving of the terminal. At the same time, when the configuration information of a DRX contains the third information, the terminal can also use the third information to determine at least one SPS indicated by the third information. The terminal can use at least one SPS to determine the non-sleep state period and the sleep state period corresponding to this DRX. In this way, the terminal can enter the non-sleep state and the sleep state based on this DRX, thereby achieving energy saving of the terminal.

[0093] In actual application, the terminal will establish a corresponding DRB to carry data related to the service flow according to the nature of the service flow, and at the same time establish the CG or SPS to transmit the data of the corresponding DRB to support the corresponding service flow characteristics. Specifically, the data related to the service flow is transmitted through the LC or LC group corresponding to the DRB. It can be seen that there is a corresponding relationship between the DRB and the nature of the service flow supported by the CG or SPS. Furthermore, there is also a corresponding relationship between the LC or LC group and the nature of the service flow supported by the CG or SPS. That is to say, the nature of the service flow supported by the corresponding CG or SPS can be determined by using at least one of the DRB, LC, and LC group.

[0094] In actual application, the presentation form of the fifth information may be a list of DRB IDs supported by DRX (which can be expressed in English as AllowedDRB-List). The DRB ID list contains at least one DRB ID, and each DRB ID is used to identify a DRB. In this way, when the configuration information contains the fifth information, the DRX corresponding to the configuration information is associated with at least one DRB; further, it is associated with the nature of the service flow supported by at least one CG or SPS corresponding to the at least one DRB.

[0095] In actual application, the presentation form of the fourth information may be a list of LCIDs supported by DRX (which can be expressed in English as logicalChannelIdentity-List), and the LCID list contains at least one LCID, and each LCID is used to identify an LC. Thus, when the configuration information includes the fourth information, the DRX corresponding to the configuration information is associated with at least one LC, and further, is associated with the nature of at least one CG or SPS supported service flow corresponding to the at least one LC.

[0096] The presentation form of the sixth information may be a list of LC group IDs supported by DRX (which can be expressed in English as logicalChannelGroupID-List), and the LC group ID list contains at least one LC group ID, and each LC group ID is used to identify an LC group. Thus, when the configuration information includes the sixth information, the DRX corresponding to the configuration information is associated with at least one LC group, and further, is associated with the nature of at least one CG or SPS supported service flow corresponding to the at least one LC group.

[0097] Exemplarily, when the configuration information of a DRX includes the fourth information, the terminal can use the fourth information to determine at least one LC indicated by the fourth information, and then determine at least one CG or SPS corresponding to the at least one LC. Thus, the terminal can use at least one CG or SPS to determine the non-sleep state period and sleep state period corresponding to this DRX, and the terminal can enter the non-sleep state and sleep state based on this DRX, thereby realizing energy saving of the terminal. At the same time, when the configuration information of a DRX includes the fifth information and / or the sixth information, the terminal can also use the fifth information and / or the sixth information to determine at least one DRB corresponding to the fifth information and / or determine at least one LC group corresponding to the sixth information, and then determine at least one CG or SPS corresponding to the at least one DRB and / or the at least one LC group. Thus, the terminal can use at least one CG or SPS to determine the non-sleep state period and sleep state period corresponding to this DRX, and the terminal can enter the non-sleep state and sleep state based on this DRX, thereby realizing energy saving of the terminal.

[0098] In actual application, the terminal transmits data through the LC, and there is a corresponding relationship between the LC and the nature of the service flow supported by the CG or SPS. Thus, the network side can use the configuration information to indicate the DRX allowed to be used by each LC, so that the DRX is associated with the nature of the service flow supported by the corresponding CG or SPS.

[0099] Specifically, in one embodiment, the configuration information may include:

[0100] Seventh information, where the seventh information is used to indicate at least one DRX that the LC is allowed to use.

[0101] Here, in actual application, the presentation form of the seventh information may be a DRX ID list that the LC is allowed to use. The DRX ID list contains at least one DRX ID, and each DRX ID is used to identify a DRX.

[0102] In actual application, the network side needs to send mapping restriction conditions (which can be expressed in English as MappingRestriction) to the terminal to control the LC priority (LCP, Logical Channel Prioritization) sorting process in the terminal, that is, to indicate which LCs the terminal can use for transmission. Among them, the mapping restriction conditions are associated with at least one LC.

[0103] Based on this, the network side can include the seventh information in the mapping restriction condition information sent to the terminal; specifically, the correspondence between each LC in at least one LC and the DRX ID list can be included in the mapping restriction condition.

[0104] Exemplarily, assume that the configuration information is used to configure 4 DRXs, namely DRX1, DRX2, DRX3, and DRX4, and the terminal transmits data through 3 LCs, namely LC1, LC2, and LC3. At this time, the correspondence between the LC and the DRX ID list (that is, the seventh information) may specifically include: LC1 - {DRX1}; LC2 - {DRX2, DRX4}; LC3 - {DRX1, DRX2, DRX3}. In this way, the terminal can determine through the correspondence that LC1 is allowed to use DRX1, LC2 is allowed to use DRX2 and DRX4, and LC3 is allowed to use DRX1, DRX2, and DRX3. Further, the terminal can use the correspondence between each LC and at least one CG or SPS to associate the corresponding DRX with the at least one CG or SPS.

[0105] In actual application, after the network side sends the configuration information to the terminal, it can activate the corresponding DRX by sending activation information corresponding to the configuration information to the terminal, so that the terminal can use the DRX to achieve terminal energy saving.

[0106] Specifically, in one embodiment, the method may further include:

[0107] Receiving eighth information, where the eighth information is used to indicate activation and / or deactivation of the DRX in the at least one DRX.

[0108] Here, in practical applications, the network side may send the eighth information to the terminal through RRC signaling, MAC CE, DCI, or the like.

[0109] In practical applications, the terminal can use the eighth information to determine which DRXs to activate and / or deactivate (i.e., activate and / or deactivate the DRXs in the at least one DRX), and control the terminal to enter the sleep state or the non-sleep state based on the activated DRX. When the terminal enters the non-sleep state (is awakened), it can perform data transmission. In this way, in the scenario of multiple periodic services, the terminal can use the corresponding DRX configuration parameters according to different services, so that the terminal can be in the sleep state at other times except when meeting the periodic data transmission requirements of each service, thereby meeting the energy-saving requirements.

[0110] In practical applications, the network side can indicate the activation and / or deactivation of the DRXs in the at least one DRX in the form of a bitmap. That is to say, in one embodiment, the activation and / or deactivation of the DRX is indicated in the form of a bitmap.

[0111] Exemplarily, the eighth information may include a bitmap corresponding to the DRX ID list. The DRX ID list includes at least one DRX ID, and each DRX ID is used to identify a DRX. Each bit in the bitmap corresponds to a DRX ID in the DRX ID list. For example, when the bit is set to 1, it indicates that the corresponding DRX is activated; when the bit is set to 0, it indicates that the corresponding DRX is not activated (which can also be understood as deactivated). Of course, it can also be set that when the bit is set to 1, it indicates that the corresponding DRX is not activated, and when the bit is set to 0, it indicates that the corresponding DRX is activated. In this way, by indicating the activation and / or deactivation of the DRX in the form of a bitmap, the network side does not need to include the DRX ID corresponding to each DRX in the eighth information, which can reduce the length of the information and thus save signaling overhead. It should be noted that the corresponding relationship between each bit in the bitmap and the DRX ID in the DRX ID list can be preset in the terminal, and the present application embodiment does not limit the presetting method of the corresponding relationship.

[0112] In practical applications, after the terminal activates the DRXs in the at least one DRX using the eighth information, it can report the confirmation information of the completion of the activation and / or deactivation of the DRX to the network side.

[0113] Based on this, in one embodiment, the method may further include:

[0114] Sending the tenth information, where the tenth information is used to instruct the terminal to confirm the completion of the activation and / or deactivation of the DRXs in the at least one DRX.

[0115] Among them, in actual application, the terminal can be instructed to confirm the completion of activation and / or deactivation of DRX in the form of a bitmap.

[0116] Exemplarily, the tenth information may include a bitmap corresponding to a DRX ID list, the DRX ID list includes at least one DRX ID, each DRX ID is used to identify a DRX, and each bit in the bitmap corresponds to a DRX ID in the DRX ID list. For example, when the bit is set to 1, it indicates that the terminal is instructed to confirm the completion of activation and / or deactivation of the corresponding DRX, and when the bit is set to 0, it indicates that the activation state of the corresponding DRX remains unchanged. Of course, it can also be set that when the bit is set to 1, it indicates that the activation state of the corresponding DRX remains unchanged, and when the bit is set to 0, it indicates that the terminal is instructed to confirm the completion of activation and / or deactivation of the corresponding DRX. In this way, by using the bitmap to instruct the terminal to confirm the completion of activation and / or deactivation of the corresponding DRX, the terminal does not need to include the DRX ID corresponding to each DRX in the tenth information, which can reduce the length of the information, thereby saving signaling overhead. It should be noted that the correspondence between each bit in the bitmap and the DRX ID in the DRX ID list can be preset in the network side, and the present application embodiment does not limit the presetting method of the correspondence.

[0117] Correspondingly, the embodiment of the present application further provides an information configuration method, which is applied to a network device, such as Figure 3 as shown, the method includes:

[0118] Step 301: Send configuration information associated with at least one DRX to the terminal, each DRX in the at least one DRX can support different CG or SPS, and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

[0119] Here, in actual application, the network device may specifically be a base station, such as a gNB. The present application embodiment does not limit the name of the network device, as long as its function can be realized.

[0120] In actual application, the terminal may report to the network device that the terminal supports multi-DRX configuration, so that the network side can send configuration information associated with at least one DRX to the terminal that supports multi-DRX configuration.

[0121] Based on this, in an embodiment, before step 301, the method may further include:

[0122] Step 300: Receive the ninth information sent by the terminal, where the ninth information is used to indicate that the terminal supports multi-DRX configuration.

[0123] In actual application, when the network device indicates that the terminal supports multiple DRX configurations, specifically, it can determine the configuration information associated with at least one DRX based on actual service requirements.

[0124] Specifically, the network device can use the nature of the traffic flow corresponding to each service in multiple services (which can also be understood as actual service requirements) to configure the corresponding CG or SPS for the terminal. Each CG or SPS supports the nature of at least one traffic flow. After the network device configures the CG or SPS for the terminal, it can determine the configuration information associated with at least one DRX according to the configured CG or SPS; and configure at least one DRX for the terminal through step 301. The configuration parameters of each DRX in the at least one DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS. Here, the specific process for the network device in the embodiments of the present application to determine the configuration information associated with at least one DRX is not limited.

[0125] In actual application, after the network device sends the configuration information to the terminal, it can activate the corresponding DRX by sending activation information corresponding to the configuration information to the terminal, so that the terminal can use the DRX to achieve terminal energy saving.

[0126] Specifically, in one embodiment, the method may further include:

[0127] Sending eighth information to the terminal, where the eighth information is used to indicate the activation and / or deactivation of the DRX in the at least one DRX.

[0128] Here, in actual application, the network device can send the eighth information to the terminal through RRC signaling, MAC CE, or DCI, etc.

[0129] In the information configuration method provided by the embodiments of the present application, the terminal receives the configuration information associated with at least one DRX sent by the network device. Each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS. In the solution provided by the embodiments of the present application, the network device configures the DRX configuration parameters for the terminal so that the DRX can support different CGs or SPSs. In this way, in the scenario of multiple services with different periods (i.e., the periods of multiple services are different), the terminal can use the corresponding DRX configuration parameters according to different services, so that the terminal can be in a sleep state at other times except when transmitting data to meet the transmission requirements of each service period, thereby meeting the energy saving requirements.

[0130] The following further describes the present application in detail with application examples.

[0131] In an actual business scenario, configuring a single DRX will cause the terminal to remain in a non-sleep state for a long time in order to meet the different cycles of multiple services, making it difficult to achieve the energy-saving effect.

[0132] In the application example of this application, the base station configures at least one DRX for the terminal based on CG or SPS, which can enable the terminal to reduce power consumption in a multi-service scenario and meet the energy-saving requirements.

[0133] As Figure 4 shown, the process of the network device configuring DRX for the terminal includes the following steps:

[0134] Step 401: The terminal reports to the network device its ability to support multi-DRX configuration;

[0135] Step 402: When the network device receives the ability of the terminal to support multi-DRX configuration reported by the terminal, it configures at least one CG or SPS for the terminal;

[0136] Here, in actual application, the network device can send the configuration information of at least one CG or SPS to the terminal through RRC signaling.

[0137] Step 403: The network device configures at least one DRX associated with the CG or SPS for the terminal;

[0138] Here, in actual application, the configuration information for configuring the DRX may specifically include:

[0139] 1) DRX ID, used to identify the DRX;

[0140] 2) allowedCG-List, used to identify the list of CG IDs supported by the DRX;

[0141] 3) allowedSPS-List, used to identify the list of SPS IDs supported by the DRX;

[0142] 4) logicalChannelIdentity-List, used to identify the list of LC IDs supported by the DRX;

[0143] 5) AllowedDRB-List, used to identify the list of DRB IDs supported by the DRX;

[0144] 6) logicalChannelGroupID-List, used to identify the list of LC group IDs supported by the DRX;

[0145] In actual application, the configuration information may also include the DRX configuration information specified in the relevant technical specifications; specifically, the configuration information may also include at least one of the following:

[0146] The DRX continuous listening timer can be expressed in English as drx-onDurationTimer;

[0147] The DRX inactivity timer can be expressed in English as drx-InactivityTimer;

[0148] The DRX downlink hybrid automatic repeat request round trip time timer (HARQ RTT, Hybrid Automatic Repeat-reQuest Round Trip Time) can be expressed in English as drx-HARQ-RTT-TimerDL;

[0149] The DRX uplink HARQ-RTT timer can be expressed in English as drx-HARQ-RTT-TimerUL;

[0150] The DRX downlink retransmission timer can be expressed in English as drx-RetransmissionTimerDL;

[0151] The DRX uplink retransmission timer can be expressed in English as drx-RetransmissionTimerUL;

[0152] The period and offset of the long DRX cycle can be expressed in English as drx-LongCycleStartOffset;

[0153] The period of the short DRX cycle can be expressed in English as drx-ShortCycle;

[0154] The period timer of the short DRX cycle can be expressed in English as drx-ShortCycleTimer;

[0155] The DRX start delay can be expressed in English as drx-SlotOffset

[0156] Here, it should be noted that the configuration information of each DRX in the at least one DRX is different. However, some configurations in the configuration information of each DRX can be the same. For example, the configuration information of two DRXs can include different DRX start delays and the same period and offset of the long DRX cycle.

[0157] When at least one of the DRX continuous listening timer, DRX inactivity timer, DRX downlink HARQ-RTT timer, DRX uplink HARQ-RTT timer, DRX downlink retransmission timer, DRX uplink retransmission timer, and the period timer of the short DRX cycle corresponding to the at least one DRX is running, the terminal is in a non-sleep state. Exemplarily, such as Figure 5As shown, when the DRX continuous listening timer, DRX inactivity timer, DRX HARQ-RTT timer, and DRX retransmission timer corresponding to the DRX with DRX ID being DRX1 are running, the terminal is in a non-sleep state and continuously consumes energy.

[0158] In practical applications, when the configuration information of the DRX does not include all the DRX configuration information specified in the relevant technical specifications, the terminal can use the configuration information of the CG or SPS supported by the DRX to determine partial configuration information of the DRX.

[0159] Exemplarily, when the configuration information of the DRX does not include the DRX continuous listening timer, the terminal can use the length of the time domain in the CG or SPS supported by the DRX to determine the continuous listening time of the DRX. That is, within the time corresponding to the length of the time domain, the terminal is in a continuous listening state.

[0160] Exemplarily, when the configuration information of the DRX does not include the DRX period, the terminal can use the period in the CG or SPS supported by the DRX to determine the period of the DRX. The period can be a long period or a short period.

[0161] Exemplarily, when the configuration information of the DRX does not include the DRX start-up delay or the period and offset of the long DRX period, the terminal can use the time domain offset (which can be expressed in English as timeDomainOffset) in the CG or SPS supported by the DRX to determine the DRX start-up delay or the period and offset of the long DRX period.

[0162] Step 404: The network device sends an activation command for at least one DRX to the terminal;

[0163] Here, in practical applications, the activation command may include:

[0164] A DRX ID list for identifying the at least one DRX;

[0165] A DRX ID list activation indication bitmap for indicating the activation and / or deactivation of the corresponding DRX.

[0166] Exemplarily, each bit in the bitmap corresponds to a DRX ID in the DRX ID list, and each DRX ID is used to identify a DRX. When the bit is set to 1, it indicates that the corresponding DRX is activated. When the bit is set to 0, it indicates that the corresponding DRX is not activated (which can also be understood as deactivated). Of course, it can also be set that when the bit is set to 1, it indicates that the corresponding DRX is not activated, and when the bit is set to 0, it indicates that the corresponding DRX is activated.

[0167] Step 405: The terminal activates DRX;

[0168] Here, in actual application, the terminal activates the corresponding DRX based on the activation command sent by the network device.

[0169] Step 406: The terminal sends an activation completion confirmation message to the network device.

[0170] Here, in actual application, the activation completion confirmation message may include:

[0171] A DRX ID list for identifying the at least one DRX;

[0172] A DRX ID activation completion confirmation indication bitmap for indicating that the terminal has completed the activation and / or deactivation of the corresponding DRX.

[0173] Exemplarily, each bit in the bitmap corresponds to a DRX ID in the DRX ID list, and each DRX ID is used to identify a DRX. When the bit is set to 1, it indicates that the terminal has confirmed the completion of the activation and / or deactivation of the corresponding DRX. When the bit is set to 0, it indicates that the activation status of the corresponding DRX remains unchanged. Of course, it can also be set that when the bit is set to 1, it indicates that the activation status of the corresponding DRX remains unchanged, and when the bit is set to 0, it indicates that the terminal has confirmed the completion of the activation and / or deactivation of the corresponding DRX.

[0174] In the information configuration scheme provided by the application example of the present application, the network device configures DRX for the terminal to support DRX configuration parameters of different CGs or SPSs. In this way, in the scenario of multiple services with different periods (i.e., the periods of multiple services are different), the terminal can use the corresponding DRX configuration parameters according to different services, so that the terminal can be in a sleep state at other times except when meeting the data transmission requirements of each service cycle, thereby meeting the energy-saving needs in the fields of XR and the metaverse, and reducing the power consumption in devices related to technologies such as Reduced Capability (RedCap) and Internet of Things (IoT).

[0175] To implement the method on the terminal side in the embodiments of the present application, the embodiments of the present application further provide an information configuration device, which is set on the terminal, as Figure 6 shown, and the device includes:

[0176] A first receiving unit 601, configured to receive configuration information associated with at least one DRX, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the service flow supported by the corresponding CG or SPS.

[0177] Wherein, in one embodiment, the first receiving unit 601 is further configured to:

[0178] Receive an eighth piece of information, where the eighth piece of information is used to indicate activation and / or deactivation of DRX in the at least one DRX.

[0179] Here, in one embodiment, the device may further include:

[0180] An activation unit, configured to activate and / or deactivate DRX in the at least one DRX by using the eighth piece of information.

[0181] In one embodiment, as Figure 6 shown, the device may further include:

[0182] A second sending unit 602, configured to send a ninth piece of information to the network side, where the ninth piece of information is used to indicate that the terminal supports multi-DRX configuration.

[0183] In actual application, the first receiving unit 601 and the second sending unit 602 may be implemented by a communication interface in the information configuration device in combination with a processor, and the activation unit may be implemented by the processor in the information configuration device.

[0184] To implement the method on the network device side in the embodiments of the present application, the embodiments of the present application further provide an information configuration device, which is disposed on the network device, as Figure 7 shown, the device includes:

[0185] A first sending unit 701, configured to send configuration information associated with at least one DRX to the terminal, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the service flow supported by the corresponding CG or SPS.

[0186] Wherein, in one embodiment, the first sending unit 701 is further configured to:

[0187] Send the eighth piece of information to the terminal, where the eighth piece of information is used to indicate activation and / or deactivation of DRX in the at least one DRX.

[0188] In one embodiment, as Figure 7 shown, the device may further include:

[0189] A second receiving unit 702, configured to receive the ninth piece of information sent by the terminal, where the ninth piece of information is used to indicate that the terminal supports multi-DRX configuration.

[0190] In one embodiment, the device may further include:

[0191] A determination unit, configured to determine configuration information associated with at least one DRX;

[0192] In actual application, the first sending unit 701 and the second receiving unit 702 may be implemented by a communication interface and a processor in an information configuration device, and the determination unit may be implemented by the processor in the information configuration device.

[0193] It should be noted that: when the information configuration device provided in the above embodiment performs information configuration, only the division of the above program units is used for illustration. In actual application, the above processing may be allocated to different program units according to needs, that is, the internal structure of the device is divided into different program units to complete all or part of the above-described processing. In addition, the information configuration device provided in the above embodiment and the information configuration method embodiment belong to the same concept, and the specific implementation process can be seen in the method embodiment, which will not be elaborated here.

[0194] Based on the hardware implementation of the above program modules, and in order to implement the method on the terminal side of the embodiments of the present application, the embodiments of the present application further provide a terminal, as Figure 8 shown, the terminal 800 includes:

[0195] A first communication interface 801, capable of performing information interaction with a network device;

[0196] A first processor 802, connected to the first communication interface 801 to implement information interaction with the network device, and when running a computer program, execute the method provided by one or more of the above technical solutions on the terminal side; the computer program is stored on the first memory 803.

[0197] Specifically, the first communication interface 801 is configured to:

[0198] Receive configuration information associated with at least one DRX, each DRX in the at least one DRX being capable of supporting different CGs or SPSs, and the configuration parameters of each DRX being associated with the nature of the traffic flow supported by the corresponding CG or SPS.

[0199] Wherein, in one embodiment, the first communication interface 801 is further configured to:

[0200] Receive an eighth piece of information, the eighth piece of information being used to indicate activation and / or deactivation of the DRX in the at least one DRX.

[0201] In one embodiment, the first processor 802 is configured to activate and / or deactivate the DRX in the at least one DRX by using the eighth piece of information.

[0202] In one embodiment, the first communication interface 801 is further configured to:

[0203] Send a ninth message to the network side, where the ninth message is used to indicate that the terminal supports multi-DRX configuration.

[0204] It should be noted that: The specific processing procedures of the first processor 802 and the first communication interface 801 can be understood with reference to the above method.

[0205] Of course, in actual application, each component in the terminal 800 is coupled together through the bus system 804. It can be understood that the bus system 804 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 804 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 8 all kinds of buses are labeled as the bus system 804.

[0206] The first memory 803 in the embodiment of the present application is used to store various types of data to support the operation of the terminal 800. Examples of these data include: any computer program for operating on the terminal 800.

[0207] The method disclosed in the embodiment of the present application above can be applied to the first processor 802, or implemented by the first processor 802. The first processor 802 may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the first processor 802 or the instructions in the form of software. The above-mentioned first processor 802 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 802 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as being completed by the hardware decoding processor, or completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in the storage medium, and this storage medium is located in the first memory 803. The first processor 802 reads the information in the first memory 803 and combines its hardware to complete the steps of the foregoing method.

[0208] In an exemplary embodiment, the terminal 800 may be implemented by one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general purpose processors, controllers, microcontroller units (MCUs), microprocessors, or other electronic components, and is used to execute the foregoing method.

[0209] Based on the hardware implementation of the foregoing program modules, and in order to implement the method on the network device side in the embodiments of the present application, the embodiments of the present application further provide a network device, as Figure 9 shown, the network device 900 includes:

[0210] A second communication interface 901, capable of interacting with the terminal;

[0211] A second processor 902, connected to the second communication interface 901 to implement information interaction with the terminal, and when running a computer program, executes the method provided by one or more technical solutions on the network device side; the computer program is stored on a second memory 903.

[0212] Specifically, the second communication interface 901 is used for:

[0213] Sending configuration information associated with at least one DRX to the terminal, each DRX in the at least one DRX being capable of supporting different CGs or SPSs, and the configuration parameters of each DRX being associated with the nature of the traffic flow supported by the corresponding CG or SPS.

[0214] Wherein, in one embodiment, the second processor 902 is used to determine the configuration information associated with at least one DRX.

[0215] In one embodiment, the second communication interface 901 is further used for:

[0216] Sending eighth information to the terminal, the eighth information being used to indicate activation and / or deactivation of the DRX in the at least one DRX.

[0217] In one embodiment, the second communication interface 901 is further used for:

[0218] Receive a ninth piece of information sent by the terminal, where the ninth piece of information is used to indicate that the terminal supports multi-DRX configuration.

[0219] It should be noted that: The specific processing procedures of the second processor 902 and the second communication interface 901 can be understood with reference to the above method.

[0220] Of course, in actual application, each component in the network device 900 is coupled together through the bus system 904. It can be understood that the bus system 904 is used to realize the connection and communication between these components. The bus system 904 includes not only a data bus, but also a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 9 all kinds of buses are labeled as the bus system 904.

[0221] The second memory 903 in the embodiments of the present application is used to store various types of data to support the operation of the network device 900. Examples of these data include: any computer program for operating on the network device 900.

[0222] The method disclosed in the embodiments of the present application above can be applied to or implemented by the second processor 902. The second processor 902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the second processor 902 or by instructions in the form of software. The above-mentioned second processor 902 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 902 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as being executed and completed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and this storage medium is located in the second memory 903. The second processor 902 reads the information in the second memory 903 and combines its hardware to complete the steps of the foregoing method.

[0223] In an exemplary embodiment, the network device 900 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, Microprocessors, or other electronic components for executing the foregoing method.

[0224] It can be understood that the memories (the first memory 803 and the second memory 903) in the embodiments of the present application can be volatile memories or non-volatile memories, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), an electrically erasable programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), a ferromagnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as a static random access memory (SRAM, Static Random Access Memory), a synchronous static random access memory (SSRAM, Synchronous Static Random Access Memory), a dynamic random access memory (DRAM, Dynamic Random Access Memory), a synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), a double data rate synchronous dynamic random access memory (DDR SDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), an enhanced synchronous dynamic random access memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), a synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and a direct rambus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0225] To implement the method provided by the embodiments of the present application, the embodiments of the present application also provide an information configuration system, as Figure 10 shown, the system includes: a terminal 1001 and a network device 1002.

[0226] Here, it should be noted that: the specific processing procedures of the terminal 1001 and the network device 1002 have been described in detail above and will not be elaborated here.

[0227] In an exemplary embodiment, the embodiments of the present application also provide a storage medium, namely a computer storage medium, specifically a computer-readable storage medium. For example, it includes a first memory 803 storing a computer program, and the above computer program can be executed by a first processor 802 of the terminal 800 to complete the steps of the foregoing method on the terminal side. Another example is a second memory 903 storing a computer program, and the above computer program can be executed by a second processor 902 of the network device 900 to complete the steps of the foregoing method on the network device side. The computer-readable storage medium can be a FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM, etc.

[0228] It should be noted that: "first", "second", etc. are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence.

[0229] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.

[0230] The above is only a preferred embodiment of the present application and is not used to limit the protection scope of the present application.

Claims

1. An information configuration method, characterized in that, applied to a terminal, includes: Receiving configuration information associated with at least one discontinuous reception (DRX), where each DRX in the at least one DRX can support different configuration grants (CGs) or semi-persistent scheduling (SPSs), and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

2. The method according to claim 1, characterized in that, the configuration information includes at least one of the following: First information, which is used to identify a DRX; Second information, which is used to indicate at least one CG supported by the DRX; Third information, which is used to indicate at least one SPS supported by the DRX; Fourth information, which is used to indicate at least one logical channel supported by the DRX; Fifth information, which is used to indicate at least one data radio bearer (DRB) supported by the DRX; Sixth information, which is used to indicate at least one logical channel group supported by the DRX.

3. The method according to claim 1, characterized in that, the configuration information includes: Seventh information, which is used to indicate at least one DRX that a logical channel is allowed to use.

4. The method according to any one of claims 1 to 3, characterized in that, the method further includes: Receiving eighth information, which is used to indicate activating and / or deactivating a DRX in the at least one DRX.

5. The method according to claim 4, characterized in that, activating and / or deactivating the DRX is indicated by means of a bitmap.

6. The method according to any one of claims 1 to 3, characterized in that, the method further includes: Sending ninth information to the network side, where the ninth information is used to indicate that the terminal supports multi-DRX configuration.

7. An information configuration method, characterized in that, applied to a network device, includes: Sending configuration information associated with at least one DRX to a terminal, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

8. The method according to claim 7, characterized in that, the configuration information includes at least one of the following: First information, which is used to identify a DRX; Second information, which is used to indicate at least one CG supported by the DRX; Third information, which is used to indicate at least one SPS supported by the DRX; Fourth information, which is used to indicate at least one logical channel supported by the DRX; Fifth information, which is used to indicate at least one DRB supported by the DRX; Sixth information, which is used to indicate at least one logical channel group supported by the DRX.

9. The method according to claim 7, characterized in that, the configuration information includes: Seventh information, which is used to indicate at least one DRX that a logical channel is allowed to use.

10. The method according to any one of claims 7 to 9, characterized in that, the method further includes: Send an eighth piece of information to the terminal, where the eighth piece of information is used to indicate activation and / or deactivation of DRX in the at least one DRX.

11. The method according to claim 10, wherein, Activation and / or deactivation of DRX is indicated by means of a bitmap.

12. The method according to any one of claims 7 to 9, wherein, The method further includes: Receiving a ninth piece of information sent by the terminal, where the ninth piece of information is used to indicate that the terminal supports multi-DRX configuration.

13. An information configuration device, wherein, It includes: A first receiving unit, configured to receive configuration information associated with at least one DRX, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

14. An information configuration device, wherein, It includes: A first sending unit, configured to send configuration information associated with at least one DRX to a terminal, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

15. A terminal, wherein, It includes: A first processor and a first communication interface; wherein, The first communication interface is configured to receive configuration information associated with at least one DRX, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

16. A network device, wherein, It includes: A second processor and a second communication interface; wherein, The second communication interface is configured to send configuration information associated with at least one DRX to a terminal, where each DRX in the at least one DRX can support different CGs or SPSs, and the configuration parameters of each DRX are associated with the nature of the traffic flow supported by the corresponding CG or SPS.

17. A terminal, wherein, It includes: A first processor and a first memory for storing a computer program that can run on the processor, wherein, when the first processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 6.

18. A network device, wherein, It includes: A second processor and a second memory for storing a computer program that can run on the processor, wherein, when the second processor is used to run the computer program, it executes the steps of the method according to any one of claims 7 to 12.

19. A storage medium, on which a computer program is stored, wherein, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6, or implements the steps of the method according to any one of claims 7 to 12.

Images