A method for dynamically applying battery-saving technology, and the terminals and network devices that implement this method.

Abstract

A method for dynamically applying battery power saving technology by a terminal is disclosed. The method includes the following steps: sending a first message to an authentication server requesting activation of the dynamic battery power saving technology service; receiving a second message from the authentication server as a response to the first message; when the response information included in the second message includes successful authentication and running at least one application included in the second message, sending data to and receiving data from a base station in a battery power saving technology disabled state; and maintaining the battery power saving technology activated state when the application included in the second message is not running.

Description

Technical Field

[0001] This invention relates to a battery energy-saving technology. Background Technology

[0002] In RRC connection mode, the terminal checks the received data by monitoring the Physical Downlink Control Channel (PDCCH) for each subframe. If PDCCH monitoring continues even when no data is being sent / received, battery consumption increases. To address this issue, Connected-Mode Discontinuous Receive (C-DRX) technology was introduced.

[0003] C-DRX technology is a technique that repeats the following cycle: when no data is being sent / received, the terminal switches its communication function to sleep mode and then wakes up after a certain period of time, instead of continuously activating the communication function in RRC connection mode. Because the PDCCH is not monitored in sleep mode (low power mode), C-DRX technology is used as a battery-saving technology to reduce battery consumption through network technology.

[0004] However, due to C-DRX technology, communication functions may be in a sleep state where they are disabled when immediate data transmission and reception are required. The drawback is a predetermined delay (e.g., 10ms to 20ms) before data transmission and reception. For example, if a user needs to immediately purchase an item while playing a game on a device, and 5G / LTE communication is switched to sleep mode via C-DRX, the purchase cannot be made until the communication function is activated. Therefore, using continuous C-DRX technology may cause some problems in 5G communication services that offer various ultra-low latency services. Summary of the Invention

[0005] Technical issues

[0006] This invention provides a method for dynamically applying battery energy-saving technology according to the application.

[0007] This invention provides a method for activating or deactivating battery power-saving technology based on the application's delay sensitivity.

[0008] Technical solution

[0009] According to an embodiment, a method for dynamically applying battery power saving technology by a terminal is provided. The method includes the following steps: sending a first message to an authentication server requesting activation of a dynamic battery power saving technology service; receiving a second message from the authentication server as a response to the first message; when the response information included in the second message includes successful authentication and running at least one application included in the second message, sending data to and receiving data from a base station in a battery power saving technology disabled state; and maintaining a battery power saving technology activated state when the application included in the second message is not running.

[0010] The second message may include a list of applications that do not apply the battery-saving technology and a first access point name (APN) used to access the network when an application included in the application list is executed.

[0011] The steps of sending data to the base station and receiving data from the base station in the battery power saving technology disabled state may include: when an application included in the application list is executed in the battery power saving technology activated state, accessing the base station using the first APN, receiving a request from the base station to release the battery power saving technology, and switching the battery power saving technology activated state to the battery power saving technology disabled state.

[0012] The steps to maintain the battery power saving technology in an active state may include: when the execution of the application included in the application list is terminated, releasing the bearer connected through the first APN, receiving a request from the base station to establish the battery power saving technology, and switching the battery power saving technology in a deactivated state to the battery power saving technology in an active state.

[0013] The method for dynamically applying the battery power saving technology may further include the following steps: when an application not included in the application list is executed in the battery power saving technology activation state, accessing the base station using a second APN different from the first APN.

[0014] The application included in the second message may be a low-latency service application.

[0015] The method for dynamically applying the battery power saving technology may further include the following steps: sending a third message to the authentication server periodically requesting a status check for the dynamic service of the battery power saving technology based on a status query time; receiving a fourth message as a response to the third message from the authentication server; and maintaining the dynamic service of the battery power saving technology in an active state when the response information included in the fourth message includes successful authentication. Here, the second message may further include a status query time.

[0016] The method for dynamically applying the battery power saving technology may further include the following steps: sending a fifth message to the authentication server requesting the deactivation of the dynamic service of the battery power saving technology; receiving a sixth message from the authentication server as a response to the fifth message; and setting the dynamic service of the battery power saving technology to a deactivated state when the response information included in the sixth message includes "deactivation successful".

[0017] According to another embodiment, a method for dynamically applying battery-saving technology by a terminal is provided. The method includes the following steps: storing a list of applications that do not apply C-DRX and transmit and receive data in a Connectivity Discontinuous Reception (C-DRX) disabled state (C-DRX off); setting the C-DRX state to the C-DRX disabled state (C-DRX off) when at least one application included in the list of applications that do not apply C-DRX is executed; and setting the C-DRX state to the C-DRX active state (C-DRX on) when none of the applications included in the list of applications that do not apply C-DRX are executed.

[0018] The application that does not apply C-DRX can be a low-latency service application, and the list of applications that do not apply C-DRX can be received from the authentication server.

[0019] Applications included in the list of applications that do not apply C-DRX can access the base station using the first APN, and applications not included in the list of applications that do not apply C-DRX can access the base station using the second APN.

