Patent ID: 12232002

DESCRIPTION OF EMBODIMENTS

Hereinafter, an embodiment of the present disclosure will be explained in detail with reference to the drawings.

EMBODIMENTS

(Communication System100)

FIG.1is a diagram illustrating the structure of a communication system100according to the present disclosure.

The communication system100comprises a communication network110, a portal site120, a management device130, and a communication device140. InFIG.1, for convenience of explanation, the portal site120and the management device130are illustrated outside the communication network110. However, they may be located inside the communication network110.

The communication network110may be a common communication network such as a 5G mobile communication system, and as shown inFIG.1, comprises a RAN (Radio Access Network)111and a CN (Core Network)112. The RAN111, like common RANs, comprises a DU (Distributed Unit) and a CU (Central Unit) as NFs (Network Functions), and also comprises an RU (Radio Unit). The CN112, like a common CN, comprises an SNF (Service Network Function) such as, for example, an AMF (Access and Mobility Management Function), an SMF (Session Management Function), a UPF (User Plane Function), and the like.

Additionally, the communication network110of the present embodiment further comprises an application (hereinafter referred to as a “service-providing application”)113for providing a service. InFIG.1, for convenience of explanation, the service-providing application113is shown separately from the RAN111and the CN112. However, the service-providing application113need only be executed in a server or the like within the communication network110, and said server may be located in the RAN111or located in the CN112.

As indicated next, the constituent elements in the communication network110are physically located at antenna sites, edge data centers, regional data centers (RDCs), central data centers (CDCs), or public data centers (PDCs). Which of the above are to be used for constructing the respective constituent elements in the communication network110such as the NFs in the RAN111, the SNFs in the CN112, and the service-providing application113may be defined as appropriate, and they may be constructed in respectively different servers.

FIG.2is a diagram illustrating servers in which the constituent elements in the communication network110may be located.

Antenna sites210are located near RUs in the RAN111.

Thousands of edge data centers220are located, in a distributed manner, in the area covered by the communication network110. Edge clouds may be located in the edge data centers220.

Tens of RDCs230are located, in a distributed manner, in the area covered, for example, by the communication network110. If the area covered by the communication network110is the entire territory of Japan, then one or two RDCs230may be located in each prefecture.

Several CDCs240are located, in a distributed manner, in the area (for, example, Japan) covered by the mobile communication system100.

PDCs250are located on the internet. Public clouds may be located in the PDCs440.

By being arranged as indicated above, the communication distances with the communication device140, which communicates with the following, are shorter in the order of the antenna sites210, the edge data centers220, the RDCs230, the CDCs240, and the PDCs250. In other words, the antenna sites210, the edge data centers220, the RDCs230, the CDCs240, and the PDCs250are located, in the given order, closer to the edge with respect to the communication device140communicating therewith.

MEC (Multi-access Edge Computing) may, for example, be provided in servers at the antenna sites210and the edge data centers220.

Returning to the explanation ofFIG.1, a portal site120registers a service and configures a policy relating to the service. Examples of the service include web distribution services, game-providing services, video distribution services, music distribution services, monitoring services, navigation services, automated driving services, email-providing services, and sensor services.

The policy indicates the quality (QOS: Quality of service) required for the service, connectable servers, etc. Registration and configuration are performed, for example, when triggered by a request from a vendor providing the service.

The portal site120configures one or more policies relating to the service.

The portal site120notifies the management device130of the one or more policies configured in connection with the service, for example, via the communication network110. Additionally, the portal site120requests the management device130to prepare a slice and to deploy the service-providing application113.

The management device130requests the communication network110to prepare a slice in accordance with the policy and to deploy the service-providing application113.

The management device130acquires information regarding the results of the slicing and deployment from the communication network110.

The management device130generates a policy file for the communication device140. The policy file includes information on network policy defining communication connections to be made when an application executed on the communication device140(hereinafter sometimes referred to simply as the “application”) receives the provided service from the service-providing application113via the communication network110. Additionally, the policy file also includes information indicating where the service-providing application113is to be executed, in other words, information indicating which server in the communication network110is to execute the service-providing application113.

The network policy, which indicates information regarding which slices or what quality of slices can be selected when an application executed on the communication device140utilizes a service, is described, in particular, as “Permission for NW policy”. That is, the permitted network policy corresponds to the QoS. The location of a server to which the communication device140may connect when the application executed thereon utilizes the service is described as “Permission for server location”. Multiple permitted network policies may be defined and multiple permitted server locations may be defined for a single application executed on the communication device140.

The policy file is prepared or updated by the management device130periodically or at the times of service registration requests and update requests to the portal site120. The newest policy configured for the service is reflected in the policy file. Details regarding the policy file will be described below.

The communication network110, in response to a slice preparation and deployment request from the management device130, prepares a slice and deploys a service-providing application113. Examples of service-providing applications113include web distribution applications, game-providing applications, video distribution applications, music distribution applications, monitoring execution applications, navigation applications, automated driving applications, email-providing applications, and sensor execution applications.

The communication device140, as mentioned above, comprises one or more applications for receiving provided services.

The communication device140need only be an ICT (Information and Communication Technology) device that can be executed by and that can communicate with an application. It may be a smartphone, a portable PC (Personal Computer) such as a tablet terminal, or a non-portable device such as a desktop PC.

