Information processing device and terminal device

Abstract

An information processing device according to the present disclosure provides an application service to a terminal device. The information processing device comprises a control unit. The control unit acquires terminal information including application information relating to the application service from the terminal device. The control unit predicts, on the basis of the terminal information, a timing at which a setting relating to communication quality by the terminal device will be performed in the future. The control unit generates calculation information for calculating future quality information relating to communication quality that can be set by the terminal device at the predicted timing.

Description

Information Processing Apparatus and Terminal Device

[0001] The present disclosure relates to an information processing apparatus and a terminal device.

[0002] Conventionally, communication has been performed between a terminal device (hereinafter also referred to as UE (User Equipment)) used by a user and an application server (AS) that provides an application service to the UE, specifying a desired communication quality (e.g., 5QI, etc.).

[0003] A plurality of ASs are connected to the network according to the application services provided to the UE. The plurality of ASs perform communication by specifying (requesting) a communication quality corresponding to the application service provided by each, for example.

[0004] Japanese Patent Application Laid-Open No. 2004-7565, Japanese Patent Application Laid-Open No. 2015-524227, Japanese Patent Application Laid-Open No. 2021-536714, Japanese Patent Application Laid-Open No. 2022-961

[0005] As the requests for communication quality by the AS increase, it becomes difficult for the AS to ensure the communication quality of the network at the timing desired by the AS. As a result, it becomes difficult for the AS to communicate with the UE with the desired communication quality.

[0006] Therefore, the present disclosure proposes an information processing apparatus and a terminal device that can better ensure a desired communication quality.

[0007] Note that the above problem or objective is only one of the plurality of problems or objectives that can be solved or achieved by the plurality of embodiments disclosed in this specification.

[0008] The information processing apparatus of the present disclosure provides an application service to a terminal device. The information processing apparatus includes a control unit. The control unit acquires terminal information including application information regarding the application service from the terminal device. The control unit predicts the timing when a setting regarding the communication quality by the terminal device will be made in the future based on the terminal information. The control unit generates calculation information for calculating future quality information regarding the communication quality that the terminal device can set at the predicted timing.

[0009] This is a sequence diagram showing an example of the information processing flow related to the proposed technology of this disclosure. This is a block diagram showing an example of the overall configuration of a communication system according to an embodiment of this disclosure. This is a block diagram showing an example of the configuration of an application server (AS) according to an embodiment of this disclosure. This is a block diagram showing an example of the configuration of a QoS server according to an embodiment of this disclosure. This is a block diagram showing an example of the configuration of a 5GC according to an embodiment of this disclosure. This is a diagram showing an example of the configuration of a base station according to the first embodiment of this disclosure. This is a block diagram showing an example of the configuration of a UE according to the first embodiment of this disclosure. This is a diagram showing an example of the priority assignment process according to an embodiment of this disclosure. This is a sequence diagram showing an example of the QoS setting request process according to an embodiment of this disclosure. This is a diagram showing an example of the QoS setting UI (User Interface) that presents candidate information according to an embodiment of this disclosure. This is a diagram showing an example of information exchanged between a 5G system and a QoS server according to an embodiment of this disclosure. This is a diagram showing an example of information exchanged between an AS and a QoS server according to an embodiment of this disclosure. This is a diagram showing an example of information exchanged between a UE and an AS according to an embodiment of this disclosure. This is a sequence diagram showing an example of the QoS setting process flow according to an embodiment of this disclosure. This figure shows an example of a UI that presents current candidate information according to the embodiments of this disclosure. This is a hardware configuration diagram showing an example of a computer that implements the functions of the UE.

[0010] Embodiments of this disclosure will be described in detail below with reference to the attached drawings. In this specification and the drawings, components having substantially the same functional configuration are denoted by the same reference numerals, and redundant descriptions will be omitted.

[0011] Furthermore, in this specification and drawings, similar components of embodiments may be distinguished by adding at least one different alphabet and number after the same reference numeral. However, if there is no need to particularly distinguish each of the similar components, only the same reference numeral will be used.

[0012] The one or more embodiments (including examples, modifications, and applications) described below can each be implemented independently. On the other hand, at least some of the embodiments described below may be implemented in appropriate combination with at least some of the other embodiments. These embodiments may contain novel features that differ from each other. Therefore, these embodiments may contribute to solving different objectives or problems and may produce different effects.

[0013] <<1. Introduction>> <1-1. Background and Issues> As described above, conventionally, communication between UE and AS has been conducted with the desired communication quality (e.g., QoS (Quality of Service) settings) specified. For example, AS requests the Network Exposure Function (NEF) of the cellular network to set the desired QoS settings (e.g., 5QI) according to the request from UE.

[0014] Multiple ASs can exist within a network (e.g., the Internet) that communicate with a UE (User Environment) with a specified communication quality.

[0015] As the number of ASs increases and the number of QoS setting requests made to NEFs also increases, it becomes difficult for cellular networks to apply the desired QoS settings at the timing desired by the ASs. As a result, it becomes difficult for ASs to conduct communications with UEs that meet their desired QoS requirements.

[0016] <1-2. Overview of the Proposed Technology> The AS relating to the proposed technology in this disclosure is an information processing device that provides application services to a UE (an example of a terminal device). The AS acquires terminal information, including application information related to the application service, from the UE. Based on the terminal information, the AS predicts the timing at which the UE will make settings regarding communication quality in the future. The AS generates calculation information for calculating future quality information regarding communication quality that the UE may set at the predicted timing.

[0017] Figure 1 is a sequence diagram showing an example of the information processing flow related to the proposed technology of this disclosure. The information processing shown in Figure 1 is performed by the communication system related to the proposed technology. The communication system related to the proposed technology comprises an AS, a UE, a 5GC, and a QoS server (an example of another information processing device).

[0018] As described above, the AS is an information processing device that provides application services to the UE. The UE is a terminal device (information processing device) that receives application services from the AS.

[0019] 5GC is the core network that provides cellular communication services to UEs. The QoS server is an information processing device that provides information about the communication quality of the UEs (e.g., QoS settings).

[0020] As shown in Figure 1, the AS requests the 5GC to set priorities (step S101). For example, the 5GC sets the priority of the AS in response to the request from the AS. For example, the 5GC sets the priority so that AS providing application services that require real-time communication, such as web conferencing and live streaming, is given a higher priority.

[0021] The 5GC notifies the QoS server of the configured AS priority (step S102).

[0022] The UE transmits terminal information to the AS (step S103). The terminal information includes, for example, application information (hereinafter also referred to as app information) related to application services provided by the AS. The terminal information may also include, for example, the UE's location information and quality information related to communication quality.

[0023] This terminal information is transmitted to the AS, for example, via the cellular network provided by 5GC. The UE, for example, periodically transmits terminal information to the AS.

[0024] Based on terminal information, the AS predicts the timing (hereinafter also referred to as the predicted timing) when the UE will configure communication quality settings (e.g., QoS settings) (step S104). For example, the UE requests the AS to configure communication quality settings when it runs an application and receives services from the AS. In this case, the AS predicts the timing when the UE will run the application.

[0025] The AS generates calculation information (step S105). The calculation information is, for example, information used to calculate information about the communication quality (QoS) that the UE can set at the predicted timing (e.g., future quality information). The calculation information may include, for example, the predicted timing, the position of the UE at this predicted timing, etc.

[0026] The AS transmits the calculation information to the QoS server (step S106). The 5GC also transmits network information to the QoS server (step S107). The network information may include, for example, information about the base station, the time required for QoS setup (hereinafter also referred to as setup time), and the status of the QoS setup.

[0027] The QoS server generates future quality information based on the acquired calculation information and / or network information (step S108). Future quality information may be generated for each connection destination (e.g., base station) that the UE can connect to. Future quality information may include, for example, recommendation information, probability information, time information, connection destination evaluation information, and parameter information, at least one of these.

[0028] Recommendation information includes, for example, information regarding the recommended communication quality settings (QoS settings) at the predicted timing. Probability information includes information regarding the probability of setting the recommended communication quality settings (hereinafter also referred to as recommended settings) at the predicted timing.

[0029] Time information includes information about the time required to perform the recommended settings at the predicted timing. Connection destination evaluation information includes information about the evaluation of the destination cellular network. Parameter information includes information about parameters that can be set at the same time as the recommended settings.

[0030] The QoS server transmits future quality information to the AS (step S109). The AS transmits future quality information to the UE (step S110).

[0031] Based on future quality information, the UE determines the communication quality settings for when executing the application (step S111). As will be described later, the timing at which the UE executes the application may be at the predicted timing or at a different timing.

[0032] The UE sends a configuration notification to the AS containing configuration information regarding the determined communication quality settings (step S112). This configuration notification may be sent, for example, at the time the UE executes the application (hereinafter also referred to as the execution timing), or it may be sent in advance before the application is executed.

[0033] At the execution timing, the AS sends a request to the 5GC to set the desired communication quality based on the configuration information (step S113). The AS then executes the application with the UE using the communication quality set by the 5GC (step S114).

[0034] When the application execution is complete, the UE sends evaluation information (hereinafter also referred to as communication evaluation information) that evaluates the communication during the application execution to the AS (step S115).

[0035] The AS sends communication evaluation information to the QoS server (step S116). The QoS server generates, for example, destination evaluation information from the communication evaluation information.

[0036] In this explanation, we have used the example of having one AS, one UE, one QoS server, and one 5GC, but the number of AS, UE, QoS servers, and 5GCs is not limited to one. A communication system may have multiple AS, UE, QoS servers, and 5GCs.

[0037] Furthermore, some of the information processing described above (for example, the transmission of communication evaluation information) may be omitted. Also, in the information processing described above, the AS makes a request to the 5GC to set the desired communication quality, but the entity that sends this setting request is not limited to the AS.

[0038] For example, the QoS server may send a request to the 5GC to configure the desired communication quality in accordance with a request from the AS.

[0039] For example, suppose the UE sends a configuration notification to the AS before the execution timing. In this case, the AS notifies the 5GC of the configuration request directly or via the QoS server at the execution timing. Alternatively, the AS may request the QoS server to make a configuration request to the 5GC at the execution timing before the execution timing. In this way, the AS can reserve the desired communication quality settings with the QoS server.

[0040] As described above, the AS (Application System) related to this proposed technology is an information processing device that provides application services to a UE (an example of a terminal device). The AS acquires terminal information, including application information related to the application service, from the UE. Based on the terminal information, the AS predicts the timing at which the UE will make settings regarding communication quality in the future. The AS generates calculation information for calculating future quality information regarding communication quality that the UE may set at the predicted timing.

[0041] The QoS server can generate future quality information based on calculated data. Furthermore, the UE can determine the desired communication quality at application execution based on this future quality information. This allows the AS and UE to communicate with each other while more effectively guaranteeing the desired communication quality.

[0042] <<2. Example of Communication System Configuration>> <2-1. Example of Overall Communication System Configuration> Figure 2 is a block diagram showing an example of the overall configuration of a communication system according to the embodiment of this disclosure. The communication system shown in Figure 2 comprises a plurality of AS 100s, a QoS server 200, one or more 5G systems 30s, one or more base stations 400s, and one or more UEs 500s.

[0043] AS100 is an information processing device that provides application services to UE500. AS100 can be arranged in the communication system for each service provided to UE500. For example, AS100 provides various services such as Web conferencing services, game services, video distribution services, etc. to UE500.

[0044] In FIG. 2, as multiple AS100s, for example, AS100_1 and 100_2 are included in the communication system. Note that the number of AS100s is not limited to two and may be three or more.

[0045] Also, AS100 performs communication with specified (configured) QoS with UE500. AS100 communicates with UE500 via, for example, one or more 5G systems 30.

[0046] QoS server 200 is an information processing device that manages QoS settings configured between AS100 and UE500.

[0047] 5G system 30 includes 5GC300 and one or more base stations 400. 5GC300 is also referred to as NGC (NG CORE), or the core network. 5G system 30 is arranged for each PLMN (Public Land Mobile Network) operator that provides 5G services.

[0048] In FIG. 2, 5G systems 30_1 and 30_2 each provide 5G services to UE500. Note that the number of 5G systems 30 is not limited to two and may be one or three or more.

[0049] 5G system 30_1 includes 5GC300_1 and base stations 400_11 and 400_12. 5G system 30_2 includes 5GC300_2 and base stations 400_1 and 400_22. Note that the number of base stations 400 included in one 5G system 30 is not limited to two and may be one or three or more.

[0050] Furthermore, while it is assumed here that the cellular network connected to the UE500 is a 5G network, the cellular network may be a network other than 5G. For example, the communication system may include a system that provides wireless services such as LTE or 6G instead of the 5G system 30.

[0051] UE500 is an information processing device that receives application services from AS100 via 5G system 30. UE500 can be connected to one or more 5G systems 30.

[0052] In the example in Figure 2, UE500_1 connects to 5G system 30_1 via base station 400_11. UE500_2 connects to 5G system 30_1 via base station 400_12 and to 5G system 30_2 via base station 400_21. UE500_3 connects to 5G system 30_1 via base station 400_12 and to 5G system 30_2 via base station 400_22. Hereafter, UE500_1 may be referred to as the first UE500_1, UE500_2 as the second UE500_2, and UE500_3 as the third UE500_3.

[0053] Furthermore, the number of UE500s included in the communication system is not limited to three. The number of UE500s may be two or fewer, or four or more. Also, the number of UE500s connected to a single base station 400 is not limited to one or two. Three or more UE500s may be connected to a single base station 400.

[0054] Furthermore, the QoS server 200 may be a cloud server or an edge server. In Figure 2, the QoS server 200 is located outside the 5G system 30, but the QoS server 200 may also be located inside the 5G system 30. For example, the QoS server 200 may be implemented as a function of the 5GC 300 (e.g., PCF (Policy Control Function) or NSSF (Network Slice Selection Function)).

[0055] In this case, if there are multiple 5G systems 30, the QoS server 200 may be located in each of the multiple 5G systems 30. When the QoS server 200 is located in each of the multiple 5G systems 30, the AS 100 obtains future quality information for the 5G system 30 to which the QoS server 200 belongs from each QoS server 200. The AS 100 notifies the UE 500 of the future quality information obtained from each QoS server 200.

[0056] Furthermore, if AS100 makes a reservation for QoS settings to a QoS server 200, for example, it may make a reservation for QoS settings to a QoS server 200 belonging to the 5G system 30 used for communication with UE500.

[0057] <2-2. Example of Application Server Configuration> Figure 3 is a block diagram showing an example of the configuration of an application server (AS) 100 according to the present disclosure.

[0058] The AS100 shown in Figure 3 comprises a communication unit 110, a storage unit 120, and a control unit 130. The configuration shown in Figure 3 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the AS100 may be implemented in a distributed manner across multiple physically separated configurations. For example, the AS100 may be composed of multiple information processing devices.

[0059] (Communication Unit 110) The communication unit 110 is a communication interface for communicating with other devices. For example, the communication unit 110 is a network interface. For example, the communication unit 110 is a LAN (Local Area Network) interface such as a NIC (Network Interface Card). The communication unit 110 may be a wired interface or a wireless interface. The communication unit 110 communicates with the QoS server 200 and the 5GC 300 according to the control of the control unit 130.

[0060] (Storage Unit 120) The storage unit 120 is a data read / write storage device such as DRAM (Dynamic Random Access Memory), SRAM (Static Random Access Memory), flash memory, or hard disk.

[0061] The memory unit 120 shown in Figure 3 stores at least one of the following: AS registration information, terminal information, candidate information, category information, and communication evaluation information.

[0062] (AS Registration Information) AS registration information includes, for example, information regarding the priority of AS100 registered in 5GC300. Here, the priority of AS100 refers to the priority given to AS100 when setting communication quality (e.g., QoS) for 5GC300. In other words, the higher the priority included in the AS registration information, the more likely it is that the QoS requested by AS100 will be set in 5GC300.

