KR20200134889A - Method for controlling Radio Access Network slice service and apparatus therefor - Google Patents

Abstract

The present invention relates to a method for controlling a radio access network (RAN) slice service in a communication environment included in a next-generation mobile communication network, and an apparatus therefor. According to an embodiment of the present invention, a method of controlling a RAN slice service in a slice management apparatus comprises the steps of: analyzing an RAN to configure a plurality of RAN slices; when a mobile terminal accesses the RAN, checking slice identification information of the mobile terminal; selecting one RAN slice corresponding to the slice identification information from among the configured plurality of RAN slices; and controlling to provide a communication service to the mobile terminal by allocating RAN resources included in the selected RAN slice to the mobile terminal.

Description

RAN slice service control method and apparatus therefor TECHNICAL FIELD [Method for controlling Radio Access Network slice service and apparatus therefor]

The present invention relates to a method and apparatus for controlling a RAN slice service in a communication environment included in a next-generation mobile communication network.

In the existing 4G/LTE system, dedicated equipment is built for each entity to form a core and access network. However, since these core and access networks are built in a static form, there is a problem in that the efficiency of using network resources is deteriorated and it is difficult to change the network configuration.

Accordingly, in a next-generation wireless access network (5G) system, design of a network structure for providing an efficient network service to network devices connected by various methods is being discussed. In particular, research on network slicing technology is active as a method to guarantee the quality of end-to-end network service for various terminals.

In the next-generation communication system through the network slicing technology, it is expected that the core network is logically separated and specialized services are provided using the logically separated core network.

However, the current slicing technology is mainly for the core network, and the configuration, generation, and control methods for slices for a radio access network (RAN) to which a mobile terminal is connected are insufficient. In addition, in a communication system environment in which a 5G-based mobile communication network and a 4G/LTE-based mobile communication network are mixed, the interworking method for how slicing RAN equipment and resources is performed is insufficient.

An object of the present invention is to provide a method and apparatus for configuring a RAN slice and controlling a slice service in a communication system environment including a 5G-based mobile communication network.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by examples of the present invention. In addition, it will be easily understood that the objects and advantages of the present invention can be realized by the means shown in the claims and combinations thereof.

A method of controlling a RAN slice service in a slice management apparatus according to a first aspect of the present invention for achieving the above object includes: analyzing a Radio Access Network (RAN) and configuring a plurality of RAN slices; When a mobile terminal accesses the RAN, checking slice identification information of the mobile terminal; Selecting one RAN slice corresponding to the slice identification information from among the configured plurality of RAN slices; And controlling to provide a communication service to the mobile terminal by allocating the RAN resources included in the selected RAN slice to the mobile terminal.

In an embodiment, in the configuring of the plurality of RAN slices, a plurality of RAN slices having different frequency bandwidths may be configured in consideration of an operating frequency for each base station included in the RAN or a bandwidth required by a mobile terminal. .

In another embodiment, in the configuring of the plurality of RAN slices, in consideration of a local CU (Central Unit) and a central CU included in the RAN, for a communication service requiring a delay of less than or equal to a first threshold, the A RAN slice may be configured to select a local CU, and a RAN slice may be configured to select the central CU for a communication service requiring a delay exceeding a first threshold.

In another embodiment, in the configuring of the plurality of RAN slices, in consideration of a delay for each base station included in the RAN and a delay required for each communication service type, a delay of less than or equal to a second threshold is required. A RAN slice may be configured to select a first slice capable of high-speed processing for a service, and a RAN slice may be configured to select a second slice for a communication service requiring a delay exceeding a first threshold.

In another embodiment, the step of configuring the plurality of RAN slices is to select a non-standalone (NSA) base station or a non-standalone (SA) base station according to the type of service to which the mobile terminal is subscribed, for a general subscriber. A RAN slice may be configured to select an NSA base station, and a RAN slice may be configured to select an SA base station for an enterprise subscriber.

In another embodiment, the step of configuring the plurality of RAN slices includes mapping a RAT/Frequency Selection Priority (RFSP) index or a Subscriber Profile ID (SPID) and RAN resources so that a RAN slice is selected based on a subscriber profile. You can configure slices.

In another embodiment, the step of configuring the plurality of RAN slices is such that a RAN slice having an uplink/downlink transmission bit rate required according to a communication service is selected in consideration of GBR (Guaranteed Bit Rate) for each communication service. RAN slices can be configured.

The method may further include monitoring a quality of a communication service being provided to the mobile terminal, and modifying RAN resources allocated to the mobile terminal when the quality of the communication service is degraded.

The step of modifying the RAN resource may include: if the quality of the communication service is degraded, determining whether the RAN resource can be supported by another base station located in the vicinity of the mobile terminal; And if there is another base station that can be supported as a result of the determination, slicing the resource of the other base station to allocate the RAN resource to the mobile terminal through the other base station, and providing the communication service using the other base station. Can include.

The method comprises, as a result of the determination, if there is another base station capable of supporting only a part of the RAN resources, the RAN resource is modified to include the resource of the base station to which the mobile terminal is currently connected and the resource of the other base station, and the current access It may include the step of providing the communication service to the mobile terminal using both the active base station and the other base station.

The method may include, as a result of the determination, if there is no other base station capable of supporting the RAN resource, accessing the mobile terminal and changing an operation parameter of a base station providing the communication service.

A slice management apparatus for controlling a RAN slice service according to a second aspect of the present invention for achieving the above object comprises: a slice configuration unit configured to configure a plurality of RAN slices by analyzing a Radio Access Network (RAN); And when the mobile terminal accesses the RAN, checks the slice identification information of the mobile terminal, selects one RAN slice corresponding to the slice identification information from among the configured plurality of RAN slices, and is included in the selected RAN slice. And a control unit for controlling to provide a communication service to the mobile terminal by allocating RAN resources to the mobile terminal.

The present invention has the advantage of providing a RAN slice service to a mobile terminal and controlling the RAN slice service even in a communication environment including a 4G/LTE mobile communication network and a 5G mobile communication network.

