Information processing device, information processing method, and information processing system

Abstract

An information processing device (100) includes a control unit (130). The control unit (130) requests a cellular communication system (30) to open a communication line used by a plurality of terminal devices (40) that are to be provided with a service. The control unit (130) allocates the plurality of terminal devices (40) to at least one group in accordance with the service to be provided. When provision of the service to the plurality of terminal devices (40) corresponding to the group is started, the control unit (130) determines a resource to be allocated to the plurality of terminal devices (40) corresponding to the group. The control unit (130) requests the cellular communication system (30) to secure the resource.

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device, an information processing method, and an information processing system. [Background technology]

[0002] Conventionally, when a user connects to a cellular communication system using a terminal device, the amount of data communication (amount of packets) that can be used is sometimes limited in advance by contract. If the amount of packets that can be used is exceeded, additional charges are incurred or the communication speed is limited.

[0003] In addition, there is known a system in which a terminal device communicates within a communication volume range according to a paid fee, such as a prepaid system. In this system, for example, there is a technology for managing the remaining communication volume of a terminal device for each connection destination when the terminal device connects to a communication network. In this technology, the terminal device acquires information about connection destinations with remaining communication volume, and connects to the connection destination with remaining communication volume to communicate. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-138709 Summary of the Invention [Problem to be solved by the invention]

[0005] With the development of cellular communication technology, various services have been proposed to be provided via cellular communication lines. For example, a system is conceivable in which a service such as live streaming is provided via a cellular communication line to a user who has signed a contract to receive the service by purchasing a ticket.

[0006] In such a system, if there is a limit on the amount of packets that a user can use, the communication speed may be limited during live streaming or the streaming itself may be stopped. If the communication speed is limited or the service is stopped while the service is being provided, user convenience will be significantly reduced.

[0007] Therefore, the present disclosure provides a mechanism that can prevent a decrease in user convenience while a service is being provided.

[0008] It should be noted that the above problem or object is merely one of multiple problems or objects that can be solved or achieved by multiple embodiments disclosed in this specification. [Means for solving the problem]

[0009] According to the present disclosure, there is provided an information processing device. The information processing device has a control unit. The control unit requests a cellular communication system to open a communication line to be used by multiple terminal devices to which a service is to be provided. The control unit assigns the multiple terminal devices to at least one group according to the service to be provided. When service provision to the multiple terminal devices corresponding to the group is started, the control unit determines resources to be assigned to the multiple terminal devices corresponding to the group. The control unit requests the cellular communication system to secure the resources. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram for explaining an overview of a proposed technique of the present disclosure. [Figure 2] FIG. 1 is a block diagram illustrating a configuration example of an information processing device according to an embodiment of the present disclosure. [Figure 3] FIG. 2 is a diagram illustrating an example of the configuration of a table stored in a storage unit according to an embodiment of the present disclosure. [Figure 4] 10 is a diagram illustrating an example of a ticket information table according to an embodiment of the present disclosure. [Figure 5] 10 is a diagram illustrating an example of a line information table according to an embodiment of the present disclosure. [Figure 6] 10 is a diagram illustrating an example of a share group information table according to an embodiment of the present disclosure. [Figure 7] 10 is a diagram illustrating an example of a service information table according to an embodiment of the present disclosure. [Figure 8] FIG. 1 illustrates an example of an architecture of a cellular communication system according to an embodiment of the present disclosure. [Figure 9] FIG. 2 is a block diagram illustrating a configuration example of a server device according to an embodiment of the present disclosure. [Figure 10] FIG. 1 is a block diagram illustrating a configuration example of a terminal device according to an embodiment of the present disclosure. [Figure 11] FIG. 10 is a sequence diagram illustrating an example of a flow of a line opening process according to an embodiment of the present disclosure. [Figure 12] FIG. 10 is a sequence diagram illustrating an example of a flow of a service providing process according to an embodiment of the present disclosure. [Figure 13] 10 is a flowchart illustrating an example of the flow of a QoS control process according to an embodiment of the present disclosure. [Figure 14] FIG. 10 is a sequence diagram illustrating an example of a flow of a line opening process according to a modified example of an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant description will be omitted.

[0012] In this specification and drawings, similar components of the embodiments may be distinguished by adding different letters or numbers after the same reference numeral. However, if there is no need to particularly distinguish between the similar components, only the same reference numeral will be used.

[0013] Furthermore, although specific values ​​are sometimes used in the present specification and drawings, these values ​​are merely examples and other values ​​may also be applied.

[0014] One or more embodiments (including examples and modifications) described below can be implemented independently. However, at least a portion of the embodiments described below may be implemented in appropriate combination with at least a portion of another embodiment. These embodiments may include novel features that are different from one another. Therefore, these embodiments may contribute to solving different purposes or problems and may produce different effects.

[0015] <<1. Overview of the proposed technology>> First, an overview of the proposed technology according to the present disclosure will be described. Fig. 1 is a diagram for explaining an overview of the proposed technology according to the present disclosure. The proposed technology according to the present disclosure is implemented in an information processing system 1 shown in Fig. 1. As shown in Fig. 1, the information processing system 1 includes a platform 10, a service server 20, a cellular communication system 30, and a terminal device 40.

[0016] The service server 20 is an information processing device that provides, for example, a live distribution service. The service server 20 provides a service to the terminal device 40 by transmitting live video to the terminal device 40 via the cellular communication system 30.

[0017] The cellular communication system 30 is, for example, a cellular wireless and wired network and nodes that construct the network, as defined by 3GPP (3rd Generation Partnership Project). The cellular communication system 30 is, for example, a communication system that uses a radio access technology (RAT) such as LTE (Long Term Evolution) or NR (New Radio). Here, the radio access network may be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or an NG-RAN (Next Generation Radio Access Network).

[0018] The cellular communication system 30 provides a communication path to the service server 20, regardless of whether it is via the Internet or a closed network, to a terminal device 40 used by a service user (hereinafter also referred to as a user).

[0019] The terminal device 40 connects to the cellular communication system 30 and receives services from the service server 20 by signing a contract to receive services provided by the service server 20, for example, when the user purchases a concert ticket.

[0020] In the information processing system 1 of the present disclosure, the contract for receiving a service includes a contract for opening a line for receiving the service to the cellular communication system 30. That is, while the user is receiving the service (for example, while live streaming is being performed), the user enjoys the service using the line opened with the cellular communication system 30. On the other hand, when the service is not being provided, such as before the service starts or after the service ends (for example, before the live streaming starts or after the streaming ends), the user cannot use the line.

[0021] In this manner, the information processing system 1 of the present disclosure is a system in which the service server 20 provides a service to the terminal device 40 for a predetermined period of time using a line of the cellular communication system 30 opened for the purpose of providing the service.

[0022] Here, the platform 10 makes a contract for service provision (for example, ticket sales) on behalf of the service server 20. The platform 10 also makes a contract for opening a line for the cellular communication system 30 on behalf of the user who has made a contract for service provision (for example, who has purchased a ticket).

[0023] 1, for example, when the platform 10 receives service registration for, for example, live streaming from the service server 20 (step S1), the platform 10 sells tickets for the service. A user purchases a ticket from the platform 10 via, for example, the terminal device 40 (step S2).

[0024] Although one terminal device 40 purchases a ticket in FIG. 1, the number of terminal devices 40 that purchase tickets may be one or more.

[0025] Thereafter, the platform 10 makes an alternative contract for a line with a BSS (Business Support System, not shown) of the cellular communication system 30 on behalf of the user (step S3), and opens the line.