[0063] (Terminal Information) Terminal information is information that AS100 obtains from UE500. Terminal information includes, for example, application information related to application services that AS100 provides to UE500, location information of UE500, and quality information related to the communication quality of UE500.

[0064] (Candidate Information) Candidate information is an example of the future quality information described above. Candidate information includes, for example, information regarding the communication quality between UE500 and AS100 (e.g., QoS settings). Candidate information may include, for example, at least one of recommendation information, probability information, time information, destination evaluation information, and parameter information.

[0065] Recommendation information includes, for example, recommended setting information regarding recommended settings at the prediction timing. Probability information includes setting probability information regarding the probability (setting probability) that the recommended settings can be set at the prediction timing.

[0066] Time information includes information about the time required to perform the recommended settings at the predicted timing. Connection destination evaluation information includes information about the evaluation of the destination cellular network. Parameter information includes information about parameters that can be set at the same time as the recommended settings.

[0067] (Category Information) Category information includes information indicating the category (type) of application services provided by AS100. Category information is, for example, information corresponding to applications such as web conferencing, games, and video streaming.

[0068] (Communication Evaluation Information) Communication evaluation information includes, for example, information evaluating the QoS set at the predicted timing. Communication evaluation information is information evaluating the communication between UE500 and AS100. For example, communication evaluation information includes evaluation results of the communication evaluated by UE500 while the application is being executed by UE500, in other words, while AS100 is providing application services to UE500.

[0069] Communication evaluation information may include, for example, a multi-level evaluation of communication between UE500 and AS100 (e.g., a three-level evaluation such as "Good," "Normal," and "Bad"). For example, communication evaluation information may include a qualitative evaluation of the user utilizing UE500.

[0070] Communication evaluation information may also include information indicating communication quality, such as average throughput or average (or maximum) latency. Thus, communication evaluation information may include quantitative evaluations.

[0071] (Control Unit 130) The control unit 130 is a controller (or control circuit) that controls each part of the AS100. The control unit 130 may be implemented by a processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

[0072] For example, the control unit 130 may be implemented by having the processor execute various programs stored in the internal storage device of the AS100 using RAM (Random Access Memory) or the like as a working area.

[0073] The control unit 130 may be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). Alternatively, the control unit 130 may be implemented by a GPU (Graphics Processing Unit).

[0074] A CPU, MPU, ASIC, FPGA, and GPU can all be considered controllers. The control unit 130 may be composed of multiple physically separate objects. For example, the control unit 130 may be composed of multiple semiconductor chips.

[0075] The control unit 130 comprises at least one block from among the registration unit 131, calculation unit 132, acquisition unit 133, request unit 134, and evaluation unit 135.

[0076] Each block (registration unit 131 to evaluation unit 135) that constitutes the control unit 130 is a functional block that indicates the function of the control unit 130. These functional blocks may be software blocks or hardware blocks.

[0077] For example, each of the above-mentioned functional blocks may be a single software module implemented in software (including a microprogram), or a single circuit block on a semiconductor chip (die). Of course, each functional block may also be a single processor or a single integrated circuit.

[0078] The control unit 130 may be composed of functional units different from the functional blocks described above. The configuration of the functional blocks is arbitrary.

[0079] (Registration Unit 131) The registration unit 131 requests registration (for example, setting a priority) from the 5GC300. The registration unit 131 comprises an application unit 1311 and a notification acquisition unit 1312.

[0080] The application unit 1311 requests (applies for) QoS setting authority from 5GC300, for example. The application unit 1311 requests (applies for) 5GC300 to set (or review) the priority of QoS settings.

[0081] The notification acquisition unit 1312 acquires, for example, notifications of the results of requests (examinations) for QoS setting authority and / or notifications of the results of setting (applications) for QoS setting priority from the 5GC300. The notification acquisition unit 1312 stores, for example, the acquired QoS setting authority and / or QoS setting priority as AS registration information in the storage unit 120.

[0082] (Calculation Unit 132) The calculation unit 132 acquires terminal information from the UE 500 and calculates calculation information based on the terminal information. The calculation unit 132 comprises a terminal information acquisition unit 1321, a prediction unit 1322, and a calculation information transmission unit 1323.

[0083] The terminal information acquisition unit 1321 acquires terminal information from the UE 500 via the communication unit 110. The terminal information acquisition unit 1321 stores the acquired terminal information in the storage unit 120.

[0084] The prediction unit 1322 predicts, for example, the timing (predicted timing) when the UE 500 will execute the application, based on terminal information. The prediction unit 1322 may also predict, for example, the location (location) where the UE 500 will execute the application. This predicted timing and predicted location (hereinafter also referred to as predicted location) will also be referred to as prediction information.

[0085] Furthermore, the prediction unit 1322 generates calculation information that includes prediction information. The calculation information includes prediction information and / or category information relating to the application category. The category information is, for example, stored in the storage unit 120 beforehand.

[0086] The calculation information transmission unit 1323 transmits the calculation information to the QoS server 200.

[0087] (Acquisition Unit 133) The acquisition unit 133 acquires candidate information from the QoS server 200 and transmits it to the UE 500. The acquisition unit 133 comprises a candidate information acquisition unit 1331 and a candidate information transmission unit 1332.

[0088] The candidate information acquisition unit 1331 acquires candidate information from the QoS server 200 via the communication unit 110. The candidate information acquisition unit 1331 stores the acquired candidate information in the storage unit 120.

[0089] The candidate information transmission unit 1332 transmits the candidate information obtained from the QoS server 200 to the UE 500.

[0090] (Request Unit 134) The Request Unit 134 requests QoS settings from 5GC300, for example, in accordance with a request from UE500. The Request Unit 134 comprises a setting notification acquisition unit 1341 and a quality setting request unit 1342.

[0091] The configuration notification acquisition unit 1341 acquires a configuration notification from the UE 500 via the communication unit 110. The configuration notification includes information regarding the QoS settings requested by the UE 500.

[0092] The quality setting request unit 1342 requests QoS settings from the 5GC300 in accordance with the setting notification. If the setting notification is received at the time when the application is actually executed, the quality setting request unit 1342 requests QoS settings from the 5GC300 at the time the setting notification is received.

[0093] If a configuration notification is received before the application is executed, the quality setting request unit 1342 requests the 5GC300 to configure QoS settings at the time the application is executed. Alternatively, in this case, the quality setting request unit 1342 may reserve a QoS configuration request at the execution time with the QoS server 200.

[0094] Alternatively, the quality setting request unit 1342 may notify the QoS setting request to the QoS server 200 instead of the 5GC 300.

[0095] (Evaluation Unit 135) The evaluation unit 135 acquires communication evaluation information from the UE 500 and notifies the QoS server 200. The evaluation unit 135 comprises an evaluation acquisition unit 1351 and an evaluation transmission unit 1352.

[0096] For example, when communication with UE500 ends, the evaluation acquisition unit 1351 acquires communication evaluation information from UE500 regarding the terminated communication. The evaluation acquisition unit 1351 stores the acquired communication evaluation information in the storage unit 120.

[0097] The evaluation transmission unit 1352 transmits the communication evaluation information to the QoS server 200.

[0098] <2-3. Example of QoS Server Configuration> Figure 4 is a block diagram showing an example of the configuration of a QoS server 200 according to the present disclosure. The QoS server 200 shown in Figure 4 comprises a communication unit 210, a storage unit 220, and a control unit 230. The configuration shown in Figure 4 is a functional configuration, and the hardware configuration may differ from this. Furthermore, the functions of the QoS server 200 may be implemented in a distributed manner across multiple physically separated configurations. For example, the QoS server 200 may be composed of multiple information processing devices.

[0099] (Communication Unit 210) The communication unit 210 is a communication interface for communicating with other devices. For example, the communication unit 210 is a network interface. For example, the communication unit 210 is a LAN interface for a NIC, etc. The communication unit 210 may be a wired interface or a wireless interface. The communication unit 210 communicates with AS100 and 5GC300 according to the control of the control unit 230.

[0100] (Storage Unit 220) The storage unit 220 is a data read / write storage device such as DRAM, SRAM, flash memory, or hard disk.

[0101] The memory unit 220 shown in Figure 4 stores at least one of the following: candidate information, AS priority correspondence table, parameter correspondence table, connection destination correspondence table, QoS correspondence table, setting upper limit correspondence table, setting delay information, and connection destination evaluation information.

[0102] (Candidate Information) Candidate information is an example of the future quality information described above. Candidate information includes, for example, information regarding the communication quality between UE500 and AS100 (e.g., QoS settings). Candidate information may include, for example, at least one of the recommendation information, probability information, time information, destination evaluation information, and parameter information described above.

[0103] (AS Priority Correspondence Table) The AS Priority Correspondence Table holds information that associates multiple AS100s with the priority of each AS100.

[0104] (Parameter Correspondence Table) The parameter correspondence table holds information that associates parameter information related to the parameters that can be set on the 5GC300 with the 5GC300 itself. Examples of parameter information include t-reordering and RLC mode.

[0105] (Connection Destination Correspondence Table) The connection destination correspondence table holds information that associates base station 400 with the communication area of ​​base station 400.

[0106] (QoS Correspondence Table) The QoS correspondence table holds information that associates category information with QoS settings. Category information indicates the category of application services provided by AS100. In other words, the QoS correspondence table holds the desired QoS settings for each application category when an application is executed.

[0107] Note that multiple categories may be assigned to a single application service. Alternatively, multiple QoS levels may be associated with a single category.

[0108] (Setting Limit Correspondence Table) The setting limit correspondence table holds the upper limits of possible settings for each base station 400. For example, possible settings for base station 400 include the number of connectable UEs and the type of QoS (e.g., 5QI).

[0109] (Setting delay information) Setting delay information is the delay time from when a QoS setting is requested from the 5GC300 until the QoS setting is actually reflected, that is, information indicating the setting time required for QoS setting in the 5GC300. The setting delay time can be stored for each 5GC300.

[0110] (Connection destination evaluation information) Connection destination evaluation information is information that shows communication evaluation information for each connection destination. The connection destinations include at least one of the following: PLMN operator (MNO (Mobile Network Operator)), 5GC300, and base station 400.

[0111] (Control Unit 230) The control unit 230 is a controller (or control circuit) that controls each part of the QoS server 200. The control unit 230 may be implemented by a processor such as a CPU or MPU.

[0112] For example, the control unit 230 may be implemented by having the processor execute various programs stored in the internal storage device of the QoS server 200 using RAM or the like as a working area.

[0113] The control unit 230 may be implemented by an integrated circuit such as an ASIC or FPGA. Alternatively, the control unit 230 may be implemented by a GPU.

[0114] A CPU, MPU, ASIC, FPGA, and GPU can all be considered controllers. The control unit 230 may be composed of multiple physically separate objects. For example, the control unit 230 may be composed of multiple semiconductor chips.

[0115] The control unit 230 includes at least one block from among the acquisition unit 231, the calculation unit 232, and the notification unit 233.

[0116] Each block (acquisition unit 231 to notification unit 233) that constitutes the control unit 230 is a functional block that indicates the function of the control unit 230. These functional blocks may be software blocks or hardware blocks.

[0117] For example, each of the above-mentioned functional blocks may be a single software module implemented in software (including a microprogram), or a single circuit block on a semiconductor chip (die). Of course, each functional block may also be a single processor or a single integrated circuit.

[0118] The control unit 230 may be composed of functional units different from the functional blocks described above. The configuration of the functional blocks is arbitrary.

[0119] (Acquisition Unit 231) The acquisition unit 231 acquires various information from the AS 100 and / or the 5GC 300. For example, the acquisition unit 231 acquires calculation information and communication evaluation information from the AS 100. The acquisition unit 231 also acquires the AS priority correspondence table, parameter correspondence table, connection destination correspondence table, QoS correspondence table, setting upper limit correspondence table, and setting delay information.

[0120] The acquisition unit 231 may also acquire parameter correspondence tables, connection destination correspondence tables, QoS correspondence tables, setting upper limit correspondence tables, etc., in advance from the PLMN operator (MNO). The information acquired in advance from the PLMN operator (MNO) in this manner is collectively referred to as pre-shared information.

[0121] Furthermore, the acquisition unit 231 may acquire network information from the 5GC 300. The network information includes information about the current and / or future network. For example, the network information includes information about the current status of the QoS server 200 settings and / or information indicating the congestion level of each base station 400. The network information also includes predicted values ​​that predict the future congestion level of each base station 400. The network information acquired by the acquisition unit 231 may be stored in the storage unit 220.

[0122] (Calculation Unit 232) The calculation unit 232 performs various calculations to generate information such as candidate information.

[0123] For example, the calculation unit 232 generates candidate information using information obtained from 5GC300 such as network information and PLMN operators, and / or information obtained from AS100 such as calculation information.

[0124] For example, the calculation unit 232 generates connection destination evaluation information as one of the candidate information. The calculation unit 232 calculates statistical information of the communication evaluation information obtained from AS 100 for each connection destination (e.g., PLMN operator, 5GC 300 and / or base station 400). Examples of statistical information include the average value, maximum value, and minimum value of the communication evaluation information.

[0125] (Notification Unit 233) The notification unit 233 notifies the AS 100 of the candidate information calculated by the calculation unit 232. In other words, the notification unit 233 is a disclosure unit that makes the candidate information public to the AS 100.

[0126] <2-4.5GC Configuration Example> Figure 5 is a block diagram showing a configuration example of a 5GC300 according to the present disclosure. In Figure 5, the configuration of the 5GC300 that performs a part of the information processing described above will be explained, and the illustration and explanation of the functional configuration for providing cellular communication services will be omitted.

[0127] As shown in Figure 5, the 5GC300 comprises a communication unit 310, a storage unit 320, and a control unit 330. The configuration shown in Figure 5 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the 5GC300 may be implemented in a distributed manner across multiple physically separated configurations. For example, the 5GC300 may be composed of multiple information processing devices.

[0128] (Communication Unit 310) The communication unit 310 is a communication interface for communicating with other devices. For example, the communication unit 310 is a network interface. For example, the communication unit 310 is a LAN interface for a NIC, etc. The communication unit 310 may be a wired interface or a wireless interface. The communication unit 310 communicates with the AS 100 and the QoS server 200 according to the control of the control unit 330.

[0129] (Storage Unit 320) The storage unit 320 is a data read / write storage device such as DRAM, SRAM, flash memory, or hard disk.

[0130] The storage unit 320 shown in Figure 5 stores at least one of the following: AS registration information, registration application history, and network information. At least one of the AS registration information, registration application history, and network information may be stored in an external storage device of the 5GC300.

[0131] (AS Registration Information) AS registration information includes, for example, information regarding the priority of AS100. This priority is registered, for example, according to a request (application) from AS100. Here, the priority of AS100 refers to the priority given to AS100 when setting communication quality (e.g., QoS) for 5GC300. In other words, the higher the priority included in the AS registration information, the more likely it is that the QoS requested by AS100 will be set in 5GC300.

[0132] (Registration Application History) The registration application history includes information regarding requests (applications) for priority setting from AS100. The registration application history includes, for example, at least one of the following: device information relating to the AS100 that made the application, the results of the examination conducted in response to the application, and information regarding the date and time the application was made.

[0133] (Network Information) Network information includes information about the current and / or future network. For example, network information includes information about the current configuration status of the QoS server 200 and / or information indicating the congestion level of each base station 400. Network information also includes predicted values ​​that forecast the future congestion level of each base station 400.

[0134] (Control Unit 330) The control unit 330 is a controller (or control circuit) that controls each part of the 5GC300. The control unit 330 may be implemented by a processor such as a CPU or MPU.

[0135] For example, the control unit 330 may be implemented by the processor executing various programs stored in the internal memory of the 5GC300 using RAM or the like as a working area.

