JP2018170681A - Communication control method and communication terminal - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a communication terminal functioning as an access point for a slave terminal to appropriately establish a communication connection between the slave terminal and a slice.SOLUTION: A user terminal 100 that functions as an access point for a terminal, and establishes a communication connection between the slave terminal and a slice that is a virtualized network generated on a network infrastructure, stores slave terminal management information associating identification information of a slave terminal 110 and identification information (slice ID) of a slice as a communication connection destination thereof on the basis of connection slice information. A communication control unit 101 performs processing of communication between the slave terminal 110 and the slice as the communication connection destination thereof on the basis of the slave terminal management information stored in a slave terminal management table 102.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a communication control method for communication connection with a slice, which is a virtual network, and a communication terminal thereof.

  In a network system using conventional virtualization technology, a virtual network logically generated on a network infrastructure by using a virtualization technology disclosed in Non-Patent Document 1 to virtually separate hardware resources. Create a slice. And based on allocating a service to the said slice, a service can be provided with respect to the user terminal which a user uses using the network of each independent slice. With this process, when a slice is assigned to each service having various request conditions, it becomes easy to satisfy the request condition of each service, and the signaling process and the like can be reduced. In addition, when using a service assigned to each slice by a user terminal, user data is transmitted and received through the communication path by providing a communication path related to the user terminal to a control node provided in the slice. Is done.

Akihiro Nakao, “Virtualization Node Project, Virtualization Technology Aiming for New Generation Network”, [online], June 2010, National Institute of Information and Communications Technology, [March 10, 2017 search], Internet <http : //www.nict.go.jp/publication/NICT-News/1006/01.html>

  By the way, a wireless terminal is considered as a user terminal that is connected to communicate with the slice. It is conceivable to make the child terminal accessible by wireless communication by so-called tethering to the wireless terminal.

  When a wireless terminal functions as an access point like tethering, it is considered that the wireless terminal is in communication connection with a plurality of slices. At that time, the wireless terminal cannot determine which slice is connected to the child terminal.

  In view of the above, an object of the present invention is to provide a communication control method and a communication terminal capable of communication-connecting a child terminal and a slice by a communication terminal functioning as an access point to the child terminal.

In order to solve the above-described problem, a communication control method of the present invention functions as an access point for a child terminal, and communicates the child terminal with a slice that is a virtualized network generated on a network infrastructure. In the terminal communication control method, based on connection slice information transmitted from the child terminal for determining a slice to be a communication connection destination, identification information of the child terminal and identification information of a slice to be a communication connection destination Based on the storage step of storing the child terminal management information associated with the child terminal management information in the child terminal management unit and the child terminal management information stored in the child terminal management unit, the communication processing between the child terminal and the slice is performed. And a communication step.
According to this invention, the communication terminal can connect the child terminal and the slice by communication according to the connection slice information that the child terminal intends to communicate with. Therefore, the child terminal can receive service provision using the selected slice.

  According to the present invention, a slice selected by a child terminal and the child terminal can be connected for communication.

