Control device, control method, and control system

Abstract

The present invention executes, in a timely manner and in response to a request for new QoS control, QoS control corresponding to the request. A QoS control device 30 comprises: a reception unit 31 that receives a start request POST for QoS control for one UE 10; and a control unit 32 that, if existing QoS control for the one UE 10 has started at the time at which the start request POST for QoS control for the one UE 10 is received, terminates the existing QoS control and controls the start of the QoS control for the one UE 10.

Description

Control device, control method, and control system

[0001] One aspect of the present disclosure relates to a control device, a control method, and a control system.

[0002] Providers that provide network services are required to provide users with a certain quality of service (QoS). A service level agreement (SLA) is established between the provider and the user regarding the level of QoS for the services provided. The provider's equipment performs QoS control to ensure the SLA. Regarding QoS control, a technology is known in which, when a network-side device receives a new QoS request from a user terminal, it allocates available resources to the user terminal as resources that satisfy the new QoS request (see, for example, Patent Document 1).

[0003] JP 2008-193430 A

[0004] In general, due to constraints on network equipment, etc., it tends to be difficult to simultaneously execute different QoS controls on the same terminal. A mechanism is desired that can provide a QoS that meets a new QoS control request for the same terminal.

[0005] Therefore, an object of the present disclosure is to timely execute QoS control in response to a new QoS control request.

[0006] The control device of the present disclosure includes a reception unit that receives a request to start QoS control for a terminal, and a control unit that, if existing QoS control for the terminal has been started when the request to start QoS control for the terminal is received, terminates the existing QoS control and controls the start of QoS control for the terminal.

[0007] Alternatively, the control method of the present disclosure includes a receiving step of receiving a request to start QoS control for a terminal, and a control step of terminating the existing QoS control and controlling the start of QoS control for the terminal if existing QoS control for the terminal has been started when the request to start QoS control for the terminal is received.

[0008] Alternatively, the control system of the present disclosure includes a reception unit that receives a request to start QoS control for a terminal, and a control unit that, if existing QoS control for the terminal has been started when the request to start QoS control for the terminal is received, terminates the existing QoS control and controls the start of QoS control for the terminal.

[0009] According to one aspect of the present disclosure, in response to a new QoS control request, QoS control can be executed in a timely manner in accordance with the request.

[0010] FIG. 1 is a block diagram showing a configuration of a communication system 1 according to the present disclosure. FIG. 2 shows an example of the data configuration of QoS state information stored in a QoS state information storage unit 33. FIG. 3 is a flowchart showing a processing procedure related to QoS control by the communication system 1 of FIG. 1. FIG. 4 is a flowchart showing a processing procedure related to QoS control by the communication system 1 of FIG. 1. FIG. 5 is a flowchart showing a processing procedure related to QoS control by the communication system 1 of FIG. 1. FIG. 6 is a flowchart showing a processing procedure related to QoS control by the communication system 1 of FIG. 1. FIG. 7 is a diagram showing an example of a hardware configuration of a QoS control device 30 according to an embodiment of the present disclosure.

[0011] The present disclosure will be described with reference to the accompanying drawings. Whenever possible, the same parts are designated by the same reference numerals and redundant description will be omitted.

[0012] FIG. 1 is a diagram illustrating the device configuration of a communication system, which is a control system according to this embodiment. As illustrated in FIG. 1 , the communication system 1 includes a UE (User Equipment) 10, a server 20, a QoS control device 30, and a network control device 40, which are configured to be able to communicate with each other via a network including a wireless communication network and a fixed communication network. The QoS control device 30 constitutes a control device that controls the initiation and termination of QoS control for the UE 10 in the network. The network control device 40 initiates or terminates QoS control for the UE 10 on the network in accordance with control by the QoS control device 30. Specifically, the network control device 40 controls various network equipment, such as wireless control devices, present on the network so as to satisfy the communication bandwidth and communication delay set in the SLA for a specific application running on the UE 10. In this case, the network control device 40 may perform QoS control on a wireless communication section on the network, or on a communication section extending from the wireless communication section on the network to a core network.

[0013] UE 10 is a user terminal that uses an application program that is subject to QoS control. UE 10 is a device such as a personal computer, a smartphone, a tablet terminal, a feature phone, a server device, or a game console. UE 10 is configured to be able to run multiple application programs, including an application program that is subject to QoS control. UE 10 transmits a request to start or delete QoS control for UE 10 to QoS control device 30 via the application program that is subject to QoS control. At this time, UE 10 can also transmit a request to start or delete QoS control for multiple UEs 10, including UE 10. Note that while only one UE 10 is shown in FIG. 1 , multiple UEs 10 can be connected to the network.

