KR20240052908A - Electronic device and method for providing network slice service - Google Patents

Abstract

According to one embodiment, a method performed by a network slice (NS) management device in a wireless communication system may include obtaining radio access network (RAN) slice profile information corresponding to attribute information of the NS service. . The method may include receiving, from a network function (NF) management device, a statistical message containing statistical information about a plurality of cells in a coverage area for providing NS services. The method may include, for each cell, identifying the PRB ratio allocated for the NS service. The method may include transmitting a configuration request message for resource allocation of the NS service to the NF management device.

Description

Electronic device and method for providing network slice service {ELECTRONIC DEVICE AND METHOD FOR PROVIDING NETWORK SLICE SERVICE}

The descriptions below relate to electronic devices and methods for providing network slice services.

In order to meet the increasing demand for wireless data traffic following the commercialization of the 4G (4th generation) communication system, efforts are being made to develop an improved 5G (5th generation) communication system or pre-5G communication system. For this reason, the 5G communication system or pre-5G communication system is called a Beyond 4G Network communication system or a Post LTE (Long Term Evolution) system.

To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (such as the 60 GHz band). In order to alleviate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, the 5G communication system uses beamforming, massive array multiple input/output (massive MIMO), and full dimension multiple input/output (FD-MIMO). ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, to improve the network of the system, the 5G communication system uses evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), and ultra-dense networks. , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation. Technology development is underway.

In addition, the 5G system uses FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding), which are advanced coding modulation (ACM) methods, and FBMC (Filter Bank Multi Carrier), which is an advanced access technology. ), NOMA (Non Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access) are being developed.

According to one embodiment, a method performed by a network slice (NS) management device in a wireless communication system may include obtaining radio access network (RAN) slice profile information corresponding to attribute information of the NS service. . The method may include receiving, from a network function (NF) management device, a statistical message containing statistical information about a plurality of cells in a coverage area for providing NS services. The statistical information about the plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. The method may include an operation of identifying a PRB ratio allocated for the NS service for each cell, based on the RAN slice profile information and the statistics message. The method may include transmitting a configuration request message for resource allocation of the NS service to the NF management device, based on the ratio of the PRB.

According to one embodiment, a method performed by a network function (NF) management device in a wireless communication system includes coverage for providing NS services based on a request for a statistics message received from a network slice (NS) management device. It may include transmitting the statistical message containing statistical information about a plurality of cells in the area to the NS management device. The statistical information about the plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. The method may include receiving a configuration request message for resource allocation of NS services from the NS management device, based on the statistics message. The method may include performing radio resource management (RRM) for the NS service based on the PRB rate identified through the setup request message.

According to one embodiment, a network slice (NS) management device in a wireless communication system may include at least one processor and a transceiver. The at least one processor may be configured to obtain radio access network (RAN) slice profile information corresponding to attribute information of the NS service. The at least one processor may be configured to receive a statistical message containing statistical information about a plurality of cells in a coverage area for providing NS services from a network function (NF) management device. The statistical information about the plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. The at least one processor may be configured to identify a PRB ratio allocated for the NS service for each cell, based on the RAN slice profile information and the statistical message. The at least one processor may be configured to transmit, to the NF management device, a configuration request message for resource allocation of the NS service, based on the ratio of the PRB.

According to one embodiment, a network function (NF) management device in a wireless communication system may include at least one processor and a transceiver. The at least one processor, based on a request for the statistics message received from an NS (network slice) management device, sends the statistics message containing statistical information about a plurality of cells in a coverage area for providing NS services, It can be set to transmit to the NS management device. The statistical information about the plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. The at least one processor may be configured to receive a configuration request message for resource allocation of NS services from the NS management device, based on the statistics message. The at least one processor may be configured to perform radio resource management (RRM) for the NS service based on the PRB rate identified through the configuration request message.

Figure 1 shows an example in which slice characteristic items are reflected in the network infrastructure of a radio access network (RAN), a core network (CN), and a transport network (TN) domain, according to an embodiment.
FIG. 2 illustrates operating procedures of a plurality of management functions included in a network slicing management system according to an embodiment.
Figure 3 is a diagram showing network capacity according to one embodiment.
Figure 4 shows an example of the operation of a RAN network slice subnet management function (NSSMF) and network function management function (NFMF), according to an embodiment.
Figure 5 shows an example of NFMF operation according to a RAN slice profile (Slice Profile) according to an embodiment.
Figure 6 shows a flowchart of the operation of a network slice (NS) management device according to an embodiment.
Figure 7 shows a flowchart of the operation of a network function (NF) management device according to an embodiment.

Terms used in the present disclosure are merely used to describe specific embodiments and may not be intended to limit the scope of other embodiments. Singular expressions may include plural expressions, unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by a person of ordinary skill in the technical field described in this disclosure. Among the terms used in this disclosure, terms defined in general dictionaries may be interpreted to have the same or similar meaning as the meaning they have in the context of related technology, and unless clearly defined in this disclosure, have an ideal or excessively formal meaning. It is not interpreted as In some cases, even terms defined in the present disclosure cannot be interpreted to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware approach method is explained as an example. However, since various embodiments of the present disclosure include technology using both hardware and software, the various embodiments of the present disclosure do not exclude software-based approaches.

Terms referring to signals used in the following description (e.g., packet, message, signal, information, signaling), terms referring to resources (e.g., section, symbol, slot, subframe ( subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), opportunity), terms for computational states (e.g. phase ( step, operation, procedure), terms referring to data (e.g. packet, message, user stream, information, bit, symbol, codeword) , a term referring to a channel, a term referring to network entities (distributed unit (DU), radio unit (RU), central unit (CU), control plane (CU-CP), user plane (CU-UP) ), O-DU (O-RAN (open radio access network) DU), O-RU (O-RAN RU), O-CU (O-RAN CU), O-CU-UP (O-RAN CU-CP ), O-CU-CP (O-RAN CU-CP)), terms referring to device components, etc. are examples for convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used. In addition, terms such as '... part', '... base', '... water', and '... body' used hereinafter mean at least one shape structure or a unit that processes a function. It can mean.

In addition, in the present disclosure, the expressions greater than or less than may be used to determine whether a specific condition is satisfied or fulfilled, but this is only a description for expressing an example, and the description of more or less may be used. It's not exclusion. Conditions written as ‘more than’ can be replaced with ‘more than’, conditions written as ‘less than’ can be replaced with ‘less than’, and conditions written as ‘more than and less than’ can be replaced with ‘greater than and less than’. In addition, hereinafter, 'A' to 'B' means at least one of the elements from A to (including A) and B (including B).

The present disclosure describes various embodiments using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), extensible radio access network (xRAN), and open-radio access network (O-RAN)), This is only an example for explanation, and various embodiments of the present disclosure can be easily modified and applied to other communication systems.

Figure 1 shows an example in which slice characteristic items are reflected in the network infrastructure of a radio access network (RAN), a core network (CN), and a transport network (TN) domain, according to an embodiment.