[0026] When the service start time arrives, the service server 20 uses the line of the cellular communication system 30 to provide the service to the terminal device 40 (step S4).

[0027] As described above, when the terminal device 40 connects to the cellular communication system 30, the amount of data communication that can be used is often determined based on, for example, a fee (coupon fee), etc. In this case, if the amount of data communication (amount of packets) that can be used is exceeded, a bandwidth control device (not shown) provided in the cellular communication system 30 often limits the bandwidth of the excess terminal device 40 to around several hundred kbps.

[0028] 1, if the amount of packets that can be used is exceeded (i.e., if a coupon expires) while the service server 20 is providing a service to the terminal device 40, the user will be unable to fully enjoy the service. If the amount of packets exceeds the limit (if a coupon expires) while the service is being provided, the quality of the service will deteriorate, and user convenience will be reduced.

[0029] Therefore, while the service server 20 is providing the service, it is desirable to perform bandwidth control so that the amount of packets does not exceed the upper limit.

[0030] Here, in the cellular communication system 30, for example, a bandwidth control device controls bandwidth based on whether or not the packet amount is exceeded (coupon expiration), the priority of packets, and the like.

[0031] For example, in recent years, the cellular communication system 30 has made available an API (Application Programming Interface) for service providers (e.g., the platform 10). This has enabled the service providers to use some of the functions of the cellular communication system 30, such as QoS (Quality of Service) control. In other words, the service providers have become able to communicate with the bandwidth control devices via the API.

[0032] However, from the viewpoint of the business model of the cellular communication system 30, it is difficult for a service provider to set, via an API, rules relating to the rate plans of the cellular communication system 30. For example, it is not realistic for a service provider to set, via an API, a rule (e.g., a new upper limit on the amount of packets) that exceeds the upper limit on the amount of packets set by the cellular communication system 30.

[0033] Therefore, in the information processing system 1 of the present disclosure, the platform 10 assigns a plurality of terminal devices 40 to at least one group (a share group, which will be described later) according to the services provided by the service server 20.

[0034] When service provision to a plurality of terminal devices 40 corresponding to a group is started, the platform 10 determines resources to be allocated to the plurality of terminal devices 40 corresponding to the group. The platform 10 performs QoS control of the line used by the terminal devices 40 by requesting the cellular communication system 30 to secure the resources (step S5 in FIG. 1).

[0035] For example, the platform 10 determines resources to be allocated to the multiple terminal devices 40 so that the amount of packets does not exceed an upper limit while the service is being provided. As a result, the platform 10 can perform QoS control of the lines used by the terminal devices 40 so that coupons for the terminal devices 40 do not expire while the service server 20 is providing the service. In this way, the platform 10 according to the present disclosure can prevent a decrease in user convenience while the service is being provided.

[0036] For example, when the service provided by the service server 20 ends, the platform 10 cancels the line with the cellular communication system 30. As a result, the terminal device 40 can no longer connect to the cellular communication system 30.

[0037] In this way, in the information processing system 1 of the present disclosure, the platform 10 makes a proxy contract (conclusion and termination of contract) with the cellular communication system 30 for the line of the terminal device 40 that has made a service contract by, for example, purchasing a ticket. This allows the information processing system 1 to provide a predetermined quality of service to the terminal device 40 using the line during the period in which the service server 20 is providing the service.

[0038] Although the information processing system 1 shown in Fig. 1 has one service server 20, this is not limiting. There may be multiple service servers 20. Furthermore, although Fig. 1 shows a case where the service server 20 provides one service, this is not limiting. The service server 20 may provide multiple services.

[0039] 1 shows a case where there is one cellular communication system 30, but this is not limiting. There may be multiple cellular communication systems 30. For example, the information processing system 1 may include multiple cellular communication systems 30 each operated and / or managed by a different mobile network operator (MNO). Furthermore, the service server 20 may provide one service to the terminal device 40 via multiple different cellular communication systems 30.

[0040] 1 shows a case where there is one terminal device 40, but this is not limiting. There may be multiple terminal devices 40. In this case, the multiple terminal devices 40 may each be connected to a different cellular communication system 30. Furthermore, the multiple terminal devices 40 may each receive different services from different service servers 20.

[0041] <<2. Example of information processing system configuration>> 1, an information processing system 1 according to an embodiment of the present disclosure includes a platform 10, a service server 20, a cellular communication system 30, and a terminal device 40. Each component will be described below.

[0042] <2.1. Information processing device> First, the information processing device 100 will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example configuration of the information processing device 100 according to an embodiment of the present disclosure. The information processing device 100 is a device that functions as a platform 10, for example.

[0043] The information processing device 100 shown in Fig. 2 includes a communication unit 110, a storage unit 120, and a control unit 130. Note that the configuration shown in Fig. 2 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the information processing device 100 may be distributed and implemented in multiple physically separated configurations. For example, the information processing device 100 may be configured by multiple server devices.

[0044] [Communications Department 110] The communication unit 110 is a communication interface for communicating with other devices. The communication unit 110 may be a network interface or a device connection interface. For example, the communication unit 110 may be a LAN (Local Area Network) interface such as a NIC (Network Interface Card), or a USB (Universal Serial Bus) interface configured with a USB host controller, a USB port, etc. The communication unit 110 may be a wired interface or a wireless interface. The communication unit 110 functions as a communication means of the information processing device 100. The communication unit 110 communicates with the service server 20, the cellular communication system 30, and the terminal device 40 under the control of the control unit 130.

[0045] [Storage section 120] The storage unit 120 is a data readable / writable storage device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, a hard disk, etc. The storage unit 120 functions as a storage means of the information processing device 100.

[0046] The storage unit 120 stores, for example, information for providing a service to the terminal device 40. Fig. 3 is a diagram showing an example of the configuration of a table stored in the storage unit 120 according to the embodiment of the present disclosure.

[0047] (Ticket information table) 3, the storage unit 120 stores ticket information about tickets to be sold as a ticket information table. The ticket information includes, for example, information about at least one of a ticket ID, ticket name, price, status, line ID, service ID, and share group ID.

[0048] 4 is a diagram illustrating an example of a ticket information table according to an embodiment of the present disclosure. The ticket information table illustrated in FIG. 4 manages information related to a ticket ID, a ticket name, a price, a status, a line ID, a share group ID, and a service ID.

[0049] "Ticket ID" stores identification information that is assigned to each ticket sold by the platform 10 and identifies each ticket. "Ticket Name" stores a name indicating the type of ticket, such as "Live 1," "Live 1 Premium," or "Live 2" in the example of FIG. 4. "Price" stores the selling price of the ticket corresponding to the ticket type. For example, the example of FIG. 4 indicates that "Live 1" will be sold for "3,000 yen," and "Live 1 Premium" will be sold for "6,000 yen."

[0050] "Status" stores information about the ticket sales status. For example, in Figure 4, "Status" stores whether the ticket is "Purchased" or "Not Purchased." "Line ID" stores identification information that identifies line information related to the line contract with the cellular communication system 30.

[0051] "Share group ID" stores identification information that identifies a share group. A share group includes multiple terminal devices 40 with open lines. The multiple terminal devices 40 share a predetermined amount of data communication (e.g., packet volume) to receive the service. "Service ID" includes identification information that identifies the service provided by the service server 20.

