KR20240022872A - Method and apparatus for providing network slice based on policy of service provider in wireless communication system - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates. The method of the present disclosure includes receiving a network slice policy management request message from a VAL server; and performing a policy management operation for the network slice based on the policy information included in the policy management request message, wherein the policy management request message may include policy information for the network slice.

Description

Method and device for providing a Network Slice based on the policy of a service provider in a wireless communication system {METHOD AND APPARATUS FOR PROVIDING NETWORK SLICE BASED ON POLICY OF SERVICE PROVIDER IN WIRELESS COMMUNICATION SYSTEM}

This disclosure relates to a wireless communication system, and more specifically to a communication method and device in a wireless communication system supporting network slices.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss in ultra-high frequency bands and increase radio transmission distance. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands. ), NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

In addition, IAB (IAB) provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links. Integrated Access and Backhaul, Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover, and 2-step Random Access (2-step RACH for simplification of random access procedures) Standardization in the field of wireless interface architecture/protocol for technologies such as NR) is also in progress, and a 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence are designed to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, Satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design operation, and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

This disclosure proposes a method and device for providing a Network Slice based on the service provider's policy.

According to an embodiment of the present disclosure, a method of a network slice capability enablement (NSCE) server includes receiving a network slice policy management request message from a vertical application layer (VAL) server, wherein the policy management request message is for a network slice. Contains policy information -; It may include performing a policy management operation for the network slice based on the policy information included in the policy management request message.

According to an embodiment of the present disclosure, a network slice capability enablement (NSCE) server includes a transceiver; and a processor, wherein the processor: receives a network slice policy management request message from a vertical application layer (VAL) server, wherein the policy management request message includes policy information for a network slice, and requests the policy management. Based on the policy information included in the message, it may be configured to perform a policy management operation for the network slice.

Figure 1 shows an example of identification information that distinguishes a network slice according to an embodiment of the present disclosure.
Figure 2 shows an example of a system for providing a network slice to a VAL server at the application layer when providing a vertical application service according to an embodiment of the present disclosure.
Figure 3 is a flowchart showing a network slice management procedure according to an embodiment of the present disclosure.
Figure 4 is a flowchart showing a network slice management procedure according to an embodiment of the present disclosure.
Figure 5 is a flowchart showing a network slice management procedure according to an embodiment of the present disclosure.
FIG. 6 is a diagram showing the configuration of a network entity in a wireless communication system according to an embodiment of the present disclosure.
Figure 7 is a diagram showing the configuration of a terminal in a wireless communication system according to an embodiment of the present disclosure.

In describing the embodiments in the present disclosure, description of technical content that is well known in the technical field to which the present disclosure belongs and that is not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanation.

For the same reason, some components are exaggerated, omitted, or schematically shown in the accompanying drawings.

It will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams may be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operations are performed on the computer or other programmable data processing equipment to generate a process that is executed by the computer and generates a computer or other programmable data. Instructions that perform processing equipment may also provide operations for executing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

* The present disclosure discloses an apparatus and method for providing network slices (or network slicing) in a wireless communication system or mobile communication system. Specifically, this disclosure describes a technology for managing network slice information in a wireless communication system that provides a network slice function. Additionally, interoperability technology between a wireless communication system and a terminal is explained.

In the following description, terms referring to signals, terms referring to channels, terms referring to control information, terms referring to network entities, terms referring to device components, etc. are used for convenience of explanation. This is exemplified. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used.

The present disclosure describes various embodiments using terms used in some communication standards (eg, 3rd Generation Partnership Project (3GPP)), but this is only an example for explanation. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.

In the present disclosure, the network technology may refer to standards defined by the ITU (international telecommunication union) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and may refer to components included in the network structure to be described later. They can refer to physical entities, software that performs individual functions, or hardware combined with software.

3GPP standards standardize the 5G network system architecture and procedures. Mobile communication operators can provide various services in 5G networks. In order to provide each service, mobile communication providers need to satisfy different service requirements for each service (e.g., delay time, communication range, data rate, bandwidth, reliability, etc.). To this end, the 5G system supports network slicing (or it can be referred to as network slice), and traffic for different network slices can be processed by different PDU (protocol data unit) sessions. there is. The PDU session may mean an association between a terminal and a data network that provides a PDU connection service. The network slice logically configures the network as a set of network functions (NF) to support various services with different characteristics such as broadband communication services, massive IoT, and mission critical services such as V2X, etc., It can be understood as a technology to separate different network slices. Therefore, even if a communication failure occurs in a certain network slice, communication in other network slices is not affected, making it possible to provide a stable communication service. To this end, mobile communication providers can configure network slices and allocate network resources suitable for specific services for each network slice or set of network slices. Network resources may mean NF (network function), logical resources provided by NF, or radio resource allocation of a base station.

For example, a mobile communication service provider may configure network slice A to provide mobile broadband services, network slice B to provide vehicle communication services, and network slice C to provide IoT services. In other words, in this 5G network, the service can be efficiently provided to the terminal through a network slice specialized for the characteristics of each service.

With the development of 5G communication systems, network slice (or network slicing) technology has been introduced for radio access network (RAN) and core network (CN) structures.

Wireless communication systems such as 5G systems or mobile communication systems provide network information and network information necessary to provide vertical application services such as automobiles, drones, or smart factories. An enabler layer can be defined for management and supported in 3rd party Vertical Application. The Vertical Application service may be briefly referred to as Application service. Meanwhile, embodiments of the present disclosure are not limited to the Vertical Application service and can be applied to various services that require network slice information.

In the Vertical Application service, the service can be provided by being allocated a network slice provided by the network operator. To this end, a method is needed for an operator (for example, a service provider) wishing to provide a Vertical Application service to convey the network slice requirements required when providing a Vertical Application service to a network operator providing a network slice. A network operator can secure network resources to allocate a network slice that satisfies the above requirements for providing vertical application services and provide a network slice by delivering network slice information to the vertical application. Hereinafter, in the embodiments of the present disclosure, a service provider providing a Vertical Application service and a network provider providing a network slice may each be implemented with at least one server.

In addition, since the network slice requirements for vertical application services must be confirmed by the vertical service provider, it is possible to provide a network slice that satisfies the requirements by defining the network slice requirements and delivering the requirements to the network provider. A method is required for network operators to confirm this. To this end, the concept of 'Network Slice as a Service' is introduced, and a system is required for Vertical Application service providers to check network slice information, request network slice allocation, and manage allocated network slices.

