WO2018173815A1

WO2018173815A1 - Slice allocation method and mobile communication system

Info

Publication number: WO2018173815A1
Application number: PCT/JP2018/009322
Authority: WO
Inventors: 拓也下城; 雅純清水; 曉山田; 滋岩科; マラレディサマ
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2017-03-21
Filing date: 2018-03-09
Publication date: 2018-09-27
Also published as: JP2018157506A

Abstract

This mobile communication system includes: an association information storage unit 15 which stores, in advance, a service type which specifies a service in association with a plurality of pieces of association information in which a slice ID that specifies a slice of an allocation destination of the service is associated with context information that indicates the status of a UE; a status acquisition unit 12 which acquires, from the UE 140, a service type that specifies a service being currently used and the context information that indicates the current status of the UE140; and a connection switching unit 14 which specifies, among the plurality of pieces of association information stored in the association information storage unit 15, association information associated with the service type and including the context information, and switches a bearer of the UE 140 on the slice specified by the slice ID included in the association information.

Description

Slice allocation method and mobile communication system

One aspect of the present invention relates to a method for allocating a slice, which is a virtual network generated on a network infrastructure, and a mobile communication system.

A network system using a conventional virtualization technology is a virtual network that is logically generated on a network infrastructure by virtually separating hardware resources using the virtualization technology disclosed in Non-Patent Document 1. Create a slice. Then, by assigning a service to the slice, it is possible to provide the service using a network of independent slices. Thereby, when a slice is assigned to each service having various requirements, it becomes easy to satisfy the requirements of each service, and the signaling processing and the like can be reduced.

However, if a slice is uniquely assigned to a service, it is difficult to assign an appropriate slice to the service according to the user situation when the situation of the user using the service changes.

An aspect of the present invention has been made in view of the above, and an object of the present invention is to provide a slice assignment method that dynamically changes a slice to be assigned to a service for each user according to a user's situation.

In order to solve the above-described problem, a slice allocation method according to one aspect of the present invention is a slice allocation method executed by a device that allocates a slice that is a virtual network to a service that uses a virtual network generated on a network infrastructure. And correspondence information which is information in which slice identification information for identifying a slice to which the service is assigned and status information which is information indicating the status of the terminal is associated with service identification information for identifying the service. , A correspondence information storage step for storing a plurality of associations in advance, a service acquisition information for identifying service currently used and a current status information indicating a current status of the terminal from a terminal used by the user From the plurality of correspondence information stored in the step and the correspondence information storage step. Connection switching for identifying correspondence information including situation information associated with current situation information and corresponding to current situation information, and switching a communication session of a terminal on a slice identified by slice identification information included in the correspondence information Steps.

Alternatively, a mobile communication system according to another aspect of the present invention is a mobile communication system in which a slice that is a virtual network is assigned to a service that uses a virtual network generated on a network infrastructure, and the service specifying information that specifies the service Corresponding information storage unit that stores in advance a plurality of correspondence information, which is information in which slice specifying information for specifying a slice to which the service is allocated and status information that is information indicating the status of the terminal is associated in advance Stored in the correspondence information storage unit, and a status acquisition unit that acquires service usage identification information for identifying a service currently in use and current status information indicating the current status of the terminal from a terminal used by the user The status that is associated with the service identification information used from the multiple correspondence information and that corresponds to the current status information To identify the corresponding information including information, on the slice identified by the slice specifying information included in the correspondence information includes a connection switching unit that switches the communication session of the terminal, the.

According to the one aspect or the other aspect described above, when information for identifying a service in use and information indicating a current situation are acquired from a terminal, a service currently used is determined based on the information. A slice corresponding to the current situation is selected from the plurality of assigned milling cutters, and the communication session of the terminal is switched to the selected slice. Thereby, the slice allocated to a service can be dynamically changed for every user of a terminal according to the condition of the user. As a result, a service can be smoothly provided to the user of the terminal.

According to the present invention, slices allocated to services can be dynamically changed for each user according to the user's situation.

It is a figure which shows the system configuration | structure of the mobile communication system concerning suitable one Embodiment of this invention. It is a figure which shows the correspondence of a slice and a resource. It is a block diagram which shows an example of the hardware constitutions of AMF100 of FIG. It is a block diagram which shows the function structure of AMF100 of FIG. It is a figure which shows the data structure of the correspondence information memorize | stored in the correspondence information storage part 15 of FIG. It is a sequence diagram which shows the procedure of the switching process of the bearer by the mobile communication system of embodiment. It is a conceptual diagram which shows the image of the switching process of the bearer by the mobile communication system of embodiment. It is a figure which shows the system configuration | structure of the mobile communication system concerning a modification. It is a block diagram which shows the function structure of NSSF150 concerning a modification. It is a sequence diagram which shows the procedure of the switching process of the bearer in a modification.

