Communication control device and communication control method

Abstract

To allow slices to be flexibly and appropriately used even when there are restrictions on slice IDs that can be handled by a base station.SOLUTION: A communication control device 10 includes a memory unit 11 that stores correspondence between a base station slice ID, which is a slice ID used in a base station 30, and a plurality of core slice IDs, which are slice IDs used in a core network CN, an allocation unit 12 that assigns a core slice ID to a mobile communication terminal 100 in the core network CN, and a notification unit 13 that notifies the base station of the base station slice ID that is associated in the correspondence stored in the memory unit 11 with the core slice ID assigned to the mobile communication terminal 100 by the allocation unit 12, as the slice ID related to the mobile communication terminal 100.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a communication control device and a communication control method. [Background technology]

[0002] Conventionally, slices have been known as a technology related to 5GC (5th Generation Core network). A slice is a virtual network logically generated on a network infrastructure, which is a physical network, using virtualization technology. Each slice provides specific network functions and network characteristics. By assigning mobile communication services (communication services) to slices, it is possible to provide mobile communication services using independent slices. This makes it easier to satisfy the requirements of each service when slices are assigned to services with various requirements, and reduces the signaling processing, etc. In a mobile communication network, slices are identified by a slice ID called S-NSSAI (Single-Network Slice Selection Assistance Information) (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-18164 Summary of the Invention [Problem to be solved by the invention]

[0004] The slice ID consists of 32 bits: an 8-bit SST (Slice / Service Type) that indicates the slice behavior for functions and services, and a 24-bit SD (Slice Differentiator) that distinguishes between multiple slices in the same SST. The SST range is standardized from 0 to 127, with 1 to 5 having standardized uses. Also, 128 to 255 are operator-specific.

[0005] If all 32 bits are used, the number of slice IDs is 2 to the power of 32, or 4,294,967,296. However, the standard specifies a total of 66559, consisting of the standard slice ID 1024 and the extended slice ID 65535, and the actual upper limit of the number of slice IDs that can be used is 66559.

[0006] However, because some base stations (radio base stations, gNBs (next generation NodeBs)) that make up mobile communication networks do not support extended slice IDs, or because some base stations have restrictions on the slice IDs that can be used, it has not been possible to use all 66559 slice IDs. This has led to the problem of being unable to use slices flexibly and appropriately in mobile communication networks.

[0007] The present invention has been made in consideration of the above, and aims to provide a communication control device and a communication control method that can flexibly and appropriately use slices even when there are restrictions on the slice IDs that can be handled by a base station. [Means for solving the problem]

[0008] In order to achieve the above-mentioned object, the communication control device of the present invention comprises a memory unit that stores a correspondence between a base station slice ID, which is a slice ID used in a base station, and a plurality of core slice IDs, which are slice IDs used in a core network; an allocation unit that assigns a core slice ID to a mobile communication terminal in the core network; and a notification unit that notifies the base station of the base station slice ID that is associated in the correspondence stored in the memory unit with the core slice ID assigned to the mobile communication terminal by the allocation unit, as the slice ID related to the mobile communication terminal.

[0009] According to the communication control device of the present invention, a base station slice ID corresponding to a core slice ID assigned to a mobile communication terminal is notified to the base station as the slice ID associated with the mobile communication terminal. A base station slice ID is associated with multiple core slice IDs. Therefore, according to the communication control device of the present invention, even if there are restrictions on the slice IDs that can be handled by a base station, the core network and the mobile communication terminal can use slice IDs that are not bound by the restrictions, enabling flexible and appropriate use of slices.

[0010] Incidentally, the present invention can be described not only as an invention of a communication control device as described above, but also as an invention of a communication control method as described below. These are essentially the same inventions, with similar actions and effects, but in different categories.

[0011] That is, the communication control method of the present invention includes an allocation step in which a communication control device having a memory unit that stores a correspondence between a base station slice ID, which is a slice ID used in a base station, and a plurality of core slice IDs, which are slice IDs used in a core network, assigns a core slice ID to a mobile communication terminal in the core network, and a notification step in which a base station slice ID that is associated in the correspondence stored in the memory unit with the core slice ID assigned to the mobile communication terminal in the allocation step is notified to the base station as the slice ID related to the mobile communication terminal. [Effects of the Invention]

[0012] According to the present invention, even if there are restrictions on the slice IDs that can be handled by a base station, slices can be used flexibly and appropriately. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating a configuration of an AMF (Access and Mobility management Function), which is a communication control device according to an embodiment of the present invention, and a configuration of a mobile communication system including the AMF. [Figure 2] 10 is an example of a mapping table relating to dummy slice IDs used in AMF. [Figure 3] 10 is another example of a mapping table relating to dummy slice IDs used in AMF. [Figure 4] 1 is a sequence diagram showing a process executed by an AMF, which is a communication control device according to an embodiment of the present invention, when registering the location of a UE (User Equipment). FIG. [Figure 5] 10 is a sequence diagram showing a process executed when a PDU (Packet Data Unit) session related to a UE is established in an AMF, which is a communication control device according to an embodiment of the present invention. FIG. [Figure 6] 10 is a flowchart illustrating a dummy slice conversion process. [Figure 7] 1 is a diagram illustrating a hardware configuration of an AMF (or a physical server or the like in which the AMF is realized) that is a communication control device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, a communication control device and a communication control method according to an embodiment of the present invention will be described in detail with reference to the drawings. In the description of the drawings, the same elements are given the same reference numerals and duplicated explanations will be omitted.

[0015] FIG. 1 shows AMF10, which is a communication control device according to this embodiment. AMF10 is a device (system, node) that controls communications in a mobile communication network N. The mobile communication network N is a communication network that provides mobile communication functions to UE100, which is a mobile communication terminal (mobile device). The mobile communication network N according to this embodiment is, for example, a 5G mobile communication network. However, the mobile communication network N does not need to be a 5G mobile communication network, and may be any mobile communication network within a framework that complies with this embodiment.

[0016] The UE 100 is a device having a function of connecting to a mobile communication network N and performing mobile communication. The UE 100 is, for example, a mobile phone or a smartphone used by a user. The UE 100 may be a conventional one.

[0017] The mobile communication network N provides mobile communication-related services to the UE 100 using a slice 20, which is a virtual network generated on a network infrastructure. The mobile communication network N includes network resources (network infrastructure), which are physical networks including links (e.g., lines or transmission paths between devices) and nodes (e.g., the devices themselves) of network devices. The slice 20 is logically generated by dividing resources physically or virtually and combining the divided resources.

[0018] Specifically, the slice 20 is realized on a physical server, which is one of the resources, or on a dedicated network device (e.g., a router or a switch). The mobile communication network N assigns the mobile communication functions required to realize the service to the slice 20, and provides the service to the UE 100 for each slice 20. The service is a service that uses network resources, such as a communication service similar to that provided by a conventional slice 20. Multiple slices 20 can be provided in the mobile communication network N, and the services provided by each slice 20 are different. When the UE 100 performs mobile communication, it connects to one of the slices 20 and receives the service from that slice 20.

[0019] In this embodiment, slice 20 constitutes a core network CN of the mobile communication network N. However, slice 20 may also constitute a part of the mobile communication network N other than the core network CN. Slice 20 is configured to include NFs (Network Functions), which are multiple functional elements (network function units). NFs have functions for realizing slice 20. Specifically, NFs include AMF, SMF (Session Management Function), and UPF (User Plane Function), etc., depending on their functions. In other words, AMF 10 may also be part of slice 20. AMF 10 is an NF that has the function of managing the location of UE 100 and performing communication path setting processing. SMF is an NF that has a session management function. UPF is an NF that has the function of transmitting and receiving user data used to provide services.

[0020] The slice 20 may include nodes other than those described above. The slice 20 itself may be a conventional one, and the generation of the slice 20 may be performed in the same manner as in the past. The slice 20 is identified by a slice ID called S-NSSAI.

[0021] The AMF 10, which is a communication control device according to this embodiment, configures (is included in) the core network CN of the mobile communication network N. The AMF 10 according to this embodiment has functions that a conventional AMF has in addition to the functions according to this embodiment described below.

[0022] The mobile communication network N includes a gNB 30, which is a base station. The gNB 30 relays data between the UE 100 and the core network CN of the mobile communication network N by wirelessly transmitting and receiving data related to mobile communication with the UE 100. The gNB 30 is usually provided at each position in the communication area of ​​the mobile communication network N. The gNB 30 itself may be a conventional one.

[0023] In addition to the above, the mobile communication network N and the core network CN may also include devices and nodes included in conventional mobile communication networks and core networks.

[0024] Conventionally, when performing processing related to a UE, a gNB uses the slice ID of the slice to which the UE is connected. Typically, a core network (CN) can use slice IDs without any restrictions. On the other hand, as mentioned above, a gNB may have restrictions on the slice IDs that it can use. Conventionally, when a gNB is newly included in a mobile communication network (when the gNB is first connected (NG Setup)), the gNB transmits a list of slice IDs that it can support (support slice list) to the AMF. When assigning a slice (slice ID) to a UE, the AMF selects one included in the list of slice IDs related to the gNB to which the UE is connected.

[0025] Therefore, conventionally, the core network CN also has restrictions according to the gNB when allocating slice IDs to UEs. Therefore, conventional mobile communication networks have had a problem in that slices cannot be used flexibly and appropriately. This embodiment enables slices to be used flexibly and appropriately even when there is a restriction on slice IDs that can be used by the gNB 30.

[0026] Next, a description will be given of the functions of the AMF 10, which is a communication control device according to this embodiment. As shown in FIG.

[0027] The storage unit 11 is a functional unit that stores correspondence between a base station slice ID, which is a slice ID used in a base station, and a plurality of core slice IDs, which are slice IDs used in a core network. The storage unit 11 may store correspondence for each base station. The storage unit 11 may store correspondence between a combination of a core slice ID and a connection destination of a mobile communication terminal, for a base station slice ID. The storage unit 11 may store correspondence between a combination of a core slice ID and contract information related to a contract of a mobile communication terminal, for a base station slice ID.

[0028] In this embodiment, the slice IDs (core slice IDs) used in the core network CN are made different from the slice IDs (base station slice IDs) used in the gNB 30. This eliminates the restriction on the use of slice IDs in the core network CN due to the restriction on slice IDs available to the gNB 30. However, the slice IDs (core slice IDs) used in the core network CN and the slice IDs (base station slice IDs) used in the gNB 30 may include the same IDs.

[0029] In the following description, the slice ID (core slice ID) used in the core network CN may be simply referred to as a slice ID. The slice ID (base station slice ID) used in the gNB30 is referred to as a dummy slice ID. The dummy slice ID is a slice ID that the gNB30 can support (use). For example, the dummy slice ID may be included in a list of slice IDs that the gNB30 can support, which is sent to the AMF when the gNB30 is newly included in the mobile communication network (when the gNB30 connects for the first time (NG Setup)). In this embodiment, the slice ID and the dummy slice ID are associated with each other, and processing related to the slice ID is performed based on this association.

[0030] As described above, the number of slice IDs that the gNB 30 can support (use) may be smaller than the number of slice IDs (core slice IDs) that can be used in the core network CN. Therefore, in the above association, one dummy slice ID is associated with multiple slice IDs (core slice IDs). However, the dummy slices may also include ones that are associated with one slice ID (core slice ID).

[0031] The storage unit 11 stores the correspondence in advance. For example, the storage unit 11 stores the correspondence between slice IDs (core slice IDs) and dummy slice IDs using the mapping table shown in FIG. 2. The correspondence is set in advance and input to the AMF 10. Alternatively, the correspondence may be generated by the AMF 10.

[0032] A slice associated with a dummy slice ID and a slice associated with a slice ID (core slice ID) associated with the dummy slice ID have similar functions (for example, functions related to communication throughput or delay). This allows the gNB 30 to perform appropriate processing using the dummy slice ID.

[0033] The storage unit 11 may store the above-mentioned association (for example, the mapping table shown in FIG. 2) for each gNB 30. That is, the association between slice IDs (core slice IDs) and dummy slice IDs may differ between gNBs 30.

[0034] As will be described later, when determining a dummy slice ID using not only a slice ID (core slice ID) but also a DNN (Data Network Name) and slice mapping information, the storage unit 11 may store the association including the DNN and the slice mapping information. For example, the storage unit 11 stores the association using a mapping table shown in FIG. 3.

[0035] The DNN is information that identifies the data network to which the UE 100 is connected. The slice mapping information is information used to determine a dummy slice ID for each UE 100 (user) that is set by a contract between the user of the UE 100 and an operator that provides the mobile communication network N. That is, the slice mapping information is contract information related to the contract of the UE 100. Note that the slice mapping information is information that is not used in conventional mobile communication networks.

[0036] Specifically, the slice mapping information may be any information that can be an identifier such as A, B, C, etc. Furthermore, the slice mapping information may be any information that can be used to determine a dummy slice ID, as will be described later. The slice mapping information is stored, for example, in a Unified Data Management (UDM) included in the core network CN, in association with the UE 100 (user) together with other contract-related information. Note that the slice mapping information does not need to be associated with all UEs 100, and may be associated with some of the UEs 100.

[0037] The correspondence may include a combination of a slice ID (core slice ID) and a DNN, a combination of a slice ID (core slice ID) and slice mapping information, and a combination of a slice ID (core slice ID), a DNN, and slice mapping information.

[0038] The information stored in the storage unit 11 need not necessarily be the above information, but may be a correspondence between slice IDs (core slice IDs) and dummy slice IDs. The information stored in the storage unit 11 is referenced by the notification unit 13, as will be described later.

[0039] The allocation unit 12 is a functional unit in the core network that allocates a core slice ID to a mobile communication terminal. The allocation unit 12 allocates, to the UE 100, the slice ID of a slice (core slice ID) that the UE 100 uses for communication, for example, as follows.

[0040] For example, when the UE 100 performs location registration (Registration) in the mobile communication network N, if the AMF 10 receives a location registration request (Registration Request) transmitted from the UE 100, the allocation unit 12 allocates a slice ID (core slice ID) to the UE 100. The allocation unit 12 allocates a slice ID to the UE 100 without considering slice IDs that can be supported by the gNB 30 to which the UE 100 is connected (i.e., slice IDs included in a support slice list).

[0041] The allocation of a slice ID by the allocation unit 12 may be performed in the same manner as conventional slice ID allocation, except that slice IDs that are supported by the gNB 30 to which the UE 100 is connected are not taken into consideration. For example, the allocation unit 12 determines whether to provide a slice, as in the conventional case, and allocates a slice ID to the UE 100. The determination of whether to provide a slice may be performed by referring to contract information of the UE 100 (the user of the UE 100) stored in the UDM included in the core network CN, as in the conventional case. Furthermore, the determination of a slice ID to be allocated to the UE 100 (slice selection) may be performed by an NSSF (Network Slice Selection Function) included in the core network CN, as in the conventional case.

[0042] The allocation unit 12 notifies the UE 100 of the slice ID allocated to the UE 100, as in the conventional manner. The UE 100 performs processing related to the slice using the notified slice ID, as in the conventional manner. Furthermore, the allocation unit 12 outputs the allocated slice ID to the notification unit 13. In the core network CN, processing related to the slice for the UE 100 is performed using the slice ID allocated by the allocation unit 12. The slice associated with the slice ID allocated to the UE 100 by the allocation unit 12 is used for communication of the UE 100 via the mobile communication network N. That is, the UE 100 connects to the slice associated with the slice ID allocated by the allocation unit 12 and receives the provision of mobile communication services.

[0043] The notification unit 13 is a functional unit that notifies the base station of a base station slice ID that is associated in the association stored in the storage unit 11 with a core slice ID assigned to the mobile communication terminal by the allocation unit 12, as a slice ID related to the mobile communication terminal. The notification unit 13 may notify the base station of a base station slice ID based on the association stored in the storage unit 11 for a base station to which the mobile communication terminal is connected. The notification unit 13 may notify the base station of a base station slice ID that is associated in the association stored in the storage unit 11 with a combination of a core slice ID assigned to the mobile communication terminal by the allocation unit 12 and a connection destination of the mobile communication terminal, as a slice ID related to the mobile communication terminal. The notification unit 13 may notify the base station of a base station slice ID that is associated in the association stored in the storage unit 11 with a combination of a core slice ID assigned to the mobile communication terminal by the allocation unit 12 and contract information related to a contract of the mobile communication terminal, as a slice ID related to the mobile communication terminal.

[0044] The notification unit 13 notifies the gNB 30 of a dummy slice ID, which is a slice ID for the base station, as the slice ID for the UE 100, for example, as follows: The notification unit 13 receives a slice ID (core slice ID) assigned to the UE 100 from the allocation unit 12. The notification unit 13 converts the slice ID received from the allocation unit 12 into a dummy slice ID, and notifies the gNB 30 of the dummy slice ID. The notification unit 13 performs the above process, for example, when the UE 100 performs location registration in the mobile communication network N and then performs a process to establish a PDU session to be used for mobile communication.

[0045] When the UE 100 establishes a PDU session in the mobile communication network N, the AMF 10 receives a session establishment request (PDU Session Establishment Request) transmitted from the UE 100. The notification unit 13 converts the slice ID into a dummy slice ID by referring to the association stored in the storage unit 11. For example, if the association stored in the storage unit 11 is as shown in FIG. 2, the notification unit 13 determines the dummy slice ID associated with the slice ID input from the allocation unit 12 as the dummy slice ID to be notified to the gNB 30. If the slice ID input from the allocation unit 12 is not included in the association, the notification unit 13 may determine the slice ID input from the allocation unit 12 as the dummy slice ID to be notified to the gNB 30. Note that, if the association stored in the storage unit 11 is for each gNB 30, the notification unit 13 determines the dummy slice ID by using the association of the gNB 30 that relayed the session establishment request (i.e., the gNB 30 to which the UE 100 is connected).

[0046] For example, when the correspondence stored by the storage unit 11 is as shown in FIG. 3, the notification unit 13 acquires information other than the slice ID for determining the dummy slice ID. The information for determining the dummy slice ID is a DNN and slice mapping information. For example, the DNN is included in the session establishment request transmitted from the UE 100, and the notification unit 13 acquires the DNN from the session establishment request. Alternatively, the DNN is included in a subscriber profile held in the core network CN, and the notification unit 13 acquires the DNN from the subscriber profile. The notification unit 13 acquires slice mapping information related to the UE 100 that transmitted the session establishment request from a UDM included in the core network CN.

[0047] If slice mapping information for the target UE 100 has been acquired, the notification unit 13 determines a dummy slice ID associated with a combination of a slice ID (core slice ID) and slice mapping information in the association shown in Fig. 3 as a dummy slice ID to be notified to the gNB 30. If slice mapping information for the target UE 100 has not been acquired, the notification unit 13 determines whether the acquired DNN is a specific DNN that has been set in advance. The specific DNN is, for example, a DNN included in the mapping table shown in Fig. 3.

[0048] If it is determined that the acquired DNN is a specific DNN that has been set in advance, the notification unit 13 determines a dummy slice ID that is associated with the combination of the slice ID (core slice ID) and the DNN in the association shown in Fig. 3 as a dummy slice ID to be notified to the gNB 30. If it is determined that the acquired DNN is not a specific DNN that has been set in advance, the notification unit 13 determines a dummy slice ID that is associated with the slice ID (core slice ID) as a dummy slice ID to be notified to the gNB 30. If the slice ID is not included in the association, the notification unit 13 determines the slice ID as a dummy slice ID to be notified to the gNB 30.

[0049] Furthermore, the notification unit 13 may determine a dummy slice ID associated with a combination of a slice ID (core slice ID), slice mapping information, and a DNN as a dummy slice ID to be notified to the gNB 30. Furthermore, the notification unit 13 may determine a dummy slice ID from a slice ID (core slice ID) by a method other than the above, as long as the method is based on the association stored in the storage unit 11.

[0050] Furthermore, the timing of determining the dummy slice ID and notifying it to the gNB 30 does not necessarily have to be as described above. For example, the dummy slice ID may be determined immediately after the slice ID (core slice ID) is assigned to the UE 100 (for example, during the process of registering the location of the UE 100).

[0051] The notification unit 13 notifies the gNB 30 of the determined dummy slice ID as the slice ID for the UE 100. The gNB 30 receives the notification of the dummy slice ID from the notification unit 13. The gNB 30 performs processing related to the slice for the UE 100 using the dummy slice ID notified by the notification unit 13. Note that the location registration processing of the UE 100, the PDU session establishment processing, and the mobile communication of the UE 100 may be performed in the same manner as conventional processing, except as described above. The above are the functions of the AMF 10 according to this embodiment.

[0052] Next, a communication control method, which is a process executed by the AMF 10 according to this embodiment (an operating method performed by the AMF 10 according to this embodiment), will be explained using the sequence diagrams of Figures 4 and 5 and the flowchart of Figure 6.

[0053] First, the process of assigning a slice ID (core slice ID) to UE 100 will be described using the sequence diagram of Fig. 4. This process is performed when the location of UE 100 is registered. In this process, first, a location registration request is transmitted from UE 100 to mobile communication network N (S01). The transmitted location registration request is transmitted to AMF 10 via gNB 30. In AMF 10, allocation unit 12 receives the location registration request.

[0054] Next, the allocation unit 12 allocates a slice ID (core slice ID) to the UE 100 in the core network CN (S02, allocation step). The allocated slice ID (core slice ID) is notified to the UE 100 from the allocation unit 12 (S03). The slice ID (core slice ID) notified to the UE 100 is used for processing related to the slice in the UE 100, as in the conventional case. Furthermore, the UE 100 and the mobile communication network N perform processing related to location registration, as in the conventional case (not shown). This completes the process of allocating a slice ID (core slice ID) to the UE 100.

[0055] Next, the process of notifying the gNB 30 of the dummy slice ID will be described using the sequence diagram of Fig. 5. This process is performed when a PDU session related to the UE 100 is established, after the process of registering the location of the UE 100 shown in Fig. 4. In this process, first, a session establishment request is transmitted from the UE 100 to the mobile communication network N (S11). The transmitted session establishment request is transmitted to the AMF 10 via the gNB 30. In the AMF 10, the notification unit 13 receives the session establishment request.

[0056] Next, the notification unit 13 determines, as the slice ID related to the UE 100, a dummy slice ID associated in the association stored in the storage unit 11 with the slice ID (core slice ID) assigned to the UE 100 by the allocation unit 12 (S12, notification step). That is, conversion from the slice ID (core slice ID) to a dummy slice ID is performed. The association stored in the storage unit 11 may be for each gNB 30. Information other than the slice ID (core slice ID) (e.g., DNN and slice mapping information) may be used to determine the dummy slice ID. The determined dummy slice ID is notified to the gNB 30 by the notification unit 13 as the slice ID related to the UE 100 (S13, notification step). Then, subsequent session establishment processing related to the session establishment request from the UE 100 is performed (S14).

[0057] The above process enables mobile communication of UE 100 in the mobile communication network N using slice 20 of the slice ID assigned to UE 100. Furthermore, the core network CN and UE 100 perform processing related to slice 20 using the slice ID (core slice ID), and gNB 30 performs processing related to slice 20 using a dummy slice ID. The above is the process by which the dummy slice ID is notified to gNB 30.

[0058] Next, using the flowchart of Figure 6, we will explain the process of converting a slice ID (core slice ID) to a dummy slice ID by the notification unit 13 (S12 in Figure 5) when the mapping table shown in Figure 3 is used as the correspondence stored by the memory unit 11.

[0059] In this process, in the previous process, the DNN indicating the connection destination of UE 100 and slice mapping information of UE 100 (the user) have been acquired by notification unit 13 as information for determining the dummy slice ID. For example, the DNN is acquired from a session establishment request transmitted from UE 100 or a subscriber profile held in the core network. The slice mapping information is acquired from the UDM when a slice ID is assigned (S02).

[0060] In this process, first, it is determined whether slice mapping information has been acquired for the target UE 100 (S121). If it is determined that slice mapping information has been acquired (NO in S121), a dummy slice ID associated with a combination of a slice ID (core slice ID) and slice mapping information in the association shown in the mapping table of Fig. 3 is determined as a dummy slice ID to be notified to the gNB 30 (S121).

[0061] If it is determined that slice mapping information has not been acquired (YES in S121), it is then determined whether the DNN is a specific DNN that has been set in advance (S123). If it is determined that the DNN is a specific DNN that has been set in advance (YES in S123), a dummy slice ID that is associated with the combination of the slice ID (core slice ID) and the DNN in the association shown in the mapping table of FIG. 3 is determined as the dummy slice ID to be notified to the gNB 30 (S124).

[0062] If it is determined that the DNN is not a specific DNN that has been set in advance (NO in S123), it is then determined whether or not the slice ID (core slice ID) exists in the mapping table of Fig. 3 (S125). If it is determined that the slice ID (core slice ID) exists in the mapping table of Fig. 3 (YES in S125), the dummy slice ID associated with the slice ID (core slice ID) in the association shown in the mapping table of Fig. 3 is determined as the dummy slice ID to be notified to the gNB 30 (S126).

[0063] If it is determined that the slice ID (core slice ID) does not exist in the mapping table of FIG. 3 (NO in S125), the slice ID (core slice ID) is determined as a dummy slice ID to be notified to the gNB 30 (S127). Once the dummy slice ID is determined as described above, the determined dummy slice ID is output (S128). The above is the process of conversion to a dummy slice ID when the mapping table shown in FIG. 3 is used.

[0064] In the present embodiment, a dummy slice ID corresponding to a slice ID (core slice ID) assigned to the UE 100 is notified to the gNB 30 as a slice ID related to the UE 100. A plurality of slice IDs (core slice IDs) are associated with the dummy slice ID. Therefore, according to the present embodiment, even if there are restrictions on the slice IDs that can be handled by the gNB 30, the core network CN and the UE 100 can use slice IDs that are not bound by the restrictions. For example, by changing the slice ID (core slice ID) used by the core network CN and the UE 100 to a dummy slice ID for the gNB 30, communication using the extended slice ID as the slice ID (core slice ID) becomes possible even if the gNB 30 does not support the extended slice ID.

[0065] The slice IDs used by the gNB 30, i.e., the control of radio resources by the slice IDs, can be consolidated to some extent by application. On the other hand, the core network CN side can separate slices 20 (networks) by slice ID, which provides the advantage of fine control. This embodiment makes it possible to use a large number of slice IDs, even if various gNBs 30, such as those that do not support extended slice IDs, are mixed, enabling flexible network design. In this way, this embodiment allows slices 20 to be used flexibly and appropriately.

[0066] As in the present embodiment, the association between slice IDs (core slice IDs) and dummy slice IDs may be for each gNB 30. According to this configuration, for example, it is possible to make an association for each gNB 30 taking into consideration slice IDs that the gNB 30 can support. As a result, it is possible to use the slices 20 more flexibly and appropriately. However, the association does not necessarily have to be for each gNB 30, and may be uniform.

[0067] As in the present embodiment, a combination of a slice ID (core slice ID) for a dummy slice and a connection destination of UE 100, such as a DNN, may be associated with the dummy slice. This configuration allows the use of a dummy slice ID that is also appropriate for the connection destination of UE 100. As a result, slice 20 can be used flexibly and appropriately depending on the connection destination of UE 100. Alternatively, the information can be flexibly used to prevent the table size of the mapping table from increasing or to simplify mapping for the purpose of reducing resources.

[0068] For example, in the core network CN, it is possible to specify a U-Plane device (UPF) using a DNN and a slice ID. For example, if DNN=xxxxxx.ne.jp and the slice ID is 1, it is possible to select equipment in region A, and if the slice ID is 3, it is possible to select equipment in region B. However, in the case of DNN=xxxxxx.ne.jp, if the requirements on the wireless (gNB30) side are similar, the dummy slice ID can be 1.

[0069] Similarly, in the case of a different DNN = yyyyyy.ne.jp, slice IDs 1 and 3 on the core network CN side can be used to map to slice ID 2 as a requirement on the radio (gNB30) side.

[0070] In the case of DNN=yyyyyy.ne.jp, it is possible to achieve the same thing without using DNN as a key by using slice IDs 2 and 4 instead of 1 and 3. However, using DNN as a key makes it possible to reduce the table size and simplify the configuration of the core network CN (for example, if slice ID is 1, it is region A, and if slice ID is 2, it is region B).

[0071] It should be noted that the connection destination of the UE 100 does not necessarily need to be used to determine the dummy slice ID.

[0072] As in the present embodiment, a combination of a slice ID (core slice ID) for a dummy slice and contract information related to the contract of UE 100, such as slice mapping information, may be associated with the dummy slice. This configuration allows the use of a dummy slice ID that is also in accordance with the contract of UE 100. As a result, slice 20 can be used flexibly and appropriately in accordance with the contract of UE 100. Alternatively, the information can be flexibly used to prevent the table size of the mapping table from increasing or to simplify mapping for the purpose of reducing resources.

[0073] The use of slice mapping information assumes, for example, a case where the same equipment is used for the DNN and the slice ID, and the core network CN uses the same facility, but only the slice ID notified to the radio (gNB 30) side is changed. Even in this case, the same thing can be achieved by changing the slice ID rather than the slice mapping information. However, if the system secures internal resources using the slice ID and DNN, changing the slice ID will result in wasted resources, even if the same equipment is selected. By using slice mapping information, it is possible to change only the slice ID notified to the radio (gNB 30) side, while the slice ID and DNN remain the same.

[0074] Note that the contract information related to the contract of UE 100 may be something other than slice mapping information. Also, the contract information related to the contract of UE 100 does not necessarily need to be used to determine a dummy slice ID.

[0075] As described above, the communication control device according to this embodiment is the AMF 10. However, the communication control device does not need to be the AMF 10, and may be a device or node other than the AMF 10 as long as it realizes the above-described functions.

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

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

[0078] For example, the AMF 10 (or a physical server or the like in which the AMF 10 is implemented) in one embodiment of the present disclosure may function as a computer that performs processing of the method of the present disclosure. FIG. 7 is a diagram illustrating an example of a hardware configuration of the AMF 10 (or a physical server or the like in which the AMF 10 is implemented) in one embodiment of the present disclosure. The above-mentioned AMF 10 (or a physical server or the like in which the AMF 10 is implemented) may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc. In addition, the hardware configurations of other components of the mobile communication network N and the UE 100 may also be as described here.

[0079] In the following explanation, the term "apparatus" can be interpreted as a circuit, device, unit, etc. The hardware configuration of AMF 10 (or the physical server on which it is implemented) may be configured to include one or more of the apparatuses shown in the figure, or may be configured to exclude some of the apparatuses.

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

[0081] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, each function of the AMF 10 described above may be realized by the processor 1001.

[0082] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, each function of the AMF 10 may be realized by a control program stored in the memory 1002 and running on the processor 1001. Although the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

[0084] Storage 1003 is a computer-readable recording medium and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray® disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The storage medium provided in AMF 10 (or the physical server on which AMF 10 is implemented, etc.) may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

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

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

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

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

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

[0090] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

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

[0092] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0093] Information etc. may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

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

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