As wireless communication technology develops (e.g., 5G (5th generation)), network slicing has been proposed to configure one network infrastructure into multiple virtual networks. In the following, slice service requirements for network slicing (service An algorithm for guaranteeing a per-slice transmission rate SLA (level agreement, SLA) and an operation procedure between network devices to perform this can be described.

A network slice may refer to a logical network that provides service-specific connectivity to a data network (DN) associated with a specific service application. For example, the terminal of a slice user who has subscribed to a service can be connected to the service application through the corresponding network slice and receive functions, performance, and security optimized for the service.

An operating entity (e.g., network operator) for operating a network can define the requirements for services to be provided through a network slice in order to create a network slice. In order to define the requirements for services to be provided through network slices, GSMA (global system for mobile communications alliance) establishes GST (generic), which includes attributes related to the characteristics of network slices among service requirements related to various industries. network slice template) was defined. The operator (e.g. network operator) who operates the network can define NEST (network slice type) by quantifying the requirements among the items related to the characteristics of various network slices defined in GST. For example, NEST can be used as an SLA negotiated between slice users and the operating entity that must be satisfied through a network slice. NEST can be structured as shown in Table 1.

Referring to Table 1, NEST may consist of numerical values of requirements based on network standards (e.g., 3GPP standards). For example, NEST may consist of quantifiable values for requirements for enhanced mobile broadband (eMBB), mobile internet of things (mIoT), and ultra-reliable and low latency communications (URLLC) services.

According to one embodiment, among the GST characteristic items constituting NEST, the item requested as SLA may include the transmission rate per slice. For example, the data rate per slice may mean the aggregated data rate of all users (or terminals) using a network slice.

According to one embodiment, the per-slice data rate may include a guaranteed data rate per slice and a maximum data rate per slice. For example, the guaranteed data rate per slice may mean the sum of data rates that must be guaranteed through GBR QoS Flows (guaranteed bit rate quality of service flows) connected by all users (or terminals) using the network slice. . For example, the maximum data rate per slice may mean the maximum data rate that can be supported within the slice for all users (or terminals) using the slice.

According to one embodiment, when a network slice as a service (NSaaS) that utilizes a service-specific slice network as a sales model is established, the charging level may be configured differently depending on the size of the transmission rate per slice network.

Referring to Figure 1, the characteristic items of a network slice composed of NEST are service profile, slice profile, and It can be interpreted as a slice profile for each domain. The slice profile for each domain can be divided into a radio access network (RAN) domain, a core network (CN) domain, and a transport network (TN) domain and reflected in the network infrastructure.

According to one embodiment, in order to reflect the characteristic items of the slice profile for each domain in the network infrastructure, conversion to parameters (or configuration parameters) of a network function (NF) related to the slice profile for each domain may be required. For example, the slice requirements described in the slice profile for each domain may be reflected differently in the network infrastructure depending on the vendor of the network equipment.

In the following specification, information (or parameters) and operations set within a slice of the RAN domain (hereinafter referred to as RAN slice) may be proposed in order to implement a network slice that satisfies the per-slice data rate requirements. Since the bottleneck of the network transmission rate is in the RAN domain, the network transmission rate can be effectively controlled according to the information and operations set within the slice of the RAN domain.

The RAN domain of the present disclosure refers to an area where communication between a base station and a terminal is performed. A base station is a network infrastructure that provides wireless access to terminals. A base station has coverage defined based on the distance over which signals can be transmitted. In addition to the base station, the base station includes 'access point (AP)', 'eNodeB (eNB)', '5G node (5th generation node)', and 'next generation nodeB (gNB). ', 'wireless point', 'transmission/reception point (TRP)' or other terms with equivalent technical meaning. Hereinafter, in explaining the mobility of the terminal of the present disclosure, the base station will be referred to as gNB, but of course, other terms may be used depending on the communication environment or embodiment.

A terminal is a device used by a user and communicates with a base station through a wireless channel. The link from the base station to the terminal is called downlink (DL), and the link from the terminal to the base station is called uplink (UL). Additionally, a terminal and another terminal can communicate through mutual wireless channels. At this time, the link between the terminal and another terminal (device-to-device link, D2D) is referred to as a sidelink, and the sidelink may be used interchangeably with the PC5 interface. In some other embodiments, the terminal may operate without user involvement. According to one embodiment, the terminal is a device that performs machine type communication (MTC) and may not be carried by the user. Additionally, according to one embodiment, the terminal may be a narrowband (NB)-internet of things (IoT) device. In addition to the terminal, the terminal includes 'user equipment (UE)', 'customer premises equipment (CPE)', 'mobile station', 'subscriber station', and 'remote device'. It may be referred to as a 'remote terminal', 'wireless terminal', electronic device', or 'user device', or other terms with equivalent technical meaning. Hereinafter, in describing the mobility of the terminal of the present disclosure, the terminal is referred to as UE, but of course, other terms may be used depending on the communication environment or embodiment.

In embodiments of the present disclosure, a function for controlling the RAN transmission rate may be implemented in a scheduler of a base station (eg, gNB). The gNB's scheduler can control the RAN transmission rate. According to one embodiment, the scheduler of the gNB may control the RAN transmission rate to satisfy slice transmission rate requirements based on priority scheduling and radio resource partitioning. For example, priority-based scheduling allows you to secure priority in resource allocation by setting priorities on a slice-by-slice basis to differentiate services between slices when different RAN slices compete while sharing the same radio resource pool. It may refer to scheduler operation. As an example, even if the quality of service (QoS) flows constituting different slices have the same 5G QoS identifier (5QI), in order to differentiate services for a specific slice, the quality of service (QoS) flows included in the high-priority slice QoS flows can be set to have priority in resource allocation.

According to one embodiment, radio resource division (or radio resource division function), unlike priority-based scheduling, separates and dedicates PRB (physical resource block), which is a radio resource of the RAN, by RAN slice or by group of slices with the same characteristics. It may refer to the function of allocating. Radio resource division can achieve the slice operation purpose of not affecting performance and operation between different slices through resource isolation. As an example, an RRMPolicy class may be defined based on the 5G network resource model (NRM) so that the operator can set the amount of resources for each RAN NF through the management domain. RRMPolicyRatio in the RRMPolicy class can be set (or defined) to set the amount of radio resources for each slice (tuple of [S-NSSAI (single-network slice selection assistance information), PLMN (public land mobile network) ID]). there is.

RRMPolicyRatio is an implementation of the abstract RRMPolicy_IOC (information object class). RRMPolicyRatio has three properties excluding inherited properties (DN, resourceType, rRMPolicyMemberList).

- The rRMPolicyMaxRatio property defines the maximum resource usage quota for the associated rRMPolicyMemberList, including at least one shared resource, priority resource, and dedicated resource. The sum of the 'rRMPolicyMaxRatio' values assigned to all RRMPolicyRatio(s) names contained by the same MangedEntity may be greater than 100.

- The rRMPolicyMinRatio property defines the minimum resource usage quota for the associated RRMPolicyMemberList, including at least one of the prioritized and dedicated resources. The sum of the 'rRMPolicyMinRatio' values assigned to all RRMPolicyRatio(s) names contained in the same MangedEntity must be less than or equal to 100.

- The rRMPolicyDedicatedRatio property defines the dedicated resource usage quota for RRMPolicyMemberList, including dedicated resources. The sum of the 'rRMPolicyDedicatedRatio' values assigned to all RRMPolicyRatio(s) names contained by the same MangedEntity must be less than or equal to 100.