[0014] The server 20 is a device that operates in opposition to an application program running on the UE 10, and transmits and receives data to and from the UE 10 via a network. A server 20 can be provided for each application program running on the UE 10. The server 20 transmits a request to start or delete QoS control for a specific UE 10 to the QoS control device 30. At this time, the server 20 can also transmit a request to start or delete QoS control for multiple UEs 10. Note that although only one server 20 is shown in FIG. 1 , multiple servers 20 can be connected to the network, one for each type of application program.

[0015] The QoS control device 30 includes, as functional components, a reception unit 31, a control unit 32, and a QoS status information storage unit (storage unit) 33. The functions of each functional unit of the QoS control device 30 will be described in detail below.

[0016] The reception unit 31 receives a POST request to start QoS control for a specific UE 10. That is, the reception unit 31 receives a POST request to start QoS control for the specific UE 10 from the specific UE 10 via the network. At this time, the reception unit 31 can also receive a POST request to start QoS control for multiple UEs 10 including the specific UE 10 from the specific UE 10. The reception unit 31 also receives a POST request to start QoS control for the specific UE 10 from the server 20 via the network. At this time, the reception unit 31 can also receive a POST request to start QoS control for multiple UEs 10 including the specific UE 10 from the server 20.

[0017] The reception unit 31 also receives a request DELETE to delete QoS control for a specific UE 10. That is, the reception unit 31 receives a request DELETE to delete QoS control for the specific UE 10 from the specific UE 10 via the network. At this time, the reception unit 31 can also receive a request DELETE to delete QoS control for multiple UEs 10 including the specific UE 10 from the specific UE 10. The reception unit 31 also receives a request DELETE to delete QoS control for the specific UE 10 from the server 20 via the network. At this time, the reception unit 31 can also receive a request DELETE to delete QoS control for multiple UEs 10 including the specific UE 10 from the server 20.

[0018] The reception unit 31 also receives a change / continuation request PATCH, which is a request for a change regarding the control content (parameters) of QoS control for a specific UE 10 or a request for the continuation of QoS control for a specific UE 10. That is, the reception unit 31 receives a change / continuation request PATCH for QoS control for a specific UE 10 from the specific UE 10 via the network. At this time, the reception unit 31 can also receive a change / continuation request PATCH for QoS control for multiple UEs 10 including the specific UE 10 from the specific UE 10. The reception unit 31 also receives a change / continuation request PATCH for QoS control for a specific UE 10 from the server 20 via the network. At this time, the reception unit 31 can also receive a change / continuation request PATCH for QoS control for multiple UEs 10 including the specific UE 10 from the server 20.

[0019] Furthermore, the reception unit 31 passes the received start request POST, deletion request DELETE, or change / continuation request PATCH to the control unit 32 .

[0020] The control unit 32 executes the following process in response to a POST request to start QoS control for one UE 10 accepted by the acceptance unit 31. At this time, if the control unit 32 accepts POST requests to start QoS control for multiple UEs 10, the control unit 32 repeats the following process for the multiple UEs 10. First, the control unit 32 determines whether existing QoS control for the one UE 10 has been started on the network by referring to the QoS status information stored in the QoS status information storage unit 33. If the control unit 32 determines that existing QoS control for the one UE 10 has already been started, the control unit 32 requests the network control device 40 to delete (terminate) the existing QoS control on the network. Thereafter, upon confirming the deletion of the existing QoS control based on a response from the network control device 40, the control unit 32 requests the network control device 40 to control the start of QoS control for the one UE 10 accepted by the acceptance unit 31.

[0021] 2 shows an example of the data configuration of the QoS status information stored in the QoS status information storage unit 33. In the QoS status information, for a terminal identifier MSISDN that identifies UE 10, data "POST completed" that manages whether QoS control for the UE 10 has been started and data "processing" that manages whether a start request POST, a deletion request DELETE, or a change / continuation request PATCH related to QoS control for the UE 10 are being processed on the network are stored in association with each other. If a value including "Subscription ID" is stored in the data "POST completed," it indicates that QoS control has been started. Furthermore, if the value "POST" is stored in the data "in processing", it indicates that a start request POST for QoS control for UE 10 is being processed; if a value including "PATCH" is stored in the data "in processing", it indicates that a change / continuation request PATCH for QoS control for UE 10 is being processed; and if a value including "DELETE" is stored in the data "in processing", it indicates that a delete request DELETE for QoS control for UE 10 is being processed.