It is a figure which shows the structure of the system which comprises the virtualized network. It is a figure which shows the system configuration | structure of a communication system. It is a block diagram which shows the function structure of the user terminal 100 and AMF200 (or NSSF210). It is a figure which shows the specific example of a subunit | mobile_unit terminal table and a slice management part. It is a figure which shows the processing sequence of the child terminal 110 of this embodiment, the user terminal 100, AMF200, and NSSF210. It is a figure which shows the process sequence of the child terminal 110 in the modification, the user terminal 100, and AMF200. It is a block diagram which shows the function structure of the user terminal 100 in the further modification. It is a figure which shows the process sequence of the child terminal 110 and the user terminal 100 in the modification. It is a figure which shows the hardware constitutions of the user terminal.

  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 system 1 that configures a virtualized network. The system 1 in FIG. 1 assigns a service to a slice that is a virtual network, thereby providing a network service to a UE (User Equipment) 90 that is a terminal (user terminal) used by a service user (Service User). provide. 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. They are separated and do not interfere with each other. The network 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 sensor device such as moving image distribution or an embedded device). Moreover, UE90 is a terminal device which has communication functions, such as a smart phone, for example.

  As shown in FIG. 1, the system 1 includes a BSS / OSS (Business Support System / Operations Support System) 10, an SO (Service Operator) 20, an NFVO 30, a VNFM 40, and a VIM (Virtualized Infrastructure Management) 50. It is configured to include. In addition, the system 1 includes an NFVI (NFV (Network Functions Virtualization) Infrastructure) 60, an eNB (eNodeB) 80, and a UE 90. Among these, NFVO30, VNFM40, and VIM50 are functions of MANO (Management & Orchestration) architecture specified by ETSI NFV-ISG.

  These components constitute a core network in the system 1. Note that the components that need to transmit and receive information to each other are connected by wire and can transmit and receive information.

  The system 1 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 system 1 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 NFVI 60 indicates a network formed from physical resources (node groups) constituting a virtual environment. The physical resources conceptually include computing resources, storage resources, and transmission resources. Specifically, the physical resource includes a node such as a physical server or a switch that is a physical server device that performs communication processing in the system 1. 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 60 are arranged together at a base such as a data center (DC). In the data center, the arranged physical servers can communicate with each other via a network inside the data center, and can exchange information with each other. Further, the system 1 is provided with a plurality of data centers. Data centers can communicate with each other via a network, and physical servers provided in different data centers can transmit / receive information to / from each other via the network.

  An SO (Service Operator) 20 is a device that requests creation of a network for providing a network service. For example, a terminal device (for example, a personal computer) of a business operator that provides a service to various users using a virtual network. ).

  The BSS / OSS 10 is a node that performs service management in the system 1 and gives instructions related to communication functions in the system 1. For example, the BSS / OSS 10 instructs the NFVO 30 to add a new network service. In addition, the BSS / OSS 10 can be operated by a telecommunications carrier related to the system 1.

  The NFVO 30 is an overall management node (functional entity) that manages the entire virtual network (slice) constructed on the NFVI 60 that is a physical resource. The NFVO 30 receives an instruction from the BSS / OSS 10 and performs processing according to the instruction. The NFVO 30 performs management over the entire virtual network constructed in the physical resources of the mobile communication network of infrastructure and network services. The NFVO 30 realizes the network service provided by the virtual network in an appropriate place in cooperation with the VNFM 40 and the VIM 50. For example, network service life cycle management (specifically, for example, network service creation, update, scale control, event collection), resource management over the entire mobile communication network, that is, resource distribution / reservation / allocation management, service -Perform instance management and policy management related to resource allocation (specifically, resource reservation / allocation, optimal allocation based on geography / laws, etc.).

  The VNFM 40 is a virtual communication function management node (functional entity) that adds a function that constitutes a network service to the NFVI 60 that is a physical resource (node). A plurality of VNFMs 40 may be provided in the system 1.

  The VIM 50 is a physical resource management node (functional entity) that manages each physical resource (node) in the NFVI 60. 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 50 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 50 is provided for each data center management method. That is, a plurality of VIMs 50 that manage each physical resource in the NFVI 60 are included in different ways. Note that the unit of physical resources managed by different management methods is not necessarily a data center unit.

  The NFVO 30, VNFM 40, and VIM 50 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 30, the VNFM 40, and the VIM 50 may be realized in separate physical server devices, or may be realized in the same server device. The NFVO 30, VNFM 40, and VIM 50 (programs for realizing) may be provided from different vendors.

  When receiving the network service creation request from the BSS / OSS 10, the NFVO 30 makes a resource securing request for the slice (slice SL1, SL2, etc.) to the VIM 50. When the VIM 50 secures resources in the server devices and switches configuring the NFVI 60, the NFVO 30 defines a slice for the NFVI 60.

  Further, when the NFVO 30 causes the VIM 50 to secure resources in the NFVI 60, the NFVO 30 stores information defining slices for the NFVI 60 in a table stored in the NFVO 30. Then, the NFVO 30 makes a software installation request for realizing the functions necessary for the network service to the VNFM 40. In response to the installation request, the VNFM 40 installs the software on the NFVI 60 (node such as a server device, a switch device, or a router device) secured by the VIM 50.

  When software is installed according to the VNFM 40, the NFVO 30 associates slices with network services in the table stored in the NFVO 30.

  FIG. 2 is a diagram illustrating a system configuration of the communication system N1 according to the present embodiment. As shown in FIG. 2, the communication system N1 is a system constructed on the NFVI 60 shown in FIG. 1, and includes an AMF (core access and mobility management function) 200, an NSSF (Network Slice Selection Function) 210, and a RAN (Regional). Area Network (150), SMF (Session Management Function) 160, 160a, UP (User Plane node) 170, 170a, DN (Data Network) 180, 180a. The user terminal 100 is configured to be communicably connected via the RAN 150 to the communication system N1.

  The user terminal 100 functions as a relay device for the child terminal 110 by a so-called tethering function, and can be connected to the communication system N1 in response to an access request from the child terminal 110. This user terminal 100 can be connected to DN 180 and 180a which are external sites via slices SL1 and SL2.

  The child terminal 110 can be connected to the DNs 180 and 180a via the user terminal 100 and the slices SL1 and SL2.

  The RAN 150 is an access network including a base station (eNB) for communication connection with the user terminal 100 by wireless communication.

  The UP 170 and UP 170 a are communication nodes that constitute a slice and transmit / receive user data to / from the user terminal 100.

  The SMFs 160 and 160a constitute a slice together with the UPs 170 and 170a, and are communication control servers that perform communication control on the UPs 170 and 170a.

  In the present embodiment, the SMF 160 and the UP 170 constitute the same slice SL1, and the SMF 160a and the UP 170a constitute the same slice SL2. Therefore, the user terminal 100 or the child terminal 110 can be connected to the slice SL1 or SL2 via the RAN 150.

  The AMF 200 is a slice connection server that performs communication connection control between the slice and the user terminal 100.

  NSSF 210 is a part that determines one corresponding slice based on the service indicated by the service type transmitted from user terminal 100 or child terminal 110 and notifies AMF 200 of identification information that identifies the one slice. is there. The function of NSSF 210 may be built in AMF 200.

  In such a communication system, the user terminal 100 determines a service according to a user operation, and transmits a service type to the AMF 200 via the RAN 150.

  Upon receiving the service type, the AMF 200 determines one slice corresponding to the service in the NSSF 210 or the own device, and returns the identification information of the one slice to the user terminal 100.

  The user terminal 100 stores the returned identification information of the slice, and thereafter connects to the slice according to the identification information of the slice.

  The child terminal 110 communicates and connects with the user terminal 100 as an access point, and communicates with each slice via the user terminal 100.

  Next, a functional configuration of the user terminal 100 according to the present embodiment will be described. FIG. 3 is a block diagram illustrating functional configurations of the user terminal 100 and the NSSF 210.

  As shown in FIG. 3, the user terminal 100 includes a communication control unit 101 and a child terminal management table 102 (child terminal management unit). The communication control unit 101 is a part that performs communication connection control for the communication system N1 that constitutes a slice, and performs communication connection by switching a slice associated with each service to be provided.

  The child terminal management table 102 stores child terminal management information in which identification information of the child terminal 110, a service type requested from the child terminal 110, and identification information for specifying a slice to which the child terminal 110 is connected to communicate are associated. To do.

  FIG. 4B is a specific example of the child terminal management information stored in the child terminal management table 102. As shown in the figure, the child terminal management table 102 stores identification information (ID), service type (ServiceParameter), and connection slice (slice ID) of the child terminal 110 in association with each other.

  The user terminal 100 including such a configuration performs authentication processing with the child terminal 110 and processing for slice determination according to the service type, and performs processing for a slice corresponding to the service requested by the child terminal 110. Communication connection is possible. Further, the user terminal 100 can relay the data transmitted to the child terminal 110 via the slice with reference to the child terminal management table 102 to the child terminal 110 corresponding to the connected slice.

  The NSSF 210 includes a slice connection determination unit 201 and a slice management unit 202.

  When the slice connection determination unit 201 receives a service type from the user terminal 100 via the AMF 200, the slice connection determination unit 201 refers to the slice management unit 202 and determines one slice from slices that the user terminal 100 is currently in the communication connection state. This is a part that returns identification information for identifying the slice to the user terminal 100.

  The slice management unit 202 is a part that stores slice management information in which service types and slices are associated with each other. The service type in the present embodiment indicates a broadband service that requires high-speed and large-capacity communication such as video distribution, a low-delay service that requires high-speed communication such as VoIP, an IoT service that allows delay such as transmission of sensor data, and the like. .

  FIG. 4A is a diagram showing slice management information stored in the slice management unit 202. As shown in the figure, a service type (ServiceParameter) and a connection slice are associated with each other. This is information set in advance by MANO.

  Furthermore, in the present embodiment, the slice management unit 202 manages the slice that the user terminal 100 is in the communication connection state for each user terminal 100.

  The slice connection determination unit 201 determines a slice according to the service type from the slices in the communication connection state, and notifies the user terminal 100 of identification information for specifying the slice.

  Next, operations of the user terminal 100, the AMF 200, and the NSSF 210 configured as described above will be described. FIG. 5 is a diagram illustrating a processing sequence of the child terminal 110, the user terminal 100, the AMF 200, and the NSSF 210.

  The user terminal 100 is in communication with the slice SL1 (FIG. 5 PDU1) and the slice SL2 (FIG. 5 PDU2) in advance. The NSSF 210 manages the communication connection state, and stores slice management information in which a preset service type and slice identification information are associated with each other.

  The child terminal 110 performs an authentication process according to a user operation. First, the child terminal 110 transmits an authentication request (Authentication request) to the user terminal 100 (S101).

  Upon receiving the authentication request, the user terminal 100 transmits a user name request (IdentityRequest) to the child terminal 110 (S102), and the child terminal 110 performs a user operation or automatically inputs a user name (S103).

  The user terminal 100 transmits a password input request (Authenticationchallenge) to the child terminal 110 (S104), and the child terminal 110 performs a user operation or automatically inputs a password (S105).

  The user terminal 100 transmits a request for authentication slice approval and connection slice information to the child terminal 110 (S106). Here, the connection slice information assumes a service type, but is not limited to this, and may be information for specifying a slice to be connected. Accordingly, a slice ID that identifies a slice may be requested. Further, the connection slice information may be information included in NSSI (Network Slice Selection Information) defined in NGN (Next Generation Network Architecture) or NS SAI (Network Slice Selection Assistant Information) which is a subdivided information type. .

  The child terminal 110 transmits the connection slice information to the user terminal 100 according to a user operation or an activated application.

  When receiving the connection slice information from the child terminal 110, the user terminal 100 transmits the connection slice information to the AMF 200 via the RAN 150 (S108).

  The AMF 200 further transmits the connection slice information to the NSSF 210 (S109).

  In the NSSF 210, the slice connection determination unit 201 determines one slice to be connected based on the connection slice information transmitted from the AMF 200 (S110). The NSSF 210 includes slice management information in which connection slice information (for example, service type) is associated with slice identification information, and manages slices SL1 and SL2 in which the user terminal 100 is in a communication connection state. Then, the slice connection determination unit 201 determines either the slice SL1 or SL2 in the communication connection state based on the received connection slice information. In the present embodiment, the slice connection determination unit 201 determines the slice SL2.

  The NSSF 210 transmits to the AMF 200 identification information for identifying the determined one slice together with the slice connection permission (S111), and the AMF 200 further transmits the identification information for identifying the slice along with the slice connection permission to the user terminal via the RAN 150. 100 (S112).

  The user terminal 100 transmits slice connection permission to the child terminal 110 (S113) and stores slice identification information in the child terminal management table (S114). Through such processing, the user terminal 100 can transmit the data transmitted from the child terminal 110 to a slice corresponding to the service provided by the child terminal 110 (S115). Further, the user terminal 100 can transmit data transmitted via the slice associated with the identification information of the child terminal 110 in the child terminal management table 102 to the child terminal 110.

  In the above example, it is assumed that the user terminal 100 is already in communication connection with one or a plurality of slices, but the present invention is not limited to this. When the user terminal 100 determines, based on the connection slice information transmitted from the child terminal 110, that a slice that satisfies the requirement indicated in the connection slice information in the NSSF 210 (for example, a slice that satisfies the service requirement) is not in the communication connection state The communication control unit 101 may newly establish a communication connection with the slice designated in the NSSF 210. Then, the communication control unit 101 registers the identification information of the slice newly in the communication connection state and the identification information of the child terminal 110 in the child terminal management table 102. This can be similarly applied to modified examples described later.

  Further, the connection slice information transmitted from the child terminal 110 to the user terminal 100 may be included in the authentication process. For example, the connection slice information may be included in the authentication request in step S101, the user name input in S103, and the password input in S105. Good.

  FIG. 6 is a process corresponding to the modified example of FIG. This modification shows a case where the AMF 200 has the function of the NSSF 210. Therefore, the AMF 200 has the same functions as the slice connection determination unit 201 and the slice management unit 202 of the NSSF 210.

  An authentication process is performed between the child terminal 110 and the user terminal 100 (S101 to S105). Then, the user terminal 100 transmits a request for connection slice information to the child terminal 110, and the child terminal 110 transmits connection slice information to the user terminal 100 as a response (S106, S107). These processes are the same as those in FIG.

  When the user terminal 100 transmits the connection slice information to the AMF 200 (S108), the slice connection determination unit provided in the AMF 200 determines one slice with reference to the slice management unit 202 (S110a), and the slice connection Along with the permission, identification information of the slice as the communication connection destination is transmitted (S112).

  Upon receiving the slice connection permission, the user terminal 100 transmits the slice connection permission to the child terminal 110 (S113) and updates the child terminal management table 102 (S114).

  In this way, when the function of NSSF 210 is built in AMF 200, slice connection determination processing can be performed in AMF 200.

  Next, a modification in which slice connection determination is performed in the user terminal 100 will be described. FIG. 7 is a block diagram showing a functional configuration of the user terminal 100 in the modification. As illustrated in FIG. 7, the user terminal 100 includes a communication control unit 101, a child terminal management table 102, a slice connection determination unit 103, and a slice management unit 104. In this modification, the user terminal 100 has the same functions as the slice connection determination unit 201 and the slice management unit 202 of the NSSF 210.

  The slice management unit 104 in this modification stores the same information as slice management information in which slice identification information stored in the NSSF 210 is associated with a service type.

  The slice connection determination unit 103 refers to the slice management unit 104 and determines a slice to be connected for communication with the child terminal 110.

  FIG. 8 is a diagram showing a processing sequence of the child terminal 110 and the user terminal 100 in the modified example.

  An authentication process is performed between the child terminal 110 and the user terminal 100 (S101 to S105). Then, the user terminal 100 transmits a request for connection slice information to the child terminal 110, and the child terminal 110 transmits connection slice information to the user terminal 100 as a response (S106, S107). These processes are the same as those in FIG.

  In the user terminal 100, when the communication control unit 101 receives the connection slice information from the child terminal 110 (S107), the slice connection determination unit 201 refers to the slice management unit 104 and determines a slice to be a connection destination. (S110b).

  In the user terminal 100, the communication control unit 101 transmits a slice connection permission to the child terminal 110 and stores the determined slice identification information and the child terminal 110 identification information in the child terminal management table 102.

  Below, the effect of the communication control method using the user terminal 100 which concerns on this embodiment is demonstrated. The communication control method according to the present embodiment functions as an access point for the child terminal 110 and is a user who is a communication terminal that communicates and connects the child terminal 110 to the slices SL1 and SL2 that are virtualized networks generated on the network infrastructure. It is executed by the terminal 100.

  The user terminal 100, based on the connection slice information transmitted from the child terminal 110 for determining the slice to be the communication connection destination, the identification information of the child terminal 110 and the identification information of the slice to be the communication connection destination (slice ID) and a child terminal management table 102 for storing child terminal management information associated with the ID.

  Then, the communication control unit 101 of the user terminal 100 performs communication processing between the child terminal 110 and the slice that is the communication connection destination based on the child terminal management information stored in the child terminal management table 102. .

  According to this configuration, the user terminal 100 can communicatively connect the child terminal 110 and the slice according to connection slice information (for example, service type) that the child terminal 110 is to communicate with. Therefore, the child terminal 110 can select an appropriate slice and receive a service using the slice without being affected by the slice to which the user terminal 100 as the parent terminal is connected.

  In the user terminal 100, when the communication control unit 101 receives the connection slice information transmitted from the child terminal 110, the communication control unit 101 inquires the NSSF 210, which is a management server that manages the slice, about the identification information of the slice that is the communication connection destination. I do. Then, the child terminal management table 102 stores slice identification information based on the query result for the query.

  According to this configuration, the child terminal management table 102 stores the identification information of the slice according to the request of the child terminal 110.

  Therefore, the user terminal 100 can be connected to a slice for the child terminal 110 based on information stored in a server that manages the slice such as the NSSF 210.

  In addition, the user terminal 100 includes a slice management unit 104 that stores slice management information in which connection slice information indicating a service type and slice identification information are associated with each other. When the communication control unit 101 receives the connection slice information transmitted from the child terminal 110, the communication control unit 101 determines the identification information of the connection destination slice based on the information stored in the slice management unit 104. Then, the child terminal management table 102 stores slice identification information based on the determination.

  Thereby, the identification information of the slice according to the request | requirement of the child terminal 110 can be memorize | stored, without performing inquiry processing with respect to NSSF210.

  Next, a hardware configuration of the user terminal 100 will be described. FIG. 9 is a diagram illustrating an example of a hardware configuration of the user terminal 100 that executes processing according to the present embodiment. The above-described user terminal 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 following description, the term “apparatus” can be read as a circuit, a device, a unit, or the like. The hardware configuration of the server described above may be configured to include one or a plurality of the devices illustrated in the figure, or may be configured not to include some devices.

  Each function in the user terminal 100 is obtained by reading predetermined software (program) on hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations, communication performed by the communication device 1004, memory 1002 and storage This is realized by controlling reading and / or writing of data in 1003.

  For example, the processor 1001 controls the entire computer by operating an operating system. 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 communication control unit 302 in the AMF 301 described above may be realized by the processor 1001.

  Further, the processor 1001 reads a program (program code), software module, 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 above-described communication control unit 302 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 implement the wireless communication method according to the embodiment of the present invention.

  The storage 1003 is a computer-readable recording medium, such as an optical disc such as a CD-ROM (Compact Disc ROM), a hard disc drive, a flexible disc, a magneto-optical disc (eg, a compact disc, a digital versatile disc, 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.

  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 above-described communication control unit 101 or the like may be realized by the communication device 1004.

  The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or the like) that accepts an external input. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

  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 user terminal 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). A part or all of each functional block may be realized by the hardware. For example, the processor 1001 may be implemented by at least one of these hardware.

  The child terminal 110, AMF 200, and NSSF 21 have the same hardware configuration.

  Although the present embodiment has been described in detail above, it will be apparent to those skilled in the art that the present embodiment is not limited to the 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.

  The notification of information is not limited to the aspect / embodiment described in the present specification, and may be performed by other methods. For example, information notification 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. The RRC signaling may be referred to as an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

  Each aspect / embodiment described herein 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.

  As long as there is no contradiction, the order of the processing procedures, sequences, flowcharts, and the like of each aspect / embodiment described in this specification may be changed. 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.

  The specific operation that is assumed to be performed by a specific device in this specification may be performed by the upper node in some cases. For example, when a specific device is a base station, various operations performed for communication with a terminal in a network including one or more network nodes having the base station are as follows. Obviously, it can be performed by the base station and / or other network nodes other than the base station. Although the case where there is one network node other than the base station in the above is illustrated, a combination of a plurality of other network nodes may be used.

  Information or the like 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.

  Input / output information and 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 independently, may be used 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.

  Also, 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.

  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. For example, the signal may be a message.

  As used herein, the terms “system” and “network” are used interchangeably.

  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 parameters described above are not limiting in any way. Further, mathematical formulas and the like that use these parameters may differ from those explicitly disclosed herein. Since various channels (eg, PUCCH, PDCCH, etc.) and information elements (eg, TPC, etc.) can be identified by any suitable name, the various names assigned to these various channels and information elements are However, it is not limited.

  A base station can accommodate one or more (eg, three) cells (also referred to as sectors). When the base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each smaller area can be divided into a base station subsystem (for example, an indoor small base station RRH: Remote). Communication service can also be provided by Radio Head). The term “cell” or “sector” refers to part or all of the coverage area of a base station and / or base station subsystem that provides communication services in this coverage. Further, the terms “base station”, “eNB”, “cell”, and “sector” may be used interchangeably herein. A base station may also be referred to in terms such as a fixed station, NodeB, eNodeB (eNB), access point, femtocell, small cell, and the like.

  User terminals can be obtained by those skilled in the art from subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless It may also be called terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terminology.

  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 “determining”. 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.”

  Where the designation "first", "second", etc. is used herein, any reference to that element does not generally limit the amount or order of those elements. These designations can be used herein as a convenient way to distinguish between two or more elements. Thus, a reference to the first and second elements does not mean that only two elements can be employed there, or that in some way the first element must precede the second element.

  These terms are similar to the term “comprising” as long as “include”, “including” and variations thereof are used herein or in the claims. 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, it is intended to include a plurality of devices, except where only one device is clearly present in context or technically.

