Method and apparatus for controlling data rate in a wireless communication system

Abstract

A method and apparatus for controlling a data rate of a terminal in a wireless communication system are disclosed. The method according to an embodiment of the disclosure is a data rate control method of a terminal in an access and mobility management function (AMF) apparatus of a wireless communication system, wherein the method can include the following operations: receiving, from a terminal, a registration request message including an identifier of the terminal; transmitting, to a unified data management (UDM), the registration request message including the identifier of the terminal; receiving, from the UDM, subscription information including network slice information that can be allocated to the terminal; inquiring, to a policy control function (PCF) apparatus, a policy association of the terminal including the network slice information; receiving, from the PCF, a policy association response message including information on a total transmission rate of a serving network slice that is limited; and providing, to a base station of the terminal, the information on the total transmission rate of the serving network slice that is limited.

Description

TECHNICAL FIELD

[0001] The disclosure relates to a method and apparatus for controlling a data rate of a terminal transmitting / receiving in a wireless communication system. BACKGROUND

[0002] To meet increasing demands with respect to wireless data traffic after deployment of 4th generation (4G) communication systems, efforts have been made to develop an improved 5th generation (5G) or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a 'Beyond 4G Network' or a 'Post long term evolution (Post-LTE) system'.

[0003] The 5G communication system is considered to be implemented in terahertz (THz) bands (e.g., 60 GHz bands), so as to accomplish higher data rates beyond the 4G communication system. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed for the 5G communication system.

[0004] In addition, the 5G communication system is developed to be implemented in a very high frequency (mmWave) bands, such as 60GHz bands, so as to accomplish higher data rates beyond the 4G communication system. To mitigate a propagation loss of radio waves and increase a transmission distance, the beamforming, massive MIMO, full dimensional MIMO (FD-MIMO), an array antenna, an analog beam forming, large scale antenna techniques are discussed for the 5G communication system.

[0005] In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), a non-orthogonal multiple access (NOMA), and a sparse code multiple access (SCMA) as an advanced access technology have been developed.

[0006] With the development of various information technologies (IT), network devices have evolved into virtualized network functions (NFs) through the application of virtualization technology, and the virtualized NFs can be implemented in the form of software beyond physical limitations and installed / operated in various types of clouds or data centers (DCs). In particular, the NFs can be freely scaled up, scaled down, installed (launched), or terminated according to service requirements, system capacity, or network load. Since the NFs should be basically executed on a physical configuration (e.g., a predetermined device), even if the NFs are implemented in the form of software, it should be noted that the physical configuration is not excluded. In addition, the NFs can be implemented simply through a physical configuration (that is, hardware).

[0007] To support various services in various network structures, a network slicing technology has been introduced. Network slicing is a technology of logically configuring a network through a set of network functions (NFs) to support a specific service and separate it from other slices. One terminal can access two or more different slices. In this case, different network slices corresponding to different services can be accessed, or even the same service can be provided through different network slices.

[0008] As described above, since various services or one service can be provided through different network slices due to the development of a mobile communication system, a scheme for efficiently controlling a communication rate of each network slice for a terminal is required. SUMMARY

[0009] TECHNICAL PROBLEM

[0010] The present disclosure provides a method and apparatus for efficiently controlling a data rate provided to a terminal (e.g., a user equipment in a wireless communication system).

[0011] SOLUTION TO PROBLEM

[0012] A method of controlling a data rate of a UE by a session management function (SMF) device in a wireless communication system according to an embodiment of the present disclosure can include receiving, from an access and mobility management function (AMF), a protocol data unit (PDU) session creation request message including network slice information of the UE and UE information, generating a session management (SM) context for managing a PDU session of the UE, acquiring UE subscription information of the UE from a unified data management (UDM) device, establishing an SM policy association with a policy control function (PCF) device, determining an aggregate maximum bit rate (AMBR) of a single network slice selection assistance information (S-NSSAI) of a PDU session of the UE based on the SM policy association, establishing an N4 session with the AMF based on the SM policy association and the S-NSSAI-AMBR, and notifying the AMF of a session establishment with a UPF.

[0013] A session management function (SMF) device in a wireless communication network according to an embodiment of the disclosure can include a network interface configured to communicate with another network entity in the wireless communication network, a memory configured to store information received from the other network entity, and at least one processor, wherein the processor can be configured to receive, from an access and mobility function (AMF) device, a protocol data unit (PDU) session creation request message including network slice information of a UE and UE information through the network interface, generate a session management (SM) context for managing a PDU session of the UE, acquire UE subscription information of the UE from a unified data management (UDM) device through the network interface, establish an SM policy association with a policy control function (PCF) device through the network interface, determine an aggregated maximum bit rate (AMBR) of a single network slice selection assistance information (S-NSSAI) of a PDU session of the UE based on the SM policy association, establish an N4 session with the AMF based on the SM policy association and the S-NSSAI-AMBR, and notify the AMF device of a session establishment with a UPF.

[0014] Advantages of the Invention

[0015] By the method and apparatus according to the disclosure, the data rate provided to a terminal (e.g., a user equipment in a wireless communication system) can be effectively controlled. In addition, when the embodiment of the disclosure is applied, a mobile communication system can effectively manage network resources by configuring a network slice to provide data according to a data rate required by a user equipment or a network. In addition, the mobile communication system can change the data rate of a network slice to which a UE subscribes according to various situations. BRIEF DESCRIPTION OF DRAWINGS

[0016] FIG. 1 A registration procedure according to an embodiment of the disclosure is illustrated.

[0017] FIG. 2 A PDU session establishment procedure according to an embodiment of the disclosure is illustrated.

[0018] FIG. 3A And FIG. 3B A PDU session establishment procedure according to an embodiment of the disclosure is illustrated.

[0019] FIG. 4A And FIG. 4B A PDU session establishment procedure according to an embodiment of the disclosure is illustrated.

[0020] FIG. 5A And FIG. 5B A PDU session establishment procedure according to an embodiment of the disclosure is illustrated.

[0021] FIG. 6A service request procedure according to an embodiment of the disclosure is illustrated.

[0022] FIG. 7 A UE configuration update procedure according to an embodiment of the disclosure is illustrated.

[0023] FIG. 8 is a block diagram illustrating an internal function of an NF according to various embodiments of the disclosure.

[0024] FIG. 9 is a block diagram illustrating an interval function of a UE according to various embodiments of the disclosure.

[0025] FIG. 10 A PDU session establishment procedure according to various embodiments of the disclosure is illustrated.

[0026] FIG. 11 A 5GS / EPS interworking structure according to various embodiments of the disclosure is illustrated. DETAILED DESCRIPTION

[0027] The terms used in the present disclosure are merely used to describe particular embodiments and are not intended to limit the present disclosure. Singular expressions can include plural expressions, unless they are clearly different in the context. Unless otherwise defined, all terms used herein, including technical terms and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure belongs. The terms defined in a general dictionary can be interpreted to have the same meaning as the contextual meaning in the relevant art and, unless otherwise defined in the present disclosure, should not be interpreted to have an ideal or overly formal meaning. In some cases, even the terms defined in the present disclosure should not be interpreted to exclude embodiments of the present disclosure.

[0028] Hereinafter, various embodiments of the present disclosure will be described based on a hardware-based method. However, various embodiments of the present disclosure include a technology using both hardware and software, and thus various embodiments of the present disclosure do not exclude a software perspective.

[0029] The present disclosure relates to a method and apparatus for supporting various services in a wireless communication system. Specifically, the present disclosure describes a technology for supporting various services by supporting mobility of a terminal in a wireless communication system.

[0030] As used in the following description, terms related to a signal, terms for identifying an access node, terms related to a network entity or a network function (NF), terms related to a message, terms related to an inter-network entity interface, terms related to various identification information, etc. are used illustratively for convenience. Accordingly, the present disclosure is not limited by the terms used below, and other terms related to the subject matter having equivalent technical meanings can be used.

[0031] The NF used in the present disclosure can be one network entity or a part of one network entity. The network entity can have a physical configuration and a software configuration, and can be implemented as one device, one apparatus, or one computing system. In another example, one NF can be implemented as one NF by two or more devices, two or more apparatuses, or two or more computing systems. Also, one NF can be installed as a specific software module in one computing system or two or more computing systems to operate as one NF.

[0032] In the following description, for convenience of description, unless specifically mentioned, the NF can be understood as having a form including a physical device and a software configuration of one network entity or implemented as one network entity.

[0033] For convenience of description, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) and 5G standards. However, the present disclosure is not limited by the terms and names, and can be identically applied to a system based on another standard.

[0034] The 5G system according to an embodiment of the present disclosure can include a terminal, a base station, and a 5G core network. The 5G core network can include network functions (hereinafter, can be used interchangeably with NF) such as an AMF, an SMF, a PCF, a UPF, a UDM, a UDR, a NEF, an NSSF, etc. According to an embodiment of the present disclosure, the network function (NF) can refer to a network entity (hereinafter, can be used interchangeably with NE) or a network resource. The next generation radio access network (NG-RAN) (hereinafter, can be used interchangeably with 5G-RAN or RAN) is a base station that provides a wireless communication function to a terminal. The terminal (user equipment or UE) can access the 5G core network through the base station.

[0035] Also, the various network functions described below can include one specific physical device or two or more physical devices. Also, each physical device can include a program (software) for performing the methods described below under the control of a processor included therein. Hereinafter, for convenience of description, only the name of the NF is given, but the NF is implemented as a physical device including at least one processor as described above, and it is obvious to those skilled in the art that the NF can have (install) a program (software) for the operations described in the present disclosure. Therefore, the expression "device" is omitted, and only the name of the specific NF is described hereinafter.

[0036] According to embodiments of the disclosure, an access and mobility management function (AMF) is a network function that manages wireless network access and mobility of a terminal. A session management function (SMF) is a network function that manages a packet data network connection provided to a terminal (e.g., a user equipment (UE)). In the following description, a terminal and a UE can refer to all devices capable of accessing a specific wireless network in the same manner through a radio access scheme. A packet data network connection is referred to as a protocol data unit (PDU) session. PDU session information can include quality of service (QoS) information, charging information, or information about packet processing. A policy control function (PCF) is a network function that applies service policies, charging policies, and policies for a PDU session of a mobile communication service provider for a terminal. A user plane function (UPF) serves as a gateway that delivers packets transmitted and received by a terminal, and is a network function controlled by an SMF. The UPF is connected to a data network (DN), and is used to transmit uplink data packets generated by a terminal to an external data network through a 5G system. Further, the UPF is used to transmit received downlink data packets generated by an external data network to a terminal through a 5G system. For example, the UPF can be connected to a data network connected through the Internet, and can route data packets transmitted from a terminal through the Internet, and route data packets transmitted from the Internet to the terminal.

[0037] A unified data management (UDM) is a network function that stores and manages information about a subscriber. A network exposure function (NEF) is a network function that can access information for managing a terminal in a 5G network in order to subscribe to a mobility management event of a terminal, subscribe to a session management event of a terminal, request session-related information, configure charging information of a terminal, and request a change in a PDU session policy of a terminal, i.e., transmit information about a terminal to an NF through a connection to a 5G core network NF, or report information about a terminal to the outside. An application function (AF) is a network function that can use services and functions provided by a 5G network through an NEF.

[0038] A unified data repository (UDR) is a network function that stores and manages data. For example, when a new terminal is subscribed or existing terminal subscription information is changed or a request for the change is made, the UDR can store terminal subscription information and provide the terminal subscription information to the UDM. The UDR can store service provider policy information and provide the service provider policy information to the PCF. The UDR can store network service exposure related information and provide the network service exposure related information to the NEF. A network slice selection function (NSSF) is a network function that determines a network slice available to a terminal and determines a network slice instance included in the network slice.

[0039] A network slice or a network slice instance can operate as a program in one device, one apparatus, and / or one computing system. In another example, a network slice or a network slice instance can operate as a program in two or more devices, two or more apparatuses, and / or two or more computing systems. In another example, a particular network slice or a particular network slice instance can operate as a program in one device, one apparatus, and / or one computing system, while another network slice or another network slice instance can operate as a program in two or more devices, two or more apparatuses, and / or two or more computing systems.

[0040] Each NF can predefine a service provided by itself, and the service provided by the NF can be referred to as an Nfcf, Nsmf, Namf, and Nnef service. For example, when the AMF transmits a session-related message to the SMF, the AMF can use the Nsmf_PDUSession_CreateSMContext service (or application program interface (API)).

[0041] In the following description, a service (e.g., an Npcf service) can be collectively referred to as messages exchanged with a PCF through an interface for communication with the PCF. In the above example, when the AMF uses the Nsmf_PDUSession_CreateSMContext service to transmit a session-related message to the SMF, the messages can be specific messages configured according to a format required by the SMF through an interface for communication with the SMF.

[0042] A terminal can access an AMF through a base station and exchange a control plane signaling message with a 5G core network. Also, the terminal can access a UPF through the base station and exchange user plane data with a data network. An application server that provides an application layer service to the terminal can be referred to as an AF when exchanging a control plane signaling message with the 5G core network and can be referred to as a DN when exchanging user plane data with the terminal. Accordingly, both the AF and the DN can be used as the name of the application server.

[0043] Meanwhile, a mobile communication system can include a network supporting network slicing. That is, one physical network can be configured and managed as logically separated network slices (hereinafter, can be used interchangeably with slicing). A mobile service provider can provide a dedicated network slice dedicated to various services having different characteristics. Each network slice can have different types and different amounts of required resources according to service characteristics, and the mobile communication system can guarantee the required resources for each network slice. For example, a network slice providing a voice call service can frequently occur control plane signaling, and thus includes NFs dedicated thereto. A network slice providing an Internet data service can frequently occur large data traffic, and thus includes NFs dedicated thereto. In the 5G system defined by 3GPP, one network slice can be referred to as an "S-NSSAI". Single network slice selection assistance information (S-NSSAI) can include a slice / service type (SST) value and a slice differentiator (SD) value. The SST can indicate characteristics of a service (e.g., enhanced mobile broadband (eMBB), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), and vehicle-to-everything (V2X)) supported by the slice. The SD can be used as an additional delimiter for a specific service referred to as the SST.

[0044] A terminal can access a mobile communication system to perform a registration procedure. In the registration procedure, the terminal can transmit network slice information to be used to the mobile communication system. The network slice information transmitted by the terminal to the mobile communication system can be referred to as "requested slice (requested NSSAI)", and the requested NSSAI can include one or more S-NSSAI values. The mobile communication system can authenticate the terminal request, and when the authentication is successful, can determine network slice information available for the terminal. The network slice information determined by the mobile communication system can be referred to as "allowed slice (allowed NSSAI)", and the allowed NSSAI can include one or more S-NSSAI values. The terminal can receive the allowed NSSAI from the mobile communication system. The terminal can store the allowed NSSAI and use it for the following procedures.

[0045] A terminal that completes the registration procedure can connect to a DN to perform a PDU session establishment procedure in order to transmit and receive data. The terminal can insert S-NSSAI and / or data network name (DNN) information to be used into a PDU session establishment request message and transmit the message to the mobile communication system. The mobile communication system can authenticate the terminal request, and when the authentication is successful, can establish a PDU session for the terminal. Through such a procedure, the terminal can establish one or more PDU sessions in one network slice. When different PDU sessions are supported for one terminal in one network slice, the DNNs can be the same or different. For example, the terminal can establish three different PDU sessions using an eMBB slice (eMBB S-NSSAI). A first PDU session can support eMBB S-NSSI and DNN1. A second PDU session can support eMBB S-NSSI and DNN2. A third PDU session can support eMBB S-NSSI and DNN2. The first PDU session and the second PDU session can correspond to a case where different DNNs are supported in the same network slice, and the second PDU session and the third PDU session can correspond to a case where the same DNN is supported in the same network slice.

[0046] The disclosure describes a method and apparatus for controlling a data rate of a network slice for each terminal in a mobile communication system. To this end, the disclosure describes operations of nodes (e.g., a terminal, a base station, an AMF, an SMF, and a UPF) included in a 5G system for controlling a data rate of a network slice for each terminal. In particular, when one S-NSSAI supports two or more PDU sessions for one terminal, a method and apparatus for controlling uplink data traffic and downlink data traffic of each PDU session are described.

[0047] When the embodiments of the disclosure are applied, the mobile communication system can configure network slices to provide a required data rate and efficiently manage network resources. In addition, the mobile communication system can change a data rate of a network slice to which a terminal subscribes according to various situations.

[0048] According to various embodiments of the disclosure, when a node included in a 5G system is described, a number can be assigned. For example, when numbers such as SMF1 and SMF2 are assigned, these numbers can mean that SMFs are logically and / or physically separated, but operations performed thereby can be the same. Assigning a number can mean that a plurality of sessions are processed by logically and / or physically different NFs.

[0049] Hereinafter, the NF can be at least one of an Access and Mobility Management Function (AMF) device, a Session Management Function (SMF) device, and a Network Slice Selection Function (NSSF) device. However, the embodiments of the disclosure can be equally applied to a case in which the NF is actually implemented as an instance (AMF instance, SMF instance, or NSSF instance).

[0050] In the disclosure, an instance can mean a state in which a specific NF exists in the form of software code and physical or / and logical resources can be allocated from a computing system to perform an NF function and can be executed by a physical computing system (for example, a specific computing system existing in a core network). Accordingly, an AMF instance, an SMF instance, or an NSSF instance can mean that physical or / and logical resources can be used for AMF, SMF, or NSSF operations after being allocated from a specific computing system existing in a core network. As a result, the AMF instance, the SMF instance, and the NSSF instance receiving physical or / and logical resources for AMF, SMF, and NSSF operations from a specific computing system existing in a network can perform the same operations as in a case in which a physical AMF, SMF, and NSSF device exist. Accordingly, in the embodiments of the disclosure, the description of the NF (AMF, SMF, UPF, NSSF, NRF, or SCP) can be replaced with the NF instance, or conversely, the description of the NF instance can be replaced with the NF. Similarly, in the embodiments of the disclosure, the description of the NW slice can be replaced with the NW slice instance, or conversely, the description of the NW slice instance can be replaced with the NW slice.

[0051] [Embodiment 1]

[0052] In various embodiments of the disclosure, Embodiment 1 describes a method of managing a data rate of a network slice for each terminal in a mobile communication system. More specifically, Embodiment 1 describes a method by which data rate information of a network slice for each terminal is defined, a terminal, a base station, and an NF store network slice data rate information for each terminal, and uplink data and downlink data traffic are controlled.

[0053] According to embodiments of the disclosure, a total transmission rate limit QoS parameter (aggregated rate limit QoS parameter associated with S-NSSAI) associated with a network slice used by a terminal can be defined. As described above, the aggregated rate limit QoS parameter associated with a network slice can include, for example, an aggregated maximum bit rate per network slice (per S-NSSAI aggregated maximum bit rate, hereinafter referred to as slice-AMBR or S-NSSAI-AMBR, NSSAI-AMBR, SST-AMBR, S-AMBR, or slice-MBR). According to an NF that stores and manages the slice-AMBR, the slice-AMBR can be classified into a subscribed slice-AMBR, a service network slice-AMBR, and an authorized slice-AMBR.