[0022] The control unit 32 determines whether existing QoS control for the one UE 10 has been initiated on the network based on whether a value is stored in the data "POST completed" associated with the terminal identifier MSISDN of the one UE 10 in the QoS status information. Furthermore, when the control unit 32 confirms the deletion of the existing QoS control for the one UE 10, it deletes the value of the data "POST completed" associated with the terminal identifier MSISDN of the one UE 10 and sets it to a "NULL" state. Furthermore, after controlling the initiation of QoS control for the one UE 10 accepted by the accepting unit 31, if it is confirmed based on a response from the network control device 40 that the initiation has been completed, the control unit 32 stores a value including "SubscriptionID" in the data "POST completed" associated with the terminal identifier MSISDN of the one UE 10.

[0023] The control unit 32 executes the following process in response to a request DELETE to delete QoS control for one UE 10 accepted by the acceptance unit 31. At this time, if the control unit 32 accepts requests DELETE to delete QoS control for multiple UEs 10, the control unit 32 repeats the following process for the multiple UEs 10. First, the control unit 32 determines whether a request POST to start QoS control for one UE 10, another request DELETE to delete QoS control, or a request PATCH to change / continue QoS control is currently being processed by referring to the QoS status information stored in the QoS status information storage unit 33. At this time, the control unit 32 determines whether a request for QoS control for one UE 10 is currently being processed by determining whether a value such as "POST" is stored in the data "in process" associated with the terminal identifier MSISDN of the one UE 10. If the control unit 32 determines that QoS control for one UE 10 is currently being processed, it rejects the deletion request DELETE and responds to the requestor to that effect. On the other hand, if the control unit 32 determines that QoS control for one UE 10 is not currently being processed, it requests the network control device 40 to delete (terminate) the QoS control on the network. Thereafter, if the control unit 32 confirms the deletion based on a response from the network control device 40, it deletes the data "POST completed" associated with the terminal identifier MSISDN of one UE 10 from the QoS status information and sets it to a "NULL" state.

[0024] The control unit 32 executes the following process in response to a PATCH requesting change / continuation of QoS control for one UE 10 accepted by the acceptance unit 31. At this time, if the control unit 32 accepts PATCH requests for change / continuation of QoS control for multiple UEs 10, the control unit 32 repeats the following process for the multiple UEs 10. First, the control unit 32 determines whether a POST requesting start of QoS control, a DELETE requesting deletion, or another PATCH requesting change / continuation of QoS control for one UE 10 is currently being processed by referring to the QoS status information stored in the QoS status information storage unit 33. At this time, the control unit 32 determines whether a request for QoS control for one UE 10 is currently being processed by determining whether a value such as "POST" is stored in the data "in process" associated with the terminal identifier MSISDN of the one UE 10. If the control unit 32 determines that QoS control for one UE 10 is currently being processed, it rejects the change / continuation request PATCH and responds to that effect to the request source. On the other hand, if QoS control for one UE 10 is not currently being processed, the control unit 32 requests the network control device 40 to change the settings of the QoS control in accordance with the change / continuation request PATCH.

[0025] Furthermore, when the reception unit 31 receives multiple POST requests to start QoS control for one UE 10 in succession, the control unit 32 executes the following process. That is, when the control unit 32 receives a POST request to start a first QoS control for one UE 10 and then receives a POST request to start a second QoS control for the one UE 10 before the first QoS control is started on the network, the control unit 32 performs control so that the start of the first QoS control takes priority over the start of the second QoS control. More specifically, the control unit 32 determines whether a POST requesting the start of the first QoS control is being processed (whether the first QoS control has not yet started) by referring to the QoS status information stored in the QoS status information storage unit 33. If the POST requesting the start of the first QoS control is being processed when the POST requesting the start of the second QoS control is accepted, the control unit 32 rejects the POST requesting the start of the second QoS control and notifies the requestor of this fact. At this time, the control unit 32 determines whether the first QoS control for the one UE 10 has not yet started by checking whether the value of “POST” is stored in the data “in process” associated with the terminal identifier MSISDN of the one UE 10 in the QoS status information.

[0026] The processing procedure for QoS control by the communication system 1 configured as described above, i.e., the flow of the control method according to this embodiment, will be described below. Figures 3 and 4 are flowcharts showing the processing procedure for a QoS control start request POST, Figure 5 is a flowchart showing the processing procedure for a QoS control deletion request DELETE, and Figure 6 is a flowchart showing the processing procedure for a QoS control change / continuation request PATCH.