Embodiments of the present invention will be described with reference to the accompanying drawings. Where possible, the same parts are denoted by the same reference numerals, and redundant description is omitted.

FIG. 1 shows the configuration of a mobile communication system that implements the slice allocation method according to the present embodiment. A mobile communication system is a system that allocates a slice, which is a virtual network, to a service that uses a virtual network generated on a network infrastructure. A slice is a virtual network or service network that is created by logically dividing the network device link and node resources and combining the separated resources, and the slices separate resources. And do not interfere with each other. The service refers to a service using network resources such as a communication service (private line service or the like) or an application service (service using a moving image distribution or sensor device such as an embedded device).

As shown in FIG. 1, the mobile communication system includes an SO (Service Operator) 20, an OSS / BSS (Operations Support System / Business Support System) 30, a slice management device 10, an NFVO 40, a VNFM 50, and a VIM (Virtualized Infrastructure). Management: Virtualization infrastructure management) 60, UDM (Unified Data Management) 70, DNS (Domain Name System) server 80, AUSF (Authentication Server Function) 90, AMF (Core Access and Mobility management Function) 100, RAN 110, SMF (Session Management Function) 120, UPF (User Plane Function) 130, and UE (User Equipment) 140 are comprised. Among these, NFVO40, VNFM50, and VIM60 are MANO (Management & Orchestration) architecture.

These components constitute the core network of the mobile communication system. Note that components that need to transmit and receive information to each other are connected by wire or the like so that information can be transmitted and received.

The mobile communication system according to the present embodiment provides a communication function for a mobile communication terminal by a virtual server operating in a virtual machine realized on a physical server. That is, the mobile communication system is a virtualized mobile communication network. The communication function is provided to the mobile communication terminal by executing a communication process corresponding to the communication function by the virtual machine.

The slice management apparatus 10 is a node that performs service management (association between slices and services) in the mobile communication system and gives instructions related to communication functions in the mobile communication system. Further, the slice management device 10 can be operated by a telecommunications carrier related to the mobile communication system.

The SO (Service Operator) 20 is a service requesting device, for example, a terminal device (for example, a personal computer) of a business provider that provides services to various users using a virtual network.

The OSS / BSS 30 is a device that receives a service request from the SO 20 and transmits information based on the request to the slice management device 10. The OSS / BSS 30 includes a service parameter (service type that is service specifying information) for identifying (specifying) a service that is a target of the service request, and slice specifying information for specifying a slice to which a service indicated by the service parameter is assigned. (Slice ID) and context information are associated with each other, and the associated information is transmitted to the slice management apparatus 10. Here, the context information is information indicating the status of the user's terminal, for example, information indicating the detection status in the service used by the user, information indicating the user's stay status (stay time), and the like. Note that the correspondence information may be received from the SO 20 and the correspondence information may be transmitted to the slice management apparatus 10.

The NFVO 40 is an overall management node (functional entity) that manages the entire virtual network (slice) constructed on the NFVI 160, which is a physical resource. The NFVO 40 receives an instruction from a device that instructs slice generation, and performs processing in accordance with the instruction. The NFVO 40 performs management over the entire virtual network constructed in the physical resources of the mobile communication network of infrastructure and communication services. The NFVO 40 implements a communication service provided by the virtual network at an appropriate location via the VNFM 50 and the VIM 60. For example, service life cycle management (specifically, for example, generation, update, scale control, event collection), resource distribution / reservation / allocation management, service / instance management, and policy management (in the mobile communication network) Specifically, for example, resource reservation / allocation, optimal placement based on geography / laws, etc.) is performed.

The VNFM 50 is a virtual communication function management node (functional entity) that adds a function related to a service to the NFVI 160 serving as a physical resource (node). A plurality of VNFMs 50 may be provided in the system.

The VIM 60 is a physical resource management node (functional entity) that manages each physical resource (node). Specifically, resource allocation / update / recovery management, association between physical resources and virtualized network, and management of hardware resources and SW resources (hypervisor) list are performed. Normally, the VIM 60 performs management for each data center (station building). Management of physical resources is performed by a method according to the data center. Data center management methods (management resource mounting methods) include OPENSTACK and vCenter. Normally, the VIM 60 is provided for each data center management method. That is, a plurality of VIMs 60 that manage each physical resource in the NFVI 160 in different manners are included. Note that the unit of physical resources managed by different management methods is not necessarily a data center unit.