The network slice is identified by an identifier called S-NSSAI (single-network slice selection assistance information) on the network system. The network transmits a set of slices (e.g., allowed NSSAI(s)) allowed to the UE in a UE registration procedure (e.g., UE registration procedure), and the UE transmits one S-NSSAI (i.e., allowed NSSAI(s)) among the allowed NSSAI(s). , application data can be transmitted and received through a PDU session created through a network slice). Specifically, the terminal can be connected to an access network and register in the 5G system. As an example, a terminal can connect to a base station and perform an access and mobility management function (AMF) and a terminal registration procedure. During the registration process, the AMF may determine an allowed network slice (allowed NSSAI) available to the terminal connected to the base station and allocate it to the terminal. The terminal can set up a PDU session for communication with the actual application server through the network slice. One PDU session can include one or multiple QoS (quality of service) Flows, and each QoS Flow can provide different transmission performance required for each application service by setting different quality of service (QoS) parameters. there is.

The network slice is created as a Network Slice Instance from the management system perspective, and the Network Slice Instance is classified by a Dedicated Name (DN).

* On the other hand, in providing Network Slice services, when the period of use of Network Slice is short and frequent, in the conventional method, the ^3rd party service provider (e.g., VAL service provider) makes Allocation each time the use of Network Slice is needed. / A Network Slice was allocated or terminated (deallocated) by sending a De-allocation message. Alternatively, in the conventional method, the Network Slice was initially allocated and the Network Slice was maintained until service provision was completed and the Network Slice was no longer needed.

In the above two cases, the ^3rd party service provider using Network Slice frequently sends and receives Network Slice Allocation / De-allocation messages, causing inconvenience in operation, or network resources may be wasted when receiving and maintaining Network Slice allocation. It can happen.

Accordingly, this disclosure provides a method for enabling/deactivating Network Slice according to policy through a system responsible for storing and managing policies (e.g., time policy) determined by a ^3rd party service provider.

Additionally, as in the case of Massive IoT, this disclosure provides a method that enables activating/deactivating Network Slice with periodicity when providing Network Slice services.

* According to an embodiment of the present disclosure, the NSCE server of the wireless communication system may be configured to perform at least one of the following operations.

- The operation of receiving a Network Slice Policy Management Request message containing the time operation policy determined by the VAL server and sending a response message whether or not it has been received,

- In order for the VAL server to receive notification of whether the Network Slice activation/deactivation operation of the 5GS MnS (Management System) is performed according to the policy of the ^3rd party service provider, the Policy Management Notification subscription Request message is received from the VAL server and a reception response message is sent. action,

- The operation of saving the policy delivered by the VAL server, managing the network slice according to the saved policy, that is, the operation of checking the network slice activation time or activation cycle,

- The operation of sending a Network Slice Allocate Request message (Allocatensi) to the 5GS MnS (Management System) at the time when Network Slice should be activated and receiving a response message whether to perform it,

- After receiving a response message about Network Slice activation from the 5GS MnS, sending a Notification message to the VAL server about whether to activate the Network Slice according to the VAL server's Policy Management Notification Subscription request,

- An operation to check the Network Slice end time or activation duration. When the Network Slice end time or duration is over, that is, when the Network Slice needs to be deactivated, a Network Slice Deallocate Request message (Deallocatensi) is sent to the 5GS MnS and a performance response message is received. movement,

- After receiving a response message about Network Slice deactivation from the 5GS MnS, the operation of sending a Notification message to the VAL server about whether or not the Network Slice is deactivated according to the VAL server's Policy Management Notification Subscription request.

* According to an embodiment of the present disclosure, a Network Slice Capability Enablement (NSCE) server of a wireless communication system may be configured to perform at least one of the following operations.

- The operation of receiving a Network Slice Policy Management Request message containing the time operation policy determined by the VAL server and sending a response message whether or not it has been received,

- The operation of receiving a Policy Management Notification subscription Request message from ^the VAL server and sending a reception response message in order for the VAL server to receive notification of whether the 5GS MnS (Management System) Network Slice activation/deactivation operation is performed according to the 3rd Party service provider policy,

- In order to receive notification from 5GS MnS about whether 5GS MnS (Management System) Network Slice activation/deactivation operation is performed according to the ^3rd Party service provider policy, the NSCE server sends a Policy Management Notification Subscription Request message to 5GS MnS and receives a reception response message. action,

- The operation of saving the ^3rd party service provider policy,

- Action to check the Network Slice start time or start cycle of the ^3rd party service provider policy,

- The operation of sending a Network Slice Allocate Request message to the 5GS MnS according to the Network Slice start time or start cycle according to the ^3rd Party service provider policy and receiving a response message whether Network Slice is activated,

- Action to notify the VAL server whether 5GS MnS Network Slice is activated,

- When the 5GS MnS deactivates the Network Slice due to the end time or duration of the Network Slice in the ^3rd party service provider policy, the operation of receiving the Network Slice deactivation notification from the 5GS MnS and delivering it to the VAL server.

In this embodiment, the 5GS MnS receives a Network Slice Allocate Request message containing a policy on the Network Slice end time and duration from the NSCE server, stores the corresponding ^3rd Party service provider policy, and stores the ^3rd Party service provider policy. It can be configured to perform at least one of the following operations: checking the policy's Network Slice end time or duration and deactivating it at that time, or transmitting a Notification message notifying deactivation to the NSCE server when deactivated.

* Additionally, according to an embodiment of the present disclosure, the NSCE (Network Slice Capability Enablement) server of the wireless communication system may be configured to perform at least one of the following operations.

- In order for the VAL server to receive notification from the NSCE server about whether to perform 5GS MnS (Management System) Network Slice activation/deactivation operation according to the ^3rd Party service provider policy, the Policy Management Notification subscription Request message is received from the VAL server and a reception response message is sent. action,

- In order to receive notification from 5GS MnS about whether 5GS MnS (Management System) Network Slice activation/deactivation operation is performed according to the ^3rd Party service provider policy, the NSCE server sends a Policy Management Notification Subscription Request message to 5GS MnS and receives a reception response message. action,

- The operation of receiving a Network Slice Allocate Request message containing the time operation policy determined by the VAL server,

- ^3rd party service provider Network Slice operation policy, that is, the operation of transmitting a Network Slice Allocate Request message containing Network Slice start time, duration, end time, and cycle information to 5GS MnS,