[0136] The control unit 330 may be implemented by an integrated circuit such as an ASIC or FPGA. Alternatively, the control unit 330 may be implemented by a GPU.

[0137] A CPU, MPU, ASIC, FPGA, and GPU can all be considered controllers. The control unit 330 may be composed of multiple physically separate objects. For example, the control unit 330 may be composed of multiple semiconductor chips.

[0138] The control unit 330 comprises at least one block from among the AS management unit 331 and the generation unit 332.

[0139] Each block constituting the control unit 330 (AS management unit 331 and generation unit 332) is a functional block that represents the function of the control unit 330. These functional blocks may be software blocks or hardware blocks.

[0140] For example, each of the above-mentioned functional blocks may be a single software module implemented in software (including a microprogram), or a single circuit block on a semiconductor chip (die). Of course, each functional block may also be a single processor or a single integrated circuit.

[0141] The control unit 330 may be composed of functional units different from the functional blocks described above. The configuration of the functional blocks is arbitrary. For example, the AS management unit 331 may be implemented as a function of an external device of the 5GC300.

[0142] (AS Management Unit 331) The AS Management Unit 331 manages the AS 100. For example, the AS Management Unit 331 manages the priority of the AS 100. In response to a request (application) from the AS 100, the AS Management Unit 331 reviews the priority of the AS 100 and decides whether or not to grant the request (application).

[0143] The AS management unit 331 comprises a reception unit 3311, an examination unit 3312, and a notification unit 3313.

[0144] The reception unit 3311 receives an application (request) for priority setting from AS 100. The review unit 3312 reviews whether or not to set the priority requested by AS 100. The notification unit 3313 notifies AS 100 of the review results by the review unit 3312. The review results include, for example, priority information related to the set (registered) priority.

[0145] (Generation Unit 332) The generation unit 332 generates network information. The generation unit 332 comprises an information generation unit 3321 and an information notification unit 3322.

[0146] The information generation unit 3321 generates network information. The information generation unit 3321 may also generate information other than network information (for example, an AS priority correspondence table, a parameter correspondence table, a connection destination correspondence table, a QoS correspondence table, a setting upper limit correspondence table, and setting delay information, etc.). For example, the information generation unit 3321 may measure the time it takes to actually set up QoS and use the measured result (or statistical information such as the average value of the measured result) as setting delay information.

[0147] The information notification unit 3322 notifies the QoS server 200 of the information generated by the information generation unit 3321, such as network information.

[0148] <2-5. Example of Base Station Configuration> The base station 400 is a communication device that operates a cell and provides wireless communication services to one or more UE500 located within the cell's coverage. The cell operates according to any wireless communication method, such as LTE or NR. The base station 400 is connected to a core network (e.g., 5GC300). The core network (e.g., 5GC300) is connected to a packet data network via a gateway device. The base station 400 also operates beams identifiable by SSB (Synchronization Signal / PBCH Block) and transmits and receives data to and from one or more UE500 via one or more beams.

[0149] The base station 400 may be composed of a collection of multiple physical or logical devices. For example, in the embodiments of this disclosure, the base station 400 may be distinguished into multiple devices of BBU (Baseband Unit) and RU (Radio Unit), and may be interpreted as a collection of these multiple devices. Furthermore or alternatively, in the embodiments of this disclosure, the base station 400 may be either or both of the BBU and RU. The BBU and RU may be connected by a predetermined interface (e.g., eCPRI). Furthermore or alternatively, the RU may be referred to as a Remote Radio Unit (RRU) or Radio DoT (RD). Furthermore or alternatively, the RU may correspond to a gNB-DU described later. Furthermore or alternatively, the BBU may correspond to a gNB-CU described later. Alternatively, the RU may be connected to a gNB-DU described later. Furthermore, the BBU may correspond to a combination of gNB-CU and gNB-DU described later. Furthermore or alternatively, the RU may be a device formed integrally with an antenna. The antenna of the base station 400 (for example, an antenna integrally formed with the RU) may employ an Advanced Antenna System and support MIMO (for example, FD-MIMO) and beamforming. The Advanced Antenna System may include, for example, 64 transmitting antenna ports and 64 receiving antenna ports.

[0150] Furthermore, multiple base stations 400 may be connected to one another. One or more base stations 400 may be included in a Radio Access Network (RAN). That is, base stations 400 may simply be referred to as RAN, RAN node, AN (Access Network), or AN node. In LTE, a RAN is called EUTRAN (Enhanced Universal Terrestrial RAN). In NR, a RAN is called NGRAN. In W-CDMA (UMTS), a RAN is called UTRAN. An LTE base station 400 is referred to as eNodeB (Evolved Node B) or eNB. That is, EUTRAN includes one or more eNodeB (eNB). Also, an NR base station 400 is referred to as gNodeB or gNB. That is, NGRAN includes one or more gNB. Furthermore, EUTRAN may include a gNB (en-gNB) connected to the core network (EPC) in an LTE communication system (EPS). Similarly, NGRAN may include an ng-eNB connected to the core network 5GC in a 5G communication system (5GS). Furthermore, or alternatively, if the base station 400 is an eNB, gNB, etc., it may be referred to as 3GPP® Access. Furthermore, or alternatively, if the base station 400 is a radio access point (e.g., a Wi-Fi® access point), it may be referred to as Non-3GPP Access. Furthermore, or alternatively, the base station 400 may be an optical extension device called an RRH (Remote Radio Head). Furthermore, or alternatively, if the base station 400 is a gNB, the base station 400 may be referred to as a combination of the aforementioned gNB CU (Central Unit) and gNB DU (Distributed Unit), or either of these. The gNB CU (Central Unit) hosts multiple upper layers of the Access Stratum (e.g., RRC, SDAP, PDCP) for communication with the UE500.On the other hand, the gNB-DU hosts several lower layers of the Access Stratum (e.g., RLC, MAC, PHY). That is, among the messages and information described later, RRC signalling (e.g., MIB, various SIBs including SIB1, RRCSetup message, RRCReconfiguration message) may be generated by the gNB CU, while DCI and various Physical Channels (e.g., PDCCH, PBCH) described later may be generated by the gNB-DU. Alternatively, among the RRC signalling, some configuration information, such as IE:cellGroupConfig, may be generated by the gNB-DU, and the remaining configuration information may be generated by the gNB-CU. These configurations may be transmitted and received via the F1 interface described later. Base station 400 may be configured to communicate with other base stations 400. For example, if multiple base stations 400 are eNBs or a combination of eNB and en-gNB, the base stations 400 may be connected via the X2 interface. Furthermore, or alternatively, if the multiple base stations 400 are gNBs or a combination of ng-eNB and gNB, the devices may be connected via the Xn interface. Furthermore, or alternatively, if the multiple base stations 400 are a combination of gNB CU (Central Unit) and gNB DU (Distributed Unit), the devices may be connected via the F1 interface described above. The messages and information described later (RRC signalling or DCI information, Physical Channel) may be communicated between the multiple base stations 400 (for example, via the X2, Xn, and F1 interfaces).

[0151] Furthermore, as mentioned above, the base station 400 may be configured to manage multiple cells. The cells provided by the base station 400 are called Serving cells. A Serving cell includes PCells (Primary Cells) and SCells (Secondary Cells). When Dual Connectivity (e.g., EUTRA-EUTRA Dual Connectivity, EUTRA-NR Dual Connectivity (ENDC), EUTRA-NR Dual Connectivity with 5GC, NR-EUTRA Dual Connectivity (NEDC), NR-NR Dual Connectivity) is provided to the UE500, the PCells and zero or more SCell(s) provided by the MN (Master Node) are called the Master Cell Group. Furthermore, a Serving cell may also include PSCells (Primary Secondary Cells or Primary SCG Cells). That is, when Dual Connectivity is provided to the UE500, the PSCells and zero or more SCell(s) provided by the SN (Secondary Node) are called the Secondary Cell Group (SCG). Unless otherwise specified (e.g., PUCCH on SCell), the physical uplink control channel (PUCCH) is transmitted by PCell and PSCell, but not by SCell. Similarly, Radio Link Failure is detected by PCell and PSCell, but not by SCell (and does not need to be detected). Because PCell and PSCell have special roles within a Serving Cell(s), they are also called Special Cells (SpCells). A single cell may be associated with one Downlink Component Carrier and one Uplink Component Carrier. Furthermore, the system bandwidth corresponding to a single cell may be divided into multiple Bandwidth Parts.In this case, one or more Bandwidth Parts (BWPs) may be configured for the UE500, and one Bandwidth Part may be used for the UE500 as the Active BWP. Furthermore, the radio resources available to the UE500 (e.g., frequency band, numerology (subcarrier spacing), slot format) may differ for each cell, component carrier, or BWP.

[0152] Figure 6 shows an example configuration of a base station 400 according to the first embodiment of this disclosure. The base station 400 is a communication device (wireless system) that communicates wirelessly with the UE 500. The base station 400 is a type of information processing device.

[0153] The base station 400 comprises a communication unit 410, a storage unit 420, a network communication unit 430, and a control unit 440. Note that the configuration shown in Figure 6 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the base station 400 may be distributed and implemented across multiple physically separated devices. For example, as mentioned above, the functions of the base station 400 may be distributed across a CU and a DU, or a CU, a DU, and a RU.

[0154] The communication unit 410 is a wireless communication interface (signal processing unit) that communicates wirelessly with other communication devices (e.g., UE500 and other base stations 400). The communication unit 410 is a wireless transceiver that operates according to the control of the control unit 440. The communication unit 410 may support multiple wireless access methods. For example, the communication unit 410 may support both NR and LTE. The communication unit 410 may also support other cellular communication methods such as W-CDMA and cdma2000. In addition to cellular communication methods, the communication unit 410 may also support wireless LAN communication methods. Of course, the communication unit 410 may only support one wireless access method.

[0155] The communication unit 410 includes a receiving processing unit 411, a transmitting processing unit 412, and an antenna 413. The communication unit 410 may have multiple receiving processing units 411, transmitting processing units 412, and antennas 413. If the communication unit 410 supports multiple wireless access methods, each part of the communication unit 410 may be configured separately for each wireless access method. For example, if the base station 400 supports NR and LTE, the receiving processing unit 411 and the transmitting processing unit 412 may be configured separately for NR and LTE.

[0156] The receiving processing unit 411 processes the uplink signal received via the antenna 413. The receiving processing unit 411 comprises a wireless receiving unit 411a, a multiplexing / decoupling unit 411b, a demodulation unit 411c, and a decoding unit 411d.

[0157] The wireless receiver 411a performs down-conversion, removal of unwanted frequency components, amplification level control, quadrature demodulation, conversion to a digital signal, removal of guard intervals, and extraction of frequency domain signals by fast Fourier transform on the uplink signal. For example, suppose the wireless access method of the base station 400 is a cellular communication method such as LTE. In this case, the multiplexing / decoupling unit 411b separates the uplink channel and uplink reference signal, such as PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel), from the signal output from the wireless receiver 411a. The demodulation unit 411c demodulates the received signal using modulation methods such as BPSK (Binary Phase Shift Keying) and QPSK (Quadrature Phase Shift Keying) for the modulation symbols of the uplink channel. The modulation scheme used by the demodulation unit 411c may be a multi-level QAM such as 16QAM (Quadrature Amplitude Modulation), 64QAM, or 256QAM. The decoding unit 411d performs decoding on the encoded bits of the demodulated uplink channel. The decoded uplink data and uplink control information are output to the control unit 440.

[0158] The transmission processing unit 412 performs the transmission processing of downlink control information and downlink data. The transmission processing unit 412 comprises an encoding unit 412a, a modulation unit 412b, a multiplexing unit 412c, and a wireless transmission unit 412d.

[0159] The encoding unit 412a encodes the downlink control information and downlink data input from the control unit 440 using encoding methods such as block encoding, convolutional encoding, and turbo encoding. Here, encoding may be performed using polar code or LDPC (Low Density Parity Check Code). The modulation unit 412b modulates the encoded bits output from the encoding unit 412a using a predetermined modulation method such as BPSK, QPSK, 16QAM, 64QAM, or 256QAM. The multiplexing unit 412c multiplexes the modulation symbols and downlink reference signals for each channel and places them in predetermined resource elements. The wireless transmission unit 412d performs various signal processing on the signals from the multiplexing unit 412c. For example, the wireless transmission unit 412d performs processing such as conversion to the frequency domain using the Fast Fourier Transform, addition of guard intervals, generation of baseband digital signals, conversion to analog signals, quadrature modulation, upconversion, removal of extraneous frequency components, and power amplification. The signal generated by the transmission processing unit 412 is transmitted from the antenna 413.

[0160] The memory unit 420 is a data read / write storage device such as DRAM, SRAM, flash memory, or hard disk. The memory unit 420 functions as a storage means for the base station 400.

[0161] The network communication unit 430 is a communication interface for communicating with other devices (for example, 5GC300 and other base stations 400). For example, the network communication unit 430 is a LAN interface such as a NIC. The network communication unit 430 may also be a USB interface consisting of a USB host controller, a USB port, etc. Furthermore, the network communication unit 430 may be a wired interface or a wireless interface. The network communication unit 430 functions as a network communication means for the base station 400. The network communication unit 430 communicates with other devices according to the control of the control unit 440.

[0162] The control unit 440 is a controller that controls various parts of the base station 400. The control unit 440 is implemented by a processor such as a CPU, MPU, or GPU. For example, the control unit 440 is implemented by the processor executing various programs stored in the memory device inside the base station 400 using RAM or the like as a working area. The control unit 440 may also be implemented by an integrated circuit such as an ASIC or FPGA. A CPU, MPU, GPU, ASIC, and FPGA can all be considered controllers.

[0163] <2-6. Example of UE Configuration> UE500 is a wireless communication device that communicates wirelessly with, for example, the base station 400. UE500 can be, for example, a mobile phone, a smart device (smartphone or tablet), a PDA (Personal Digital Assistant), or a personal computer. UE500 may also be a wearable device such as a head-mounted display, VR goggles, or smart glasses that has the function of sending and receiving data wirelessly. Alternatively, UE500 may be a mobile terminal such as a portable game console.

[0164] Furthermore, the UE500 may be capable of sidelink communication with other UE500s. When performing sidelink communication, the UE500 may be able to use automatic retransmission technology such as HARQ (Hybrid Automatic Repeat reQuest). The UE500 may be capable of NOMA (Non Orthogonal Multiple Access) communication with the base station 400. In addition, the UE500 may be capable of NOMA communication in communication (sidelink) with other UE500s. Furthermore, the UE500 may be capable of LPWA (Low Power Wide Area) communication with other communication devices (e.g., the base station 400 and other UE500s). In addition, the wireless communication used by the UE500 may be wireless communication using millimeter waves. Furthermore, the wireless communication used by the UE500 (including sidelink communication) may be wireless communication using radio waves, or wireless communication using infrared or visible light (optical wireless).

[0165] The UE500 may simultaneously connect to and communicate with multiple base stations 400 or multiple cells. For example, if one base station 400 can provide multiple cells, the UE500 can perform carrier aggregation by using one cell as a PCell and other cells as SCells. Also, if multiple base stations 400 can each provide one or more cells, the UE500 can achieve Dual Connectivity (DC) by using one or more cells managed by one base station 400 (MN (e.g., MeNB or MgNB)) as a PCell, or a PCell and SCell(s), and one or more cells managed by the other base station 400 (SN (e.g., SeNB or SgNB)) as a PCell (PSCell), or a PCell (PSCell) and SCell(s). DC may also be referred to as Multi Connectivity (MC).

[0166] Furthermore, when the communication area is supported via cells from different base stations 400 (multiple cells with different cell identifiers or the same cell identifier), it is possible to combine these multiple cells and communicate between the base station 400 and the UE 500 using carrier aggregation (CA), dual connectivity (DC), or multi-connectivity (MC) technologies. Alternatively, it is also possible for the UE 500 to communicate with these multiple base stations 400 via cells from different base stations 400 using coordinated multi-point transmission and reception (CoMP) technology.