In addition, by configuring a RAN slice in consideration of one or more of the RAN equipment level, node level, bandwidth level, delay level, structure type level, RFSP (RAT/Frequency Selection Priority) type, and transmission rate of the present invention, service It has the advantage of improving the scalability of the system and accommodating various service scenarios.

In addition, the present invention has an effect of minimizing deterioration in quality of a communication service of a mobile terminal by reconfiguring the RAN slice or changing an operation parameter included in the RAN slice when the quality of the RAN slice service is deteriorated.

The following drawings attached to the present specification illustrate preferred embodiments of the present invention, and serve to further understand the technical idea of the present invention together with specific details for carrying out the invention, so the present invention is described in such drawings. It is limited only to matters and should not be interpreted.
1 is a diagram illustrating a non-standalone (NSA) network environment in which a 4G/LTE mobile communication system and a 5G mobile communication system are mixed according to an embodiment of the present invention.
2 is a diagram illustrating a slice management apparatus according to an embodiment of the present invention.
3 is a flowchart illustrating a method of slicing a RAN for a communication service of a mobile terminal in a slice management apparatus according to an embodiment of the present invention.
4 is a flowchart illustrating a method of reconfiguring a RAN slice of a mobile terminal in a slice management apparatus according to an embodiment of the present invention.
5 is a flowchart illustrating a method of changing a parameter of a RAN slice of a mobile terminal in a slice management apparatus according to another embodiment of the present invention.

The above-described objects, features, and advantages will become more apparent through the following detailed description in connection with the accompanying drawings, whereby those of ordinary skill in the technical field to which the present invention pertains can easily implement the technical idea of the present invention. There will be. In addition, in describing the present invention, when it is determined that a detailed description of a known technology related to the present invention may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a non-standalone (NSA) network environment in which a 4G/LTE mobile communication system and a 5G mobile communication system are mixed according to an embodiment of the present invention.

Referring to FIG. 1, a Radio Access Network (RAN) according to an embodiment of the present invention includes a Long Term Evolution evolved NodeB (LTE eNB) 310 and a plurality of next Generation NodeBs (gNBs) 320 and 330. .

The LTE eNB 310 is a legacy network device supporting 4G/LTE, and includes an LTE radio unit (RU) 311 and an LTE digital unit (DU) 312. The LTE RU 311 and the LTE DU 312 may be logically or physically divided and included in the LTE eNB 310.

The LTE RU 311 is a base station of the LTE communication system and can wirelessly access the mobile terminal 100. The LTE DU 312 is a unit distributed in an LTE-based RAN and may be connected to a plurality of LTE RUs 311. The LTE DU 312 is designed to interwork with the central CU 323 of the 5G system. The LTE DU 312 may interwork with the central CU 323 through an X2 interface defined by 3rd Generation Partnership Project (3GPP).

The first gNB 320 is a next-generation network device supporting a 5G communication service, and includes a radio unit (RU), a distributed unit (DU) 322, and a central CU 323. Each of the RU 321, DU 322, and central CU 323 may be logically or physically divided and included in the first gNB 320.

The RU 321 is a 5G base station capable of operating in a 3.5 GHz band, which is a Sub-6 GHz frequency, and may allocate RAN resources sliced by the slice management apparatus 200 to the mobile terminal 100. For example, the RU 321 may slice its own bandwidth into 10 and then allocate one or more of the sliced bandwidths into 10 as radio resources of the mobile terminal 100.

The DU 322 is a unit distributed in the 5G RAN and may be connected to a plurality of RUs 321. The DU 322 communicates with the RU 321 through a fronthaul interface defined by the manufacturer itself or O-RAN, and also communicates with the central CU 323 using the F1 interface defined by 3GPP.

The second gNB 330 is a next-generation network device supporting 5G communication service, and includes an AU 331 and a local CU 332. The second gNB 330 may be constructed to provide a specialized service to subscribers of a specific group, and may perform high-speed data processing compared to the first gNB 320. Each of the AU 331 and the local CU 332 may be logically or physically divided and included in the second gNB 330.

An AU (Access Unit) 331 is a base station capable of using a millimeter wave (mmWave) broadband frequency such as a 28 GHz band, and supports ultra-high-speed wireless communication. The AU 331 may be a base station for a subscriber (eg, a corporate dedicated subscriber) receiving a specialized service. However, the AU 331 can be divided into DU and RU according to the equipment design and configuration, and all or some functions of the RLC, MAC, and PHY of the AU can be included in the DU, and some of the PHY and RF functions are Can be included. In the embodiment described below and in FIG. 1, the 4G/LTE base station is represented by the LTE RU 311, and the 5G base station is represented by the RU 321.

Each CU (323, 332) is a unit that communicates with one or more of a plurality of DUs (322) and AU (331), can perform call processing of each DU (322), and LTE DU through the X2 interface. It can also be linked with (312). In addition, the CUs 323 and 332 may communicate with each of the MME 410 and AMF/SMF 430 included in the core network. The CUs 323 and 332 may communicate with the MME 410 based on the S1 interface defined in 3GPP, and may also communicate with the AMF/SMF 430 based on the N2 interface defined in 3GPP.

The CUs 323 and 332 may be divided into a central CU 323 located at a central office and a regional CU 332 located at a regional office. The central CU 323 can communicate with a plurality of local CUs 332 and can control and manage each local CU 332. The region CU 332 may be formed on a small scale for each region. When the local CU 332 provides a service to the mobile terminal 100 located in the same area (eg, district or county) in which it is installed, the mobile terminal 100 provides a service quickly and quickly (that is, with low delay). ) Can be provided.

The core network is a mixture of a 4G/LTE-based core network and a 5G-based core network, and includes a Mobility Management Entity (MME) 410, a gateway 420, and an AMF/SMF 430.

The MME 410 is a device belonging to a 4G/LTE-based core network and performs subscriber authentication, data signaling, call processing, and the like. In addition, the gateway 420 is a device belonging to a 4G/LTE-based core network and performs interworking with a public data network (PDN) 500.

