Method and apparatus for changing data session in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. This method for processing a control signal in a wireless communication system comprises the operations of: receiving a first control signal transmitted from a network entity; processing the received first control signal; and transmitting, to the network entity, a second control signal generated on the basis of the processing.

Description

Method and device for changing a data session in a wireless communication system

[0001] The present disclosure relates to a method and device for changing a data session in a wireless communication system, and more particularly, to a method and device for changing a PDU Session to support a new service data flow that occurs due to a user's use of a new service.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz band, such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band (Above 6GHz), also called millimeter wave (mmWave), such as 28GHz and 39GHz. In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and ultra-low latency that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for ultra-wideband services (eMBB: enhanced Mobile Broadband), ultra-reliable / ultra-low-latency communications (URLLC: Ultra-Reliable Low-Latency Communications), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO (Massive MIMO) to alleviate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple sub-carrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and polar codes for reliable transmission of control information, L2 pre-processing, and specific services. Standardization has been progressed for network slicing, which provides specialized, dedicated networks.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

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

[0006] When such 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, which will require enhanced functions and performance of 5G mobile communication systems and integrated operation of connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, and AI (Artificial Intelligence) from the design stage and internalize end-to-end AI support functions to realize system optimization, and ultra-high-performance communication and computing resources to realize services with complexity that exceeds the limits of terminal computing capabilities. It could serve as a basis for the development of next-generation distributed computing technologies.

[0008] The present disclosure aims to provide a method and device that can effectively provide a change in a PDU Session when a new service data flow is created in a wireless communication system.

[0009] Based on the discussion described above, the present disclosure provides a method for processing a control signal in a wireless communication system, which may include: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0010] According to an embodiment of the present disclosure, a device and method capable of effectively providing a service in a wireless communication system are provided.

[0011] FIG. 1 illustrates the structure of a 5G network according to one embodiment of the present disclosure.

[0012] FIG. 2 illustrates a UPF module according to one embodiment of the present disclosure.

[0013] FIG. 3 illustrates Light UPF and Heavy UPF deployment scenarios according to one embodiment of the present disclosure.

[0014] FIG. 4 illustrates a route selection method for transmitting a service data flow of a terminal to a data network according to one embodiment of the present disclosure.

[0015] FIG. 5 illustrates a route selection method for transmitting a service data flow of a terminal to a data network based on Light UPF according to one embodiment of the present disclosure.

[0016] FIG. 6 illustrates a UPF instance change according to one embodiment of the present disclosure.

[0017] FIG. 7 illustrates PDU Session Modification procedures according to one embodiment of the present disclosure.

[0018] Figure 8 shows the configuration of a terminal according to an embodiment of the present disclosure.

[0019] FIG. 9 illustrates the configuration of a base station or network entity according to an embodiment of the present disclosure.

[0020] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

[0021] In describing the embodiments herein, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0022] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0023] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0024] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0025] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0026] Here, the term '~ unit' used in this embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to regenerate one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card.

[0027] In this disclosure, phrases such as “A and / or B,” “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used merely to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

[0028] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel form to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0029] In the present disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and components included in the network structure of FIG. 1 may each mean a physical entity, or may mean software performing an individual function, or hardware combined with software. Reference symbols shown as Nx, such as N1, N2, N3, ... in the drawings, represent known interfaces between NFs in a 5G core network (CN), and since a related description may refer to the standard specification (TS 23.501), a detailed description will be omitted.

[0030] In the following description, terms used to identify connection nodes, terms referring to network entities (NEs) or network functions (NFs), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0031] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0032] FIG. 1 is a diagram showing an example of a configuration of a wireless communication system according to an embodiment of the present disclosure, and FIG. 1 exemplifies the configuration of a 5G system.

[0033] Referring to FIG. 1, a 5G network may include network entities (NE) or network functions (NF) described below.

[0034] (R)AN ((Radio) Access Network) is an entity that performs wireless resource allocation of a terminal, and may be at least one of an eNode B, a Node B, a BS (Base Station), an NG-RAN (Next Generation Radio Access Network), a 5G-AN (5G Access Network), a 5G NR (5G New Radio), a radio access unit, a base station controller, or a node on a network.

