Network slice management device and management method

Abstract

A network slice management device according to one aspect manages network slices in a cellular network. The network slice management device has a control unit. The control unit uses packet information indicating an operation in a cellular network of packets, and a communication type determination model for determining a communication type, to set network slices, and the control unit generates a new communication type determination model in accordance with the resource conditions of the cellular network.

Description

Network slice management device and management method

[0001] The present invention relates to a network slice management device and a management method.

[0002] Network slicing has been introduced in mobile communication systems including cellular networks. Network slicing is a technology that virtually divides a physical network constructed by a carrier to create multiple virtual networks. Each virtual network is called a network slice. Network slicing allows carriers to create network slices according to the service requirements of different service types, such as enhanced Mobile Broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine type communications (mMTC). Network slicing can, for example, optimize network resources.

[0003] On the other hand, users may use terminal devices such as smartphones to execute various applications. In particular, there are now use cases in which new applications not seen before, such as remote medical care or robot control, are executed.

[0004] 3GPP TS 38.300 V17.5.0 (2023-06)3GPP TS 23.501 V17.9.0 (2023-06)

[0005] A network slice management device according to one embodiment is a network slice management device that manages network slices in a cellular network. The network slice management device includes a control unit. The control unit configures the network slice using packet information indicating the operation of a packet in the cellular network and a communication type determination model that determines the communication type. The control unit also generates a new communication type determination model according to the resource status of the cellular network.

[0006] A management method according to one embodiment is a management method in a network slice management device that manages network slices in a cellular network. The management method includes a step of setting a network slice using packet information that indicates packet behavior in the cellular network and a communication type determination model that determines the communication type. The management method also includes a step of generating a new communication type determination model according to the resource status of the cellular network.

[0007] FIG. 1 is a diagram illustrating an example of the configuration of a communication system according to the first embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a cellular network according to the first embodiment. FIG. 3 is a diagram illustrating an example of a network slice according to the first embodiment. FIG. 4 is a diagram illustrating an example of a network slice according to the first embodiment. FIG. 5 is a diagram illustrating an example of management of a network slice according to the first embodiment. FIG. 6 is a diagram illustrating an example of the configuration of a UE according to the first embodiment. FIG. 7 is a diagram illustrating an example of the configuration of a node according to the first embodiment. FIG. 8 is a diagram illustrating an example of the configuration of a CN device. FIG. 9 is a diagram illustrating an example of the configuration of a network slice management device according to the first embodiment. FIG. 10 is a diagram illustrating an example of operation according to the first embodiment. FIG. 11 is a diagram illustrating an example of a communication type determination model according to the first embodiment. FIG. 12 is a diagram illustrating an example of a communication type determination model according to the first embodiment.

[0008] [First Embodiment] As described above, network slicing has been introduced into mobile communication systems. Meanwhile, new types of communication not previously seen in mobile communication systems, such as telemedicine or robot control, may be implemented in some cases. For example, telemedicine requires not only high-speed, large-capacity communication but also low-latency communication. Furthermore, for example, robot control requires both low-latency communication and multi-connection communication.

[0009] Operators of mobile communication system infrastructure manually decide which network slice to apply for each application, from among high-speed, large-capacity (eMBB), ultra-low latency (URLLC), and multiple connections (mMTC), depending on the communication requirements of each application.

[0010] However, in the current situation where new applications are expected to increase in the future, it may take a huge amount of time and effort for an operator to manually determine which network slice to apply to each application. Also, it may take a huge amount of time and effort for an operator to manually set the performance (i.e., capability) of packets transmitted within the network for each application.

[0011] Here, a network slice refers to each virtual network obtained by virtually dividing a physical network constructed by a carrier in a cellular network. A network slice may be a logical network in a cellular network, which allows dynamic allocation of resources in the cellular network. Alternatively, a network slice may be a network obtained by virtually dividing a cellular network according to services to be provided to users.

[0012] A network slice includes a RAN slice, a transport slice, and a core slice. The RAN slice provides, for example, resource control and priority control for each network slice in a RAN (Radio Access Network) that performs radio access control. The RAN slice may also be called a RAN slice subnet. Furthermore, the transport slice provides network slice functions for each network, for example, a fronthaul (a network between a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU) when the RAN is separated into an RU, a DU, and a CU), a middlehaul (a network between a DU and a CU), and a backhaul (a network between a CU and a core network (CN)). The transport slice may also be called a transport slice subnet. Furthermore, the core slice provides, for example, core network functions in each network slice. The core slice may also be called a core slice subnet.

[0013] The network slice that the operator manually applies is intended to be applied to the entire network slice, including the RAN slice, transport slice, and core slice, for each application.

[0014] Therefore, the first embodiment aims to enable packets to exhibit optimal performance within the network.

[0015] The first embodiment will be described in detail below with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0016] (1) Example of Configuration of Communication System First, an example of the configuration of the communication system according to the first embodiment will be described.

[0017] FIG. 1 is a diagram illustrating an example of the configuration of a communication system 1.

[0018] 1, the communication system 1 includes a user equipment (UE) 100, a node 110, a CN (Core Network) device 120, and a network slice management device 130. The communication system 1 may include a cellular network 10. The cellular network 10 includes the UE 100, the node 110, the CN device 120, and the network slice management device 130.

[0019] The cellular network 10 is a network capable of wireless communication with a mobile UE 100. The cellular network 10 is also a network to which a 3GPP-standard mobile communication system is applied. The cellular network 10 is, for example, a network compliant with the 3GPP-standard 5th Generation System (5GS). The cellular network 10 may partially adopt a network compliant with the 3GPP-standard Long Term Evolution (LTE) system, or may at least partially adopt a 6th Generation (6G) system that is scheduled to be standardized in the future. The cellular network 10 may also be a mobile communication system. A configuration example of the cellular network 10 will be described later.