An Access and Mobility Function (AMF)/Session Management Function (SMF) 430 is a device belonging to a 5G-based SA core network, and takes charge of access and mobility of the mobile terminal 100 and manages a session. In addition, the core network may further include a User Plane Function (UPF) in charge of a user plane by adding or replacing the gateway.

The slice management device 200 is a device that configures and manages a slice in an NSA (Non-Standalone) network or an SA (Standalone) network.

2 is a diagram illustrating a slice management apparatus according to an embodiment of the present invention.

As shown in Fig. 2, the slice management apparatus 200 according to an embodiment of the present invention includes a storage unit 210, a quality monitoring unit 220, a control unit 230, and a slice configuration unit 240, and , These components may be implemented as hardware or software, or may be implemented through a combination of hardware and software.

In addition, the slice management apparatus 200 includes one or more processors and a memory, and the control unit 230, the quality monitoring unit 220, and the slice configuration unit 240 are stored in the memory in the form of programs executed by the processor. Can be mounted (stored).

The storage unit 210 is a storage means such as a memory and a disk device, and stores a slice management table. In addition, the storage unit 210 stores available states for each base station. The availability status for each base station includes identification information of a base station, an installation location of the base station, a service area of the base station, resources currently being used, and available resources.

The storage unit 210 includes a slice management table in which slice identification information (hereinafter, referred to as'slice ID') and required Radio Access Network (RAN) resources are mapped and recorded. As the RAN resource, one or more resource information from among a base station type, an uplink/downlink frequency band of the base station, and office information may be included.

In addition, one or more service types may be mapped to and recorded in the slice management table. For example, the slice ID '1' may be mapped to a service type capable of processing large amounts of data at a high speed and RAN resources required to process large amounts of data at a high speed, and stored in a slice management table. As another example, the slice ID '2' may be mapped to an HD or VAR video streaming service type and RAN resource information required to process video streaming and stored in the slice management table.

In addition, in the slice management table, an RFSP index (RAT/Frequency Selection Priority index) or SPID (Subscriber Profile ID) may be additionally mapped and recorded with the slice ID. For example, an RFSP index (or SPID) '1' and a resource of the LTE eNB 310 may be mapped to the slice ID '1' and recorded in the slice management table. In addition, an RFSP index (or SPID) '2' and a resource of the first gNB 320 may be mapped and recorded to the slice ID '2', and an RFSP index '3' and a second gNB ( 330) may be mapped and recorded.

Meanwhile, in the NSA network, the use of Network Slice Selection Assistance Information (NSSAI) defined in the standard is not possible, so QCI (QoS Class Identifier), APN (Access Point Name), DCN ID (Dedicated Core Network Identifier), TEID (Termination Endpoint Identifier) ), one or more of them may be mapped to the slice ID and stored in the slice management table. Of course, if the use of NSSAI (or S-NSSAI) information is possible in the NSA network, it can be used.

The slice configuration unit 240 configures a plurality of RAN slices by analyzing a radio access network (RAN). Specifically, the slice configuration unit 240 considers one or more of an equipment level, a node level, a bandwidth level, a latency level, a structure type level, a RAT/Frequency Selection Priority (RFSP) type, a transmission rate, and the like, The RAN slice is configured, and the slice ID and RAN resources are recorded in the slice management table based on the configured RAN slice. That is, the slice configuration unit 240 configures the RAN slice and records related data in the slice management table.

As an embodiment, the slice configuration unit 240 may configure a plurality of RAN slices having different frequency bandwidths in consideration of operating frequencies for each base station included in the RAN and record the corresponding data in the slice management table. Specifically, the slice configuration unit 240 may predefine a plurality of slices in consideration of operating frequencies of each of the 5G RAN equipment and the 4G/LTE RAN equipment. For example, the slice configuration unit 240 may map a slice ID '1', a voice/video call service, and some bandwidths of the LTE eNB 310 and store them in the slice management table. Here, the slice ID '1' is used for a voice/video call service, and it means that some bandwidth of the LTE eNB 310 is used as a RAN resource. As another example, the slice configuration unit 240 uses a slice ID '2' for a general data service, and a slice is configured by assigning a resource of the first gNB 320 as a RAN resource. A general data service and a partial bandwidth of the first gNB 320 may be mapped and stored in a slice management table. As another example, the slice configuration unit 240 uses a slice ID '3' for an enterprise-specific data service, and a slice is formed by allocating resources of the second gNB 330 as RAN resources. , The enterprise data service and some bandwidths of the second gNB 330 may be mapped and stored in the slice management table.

In another embodiment, the slice configuration unit 240 considers the RAN node level, that is, the local CU 332 and the central CU 323, and the local CU for a communication service requiring a delay of less than a first threshold. The RAN slice is configured so that the second gNB 330 including 332 is selected, and a second gNB including the central CU 323 for a communication service requiring a delay exceeding a first threshold ( By configuring the RAN slice so that 330) is selected, the corresponding data may be recorded in the slice management table. That is, the slice configuration unit 240 pre-configures a plurality of slices in consideration of the node load and low-latency processing generated in the first gNB 320 and the node load and low-latency processing that may occur in the second gNB 330. Can be defined in For example, the slice configuration unit 240 is centered on a slice ID '1' related to a voice/video call service and a slice ID '2' related to a general user data service that can allow a delay exceeding the first threshold. A slice management table by mapping the resources of the first gNB 320 to each of the slice ID '1' and the slice ID '2' so that the resources of the first gNB 320 including the CU 323 are allocated to form a slice. Can be saved on. As another example, the slice configuration unit 240 includes the region CU 332 in the slice ID '3' related to the enterprise-specific data service requiring a degree of delay equal to or less than the first threshold. The slice ID '3' and the resource of the second gNB 330 may be mapped and stored in the slice management table so that the resource is allocated to form a slice.