[0035] The terminal may include a UE (User Equipment), NG UE (Next Generation UE), MS (Mobile Station), cellular phone, smartphone, computer, IoT (Internet of Things) device, or multimedia system capable of performing communication functions.

[0036] Furthermore, while the embodiments of the present disclosure are described below with respect to a 5G system, the embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure can be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0037] As wireless communication systems evolve from 4G to 5G, a new core network (CN) called the Next Generation Core (NG Core) or 5GC (5G Core Network) is defined. This new core network virtualizes all existing network entities (NEs) into network functions (NFs). According to one embodiment of the present disclosure, a network function may refer to a network entity, a network component, or a network resource.

[0038] According to one embodiment of the present disclosure, 5GC may include NFs as illustrated in FIG. 1. Of course, the present invention is not limited to the example illustrated in FIG. 1, and 5GC may include more or fewer NFs than the number of NFs illustrated in FIG. 1.

[0039] The Access and Mobility Management Function (AMF) may be a network function that manages the access and mobility of a terminal (UE). For example, AMF may perform network functions such as terminal registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0040] The Session Management Function (SMF) may be a network function that manages the Packet Data Network (PDN) connection provided to the user equipment (UE). The PDN connection may be referred to as a Packet Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management through the establishment, modification, and release of sessions and the maintenance of tunnels between the UPF and the RAN required for this; user plane (UP) selection and control; traffic processing control in the UPF; and charging data collection control.

[0041] PCF (Policy Control Function) may be a network function that applies the mobile carrier's service policy, charging policy, and PDU Session policy to the terminal.

[0042] Unified Data Management (UDM) can be a network function that stores subscriber information. For example, UDM can perform functions such as generating authentication information for 3GPP security, processing user identifiers (User IDs), managing a list of network functions supporting UEs, and managing subscription information.

[0043] The Network Exposure Function (NEF) may provide terminal information to servers outside the 5G network. Additionally, NEF may provide the information necessary for 5G network services and store it in the Unified Data Repository (UDR).

[0044] The User Plane Function (UPF) may function as a gateway that transmits user data (PDU) to the Data Network (DN). More specifically, the UPF may perform the role of processing data so that data transmitted by a terminal can be transmitted to an external network or data received from an external network can be transmitted to the terminal. For example, the UPF may perform network functions such as serving as an anchor between radio access technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report generation, and buffering.

[0045] NRF (Network Repository Function) can store the profiles of NFs and perform the function of discovering NFs.

[0046] AUSF (Authentication Server Function) can perform terminal authentication in 3GPP access networks and non-3GPP access networks.

[0047] NSSF (Network Slice Selection Function) can perform the function of selecting a Network Slice Instance provided to a terminal.

[0048] The Network Data Analytics Function (NWDAF) collects data from multiple NFs (Network Functions) to ensure efficient operation of the 5GC network. This data is analyzed using artificial intelligence (e.g., machine learning (ML) or deep learning) models, and the results are provided back to the NFs, supporting each NF in providing efficient network services.

[0049] An Application Function (AF) can communicate with a network operator to enable external servers (Application Servers) to utilize network services provided by the network operator. Depending on the deployment entity, AFs can be categorized as internal AFs and external AFs. Internal AFs deployed by network operators can communicate directly with NFs within the network operator. AFs deployed by third-party service providers (3rd-party service providers) may need to go through an NEF to communicate with NFs within the network operator.

[0050] DN (Data Network) includes a data network where terminals transmit and receive data in order to use network operator services or third-party services.

[0051] The terminal may include an IoT device. The IoT device may include a device that does not use battery power or operates with very little power, and such IoT devices may be referred to as ambient IoT devices (or simply Ambient IoT).

[0052] According to one embodiment of the present disclosure, the UPF module may be composed of multiple modules and functions according to a modular design. According to one embodiment of the present disclosure, when a newly created service data flow (Service Data Flow or IP Flow) uses a new module of the UPF, or when an existing service data flow terminates service and the UPF module it was using is no longer in use, the use of the UPF module may be changed using a PDU Session Modification procedure.

[0053] FIG. 2 illustrates a UPF according to one embodiment of the present disclosure.