[0020] The UE 100 is a mobile wireless communication device. The UE 100 may be any device used by a user, but for example, the UE 100 may be a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), an aircraft or a device provided in an aircraft (Aerial UE, or UAV (Unmanned Aerial Vehicle)). Alternatively, the UE 100 may be an IoT (Internet of Things) device, an IoT sensor, or the like.

[0021] The node 110 may be connected as one node or as multiple nodes in the cellular network 10. The node 110 may function as a base station in the cellular network 10. Details of the node 110 will be described later. The node 110 may also be called a network node.

[0022] The CN device 120 functions as a communication device in the cellular network 10. The CN device 120 may be a device that connects the cellular network 10 to an external network. Alternatively, the CN device 120 may be a device having a gateway function that connects the cellular network 10 to an external network. The CN device 120 may be an Access and Mobility Management Function (AMF) that manages access and mobility control of the UE 100. Alternatively, the CN device 120 may be a Session Management Function (SMF) that manages a communication session of the UE 100 in the cellular network 10. Alternatively, the CN device 120 may be a User Plane Function (UPF) that functions as a termination point of a communication session (e.g., a Protocol Data Unit (PDU) session) with the UE 100 in the cellular network 10 and exchanges user data with the UE 100.

[0023] The network slice management device 130 manages one or more network slices in the cellular network 10. As a network slice orchestrator, the network slice management device 130 manages the RAN slice, transport slice, and core slice included in the network slice. The network slice management device 130 may manage the generation of network slices. The network slice management device 130 may also configure network slices in the node 110 and the CN device 120 by sending configuration information to the node 110 and the CN device 120. Note that "management" of a network slice may include "control" of the network slice. Alternatively, "management" of a network slice and "control" of a network slice may be used to have the same meaning.

[0024] In the first embodiment, the network slice management device 130 can also manage network slices using a learning function based on AI (Artificial Intelligence). Details will be described later. Note that, hereinafter, the network slice management device 130 may be referred to as a "network slice orchestrator" (or simply as an "orchestrator").

[0025] (1.1) Example of Cellular Network Configuration Next, an example of the configuration of the cellular network 10 will be described.

[0026] FIG. 2 is a diagram illustrating an example of the configuration of the cellular network 10 according to the first embodiment.

[0027] As shown in FIG. 2 , the cellular network 10 includes a UE 100 , a Radio Access Network (RAN) 30 , a Core Network (CN) 40 , and an orchestrator 130 .

[0028] The RAN 30 includes one or more nodes 110 (110-1 to 110-3 in the example of FIG. 2) described above. The nodes 110 are connected to each other via inter-node interfaces. The nodes 110 may also be referred to as base stations. When the cellular network 10 is 5GS, the nodes 110 are also referred to as gNBs. The nodes 110 may be configured with an RU, a CU, and a DU (i.e., functionally divided).

[0029] The node 110 manages one or more cells. The node 110 performs wireless communication with the UE 100 that has established a connection with the node 110's own cell. The node 110 has a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, and the like. Note that the term "cell" is used to indicate the smallest unit of a wireless communication area. The term "cell" is also used to indicate a function or resource for performing wireless communication with the UE 100. One cell belongs to one carrier frequency (hereinafter simply referred to as "frequency").

[0030] The CN 40 includes the CN device 120 described above.

[0031] (1.1.1) Network Slice The network slice according to the first embodiment is constructed in the cellular network 10. Here, the network slice will be described.

[0032] As described above, a network slice is a virtual network created by virtually dividing a physical network built by an operator. By building a network slice, services such as high-speed, large-capacity (eMBB), ultra-low latency (URLLC), and multiple connections (mMTC) can be provided to the UE 100 by occupying resources within the cellular network 10.

[0033] FIG. 3 is a diagram illustrating an example of a network slice. The network slice is configured on a network consisting of a RAN 30 and a CN 40. One or more network slices can be configured on the network. Each network slice is associated with one service type. Examples of service types include eMBB, URLLC, Massive Internet of Things (MIoT), Vehicle to Everything (V2X), and High Performance Machine Type Communication (HMTC). For example, as shown in FIG. 3, network slice #1 is associated with the service type eMBB, network slice #2 is associated with the service type MIoT, and network slice #3 is associated with the service type HMTC.

[0034] Each network slice is provided with a slice identifier that identifies the network slice. An example of a slice identifier is S-NSSAI (Single Network Slicing Selection Assistance Information). The S-NSSAI includes an 8-bit SST (slice / service type). The S-NSSAI may further include a 24-bit SD (slice differentiator).

[0035] SST is an example of service type information indicating a service type to which a network slice is associated. For example, SST=1 indicates eMBB, SST=2 indicates URLLC, SST=3 indicates MIoT (Massive Internet of Things), SST=4 indicates V2X (Vehicle to everything), and SST=5 indicates HMTC (High Performance Machine Type Communication). However, these are merely examples, and SST values ​​may be associated with other service types, or other service types may be associated with other SST values.

[0036] The SD is information for differentiating multiple network slices associated with the same service type.

[0037] Information including multiple S-NSSAIs is called NSSAI (Network Slice Selection Assistance Information). One or more network slices may be grouped to form a slice group. A slice group is a group including one or more network slices, and a slice group identifier is assigned to the slice group.

[0038] As shown in FIG. 3, multiple slices may be configured for one UE 100, in which case the UE 100 can simultaneously receive multiple services via each slice.

[0039] As shown in FIG. 3 , the network slices include hardware and functional blocks in the RAN 30 and the CN 40. In the example of FIG. 3 , network slice #1 includes an RU, a DU, a CU #1, and a UPF #1. Network slice #2 includes an RU, a DU, a CU #2, and a UPF #2. Network slice #3 includes an RU, a DU, a CU #3, and a UPF #3. Each hardware and logical functional block in the RAN 30 and the CN 40 may be shared by multiple network slices. Each network slice can provide services such as eMBB and URLLC to the UE 100 by using the hardware and functional blocks. Hereinafter, the hardware and functional blocks in the cellular network 10 may be simply referred to as "resources."