[0052] As shown in Figure 4, "Live 1" and "Live 1 Premium" have different "ticket names" but the "service ID" is the same, "1." In this way, even with the same service, the service can be provided in different modes, for example, with different data communication volumes (for example, "Live 1" is "20 Gbytes" and "Live 1 Premium" is "40 Gbytes").

[0053] Also, in FIG. 4, "ticket name" and "share group ID" correspond one-to-one, that is, if the "ticket name" is the same, the "share group ID" is also the same, but this is not limited to this. For example, tickets with the same "ticket name" may be divided into multiple share groups. For example, if there are 50 tickets with the "ticket name" "Live 1", the tickets with the "ticket name" "Live 1" may be divided into two share groups of 25 tickets each (for example, share groups with "share group ID" "1-1" and "1-2").

[0054] Tickets with different "ticket names" will not be classified into the same share group. For example, a ticket with the "ticket name" "Live 1" and a ticket with the "Live 1 Premium" will not be classified into the same share group (for example, a share group with a "share group ID" of "1").

[0055] (Line information table) Returning to Fig. 3, as shown in Fig. 3, the storage unit 120 stores line information related to the lines of the cellular communication system 30 as a line information table. The line information includes, for example, at least one of a line ID, an MSISDN (Mobile Subscriber Integrated Services Digital Network Number), a SUPI (Subscriber Permanent Identifier), and information related to the line status.

[0056] 5 is a diagram illustrating an example of a line information table according to an embodiment of the present disclosure. In the line information table illustrated in FIG. 5, information related to a line ID, MSISDN, SUPI, and line status is managed.

[0057] "Line ID" stores identification information for identifying line information related to the line contract with the cellular communication system 30. This "line ID" corresponds to the "line ID" in the ticket information table shown in FIG.

[0058] "MSISDN" and "SUPI" store information about the MSISDN and SUPI corresponding to the line ID, respectively.

[0059] The "Line Status" indicates whether the line is open or closed. For example, a ticket with a "Ticket ID" of "1" has been purchased by a user (see Figure 4). As will be explained in more detail later, the line is opened when the ticket is purchased. In this way, a line whose ticket "Status" is "Purchased" (see Figure 4) is managed with a "Line Status" of "Started" as shown in Figure 5. On the other hand, a line whose ticket "Status" is "Not Purchased" (see Figure 4) is not open, and is managed with a "Line Status" of "Stopped" as shown in Figure 5.

[0060] (Share group information table) Returning to Fig. 3, as shown in Fig. 3, the storage unit 120 stores share group information related to share groups as a share group information table. The share group information includes, for example, at least one of a share group ID, the number of shares, a DNN (Data Network Name), and information related to the amount of packets.

[0061] Fig. 6 is a diagram showing an example of a share group information table according to an embodiment of the present disclosure. In the share group information table shown in Fig. 6, information related to the share group ID, the number of shares, the DNN, and the amount of packets is managed.

[0062] "Share group ID" stores identification information for identifying a share group managed by the platform 10. This "share group ID" corresponds to the "share group ID" in the ticket information table shown in FIG.

[0063] "Number of shares" stores information about the number of tickets included in one share group. For example, in Figure 4, the number of tickets for which the "share group ID" is "1" is "3." Therefore, "3" is stored in the "number of shares" for which the "share group ID" shown in Figure 6 is "1."

[0064] "DNN" stores information about the DNN of each line. As shown in Fig. 6, in an embodiment of the present disclosure, a share group is created for each DNN when a line contract is made. That is, when a line contract is made, the platform 10 manages lines (tickets) with the same DNN as the same share group.

[0065] "Packet volume" stores information about the upper limit of the data communication volume shared by the share group. In the example of Fig. 6, the "packet volume" of the share group whose "share group ID" is "1" is "20 Gbytes" and the "number of shares" is "3". Therefore, up to three terminal devices 40 that have purchased tickets can share up to 20 Gbytes of packet volume to receive the service.

[0066] (Service Information Table) Returning to Fig. 3, as shown in Fig. 3, storage unit 120 stores service information related to services as a service information table. The service information includes, for example, at least one of the following information: a service ID, a service name, a start date and time, an end date and time, a service status, and an address.

[0067] 7 is a diagram illustrating an example of a service information table according to an embodiment of the present disclosure. The service information table illustrated in FIG. 7 manages information related to a service ID, a service name, a start date and time, an end date and time, a service status, and an address.

[0068] The "service ID" stores identification information for identifying a service managed by the platform 10. This "service ID" corresponds to the "service ID" in the ticket information table shown in FIG.

[0069] "Service Name" indicates the type of service, for example, "Live 1," "Live 2," etc., in the example of Figure 7. The "Service Name" may be the same as or different from the "Ticket Name" (see Figure 4).

[0070] The start date and time and the end date and time of the service are stored in "Start date and time" and "End date and time," respectively. The address of the service server 20 that provides the service is stored in "Address."

[0071] [Control unit 130] Returning to FIG. 2, the control unit 130 is a controller that controls each unit of the information processing device 100. The control unit 130 is realized by a processor such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a GPU (Graphics Processing Unit). For example, the control unit 130 is realized by the processor executing various programs stored in a storage device inside the information processing device 100 using a RAM (Random Access Memory) or the like as a working area. Note that the control unit 130 may also be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The CPU, MPU, GPU, ASIC, and FPGA can all be considered as controllers.

[0072] The control unit 130 includes a contract acceptance unit 131, a contract control unit 132, a service control unit 133, and a QoS control unit 134. Each block constituting the control unit 130 (contract acceptance unit 131 to QoS control unit 134) is a functional block indicating a function of the control unit 130. These functional blocks may be software blocks or hardware blocks. For example, each of the above-mentioned functional blocks may be a software module realized by software (including a microprogram), or may be a circuit block on a semiconductor chip (die). Of course, each functional block may be a processor or an integrated circuit. The functional blocks may be configured in any manner. The control unit 130 may be configured by functional units different from the above-mentioned functional blocks.

[0073] (Contract Reception Department 131) The contract acceptance unit 131 accepts ticket purchases from users. The contract acceptance unit 131 may accept ticket purchases directly from users, or may accept ticket purchases via the terminal device 40 used by the users.

[0074] When a ticket is purchased by a user, the contract acceptance unit 131 updates, for example, the "status" in the ticket information table in the storage unit 120 from "not purchased" to "purchased." Furthermore, when a ticket is purchased by a user, the contract acceptance unit 131 notifies the contract control unit 132 to that effect.

[0075] (Contract control unit 132) The contract control unit 132 makes a line contract with the MNO (hereinafter also referred to as the carrier) that operates and / or manages the cellular communication system 30 on behalf of the user via the BSS (not shown) of the cellular communication system 30. The contract control unit 132 makes a line substitution contract in accordance with service information (for example, the number of tickets to be sold and the service quality required for the service) acquired by the service control unit 133, which will be described later. The contract control unit 132 updates, for example, a line information table and a share group information table in accordance with the concluded contract.

[0076] Furthermore, when the contract control unit 132 receives a notification from the contract acceptance unit 131 regarding a ticket purchase by a user, it opens a line corresponding to the "ticket ID" of the purchased ticket. For example, the contract control unit 132 opens the line via a BSS (not shown) of the cellular communication system 30. When the contract control unit 132 opens the line, it updates, for example, the "line status" in the line information table of the storage unit 120 from "stopped" to "started."

[0077] Furthermore, the contract control unit 132 performs cancellation processing for the line for which the provision of service has ended. After the cancellation processing, the contract control unit 132 can delete information related to the canceled line from the storage unit 120.