[0054] The services provided by UPF can be divided into mandatory functionality and optional functionality. Mandatory functionality includes at least one function essential for the services UPF must provide, while optional functionality may include at least one function necessary to provide additional services beyond the essential functionality of UPF.

[0055] Mandatory functionality provided by UPF may include at least one of a data storage module, a data processing module, a packet processing module, a packet buffer module, a policy rule enforcement module, a traffic usage reporting module, a traffic verification module, and a quality of service (QoS) handling module.

[0056] Optional functionality provided by UPF may include at least one of a network address translation (NAT) module for network address translation, a domain name system (DNS) snooping module, a firewall module, a traffic optimization module, a shallow packet inspection (SPI) module, and a deep packet inspection (DPI) module.

[0057] Referring to Figure 2, a UPF in which all functions are modularized according to the module design and only essential functions are included, excluding additional functions, may be referred to as a Light UPF. Furthermore, a UPF in which functions are not modularized and all essential and additional functions are included may be referred to as a Heavy UPF.

[0058] For example, the UPF may include a packet processing module to receive user packets from a data network and transmit them to a terminal, and to receive user packets from a terminal and transmit them to the data network.

[0059] For example, the UPF may include an SPI module (shallow packet inspection) and / or a DPI module (deep packet inspection) for examining user packets received from a terminal or data network. However, the SPI module (shallow packet inspection) and the DPI module (deep packet inspection) may not be services / functions that the UPF must necessarily provide.

[0060] Modularizing UPF by function allows for the expansion and reduction of resources for each module, thereby enhancing the flexibility of UPF resource provision. Furthermore, modularizing UPF by function allows for the addition and / or deletion of non-essential features to UPF at any time as needed, potentially resulting in cost savings compared to the traditional, fully-functional Heavy UPF.

[0061] FIG. 3 illustrates Light UPF and Heavy UPF deployment scenarios according to one embodiment of the present disclosure.

[0062] Referring to FIG. 3, in a scenario based on Heavy UPF, all service data flows are processed by the same UPF regardless of the type of service data flow used by the terminal. However, in a scenario based on Light UPF, a Light UPF that will handle the service data flow may be selected based on the type of service data flow used by the terminal, taking into account the additional functions of the UPF. In one embodiment, in the case of a service data flow for a banking service, a Light UPF that provides a Firewall additional function may be selected because security is important. In one embodiment, in the case of a service data flow for a video streaming service, a Light UPF that provides a Caching additional function may be selected because packet latency, which may cause buffering, is important.

[0063] FIG. 4 illustrates a route selection method for transmitting a service data flow of a terminal to a data network according to one embodiment of the present disclosure.

[0064] In 5G networks, URSP (UE Route Selection Policy) information can be used to select a path for transmitting service data flows generated from terminals to the data network.

[0065] In one embodiment, the URSP information may include a prioritized list of URSP rules. In one embodiment, each URSP rule may include at least one of a Rule precedence for application priority, a Traffic descriptor for distinguishing service data flows, and a List of Route Selection Descriptors for selecting a path for the service data flows distinguished by the Traffic descriptor.

[0066] In one embodiment, the Traffic descriptor may include at least one of Application descriptors, IP descriptors, Domain descriptors, Non-IP descriptors, and a data network name (DNN).

[0067] In one embodiment, each Route Selection Descriptor may include at least one of Route Selection Descriptor Precedence, Route Selection Components, and Route Selection Validation Criteria for application priority of each Route Selection Descriptor.

[0068] In one embodiment, Route Selection Components may include at least one of Session and Service Continuity (SSC) Mode Selection, Network Slice Selection, Data Network Name (DNN) Selection, Protocol Data Unit (PDU) Session Type Selection, and Access Type preference.

[0069] Tables 1 to 3 below describe UE Route Selection Policy information.

[0070]

[0071] In one embodiment, a UE Route Selection Policy (URSP) Rule may be pre-configured in the terminal. In one embodiment, the URSP Rule may be configured by a network entity (or PCF).

[0072] In one embodiment, the PCF may transmit or provide the URSP Rule to the terminal during the initial registration procedure. In one embodiment, the PCF may transmit or provide the URSP Rule to the terminal when the location of the terminal changes or when the AMF managing the mobility of the terminal changes.