As another embodiment, the slice configuration unit 240 may configure a plurality of RAN slices having different frequency bandwidths in consideration of the bandwidth required by the mobile terminal 100 and record them in the slice management table. Specifically, the slice configuration unit 240 may predefine a plurality of slices in consideration of a required bandwidth for each service type that can be performed by the mobile terminal 100. For example, when a voice/video call service is required, the slice configuration unit 240 is configured with a slice ID '1' related to the voice/video call service and the LTE eNB ( The bandwidth of 310) can be mapped and stored in the slice management table. As another example, when a general data service is required, the slice configuration unit 240 is configured with a slice ID '2' related to the general data service and the first gNB ( 320) may be mapped and stored in a slice management table. As another example, the slice configuration unit 240 is configured to configure a slice by allocating a portion of the bandwidth of the second gNB 330 when an enterprise-specific data service is required. A portion of the bandwidth of 1 gNB 320 may be mapped and stored in a slice management table. Information on whether each of the bandwidths is variable or fixed may be additionally recorded in the slice management table, and as bandwidth information, a cell maximum and allocation bandwidth, a bandwidth per terminal (BWP; BandWidth Part), a CC (Component Carrier) number or PRB (Physical Resource Block) information may be used.

As another embodiment, the slice configuration unit 240 considers the delay of the base station included in the RAN and the delay sensitivity for each communication service type, and provides a slice capable of high-speed processing for a communication service requiring a delay of less than a second threshold. A RAN slice may be configured to be selected, and a RAN slice may be configured to select another slice for a communication service allowing a delay exceeding the second threshold, and corresponding data may be recorded in the slice management table. That is, the slice configuration unit 240 may pre-define a plurality of slices in consideration of a latency that may occur in 5G RAN equipment and 4G/LTE RAN equipment and a delay required for each communication service. For example, the slice configuration unit 240 maps the first service (eg, voice/video service) that is not sensitive to the degree of delay and the slice ID '1', and the LTE eNB 310 having a relatively large degree of delay. The slice ID '1' and the resource of the LTE eNB 310 may be mapped and stored in the slice management table so that the slice responsible for the first service is configured. As another example, the slice configuration unit 240 maps a second service (eg, a general data service) having an intermediate level of delay sensitivity and a slice ID '2', and generates a first gNB that generates an intermediate degree of delay. The slice ID '2' and the resource of the first gNB 320 may be mapped and stored in the slice management table so that the slice in charge of the second service 320 is configured. As another example, the slice configuration unit 240 maps the third service (eg, enterprise data service) that requires the lowest level of delay and the slice ID '3', and generates the lowest delay. 2 The slice ID '3' and the resource of the second gNB 330 may be mapped and stored in the slice management table so that the gNB 330 configures a slice in charge of the third service.

As another embodiment, the slice configuration unit 240 configures a RAN slice so that the NSA base stations 311 and 321 or the SA base station 331 are selected according to the subscriber type of the mobile terminal 100 and slices the corresponding data. Can be recorded in the management table. Here, the NSA base stations 311 and 321 include the LTE RU 311 and the RU 321, and the SA base station 331 includes the AU 331. The types of subscribers can be classified as general subscribers or corporate subscribers. For example, the slice configuration unit 240 is a slice ID '1' related to the general subscriber and the resource of the LTE eNB 310 or the first, so that the resources of the NSA base stations 311 and 321 are allocated to the general subscriber to configure the RAN slice. The resources of the gNB 320 may be mapped and stored in a slice management table. As another example, the slice configuration unit 240 maps the resources of the second gNB 330 with the slice ID '3' related to the corporate subscriber so that the resources of the SA base station 331 are allocated to the corporate subscriber to configure the RAN slice. Can be stored in the slice management table.

As another embodiment, the slice configuration unit 240 maps a RAT/Frequency Selection Priority (RFSP) index or a Subscriber Profile ID (SPID) and RAN resources so that a RAN slice is selected based on data stored in a subscriber profile to manage slices. You can write to the table. That is, the slice configuration unit 240 may match the RFSP index (or SPID) to define a plurality of slices in advance. For example, the slice configuration unit 240 maps the RFSP index (or SPID) '1' and the slice ID '1', and the LTE eNB 310 is responsible for the service related to the RFSP index '1' so that the slice is configured. , Slice ID '1' and the resource of the LTE eNB 310 may be mapped and stored in a slice management table. As another example, the slice construction unit 240 maps the RFSP index (or SPID) '2' and the slice ID '2', and the first gNB 320 is in charge of the service related to the RFSP index '2' to slice The slice ID '2' and the resource of the first gNB 320 may be mapped and stored in the slice management table so that is configured. As another example, the slice configuration unit 240 maps the RFSP index (or SPID) '3' and the slice ID '3', and the second gNB 330 is responsible for the service related to the RFSP index '3'. Thus, the slice ID '3' and the resource of the second gNB 330 may be mapped and stored in the slice management table so that a slice is formed.

As another embodiment, the slice configuration unit 240 configures the RAN slice to select a RAN slice having an uplink/downlink transmission bit rate required according to a communication service in consideration of GBR (Guaranteed Bit Rate) for each communication service type. And, the configured data can be stored in the slice management table. In other words, the GBR type bearer has a guaranteed bit rate (GBR), which is the minimum uplink/downlink DL/UL transmission bit rate that must be guaranteed by the bearer, and the maximum uplink/downlink transmission bit rate (MBR (Maximum)), which is allowed by the bearer. Bit Rate). For MBR, only the UL value is applied to the terminal and the base station, and only the DL value is applied to the serving gateway (S-GW) and the PDN gateway (P-GW). On the other hand, for GBR, DL and UL values are applied to all nodes except for the terminal. On the other hand, the non-GBR type bearer has an Aggregated Maximum Bit Rate (AMBR) value, which means the maximum transmission bit rate that can be used with other bearers, and there are APN-AMBR and UE-AMBR. APN-AMBR is the maximum uplink/downlink transmission bit rate shared by Non-GBR type bearers in the same PDN, and UE-AMBR is the maximum uplink/downlink transmission bit rate that can be shared within the same terminal. However, when one UE is connected to multiple PDNs 500, the sum of APN-AMBRs of each PDN 500 cannot exceed UE-AMBR. APN-AMBR is a value applied only to a specific PDN identified as an APN to be used, and UE-AMBR is a value applied to a specific UE and includes all PDNs.