[0020] The first APN may be received from the authentication server.

[0021] The step of setting the C-DRX state to the C-DRX disabled state (C-DRX off) may include: when executing an application that does not apply C-DRX and is included in the list of applications that do not apply C-DRX, accessing the base station using the first APN, receiving a C-DRX release request from the base station, and switching the C-DRX state to the C-DRX disabled state.

[0022] The step of setting the C-DRX state to the C-DRX active state (C-DRX enabled) may include: when an application that is not using C-DRX is terminated, releasing the bearer connected through the first APN, receiving a C-DRX establishment request from the base station, and switching the C-DRX disabled state to the C-DRX active state.

[0023] According to an embodiment, a method for dynamically applying battery-saving technology by an authentication server is provided. The method includes the following steps: receiving a first message from a terminal requesting activation of a dynamic battery-saving technology service; and sending a second message to the terminal as a response to the first message. The second message may include a list of applications for which the battery-saving technology is not applied, and a first Access Point Name (APN) used for network access when an application included in the application list is executed. The first APN is a different APN from a second APN used for network access when an application not included in the application list is executed.

[0024] The method for dynamically applying the battery power saving technology may further include the following steps: receiving a third message from the terminal periodically requesting a status check of the dynamic battery power saving technology service, and sending a fourth message to the terminal as a response to the third message. When the fourth message includes successful authentication, the terminal can keep the dynamic battery power saving technology service active.

[0025] The method for dynamically applying the battery power saving technology may further include the following steps: receiving a fifth message from the terminal requesting the deactivation of the dynamic battery power saving technology service, and sending a sixth message to the terminal as a response to the fifth message. When the sixth message includes "deactivation successful," the terminal may set the dynamic battery power saving technology service to a deactivated state.

[0026] A method for dynamically applying battery-powered technologies by a base station is provided. The method includes the following steps: receiving a request from a terminal to access the network using a first APN; sending a C-DRX establishment request including C-DRX parameters to the terminal, and sending and receiving data from the terminal while the C-DRX is active; receiving a request from the terminal to access the network using a second APN; and sending a C-DRX release request to the terminal, and sending and receiving data from the terminal while the C-DRX is deactivated.

[0027] The method for dynamically applying the battery power saving technology may further include the following steps: receiving a request from the terminal to release the bearer connected through the second APN, and sending a C-DRX establishment request including C-DRX parameters to the terminal.

[0028] The second APN can be an APN assigned to an application that does not apply C-DRX.

[0029] Beneficial effects

[0030] According to the present invention, by activating or deactivating C-DRX according to the latency sensitivity of the application, battery consumption can be reduced while providing ultra-low latency service. Attached Figure Description

[0031] Figure 1 This is a diagram illustrating Connected-Mode Discontinuous Reception (C-DRX) technology.

[0032] Figure 2 This is a schematic illustration of a communication system according to an embodiment.

[0033] Figure 3 This is a flowchart illustrating a method for activating C-DRX dynamic services according to an implementation method.

[0034] Figure 4 This is a flowchart illustrating a method for checking the dynamic service status of C-DRX according to an implementation method.

[0035] Figure 5 This is a flowchart illustrating a method for disabling C-DRX dynamic services according to an implementation method.

[0036] Figure 6 This is a flowchart illustrating a method for activating / deactivating C-DRX dynamic services according to an implementation method.

[0037] Figure 7 This is a flowchart of the C-DRX dynamic service method according to the implementation method.

[0038] Figure 8 This is a flowchart illustrating a method for switching between C-DRX activation / deactivation states according to an implementation of an application. Detailed Implementation

[0039] In the following detailed description, specific embodiments of the invention are shown and described by way of illustration only. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the spirit or scope of the invention. Therefore, the drawings and description should be considered illustrative in nature and not restrictive. Throughout the description, the same reference numerals denote the same elements.

[0040] Throughout this specification, when a component is referred to as "comprising" a particular constituent element, unless otherwise specifically stated, it means that it may include other constituent elements rather than excluding them. In this specification, terms such as "...unit," "...device / component," "...module," etc., refer to a unit that can be implemented in hardware, software, or a combination thereof to perform at least one function or operation.

[0041] A terminal refers to a user terminal that communicates with a remote server via a 3G / LTE / 5G communication network. The following will describe terminal access to LTE / 5G communication networks. Terminals can be mobile terminals of various types and purposes, such as portable terminals, IoT terminals, vehicle terminals, display terminals, broadcast terminals, and gaming terminals.

[0042] The terminal accesses the access network / radio access network (RAN) via a communication network interface. In this specification, it is assumed that the terminal accesses a base station (eNB / gNB) of the access network. The terminal accessing the RAN connects to the core network. The core network will be described below primarily with respect to the devices / functions relevant to this invention.

[0043] Figure 1 This is a diagram illustrating Connected-Mode Discontinuous Reception (C-DRX) technology.