[0073] In one embodiment, the URSP Rule may be used to determine whether to associate application traffic detected by the terminal with a previously created PDU Session (or data session), offload application traffic detected by the terminal to a non-3GPP access network other than the PDU Session, or request creation of a new PDU Session.

[0074] In one embodiment, the URSP Rule may include at least one of a service and session continuity mode (SSC) selection policy, a network slice selection policy, a data network name (DNN) selection policy, a non-seamless offloading policy, and an access type preference indicating whether to prefer a 3GPP access network or a non-3GPP access network.

[0075]

[0076]

[0077] Referring to FIG. 4, a service data flow generated at a terminal can be distinguished by a traffic descriptor and a path can be selected by the corresponding route selection components. Here, the selection of a path can indicate the selection of a PDU session.

[0078] In one embodiment, if there is a PDU Session that satisfies the Route Selection Components value among the existing PDU Sessions (or data sessions) created by the terminal, the terminal can transmit a newly created service flow to the data network using the PDU Session.

[0079] In one embodiment, if there is no PDU Session that satisfies the Route Selection Components value among the existing PDU Sessions created by the terminal, the terminal can create a new PDU Session based on the Route Selection Components value and transmit the service data flow to the data network using the newly created PDU Session.

[0080] In one embodiment disclosed in Fig. 4, the values ​​of Route Selection Components are as follows.

[0081] SSC Mode Selection: SSC 1

[0082] Network Slice Selection: S-NSSAI #1

[0083] DNN Selection: DNN #1

[0084] PDU Session Type Selection: IP Type

[0085] In Fig. 4, since PDU Session #1 among the existing PDU Sessions (PDU Session #1, PDU Session #2) satisfies the Route Selection Components, the service data flow generated at the terminal is selected as a path to PDU Session #1, and the terminal can transmit data to the data network using PDU Session #1.

[0086] FIG. 5 illustrates a route selection method for transmitting a service data flow of a terminal to a data network via Light UPF according to one embodiment of the present disclosure.

[0087] Referring to FIG. 5, the system may include at least one of a terminal, a base station, a first Light UPF, a second Light UPF, and a data network. Each of the first Light UPF and the second Light UPF may include mandatory functionalities and at least one specific optional functionality.

[0088] For example, the first Light UPF may include a data processing module as mandatory functionality and a firewall module as specific optional functionality. Furthermore, for example, the second Light UPF may include a data processing module as mandatory functionality and a caching module as specific optional functionality.

[0089] For example, a data network may include a content service provider (e.g., Netflix) that can provide content to a terminal, a public service provider that can provide public services to a terminal, a banking service provider that can provide banking services to a terminal, and may include various other service providers.