The following defines the three resource categories mentioned above.

- Shared resource: refers to a resource shared with other rRMPolicyMemberList(s) (i.e., rRMPolicyMemberList(s) defined in the RRMPolicyRatio(s) name included in the same ManagedEntity). The use of shared resources is not guaranteed in the connected rRMPolicyMemberList. Shared resource quotas are expressed as [rRMPolicyMaxRatio-rRMPolicyMinRatio].

- Prioritized resources: This means that resources are used preferentially in the associated RRMPolicyMemberList. These resources are guaranteed to be used by the associated RRMPolicyMemberList when needed. When not in use, these resources can be used by other rRMPolicyMemberList(s) (i.e. rRMPolicyMemberList(s) defined in the name RRMPolicyRatio(s) contained in the same ManagedEntity). Prioritized resource quotas are indicated as [rRMPolicyMinRatio-rRMPolicyDedicatedRatio].

- Dedicated resources: means that the resource is dedicated for use in the associated RRMPolicyMemberList. These resources cannot be shared even if the associated RRMPolicyMember is not using them. Dedicated resource allocation is indicated as [rRMPolicyDedicatedRatio].

According to one embodiment, priority-based scheduling and radio resource partitioning may both be used to control the RAN transmission rate to satisfy slice transmission rate requirements. For example, the gNB's scheduler can separate available resources into a shared resource pool and a dedicated resource pool. The gNB's scheduler can provide differentiation of transmission rate performance using priority-based scheduling between different RAN slices within the common resource pool. The gNB's scheduler can adjust the allocation of dedicated resources for RAN slices using the dedicated resource pool to provide differentiation of transmission rates.

According to one embodiment, the slice profile of 5G NRM of the 3GPP standard may include resourceSharingLevel as a characteristic item for setting whether radio resources in the RAN domain can be shared between RAN slices. 'resourceSharingLevel' specifies whether the resources to be allocated to a network slice subnet can be shared with other network slice subnets. As a setting value ('resourceSharingLevel') of a characteristic item for setting whether radio resources of the RAN domain can be shared between RAN slices, an allowed value of {shared, non-shared} can be defined.

According to the above-described embodiment, priority-based scheduling and radio resource division can be used to create a RAN slice that satisfies the per-slice transmission rate SLA. Priority-based scheduling and radio resource partitioning may not guarantee the specified value of per-slice transmission rate SLA.

For example, according to priority-based scheduling, the priority of resource allocation may be set to be differentially distributed between different slices using the same resource (e.g., a common resource pool) based on the priority set by the operator. In this case, by giving resource allocation priority to slices that require a high per-slice transmission rate SLA, there is an effect of relatively increasing the transmission rate in a limited resource pool. However, the above-described operation is a best-effort method with limited resources, and the specified value of the data rate SLA per slice may not be guaranteed.

For example, according to the radio resource division function, by allocating dedicated radio PRB resources to each RAN slice or group of slices, the per-slice data rate can be set to satisfy the specified value of the per-slice data rate SLA. However, logical setting standards for allocating wireless PRB resources appropriate for the transmission rate per slice may not be defined. Therefore, the amount of PRB resources to satisfy the SLA of a specific service can be manually set depending on the network operator's network operation experience. The amount of PRB resources to satisfy the SLA of a specific service can be set by a predefined policy. In addition, since the network slice must be able to freely set the service area according to the slice user's request in any region, the amount of wireless PRB resources that can be set in the network may vary depending on the slice service operation region for the same performance requirements. there is. For example, a situation may occur in which resource use efficiency is reduced by reserving more PRB resources compared to the required performance. For example, a situation may arise in which required performance cannot be met by reserving insufficient PRB resources. To prevent the above-mentioned situations, optimal PRB resource allocation must be calculated from the slice creation process.

In the following specification, an algorithm for calculating the amount of wireless PRB resources per slice required to create a slice that guarantees a transmission rate per slice, which is a representative SLA item related to NSaaS, may be proposed. For example, to calculate the amount of radio resources, an algorithm can be proposed that can reflect the characteristics of the slice service area for the same SLA requirements by using network traffic statistics of the service area in which the slice will be created. A process between slice management functions according to the 3GPP standard to reflect the proposed algorithm may be proposed along with the algorithm.

According to one embodiment, the RAN network slice subnet management function (NSSMF) sets the DL/UL throughput per slice among the GST attributes as an SLA requirement for the network slice. An algorithm for converting the PRB portion of the constituting cell may be proposed.

According to one embodiment, for the service area among the characteristic items of GST as a requirement for creating a network slice, in the RAN NSSMF, the service for which a slice will be created from EMS (or network function management function (NFMF)) A process for obtaining a cell list corresponding to an area may be proposed.

According to one embodiment, a process for obtaining statistics of the network in operation for the acquired cell list and calculating the spectral efficiency by the RAN NSSMF based on the PRB usage rate and transmission volume statistics for each cell will be proposed. You can.

According to one embodiment, an operation of calculating the amount of radio PRB resources of a cell to form a slice in RAN NSSMF using the calculated frequency use efficiency, and the calculated value defined in resourceSharingLevel among the NRM characteristic items according to the 3GPP standard A process for performing an operation to select the function of the gNB scheduler to guarantee the per-slice transmission rate requirement SLA can be proposed by reflecting the value in the common resource pool or dedicated resource pool.

FIG. 2 illustrates operating procedures of a plurality of management functions included in a network slicing management system according to an embodiment.

Referring to FIG. 2, within the network slicing management system of the 3GPP standard, a plurality of management functions may be configured for interpreting the SLA of a slice and setting it as a network parameter. For example, the plurality of management functions include a communication service management function (CSMF) 220, a network slice management function (NSMF) 230, a RAN network slice subnet management function (NSSMF) 240, and a network function management (NFMF). function) (or EMS (element management system)) 250.

A plurality of management functions based on 3GPP specifications can identify (or interpret) slice characteristic items for SLA based on 5G NRM defined in 3GPP specifications (e.g., 3GPP TS 28.541). A plurality of management functions may use information obtained based on identifying slice characteristic items for an SLA to create a profile and deliver (or transmit, provide) the generated profile to the network infrastructure. A user (or customer) using a slice can select characteristic items of the service the user wishes to operate through the slice Service Portal (210). For example, users using slices can directly set (or define) values (or numbers) for the service provision environment. For example, a user using a slice can determine the value (or numerical value) for the service provision environment based on consultation with the slice provider or network operator.

Based on the user using the slice setting (or determining) values for the service provision environment, the NEST (or the NEST of the user using the slice) may be set. The NEST of a user using a slice may be delivered (or transmitted) to the CSMF 220 (communication service management function).

Hereinafter, NEST can be described as including the service area in which the slice will be operated, per-slice transmission rate characteristic items, and requirements for creating a user-only slice that does not share network resources with other slices in operation. However, it is not limited to this. Depending on the embodiment, when a slice service area is not designated, a slice may be created in the entire network and network resources may be shared with other slices.

According to one embodiment, the CSMF (220) organizes the NEST information into a list that can be processed in a management area based on 3GPP standards in the form of a ServiceProfile and delivers (or transmits) it to the NSMF (230) (Network Slice Management Function). You can. NSMF 230 may receive ServiceProfile from CSMF 220.