[0096] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

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

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

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

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

[0102] As used in this disclosure, the terms "system" and "network" are used interchangeably.

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

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

[0105] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0106] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

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

[0109] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, or the mobile body itself. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0110] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the UE 100 may be configured to have the functions of the gNB 30 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0111] Similarly, the user terminal in the present disclosure may be interpreted as a base station. In this case, the gNB 30 may be configured to have the functions of the UE 100 described above.

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

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

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

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

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

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

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

[0119] The communication control device and the communication control method according to the present disclosure have the following configuration. [1] A storage unit that stores correspondence between a base station slice ID, which is a slice ID used in a base station, and a plurality of core slice IDs, which are slice IDs used in a core network; an allocation unit in a core network that allocates a core slice ID to a mobile communication terminal; a notification unit that notifies a base station of a base station slice ID that is associated with a core slice ID assigned to a mobile communication terminal by the allocation unit in the association stored in the storage unit as a slice ID related to the mobile communication terminal; A communication control device comprising: [2] The storage unit stores the association for each base station; The communication control device according to [1], wherein the notification unit notifies the base station of a slice ID for the base station based on the correspondence stored by the memory unit for the base station to which the mobile communication terminal is connected. [3] The storage unit stores a correspondence between a combination of a core slice ID and a connection destination of a mobile communication terminal for a base station slice ID; A communication control device as described in [1] or [2], wherein the notification unit notifies the base station of the slice ID for the base station that is associated in the correspondence stored in the memory unit with the combination of the core slice ID assigned to the mobile communication terminal by the allocation unit and the connection destination of the mobile communication terminal as the slice ID related to the mobile communication terminal. [4] The storage unit stores a correspondence between a combination of a core slice ID and contract information related to a contract of a mobile communication terminal, for a base station slice ID; A communication control device described in any of [1] to [3], wherein the notification unit notifies the base station of the slice ID for the base station that is associated in the association stored in the memory unit with the combination of the core slice ID assigned to the mobile communication terminal by the allocation unit and contract information related to the contract of the mobile communication terminal as the slice ID related to the mobile communication terminal. [5] A communication control device including a storage unit that stores correspondence between a base station slice ID, which is a slice ID used in a base station, and a plurality of core slice IDs, which are slice IDs used in a core network, assigns a core slice ID to a mobile communication terminal in the core network; a notification step of notifying the base station of a slice ID for a base station that is associated with the core slice ID assigned to the mobile communication terminal in the assignment step in the association stored in the storage unit as a slice ID related to the mobile communication terminal; A communication control method including: [Explanation of symbols]