[0078] (Service control unit 133) The service control unit 133 acquires service information related to the service from the service server 20 via the communication unit 110. The service information may include at least one of the following information: Information about the name of the service provided by the service server 20 (service name) -Ticket type to be sold (ticket name) Information on the number of tickets sold by type Information on sales prices for each type of ticket Information about the service start date and time Information about the end date and time of the service Information about the quality of service required for each type of service

[0079] The information regarding the service quality required for each type of service may be information indicating a specific packet volume and / or throughput, etc., or may be information indicating an index of service quality (e.g., high quality, low quality, etc.).

[0080] When the service control unit 133 acquires the service information, it updates the ticket information table, the service information table, etc. in the storage unit 120. Furthermore, when the service control unit 133 acquires the service information, it requests the contract control unit 132 to make an alternative contract for a line according to the acquired service information.

[0081] The service control unit 133 notifies the service server 20 of the start of the service at the service start time based on the service start date and time ("start date and time" in FIG. 7) stored in the service information table. The service control unit 133 also notifies the QoS control unit 134 of the start of the service.

[0082] The service control unit 133 notifies the service server 20 of the end of the service at the end time of the service based on the service end date and time ("End date and time" in FIG. 7) stored in the service information table. The service control unit 133 also notifies the QoS control unit 134 of the end of the service at the end time of the service.

[0083] (QoS control unit 134) When notified of the start of service from the service control unit 133, the QoS control unit 134 determines resources for the terminal device 40 that will receive the service. The QoS control unit 134 determines, for example, for each share group, the average bandwidth during the provision of service to the terminal device 40.

[0084] More specifically, the QoS control unit 134 determines the average bandwidth of the terminal device 40 based on at least one of the upper limit of the packet amount assigned to the share group (see "Packet amount" in FIG. 6), the number of opened lines included in the share group, and the service provision time. The QoS control unit 134 calculates the average bandwidth of the terminal device 40 receiving the service for each share group based on the following formula (1):

[0085] Average bandwidth = Amount of packets allocated to a share group / (Number of open lines x Service duration) (1)

[0086] The service providing time can be calculated from the service start time and the service end time.

[0087] The QoS control unit 134 requests the determined average bandwidth from the cellular communication system 30. The QoS control unit 134 may request the average bandwidth via a Network Exposure Function (NEF, not shown) of the cellular communication system 30, or may directly request a Policy Control Function (PCF, not shown).

[0088] When receiving a service termination notification from the service control unit 133, the QoS control unit 134 decides to release the resources that the terminal device 40 has been using. The QoS control unit 134 requests the cellular communication system 30 to release the resources (e.g., bandwidth) that have been used to provide the service. The QoS control unit 134 may notify the release of the bandwidth via the NEF of the cellular communication system 30, or may notify the PCF directly.

[0089] Furthermore, the QoS control unit 134 may update the average bandwidth requested from the cellular communication system 30 while the service server 20 is providing the service. For example, the QoS control unit 134 calculates the average bandwidth of the terminal device 40 receiving the service at a predetermined interval.

[0090] The QoS control unit 134 calculates the average bandwidth based on, for example, the amount of packets available in the share group at the time of calculating the average bandwidth (hereinafter also referred to as the remaining packet amount) and the remaining provision time of the service (hereinafter also referred to as the remaining provision time). The QoS control unit 134 calculates the average bandwidth using, for example, the following formula (2):

[0091] Average bandwidth = remaining packets in the share group / (number of open lines x remaining service time) (2)

[0092] The QoS control unit 134 may acquire the remaining packet amount of the share group from the cellular communication system 30. Alternatively, the QoS control unit 134 may acquire the packet amount used by the terminal devices 40 included in the share group from the cellular communication system 30, and calculate the remaining packet amount based on the used packet amount.

[0093] The QoS control unit 134 requests the determined average bandwidth from the cellular communication system 30. The QoS control unit 134 may request the average bandwidth via the NEF of the cellular communication system 30, or may request the PCF directly.

[0094] <2.2. Example of cellular communication system configuration> Next, an example of the network architecture of the cellular communication system 30 according to an embodiment of the present disclosure will be described. Here, as an example of the network architecture of the cellular communication system 30, the architecture of a fifth-generation mobile communication system (5G) will be described.

[0095] 8 is a diagram illustrating an example of the architecture of a cellular communication system 30 according to an embodiment of the present disclosure. The cellular communication system 30 includes a core network CN, an (R)AN 330, and a BSS 310.

[0096] The 5G core network CN is also called 5GC (5G Core) / NGC (Next Generation Core). Hereinafter, the 5G core network CN is also referred to as 5GC / NGC. The core network CN is connected to a UE (User Equipment) 40 via an (R)AN 330. The UE 40 refers to a terminal device 40.

[0097] The (R)AN 330 has the function of enabling connection to a Radio Access Network (RAN) and to an Access Network (AN) other than the RAN. The (R)AN 330 includes a base station called a gNB or ng-eNB.

[0098] The core network CN mainly performs connection permission and session management when the UE 40 connects to the network. The core network CN may be configured with one or more information processing devices. The core network CN includes a user plane function group and a control plane function group.

[0099] The user plane functions include a User Plane Function (UPF) 340 and a Data Network (DN) 350. The UPF 340 has a function for processing the user plane. The UPF 340 includes a function for routing / forwarding data handled in the user plane. The DN 350 has a function for providing a connection to an operator's own services, such as an MNO (Mobile Network Operator), an Internet connection, or a connection to a third-party service, such as a service server 20. In this way, the user plane functions act as a gateway that serves as the boundary between the core network CN and the Internet.

[0100] The control plane function group includes an AUSF (Authentication Server Function) 301, an NEF 302, an NRF (Network Repository Function) 303, an NSSF (Network Slice Selection Function) 304, a PCF 305, an SMF (Session Management Function) 306, an UDM (Unified Data Management) 307, and an AMF (Access and Mobility Management Function) 309.

[0101] The AUSF 301 has an authentication function. The NEF 302 has a function of providing network function capabilities and events to third parties, AFs (Application Functions), and edge computing functions. In this embodiment, the NEF 302 presents the core network CN functions as an API to, for example, the platform 10 or a service provider.

[0102] The NRF 303 has the function of discovering network functions and maintaining network function profiles. The NSSF 304 has the function of selecting network slices.

[0103] The PCF 305 has functions related to the control of line charging rules and network policies. Note that, although Fig. 8 shows a case where the platform 10 is connected to the core network CN via the NEF 302, the platform 10 may be directly connected to the PCF 305.

[0104] The SMF 306 has functions such as session management, IP allocation and management for the UE 40, etc. The UDM 307 has functions such as generating 3GPP AKA authentication information and processing user IDs, and the AMF 309 has functions such as registration processing for the UE 40, connection management, and mobility management.

[0105] Note that the communication between the platform 10 and the PCF 305 and the communication between the platform 10 and the NEF 302 are performed using, for example, the N5 interface and the N33-N30 interface in 3GPP TS23.501.

[0106] For example, as described above, when the platform 10 requests an average bandwidth from the PCF 305, the platform 10 uses Npcf_PolicyAuthorization to make the request, whether the request is made directly to the PCF 305 or via the NEF 302. Note that Npcf_PolicyAuthorization is described in Table 5.2.5.1-1 NF Services Provided by PCF in 3GPP TS23.502.