The slice configuration unit 240 may perform a RAN slice in consideration of the characteristics of the transmission bit rate. For example, the slice configuration unit 240 maps the first service requiring the least bandwidth to slice ID '1', and the lowest uplink/downlink MBR and UE-AMBR are allocated to the first service to slice To be configured, slice ID '1' and resources of the base station may be allocated. As another example, the slice configuration unit 240 maps a second service requiring an intermediate bandwidth with a slice ID '2', and allocates an intermediate uplink/downlink MBR and a UE-AMBR to the second service. The slice ID '2' and resources of the base station can be allocated so that the slice is formed. As another example, the slice configuration unit 240 maps the third service requiring the most bandwidth with the slice ID '3', and the maximum uplink/downlink MBR and UE-AMBR are The slice ID '3' and resources of the base station may be allocated so that the slice is allocated and configured.

The controller 230 configures a RAN slice required for a communication service of the mobile terminal 100 and also performs a function of controlling a previously configured RAN slice. When the mobile terminal 100 accesses the communication network, the controller 230 checks the slice ID corresponding to the communication service of the mobile terminal 100 in the slice management table of the storage unit 210, and RAN resources are checked in the slice management table. In addition, the control unit 230 identifies the base stations 311, 321, and 331 capable of supporting RAN resources in the vicinity of the mobile terminal 100, based on the available state of each base station, and provides slice information including the identified RAN resources. It transmits to nodes 310, 320, and 330 including the identified base stations 311, 321, and 331, so that RAN resources for the mobile terminal 100 are allocated by the nodes 310, 320, and 330. In addition, when the quality of the slice service being provided to the mobile terminal 100 is deteriorated, the control unit 230 controls the RAN service by reconfiguring the RAN slice or changing an operation parameter of a base station currently providing the slice service.

The quality monitoring unit 220 receives and analyzes a quality report from the mobile terminal 100, and continuously monitors whether the quality of the slice service being provided to the mobile terminal 100 is deteriorated. In this case, the quality monitoring unit 220 may analyze the quality report received from the mobile terminal 100 to determine a decrease in bandwidth and an increase in service delay.

The slice management device 200 may be implemented by being integrated with the CUs 323 and 332 or the DU 322, or implemented as a separate device and applied to the system.

3 is a flowchart illustrating a method of slicing a RAN for a communication service of a mobile terminal in a slice management apparatus according to an embodiment of the present invention.

In the description with reference to FIG. 3, it is described that RAN slicing is performed through the second gNB 330 including the AU 331 and the local CU 332, and the mobile terminal 100 is a terminal compatible with the NSA network. Explain.

Referring to FIG. 3, when the mobile terminal 100 is initially driven, it accesses the LTE eNB 310, which is a 4G communication network (S301).

Then, the LTE eNB 310 checks one or more of a service type requested by the mobile terminal 100 and a QCI, APN, TEID, and DCN-ID of the mobile terminal 100. In addition, the LTE eNB 310 notifies the access of the mobile terminal 100, and slice management of an access notification message including one or more of the identified service type, the mobile terminal 100's QCI, APN, TEID, and DCN-ID. It transmits to the device 200 (S303). As another embodiment, the LTE eNB 310 may obtain a slice ID from the mobile terminal 310 and transmit it to the slice management apparatus 200.

Subsequently, the control unit 230 of the slice management apparatus 200 checks whether the mobile terminal 100 is a terminal capable of accessing the 5G communication service (S305). At this time, the control unit 230 of the slice management apparatus 200 acquires the identification information of the mobile terminal 100, and based on the identification information of the mobile terminal 100, the mobile terminal (not shown in the drawing) in the subscriber database ( Inquire whether 100) supports 5G. In addition, the controller 230 of the slice management apparatus 200 may obtain the RFSP index of the mobile terminal 100 by inquiring it from a subscriber database or a home subscriber server (not shown in the drawing).

Next, if the mobile terminal 100 is a terminal capable of supporting 5G, the controller 230 identifies a slice ID matching the communication service of the mobile terminal 100 in the slice management table (S307). At this time, the control unit 230 checks any one of the service type, QCI, APN, TEID, or DCN-ID included in the access notification message, and is mapped with the checked service type, QCI, APN, TEID, or DCN-ID. You can check the slice ID in the slice management table. As another embodiment, the controller 230 checks whether the subscriber of the mobile terminal 100 is a general subscriber or a corporate subscriber by interworking with a subscriber database or a home subscriber server, and determines the slice ID mapped to the identified subscriber type. You can check it in the slice management table. In another embodiment, the controller 230 interworks with a subscriber database or a home subscriber server to obtain a subscriber profile of the mobile terminal 100, checks the RFSP index or SPID included in the subscriber profile, and then checks the RFSP. The slice ID mapped to the index or SPID can be identified in the slice management table. Meanwhile, the slice ID may be recorded in the access notification message, and in this case, the controller 230 may check the slice ID directly from the access notification message.

Subsequently, the control unit 230 of the slice management apparatus 200 checks the RAN resource matching the slice ID in the slice management table (S309). The control unit 230 checks whether there is a base station capable of supporting the RAN resource in the vicinity of the location of the mobile terminal 100, and the base station capable of supporting the RAN resource is a base station to which the mobile terminal 100 is connected. I judge it. In this case, the control unit 230 checks whether there is a neighboring base station capable of supporting the RAN resource based on the available state of each base station stored in the storage unit 210 and the location of the mobile terminal 100. Meanwhile, the local CU 332 may be included in the RAN resource identified in the slice management table. In this case, the control unit 230 is located around the mobile terminal 100 and manages the base station to be connected to the mobile terminal 100. The local CU 332 is additionally selected as a device that provides a slice service of the mobile terminal 100.