- When the 5GS MnS activates Network Slice according to the time operation policy, the operation of receiving a Network Slice Allocate Response message containing the name (Dedicated Name) that identifies the activated Network Slice,

- The operation of transmitting a Network Slice Allocate Response message containing the activated Network Slice identification name (Dedicated Name) to the VAL server,

- The operation of receiving a Network Slice Deallocation Notification message containing a name (Dedicated Name) identifying the deactivated Network Slice when the Network Slice is deactivated according to the ^3rd party service provider time operation policy,

- The operation of transmitting a Network Slice Deallocation Notification message containing the Dedicated Name of a deactivated Network Slice to the VAL server.

In this embodiment, the 5GS MnS receives a Network Slice Allocate Request message containing the Network Slice operation policy, Network Slice start time, duration, end time, and cycle information from the NSCE server, and stores the ^3rd party service provider policy. Operation, operation to check the Network Slice start time or cycle information of the ^3rd party service provider policy and activate at that time, Network Slice Allocate Response message containing the name (Dedicated Name) that identifies the activated Network Slice on the NSCE server when activated. To perform at least one of the following actions: transmitting a ^3rd party service provider policy, checking the end time or duration of the Network Slice of the 3rd Party Service Provider Policy and deactivating it at that time, or sending a Notification message notifying the deactivation to the NSCE server when deactivated. It can be configured.

Figure 1 shows an example of identification information that distinguishes a network slice according to an embodiment of the present disclosure.

As an embodiment, S-NSSAI defined by 3GPP may be used as an identifier (or identification information) to distinguish (or identify) a network slice.

Figure 1 shows an example of the configuration of an S-NSSAI information element (IE) 100 used as identification information to distinguish a network slice. In the present disclosure, S-NSSAI IE may be used interchangeably with S-NSSAI.

Referring to FIG. 1, one S-NSSAI (or S-NSSAI IE) 100 is a slice/service type (SST) 116 used in HPLMN (home PLMN: home public land mobile network), in HPLMN. It may include at least one of a slice differentiator (SD) 118 used, an SST 112 used by the serving PLMN, and an SD 114 used by the serving PLMN. The S-NSSAI (or S-NSSAI IE) 100 may further include a field 110 indicating the length of content included in the S-NSSAI IE 100. In a non-roaming situation, the SST (112) used by the serving PLMN may be the same as the SST (116) used by the HPLMN, and the SD (114) used by the serving PLMN may be the same as the SD used by the HPLMN. It may be the same as (118).

Each SST and SD value that makes up one S-NSSAI may be included or omitted depending on the situation.

Network slice selection assistance information (NSSAI) may consist of one or more S-NSSAI. Examples of the NSSAI include Configured NSSAI stored in the terminal, Requested NSSAI requested by the terminal, NF of the 5G core network (e.g., AMF, session management function (SMF), user plane function (UPF), and policy (PCF) control function, UDM (user data management), UDR (user data repository), NSSF (network slice selection function), etc.) and includes allowed NSSAI that the terminal is allowed to use, subscribed NSSAI to which the terminal is subscribed, etc. However, this is only an example, and the example of NSSAI is not limited to the above.

As described above, S-NSSAI may include SST values and SD values. The SST may indicate characteristics of services supported by the network slice (e.g., enhanced mobile broadband (eMBB), IoT, Ultra Reliability Low Latency Communication (URLLC), V2X, etc.). The SD may be a value used as an additional identifier for a specific service referred to as the SST.

Network operators operating 5G systems can operate their networks through network slicing. Network slices can also be used when a network operator becomes a communication service provider and provides services directly to customers in a B2C (business to customer) manner. In a B2B (business to business) scenario, the network can be leased to a VAL (vertical application layer) service provider that provides the above Vertical Application service, and the network provider can allocate and provide network resources to the VAL service provider through network slices. there is. When the VAL service provider delivers service requirements to the network provider, the network provider can create and manage a network slice by allocating network resources that satisfy the requirements.

In one embodiment, a network operator may create a network slice without allocating network resources, that is, without creating a network slice instance. A network slice for which network resources are not allocated may include information about what purpose the network slice can be used for and/or what characteristics it has. In this case, since network resources have not been allocated to the network slice, no VAL service provider has yet used the network slice, so information in the network slice for which no network resources have been allocated can be delivered to the VAL service provider, and the VAL service provider The network slice information can be used to determine which network slice will be allocated and used to provide future services.

Figure 2 shows an example of a system for providing a network slice to a VAL server at the application layer when providing a vertical application service according to an embodiment of the present disclosure.

Referring to FIG. 2, system 200 includes a VAL UE 210, a network system 220 (e.g., a 3GPP network system or a 5G system), at least one VAL server 230, and/or It may include a network slice capability enablement (NSCE) server 240. According to one embodiment, UE 210 may include a VAL client 212 and/or NSCE client 214. In this disclosure, the NSCE server may be referred to as a network slice capability management (NSCM) server, and the NSCE client may be referred to as an NSCM client. In this disclosure, VAL UE may be abbreviated as UE.

The VAL server 230 may be an application server of a VAL service provider that operates Vertical Application service(s) (e.g., IoT, unmanned flight, V2X (vehicle to everything), and/or factory automation) provided to users. The VAL client 212 may be a client that receives the Vertical Application service(s) provided to the user.

The NSCE server 240 and NSCE client 214 may obtain and store relevant information so that the VAL server 230 and VAL client 212 can use the network slice. NSCE server 240 and NSCE client 214 may respond to network slice related request(s) from VAL server 230 and/or VAL client 212 (e.g., network slice information transfer, network slice appropriate for service characteristics). Operation(s) corresponding to the decision (and/or request for network slice change) may be performed.

The network system 220 (e.g., 3GPP network system or 5G system) transmits control plane and user plane data to provide ^3rd party services and performs accompanying NAS (non-access-stratum) (NF). In addition, it may include Network Function(s) that perform Network Management functions. The service or system that supports this Network Management function may be referred to as 5GS MnS (Management Service or system) or MnS (Management Service or system). 5GS MnS may include at least one of EGMF (Exposure Governance Function), NSMF (Network Slice Management Function), NSSMF (Network Slice Subnet Management Function), NFMF (Network Slice Management Function), or MDAF (Management Data Analytics Function). there is. EGMF can provide 5G System Management services to the ^3rd Party Application Function (i.e. VAL server) by utilizing the function(s) provided by the NF(s) of the 5GS MnS. NSMF can provide the ability to manage one or multiple Network Slices using function(s) such as NSSMF, NFMF, and/or MDAF.