The NFVO 40, the VNFM 50, and the VIM 60 are realized by executing a program on a physical server device (however, they are not limited to being realized on virtualization, and are separated from a management system). And may be realized on virtualization). The NFVO 40, the VNFM 50, and the VIM 60 may be realized by separate physical server devices, or may be realized by the same server device. The NFVO 40, VNFM 50, and VIM 60 (programs for realizing) may be provided from different vendors.

When the NFVO 40 receives the slice generation request, the NFVO 40 makes a resource securing request for the slice (slice SL1, SL2, etc.) to the VIM 60. When the VIM 60 secures resources in the server devices and switches that make up physical resources, the NFVO 40 defines slices for these physical resources.

Further, when the NFVO 40 causes the VIM 60 to secure a resource in the physical resource, the NFVO 40 stores information defining a slice for the physical resource in a table stored in the NFVO 40. Then, the NFVO 40 requests the VNFM 50 to install software for realizing functions required for the service. In response to the installation request, the VNFM 50 installs the software on a physical resource (node such as a server device, a switch device, or a router device) secured by the VIM 60.

When the software is installed by the VNFM 50, the NFVO 40 associates the slice and the service with the table stored in the NFVO 40. The slices SL1 to SL3 are slices that are units for allocating services.

For example, as shown in FIG. 2, when the NFVO 40 makes a resource securing request for the slices (Slice 1 and Slice 2) to the VIM 60, the VIM 60 sends an instruction to that effect to the switch SW1, the switch SW2, the server SV1, and the switch SW3. Do it. Then, the switch SW1, the switch SW2, the server SV1, and the switch SW3 reserve resources for Slice1. Similarly, according to an instruction from the VIM 60, the switch SW1, the switch SW2, the server SV1, and the switch SW4 reserve resources for Slice2.

NFVI 160, which is the above-described physical resource, indicates a network formed from physical resources (node groups) that constitute a virtual environment. The physical resources conceptually include computing resources, storage resources, and transmission resources. Specifically, the physical resource includes nodes such as a physical server and a switch that are physical server devices that perform communication processing in the system. The physical server includes a storage unit such as a CPU (core, processor), a memory, and a hard disk. Normally, a plurality of nodes such as physical servers that constitute the NFVI 160 are arranged together at a base such as a data center (DC). In the data center, the arranged physical servers are connected by a network inside the data center, and can exchange information with each other. The system is provided with a plurality of data centers. Data centers are connected by a network, and physical servers provided in different data centers can transmit / receive information to / from each other via the network.

As described above, when the VNFM 50 adds various functions to the NFVI 160 serving as a physical resource (node), the NFVI 160 realizes the functions of the UDM 70, the DNS server 80, the AUSF 90, the AMF 100, the SMF 120, and the UPF 130. .

The UDM 70 is a function for managing subscriber information including contract information, authentication information, communication service information, terminal type information, and location information of communication terminals such as the UE 140 in a database. Here, the communication service information is information that defines the type of communication service used by each UE 140. The communication service information includes information for identifying the UE 140 (for example, IMSI (International Mobile Subscriber Identity)) and service parameters indicating requirements of the communication service used by the UE 140.

DNS server 80 is a function for managing the correspondence between domain names and host names and IP addresses on the network. Further, the DNS server 80 stores information in which information for identifying a slice (for example, slice ID) is associated with the address of the SMF 120. When the DNS server 80 receives an address transmission request from the AMF 100, the DNS server 80 transmits the address of the SMF 120 corresponding to the request to the AMF 100.

The AUSF 90 and the AMF 100 are communication devices that are connected to communicate with a user terminal (UE 140) located in an LTE (Long Term Evolution) network. The AUSF 90 is a function that performs authentication management of the UE 140. The AMF 100 is a function that performs location management of the UE 140 and processing for setting a communication path for user data between the UPF 130 and the UE 140.

In addition, when the AMF 100 receives a slice switching request including service parameters and context information from the UE 140, the AMF 100 transmits a bearer, which is a communication session set between the UE 140 and the UPF 130 on one slice, on another slice. There is also a function of switching to a bearer (details will be described later).

The RAN 110 is a radio base station connected to the AMF 100 and a device having a radio access control function.

The SMF 120 is a session management function that manages bearers set between the UE 140 and the UPF 130. The UPF 130 is a function of a serving packet switch that accommodates LTE, and transmits / receives user data used for providing communication services to / from the RAN 110. A plurality of UPFs 130 are provided corresponding to the requirements of a plurality of communication services. The UPF 130 is a junction with a PDN (Packet data network), and is a gateway that transfers user data between the RAN 110 and the PDN.