In FIG. 3, it is described that the second gNB 330 including the AU 331 and the local CU 332 is a node supporting RAN resources. When a subscriber of the mobile terminal 100 subscribes to an enterprise-specific service, requires a high bandwidth, or requires a low delay, an AU 331 is selected as a base station to which the mobile terminal 100 is connected, and the mobile terminal ( Related data may be stored in the slice management table so that the local CU 332 installed in the vicinity of 100) is selected as a device responsible for the service of the mobile terminal 100.

Further, the control unit 230 of the slice management apparatus 200 generates slice information so that necessary resources are allocated to the second gNB 330 and transmits the slice information to the second gNB 330 (S311). The slice information includes identification information of the mobile terminal 100, resources of the AU 331 to be allocated to the mobile terminal 100, and resources of the local CU 332. The control unit 230 of the slice management apparatus 200 may transmit a frequency bandwidth, memory, number of processors, etc. allocated to the mobile terminal 100 in the slice information. In addition, the control unit 230 of the slice management apparatus 200 may set a downlink bandwidth and an uplink bandwidth among the allocated frequency bandwidths, and thus include the downlink bandwidth and the uplink bandwidth in the slice information.

Then, the second gNB 330 performs RAN slicing by allocating radio resources for the communication service of the mobile terminal 100 from its available radio resources based on the RAN resources included in the slice information (S313). ). At this time, the AU 331 included in the second gNB 330 checks the frequency bandwidth in the RAN resource of the mobile terminal 100, and allocates the identified frequency bandwidth as the bandwidth of the mobile terminal 100 from the available bandwidth. can do. In addition, when the uplink bandwidth and the downlink bandwidth are included in the slice information, the AU 331 may allocate as much as the uplink bandwidth and the downlink bandwidth as a bandwidth for the mobile terminal 100 among available bandwidths. . In addition, the local CU 332 may allocate one or more of a bandwidth, a memory, a processor, etc. as RAN resources for the mobile terminal 100 based on the RAN resources included in the slice information.

When the second gNB 330 normally ends RAN slicing, the slicing response message is transmitted to the slice management device 200 (S315), and the slice management device 200 is the AU 331, which is the base station that has performed the RAN slicing. The available status of each base station is updated by changing the available status of.

Subsequently, the second gNB 330 induces connection of the mobile terminal 100, wirelessly connects with the mobile terminal 100, relays communication with the mobile terminal 100, and connects the mobile terminal 100 and the bearer. To form (S317). In addition, the mobile terminal 100 transmits and receives data through the bearer in which the required quality is guaranteed.

When resource allocation is performed as shown in FIG. 3, the mobile terminal 100 is in a wireless connection state with the LTE eNB 310 and at the same time is in a wireless connection state with the second gNB 330. The mobile terminal 100 transmits a control message (i.e., signaling message) to the LTE eNB 310 or receives from the LTE eNB 310, and general data (eg, streaming data, drone data, etc.) is an LTE eNB It transmits and receives through the second gNB 330 instead of 310.

In this way, in a state in which the mobile terminal 100 transmits/receives data through the second gNB 330, it is far from the service area of the second gNB 330 or an overload occurs in the second gNB 330, thereby reducing the required RAN resources. May not be supported. Accordingly, the slice management apparatus 200 monitors the quality of the slice service being provided to the mobile terminal 100, and when the quality of the service decreases, the RAN slice of the mobile terminal 100 is reconfigured or the base station providing the slice service You can change the operating parameters of

4 is a flowchart illustrating a method of reconfiguring a RAN slice of a mobile terminal in a slice management apparatus according to an embodiment of the present invention.

Referring to FIG. 4, the quality monitoring unit 220 of the slice management apparatus 200 may periodically monitor the quality of the slice service being provided to the mobile terminal 100 to detect a decrease in the quality of the slice service ( S401). At this time, the quality monitoring unit 220 may periodically receive a quality report from the mobile terminal 100 and analyze the quality report to detect a decrease in the quality of the slice service. That is, the mobile terminal 100 periodically measures the current PER (Packet Error Rate), PDB (Packet Delay Budget), downlink bandwidth, and uplink bandwidth, and the measured PER, PDB, downlink bandwidth, and uplink bandwidth. A quality report including bandwidth, etc. is periodically transmitted to the slice management device 200, and the quality monitoring unit 220 of the slice management device 200 analyzes the quality report received from the mobile terminal 100, and moves It is possible to check whether the quality of the slice service being provided to the terminal 100 is degraded. The quality monitoring unit 220 compares the service quality (e.g., delay, bandwidth, etc.) required for the RAN slice service with the service quality checked through the quality report, and whether quality deterioration occurs in the slice of the mobile terminal 100. Whether or not can be determined.

When the quality monitoring unit 220 determines that quality deterioration has occurred in the slice service of the mobile terminal 100, the control unit 230 of the slice management device 200 checks the current location of the mobile terminal 100 (S403). ). At this time, the control unit 230 of the slice management device 200 may receive a GPS signal from the mobile terminal 100 and locate the location of the mobile terminal 100, or the radio of the base station communicating with the mobile terminal 100 Based on the signal, the location of the mobile terminal 100 or a service area (ie, a cell area) of the mobile terminal 100 can be identified. Next, the control unit 230 of the slice management apparatus 200 checks whether there is a base station 311, 321, 331 capable of supporting required RAN resources among neighboring base stations in which the mobile terminal 100 is located (S405). ). The control unit 230 of the slice management apparatus 200 determines whether there is a neighboring base station 311, 321, 331 capable of supporting RAN resources required for the communication service of the mobile terminal 100 based on the available state of each base station. Check. In FIG. 4, it has been described that the RU 321 is capable of supporting RAN resources required for the communication service of the mobile terminal 100, but another base station such as the AU 331 may support the required resources.

Next, the control unit 230 of the slice management apparatus 200 reconfigures the RAN slice to ensure the slice service of the mobile terminal 100 as the quality of the slice service being provided to the mobile terminal 100 deteriorates. Is performed (S407). That is, the control unit 230 of the slice management apparatus 200 is able to support the communication service of the mobile terminal 100 by the RU 321 included in the first gNB 320. The RAN slice is reconfigured so that the identified RAN resource is supported by the first gNB 320.