The NSCE server 240 may be an external ^3rd Party AF (application function) from the 5GS MnS perspective, or may be implemented as an internal AF within the 5G System, depending on the deployment option of the Network Slice service provider. In other words, depending on the Deploy Option, in the case of external ^3rd Party AF, the NSCE server 240 can use the Network Slice Management function using the function of EGMF, and in the case of 5G System internal AF, the NSCE server 240 can use the NSMF function. You can use the Network Slice Management function.

The NSCE server 240 may be a server of a network slice service provider that provides a network slice that satisfies the request(s) for providing Vertical Application services. The NSCE server 240 receives the related request(s) for Network Slice, and uses the VAL server 230 and the NSCE client 214 and a reference point (e.g., NSCE) to respond to the related request(s). -S and NSCE-UU) can be used. According to one embodiment, the NSCE server 240 transmits a request for network slice information for use by the VAL server 230 or the NSCE server 240 to the network system 220 and requests the network system 220 for necessary subsequent procedures. NFs and reference points within the system 220 can be used. According to one embodiment, the NSCE server 240 provides network slice information (or NSCM-OAM) through one of the NFs in the network system 220, for example, EGMF, or NSCE-OAM (or NSCM-OAM), which is a reference point with NSMF. For example, network slice product information) can be exchanged.

In the present disclosure, NSCE-OAM is only an example of a reference point for configuring one embodiment, and the present disclosure is not limited to using only the NSCE-OAM in acquiring network slice information. NSCE-OAM reference point is a reference point defined in the 3GPP SEAL (Service Enabler Architecture Layer) Rel-17 standard Specification, and may be changed to NSCE-OAM or another name in Rel-18.

Figure 3 is a flowchart showing a network slice management procedure according to an embodiment of the present disclosure.

In the embodiment of Figure 3, the network slice management procedure is when the VAL server transmits the network slice-related policy (e.g., time operation policy of the network slice) of the VAL service provider (e.g., 3rd party service provider) to the NSCE server. This may be an example of a procedure that is responsible for storing and operating (management) the policy of a 3rd party service provider, performing Network Slice activation/deactivation, and delivering the results to the VAL server. In the embodiment of Figure 3, the network slice-related policy may be abbreviated as policy.

Referring to FIG. 3, the network slice management procedure may include the steps (or operations) below.

1. The NSCE server receives the Policy Management Notification subscription Request message from the VAL server. This Policy Management Notification Subscription Request message may be a message requesting that the NSCE server deliver the result to the VAL server through Notification every time it performs an operation according to the policy. In the embodiment of Figure 3, the Policy Management Notification Subscription Request message may also be referred to as a Notification Subscription Request message or a first request message.

2. After receiving the Policy Management Notification Subscription Request message, the NSCE server sends a response message (Policy Management Notification subscription Response message) to the VAL server regarding whether the message was received. In the embodiment of Figure 3, the Policy Management Notification Subscription Response message may also be referred to as a Notification Subscription Response message or a first response message.

The VAL server can independently transmit the Policy Management Notification subscription Request message regardless of the transmission time of the Network Slice Policy Management Request message. For example, unlike the example illustrated in FIG. 3, the VAL server may transmit a Policy Management Notification subscription Request message after transmitting the Network Slice Policy Management Request message.

3. The NSCE server can receive a Network Slice Policy Management Request message from the VAL server.

The Network Slice Policy Management Request message may include the network slice-related policy of the VAL service provider (e.g., the network slice-related policy of the ^3rd party service provider). For example, the Network Slice Policy Management Request message (or, the network slice-related policy within the Network Slice Policy Management Request message) includes at least one of the Network Slice Identifier, NS_StartTime, NS_EndTime, NS_duration, or Periodicity attributes (parameters). It can contain one.

As an example, a ^3rd party service provider (VAL service provider) can set a policy (network slice-related policy) for each network slice. As an embodiment, the Network Slice Policy Management Request message may include a network slice-specific policy. That is, the Network Slice Policy Management Request message may include policies for each Network Slice. In this case, the properties (parameters) within the policy can define (or set) the policy of the Network Slice.

The description of each attribute (parameter) included in the Network Slice Policy Management Request message (or policy within the Network Slice Policy Management Request message) may be as follows.

The attribute Network Slice Identifier is a factor that distinguishes (or identifies) a Network Slice, and is a value (attribute value) that specifies the Dedicated Name (DN) of the S-NSSAI (e.g., S-NSSAI IE in Figure 1) or Network Slice Instance. ) can be set. If the VAL server already knows the Network Slice Identifier to which the policy will be applied, it may include this value in the Network Slice Policy Management Request message. If it does not know, it may not include the value.

The attribute NS_StartTime represents the start time for the Network Slice required to provide the services of the ^3rd Party service provider (VAL service provider). NS_StartTime can be set to a value (property value) that specifies the start time (activation time) of the Network Slice.

The property NS_EndTime indicates the end time for the activated Network Slice. NS_EndTime can be set to a value (property value) that specifies the end time of the activated Network Slice.

The property NS_duration represents the duration from the start of Network Slice activation. NS_duration can be set to a value (property value) that specifies the duration of the activated Network Slice.

The attribute Periodicity represents the activation cycle of Network Slice. Periodicity can be set to a value (property value) that specifies the activation cycle of the Network Slice. For example, if the property value of Periodicity is set to a value corresponding to 24 hours (hours), Network Slice is executed for the duration corresponding to the property value of NS_duration every 24 hours based on the start time corresponding to the property value of NS_StartTime. It may mean to activate it.

Meanwhile, as described above, some of the attributes included in the Network Slice Policy Management Request message (or policy within the Network Slice Policy Management Request message) may be omitted, or additional attributes may be further included. For example, depending on the embodiment, only one of the attribute NS_EndTime and the attribute NS_duration may be included in the policy. In the embodiment of Figure 3, the Network Slice Policy Management Request message may also be referred to as a Policy Management Request message or a second request message.

4. After receiving the Network Slice Policy Management Request message, the NSCE server sends a Network Slice Policy Management Response message, which is a response message about whether to receive the message and whether to perform the action, to the VAL server. In the embodiment of Figure 3, the Network Slice Policy Management Response message may also be referred to as a Policy Management Response message or a second response message.

5. The NSCE server can perform policy storing of the policy included in the received Network Slice Policy Management Request message. For example, after receiving the Network Slice Policy Management Request message, the NSCE server may store the values of the policy properties (e.g., Network Slice Identifier, NS_StartTime, NS_EndTime, NS_duration, and/or Periodicity) included in the message. .