[0120] 10...AMF, 11...storage unit, 12...allocation unit, 13...notification unit, 20...slice, 30...gNB, N...mobile communication network, CN...core network, 100...UE, 1001...processor, 1002...memory, 1003...storage, 1004...communication device, 1005...input device, 1006...output device, 1007...bus.

Claims

1. a storage unit that stores a correspondence between a base station slice ID, which is a slice ID used in a base station, and a plurality of core slice IDs, which are slice IDs used in a core network; an allocation unit in a core network that allocates a core slice ID to a mobile communication terminal; a notification unit that notifies a base station of a base station slice ID that is associated with a core slice ID assigned to a mobile communication terminal by the allocation unit in the association stored in the storage unit as a slice ID related to the mobile communication terminal; A communication control device comprising:

2. the storage unit stores the association for each base station; The communication control device according to claim 1 , wherein the notification unit notifies the base station of a base station slice ID based on the association stored in the storage unit for the base station to which the mobile communication terminal is connected.

3. the storage unit stores a correspondence between a combination of a core slice ID and a connection destination of a mobile communication terminal for a slice ID for a base station; The communication control device described in claim 1, wherein the notification unit notifies the base station of the slice ID for the base station that is associated in the correspondence stored in the memory unit with the combination of the core slice ID assigned to the mobile communication terminal by the allocation unit and the connection destination of the mobile communication terminal as the slice ID related to the mobile communication terminal.

4. the storage unit stores a correspondence between a combination of a core slice ID and contract information relating to a contract of a mobile communication terminal, for a slice ID for a base station; The communication control device described in claim 1, wherein the notification unit notifies the base station of the slice ID for the base station that is associated in the correspondence stored in the memory unit with the combination of the core slice ID assigned to the mobile communication terminal by the allocation unit and contract information related to the contract of the mobile communication terminal as the slice ID related to the mobile communication terminal.

5. an allocation step in which a communication control device including a storage unit that stores correspondence between a base station slice ID, which is a slice ID used in a base station, and a plurality of core slice IDs, which are slice IDs used in a core network, allocates a core slice ID to a mobile communication terminal in the core network; a notification step of notifying the base station of a slice ID for a base station that is associated with the core slice ID assigned to the mobile communication terminal in the assignment step in the correspondence stored in the storage unit as a slice ID related to the mobile communication terminal; A communication control method including:

Images