Next, the control unit 230 of the slice management apparatus 200 transmits the reconstructed slice information to the corresponding first gNB 320 and controls the RAN slicing for the mobile terminal 100 in the RU 321 to be performed. Do (S409). At this time, the control unit 230 of the slice management apparatus 200 generates slice information so that the RAN resource is allocated to the first gNB 320, and transmits the slice information to the first gNB 320. The slice information includes identification information of the mobile terminal 100 and RAN resources to be allocated to the mobile terminal 100 (ie, the RAN resources identified in step S309).

Accordingly, the first gNB 320 performs RAN slicing by allocating resources necessary for the communication service of the mobile terminal 100 based on the RAN resources included in the received RAN slice information (S411), and resource allocation is completed. If so, the slice completion response message is transmitted to the slice management apparatus 200 (S413).

Then, the control unit 230 of the slice management apparatus 200 changes the available state of the RU 321, which is the base station that has performed the RAN slicing, and updates the available state for each base station. At this time, the slice management apparatus 200 also changes the available state of the AU 331 as resources are recovered to the AU 331. Next, the slice management apparatus 200 transmits a reconnection instruction message including the identification information of the RU 321 to the mobile terminal 100 (S415). In this case, the slice management apparatus 200 may transmit the reconnection indication message to the mobile terminal 100 using the LTE eNB 310 which is a 4G/LTE-based access network.

Then, the mobile terminal 100 wirelessly accesses the RU 321 from the second gNB 330 to the first gNB 320 (S417). Further, the first gNB 320 forms a radio link with the mobile terminal 100 using the allocated frequency band for the mobile terminal 100, and transmits and receives data to and from the mobile terminal 100 through the radio link.

As another embodiment, when the slice management apparatus 200 detects a decrease in the quality of the slice service, but the available resources in the neighboring base stations of the mobile terminal 100 are not sufficient, the RAN may partially use the available resources of the neighboring base stations. You can also reconstruct the slice. In this case, the control unit 230 of the slice management apparatus 200 configures a RAN slice including some resources available in the RU 321, which is a neighboring base station, and transmits the RAN slice information to the first gNB 320. send. And the control unit 230 of the slice management apparatus 200 transmits a message instructing the additional access to the first gNB 320 to the mobile terminal 100, as well as the second gNB 330 of the mobile terminal 100 It is also controlled to be connected to the first gNB 320. In this case, the mobile terminal 100 may distribute the data using both the first gNB 320 and the second gNB 330 and transmit the data to the destination.

5 is a flowchart illustrating a method of changing a parameter of a RAN slice of a mobile terminal in a slice management apparatus according to another embodiment of the present invention.

FIG. 5 illustrates a case in which a neighboring base station required for a slice service of the mobile terminal 100 is not searched, an operation parameter of already established slice information is changed.

Referring to FIG. 5, the quality monitoring unit 220 of the slice management apparatus 200 periodically monitors the quality of the slice service being provided to the mobile terminal 100, and detects a decrease in the quality of the slice service (S501). .

When the quality monitoring unit 220 determines that quality deterioration has occurred in the slice service of the mobile terminal 100, the control unit 230 of the slice management device 200 checks the current location of the mobile terminal 100 (S503). ). Next, the control unit 230 of the slice management apparatus 200 checks whether there is a base station 311, 321, 331 capable of supporting required RAN resources among neighboring base stations in which the mobile terminal 100 is located (S505). ). In FIG. 5, it is described that there is no neighboring base station capable of supporting RAN resources required for a communication service of the mobile terminal 100.

Next, the control unit 230 of the slice management apparatus 200 has deteriorated the quality of the slice service being provided to the mobile terminal 100, but there is no base station capable of supporting the necessary resources of the mobile terminal 100 in the vicinity. According to this, the process of changing the operation parameter of the RAN slice of the mobile terminal 100 (that is, the operation parameter of the second gNB) is performed (S507).

In one embodiment, the control unit 230 of the slice management apparatus 200 checks whether the second gNB 330 to which the mobile terminal 100 is connected is operated in a Time Division Duplex (TDD) mode, In the case of operation, the parameter can be changed to adjust the transmission ratio of the downlink bandwidth and the uplink bandwidth. At this time, the control unit 230 of the slice management apparatus 200 analyzes the quality report received from the mobile terminal 100, and is a type of communication that is relatively frequently used among uplink communication and downlink communication in the mobile terminal 100. And, based on this communication type, the transmission rate parameter can be changed so that the transmission ratio of the uplink bandwidth and the downlink bandwidth is changed. For example, when the mobile terminal 100 mainly uses downlink communication, the control unit 230 of the slice management apparatus 200 sets the transmission rate parameter so that the transmission rate of the downlink communication is relatively high from the existing transmission rate. Conversely, when the mobile terminal 100 mainly uses uplink communication, the operation parameter may be changed so that the transmission rate of the uplink communication is relatively higher than the existing transmission rate. When the second gNB 330 is operated by FDD, the control unit 230 of the slice management apparatus 200 sets the operation parameter to adjust the uplink transmission ratio and the downlink transmission ratio after changing the operation mode to TDD. You can change it.

As another embodiment, the control unit 230 of the slice management apparatus 200 analyzes the quality report of the mobile terminal 100, and when it is determined that a service delay occurs in the mobile terminal 100, the degree of delay is determined. To lower it, one or more of the slot format, the number of slot symbols, the MCS level, and sub-carrier spacing may be changed. That is, when a service delay occurs, the control unit 230 of the slice management apparatus 200 may change the operation parameter so that the number of slot symbols decreases, or change the DL and UL transmission rates through a slot format change, or The operation parameter may be changed to change to a higher level MCS, or the operation parameter may be changed to increase the subcarrier interval. In addition, when the service delay is increased, the slice management apparatus 200 may change the operation parameter so that the same packet is retransmitted a preset number of times.

Next, the slice management apparatus 200 transmits the slice information in which the operation parameter is changed to the second gNB 330 (S509).