[0040] As described above, a network slice includes a RAN slice, a transport slice, and a core slice. Figure 4 is a diagram illustrating an example of a network slice including a RAN slice, a transport slice, and a core slice. In the example of Figure 4, network slice #1 includes RAN slice #1, transport slice #1, and core slice #1. Network slice #2 includes RAN slice #2, transport slice #2, and core slice #2. Network slice #3 includes RAN slice #3, transport slice #3, and core slice #3. In this way, by including a RAN slice, a transport slice, and a core slice in a network slice, it is possible to dynamically change the resources used in the RAN slice, for example, and to flexibly respond to the requirements of each network slice for each RAN slice, transport slice, and core slice.

[0041] The orchestrator 130 (network slice management device 130) includes a RAN slice controller 131, a transport slice controller 132, and a core slice controller 133 to manage the RAN slice, transport slice, and core slice included in the network slice, respectively. The orchestrator 130 also includes a network slice controller 135 to manage the entire network slice.

[0042] The RAN slice controller 131 controls RAN slices in the RAN 30. For example, the RAN slice controller 131 controls radio resources used in wireless communication with the UE 100 and which RAN slices resources (e.g., RU, DU, CU, etc.) in the RAN 30 used in communication with the UE 100 correspond to. The RAN slice controller 131 may control each RAN slice in accordance with instructions from the network slice controller 135. Furthermore, when a packet is transmitted in the RAN 30, the RAN slice controller 131 may obtain RAN packet information indicating how the packet operated in the RAN 30. The RAN slice controller 131 outputs the RAN packet information to the network slice controller 135.

[0043] The transport slice controller 132 controls transport slices in the fronthaul, middlehaul, and backhaul. For example, the transport slice controller 132 controls route information indicating the route from the fronthaul to the backhaul for each transport slice. The transport slice controller 132 may also control each transport slice in accordance with instructions from the network slice controller 135. Furthermore, when a packet is transmitted in the backhaul, middlehaul, and fronthaul, the transport slice controller 132 may obtain transport packet information indicating how the packet operated in the backhaul, middlehaul, and fronthaul. The transport slice controller 132 outputs the transport packet information to the network slice controller 135.

[0044] The core slice controller 133 controls which CN device 120 is applied to each network slice. The core slice controller 133 may control each core slice according to instructions from the network slice controller 135. The core slice controller 133 also outputs core packet information indicating how packets transmitted in the CN 40 behaved to the network slice controller 135.

[0045] The network slice controller 135 manages the entire network slice in the cellular network. The network slice controller 135 may instruct the RAN slice controller 131, the transport slice controller 132, and the core slice controller 133 to configure a RAN slice, a transport slice, and a core slice, respectively. The network slice controller 135 may configure a network slice as shown in FIG. 4 in advance and transmit network slice configuration information indicating the configured network slice to the AMF (or SMF) which is the CN device 120. The AMF (or SMF) may select an allowed network slice (specifically, an Allowed NSSAI) for a network slice (specifically, a Requested NSSAI) requested by the UE 100 based on the network slice configuration information.

[0046] 5(A) and 5(B) are diagrams showing examples of network slice configuration information according to the first embodiment. The network slice configuration information is managed by the orchestrator 130. As shown in FIGS. 5(A) and 5(B), each network slice is identified by an S-NSSAI, and the RAN slice, transport slice, and core slice included in the network slice are linked to the S-NSSAI.

[0047] In the example of Figure 5(A), the network slice #1 shown in Figure 4 is represented by S-NSSAI #1, and S-NSSAI #1 is linked to the identification information (ID) of RAN slice #1, the identification information (ID) of transport slice #1, and the identification information (ID) of core slice #1. This allows the network slice controller 135 to manage the RAN slice #1, transport slice #1, and core slice #1 in the network slice #1. The ID of the RAN slice #1 then links the radio resources used in the RAN slice #1 to the identification information of the RU, DU, and CU #1 in the RAN 30. This allows the network slice controller 135 to manage the radio resources and hardware used in the RAN slice #1.

[0048] Furthermore, the network slice controller 135 associates route information #1 with the ID of the transport slice #1 and manages it, thereby enabling management of which backhaul, which middlehaul, and which fronthaul are used for the transport slice #1. Furthermore, the network slice controller 135 associates UPF #1 with the ID of the core slice #1 and manages it, thereby enabling management of which core network function is included in the core slice #1 (UPF #1 in FIG. 5A). Note that, regarding route information, a route table (or routing table) may be prepared that stores route information representing each route from the backhaul to the fronthaul. The network slice controller 135 may acquire route information using the route table.

[0049] In addition, the network slice configuration information and route table shown in Figures 5 (A) and 5 (B) may be stored in memory within the orchestrator 130.

[0050] Returning to FIG. 4, the network slice controller 135 may obtain packet information indicating the behavior of packets transmitted in the cellular network 10 based on the RAN packet information, the transport packet information, and the core packet information.

[0051] (1.1.2) Example of Configuration of Each Device in the Cellular Network Next, an example of the configuration of each device in the cellular network 10 will be described.

[0052] First, a configuration example of the UE 100 will be described.

[0053] 6 is a diagram illustrating an example of the configuration of a UE 100 (user equipment) according to the first embodiment. As illustrated in FIG. 6, the UE 100 includes a receiving unit 101, a transmitting unit 102, and a control unit 103. The receiving unit 101 and the transmitting unit 102 configure a wireless communication unit that performs wireless communication with a node 110.

[0054] The receiving unit 101 performs various reception operations under the control of the control unit 103. The receiving unit 101 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 103.