[0107] The types of data used when the platform 10 directly or indirectly communicates with the PCF 305 are described in 6.2.1 of 3GPP TS23.503 (e.g., 6.2.1.2 input for PCC (policy and charging control) decisions). More specifically, the platform 10 sets the average bandwidth to Bandwidth described in 3GPP TS23.503 and specifies SUPI as Subscriber Identifier. This allows the platform 10 to request the PCF 305 to use the determined average bandwidth as the bandwidth of the line (or terminal device 40) corresponding to the SUPI.

[0108] The above-described bandwidth control device can be realized as at least one function of the UPF 340, the SMF 306, and the PCF 305, for example.

[0109] The BSS 310 is connected to the core network CN and has a function of updating line contract information, issuing a SIM (Subscriber Identity Module), etc. The BSS 310 may be disclosed to a carrier or a Mobile Virtual Network Operator (MVNO) as an operation terminal (information processing device) or an API installed in a store, for example.

[0110] Although the case where the cellular communication system 30 is a fifth generation mobile communication system (5G) has been described here, the present invention is not limited to this. For example, the cellular communication system 30 may be another wireless communication system.

[0111] For example, the cellular communication system 30 may be LTE, that is, the core network CN of the cellular communication system 30 may be an LTE core network (Evolved Packet Core (EPC)). In this case, the core network CN may include a Mobility Management Entity (MME), a Serving gateway (S-GW), a PDN gateway (P-GW), a Policy and Charging Rule Function (PCRF), and a Home Subscriber Server (HSS).

[0112] The MME is a control node that handles control plane signals and manages the mobility of the terminal device 40. The S-GW / P-GW is a node that handles user plane signals. The PCRF is a control node that controls policies such as QoS (Quality of Service) for PDU sessions or bearers and billing. The HSS is a control node that handles subscriber data and performs service control.

[0113] The platform 10 may request, for example, an average bandwidth from, for example, a PCRF. The above-described bandwidth control device may be realized as, for example, at least one function of a PCEF (Policy and Charging Enforcement Function) and a PCRF. The PCEF may be included in the functions of the P-GW.

[0114] <2.3. Server equipment> Next, the server device 200 will be described with reference to Fig. 9. Fig. 9 is a block diagram showing an example configuration of the server device 200 according to an embodiment of the present disclosure. The server device 200 is a device that functions as the service server 20, for example.

[0115] The server device 200 shown in Fig. 9 includes a communication unit 210, a storage unit 220, and a control unit 230. Note that the configuration shown in Fig. 9 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the server device 200 may be distributed and implemented in multiple physically separated configurations. For example, the server device 200 may be configured by multiple server devices.

[0116] [Communications Department 210] The communication unit 210 is a communication interface for communicating with other devices. The communication unit 210 may be a network interface or a device connection interface. For example, the communication unit 210 may be a LAN (Local Area Network) interface such as a NIC (Network Interface Card), or a USB (Universal Serial Bus) interface configured by a USB host controller, a USB port, etc. The communication unit 210 may be a wired interface or a wireless interface. The communication unit 210 functions as a communication means of the server device 200. The communication unit 210 communicates with the platform 10 and the cellular communication system 30 under the control of the control unit 230.

[0117] [Storage section 220] The storage unit 220 is a data readable / writable storage device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, a hard disk, etc. The storage unit 220 functions as a storage means of the server device 200.

[0118] [Control unit 230] The control unit 230 is a controller that controls each unit of the server device 200. The control unit 230 is realized by a processor such as a central processing unit (CPU), a micro processing unit (MPU), or a graphics processing unit (GPU). For example, the control unit 230 is realized by a processor executing various programs stored in a storage device inside the server device 200 using a random access memory (RAM) or the like as a working area. The control unit 230 may also be realized by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The CPU, MPU, GPU, ASIC, and FPGA can all be considered as controllers.

[0119] The control unit 230 can function as a control unit (application control unit) of an application (not shown) that provides a service to the terminal device 40. For example, if the service server 20 is a device that provides a live distribution service that distributes images captured by a camera (not shown) in real time, the control unit 230 controls the application that acquires and distributes the captured images.

[0120] <2.4. Terminal Device> Next, a description will be given of a terminal device 40 according to an embodiment of the present disclosure. The terminal device 40 is a wireless communication device that performs wireless communication with other communication devices such as the cellular communication system 30 and the platform 10. The terminal device 40 is, for example, a mobile phone, a smart device (smartphone or tablet), a PDA (Personal Digital Assistant), or a personal computer.

[0121] Fig. 10 is a block diagram showing an example configuration of a terminal device 40 according to an embodiment of the present disclosure. The terminal device 40 shown in Fig. 10 includes a wireless communication unit 41, a storage unit 42, and a control unit 43. Note that the configuration shown in Fig. 10 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the terminal device 40 may be distributed and implemented in multiple physically separated configurations.

[0122] [Wireless Communication Unit 41] The wireless communication unit 41 is a signal processing unit for wireless communication with other wireless communication devices. The wireless communication unit 41 operates under the control of the control unit 43. The wireless communication unit 41 operates under the control of the control unit 43. The wireless communication unit 41 supports one or more wireless access methods. For example, the wireless communication unit 41 may support both NR and LTE. The wireless communication unit 41 may also support other wireless access methods such as W-CDMA and cdma2000.

[0123] The wireless communication unit 41 includes a reception processing unit 411, a transmission processing unit 412, and an antenna 413. The wireless communication unit 41 may include a plurality of reception processing units 411, a plurality of transmission processing units 412, and a plurality of antennas 413. When the wireless communication unit 41 supports a plurality of wireless access methods, each unit of the wireless communication unit 41 may be configured separately for each wireless access method. For example, the reception processing unit 411 and the transmission processing unit 412 may be configured separately for LTE and NR.

[0124] The reception processing unit 411 processes downlink signals received via the antenna 413. The reception processing unit 411 includes a radio reception unit 411a, a demultiplexing unit 411b, a demodulation unit 411c, and a decoding unit 411d.

[0125] The radio receiving unit 411a performs downconversion, removal of unnecessary frequency components, control of amplification level, quadrature demodulation, conversion to a digital signal, removal of guard intervals, extraction of frequency domain signals by fast Fourier transform, etc. on the downlink signal. The demultiplexing unit 411b separates the signal output from the radio receiving unit 411a into a downlink channel, a downlink synchronization signal, and a downlink reference signal. The downlink channel is, for example, a PBCH (Physical Broadcast Channel), a PDSCH (Physical Downlink Shared Channel), a PDCCH (Physical Downlink Control Channel), etc. The demodulating unit 411c demodulates the received signal using a modulation scheme such as BPSK, QPSK, 16QAM, 64QAM, or 256QAM for the modulation symbols of the downlink channel. The decoding unit 411d performs decoding processing on the coded bits of the demodulated downlink channel. The decoded downlink data and downlink control information are output to the control unit 43.

[0126] The transmission processing unit 412 performs transmission processing of the uplink control information and the uplink data, and includes an encoding unit 412a, a modulation unit 412b, a multiplexing unit 412c, and a radio transmission unit 412d.

[0127] The encoder 412a encodes the uplink control information and uplink data input from the controller 43 using a coding method such as block coding, convolutional coding, or turbo coding. The modulator 412b modulates the coded bits output from the encoder 412a using a predetermined modulation method such as BPSK, QPSK, 16QAM, 64QAM, or 256QAM. The multiplexer 412c multiplexes the modulation symbols of each channel and the uplink reference signal, and allocates the multiplexed symbols to predetermined resource elements. The radio transmitter 412d performs various signal processing on the signal from the multiplexer 412c. For example, the radio transmitter 412d performs processing such as conversion to the time domain using an inverse fast Fourier transform, addition of a guard interval, generation of a baseband digital signal, conversion to an analog signal, quadrature modulation, upconversion, removal of unnecessary frequency components, and power amplification. The signal generated by the transmission processor 412 is transmitted from the antenna 413.