[0054] The subscribed slice-AMBR can be stored in the UDM as UE subscription information. The UDM can provide the subscribed slice-AMBR to a 5G core network NF (e.g., AMF or SMF). The UDM can manage the subscribed slice-AMBR of a terminal as well as the subscribed S-NSSAI. For example, when there are eMBB S-NSSAI, URLLC S-NSSAI, and IoT S-NSSAI as UE subscription slices, there can be a slice-AMBR linked to each S-NSSAI. That is, for example, there can be an eMBB slice-AMBR, a URLLC slice-AMBR, and an IoT Slice-AMBR. In addition, there can be a default slice-AMBR, which can be applied when there is no slice-AMBR linked to a specific S-NSSAI. For example, when there is no IoT slice-AMBR, the default slice-AMBR can be used for the IoT S-NSSAI.

[0055] The service network slice-AMBR can be managed by the PCF. The PCF can determine the service network slice-AMBR based on the S-NSSAI, mapping of the S-NSSAI (mapping information of the S-NSSAI of the subscription of the terminal and the service network S-NSSAI), the subscribed slice-AMBR, the session-AMBR, the mobile communication service provider policy, the local policy, and the roaming agreement. For example, the PCF can determine the slice-AMBR of the S-NSSAI mapped to the S-NSSAI of the subscription of the terminal, which is the network slice of the subscription of the terminal and used by the service network, i.e., the service network slice-AMBR. The service network slice-AMBR can be used to support a roaming subscriber. The PCF can provide the service network slice-AMBR to the 5G core network NFs (e.g., AMF and SMF).

[0056] The authorized slice-AMBR can be managed by the PCF. The PCF can determine the authorized network slice-AMBR based on the S-NSSAI, mapping of the S-NSSAI (mapping information of the S-NSSAI of the subscription of the terminal and the service network S-NSSAI), the subscribed slice-AMBR, the service network slice-AMBR, the session-AMBR, the mobile communication service provider policy, the local policy, and the roaming agreement. The PCF can provide the authorized network slice-AMBR to the 5G core network NFs (e.g., AMF and SMF).

[0057] The 5G core network NFs (e.g., AMF and SMF) can determine to use the subscribed slice-AMBR acquired from the UDM, change the subscribed slice-AMBR acquired from the UDM based on the local policy, and then use the changed subscribed slice-AMBR, or use the service network slice-AMBR or / and the authorized slice-AMBR acquired from the PCF, in order to manage the data rate of the network slice used by the terminal.

[0058] The slice-AMBR can indicate a limit of an aggregated bit rate expected to be provided on non-GBR QoS flows for all PDU sessions associated with the corresponding S-NSSAI. Further, the slice-AMBR can indicate a value measured in an AMBR averaging window. For example, when a terminal establishes three PDU sessions associated with an eMBB S-NSSAI and user planes of the three PDU sessions are in an activated state (PDU sessions have an active user plane to a RAN), a slice-AMBR of the eMBB S-NSSAI can be calculated as a sum of AMBRs used by the three PDU sessions. At this time, the slice-AMBR can be configured to be equal to or less than a value determined as a slice-AMBR of a subscription or / and a slice-AMBR of authorization or / and a service network slice-AMBR to be used by a 5G NF. For example, when an eMBB slice-AMBR determined to be used by a 5G NF is 1 Giga bit per second (Gbps) and AMBRs to be used by the three PDU sessions are 200 Mega bit per second (Mbps), 100 Mbps, and 150 Mbps, a final slice-AMBR of the eMBB S-NSSAI can be configured as 450 Mbps, which is a sum of AMBRs of the PDU sessions. According to another embodiment of the disclosure, when the eMBB slice-AMBR determined to be used by the 5G NF is 1 Gbps and the AMBRs used by the three PDU sessions are 500 Mbps, 300 Mbps, and 400 Mbps, the final slice-AMBR of the eMBB S-NSSAI can be configured as 1 Gbps. Accordingly, the 5G system can control an AMBR that each PDU session can use.

[0059] A terminal can use one or more S-NSSAIs, and a sum of slice-AMBRs of the S-NSSAIs can be configured to be equal to or less than a UE-AMBR. For example, when a UE-AMBR of a terminal is 4 Gbps, a slice-AMBR of an eMBB S-NSSAI used by the terminal is 1 Gbps, a slice-AMBR of a URLLC S-NSSAI is 1 Gbps, and a slice-AMBR of a CIoT S-NSSAI is 500 Mbps, a final UE-AMBR can be configured as 2.5 Gbps, which is a sum of the slice-AMBRs. Generally, CIoT is a communication method, and can be IoT using a cellular network. For example, it can be a technology for providing an IoT service in a mobile communication system (cellular network).

[0060] In another example, when the UE-AMBR of a terminal is 4 Gbps, the slice-AMBR of the eMBB S-NSSAI used by the terminal is 3 Gbps, the slice-AMBR of the URLLC S-NSSAI is 1 Gbps, and the slice-AMBR of the CIoT S-NSSAI is 500 Mbps, the final UE-AMBR can be configured to be 4 Gbps. Therefore, the 5G system can control the slice-AMBR associated with the S-NSSAI.

[0061] Through the above description, operations of the core network NF and the terminal are described in more detail with reference to the accompanying drawings.

[0062] FIG. 1 A registration process according to an embodiment of the present disclosure is shown.

[0063] In reference FIG. 1 Before the description, the UE 100 and the network entities are described. The UE 100 is located in a specific RAN 101 and can configure a radio channel and communicate with the RAN 101. As described above, the RAN 101 can be a base station of a 5G network, a base station of LTE or LTE-A, or a network entity used as a base station in other wireless communication networks. In the following, for ease of description, it is assumed that the RAN 101 is a 5G base station and the mobile communication system is a 5G wireless communication network. In addition, it is assumed that in addition to the RAN 101, the 5G core network also includes an AMF 102, a PCF 103, and a UDM 104. FIG. 1 The portion marked by the dotted line in may be a process that can be omitted when only the signal flow is considered.

[0064] Meanwhile, the 5G system may determine the slice-AMBR of the S-NSSAI that may be used by the UE 100 and provide the slice-AMBR to the UE 100, the RAN 101, and related 5G NFs during the registration procedure of the UE 100.

[0065] refer to FIG. 1 In order to perform the registration procedure, the UE 100 may send a registration request message in operation 110. The registration request message may include a requested NSSAI that the UE desires to use, such as a UE ID, for example, a subscription permanent identifier (SUPI), a 5G globally unique temporary identifier (5G-GUTI), etc. For the purpose of describing the present disclosure, it is assumed that the requested NSSAI includes an eMBB S-NSSAI and a URLLC S-NSSAI.

[0066] In operation 112, the RAN 101 can select the AMF 102 to which the registration request message is transmitted, based on at least one of the received UE ID, the requested NSSAI, and the local policy. The RAN 101 can transfer the registration request message to the selected AMF 102.

[0067] In operation 114, the AMF 102 can transmit, to the UDM 104, an Nudm_SDM_Ge request message to request subscription information of the UE 100. The Nudm_SDM_Ge request message can include the UE ID, e.g., SUPI, etc.

[0068] In operation 116, the UDM 104 can transmit, to the AMF 102 in response thereto, UE subscription information related to the UE ID. The UE subscription information can include subscribed S-NSSAIs to which the UE 100 is subscribed and subscribed slice-AMBRs for each of the subscribed S-NSSAIs. For example, when the UE subscription information includes an eMBB S-NSSAI, an URLLC S-NSSAI, and an IoT S-NSSAI as the plurality of subscribed S-NSSAIs, the subscribed slice-AMBRs of the UE subscription information can include a subscribed slice-AMBR for the eMBB S-NSSAI, a subscribed slice-AMBR for the URLLC S-NSSAI, and a subscribed slice-AMBR for the IoT S-NSSAI. For the purpose of describing the present disclosure, it is assumed that the eMBB S-NSSAI, the URLLC S-NSSAI, and the IoT S-NSSAI are included as the subscribed S-NSSAIs.