6 ~ 7. NSCE server performs management operations according to policy. The NSCE server checks the value of NS_StartTime in the policy and can perform a request/action to activate Network Slice in the 5GS MnS at that time (e.g., 'AllocateNsi' operation defined in 3GPP TS 28.531). Additionally, the NSCE server can check the value of Periodicity and send a request to activate Network Slice to the 5GS MnS every cycle. The 5GS MnS that receives this request can perform subsequent procedures to allocate and activate the Network Slice.

If the Network Slice Policy Management Request message sent by the VAL server includes a Network Slice Identifier, the NSCE server can check whether a Network Slice with the same Network Slice Identifier exists. If a Network Slice with the same Network Slice Identifier does not exist, the NSCE server can perform the operation of allocating and activating a new Network Slice as described above. If a Network Slice with the same Network Slice Identifier exists, the NSCE server can perform an operation to activate the existing Network Slice.

The response message for Network Slice allocation and activation sent by the 5G MnS may include S-NSSAI (e.g., S-NSSAI IE in FIG. 1) and/or Dedicated Name (DN) of the Network Slice Instance.

The NSCE server can deliver S-NSSAI to the NSCE Client in the UE using the VAL service, or to the UE through PCR or AMF, for example, using the 'AF-guidance for URSP determination procedure' defined in 3GPP SA2.