The UE 140 is used by a user and is realized as a device having a communication function such as a mobile phone or a PDA (Personal Digital Assistance). Further, the UE 140 acquires context information such as information indicating a detection status in the service used by the user. For example, the UE 140 is triggered by detecting a change in environmental conditions (intruder detection, temperature detection, fire detection, etc.) in the vicinity of the UE 140 based on an image obtained by an image acquisition device such as a camera. Corresponding context information (eg, “normal”, “emergency”, etc.) is acquired. In addition to the camera, the context information can be acquired using various sensors such as a microphone, a positioning sensor, and an optical sensor. Then, when the UE 140 acquires specific context information (for example, “emergency”), the UE 140 sends a slice switching request for switching the slice assigned to the currently used service via the RAN 110. Send to. This slice switching request includes the service type (used service specifying information) corresponding to the service currently used, and the acquired context information (current status information) indicating the current status of the UE 140. Here, the context information is automatically acquired using the sensor of the UE 140, and the slice switching request may be automatically transmitted in response to the context information, or the context information is acquired according to the input of the user of the UE 140. The slice switching request may be transmitted by a user instruction input.

Hereinafter, the configuration of the AMF 100 will be described in detail. In addition to the functions described below, the AMF 100 also has functions described using a sequence diagram of FIG.

3 shows a hardware configuration of the AMF 100, and FIG. 4 shows a functional configuration of the AMF 100. As shown in FIG. 4, the AMF 100 includes a connection / mobility management function unit 11, a situation acquisition unit 12, a switching determination unit 13, a connection switching unit 14, and a correspondence information storage unit 15 as functional components. Has been.

The block diagram shown in FIG. 4 shows functional unit blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Further, the means for realizing each functional block is not particularly limited. That is, each functional block may be realized by one device physically and / or logically coupled, and two or more devices physically and / or logically separated may be directly and / or indirectly. (For example, wired and / or wireless) and may be realized by these plural devices.

For example, the AMF 100 according to an embodiment of the present invention may function as a computer that performs processing of the AMF 100 according to the present embodiment. FIG. 3 shows an example of the hardware configuration of the AMF 100 according to the present embodiment. The AMF 100 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, and the like.

In the description in this specification, the term “apparatus” can be read as a circuit, a device, a unit, or the like. The hardware configuration of the AMF 100 may be configured to include one or a plurality of devices illustrated in the figure, or may be configured not to include some devices.

Each function in the AMF 100 reads predetermined software (program) on hardware such as the processor 1001 and the memory 1002 so that the processor 1001 performs an operation to perform communication by the communication device 1004 and data in the memory 1002 and the storage 1003. This is realized by controlling reading and / or writing.

The processor 1001 controls the entire computer by operating an operating system, for example. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like. For example, the connection / mobility management function unit 11, the situation acquisition unit 12, the switching determination unit 13, and the connection switching unit 14 may be realized by the processor 1001.

Further, the processor 1001 reads programs (program codes), software modules, and data from the storage 1003 and / or the communication device 1004 to the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, the connection / mobility management function unit 11 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and may be realized similarly for other functional blocks. Although the above-described various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunication line.

The memory 1002 is a computer-readable recording medium, and includes, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), and the like. May be. The memory 1002 may be called a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code), a software module, and the like that can be executed to perform various processes of mobile communication according to an embodiment of the present invention.

The storage 1003 is a computer-readable recording medium such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu-ray). (Registered trademark) disk, smart card, flash memory (for example, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like. The storage 1003 may be referred to as an auxiliary storage device. The storage medium described above may be, for example, a database, server, or other suitable medium including the memory 1002 and / or the storage 1003. For example, the correspondence information storage unit 15 and the like may be realized by the storage 1003.

The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, or the like. For example, the connection / mobility management function unit 11, the situation acquisition unit 12, the connection switching unit 14, and the like may be realized by the communication device 1004.

The input device 1005 is an input device that accepts input from the outside, and the output device 1006 is an output device that performs output to the outside. The input device 1005 and the output device 1006 may be realized by a touch panel display in which both are integrated.

Also, 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 with a single bus or may be configured with different buses between apparatuses.

The AMF 100 includes hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). Alternatively, some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented by at least one of these hardware.

Next, the function of each functional part of the AMF 100 will be described.

The connection / mobility management function unit 11 is a part that performs location management of the UE 140 located in the mobile communication system and setting processing of a communication path of control data or user data between the UPF 130 and the UE 140.