[0055] The transmitting unit 102 performs various transmissions under the control of the control unit 103. The transmitting unit 102 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 103 into a radio signal and transmits it from the antenna.

[0056] The control unit 103 performs various controls and processes in the UE 100. Such processes include processes of each layer described below. The control unit 103 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation, encoding / decoding, etc. of baseband signals. The CPU executes programs stored in the memory to perform various processes. Note that the processes or operations in the UE 100 described below may be performed by the control unit 103. Furthermore, transmission of messages in the UE 100 described below may be performed by the transmitting unit 102, and reception of messages in the UE 100 may be performed by the receiving unit 101.

[0057] Next, an example of the configuration of the node 110 will be described.

[0058] 7 is a diagram showing the configuration of a node 110 (base station) according to the first embodiment. As shown in FIG. 7, the node 110 includes a transmitting unit 111, a receiving unit 112, a control unit 113, and a network communication unit 115. The transmitting unit 111 and the receiving unit 112 constitute a wireless communication unit that performs wireless communication with the UE 100. The network communication unit 115 constitutes a network communication unit that performs communication with the CN device 120.

[0059] The transmitting unit 111 performs various transmissions under the control of the control unit 113. The transmitting unit 111 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 113 into a radio signal and transmits it from the antenna.

[0060] The receiving unit 112 performs various types of reception under the control of the control unit 113. The receiving unit 112 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 113.

[0061] The control unit 113 performs various controls and processes in the node 110. Such processes include processes in each layer described below. The control unit 113 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes. Note that the processes or operations in the node 110 described below may be performed by the control unit 113. Furthermore, message transmission in the node 110 described below may be performed by the transmitter 111 and the network communication unit 115, and message reception in the node 110 may be performed by the receiver 112 and the network communication unit 115.

[0062] The network communication unit 115 is connected to the CN device 120 via an NG interface, which is an interface between a base station and a core network. The network communication unit 115 is also connected to other nodes via an Xn interface. The network communication unit 115 may also perform various processes under the control of the control unit 113.

[0063] Next, an example of the configuration of the CN device 120 will be described.

[0064] 8 is a diagram illustrating an example of the configuration of the CN device 120 according to the first embodiment. As shown in FIG. 8, the CN device 120 includes a receiving unit 121, a transmitting unit 122, and a control unit 123.

[0065] The receiving unit 121 receives various types of messages under the control of the control unit 123. The receiving unit 121 receives messages transmitted from the node 110 (e.g., messages transmitted via the N2 interface). The receiving unit 121 may also receive messages transmitted from other CN devices (e.g., messages transmitted via the N11 interface). The receiving unit 121 outputs the received messages to the control unit 123.

[0066] The transmitting unit 122 performs various transmissions under the control of the control unit 123. In accordance with instructions from the control unit 123, the transmitting unit 122 transmits messages received from the control unit 123 (e.g., messages via the N2 interface) to the node 110. In addition, in accordance with instructions from the control unit 123, the transmitting unit 122 transmits messages received from the control unit 123 (e.g., messages via the N11 interface) to other CN devices.

[0067] The control unit 123 performs various controls and processes in the CN device 120. The control unit 123 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a CPU. The CPU executes programs stored in the memory to perform various processes. Note that the processing or operations in the CN device 120, which will be described later, may be performed by the control unit 123. Furthermore, message transmission in the CN device 120, which will be described later, may be performed by the transmitting unit 122, and message reception in the CN device 120 may be performed by the receiving unit 121.

[0068] Next, an example configuration of the network slice management device (or orchestrator) 130 will be described.

[0069] 9 is a diagram illustrating an example of the configuration of the orchestrator 130. As illustrated in FIG. 9, the orchestrator 130 includes a receiving unit 136, a transmitting unit 137, and a control unit 138.

[0070] The receiving unit 136 performs various types of reception under the control of the control unit 138. For example, the receiving unit 136 receives RAN packet information from the RAN 30, core packet information from the CN 40, and transport packet information from the RAN 30 and the CN 40. The receiving unit 136 outputs the RAN packet information, core packet information, and transport packet information to the control unit 138.

[0071] The transmitting unit 137 performs various transmissions under the control of the control unit 138. For example, the transmitting unit 137 transmits a message or the like to the RAN 30 and / or the CN 40 in accordance with an instruction from the control unit 138.

[0072] The control unit 138 performs various controls and processes in the orchestrator 130. The control unit 138 may be a block that realizes the functions of the RAN slice controller 131, the transport slice controller 132, the core slice controller 133, and the network slice controller 135. The control unit 138 may be divided into four control units 138 to realize the functions of the RAN slice controller 131, the transport slice controller 132, the core slice controller 133, and the network slice controller 135, respectively. The control unit 138 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in processing by the processor. The processor may include a CPU. The CPU executes programs stored in the memory to perform various processes. Note that the processing or operations in the orchestrator 130 described below may be performed by the control unit 138.

[0073] (2) Operation Example According to First Embodiment Next, an operation example according to the first embodiment will be described.

[0074] FIG. 10 is a diagram illustrating an example of operation according to the first embodiment.

[0075] An example of operation according to the first embodiment will be described in the following order.

[0076] (2.1) Collection of communication path information (step S1)

[0077] (2.2) Communication Type Determination (Step S2)

[0078] (2.3) Network slice design (step S3)

[0079] (2.4) Communication Control (Step S4) The operation example shown in FIG. 10 is performed, for example, by the control unit 138 (for example, the network slice controller 135) of the orchestrator 130.

[0080] (2.1) Collection of communication path information (step S1) When an application is executed in the UE 100, a packet related to the application is transmitted from the UE 100. The packet is input to the RAN 30 and the CN 40 of the cellular network 10. At this time, the orchestrator 130 collects communication path information of the packet from the node 110 included in the RAN 30 and / or the CN device 120 included in the CN 40 (step S1).