[0090] Referring to FIG. 5, a terminal can create two PDU Sessions (PDU Session #1, PDU Session #2). The two PDU Sessions (PDU Session #1, PDU Session #2) can have the same Route Selection Components values ​​except for the UPF Functionality value.

[0091] In one embodiment, PDU Session #1 may be connected to the data network via a first Light UPF with an added Firewall module. Additionally, PDU Session #2 may be connected to the data network via a second Light UPF with an added Caching module.

[0092] In one embodiment, the UPF Functionality value of the Route Selection Components for a newly created service data flow may be defined as a Firewall value. At this time, the terminal may select PDU Session #1 using the first Light UPF with the Firewall additional function based on the Route Selection Components value, and may transmit and receive the service data flow to and from the data network based on PDU Session #1.

[0093] In one embodiment, the UPF Functionality value of the Route Selection Components for a newly created service data flow may be defined as a Caching value. At this time, the terminal may select PDU Session #2 using the second Light UPF with the Caching additional function based on the Route Selection Components value, and may transmit and receive the service data flow to and from the data network based on PDU Session #2.

[0094] Table 4 below shows the extended Route Selection Descriptor including the List of UPF Functionality Descriptors values.

[0095]

[0096] In Table 4, List of UPF Functionality Descriptors represents a list of UPF Functionality Descriptors, and the components of UPF Functionality Descriptors are described in Table 5.

[0097] The Extended Route Selection Descriptor in Table 4 may be included in a UE Route Selection Policy (URSP) Rule. In one embodiment, the URSP Rule may be pre-configured in the UE. In one embodiment, the URSP Rule may be configured by a network entity (or PCF).

[0098] In one embodiment, the PCF may transmit or provide the URSP Rule to the terminal during the initial registration procedure. In one embodiment, the PCF may transmit or provide the URSP Rule to the terminal when the location of the terminal changes or when the AMF managing the mobility of the terminal changes.

[0099] In one embodiment, a URSP Rule may be used by a terminal to determine whether to associate application traffic detected by the terminal with a previously created PDU Session or to request the creation of a new PDU Session.

[0100] Table 5 below shows the UPF Functionality Descriptors.

[0101]

[0102] Referring to Table 5, UPF Functionality Descriptor Precedence indicates the priority in applying the UPF Functionality Descriptor.

[0103] Referring to Table 5, UPF Functionality Components can be composed of UPF Functionality values ​​and Mandatory or Optional values. However, UPF Functionality Components values ​​are not limited to the values ​​listed above. UPF Functionality Components values ​​can include more values ​​as needed. For example, UPF Functionality Components values ​​can include more values ​​related to Light UPF (such as packet processing capability) and / or the performance of additional features.

[0104] UPF Functionality indicates the UPF additional functionality required by the service data flow. UPF Functionality values ​​may include, but are not limited to, NAT, DNS Snooping, Firewall, Traffic Optimization, Shallow Packet Inspection, and / or Deep Packet Inspection.

[0105] Mandatory or Optional indicates whether the UPF Functionality value is a mandatory function or an additional function for processing the service data flow. In one embodiment, if the UPF Functionality value is a mandatory function for processing the service data flow, a Light UPF capable of performing the UPF Functionality must be selected. If the UPF Functionality value is an additional function for processing the service data flow, a Light UPF that cannot perform the UPF Functionality may be selected in some cases.

[0106] In one embodiment, UPF Functionality Components that are Optional cannot have a UPF Functionality Descriptor Precedence value that takes precedence over UPF Functionality Components that are Mandatory.

[0107] FIG. 6 illustrates a UPF instance change according to one embodiment of the present disclosure.

[0108] In one embodiment, a user may run a banking application on a terminal to use banking services. The terminal may use a URSP Rule to select a PDU Session to transmit a service data flow generated by the banking application to a data network. Referring to FIG. 6, if a previously generated PDU Session (or data session) on the terminal satisfies the Route Selection Components values ​​of the new service data flow, the terminal may transmit the banking service data flow using the existing PDU Session.

[0109] However, the UPF Functionality Components of the banking service data flow include a firewall module, an additional feature of UPF. This additional feature is not included in the Light UPF, which currently handles PDU sessions. If this additional feature is Optional, SMF can ignore it. However, if it is Mandatory, it must be supported. To achieve this, SMF must switch to Light UPF, which includes the firewall feature.

[0110] One embodiment of the present disclosure may propose PDU Session Modification procedures for modifying UPF instances for additional functionality of Light UPF and other reasons.

[0111] FIG. 7 illustrates PDU Session Modification procedures according to one embodiment of the present disclosure.

[0112] In operation 1a, the terminal can initiate the PDU Session modification procedure by sending a PDU Session Modification Request message to the network. To transmit a newly created service data flow to the data network, the terminal can select a PDU Session using the URSP Rule. At this time, if the existing PDU Session satisfies the Route Selection Components value of the service data flow but does not satisfy the UPF Functionality Components value, the terminal can initiate the PDU Session modification procedure. As another example, when the additional functionality of the UPF required by the existing service data flow is changed, the terminal can also change it through the PDU Session modification procedure. If the UPF Functionality is Optional, the terminal may not perform the PDU Session modification procedure depending on the mobile network operator's policy or the terminal implementation and service provider's policy. However, if the UPF Functionality is Mandatory, the terminal can perform the PDU Session modification procedure.

[0113] The terminal includes Requested UPF Functionality Components in the PDU Session Modification Request message. This may indicate the UPF Functionality Components values ​​included in the URSP Rule of the new service data flow.

[0114] When the user's subscription information (e.g., Session Management Subscription Data) stored in the UDM in Action 1c is changed, the PDU Session change procedure may be initiated. For example, when some of the UPF add-ons available to the user become unavailable due to a change in the user's subscription information, the UPF instance may be changed using the PDU Session change procedure to reflect this change.

[0115] In Action 1d, a PDU Session change procedure may be performed by the SMF. For example, if the SMF recognizes that a newly created service data flow requires or no longer requires a specific UPF add-on, the SMF may initiate a PDU Session change procedure to reflect this.

[0116] SM Policy Association information may change in connection with additional UPF features requested in Action 2. For example, a new UPF feature may be added to an existing PDU Session, or conversely, a UPF feature previously applied to an existing PDU Session may be removed. Furthermore, the associated SM Policy Rule may change depending on the addition / deletion of a UPF feature.

[0117] In Action 2-1, the SMF can select a new UPF instance. If the UPF currently handling the PDU Session does not support the requested UPF Functionality, the SMF can switch to a new UPF instance that can support the requested additional functionality.

[0118] If SMF changed the responsible UPF to a new UPF instance in Actions 2-1a and 2-1b, it can create a new UPF instance and N4 Session by creating N4 Rules with additional UPF Functionality.

[0119] If SMF has not modified the new UPF instance, i.e., if the existing UPF instance supports the requested UPF Functionality but has been deactivated because it is not using the functionality, the N4 Session Modification procedure can be used to activate the UPF Functionality and transfer the related N4 Rules to the UPF instance.

[0120] If SMF deactivates or activates UPF Functionality without changing the existing UPF instance in Action 2-1c, SMF can update the corresponding UPF Instance Profile stored in NRF using the Nnrf_NFManagement_NFUpdate Rquest message.

[0121] In the procedures of operation 3a to operation 5, information related to PDU Session modification can be transmitted to the RAN and the UE. The SMF transmits QoS Rule information related to the UPF Functionality requested additionally to the N2 SM information to the RAN. The SMF can inform the UE of the result of the Requested UPF Functionality requested by the UE (whether the network accepted the addition or change of a new UPF Functionality) with the Granted Indication for Requested UPF Functionality value in the PDU Session Modification Command message. The SMF can reject the UE's request. In addition, the SMF can provide the UE with QoS Rules and QoS Profile information related to the additionally requested UPF Functionality.

[0122] FIG. 8 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0123] A terminal according to one embodiment of the present disclosure may include a processor (820) that controls the overall operation of the terminal, a transceiver (800) including a transmitter and a receiver, and a memory (810). Of course, the present invention is not limited to the above example, and the terminal may include more or fewer components than those illustrated in FIG. 8. The terminal of FIG. 8 may correspond to the terminals of FIGS. 1 to 7.