[0044] Reference Figure 1 In (a), when C-DRX technology is not applied, the communication function is continuously activated in the RRC connection state. Therefore, battery consumption increases because the terminal monitors and checks the received data via PDCCH.

[0045] Reference Figure 1 (b) When C-DRX technology is applied, the terminal repeats the following cycle: in this cycle, when there is no data to be sent / received in the RRC connection state, the terminal switches the communication function to sleep mode, wakes up after a specific period of time, and then monitors the PDCCH. Therefore, since the terminal does not monitor the PDCCH in sleep mode (low power mode), battery consumption can be reduced.

[0046] The following describes a method for dynamically applying battery-saving technologies according to the application. In this specification, Connected Mode Discontinuous Reception (C-DRX) technology is referred to as a battery-saving technology. However, the battery-saving technologies to which this invention applies are not limited to C-DRX. This invention can be used with technologies improved from C-DRX or with technologies of different types than C-DRX.

[0047] In the manual, C-DRX dynamic service refers to the service in which the terminal's C-DRX status is dynamically activated (C-DRX enabled) or deactivated (C-DRX disabled) depending on the application being executed.

[0048] Figure 2 This is a schematic illustration of a communication system according to an embodiment.

[0049] Reference Figure 2Terminal 100 uses communication services via network equipment. Specifically, terminal 100 accesses the base station (gNB / eNB) 200 of the access network / radio access network (RAN). The core network includes Access and Mobility Management Functions (AMF) / Mobility Management Entity (MME) 210, User Plane Functions (USF) / P-GW 230, Policy Control Functions (PCF) (250), and Authentication Server 300. The 5G core network also includes Session Management Functions (SMF), Network Openness Functions (NEF), Application Functions (AF), etc. Detailed descriptions of these will be omitted. For reference, in Figure 2 In the documentation, UPF is described as a network function of the 5G core network corresponding to P-GW 230. However, in... Figure 7 In this context, SMF can be described as a network function of the 5G core network corresponding to P-GW 230. Terminal 100 can support multiple Access Point Names (APNs).

[0050] Terminal 100 is equipped with service applications that provide various content (e.g., video service applications, game service applications, etc.). Furthermore, terminal 100 is equipped with a management application (hereinafter referred to as the "C-DRX management application") 110 for dynamically applying battery-saving technologies according to the executed service applications. Among the service applications, those designated to send and receive data in a C-DRX-activated state (C-DRX enabled) are called general service applications or C-DRX-enabled applications, and those designated to send and receive data in a C-DRX-disabled state (C-DRX disabled) are called low-latency service applications or non-C-DRX-enabled applications. The C-DRX management application 110 may have various interactive interfaces required for performing the operations of this invention.

[0051] When the C-DRX management application 110 requests activation of the C-DRX dynamic service, the terminal 100 sends a C-DRX dynamic service activation request message to the authentication server 300 and receives a response message based on the authentication result. If authentication is successful, the terminal 100 can use the C-DRX dynamic service, which dynamically applies C-DRX according to the application. Even after the C-DRX dynamic service has been successfully authenticated, the terminal 100 can periodically request authentication status from the authentication server 300 and then receive authentication status responses. Furthermore, when the C-DRX management application 110 requests deactivation of the C-DRX dynamic service, the terminal 100 sends a C-DRX dynamic service deactivation request message to the authentication server 300, and can then choose not to use the C-DRX dynamic service.

[0052] First, when a general service application is executed in terminal 100, terminal 100 accesses base station 200 using the general APN. Then, base station 200 sends a C-DRX establishment request, including C-DRX parameters, to terminal 100 that accessed via the general APN, and terminal 100, upon receiving the C-DRX establishment request, sends and receives data in a C-DRX active state (C-DRX enabled).

[0053] When a low-latency service application is executed in terminal 100, terminal 100 accesses base station 200 using the APN assigned to the low-latency service application (hereinafter referred to as the "low-latency APN"). Then, base station 200 sends a C-DRX release request to terminal 100 accessing via the low-latency APN, and terminal 100 receiving the C-DRX release request immediately transitions to a C-DRX disabled state (C-DRX off). As a result, the low-latency service application can send and receive data in the C-DRX disabled state (C-DRX off). Subsequently, when the executed low-latency service application is terminated, terminal 100 releases the bearer connected to the low-latency APN. Then, base station 200 sends a C-DRX establishment request including C-DRX parameters to terminal 100, and terminal 100 transitions to a C-DRX active state (C-DRX enabled).

[0054] As described above, terminal 100 accesses base station 200 using an APN classified according to application. Base station 200 sends a C-DRX establishment request or C-DRX release request to terminal 100 based on the APN used for terminal 100 access. For this purpose, terminal 100 manages the low-latency service application list and low-latency APNs. The low-latency service application list and low-latency APNs can be received from the authentication server (300). Authentication server 300 can send a response including the low-latency service application list and low-latency APNs as a C-DRX dynamic service activation request. The low-latency service application list can be sent in detail using RESTful JSON as HTTP.