[0167] An example of the configuration of UE500 according to an embodiment of this disclosure will be described using Figure 7. Figure 7 is a block diagram showing an example of the configuration of UE500 according to the first embodiment of this disclosure.

[0168] The UE500 comprises a communication unit 510, a storage unit 520, a network communication unit 530, an input / output unit 540, and a control unit 550. Note that the configuration shown in Figure 7 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the UE500 may be distributed and implemented across multiple physically separated configurations.

[0169] (Communication Unit 510) The communication unit 510 is a signal processing unit for wireless communication with other wireless communication devices (for example, the base station 400 and other UE 500). The communication unit 510 operates according to the control of the control unit 550. The communication unit 510 may be a wireless transceiver that supports one or more wireless access schemes. For example, the communication unit 510 supports both NR and LTE. In addition to NR and LTE, the communication unit 510 may also support W-CDMA and cdma2000. Furthermore, the communication unit 510 may also support communication using NOMA.

[0170] The communication unit 510 includes a receiving processing unit 511, a transmitting processing unit 512, and an antenna 513. The communication unit 510 may have multiple receiving processing units 511, transmitting processing units 512, and antennas 513. The configuration of the communication unit 510, receiving processing unit 511, transmitting processing unit 512, and antenna 513 is the same as that of the communication unit 410, receiving processing unit 411, transmitting processing unit 412, and antenna 413 of the base station 400.

[0171] (Storage Unit 520) The storage unit 520 is a data read / write storage device such as DRAM, SRAM, flash memory, or hard disk. The storage unit 520 functions as a storage means for the UE 500.

[0172] The memory unit 520 shown in Figure 7 stores terminal information and at least one of candidate information.

[0173] (Terminal Information) Terminal information is information that UE500 transmits to AS100. Terminal information includes, for example, application information related to application services provided by AS100 to UE500, location information of UE500, and quality information related to the communication quality of UE500. UE500 collects information from various parts, such as sensors, to generate terminal information and stores it in the storage unit 520.

[0174] (Candidate Information) Candidate information is an example of the future quality information described above. Candidate information includes, for example, information regarding the communication quality between UE500 and AS100 (e.g., QoS settings). Candidate information may include, for example, at least one of recommendation information, probability information, time information, destination evaluation information, and parameter information.

[0175] The candidate information stored in the memory unit 520, that is, the candidate information acquired by the UE 500, may be the same as or different from the candidate information acquired by the AS 100 from the QoS server 200. For example, the AS 100 may notify the UE 500 of all of the candidate information acquired from the QoS server 200, or it may notify the UE 500 of only a portion of the acquired candidate information.

[0176] (Network Communication Unit 530) The network communication unit 530 is a communication interface for communicating with other devices connected via a network. For example, the network communication unit 530 is a LAN interface such as a NIC. The network communication unit 530 may be a wired interface or a wireless interface. The network communication unit 530 functions as a network communication means for the UE 500. The network communication unit 530 communicates with other devices according to the control of the control unit 550.

[0177] (Input / Output Unit 540) The input / output unit 540 is a user interface for exchanging information with the user. For example, the input / output unit 540 is an operating device for the user to perform various operations, such as a keyboard, mouse, operation keys, or touch panel. Alternatively, the input / output unit 540 is a display device such as a liquid crystal display or an organic electroluminescence display. The input / output unit 540 may also be an audio device such as a microphone, speaker, or buzzer. Furthermore, the input / output unit 540 may also be a lighting device such as an LED (Light Emitting Diode) lamp. The input / output unit 540 functions as an input / output means (input means, output means, operation means, or notification means) of the UE 500. For example, if the UE 500 is a sensor, the input / output unit 540 may be omitted.

[0178] (Control Unit 550) The control unit 550 is a controller that controls each part of the UE500. The control unit 550 is implemented by a processor such as a CPU, MPU, or GPU. For example, the control unit 550 is implemented by the processor executing various programs stored in the memory device inside the UE500 using RAM or the like as a working area. The control unit 550 may also be implemented by an integrated circuit such as an ASIC or FPGA. A CPU, MPU, GPU, ASIC, and FPGA can all be considered as controllers.

[0179] The control unit 550 comprises at least one block from among the terminal information unit 551, the QoS information unit 552, and the evaluation unit 553.

[0180] Each block constituting the control unit 550 (terminal information unit 551 to evaluation unit 553) is a functional block that indicates the function of the control unit 550. These functional blocks may be software blocks or hardware blocks.

[0181] For example, each of the above-mentioned functional blocks may be a single software module implemented in software (including a microprogram), or a single circuit block on a semiconductor chip (die). Of course, each functional block may also be a single processor or a single integrated circuit.

[0182] The control unit 550 may be composed of functional units different from the functional blocks described above. The configuration of the functional blocks is arbitrary.

[0183] (Terminal Information Unit 551) The terminal information unit 551 generates and transmits terminal information. The terminal information unit 551 comprises an information generation unit 5511 and an information transmission unit 5512.

[0184] The information generation unit 5511 collects application information from applications running on the UE500, for example. The information generation unit 5511 can also acquire location information of the UE500 using GNSS (Global Navigation Satellite System) sensors or the like installed on the UE500. Furthermore, the information generation unit 5511 can measure the communication quality of the communication unit 510 and generate communication information.

[0185] The information generation unit 5511 generates terminal information from the collected information, etc.

[0186] (Information transmission unit 5512) The information transmission unit 5512 notifies the AS 100 of the terminal information generated by the information generation unit 3321 via the communication unit 510.

[0187] (QoS Information Unit 552) The QoS Information Unit 552 acquires candidate information and requests QoS settings. The QoS Information Unit 552 comprises an information acquisition unit 5521 and a QoS request unit 5522.

[0188] (Information Acquisition Unit 5521) The information acquisition unit 5521 acquires candidate information from AS100. The information acquisition unit 5521 may present the acquired candidate information to the user via the input / output unit 540. For example, the information acquisition unit 5521 may present the candidate information to the user at the time the candidate information is acquired. Alternatively, the information acquisition unit 5521 may present the candidate information to the user at the time the application is executed, or at a time specified by the user.

[0189] Alternatively, the information acquisition unit 5521 may present candidate information to the user at a timing corresponding to the predicted timing. For example, the information acquisition unit 5521 may present candidate information to the user a predetermined period (e.g., one day or several hours) before the predicted timing. The predetermined period may be determined by the information acquisition unit 5521, for example, according to the candidate information.

[0190] For example, the predetermined period may be determined by the information acquisition unit 5521 according to the probability of setting the recommended setting at the prediction timing. For example, the information acquisition unit 5521 may set the predetermined period to be longer when the setting probability is low compared to when it is high.

[0191] For example, as will be discussed later, if the setting probability is low, the timing of when the application is executed (e.g., the start time of an online meeting) may be changed. Alternatively, the location where the application is executed may be changed.

[0192] Therefore, if the setting probability is low, the information acquisition unit 5521 notifies the user of candidate information at an early stage. This allows the user to take measures other than QoS settings (for example, changing movement or execution timing) to improve the communication quality of the UE500 during application execution with ample time to spare.

[0193] (QoS Request Unit 5522) The QoS Request Unit 5522 requests the AS 100 to set up QoS, for example, in accordance with instructions from the user. The QoS Request Unit 5522 requests the AS 100 to set up QoS, selected (instructed) by the user, for example, in accordance with candidate information presented by the Information Acquisition Unit 5521.

[0194] The QoS request unit 5522 may request the QoS settings from AS 100 at the time the user selects the QoS settings according to the candidate information, or it may request the QoS settings from AS 100 at the time instructed by the user.

[0195] Alternatively, the QoS request unit 5522 may request AS 100 to set QoS at a timing corresponding to the predicted timing. For example, the QoS request unit 5522 may request AS 100 to set QoS a predetermined period (e.g., one day, several hours, several seconds, etc.) before the predicted timing. The predetermined period may be determined by the QoS request unit 5522 according to the candidate information, for example.

[0196] For example, the predetermined period may be determined by the QoS request unit 5522 according to the probability of setting the recommended setting at the predicted timing. For example, the QoS request unit 5522 may set the predetermined period to be longer when the setting probability is low compared to when it is high.

[0197] For example, the QoS request unit 5522 can reserve QoS settings by requesting them from the AS 100 before the application is executed (for example, at a time before the initial period of the predicted timing). This allows the UE 500 to communicate with the desired QoS settings more reliably.

[0198] Alternatively, the predetermined period may be determined by the QoS request unit 5522 according to the setting delay information. For example, the QoS request unit 5522 sets the setting delay time of the setting delay information of the candidate information as the predetermined period. This allows the UE 500 to communicate with the desired QoS settings more reliably at the application execution timing.

[0199] (Evaluation Unit 553) The evaluation unit 553 generates communication evaluation information and notifies the AS 100. For example, when communication with the AS 100 ends, the evaluation unit 553 evaluates the communication while the application is running on the UE 500, in other words, while the AS 100 is providing application services to the UE 500, and generates communication evaluation information. The evaluation unit 553 notifies the AS 100 of the communication evaluation information.

[0200] <<3. Example of Communication System Operation>> <3-1. AS Priority Assignment> First, we will explain an example of a priority assignment method for assigning a priority to each of the multiple AS100s. As mentioned above, the priority of the AS100 here refers to the priority when requesting QoS settings from the 5GC300.

[0201] For example, before providing application services to UE500, in other words, before communicating with UE500, AS100 requests (applies for) priority registration (setting) from 5GC300. AS100 may request priority registration from each of multiple 5GC300.

[0202] Figure 8 shows an example of priority assignment processing according to the embodiment of this disclosure. In Figure 8, it is assumed that the priority registration (setting) of AS100_1 has been completed, that is, AS100_1 has already been assigned a priority. In Figure 8, an example of assignment processing is shown when AS100_2 requests (applies) 5GC300 to register (set) a priority in this state.

[0203] AS100_2 requests (applies for) priority registration (setting) from 5GC300 (step S11). This request includes, for example, application information about the application services provided by AS100_2 and an identifier (AS ID) that identifies AS100_2. The application information includes, for example, category information about the type (category) of the application service.

[0204] When 5GC300 receives a request from AS100_2, for example, the administrator of 5GC300 reviews the request from AS100_2 (step S12). For example, the administrator reviews the priority of AS100_2 according to the application information, etc., included in the request from AS100_2.

[0205] For example, suppose the application information (e.g., category information) of AS100_1, which has already been assigned a priority, is "automotive systems" related to autonomous driving, and the application information (e.g., category information) of the requesting AS100_1 is online meetings (web conferences).

[0206] In this case, for example, if the priority requested by AS100_2 is lower than the priority requested by AS100_1, 5GC300 will accept AS100_2's request in accordance with the administrator's instructions. 5GC300 will then update the AS registration information and registration application history.

[0207] On the other hand, if the priority requested by AS100_2 is higher than or equal to the priority of AS100_1, 5GC300 will deny AS100_2's request in accordance with the administrator's instructions. 5GC300 will then update the registration application history.

[0208] In Figure 8, assume that 5GC300 has accepted the request of AS100_2. In this case, 5GC300 adds AS100_2's priority information to the AS registration information in the DB (corresponding to the storage unit 320 in Figure 5). For example, 5GC300 adds AS100_2's AS ID ("1235" in Figure 8), application information ("Online Meeting" in Figure 8), and AS100_2's priority ("1" in Figure 8) to the AS registration information.

[0209] Since AS100_1 is already registered, the AS registration information in Figure 8 includes the AS ID of AS100_2 (shown as "1234" in Figure 8), application information (shown as "Automotive System" in Figure 8), and the priority of AS100_2 (shown as "2" in Figure 8).

[0210] 5GC300 notifies AS100_2 of the review results (step S13). In Figure 8, 5GC300 sends a notification to AS100_2 stating that it accepts AS100_2's request (application).

[0211] Furthermore, 5GC300 notifies the QoS server 200 that it has set (registered) the priority of AS100_2 (step S14). This notification may include, for example, information regarding the priority of AS100_2 (e.g., AS registration information).

[0212] On the other hand, if 5GC300 denies AS100_2's request (application), it sends a notification to AS100_2 to that effect. At this time, 5GC300 may also notify AS100_2 of information regarding the priority that can be registered (set) and the reason for the denial.

[0213] Here, we have described the case where the priority of AS100 is set (registered) systemically by 5GC300, but the method of setting the priority of AS100 is not limited to this. For example, the priority of AS100 may be set directly (physically) between the administrator of AS100 and the administrator of 5GC300.

[0214] Furthermore, while it is stated here that priority registration can be requested for each of the multiple 5GC300 units, AS100 may also request priority registration for multiple 5GC300 units collectively.

[0215] For example, if one PLMN operator (MNO) operates (installs) multiple 5GC300s, the AS100 may request priority registration from this PLMN operator. This allows the PLMN operator to determine that a priority registration request has been made for the multiple 5GC300s it operates.

[0216] Furthermore, even after registering the priority of the AS100, the 5GC300 may take actions such as changing the priority of the AS100 or rejecting the QoS setting. For example, the 5GC300 may change the priority of the AS100 depending on the usage status of the AS100's wireless resources, or reject the QoS setting request even if the priority of the AS100 is high.

[0217] Specifically, for example, 5GC300 may reject the QoS setting for AS100 if it has set up QoS and secured wireless resources, but AS100 is not using these resources at all. This frees up the wireless resources that were allocated to AS100, thereby improving the frequency efficiency of the wireless resources.

[0218] Furthermore, while it is stated here that 5GC300 performs priority reviews of AS100 according to the administrator of 5GC300, it is also possible, for example, for 5GC300 to perform priority reviews of AS100 independently of the administrator.

[0219] For example, 5GC300 can perform priority reviews of AS100 according to machine learning or predetermined rules.

[0220] Here, as mentioned above, the priority of AS100 is not the priority of packets on the communication path between AS100 and UE500, but rather an indicator of priority when configuring QoS settings.

[0221] Therefore, when the 5GC300 receives QoS setting requests from multiple AS100s, it assigns the QoS settings of the 5G system 30 to the base station 400 according to priority, that is, prioritizing the QoS settings of the AS100s with higher priority. Also, requests from the AS100s with higher priority are read into the 5GC300 first.

[0222] For example, suppose AS100_1 has a higher priority than AS100_2. Also, suppose that the base station 400 to which UE500_1, which communicates with AS100_1, is connected is the same base station 400 to which UE500_2, which communicates with AS100_2, is connected. In this base station 400, suppose that there is one UE500 that can perform a QoS setting with 5QI set to "3".

[0223] In this case, AS100_2 makes a request to 5GC300 to set the QoS setting (5QI) of AS100_2's application to "3" for UE500_2. Also, after AS100_2's request, AS100_1 makes a request to 5GC300 to set the QoS setting (5QI) of AS100_2's application to "3" for UE500_2.

[0224] If AS100's priority is not set, a QoS setting of "3" will be applied to UE500_2, but the requested QoS setting will not be applied to UE500_1.

[0225] On the other hand, in this embodiment, priority is set for AS100. Therefore, even if AS100_2 requests QoS settings first, the request from AS100_1, which has a higher priority, will be executed first. In other words, the QoS settings that were made for UE500_2 are canceled in response to the QoS setting request from AS100_1, and the QoS settings as requested, for example, setting 5QI to "3", are reflected for UE500_1.

[0226] Furthermore, if QoS configuration requests are made simultaneously from AS100_1 and 100_2, 5GC300 will apply the QoS configuration request from AS100_1 to the network first, according to the priority of AS100. Next, 5GC300 will apply the QoS configuration request from AS100_2 to the network.

[0227] Thus, in this embodiment, the higher the priority of AS100, the more likely the QoS settings are to be applied to the network.