The status acquisition unit 12 receives (acquires) a slice switching request from the UE 140 via the RAN 110 for switching the slice assigned to the service currently in use. At this time, the status acquisition unit 12 receives the slice switching request including the service type that identifies the service currently used by the US 140 and the context information indicating the current status of the UE 140.

When the status acquisition unit 12 receives a slice switching request, the switching determination unit 13 determines whether or not there is a need to switch slices based on the service type and context information included in the slice switching request. That is, the switching determination unit 13 refers to the correspondence information regarding the service management stored in the correspondence information storage unit 15 based on the service type and context information included in the slice switching request, thereby determining whether switching is necessary. Judging.

FIG. 5 shows an example of the data configuration of the correspondence information stored in the correspondence information storage unit 15. This correspondence information is stored in advance by extracting necessary information from the correspondence information stored in the slice management apparatus 10 by the AMF 100. As described above, in the correspondence information, for the service type (for example, “AAA”) for specifying the service, the slice ID (for example, “Slice 1”) for specifying the slice to which the service is allocated, and the status of the terminal Is stored in association with context information (for example, “normal”). This correspondence information indicates that when the terminal status is the status indicated by the context information, the terminal should be controlled to use the slice indicated by the slice ID when using the service indicated by the service type. Show. Here, in the correspondence information, for the same service type (for example, “AAA”), a plurality of combinations (for example, “Slice 1”, “Normal”, and “Slice 2” including different slice IDs and different context information) “Abnormal”) is associated. Accordingly, different slices are allocated when the same service is used when the terminals are in different situations.

Specifically, the switching determination unit 13 is associated with a service type included in the slice switching request and includes correspondence information including context information included in the slice switching request. The slice ID included in the correspondence information is extracted from the information. For example, when the service type “AAA” and the context information “emergency” are included in the slice switching request, the slice ID “Slice2” is extracted from the plurality of correspondence information shown in FIG. Then, when the slice ID extraction is successful, the switching determination unit 13 determines that the slice needs to be switched, and sends a slice switching request to the connection switching unit 14 with the slice indicated by the slice ID as the switching destination. Output.

The connection switching unit 14 receives a slice switching request from the switching determination unit 13 and switches a slice in which a communication session (bearer) between the UE 140 and the UPF 130 is set. That is, the connection switching unit 14 sets the bearer for the service currently used by the UE 140 on the slice specified by the slice ID extracted by the switching determination unit 13 from the slice currently allocated to the service. Switch. Specifically, when the slice switching request is received, the connection switching unit 14 obtains the address of the SMF 120 corresponding to the slice ID that specifies the slice to be switched from the DNS server 80, and sends a new bearer to the SMF 120 of that address. Send a request to establish As a result, a bearer on the slice specified by the slice ID is newly established between the UE 140 and the UPF 130. Further, the connection switching unit 14 acquires the address of the SMF 120 to which the switching source slice is assigned from the DNS server 80, and sends an existing bearer disconnection request for requesting disconnection of the bearer set on the switching source slice, Transmit to the corresponding SMF 120. As a result, the existing bearer on the switching source slice between the UE 140 and the UPF 130 is disconnected, and the bearer switching is completed.

Next, the procedure of the bearer switching process of the mobile communication system described above will be described, and the slice allocation method according to the present embodiment will be described in detail. FIG. 6 is a sequence diagram showing a procedure of bearer switching processing by the mobile communication system, and FIG. 7 is a conceptual diagram showing an image of bearer switching processing by the mobile communication system.

First, the bearer switching process will be described with reference to FIG. First, context information is acquired in the UE 140 in a state where a service bearer between the UE 140 and the UPF 130 is connected (step S01). Upon acquisition of the context information, a slice switching request is transmitted from the UE 140 to the AMF 100 (step S02).

Next, when the slice acquisition request is received by the status acquisition unit 12 of the AMF 100 (step S02), the following determination process for determining the necessity of switching and the bearer switching process are executed. That is, the service used by the UE 140 and the UE 140 out of the correspondence information stored in the correspondence information storage unit 15 based on the service type and context information included in the slice switching request by the switching judgment unit 13 of the AMF 100. By identifying the correspondence information corresponding to the situation, it is determined whether or not switching is necessary (step S03). As a result, if it is determined that there is a need for switching, the SMF 120 and the UPF 130 (hereinafter referred to as the switching destination slices) to which the switching destination slices identified by the slice ID included in the correspondence information are assigned from the connection switching unit 14 of the AMF 100 The new bearer establishment request (Create session request) is transmitted to “switched destination SMF or UPF” (step S04). As a result, after the bearer connection processing is performed in the switching destination SMF 120 and the switching destination UPF 130, a new bearer establishment response (Create session response) is returned to the AMF 100 (step S05). After that, a bearer change request (Barer modify request) between the UE 140 and the UPF 130 is transmitted from the AMF 100 to the RAN 110, and a response (Barer modify response) is returned to the AMF 100 after the bearer change process is executed in the RAN 110 (step S06).