By interpreting (or processing) the ServiceProfile, the NSMF 230 decomposes the ServiceProfile into RAN SliceProfile, CN SliceProfile, and TN SliceProfile, which are the requirements of each network domain (e.g., RAN, CN, TN) for slice creation. (or can be distinguished). NSMF 230 can create an End-to-End SliceProfile by mapping the RAN SliceProfile, CN SliceProfile, and TN SliceProfile to the End-to-End Slice Index (e.g., S-NSSAI, PLMN ID). NSMF 230 may retain (or store) the created End-to-End SliceProfile. The NSMF 230 may deliver (or transmit) the created SliceProfile for each domain to the Network Slice Subnet Management function (NSSMF) that manages each network domain.

According to one embodiment, the NSMF 230 may convert the service area, which is a slice characteristic item, into coverageAreaTAList and the data rate per slice into ThptPerSliceSubnet, and then deliver (or transmit) them to the RAN NSSMF 240. For example, coverageAreaTAList may be a list of tracking area identities (TAIs) to indicate slice service coverage. For example, in order to generate a user-only slice, the NSMF 230 may map non-shared to the resourceSharing Level attribute item so as not to share network resources with other previously created slices. The NSMF 230 may deliver (or transmit) the resourceSharing Level attribute item mapped as non-shared to the RAN NSSMF 240.

Embodiments described below may relate to a distribution process of RAN resources to satisfy per-slice data rate attribute items. Accordingly, an embodiment in which the slice profile for each domain classified by the NSMF 230 is transmitted to the RAN NSSMF 240 can be described.

According to one embodiment, the RAN NSSMF 240 may receive attribute items of the RAN slice profile from the NSMF 230. The attribute items of the RAN slice profile delivered to the RAN NSSMF (240) can be converted into parameters that can be set in the network infrastructure.

According to one embodiment, the transmission rate per slice can be converted to wireless PRB resources of RAN. An embodiment for identifying the amount of radio PRB resources in RAN based on the transmission rate per slice can be described below.

Figure 3 is a diagram showing network capacity according to one embodiment.

Referring to FIG. 3, the transmission rate per slice, which is a GST characteristic item, may mean the network capacity of one logical network called a slice. Within a communications network, network capacity refers to the total amount of frequency resources owned (or acquired) by a communications service provider (allocated spectrum), and spectral efficiency, which indicates how efficiently data can be transmitted by utilizing the possessed frequency resources. ), and can be expressed as the sum of the number of cells, which are the infrastructure installed within the telecommunications carrier network.

For example, a communication network operator can operate a network by receiving multiple frequencies. Since characteristics may differ depending on the allocated frequency band, the antenna shape, number of operating cells, and installation environment of the base station installed for each frequency band may vary depending on the operation policy of the network operator. Therefore, frequency use efficiency may vary for each frequency band. According to the above-described characteristics, network capacity can be set as in Equation 1.

Referring to Equation 1, network capacity is the total amount of frequency resources (quantity of spectrum), cell spectral efficiency, and number of cells within the frequency band allocated within the service area. It is calculated as the sum of the products. For example, the unit of network capacity is [bit/s]. The unit of the total amount of frequency resources is [Hz]. The unit of cell frequency usage efficiency is [bit/s/Hz].

According to one embodiment, network capacity may be converted (or expressed) into a network slice, which is one logical network. For example, the transmission rate per slice, which is a GST characteristic item, can be expressed as a combination of the amount of resources for each frequency band and the frequency use efficiency for each cell within the service area that will support the slice. According to the above-described characteristics, the transmission rate per slice can be set as shown in Equation 2.

Referring to Equation 2, throughput per slice is identified based on the product of the total amount of frequency resources (quantity of spectrum) and cell spectral efficiency.

According to Equation 2, if the frequency use efficiency of individual cells included in the service area that needs to support slices can be obtained, the PRB portion, which is the quantity of spectrum_i for each frequency band to achieve the transmission rate per slice, is identified. (or can be calculated). Additionally, the PRB portion for each frequency band may be associated with the resource pool for each slice of the gNB scheduler to guarantee the transmission rate requirements of the RAN slice.

Below, an embodiment for identifying (or calculating) the frequency use efficiency of a cell included in a service area to generate a slice may be described.

According to one embodiment, frequency use efficiency may be identified (or calculated) by a combination of information (e.g., statistical indicators) collected from a telecommunications service provider network. Referring to Equation 2, frequency use efficiency refers to the transmission rate per unit used frequency. The transmission rate per unit used frequency can be set as in Equation 3.

Equation 3 represents Cell SE when subcarrier spacing of 15 kHz is used, based on frequency division duplex (FDD). Cell SE indicates frequency use efficiency for each cell. The unit of Cell SE is [bps/Hz]. Volume represents the amount of data transmitted per cell per unit time. The unit of Volume is [GB (gigabyte)]. PRB Usage is an hourly statistic that represents the PBR usage rate for each cell. The unit of PRB Usage is [%]. MaxPRB represents the maximum number of PRBs available in a cell. For example, if subcarrier spacing is 15 kHz, MaxPRB may be 100 in a frequency bandwidth of 20 MHz. For example, if subcarrier spacing is 15 kHz, MaxPRB may be 50 in a frequency bandwidth of 10 MHz. In Equation 3, 3600 represents 3600 seconds. 12 indicates the number of subcarrier spacing per RB. 15000 represents 15 kHz, which is the size of subcarrier spacing.

According to one embodiment, when the frequency use efficiency for each cell is identified according to Equation 3, the amount of resources required for each frequency band to achieve the data rate SLA per slice can be identified according to Equation 2. Based on the amount of resources required for each frequency band, a slice-only PRB resource allocation ratio (PRB Portion) can be identified according to the ratio with the operating frequency bandwidth. Depending on the embodiment, when the bandwidth for each operating frequency is different, the slice-only PRB resource allocation ratio (PRB Portion) may be identified (or calculated) by distributing the per-slice transmission rate SLA by frequency the same as the bandwidth ratio.

An example in which PRB Portion is identified for each slice according to the above-described process can be described in Table 2.

Referring to Table 2, telecommunication operators can operate networks (e.g. 5G networks) in two frequency bands: 1800 MHz (megahertz) and 850 MHz, with bandwidths of 10 MHz and 20 MHz, respectively. Telecommunications operators can operate 10,000 cells per frequency. For example, a telecommunications provider may provide a service with a 10 MHz bandwidth in the 1800 MHz frequency band. Telecommunications operators can operate 10,000 cells to provide services in the 1800 MHz frequency band. Telecommunications operators can provide services with a bandwidth of 20 MHz in the 850 MHz frequency band. Telecommunications operators can operate 10,000 cells to provide services in the 850 MHz frequency band. The average frequency use efficiency of cells within the 1800 MHz frequency band can be identified as 2.0 bps/Hz, based on network operation history. The average frequency use efficiency of cells within the 850 MHz frequency band can be identified as 1.6 bps/Hz, based on network operation history. The communication service provider can agree with the user to create a slice exclusively for the user (or client). Carriers can agree with users to guarantee a per-slide data rate of 150 Gbps for user-dedicated slices.