[0228] Figure 9 is a sequence diagram showing an example of the QoS setting request processing flow according to the embodiment of this disclosure. In Figure 9, AS100_1 and AS100_2 make QoS setting requests to 5GC300. It is also assumed that the priority of AS100_1 is higher than the priority of AS100_2.

[0229] As shown in Figure 9, first, AS100_2 sends a QoS configuration request (hereinafter also referred to as the first QoS configuration request) to the NEF (Network Exposure Function) 301 of 5GC300 (step S21). Next, AS100_1 sends a QoS configuration request (hereinafter referred to as the second QoS configuration request) to the NEF 301 of 5GC300 (step S22).

[0230] Now, let's assume that NEF301 has been notified of an excessive number of QoS configuration requests. In this case, NEF301 stores the received QoS configuration requests in a buffer (step S23). At this time, NEF301 stores the requests in the buffer in order of priority of AS100, for example.

[0231] The NEF 301 sends the QoS setting requests stored in the buffer to the PCF (Policy Control Function) 302. For example, the NEF 301 sends the second QoS setting request for the higher-priority AS100_1 to the PCF 302 (step S24), and then sends the first QoS setting request for the lower-priority AS100_2 to the PCF 302 (step S25).

[0232] For example, PCF302 determines whether to reflect the QoS settings in the order in which requests are received (step S26). PCF302 determines whether to reflect the QoS settings based on, for example, the QoS setting status of RAN (base station 400) and the priority information of AS100. Here, let's assume that PCF302 has determined to reflect the QoS settings of AS100_1 and 100_2.

[0233] PCF302 requests the SMF (Session Management Function) to reflect the QoS settings requested by AS100_1 (hereinafter also referred to as the second QoS settings) (step S27). PCF302 also requests the SMF to reflect the QoS settings requested by AS100_2 (hereinafter also referred to as the first QoS settings) (step S28).

[0234] When PCF302 receives a notification from SMF indicating the successful configuration of the second QoS setting, it sends this notification to AS100_1 via NEF301 (step S29). Also, when PCF302 receives a notification from SMF indicating the successful configuration of the first QoS setting, it sends this notification to AS100_2 via NEF301 (step S30).

[0235] The PCF302 updates the QoS configuration status of the RAN (base station 400) under its management (step S31).

[0236] As described above, when AS100 requests (requests) the setting (registration) of a priority, it may include priority information regarding the desired priority in addition to the AS ID and application information when submitting a request to 5GC300. For example, the request for setting a priority may be made by extending the AsSessionWithQoS API defined in 3GPP (registered trademark), or by using a newly created API. Furthermore, the request for setting a priority may be made not only via NEF, but also via the GSMA CAMARA QoD API. Thus, the request for setting a priority may be made via an API within 5GC300, or via an API outside of 5GC300.

[0237] In this case, 5GC300 examines whether to reflect the priority desired by AS100 in the QoS setting process, based on the AS ID, application information, and other information, or in other words, whether to set (register) the priority desired by AS100.

[0238] If the review results approve the application, 5GC300 registers the priority desired by AS100 (reflecting this in the QoS configuration process). For example, 5GC300 may advance the order in which QoS configuration requests are reflected according to priority, or assign QoS with priority.

[0239] On the other hand, if the review results in rejection of the application, 5GC300 may set a different priority in place of the priority desired by AS100. This alternative priority may be notified to AS100 along with the review result.

[0240] Alternatively, AS100 may choose not to include the desired priority in the application (request) for setting (registering) the priority. In this case, AS100 can use, for example, the AsSessionWithQoS API defined in 3GPP to apply for setting the priority.

[0241] Upon receiving the application, the 5GC300 determines the priority of the AS100 based on the information provided by the AS100. For example, the 5GC300 determines the priority of the AS100 based on at least one of the following: the information on the requestbody included in the application, the number of past applications (requests) made by the AS100, and information previously registered in the storage unit 320.

[0242] The 5GC300 registers the determined priority (reflecting it in the QoS configuration process). For example, the 5GC300 adjusts the order in which QoS configuration requests are reflected according to the determined priority, or assigns QoS to those requests with priority.

[0243] Thus, the communication system of this embodiment makes it easier to set QoS according to the application service provided by AS100 by pre-setting the priority of QoS settings.

[0244] <3-2. QoS Settings> Figures 10 to 12 show an example of the QoS setting process according to the embodiment of this disclosure. Figures 10 to 12 show an example of calculating candidate information for UE500_1 and 500_3 which communicate with AS100_1, and UE500_2 which communicates with AS100_2.

[0245] Note that in Figures 10 to 12, only the base station 400 of the 5G system 30 is shown for the sake of simplicity in the illustration, but the explanation will assume that the 5GC 300 performs QoS settings, etc., via the base station 400.

[0246] AS100_1 will provide web conferencing (online meeting) services to UE500_1 and 500_3. Both UE500_1 and 500_3 are scheduled to participate in a meeting starting at 13:00.

[0247] Furthermore, AS100_1 provides game services to UE500_2. UE500_2 has a ticket to participate in an event starting at 13:00, meaning it is scheduled to participate in the event starting at 13:00.

[0248] As shown in Figure 10, UE500_1 transmits terminal information to AS100_1 (step S201). This terminal information includes at least one of application information, communication quality information, and location information of UE500_1.

[0249] App information includes, for example, information about the time when UE500_1 is expected to receive the service (e.g., schedule information). In this case, the app information includes the scheduled information for a meeting to be held at 13:00.

[0250] UE500_2 transmits terminal information to AS100_2 (step S202). This terminal information includes at least one of application information, communication quality information, and location information of UE500_2.

[0251] App information includes, for example, information about the time when UE500_2 is expected to use the service (e.g., schedule information). In this case, the app information includes scheduled information for an event that will be held from 13:00.

[0252] UE500_3 transmits terminal information to AS100_1 (step S203). This terminal information includes at least one of application information, communication quality information, and location information of UE500_3.

[0253] App information includes, for example, information about the time when UE500_3 is expected to receive the service (e.g., schedule information). In this case, the app information includes the scheduled meeting information that will be held from 13:00.

[0254] This transmission of terminal information may occur periodically.

[0255] AS100_1 calculates calculation information for each UE500_1 and 500_3 from the acquired terminal information (step S204). The calculation information includes, for example, information regarding the timing (predicted timing) and location (predicted location) at which UE500_1 and 500_3 are expected to receive application services.

[0256] For example, AS100_1 assumes that the predicted timing is 13:00 based on the schedule information of UE500_1. AS100_1 also calculates the predicted location from the location information of UE500_1 included in the terminal information.

[0257] For example, if UE500_1's location is at the company when AS100_1 receives terminal information (for example, at 9:00), AS100_1 predicts that UE500_1 will be at the company participating in a web conference, i.e., the predicted location is the company.

[0258] Alternatively, AS100_1 may determine its predicted location from the meeting participants and the venue listed in the schedule. AS100_1 may also determine its predicted location from the travel path of UE500_1.

[0259] AS100_1 calculates the calculation information for UE500_3 in the same manner.

[0260] Additionally, AS100_1 may calculate the importance of application execution as part of its calculation information. Importance is an indicator that shows what level of QoS is desired, such as wanting to guarantee QoS above the standard.

[0261] For example, AS100_1 calculates the importance of a meeting (application execution) based on factors such as the user's role in UE500_1 and 500_3, and whether they are the meeting organizer or presenter. Alternatively, AS100_1 may determine the importance based on specifications from the users of UE500_1 and 500_3.

[0262] AS100_2 calculates the calculation information for UE500_2 from the acquired terminal information (step S205).

[0263] For example, AS100_2 might determine the predicted timing to be 13:00 based on the ticket information held by UE500_2. AS100_2 also uses the ticket information to determine the location where the event will be held, and uses this location as the predicted position.

[0264] If the event is accessible from any location, AS100_2 calculates a predicted location based on the location information of UE500_2 included in the terminal information, as well as past event participation locations. In other words, AS100_2 can calculate a predicted location based on past and / or current location information of UE500_2.

[0265] For example, if UE500_2 often runs games from home, AS100_2 will predict home as its location.

[0266] Furthermore, if a ticket is not required to participate in the event, i.e., if UE500_2 does not have a ticket, AS100_2 may decide whether to participate in the event based on UE500_2's past participation history in similar events. If AS100_2 predicts that UE500_2 will participate in the event, it will use the event's disclosure time as the prediction timing.

[0267] Furthermore, AS100_2 may also calculate the importance of application execution as calculated information. For example, AS100_2 calculates importance based on the presence or absence of a ticket (or the type of ticket, such as paid / free). For example, AS100_2 might assign a higher importance to UE500 with a ticket than to UE500 without a ticket.

[0268] As shown in Figure 11, AS100_1 transmits calculation information to the QoS server 200 (step S206). Based on this calculation information and network information obtained from 5GC300, the QoS server 200 calculates candidate information for UE500_1 and 500_3 respectively (step S207).

[0269] Candidate information includes, for example, information regarding communication quality (e.g., QoS settings) between UE500_1, 500_3, and AS100. Candidate information may include, for example, at least one of recommendation information, probability information, time information, destination evaluation information, and parameter information.

[0270] The QoS server 200 transmits the calculated candidate information to AS100_1 (step S208).

[0271] As shown in Figure 12, AS100_2 transmits calculation information to the QoS server 200 (step S209). Based on this calculation information and network information obtained from 5GC300, the QoS server 200 calculates candidate information for UE500_2 (step S210).

[0272] Candidate information includes, for example, information regarding the communication quality between UE500_2 and AS100 (e.g., QoS settings). Candidate information may include, for example, at least one of recommendation information, probability information, time information, destination evaluation information, and parameter information.

[0273] The QoS server 200 transmits the calculated candidate information to AS100_2 (step S211).

[0274] AS100_1 transmits the acquired candidate information for UE500_1 to UE500_1 (step S212).

[0275] UE500_1 determines the execution timing for running the application based on the candidate information and notifies AS100_1 of the configuration notification regarding the QoS settings to be requested at the execution timing (step S213). Here, UE500_1 notifies AS100_1 of the configuration notification before the execution timing. In other words, UE500_1 reserves the QoS configuration request for the execution timing.

[0276] Upon receiving the configuration notification, AS100_1, for example, makes a reservation with the QoS server 200 for a QoS configuration request at the execution timing (step S214).

[0277] Furthermore, AS100_1 transmits the acquired candidate information for UE500_3 to UE500_3 (step S215). Here, UE500_3 decides not to request QoS settings based on the candidate information. In this way, UE500_3 may choose not to request QoS settings.

[0278] AS100_2 transmits the acquired candidate information for UE500_2 to UE500_2 (step S216).

[0279] UE500_2 determines the execution timing for executing the application according to the candidate information and notifies AS100_2 of a setting notification requesting the desired QoS settings at the execution timing (step S217).

[0280] In response to the configuration notification, AS100_2 requests 5GC300 to configure the QoS settings for UE500_2 (step S218).

[0281] Furthermore, the QoS server 200 requests the 5GC300 to configure the QoS settings for UE500_1 at the execution timing specified by UE500_1 (step S219). As a result, the 5GC300 executes the QoS settings for UE500_1 and UE500_2 according to the priority of AS100.

[0282] For example, when communication with UE500 ends and the QoS settings of UE500 are canceled, AS100 obtains communication evaluation information regarding the connection destination from UE500. AS100 then notifies the QoS server 200 of the obtained communication evaluation information.

[0283] Furthermore, AS100 may, for example, generate QoS setting history information for each UE500. The QoS setting history information includes information about the QoS setting requests made by the UE500 at the predicted timing.

[0284] For example, the QoS setting history information may include information indicating whether or not the UE500 made a QoS setting request with the predicted timing as the execution timing, and / or information indicating the number of times the QoS setting request was made with the predicted timing as the execution timing.

[0285] Additionally, AS100 may include application information from when UE500 requested QoS settings in the QoS setting history information.

[0286] <3-3. Candidate Information> Next, we will explain the details of the candidate information. As mentioned above, the UE500 requests QoS settings based on the candidate information. In this case, for example, the UE500 presents the candidate information to the user and requests QoS settings in response to the user's instructions. Here, we will explain the details of the candidate information using an example of candidate information that the UE500 presents to the user.

[0287] Figure 13 shows an example of a User Interface (UI) that presents candidate information according to the embodiment of this disclosure.

[0288] As shown in Figure 13, the UI includes information about the target UE (User Interface) for which the candidate information is based, and the application (target app) that the target UE will receive. In Figure 13, the target UE is the first UE500_1 (an example of UE500), and the target app is a web conferencing application.

[0289] Furthermore, the UI includes a predicted start time and a predicted end time. The predicted start time is the time when the application service is expected to be provided, in other words, when the QoS settings are expected to begin, and corresponds to the predicted timing described above. The predicted end time is the time when the application service is expected to be provided, in other words, when the QoS settings are expected to end, and is calculated from the application information's schedule information, etc.

[0290] In the example in Figure 13, the predicted start time is 13:00, the meeting start time, and the predicted end time is 13:30, the meeting end time.

[0291] Furthermore, the UI includes connection destination candidates, recommended QoS for the predicted time, configurable probability of the recommended QoS, QoS setting delay time for the predicted time, evaluation, and additional configurable parameters. Thus, the candidate information includes information for each UE500 connection destination candidate (e.g., base station 400).

[0292] (Candidate connection destination) A candidate connection destination is, for example, information indicating a connection destination that the target UE (first UE 500_1) can connect to at the predicted location. A candidate connection destination includes, for example, at least one of the following: information about a PLMN operator, information about 5GC 300, and information about a base station 400.

[0293] Candidate connection destinations are information generated by the QoS server 200, for example, based on the connection destination correspondence table and the predicted location. The QoS server 200 generates candidate connection destinations according to the predicted location calculated based on the connection destination correspondence table previously obtained from the PLMN operator and terminal information, and notifies the first UE 500_1.

[0294] In the example shown in Figure 13, three potential connection destinations are presented: the first base station of the first 5GC of Company A, the second base station of the second 5GC of Company B, and the third base station of the third 5GC of Company C.

[0295] Here, one 5GC300 corresponding to one PLMN operator is listed as a candidate connection destination, but multiple 5GC300s operated by one PLMN operator may also be included as candidate connection destinations. Also, here, one base station 400 corresponding to one 5GC300 is listed as a candidate connection destination, but multiple base stations 400 connected to one 5GC300 may also be included as candidate connection destinations.

[0296] (Recommended QoS for predicted time) The recommended QoS for predicted time is recommended information for each candidate connection destination. The recommended QoS for predicted time is information generated by, for example, the QoS server 200 based on application information and a QoS correspondence table.

[0297] The QoS server 200 calculates recommended QoS from the application information (more specifically, category information) and the QoS correspondence table included in the calculation information. The QoS server 200 may also calculate recommended QoS according to the importance included in the calculation information and the congestion level of the base station 400 in the future (e.g., at the predicted timing). Here, importance is an indicator that shows what level of QoS is to be guaranteed, such as wanting to guarantee QoS above the standard level. Standard QoS is the QoS calculated, for example, when the importance level is normal (or when no importance level is set).

[0298] Furthermore, the QoS server 200 may change the recommended QoS according to the priority assigned to the AS 100. The recommended QoS may also include "no configuration required," which does not require QoS configuration. For example, if the QoS server 200 determines that QoS configuration is unnecessary based on the future congestion level of the base station 400 (e.g., at a predicted timing), it will select "no configuration required" as the recommended QoS.

[0299] In the example in Figure 13, the recommended QoS for the predicted time of the "first base station" is "5qi7". The recommended QoS for the predicted time of the "second base station" and the "third base station" is "5qi9".

[0300] For example, if the first UE500_1 requests QoS settings from the first base station at the predicted timing, it is recommended to request setting 5qi7. Similarly, if the first UE500_1 requests QoS settings from the second or third base station at the predicted timing, it is recommended to request setting 5qi9.