[0128] The antenna 413 is an antenna device (antenna unit) that converts electric current and radio waves into each other. The antenna 413 may be configured with one antenna element (for example, one patch antenna) or multiple antenna elements (for example, multiple patch antennas). When the antenna 413 is configured with multiple antenna elements, the wireless communication unit 41 may be configured to be capable of beamforming. For example, the wireless communication unit 41 may be configured to generate a directional beam by controlling the directivity of a wireless signal using the multiple antenna elements.

[0129] [Storage unit 42] The storage unit 42 is a data readable / writable storage device such as a DRAM, an SRAM, a flash memory, a hard disk, etc. The storage unit 42 functions as a storage means of the terminal device 40.

[0130] [Control unit 43] The control unit 43 is a controller that controls each unit of the terminal device 40. The control unit 43 is realized by a processor such as a CPU or an MPU. For example, the control unit 43 is realized by a processor executing various programs stored in a storage device inside the terminal device 40 using RAM or the like as a work area. The control unit 43 may also be realized by an integrated circuit such as an ASIC or an FPGA. The CPU, MPU, ASIC, and FPGA can all be considered as controllers. The control unit 43 may also be realized by a GPU in addition to or instead of a CPU.

[0131] <<3. Information Processing>> An example of information processing executed in the information processing system 1 according to an embodiment of the present disclosure will be described. In the information processing system 1 according to an embodiment of the present disclosure, a line opening process and a service providing process are executed as information processing.

[0132] <3.1. Line Activation Processing> First, a line opening process executed in the information processing system 1 will be described with reference to Fig. 11. Fig. 11 is a sequence diagram showing an example of the flow of the line opening process according to an embodiment of the present disclosure.

[0133] 11, the platform 10 accepts the registration of a service from the service server 20 (step S101). Here, for example, it is assumed that the platform 10 has accepted the registration of a service whose "service name" is "Live 1." Furthermore, when the service is registered, the platform 10 acquires service information related to the service (such as the number and type of tickets to be sold, the start and end times of the service, etc.).

[0134] The platform 10 updates the service information table based on the acquired service information (step S102). For example, the platform 10 assigns a service ID "1" to the service for which registration has been accepted, and stores the service start time, end time, etc. in the service information table.

[0135] Next, the platform 10 performs line registration with the BSS 310 (step S103). More specifically, the platform 10 performs line registration with the cellular communication system 30 via the BSS 310. At this time, the platform 10 performs line registration according to the type of ticket and the number of tickets sold.

[0136] For example, the platform 10 registers lines with line IDs "1" to "3" as lines for a service with the service name "Live 1" and lines for a ticket with the ticket name "Live 1". The platform 10 also registers lines with line IDs "4" and "5" as lines for a service with the service name "Live 1" and lines for a ticket with the ticket name "Live 1 Premium".

[0137] The platform 10 updates the line information table based on the information related to the registered lines (step S104). For example, the platform 10 updates the line information corresponding to the line IDs "1" to "5" shown in Fig. 5. Note that in Fig. 5, the line statuses of the line IDs "1", "2", "4", and "5" are "started", but at the stage when the platform 10 registers the lines, the line status is "stopped".

[0138] Returning to Fig. 11, the platform 10 updates the share group information table based on the information related to the registered lines (step S105). For example, the platform 10 classifies the registered multiple lines into different share groups for each DNN, and updates the share group information table. In the example of Fig. 5, the platform 10 classifies the lines so that the line IDs "1" to "3" are included in one share group, and the line IDs "4" and "5" are included in one share group.

[0139] Returning to Figure 11, the platform 10 updates the ticket information table based on the information about the registered line (step S106). For example, the platform 10 updates the ticket information corresponding to "Live 1" and "Live 1 Premium" shown in Figure 4. Note that in Figure 4, the status of tickets with ticket IDs "1," "2," "4," and "5" is "Purchased," but at the stage when the platform 10 registers the line, the status is assumed to be "Not Purchased."

[0140] Returning to FIG. 11, it is assumed that the user next purchases a ticket sold by the platform 10 (step S107). The platform 10 requests the BSS 310 to activate the line (step S108). For example, if the user purchases a ticket with ticket ID "1", the platform 10 requests the BSS 310 to activate a SIM corresponding to the line with line ID "1" and to ship the SIM.

[0141] When the line is opened, the platform 10 updates the ticket information table (step S109). The platform 10 updates the status of the line ID "1" in FIG. 4 to "Purchased".

[0142] Returning to Fig. 11, the platform 10 updates the ticket information table (step S110). The platform 10 updates the line status of the line ID "1" in Fig. 5 to "started".

[0143] Returning to Figure 11, upon receiving the SIM delivery request, BSS 310 delivers the SIM to the user who purchased the ticket (step S111). The SIM is delivered to the user, for example, by mail. When the user installs the SIM in terminal device 40, the user is able to receive services from service server 20 via cellular communication system 30.

[0144] In the following description, it is assumed that tickets with ticket IDs "1," "2," "4," and "5" shown in FIG. 4 have been purchased.

[0145] <3.2. Service provision processing> 12 is a sequence diagram illustrating an example of the flow of a service provision process according to an embodiment of the present disclosure. Here, an example of the flow of a service provision process for providing a service with the service name "LIVE 1" will be described.

[0146] 12, the platform 10 refers to the start time in the service information table (step S201) and monitors the start time of the service. When the start time of the service arrives, the platform 10 executes QoS control processing (step S202). By executing the QoS control processing, the platform 10 determines the average bandwidth to be allocated to the terminal device 40 that receives the service. Details of the QoS control processing will be described later with reference to FIG. 13.

[0147] The platform 10 transmits a service start notification to the service server 20 (step S203). The platform 10 also transmits a service start notification including a QoS control request to the NEF 302 (step S204). Note that in FIG. 12, the platform 10 requests QoS control (e.g., average bandwidth) from the PCF 305 by transmitting the service start notification to the NEF 302, but this is not limiting. For example, the platform 10 may request QoS control by directly transmitting the service start notification to the PCF 305.

[0148] The platform 10 updates the service information table (step S205). For example, the platform 10 updates the service status of "Live 1" in Fig. 7 to "Service in progress".

[0149] Returning to Figure 12, upon receiving the service start notification from the platform 10, the service server 20 provides the service to the user using the line of the cellular communication system 30 (step S206). For example, the service server 20 provides the service (for example, delivery of captured images) to the terminal device 40 used by the user, in other words, to the terminal device 40 equipped with the SIM sent from the BBS 310.

[0150] While the service server 20 is providing the service, the platform 10 refers to the end time in the service information table (step S207) and monitors the end time of the service.

[0151] When the time for the service to end arrives, the platform 10 transmits a service end notification to the service server 20 (step S208), which causes the service server 20 to end the provision of the service to the user.

[0152] After the service ends, the platform 10 updates the service information table (step S210). The platform 10 updates the line information table (step S211). The platform 10 updates the share group information table (step S212). The platform 10 updates the ticket information table (step S213). For example, the platform 10 deletes information corresponding to "Live 1" from the service information table, line information table, share group information table, and ticket information table.