[0055] Furthermore, without interacting with the authentication server 300, the terminal 100 can manage the list of low-latency service applications and the low-latency APN, and provide dynamic C-DRX services while switching between C-DRX active state (C-DRX enabled) and C-DRX disabled state (C-DRX disabled) depending on the application being executed. This description primarily focuses on dynamic C-DRX services based on interaction between the terminal 100 and the authentication server 300; however, dynamic C-DRX services can be provided without such interaction.

[0056] Terminal 100's C-DRX management application 110 and authentication server 300 can interact using a specified interaction protocol (e.g., HTTPS) and a specified TCP port (e.g., 8887). The data format can be, for example, JSON. The HTTP POST request method is used as the interaction method, and an HTTP URI can be used. The interaction data consists of an HTTP header and an HTTP content area, and the header and content can be separated by newline characters (carriage return / line feed, CRLF). The attributes of the content area can be represented by the content type field included in the HTTP header. The length of the content object can be defined by the content length field, which includes CRLF characters, and consecutive CRLF characters can be inserted at the end of the content data.

[0057] The C-DRX management application 110 of terminal 100 can send HTTP request packets to authentication server 300, including, for example, the information in Table 1.

[0058] [Table 1]

[0059]

[0060] The authentication server 300 can send HTTP response packets, including information from Table 2, to the C-DRX management application 110 of the terminal 100.

[0061] [Table 2]

[0062]

[0063] In the following description, a method will be described in which the C-DRX management application 110 of terminal 100 activates or deactivates the C-DRX dynamic service by interacting with the authentication server 300, and periodically checks the authentication status while the C-DRX dynamic service is activated. In this specification, terminal 100 or C-DRX management application 110 will be interchangeably described as the entity performing the operation.

[0064] Figure 3 This is a flowchart illustrating a method for activating C-DRX dynamic services according to an implementation method. (Refer to...) Figure 3 When a C-DRX dynamic service activation request (C-DRX dynamic service activation and establishment) is entered in the C-DRX management application 110, the terminal 100 sends a DNS query request message requesting the authentication server address to the domain name server (not shown) (S110).

[0065] Terminal 100 receives a DNS query response message from a domain name server, which includes the address of the authentication server (S120). The DNS query response message may include multiple authentication server addresses, such as IPv4 addresses or IPv6 addresses.

[0066] Terminal 100 sends a C-DRX dynamic service activation request message to the address of authentication server 300 included in the DNS query response message (S130). When the DNS query response message includes multiple authentication server addresses, terminal 100 can select one authentication server address. Terminal 100 can send an activation request message written in HTTPS JSON format to authentication server 300. Terminal 100 connects to authentication server 300 via a specified TCP connection port.

[0067] The authentication server 300 generates response information based on the subscriber information and service availability status of the terminal 100, and sends a response message (C-DRX Dynamic Service Activation Response) including the response information to the terminal 100 (S140). The response information includes the authentication result. The authentication result may include a value selected from the response code. If authentication is successful, the response information may include a list of low-latency service applications and a low-latency APN assigned to the low-latency service application. The list of low-latency service applications may include at least one low-latency service application.

[0068] Terminal 100 determines whether the authentication result included in the response message is successful (S150).

[0069] If the authentication result included in the response message is successful, terminal 100 sets the C-DRX dynamic service to an active state (enabled state) and stores the low-latency service application list and low-latency APN included in the response message (S160). Furthermore, when executing a low-latency service application, terminal 100 can access base station 200 using the low-latency APN. Then, upon receiving a C-DRX release request, terminal 100 can switch to a C-DRX disabled state (C-DRX off).

[0070] If the authentication result included in the response message is a failure, terminal 100 can set the C-DRX dynamic service to a disabled state (off state) and notify the authentication failure by displaying a failure message on the screen (S170). Terminal 100 can check the response code of the response message and display a notification message corresponding to the response code using a UI toast.

[0071] Variables included in the C-DRX dynamic service activation request message can be defined as shown in Table 3, and the message format can be as shown in Table 4. The C-DRX dynamic service activation request message can also include a request URL. In Table 4, " / / " can represent a newline character (CRLF).

[0072] [Table 3]

[0073]

[0074]

[0075] [Table 4]

[0076]

[0077] The variables included in the C-DRX dynamic service activation response message can be defined as shown in Table 5. The response codes in the response variables can include codes corresponding to successful or failed authentication. When authentication fails, a code can be assigned based on the reason for the failure. Response codes can be defined as shown in Table 6. When the authentication result is a failure, terminal 100 can use a UI toast to display a notification message corresponding to the response code.

[0078] [Table 5]

[0079]

[0080] [Table 6]

[0081]

[0082]

[0083] The format of the C-DRX dynamic service activation response message can be shown in Table 7.

[0084] [Table 7]

[0085]

[0086]