[0301] While the UI here assumes that the recommended QoS for the predicted time is displayed, information regarding recommended communication quality may be displayed instead. For example, instead of 5qi, information indicating communication quality such as "high reliability" or "low latency" may be displayed in the UI. Alternatively, a specific value indicating communication quality, such as "maximum latency of 50ms," may be displayed in the UI.

[0302] Note that while this example shows a case where there is only one recommended QoS for each potential connection destination, there may be multiple recommended QoS settings for each potential connection destination. For example, the "first base station" may have three recommended QoS settings: "5qi3, bitrate:20M", "5qi3, bitrate:30M", and "5qi3, bitrate:40M".

[0303] Furthermore, the number of recommended QoS levels is not limited to one or three. There may be two or four or more recommended QoS levels. Also, five different recommended QoS levels may be set for a single candidate connection destination. In addition, other communication quality parameters (e.g., latency) may be set instead of, or in addition to, the bitrate.

[0304] (Recommended QoS Configurability Probability) The recommended QoS configurability probability is probability information for each candidate connection destination. The recommended QoS configurability probability is information generated by the QoS server 200, for example, based on network information and a configuration upper limit correspondence table.

[0305] The setting limit correspondence table includes information showing the correspondence between, for example, the base station 400, the number of configurable UEs (e.g., the number of QoS flows), and the type of QoS (e.g., 5qi). The QoS server 200 calculates the probability of being able to configure the recommended QoS for each UE 500 using the recommended QoS settings, predicted timing, AS 100 priority, reservation status of QoS setting requests, and the setting limit correspondence table, etc.

[0306] In the example in Figure 13, the probability of being able to set the recommended QoS for the "first base station" is "90%". The probability of being able to set the recommended QoS for the "second base station" is "50%". The probability of being able to set the recommended QoS for the "third base station" is "99%".

[0307] For example, if the first UE500_1 requests the first base station to configure 5qi7 at the predicted timing, there is a 90% probability that the requested QoS will be configured. Similarly, if the first UE500_1 requests the second base station to configure 5qi9 at the predicted timing, there is a 50% probability that the requested QoS will be configured. If the first UE500_1 requests the third base station to configure 5qi9 at the predicted timing, there is a 99% probability that the requested QoS will be configured.

[0308] (Predicted Time QoS Configuration Delay) The predicted time QoS configuration delay is time information for each candidate connection destination. The predicted time QoS configuration delay is information generated by, for example, the QoS server 200 based on configuration delay information, etc.

[0309] For example, the QoS server 200 calculates the QoS setting delay time for the predicted time using the predicted timing, the priority of AS 100, the reservation status of the QoS setting request, and setting delay information.

[0310] In the example in Figure 13, the QoS setting delay time for the predicted time of the "first base station" is "1 s". The QoS setting delay time for the predicted time of the "second base station" is "4 s". The QoS setting delay time for the predicted time of the "third base station" is "5 s".

[0311] For example, if the first UE500_1 requests QoS settings from the first base station at the predicted timing, it takes 1 second for the QoS settings to be reflected. Similarly, if the first UE500_1 requests QoS settings from the second base station at the predicted timing, it takes 4 seconds for the QoS settings to be reflected. If the first UE500_1 requests QoS settings from the third base station at the predicted timing, it takes 5 seconds for the QoS settings to be reflected.

[0312] (Evaluation) The evaluation is connection destination evaluation information for each candidate connection destination. For example, the QoS server 200 generates connection destination evaluation information by averaging the communication evaluation information collected by the UE500 via the AS100.

[0313] In the example in Figure 13, the evaluation of "Base Station 1" is "Normal". The evaluation of "Base Station 2" is "Good". The evaluation of "Base Station 3" is "Bad". Note that the UI evaluation may be a tiered evaluation (for example, "3" on a 5-point scale), or it may be based on user reviews, etc.

[0314] (Configurable Additional Parameters) The configurable additional parameters are parameter information for each candidate connection destination. In the example in Figure 13, the configurable additional parameter for the "first base station" is "t-reordering". The configurable additional parameters for the "second base station" are "t-reordering" and "RLC Mode". The configurable additional parameters for the "third base station" are "none". In other words, when the "third base station" is selected, there are no additional parameters that can be configured simultaneously with the QoS settings.

[0315] The reservation button shown in Figure 13 is a button that instructs the user to reserve a QoS setting request. For example, when this reservation button is pressed by the user, a recommended QoS setting request is reserved for the corresponding base station 400. The reservation button can also be described as a selection button. That is, the user uses the reservation button to select the connection destination and the requested QoS settings when the application is executed.

[0316] For example, the first UE500_1 sends a configuration notification to the AS100 requesting that a recommended QoS setting request be made to the base station 400 at the predicted timing. Alternatively, the first UE500_1 may make a recommended QoS setting request to the base station 400 designated by the user to the AS100 at the predicted timing.

[0317] Furthermore, the QoS settings requested by the first UE500_1 are not limited to the recommended QoS settings (recommended QoS). For example, the first UE500_1 may request the AS100 to provide modified QoS settings based on candidate information.

[0318] For example, instead of a single reservation button, two buttons (options) could be provided: "Reserve with recommended settings" and "Reserve with modified settings." If the user selects "Reserve with recommended settings," the first UE500_1 requests the AS100 to configure the recommended QoS settings at the predicted timing.

[0319] When the user selects "Change settings and make a reservation," the first UE500_1 modifies some information (parameters) from the recommended QoS settings and requests the AS100 to configure the QoS settings. For example, the first UE500_1 may determine the modified QoS settings according to the user's instructions.

[0320] For example, the first UE requests AS100 to configure QoS settings at a timing different from the predicted timing. Alternatively, the first UE500_1 may request AS100 to configure QoS settings by specifying 5qi, which is different from the recommended QoS.

[0321] <3-4. Examples of Various Information> This section describes some examples of various types of information exchanged between devices.

[0322] (5G System 30 - QoS Server 200) Figure 14 shows an example of information exchanged between the 5G system 30 and the QoS server 200 according to the embodiment of this disclosure. The 5G system 30 in Figure 14 includes a PLMN operator, a 5GC 300, and a base station 400.

[0323] As shown in Figure 14, the 5G system 30 notifies the QoS server 200 of the connection destination correspondence table, the QoS correspondence table, the setting limit correspondence table, the setting time required for QoS settings (for example, equivalent to the setting delay time), and the additional configurable parameters (for example, equivalent to parameter information).

[0324] Furthermore, the 5G system 30 notifies the QoS server 200 of the priority and network information for each AS 100.

[0325] Note that the information shown in Figure 14 is just an example, and other information may be exchanged between the 5G system 30 and the QoS server 200. For example, the QoS server 200 may send a QoS configuration request to the 5G system 30 in accordance with instructions from the AS 100.

[0326] (AS100-QoS Server 200) Figure 15 shows an example of information exchanged between AS100 and QoS Server 200 according to the embodiment of this disclosure.

[0327] As shown in Figure 15, AS100 notifies the QoS server 200 of the calculation information and communication evaluation information. The communication evaluation information may be included in the calculation information.

[0328] Furthermore, the QoS server 200 notifies the AS100 of the candidate information.

[0329] Note that the information shown in Figure 15 is just an example, and other information may be exchanged between AS100 and the QoS server 200. For example, AS100 may request the QoS server 200 to reserve a QoS configuration request.

[0330] (UE500-AS100) Figure 16 shows an example of information exchanged between UE500 and AS100 according to an embodiment of the present disclosure.

[0331] As shown in Figure 16, UE500 notifies AS100 of terminal information and communication evaluation information. Communication evaluation information may be included in the terminal information.

[0332] Furthermore, AS100 notifies UE500 of the candidate information.

[0333] Note that the information shown in Figure 16 is just an example, and other information may be exchanged between UE500 and AS100. For example, UE500 may send a configuration notification including a QoS configuration request to AS100.

[0334] <3-5. Example of operation after obtaining candidate information> As described above, the UE500 requests the desired QoS settings using a setting notification based on the candidate information. At this time, the UE500 may use the QoS settings included in the candidate information as the desired QoS settings, or it may use settings different from the QoS settings included in the candidate information as the desired QoS settings.

[0335] For the sake of simplicity, we will assume that the recommended QoS, evaluation, and configurable additional parameters included in the candidate information do not need to be changed. Furthermore, for the sake of simplicity, we will assume that there is only one candidate connection destination included in the candidate information.

[0336] If there are no problems with both the recommended QoS configurability probability and the QoS configuration delay time, for example, if both are at the desired values, the UE500 will send a configuration notification using the QoS settings included in this candidate information as the desired QoS settings.

[0337] If there is a problem with the probability of setting the recommended QoS, for example, if the setting probability is not the desired value (for example, if the setting probability is lower than a predetermined value), the UE500 will reserve the QoS setting request using the QoS setting included in this candidate information as the desired QoS setting.

[0338] Alternatively, in this case, the UE500 may connect to a network other than a cellular network, such as Wi-Fi (registered trademark), at the time of execution and run the application.

[0339] Furthermore, the UE500 may ensure the desired communication quality by means other than QoS settings, for example. For instance, the UE500 may move to another location with a better communication environment (a location different from the predicted location) at the predicted timing (i.e., the execution timing).

[0340] UE500 may, for example, halt the execution of the application at the predicted timing. UE500 may also, for example, shift the timing of execution away from the predicted timing. For example, if the application is a web conference, UE500 may cancel the web conference or change its date (bring it forward or postpone it).

[0341] UE500 may adjust the importance of application execution, for example, by becoming the host of a web conference or purchasing a paid ticket.

[0342] If there is a problem with the QoS setting delay time, for example, if the QoS setting delay time is not the desired value (for example, if the QoS setting delay time is longer than the specified time), the UE500 can take the same measures as in the case of the recommended QoS setting probability.

[0343] For example, in this case, the UE500 may pre-book QoS configuration requests or connect to a network other than a cellular network. Furthermore, the UE500 may ensure the desired communication quality through means other than QoS configuration, or suspend application execution at predicted timings.

[0344] Alternatively, in this case, the UE500 may request the QoS setting earlier than the predicted timing by a time corresponding to the QoS setting delay time. For example, if the predicted timing (i.e., the execution timing) is exactly 13:00 and the QoS setting delay time is "10s", the UE500 will request (notify) the QoS setting 10s (or 10s plus a margin) earlier than 13:00.

[0345] This allows the UE500 to set the desired QoS at the predicted timing.

[0346] If there are problems with both the configurable probability of recommended QoS and the QoS configuration delay time, the UE500 can take the same measures as in the case of the configurable probability of recommended QoS.

[0347] For example, in this case, the UE500 may pre-book QoS configuration requests or connect to a network other than a cellular network. Furthermore, the UE500 may ensure the desired communication quality through means other than QoS configuration, or suspend application execution at predicted timings.

[0348] In this way, the UE500 can more reliably achieve communication that meets the desired communication quality by making a QoS setting request after modifying some of the settings, rather than simply requesting the QoS settings of the candidate information as is.

[0349] <3-6. Example of QoS Configuration Reservation> As described above, UE500 can make a reservation for a QoS configuration request to the QoS server 200 via AS100. AS100 makes a reservation for a QoS configuration request, for example, using the reservation API published by the QoS server 200.

[0350] The QoS server 200, upon receiving a reservation for a QoS configuration request, can, for example, notify the 5GC 300 of the received reservation details. This ensures that the 5GC 300 can reliably receive the reserved QoS configuration request at the reserved time (e.g., the predicted timing).

[0351] The QoS server 200, which has received a reservation for a QoS configuration request, may, for example, send the QoS configuration request to the 5GC 300 on behalf of the AS 100 when the reserved time for the QoS configuration request (e.g., the predicted timing) arrives.

[0352] Furthermore, the QoS server 200 can use the reservation status of QoS configuration requests to derive candidate information such as the probability of being able to configure recommended QoS. For example, if there are many reservations for QoS configuration requests, the QoS server 200 will calculate a lower probability of being able to configure recommended QoS. Also, for example, if there are many reservations for QoS configuration requests, the QoS server 200 will calculate a longer QoS configuration delay time.

[0353] For example, the QoS server 200 may reject a reservation request for a QoS configuration depending on the requested QoS configuration. In other words, the QoS server 200 may define which QoS configurations it will accept reservations for.

[0354] For example, the QoS server 200 determines the QoS settings to accept reservations based on the predicted value of the QoS settings reflected in the base station 400. An example of the predicted value of the QoS settings reflected in the base station 400 is the number of UE500 units to which a predetermined 5qi setting is configured at the predicted timing. This predicted value is calculated by the QoS server 200.

[0355] For example, the QoS server 200 may refuse to accept bandwidth guarantees exceeding a predetermined value (e.g., N (Mbps)) during times when a high volume of QoS configuration requests is expected (e.g., evenings). In this way, the QoS server 200 can define which QoS configurations it will accept reservations for.

[0356] <3-7. Sequence Example> Figure 17 is a sequence diagram showing an example of the flow of the QoS setting process according to the embodiment of this disclosure. In Figure 17, the first UE500_1 receives application services from the first AS100_1. The second UE500_2 receives application services from the second AS100_2.

[0357] Furthermore, the first UE500_1 and the second UE500_2 are connected to the first 5GC300_1, out of the two 5GC300_2.

[0358] As shown in Figure 17, the first UE 500_1 sends a connection request to the first 5GC 300_1 (step S301). The second UE 500_2 also sends a connection request to the first 5GC 300_1 (step S302).

[0359] When the first 5GC300_1 performs connection processing with the first UE500_1, it notifies the first UE500_1 of the completion of the connection (step S303). When the first 5GC300_1 performs connection processing with the second UE500_2, it notifies the second UE500_2 of the completion of the connection (step S304).

[0360] The first UE500_1 transmits terminal information to the first AS100_1 (step S305). The second UE500_2 transmits terminal information to the second AS100_2 (step S306).

[0361] The first AS100_1 calculates the predicted timing and predicted position using terminal information obtained from the first UE500_1 (step S307). The second AS100_2 calculates the predicted timing and predicted position using terminal information obtained from the second UE500_2 (step S308).

[0362] The first 5GC300_1 transmits network information to the QoS server 200 (step S309). The second 5GC300_2 transmits network information to the QoS server 200 (step S310).

[0363] The first AS100_1 transmits the calculated information, including the predicted timing and predicted position calculated in step S307, to the QoS server 200 (step S311). The second AS100_2 transmits the calculated information, including the predicted timing and predicted position calculated in step S308, to the QoS server 200 (step S312).

[0364] The processes in steps S305 to S311 can be executed repeatedly, for example. Note that the following cycles may be different or the same: - Cycle in which the first UE500_1 transmits terminal information - Cycle in which the second UE500_2 transmits terminal information - Cycle in which the first AS100_1 calculates the predicted timing and predicted position - Cycle in which the second AS100_2 calculates the predicted timing and predicted position - Cycle in which the first 5GC300_1 transmits network information - Cycle in which the second 5GC300_2 transmits network information - Cycle in which the first AS100_1 transmits calculated information - Cycle in which the second AS100_2 transmits calculated information

[0365] For example, the first AS100_1 may calculate the predicted timing and predicted position if the difference between the terminal information acquired this time and the terminal information acquired last time is greater than or equal to a predetermined threshold. Alternatively, for example, the first AS100_1 may send the calculation information generated this time to the QoS server 200 if the calculation information generated this time differs from the calculation information generated last time by a predetermined threshold or more.

[0366] In this way, the information that is transmitted or calculated periodically may be transmitted or calculated according to predetermined conditions (for example, the difference from the previous time).

[0367] Next, the first UE500_1 sends a request for candidate information to the QoS server 200, for example, via the first AS100_1 (step S313). The second UE500_2 sends a request for candidate information to the QoS server 200, for example, via the second AS100_2 (step S314).