[0081] First, the communication path information may include packet information indicating the operation of the packet in the cellular network. The packet information may be packet information of one packet transmitted from the UE 100 itself. Alternatively, the packet information may be packet information of multiple packets transmitted from the UE 100 itself. Alternatively, the packet information may be packet information of not only the UE 100 itself but also other UEs 100. The packet information includes, for example, at least one of the following pieces of information:

[0082] (2.1.1.1) Data length of data included in the payload portion of the packet

[0083] (2.1.1.2) Packet Transmission Interval

[0084] (2.1.1.3) The number of UEs 100 (or terminal devices) connected to the cellular network when executing the application, and

[0085] (2.1.1.4) Amount of data accumulated in the transmission queue of the CN device 120 in the cellular network The orchestrator 130 can obtain the actual behavior of the packet in the cellular network 10 from the packet information.

[0086] Second, the communication path information may include network slice configuration information indicating information for configuring a network slice. The network slice configuration information is, for example, configuration information regarding a network slice configured in the cellular network 10 when the UE 100 executes an application. The network slice configuration information is, for example, shown in FIG. 5 . The network slice configuration information is configured in the CN device 120 (e.g., AMF) when the UE 100 performs a registration procedure with the cellular network 10. Regarding the network slice configuration information, the CN device 120 may use the instructed network slice configuration information if instructed by the UE 100. Furthermore, the CN device 120 may use default network slice configuration information if instructed by the UE 100. The network slice configuration information may be generated by the CN device 120 and transmitted from the CN device 120 to the orchestrator 130. Alternatively, the orchestrator 130 may generate network slice configuration information and transmit it to the AMF, and the AMF may select any of the network slice configuration information from the network slice configuration information received from the orchestrator 130 during the registration procedure. If the UE 100 instructs the orchestrator 130 to provide network slice configuration information, the orchestrator 130 may generate the instructed network slice configuration information and transmit it to the CN device 120. Furthermore, if the orchestrator 130 does not instruct the orchestrator 130, the orchestrator 130 may transmit default network slice configuration information to the CN device 120.

[0087] Here, default network slice configuration information will be described. The default network slice configuration information is, for example, predetermined (or preset) network slice configuration information. The CN device 120 or the orchestrator 130 may store the predetermined network slice configuration information in a memory or the like, and read and use it from the memory as needed. Among the network slice configuration information shown in Figures 5(A) and 5(B), for example, the network slice configuration information of network slice #1 may be the default network slice configuration information. Alternatively, network slice #0 may be newly generated and used as the default network slice configuration information. The orchestrator 130 may obtain the default network slice configuration information from the CN device 120, or may obtain it by reading it from its own memory.

[0088] In the cellular network 10, default network slice configuration information may be set before step S1 shown in Fig. 10 is executed. Between the UE 100 and the CN device 120, a default network slice may be set based on the default network slice configuration information before step S1 is executed. Thereafter, in step S3, at the stage where network slice configuration information is generated by network slice design (step S3), the default network slice configuration information may be changed to the generated network slice configuration information.

[0089] Third, the communication path information may include communication control information. The communication control information indicates information for controlling communication of a packet in the cellular network 10. In other words, the communication control information indicates information for controlling communication of the packet in the cellular network 10 when the packet is transmitted in the cellular network 10. The communication control information may include, for example, information about a QoS flow established between the UE 100 and a UPF (an example of the CN device 120). The information about the QoS flow may include a QoS flow identifier (QFI: QoS Flow ID) that distinguishes each QoS flow from other QoS flows, a 5QI (5G QoS Identifier) ​​that indicates the characteristics of each QoS flow, and / or a priority (ARP: Allocation and Retention Priority) of each QoS flow. The information about the QoS flow is set in the SMF (an example of the CN device 120) when the UE 100 establishes a PDU session with the UPF. Information about the QoS flow (communication control information) may be generated by the SMF and transmitted from the SMF to the orchestrator 130. The communication control information may also include, for example, information about radio resources allocated by the node 110 to the UE 100. The information about the radio resources may include, for example, time resources, frequency resources, and / or modulation levels. The information about the radio resources is set in the node 110 when the node 110 performs wireless communication with the UE 100. The information about the radio resources (communication control information) may also be generated by the node 110 and transmitted from the node 110 to the orchestrator 130. Alternatively, the communication control information may include information about computing resources in the node 110. The computing resources may be expressed by the number of CPUs, the number of CPU clocks per unit time, and / or the processing speed of the CPU per unit time. Alternatively, the computing resources may be expressed by the number of memories and / or memory capacity. Alternatively, the communication control information may include information about routing. The information about routing is information related to the selection of a communication path for a packet.Alternatively, the information regarding routing may be information indicating which node among the plurality of nodes 110 a packet is to be transmitted through.

[0090] (2.2) Determining the Communication Type (Step S2) In step S2, the control unit 138 of the orchestrator 130 determines the communication type from the packet information using the communication type determination model.

[0091] FIG. 11 is a diagram illustrating an example of a communication type determination model. As illustrated in FIG. 11 , by using the communication type determination model, when packet information satisfies a "condition," the type indicated by "communication type" can be determined (or identified). The communication type determination model illustrated in FIG. 11 is a rule-based model. For example, if traffic exists that satisfies a condition that the packet size is equal to or greater than a first threshold based on packet information, the communication type of the traffic can be determined to be "eMBB." Furthermore, for example, if traffic exists that satisfies a condition that the packet transmission interval is less than a second threshold based on packet information, the communication type of the traffic can be determined to be "URLLC." The communication type represents, for example, the type of service supported by the network slice. Alternatively, the communication type may represent communication characteristics in the cellular network 10.