8. After receiving a response message from the 5GS MnS to the Network Slice allocation and activation request, the NSCE server delivers a Policy Management Notification message including the result to the VAL server. At this time, if the 5GS MnS activates Network Slice, the NSCE server sends a parameter (e.g., parameter 'Network Slice Allocated') and/or assigned (or, It can be transmitted to the VAL server, including the Dedicated Name (DN) of the activated Network Slice Instance.

9 ~ 10. The NSCE server checks the value of NS_EndTime in the policy and, at that time, can perform a request/action to terminate and disable the Network Slice in the 5GS MnS (e.g., 'DeallocateNsi' operation defined in 3GPP TS 23.531). there is. The NSCE server can check NS_duration and send a request to disable Network Slice to the 5GS MnS even when the duration has expired.

The response message to the Network Slice deactivation (Deallocate) request sent by the 5G MnS may include S-NSSAI (e.g., S-NSSAI IE in FIG. 1) and/or Dedicated Name (DN) of the Network Slice Instance.

The NSCE server delivers the deactivated S-NSSAI to the NSCE Client in the UE using the VAL service, or, for example, performs PCR and AMF using the 'AF-guidance for URSP (UE route selection policy) determination procedure' defined in 3GPP SA2. It can be delivered to the UE through.

11. After receiving a response message from the 5GS MnS to the Network Slice deactivation request, the NSCE server delivers a Policy Management Notification message including the result to the VAL server. At this time, if the 5GS MnS has deactivated the Network Slice, the Policy Management Notification message includes a parameter indicating that the Network Slice has been deactivated (parameter 'Network Slice Deallocated') and/or the Dedicated Name (DN) of the deactivated Network Slice Instance to the VAL server. send to

Meanwhile, if necessary, some of the steps (or operations) illustrated in FIG. 3 may be omitted and/or additional steps may be further performed. Additionally, steps may be performed in an order other than that illustrated in FIG. 3 . For example, step 1 of FIG. 3 may be performed after step 3 of FIG. 3 and before step 5 of FIG. 3 . Additionally, the steps illustrated in FIG. 3 may be combined with the steps illustrated in FIGS. 4 and 5 to be described later as long as they do not contradict each other.

Figure 4 is a flowchart showing a network slice management procedure according to an embodiment of the present disclosure.

In the embodiment of Figure 4, the network slice management procedure is when the VAL server transmits the network slice-related policy (e.g., time operation policy of the network slice) of the VAL service provider (e.g., 3rd party service provider) to the NSCE server, the NSCE server Network Slice is responsible for the storage and operation (management) of Network Slice's start time (time) and cycle information policy, and 5GS MnS is responsible for storage and operation (management) of Network Slice's end time and duration policy. This may be an example of a procedure for performing activation/deactivation and delivering the results to the VAL server. In the embodiment of Figure 4, the network slice-related policy may be abbreviated as policy.

Referring to FIG. 4, the network slice management procedure may include the steps (or operations) below.

1. The NSCE server receives the Policy Management Notification subscription Request message from the VAL server. This Policy Management Notification subscription Request message may be a message requesting that the NSCE server deliver the result to the VAL server through Notification every time it performs an operation according to the policy.

2. After receiving the Policy Management Notification subscription Request message, the NSCE server sends a response message (Policy Management Notification subscription Response message) to the VAL server regarding whether the message has been received.

The VAL server can independently transmit the Policy Management Notification subscription Request message regardless of the transmission time of the Network Slice Policy Management Request message. For example, unlike the example illustrated in FIG. 4, the VAL server may transmit a Policy Management Notification subscription Request message after transmitting the Network Slice Policy Management Request message.

3. The NSCE server sends a Policy Management Notification subscription Request message to the 5GS MnS. This Policy Management Notification Subscription Request message may be a message that requests delivery of notification results to the NSCE server whenever the 5G MnS server performs an operation according to the policy. In the embodiment of FIG. 4, the NSCE server deactivates the Network Slice allocated and activated by the 5GS MnS at a time corresponding to NS_EndTime, and/or when the duration corresponding to NS_duration expires and deactivates the Network Slice to the NSCE server. To request the 5GS MnS to transmit related Notifications, the Policy Management Notification Subscription Request message can be used.

4. The NSCE server receives a response message (Policy Management Notification subscription Response message) to the Policy Management Notification subscription Request from the 5GS MnS.

5. The NSCE server can receive a Network Slice Policy Management Request message from the VAL server. This Network Slice Policy Management Request message may include the network slice-related policy of the VAL service provider (e.g., the network slice-related policy of the ^3rd party service provider). For example, the Network Slice Policy Management Request message (or network slice-related policy within the Network Slice Policy Management Request message) may include at least one of the following properties: Network Slice Identifier, NS_StartTime, NS_EndTime, NS_duration, or Periodicity. For a description of each attribute (parameter), refer to the description of FIG. 3.

6. After receiving the Network Slice Policy Management Request message, the NSCE server sends a Network Slice Policy Management Response message, which is a response message about whether to receive the Network Slice Policy Management Request message and whether to perform the action, to the VAL server.

7. The NSCE server can perform policy storing of the policy included in the received Network Slice Policy Management Request message. For example, after receiving the Network Slice Policy Management Request message, the NSCE server can store the attribute values of the policy attributes (e.g., Network Slice Identifier, NS_StartTime, NS_EndTime, NS_duration, and/or Periodicity) included in the message. there is.

As an embodiment, the Periodicity policy may be managed by the NSCE server or the 5GS MnS. For example, if the Periodicity policy is not managed by the NSCE server, the attribute Periodicity may be included in the Network Slice Allocate request message. Through this, 5GS MnS can manage periodicity policy.

8. NSCE server performs management operations according to policy. For example, the NSCE server may perform management operations according to the NS_StartTime policy and/or Periodicity policy. The NSCE server can continuously check the NS_StartTime value and/or Periodicity value in the policy.

9. When the start time corresponding to NS_StartTime comes, the NSCE server transmits a request to activate Network Slice (e.g., Network Slice Allocate Request message) to the 5GS MnS.

The NSCE server can check the periodicity and send a request (e.g., Network Slice Allocate Request message) to the 5GS MnS to activate Network Slice at the return of each cycle.

The NSCE server may include NS_EndTime and/or NS_duration parameter values in the Network Slice Allocate Request message.

When the Network Slice Policy Management Request message received from the VAL server includes the Network Slice Identifier, the NSCE server adds the Network Slice Identifier to the Network Slice Allocate Request message to check which Network Slice the ^3rd party service provider's policy applies to. may include.

If the Network Slice Policy Management Request received from the VAL server includes a Network Slice Identifier, the NSCE server can check whether a Network Slice with the same Network Slice Identifier exists. If a Network Slice with the same Network Slice Identifier does not exist, the NSCE server may not include the Network Slice Identifier in the Network Slice Allocate Request message sent to the 5GS MnS. If a Network Slice with the same Network Slice Identifier exists, the NSCE server can include the Network Slice Identifier in the Network Slice Allocate Request message sent to the 5GS MnS, and this message is newly added to the Network Slice corresponding to the Network Slice Identifier. It can be used to apply policy. In this case, the Network Slice Allocate Request message may be referred to as the Network Slice Modify (or Update) Request message.

After receiving a Network Slice Allocate Request message from the NSCE server, the 5GS MnS can newly allocate and activate a Network Slice. Meanwhile, if the Network slice corresponding to the Network Slice Identifier already exists and is activated, the process can proceed to the Policy storage step in Step 12.

If the 5GS MnS receives a Network Slice Allocate Request message containing the Periodicity attribute value from the NSCE server, Network Slice can be activated when the period corresponding to the Periodicity arrives, even if the Network Slice Allocate Request message is not received from the NSCE server.

10. The NSCE server can receive a Network Slice Allocate Response message from the 5G MnS. This Network Slice Allocate Response message may include S-NSSAI (eg, S-NSSAI IE in Figure 1) and/or the Dedicated Name of the Network Slice Instance.

The NSCE server can deliver S-NSSAI to the NSCE Client in the UE using the VAL service, or to the UE through PCR or AMF, for example, using the 'AF-guidance for URSP determination procedure' defined in 3GPP SA2.

11. After receiving the Network Slice Allocate Response message from the 5GS MnS, the NSCE server delivers a Policy Management Notification message including the result to the VAL server. At this time, if the 5GS MnS activates Network Slice, the NSCE server sends a parameter (e.g., parameter 'Network Slice (NS) Allocated') and/or assigned information in the Policy Management Notification message indicating that Network Slice has been activated (or allocated). (Or, it can be sent to the VAL server, including the Dedicated Name (DN) of the activated Network Slice Instance.

12. 5GS MnS can perform policy storing of the policy included in the received Network Slice Allocate Request message. For example, 5GS MnS can store NS_EndTime and/or NS_duration attribute values included in the received Network Slice Allocate Request message.

13. 5GS MnS performs management operations according to policy. For example, the NSCE server may perform management operations according to the NS_EndTime policy and/or NS_duration policy.

5GS MnS can check the value of NS_EndTime and terminate and disable Network Slice at that time.

5GS MnS can check NS_duration and terminate and disable Network Slice when the duration has ended.

14. The NSCE server receives a Policy Management Notification message from the 5GS MnS when the 5G MnS disables Network Slice. This Policy Management Notification message may include the Dedicated Name of S-NSSAI (eg, S-NSSAI IE in FIG. 1) and/or Network Slice Instance.

The NSCE server can deliver the deactivated S-NSSAI to the NSCE Client in the UE using the VAL service, or to the UE through PCR or AMF, for example, using the 'AF-guidance for URSP determination procedure' defined in 3GPP SA2. .

15. After receiving the Policy Management Notification message from the 5GS MnS, the NSCE server delivers the Policy Management Notification message including the result to the VAL server. At this time, if the 5GS MnS has deactivated the Network Slice, a parameter indicating that the Network Slice has been deactivated in the Policy Management Notification (e.g., parameter 'Network Slice (NS) Deallocated') and/or the Dedicated Name (DN) of the deactivated Network Slice Instance ) and transmit it to the VAL server.

Meanwhile, if necessary, some of the steps (or operations) illustrated in FIG. 4 may be omitted and/or additional steps may be further performed. Additionally, steps may be performed in an order other than that illustrated in FIG. 4 . For example, step 1 and/or step 3 of FIG. 4 may be performed after step 5 of FIG. 4 and before step 7 of FIG. 4 . Additionally, the steps illustrated in FIG. 4 may be combined with the steps illustrated in FIGS. 3 and 5 as long as they do not contradict each other.

Figure 5 is a flowchart showing a network slice management procedure according to an embodiment of the present disclosure.

In the network slice management procedure of the embodiment of Figure 5, the VAL server transmits the network slice-related policy (e.g., time operation policy of the network slice) of the VAL service provider (e.g., 3rd party service provider) by including it in the Network Slice Allocate Request message. This may be an example of a procedure in which the 5GS MnS is responsible for storing and operating (management) the policy, performing Network Slice activation/deactivation, and delivering the results to the VAL server. In the embodiment of Figure 5, the network slice-related policy may be abbreviated as policy.

Referring to FIG. 5, the network slice management procedure may include the steps (or operations) below.

1. The NSCE server receives the Policy Management Notification subscription Request message from the VAL server. This Policy Management Notification Subscription Request message may be a message requesting that the NSCE server deliver the result to the VAL server through Notification every time it performs an operation according to the policy.

2. After receiving the Policy Management Notification subscription Request message, the NSCE server sends a response message (Policy Management Notification subscription Response message) to the VAL server regarding whether the message has been received.

The VAL server can independently transmit the Policy Management Notification subscription Request message regardless of the transmission time of the Network Slice Policy Management Request message. For example, unlike the example illustrated in FIG. 5, the VAL server may transmit a Policy Management Notification subscription Request message after transmitting the Network Slice Policy Management Request message.

3. The NSCE server sends a Policy Management Notification subscription Request message to the 5GS MnS. This Policy Management Notification Subscription Request message may be a message that requests delivery of notification results to the NSCE server whenever the 5G MnS server performs an operation according to the policy. In the embodiment of Figure 5, the NSCE server deactivates the Network Slice allocated and activated by the 5G MnS at the time corresponding to NS_EndTime, and/or when the duration corresponding to NS_duration expires and deactivates the Network Slice to the NSCE server. To request the 5GS MnS to transmit related Notifications, the Policy Management Notification Subscription Request message can be used.

4. The NSCE server receives a response message (Policy Management Notification subscription Response message) to the Policy Management Notification subscription Request from the 5GS MnS.

5. The NSCE server can receive a Network Slice Allocate Request message from the VAL server. The Network Slice Allocate Request message may include the network slice-related policy of the VAL service provider (eg, policy of the ^3rd party service provider). For example, the Network Slice Allocate Request message (or network slice-related policy within the Network Slice Allocate Request message) may include Network Slice Identifier, NS_StartTime, NS_EndTime, NS_duration, and/or Periodicity properties (parameters). For a description of each attribute (parameter), refer to the description of Figure 3.

6. The NSCE server sends a Network Slice Allocate Request message to the 5GS MnS to activate Network Slice.

The NSCE server can include the policy of the ^3rd party service provider (VAL service provider) in the Network Slice Allocate Request message. For example, a Network Slice Allocate Request message (or a network slice-related policy within a Network Slice Allocate Request message) may include Network Slice Identifier, NS_StartTime, NS_EndTime, NS_duration, and/or Periodicity properties (parameters). .

If the Network Slice Allocate Request message received from the VAL server includes a Network Slice Identifier, the NSCE server sends a Network Slice Allocate Request message to the 5GS MnS to check which Network Slice the policy of the ^3rd party service provider applies to. Can include Network Slice Identifier.

If the Network Slice Allocate Request received from the VAL server includes a Network Slice Identifier, the NSCE server can check whether a Network Slice with the same Network Slice Identifier exists. If a Network Slice with the same Network Slice Identifier does not exist, the NSCE server may not include the Network Slice Identifier in the Network Slice Allocate Request message sent to the 5GS MnS. If a Network Slice with the same Network Slice Identifier exists, the NSCE server can include the Network Slice Identifier in the Network Slice Allocate Request message sent to the 5GS MnS, and this message is newly added to the Network Slice corresponding to the Network Slice Identifier. It can be used to apply policy. In this case, the Network Slice Allocate Request message may be referred to as the Network Slice Modify (or Update) Request message.

7. 5GS MnS can perform policy storing of the policy included in the received Network Slice Allocate Request message. For example, after receiving the Network Slice Allocate Request message from the NSCE server, the 5GS MnS can store the Policy (Policy properties) included in the message.

8. 5GS MnS performs management operations according to policy. For example, 5GS MnS can perform management operations according to the NS_StartTime policy and/or Periodicity policy. 5GS MnS can continuously check the NS_StartTime value and/or Periodicity value in the policy.

When the 5GS MnS reaches the start time corresponding to NS_StartTime, Network Slice can be activated even without a request to activate Network Slice (e.g., Network Slice Allocate Request) from the NSCE server.

Additionally, the 5GS MnS can check the periodicity and activate the Network Slice every time a cycle returns, even without a request to activate the Network Slice (e.g., Network Slice Allocate Request) from the NSCE server.

9. The NSCE server can receive a Network Slice Allocate Response message from the 5G MnS. This Network Slice Allocate Response message may include S-NSSAI (eg, S-NSSAI IE in Figure 1) and/or Dedicated Name (DN) of the Network Slice Instance.

The NSCE server can deliver S-NSSAI to the NSCE Client in the UE using the VAL service, or to the UE through PCR or AMF, for example, using the 'AF-guidance for URSP determination procedure' defined in 3GPP SA2.

10. After receiving the Network Slice Allocate Response message from the 5GS MnS, the NSCE server delivers the message to the VAL server. At this time, the Network Slice Allocate Response message may include the Dedicated Name (DN) of the allocated Network Slice Instance.

11. 5GS MnS performs management operations according to policy. For example, the NSCE server may perform management operations according to the NS_EndTime policy and/or NS_duration policy.

5GS MnS can check the NS_EndTime value and terminate and disable Network Slice at that time.

5GS MnS can check NS_duration and terminate and disable Network Slice when the duration has ended.

12. The NSCE server receives a Policy Management Notification message from the 5G MnS when the 5G MnS disables Network Slice. This Policy Management Notification message may include S-NSSAI (eg, S-NSSAI IE in FIG. 1) and/or Dedicated Name (DN) of the Network Slice Instance.

The NSCE server can deliver the deactivated S-NSSAI to the NSCE Client in the UE using the VAL service or, for example, to the UE through PCR or AMF using the AF-guidance for URSP determination procedure defined in 3GPP SA2.

13. After receiving the Policy Management Notification message from the 5GS MnS, the NSCE server delivers the Policy Management Notification message including the result to the VAL server. At this time, if the 5GS MnS has deactivated the Network Slice, the VAL information includes a parameter indicating that the Network Slice has been deactivated in the Policy Management Notification (e.g., parameter 'Network Slice (NS) Deallocated') and the Dedicated Name (DN) of the deactivated Network Slice Instance. Send to server.

Meanwhile, if necessary, some of the steps (or operations) illustrated in FIG. 5 may be omitted and/or additional steps may be further performed. Additionally, steps may be performed in an order other than that illustrated in FIG. 5 . For example, step 1 and/or step 3 of FIG. 5 may be performed after step 5 of FIG. 5 and before step 7 of FIG. 5 . Additionally, the steps illustrated in FIG. 5 may be combined with the steps illustrated in FIGS. 3 and 4 as long as they do not contradict each other.

FIG. 6 is a diagram showing the configuration of a network entity in a wireless communication system according to an embodiment of the present disclosure. The network entity in FIG. 6 may be one of the network entities described in the embodiments of FIGS. 1 to 5, such as a VAL server, NSCE server, and NFs of the 5GS MnS (eg, EGMF, NSMF, etc.).

As shown in FIG. 6, the network entity may include a processor 601, a transceiver 603, and a memory 605. In the embodiments of FIGS. 1 to 5 , the processor 601, transceiver 603, and memory 605 of the network entity may operate according to the operations of the network entity described above. However, the components of the network entity are not limited to the examples described above. For example, a network entity may include more or fewer components than those described above. In addition, the processor 601, transceiver 603, and memory 605 may be implemented in the form of a single chip.

The transceiver 603 is a general term for a receiver of a network entity and a transmitter of a network entity, and can transmit and receive signals to and from a terminal or another network entity. At this time, the transmitted and received signal may include at least one of control information and data. To this end, the transceiver 603 may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. This is only an example of the transceiver 603, and the components of the transceiver 603 are not limited to the RF transmitter and RF receiver. The transceiver 603 may include a wired/wireless transceiver and may include various components for transmitting and receiving signals. Additionally, the transceiver 603 may receive a signal through a designated communication interface, output the signal to the processor 601, and transmit the signal output from the processor 601. Additionally, the transceiver 603 may receive a communication signal and output it to the processor 601, and transmit the signal output from the processor 601 to a terminal or another network entity through a network.

The memory 605 may store programs and data necessary for operation of a network entity according to at least one of the embodiments of FIGS. 1 to 5. Additionally, the memory 605 may store control information or data included in signals obtained from a network entity. The memory 605 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

The processor 601 may control a series of processes so that the network entity can operate according to at least one of the embodiments of FIGS. 1 to 5. Processor 601 may include at least one processor. Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

These programs (software modules, software) may include random access memory, non-volatile memory, including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of disk storage. It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included. The program is accessed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored in an attachable storage device that can be accessed. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to the device performing an embodiment of the present disclosure.

Figure 7 is a diagram showing the configuration of a terminal in a wireless communication system according to an embodiment of the present disclosure. The terminal in FIG. 7 may be a VAL UE described in the embodiments of FIGS. 1, 2, 3, 4, and 5.

As shown in FIG. 7, the terminal may include a processor 701, a transceiver 703, and a memory 705. In the embodiments of FIGS. 1, 2, 3, 4, and 5, the processor 701, transceiver 703, and memory 705 of the terminal may operate according to the operations of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the aforementioned components. In addition, the processor 701, transceiver 703, and memory 705 may be implemented in the form of a single chip.

The transceiver 703 is a general term for a terminal receiver and a terminal transmitter and is capable of transmitting and receiving signals to and from other terminals or network entities. At this time, the transmitted and received signal may include at least one of control information and data. To this end, the transceiver 703 may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. This is only an example of the transceiver 703, and the components of the transceiver 703 are not limited to the RF transmitter and RF receiver. The transceiver 703 may include a wired/wireless transceiver and may include various components for transmitting and receiving signals. Additionally, the transceiver 703 may receive a signal through a designated communication interface, output the signal to the processor 701, and transmit the signal output from the processor 701. Additionally, the transceiver 703 may receive a communication signal and output it to the processor 701, and transmit the signal output from the processor 701 to a terminal or another network entity through a network.

The memory 705 may store programs and data necessary for operation of the terminal according to at least one of the embodiments of FIGS. 1, 2, 3, 4, and 5. Additionally, the memory 705 may store control information or data included in signals obtained from the terminal. The memory 705 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

The processor 701 may control a series of processes so that the terminal can operate according to at least one of the embodiments of FIGS. 1, 2, 3, 4, and 5. Processor 701 may include at least one processor. Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

These programs (software modules, software) may include random access memory, non-volatile memory, including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of disk storage. It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included. The program is accessed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored in an attachable storage device that can be accessed. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to the device performing an embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the disclosure are expressed in singular or plural numbers depending on the specific embodiment presented. However, singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but of course, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the patent claims described later, but also by the scope of this patent claim and equivalents.

Claims (12)

In the method of the NSCE (network slice capability enablement) server,
Receiving a network slice policy management request message from a vertical application layer (VAL) server, wherein the policy management request message includes policy information for a network slice;
A method comprising performing a policy management operation for the network slice based on the policy information included in the policy management request message. According to paragraph 1,
The above policy information:
Start time information specifying the start time of the network slice; and
A method including period information specifying an activation period of the network slice. According to paragraph 2,
The above policy information:
Identification information identifying the network slice;
End time information specifying the end time of the network slice; or
The method further includes at least one of duration information specifying the duration of the network slice. According to paragraph 3,
The identification information is S-NSSAI information of the network slice or dedicated name information of the network slice. The method of claim 1, wherein:
Receiving, from the VAL server, a policy management notification subscription request message requesting delivery of a notification of a result to the policy management operation; and
Method further comprising transmitting a response message to the request message. 6. The method of claim 5, wherein:
Further comprising transmitting a policy management notification message associated with the policy management notification subscription request message to the VAL server,
The policy management notification message includes at least one of information indicating allocation or activation of the network slice or dedicated name information of the network slice. In NSCE (network slice capability enablement) server,
transceiver; and
A processor comprising:
Receiving a network slice policy management request message from a VAL (vertical application layer) server, where the policy management request message includes policy information about the network slice,
An NSCE server configured to perform a policy management operation for the network slice based on the policy information included in the policy management request message. In clause 7,
The above policy information:
Start time information specifying the start time of the network slice; and
An NSCE server including cycle information specifying an activation cycle of the network slice. According to paragraph 2,
The above policy information:
Identification information identifying the network slice;
End time information specifying the end time of the network slice; or
NSCE server further comprising at least one of duration information specifying the duration of the network slice. According to clause 9,
The identification information is S-NSSAI information of the network slice or dedicated name information of the network slice, NSCE server. 10. The method of claim 9, wherein the processor:
Receiving, from the VAL server, a policy management notification subscription request message requesting delivery of a notification of a result to the policy management operation,
NSCE server further configured to transmit a response message to the request message. 12. The method of claim 11, wherein the processor:
further configured to transmit a policy management notification message associated with the policy management notification subscription request message to the VAL server;
The policy management notification message includes at least one of information indicating allocation or activation of the network slice or dedicated name information of the network slice.

Images