For example, the transmission rate per slice may be distributed (or set) in proportion to each frequency bandwidth. As an example, in the 850 MHz band, the required data rate may be set to 100 Gbps. In the 18000 MHz band, the required transmission rate can be set to 50 Gbps.

Based on Equation 2, the required amount of resources for each frequency band can be identified. For example, in the 850 MHz band, the required resource amount may be identified (or calculated) as 6.25 MHz. In the 1800 MHz band, the required resource amount can be identified (or calculated) as 2.5 MHz.

Based on the amount of resources required for each frequency band, a PRB portion can be identified. For example, in the 850 MHz band, the PRB portion can be identified as 31.25% (or 6.25/20). In the 1800 MHz band, the PRB portion can be identified as 25% (or 2.5/10).

Based on the PRB portion, the number of PRBs allocated for each frequency can be identified. For example, the number of PRBs allocated in the 850 MHz band may be identified as 32. The number of PRBs allocated in the 1800 MHz band can be identified as 13. To meet the per-slice requirements, 32 PRBs in the 850 MHz band can be dedicated to the slice served, and 13 PRBs in the 1800 MHz band can be dedicated to the slice served.

According to the above, in the slice management system, an embodiment in which requirements regarding the service area, transmission rate per slice, and whether to create a dedicated slice are created as a RAN slice profile, and a wireless parameter that can be set in the network to satisfy the requirements. An example for calculating the amount of PRB resources has been described. Below, an embodiment in which the RAN NSSMF identifies parameters for RAN operation based on the RAN slice profile can be described.

Figure 4 shows an example of the operation of a RAN network slice subnet management function (NSSMF) and network function management function (NFMF), according to an embodiment.

Referring to FIG. 4, the RAN NSSMF, which has received (or received) a RAN slice profile, based on the operation statistics of the current network in order to create a slice that can satisfy the requirements of the slice user expressed in characteristic items, RAN slice profile can be converted into parameters for RAN operation.

In operation 410, the RAN NSSMF transmits (or delivers) a tracking area ID list to the NFMF (or ENS) or inventory storing network information to obtain a list of cells included in the tracking area corresponding to the service area. You can. RAN NSSMF can request a list of cells included in the tracking area along with a list of tracking area IDs.

In operation 420, the RAN NSSMF may receive a list of cells included in the tracking area from the NFMF.

In operation 430, the RAN NSSMF may request the NFMF (or EMS) for PRB usage rate and transmission volume statistics per unit time for each cell for the received cell list. For example, RAN NSSMF is a configurable parameter of the RAN domain that can satisfy the per-slice transmission rate requirement, and is used to identify the PRB portion of the cell for each frequency band within the service area, the PRB utilization rate for each cell for the received cell list, and You can request transmission volume statistics per unit time from NFMF (or EMS).

In operation 440, the RAN NSSMF may receive PRB usage rate per cell and transmission volume statistics per unit time for the cell list received from the NFMF (or EMS).

In operation 450, the RAN NSSMF may identify the amount of resources required for each frequency band. For example, RAN NSSMF can identify (or calculate) the frequency use efficiency for each cell using Equation 3 described above, based on the PRB usage rate for each cell and the transmission volume statistics per unit time for the received cell list. . RAN NSSMF can identify (or calculate) the amount of PRB resources required for each band to satisfy the transmission rate per slice using Equation 2 described above, based on the frequency use efficiency for each cell.

In operation 460, the RAN NSSMF provides the amount of PRB resources required for each identified band to the base station in the cell list within the service area through NFMF (or EMS) in order to create a slice to satisfy the user's requirements in the network infrastructure. You can request to reserve a PRB portion so that it can be used for slicing.

According to the above, for the operation of RAN slices, the gNB scheduler shares the radio resource division method and resource pool to allocate dedicated radio resources according to the isolation degree of inter-slice resources, but preempts inter-slice resources within the shared resource pool. By specifying the priority, at least one of the priority-based scheduling methods in which the specified priority is used for resource allocation can be used. According to one embodiment, the gNB scheduler may use both a radio resource partitioning method and a priority-based scheduling method according to the network operator's resource operation policy.

Below, when the RAN slice profile includes a transmission rate per slice within the service area determined by the user's SLA requirements, an embodiment for NFMF (or EMS) to reflect the transmission rate per slice in the network infrastructure can be described.

Figure 5 shows an example of NFMF operation according to a RAN slice profile (Slice Profile) according to an embodiment.