[0368] In response to this request, the QoS server 200 calculates candidate QoS settings from various pieces of information (step S315). For example, in response to a request from the first UE500_1, the QoS server 200 calculates candidate QoS settings for the first UE500_1. For example, in response to a request from the second UE500_2, the QoS server 200 calculates candidate QoS settings for the second UE500_2.

[0369] The QoS server 200 transmits the calculated candidate QoS settings information for the first UE500_1 to the first UE500_1 via the first AS100_1 (step S316).

[0370] The QoS server 200 transmits the calculated candidate information for the QoS settings in the second UE500_2 to the second UE500_2 via the second AS100_2 (step S317).

[0371] Here, for example, let's say UE500 requests the calculation of candidate information. For example, UE500 may request candidate information when the application of the service provided by AS100 is executed.

[0372] The request for candidate information calculation may be made by AS100. For example, AS100 notifies the QoS server 200 of the request for candidate information calculation at a predetermined time before the calculated predicted timing (for example, one day before the start time of the web conference). In this case, AS100 may also notify the UE500 of the candidate information using push notifications or the like.

[0373] Based on the candidate information, the first UE500_1, having determined the required QoS settings, transmits the QoS setting request to the first 5GC300_1 via the first AS100_1 (step S318).

[0374] Based on the candidate information, the second UE500_2, having determined the required QoS settings, transmits the QoS setting request to the first 5GC300_1 via the second AS100_2 (step S319).

[0375] The first 5GC300_1 performs QoS settings for the first and second UE500_1 and 500_2 according to the QoS setting request, the priority of the first and second AS100_1 and 100_2, etc. (step S320).

[0376] Alternatively, UE500 may make a QoS setting reservation to AS100, or to the QoS server 200 via AS100.

[0377] Alternatively, UE500 may request a QoS configuration from a second 5GC300_2 that is not connected. In this case, UE500 may, for example, terminate its connection with the first 5GC300_1 and then perform a connection process with the second 5GC300_2. UE500 may then request a QoS configuration from the second 5GC300_2.

[0378] After the QoS setting is deactivated, the first UE500_1 transmits communication evaluation information to the QoS server 200 via the first AS100_1 (step S321). After the QoS setting is deactivated, the second UE500_2 transmits communication evaluation information to the QoS server 200 via the second AS100_2 (step S322).

[0379] The QoS server 200 calculates connection destination evaluation information using the acquired communication evaluation information (step S323).

[0380] As described above, the QoS server 200 of the communication system according to this embodiment can generate candidate information (future quality information) regarding QoS settings at predicted timings using terminal information including application information.

[0381] The UE500 can select the connection destination, the QoS settings to request, and the timing for requesting QoS settings from the candidate information. This allows the AS100 and UE500 to communicate with each other while ensuring the desired communication quality.

[0382] <3-8. Examples of Information Derivation> For example, at least some of the various types of information described above may be calculated using machine learning or the like. Here, as an example of calculating information using machine learning, we will explain how to calculate the prediction timing (QoS setting time) and the prediction position.

[0383] For example, when calculating the predicted timing, the QoS server 200 inputs at least one of the following into the model: past application information, past location information, past communication quality information, and QoS setting history collected from the UE 500, and uses the model's output as the predicted timing. The QoS setting history includes, for example, the number of QoS settings.

[0384] In other words, at least one of the following—past application information, past location information, past communication quality information, and QoS setting history—collected from the UE500 becomes an explanatory variable in the model for calculating the predicted timing (hereinafter also referred to as the timing estimation model). Furthermore, the predicted timing is listed as the dependent variable of the timing estimation model.

[0385] The output of the timing estimation model (predicted timing) may be the time to set QoS, or it may be a binary value (e.g., "0" or "1") indicating whether or not UE500 will set QoS at a predetermined time. Alternatively, the output of the model may be the probability that UE500 will set QoS at a predetermined time.

[0386] For example, when calculating a predicted location, the QoS server 200 inputs at least one of the following into the model: past application information, past location information, and past communication quality information collected from the UE 500, and the output of the model is used as the predicted location.

[0387] In other words, at least one of the following—past application information, past location information, and past communication quality information—collected from UE500 becomes an explanatory variable in the model for calculating the predicted location (hereinafter also referred to as the location estimation model). Furthermore, the predicted location is the dependent variable of the location estimation model.

[0388] Methods for generating timing estimation models and / or position estimation models include, for example, statistical analysis methods using linear regression analysis or multiple regression analysis, or methods using AI (Artificial Intelligence) / ML (Machine Learning), or other so-called artificial intelligence, machine learning, and deep learning.

[0389] Examples of AI / ML-based methods include: - Deep Learning - Multilayer Perceptron (MLP) - Convolutional Neural Network (CNN) - Stochastic Gradient Descent - Decision Tree - Random Forest - Support Vector Machine - k-Nearest Neighbors - Naive Bayes Classifier

[0390] It should be noted that AI / ML-based methods are not limited to the examples described above. Numerous AI / ML-based methods exist. Therefore, it is desirable that timing estimation models and / or position estimation models be generated using appropriate methods according to the principles of each method.

[0391] The generation of timing estimation models and / or position estimation models may be performed in coordination among multiple AS100s. Alternatively, the AS100 may use techniques such as fine-tuning to generate timing estimation models and / or position estimation models using pre-trained models.

[0392] Note that the calculation of predicted timing and / or predicted position using a timing estimation model and / or position estimation model is just one example. The QoS server 200 may also calculate predicted timing and / or predicted position without using a timing estimation model and / or position estimation model.

[0393] For example, the QoS server 200 calculates the predicted timing using application information, the location information of the UE500, quality information regarding the communication quality of the UE500, and the QoS setting history, etc.

[0394] For example, if the application information (application category information) is for web conferencing, the QoS server 200 calculates a predicted timing according to the web conferencing schedule. For example, if a meeting is scheduled for 3 PM, the QoS server 200 will set 3 PM as the timing (predicted timing) for configuring the QoS server 200.

[0395] Furthermore, the QoS server 200 may determine the importance of the QoS settings according to the importance of the meeting. For example, if an important meeting is scheduled, the QoS server 200 will set the importance of the QoS settings to a high level. The importance of the meeting may be determined based on the positions of the participants and the user's role in the meeting (e.g., organizer or presenter).

[0396] Furthermore, for example, the QoS server 200 calculates the predicted location using application information and location information of the UE 500. The QoS server 200 may also use quality information related to the communication quality of the UE 500 in calculating the predicted location.

[0397] For example, the QoS server 200 predicts the location when configuring QoS settings based on past location information and application information of the UE500. For example, the QoS server 200 predicts the location where the UE500 participated in a meeting in a similar past schedule. For example, if the meeting is held on the same schedule as usual, the QoS server 200 predicts that the UE500 will participate in the meeting from its usual location (for example, home).

[0398] For example, the QoS server 200 may calculate a predicted location based on application information, past location information of the UE500, as well as the work location (remote or in-office) and schedule before and after meetings.

[0399] This section describes the case where the application executed by UE500 is a web conferencing system, but the applications executed by UE500 are not limited to web conferencing. Examples of applications executed by UE500 include game applications and autonomous driving systems. Predicted timing and / or predicted position can be calculated in a similar manner for applications other than web conferencing.

[0400] For example, in the case of a game application, the QoS server 200 can calculate the predicted timing and / or predicted position using the information described above, as well as event participation registration, event information, in-game rank, and game play time.

[0401] For example, in the case of an autonomous driving system, the QoS server 200 can calculate predicted timing and / or predicted position using the route to the destination and surrounding environment information, in addition to the information described above. Furthermore, the surrounding environment information can be used, for example, to configure the QoS necessary for remote monitoring.

[0402] <<4. Other Embodiments>> The processing according to the above embodiments may be carried out in various other forms besides those described above.

[0403] In the embodiment described above, the QoS server 200 calculates candidate information for a predicted timing (future). In addition to this, the QoS server 200 may also calculate current candidate information (for example, also referred to as current quality information).

[0404] Current candidate information may include, for example, at least one of the following: current recommendation information, current configurability information, current time information, connection destination evaluation information, and parameter information.

[0405] Current recommended information includes, for example, information regarding currently recommended communication quality settings (QoS settings). Current configurability information includes information indicating whether or not currently recommended communication quality settings (recommended settings) can be configured. Current time information includes information regarding the configuration time required to currently configure the recommended settings.

[0406] The UE500 obtains current candidate information from the QoS server 200 via the AS100, similar to candidate information (future quality information) at the predicted timing, and presents it to the user.

[0407] Figure 18 shows an example of a UI that presents current candidate information according to an embodiment of this disclosure.

[0408] As shown in Figure 18, the UI includes information about the target UE (User Interface) for which the candidate information is based, and the application (target app) that the target UE will receive. In Figure 18, the target UE is the first UE500_1, and the target app is a web conferencing application.

[0409] The UI also includes connection target candidates, recommended QoS settings, configurability, QoS setting delay time, evaluation, and additional configurable parameters.

[0410] (Candidate connection destination) A candidate connection destination is, for example, information indicating a connection destination that the target UE (first UE 500_1) can connect to at its current location. A candidate connection destination includes, for example, at least one of the following: information about a PLMN operator, information about 5GC 300, and information about a base station 400.

[0411] Candidate connection destinations are information generated by the QoS server 200, for example, based on the connection destination correspondence table and the current location. The QoS server 200 generates candidate connection destinations based on the connection destination correspondence table previously obtained from the PLMN operator and the current location of the UE 500, and notifies the first UE 500_1.

[0412] In the example shown in Figure 18, three potential connection destinations are presented: the first base station of the first 5GC of Company A, the second base station of the second 5GC of Company B, and the third base station of the third 5GC of Company C.

[0413] (Recommended QoS) Recommended QoS is the current recommended information for each candidate connection destination. Recommended QoS is information generated by, for example, the QoS server 200 based on application information and a QoS correspondence table.

[0414] The QoS server 200 calculates the recommended QoS from the application information (more specifically, category information) and the QoS correspondence table included in the calculation information. The QoS server 200 may also calculate the recommended QoS according to the importance included in the calculation information and the current congestion level of the base station 400. Here, importance is an indicator that shows what level of QoS is to be guaranteed, such as wanting to guarantee QoS above the standard level. Standard QoS is the QoS calculated, for example, when the importance level is normal (or when no importance level is set).

[0415] Furthermore, the QoS server 200 may change the recommended QoS according to the priority assigned to the AS 100. The recommended QoS may also include "no configuration required," which does not require QoS configuration. For example, if the QoS server 200 determines that QoS configuration is unnecessary based on the current congestion level of the base station 400, it will select "no configuration required" as the recommended QoS.

[0416] In the example in Figure 18, the recommended QoS for the "first base station" is "5qi7". The recommended QoS for the "second base station" and the "third base station" is "5qi9".

[0417] While it is stated here that the recommended QoS is displayed in the UI, information regarding recommended communication quality may be displayed instead. For example, instead of 5qi, information indicating communication quality such as "high reliability" or "low latency" may be displayed in the UI. Alternatively, a specific value indicating communication quality, such as "maximum latency of 50ms," may be displayed in the UI.

[0418] Note that while this example shows a case where there is only one recommended QoS for each potential connection destination, there may be multiple recommended QoS settings for each potential connection destination. For example, the "first base station" may have three recommended QoS settings: "5qi3, bitrate:20M", "5qi3, bitrate:30M", and "5qi3, bitrate:40M".

[0419] Furthermore, the number of recommended QoS levels is not limited to one or three. There may be two or four or more recommended QoS levels. Also, five different recommended QoS levels may be set for a single candidate connection destination. In addition, other communication quality parameters (e.g., latency) may be set instead of, or in addition to, the bitrate.

[0420] (Configurability) Configurability indicates whether the recommended QoS can be configured for each candidate connection destination. Configurability is information generated by the QoS server 200, for example, based on network information and a configuration limit correspondence table.

[0421] The setting limit correspondence table includes information showing the correspondence between, for example, the base station 400, the number of configurable UEs (e.g., the number of QoS flows), and the type of QoS (e.g., 5qi). The QoS server 200 calculates whether the recommended QoS settings can be configured using the recommended QoS settings for each UE 500, the priority of the AS 100, the status of QoS setting requests, and the setting limit correspondence table, etc.

[0422] In the example in Figure 18, the configurability of the "first base station" is "possible (indicated by a circle in Figure 18)". The configurability of the "second base station" is "possible (indicated by a circle in Figure 18)". The configurability of the "third base station" is "not possible (indicated by an X in Figure 18)".

[0423] For example, the first UE500_1 can now request the first base station to configure 5qi7. Similarly, the first UE500_1 can now request the second base station to configure 5qi9. On the other hand, the first UE500_1 cannot now request the third base station to configure 5qi9.

[0424] (QoS Configuration Delay Time) The QoS configuration delay time is the current time information for each candidate connection destination. The predicted QoS configuration delay time is information generated by the QoS server 200, for example, based on configuration delay information, etc.

[0425] For example, the QoS server 200 calculates the current QoS configuration delay time using the priority of AS 100, the status of QoS configuration requests, and configuration delay information.

[0426] In the example in Figure 18, the QoS setup delay time for the "first base station" is "1 s". The QoS setup delay time for the "second base station" is "4 s". For the "third base station", QoS setup cannot be performed (setting availability is "not"), so the QoS setup delay time is not set (indicated by "-" in Figure 18).

[0427] For example, if the first UE500_1 requests QoS settings from the first base station, it takes 1 second for the QoS settings to be reflected. Similarly, if the first UE500_1 requests QoS settings from the second base station, it takes 4 seconds for the QoS settings to be reflected.

[0428] (Evaluation) The evaluation is connection destination evaluation information for each candidate connection destination. For example, the QoS server 200 generates connection destination evaluation information by averaging the communication evaluation information collected by the UE500 via the AS100.

[0429] In the example in Figure 18, the evaluation of "Base Station 1" is "Normal". The evaluation of "Base Station 2" is "Good". The evaluation of "Base Station 3" is "Bad". Note that the UI evaluation may be a tiered evaluation (for example, "3" on a 5-point scale), or it may be based on user reviews, etc.

[0430] (Configurable Additional Parameters) The configurable additional parameters are parameter information for each candidate connection destination. In the example in Figure 18, the configurable additional parameter for "Base Station 1" is "t-reordering". The configurable additional parameters for "Base Station 2" are "t-reordering" and "RLC Mode". The configurable additional parameters for "Base Station 3" are "none". In other words, when "Base Station 3" is selected, there are no additional parameters that can be configured simultaneously with the QoS settings.

[0431] The selection button shown in Figure 18 is a button that instructs a QoS setting request. For example, when this selection button is pressed by the user, a recommended QoS setting request is sent to the corresponding base station 400. The user uses the selection button to select the current connection destination and the requested QoS settings.

[0432] For example, the first UE500_1 sends a configuration notification to the AS100 requesting that it make a recommended QoS configuration request for the base station 400 in question.

[0433] Furthermore, the QoS settings requested by the first UE500_1 are not limited to the recommended QoS settings (recommended QoS). For example, the first UE500_1 may request the AS100 to provide modified QoS settings based on the current candidate information.

[0434] For example, instead of a single selection button, two buttons (options) may be provided: "Select with recommended settings" and "Change settings and select." If the user selects "Select with recommended settings," the first UE500_1 requests the AS100 to provide the recommended QoS settings.

[0435] When the user selects "Change settings and select," the first UE500_1 modifies some information (parameters) from the recommended QoS settings and requests the AS100 to configure the QoS settings. For example, the first UE500_1 may determine the modified QoS settings according to the user's instructions.

[0436] For example, the first UE500_1 may request AS100 to configure QoS by specifying 5qi, which is different from the recommended QoS.

