Method, apparatus and device for controlling device power consumption, and storage medium
By pre-configuring power consumption policies and their association with network slicing on the terminal device side, the terminal device can autonomously select the corresponding power consumption policies for applications or services, thus solving the power consumption management problem of non-air interface terminal devices and achieving autonomous energy saving.
Patent Information
- Application Number
- CN202111467624.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-02
- Publication Date
- 2026-01-02
- Estimated Expiration
- 2041-12-02
AI Technical Summary
Existing low-power solutions are mainly designed for terminal devices that rely on base stations or wireless air interfaces. They cannot effectively control the power consumption of terminal devices in non-air interface fields, resulting in the inability to effectively manage the power consumption of these devices in the context of rapid development of wireless technology and the increase of smart devices.
By pre-configuring power consumption policies and their association with network slices on the terminal device side, the terminal device can autonomously select the power consumption policy corresponding to the application or service to achieve differentiated power consumption control. This includes receiving device power consumption configuration information, determining the device power consumption policy corresponding to the target application, and exchanging information with network devices.
It enables autonomous power consumption management of terminal devices under different applications or services, reduces device power consumption, and achieves energy saving without relying on network control.
Smart Images

Figure CN115767691B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of communication, and in particular to a device power consumption control method and device, apparatus, and storage medium. BACKGROUND
[0002] The low-power solution of the fifth generation mobile communication technology (5G) is mainly based on the wireless air interface field, and the base station controls the terminal to process different services with low power consumption. The base station can associate different low-power strategies with services based on slices, that is, different services use different low-power processing.
[0003] With the rapid development of wireless technology, the number of intelligent devices is rapidly increasing, and more and more devices have networking capabilities. Among them, the largest proportion is low-power devices. The current low-power solution is not suitable for terminals in non-air interface fields, such as low-power devices that do not depend on base stations or wireless air interfaces. Therefore, it is urgent to design a power consumption control solution for such terminals. SUMMARY
[0004] The embodiments of the present application provide a device power consumption control method, device, apparatus, and storage medium, which reduce device power consumption and achieve the purpose of energy saving.
[0005] The first aspect of the embodiments of the present application provides a device power consumption control method, comprising:
[0006] Receiving device power consumption configuration information, the device power consumption configuration information being used to indicate device power consumption strategies corresponding to different applications;
[0007] Determining a device power consumption strategy corresponding to a target application according to the device power consumption configuration information;
[0008] Performing information interaction with a network device by using the device power consumption strategy corresponding to the target application.
[0009] In an optional embodiment of the first aspect of the present application, the device power consumption configuration information comprises:
[0010] A device power consumption strategy configured for different applications according to a terminal route selection policy (URSP) rule, the URSP rule describing the correspondence between an application and a network slice.
[0011] In an optional embodiment of the first aspect of the present application, the device power consumption strategy configured for different applications according to a terminal route selection policy (URSP) rule comprises:
[0012] A correspondence between a path descriptor describing an application attribute and a device power consumption strategy, the path descriptor comprising an identifier of the application.
[0013] In an optional embodiment of the first aspect of the present application, the determining of the device power consumption strategy corresponding to the target application according to the device power consumption configuration information comprises:
[0014] When the terminal device establishes the network slice corresponding to the target application based on the route descriptor, the device power consumption strategy corresponding to the target application is determined according to the correspondence between the route descriptor and the device power consumption strategy.
[0015] In an optional embodiment of the first aspect of the present application, the device power consumption strategy configured for different applications according to the URSP rule comprises:
[0016] The correspondence between the route descriptor describing the data bearer attribute and the device power consumption strategy comprises the network slice selection assistance information (NSSAI).
[0017] In an optional embodiment of the first aspect of the present application, the determining of the device power consumption strategy corresponding to the target application according to the device power consumption configuration information comprises:
[0018] When the terminal device establishes the network slice corresponding to the target application based on the route descriptor, the device power consumption strategy corresponding to the target application is determined according to the correspondence between the route descriptor and the device power consumption strategy.
[0019] In an optional embodiment of the first aspect of the present application, the information interaction between the network device and the terminal device using the device power consumption strategy corresponding to the target application comprises:
[0020] If the terminal device successfully establishes the network slice corresponding to the target application, the device power consumption strategy corresponding to the target application is activated.
[0021] The information interaction between the network device and the terminal device using the device power consumption strategy corresponding to the target application.
[0022] In an optional embodiment of the first aspect of the present application, the method further comprises:
[0023] If the terminal device deletes the network slice corresponding to the target application, the device power consumption strategy corresponding to the target application is deactivated.
[0024] In an optional embodiment of the first aspect of the present application, the method further comprises:
[0025] If the terminal device performs information interaction with the network device for multiple target applications in the same period, the device power consumption strategy corresponding to each target application is obtained.
[0026] The information interaction of the plurality of target applications with the network device is performed by using the same device power consumption strategy corresponding to the plurality of target applications, or by using all device power consumption strategies corresponding to the plurality of target applications.
[0027] In an optional embodiment of the first aspect of the present application, the device power consumption strategy includes at least one of the following:
[0028] The maximum uplink transmission power of the terminal device;
[0029] The maximum number of uplink transmission antennas of the terminal device;
[0030] The maximum MIMO capability of the terminal device in uplink or downlink;
[0031] Whether the terminal device loads a secondary carrier (SCC);
[0032] The maximum number of SCCs loaded by the terminal device;
[0033] The transmission rate limit of the terminal device.
[0034] The second aspect of the embodiment of the present application provides a device power consumption control apparatus, including:
[0035] A receiving module configured to receive device power consumption configuration information, the device power consumption configuration information being used to indicate device power consumption strategies corresponding to different applications;
[0036] A processing module configured to determine a device power consumption strategy corresponding to a target application according to the device power consumption configuration information;
[0037] The information interaction with the network device is performed by using the device power consumption strategy corresponding to the target application.
[0038] The third aspect of the embodiment of the present application provides an electronic device, including:
[0039] A memory;
[0040] A processor; and
[0041] A computer program;
[0042] The computer program is stored in the memory and is configured to be executed by the processor to implement the method according to any one of the first aspect.
[0043] The fourth aspect of the embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method according to any one of the first aspect.
[0044] The fifth aspect of the embodiments of the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of any one of the first aspect.
[0045] Embodiments of the present application provide a device power consumption control method, device, apparatus and storage medium. The device power consumption control method comprises: receiving device power consumption configuration information, the device power consumption configuration information being used to indicate device power consumption strategies corresponding to different applications; determining a device power consumption strategy corresponding to a target application according to the device power consumption configuration information; and performing information interaction with a network device by using the device power consumption strategy corresponding to the target application. The target application is an application in a terminal device that has information transmission requirements. The above scheme does not need to obtain device power consumption strategies from a network side, and can realize autonomous selection of device power consumption strategies by the terminal device, thereby further reducing device power consumption and realizing energy saving. BRIEF DESCRIPTION OF DRAWINGS
[0046] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative labor.
[0047] Figure 1 The scenario diagram of the device power consumption control method provided by the embodiments of the present application is shown in the following figure.
[0048] Figure 2 The flowchart of the device power consumption control method provided by the embodiments of the present application is shown in the following figure. Figure 1
[0049] Figure 3 The flowchart of the device power consumption control method provided by the embodiments of the present application is shown in the following figure. Figure 2
[0050] Figure 4 The structure diagram of the device power consumption control apparatus provided by the embodiments of the present application is shown in the following figure.
[0051] Figure 5 The hardware structure diagram of the electronic device provided by the embodiments of the present application is shown in the following figure.
[0052] Through the above drawings, the specific embodiments of the present application have been shown, and more detailed descriptions will be given in the following. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application by any means, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0053] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.
[0054] The terms “first”, “second”, and the like in the description of the embodiments of the present application, claims and the above drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be exchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.
[0055] It should be understood that the terms “include” and “have” and any variations thereof used herein are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units need not be limited to those clearly listed steps or units, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.
[0056] In the description of the embodiments of the present application, the term “corresponding” can mean a direct or indirect corresponding relationship between the two, can also mean an associated relationship between the two, or can indicate a relationship with the indicated, configured and configured.
[0057] The fifth generation mobile communication technology 5G is a new generation of wireless communication technology of the 3rd Generation Partnership Project (3GPP), which has the characteristics of high speed, low delay, large capacity, etc. It is being rapidly deployed and applied at home and abroad, especially in the field of enterprises and industries, and 5G is playing an increasingly important role.
[0058] Network slicing is one of the key technologies of 5G, and is the basis for 5G to support multiple service types, such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (uRLLC), and massive machine type communication (mMTC). Network slicing is also the basis for supporting differentiated operation of 5G service experience in the 5G era. Network slicing essentially corresponds to a service, which is a combination of network functions and resources required to complete a service. Network slicing is a logical network with independent resources divided from a physical network to meet different service requirements.
[0059] With the introduction of network slicing technology, operators will be able to provide network capabilities with different features, provide "dedicated" networks for users with different service requirements, and guarantee high-quality service levels to meet differentiated service requirements. Users can also use more exciting application products, further stimulating the development of new industry application blue ocean, and ultimately achieving the goal of improving network resource utilization efficiency, optimizing operator network construction investment, and building a flexible and agile 5G network.
[0060] Currently, a base station of a 5G system can associate different power consumption strategies with services based on network slicing to control terminals to perform corresponding power consumption processing on different services. However, with the advent of the Internet of Everything era, intelligent terminals can not rely on network base stations or wireless air interfaces to configure power consumption strategies for them. For such terminals, the embodiments of the present application provide a device power consumption control method that can be applied to terminals in non-air interface fields or sidelink terminals to achieve their own power consumption control. The main invention idea of the case is as follows: by preconfiguring the association between power consumption strategies and network slices (or applications or services) on the terminal side, the terminal can perform differentiated power consumption processing under different applications or services. This process does not depend on network control, and the terminal can independently select the power consumption strategy corresponding to the application or service, further reducing device power consumption, and achieving the purpose of energy saving.
[0061] It should be noted that the power consumption strategy described in the embodiments generally refers to a low-power consumption strategy.
[0062] Before introducing the device power consumption control method provided by the present application, the application scenario of the method is first briefly introduced.
[0063] Figure 1 The scenario diagram of the device power consumption control method provided by the embodiments of the present application is shown in FIG. 1. Figure 1As shown, the scenario includes a terminal device 11, a terminal device 12 and a communication infrastructure 13. As an example, the terminal device 11 supports application 1, application 2 and application 3, the terminal device 12 supports application 3 and application 4, for example, application 1 and 2 are audio applications, video applications, and application 3 and 4 are non-real-time applications for text transmission. The terminal device 11 can be communicatively connected with the terminal device 12 through the communication infrastructure 13, or can be directly communicatively connected with the terminal device 12.
[0064] In this embodiment, the terminal device can also be referred to as a user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device.
[0065] The terminal device can be a device that provides voice / data connectivity to a user, such as a handheld device with wireless connectivity, a vehicle-mounted device, etc. Currently, some examples of terminals can be: a mobile phone, a pad, a computer with wireless transceiver function (such as a notebook, a palm computer, etc.), a mobile internet device (MID), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN), etc.
[0066] Among them, the wearable device can also be called a wearable smart device, which is a general term for devices that can be worn, such as glasses, gloves, watches, clothing, and shoes, which are designed and developed by applying wearable technology to daily wear. The wearable device is a portable device that can be directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a hardware device, but also a powerful function realized through software support and data interaction, cloud interaction. The general wearable smart device includes functions, large size, and can realize complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, and focuses on a certain application function and needs to cooperate with other devices such as a smart phone, such as various smart bracelets, smart jewelry, and other devices for monitoring vital signs.
[0067] In addition, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network to realize the intelligent network of man-machine interconnection and object-object interconnection. IoT technology can achieve mass connection, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.
[0068] In addition, the terminal device can also include a smart printer, a train detector, a gas station sensor, and the like, and the main functions include collecting data (part of the terminal device), receiving control information and downlink data of the network device, and transmitting electromagnetic waves to transmit uplink data to the network device.
[0069] In this embodiment, the operator deploys three network slices for transmitting audio data, video data, and non-real-time data through the communication infrastructure 13, respectively, which are TR1, TR2, and TR3. As an example, the network slices TR1 and TR2 provide access to the data network platform 14 included in the communication infrastructure 13, and the network slice TR3 provides access to the data network platform 15 not included in the communication infrastructure 13. It should be understood that other network slices can be extended in the figure to supplement the current communication infrastructure according to the needs of the operator.
[0070] Optionally, in some embodiments, the communication infrastructure 13 further includes a rule server 16 for providing rules related to terminal applications or services of the network slice, that is, the terminal route selection policy URSP rule.
[0071] Based on the above scenario, the terminal device 11 and the terminal device 12 can both use the device power consumption control method provided by the embodiments of the present application to independently control the power consumption, without relying on the power consumption control of the network device, to achieve the purpose of reducing the power consumption of the device.
[0072] The technical solutions provided by the embodiments of the present application are described in detail below through specific embodiments. It should be noted that the technical solutions provided by the embodiments of the present application can include part or all of the following content, and the following several specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described again in some embodiments.
[0073] Figure 2 Flowchart of the device power consumption control method provided by the embodiments of the present application Figure 1 The method provided by the embodiments of the present application can be applied to Figure 1 The terminal device 11 or the terminal device 12 shown in FIG. 1. As shown in FIG. 2, the device power consumption control method comprises the following steps. Figure 2 The device power consumption control method comprises the following steps.
[0074] Step 201, receiving device power consumption configuration information, the device power consumption configuration information being used to indicate device power consumption strategies corresponding to different applications.
[0075] In an optional embodiment of the present embodiment, the device power consumption configuration information comprises device power consumption strategies configured for different applications according to a URSP rule. The URSP rule describes the correspondence between the application and the network slice.
[0076] There are two important parameters in the URSP rule:
[0077] One is the traffic descriptor parameter describing the application (app) attribute, which includes the application ID, the data network name (DNN), the IP descriptor, the domain descriptor, the connection capability and other parameters.
[0078] The other is the route selection descriptor describing the data bearer attribute, which includes the network slice (network slice selection assistance information, NSSAI), the session and service continuity mode (SSC Mode), the DNN and other parameters.
[0079] The URSP rule actually includes the correspondence between multiple traffic descriptors and route selection descriptors. It should be understood that when the terminal device learns multiple traffic descriptor parameters related to the application, it can determine the route selection descriptor related to the data bearer according to the URSP rule, which includes the network slice information. In this way, the terminal device can determine which network slice to access the application.
[0080] In an optional embodiment of the embodiment, the device power consumption strategy configured for different applications according to the URSP rule includes configuring the corresponding device power consumption strategy according to the traffic descriptor, i.e., the correspondence between the traffic descriptor describing the application attribute and the device power consumption strategy.
[0081] In an optional embodiment of the embodiment, the device power consumption strategy configured for different applications according to the URSP rule includes configuring the corresponding device power consumption strategy according to the route selection descriptor, i.e., the correspondence between the route selection descriptor and the device power consumption strategy. For example, the correspondence between the NSSAI and the device power consumption strategy.
[0082] It should be noted that the device power consumption configuration information is pre-configuration information, and the related configuration parameters are stored in the storage space of the terminal device.
[0083] Optionally, the device power consumption strategy includes at least one of the following:
[0084] (1) The maximum uplink transmission power of the terminal device.
[0085] For example, the value range is 0-23, and the unit is dbm. The default value is 23 dbm.
[0086] (2) The maximum number of uplink transmission antennas of the terminal device.
[0087] For example, the value range is (1, 2), and the default value is 2.
[0088] (3) The maximum MIMO (multiple input multiple output) capability of the terminal device in uplink or downlink.
[0089] For example, the value range is 1-4, the default value in uplink is 2, and the default value in downlink is 4.
[0090] (4) Whether the terminal device loads SCC (secondary component carrier).
[0091] For example, the default value is to load SCC.
[0092] (5) The maximum number of SCCs loaded by the terminal device.
[0093] For example, the value range is 1-7, and the default value is 7.
[0094] (6) The transmission rate limit of the terminal device.
[0095] For example, the terminal device limits the transmission rate of the application or service corresponding to the network slice, the rate limiting range is 1-2000, the unit is Mbps, and the default is 2000.
[0096] It should be noted that the device power consumption strategy in the above embodiment is only an example and does not constitute a limitation on the technical solutions of the present application. Other possible device power consumption strategies are within the protection scope of the present application.
[0097] As can be seen from the above embodiment, the device power consumption strategy includes configuration of at least one of the above-mentioned parameters. It should be understood that different network slices can be configured with different parameter sets, that is, different applications or services can be configured with different parameter sets.
[0098] Step 202, determining the device power consumption strategy corresponding to the target application according to the device power consumption configuration information.
[0099] In this embodiment, the target application is an application with information transmission requirements in the terminal device.
[0100] In an optional embodiment of this embodiment, the device power consumption configuration information includes the correspondence between the path descriptor describing the application attribute and the device power consumption strategy. When the terminal device establishes the network slice corresponding to the target application based on the path descriptor, the device power consumption strategy corresponding to the target application is determined according to the correspondence between the path descriptor and the device power consumption strategy.
[0101] In an optional embodiment of this embodiment, the device power consumption configuration information includes the correspondence between the routing descriptor describing the data bearer attribute and the device power consumption strategy. When the terminal device establishes the network slice corresponding to the target application based on the routing descriptor, the device power consumption strategy corresponding to the target application is determined according to the correspondence between the routing descriptor and the device power consumption strategy.
[0102] Step 203, performing information interaction with the network device by using the device power consumption strategy corresponding to the target application.
[0103] If the terminal device successfully establishes the network slice corresponding to the target application, the device power consumption strategy corresponding to the target application can be determined through step 202, the device power consumption strategy corresponding to the target application is activated, and information interaction with the network device is performed by using the device power consumption strategy corresponding to the target application.
[0104] In a possible implementation, when the terminal device establishes a network slice corresponding to a target application based on a path descriptor matching a URSP rule, a device power consumption strategy corresponding to a target path descriptor can be determined according to a correspondence between the path descriptor and the device power consumption strategy in the device power consumption configuration information. If a slice pipe corresponding to the target path descriptor is successfully established, the terminal device activates the device power consumption strategy corresponding to the target path descriptor and interacts with the network device. The target path descriptor indicates an identifier of the target application.
[0105] In a possible implementation, when the terminal device establishes a network slice corresponding to a target application based on a path descriptor matching a URSP rule, a device power consumption strategy corresponding to a target path descriptor can be determined according to a correspondence between the path descriptor and the device power consumption strategy in the device power consumption configuration information. If a slice pipe corresponding to the target path descriptor is successfully established, the terminal device activates the device power consumption strategy corresponding to the target path descriptor and interacts with the network device. The target path descriptor indicates an identifier of the target application.
[0106] Optionally, in some embodiments, if the terminal device deletes a network slice corresponding to a target application, the terminal device deactivates the device power consumption strategy corresponding to the target application.
[0107] Optionally, in some embodiments, the terminal device interacts with other terminal devices using the device power consumption strategy corresponding to the target application. For example, Figure 1 The terminal device 11 shown in FIG. 1 interacts with other terminal devices using the device power consumption strategy corresponding to the target application determined in step 202. Figure 1 The terminal device 12 shown in FIG. 1 interacts with other terminal devices using the device power consumption strategy corresponding to the target application determined in step 202.
[0108] It should be noted that the application in the above embodiments can also be replaced by a service, and the device power consumption configuration information can be used to indicate device power consumption strategies corresponding to different services.
[0109] The device power consumption control method shown in the embodiments of the present application receives device power consumption configuration information, the device power consumption configuration information is used to indicate device power consumption strategies corresponding to different applications, determines a device power consumption strategy corresponding to a target application according to the device power consumption configuration information, and then interacts with a network device using the device power consumption strategy corresponding to the target application. The target application is an application in the terminal device that has a demand for information transmission. The above solution does not need to obtain a device power consumption strategy from the network side, realizes autonomous selection of a device power consumption strategy by the terminal device, can further reduce device power consumption, and realizes energy saving.
[0110] Figure 3 The device power consumption control method provided in the embodiments of the present application is shown in the flowchart Figure 2 The device power consumption control method provided in the embodiments of the present application is shown in the flowchart Figure 3 The device power consumption control method provided in the embodiments of the present application is shown in the flowchart Figure 4As shown, the device power consumption control method of the embodiment further includes:
[0111] In step 301, if the terminal device performs information interaction with the network device for multiple target applications in the same time period, the device power consumption strategy corresponding to each target application is acquired.
[0112] In step 302, the same device power consumption strategy corresponding to the multiple target applications is used to perform information interaction with the network device for the multiple target applications. Alternatively,
[0113] In step 303, all device power consumption strategies corresponding to the multiple target applications are used to perform information interaction with the network device for the multiple target applications.
[0114] It should be understood that the same device power consumption strategy corresponding to the multiple target applications in step 302 can be understood as the intersection of the device power consumption strategies corresponding to the multiple target applications. All device power consumption strategies corresponding to the multiple target applications in step 303 can be understood as the union of the device power consumption strategies corresponding to the multiple target applications.
[0115] In an optional embodiment of the embodiment, if the terminal device successfully establishes multiple network slices based on the path descriptor, the terminal device acquires the device power consumption strategy corresponding to each target path descriptor, takes the intersection of the device power consumption strategies corresponding to the multiple target path descriptors, and activates the corresponding device power consumption strategy. The target path descriptor indicates the identifier of the target application.
[0116] In an optional embodiment of the embodiment, if the terminal device successfully establishes multiple network slices based on the path descriptor, the terminal device acquires the device power consumption strategy corresponding to each target path descriptor, takes the union of the device power consumption strategies corresponding to the multiple target path descriptors, and activates the corresponding device power consumption strategy.
[0117] In an optional embodiment of the embodiment, if the terminal device successfully establishes multiple network slices based on the NSSAI, the terminal device acquires the device power consumption strategy corresponding to each target NSSAI, takes the intersection of the device power consumption strategies corresponding to the multiple target NSSAIs, and activates the corresponding device power consumption strategy. The target NSSAI corresponds to the identifier of the target application.
[0118] In an optional embodiment of the embodiment, if the terminal device successfully establishes multiple network slices based on the NSSAI, the terminal device acquires the device power consumption strategy corresponding to each target NSSAI, takes the union of the device power consumption strategies corresponding to the multiple target NSSAIs, and activates the corresponding device power consumption strategy.
[0119] For example, the terminal device successfully establishes multiple network slices, such as TR1, TR1 and TR3, which correspond to application 1, application 2 and application 3 respectively, wherein the device power consumption policy corresponding to TR1 is policy 1 and policy 2, the device power consumption policy corresponding to TR2 is policy 2, and the device power consumption policy corresponding to TR3 is policy 2 and policy 3. For example, policy 1 is that the maximum uplink transmission power is 23dbm, policy 2 is that the maximum number of uplink transmission antennas is 2, and policy 3 is to load SCC.
[0120] In a possible implementation, the intersection of the device power consumption policies corresponding to the three network slices is taken, for example, policy 2 is used to interact with the network device for application 1, 2 and 3.
[0121] In a possible implementation, the union of the device power consumption policies corresponding to the three network slices is taken, for example, policies 1, 2 and 3 are used to interact with the network device for application 1, 2 and 3.
[0122] In an optional embodiment of the embodiment, if the terminal device deletes one or more network slices in the multiple network slices, the terminal device deactivates the device power consumption policy that is not needed. For the device power consumption policy corresponding to the network slice still existing, the intersection or union is taken, and the device power consumption policy not in the intersection or union is deactivated.
[0123] The device power consumption control method shown in the embodiment of the present application is used when the terminal device simultaneously establishes multiple network slices. The terminal device obtains the device power consumption policy corresponding to the multiple network slices (or the device power consumption policy corresponding to the target application of the multiple network slices) according to the device power consumption configuration information, and interacts with the network device for multiple target applications according to the intersection or union of the device power consumption policies corresponding to the multiple network slices. The above scheme does not need to obtain the device power consumption policy from the network side, realizes the self-selection of the device power consumption policy by the terminal device, can further reduce the device power consumption, and realizes energy saving.
[0124] The device power consumption control method provided by the embodiment of the present application is described above, and the device power consumption control device provided by the embodiment of the present application will be described below.
[0125] The device power consumption control device can be divided into functional modules according to the method embodiment described above, for example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The integrated module can be realized in the form of hardware or in the form of a software functional module.
[0126] It should be noted that the division of the modules in the embodiments of the present application is illustrative, and is only a logical function division. Actual implementation can have another division manner. The following will be described by taking the division of each functional module corresponding to each function as an example.
[0127] Figure 4 The structure diagram of the device power consumption control device provided in the embodiments of the present application is shown in FIG. 4. As shown in FIG. 4, the device power consumption control device 400 provided in the embodiments of the present application includes a receiving module 401 and a processing module 402. Figure 5
[0128] The receiving module 401 is configured to receive device power consumption configuration information, wherein the device power consumption configuration information is used to indicate a device power consumption strategy corresponding to a target application.
[0129] The processing module 402 is configured to determine the device power consumption strategy corresponding to the target application according to the device power consumption configuration information.
[0130] The device power consumption control device 400 is configured to perform information interaction with a network device by using the device power consumption strategy corresponding to the target application.
[0131] In an optional embodiment of the present application, the device power consumption configuration information includes:
[0132] A device power consumption strategy configured for different applications according to a terminal route selection policy (URSP) rule, wherein the URSP rule describes a corresponding relationship between an application and a network slice.
[0133] In an optional embodiment of the present application, the device power consumption strategy configured for different applications according to the terminal route selection policy (URSP) rule includes:
[0134] A corresponding relationship between a path descriptor describing an application attribute and a device power consumption strategy, wherein the path descriptor includes an identifier of the application.
[0135] In an optional embodiment of the present application, the processing module 402 is configured to:
[0136] When the terminal device establishes a network slice corresponding to the target application based on the path descriptor, determine the device power consumption strategy corresponding to the target application according to the corresponding relationship between the path descriptor and the device power consumption strategy.
[0137] In an optional embodiment of the present application, the device power consumption strategy configured for different applications according to the terminal route selection policy (URSP) rule includes:
[0138] A corresponding relationship between a route selection descriptor describing a data bearer attribute and a device power consumption strategy, wherein the route selection descriptor includes network slice selection assistance information (NSSAI).
[0139] In an optional embodiment of the present embodiment, the processing module 402 is configured to:
[0140] When the terminal device establishes the network slice corresponding to the target application based on the routing descriptor, the device power consumption policy corresponding to the target application is determined according to the correspondence between the routing descriptor and the device power consumption policy.
[0141] In an optional embodiment of the present embodiment, the processing module 402 is configured to:
[0142] If the terminal device successfully establishes the network slice corresponding to the target application, the device power consumption policy corresponding to the target application is activated;
[0143] The terminal device performs information interaction with the network device by using the device power consumption policy corresponding to the target application.
[0144] In an optional embodiment of the present embodiment, the processing module 402 is configured to:
[0145] If the terminal device deletes the network slice corresponding to the target application, the device power consumption policy corresponding to the target application is deactivated.
[0146] In an optional embodiment of the present embodiment, the processing module 402 is configured to:
[0147] If the terminal device performs information interaction with the network device for multiple target applications in the same time period, the device power consumption policy corresponding to each target application is obtained;
[0148] The terminal device performs information interaction with the network device for the multiple target applications by using the same device power consumption policy corresponding to the multiple target applications, or by using all the device power consumption policies corresponding to the multiple target applications.
[0149] In an optional embodiment of the present embodiment, the device power consumption policy comprises at least one of the following:
[0150] The maximum uplink transmission power of the terminal device;
[0151] The maximum number of uplink transmission antennas of the terminal device;
[0152] The maximum MIMO capability of the terminal device in uplink or downlink;
[0153] Whether the terminal device loads a secondary carrier (SCC);
[0154] The maximum number of SCCs loaded by the terminal device;
[0155] The transmission rate limit of the terminal device.
[0156] The device power consumption control apparatus provided by the embodiment can implement the technical solutions of any of the method embodiments, and has similar implementation principles and technical effects, which will not be repeated here.
[0157] Figure 5 A hardware structure diagram of an electronic device provided by the embodiment is shown in FIG. 5. As shown in FIG. 5, the electronic device 500 provided by the embodiment includes:
[0158] a memory 501;
[0159] a processor 502; and
[0160] a computer program;
[0161] The computer program is stored in the memory 501 and is configured to be executed by the processor 502 to implement the technical solutions of any of the method embodiments, and has similar implementation principles and technical effects, which will not be repeated here.
[0162] Optionally, the memory 501 can be independent or integrated with the processor 502. When the memory 501 is independent of the processor 502, the electronic device 500 further includes a bus 503 for connecting the memory 501 and the processor 502.
[0163] The embodiment of the application further provides a computer readable storage medium having a computer program stored thereon, and the computer program is executed by the processor 502 to implement the technical solutions of any of the method embodiments.
[0164] The embodiment of the application provides a computer program product including a computer program, and the computer program is executed by the processor to implement the technical solutions of any of the method embodiments.
[0165] The embodiment of the application further provides a chip including a processing module and a communication interface, and the processing module can execute the technical solutions of any of the method embodiments.
[0166] Further, the chip further includes a storage module (such as a memory), and the storage module is used for storing instructions, the processing module is used for executing the instructions stored in the storage module, and the execution of the instructions stored in the storage module causes the processing module to execute the technical solutions of any of the method embodiments.
[0167] It should be appreciated that the above processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in combination with the application can be directly embodied as hardware processor execution, or executed by a combination of hardware and software modules in the processor.
[0168] The memory can include a high-speed RAM memory, and can also include a non-volatile storage NVM, such as at least one disk memory, and can also be a U disk, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.
[0169] The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, the bus in the drawings of the present application does not limit to only one bus or one type of bus.
[0170] The above storage medium can be realized by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.
[0171] An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium, and can write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in the electronic device.
[0172] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit the present application; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions recorded in the foregoing embodiments can still be modified, or some or all of the technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A method of controlling power consumption of a device, the method comprising: The method is applied to a terminal device, and comprises the following steps: receiving device power consumption configuration information, wherein the device power consumption configuration information is used to indicate device power consumption strategies corresponding to different applications, and the device power consumption configuration information comprises device power consumption strategies configured for different applications according to a terminal route selection policy (URSP) rule, wherein the URSP rule describes a corresponding relationship between an application and a network slice; when the terminal device successfully establishes a network slice corresponding to a target application based on the URSP rule, determining a device power consumption strategy corresponding to the target application according to the device power consumption configuration information; activating the device power consumption strategy corresponding to the target application, and performing information interaction with a network device by using the device power consumption strategy corresponding to the target application, wherein the activation and use of the device power consumption strategy are both performed by the terminal device autonomously.
2. The method of claim 1, wherein, The device power consumption strategies configured for different applications according to the URSP rule comprise the following steps: describing a corresponding relationship between a path descriptor describing an application attribute and a device power consumption strategy, wherein the path descriptor comprises an identifier of the application.
3. The method of claim 2, wherein, The step of determining a device power consumption strategy corresponding to a target application according to the device power consumption configuration information comprises the following steps: when the terminal device establishes a network slice corresponding to the target application based on the path descriptor, determining the device power consumption strategy corresponding to the target application according to the corresponding relationship between the path descriptor and the device power consumption strategy.
4. The method of claim 1, wherein, The device power consumption strategies configured for different applications according to the URSP rule comprise the following steps: describing a corresponding relationship between a route selection descriptor describing a data bearer attribute and a device power consumption strategy, wherein the route selection descriptor comprises network slice selection assistance information (NSSAI).
5. The method of claim 4, wherein, The step of determining a device power consumption strategy corresponding to a target application according to the device power consumption configuration information comprises the following steps: when the terminal device establishes a network slice corresponding to the target application based on the route selection descriptor, determining the device power consumption strategy corresponding to the target application according to the corresponding relationship between the route selection descriptor and the device power consumption strategy.
6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises the following steps: if the terminal device deletes the network slice corresponding to the target application, deactivating the device power consumption strategy corresponding to the target application.
7. The method according to any one of claims 1 to 5, characterized in that, The method further comprises the following steps: if the terminal device performs information interaction with the network device for multiple target applications in the same period, obtaining device power consumption strategies corresponding to each target application; performing information interaction with the network device for the multiple target applications by using the same device power consumption strategy corresponding to the multiple target applications, or by using all the device power consumption strategies corresponding to the multiple target applications.
8. The method according to any one of claims 1 to 5, characterized in that, The device power consumption strategy comprises at least one of the following: a maximum uplink transmission power of the terminal device; a maximum number of uplink transmission antennas of the terminal device; a maximum MIMO capability of the terminal device in uplink or downlink; whether the terminal device loads a secondary carrier (SCC); a maximum number of SCCs loaded by the terminal device; a transmission rate limit of the terminal device.
9. An apparatus for controlling power consumption, comprising: The method comprises the following steps: The receiving module is configured to receive device power consumption configuration information, wherein the device power consumption configuration information is used to indicate device power consumption strategies corresponding to different applications, and the device power consumption configuration information comprises device power consumption strategies configured for different applications according to a terminal route selection policy (URSP) rule, and the URSP rule describes a correspondence between an application and a network slice; The processing module is configured to determine a device power consumption strategy corresponding to a target application according to the device power consumption configuration information when the terminal device successfully establishes a network slice corresponding to the target application based on the URSP rule; The device power consumption strategy corresponding to the target application is activated, and the device power consumption strategy corresponding to the target application is used for information interaction with a network device, and the activation and use of the device power consumption strategy are both performed by the terminal device autonomously.
10. An electronic device, comprising: comprise: a memory; a processor; and a computer program; wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method according to any one of claims 1-8. a computer program is stored on the computer readable medium, and the computer program is executed by a processor to implement the method according to any one of claims 1-8.
11. A computer readable storage medium, characterized in that, a computer program is stored on the computer readable medium, and the computer program is executed by a processor to implement the method according to any one of claims 1-8.
12. A computer program product, characterised in that,
Citation Information
Patent Citations
Method and device for controlling power consumption
CN106774786A
Method for adjusting accessed network slice, communication equipment, network equipment and system
CN113498086A