[0087] Referring to Table 7, when the response code is 200, indicating successful authentication, terminal 100 can access the communication network using the low-latency APN "APNName = abc.private.5g.com" and send services with the low-latency service application "PackageName = com.kt.game1". When connecting to the 5G / LTE network, if the UPF / P-GW requests the transmission of PCO ID / PW, as shown in Table 7, terminal 100 can use the authentication type "PcoAuthType = PAP" included in the HTTP response message and can send a PDN connection request to the UPF / P-GW including the PCO values ​​"PcoID" and "PcoPassword". Here, terminal 100 may mistakenly send the PCO value, or may receive a PDN connection response from the 5G / LTE UPF / PGW indicating PDN rejection for other reasons. Then, terminal 100 can attempt to reconnect to the PDN. When a PDN connection ultimately fails, the terminal can choose not to attempt to connect via a low-latency APN, but instead use a general APN to send and receive services from low-latency service applications.

[0088] If "UEVersion:ProtocolVersion" is "1", and the "InstallerName" of the application included in the response message includes information about two or more stores (Google Play Store, Galaxy App Store, One Store, etc.), then terminal 100 should check whether the corresponding application was installed from the store included in the "InstallerName". When the installed application was not installed through the "InstallerName" included in the response message, terminal 100 can provide the service of the application included in the response message via the bearer of the universal APN.

[0089] When "UEVersion:ProtocolVersion" is "2", terminal 100 determines whether the PublicKey of the corresponding application is normal by using the "PublicKey" of the application included in the response message. If the PublicKey of the installed application is different from the PublicKey included in the response message, terminal 100 can provide the service of the application included in the response message through the bearer of the universal APN.

[0090] Figure 4 This is a flowchart illustrating a method for checking the dynamic service status of C-DRX according to an implementation method.

[0091] Reference Figure 4After the C-DRX dynamic service is set to active (enabled), terminal 100 periodically sends C-DRX dynamic service status check request messages to authentication server 300 (S210). Terminal 100 may periodically send status check request messages based on the status query time (StatusQueryTime) included in the C-DRX dynamic service activation response message. Terminal 100 may send status check request messages to the server address (StatusServerURL) included in the C-DRX dynamic service activation response message. The server address may be the same as or different from the address included in the DNS query response message of authentication server 300.

[0092] After activating the C-DRX dynamic service, terminal 100 continuously checks whether the C-DRX dynamic service remains active (authenticated). As a result, the user can identify that the C-DRX dynamic service is continuously maintained.

[0093] The authentication server 300 sends a C-DRX dynamic service status check response message (S220) containing status information to the terminal 100.

[0094] Terminal 100 checks whether the authentication result included in the C-DRX dynamic service status response message is successful (S230).

[0095] When the authentication result indicates successful authentication, terminal 100 maintains the C-DRX dynamic service in an active state (on state) (S240). Terminal 100 waits for the next state query time and repeats step S210 when the next state query time arrives.

[0096] If the authentication result includes authentication failure, terminal 100 switches the C-DRX dynamic service to a disabled state (closed state) (S250). Terminal 100 may display a notification of the authentication result.

[0097] Through this message exchange, the authentication server 300 manages the authentication status of the terminal 100. The terminal 100 can exchange messages with the authentication server 300 via 5G / LTE / 3G / WiFi networks.

[0098] The variables included in the C-DRX dynamic service status check request message can be defined as shown in Table 8, and the message format can be shown in Table 9. The C-DRX dynamic service status check request message may also include a request URL.

[0099] [Table 8]

[0100]

[0101] [Table 9]

[0102]

[0103] The variables included in the C-DRX dynamic service status check response message can be defined as shown in Table 10. The response codes among the response variables include codes corresponding to successful or failed authentication. When authentication fails, a code can be assigned based on the reason for the failure. Response codes can be defined as shown in Table 11. If the authentication result is a failure, terminal 100 may not display the additional notification message corresponding to the response code.

[0104] [Table 10]

[0105]

[0106]

[0107] [Table 11]

[0108]

[0109] The format of the C-DRX dynamic service status response message can be shown in Table 12.

[0110] [Table 12]

[0111]

[0112]

[0113] Figure 5 This is a flowchart illustrating a method for disabling C-DRX dynamic services according to an implementation method. (See also...) Figure 5 When a C-DRX dynamic service shutdown request (C-DRX dynamic service shutdown establishment) is entered in the C-DRX management application 100, the terminal 100 sends a DNS query request message requesting the authentication server address to the domain name server (not shown) (S310).

[0114] Terminal 100 receives a DNS query response message from a domain name server, which includes the address of the authentication server (S320). The DNS query response message may include multiple authentication server addresses (e.g., IPv4 addresses or IPv6 addresses).

[0115] Terminal 100 sends a C-DRX dynamic service deactivation request message to the address included in the DNS query response message of authentication server 300 (S330).

[0116] The authentication server 300 switches the C-DRX dynamic service status of the terminal 100 to the disabled state and sends a C-DRX dynamic service disabled response message to the terminal 100 (S340).