[0027] 3 and 4, the procedure for processing a POST request to start QoS control will be described. The reception unit 31 of the QoS control device 30 receives a POST request to start QoS control for a particular UE 10 from the UE 10 or the server 20 (step S101). The control unit 32 of the QoS control device 30 then determines whether a value is stored in the "Processing" data corresponding to the particular UE 10 in the QoS status information (step S102). If a value is stored (step S102; Yes), the control unit 32 determines that another process for QoS control for the particular UE 10 is currently being processed, rejects the POST request (step S103), and terminates the process for the POST request.

[0028] On the other hand, if no value is stored (step S102; No), the control unit 32 determines that another process for QoS control for the one UE 10 is not currently being processed, and adds (stores) the value "POST" to the data "Processing" corresponding to the one UE 10 in the QoS status information (step S104). Thereafter, the control unit 32 determines whether a value is stored in the data "POST Completed" corresponding to the one UE 10 in the QoS status information (step S105). As a result of the determination, if no value is stored (step S105; No), the process proceeds to step S111 described below. On the other hand, if a value is stored (step S105; Yes), the control unit 32 determines that the existing QoS control for the one UE 10 has started, and causes the network control device 40 to execute a process for deleting the existing QoS control (step S106). In response to this, the control unit 32 determines whether or not the deletion process of the QoS control has been successful based on the response from the network control device 40 (step S107).

[0029] If it is determined that the QoS control deletion process has failed (step S107; No), the control unit 32 deletes the value "POST" from the data "in process" corresponding to one UE 10 in the QoS status information (step S108). Next, the control unit 32 rejects the start request POST accepted in step S101 (step S109), and the process for the start request POST is terminated.

[0030] If it is determined in step S107 that the QoS control deletion process has been successful (step S107; Yes), the control unit 32 deletes a value from the data "POST completed" corresponding to the one UE 10 in the QoS status information (step S110). Next, the control unit 32 processes the start request POST accepted in step S101 and causes the network control device 40 to execute the QoS control start process for the one UE 10 (step S111). In response to this, the control unit 32 determines whether the QoS control start process has been successful or not based on a response from the network control device 40 (step S112).

[0031] If it is determined that the QoS control start process has failed (step S112; No), the control unit 32 moves the process to step S108 and rejects the QoS control start request POST. On the other hand, if it is determined that the QoS control start process has succeeded (step S112; Yes), the control unit 32 moves the value of the data "in process" corresponding to one UE 10 in the QoS status information to the data "POST completed," and ends the process for the start request POST.

[0032] 5, the procedure for processing a QoS control deletion request DELETE will be described. The reception unit 31 of the QoS control device 30 receives a QoS control deletion request DELETE for a particular UE 10 from the UE 10 or the server 20 (step S201). The control unit 32 of the QoS control device 30 then determines whether a value is stored in the "in progress" data field corresponding to the particular UE 10 in the QoS status information (step S202). If a value is stored (step S202; Yes), the control unit 32 determines that another process for QoS control for the particular UE 10 is in progress, rejects the deletion request DELETE (step S203), and terminates the process for the deletion request DELETE.

[0033] On the other hand, if the value is not stored (step S202; No), the control unit 32 determines that another process for the QoS control for the one UE 10 is not being processed, and causes the network control device 40 to execute a process for deleting the QoS control for the one UE 10 (step S204). Thereafter, the control unit 32 deletes the value from the data "POST completed" corresponding to the one UE 10 in the QoS status information (step S205).

[0034] Next, the procedure for processing a QoS control change request PATCH will be described with reference to Figure 6. The reception unit 31 of the QoS control device 30 receives a QoS control change request PATCH for one UE 10 from the UE 10 or the server 20 (step S301). Then, the control unit 32 of the QoS control device 30 determines whether a value is stored in the data "in process" corresponding to the one UE 10 in the QoS status information (step S302). If a value is stored (step S302; Yes), the control unit 32 determines that another process for QoS control for the one UE 10 is in process, rejects the change request PATCH (step S303), and ends the process for the change request PATCH.

[0035] On the other hand, if the value is not stored (step S302; No), the control unit 32 determines that no other processing for the QoS control for the one UE 10 is in progress, and after having the network control device 40 execute processing to change the QoS control for the one UE 10 (step S304), the processing for the change request PATCH is terminated.