Referring to FIG. 5, NSSMF can identify the amount of wireless PRB resources to satisfy the data rate per slice based on the RAN domain slice profile. For example, the RAN domain slice profile may include information about the target slice (eg, Slice #3), service area, and data rate per slice.

According to one embodiment, NFMF (or EMS) may operate in one of cases 510 to 530. Cases 510 to 530 are intended to explain an example in which PRB resources are allocated when at least one of the priority-based scheduling function and the radio resource division function is used, but are not limited thereto.

In case 510, the NSSMF may set the resourceSharingLevel characteristic item of the RAN slice profile to shared and transmit the RAN slice profile to the NFMF (or EMS). Depending on the embodiment, the RAN slice profile may further include an RRMPolicyRatio characteristic item. NFMF (or EMS) can additionally allocate the identified wireless PRB resource amount to the operating common resource pool. The common resource pool can be increased by the amount of identified wireless PRB resources. NFMF (or EMS) can grant each slice priority for use of the common resource pool, depending on the inter-slice priority in the increased resource pool. For example, the priority of Slice #1 may be set to 1. The priority of Slice #2 can be set to 2. The priority of Slice #3 can be set to 3. NFMF (or EMS) may grant priority for use of the common resource pool in the order of Slice #1, Slice #2, and Slice #3.

In case 520, the NSSMF may set the resourceSharingLevel characteristic item of the RAN slice profile to non-shared and transmit the RAN slice profile to the NFMF (or EMS). Depending on the embodiment, the RAN slice profile may further include an RRMPolicyRatio characteristic item. NFMF (or EMS) can create a dedicated resource pool for the slice being created. NFMF (or EMS) can be set so that the traffic of users using services based on the created slice is operated within the created dedicated resource pool.

In case 530, when the NFMF (or EMS) operates both a common resource pool and a dedicated resource pool, operating resources for a new slice according to the slice user's resource sharing requirements described in the resourceSharingLevel characteristic item. This can be identified.

For example, when both a common resource pool and a dedicated resource pool are operated, the amount of wireless PRB resources identified in the operating common resource pool may be additionally allocated for a new slice, based on the resourceSharingLevel property being set to shared. .

For example, when both the common resource pool and the dedicated resource pool are operated, a dedicated resource pool according to the amount of identified wireless PRB resources can be additionally allocated for a new slice, based on the resourceSharingLevel property being set to non-shared. there is.

According to the above-described embodiments, when the slice user's requirement includes the transmission rate per slice within the service area, the wireless PRB resource of the cell in which the slice will be created can be identified based on the transmission rate per slice. By applying the wireless PRB resources of the cell in which the slice will be created to the network, a framework for configuring a slice network that satisfies the user's required SLA can be provided.

According to the above-described embodiments, the area of the service to be provided through the slice may be identified as a cell list. Based on the identified cell list, the optimal amount of wireless PRB resources required to satisfy the per-slice transmission rate requirement, which is a characteristic item of the service, can be identified.

According to the above-described embodiments, the SLA of the individual slice service can be guaranteed based on the identified wireless PRB resource amount. Radio resource allocation operations may be performed so as not to affect performance or operation between different slices.

According to the above-described embodiments, operation procedures between network management systems are defined to interpret user requirements and configure network parameters accordingly, so that network parameters that can satisfy a specific SLA can be manually set by the operator. According to the above-described embodiments, when parameter values are set based on a predefined manual, network performance degradation can be prevented.

Figure 6 shows a flowchart of the operation of a network slice (NS) management device according to an embodiment.

Referring to FIG. 6, in operation 610, a processor (hereinafter referred to as processor) of a network slice (NS) management device may obtain RAN slice profile information. According to one embodiment, the processor may obtain RAN slice profile information corresponding to attribute information of the NS service. The attribute information of the NS service may include at least one of guaranteed data rate information per slice, NF selection assistance information, and network communication network ID (identifier) information.

According to one embodiment, the NS management device may include a RAN NSSMF. According to one embodiment, the NS management device may perform a function for managing the RAN network slice subnet.

According to one embodiment, RAN slice profile information may be obtained based on service profile information corresponding to attribute information of the NS service.

According to one embodiment, a communication service management device (eg, CSMF) may obtain service profile information based on NS type (eg, NEST). As an example, service profile information may be created by a communication service management device based on NS type.

According to one embodiment, the communication service management device may transmit service profile information to another device for NS management (eg, NSMF). Another device for NS management may obtain RAN slice profile information based on service profile information. As an example, service profile information may be divided into slice profile information regarding a plurality of network domains. Slice profile information regarding a plurality of network domains may include core network (CN) slice profile information, the RAN slice profile information, and transport network (TN) slice profile information.

According to one embodiment, another device for NS management may transmit RAN slice profile information to the device for NS management. The processor of the device for NS management can obtain RAN slice profile information.

At operation 620, the processor may receive a statistics message from the NF management device. According to one embodiment, the processor may receive a statistical message containing statistical information about a plurality of cells in a coverage area for providing NS services from a network function (NF) management device.

According to one embodiment, the RAN slice profile information may include resource sharing information between slices, guaranteed transmission rate information within a subnet regarding the slice, and coverage information for providing NS services.

According to one embodiment, the processor may request information about cells constituting the coverage area from the NF management device based on coverage information included in the RAN slice profile information. The processor may receive a list of a plurality of cells in the coverage area from the NF management device based on the request. According to one embodiment, the processor may receive a list of a plurality of cells included in the coverage area from the NF management device. The processor may request a statistics message from the NF management device based on the list of multiple cells. The processor may receive a statistics message from the NF management device based on requesting the statistics message from the NF management device.

According to one embodiment, the statistics message may include statistical information about a plurality of cells in a coverage area for providing NS services. Statistical information about a plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. PRB usage information may include, for each cell, information on the ratio of PRBs used for wireless communication within the cell among available RPBs.

At operation 630, the processor may identify, for each cell, the PRB ratio allocated for the NS service. According to one embodiment, the processor may identify the PRB ratio allocated for the NS service for each cell, based on RAN slice profile information and statistics messages.

According to one embodiment, the processor may identify the PRB ratio allocated for the NS service for each cell based on RAN slice profile information, data amount per unit time, and PRB usage information. According to one embodiment, the processor may identify frequency use efficiency information for each cell based on a statistical message including RAN slice profile information, data amount per unit time, and PRB usage information. The processor can identify frequency use efficiency information for each cell using Equation 3.

The processor may identify the PRB ratio allocated for the NS service for each cell based on frequency use efficiency information. The processor can use Equation 2 to identify the PRB ratio allocated for the NS service for each cell.

In operation 640, the processor may transmit a configuration request message to the NF management device. According to one embodiment, the processor may transmit a configuration request message for resource allocation of the NS service to the NF management device based on the PRB ratio. According to one embodiment, the configuration request message may include resource sharing information between slices. Resource sharing information between slices included in the configuration request message may correspond to resource sharing information between slices included in RAN slice profile information. Resource sharing information between slices includes a first value (e.g., a value indicating non-shared) for allocating a dedicated resource pool for the NS service and a second value (e.g., a value indicating non-shared) for setting a shared resource pool for the NS service. : value representing shared) can be set to one of the following.

According to one embodiment, the processor may cause the NF management device to perform radio resource management for the NS service based on sending a configuration request message to the NF management device.

Figure 7 shows a flowchart of the operation of a network function (NF) management device according to an embodiment.

Referring to FIG. 7 , in operation 710, a processor (hereinafter referred to as processor) of a network function (NF) management device may transmit a statistics message to the NS management device. According to one embodiment, the processor may receive a request for information on cells constituting the identified coverage area based on coverage information included in the RAN slice profile information from the NS management device. Based on the request, the processor may transmit a list of a plurality of cells in the coverage area to the NS management device. According to one embodiment, the processor may transmit a list of a plurality of cells included in the coverage area to the NS management device. The processor may transmit a list of a plurality of cells and then receive a request for a statistics message from the NS management device. The processor may transmit the statistics message to the NS management device based on the request for the statistics message.

For example, the statistics message may include statistical information about a plurality of cells in a coverage area for providing NS services. Statistical information about a plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. PRB usage information may include, for each cell, information on the ratio of PRBs used for wireless communication within the cell among available RPBs.

At operation 720, the processor may receive a setup request message from the NS management device. According to one embodiment, the processor may receive a configuration request message for resource allocation of NS service from the NS management device based on the statistics message.

In operation 730, the processor may perform radio resource management for the NS service based on the PRB rate identified through the setup request message.

According to one embodiment, the configuration request message may include resource sharing information between slices. Resource sharing information between slices included in the configuration request message may correspond to resource sharing information between slices included in RAN slice profile information. Resource sharing information between slices includes a first value (e.g., a value indicating non-shared) for allocating a dedicated resource pool for the NS service and a second value (e.g., a value indicating non-shared) for setting a shared resource pool for the NS service. It can be set to one of the values representing shared.

According to one embodiment, the processor may identify that resource sharing information is set to a first value. Based on identifying that the resource sharing information is set to the first value, the processor may set a dedicated resource pool for each cell according to the radio resource partitioning function and according to the PRB ratio for the NS service.

According to one embodiment, the processor may identify that resource sharing information is set to a second value. The processor sets the shared resource pool and the priority of the shared resource pool for each cell, according to the PRB ratio, according to priority half scheduling, based on identifying that the resource sharing information is set to the second value. You can.

According to one embodiment, the processor may identify allocatable resources for each cell based on the configuration request message. The processor may transmit a feedback message indicating a lack of allocable resources to the NS management device based on identifying that the size of the allocable resource is less than the size of the resource identified based on the identified PRB ratio.

In embodiments of the present disclosure, a technology for mapping attribute information (e.g., service attributes of GMSA) to resource management parameters defined in the 3GPP standard is described by RAN NSSMF, NFMF, and NSMF. Operations for the mapping may be performed by various functions (e.g., RAN NSSMF, NFMF, or NSMF) within operations support systems (OSS). The above operations may be implemented as software in a specific device (eg, server) or as separate hardware devices. A device for performing the above-described operations may include a communication unit, a control unit, and a storage unit.