[0117] Terminal 100 sets the C-DRX dynamic service to disabled (S350).

[0118] The variables included in the C-DRX dynamic service deactivation request message can be defined as shown in Table 8, and the message format can be shown in Table 13.

[0119] [Table 13]

[0120]

[0121] Terminal 100 operates based on the C-DRX dynamic service deactivation response message received from authentication server 300. The C-DRX dynamic service deactivation response message may include a response code corresponding to successful deactivation. Variables included in the C-DRX dynamic service deactivation response message can be defined as shown in Table 14, and the message format can be as shown in Table 15. The response code in the response variables can be defined as shown in Table 16. If the authentication result fails, terminal 100 may not display the additional notification message corresponding to the response code.

[0122] [Table 14]

[0123]

[0124]

[0125] [Table 15]

[0126]

[0127] [Table 16]

[0128] Response code notify 200 success 401 Failed (Incorrect content type) 402 Failure (HTTP method error) 403 Failed (Channel-Authentication-Token Missing Error) 404 Failed (JSON body decryption failed) 405 Failed (Username decryption failed) 406 Failed (MSISDN format error) 407 Failed (Incorrect accessToken) 408 Failed (Incorrect ServicePackageName) 409 Failed (Incorrect AppPackageName) 900 Failure (Service terminated completely)

[0129] Figure 6 This is a flowchart illustrating a method for activating / deactivating C-DRX dynamic services according to an implementation method. (See also...) Figure 6 When performing general service applications, terminal 100 accesses base station 200 (S410) using general APN.

[0130] Base station 200 sends a C-DRX establishment request including C-DRX parameters to terminal 100 accessing using the common APN (S412). Base station 200 may also send an RRC connection reconfiguration including C-DRX parameters.

[0131] Terminal 100 sets C-DRX activation status (C-DRX enabled) (S414).

[0132] Terminal 100 sends and receives data from general service applications while in C-DRX active state (C-DRX enabled) (S416). Because it is in C-DRX active state (C-DRX enabled), terminal 100 can reduce battery consumption.

[0133] When a low-latency service application is executed in the C-DRX dynamic service active state (C-DRX dynamic service enabled), the terminal 100 accesses the base station 200 using the low-latency APN (S420).

[0134] Base station 200 sends a C-DRX release request to terminal 100 accessing via low-latency APN (S422). Base station 200 may send an RRC connection reconfiguration including the C-DRX release request.

[0135] Terminal 100 switches from C-DRX active state (C-DRX enabled) to C-DRX disabled state (C-DRX disabled) (S424).

[0136] Terminal 100 sends and receives data for low-latency service applications in the C-DRX disabled state (C-DRX off) (S426).

[0137] When the low-latency service application being executed is terminated, terminal 100 releases the bearer connected via the low-latency APN (S430).

[0138] Base station 200 sends a C-DRX establishment request including C-DRX parameters to terminal 100 (S432). Base station 200 may also send an RRC connection reconfiguration request including C-DRX parameters.

[0139] Terminal 100 switches from C-DRX disabled state (C-DRX off) to C-DRX active state (C-DRX on) (S434).

[0140] Figure 7 This is a flowchart of the C-DRX dynamic service method according to the implementation method.

[0141] Reference Figure 7 Terminal 100 sends a C-DRX dynamic service activation request message to authentication server 300 (S510). When a C-DRX dynamic service activation request (C-DRX dynamic service enable setting) is entered in C-DRX management application 110, terminal 100 begins to exchange information with authentication server 300 to activate C-DRX dynamic service.

[0142] The authentication server 300 sends a response message (C-DRX dynamic service activation response) including response information to the terminal 100 (S511). The response information includes the authentication result. If authentication is successful, the response information may include a list of low-latency service applications and the low-latency APN assigned to the low-latency service application. If the authentication result is successful, it changes to the C-DRX dynamic service activation state (C-DRX dynamic service enabled state), where C-DRX can be dynamically enabled / disabled.

[0143] When a low-latency service application is executed in C-DRX dynamic service activation state, terminal 100 accesses base station 200 using a low-latency APN and sends a PDN connection request (S520). The PDN connection request is sent to AMF / MME 210. The PDN connection request may include the "PcoID" and "PcoPassword" required by SMF / P-GW 230. The "PcoID" and "PcoPassword" may be included in the C-DRX dynamic service activation response message.

[0144] MME 210 sends a session creation request to SMF / P-GW 230 (S521).

[0145] The SMF / P-GW 230 sends an authentication request (Credit Control Request, CCR-I) to the PCF 250 to establish a session (S522), and receives an authentication response (Credit Control Response, CCA-I) from the PCF 250 (S523). The PCF 250 may send an authentication response that includes quality information (e.g., QCI=9).

[0146] The SMF / P-GW 230 sends a session creation response (S524) to the MME 210.

[0147] AMF / MME 210 sends an E-RAB establishment request to base station 200 (S525).