Further, from the connection switching unit 14 of the AMF 100, an existing bearer disconnection request (Delete session) is sent to the SMF 120 and the UPF 130 (hereinafter simply referred to as “switching source SMF or UPF”) to which the switching source slice is assigned. request) is transmitted (step S07). As a result, the bearer disconnection process is performed in the switching source SMF 120 and the switching source UPF 130, and then the existing bearer disconnection response (Delete session response) is returned to the AMF 100 (step S08).

By the switching control process by the AMF 100 as described above, the service bearer used by the UE 140 is switched from the switching source slice to the switching destination slice. That is, as shown in FIG. 7, with the slice switching request transmitted from the UE 140, the slice allocated to the service being used by the UE 140 is the slice switching request from the slice “Slice 1” allocated until immediately before. Is switched to the slice “Slice 2” corresponding to the situation indicated by the context information included in.

Next, operational effects of the mobile communication system and the slice allocation method according to the present embodiment will be described. According to the mobile communication system described above, when information identifying the service in use and information indicating the current situation are acquired from the UE 140, the information assigned to the service currently used is allocated based on the information. A slice corresponding to the current situation is selected from the plurality of milling machines, and the bearer between the UE 140 and the UPF 130 is switched on the selected slice. Thereby, the slice allocated to a service can be dynamically changed for every user of UE according to the condition of the user. As a result, a service can be smoothly provided to the user of the UE.

In the above embodiment, a bearer between the UE 140 and the UPF 130 is set on the slice specified by the slice ID included in the specified correspondence information, and the bearer set on the slice other than the slice is disconnected. . By doing so, the service allocation can be switched from one slice to another according to the situation for each user of the UE, and the slice can be efficiently allocated between the UE users.

Furthermore, in the above-described embodiment, when the slice switching request is acquired from the UE 140, identification of correspondence information and switching of bearers between the UE 140 and the UPF 130 are executed. By doing so, the slice assignment can be quickly changed according to the situation of the user of the UE.

As mentioned above, although this embodiment was described in detail, it is clear for those skilled in the art that this embodiment is not limited to embodiment described in this specification. The present embodiment can be implemented as a modification and change without departing from the spirit and scope of the present invention defined by the description of the scope of claims. Therefore, the description of the present specification is for illustrative purposes and does not have any limiting meaning to the present embodiment.

For example, in the above embodiment, the AMF 100 receives a slice switching request from the UE 140, determines whether or not there is a need to switch slices, and executes bearer switching control based on the determination result. Other than the above, it may be determined whether or not slice switching is necessary, or bearer switching control may be performed. In the following, a configuration will be described in which an NSSF (NW Slice Selection Function) 150, which is a node different from the AMF 100, has a function for determining whether or not a slice needs to be switched and a bearer switching control function. FIG. 8 is a diagram showing a system configuration according to a modification of the mobile communication system of the above-described embodiment, and FIG. 9 is a block diagram showing a functional configuration of the NSSF 150 in FIG.

The NSSF 150 illustrated in FIG. 8 is a node that performs a function of determining whether or not to switch a slice and a bearer switching control function among the functional units included in the AMF 100 according to the above-described embodiment. As illustrated in FIG. The functional component includes a status acquisition unit 22, a switching determination unit 23, a connection switching request unit 24, and a correspondence information storage unit 25. The functions of the situation acquisition unit 22, the switching determination unit 23, and the correspondence information storage unit 25 are the same as the functions of the situation acquisition unit 12, the switching determination unit 13, and the correspondence information storage unit 15 of the AMF 100 described above. The connection switching request unit 24 receives the slice switching request from the switching determination unit 23 and transfers the slice switching request to the AMF 100. On the other hand, the AMF 100 transmits a request for establishing a new bearer and a request for disconnecting an existing bearer to the corresponding SMF 120 in the same manner as the connection switching unit 14 described above.

The block diagram shown in FIG. 9 shows functional unit blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Further, the means for realizing each functional block is not particularly limited. That is, each functional block may be realized by one device physically and / or logically coupled, and two or more devices physically and / or logically separated may be directly and / or indirectly. (For example, wired and / or wireless) and may be realized by these plural devices.