[0036] Next, a description will be given of the operation and effect of the QoS control device 30 of the present disclosure. The QoS control device 30 of the present disclosure includes a reception unit 31 that receives a POST request to start QoS control for a certain UE 10, and a control unit 32 that, if existing QoS control for the certain UE 10 has been started when the POST request to start QoS control for the certain UE 10 is received, ends the existing QoS control and controls the start of QoS control for the certain UE 10.

[0037] With this configuration, when the QoS control device 30 receives a POST request to start new QoS control for a particular UE 10, it terminates the existing QoS control for the particular UE 10 and then starts the new QoS control for the particular UE 10. As a result, QoS control can be executed in a timely manner in response to the request for new QoS control for the particular UE 10. Generally, due to constraints on network equipment (radio base stations, core network equipment, etc.), it may be difficult to simultaneously perform multiple QoS controls with different content on the same UE 10. In such cases, the problem of new QoS control for the particular UE 10 being unable to be started due to the existing QoS control for the particular UE 10 can be avoided. Furthermore, the problem of being unable to process a request to start QoS control from a legitimate user's UE 10 can also be avoided. That is, the QoS control device 30 can timely process the start of QoS control that is requested later. Furthermore, the QoS control device 30 can avoid the problem that, in a situation where QoS control has been started first in response to a request from the UE 10 and then the UE 10 moves out of the communication coverage area of ​​the network, it becomes impossible to start new QoS control from an application program running in the foreground on the UE 10.

[0038] Here, the QoS control device 30 of the present disclosure further includes a QoS status information storage unit 33 that stores QoS status information that manages the start of existing QoS control for multiple UEs 10, and the control unit 32 determines whether or not existing QoS control has been started for one UE 10 by referring to the QoS status information storage unit 33. This makes it possible to efficiently determine whether or not existing QoS control exists for one UE 10 in the network, and to reliably execute new QoS control.

[0039] In the QoS control device 30 of the present disclosure, if the reception unit 31 receives a POST request to start a first QoS control for a UE 10 and then receives a POST request to start a second QoS control for the UE 10 before the first QoS control for the UE 10 is started, the control unit 32 prioritizes the start of the first QoS control over the start of the second QoS control and rejects the POST request to start the second QoS control. As a result, if two POST requests to start QoS control for the UE 10 are received in succession, the first received POST request can be processed preferentially. As a result, contention in the QoS control start processes can be prevented.

[0040] Furthermore, the QoS control device 30 of the present disclosure further includes a QoS status information storage unit 33 that stores QoS status information that manages the initiation of QoS control for multiple UEs 10, and the control unit 32 determines whether the first QoS control has not yet started by referring to the QoS status information. This makes it possible to efficiently determine whether the first QoS control for one UE 10 has not yet started. As a result, it is possible to reliably prevent contention in the initiation of QoS control for one UE 10.

[0041] The control device and control method of the present disclosure have the following configuration.

[0042] [1] A control device comprising: a reception unit that receives a request to start QoS control for a terminal; and a control unit that, if existing QoS control for the terminal has been started when the request to start QoS control for the terminal is received, ends the existing QoS control and controls the start of QoS control for the terminal.

[0043] [2] The control device according to [1] above, further comprising a storage unit that stores information for managing the start of existing QoS control for a plurality of terminals, wherein the control unit determines whether or not existing QoS control for the one terminal has been started by referring to the storage unit.

[0044] [3] The control device according to [1] or [2] above, wherein, when the reception unit receives a request to start a first QoS control for the one terminal and then receives a request to start a second QoS control for the one terminal before starting the first QoS control for the one terminal, the control unit controls the start of the first QoS control to take priority over the start of the second QoS control.

[0045] [4] The control device according to [3], wherein the control unit rejects the request to start the second QoS control.

[0046] [5] The control device according to [3] or [4] above, further comprising a storage unit that stores information for managing the initiation of QoS control for a plurality of terminals, wherein the control unit determines whether the first QoS control has not yet been initiated by referring to the information.

[0047] [6] A control method comprising: a receiving step of receiving a request to start QoS control for a terminal; and a control step of terminating the existing QoS control and controlling the start of QoS control for the terminal, if existing QoS control for the terminal has been started when the request to start QoS control for the terminal is received.

[0048] [7] A control system comprising: a receiving step of receiving a request to start QoS control for a terminal; and a control step of terminating the existing QoS control and controlling the start of QoS control for the terminal, if existing QoS control for the terminal has been started when the request to start QoS control for the terminal is received.

[0049] [8] The control system according to [7] above, including a terminal that requests the termination of the existing QoS control and requests the start of QoS control.