Then, the second gNB 330 checks the changed operation parameter in the slice information, and selects from among downlink bandwidth, uplink bandwidth, slot format, number of slot symbols, MCS level, and sub-carrier spacing. After changing one or more parameters, communication with the mobile terminal 100 is continuously performed (S513).

While this specification includes many features, such features should not be construed as limiting the scope or claims of the invention. In addition, features described in separate embodiments herein may be combined and implemented in a single embodiment. Conversely, various features described in a single embodiment herein may be individually implemented in various embodiments, or may be properly combined and implemented.

Although the operations have been described in a specific order in the drawings, it should not be understood that such operations are performed in a specific order as shown, or as a series of consecutive sequences, or that all described operations are performed to obtain a desired result. . Multitasking and parallel processing can be advantageous in certain environments. In addition, it should be understood that classification of various system components in the above-described embodiments does not require such classification in all embodiments. The above-described program components and systems may generally be implemented as a package in a single software product or multiple software products.

The method of the present invention as described above may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a computer-readable form. This process can be easily carried out by a person of ordinary skill in the art to which the present invention pertains, and thus will not be described in detail.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those of ordinary skill in the technical field to which the present invention belongs. It is not limited by the drawings.

100: mobile terminal 200: slice management device
210: storage unit 220: quality monitoring unit
230: control unit 240: slice configuration unit
310: LTE eNB 311: LTE RU
312: LTE DU 320: first gNB
321: RU 323: DU
323: central CU 330: second gNB
331: AU 332: Region CU
410: MME 420: GW
430: AMF/SMF 500: PDN

Claims (14)

A method of controlling a RAN slice service in a slice management apparatus, comprising:
Analyzing a Radio Access Network (RAN) and configuring a plurality of RAN slices;
When a mobile terminal accesses the RAN, checking slice identification information of the mobile terminal;
Selecting one RAN slice corresponding to the slice identification information from among the configured plurality of RAN slices; And
And controlling to provide a communication service to the mobile terminal by allocating RAN resources included in the selected RAN slice to the mobile terminal. The method of claim 1,
The step of configuring the plurality of RAN slices,
A method of controlling a RAN slice service, comprising configuring a plurality of RAN slices having different frequency bandwidths in consideration of an operating frequency for each base station included in the RAN or a bandwidth required by a mobile terminal. The method of claim 1,
The step of configuring the plurality of RAN slices,
In consideration of the regional CU (Central Unit) and the central CU included in the RAN, the RAN slice is configured so that the regional CU is selected for a communication service requiring a delay of less than a first threshold, and a first threshold is A method for controlling a RAN slice service, comprising configuring a RAN slice so that the central CU is selected for a communication service requiring an excessive delay. The method of claim 1,
The step of configuring the plurality of RAN slices,
The RAN slice is configured to select a first slice capable of high-speed processing for a communication service requiring a delay of less than a second threshold in consideration of the delay for each base station included in the RAN and the delay required for each communication service type. And configuring a RAN slice such that a second slice is selected for a communication service requiring a delay exceeding the first threshold. The method of claim 1,
The step of configuring the plurality of RAN slices,
The RAN slice is configured so that the NSA base station or the SA base station is selected according to the type of service to which the mobile terminal is subscribed, the NSA base station is selected for the general subscriber, and the RAN slice is configured so that the SA base station is selected for the corporate subscriber. RAN slice service control method. The method of claim 1,
The step of configuring the plurality of RAN slices,
A RAN slice service control method, comprising configuring a RAN slice by mapping a RAT/Frequency Selection Priority (RFSP) index or a Subscriber Profile ID (SPID) and RAN resources so that a RAN slice is selected based on a subscriber profile. The method of claim 1,
The step of configuring the plurality of RAN slices,
A method for controlling a RAN slice service, comprising configuring a RAN slice such that a RAN slice having an uplink/downlink transmission bit rate required according to a communication service is selected in consideration of GBR (Guaranteed Bit Rate) for each communication service. The method according to any one of claims 1 to 7,
Monitoring the quality of the communication service being provided to the mobile terminal, and modifying the RAN resources allocated to the mobile terminal when the quality of the communication service is degraded. The method of claim 8,
The step of modifying the RAN resource,
If the quality of the communication service is degraded, determining whether the RAN resource can be supported by another base station located in the vicinity of the mobile terminal; And
If there is another base station that can be supported as a result of the determination, slicing the resource of the other base station, allocating the RAN resource to the mobile terminal through the other base station, and providing the communication service using the other base station; RAN slice service control method including. The method of claim 9,
As a result of the determination, if there is another base station capable of supporting only a part of the RAN resources, the mobile terminal modifies the RAN resource to include the resource of the currently connected base station and the resource of the other base station, and the currently connected base station and the Providing the communication service to the mobile terminal using all other base stations; RAN slice service control method comprising a. The method of claim 9,
As a result of the determination, if there is no other base station capable of supporting the RAN resource, accessing the mobile terminal and changing an operation parameter of a base station providing the communication service. The method of claim 11,
The step of changing the operation parameter,
At least one of the transmission rate of the uplink bandwidth and the downlink bandwidth of the base station, a slot symbol format, the number of slot symbols, a Modulation Coding Scheme (MCS) level, and a sub-carrier spacing is changed. RAN slice service control method. In the slice management apparatus for controlling a RAN slice service,
A slice construction unit that analyzes a radio access network (RAN) and configures a plurality of RAN slices; And
When the mobile terminal accesses the RAN, the mobile terminal checks the slice identification information, selects one RAN slice corresponding to the slice identification information from among the plurality of configured RAN slices, and then the RAN included in the selected RAN slice. Slice management apparatus comprising a; a control unit for controlling to allocate resources to the mobile terminal to provide a communication service to the mobile terminal. The method of claim 13,
Includes; a quality monitoring unit for monitoring the quality of the communication service being provided to the mobile terminal,
The controller, when the quality of the communication service is degraded as a result of the monitoring, modifies the RAN resources allocated to the mobile terminal.

Images