According to one embodiment, the communication unit provides an interface for communicating with other devices in the network. That is, the communication unit converts a bit string transmitted from an entity of the core network to another entity into a physical signal, and converts a physical signal received from another device into a bit string. That is, the communication unit can transmit and receive signals. Accordingly, the communication unit may be referred to as a modem, a transmit unit, a receive unit, or a transmit/receive unit. At this time, the communication unit allows the core network device to communicate with other devices or systems through a backhaul connection (e.g., wired backhaul or wireless backhaul) or through the network. The communication unit may include one or more transceivers. According to one embodiment, the communication unit of the RAN NSSMF may receive a statistics message from the communication unit of the NSMF (or EMS).

According to one embodiment, the storage unit stores data such as basic programs, application programs, and setting information for the operation of the core network device. The storage unit may be comprised of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. And, the storage unit provides stored data according to the request of the control unit.

According to one embodiment, the control unit controls overall operations of the core network device. For example, the control unit transmits and receives signals through the communication unit. Additionally, the control unit records and reads data from the storage unit. For this purpose, the control unit may include at least one processor. According to various embodiments, the controller may control the device to perform operations according to various embodiments described in this disclosure.

According to one embodiment, a method performed by a network slice (NS) management device in a wireless communication system may include obtaining radio access network (RAN) slice profile information corresponding to attribute information of the NS service. . The method may include receiving, from a network function (NF) management device, a statistical message containing statistical information about a plurality of cells in a coverage area for providing NS services. The statistical information about the plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. The method may include an operation of identifying a PRB ratio allocated for the NS service for each cell, based on the RAN slice profile information and the statistics message. The method may include transmitting a configuration request message for resource allocation of the NS service to the NF management device, based on the ratio of the PRB.

According to one embodiment, the attribute information of the NS service may include at least one of guaranteed data rate information per slice, NF selection assistance information, and network communication network ID (identifier) information.

According to one embodiment, the RAN slice profile information may be obtained based on service profile information corresponding to attribute information of the NS service.

According to one embodiment, the service profile information may be divided into slice profile information regarding a plurality of network domains. The slice profile information regarding the plurality of network domains may include core network (CN) slice profile information, the RAN slice profile information, and transport network (TN) slice profile information.

According to one embodiment, the service profile information may be generated by the communication service management device based on NS type.

According to one embodiment, RAN slice profile information may include resource sharing information between slices, guaranteed transmission rate information within a subnet for the slice, and coverage information for providing the NS service.

According to one embodiment, the method may include requesting information about cells constituting the coverage area from the NF management device, based on the coverage information included in the RAN slice profile information. there is. The method may include receiving a list of the plurality of cells in the coverage area from the NF management device based on the request. The method may include requesting the statistics message from the NF management device based on the list of the plurality of cells.

According to one embodiment, the setup request message may include resource sharing information between the slices. Resource sharing information between the slices may be set to one of a first value for setting a dedicated resource pool for the NS service and a second value for setting a shared resource pool for the NS service.

According to one embodiment, the PRB usage information may include, for each cell, information on the ratio of PRBs used for wireless communication within the cell among available PRBs.

According to one embodiment, the method may include identifying frequency use efficiency information for each cell based on the RAN slice profile information and the statistical message. The method may include an operation of identifying the PRB ratio allocated for the NS service for each cell, based on the frequency use efficiency information.

According to one embodiment, a method performed by a network function (NF) management device in a wireless communication system includes coverage for providing NS services based on a request for a statistics message received from a network slice (NS) management device. It may include transmitting the statistical message containing statistical information about a plurality of cells in the area to the NS management device. The statistical information about the plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. Based on the statistical message, it may include receiving a configuration request message for resource allocation of NS service from the NS management device. The method may include performing radio resource management (RRM) for the NS service based on the PRB rate identified through the setup request message.

According to one embodiment, the setup request message may include resource sharing information between slices. Resource sharing information between the slices may be set to one of a first value for allocating dedicated resources for the NS service and a second value for allocating common resources for the NS service.

According to one embodiment, the method may include an operation of identifying that the resource sharing information is set to the second value based on the setting request message. The method is based on identifying that the resource sharing information is set to the second value, and according to priority-based scheduling, for each cell, a shared resource pool according to the PRB ratio and the It may include an operation of setting the priority of the shared resource according to the PRB ratio.

According to one embodiment, the method may include an operation of identifying that the resource sharing information is set to the first value. The method is configured to create, for each cell, a dedicated resource pool according to the PRB ratio for the NS service, according to a radio resource partitioning function, based on identifying that the resource sharing information is set to the first value. It may include an operation to set up a (pool).

According to one embodiment, the method may include an operation of identifying allocatable resources for each cell based on the configuration request message. The method transmits a feedback message indicating that the allocable resource is insufficient to the NS management device based on identifying that the size of the allocable resource is smaller than the size of the resource identified based on the PRB ratio. It may include actions such as:

According to one embodiment, a network slice (NS) management device in a wireless communication system includes at least one processor and a transceiver, and the at least one processor is a radio access network (RAN) corresponding to attribute information of the NS service. ) Can be set to obtain slice profile information. The at least one processor may be configured to receive a statistical message containing statistical information about a plurality of cells in a coverage area for providing NS services from a network function (NF) management device. The statistical information about the plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. The at least one processor may be configured to identify a PRB ratio allocated for the NS service for each cell, based on the RAN slice profile information and the statistical message. The at least one processor may be configured to transmit, to the NF management device, a configuration request message for resource allocation of the NS service, based on the ratio of the PRB.

According to one embodiment, the attribute information of the NS service may include at least one of guaranteed data rate information per slice, NF selection assistance information, and network communication network ID (identifier) information.

According to one embodiment, the service profile information may be divided into slice profile information regarding a plurality of network domains. The slice profile information regarding the plurality of network domains may include core network (CN) slice profile information, the RAN slice profile information, and transport network (TN) slice profile information.

According to one embodiment, RAN slice profile information may include resource sharing information between slices, guaranteed transmission rate information within a subnet for the slice, and coverage information for providing the NS service.

According to one embodiment, a network function (NF) management device in a wireless communication system may include at least one processor and a transceiver. The at least one processor, based on a request for the statistics message received from an NS (network slice) management device, sends the statistics message containing statistical information about a plurality of cells in a coverage area for providing NS services, It can be set to transmit to the NS management device. The statistical information about the plurality of cells may include, for each cell, the amount of data per unit time and PRB usage information. The at least one processor may be configured to receive a configuration request message for resource allocation of NS services from the NS management device, based on the statistics message. The at least one processor may be configured to perform radio resource management (RRM) for the NS service based on the PRB rate identified through the configuration request message.

Electronic devices according to various embodiments disclosed in this document may be of various types. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

The various embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various changes, equivalents, or replacements of the embodiments. In connection with the description of the drawings, similar reference numbers may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the above items, unless the relevant context clearly indicates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one element from another, and may be used to distinguish such elements in other respects, such as importance or order) is not limited. One (e.g. first) component is said to be "coupled" or "connected" to another (e.g. second) component, with or without the terms "functionally" or "communicatively". Where mentioned, it means that any of the components can be connected to the other components directly (e.g. wired), wirelessly, or through a third component.