[0124] According to one embodiment of the present disclosure, the transceiver (800) can transmit and receive signals with network entities or other terminals. The signals transmitted and received with the network entities may include control information and data. In addition, the transceiver (800) can receive signals via a wireless channel, output them to the processor (820), and transmit the signals output from the processor (820) via the wireless channel.

[0125] According to one embodiment of the present disclosure, the processor (820) can control the terminal to perform any one of the operations described above. Meanwhile, the processor (820), the memory (810), and the transceiver (800) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (820) and the transceiver (800) can be electrically connected. In addition, the processor (820) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0126] According to one embodiment of the present disclosure, the memory (810) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (510) provides the stored data upon request of the processor (820). The memory (510) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (810). In addition, the processor (820) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (810).

[0127] FIG. 9 is a diagram illustrating the configuration of a base station or network entity according to an embodiment of the present disclosure.

[0128] A network entity according to one embodiment of the present disclosure may include a processor (920) that controls the overall operation of the network entity, a transceiver (900) including a transmitter and a receiver, and a memory (910). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than those illustrated in FIG. 9. The network entity of FIG. 9 may correspond to the network entities (or network functions) of FIGS. 1 to 7.

[0129] According to one embodiment of the present disclosure, the transceiver (900) can transmit and receive signals with at least one of other network entities or terminals. The signals transmitted and received with at least one of the other network entities or terminals may include control information and data.

[0130] According to one embodiment of the present disclosure, the processor (920) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (920), the memory (910), and the transceiver (900) do not necessarily have to be implemented as separate modules, and can of course be implemented as a single component in the form of a single chip. In addition, the processor (920) and the transceiver (600) can be electrically connected. In addition, the processor (920) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0131] According to one embodiment of the present disclosure, the memory (910) can store data such as basic programs, application programs, and setting information for the operation of a network entity. In particular, the memory (910) provides the stored data upon request of the processor (920). The memory (910) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (910). In addition, the processor (920) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (910).