1 ... System, 90 ... UE, 10 ... OSS, 20 ... SO, 30 ... NFVO, 40 ... VNFM, 50 ... VIM, 60 ... NFVI, 150 ... RAN, 200 ... AMF, 210 ... NSSF, 160 ... SMF, 170 ... UP, 180 ... DN, 100 ... user terminal, 110 ... child terminal, 101 ... communication control unit, 102 ... child terminal management table, 103 ... slice connection determination unit, 104 ... slice management unit, 201 ... slice connection determination unit, 202 ... Slice management department.

Claims (4)

In a communication control method of a communication terminal that functions as an access point for a child terminal and connects the child terminal to a slice that is a virtualized network generated on a network infrastructure.
Child terminal management in which identification information of the child terminal is associated with identification information of the slice that is the communication connection destination based on connection slice information transmitted from the child terminal for determining a slice that is a communication connection destination A storage step of storing information in the child terminal management unit;
A communication step of performing communication processing between the child terminal and the slice based on the child terminal management information stored in the child terminal management unit;
A communication control method comprising: When the connection slice information transmitted from the child terminal is received, identification of a slice as a connection destination for a management server that stores slice management information in which connection slice information indicating a service type and slice identification information are associated with each other A query step for querying information;
In the storage step, based on a query result for the query in the query step, the slave terminal management unit stores slave terminal management information in which the identification information of the slice is associated with the identification information of the slave terminal.
The communication control method according to claim 1. A slice management unit that stores slice management information in which connection slice information indicating a service type is associated with slice identification information;
When receiving the connection slice information transmitted from the child terminal, a determination step of determining identification information of a slice to be connected based on the slice management information stored in the slice management unit;
Further comprising
In the storage step, based on the determination in the determination step, the slave terminal management unit stores the slave terminal management information in which the identification information of the slice is associated with the identification information of the slave terminal.
The communication control method according to claim 1. In a communication terminal that functions as an access point for a child terminal and connects the child terminal to a slice that is a virtualized network generated on a network infrastructure,
A child terminal in which identification information of the child terminal is associated with identification information of a slice serving as a communication connection destination based on connection slice information transmitted from the child terminal for determining a slice serving as a communication connection destination A child terminal management unit for storing management information;
Based on the child terminal management information stored in the child terminal management unit, a communication control unit that performs communication processing between the child terminal and the slice;
A communication terminal comprising:

Images