[0153] 12, the platform 10 executes the QoS control process at the service start time and notifies the service server 20 of the start of the service, but this is not limiting. For example, the platform 10 may execute the QoS control process before the service start time so that the service server 20 can start the service exactly at the service start time. For example, the platform 10 may execute the QoS control process after ticket sales have ended or a predetermined time before the service start time, and notify the service server 20 of the start of the service at the service start time.

[0154] <3.3. QoS control processing> 13 is a flowchart showing an example of the flow of a QoS control process according to an embodiment of the present disclosure. The QoS control process shown in FIG. 13 is executed by the platform 10, for example, in step S202 of the service providing process in FIG.

[0155] 13, the platform 10 refers to the service information table and acquires the service ID of the start time (step S301). Here, the platform 10 acquires, for example, the service ID "1" (see FIG. 7). Hereinafter, the service ID acquired by the platform 10 in step S301 will also be referred to as the target service ID.

[0156] As shown in Fig. 13, the platform 10 refers to the ticket information table and acquires a share group ID corresponding to the target service ID (step S302). Here, the platform 10 acquires, for example, a share group ID "1" (see Fig. 4). Hereinafter, the share group ID acquired by the platform 10 in step S302 will also be referred to as a target share group ID.

[0157] Returning to Figure 13, the platform 10 refers to the ticket information table and acquires the line ID corresponding to the target share group ID (step S303). Here, the platform 10 acquires, for example, line ID "1" (see Figure 4). Hereinafter, the line ID acquired by the platform 10 in step S303 will also be referred to as the target line ID.

[0158] Returning to Fig. 13, the platform 10 refers to the line information table and acquires the line status of the target line ID (step S304). Here, since the line ID "1" is the target line ID, the platform 10 acquires, for example, "started" as the line status of the target line ID (see Fig. 4).

[0159] Returning to Fig. 13, the platform 10 determines whether the target line ID is opened or closed based on the acquired line status (step S305). For example, if the acquired line status is "opened", the platform 10 determines that the line is opened, and if the acquired line status is "stopped", the platform 10 determines that the line is not opened.

[0160] If the line has not been opened (step S305; No), the platform 10 proceeds to step S307.

[0161] If the line has been opened (step S305; Yes), the platform 10 increments the number of opened lines by 1 (step S306).

[0162] Next, the platform 10 determines whether or not the number of opened lines has been counted for all line IDs included in the target share group ID (step S307).

[0163] For example, when the target line ID is "1", the platform 10 has not counted the number of connections opened for the line IDs "2" and "3" included in the target share group ID. In this way, when there is a line ID for which the number of connections opened has not been counted (step S307; No), the platform 10 changes the next line ID to the target line ID (step S308) and returns to step S304. For example, the platform 10 changes the line ID "2" to the target line ID and returns to step S304.

[0164] On the other hand, if the number of opened lines has been counted for all line IDs included in the target share group ID (for example, line IDs "1" to "3") (step S307; Yes), the platform 10 determines the average bandwidth to be allocated to the opened lines (step S309). The platform 10 determines the average bandwidth of the opened lines corresponding to the target share group ID using the above-mentioned formula (1).

[0165] Here, as shown in Figure 5, among line IDs "1" to "3," there are two lines (line IDs "1" and "2") that have been opened (line status is "started"). As shown in Figure 6, the packet volume of share group ID "1" is "20 Gbytes." As shown in Figure 7, the service with service ID "1" will be provided for two hours from 7:00 PM to 9:00 PM on April 21, 2021. In other words, the two lines with line IDs "1" and "2" will share 20 Gbytes for communication during the two hours that the service is provided.

[0166] Therefore, the average bandwidth W that line IDs "1" and "2" can use while the service is being provided without causing the coupon to expire is W = 20 Gbyte / (2 × 2 hours) = 11.11 mbps. The platform 10 determines 11.11 mbps as the average bandwidth to request from the cellular communication system 30.

[0167] Returning to Fig. 13, the platform 10 requests the average bandwidth determined in step S309 from the cellular communication system 30 (step S310). Note that the process of step S310 can be executed as the process of step S304 in Fig. 12.

[0168] Returning to Fig. 13, the platform 10 determines whether or not the average bandwidth has been requested for all share group IDs included in the target service ID (step S311).

[0169] For example, when the target service ID is "1", the platform 10 requests an average bandwidth using the share group ID "1" corresponding to the target service ID as the target share group ID. On the other hand, the platform 10 has not requested an average bandwidth for the share group ID "2" corresponding to the target service ID "1". In this way, when there is a share group ID for which an average bandwidth has not been requested (step S311; No), the platform 10 changes the next share group ID to the target share group ID (step S312) and returns to step S303. For example, the platform 10 changes the share group ID "2" to the target share group ID and returns to step S303.

[0170] On the other hand, if an average bandwidth request has been made for all share group IDs included in the target service ID (for example, share group IDs "1" and "2") (step S311; Yes), the platform 10 ends the process.

[0171] <<4. Modifications>> The above-described embodiment is merely an example, and various modifications and applications are possible.

[0172] For example, in the above-described embodiment, the BSS 310 delivers a SIM to the user, but this is not limiting. For example, instead of a physical SIM (e.g., a SIM card), an electronic SIM called an eSIM (embedded SIM) or a soft SIM may be used.

[0173] In this case, the BSS 310 provides an eSIM to the terminal device 40 used by the user via the SM-DP+ 311, for example.

[0174] Here, the SM-DP+ 311 is a node that constitutes an eSIM system for consumers. The SM-DP+ 311 is defined by, for example, the GSM Association (GSMA). The SM-DP+ 311 manages eSIM profiles.

[0175] The user accesses the SM-DP+311 using the activation code obtained from the BSS 310. By downloading a profile from the SM-DP+311 to the terminal device 40, the user can install an eSIM in the terminal device 40 and use the line of the cellular communication system 30.

[0176] The BSS 310 may distribute the activation code to the user using, for example, a QR code (registered trademark) or a character string.

[0177] 14 is a sequence diagram showing an example of the flow of a line opening process according to a modified example of an embodiment of the present disclosure. Note that the flow of the process up to step S110 is the same as in FIG. 11, so the same reference numerals are used and the description will be omitted.

[0178] Upon receiving the request to activate the line, the BSS 310 activates the line to the cellular communication system 30 and provides an activation code to the user (step S401). For example, the BSS 310 provides the activation code to the user by transmitting the activation code to the terminal device 40 used by the user.

[0179] Upon receiving the activation code, the user accesses the SM-DP+311 using the activation code and requests a profile (step S402). The user obtains an eSIM by downloading the profile from the SM-DP+311 (step S403).

[0180] In this way, by using an eSIM, the information processing system 1 does not need to ship a SIM card. Furthermore, the user can obtain the eSIM at any time after purchasing a ticket, further improving user convenience.

[0181] The information processing device 100, the server device 200, and the control device that controls the terminal device 40 of this embodiment may be realized by a dedicated computer system or a general-purpose computer system.

[0182] For example, a communication program for executing the above-described operations is stored in a computer-readable recording medium such as an optical disk, a semiconductor memory, a magnetic tape, or a flexible disk and distributed. Then, for example, the program is installed in a computer and the above-described processing is executed to configure a control device. In this case, the control device may be a device (e.g., a personal computer) external to the information processing device 100, the server device 200, and the terminal device 40. Alternatively, the control device may be a device (e.g., a control unit 130, a control unit 230, and a control unit 43) internal to the information processing device 100, the server device 200, and the terminal device 40.