[0092] Generally, eMBB is used as a service supporting applications that transmit large amounts of data. For example, eMBB is expected to support services such as high-definition video streaming, virtual reality, or augmented reality. Therefore, the control unit 138 of the orchestrator 130 can determine that a packet is an eMBB if the packet size is equal to or greater than a first threshold based on the packet information. Here, the packet size may represent the amount of data obtained by accumulating the data contained in each packet in consecutive packets.

[0093] Furthermore, URLLC is a packet that is small in size compared to video and the like, and is used in services that require high reliability and low latency while maintaining a certain interval between packets. For example, URLLC is intended for services such as communications with self-driving vehicles and industrial robots. Therefore, the control unit 138 of the orchestrator 130 can determine the packet as URLLC based on the packet information if the transmission interval between packets is less than a second threshold.

[0094] Furthermore, MIoT is used as a service that supports a huge number of IoT devices. For example, MIoT is used in use cases that support sensing technologies such as smart cities and smart agriculture. Therefore, the control unit 138 of the orchestrator 130 can determine the communication type as MIoT based on the packet information when the packet size is less than a third threshold (third threshold<first threshold).

[0095] Furthermore, V2X is used as a service intended for communication with automobiles or communication between automobiles. In V2X, packet reliability may be required. Therefore, the control unit 138 of the orchestrator 130 can determine the communication type as V2X if the packet error rate is less than a fourth threshold based on the packet information.

[0096] The "conditions" shown in FIG. 11 are an example. Other conditions may be used as conditions for identifying the communication type. In particular, depending on the communication type, the required conditions may be common to the communication types or may differ. When the conditions are common to the communication types, one of the multiple communication types may be selected.

[0097] Note that, in FIG. 11 , a rule-based model has been described as an example of the communication type determination model, but the communication type determination model is not limited to this. For example, the communication type determination model may be an AI model with a learning function. For example, the control unit 138 of the orchestrator 130 inputs the "packet information" and "communication type" shown in FIG. 11 into the learning model to generate a trained model. The "packet information" may be expressed by the "conditions" shown in FIG. 11 . Then, the control unit 138 can identify the communication type from the packet information using the trained AI model.

[0098] (2.3) Network Slice Design (Step S3) In step S3, the control unit 138 of the orchestrator 130 identifies network slice configuration information from the communication type and configures the network slice based on the identified network slice configuration information. For example, the network slice configuration information (e.g., FIG. 5A) and the communication type are associated and stored in the memory of the orchestrator 130. The control unit 138 may identify the network slice configuration information for the communication type determined in step S2 by reading from the memory the network slice configuration information associated with the communication type. Then, the transmission unit 137 of the orchestrator 130 may transmit a predetermined message including the identified network slice configuration information to the AMF. The AMF may transmit the network slice configuration information to the UE 100 using a NAS message. Alternatively, the transmission unit 137 of the orchestrator 130 may transmit a predetermined message including the network slice configuration information directly to the UE 100. Alternatively, the transmitting unit 137 of the orchestrator 130 may transmit a predetermined message including the network slice configuration information to the AMF and the UE 100. The UE 100 and the CN device 120 configure the network slice based on the network slice configuration information.

[0099] (2.4) Communication Control (Step S4) In step S4, the control unit 138 of the orchestrator 130 identifies communication control information from the communication type, and performs communication control for the cellular network 10 based on the identified communication control information.

[0100] Regarding the identification of the communication control information, for example, each piece of communication control information may be associated with a communication type and stored in the memory of the orchestrator 130. When 5QI is used as the communication control information, for example, a 5QI value of "3" may be associated with V2X and stored, and a 5QI value of "6" may be associated with eMBB and stored. Then, when "V2X" is identified as the communication type in step S2, the control unit 138 may identify the communication control information by retrieving the communication control information associated with "V2X" (5QI value of "3") from the memory.

[0101] The orchestrator 130 may perform communication control for the cellular network 10 by transmitting the identified communication control information to the CN device 120 and the UE 100. For example, the transmitter 127 of the orchestrator 130 may transmit a predetermined message including the communication control information to the CN device 120 and the UE 100.

[0102] Regarding the communication control information, default communication control information may also be used before step S1 is executed. The UE 100 and the CN device 120 (e.g., UPF) may perform communication control using default communication control information stored in advance in memory. Alternatively, the transmitter 137 of the orchestrator 130 may perform default communication control by transmitting a specific message including the default communication control information to the UE 100 and the CN device 120.

[0103] In this way, the orchestrator 130 according to the first embodiment sets a network slice using packet information and a communication type determination model in steps S1 to S3. Setting the network slice changes the network slice set as the default. This allows, for example, a network slice to be set according to the traffic situation, making it possible to automatically set an optimal network slice. Furthermore, in step S4, communication control is performed according to the communication type, making it possible to perform optimal communication control according to the traffic situation.

[0104] (2.5) Changing the Communication Type Determination Model Here, the following scenario is assumed. That is, the number of network slices set based on the determination by the orchestrator 130 increases (becomes excessive), causing a shortage of network resources. A possible reason for this situation is that the communication types that meet the conditions in FIG. 11 become stable (increase) and no longer match the network resources. Therefore, when the orchestrator 130 according to the first embodiment detects a shortage of network resources, it changes the conditions of the communication type determination model to secure network resources. A specific example will be described below.

[0105] (2.5.1) Modification Example 1 As shown in FIG. 11 , the orchestrator 130 sets a network slice that supports eMBB when the packet size satisfies the condition of being equal to or greater than the first threshold. After that, statistically, the number of times that a network slice that supports eMBB is set increases. This is expected to mean that the number of times that communication with a packet size equal to or greater than the first threshold is performed has become greater than a predetermined number.

[0106] Therefore, when the control unit 138 of the orchestrator 130 detects that resources in the network are running low due to an increase in the number of times that network slices that simultaneously support eMBB are configured, the control unit 138 changes the first threshold to a fifth threshold (first threshold < fifth threshold). That is, the control unit 138 changes the "condition" for the communication type "eMBB" to the fifth threshold, which is higher than the first threshold. Figure 12 shows an example of the communication type determination model after the change.