[0132] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operations described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made within a scope that does not detract from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

[0133] The operations of the base station or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the base station or terminal device. That is, the control unit of the base station or terminal device can execute the operations described above by reading and executing the program code stored in the memory device using a processor or CPU (Central Processing Unit).

[0134] The various components and modules of the entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.

[0135] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

[0136] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0137] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

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

[0139] While the detailed description of the present disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims described below but also by equivalents thereof. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-described embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above-described embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

[0140] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. A method performed by an SMF (session management function) entity of a wireless communication system, A step of receiving information about a user plane function (UPF) function requested for a new service data flow from a terminal via an access and mobility management function (AMF) entity; and A method comprising the steps of selecting a second UPF supporting the requested UPF function and establishing an N4 session with the second UPF, if the first UPF for the current PDU (packet data unit) session does not support the requested UPF function.

2. In paragraph 1, If the requested UPF function is disabled in the first UPF for the current PDU session: A step of activating the requested UPF function through the above 1st UPF and N4 session change procedures; and A method further comprising the step of transmitting a message to a network repository function (NRF) entity for updating a profile of a first UPF.

3. In paragraph 1, A step of transmitting a QoS (quality of service) rule regarding the requested UPF function to the base station; and A method further comprising the step of transmitting an indication of whether or not the requested UPF function is applicable to the terminal via the base station.

4. In paragraph 3, A method further comprising the step of transmitting QoS rules and QoS profiles regarding the requested UPF function to the terminal via the base station.

5. In paragraph 1, A method wherein the information about the requested UPF function comprises either information about a mandatory UPF function or information about an optional UPF function.

6. In paragraph 1, A method further comprising the step of performing a PCF (policy control function) entity and an SM Policy association modification procedure.

7. In a method performed by a terminal of a wireless communication system, A step of transmitting information about a requested UPF (user plane function) function for a new service data flow to an SMF (session management function) entity via an AMF (access and mobility management function) entity; and A method comprising the step of receiving an indication of whether the requested UPF function is applicable, via a base station, from the SMF entity.

8. In paragraph 7, A method further comprising the step of receiving QoS rules and QoS profiles regarding the requested UPF function from the SMF entity via the base station.

9. In the SMF (session management function) of a wireless communication system, Transmitter and receiver; and Including a control unit connected to the above transmitter and receiver, The above control unit: Receive information about a requested UPF (user plane function) function for a new service data flow from the terminal via an AMF (access and mobility management function) entity, and An SMF entity configured to select a second UPF supporting the requested UPF functionality and establish an N4 session with the second UPF if the first UPF for the current PDU (packet data unit) session does not support the requested UPF functionality.

10. In paragraph 9, the control unit, If the requested UPF function is disabled in the first UPF for the current PDU session: Activate the requested UPF function through the above 1st UPF and N4 session change procedures, and An SMF entity configured to send a message to an NRF (network repository function) entity to update the profile of the first UPF.

11. In paragraph 9, the control unit, Transmitting to the base station, a QoS (quality of service) rule regarding the requested UPF function, and An SMF entity configured to transmit an indication to the terminal via the base station regarding whether the requested UPF function is applicable.

12. In paragraph 11, the control unit, An SMF entity further configured to transmit QoS rules and QoS profiles regarding the requested UPF function to the terminal via the base station.

13. In paragraph 9, An SMF entity that contains information about the requested UPF capability, either information about mandatory UPF capabilities or information about optional UPF capabilities.

14. In the terminal of a wireless communication system, Transmitter and receiver; and Including a control unit connected to the above transmitter and receiver, The above control unit: Transmits information about the requested UPF (user plane function) function for a new service data flow to the SMF (session management function) entity via the AMF (access and mobility management function) entity, and A terminal configured to receive an indication of whether the requested UPF function is applicable via the base station from the SMF entity.

15. In paragraph 14, the control unit, A terminal further configured to receive QoS rules and QoS profiles regarding the requested UPF function from the SMF entity via the base station.

Images