[0050] The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., via wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0051] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0052] For example, the QoS control device 30 constituting the communication system 1 according to an embodiment of the present disclosure may function as a computer that performs processing of the control method of the present disclosure. FIG. 7 is a diagram illustrating an example of the hardware configuration of the QoS control device 30 according to an embodiment of the present disclosure. The above-described QoS control device 30 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. The QoS control device 30 may be configured as a computer device including at least one processor such as a CPU or a GPU, or may be configured as a computer device including multiple processors or may be configured to include multiple computer devices. The UE 10, the server 20, and the network control device 40 may also have similar hardware configurations.

[0053] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the QoS control device 30 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

[0054] Each function in the QoS control device 30 is realized by loading specified software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and storage 1003.

[0055] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned reception unit 31, control unit 32, etc. may be realized by the processor 1001.

[0056] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the reception unit 31 and the control unit 32 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be used for other functional blocks. While the above-described various processes have been described as being executed by a single processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0057] The memory 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a control method according to an embodiment of the present disclosure.

[0058] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0059] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned reception unit 31, control unit 32, etc. may be realized by the communication device 1004.

[0060] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0061] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0062] The QoS control device 30 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0063] The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0064] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0065] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0066] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0067] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0068] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0069] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0070] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0071] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0072] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0073] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0074] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0075] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.

[0076] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0077] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0078] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0079] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0080] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0081] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0082] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0083] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0084] The control unit 32 of the QoS control device 30 of the present disclosure may function as follows. That is, when the control unit 32 receives a POST requesting initiation of QoS control for a certain UE 10, if the existing QoS control for the certain UE 10 is managed as a type that should be applied at all times, the control unit 32 may always reject the POST requesting initiation without processing the POST. In this case, the control unit 32 may determine whether the existing QoS control is a type that should be applied at all times by referring to QoS status information or based on information managed by other equipment on the network.

[0085] Furthermore, in the communication system 1 of the present disclosure, the QoS control device 30 includes functional units, namely, the reception unit 31, the control unit 32, and the QoS status information storage unit 33. However, these functional units may be realized by the communication system 1 or may be provided by other devices within the communication system 1. For example, the UE 10 or the server 20 may request the network control device 40 via the QoS control device 30 to delete existing QoS control for one UE 10, or may request the network control device 40 via the QoS control device 30 to start QoS control for one UE 10 accepted by the reception unit 31. In this case, the UE 10 (or the server 20) may obtain information necessary for starting or deleting QoS control from an application or OS, etc., within the UE 10 that has requested the QoS control, or may obtain information from the QoS control device 30, the server 20, etc., within the communication system 1.

[0086] 1...communication system, 10...UE (terminal), 20...server, 30...QoS control device, 40...network control device, 31...reception unit, 32...control unit, 33...QoS status information storage unit (storage unit).

Claims

1. A control device comprising: a reception unit that receives a request to start QoS control for a terminal; and a control unit that, if existing QoS control for the terminal has been started when the request to start QoS control for the terminal is received, ends the existing QoS control and controls the start of QoS control for the terminal.

2. The control device according to claim 1, further comprising a storage unit that stores information for managing the initiation of existing QoS control for a plurality of terminals, wherein the control unit determines whether existing QoS control for one of the terminals has been initiated by referring to the storage unit.

3. The control device according to claim 1, wherein, when the reception unit receives a request to start a first QoS control for the one terminal and then receives a request to start a second QoS control for the one terminal before starting the first QoS control for the one terminal, the control unit controls the start of the first QoS control to take priority over the start of the second QoS control.

4. The control device according to claim 3, wherein the control unit rejects the request to start the second QoS control.

5. The control device according to claim 3, further comprising a storage unit for storing information for managing the initiation of QoS control for multiple terminals, wherein the control unit determines whether the first QoS control has not yet been initiated by referring to the information.

6. A control method comprising: a receiving step of receiving a request to start QoS control for a terminal; and a control step of terminating the existing QoS control and controlling the start of QoS control for the terminal if existing QoS control for the terminal has been started when the request to start QoS control for the terminal is received.

7. A control system comprising: a reception unit that receives a request to start QoS control for a terminal; and a control unit that, if existing QoS control for the terminal is started when the request to start QoS control for the terminal is received, terminates the existing QoS control and controls the start of QoS control for the terminal.

8. The control system according to claim 7, further comprising a terminal that requests the termination of the existing QoS control and the start of QoS control.

Images