[0107] As a result, for example, the conditions for determining "eMBB" become stricter than in the case of the first threshold, and the orchestrator 130 can appropriately allocate network slices that support eMBB according to network resources. Also, the orchestrator 130 can allocate resources to network slices for other communication types.

[0108] Modification example 1 shows an example in which, for example, video streaming packets of 4K quality (4K resolution) or higher are supported by network slices using eMBB, but at the same time, due to an increase in the number of network slice settings that support eMBB based on video streaming of 4K quality (4K resolution) or higher, resources in the network become insufficient, and the conditions of the communication type determination model are changed so that only video streaming packets of 8K quality (8K resolution) or higher are supported by network slices using eMBB.

[0109] (2.5.2) Modification Example 2 Modification Example 2 is an example of a case where the number of times that network slices supporting MIOT are simultaneously configured exceeds a predetermined number, causing a shortage of network resources. In such a situation, the orchestrator 130 may be unable to allocate resources to network slices of other communication types.

[0110] Therefore, when the control unit 138 of the orchestrator 130 detects that resources in the network are running short due to an increase in the number of times that network slices that simultaneously support MIOT are set, the control unit 138 changes the "condition" for the communication type "MIOT" to a seventh threshold value that is lower than the third threshold value (third threshold value > seventh threshold value). Figure 12 shows an example of the communication type determination model after the change.

[0111] As a result, for example, the condition for determining "MIoT" becomes "packet size less than the seventh threshold," which is stricter than the condition for the second threshold. Therefore, the orchestrator 130 can appropriately allocate network slices that support MIoT according to network resources. In addition, the orchestrator 130 can allocate resources to network slices for other communication types.

[0112] (2.5.3) Modification Example 3 Modification Example 3 differs from Modification Example 1 and Modification Example 2 in that the orchestrator 130 allocates its own resources to a network slice that supports a specific communication type.

[0113] For example, the orchestrator 130 is attempting to secure resources to be allocated to a network slice that supports eMBB. Therefore, the orchestrator 130 changes the conditions for communication types other than "eMBB" to stricter conditions. For example, the control unit 138 of the orchestrator 130 changes the condition for "URLLC" in the communication type determination model to a sixth threshold that is lower than the second threshold (second threshold > sixth threshold). FIG. 12 shows an example of the communication type determination model after the change. As a result, for example, by making the condition for "URLLC" stricter than before, the orchestrator 130 allocates fewer resources to the network slice that supports URLLC. Therefore, the orchestrator 130 can secure its own resources to be allocated to "eMBB."

[0114] Modifications 1 to 3 have been described above.

[0115] In this way, the control unit 138 of the orchestrator 130 according to the first embodiment changes the communication type determination model for determining the communication type depending on the resource status in the cellular network 10. This makes it possible, for example, for the orchestrator 130 to secure resources to be allocated to a network slice of a specific communication type.

[0116] Note that the change in the communication type determination model may be a change in the conditions for determining the communication type, as described in Modification Examples 1 to 3. Specifically, the change in the communication type determination model may be a change in a threshold included in the conditions of the communication type determination model. Alternatively, the change in the communication type determination model may be a change in a new element to the conditions. For example, in FIG. 11 , the condition for "MIoT" may be changed to "packet size is less than a third threshold, and the number of connections of UE 100 is equal to or greater than an eighth threshold" (a new element, "the number of connections of UE 100 is equal to or greater than an eighth threshold", is added).

[0117] (2.6) New Creation of Communication Type Determination Model Next, an example of operation when an application that has not been executed so far (hereinafter, "new application") is executed in the UE 100 will be described.

[0118] When a new application is executed, if packet information such as packet size matches the conditions included in the communication type determination model, it is expected that packets will be transmitted without any particular problems in the network slice. On the other hand, when a new application is executed, if the packet information does not match the conditions included in the communication type determination model, or if some of the conditions are met but other packet information exists that should be considered, it is expected that resources will be consumed in the network slice in excess of those expected for the communication type once determined.

[0119] Therefore, the control unit 138 of the orchestrator 130 according to the first embodiment generates a new communication type determination model according to the resource status of the cellular network 10. Specifically, the control unit 138 generates a new communication type determination model by adding a new communication type and a condition for determining the communication type for a new application. This allows appropriate resource management according to the situation, even if a new application (a device with a new function) that was not anticipated when the network was initially designed appears.

[0120] For example, assume the following case. That is, assuming that the IoT device is a UE 100, a network slice supporting "MIoT" is assigned between the IoT device and the cellular network 10. The IoT device in this case is, for example, a device that measures traffic volume or rainfall. Generally, the size of packets transmitted from an IoT device is small and the packet transmission interval is longer than a predetermined length. Therefore, a network slice supporting MIoT would normally have a lower load on the cellular network 10 than other network slices. However, IoT devices that measure traffic volume or rainfall, by their nature, transmit packets that are smaller than a predetermined size, but have shorter packet transmission intervals than general IoT devices. As a result, the load on the cellular network 10 increases, and there are cases in which resources for the network slice supporting MIoT also increase.

[0121] In such a case where a new application (device with new functions) that was not anticipated when the network was initially designed appears, the control unit 138 of the orchestrator 130 detects a sudden increase in network resource allocation in communication in which a network slice supporting "MIoT" is set. The control unit 138 then detects from the packet information that the packet interval is less than the second threshold. In such a case, the control unit 138 adds "MIoT+URLLLC" as a communication type to the communication type determination model, and adds the condition "packet size is less than the third threshold and packet transmission interval is less than the second threshold" to the communication type determination model. FIG. 12 shows an example of a communication type determination model to which a new condition and communication type have been added (i.e., a new communication type determination model). A new communication type, "MIoT+URLLLC," and its condition are added to the communication type determination model.