[0437] Furthermore, the QoS server 200 may predict the QoS configuration delay time in the 5GC300 configuration, for example, based on the reservation status of QoS configuration requests. The QoS server 200 notifies the predicted QoS configuration delay time (hereinafter also referred to as the predicted delay time).

[0438] The 5GC300 may be configured to handle more QoS server 200 configuration requests in accordance with the acquired predicted delay time. For example, the 5GC300 may increase its processing capacity to reduce the processing time of QoS configuration requests per unit time. For example, the 5GC300 may scale out the NEF301, PCF302, and SMF.

[0439] In this way, by having the QoS server 200 predict the QoS configuration delay time, the communication system can further improve the availability of the 5GC 300.

[0440] Furthermore, the QoS server 200 may predict the amount of resources (e.g., bandwidth) to be used for QoS configuration at a predetermined base station 400, for example, based on the reservation status of QoS configuration requests. The QoS server 200 notifies the 5GC 300 of the predicted amount of resources (hereinafter also referred to as the predicted amount of resources).

[0441] If the predicted resource volume exceeds the capacity of a predetermined base station 400, the 5GC 300 increases the processing capacity of the cells of the predetermined base station 400. For example, the 5GC 300 increases the processing capacity of the cells of the predetermined base station 400 using a mobile base station or the like. Mobile base stations include, for example, non-ground stations such as artificial satellites and HAPS (High Altitude Platform Stations), and ground stations installed on mobile vehicles moving on the ground.

[0442] In this way, by having the QoS server 200 predict the amount of resources to be used for QoS configuration, the communication system can further improve the availability of the base station 400.

[0443] For example, the control device that controls the AS100, QoS server 200, 5GC300, base station 400, and UE500 in the above-described embodiment may be implemented by a dedicated computer system or by a general-purpose computer system.

[0444] For example, a communication program for performing the above-described operations is stored in a computer-readable recording medium such as an optical disc, semiconductor memory, magnetic tape, or flexible disk and distributed. Then, for example, the control device is configured by installing the program on a computer and executing the above-described process. In this case, the control device may be an external device (e.g., a personal computer) of the AS100, QoS server 200, 5GC300, base station 400, and UE500. Alternatively, the control device may be an internal device (e.g., control units 130, 230, 330, 440, 550) of the AS100, QoS server 200, 5GC300, base station 400, and UE500.

[0445] Alternatively, the above-mentioned communication program may be stored on a disk device provided by a server on a network such as the Internet, and made available for download to a computer. Furthermore, the above-mentioned functions may be realized through the cooperation of an OS (Operating System) and application software. In this case, the parts other than the OS may be stored on a medium and distributed, or the parts other than the OS may be stored on a server device and made available for download to a computer.

[0446] Of the processes described in the embodiments of this disclosure described above, all or part of the processes described as being performed automatically may be performed manually, or all or part of the processes described as being performed manually may be performed automatically by known methods. In addition, the processing procedures, specific names, and information including various data and parameters shown in the above documents and drawings may be changed at will unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown.

[0447] Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those shown, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions.

[0448] Also, the embodiments of the present disclosure described above can be appropriately combined in areas where the processing contents do not conflict. Also, the respective steps shown in the sequence diagram or flowchart of the present embodiment can be appropriately changed in order. For example, each step may be processed in time series, may be processed repeatedly, or may be processed partially in parallel.

[0449] Also, the effects described in this specification are merely examples and are not limiting, and there may be other effects.

[0450] Also, for example, the embodiment can be implemented as any configuration constituting the device or system, such as a processor as a system LSI (Large Scale Integration), a module using a plurality of processors, etc., a unit using a plurality of modules, etc., a set obtained by adding other functions to the unit (i.e., a part of the configuration of the device).

[0451] In the embodiment, the system means a collection of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all the components are in the same housing. Therefore, a plurality of devices housed in separate housings and connected via a network, and one device in which a plurality of modules are housed in one housing are both systems.

[0452] Also, for example, the embodiment can take a configuration of cloud computing in which one function is shared and jointly processed by a plurality of devices via a network.

[0453] <<5. Hardware Configuration>> The AS100, QoS server 200, 5GC 300, base station 400, UE 500, etc. according to the embodiments of the present disclosure described above are realized by a computer 1000 having a configuration as shown in FIG. 19, for example. Taking the UE 500 as an example for explanation. FIG. 19 is a hardware configuration diagram showing an example of a computer 1000 that realizes the functions of the UE 500. The computer 1000 includes a processing circuitry 1100, a RAM 1200, a ROM 1300, a secondary storage device 1400, a communication interface 1500, an input / output interface 1600, a display unit 1700, a camera unit 1800, a microphone 1900, and a speaker 2000. Each part of the computer 1000 is connected by a bus 1050.

[0454] The processing circuitry 1100 operates based on programs stored in the ROM 1300 or the secondary storage device 1400 and controls each part. For example, the processing circuitry 1100 expands a program stored in the ROM 1300 or the secondary storage device 1400 into the RAM 1200 and executes processing corresponding to various programs.

[0455] The ROM 1300 stores a boot program such as BIOS (Basic Input Output System) executed by the processing circuitry 1100 when the computer 1000 is started, and programs dependent on the hardware of the computer 1000, etc.

[0456] The secondary storage device 1400 is a computer-readable recording medium that non-temporarily records programs executed by the processing circuitry 1100 and data used by such programs, etc. Specifically, the secondary storage device 1400 is a recording medium that records programs for each process of the UE 500 according to the embodiments of the present disclosure, which is an example of program data 1450.

[0457] The communication interface 1500 is an interface for the computer 1000 to connect to the external network 1550. The communication interface 1500 corresponds to the network communication unit 530 provided by the UE 500. For example, the processing circuit 1100 receives data from other devices or transmits data generated by the processing circuit 1100 to other devices via the communication interface 1500.

[0458] The input / output interface 1600 is an interface for connecting the input / output device 1650 and the computer 1000. For example, the processing circuit 1100 receives data from input devices such as a microphone 1900 or a touch panel via the input / output interface 1600. The processing circuit 1100 also transmits data to output devices such as a display unit 1700 or a speaker 2000 via the input / output interface 1600. The input / output interface 1600 may also function as a media interface for reading programs recorded on a predetermined recording medium (media). Examples of media include optical recording media such as DVDs (Digital Versatile Discs) and PDs (Phase Change Rewritable Disks), magneto-optical recording media such as MOs (Magneto-Optical Disks), tape media, magnetic recording media, or semiconductor memory.

[0459] The display unit 1700 is an interface for displaying information processed by the computer 1000. The display unit 1700 is, for example, a liquid crystal display or an organic electroluminescent display (Organic Electro Luminescence Display). Alternatively, the display unit 1700 may be a touch panel display device or an image projection device.

[0460] The camera unit 1800 is an interface for the computer 1000 to capture images. The microphone 1900 is an interface for the computer 1000 to capture sound. The speaker 2000 is an interface for the computer 1000 to output processed sound. The various parts of the computer 1000 are connected by the bus 1050. Each interface does not necessarily have to be located inside the computer 1000, but may be located outside the computer 1000 via a network or the like. Furthermore, each part of the computer 1000 may be controlled by a circuit different from the processing circuit 1100. For example, the display unit 1700 may be controlled not by the processing circuit 1100, but by a circuit dedicated to display processing provided within the display unit 1700.

[0461] For example, when computer 1000 functions as UE 500 according to an embodiment of this disclosure, the processing circuit 1100 of computer 1000 functions as a control unit 550 by executing a program loaded on RAM 1200. The secondary storage device 1400 stores the information processing program according to this disclosure and various data stored by the storage unit 520. The processing circuit 1100 reads and executes the program data 1450 from the secondary storage device 1400, but as another example, these programs may be obtained from other devices via an external network 1550. In other words, the secondary storage device 1400 is not limited to being inside computer 1000, but may be located outside computer 1000. The processing circuit 1100 is an example of an integrated circuit, and CPU, MPU, GPU, APU, ASIC, and FPGA can all be considered integrated circuits.

[0462] <<6. Conclusion>> Although the embodiments of this disclosure have been described above, the technical scope of this disclosure is not limited to the embodiments described above, and various modifications are possible without departing from the gist of this disclosure. Furthermore, components from different embodiments and modifications may be combined as appropriate.

[0463] Furthermore, the effects described in each embodiment of this specification are merely illustrative and not limiting, and other effects may also occur.

[0464] Furthermore, this technology can also take the following configurations: (1) An information processing device that provides application services to a terminal device, comprising: a control unit that acquires terminal information including application information relating to the application service from the terminal device, predicts the timing at which the terminal device will set communication quality in the future based on the terminal information, and generates calculation information for calculating future quality information relating to the communication quality that the terminal device can set at the predicted timing. (2) The information processing device according to (1), wherein the terminal information includes at least one of the location information of the terminal device and quality information relating to the communication quality. (3) The information processing device according to (1) or (2), wherein the calculation information includes at least one of the timing, the location of the terminal device at the timing predicted by the control unit based on the terminal information, the category information of the application service, and evaluation information of the communication quality. (4) The information processing device according to (3), wherein the evaluation information includes information evaluating the communication quality set at the predicted timing. (5) The information processing device according to any one of (1) to (4), wherein the future quality information includes at least one of the following: recommendation information regarding the recommended setting of the communication quality at the predicted timing, probability information regarding the probability of setting the recommended setting, time information regarding the setting time for making the setting, evaluation information regarding the evaluation of the connection destination, and parameter information regarding parameters that can be set simultaneously with the setting of the communication quality. (6) The information processing device according to any one of (1) to (5), wherein the control unit notifies the calculation information to another information processing device that generates information regarding the communication quality of the terminal device. (7) The information processing device according to (6), wherein the control unit acquires the future quality information from the other information processing device. (8) The information processing device according to (6) or (7), wherein the control unit acquires the future quality information for each base station to which the terminal device can connect.(9) The other information processing device generates the future quality information based on the calculation information, network information relating to the network to which the terminal device can connect, and at least one of the priority of the information processing device, as described in any one of (6) to (8). (10) The control unit notifies the terminal device of the future quality information, as described in any one of (1) to (9). (11) The control unit obtains a setting notification from the terminal device instructing the setting of the communication quality, as described in any one of (1) to (10). (12) The control unit requests the network to which the terminal device connects to perform the setting of the communication quality in response to the setting notification, as described in (11). (13) The control unit requests the network to which the terminal device connects to perform the setting in response to the setting notification, before the timing corresponding to the setting time for the network to perform the setting of the communication quality, as described in (11) or (12). (14) The information processing device according to (11) or (12), wherein the control unit obtains from the terminal device a setting notification instructing the terminal device to make the setting for communication quality in communication via a base station different from the base station included in the future quality information, and / or a setting notification instructing the terminal device to make the setting at a time different from the predicted timing. (15) The information processing device according to any one of (11) to (14), wherein the control unit obtains the setting notification after the future quality information has been sent but before the predicted timing, and reserves the setting for communication quality to another information processing device that generates information regarding the communication quality of the terminal device in response to the setting notification, thereby requesting the network to which the terminal device is connected to make the setting for communication quality via the other information processing device when the timing arrives. (16) The information processing device generates future quality information regarding communication quality that the terminal device can make at a timing predicted from application information relating to an application service provided to the terminal device.(17) A terminal device that receives application services via a network, comprising a control unit that notifies an information processing device of terminal information including application information relating to the application services, and acquires future quality information relating to the communication quality that the terminal device can set from the information processing device at a timing when it is predicted that the terminal device will set the communication quality based on the terminal information. (18) An information processing method for an information processing device that provides application services to a terminal device, comprising: acquiring terminal information including application information relating to the application services from the terminal device; predicting a timing when the terminal device will set the communication quality based on the terminal information; and generating calculation information for calculating future quality information relating to the communication quality that the terminal device can set at the predicted timing. (19) An information processing method in which the information processing device generates future quality information relating to the communication quality that the terminal device can set at a timing predicted from application information relating to the application services that the terminal device receives. (20) An information processing method for a terminal device that receives an application service via a network, comprising: notifying an information processing device of terminal information including application information relating to the application service; and obtaining future quality information relating to the communication quality that the terminal device may set from the information processing device at a timing when it is predicted that the terminal device will set the communication quality in the future based on the terminal information.

[0465] 30 5G System 100 Application Server (AS) 110, 210, 310, 410, 510 Communication Unit 120, 220, 320, 420, 520 Storage Unit 130, 230, 330, 440, 550 Control Unit 200 QoS Server 300 5GC 400 Base Station 500 UE

Claims

1. An information processing device that provides application services to a terminal device, comprising: a control unit that acquires terminal information including application information relating to the application service from the terminal device; predicts the timing at which the terminal device will make settings relating to communication quality in the future based on the terminal information; and generates calculation information for calculating future quality information relating to communication quality that the terminal device can set at the predicted timing.

2. The information processing apparatus according to claim 1, wherein the terminal information includes at least one of the location information of the terminal device and the quality information relating to the communication quality.

3. The information processing apparatus according to claim 1, wherein the calculated information includes the timing, the position of the terminal device at the timing as predicted by the control unit based on the terminal information, the category information of the application service, and at least one of the communication quality evaluation information.

4. The information processing apparatus according to claim 3, wherein the evaluation information includes information evaluating the communication quality set at the predicted timing.

5. The information processing apparatus according to claim 1, wherein the future quality information includes at least one of the following: recommendation information regarding the recommended settings for the communication quality at the predicted timing; probability information regarding the probability of setting the recommended settings; time information regarding the setting time for making the settings; evaluation information regarding the evaluation of the connection destination; and parameter information regarding parameters that can be set simultaneously with the settings for the communication quality.

6. The information processing apparatus according to claim 1, wherein the control unit notifies another information processing apparatus that generates information regarding the communication quality of the terminal device of the calculated information.

7. The information processing apparatus according to claim 6, wherein the control unit acquires the future quality information from the other information processing apparatus.

8. The information processing apparatus according to claim 6, wherein the control unit acquires the future quality information for each base station to which the terminal device can connect.

9. The information processing apparatus according to claim 6, wherein the other information processing apparatus generates the future quality information based on the calculation information, network information relating to a network to which the terminal device can connect, and the priority of the information processing apparatus.

10. The information processing apparatus according to claim 1, wherein the control unit notifies the terminal device of the future quality information.

11. The information processing apparatus according to claim 1, wherein the control unit obtains a setting notification from the terminal device instructing the setting relating to the communication quality.

12. The information processing apparatus according to claim 11, wherein the control unit requests the network to which the terminal device is connected to perform the settings relating to the communication quality in response to the setting notification.

13. The information processing apparatus according to claim 11, wherein the control unit requests the network to which the terminal device is connected to perform the setting in response to the setting notification, at a time corresponding to the setting time for the network to perform the setting regarding the communication quality, before the timing.

14. The information processing apparatus according to claim 11, wherein the control unit obtains from the terminal device a setting notification instructing the setting of the communication quality in communication via a base station different from the base station included in the future quality information, and / or a setting notification instructing the setting at a time different from the predicted timing.

15. The information processing apparatus according to claim 11, wherein the control unit obtains the setting notification after the sending of the future quality information but before the predicted timing, and reserves the setting for the communication quality to another information processing apparatus that generates information regarding the communication quality of the terminal device in response to the setting notification, thereby requesting the network to which the terminal device is connected to perform the setting for the communication quality via the other information processing apparatus when the timing arrives.

16. An information processing device that generates future quality information regarding the communication quality that can be set by the terminal device at a timing predicted from application information related to the application services provided to the terminal device.

17. A terminal device that receives application services via a network, comprising: a control unit that notifies an information processing device of terminal information including application information relating to the application services, and, based on the terminal information, acquires future quality information relating to the communication quality that the terminal device can set from the information processing device at a timing when it is predicted that the terminal device will set the communication quality in the future.

Images