[0148] AMF / MME 210 sends an activation request for the default EPS bearer context to terminal 100 (S526).

[0149] Base station 200 sends an RRC connection reconfiguration request including a C-DRX release request to terminal 100 (S527).

[0150] Terminal 100 disables C-DRX (C-DRX off) and sends an RRC connection reconfiguration completion message to base station 200 (S528).

[0151] Base station 200 sends an E-RAB establishment response to AMF / MME 210 (S529).

[0152] Terminal 100 sends an Activate Default EPS Bearer Context Accept to AMF / MME 210 (S530).

[0153] AMF / MME 210 and SMF / P-GW 230 send a modification bearer request / response (S531).

[0154] When a low-latency service application is terminated in a C-DRX disabled state (C-DRX off), terminal 100 sends a PDN disconnection request (S540). The PDN disconnection request is transmitted to AMF / MME 210.

[0155] AMF / MME 210 sends a session deletion request to SMF / P-GW 230 (S541).

[0156] SMF / P-GW 230 sends an authentication request (Credit Control Request, CCR-T) to terminate the session to PCF 250 (S542) and receives an authentication response (Credit Control Response, CCA-T) from PCF 250 (S543).

[0157] SMF / P-GW 230 sends a session deletion response to AMF / MME 210 (S544).

[0158] AMF / MME 210 sends an E-RAB release request to base station 200 (S545).

[0159] AMF / MME 210 sends a request to disable EPS bearer context to terminal 100 (S546).

[0160] Base station 200 sends an RRC connection reconfiguration request, including a C-DRX establishment request, to terminal 100 (S547).

[0161] Terminal 100 activates C-DRX (C-DRX enabled) and sends an RRC connection reconfiguration complete message to base station 200 (S548).

[0162] Base station 200 sends an E-RAB release response to AMF / MME 210 (S549).

[0163] Terminal 100 sends a disabled EPS bearer context accept to AMF / MME 210 (S550).

[0164] Figure 8 This is a flowchart illustrating a method for switching between C-DRX activation / deactivation states according to an implementation of an application.

[0165] Reference Figure 8When the C-DRX dynamic service is activated, the terminal 100 sets the C-DRX activation state (C-DRX enabled) to the default state (S610).

[0166] Terminal 100 determines whether to execute an application (low-latency service application) that disables C-DRX (C-DRX off) in the foreground (S620).

[0167] When no low-latency service application is running in the foreground, terminal 100 maintains C-DRX activation (C-DRX enabled) (S630).

[0168] When a low-latency service application is executed in the foreground, terminal 100 accesses the communication network using the APN (low-latency APN) connected when C-DRX is disabled, and maintains the C-DRX disabled state (C-DRX off) (S640).

[0169] Terminal 100 monitors whether a low-latency service application running in the foreground has been moved to the background, and then determines whether the low-latency service application has been terminated (S650). When a predetermined time (e.g., 120 seconds) has elapsed after the low-latency service application has been moved to the background, terminal 100 can determine that the low-latency service application has been terminated.

[0170] When a low-latency service application is terminated, terminal 100 releases the bearer connected via the low-latency APN and transitions to the C-DRX active state (C-DRX enabled) (S660). When a low-latency service application is running, terminal 100 determines whether the low-latency service application should still be running in the foreground.

[0171] As described above, according to the present invention, by activating or deactivating C-DRX according to the latency sensitivity of the application, battery consumption can be reduced while providing ultra-low latency services. Specifically, the terminal can be dynamically configured to allow latency-sensitive low-latency service applications to send and receive data in a C-DRX-disabled state (C-DRX off), and to allow low-latency service applications that are less sensitive to latency to send and receive data in a C-DRX-activated state (C-DRX on).

[0172] The embodiments of the present invention described above are not implemented solely by the device and the method described above, but can be implemented by a program for implementing functions corresponding to the configuration of the embodiments of the present invention or by a recording medium containing the program.

[0173] While the invention has been described in conjunction with what are now considered practical embodiments, it should be understood that the invention is not limited to the disclosed embodiments. Rather, it is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A method for dynamically applying battery power-saving technology at a terminal, the method comprising the following steps: The first message sent to the authentication server to request activation of the battery power saving technology dynamic service; Receive a second message from the authentication server as a response to the first message; When the response information included in the second message includes successful authentication and running at least one application included in the second message that does not apply battery power saving technology, data is sent to and received from the base station in the battery power saving technology disabled state; as well as When the application included in the second message is not running, maintain the battery power saving technology in an active state. The battery power saving technology dynamic service activates or deactivates the service based on the type of application running on the terminal.

2. The method according to claim 1, wherein, The second message includes a list of applications that do not use the battery-saving technology and a first access point name (APN) used to access the network when an application included in the application list is executed.

3. The method according to claim 2, wherein, The steps of sending data to the base station and receiving data from the base station when the battery power-saving technology is disabled include: When an application included in the application list is executed while the battery power saving technology is activated, the base station is accessed using the first APN. Receive a request from the base station to release the battery power-saving technology, and Switch the battery power saving technology from active to disabled state.