[0122] Then, the control unit 138 generates new network slice configuration information corresponding to the new communication type in the network slice configuration (step S3). In the above example, for example, the control unit 138 may generate new network slice configuration information based on network slice configuration information corresponding to MIOT (e.g., configuration information represented by network slice #1 shown in FIG. 5A) and network slice configuration information corresponding to URLLC (e.g., network slice #2 shown in FIG. 5B). The transmission unit 137 of the orchestrator 130 may transmit a predetermined message including the new network slice configuration information to the CN device 120 and the UE 100. Alternatively, the transmission unit 137 may transmit the predetermined message to the CN device 120, and the CN device 120 (e.g., the AMF) may transmit the predetermined message to the UE 100 using a NAS message.

[0123] For example, "MIoT+URLLC" is a network slice set for traffic whose packet size is less than the third threshold, but it can be an effective communication type when traffic suddenly increases more than before at a certain time.

[0124] Note that "MIoT+URLLC" is just one example, and the communication types that can be added to the communication type determination model are not limited to this, and any new communication type not included in the communication type determination model may be added. For example, "eMBB+URLLC" (conditions that "packet size is equal to or greater than a first threshold and packet transmission interval is less than a second threshold") may be added to the communication type determination model. In this case, it becomes possible to deal with cases where traffic of packets with packet intervals equal to or less than a predetermined threshold suddenly increases.

[0125] [Other Embodiments] The above-described operational flows are not limited to being implemented independently, but can be implemented by combining two or more operational flows. For example, some steps of one operational flow may be added to another operational flow, or some steps of one operational flow may be replaced with some steps of another operational flow. In each flow, it is not necessary to execute all steps, and only some steps may be executed.

[0126] In the above-described embodiments and examples, an example in which the base station is an NR base station (gNB) is described, but the base station may also be an LTE base station (eNB) or a 6G base station.

[0127] Also, the term "network node" or "node" primarily refers to a base station, but may also refer to a device in the core network or part of a base station (CU, DU, or RU).

[0128] A program may be provided that causes a computer to execute each process performed by the UE 100, the node 110, the CN device 120, or the network slice management device 130. The program may be recorded on a computer-readable medium. Using a computer-readable medium, the program can be installed on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM. Furthermore, circuits that execute each process performed by the UE 100, the node 110, the CN device 120, or the network slice management device 130 may be integrated, and at least a portion of the UE 100, the node 110, the CN device 120, or the network slice management device 130 may be configured as a semiconductor integrated circuit (chipset, SoC).

[0129] As used in this disclosure, the terms "based on" and "depending on / in response to" do not mean "based only on" or "depending only on," unless expressly stated otherwise. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "depending only on" and "depending at least in part on." The terms "include," "comprise," and variations thereof do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items. Additionally, the term "or," as used in this disclosure, is not intended to mean an exclusive or. Furthermore, any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used herein 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 therein or that the first element must precede the second element in some way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall include the plural unless the context clearly indicates otherwise.

[0130] Additionally, the functions performed by the UE 100 or the base station 200 (network node) may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes a program stored in a memory.

[0131] In this specification, a circuitry, unit, or means is hardware that is programmed to realize or performs the described functions, which may be any hardware disclosed herein or any hardware known to be programmed to realize or perform the described functions.

[0132] If the hardware is a processor considered to be a type of circuitry, the circuitry, means, or unit is a combination of hardware and software used to configure the hardware and / or processor.

[0133] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes can be made within the scope of the gist. Furthermore, the embodiments, operation examples, and processes can be appropriately combined within the scope of not being inconsistent.

[0134] (Additional Note)

[0135] (Supplementary Note 1) A network slice management device that manages network slices in a cellular network, comprising: a control unit that sets the network slice using packet information indicating the behavior of a packet in the cellular network and a communication type determination model that determines the communication type, and the control unit generates a new communication type determination model depending on the resource status of the cellular network.

[0136] (Supplementary Note 2) The control unit generates the new communication type determination model by adding the communication type and a condition for determining the communication type to the communication type determination model. The network slice management device according to Supplementary Note 1.

[0137] (Supplementary Note 3) The network slice management device according to Supplementary Note 1, wherein the communication type represents a type of service supported by the network slice.

[0138] (Supplementary Note 4) A management method in a network slice management device that manages network slices in a cellular network, comprising: a step of setting the network slice using packet information indicating the behavior of a packet in the cellular network and a communication type determination model that determines the communication type; and a step of generating a new communication type determination model according to the resource status of the cellular network.

[0139] 1: Communication system 10: Cellular network 20: SDN 30: RAN 40: CN 100: UE 102: Transmitter 103: Controller 110: Node 111: Transmitter 113: Controller 120: CN device 121: Receiver 122: Transmitter 123: Controller 130: Network slice management device 131: RAN slice controller 132: Transport slice controller 133: Core slice controller 136: Receiver 137: Transmitter 138: Controller 1380: Model learning unit 1381: Model inference unit

Claims

1. A network slice management device that manages network slices in a cellular network, comprising: a control unit that sets the network slice using packet information that indicates the behavior of a packet in the cellular network and a communication type determination model that determines the communication type, and the control unit generates a new communication type determination model depending on the resource status of the cellular network.

2. The network slice management device of claim 1, wherein the control unit generates the new communication type determination model by adding the communication type and the conditions for determining the communication type to the communication type determination model.

3. The network slice management device of claim 1, wherein the communication type represents the type of service supported by the network slice.

4. A management method in a network slice management device that manages network slices in a cellular network, comprising: a step of setting the network slice using packet information indicating the behavior of a packet in the cellular network and a communication type determination model that determines the communication type; and a step of generating a new communication type determination model according to the resource status of the cellular network.

Images