[0069] The AMF 102 that receives the UE subscription information from the UDM 104 in operation 116 can determine the allowed NSSAI based on at least one of the requested NSSAI received from the UE 100, the subscribed S-NSSAIs received from the UDM 104, and the local policy, before operation 118. According to another embodiment of the present disclosure, the method in FIG. 1 may acquire the allowed NSSAI from the NSSF (not shown in FIG. 1 For example, the AMF 102 or / and the NSSF can identify that the eMBB-S-NSSAI and the URLLC S-NSSAI included in the requested NSSAI are included in the subscribed S-NSSAIs, and determine to provide the eMBB S-NSAAI and the URLLC S-NSSAI to the allowed NSSAI. The AMF 102 can store the allowed NSSAI and the subscribed slice-AMBRs through the UE context of the UE 100.

[0070] In operation 118, the AMF 102 can establish an access and mobility policy association or / and a UE policy association with the PCF 103. The policy association request message sent by the AMF 102 to the PCF 103 can include at least one of the subscribed S-NSSAI, the allowed NSSAI, the mapping of S-NSSAI, the subscribed slice-AMBR, the SUPI, and a home public land mobile network (HPLMN) ID. At this time, the subscribed slice-AMBR can include all of the subscribed slice-AMBRs received by the AMF 102 from the UDM 104. According to an embodiment of the disclosure, all of the subscribed slice-AMBRs received by the AMF 102 from the UDM 104 can include the subscribed slice-AMBR of the eMBB S-NSSAI, the subscribed slice-AMBR of the URLLC S-NSSAI, and the subscribed slice-AMBR of the IoT S-NSSAI. According to another embodiment of the disclosure, the subscribed slice-AMBR can include only the subscribed slice-AMBR of the S-NSSAI included in the allowed NSSAI determined by the AMF 102 or / and the NSSF. In its detailed example, the subscribed slice-AMBR can include only the subscribed slice-AMBR of the S-NSSAI included in the allowed NSSAI determined by the AMF 102 or / and the NSSF, the subscribed slice-AMBR of the eMBB S-NSSAI, and the subscribed slice-AMBR of the URLLC S-NSSAI.

[0071] In operation 120, the PCF 103 can determine a service network slice-AMBR of each of the received subscribed slice-AMBRs. For example, the PCF 103 can determine the HPLMN of the UE based on the received SUPI and HPLMN ID, and determine the service network slice-AMBR of the S-NSSAI used by the service network based on the subscribed S-NSSAI, the mapping of the S-NSSAI (the S-NSSAI mapped to the subscribed S-NSSAI and used by the service network), and a roaming agreement with the HPLMN. The subscribed slice-AMBR and the service network slice-AMBR determined by the PCF 103 can be the same as or different from each other. The PCF 103 can transmit a policy association response message to the AMF 102 and establish a policy association. The policy association response message can include the service network slice-AMBR.

[0072] The AMF 102 receiving the service network slice-AMBR from the PCF 103 can determine one of using the subscribed slice-AMBR or / and the slice-AMBR modified by the AMF 102 based on the subscribed slice-AMBR or / and the service network slice-AMBR received from the PCF 103 as the slice-AMBR for each S-NSSAI included in the allowed NSSAI of the UE 100. The AMF 102 can add the slice-AMBR to the UE context of the UE 100.

[0073] In operation 122, the AMF 102 can transmit an N2 message to the RAN 101. The N2 message can include the allowed NSSAI, the slice-AMBR to be used for each S-NSSAI included in the allowed NSSAI, the UE-AMBR, and a registration accept message that the AMF 102 transmits to the UE 100. The registration accept message can include the allowed NSSAI and the slice-AMBR for each S-NSSAI included in the allowed NSSAI.

[0074] The RAN 101 receiving the N2 message can store the allowed NSSAI, the slice-AMBR for each S-NSSAI included in the allowed NSSAI, and the UE-AMBR for the UE 100. The RAN 101 can use the stored slice-AMBR and the UE-AMBR to control the uplink and downlink data traffic rate of the UE thereafter. According to various embodiments of the disclosure, when the operation is described only through a signal flow, this operation (the operation stored in the RAN) can be omitted.

[0075] In operation 124, the RAN 101 can transmit a registration accept message to the UE 100. At this time, the registration accept message can further include the allowed NSSAI and the slice-AMBR for each S-NSSAI included in the allowed NSSAI.

[0076] The UE 100 receiving the registration accept message can store the allowed NSSAI and the slice-AMBR for each S-NSSAI included in the allowed NSSAI. The UE 100 can use the stored slice-AMBR in order to control the uplink data traffic rate in the following procedure. According to various embodiments of the disclosure, when the operation is described only through a signal flow, this operation (the operation stored in the UE) can be omitted.

[0077] The UE 100, the RAN 101, and the AMF 102 according to various embodiments of the disclosure can perform the above-described operations by the above-described FIG. 1In addition, RAN 101 and AMF 102 can obtain and store slice-AMBR information by using the above FIG. 1 The process shown obtains slice-AMBR information to provide services to UE 100.

[0078] FIG. 2 The PDU session establishment process according to an embodiment of the present disclosure is shown.

[0079] In reference FIG. 2 Prior to this description, the UE 100 and network entities were described. The UE 100 is located within a specific RAN 101 and can configure radio channels and communicate with the RAN 101. As described above, the RAN 101 can be a base station for a 5G network, a base station for LTE or LTE-A, or a network entity used as a base station in another wireless communication network. Below, for ease of description, it is assumed that the RAN 101 is a 5G base station and the mobile communication system is a 5G wireless communication network. Furthermore, it is assumed that, in addition to the RAN 101, the 5G core network also includes the AMF 102, SMF1 200, PCF 103, UPF1 202, UDM 104, and DN1 203. FIG. 1 PCF 103 and FIG. 2 The PCF 103 may be the same element. In addition, FIG. 2 The portion marked by the dotted line in may be a process that can be omitted when only the signal flow is considered.

[0080] At the same time, the 5G system can determine the slice-AMBR of the S-NSSAI associated with the PDU session during the PDU session establishment process, and provide the slice-AMBR to the UE 100, RAN 101 and related 5G NFs, such as SMF1 200, UPF1202, etc.

[0081] The UE 100 according to an embodiment of the present disclosure may connect to the DN1 203 to initiate a PDU session establishment procedure to transmit and receive data. FIG. 2 In operation 210, the UE 100 may send a PDU session establishment request message to the AMF 102 through the RAN 101 to establish a PDU session. The PDU session establishment request message may include at least one of a PDU session ID, an S-NSSAI to be used by the UE 100, and a DNN.

[0082] In operation 212, the AMF 102 may select an SMF that can manage the PDU session requested by the UE 100. For example, the AMF 102 may select an SMF that supports the S-NSSAI and / or DNN requested by the UE 100.

[0083] In operation 214, the AMF 102 can transmit a PDU session creation request message to the selected SMF 1200. The PDU session creation request message can include at least one of a PDU session ID, an S-NSSAI, a DNN, and a service network slice-AMBR.

[0084] The SMF1 200 can generate a session management (SM) context. The SM context is a set of information for managing the PDU session requested in operation 214. The SM context can be referred to as an SM context ID. In connection with the SM context, one SM context or a plurality of SM contexts can be assigned to one UE. For example, when a plurality of PDU sessions are assigned to one UE, an SM context can be assigned for each PDU session. In this case, a plurality of context IDs can be assigned to one UE.

[0085] In operation 216, the SMF1 200 can request UE 100 subscription information from the UDM 104, and acquire the UE subscription information from the UDM 104. The UE subscription information can include at least one of a subscribed S-NSSAI, a subscribed slice-AMBR for the subscribed S-NSSAI, a subscribed session-AMBR for the subscribed S-NSSAI, and a DNN.

[0086] The SMF1 200 can authenticate the UE request received in operation 214 based on the UE subscription information. For example, the SMF1 200 can identify whether the S-NSSAI and / or the DNN requested by the UE included in the PDU session creation request message is included in the UE subscription information.

[0087] In operation 218, the SMF1 200 can transmit a PDU session creation response message to the AMF 102. When the authentication performed in operation 216 is successful, the PDU session creation response message can include the SM context ID.

[0088] The AMF 102 can store the received SM context ID. The AMF 102 can use the SM context ID in order to indicate the SM context of the PDU session referred to as a PDU session ID.

[0089] In operation 220, the SMF1 200 can establish an SM policy association with the PCF 103. The PCF 103 with which the SMF1 200 establishes the SM policy association can be the same as or different from the PCF 103 with which the AMF 102 has established a policy association in the registration procedure. The policy association request message transmitted by the SMF1 200 to the PCF 103 can include at least one of an S-NSSAI for PDU session establishment, a subscribed slice-AMBR, a service network slice-AMBR, a subscribed session-AMBR, a SUPI, and an HPLMN ID. At this time, the subscribed slice-AMBR can be a subscribed slice-AMBR configured in a PDU session according to a specific S-NSSAI. For example, the subscribed slice-AMBR can be a value corresponding to the S-NSSAI. That is, when the UE establishes two PDU sessions and the two PDU sessions use the same S-NSSAI, the subscribed slice-AMBRs of the two PDU sessions can be the same as each other. Further, the subscribed slice-AMBR is a value stored in the UDM as UE subscription information (UE subscription data), and thus, even if the UE does not establish a PDU session through the corresponding S-NSSAI, the subscribed slice-AMBR can always be stored in the UDM. Further, the service network slice-AMBR can be a service network slice-AMBR for a PDU session used by the service network.

[0090] In operation 222, the PCF 103 can determine an authorized slice-AMBR of the received subscribed slice-AMBR or / and service network slice-AMBR based on at least one of UE subscription information and a local policy. Further, when determining the authorized slice-AMBR, the PCF 103 can consider a roaming agreement with an HPLMN of the UE 100. The subscribed slice-AMBR or the service network slice-AMBR can be the same as or different from the authorized slice-AMBR determined by the PCF 103. Further, the PCF 103 can determine an authorized session-AMBR. The authorized session-AMBR can be a value equal to or smaller than the authorized slice-AMBR. The PCF 103 can transmit a policy association response message to the SMF1 200 and establish a policy association. The policy association response message can include at least one of the authorized slice-AMBR and the authorized session-AMBR.

[0091] The SMF1 200 can determine one of a subscribed slice-AMBR, a slice-AMBR modified by the AMF 102 or the SMF1 200, a service network slice-AMBR, and / or an authorized slice-AMBR to be used as a slice-AMBR for the S-NSSAI associated with the PDU session. The SMF1 200 can add the slice-AMBR to the SM context of the UE 100. In addition, the SMF1 200 can add the session-AMBR to the SM context of the UE 100.

[0092] In operation 224, the SMF1 200 can transmit an N4 session establishment request message to establish an N4 session with the UPF1 202 selected for the PDU session establishment. The N4 session establishment request message transmitted by the SMF1 200 to the UPF1 202 can include at least one of the slice-AMBR and the session-AMBR for the PDU session. The UPF1 202 can store the received slice-AMBR and session-AMBR and use them to control downlink data and / or uplink data traffic.

[0093] In operation 226, the UPF1 202 can transmit an N4 session establishment response message to the SMF1 200.

[0094] In operation 228, the SMF1 200 can transmit a Namf_Communication_N1N2MessageTransfer message to the AMF 102 to inform the PDU session establishment. The Namf_Communication_N1N2MessageTransfer message can include at least one of information transmitted by the SMF1 200 to the AMF 102, an N2 message transmitted by the SMF1 200 to the RAN 101, and an N1 message transmitted by the SMF1 200 to the UE 100.

[0095] The information transmitted by the SMF1 200 to the AMF 102 can include at least one of a PDU session ID, an SM context ID, and a slice-AMBR.

[0096] The N2 message transmitted by the SMF1 200 to the RAN 101 through the AMF 102 can include at least one of a PDU session ID, a session-AMBR, an S-NSSAI, and a slice-AMBR.

[0097] The N1 message sent by SMF1 200 to UE 100 through AMF 102 and RAN 101 may include a PDU session establishment accept message including at least one of S-NSSAI, session-AMBR, and slice-AMBR.

[0098] In operation 230 , the AMF 102 may send a Namf_Communication_N1N2MessageTransfer response message to the SMF1 200 in response to the PDU session establishment based on the message received in operation 228 .

[0099] In operation 232, the AMF 102 may transmit an N2 PDU Session Request message for session establishment to the RAN 101. The N2 PDU Session Request message may include the N2 message received by the AMF 102 from the SMF1 200.

[0100] The RAN 101 may store the S-NSSAI, slice-AMBR, and PDU session ID received in operation 232 and use them to control downlink data and / or uplink data traffic of the PDU session associated with the S-NSSAI. At this time, when the slice-AMBR information of the S-NSSAI exists in the RAN 101 (for example, when the FIG. 1 When obtaining the slice-AMBR of the S-NSSAI during the UE registration process shown in operation 122, or when RAN configuration information exists, the RAN 101 may use the slice-AMBR information pre-stored in the RAN 101 instead of using the slice-AMBR received in operation 232. According to another embodiment of the present disclosure, the RAN 101 may use the slice-AMBR information received in operation 232 instead of using the pre-stored slice-AMBR information.

[0101] In operation 234, the RAN 101 may perform an access network (AN)-specific resource establishment procedure with the UE 100. In the AN-specific resource establishment procedure, the RAN 101 may send a PDU session establishment accept message received from the AMF 102 to the UE 100. The UE 100 may store the received slice-AMBR and use it to control the uplink data flow of the PDU session associated with the S-NSSAI. At this time, when the slice-AMBR information of the S-NSSAI exists in the UE 100 (for example, when the slice-AMBR information of the S-NSSAI is not available in the UE 100), the RAN 101 may send a PDU session establishment accept message received from the AMF 102 to the UE 100. FIG. 1When obtaining the slice-AMBR of the S-NSSAI during the UE registration process shown in operation 124, or when the UE configuration information or the UE policy information exists, the UE 100 may use the slice-AMBR information pre-stored in the UE 100 instead of using the slice-AMBR received in operation 234. According to another embodiment of the present disclosure, the UE 100 may use the slice-AMBR information received in operation 234 instead of using the pre-stored slice-AMBR information.

[0102] In operation 236, SMF1 200, which successfully performs the PDU session establishment procedure, may register SMF1 200 itself as a service SMF of the PDU session in UDM 104. UDM 104 may store the SMF instance ID of SMF1 200.

[0103] The UE 100 may transmit uplink data to the DN1 203 via the RAN 101 and the UPF1 202. In addition, the DN1 203 may transmit downlink data to the UE 100 via the UPF1 202 and the RAN 101.

[0104] [Example 2]

[0105] In passing FIG. 2 After the illustrated process establishes a PDU session for the S-NSSAI, the UE according to various embodiments of the present disclosure can send uplink data traffic to the DN and receive downlink data traffic from the DN. In addition, the UE according to various embodiments of the present disclosure can establish another PDU session for the same S-NSSAI. For example, a first PDU session can be established for communication with DN1 203, and a second PDU session can be established for communication with DN2 300. At this time, the first PDU session and the second PDU session are associated with the same S-NSSAI, so the 5G system should be able to control the sum of the uplink and downlink data traffic of the first PDU session and the second PDU session to be equal to or less than the sum of the slice-AMBRs associated with the S-NSSAI. Although two PDU sessions are described in the above example, according to various embodiments of the present disclosure, the same configuration can be applied even when three or more PDU sessions are established.

[0106] Example 2 describes a method that, when selecting the SMF and UPF for the second PDU session, selects the same SMF and UPF as the SMF and UPF in the first PDU session, manages the slice-AMBR of the S-NSSAI of the first PDU session and the second PDU session by the SMF and / or UPF, and controls the sum of uplink and downlink data traffic.

[0107] FIG. 3A and FIG. 3B A PDU session establishment procedure according to an embodiment of the disclosure is shown.

[0108] In FIG. 3A and FIG. 3B In the description of FIG. 3A and FIG. 3B may be a continuous signal flowchart. For example, the operation of FIG. 3A may be performed after the operation of the flowchart in FIG. 3B However, specific cases in which the order should be changed or omitted will be described separately. In addition, the UE 100 and the network entity are described in FIG. 3A and FIG. 3B The UE 100 is located within a specific RAN 101, and can be configured with a radio channel and communication with the RAN 101. As described above, the RAN 101 can be a base station of a 5G network, a base station of LTE or LTE-A, or a network entity serving as a base station in other wireless communication networks. Hereinafter, for convenience of description, it is assumed that the RAN 101 is a 5G base station, and the mobile communication system is a 5G wireless communication network. In addition, it is assumed that the 5G core network includes the AMF 102, the SMF1 200, the PCF 103, the UPF1 202, the UDM 104, the DN1 203, and the DN2 300 in addition to the RAN 101. The DN1 203 and the DN2 300 can be local or / and physically different DNs. In addition, FIG. 3A and FIG. 3B The part marked by a dotted line in

[0109] Referring to FIG. 3A and FIG. 3B , the UE 100 can establish a first PDU session for an S-NSSAI and exchange uplink data and / or downlink data traffic with the DN1 203 in operation 305 as described in FIG. 2 . In operation 305, the UE 100, the RAN 101, and the UPF1 202 can store a slice-AMBR for the S-NSSAI, and control a data rate of the uplink data and / or the downlink data traffic.

[0110] The UE 100 according to an embodiment of the disclosure can determine to establish another PDU session for the S-NSSAI, i.e., a second PDU session associated with the first PDU session, based on at least one of a UE policy and local configuration information of the UE.

[0111] In operation 310, the UE 100 can transmit a PDU session establishment request message in order to establish a second PDU session. The PDU session establishment request message can include at least one of a PDU session ID, an S-NSSAI, and a DNN to be used by the UE 100. At this time, the S-NSSAI included in the PDU session establishment request can be the same as the S-NSSAI of the first PDU session. In addition, the DNN included in the PDU session establishment request can be the same as or different from the DNN of the first PDU session.

[0112] In operation 312, the AMF 102 can select an SMF capable of managing the PDU session requested by the UE 100. The AMF 102 according to various embodiments of the disclosure can identify that there is a PDU session, i.e., the first PDU session associated with the S-NSSAI requested by the UE 100, based on the UE context stored in the AMF 102, and select the serving SMF1 200 of the first PDU session as the SMF of the second PDU session.

[0113] In operation 314, the AMF 102 can transmit a PDU session creation request message to the selected SMF1 200. The PDU session creation request message can include at least one of a PDU session ID, an S-NSSAI, and a DNN. In addition, the AMF 102 can insert an SM context ID or a PDU session ID associated with the first PDU session into the PDU session creation request message. The AMF 102 can notify the SMF1 200 that the second PDU session request is associated with the first PDU session (e.g., they are PDU sessions using the same S-NSSAI) by inserting the SM context ID or the PDU session ID linked to the first PDU session into the PDU session creation request message.

[0114] The SMF1 200 can generate an SM context of the second PDU session. The SM context is a set of information for managing the requested PDU session in operation 314. The SM context can be referred to as an SM context ID.

[0115] In operation 316, the SMF1 200 can request the subscription information of the UE 100 from the UDM 104 and acquire the UE subscription information from the UDM 104. The UE subscription information can include at least one of a subscribed S-NSSAI, a subscribed slice-AMBR of the subscribed S-NSSAI, a subscribed session-AMBR of the subscribed S-NSSAI, and a DNN. According to another embodiment of the disclosure, the SMF1 200 can omit operation 316 and can use the UE subscription information received in operation 216 of the message 200. FIG. 2 In operation 318, the SMF1 200 can create an SM context of the second PDU session. The SM context is a set of information for managing the requested PDU session. The SM context can be referred to as an SM context ID. The SMF1 200 can create the SM context of the second PDU session by using the SM context of the first PDU session.

[0116] The SMF1 200 can authenticate the UE request received in operation 314 based on the UE subscription information. For example, the SMF1 200 can identify whether the S-NSSAI and / or the DNN requested by the UE, which is included in the PDU session creation request message, is included in the UE subscription information.

[0117] In operation 318, the SMF1 200 can transmit a PDU session creation response message to the AMF 102. The PDU session creation response message can include the SM context ID of the second PDU session.

[0118] The AMF 102 can store the received SM context ID. The AMF 102 can use the second SM context ID in order to indicate the SM context of the second PDU session, which is referred to as a second PDU session ID.

[0119] In operation 320, the SMF1 200 can establish an SM policy association for the second PDU session with the PCF 103. The PCF 103 with which the SMF1 200 establishes the SM policy association can be the same as or different from the PCF 103 with which the SMF1 200 has established the policy association in the first PDU session establishment procedure. The policy association request message transmitted by the SMF1 200 to the PCF 103 can include at least one of the S-NSSAI for the second PDU session establishment, the subscribed slice-AMBR, the serving network slice-AMBR, the subscribed session-AMBR, the SUPI, and the HPLMN ID. At this time, the subscribed slice-AMBR can be the subscribed slice-AMBR in the second PDU session configured according to the S-NSSAI. For example, the subscribed slice-AMBR can be a value corresponding to the S-NSSAI. That is, when the UE establishes two PDU sessions and the two PDU sessions use the same S-NSSAI, the subscribed slice-AMBRs of the two PDU sessions can be the same as each other. Further, the subscribed slice-AMBR is a value stored in the UDM as the UE subscription information (UE subscription data), and thus, the subscribed slice-AMBR can always be stored in the UDM even if the UE does not establish a PDU session through the corresponding S-NSSAI. Further, the serving network slice-AMBR can be the serving network slice-AMBR for the second PDU session of the serving network.

[0120] In operation 322, PCF 103 may determine an authorized slice-AMBR for the received subscribed slice-AMBR or serving network slice-AMBR based on at least one of the UE subscription information and a local policy. Furthermore, PCF 103 may consider the roaming agreement with the UE's HPLMN when determining the authorized slice-AMBR. The subscribed slice-AMBR or serving network slice-AMBR may be the same as or different from the authorized slice-AMBR determined by PCF 103. Furthermore, PCF 103 may determine an authorized session-AMBR. The authorized session-AMBR may be a value equal to or less than the authorized slice-AMBR. PCF 103 may send a policy association response message to SMF1 200 and establish a policy association. The policy association response message may include at least one of the authorized slice-AMBR and the authorized session-AMBR.

[0121] According to another embodiment of the present disclosure, SMF1 200 may use FIG. 2 The information of the authorized slice-AMBR or the authorized session-AMBR received in operation 222 is used.

[0122] According to another embodiment of the present disclosure, SMF1 200 may use FIG. 2 All information of the authorized slice-AMBR received in operation 222 and the authorized session-AMBR received in operation 322.

[0123] SMF1 200 may determine the slice-AMBR to be used for the first PDU session and the second PDU session. FIG. 2 As shown, SMF1 200 may use the slice-AMBR determined during the first PDU session establishment procedure for the second PDU session. According to another embodiment of the present disclosure, SMF1 200 may newly determine the slice-AMBR during the second PDU session establishment procedure, and if the newly determined slice-AMBR is different from the slice-AMBR determined during the first PDU session establishment procedure, SMF1 200 may add the slice-AMBR to the SM context of the first PDU session of UE 100 and may additionally perform the same operation as described in operation 350 in operation 322.

[0124] The slice-AMBR for the first PDU session and the second PDU session can be configured as a sum of the AMBR of the first PDU session and the AMBR of the second PDU session. At this time, when the sum of the AMBR of the first PDU session and the AMBR of the second PDU session is greater than the value of the subscribed slice-AMBR, the service network slice-AMBR, or the authorized slice-AMBR, the SMF1 200 can determine to use one of the subscribed slice-AMBR or the slice-AMBR modified by the AMF 120 or the SMF1 200 based on the subscribed slice-AMBR, the service network slice-AMBR, and the authorized slice-AMBR as the slice-AMBR for the first PDU session and the second PDU session. The SMF1 200 can add the slice-AMBR to the SM context of the second PDU session of the UE 100. In addition, the SMF1 200 can add the session-AMBR of the second PDU session to the SM context of the second PDU session of the UE 100.

[0125] In operation 324, the SMF1 200 can establish an N4 session with the UPF1 202 selected for the establishment of the second PDU session. For example, the SMF1 200 can select the UPF1 202 of the first PDU session as the UPF for the second PDU session. The N4 session establishment request message transmitted by the SMF1 200 to the UPF1 202 can include at least one of the slice-AMBR and the session-AMBR of the second PDU session. The UPF1 202 can store the received slice-AMBR and session-AMBR and use them to control downlink data and / or uplink data traffic. For example, the UPF1 202 can control the sum of downlink data traffic transmitted through a core network (CN) tunnel for the first PDU session and downlink data traffic transmitted through a CN tunnel for the second PDU session to be less than or equal to the received slice-AMBR. When downlink traffic exceeding the slice-AMBR is generated, the UPF1 202 can discard some of the downlink data traffic of the first PDU session and / or the second PDU session.

[0126] In operation 326, the UPF1 202 can transmit an N4 session establishment response message to the SMF1 200.

[0127] In operation 328, the SMF1 200 can send a Namf_Communication_N1N2MessageTransfer message in order to inform the AMF 102 about the PDU session establishment. The Namf_Communication_N1N2MessageTransfer message can include at least one of information that the SMF1 200 sends to the AMF 102, an N2 message that the SMF1 200 sends to the RAN 101, and an N1 message that the SMF1 200 sends to the UE 100.

[0128] The information that the SMF1 200 sends to the AMF 102 can include at least one of a PDU session ID, an SM context ID, and a slice-AMBR.

[0129] The N2 message that the SMF1 200 sends to the RAN 101 can include at least one of a PDU session ID, a session-AMBR, a session-NSSAI, and a slice-AMBR.

[0130] The N1 message that the SMF1 200 sends to the UE 100 can include a PDU session establishment accept message including at least one of an S-NSSAI, a session-AMBR, and a slice-AMBR.

[0131] In operation 330, the AMF 102 can send a Namf_Communication_N1N2MessageTransfer response message to the SMF1 200 in response to the PDU session establishment.

[0132] In operation 332, the AMF 102 can send an N2 PDU session request message to the RAN 101. The N2 PDU session request message can include the N2 message that the AMF 102 receives from the SMF1 200.

[0133] The RAN 101 can store the received S-NSSAI and slice-AMBR and PDU session ID, and thereafter use them to control downlink data and / or uplink data traffic of the second PDU session. For example, the RAN 101 can control that the sum of uplink data traffic or downlink data traffic of the first PDU session and uplink data traffic or downlink data traffic of the second PDU session is less than or equal to the received slice-AMBR. When uplink traffic or downlink traffic that exceeds the slice-AMBR is generated, the RAN 101 can discard some of the data traffic of the first PDU session and / or the second PDU session.

[0134] In operation 334, the RAN 101 can perform an AN-specific resource setup procedure with the UE 100. In the AN-specific resource setup procedure, the RAN 101 can transmit, to the UE 100, the PDU session establishment accept message received from the AMF 102. The UE 100 can store the received slice-AMBR and use it to control uplink data traffic of the PDU sessions associated with the S-NSSAI. For example, the UE 100 can control a sum of uplink data traffic of the first PDU session and uplink data traffic of the second PDU session to be less than or equal to the received slice-AMBR. When generating uplink data traffic exceeding the slice-AMBR, the UE 100 can first transmit a PDU session and / or data traffic having a higher priority, and then transmit a PDU session and / or data traffic having a lower priority, or discard some data.

[0135] In operation 336, the SMF1 200 that successfully performs the PDU session establishment procedure can register itself as a serving SMF of the second PDU session in the UDM 104. The UDM 104 can store the SMF instance ID of the SMF1 200.

[0136] The UE 100 can transmit uplink data to the DN1 203 via the RAN 101 and the UPF1 202. Also, the DN1 203 can transmit downlink data to the UE 100 via the UPF1 202 and the RAN 101.

[0137] According to an embodiment of the disclosure, the slice-AMBR determined during the second PDU session establishment procedure can be different from the slice-AMBR determined during the first PDU session establishment procedure. To control uplink and / or downlink data traffic of the first PDU session, the UE 100, the RAN 101, and the UPF1 202 can use the slice-AMBR determined during the second PDU session establishment procedure. According to another embodiment of the disclosure, the SMF1 200 can perform operations 352 and 354 to transmit the changed slice-AMBR to be used for the first PDU session to the UPF1 202 and transmit the changed slice-AMBR to be used for the first PDU session to be used by the UE 100 and the RAN 101 to the AMF 102. Accordingly, in operation 358, the AMF 102 can transmit the changed slice-AMBR to be used for the first PDU session to the RAN 101. In operation 360, the RAN can update the first PDU session and transmit the changed slice-AMBR to be used for the first PDU session to the UE 100.

[0138] The UE 100 may use the slice-AMBR received in operation 360 to control the uplink data flow of the first PDU session. The RAN 101 may use the slice-AMBR received in operation 358 to control the uplink and / or downlink data flow of the first PDU session. The UPF 1202 may use the slice-AMBR received in operation 352 to control the downlink data flow of the first PDU session.

[0139] [Example 3]

[0140] In passing FIG. 2 After the illustrated process establishes a PDU session for the S-NSSAI, the UE according to various embodiments of the present disclosure can send uplink data traffic to the DN and receive downlink data traffic from the DN. In addition, the UE according to various embodiments of the present disclosure can establish another PDU session for the same S-NSSAI. For example, a first PDU session can be established for communication with DN1 203, and a second PDU session can be established for communication with DN2 300. At this time, the first PDU session and the second PDU session are associated with the same S-NSSAI, so the 5G system should be able to control the sum of the uplink and downlink data traffic of the first PDU session and the second PDU session to be equal to or less than the sum of the slice-AMBRs associated with the S-NSSAI.

[0141] Embodiment 3 describes a method that, when selecting an SMF for the second PDU session, selects the same SMF as the SMF used in the first PDU session, and has the SMF manage the slice-AMBR of the S-NSSAI of the first and second PDU sessions and control the sum of uplink and downlink data traffic. According to the method described in Embodiment 3, the UPF selected for the first PDU session and the UPF selected for the second PDU session can be different.

[0142] FIG. 4A and FIG. 4B The PDU session establishment process according to an embodiment of the present disclosure is shown.

[0143] In the description FIG. 4A and FIG. 4B Before, FIG. 4A and FIG. 4B is a continuous signal flow graph. For example, FIG. 4A The operations of the flowchart are executed after FIG. 4B However, specific cases where the order should be changed or omitted will be described separately. FIG. 4A and FIG. 4BThe UE 100 and network entities are described in FIGS. 1 to 4. The UE 100 is located within a specific RAN 101, and can be configured with a radio channel and communication with the RAN 101. As described above, the RAN 101 can be a base station of a 5G network, a base station of LTE or LTE-A, or a network entity serving as a base station in other wireless communication networks. Hereinafter, for convenience of description, it is assumed that the RAN 101 is a 5G base station, and the mobile communication system is a 5G wireless communication network. Further, it is assumed that, in addition to the RAN 101, a 5G core network includes an AMF 102, an SMF1 200, a PCF 103, a UPF1 202, a UPF2 400, a UDM 104, a DN1 203, and a DN2 300. The DN1 203 and the DN2 300 can be local or / and physically different DNs. The UPF1 202 and the UPF2 400 can be logically and / or physically different UPFs. Further, FIG. 4A and FIG. 4B The part marked by a dashed line in FIG. 4 can be a procedure that can be omitted when considering only a signal flow.

[0144] Referring to FIG. 2 and FIG. 3A , the UE 100 can establish a first PDU session for an S-NSSAI, and initiate a second PDU session establishment procedure for the same S-NSSAI, as shown in FIG. 3B , FIG. 2 and FIG. 4A For a more detailed description, the SMF1 200 can determine a slice-AMBR to be used for the first PDU session and the second PDU session after performing operations 210 to 236 of FIG. 3A (operation 411 in the first block of FIG. 3B , and then performing operations 310 to 322 of FIG. 4A and FIG. 4A (operation 412 in the second block of FIG. 4B .

[0145] The SMF1 200 according to an embodiment of the disclosure can determine a session-AMBR for the first PDU session and a session-AMBR for the second PDU session, taking into account the slice-AMBR.

[0146] In operation 424, the SMF1 200 can establish an N4 session with the UPF1 202 selected for the second PDU session establishment. For example, the SMF1 200 according to an embodiment of the disclosure can identify that there is a PDU session, i.e., the first PDU session associated with the S-NSSAI requested by the UE 100, based on the SM context stored in the SMF1 200. When the DNN of the first PDU session is different from the DNN requested for the second PDU session establishment, the SMF1 200 can select a different UPF. Alternatively, when the DNN of the first PDU session is the same as the DNN requested for the second PDU session establishment, the SMF1 200 can select the same UPF as shown in Embodiment 2. FIG. 3A and FIG. 3B A case in which a different UPF is selected is shown.

[0147] The N4 session establishment request message that the SMF1 200 transmits to the UPF1 202 can include at least one of the slice-AMBR and the session-AMBR of the second PDU session. The UPF2 400 can store the received slice-AMBR and session-AMBR and use them to control downlink data and / or uplink data traffic.

[0148] In operation 426, the UPF1 202 can transmit an N4 session establishment response message to the SMF1 200.

[0149] In operation 431, the SMF1 200 that receives the N4 session establishment response message can perform operations 328 to 336 of FIG. 3.

[0150] The RAN 101 can store the S-NSSAI and the slice-AMBR and the received PDU session ID and use them thereafter to control downlink data and / or uplink data traffic of the second PDU session. For example, the RAN 101 can control the sum of the uplink data traffic and / or the downlink data traffic of the first PDU session and the uplink data traffic and / or the downlink data traffic of the second PDU session to be less than or equal to the received slice-AMBR. When uplink traffic or downlink traffic exceeding the slice-AMBR is generated, the RAN 101 can discard some of the data traffic of the first PDU session and / or the second PDU session.

[0151] The UE 100 can store the received slice-AMBR and use it to control uplink data traffic of PDU sessions associated with the S-NSSAI. For example, the UE 100 can control the sum of uplink data traffic of the first PDU session and uplink data traffic of the second PDU session to be less than or equal to the received slice-AMBR. When uplink data traffic exceeding the slice-AMBR is generated, the UE 100 can first transmit a PDU session or data traffic having a higher priority, later transmit a PDU session or data traffic having a lower priority, or discard some data.

[0152] According to an embodiment of the disclosure, the session-AMBR allocated for each PDU session can be configured to be less than or equal to the slice-AMBR configured to be provided for a specific network slice in the network. The UPF1 202 can control downlink data traffic by using the session-AMBR for the first PDU session, and the UPF2 400 can control downlink data traffic by using the session-AMBR for the second PDU session.

[0153] When the sum of the session-AMBR of the first PDU session and the session-AMBR of the second PDU session is less than or equal to the slice-AMBR, the sum of downlink data traffic of the first PDU session and the second PDU session transmitted to the RAN 101 via the UPF1 202 and the UPF2 400 can not exceed the slice-AMBR managed by the RAN 101.

[0154] When the sum of the session-AMBR of the first PDU session and the session-AMBR of the second PDU session is greater than the slice-AMBR, the sum of downlink data traffic of the first PDU session and the second PDU session transmitted to the RAN 101 via the UPF1 202 and the UPF2 400 can exceed the slice-AMBR managed by the RAN 101. In this case, the RAN 101 can discard some data in the downlink data traffic of the first PDU session and / or the second PDU session.

[0155] The UE 100 can transmit uplink data to the DN1 203 via the RAN 101 and the UPF1 202. In addition, the DN1 203 can transmit downlink data to the UE 100 via the UPF1 202 and the RAN 101.

[0156] According to various embodiments of the disclosure, the slice-AMBR determined during the second PDU session establishment procedure can be different from the slice-AMBR determined during the first PDU session establishment procedure. The SMF 1200 can perform operations 350 to 360 described in FIG. 2 and FIG. 5A The UE 100, the RAN 101, and the UPF1 202 can control uplink and / or downlink data traffic by using the slice-AMBR updated for the first PDU session.

[0157] [Embodiment 4]

[0158] After the PDU session for the S-NSSAI is established through the procedure shown in FIG. 5B , the UE according to various embodiments of the disclosure can transmit uplink traffic to the DN and receive downlink data traffic from the DN. In addition, the UE according to various embodiments of the disclosure can establish another PDU session for the same S-NSSAI. For example, the first PDU session can be established for communication with the DN1 203, and the second PDU session can be established for communication with the DN2 300. At this time, the first PDU session and the second PDU session are associated with the same S-NSSAI, and thus the 5G system should be able to control the sum of uplink and downlink data traffic of the first PDU session and the second PDU session to be equal to or less than the sum of the slice-AMBRs associated with the S-NSSAI.

[0159] Embodiment 4 describes a method by which the AMF manages the slice-AMBRs of the S-NSSAI of the first PDU session and the second PDU session and controls the sum of uplink and downlink data traffic. According to the method described in Embodiment 4, the SMF and / or the UPF for the first PDU session can be different from the SMF and / or the UPF for the second PDU session.

[0160] FIG. 5A and FIG. 5B A PDU session establishment procedure according to an embodiment of the disclosure is shown.

[0161] In the description of FIG. 5A and FIG. 5B , FIG. 5A and FIG. 5B may be continuous signal flowcharts. For example, the operations of the flowchart in FIG. 5A may be performed after the operations of the flowchart in FIG. 5B . However, specific cases in which the order should be changed or omitted will be described separately. In addition, in FIG. 5A and FIG. 5BThe UE 100 and network entities are described in the following. The UE 100 is located within a specific RAN 101, and can be configured with a radio channel and communication with the RAN 101. As described above, the RAN 101 can be a base station of a 5G network, a base station of LTE or LTE-A, or a network entity serving as a base station in other wireless communication networks. Hereinafter, for ease of description, it is assumed that the RAN 101 is a 5G base station, and the mobile communication system is a 5G wireless communication network. Further, it is assumed that, in addition to the RAN 101, a 5G core network includes an AMF 102, an SMF1 200, an SMF2 500, a PCF 103, a UPF1 202, a UPF2 400, a UDM 104, a DN1 203, and a DN2 300. The DN1 203 and the DN2 300 can be local or / and physically different DNs. The UPF1 202 and the UPF2 400 can be logically and / or physically different UPFs. The SMF1 200 and the SMF2 500 can be logically or / and physically different SMFs. Further, FIG. 5A and FIG. 5B The part marked by a dashed line in the following can be a procedure that can be omitted when considering only signal flows. FIG. 2 and FIG. 2 The signal flow marked by a dashed line in the following.

[0162] Referring to FIG. 3A and FIG. 3B , in operation 511, the UE 100 can establish a first PDU session for the S-NSSAI as described in FIG. 3A , and exchange uplink data and / or downlink data traffic with the DN1 203. Accordingly, in operation 511, the UE 100, the RAN 101, and the UPF1 202 can store the slice-AMBR for the S-NSSAI, and control the data rate of the uplink data and / or the downlink data traffic.

[0163] Meanwhile, as illustrated in FIG. 3B or FIG. 2 , during the first PDU session establishment procedure, in operation 228 or operation 328, the Namf_Communication_N1N2MessageTransfer message transmitted by the SMF1 200 to the AMF 102 can include the slice-AMBR information and the session-AMBR information for the first PDU session of the S-NSSAI. The AMF 102 can store the slice-AMBR information and the session-AMBR information as a UE context.

[0164] The UE 100 according to an embodiment of the disclosure can determine to establish another PDU session for the S-NSSAI, i.e., a second PDU session associated with the first PDU session, based on at least one of a UE policy and local configuration information of the UE.

[0165] In operation 510, the UE 100 can transmit a PDU session establishment request message in order to establish a second PDU session. The PDU session establishment request message for establishing the second PDU session can include at least one of a PDU session ID, an S-NSSAI, and a DNN to be used by the UE 100. At this time, the S-NSSAI included in the PDU session establishment request can be the same as the S-NSSAI of the first PDU session. In addition, the DNN included in the PDU session establishment request can be the same as or different from the DNN of the first PDU session.

[0166] In operation 512, the AMF 102 can select an SMF capable of managing the PDU session requested by the UE 100. For example, the AMF 102 can select an SMF supporting the S-NSSAI and / or the DNN requested by the UE 100. According to an embodiment of the disclosure, the SMF selected by the AMF 102 can be different from the serving SMF1 200 of the first PDU session.

[0167] In operation 514, the AMF 102 can transmit a PDU session creation request message to the selected SMF2 500. The PDU session creation request message can include at least one of a PDU session ID, an S-NSSAI, and a DNN. The AMF 102 according to an embodiment of the disclosure can identify that there is a UE session, i.e., a first UE session associated with the S-NSSAI requested by the UE 100, based on a UE context stored in the AMF 102. The PDU session creation request message for establishing the second PDU session can include a slice-AMBR of the first PDU session, a session-AMBR, and a serving SMF of the first PDU session, i.e., SMF1 ID information stored by the AMF 102.

[0168] In operation 514, the SMF2 500 can generate an SM context of the second PDU session based on the reception of the message. The SM context is a set of information for managing the requested PDU session in operation 514. The SM context can be referred to as an SM context ID.

[0169] In operation 516, the SMF2 500 can request the subscription information of the UE 100 from the UDM 104, and acquire the UE subscription information from the UDM 104 in response thereto. The UE subscription information can include at least one of the subscribed S-NSSAI, the subscribed slice-AMBR of the subscribed S-NSSAI, the subscribed session-AMBR of the subscribed S-NSSAI, and the DNN.

[0170] The SMF2 500 can authenticate the UE request received in operation 514 based on the UE subscription information acquired from the UDM 104. For example, the SMF2 500 can identify whether the S-NSSAI and / or the DNN requested by the UE, included in the PDU session creation request message, is included in the UE subscription information.

[0171] In operation 518, the SMF2 500 can transmit a PDU session creation response message to the AMF 102. The PDU session creation response message can include the SM context ID of the second PDU session.

[0172] The AMF 102 can store the SM context ID received in operation 518. The AMF 102 can use the second SM context ID in order to indicate the SM context of the second PDU session, referred to as a second PDU session ID.

[0173] In operation 520, the SMF2 500 can establish an SM policy association for the second PDU session with the PCF 103. The PCF 103 with which the SMF2 200 establishes the SM policy association can be the same as or different from the PCF 103 with which the SMF1 200 has already established the policy association in the first PDU session establishment procedure. The policy association request message transmitted by the SMF2 500 to the PCF 103 can include at least one of the S-NSSAI for the second PDU session establishment, the subscribed slice-AMBR, the service network slice-AMBR, the subscribed session-AMBR, the SUPI, and the HPLMN ID. At this time, the subscribed slice-AMBR can be the subscribed slice-AMBR of the second PDU session. In addition, the service network slice-AMBR can be the service network slice-AMBR of the service network for the second PDU session.

[0174] In operation 522, the PCF 103 can determine an authorized slice-AMBR of a received subscribed slice-AMBR or a service network slice-AMBR based on at least one of the UE subscription information and the local policy. Further, when determining the authorized slice-AMBR, the PCF 103 can consider a roaming agreement with the HPLMN of the UE. The subscribed slice-AMBR or the service network slice-AMBR can be the same as or different from the authorized slice-AMBR determined by the PCF 103. Further, the PCF 103 can determine an authorized session-AMBR. The authorized session-AMBR can be a value equal to or less than the authorized slice-AMBR. The PCF 103 can transmit a policy association response message to the SMF2 500 and establish a policy association. The policy association response message can include at least one of the authorized slice-AMBR and the authorized session-AMBR.

[0175] The SMF2 500 can determine a slice-AMBR to be used for the first PDU session and the second PDU session. The SMF2 500 can determine the slice-AMBR based on at least one of the slice-AMBR and the session-AMBR of the first PDU session received in operation 514 and the slice-AMBR and the session-AMBR of the second PDU session received in operations 516 to 522. For example, the SMF2 500 can determine to use the slice-AMBR received from the AMF 102 in operation 514 for the second PDU session. According to another embodiment of the disclosure, the SMF1 200 can newly determine the slice-AMBR during the second PDU session establishment procedure. The SMF2 500 can determine the slice-AMBR in a manner similar to that described in Embodiments 2 to 3. For example, the slice-AMBR to be used for the first PDU session and the second PDU session can be configured as a sum of the AMBR of the first PDU session and the AMBR of the second PDU session. At this time, when the sum of the AMBR of the first PDU session and the AMBR of the second PDU session is greater than the value of the subscribed slice-AMBR, the service network slice-AMBR, or the authorized slice-AMBR, the SMF1 200 can determine to use one of the subscribed slice-AMBR or the slice-AMBR modified by the AMF 120 or the SMF1 200 based on the subscribed slice-AMBR, the service network slice-AMBR, and the authorized slice-AMBR as the slice-AMBR for the first PDU session and the second PDU session. The SMF2 500 can add the slice-AMBR to the SM context of the second PDU session of the UE 100. The SMF2 500 can add the session-AMBR of the second PDU session to the SM context of the second PDU session of the UE 100.

[0176] In operation 524, the SMF2 500 can establish an N4 session with the UPF2 501 selected for the second PDU session establishment. The N4 session establishment request message transmitted by the SMF2 500 to the UPF2 501 can include at least one of the slice-AMBR and the session-AMBR of the second PDU session. The UPF2 501 can store the received slice-AMBR and session-AMBR and use them hereafter to control downlink data and / or uplink data traffic.

[0177] In operation 526, the UPF2 501 can transmit an N4 session establishment response message to the SMF2 500.

[0178] In operation 528, the SMF2 500 can transmit a Namf_Communication_N1N2MessageTransfer message in order to inform the AMF 102 of the session establishment with the UPF2 501. The Namf_Communication_N1N2MessageTransfer message can include at least one of information that the SMF2 500 transmits to the AMF 102, an N2 message that the SMF2 500 transmits to the RAN 101, and an N1 message that the SMF2 500 transmits to the UE 100.

[0179] The information that the SMF2 500 transmits to the AMF 102 can include at least one of a PDU session ID, an SM context ID, a slice-AMBR, and a session-AMBR. When the slice-AMBR received in operation 528 is different from the slice-AMBR that the AMF 102 stores as being used by the first PDU session, the AMF 102 can update the slice-AMBR of the first PDU session of the UE 100 that the AMF 102 stores to the newly received slice-AMBR.

[0180] The N2 message that the SMF1 200 transmits to the RAN 101 through the AMF 102 can include at least one of a PDU session ID, a session-AMBR, an S-NSSAI, and a slice-AMBR.

[0181] The N1 message that the SMF1 200 transmits to the UE 100 through the AMF 102 and the RAN 101 can include a PDU session establishment accept message including at least one of an S-NSSAI, a session-AMBR, and a slice-AMBR.

[0182] In operation 530, the AMF 102 can transmit a Namf_Communication_N1N2MessageTransfer response message to the SMF2 500 in response to the message of the session establishment with the UPF2 501.

[0183] In operation 532, the AMF 102 can transmit an N2 PDU session request message for the second PDU session to the RAN 101. The N2 PDU session request message can include the N2 message that the AMF 102 receives from the SMF2 500.

[0184] The RAN 101 can store the S-NSSAI and the slice-AMBR and the received PDU session ID, and thereafter use them to control downlink data and / or uplink data traffic of the second PDU session. For example, the RAN 101 can control that the sum of the uplink data traffic or the downlink data traffic of the first PDU session and the uplink data traffic or the downlink data traffic of the second PDU session is less than or equal to the received slice-AMBR. When generating uplink traffic or downlink traffic exceeding the slice-AMBR, the RAN 101 can discard some of the data traffic of the first PDU session and / or the second PDU session.

[0185] In operation 534, the RAN 101 can perform an AN-specific resource setup procedure with the UE 100 according to the second PDU session setup. In the AN-specific resource setup procedure, the RAN 101 can transmit the PDU session setup accept message received from the AMF 102 to the UE 100. The UE 100 can store the received slice-AMBR and use it to control uplink data traffic of the PDU session associated with the S-NSSAI. For example, the UE 100 can control that the sum of the uplink data traffic of the first PDU session and the uplink data traffic of the second PDU session is less than or equal to the received slice-AMBR. When generating uplink data traffic exceeding the slice-AMBR, the UE 100 can first transmit the PDU session or data traffic having a higher priority, later transmit the PDU session or data traffic having a lower priority, or discard some data.

[0186] In operation 536, the SMF2 500 that successfully performs the second PDU session setup procedure can register itself as a serving SMF of the second PDU session in the UDM 104. The UDM 104 can store the SMF instance ID of the SMF2 500.

[0187] The UE 100 can transmit uplink data to the DN 501 via the RAN 101 and the UPF1 202. Also, the DN1 203 can transmit downlink data to the UE 100 via the UPF 501 and the RAN 101.

[0188] According to various embodiments of the present disclosure, the slice-AMBR determined during the second PDU session establishment procedure can be different from the slice-AMBR determined during the first PDU session establishment procedure. To control the uplink and / or downlink data traffic of the first PDU session, the UE 100 and the RAN 101 can use the slice-AMBR received during the second PDU session establishment procedure. Since the UPF1 202 does not participate in the second PDU session, the slice-AMBR information of the UPF1 202 can need to be updated. Accordingly, the AMF 102 or the SMF2 500 can update the slice-AMBR of the first PDU session used by the UE 100, the RAN 101, and the UPF1 202.

[0189] For example, the AMF 102 can compare the slice-AMBR of the S-NSSAI received in operation 528 with the slice-AMBR of the S-NSSAI stored in the AMF 102. When the slice-AMBR of the S-NSSAI received in operation 528 is different from the slice-AMBR of the S-NSSAI stored in the AMF 102, the AMF 102 can determine to change the slice-AMBR of the first PDU session to the latest slice-AMBR value, i.e., the slice-AMBR received in operation 528. Accordingly, in operation 548a, the AMF 102 can transmit the latest slice-AMBR value to the SMF1 200 which is the serving SMF of the first PDU session.

[0190] According to another embodiment of the present disclosure, determining the slice-AMBR of the second PDU session, the SMF2 500 can compare the slice-AMBR of the S-NSSAI received in operation 514 with the slice-AMBR newly determined by the SMF2 500. When the slice-AMBR of the S-NSSAI received in operation 514 is different from the slice-AMBR determined by the SMF2 500, the SMF2 500 can determine to change the slice-AMBR of the first PDU session to the latest slice-AMBR value, i.e., the slice-AMBR determined for the second PDU session after operation 514. Accordingly, in operation 548b, by using the serving SMF information of the first session received in operation 514, the SMF2 500 can transmit the latest slice-AMBR value to the SMF1 200.

[0191] As described above FIG. 5AThe SMF1 200 that receives the latest slice-AMBR can determine to update the slice-AMBR of the first PDU session as illustrated in operation 350. Accordingly, in operation 550, the NF including the SMF1 200 can perform operations similar to operations 350 to 360 described in FIG. 5B and FIG. 5A . Thereafter, the UE 100, the RAN 101, and the UPF1 202 can control uplink and / or downlink data traffic by using the slice-AMBR updated for the first PDU session.

[0192] [Embodiment 5]

[0193] After the PDU session for the S-NSSAI is established through the procedure illustrated in FIG. 5B , the UE according to various embodiments of the disclosure can transmit uplink traffic to the DN and receive downlink data traffic from the DN. In addition, the UE according to various embodiments of the disclosure can establish another PDU session for the same S-NSSAI. For example, the first PDU session can be established for communication with the DN1 203, and the second PDU session can be established for communication with the DN2 300. At this time, the first PDU session and the second PDU session are associated with the same S-NSSAI, and thus the 5G system should be able to control the sum of uplink and downlink data traffic of the first PDU session and the second PDU session to be equal to or less than the sum of slice-AMBRs associated with the S-NSSAI.

[0194] Embodiment 5 describes a method by which the UDM manages slice-AMBRs of S-NSSAI of the first PDU session and the second PDU session and controls the sum of uplink and downlink data traffic. According to the method described in Embodiment 5, the SMF and / or the UPF for the first PDU session can be different from the SMF and / or the UPF for the second PDU session.

[0195] Embodiment 5 is described using the PDU session establishment procedure described above FIG. 2 and FIG. 2 .

[0196] Referring to FIG. 3B and FIG. 3A , in operation 511, the UE 100 can determine to establish another PDU session for the same S-NSSAI as the first PDU session as described in FIG. 3BThe first PDU session for the S-NSSAI is established, and uplink data and / or downlink data traffic is exchanged with the DN1 203. In operation 511, the UE 100, the RAN 101, and the UPF1 202 can store the slice-AMBR for the S-NSSAI and control the data rate of the uplink data and / or downlink data traffic.

[0197] As shown in operation 236 of FIG. 2, the registration message transmitted by the SMF1 200 to the UDM 104 can include the slice-AMBR information and the session-AMBR information used by the first PDU session for the S-NSSAI during the first PDU session establishment procedure. The UDM 104 can store the slice-AMBR information and the session-AMBR information as SM data of the UE. FIG. 2 The UE 100 according to an embodiment of the disclosure can determine to establish another PDU session for the S-NSSAI, i.e., a second PDU session associated with the first PDU session, based on at least one of a UE policy and local configuration information of the UE.

[0198] In operation 510, the UE 100 can transmit a PDU session establishment request message in order to establish a second PDU session. The PDU session establishment request message can include at least one of a PDU session ID, an S-NSSAI, and a DNN to be used by the UE 100. At this time, the S-NSSAI included in the PDU session establishment request can be the same as the S-NSSAI of the first PDU session. In addition, the DNN included in the PDU session establishment request can be the same as or different from the DNN of the first PDU session.

[0199] In operation 512, the AMF 102 can select an SMF capable of managing the PDU session requested by the UE 100. For example, the AMF 102 can select an SMF supporting the S-NSSAI and / or the DNN requested by the UE 100. According to various embodiments of the disclosure, the SMF selected by the AMF 102 can be different from the serving SMF1 200 of the first PDU session.

[0200] In operation 514, the AMF 102 can transmit a PDU session creation request message to the selected SMF2 500. The PDU session creation request message can include at least one of a PDU session ID, an S-NSSAI, and a DNN.

[0201]

[0202] ​The SMF2 500 can generate an SM context for the second PDU session. In operation 514, the SM context is a set of information for managing the requested PDU session. The SM context can be referred to as an SM context ID.

[0203] In operation 516, the SMF2 500 can request the subscription information of the UE 100 from the UDM 104, and acquire the UE subscription information from the UDM 104 in response thereto. The UE subscription information can include at least one of a subscribed S-NSSAI, a subscribed slice-AMBR of the subscribed S-NSSAI, a subscribed session-AMBR of the subscribed S-NSSAI, and a DNN. The UDM 104 according to various embodiments of the disclosure can provide the SMF2 500 with information related to the first PDU session of the UE 100 (e.g., a slice-AMBR and / or a session-AMBR for the first PDU session).

[0204] The SMF2 500 can authenticate the UE request received in operation 514 based on the UE subscription information. For example, the SMF2 500 can identify whether the S-NSSAI and / or the DNN requested by the UE 100, included in the PDU session creation request message, is included in the UE subscription information.

[0205] In operation 518, the SMF2 500 can transmit a PDU session creation response message to the AMF 102. The PDU session creation response message can include the SM context ID of the second PDU session.

[0206] The AMF 102 can store the received SM context ID. The AMF 102 can use the second SM context ID in order to indicate the SM context of the second PDU session, referred to as a second PDU session ID.

[0207] In operation 520, the SMF2 500 can establish an SM policy association for the second PDU session with the PCF 103. The PCF 103 with which the SMF2 200 establishes the SM policy association can be the same as or different from the PCF 103 with which the SMF1 200 has already established the policy association in the first PDU session establishment procedure. The policy association request message transmitted by the SMF2 500 to the PCF 103 can include at least one of an S-NSSAI for the second PDU session establishment, a subscribed slice-AMBR, a service network slice-AMBR, a subscribed session-AMBR, a SUPI, and an HPLMN ID. At this time, the subscribed slice-AMBR can be a subscribed slice-AMBR for an S-NSSAI of the second PDU session. Also, the service network slice-AMBR can be a service network slice-AMBR for a service network of the second PDU session.

[0208] In operation 522, the PCF 103 can determine an authorized slice-AMBR of the received subscribed slice-AMBR or service network slice-AMBR based on at least one of UE subscription information and a local policy. Also, when determining the authorized slice-AMBR, the PCF 103 can consider a roaming agreement with an HPLMN of the UE. The subscribed slice-AMBR or the service network slice-AMBR can be the same as or different from the authorized slice-AMBR determined by the PCF 103. Also, the PCF 103 can determine an authorized session-AMBR. The authorized session-AMBR can be a value equal to or smaller than the authorized slice-AMBR. The PCF 103 can transmit a policy association response message to the SMF2 500 and establish the policy association. The policy association response message can include at least one of the authorized slice-AMBR and the authorized session-AMBR.

[0209] The SMF2 500 can determine a slice-AMBR to be used for the first PDU session and the second PDU session. The SMF2 500 can determine the slice-AMBR based on at least one of the slice-AMBR and the session-AMBR that the first PDU session is using received from the UDM 104 in operation 516 and the slice-AMBR and the session-AMBR of the second PDU session received in operation 516 to operation 522. For example, the SMF2 500 can determine to use the slice-AMBR that the first PDU session is currently using received from the UDM 102 in operation 516 for the second PDU session. Alternatively, the SMF2 500 can newly determine the slice-AMBR during the second PDU session establishment procedure. The SMF2 500 can determine the slice-AMBR in a similar manner as described in embodiments 2 to 3. For example, the slice-AMBR for the first PDU session and the second PDU session can be configured as a sum of the AMBR of the first PDU session and the AMBR of the second PDU session. At this time, when the sum of the AMBR of the first PDU session and the AMBR of the second PDU session is greater than the value of the subscribed slice-AMBR, the service network slice-AMBR, or the authorized slice-AMBR, the SMF1 200 can determine to use one of the subscribed slice-AMBR or the slice-AMBR modified by the AMF 120 or the SMF1 200 based on the subscribed slice-AMBR, the service network slice-AMBR, and the authorized slice-AMBR as the slice-AMBR for the first PDU session and the second PDU session. The SMF2 500 can add the slice-AMBR to the SM context of the second PDU session of the UE 100. The SMF2 500 can add the session-AMBR of the second PDU session to the SM context of the second PDU session of the UE 100.

[0210] Operations 524 to 526 follow the method described in embodiment 4.

[0211] In operation 528, the SMF2 500 can transmit a Namf_Communication_N1N2MessageTransfer message in order to notify the AMF 102 of the second PDU session establishment. The Namf_Communication_N1N2MessageTransfer message can include at least one of the information that the SMF2 500 transmits to the AMF 102, the N2 message that the SMF2 500 transmits to the RAN 101, and the N1 message that the SMF2 500 transmits to the UE 100.

[0212] The information sent by the SMF2 500 to the AMF 102 can include at least one of a PDU session ID, an SM context ID, a slice-AMBR, and a session-AMBR.

[0213] The N2 message sent by the SMF2 500 to the RAN 101 through the AMF 102 can include at least one of a PDU session ID, a session-AMBR, an S-NSSAI, and a slice-AMBR.

[0214] The N1 message sent by the SMF2 500 to the UE 100 through the AMF 102 and the RAN 101 can include a PDU session establishment accept message including at least one of an S-NSSAI, a session-AMBR, and a slice-AMBR.

[0215] In operation 530, the AMF 102 can send a Namf_Communication_N1N2MessageTransfer response message to the SMF2 500 in response to receiving the message of the second PDU session.

[0216] Operations 532 to 534 follow the method described in Embodiment 4.

[0217] In operation 536, the SMF2 500 that successfully performs the second PDU session establishment procedure can register itself as a serving SMF of the second PDU session in the UDM 104. The SMF2 500 according to various embodiments of the disclosure can insert the latest slice-AMBR using the S-NSSAI into the registration message. The UDM 104 according to various embodiments of the disclosure can store the SMF instance ID of the SMF2 500 and store the latest slice-AMBR currently used for the S-NSSAI.

[0218] According to various embodiments of the disclosure, the slice-AMBR determined during the second PDU session establishment procedure can be different from the slice-AMBR determined during the first PDU session establishment procedure. In order to control uplink and / or downlink data traffic of the first PDU session, the UE 100 and the RAN 101 can use the slice-AMBR received during the second PDU session establishment procedure. Since the UPF1 202 does not participate in the second PDU session, the slice-AMBR information of the UPF1 202 can need to be updated. Accordingly, the UDM 104 can update the slice-AMBR of the first PDU session used by the UE 100, the RAN 101, and the UPF1 202.

[0219] For example, the UDM 104 can compare the slice-AMBR of the S-NSSAI received in operation 536 with the slice-AMBR of the S-NSSAI stored in the UDM 104. When the slice-AMBR of the S-NSSAI received in operation 536 is different from the slice-AMBR of the S-NSSAI stored in the UDM 104, the UDM 104 can determine to change the slice-AMBR of the first PDU session to the latest slice-AMBR value, i.e., the slice-AMBR received in operation 536. Accordingly, in operation 548c, the UDM 104 can transmit the latest slice-AMBR value to the SMF 1 200 which is the serving SMF of the first PDU session.

[0220] As described above in operation 550 FIG. 5A As illustrated in operation 350 of FIG. 5, the SMF 1 200 which receives the latest slice-AMBR can determine to update the slice-AMBR of the first PDU session. In operation 550, the SMF 1 200 can perform operations 350 to 360 described in FIG. 5B and FIG. 5A In operation 550, the UE 100, the RAN 101, and the UPF 1 202 can control uplink and / or downlink data traffic by using the slice-AMBR which is updated for the first PDU session.

[0221]

Embodiment 6

[0222] After the PDU session for the S-NSSAI is established through the procedure illustrated in FIG. 5B After the PDU session for the S-NSSAI is established through the procedure illustrated in

[0223] Embodiment 6 describes a method for selecting the same PDU as that used in the first PDU session when selecting a PDU for the second PDU session, managing the slice-AMBR of the S-NSSAI of the first and second PDU sessions by the PDU, and controlling the sum of uplink and downlink data traffic. According to the method described in Embodiment 6, the SMF and / or UPF used for the first PDU session may be different from the SMF and / or UPF used for the second PDU session.

[0224] Use the above FIG. 2 and FIG. 3A Example 6 is used to describe the PDU session establishment process.

[0225] refer to FIG. 3A and FIG. 3B In operation 511, the UE 100 may FIG. 6 The first PDU session for S-NSSAI is established, and uplink data and / or downlink data traffic is exchanged with DN1 203. Therefore, in operation 511, UE 100, RAN 101, and UPF1 202 may store the slice-AMBR of S-NSSAI and control the data rate of uplink data and / or downlink data traffic.

[0226] like FIG. 6 As shown, the Namf_Communication_N1N2MessageTransfer message sent by SMF1 200 to AMF 102 during the first PDU session establishment procedure in operation 328 may include PCF information having a policy association with SMF1 200 of the first PDU session, that is, the ID of PCF 103. In operation 511, AMF 102 may store information about the ID of PCF 103 as UE context.

[0227] The UE 100 according to an embodiment of the present disclosure may determine to establish another PDU session for S-NSSAI, ie, a second PDU session associated with the first PDU session, based on at least one of a UE policy and local configuration information of the UE.

[0228] In operation 510, the UE 100 may send a PDU session establishment request message to establish a second PDU session. The PDU session establishment request message may include at least one of a PDU session ID, an S-NSSAI to be used by the UE 100, and a DNN. In this case, the S-NSSAI included in the PDU session establishment request may be the same as the S-NSSAI of the first PDU session. In addition, the DNN included in the PDU session establishment request may be the same as or different from the DNN of the first PDU session.

[0229] In operation 512, the AMF 102 can select an SMF capable of managing the PDU session requested by the UE 100. For example, the AMF 102 can select an SMF supporting the S-NSSAI and / or the DNN requested by the UE 100. According to various embodiments of the disclosure, the SMF selected by the AMF 102 can be different from the serving SMF1 200 of the first PDU session.

[0230] In operation 514, the AMF 102 can transmit a PDU session creation request message to the selected SMF 500. The PDU session creation request message can include at least one of the PDU session ID, the S-NSSAI, and the DNN. According to an embodiment of the disclosure, the AMF 102 can identify that there is a PDU session, i.e., the first UE session associated with the S-NSSAI requested by the UE 100, based on the UE context stored in the AMF 102. The PDU session creation request message can include the PCF ID information of the first PDU session stored by the AMF 102.

[0231] The SMF2 500 can generate an SM context of the second PDU session. In operation 514, the SM context is a set of information for managing the requested PDU session. The SM context can be referred to as an SM context ID.

[0232] In operation 516, the SMF2 500 can request the subscription information of the UE 100 from the UDM 104, and acquire the UE subscription information from the UDM 104 in response thereto. The UE subscription information acquired from the UDM 104 can include at least one of the subscribed S-NSSAI, the subscribed slice-AMBR of the subscribed S-NSSAI, the subscribed session-AMBR of the subscribed S-NSSAI, and the DNN.

[0233] The SMF2 500 can authenticate the UE request received in operation 514 based on the UE subscription information. For example, the SMF2 500 can identify whether the S-NSSAI and / or the DNN requested by the UE included in the PDU session creation request message is included in the UE subscription information.

[0234] In operation 518, the SMF 500 can transmit a PDU session creation response message to the AMF 102. The PDU session creation response message can include the SM context ID of the second PDU session.

[0235] The AMF 102 can store the received SM context ID. The AMF 102 can use the second SM context ID in order to indicate the SM context of the second PDU session referred to as a second PDU session ID.

[0236] In operation 520, the SMF2 500 can establish a policy association for a second PDU session SM with the PCF. The SMF2 500 can select the same PCF 103 as the first PDU session by using the PCF ID information of the first PDU session received in operation 514, as a PCF for establishing a policy association for a second PDU session SM. The policy association request message transmitted by the SMF2 500 to the PCF 103 can include at least one of an S-NSSAI for second PDU session establishment, a subscribed slice-AMBR, a service network slice-AMBR, a subscribed session-AMBR, a SUPI, and an HPLMN ID. At this time, the subscribed slice-AMBR can be a subscribed slice-AMBR for the second PDU session. In addition, the service network slice-AMBR can be a service network slice-AMBR used by a service network for the second PDU session.

[0237] In operation 522, the PCF 103 can determine an authorized slice-AMBR of the received subscribed slice-AMBR or service network slice-AMBR based on at least one of UE subscription information and a local policy. The PCF 103 according to various embodiments of the disclosure can consider not only the information received in operation 520, but also a slice-AMBR currently used for the first PDU session in order to determine the authorized slice-AMBR. In addition, the PCF 103 can consider a roaming agreement with the HPLMN of the UE when determining the authorized slice-AMBR. The subscribed slice-AMBR or the service network slice-AMBR can be the same as or different from the authorized slice-AMBR determined by the PCF 103. In addition, the PCF 103 can determine an authorized session-AMBR. The authorized session-AMBR can be a value equal to or less than the authorized slice-AMBR. The PCF 103 can transmit a policy association response message to the SMF2 500 and establish a policy association. The policy association response message can include at least one of the authorized slice-AMBR and the authorized session-AMBR. The authorized slice-AMBR or the authorized session-AMBR newly determined by the PCF 103 can be the same as or different from the slice-AMBR or the session-AMBR currently used for the first PDU session.

[0238] The SMF2 500 can determine a slice-AMBR to be used for the second PDU session. The SMF 500 can determine the slice-AMBR based on at least one of the slice-AMBR and the session-AMBR of the second PDU session received in operations 516 to 522. For example, the SMF2 500 can determine to use the slice-AMBR received from the PCF 103 in operation 522 for the second PDU session. The SMF2 500 can add the slice-AMBR to the SM context of the second PDU session of the UE 100. The SMF2 500 can add the session-AMBR of the second PDU session to the SM context of the second PDU session of the UE 100.

[0239] Operations 524 to 534 follow the method described in Embodiment 5.

[0240] Operation 536 follows the method described in Embodiment 4.

[0241] According to various embodiments of the disclosure, the slice-AMBR determined during the second PDU session establishment procedure can be different from the slice-AMBR determined during the first PDU session establishment procedure. To control the uplink and / or downlink data traffic of the first PDU session, the UE 100 and the RAN 101 can use the slice-AMBR received during the second PDU session establishment procedure. Since the UPF1 202 does not participate in the second PDU session, the slice-AMBR information of the UPF1 202 can need to be updated. Accordingly, the PCF 103 can perform a slice-AMBR update procedure for the first PDU session used by the UE 100, the RAN 101, and the UPF1 202.

[0242] For example, in operation 548d, the PCF 103 can transmit the latest slice-AMBR value determined in operations 520 to 522 to the SMF1 200 which is a serving SMF of the first PDU session.

[0243] As shown in operation 350 of FIG. 3 described above in operation 550, the SMF1 200 which receives the latest slice-AMBR can determine to update the slice-AMBR of the first PDU session. In operation 550, the SMF1 200 can perform operations 350 to 360 described in Embodiments 4 and 5. FIG. 6 and FIG. 6 In operation 550, the UE 100, the RAN 101, and the UPF1 202 can control the uplink and / or downlink data traffic by using the slice-AMBR updated for the first PDU session.

[0244] [Example 7]

[0245] According to various embodiments of the present disclosure, the UE can establish a PDU session and exchange data with the DN in the connected state. The UE can change the state to the idle state, and the 5G system can release the radio resources between the UE and the RAN while keeping the PDU session in the deactivated state.

[0246] Example 7 describes a method for configuring slice-AMBR related to a PDU session in the UE, RAN, and 5G NF during the process of changing the PDU session to an active state.

[0247] FIG. 6 The service request process according to an embodiment of the present disclosure is shown.

[0248] In reference FIG. 7 Before the description, the UE 100 and the network entities are described. The UE 100 is located in a specific RAN 101 and can configure a radio channel and communicate with the RAN 101. As described above, the RAN 101 can be a base station of a 5G network, a base station of LTE or LTE-A, or a network entity used as a base station in other wireless communication networks. In the following, for ease of description, it is assumed that the RAN 101 is a 5G base station and the mobile communication system is a 5G wireless communication network. In addition, it is assumed that in addition to the RAN 101, the 5G core network also includes an AMF 102, a PCF 103, an SMF1 200, and an SMF2 500. In the following description FIG. 7 , the portion marked by the dotted line may be a process that can be omitted.

[0249] refer to FIG. 7 , downlink data traffic can be generated from the DN. At this time, when the corresponding PDU session is in the deactivated state, in operation 610, the network can send a paging message or a NAS notification message to the UE 100. In operation 612, the UE 100 that receives the paging message and / or the NAS notification message can send a service request message. Alternatively, in order to send uplink data traffic, in operation 612, the UE 100 in the idle state can send a service request message. The service request message may include at least one of a list of PDU sessions to be activated and a list of allowed PDU sessions. The list of PDU sessions to be activated and / or the list of allowed PDU sessions may include one or more PDU session information through which the UE and / or DN transmits data.

[0250] In operation 614, the RAN 101 can transmit the received service request message to the AMF 102. The AMF 102 can select PDU sessions to be switched to the activated state based on the received list of PDU sessions to be activated and / or the list of allowed PDU sessions. For example, according to various embodiments of the disclosure, the AMF 102 can determine to switch the first PDU session and the second PDU session to the activated state. The AMF 102 can determine that the first PDU session and the second PDU session are associated with the same S-NSSAI.

[0251] In operations 620 and 630, the AMF 102 can transmit Nsmf_PDUSession_UpdateSMContext request messages to service SMFs of PDU sessions to be switched to the activated state. For example, according to embodiments of the disclosure, the AMF 102 can determine to switch the first PDU session and the second PDU session to the activated state, and transmit Nsmf_PDUSession_UpdateSMContext request messages to each of SMF1 200 which is a service SMF of the first PDU session and SMF2 500 which is a service SMF of the second PDU session. The Nsmf_PDUSession_UpdateSMContext request message transmitted to each service SMF can include slice-AMBR information of the S-NSSAI associated with the PDU session.

[0252] In operations 622 and 632, the SMF1 200 and the SMF2 500 can perform a policy association modification procedure with the PCF 103. The PCF 103 can provide the SMF1 200 and the SMF2 500 with slice-AMBR information of the S-NSSAI associated with the PDU session.

[0253] In operations 624 and 634, the SMF1 200 and the SMF2 500 can select a UPF for the first PDU session or / and the second PDU session, and perform an N4 session establishment or N4 session modification procedure. The SMF1 200 and / or the SMF2 500 can transmit slice-AMBR information of each PDU session to the corresponding UPF (not shown in the drawings). FIG. 10 The slice-AMBR information can be a slice-AMBR value acquired in operations 620 to 622 or / and operations 630 to 632, or a slice-AMBR value determined by the corresponding SMF.

[0254] In operation 626 and operation 636, the SMF1 200 and the SMF2 500 can transmit the Nsmf_PDUSession_UpdateSMContext response message to the AMF 102. The Nsmf_PDUSession_UpdateSMContext response message can include the slice-AMBR information for each PDU session associated with the S-NSSAI.

[0255] As described above, when both the SMFs 200 and 500 or only one of them exists and receives the Nsmf_PDUSession_UpdateSMContext response message from the corresponding SMF among the different SMFs 200 and 500, in operation 640, the AMF 102 can transmit the N2 message to the RAN 101. The N2 message can include information related to the PDU sessions activated by the service request procedure. For example, the S-NSSAI information associated with the activated PDU sessions can be included. In addition, the slice-AMBR information associated with each of the S-NSSAI can be included. For example, when the first PDU session and the second PDU session are activated by the service request procedure, the slice-AMBR can be configured as the sum of the first PDU session and the second PDU session. Alternatively, the session-AMBR information associated with each PDU session can be included.

[0256] The RAN 101 can store the information received from the AMF 102 and use it thereafter to control uplink and downlink data traffic. For example, the RAN 101 can store the received S-NSSAI and the slice-AMBR associated with the S-NSSAI. According to another embodiment of the disclosure, the RAN 101 can calculate and store the slice-AMBR for the S-NSSAI based on the received session-AMBR.

[0257] In operation 642, the RAN 101 can perform the RRC connection reconfiguration procedure with the UE 100. At this time, in operation 640, the RAN 101 can transmit the service accept message received from the AMF 102 to the UE 100. The service accept message can include information related to the PDU sessions activated by the service request procedure. For example, the S-NSSAI information associated with the activated PDU sessions can be included. In addition, the slice-AMBR information associated with each S-NSSAI can be included. For example, when the first PDU session and the second PDU session are activated by the service request procedure, the slice-AMBR can be configured as the sum of the first PDU session and the second PDU session. Alternatively, the session-AMBR information associated with each PDU session can be included.

[0258] The UE 100 can store the information received from the RAN 101 and thereafter use it to control uplink and downlink data traffic. For example, the UE 100 can store the received S-NSSAI and the slice-AMBR associated with the S-NSSAI. Alternatively, the UE 100 can calculate and store the slice-AMBR of the S-NSSAI based on the received session-AMBR.

[0259] FIG. 2 A UE configuration update procedure according to an embodiment of the disclosure is illustrated.

[0260] Before describing the UE 100 and the network entities, a description is made. FIG. 10 The UE 100 is located within a specific RAN 101 and can be configured with a radio channel and communication with the RAN 101. As described above, the RAN 101 can be a base station of a 5G network, a base station of LTE or LTE-A, or a network entity serving as a base station in other wireless communication networks. Hereinafter, for convenience of description, it is assumed that the RAN 101 is a 5G base station and the mobile communication system is a 5G wireless communication network. Further, it is assumed that, in addition to the RAN 101, a 5G core network includes an AMF 102, a PCF 103, an SMF1 200, and a UDM 104.

[0261] Referring to FIG. 1 In operation 710, the 5G core network can change the slice-AMBR associated with the S-NSSAI. For example, the UDM 104 can change the slice-AMBR due to a change in UE subscription information. Alternatively, for example, the PCF 103 can change the slice-AMBR due to a change in policy information. Alternatively, for example, the SMF1 300 or the AMF 102 can change the slice-AMBR due to a change in PDU session status.

[0262] In operation 720, the AMF 102 can transmit the changed information to the UE 100. For example, the AMF 102 can transmit the S-NSSAI and the slice-AMBR information associated with the S-NSSAI.

[0263] The UE 100 can store the received information and thereafter use the information to control uplink data traffic of the PDU session associated with the S-NSSAI.

[0264] In operation 722, the AMF 102 can transmit the changed information to the RAN 101. For example, the AMF 102 can transmit the UE ID, the S-NSSAI, and the slice-AMBR information associated with the S-NSSAI.

[0265] The RAN 101 can store the received information and thereafter use it to control uplink or downlink data traffic of the PDU session associated with the S-NSSAI.

[0266] [EMBODIMENT 8]

[0267] FIG. 2 A PDU session establishment procedure according to various embodiments of the disclosure is illustrated.

[0268] In operation 1001, the UE 100 can transmit a PDU session establishment request message to the AMF 102. The PDU session establishment request message can include an S-NSSAI as network slice information which the UE 100 desires to use.

[0269] In operation 1002, the AMF 102 can select an SMF supporting the S-NSSAI received in operation 1011. The AMF 102 can determine whether all PDU sessions for the S-NSSAI should be supported for the same SMF or SMFs belonging to the same SMF set (SMFs within the same SMF set) based on at least one of a local policy of the AMF 102, a slice policy acquired from the PCF 103, and UE subscription data acquired from the UDM 104. When all sessions for the S-NSSAI should be supported for the same SMF or SMFs belonging to the same SMF set, the AMF 102 can select the same SMF or SMFs belonging to the same SMF set for the S-NSSAI. For example, when the AMF 102 has not selected an SMF for the S-NSSAI, a new SMF can be selected. According to another embodiment, when the AMF 102 has previously selected an SMF for the S-NSSAI or has a history of selecting an SMF and stores previously selected SMF information (e.g., SMF ID, SMF instance ID, or SMF set ID), the AMF 102 can perform the following procedure with the SMF corresponding to the previously selected and stored information (e.g., the same SMF as the previously selected SMF (the same SMF) or another SMF belonging to the same SMF set to which the previously selected SMF belongs (an SMF within the same SMF set)). According to another embodiment, the AMF 102 can receive SMF information (e.g., SMF ID, SMF instance ID, or SMF set ID) supporting the S-NSSAI acquired from the NRF (not shown), the PCF 103, or the UDM 104 (e.g., SMF information included in SMF selection subscription data), and perform the following procedure with the SMF corresponding to the received information (e.g., an SMF indicated by the SMF ID or the SMF instance ID or an SMF belonging to the SMF set indicated by the SMF set ID).

[0270] SMFs belonging to the same SMF set according to an embodiment of the disclosure can share PDU session-related information (e.g., SM context) managed by each SMF.

[0271] In operation 1003, the AMF 102 can transmit a PDU session creation request message to the SMF1 200 selected in operation 1002. The PDU session creation request message can include S-NSSAI information.

[0272] In operation 1004, the SMF1 200 can receive UE subscription information (e.g., UE subscription data and session management subscription data) from the UDM 104. The UE subscription information can include a subscribed slice-AMBR per S-NSSAI. When the UE 100 previously established a PDU session for the same S-NSSAI and is currently using the session, and when the SMF1 200 stores or can acquire PDU session information that the UE 100 established and is currently using from another SMF, the SMF1 200 can omit operation 1004. The subscribed slice-AMBR can be a value obtained by adding a guaranteed bit rate (GBR or GBR QoS flow) and a non-guaranteed bit rate (non-GBR or non-GBR QoS flow). Alternatively, the subscribed slice-AMBR can be a value including only non-GBR (or non-GBR QoS flow).

[0273] In operation 1005, the SMF1 200 can establish a policy association with the PCF 103. The SMF1 200 can transmit at least one of the subscribed slice-AMBR and the subscribed session-AMBR of the UE 100 to the PCF 103. The PCF 103 can determine an authorized slice-AMBR based on at least one of the information received from the SMF1 200, a local policy of a mobile communication service provider, UE subscription information, and a roaming agreement.

[0274] For example, the PCF 103 can determine the authorized slice-AMBR for non-GBR QoS flows, taking into account a data bit rate being used by a guaranteed bit rate (GBR) QoS flow associated with the S-NSSAI that the UE 100 is using. When the UE 100 is using / requesting one or more PDU sessions for the S-NSSAI, the PCF 103 can determine the authorized slice-AMBR taking into account the GBR QoS flows included in all PDU sessions.

[0275] As described in the method, the PCF 103 can transmit the determined authorized slice-AMBR to the SMF1 200.

[0276] If the UE 100 previously established a PDU session for the same S-NSSAI and is using the session, and the SMF1 200 can store or acquire PDU session information that the UE 100 established and is using, the SMF1 200 can omit operation 1005.

[0277] In operation 1006, the SMF1 200 can determine the slice-AMBR for the S-NSSAI based on the information received from the AMF 102 in operation 1003, the information received from the UDM 104 in operation 1004, and the information received from the PCF 103 in operation 1005.

[0278] For example, the SMF1 200 can configure the slice-AMBR for the non-GBR QoS flow to be the sum of the session-AMBR values of all PDU sessions with an active user plane associated with the S-NSSAI. In addition, the SMF1 200 can configure the slice-AMBR value not to exceed the subscribed slice-AMBR. That is, for example, when the sum of the session-AMBR values of all PDU sessions with an active user plane associated with the S-NSSAI is greater than the subscribed slice-AMBR or the granted slice-AMBR, the SMF can configure the slice-AMBR for the non-GBR QoS flow to be the subscribed slice-AMBR or the granted slice-AMBR.

[0279] For example, the SMF1 200 can determine the slice-AMBR for the non-GBR QoS flow, taking into account the GBR QoS flow included in the PDU session associated with the S-NSSAI. If the subscribed slice-AMBR received from the UDM 104 is 100 megabits per second (Mbps) and the GBR QoS flow uses 60 Mbps, the SMF can configure the slice-AMBR for the non-GBR QoS flow to be the value of all subscribed slice-AMBR except for the GBR QoS flow, i.e., 40 Mbps.

[0280] In another example, the SMF1 200 can determine the slice-AMBR for the non-GBR QoS flow, taking into account the GBR QoS flows of all PDU sessions used / requested by the UE associated with the S-NSSAI. If the subscribed slice-AMBR received from the UDM 104 is 100 megabits per second (Mbps), the GBR QoS flow of a first PDU session using the S-NSSAI uses 40 Mbps, and the GBR QoS flow of a second PDU session using the same S-NSSAI uses 35 Mbps, the SMF can configure the slice-AMBR for the non-GBR QoS flow to be the value of all subscribed slice-AMBR except for the GBR QoS flows of all PDU sessions, i.e., for example, 25 Mbps.

[0281] In another example, the UE 100 can make a request / establish a PDU session for an S-NSSAI by accessing the AMF 102 via a 3GPP access network (AN) (e.g., NR or E-UTRA), and can make a request / establish a PDU session for the S-NSSAI by accessing the AMF 102 via a non-3GPP access network (e.g., Wi-Fi). That is, the UE 100 can use a PDU session for an S-NSSAI through a 3GPP access network, and use a PDU session for the same S-NSSAI through a non-3GPP access network. In operation 1003, the AMF 102 can insert the UE's access network information into a message transmitted to the SMF1 200. The SMF1 200 can know the access network of the requested PDU session based on the information received in operation 1003. The SMF1 200 can split the slice-AMBR into a value that can be used in a 3GPP access network and a value that can be used in a non-3GPP access network. For example, when the slice-AMBR is 40 Mbps, the SMF can configure the slice-AMBR that can be used in the 3GPP access network to 30 Mbps, and configure the slice-MABR that can be used in the non-3GPP access network to a value other than the value that can be used in the 3GPP access network, i.e., 10 Mbps, of all the slice-AMBR.

[0282] In operation 1007, the SMF1 200 can transmit the slice-AMBR determined in operation 1006 to the AMF. At this time, the slice-AMBR transmitted by the SMF1 200 can vary depending on the type of the access network (e.g., 3GPP access network or non-3GPP access network). Alternatively, the slice-AMBR transmitted by the SMF1 200 can be the same value regardless of the type of the access network.

[0283] In operation 1008, the AMF 102 can transmit the slice-AMBR received from the SMF1 200 in operation 1007 to the RAN 101.

[0284] In operation 1009, the RAN 101 can apply the received slice-AMBR (slice-AMBR enforcement). For example, the RAN 101 can control the sum of the maximum uplink data rates (maximum uplink data throughput) of one or more non-GBR QoS flows associated with the S-NSSAI to be at most the slice-AMBR. In addition, the RAN 101 can control the sum of the maximum downlink data rates (maximum downlink data throughput) of one or more non-GBR QoS flows associated with the S-NSSAI to be at most the slice-AMBR.

[0285] In operation 1010, the RAN 101 can transmit the PDU session establishment accept message received from the AMF 102 in operation 1008 to the UE 100.

[0286] When the slice-AMBR is included in the PDU session establishment accept message, the UE can control the sum of the maximum uplink data rates of the non-GBR QoS flows of all PDU sessions associated with the PDU session to be at most the slice-AMBR.

[0287] [Embodiment 9]

[0288] The AMF 102 according to an embodiment of the disclosure can identify, in operation 212 of FIG. 2, operation 312 of FIG. 3, operation 512 of FIG. 5, or operation 1002 of FIG. 10, whether the SMF selection subscription data received in operation 116 of FIG. 1 is indicative of selecting the same SMF for multiple PDU sessions. FIG. 10 FIG. 1 The AMF 102 according to an embodiment of the disclosure can identify, in operation 212 of FIG. 2, operation 312 of FIG. 3, operation 512 of FIG. 5, or operation 1002 of FIG. 10, whether the SMF selection subscription data received in operation 116 of FIG. 1 is indicative of selecting the same SMF for multiple PDU sessions.

[0289] In the method in which the AMF 102 selects the SMF, the AMF 102 can determine the SMF selection method based on subscription data received from the UDM 104 in operation 116 of FIG. 1. The subscription data can include SMF selection subscription information (selection subscription data). The SMF selection subscription data can include information (e.g., an indication) indicating whether the same SMF should be selected for multiple PDU sessions associated with the same S-NSSAI. FIG. 2 The AMF 102 according to an embodiment of the disclosure can identify, in operation 212 of FIG. 2, operation 312 of FIG. 3, operation 512 of FIG. 5, or operation 1002 of FIG. 10, whether the SMF selection subscription data received in operation 116 of FIG. 1 is indicative of selecting the same SMF for multiple PDU sessions.

[0290] FIG. 10 The AMF 102 according to an embodiment of the disclosure can identify, in operation 212 of FIG. 2, operation 312 of FIG. 3, operation 512 of FIG. 5, or operation 1002 of FIG. 10, whether the SMF selection subscription data received in operation 116 of FIG. 1 is indicative of selecting the same SMF for multiple PDU sessions. FIG. 2 FIG. 10 The AMF 102 according to an embodiment of the disclosure can identify, in operation 212 of FIG. 2, operation 312 of FIG. 3, operation 512 of FIG. 5, or operation 1002 of FIG. 10, whether the SMF selection subscription data received in operation 116 of FIG. 1 is indicative of selecting the same SMF for multiple PDU sessions.

[0291] The AMF 102 according to an embodiment of the disclosure can identify, in operation 212 of FIG. 2, operation 312 of FIG. 3, operation 512 of FIG. 5, or operation 1002 of FIG. 10, whether the SMF selection subscription data received in operation 116 of FIG. 1 is indicative of selecting the same SMF for multiple PDU sessions. FIG. 2 FIG. 2 The AMF 102 according to an embodiment of the disclosure can identify, in operation 212 of FIG. 2, operation 312 of FIG. 3, operation 512 of FIG. 5, or operation 1002 of FIG. 10, whether the SMF selection subscription data received in operation 116 of FIG. 1 is indicative of selecting the same SMF for multiple PDU sessions.

[0292] ​​​​If there is an SMF that has been selected for S-NSSAI and stored in AMF 102, AMF 102 can select the stored SMF. Through the above method, AMF 102 can use the same SMF for multiple PDU sessions (or additional PDU sessions) of S-NSSAI.

[0293] If there is no SMF previously selected for S-NSSAI, AMF 102 may reselect an SMF. AMF 102 may store the newly selected SMF information.

[0294] According to an embodiment of the present disclosure, when the SMF selection subscription data does not indicate selection of the same SMF for multiple PDU sessions, the AMF 102 may FIG. 3A Operation 212 of FIG. 3 , operation 312 of FIG. 5 , FIG. 2 In operation 1002, the AMF 102 newly selects an SMF. The AMF 102 may store information of the newly selected SMF.

[0295] The slice-AMBR according to an embodiment of the present disclosure may refer to a total data transmission rate (aggregate bit rate) provided in GBR QoS flows and non-GBR QoS flows of all PDU sessions associated with an S-NSSAI, or may be used to define a limit on the aggregate bit rate.

[0296] According to an embodiment of the present disclosure, the network or NF (e.g., SMF, PCF, UDM, AMF, NSSF, NWDAF, and RAN) may allow the remaining portion of the slice-AMBR excluding the aggregate bit rate of the GBR QoS flow to a non-GBR QoS flow. For example, the aggregate bit rate of the non-GBR QoS flow may be the sum of the session-AMBRs of all PDU sessions associated with the S-NSSAI. In addition, when the sum of the session-AMBRs is greater than the remaining portion of the slice-AMBR excluding the aggregate bit rate of the GBR QoS flow, the network or NF (e.g., SMF, PCF, UDM, AMF, NSSF, NWDAF, and RAN) according to an embodiment of the present disclosure may limit the aggregate bit rate of the non-GBR QoS flow to the remaining portion of the slice-AMBR excluding the aggregate bit rate of the GBR QoS flow. The aggregate bit rate of the GBR QoS flow may be the sum of the MFBRs of the GBR QoS flows of all PDU sessions associated with the S-NSSAI. In another example, the aggregate bit rate of the GBR QoS flow may be the sum of the GFBRs of the GBR QoS flows of all PDU sessions associated with the S-NSSAI.

[0297] The network or NF (e.g., SMF, PCF, UDM, AMF, NSSF, NWDAF, and RAN) according to embodiments of the disclosure can control the session-AMBR of each PDU session based on the status information (e.g., activated, not activated, deactivated, or released) of the PDU session associated with the S-NSSAI. For example, when the UE is using a first PDU session and a second PDU session associated with the same S-NSSAI, the network or NF can limit the sum of the session-AMBR of the first PDU session and the session-AMBR of the second PDU session to the remaining part of the slice-AMBR except for the aggregate bit rate of the GBR QoS flow. Thereafter, when the status of the second PDU session changes and the changed status information indicates that the second PDU session is not currently used (e.g., the status of the first PDU session changes from the activated state to the deactivated state), the network or NF can identify (determine) that the data rate used as the session-AMBR of the second PDU session is not currently used. Accordingly, the network or NF can change the data rate used as the session-AMBR of the second DPU session to the session-AMBR used as the PDU session (e.g., the first PDU session) currently in the activated state. The network or NF can transmit the changed session-AMBR to other NFs (e.g., SMF, PCF, UDM, AMF, NSSF, and NWDAF) and / or the RAN. The other NF or the RAN receiving the changed session-AMBR can control the data rate of the corresponding PDU session according to the newly received session-AMBR (i.e., the changed session-AMBR).

[0298] Reference FIG. 1 , the UE 100 can establish a first PDU session with a first DN1 203 according to the procedure shown in FIG. 2A. For example, the first PDU session can be a PDU session established for an S-NSSAI and a first data network name (DNN). FIG. 1

[0299] In operation 216, the SMF1 200 can acquire slice-AMBR information of the first PDU session from the UDM 104. For example, the slice-AMBR can be the slice-AMBR information of the S-NSSAI. In addition, the SMF1 200 can acquire first session-AMBR information of the first PDU session from the UDM 104. For example, the first session-AMBR can be the session-AMBR information of the S-NSSAI and the first DNN.

[0300] Reference FIG. 2 ​, the UE 100 can establish a second PDU session with the second DN 300 according to the procedure illustrated in FIG. 3. For example, the second PDU session can be a PDU session established with the S-NSSAI and the second DNN.

[0301] In operation 312, the AMF 102 can determine to select the same SMF1 200 as the service SMF for the second PDU session as the SMF1 200 selected for the first PDU session in operation 212 of FIG. 2. FIG. 3B For example, the AMF 102 can make such a decision based on the information received from the UDM 104 in operation 116 of FIG. 1. FIG. 2 to FIG. 3A For example, the UDM 104 sends the subscription information to the AMF 102 in operation 116 of FIG. 1. The subscription information can include information (e.g., an indication) indicating to select the same NF (e.g., SMF and PCF) for the S-NSSAI. The AMF 102 can select the SMF 200 by using the service SMF information of the first PDU session stored in the AMF 102. FIG. 3B

[0302] In operation 316, the SMF1 200 can acquire slice-AMBR information for the second PDU session from the UDM 104. For example, the slice-AMBR can be slice-AMBR information for the S-NSSAI. In another example, the SMF1 200 can use the slice-AMBR information acquired for the S-NSSAI in operation 216. Further, the SMF1 200 can acquire second session-AMBR information for the second PDU session from the UDM 104. For example, the second session-AMBR can be session-AMBR information for the S-NSSAI and the second DNN.

[0303] According to an embodiment of the disclosure, one same SMF can be selected for all PDU sessions supporting the same S-NSSAI, and the SMF can manage the slice-AMBR, the first session-AMBR, and the second session-AMBR.

[0304] ​The SMF 200 according to an embodiment of the disclosure can determine the first session-AMBR and the second session-AMBR in consideration of the slice-AMBR, the GBR QoS flow of the first PDU session, the first session-AMBR of the first PDU session, the GBR QoS flow of the second PDU session, and the second session-AMBR of the second PDU session. For example, the SMF 1 200 can determine to use a remaining value among the slice-AMBR except for a data rate of the GBR QoS flow of the first PDU session and a data rate of the GBR QoS flow of the second PDU session for the first session-AMBR and the second session-AMBR. The first session-AMBR and the second session-AMBR determined by the SMF 1 200 can be the same as or different from each other. For example, the SMF 1 200 can determine the first session-AMBR and the second session-AMBR in consideration of a session-AMBR of a subscription of the first PDU session and a session-AMBR of a subscription of the second PDU session or a ratio therebetween, which are acquired from the UDM 104, when determining the first session-AMBR and the second session-AMBR.

[0305] The SMF 1 200 can transmit the first session-AMBR to the RAN 101 and the UPF 1 202 supporting the first PDU session through the procedure illustrated in FIG. 4A In addition, the SMF 1 200 can transmit the slice-AMBR of the first PDU session to the RAN 101 and the UPF 1 202 supporting the first PDU session.

[0306] The RAN 101 and the UPF 1 202 can control a data rate of the non-GBR QoS flow of the first PDU session based on at least one of the first session-AMBR and the slice-AMBR.

[0307] The SMF 1 200 can transmit the second session-AMBR to the RAN 101 and the UPF (the UPF 1 202 when the first PDU session and the second PDU session are supported by the same UPF, the UPF 2 400 when the first PDU session and the second PDU session are supported by different UPFs) supporting the second PDU session through the procedure illustrated in FIG. 3A In addition, the SMF 1 200 can transmit the slice-AMBR of the second PDU session to the RAN 101 and the UPF 202 or 400 supporting the second PDU session.

[0308] The RAN 101 and the UPF 202 or 400 can control a data rate of a non-GBR QoS flow of the second PDU session based on at least one of the second session-AMBR and the slice-AMBR.

[0309] Further, the SMF1 200 according to an embodiment of the disclosure can control / change the first session-AMBR and the second session-AMBR based on the first PDU session status information and the second PDU session status information. For example, when the status of the second PDU session is changed after the first PDU session and the second PDU session are established through the procedure illustrated in FIG. 10 and the changed status information indicates that the second PDU session is not currently used (e.g., the status of the first PDU session is changed from the active state to the deactivated state), the SMF1 200 can determine that the data rate used as the session-AMBR of the second PDU session is not currently used, and change the data rate used as the session-AMBR of the second PDU session to the session-AMBR used as the PDU session (e.g., the first PDU session) currently in the active state. FIG. 2

[0310] The SMF1 200 can transmit the changed first session-AMBR to the RAN 101 and the UPF1 202 supporting the first PDU session through the procedure illustrated in FIG. 11. Further, the SMF1 200 can transmit the slice-AMBR of the first PDU session to the RAN 101 and the UPF1 202 supporting the first PDU session. FIG. 5A

[0311] The RAN 101 and the UPF1 202 can control a data rate of a non-GBR QoS flow of the first PDU session based on at least one of the changed first session-AMBR and the slice-AMBR.

[0312] The SMF1 200 can transmit the changed second session-AMBR to the RAN 101 and the UPF (the UPF1 202 when the first PDU session and the second PDU session are supported by the same UPF, the UPF2 400 when the first PDU session and the second PDU session are supported by different UPFs) supporting the second PDU session through the procedure (PDU session modification procedure) illustrated in FIG. 12. Further, the SMF 200 can transmit the slice-AMBR of the second PDU session to the RAN 101 and the UPF 202 or 400 supporting the second PDU session. FIG. 2

[0313] ​​​The RAN 101 and the UPF 202 or 400 can control a data rate of a non-GBR QoS flow of the second PDU session based on at least one of the changed second session-AMBR and slice-AMBR.

[0314] According to embodiments of the disclosure, one same PCF 103 can be selected for all PDU sessions supporting the same S-NSSAI, and the PCF 103 can manage the slice-AMBR, the first session-AMBR, and the second session-AMBR.

[0315] To select the same PCF 103, the AMF 102 can select the same SMF1 200 by the method shown in FIG. 2

[0316] Alternatively, to select the same PCF 103, the AMF 102 can provide the PCF information to the SMF1 200. For example, after operations 218 to 220 of FIG. 3A , the SMF1 200 can send information about the selected PCF 103 to the AMF 102 for the first PDU session in operation 228. The AMF 102 can store the S-NSSAI information associated with the first PDU session and the information about the PCF 103. Thereafter, the second PDU session can be established according to the procedure shown in FIG. 5A The AMF 102 can identify (determine or decide) that the S-NSSAI of the second PDU session is the same as the S-NSSAI of the first PDU session that the UE 100 has established. Accordingly, the AMF 102 can provide the PCF information of the first PDU session to the serving SMF2 500 of the second PDU session in operation 514. The PCF information can be information about the PCF 103 associated with the first PDU session stored by the AMF 102 in the procedure of FIG. 2 The SMF 500 receiving the PCF information from the AMF 102 can select the same PCF 103 as the PCF for the first PDU session as the PCF for the second PDU session based on the PCF information received from the AMF 102, and send a message to the selected PCF 103 in operation 520.

[0317] The SMF 103 according to embodiments of the disclosure can determine the first session-AMBR and the second session-AMBR considering the slice-AMBR, the GBR QoS flow of the first PDU session, the first session-AMBR of the first PDU session, the GBR QoS flow of the second PDU session, and the second session-AMBR of the second PDU session.​FIG. 3A In operation 220, the SMF 1200 may send at least one of the first session-AMBR and the slice-AMBR of the first PDU session to the PCF 103. FIG. 5A Operation 320 or FIG. 2 In operation 520 , the SMF 200 or 500 may send at least one of a second session-AMBR and a slice-AMBR of the second PDU session to the PCF 103 .

[0318] Based on the information received from the SMF 200 or 500, the PCF 103 may determine to use the remaining values ​​of the session-AMBR, excluding the data rate of the GBR QoS flow of the first PDU session and the data rate of the GBG QoS flow of the second PDU session, for the first session-AMBR and the second session-AMBR. The first session-AMBR and the second session-AMBR determined by the PCF 103 may be the same as or different from each other. For example, when determining the first session-AMBR and the second session-AMBR, the PCF 103 may determine the first session-AMBR and the second session-AMBR, taking into account the subscribed session-AMBR of the first PDU session and the subscribed session-AMBR of the second PDU session obtained from the SMF 200 or 500 and / or the ratio therebetween.

[0319] exist FIG. 3B to FIG. 5A In operation 222, the PCF 103 may send at least one of the first session-AMBR and the slice-AMBR of the first PDU session determined by the PCF 103 to the SMF 200. FIG. 2 Operation 322 or FIG. 3A In operation 522 , the PCF 103 may send at least one of a second session-AMBR and a slice-AMBR of the second PDU session determined by the PCF 103 to the SMF 200 or 500 .

[0320] SMF1 200 can be FIG. 5A The process shown is used to send the first session-AMBR received from PCF 103 to RAN 101 and UPF1 202 supporting the first PDU session. In addition, SMF1 200 may send the slice-AMBR of the first PDU session to RAN 101 and UPF1 202 supporting the first PDU session.

[0321] The RAN 101 and the UPF1 202 can control the data rate of the non-GBR QoS flow of the first PDU session based on at least one of the first session-AMBR and the slice-AMBR.

[0322] The SMF 200 or 500 can transmit the second session-AMBR received from the PCF 103 to the RAN 101 and the UPF (the UPF1 202 when the first PDU session and the second PDU session are supported by the same UPF, and the UFP2 400 when the first PDU session and the second PDU session are supported by different UPFs) by the procedures shown in FIGS. 10 and 11. FIG. 3A to FIG. 5A Further, the SMF 200 or 500 can transmit the slice-AMBR of the second PDU session to the RAN 101 and the UPF 202 or 400 supporting the second PDU session.

[0323] The RAN 101 and the UPF 202 or 400 can control the data rate of the non-GBR QoS flow of the second PDU session based on at least one of the second session-AMBR and the slice-AMBR.

[0324] Further, the PCF 103 according to an embodiment of the disclosure can control / change the first session-AMBR and the second session-AMBR based on the first PDU session status information and the second PDU session status information. To this end, the PCF 103 can request the SMF 200 or 500 for the first PDU session status information and the second PDU session status information, and acquire the first PDU session status information and the second PDU session status information from the SMF 200 or 500. For example, in operation 222 of FIG. 9, FIG. 3B The PCF 103 can request an event subscription for the first PDU session status in order to receive information of a change when the first PDU session status information is changed. The SMF1 200 can store the event subscription request from the PCF 103, and notify the PCF 103 of the change when the first PDU session related status is changed. Further, the PCF 103 can request an event subscription for the second PDU session status in order to receive information of a change when the second PDU session status information is changed in operation 322 of FIG. 10 or operation 522 of FIG. 11. The SMF 200 or 500 can store the event subscription request from the PCF 103, and notify the PCF 103 of the change when the second PDU session related status is changed. FIG. 10 FIG. 10 For example, when the status of the second PDU session is changed by the procedure shown in FIG. 11, the PCF 103 can receive the changed information of the second PDU session status from the SMF 200 or 500 in operation 322 of FIG. 10 or operation 522 of FIG. 11.

[0325] For example, when the status of the second PDU session is changed by the procedure shown in FIG. 11, the PCF 103 can receive the changed information of the second PDU session status from the SMF 200 or 500 in operation 322 of FIG. 10 or operation 522 of FIG. 11. FIG. 11 ​The illustrated procedure changes after the first PDU session and the second PDU session are established, and the changed status information means that the second PDU session is not currently used when the status of the first PDU session changes from the active state to the deactivated state. The SMF 200 or 500 can notify the PCF 103 of the second PDU session status information. The PCF 103 can determine that the data rate used as the session-AMBR for the second PDU session is not currently used based on the information received from the SMF 200 or 500, and change the data rate used as the session-AMBR for the second PDU session to the session-AMBR used for the PDU session currently in the active state (e.g., the first PDU session). Accordingly, the PCF 103 can notify the SMF1 200 of the changed first session-AMBR. In addition, the PCF 103 can notify the SMF 200 or 500 of the changed second session-AMBR.

[0326] The SMF1 200 can transmit the changed first session-AMBR to the RAN 101 and the UPF1 202 supporting the first PDU session through a procedure (PDU session modification procedure) illustrated below. In addition, the SMF1 200 can transmit the slice-AMBR for the first PDU session to the RAN 101 and the UPF1 202 supporting the first PDU session. FIG. 11 The RAN 101 and the UPF1 202 can control the data rate of the non-GBR QoS flow of the first PDU session based on at least one of the first session-AMBR and the slice-AMBR.

[0327] The RAN 101 and the UPF1 202 can control the data rate of the non-GBR QoS flow of the first PDU session based on at least one of the first session-AMBR and the slice-AMBR.

[0328] The SMF 200 or 500 can transmit the changed second session-AMBR to the RAN 101 and the UPF (the UPF1 202 when the first PDU session and the second PDU session are supported by the same UPF, and the UFP2 400 when the first PDU session and the second PDU session are supported by different UPFs) supporting the second PDU session through a PDU session modification procedure. In addition, the SMF 200 or 500 can transmit the slice-AMBR for the second PDU session to the RAN 101 and the UPF1 202 or 400 supporting the second PDU session.

[0329] The RAN 101 and the UPF1 202 or 400 can control the data rate of the non-GBR QoS flow of the second PDU session based on at least one of the changed second session-AMBR and the slice-AMBR.

[0330] Subsequently, another embodiment according to the disclosure is described.

[0331] Embodiments of the disclosure can be applied to a roaming case. According to an embodiment, based on a service provider policy, a slice-AMBR can be applied to data rates of a home routed roaming session and a local breakout roaming session. In this case, the slice-AMBR applied to the data rates of the home routed roaming session and the local breakout roaming session can be determined based on a home public land mobile network (HPLMN) policy or a visited public land mobile network (VPLMN) policy. Further, the slice-AMBR can be determined based on an agreement between the HPLMN and the VPLMN (e.g., a service level agreement (SLA) between the HPLMN and the VPLMN or an interaction between NFs of the HPLMN and NFs of the VPLMN (e.g., an interaction between a hPCF and a vPCF or a value determined by a vSMF or a vPCF based on a value received from a hUDM)). In the above description, "h" is an abbreviation for home, and "v" is an abbreviation for visited. That is, the hPCF can be a PCF located in a home network, and the vPCF can be a PCF located in a visited network.

[0332] According to another embodiment, based on a service provider policy, a slice-AMBR can be divided into a value applied to data rates of a home routed roaming session and a value applied to data rates of a local breakout roaming session. In this case, the slice-AMBR applied to the data rates of the home routed roaming session can be determined based on an HPLMN policy. The slice-AMBR applied to the data rates of the local breakout roaming session can be determined based on a VPLMN policy. Further, the slice-AMBR can be determined based on an agreement between the HPLMN and the VPLMN (e.g., an SLA between the HPLMN and the VPLMN or an interaction between NFs of the HPLMN and NFs of the VPLMN (e.g., an interaction between a hPCF and a vPCF or a value determined by a vSMF or a vPCF based on a value received from a hUDM)).

[0333] According to another embodiment, based on the service provider policy, a first slice-AMBR can be applied to the data rate of the home routed roaming session and a second slice-AMBR can be applied to the data rate of the local breakout roaming session. In this case, the first slice-AMBR applied to the data rate of the home routed roaming session can be determined based on the HPLMN policy. The second slice-AMBR applied to the data rate of the local breakout roaming session can be determined based on the VPLMN policy. Further, the slice-AMBR can be determined based on the agreement between the HPLMN and the VPLMN (e.g., the SLA between the HPLMN and the VPLMN or the interaction between the NFs of the HPLMN and the NFs of the VPLMN (e.g., the interaction between the hPCF and the vPCF or the value determined by the vSMF or the vPCF based on the value received from the hUDM)).

[0334] Referring to FIG. 11 The AMF 102 that receives the PDU session establishment request message from the UE 100 in operation 1001 can determine whether the session requested by the UE 100 corresponds to home routed roaming or local breakout roaming. The AMF 102 can select the SMF based on the determination and / or the service provider policy.

[0335] According to an embodiment, when the slice-AMBR is applied to the data rate of the home routed roaming session and the local breakout roaming session, the AMF 102 can select the SMF (and / or the PCF) such that the SMF (and / or the PCF) for the home routed roaming session is the same as the SMF (and / or the PCF) for the local breakout roaming session in operation 1002.

[0336] According to another embodiment, when the slice-AMBR applied to the data rate of the home routed roaming session and the data rate of the local breakout roaming session is separated, the AMF 102 can select the SMF such that the SMF (and / or the PCF) for the home routed roaming session is different from the SMF (and / or the PCF) for the local breakout roaming session in operation 1002, which is different from FIG. 11

[0337] When the AMF 102 selects the SMF1 200 based on one of the above-described methods, the AMF 102 can transmit a PDU session creation request message to the SMF1 200 in order to generate a PDU session in operation 1003.

[0338] ​The SMF1 200 receiving the PDU session creation request message from the AMF 102 in operation 1003 can determine the session-AMBR for the roaming session requested by the UE considering the slice-AMBR (not shown). Alternatively, the PCF 103 establishing a policy association with the SMF1 200 can determine the session-AMBR for the roaming session requested by the UE considering the slice-AMBR (not shown). The following SMF1 200 can be an SMF of the HPLMN or an SMF of the VPLMN. The following PCF can be a PCF of the HPLMN or a PCF of the VPLMN.

[0339] According to an embodiment, when the session requested by the UE 100 is a home-routed roaming session and the slice-AMBR applied to the data rate of the home-routed roaming session is determined based on the HPLMN policy, the SMF (and / or the PCF) can determine the session-AMBR based on at least one of the subscribed slice-AMBR, the service network slice-AMBR, and the authorized slice-AMBR received from the NF (e.g., UDM, PCF, or SMF) of the HPLMN.

[0340] According to an embodiment, when the session requested by the UE 100 is a home-routed roaming session and the slice-AMBR applied to the data rate of the home-routed roaming session is determined based on the VPLMN policy, the SMF (and / or the PCF) can determine the session-AMBR based on at least one of the subscribed slice-AMBR, the service network slice-AMBR, and the authorized slice-AMBR received from the NF (e.g., UDM, PCF, or SMF) of the HPLMN and / or the NF (e.g., PCF) of the VPLMN.

[0341] According to an embodiment, when the session requested by the UE 100 is a home-routed roaming session and the slice-AMBR applied to the data rate of the home-routed roaming session is determined based on the VPLMN policy, the SMF (and / or the PCF) can determine the session-AMBR based on at least one of the subscribed slice-AMBR, the service network slice-AMBR, and the authorized slice-AMBR received from the NF (e.g., UDM, PCF, or SMF) of the HPLMN and / or the NF (e.g., PCF) of the VPLMN.

[0342] According to an embodiment, when the session requested by the UE 100 is a local breakout roaming session and a slice-AMBR applied to the data rate of the local breakout roaming session is determined based on a VPLMN policy, the SMF (and / or the PCF) can determine the session-AMBR based on at least one of a subscribed slice-AMBR, a serving network slice-AMBR, and an authorized slice-AMBR received from an NF (e.g., a UDM, a PCF, or an SMF) of an HPLMN and / or an NF (e.g., a PCF) of a VPLMN.

[0343] The above-disclosed embodiments can be applied to an EPC interworking case.

[0344] FIG. 11 An interworking structure of a 5GS system and an EPS system is illustrated.

[0345] In FIG. 11 , the UE 100, the RAN 101, and the AMF 102 can be elements of the same 5G network described above. In addition, a second UE 1100 of a mobile communication network such as 3G and / or 4G can be connected to an SGW 1103 and an MME 1102 via an E-TURAN 1101. The SGW 1103 can transmit data / information / signals to a network entity capable of performing the same or similar operations as those described in the present disclosure.

[0346] In FIG. 11 , elements for interworking between a 3G and / or 4G mobile communication network and a 5G mobile communication network are additionally included. Specifically, in FIG. 8 , the UFP+PGW-U 1111 and the E-UTRAN 1101 can perform data processing of the user plane described above and perform data processing in units of network slices. Accordingly, when a data service is provided to a specific UE through one or more network slices, data transmission can be performed based on at least one of a subscribed slice-AMBR, a serving network slice-AMBR, and an authorized slice-AMBR.

[0347] In addition, in FIG. 8 , the SMF+PGW-C 1112 can be a network entity capable of providing an SMF function according to the above-disclosed embodiments. FIG. 8 The PCF 1113 of may provide a PCF function according to the above-disclosed embodiments. FIG. 9The HSS+UDM 1114 can provide UDM functions according to the above-disclosed embodiments. The SMF+PGW-UDM 1112 can receive UE subscription information of a specific UE 100 or 1100 from the HSS+ 1114. The UE subscription information can include the slice-AMBR. The SMF+PGW-C 1112 and / or the PCF 1113 can consider the slice-AMBR to determine a data rate of a PDU connection requested by the UE. When the SMF+PGW-C 1112 determines the data rate, the SMF+PGW-C 1112 can determine the data rate through interaction with the PCF 1113. The SMF+PGW-C 1112 can transmit the data rate determined by the SMF+PGW-C 1112 or received from the PCF 1113 to the UPF-PGW-U 1111. Further, the SMF+PGW-C 1112 can transmit the data rate determined by the SMF+PGW-C 1112 or received from the PCF 1113 to the E-UTRAN 1101 via the SGW 1103 and the MME 1102.

[0348] FIG. 9 is a block diagram illustrating internal functions of an NF according to various embodiments of the disclosure.

[0349] Before describing FIG. 1 to FIG. 7 , the NF can be one of the AMF 102, the PCF 103, the UDM 104, the SMF1 200, the SMF2 500, the UPF1 202, and the UPF2 400 described in the disclosure. Further, the NF can be one of the SGW 1103, the UPF+PFW-U 1111, the SMF+PGW-C 1112, the PCF 1113, and the HSS+UDM 1114 interworking with a 3G mobile communication network and / or a 4G mobile communication network.

[0350] Referring to ​ , the network interface 810 can communicate with another network entity in the core network. For example, when the NF is the AMF 102, the NF can communicate with the SMF1 200, the SMF2 500, and the PCF 103. In another example, when the NF is the PCF 103, the NF can communicate with the AMF 102, the UDM 104, and the SMF1 200. In a similar or identical manner, when the NF is one specific network entity, the network interface 810 can communicate with another entity in the core network. In another example, when the NF is the SMF+PGW-C 1112, the NF can communicate with one of the UPF+PFW-U 1111, the PCF 1113, and the HSS+UDM 1114. The network interface can be implemented in a specific circuit / logic hardware.

[0351] The controller 811 can be implemented as at least one processor or / and a program for performing operations of the NF. For example, when the NF is the AMF 102, the controller 811 can perform operations of the AMF 102. In another example, when the NF is the PCF 103, operations of the PCF 103 can be performed. In another example, when the NF is the SMF+PGW-C 1112, control operations corresponding to the SMF+PGW-C 1112 can be performed. In the case of other network entities, control required for performing operations can be performed identically.

[0352] The memory 812 can store programs and pieces of control information required for the controller 811, and also store information described in the present disclosure. The memory 812 can be implemented in various forms, and configured in any form having a format such as a semiconductor memory, a buffer, a hard disk, a RAM, or a ROM. Further, data that can be stored in the memory 812 can store information received by the AMF 102 or information received from an external entity when the NF is the AMF 102. In another example, when the NF is the PCF 103, control information required for the PCF 103 and / or received information can be stored. In another example, when the NF is the UDM 104, pieces of information such as information related to a user equipment and information for UDM control can be stored. In another example, when the NF is the SMF1 200, the above-described data and data for control can be stored. Other network entities can also store information required for the above-described operations.

[0353] In addition to the above-described elements, the NF can further include various interfaces for accessing an operator. In the present disclosure, there is no special limitation on such additional elements.

[0354] ​ is a block diagram illustrating an interval function of a UE according to various embodiments of the present disclosure.

[0355] Referring to ​ , the UE 100 can include a transceiver 910, a controller 920, and a memory 930. The UE 100 can further have more elements according to implementation scenarios. For example, various additional devices for a user interface, such as a display, an input unit, a sensor, etc., can be further included. The present disclosure does not limit such additional elements.

[0356] Based on the reference ​In the described embodiment, the transceiver 910 can be connected to the RAN 101 via a radio channel and can transmit and receive signals and / or messages to and from the RAN 101. When the UE 100 is communicating with a 5G network, the transceiver 910 can be a device capable of transmitting and receiving signals with the 5G communication network. Furthermore, the transceiver 910 can include a communication processor as needed. If the transceiver 910 does not include a communication processor, all signals and / or messages can be processed by a controller.

[0357] The controller 920 may control the basic operations of the UE 100 and control the reception and storage of the above-mentioned messages. In addition, the controller 920 may control the transmission or reception of data through a specific network slice. The controller 920 may be configured by at least one processor.

[0358] The memory 930 may store various pieces of data required to control the UE 100 and may have an area for storing messages received from the RAN 101 and / or a specific NF of the core network in order to perform communication through the aforementioned network slice. The memory 930 may be implemented in various forms and configured in any form having a format such as a semiconductor memory, a buffer, a hard disk, a RAM, or a ROM.

[0359] The methods according to various embodiments described in the claims or specification of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0360] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. At least one program may include instructions for causing the electronic device to perform the method according to the various embodiments of the present disclosure as defined by the appended claims and / or disclosed herein.

[0361] Programs (software modules or software) can be stored in non-volatile memories, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, compact disk ROM (CD-ROM), digital versatile disk (DVD) or other types of optical storage devices or magnetic tapes. Alternatively, any combination of some or all of them can form a memory for storing programs. In addition, multiple such memories may be included in an electronic device.

[0362] Further, programs can be stored in an attachable storage device that can access the electronic device through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), and a storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. Further, a storage device separated on a communication network can access the portable electronic device.

[0363] In the above detailed embodiments of the disclosure, according to the presented detailed embodiments, the elements included in the disclosure are expressed in singular or plural. However, for the convenience of description, the singular form or the plural form is appropriately selected to the presented case, and the disclosure is not limited by the elements expressed in singular or plural. Therefore, the elements expressed in plural can also include a single element, or the elements expressed in singular can also include a plurality of elements.

[0364] Although specific embodiments have been described in the detailed description of the disclosure, various modifications and changes can be made to the disclosure without departing from the scope of the disclosure. Therefore, the scope of the disclosure should not be defined as limited to the embodiments, but should be defined by the appended claims and their equivalents.

[0365]

Industrial applicability

[0366] The disclosure can be used to control the data rate of a UE when a wireless communication system has a network slicing structure.

Claims

1.A method, performed by a session management function (SMF) entity, for controlling a data rate of a terminal in a wireless communication system, the method comprising: receiving, from an access and mobility management function (AMF) entity, a protocol data unit (PDU) session creation request message including a PDU session identifier (ID), a single network slice selection assistance information (S-NSSAI), and a data network name (DNN); receiving, from a unified data management (UDM) entity, subscription information including a subscribed S-NSSAI and a subscribed session aggregate maximum bit rate (AMBR) for the subscribed S-NSSAI; transmitting, to the AMF entity, a PDU session creation response message based on the PDU session creation request message; and transmitting, to the AMF entity, a first message including session management information including a per-slice maximum bit rate (MBR) corresponding to the S-NSSAI, wherein the per-slice MBR is applied to at least one PDU session of the terminal corresponding to the S-NSSAI, and wherein bit rates of all guaranteed bit rate (GBR) quality of service (QoS) flows and non-GBR QoS flows included in the at least one PDU session do not exceed the per-slice MBR. 2.A method, performed by an access and mobility management function (AMF) entity, for controlling a data rate of a terminal in a wireless communication system, the method comprising: transmitting, to a session management function (SMF) entity, a protocol data unit (PDU) session creation request message including a PDU session identifier (ID), a single network slice selection assistance information (S-NSSAI), and a data network name (DNN); receiving, from the SMF entity, a PDU session creation response message based on the PDU session creation request message; receiving, from the SMF entity, a first message including session management information including a per-slice maximum bit rate (MBR) corresponding to the transmitted S-NSSAI; transmitting, to a base station, an N2 PDU session request message including the session management information, wherein the per-slice MBR is applied to at least one protocol data unit (PDU) session of a terminal corresponding to the S-NSSAI, and wherein bit rates of all guaranteed bit rate (GBR) quality of service (QoS) flows and non-GBR QoS flows included in the at least one PDU session do not exceed the per-slice MBR. 3.A method, performed by a base station, for controlling a data rate of a terminal in a wireless communication system, the method comprising: transmitting, to an access and mobility management (AMF) entity, a registration request message for a terminal; and receiving, from the AMF, an N2 PDU session request message including session management information based on the transmission of the registration request message, wherein the session management information includes a per-slice maximum bit rate (MBR), wherein the per-slice MBR is applied to at least one protocol data unit (PDU) session of a terminal corresponding to a single network slice selection assistance information (S-NSSAI), and ​ ​ ​ wherein a bit rate of all guaranteed bit rate (GBR) quality of service (QoS) flows and non-GBR QoS flows included in the at least one PDU session does not exceed the per-slice MBR. 4.A session management function (SMF) entity for controlling a data rate of a terminal in a wireless communication system, the SMF entity comprising: a transceiver; and at least one processor configured to: receive, from an access and mobility management function (AMF) entity, a protocol data unit (PDU) session creation request message including a PDU session identifier (ID), a single network slice selection assistance information (S-NSSAI), and a data network name (DNN), receive, from a unified data management (UDM) entity, subscription information including a subscribed S-NSSAI and a subscribed session aggregate maximum bit rate (AMBR) for the subscribed S-NSSAI, transmit, to the AMF entity, a PDU session creation response message based on the PDU session creation request message, and transmit, to the AMF entity, a first message including session management information including a per-slice maximum bit rate (MBR) corresponding to the S-NSSAI, wherein the per-slice MBR is applied to at least one PDU session of the terminal corresponding to the S-NSSAI, and wherein a bit rate of all guaranteed bit rate (GBR) quality of service (QoS) flows and non-GBR QoS flows included in the at least one PDU session does not exceed the per-slice MBR. 5.An access and mobility management function (AMF) entity for controlling a data rate of a terminal in a wireless communication system, the AMF entity comprising: a transceiver; and at least one processor configured to: transmit, to a session management function (SMF) entity, a protocol data unit (PDU) session creation request message including a PDU session identifier (ID), a single network slice selection assistance information (S-NSSAI), and a data network name (DNN), receive, from the SMF entity, a PDU session creation response message based on the PDU session creation request message, receive, from the SMF entity, a first message including session management information including a per-slice maximum bit rate (MBR) corresponding to the transmitted S-NSSAI, and transmit, to a base station, an N2 PDU session request message including the session management information, wherein the per-slice MBR is applied to at least one protocol data unit (PDU) session of the terminal corresponding to the S-NSSAI, and wherein a bit rate of all guaranteed bit rate (GBR) quality of service (QoS) flows and non-GBR QoS flows included in the at least one PDU session does not exceed the per-slice MBR. 6.A base station for controlling a data rate of a terminal in a wireless communication system, the base station comprising: a transceiver; and at least one processor configured to: transmit, to an access and mobility (AMF) entity, a registration request message for a terminal, and ​ receiving, from the AMF based on the sending of the registration request message, an N2 PDU session request message including session management information, wherein the session management information includes a maximum bit rate, MBR, wherein the per-slice MBR is applied to at least one protocol data unit, PDU, session of the terminal corresponding to a single network slice selection assistance information, S-NSSAI, and wherein a bit rate of all guaranteed bit rate, GBR, quality of service, QoS, flows and non-GBR QoS flows included in the at least one PDU session does not exceed the per-slice MBR.

Images