In various embodiments of this document, the term "module" used may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as logic, logic block, component, or circuit, for example. It can be used as A module may be an integrated part or a minimum unit of the parts or a part thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of this document are one or more instructions stored in a storage medium (e.g., built-in memory 136 or external memory 138) that can be read by a machine (e.g., electronic device 101). It may be implemented as software (e.g., program 140) including these. For example, a processor (e.g., processor 120) of a device (e.g., electronic device 101) may call at least one command among one or more commands stored from a storage medium and execute it. This allows the device to be operated to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves). This term refers to cases where data is stored semi-permanently in the storage medium. There is no distinction between temporary storage cases.

According to one embodiment, methods according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products are commodities and can be traded between sellers and buyers. A computer program product may be distributed in the form of a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)), or through an application store (e.g. Play Store), or on two user devices (e.g. : Smartphones) can be distributed (e.g. downloaded or uploaded) directly or online. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to various embodiments, each component (e.g., module or program) of the above-described components may include a single or plural entity, and some of the plurality of entities may be separately placed in other components. . According to various embodiments, one or more of the components or operations described above may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component of the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or , or one or more other operations may be added.

Claims (20)

In a method performed by a network slice (NS) management device in a wireless communication system,
An operation of acquiring RAN (radio access network) slice profile information corresponding to attribute information of an NS service,
An operation of receiving, from an NF (network function) management device, a statistical message containing statistical information about a plurality of cells in a coverage area for providing NS services, wherein the statistical information about the plurality of cells is for each cell. , Contains data amount per unit time and PRB (physical resource block) usage information,
An operation of identifying a PRB ratio allocated for the NS service for each cell, based on the RAN slice profile information and the statistics message, and
Based on the ratio of the PRB, transmitting a configuration request message for resource allocation of the NS service to the NF management device.
method.
The method of claim 1, wherein the attribute information of the NS service is:
Containing at least one of guaranteed transmission rate information per slice, NF selection assistance information, and network communication network ID (identifier) information.
method.
The method of claim 1, wherein the RAN slice profile information is:
Obtained based on service profile information corresponding to the attribute information of the NS service
method.
The method of claim 3, wherein the service profile information is:
Divided into slice profile information about a plurality of network domains,
Slice profile information regarding the plurality of network domains is:
Containing core network (CN) slice profile information, the RAN slice profile information, and transport network (TN) slice profile information.
method.
The method of claim 3, wherein the service profile information is:
Based on the NS type, generated by the communication service management device,
method.
The method of claim 1, wherein the RAN slice profile information is:
Contains resource sharing information between slices, guaranteed transmission rate information within a subnet for the slice, and coverage information for providing the NS service.
method.
According to clause 6,
An operation of requesting information about cells constituting the coverage area from the NF management device based on the coverage information included in the RAN slice profile information, and
Based on the request, receiving a list of the plurality of cells in the coverage area from the NF management device, and
Based on the list of the plurality of cells, further comprising requesting the statistics message from the NF management device.
method.
The method of claim 6, wherein the setting request message is:
Contains resource sharing information between the slices,
Resource sharing information between the slices is,
Set to one of a first value for setting a dedicated resource pool for the NS service and a second value for setting a shared resource pool for the NS service.
method.
The method of claim 1, wherein the PRB usage information is:
For each cell, among the available PRBs, it contains information on the ratio of PRBs used for wireless communication within the cell.
method.
According to claim 1,
An operation of identifying frequency use efficiency information for each cell based on the RAN slice profile information and the statistical message, and
Based on the frequency use efficiency information, for each cell, further comprising the operation of identifying the PRB ratio allocated for the NS service.
method.
In a method performed by a network function (NF) management device in a wireless communication system,
Based on a request for a statistics message received from a network slice (NS) management device, transmitting to the NS management device the statistics message containing statistical information about a plurality of cells in a coverage area for providing NS services. Operation, the statistical information about the plurality of cells includes, for each cell, data amount per unit time and PRB (physical resource block) usage information,
An operation of receiving a configuration request message for resource allocation of NS services from the NS management device based on the statistics message, and
Including the operation of performing radio resource management (RRM) for the NS service based on the PRB rate identified through the setup request message.
method.
The method of claim 11, wherein the setting request message is:
Further includes resource sharing information between slices,
The resource sharing information between the slices is set to one of a first value for allocating dedicated resources for the NS service and a second value for allocating common resources for the NS service.
method.
According to claim 12,
An operation of identifying that the resource sharing information is set to the second value based on the setting request message, and
Based on identifying that the resource sharing information is set to the second value, according to priority-based scheduling, for each cell, a shared resource pool according to the PRB ratio and according to the PRB ratio Further comprising the operation of setting the priority of the shared resource
method.
According to claim 12,
An operation of identifying that the resource sharing information is set to the first value, and
Based on identifying that the resource sharing information is set to the first value, for each cell, according to the radio resource partitioning function, a dedicated resource pool is created according to the PRB ratio for the NS service. Contains more actions to set
method.
According to claim 11,
An operation of identifying allocatable resources for each cell, based on the setup request message, and
Based on identifying that the size of the allocable resource is smaller than the size of the resource identified based on the PRB ratio, transmitting a feedback message indicating that the allocable resource is insufficient to the NS management device. containing
method.
In a network slice (NS) management device in a wireless communication system,
at least one processor, and
comprising a transceiver, wherein the at least one processor includes:
Obtain RAN (radio access network) slice profile information corresponding to the attribute information of the NS service,
A statistical message containing statistical information about a plurality of cells in a coverage area for providing NS services is received from an NF (network function) management device, and the statistical information about the plurality of cells is for each cell, Contains data amount and PRB usage information per unit time,
Based on the RAN slice profile information and the statistics message, for each cell, identify a PRB ratio allocated for the NS service,
Based on the ratio of the PRB, configured to transmit a configuration request message for resource allocation of the NS service to the NF management device.
NS management device.
The method of claim 16, wherein the attribute information of the NS service is:
Containing at least one of guaranteed transmission rate information per slice, NF selection assistance information, and network communication network ID (identifier) information.
NS management device.
The method of claim 16, wherein the service profile information is:
Divided into slice profile information about a plurality of network domains,
Slice profile information regarding the plurality of network domains,
Containing core network (CN) slice profile information, the RAN slice profile information, and transport network (TN) slice profile information.
NS management device.
The method of claim 16, wherein the RAN slice profile information is:
Contains resource sharing information between slices, guaranteed transmission rate information within a subnet for the slice, and coverage information for providing the NS service.
NS management device.
In a NF (network function) management device in a wireless communication system,
at least one processor, and
Comprising a transceiver, and the at least one processor,
Based on a request for a statistics message received from a network slice (NS) management device, transmitting, to the NS management device, the statistics message containing statistical information about a plurality of cells in a coverage area for providing NS services; , The statistical information about the plurality of cells includes, for each cell, data amount per unit time and PRB (physical resource block) usage information,
Based on the statistical message, a configuration request message for resource allocation of NS service is received from the NS management device,
Based on the PRB rate identified through the setup request message, configured to perform radio resource management (RRM) for the NS service.
NF management device.

Images