4. The method according to claim 3, wherein, The steps to maintain the activated state of the battery power-saving technology include: When the execution of an application included in the application list is terminated, the bearer connected via the first APN is released. Receive a request from the base station to establish the battery power saving technology, and Switch the battery energy-saving technology from the disabled state to the activated state.

5. The method according to claim 4, further comprising the following step: When an application not included in the application list is executed while the battery power saving technology is activated, the base station is accessed using a second APN that is different from the first APN.

6. The method according to claim 1, wherein, Applications that do not utilize the battery-saving technology include low-latency service applications.

7. The method according to claim 1, further comprising the following steps: Based on the status query time, a third message is sent periodically to the authentication server requesting a status check for the dynamic service of battery power saving technology. Receive a fourth message from the authentication server as a response to the third message; and When the response information included in the fourth message includes successful authentication, the battery power saving technology dynamic service will remain active. The second message also includes the status query time.

8. The method according to claim 1, further comprising the following step: Send a fifth message to the authentication server requesting the deactivation of the battery power saving technology dynamic service; Receive a sixth message from the authentication server as a response to the fifth message; and When the response information included in the sixth message includes "disabled successfully", the battery power saving technology dynamic service is set to a disabled state.

9. A method for dynamically applying battery power-saving technology at a terminal, the method comprising the following steps: A list of applications that do not apply C-DRX when sending and receiving data in the connected mode discontinuous reception C-DRX disabled state (C-DRX off); During the activation of the C-DRX dynamic service, when at least one application included in the list of applications that do not apply C-DRX is executed, the C-DRX status is set to the C-DRX disabled state (C-DRX off); and During the activation of the C-DRX dynamic service, when none of the applications included in the list of applications that do not apply C-DRX are executed, the C-DRX state is set to the C-DRX active state (C-DRX enabled).

10. The method according to claim 9, wherein, The applications that do not apply C-DRX are low-latency service applications, and the list of applications that do not apply C-DRX is received from the authentication server.

11. The method according to claim 9, wherein, Applications included in the list of applications that do not use C-DRX access the base station using the first APN, and applications not included in the list of applications that do not use C-DRX access the base station using the second APN.

12. The method according to claim 11, wherein, The first APN is received from the authentication server.

13. The method according to claim 11, wherein, The steps to set the C-DRX status to the C-DRX disabled status (C-DRX off) include: When executing an application that is not subject to C-DRX and is included in the list of applications that are not subject to C-DRX, the user accesses the base station using the first APN. Receive C-DRX release request from the base station, and Switch the C-DRX status to the C-DRX disabled status.

14. The method according to claim 13, wherein, The steps to set the C-DRX status to the C-DRX active status (C-DRX enabled) include: When an application that is not using C-DRX is terminated, the bearer connected through the first APN is released. Receive a C-DRX establishment request from the base station, and Switch the C-DRX deactivated state to the C-DRX activated state.

15. A method for dynamically applying battery-saving technology by an authentication server, the method comprising the following steps: The terminal receives the first message requesting activation of the dynamic battery power saving technology service. as well as Send a second message to the terminal as a response to the first message; The second message includes a list of applications that do not use the battery-saving technology and a first access point name (APN) used for network access when an application included in the application list is executed. Wherein, the first APN is a different APN from the second APN used for network access when executing an application not included in the application list, and The battery power saving technology dynamic service activates or deactivates the service based on the type of application running on the terminal.

16. The method of claim 15, further comprising the step of: The terminal receives a third message periodically requesting a status check of the battery power saving technology dynamic service, and Send a fourth message to the terminal as a response to the third message. When the fourth message includes successful authentication, the terminal will keep the battery power saving technology dynamic service active.

17. The method of claim 15, further comprising the step of: The terminal receives a fifth message requesting the disabling of the battery power saving technology dynamic service, and Send a sixth message to the terminal as a response to the fifth message. When the sixth message includes "disabled successfully", the terminal sets the battery power saving technology dynamic service to a disabled state.

18. A method for dynamically applying battery power-saving technology by a base station, the method comprising the following steps: When all applications included in the list of non-C-DRX-enabled applications that send and receive data in the discontinuous C-DRX-disabled state of connected mode are not executed, a request for access using the first APN is received from the terminal. Send a C-DRX establishment request including C-DRX parameters to the terminal, and send data to and receive data from the terminal while the C-DRX is active; When at least one of the applications included in the list of applications that do not apply C-DRX is executed, a request for access using the second APN is received from the terminal. as well as Send a C-DRX release request to the terminal, and send data to and receive data from the terminal while the C-DRX is disabled.

19. The method of claim 18, further comprising the step of: Receive a request from the terminal to release the bearer connected via the second APN, and Send a C-DRX establishment request, including C-DRX parameters, to the terminal.

20. The method according to claim 18, wherein, The second APN is the APN assigned to applications that do not apply C-DRX.

Images