Examples of the application include web browsers, game-playing applications, video-watching applications, music-listening applications, applications for checking monitoring results, navigation applications, automated driving applications, applications for sending and receiving email, and sensor monitoring applications.

The application does not necessarily correspond to a single service. For example, when watching a video (described as “video #1”) from a certain video distribution service, instead of using a dedicated video-watching application (described as “video-watching application #1”) provided by the vendor providing this video distribution service, an alternative video-watching application (described as “video-watching application #2”) may be used. That is, instead of using a dedicated browser, which is video-watching application #1, for example, a general-purpose web browser may be used as video-watching application #2. When watching videos provided by different vendors on dedicated video-watching applications #1 provided by each vendor, there are cases in which the operations differ for each application, thus requiring a user to memorize the operations for each application separately. By using video-watching application #2, which can play videos on the cloud with a web browser regardless of the vendor, the user does not need to memorize the operations of video-watching applications #1 that differ for each vendor. If a web browser is used to watch videos as video-watching application #2 instead of a dedicated video-watching application #1, then there are also cases in which functions such as those for changing the playback speed or for repeated playback cannot be used. Nevertheless, among some users, rather than the ability to use these functions, there is a demand to be able to use the same video-watching application #2, regardless of the vendor providing the video, when watching videos. Thus, there are cases in which users wish to use applications that support multiple services.

Details regarding the communication device140will be described below.

(Policy File)

Next, the policy file will be explained. The policy file includes a permission table. The permission table includes the aforementioned information regarding permitted network policies and server locations.

The management device130, for example, prepares a permission table when triggered by a service registration request from a vendor.

FIG.3illustrates an example of a permission table.

The permission table includes combinations of “Application ID”, “Connection Destination Server Application URL”, “NW policy ID” (Permission for NW Policy ID), and “server location” (Permission for server location). The “NW policy ID” (Permission for NW Policy ID) and the “Server Location” (Permission for server location) are permitted for communication connections between the relevant applications and service-providing applications113. A management ID is assigned to each of these combinations.

(Application ID)

The “Application ID” is an identifier for identifying an application executed by the communication device140, wherein the application is for receiving a provided service.

(Connection Destination Server Application URL)

The “Connection Destination Server Application URL” indicates a connection destination of the service-providing application.

(Permission for NW Policy ID)

The “Permission for NW Policy ID” is an identifier for indicating network policies permitted for a service.

Examples of NW policy IDs include the following.any: freely selectable01: high-speed, best effort02: high-speed, guaranteed-bandwidth03: low-speed, best effort04: low-speed, guaranteed-bandwidth

If the “Permission for NW Policy ID” is “any”, then this indicates that the permitted network policy is freely selectable.

If the “Permission for NW Policy ID” is “01”, then this indicates that the permitted network policy is high-speed, best-effort. High-speed, best-effort tends to be used for high-capacity services in which some latency is permissible, and generally tends to be used, for example, for on-line game services.

If the “Permission for NW Policy ID” is “02”, then this indicates that the permitted network policy is high-speed, guaranteed-bandwidth. High-speed, guaranteed-bandwidth tends to be used for high-capacity services in which even slight latency cannot be permitted, and generally tends to be used, for example, for video distribution services.

If the “Permission for NW Policy ID” is “03”, then this indicates that the permitted network policy is low-speed, best-effort. Low-speed, best-effort tends to be used for low-capacity services in which some latency is permissible, and generally tends to be used, for example, for sensor services for the purpose of data collection.

If the “Permission for NW Policy ID” is “04”, then this indicates that the permitted network policy is low-speed, guaranteed-bandwidth. Low-speed, guaranteed-bandwidth tends to be used for low-capacity services in which even slight latency cannot be permitted, and generally tends to be used, for example, for real-time monitoring services for the purpose of security.

(Permission for Server Location)

The “Permission for server location” indicates server locations that are permitted as connection destination servers for providing services.

(Other Conditions)

The permission table may further include “Other conditions” relating to communication connections.

Examples of “Other conditions” include time-based connection destination constraint conditions, connection destination priority rankings, time-based network policy constraint conditions, and the like. If the services are game services, then an example is the condition of connecting to an MEC 1 at times during which game events are being held. Additionally, an example is the condition that the connection destination priority ranking be in the order of an MEC 1 and an MEC 2. Additionally, if the service is a monitoring service, then an example is the condition that the network policy “Permission for NW Policy ID” should be changed from “03” to “02” at specific times during which the security level is to be raised.

Returning to the explanation ofFIG.3, in the table inFIG.3, the record (row) with the management ID “1111” and the record with the management ID “1112” indicate the “NW policy ID” and the “server location” permitted for cases in which the same application, designated by the application ID “0001”, is used to connect to different connection destination server application URLs.

The record with the management ID “1111” indicates that, in the case in which the application designated by the application ID “0001” is used to connect to a service-providing application designated by “Connection Destination Server Application URL: xxxxxxx1”, the permitted NW policy ID is 01, and the server location is MEC 1 or MEC 2.

The record with the management ID “1112” indicates that, in the case in which the application designated by the application ID “0001” is used to connect to a service-providing application designated by “Connection Destination Server Application URL: xxxxxxx2”, the permitted NW policy ID is “03”, and the server location is freely selectable. If there are multiple permitted server locations or if they are freely selectable, then this indicates that there may be one or more server locations that are permitted for connections between the application and the service-providing application.

Additionally, the record with the management ID “1111” and the record with the management ID “1112” indicate that, in the case in which the same application designated by the application ID “0001” is used, the “NW policy ID” and the “server location” that are permitted differ depending on the connection destination.

The record with the management ID “1113” indicates that, in the case in which the application designated by the application ID “0002” is used to connect to a service-providing application designated by “Connection Destination Server Application URL: xxxxxxx3”, the permitted NW policy ID is 03, and the server location is MEC 3.

The record with the management ID “1114” indicates that, in the case in which the application designated by the application ID “0003” is used to connect to the service-providing application designated by “Connection Destination Server Application URL: xxxxxxx3”, the permitted NW policy ID is freely selectable, and the server location is freely selectable. If the permitted NW policy ID is freely selectable, then this indicates that there may be one or more network policies permitted for connections between the application and the service-providing application.

Additionally, the record with the management ID “1113” and the record with the management ID “1114” indicate that, even if the connection destination is the same, in the case in which the applications used when receiving the provided service are different, the “NW policy ID” and the “server location” that are permitted differ depending on the applications.

Thus, the management device130prepares a policy file including a permission table.

(Communication Device140)

Next,FIG.4will be used to explain the communication device140.

FIG.4is a functional block diagram indicating the structure of the communication device140according to the present disclosure.

The communication device140comprises an application141, a slice controller142, an OS143(Operation System), and a chip set144.

As mentioned above, the application141is an application that is executed with the communication device140in order to receive a provided service. One or more applications141may be installed in the communication device140.

The application141notifies the slice controller142of requirements for receiving the provided service. The requirements for receiving the provided service include the address (URL) of the service-providing application113, the network policy when receiving the provided service, and information regarding the location of the server providing the service. The requirements for receiving the provided service will be described below.

In the present disclosure, the slice controller142is constructed between the OS143and the application141.

The slice controller142selects a slice for receiving the provided service based on the requirements for receiving the provided service, regarding which a notification is provided by the application141. The slice selection method will be described below.

When a slice is selected, the slice controller142generates a communication connection request associated with an application corresponding to the selected slice. Hereinafter, said communication connection request will be described as the “first communication connection request”. Details regarding the first communication connection request will be described below.

The slice controller142notifies the chip set144of the first communication connection request via the OS143.

Details regarding the operations of the slice controller142will be described below.

The OS143is located between the slice controller142and the chip set144, and provides an interface for the slice controller142. Additionally, the OS143performs memory management and process management of the chip set144.

The chip set144comprises a CPU (central processing unit) and a GPU (graphics processing unit). The chip set144may be a virtual chip set that is realized by software. The chip set144manages the correspondence relationships between applications and slices provided in the communication network110. The correspondence relationships will be described below.

The chip set144acquires the aforementioned first communication connection request from the slice controller142through the OS143.

Upon acquiring the first communication connection request, the chip set144generates a communication connection request based on the first communication connection request and the correspondence relationships (said correspondence relationships will be described below) between applications and slices provided in the communication network110. Said communication connection request is a communication connection request that is sent to the communication network110for performing communication associated with the application141with which the provided service is to be provided via the slice selected by the slice controller142. Hereinafter, said communication connection request will be described as the “second communication connection request”. Thus, in other words, the chip set144sends the generated second communication connection request to the communication network110.

In this way, a request for a slice connection satisfying the requirements for receiving the provided service from the application141is made from the chip set144to the communication network110. Thereafter, processing is performed so that the application141and the service-providing application113are communicatively connected by using a slice satisfying the requirements for receiving the provided service.

(Requirements for Receiving Provided Services)

Next, the requirements for receiving the provided service regarding which the slice controller142was notified by the application141will be explained.

The requirements for receiving provided services include information such as “Request URL”, “NW Policy ID” and “Server location”.

The “Request URL” designates the URL (including a header and a body) of a service-providing application113with which to connect.

The “NW Policy ID” designates the QoS (Quality of Service), which is the quality of the services provided on the communication network110. The QoS types may include, for example, QoS1, QoS2, QoS3, and QoS4. QoS1 indicates high-speed, best-effort and is designated by setting the “NW Policy ID” to “01”. QoS2 indicates high-speed, guaranteed-bandwidth and is designated by setting the “NW Policy ID” to “02”. QoS3 indicates low-speed, best-effort and is designated by setting the “NW Policy ID” to “03”. QoS4 indicates low-speed, guaranteed-bandwidth and is designated by setting the “NW Policy ID” to “04”. The number of types of QoS is not limited to four.

The “Server location” designates the location of a server with which to connect. The location of the server may, for example, be an MEC or the like provided on a server in an antenna site or an edge data center.

The combinations of the “Request URL”, the “NW Policy ID”, and the “Server location” included in the requirements for receiving provided services are predetermined for each application141in accordance with use cases that are contemplated for the cases in which the application141and the service-providing application113are connected.

FIG.5indicates examples of the correspondence between use cases and the requirements for receiving provided services.

As use cases, optimization, designation of only “NW Policy ID” (QoS), designation of only server location, designation of both QoS and server location, and the like may be contemplated. Optimization refers to the QoS and the server location both not being designated and being freely selectable.

For example, in the case of an automated driving service, the QoS must be high-speed, guaranteed-bandwidth (QoS2).

Additionally, depending on the service, cases in which the QoS is freely selectable but the server location must be designated could be contemplated.

The use cases may differ, depending on the application141, even when connecting to the same “Request URL”. Additionally, even with the same application141, when it is possible to connect to different “Request URLs”, there may be multiple use cases depending on the “Request URL”,

The application141holds, in advance, one or more combinations of information for the “Request URL”, the “NW Policy ID” and the “Server location”. The application141notifies the slice controller142of the requirements for receiving provided services, including the URL (“Request URL”) of a service-providing application113with which to connect, and the “NW Policy ID” and the “Server location” combined with this “Request URL”.

(Slice Controller142)

Next, the structure and operations of the slice controller142in the communication device140will be explained.

FIG.6is a functional block diagram illustrating the structure of the slice controller142. The slice controller142comprises a slice selector1421and a first communication connection request generator1422. The slice controller142is capable of communicating with the management device130via the OS143and the chip set144in the communication device140.

The slice selector1421, upon receiving a trigger, notifies the management device130of a request to send a policy file. The trigger may, for example, be a signal generated when the slice controller142is first activated, when the power of the communication device140is turned on, or the like.

The slice selector1421acquires a policy file from the management device130. If there is a policy file that has already been acquired, then the slice selector1421updates the permission table based on the newest policy file.

The slice selector1421acquires requirements for receiving a provided service from the application141. As mentioned above, the requirements for receiving the provided service include the “Request URL”, the “NW Policy ID”, and the “Server location” information.

The slice selector1421collates the “Request URL”, the “NW Policy ID”, and the “Server location” included in the requirements for receiving the provided service with the policy file, and selects a slice satisfying the requirements for receiving the provided service.

Specifically, the slice selector1421refers to the permission table and checks the “NW policy ID” (Permission for NW policy ID) and the “Server location” (Permission for server location) that are permitted for the “Connection Destination Server Application URL” designated by the “Request URL”. As described below, the slice selector1421selects a slice satisfying the permitted “NW policy ID” and “Server location” as the slice.

The manner in which the slice selector1421selects a slice in accordance with the “NW Policy ID” and the “Server location” included in the requirements for receiving the provided services will be explained below.

(1) Case in which “NW Policy ID” is “AUTO” and “Server location” is “AUTO”

When the “NW Policy ID” is “AUTO”, this means that a QoS is not designated. When the “Server location” is “AUTO”, this means that a server is not designated. In other words, when the “NW Policy ID” is “AUTO” and the “Server location” is “AUTO”, this means that there are multiple selectable slices (also described as slice candidates).

When there are multiple slice candidates, the slice selector1421may select any of the slices. For example, the slice selector1421may select the slice with the highest quality from among the multiple slice candidates. In this case, services can be provided to a user at the highest QoS.

Additionally, for example, the slice selector1421may select the slice with the lowest quality from among the multiple slice candidates. In this case, services are provided to a user at the lowest QoS, but it is instead possible to suppress consumption of resources in the communication network110.

Additionally, the slice selector1421may select a slice from among the multiple slice candidates based on the status of the communication network110. The method for selecting a slice based on the status of the communication network110will be described below.

(2) Case in which “NW Policy ID” is “AUTO” and “Server Location” is “MEC1 (Designated)”

When the “NW Policy ID” is “AUTO”, this means that a QoS is not designated. When the “Server location” is “MEC1”, this means that MEC1 is designated as the server.

In this case, the slice selector1421filters slices that are capable of connecting with the server (MEC1) designated by the application141to extract slice candidates.

FIG.7is a diagram illustrating an example of a correspondence table (correspondence table #1) for Server location IDs and NSSAIs. An NSSAI refers to a slice ID, and said correspondence table indicates the NSSAIs of slices capable of connecting with the servers indicated by the Server location IDs. The slice selector1421may, for example, use correspondence table #1 as illustrated inFIG.7to extract slice candidates. Correspondence table #1 may be prepared in the management device130by using deployment information, or may be included in the policy file.

When there are multiple slice candidates, the slice selector1421may select a slice in a manner similar to the above-described case in which the “NW Policy ID” is “AUTO” and the “Server location” is “AUTO”.

(3) Case in which “NW Policy ID” is “03 (Designated)” and “Server Location” is “AUTO”

When the “NW Policy ID” is “03”, this means that low-speed, best-effort is designated as the QoS. When the “Server location” is “AUTO”, this means that a server is not designated.

In this case, the slice selector1421filters slices to extract slices that are defined to be low-speed, best-effort as the slice candidates.

FIG.8is a diagram illustrating an example of a correspondence table (correspondence table #2) for NW Policy IDs and NSSAIs. The slice selector1421may, for example, use correspondence table #2 as illustrated inFIG.8to extract slice candidates. In correspondence table #2, NW Policy IDs are associated with NSSAIs satisfying the QoS indicated by said NW Policy IDs. Correspondence table #2 may be prepared in the management device130by using deployment information, or may be included in the policy file.

When there are multiple slice candidates, the slice selector1421may select a slice in a manner similar to the above-described case in which the “NW Policy ID” is “AUTO” and the “Server location” is “AUTO”.

(4) Case in which “NW Policy ID” is “03” and “Server Location” is “MEC3 (Designated)”

When the “NW Policy ID” is “03”, this means that low-speed, best-effort is designated as the QoS. When the “Server location” is “MEC3”, this means that MEC3 is designated as the server.

In this case, the slice selector1421selects a slice that is capable of connecting to the MEC3 from among slices defined to be low-speed, best-effort.

The slice selector1421may, for example, use the above-mentioned correspondence table #1 and correspondence table #2 to extract slice candidates. For example, from correspondence table #1, it can be understood that the NSSAI of a slice for which the “Server location” is “MEC3” is “3” (filtering result #1). Additionally, from correspondence table #2, it can be understood that the slices in which the “NW Policy ID” is “03” are a slice in which NSSAI is “3” and a slice in which “NSSAI” is “4” (filtering result #2). The slice selector1421selects, as the slice satisfying the designated requirements, the slice in which NSSAI is “3”, which is included in both filtering result #1 and filtering result #2.

When there are multiple slice candidates included in both filtering result #1 and filtering result #2, the slice selector1421may select a slice in a manner similar to the above-described case in which the “NW Policy ID” is “AUTO” and the “Server location” is “AUTO”.

That is, when there are multiple slice candidates, the slice selector1421may select any of the slices. Additionally, the slice selector1421may select the slice with the highest QoS from among the multiple slice candidates. Additionally, the slice selector1421may select the slice with the lowest QoS from among the multiple slice candidates.

Additionally, the slice selector1421may select a slice from among multiple slice candidates based on the status of the communication network110. Examples of parameters indicating the status of the communication network110include RTT (Round Trip Time), jitter, error rate, and the like. If the communication device140is provided with functions for measuring, computing, or acquiring parameters indicating the status of the communication network110, then the slice selector1421can select a slice from among the slice candidates in accordance with the value of a parameter indicating the status of the communication network110.

For example, the slice selector1421selects a slice from among the slice candidates by referring to a switching conditions table including information regarding “NW Policy ID” (Permission for NW Policy ID) and “Server location” (Permission for Server location) that are permitted.

FIG.9is a diagram illustrating an example of a switching conditions table. The switching conditions table illustrated inFIG.9indicates information regarding the “NW Policy IDs” (Permission for NW Policy ID) and the “Server locations” (Permission for Server location) permitted in accordance with the status of the communication network110for the record with the management ID “1114” in the permission table.

For example, it is indicated that, for the record with the management ID “1114”, in the case in which the RTT is longer than 5000 ms, the permitted “NW Policy IDs” are “01” and “04”, and the permitted “Server locations” are “MEC1” and “MEC2”. Additionally, it is indicated that, for the record with the management ID “1114”, in the case in which the jitter is longer than 20 ms, the permitted “NW Policy IDs” are “01” and “04”, and the permitted “Server locations” are “MEC1” and “MEC2”. Additionally, it is indicated that, for the record with the management ID “1114”, in the case in which the error rate is greater than 50%, the permitted “NW Policy IDs” are “01” and “04”, and the permitted “Server locations” are “MEC1” and “MEC2”.

By using the switching conditions table mentioned above, the slice may be changed in the case in which the status of the communication network110has deteriorated. For example, suppose that the slice selector1421has selected one of the slices to be used for communication with the application having the application ID 0003 based on the record with the management ID “1114” in the permission table inFIG.3. In this case, if the RTT becomes longer than 5000 ms, the jitter becomes longer than 20 ms, or the error rate becomes greater than 50%, so that the status of the communication network110satisfies the switching conditions, then the slice selector1421reselects the slice used for communicating with the application having the application ID 0003 based on the switching conditions table.

In this way, the slice selector1421may switch the slice when the status of the communication network110has deteriorated. Thus, the connection status between the application141and the service-providing application113can be improved, thereby suppressing deterioration of the usability by users. The slice selector1421may, for example, determine the status of the communication network110under which the slice is or is not to be switched in accordance with a comparison result between a parameter indicating the status of the communication network110and a set threshold value. When a slice is selected, the slice selector1421notifies the first communication connection request generator1422of the NSSAI of the selected slice.

Returning to the explanation ofFIG.6, the operations of the first communication connection request generator1422will be explained. The first communication connection request generator1422generates a first communication connection request. The first communication connection request, as mentioned above, is a connection request associated with the application corresponding to the slice selected by the slice selector1421. In order to generate the first communication connection request, the first communication connection request generator1422, for example, refers to a correspondence table defining the correspondence between NSSAIs and application IDs. The first communication connection request generator1422extracts, from the correspondence table, the application ID corresponding to the NSSAI of the slice selected by the slice selector1421. Furthermore, the first communication connection request generator1422generates a first communication connection request including the extracted application ID.

FIG.10is a diagram illustrating an example of a correspondence table defining the correspondence between NSSAIs and application IDs. In the case in which the NSSAI identifying a selected slice is “1”, the first communication connection request generator1422refers to the correspondence table inFIG.10and generates a first communication connection request including information indicating that the “application ID” is “a0001”. In the case in which the NSSAI identifying the selected slice is “2”, the first communication connection request generator1422refers to the correspondence table inFIG.10and generates a first communication connection request including information indicating that the “application ID” is “a0002”. In the case in which the NSSAI identifying the selected slice is “3”, the first communication connection request generator1422refers to the correspondence table inFIG.10and generates a first communication connection request including information indicating that the “application ID” is “a0003”.

The correspondence relationships between NSSAIs and application IDs to which the first communication connection request generator1422refers are the same as the correspondence relationships between the application IDs and the NSSAIs to which the chip set144refers. In other words, the first communication connection request includes an identifier identifying an application corresponding to the selected slice indicated by the correspondence relationships between the applications141and the slices provided in the communication network110, which are managed by the chip set144.

The first communication connection request generator1422notifies the chip set144of the first communication connection request.

(Operations of Communication System100)

Next,FIG.11AandFIG.11Bwill be used to explain the operations of the communication system100according to the present disclosure.FIG.11AandFIG.11Bare diagrams illustrating an example of the processing sequence in the communication system100according to the present disclosure.

As illustrated inFIG.11A, the portal site120registers a service and configures a policy for the service (T1). The registration and configuration are triggered, for example, by a request from a vendor providing the service. Additionally, the portal site120requests the management device130to prepare a slice and to deploy a service-providing application113(T2).

The management device130requests the communication network110to prepare a slice in accordance with the policy (T3). The management device130requests a server to deploy the service-providing application113(T4).

The server that has received the request deploys the service-providing application113(T5), and the communication network110prepares a slice (T6) and deploys what is necessary to prepare the slice (T7). The management device130acquires, from the communication network110and the server in which the service-providing application113was deployed, information regarding the results of slicing and deployment (T8and T9).

The management device130prepares a policy file including a permission table (T10).

Next, as illustrated inFIG.11B, a slice controller142, triggered by the slice controller142first being activated by the power supply to the communication device140being switched on, or the like (T11), notifies the management device130of a request to send the policy file (T12).

The management device130sends the policy file to the slice controller142(T13).

The slice controller142acquires the policy file from the management device130(T14). If there is a policy file that has already been acquired, then the slice controller142updates the policy file (T15).

The slice controller142acquires the requirements for receiving the provided service from the application141(T16).

The slice controller142refers to the policy file and selects a slice satisfying the requirements for receiving the provided service (T17).

The slice controller142generates a first communication connection request including an application ID corresponding to an NSSAI that identifies the selected slice (T18), and notifies the chip set144of the first communication connection request (T19).

The chip set144, upon acquiring the first communication connection request from the slice controller142, generates a second communication connection request (T20), and sends the second communication connection request to the communication network110(T21).

The communication network110implements processing for communicating with the slice having the NSSAI indicated by the second communication connection request (T22), and as a result thereof, the request to the service-providing application113is sent via said slice (T23).

The connection destination server implements a process for providing the service (T24) and returns, to the communication device140, a response in accordance with the process (T25). Said response is received by the slice controller142via the chip set144, and the slice controller142sends said response to the application141with which the provided service is to be received (T26). As a result thereof, the application141can receive the provided service by using a slice that is not supposed to be used under the correspondence relationships between the application IDs and the NSSAI managed by the chip set144.

As described above, the communication device140according to the present disclosure comprises a slice controller142. The slice controller142comprises a slice selector1421and a first communication connection request generator1422. The slice selector1421, upon acquiring the requirements for receiving the provided service to connect the application141with the service-providing application113, refers to the policy file and selects a slice satisfying the requirements for receiving the provided service. The first communication connection request generator1422generates a first communication connection request that is associated with the application corresponding to the selected slice and not with the preferred application141with which the provided service is to be received via the communication network110. Specifically, the first communication connection request generator1422generates the first communication connection request including an application ID corresponding to the NSSAI identifying the selected slice. The first communication connection request generator1422notifies the chip set144of the first communication connection request.

By employing the features described above, slices can be dynamically configured, and the usability for users can be improved.

In contrast therewith, until now, connection was only possible by means of a uniquely determined slice in accordance with the application141to be used for receiving a provided service. For this reason, if the application141was, for example, a web browser, then the same web browser could not be used for communicating with a high QoS and for communicating with a low QoS, and the slice could not be dynamically configured. Supposing that the slices were to be managed in the applications141, each application141would need to manage the selection logic used to select the slice, the connection destination list, the NSSAI, and the like, thus complicating matters. Additionally, when the correspondence relationships between application IDs and NSSAI to which the chip set144refers are changed, the implementation of the application141would also need to be changed. Additionally, when the same service is used by multiple applications141, the same implementation must be performed in the multiple applications141.

Additionally, with the communication device140according to the present disclosure, the application141simply needs to notify the slice controller142of the requirements for receiving the provided service, including the network policy for receiving the provided service and information on the location of the server that is to provide the service. Thereafter, slice selection is performed in the slice controller142so that the application141and the service-providing application113are connected by a slice satisfying the requirements for receiving the provided service. For this reason, the application141does not need to consider the slice. Additionally, when the correspondence relationships between the application IDs and the NSSAIs to which the chip set144refers are changed, only said correspondence relationships to which the slice controller142refers need to be changed.

Additionally, with the communication device140according to the present disclosure, slices can be dynamically configured without changing the design of the chip set144. According to Non-Patent Document 1, the chip set144is designed to acquire an identifier (corresponding to the application ID) for identifying the service from the application141via the OS143. The chip set144refers to pre-defined correspondence relationships between application IDs and NSSAIs, and sends, to the communication network110, a second communication connection request including the NSSAI corresponding to the application ID.

The slice controller142according to the present disclosure uses the same correspondence relationships as the correspondence relationships to which the chip set144refers. Therefore, the chip set144does not need to undergo a design change.

(Operations in Slice Controller142)

Next, the flow chart inFIG.12will be used to explain the operations in the slice controller142.

The slice controller142acquires, from the application141, the requirements for receiving the provided service in order to connect with the service-providing application113(S11). The requirements for receiving the provided service include information regarding the network policy for receiving the provided service and the location of the server that provides the service.

The slice controller142refers to the policy file and selects a slice satisfying the requirements for receiving the provided service (S12). The policy file includes information regarding network policies and server locations permitted for the connection between the application141and the service-providing application113.

In S12, if there are multiple slices satisfying the requirements for receiving the provided service, then the slice controller142may select a slice freely. Additionally, in S12, if there are multiple slices satisfying the requirements for receiving the provided service, then the slice controller142may select the slice with the highest quality. Additionally, in S12, if there are multiple slices satisfying the requirements for receiving the provided service, then the slice controller142may select the slice with the lowest quality.

Additionally, in S12, if the policy file includes one or more slice switching conditions and at least one of the slice switching conditions is satisfied, then the slice controller142may switch the slice. Additionally, the slice switching conditions may define a relation between the status of the communication network110and a switching condition threshold value, and the slice controller142may switch the slice in accordance with a comparison result between the status of the communication network110and the switching condition threshold value. The status of the communication network110may include at least one index indicating the status, such as the RTT (Round Trip Time), the jitter, and the error rate.

The slice controller142generates a first communication connection request. The first communication connection request includes an application ID identifying an application corresponding to the selected slice (S13).

The slice controller142notifies the chip set144of the first communication connection request (S14). The chip set144is configured to send, to the communication network110, a second communication connection request for connecting with a slice. The second communication connection request includes NSSAI information corresponding to the application ID included in the first communication connection request.

(Slice Selection)

The method for selecting the slice in the slice controller142will be explained by using the flow chart inFIG.13.

The slice controller142checks whether or not the requirements for receiving the provided service acquired from the application141is a request in accordance with the permission table (S21). In other words, it checks whether or not the requirements for receiving the provided service include “Request URL”, “Server location”, and “NW Policy ID” information. Furthermore, in S21, the slice controller142may check whether or not there is a combination of “Request URL”, “Server location”, and “NW Policy ID” included in the requirements for receiving the provided service in the permission table.

If the requirements for receiving the provided service are not a request in accordance with the permission table, then the slice controller142determines that an error has occurred, and the flow is terminated (S22). Additionally, if the permission table does not contain the combination of “Request URL”, “Server location”, and “NW Policy ID” included in the requirements for receiving the provided service, then the slice controller142also determines that an error has occurred, and the flow is terminated (S22). If the slice controller142determines that an error has occurred, then it may notify the application141of the error.

If a request has requirements for receiving the provided service that are in accordance with the permission table, then the slice controller142checks whether or not the “NW Policy ID” is “Auto” (S23).

If the “NW Policy ID” is “Auto”, then the slice controller142checks whether or not the “Server location” is “Auto” (S24).

If the “Server location” is “Auto”, then the slice controller142, for example, selects a slice freely (S25).

If the “Server location” is not “Auto”, then the slice controller142selects one of the slices that is capable of connecting with the server designated by the application141(S26).

If the “NW Policy ID” is not “Auto”, then the slice controller142checks whether or not the “server location” is “Auto” (S27).

If the “Server location” is “Auto”, then the slice controller142selects one of the slices satisfying the QoS designated by the application141(S28).

If the “Server location” is not “Auto”, then the slice controller142selects a slice that satisfies the QoS designated by the application141and that connects to the server designated by the application141(S29).

(Structure of Communication Device140)

FIG.14is a block diagram illustrating an example of the structure of the communication device140illustrated inFIG.4.

The communication device140comprises a chip set310, a processor320, a memory330, and a communicator340. The communication device140may also comprise one or more processors320and memories330.

The chip set310performs the processes in the chip set144illustrated inFIG.4. The chip set310may be a virtual chip set that is realized by software.

The processor320operates the memory330and the communicator340, and the processor320also performs the processes in the slice controller142illustrated inFIG.4. That is, the slice controller142is realized by the processor320.

The memory330, for example, stores policy files. A program that is read for the processor320to realize the slice controller142may be stored in a non-volatile manner in the memory330. Alternatively, the program may be stored in a non-volatile manner in an external storage medium, and the program may also be temporarily stored in the memory330to allow the program to be read by the processor320.

The communicator340exchanges data with the application141and the OS143illustrated inFIG.4.

The communication device140may further include other structures that are not illustrated.

As mentioned above, the communication device140according to the present disclosure includes a chip set310and one or more processors320. The chip set310manages correspondence relationships between applications and slices provided in the communication network. The chip set310, upon acquiring a first communication connection request, sends, to the communication network, a second communication connection request based on the correspondence relationships. The first communication connection request is a connection request for receiving the provided service via the communication network110. The second communication connection request is a connection request for performing, via a corresponding slice, communication associated with the application with which the provided service is to be received.

The one or more processors acquire, from a preferred application with which the provided service is to be received via the communication network110, requirements for receiving the provided service. The one or more processors refer to a policy file to select a slice satisfying the requirements for receiving the provided service from among one or more slices provided in the communication network110. The one or more processors generate the first communication connection request associated with an application corresponding to the selected slice and not with the preferred application with which the provided service is to be received via the communication network110. The one or more processors notify the chip set of the generated first communication connection request.

By employing the features described above, a process for connecting to a slice satisfying a desired policy is performed, and slices can be dynamically configured. As a result thereof, the usability for users can be improved.

Additionally, a policy that can be permitted between the application141and the service-providing application113is configured in the policy file. Therefore, a slice not satisfying a permitted policy will not be selected. In other words, restrictions can be placed on the connections between the application141and the service-providing application113.

Additionally, in the policy file, a network policy and a server location that are permitted for connections between the application141and the service-providing application113can be configured. For this reason, for example, the slice can also be changed in accordance with the status of the communication network110.

The present disclosure is not limited to the structures mentioned above, and the present disclosure also includes a program. That is, a program that, when read by a computer, makes one or more processors in the computer execute the slice configuration method of the present disclosure is also included in the present disclosure. Additionally, a non-transitory, computer-readable medium having the above-mentioned program recorded therein is also included in the present disclosure.

The present disclosure includes the following embodiments.

[1] A communication device comprising:a chip set that is configured to manage correspondence relationships between applications and slices provided in a communication network, and upon acquiring a first communication connection request for receiving a provided service via the communication network, to send, to the communication network, a second communication connection request for performing, via a corresponding slice, communication associated with an application with which the provided service is to be received, based on the correspondence relationships; andone or more processors;whereinthe one or more processors execute processes ofacquiring, from a preferred application with which the provided service is to be received via the communication network, a requirement for receiving the provided service, and referring to a policy file to select a slice satisfying the requirement from among one or more slices provided in the communication network,generating the first communication connection request associated with an application corresponding to the selected slice and not with the preferred application with which the provided service is to be received via the communication network, andnotifying the chip set of the generated first communication connection request.

[2] The communication device according to [1], whereinthe policy file includes information regarding a network policy and a server location that are permitted for a connection between the application with which the provided service is to be received and a service-providing application executed on a server for providing the service.

[3] The communication device according to [2], whereinthe requirement includes information regarding an address of the service-providing application, a network policy for receiving the provided service, and a location of the server for providing the service.

[4] The communication device according to any one of [1] to [3], whereinthe first communication connection request includes an identifier for identifying an application corresponding to the selected slice among the correspondence relationships managed by the chip set.

[5] The communication device according to any one of [2] to [4], whereinthere are one or more network policies that are permitted for the connection between the application with which the provided service is to be received and the service-providing application.

[6] The communication device according to any one of [2] to [5], whereinthere are one or more server locations that are permitted for the connection between the application with which the provided service is to be received and the service-providing application.

[7] The communication device according to any one of [1] to [6], whereinselecting the slice means selecting a slice freely when there are multiple slices satisfying the requirement.

[8] The communication device according to any one of [1] to [6], whereinselecting the slice means selecting the slice with the highest quality when there are multiple slices satisfying the requirement.

[9] The communication device according to any one of [1] to [6], whereinselecting the slice means selecting the slice with the lowest quality when there are multiple slices satisfying the requirement.

[10] The communication device according to any one of [1] to [9], whereinthe policy file further includes one or more slice switching conditions, andthe one or more processors further execute a process ofswitching the slice when at least one of the slice switching conditions is satisfied.

[11] The communication device according to [10], whereinin the slice switching conditions, a relation is defined between a status of the communication network and a switching condition threshold value, andthe one or more processors further execute a process ofswitching the slice in accordance with a comparison result between the status of the communication network and the switching condition threshold value.

[12] The communication device according to [11], whereinthe status of the communication network includes at least one of RTT (Round Trip Time), jitter, and error rate.

[13] The communication device according to any one of [1] to [12], whereinthe policy file is prepared or updated when requesting to register for a service, when requesting an update, or periodically.

[14] The communication device according to any one of [1] to [13], whereinthe chip set is a virtual chip set that is realized by software.

[15] A slice configuration method that involvesacquiring, from a preferred application with which a provided service is to be received via a communication network, a requirement for receiving the provided service, and referring to a policy file to select a slice satisfying the requirement from among one or more slices provided in the communication network,generating a first communication connection request associated with an application corresponding to the selected slice and not with the preferred application with which the provided service is to be received via the communication network, andnotifying a chip set of the generated first communication connection request, the chip set being configured to manage correspondence relationships between applications and slices provided in the communication network, and upon acquiring the first communication connection request for receiving the provided service via the communication network, to send, to the communication network, a second communication connection request for performing, via a corresponding slice, communication associated with the application with which the provided service is to be received, based on the correspondence relationships.

[16] A non-transitory, computer-readable medium having, recorded therein, a program that, when read by a computer, makes one or more processors in the computer execute processes of:acquiring, from a preferred application with which a provided service is to be received via a communication network, a requirement for receiving the provided service, and referring to a policy file to select a slice satisfying the requirement from among one or more slices provided in the communication network,generating a first communication connection request associated with an application corresponding to the selected slice and not with the preferred application with which the provided service is to be received via the communication network, andnotifying a chip set of the generated first communication connection request, the chip set being configured to manage correspondence relationships between applications and slices provided in the communication network, and upon acquiring the first communication connection request for receiving the provided service via the communication network, to send, to the communication network, a second communication connection request for performing, via a corresponding slice, communication associated with the application with which the provided service is to be received, based on the correspondence relationships.

REFERENCE SIGNS LIST

100Communication system111RAN (Radio Access Network)112CN (Core Network)113Service-providing application110Communication network120Portal site130Management device140Communication device141Application142Slice controller1421Slice selector1422First communication connection request generator143OS (Operation System)144Chip set210Antenna site220Edge data center230RDC (Regional Data Center)240CDC (Central Data Center)250PDC (Public Data Center)310Chip set320Processor330Memory340Communicator