[0183] The communication program may also be stored in a disk device provided in a server device on a network such as the Internet, and may be downloaded to a computer. The above functions may also be realized by cooperation between 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 may be stored in a server device and may be downloaded to a computer.

[0184] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0185] Furthermore, the components of each device shown in the figure are conceptual functional units and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads and usage conditions. This distribution and integration configuration may also be performed dynamically.

[0186] The above-described embodiments can be combined as appropriate within the scope of the processing content without causing inconsistency. The order of the steps shown in the flowcharts and sequence diagrams of the above-described embodiments can be changed as appropriate.

[0187] Furthermore, for example, this embodiment can also be implemented as any configuration that constitutes an apparatus or system, such as a processor as a system LSI (Large Scale Integration), a module using multiple processors, a unit using multiple modules, a set in which other functions are added to a unit, etc. (i.e., a configuration of a part of an apparatus).

[0188] In this embodiment, a system refers to a collection of multiple components (devices, modules (components), etc.), regardless of whether all the components are in the same housing. Therefore, multiple devices housed in separate housings and connected via a network, and a single device in which multiple modules are housed in a single housing, are both systems. For example, the information processing device 100 of this embodiment can be realized as a single system.

[0189] Furthermore, for example, this embodiment can be configured as a cloud computing system in which one function is shared and processed jointly by a plurality of devices via a network.

[0190] <<5. Conclusion>> Although the embodiments of the present disclosure have been described above, the technical scope of the present disclosure is not limited to the above-described embodiments, and various modifications are possible within the scope of the gist of the present disclosure. Furthermore, components of different embodiments and modifications may be combined as appropriate.

[0191] Furthermore, the effects of each embodiment described in this specification are merely examples and are not intended to be limiting, and other effects may also be obtained.

[0192] The present technology can also be configured as follows. (1) requesting the cellular communication system to open a communication line to be used by a plurality of terminal devices to which the service is to be provided; assigning a plurality of the terminal devices to at least one group according to the services provided; determining resources to be allocated to the plurality of terminal devices corresponding to the group when service provision to the plurality of terminal devices corresponding to the group is started; a control unit that requests the cellular communication system to reserve the resources; An information processing device comprising: (2) The information processing device described in (1), wherein the control unit determines the average bandwidth during the provision of the service as the resource based on at least one of the amount of packets available in the group, the number of terminal devices corresponding to the group, and the provision time of the service. (3) The information processing device according to (1) or (2), wherein the terminal device receives the service using a SIM (Subscriber Identity Module) card or an eSIM (embedded SIM). (4) The control unit Accepting an application for use of the service from a user; requesting the cellular communication system to open the communication line of the terminal device used by the user; The information processing device according to any one of (1) to (3). (5) The information processing device according to any one of (1) to (4), wherein the control unit registers the communication line with the cellular communication system. (6) The information processing device according to any one of (1) to (5), wherein the control unit cancels the communication line when the provision of the service ends. (7) The information processing device according to any one of (1) to (6), wherein the control unit acquires service information relating to the service from a service server that provides the service to the terminal device. (8) The information processing device according to any one of (1) to (7), wherein the control unit notifies a service server that provides the service to the terminal device of at least one of the start and end of the service. (9) The information processing device according to any one of (1) to (8), wherein the control unit requests the resources from a PCF (Policy Control Function) of the cellular communication system. (10) The information processing device according to any one of (1) to (9), wherein the control unit requests the resource via a Network Exposure Function (NEF) of the cellular communication system. (11) The information processing device described in any one of (1) to (10), wherein the control unit divides the communication lines registered in the cellular communication system into one group by those communication lines having the same DNN (Data Network Name). (12) requesting the cellular communication system to open a communication line to be used by a plurality of terminal devices to which the service is to be provided; assigning a plurality of the terminal devices to at least one group according to the services provided; determining resources to be allocated to the plurality of terminal devices corresponding to the group when service provision to the plurality of terminal devices corresponding to the group is started; requesting the cellular communication system to reserve the resources; An information processing method including: (13) requesting the cellular communication system to open a communication line to be used by a plurality of terminal devices to which the service is to be provided; assigning a plurality of the terminal devices to at least one group according to the services provided; determining resources to be allocated to the plurality of terminal devices corresponding to the group when service provision to the plurality of terminal devices corresponding to the group is started; a control unit that requests the cellular communication system to reserve the resources; An information processing system comprising: [Explanation of symbols]

[0193] 1. Information Processing Systems 10 Platform 20 Service Server 30 Cellular Communication Systems 40 Terminal Equipment 41 Radio Communication Department 42 Storage section 43 Control Unit 100 Information processing device 110 Communications Department 120 Storage section 130 Control Unit 131 Contract Reception Department 132 Contract Control Section 133 Service Control Section 134 QoS control section 200 Server Devices 210 Communications Department 220 Storage section 230 Control Unit

Claims

1. requesting a cellular communication system to open a communication line to be used for receiving the service while a plurality of terminal devices to which the service is to be provided are receiving the service; assigning a plurality of the terminal devices to at least one group according to the services provided; determining resources to be allocated to the plurality of terminal devices corresponding to the group when service provision to the plurality of terminal devices corresponding to the group is started via the communication line; a control unit that requests the cellular communication system to reserve the resources; An information processing device comprising:

2. The information processing device according to claim 1, wherein the control unit determines the average bandwidth during the provision of the service as the resource based on at least one of the amount of packets available to the group, the number of the terminal devices corresponding to the group, and the provision time of the service.

3. The information processing device according to claim 1 , wherein the terminal device receives the service using a Subscriber Identity Module (SIM) card or an embedded SIM (eSIM).

4. The control unit Accepting an application for use of the service from a user; requesting the cellular communication system to open the communication line of the terminal device used by the user; The information processing device according to claim 1 .

5. The information processing device according to claim 1 , wherein the control unit registers the communication line with the cellular communication system.

6. The information processing device according to claim 1 , wherein the control unit cancels the communication line when the provision of the service is terminated.

7. The information processing device according to claim 1 , wherein the control unit acquires service information relating to the service from a service server that provides the service to the terminal device.

8. The information processing device according to claim 1 , wherein the control unit notifies a service server that provides the service to the terminal device of at least one of the start and end of the service.

9. The information processing device according to claim 1 , wherein the control unit requests the resource from a PCF (Policy Control Function) of the cellular communication system.

10. The information processing device according to claim 1 , wherein the control unit requests the resource via a Network Exposure Function (NEF) of the cellular communication system.

11. The information processing device according to claim 1 , wherein the control unit divides the plurality of communication lines registered in the cellular communication system into one group by dividing the communication lines having the same DNN (Data Network Name).

12. requesting a cellular communication system to open a communication line to be used for receiving the service while a plurality of terminal devices to which the service is to be provided are receiving the service; assigning a plurality of the terminal devices to at least one group according to the services provided; determining resources to be allocated to the plurality of terminal devices corresponding to the group when service provision to the plurality of terminal devices corresponding to the group is started via the communication line; requesting the cellular communication system to reserve the resources; An information processing method including:

13. requesting a cellular communication system to open a communication line to be used for receiving the service while a plurality of terminal devices to which the service is to be provided are receiving the service; assigning a plurality of the terminal devices to at least one group according to the services provided; determining resources to be allocated to the plurality of terminal devices corresponding to the group when service provision to the plurality of terminal devices corresponding to the group is started via the communication line; a control unit that requests the cellular communication system to reserve the resources; An information processing system comprising:

Images