For example, the NSSF 150 in the present modification may function as a computer that performs the processing of the NSSF 150 in the present modification. A computer that performs processing of the NSSF 150 can employ a hardware configuration similar to the configuration of FIG.

Next, the procedure of the bearer switching process of the mobile communication system in the above-described modification will be described, and the slice allocation method according to the modification will be described in detail. FIG. 10 is a sequence diagram showing a procedure of bearer switching processing by the mobile communication system according to the present modification.

First, context information is acquired in the UE 140 in a state where a service bearer between the UE 140 and the UPF 130 is connected (step S101). In response to the acquisition of the context information, a slice switching request is transmitted from the UE 140 to the NSSF 150 via the AMF 100 (step S102).

Next, when the slice acquisition request is received by the status acquisition unit 22 of the NSSF 150 (step S102), the following determination process for determining the necessity of switching and the bearer switching process are executed. That is, the service used by the UE 140 and the UE 140 out of the correspondence information stored in the correspondence information storage unit 25 based on the service type and context information included in the slice switching request by the switching judgment unit 23 of the NSSF 150. By identifying the correspondence information corresponding to the situation, it is determined whether or not switching is necessary (step S103). As a result, if it is determined that the necessity of switching is “present”, a slice switching request is transmitted from the connection switching request unit 24 of the NSSF 150 to the AMF 100 (step S104). In response to this, a request for establishing a new bearer (Create session request) is transmitted from the AMF 100 to the SMF 120 and the UPF 130 of the switching destination (step S105). Thus, after bearer connection processing is performed in the switching destination SMF 120 and the switching destination UPF 130, a new bearer establishment response (Create session response) is returned to the AMF 100 (step S 106). After that, a bearer change request (Barer modify request) between the UE 140 and the UPF 130 is transmitted from the AMF 100 to the RAN 110, and a response (Barer modify response) is returned to the AMF 100 after the bearer change process is executed in the RAN 110 (step S107).

Further, an existing bearer disconnect request (Delete session request) is transmitted from the AMF 100 to the switching source SMF 120 and UPF 130 (step S108). As a result, the bearer disconnection process is performed in the switching source SMF 120 and the switching source UPF 130, and then the existing bearer disconnection response (Delete session response) is returned to the AMF 100 (step S109).

By such switching control processing by the NSSF 150, the service bearer used by the UE 140 is switched from the switching source slice to the switching destination slice. Also by the mobile communication system according to the above-described modification, the slice allocated to the service can be dynamically changed for each user of the UE according to the situation of the user. As a result, a service can be smoothly provided to the user of the UE.

The notification of information is not limited to the aspect / embodiment described in this specification, and may be performed by other methods. For example, notification of information includes physical layer signaling (for example, DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Further, the RRC signaling may be called an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (RRC ConnectionReconfiguration) message, or the like.

Each aspect / embodiment described in this specification includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA. (Registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-WideBand), The present invention may be applied to a Bluetooth (registered trademark), a system using another appropriate system, and / or a next generation system extended based on the system.

The processing procedures, sequences, flowcharts and the like of each aspect / embodiment described in this specification may be switched in order as long as there is no contradiction. For example, the methods described herein present the elements of the various steps in an exemplary order and are not limited to the specific order presented.

Information etc. can be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input / output may be performed via a plurality of network nodes.

The input / output information or the like may be stored in a specific location (for example, a memory) or may be managed by a management table. Input / output information and the like can be overwritten, updated, or additionally written. The output information or the like may be deleted. The input information or the like may be transmitted to another device.

The determination may be performed by a value represented by 1 bit (0 or 1), may be performed by a true / false value (Boolean: true or false), or may be performed by comparing numerical values (for example, a predetermined value) Comparison with the value).

Each aspect / embodiment described in this specification may be used alone, in combination, or may be switched according to execution. In addition, notification of predetermined information (for example, notification of being “X”) is not limited to explicitly performed, but is performed implicitly (for example, notification of the predetermined information is not performed). Also good.

Software, whether it is called software, firmware, middleware, microcode, hardware description language, or other names, instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. should be interpreted broadly.

Further, software, instructions, etc. may be transmitted / received via a transmission medium. For example, software may use websites, servers, or other devices using wired technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or wireless technology such as infrared, wireless and microwave. When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission media.

The information, signals, etc. described herein may be represented using any of a variety of different technologies. For example, data, commands, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these May be represented by a combination of

Note that the terms described in this specification and / or terms necessary for understanding this specification may be replaced with terms having the same or similar meaning.

In addition, information, parameters, and the like described in this specification may be represented by absolute values, may be represented by relative values from a predetermined value, or may be represented by other corresponding information. . For example, the radio resource may be indicated by an index.

The names used for the above parameters are not limited in any way.

As used herein, the terms “determining” and “determining” may encompass a wide variety of actions. “Judgment”, “decision” can be, for example, calculating, computing, processing, deriving, investigating, looking up (eg, table, database or another (Searching in the data structure), and confirming (ascertaining) what has been confirmed may be considered as “determining” or “deciding”. In addition, “determination” and “determination” include receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (accessing) (e.g., accessing data in a memory) may be considered as "determined" or "determined". In addition, “determination” and “decision” means that “resolving”, “selecting”, “choosing”, “establishing”, and “comparing” are regarded as “determining” and “deciding”. May be included. In other words, “determination” and “determination” may include considering some operation as “determination” and “determination”.

The terms “connected”, “coupled”, or any variation thereof, means any direct or indirect connection or coupling between two or more elements and It can include the presence of one or more intermediate elements between two “connected” or “coupled” elements. The coupling or connection between the elements may be physical, logical, or a combination thereof. As used herein, the two elements are radio frequency by using one or more wires, cables and / or printed electrical connections, and as some non-limiting and non-inclusive examples By using electromagnetic energy, such as electromagnetic energy having a wavelength in the region, microwave region, and light (both visible and invisible) region, it can be considered to be “connected” or “coupled” to each other.

As used herein, the phrase “based on” does not mean “based only on”, unless expressly specified otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”

As long as “include”, “comprising”, and variations thereof, are used in the specification or claims, these terms are similar to the term “comprising”. It is intended to be comprehensive. Furthermore, the term “or” as used herein or in the claims is not intended to be an exclusive OR.

In this specification, unless there is only one device that is clearly present in context or technically, a plurality of devices are also included.

In the whole of the present disclosure, a plural is included unless it is clearly indicated by a context.

One embodiment of the present invention uses a method and a mobile communication system for assigning slices, which are virtual networks generated on a network infrastructure, and dynamically changes slices assigned to services for each user according to the user's situation. Is possible.

DESCRIPTION OF SYMBOLS 100 ... AMF, 11 ... Connection / mobility management function part, 12 ... Situation acquisition part, 13 ... Switching judgment part, 14 ... Connection switching part, 15 ... Corresponding information storage part, 150 ... NSSF, 22 ... Situation acquisition part, 23 ... Switching judgment unit, 24... Connection switching request unit (connection switching unit), 25... Correspondence information storage unit, SL 1 to SL 3.

Claims

A slice allocation method executed by an apparatus that allocates a slice that is a virtual network to a service that uses a virtual network generated on a network infrastructure,
A plurality of correspondence information that is information in which slice identification information for identifying a slice to which the service is assigned and status information that is information indicating the status of the terminal is associated with the service identification information for identifying the service in advance. A correspondence information storing step for storing the information in association;
A status acquisition step of acquiring from the terminal used by the user service usage information identifying service currently in use and current status information indicating the current status of the terminal;
Among the plurality of pieces of correspondence information stored in the correspondence information storage step, the correspondence information that is associated with the use service identification information and includes the situation information corresponding to the current situation information is identified and included in the correspondence information. A connection switching step of switching the communication session of the terminal on the slice specified by the slice specifying information,
Slice allocation method including
In the connection switching step, the communication session of the terminal is set on a slice specified by the slice specifying information included in the specified correspondence information, and the service is set on a slice other than the slice Disconnect the communication session of
The slice allocation method according to claim 1.
In the connection switching step, when the device acquires the current status information from the terminal in the status acquisition step, the correspondence information is specified and the communication session of the terminal is switched.
The slice allocation method according to claim 1 or 2.
A mobile communication system that allocates a slice that is a virtual network to a service that uses a virtual network generated on a network infrastructure,
A plurality of correspondence information that is information in which slice identification information for identifying a slice to which the service is assigned and status information that is information indicating the status of the terminal is associated with the service identification information for identifying the service in advance. A correspondence information storage unit for storing the information in association with each other;
A status acquisition unit that acquires service usage identification information for identifying a service currently in use from a terminal used by a user, and current status information indicating the current status of the terminal;
Among the plurality of pieces of correspondence information stored in the correspondence information storage unit, the correspondence information that is associated with the use service identification information and includes the situation information corresponding to the current situation information is identified and included in the correspondence information A connection switching unit that switches a communication session of the terminal on the slice specified by the slice specifying information,
A mobile communication system.