Method and apparatus for managing traffic on basis of dynamic traffic characteristics in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. In an embodiment of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system may comprise the steps of: receiving a request message associated with traffic characteristics in a target service flow; generating first PCC rule information regarding first traffic characteristics of the target service flow and second PCC rule information regarding second traffic characteristics thereof on the basis of the request message; and transmitting the first PCC rule information and the second PCC rule information to a session management function (SMF) entity.

Description

Method and device for managing traffic based on dynamic traffic characteristics in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for managing traffic based on dynamic traffic characteristics in a wireless communication system.

[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 frequency band, such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band (above 6GHz), 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 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate 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 subcarrier 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, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[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 (Industrial Internet of Things, IIoT) 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 technologies 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, service-based interface) 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] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these 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 will require the development of 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, AI-based communication technology that utilizes artificial intelligence (AI) from the design stage and internalizes end-to-end AI support functions to realize system optimization, and next-generation distributed computing technology that realizes services with complexity that exceeds the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis.

[0008] In one embodiment of the present disclosure, a method performed by a Policy Control Function (PCF) entity in a wireless communication system may include: receiving a request message associated with a traffic characteristic in a target service flow; generating, based on the request message, first Policy and Charging Control (PCC) rule information for a first traffic characteristic of the target service flow and second PCC rule information for a second traffic characteristic of the target service flow; and transmitting the first PCC rule information and the second PCC rule information to a Session Management Function (SMF) entity.

[0009] In one embodiment of the present disclosure, a method performed by a Session Management Function (SMF) entity in a wireless communication system may include the steps of receiving first Policy and Charging Control (PCC) rule information for a first traffic characteristic of a target service flow and second PCC rule information for a second traffic characteristic of the target service flow from a Policy Control Function (PCF) entity, generating first N4 rule information for the first traffic characteristic and second N4 rule information for the second traffic characteristic based on the first PCC rule information and the second PCC rule information, and transmitting the first N4 rule information and the second N4 rule information to a User Plane Function (UPF) entity.

[0010] In one embodiment of the present disclosure, a Policy Control Function (PCF) entity in a wireless communication system includes a transceiver and at least one processor connected to the transceiver, wherein the at least one processor receives a request message associated with a traffic characteristic in a target service flow, and generates, based on the request message, first Policy and Charging Control (PCC) rule information for a first traffic characteristic of the target service flow and second PCC rule information for a second traffic characteristic of the target service flow, and transmits the first PCC rule information and the second PCC rule information to a Session Management Function (SMF) entity.

[0011] In one embodiment of the present disclosure, a Session Management Function (SMF) entity in a wireless communication system includes a transceiver and at least one processor connected to the transceiver, wherein the at least one processor receives first Policy and Charging Control (PCC) rule information for a first traffic characteristic of a target service flow and second PCC rule information for a second traffic characteristic of the target service flow from a Policy Control Function (PCF) entity, generates first N4 rule information for the first traffic characteristic and second N4 rule for the second traffic characteristic based on the first PCC rule information and the second PCC rule information, and transmits the first N4 rule information and the second N4 rule information to a User Plane Function (UPF) entity.

[0012] FIG. 1 is a diagram illustrating an example of a network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0013] FIG. 2 is a diagram illustrating an example of transmitting information related to changes in traffic characteristics within a floor to a control plane via a 5G system in one embodiment of the present disclosure.

[0014] FIG. 3A is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a radio access network (RAN) to support temporary traffic changes within a service floor, according to one embodiment of the present disclosure.

[0015] FIG. 3b is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a RAN to support temporary traffic changes within a service floor, according to one embodiment of the present disclosure.

[0016] FIG. 4A is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a radio access network (RAN) to support temporary traffic changes within a service floor, according to one embodiment of the present disclosure.

[0017] FIG. 4b is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a radio access network (RAN) to support temporary traffic changes within a service floor, according to one embodiment of the present disclosure.

[0018] FIG. 5A is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a RAN to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure.

[0019] FIG. 5b is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a RAN to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure.

[0020] FIG. 5c is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a RAN to support temporary traffic changes within a service floor, according to one embodiment of the present disclosure.

[0021] FIG. 6 is a drawing showing an example of a configuration of a terminal according to one embodiment of the present disclosure.

[0022] FIG. 7 is a diagram illustrating an example of a configuration of a base station or network entity according to one embodiment of the present disclosure.

[0023] FIG. 8 is a diagram illustrating an example of a method performed by a network entity in one embodiment of the present disclosure.

[0024] FIG. 9 is a diagram illustrating an example of a method performed by a network entity in one embodiment of the present disclosure.

[0025] 3GPP, responsible for cellular mobile communications standards, is currently standardizing a new core network architecture, named 5G Core (5GC), to facilitate the evolution of 4G LTE systems to 5G systems. Compared to the Evolved Packet Core (EPC), the network core for 4G, 5GC can support the following differentiated features:

[0026] 5GC introduces network slice functionality. As a requirement of 5G, 5GC must support a variety of terminal types and services. For example, enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine Type Communications (mMTC). These terminals and services may each have different requirements for the core network. For example, eMBB services may require high data rates, while URLLC services may require high reliability and low latency. To meet these diverse service requirements, network slice technology has been proposed.

[0027] Network slicing can refer to a method of virtualizing a single physical network to create multiple logical networks (e.g., network slices). An activated network slice can be called a network slice instance (NSI), and each network slice instance can have different characteristics. By configuring a network function (NF) for each NSI according to its characteristics, mobile carriers can satisfy various service requirements for different terminals / services. For example, mobile carriers can efficiently support various 5G services (e.g., eMBB, URLLC, or mMTC) by allocating an NSI that matches the characteristics of the service required for each terminal.

[0028] 5GC can easily support the network virtualization paradigm by separating mobility management functions from session management functions. In 4G LTE, all terminals can receive services from the network through signaling exchanges with a single core entity called the Mobility Management Entity (MME), which is responsible for registration, authentication, mobility management, and session management. In 5G, the number of terminals (including, for example, MTC terminals) will explode, and the mobility and traffic / session characteristics that must be supported depending on the terminal type will become more specialized. Therefore, supporting all functions from a single entity (e.g., MME) will inevitably reduce scalability by adding entities for each required function. Therefore, various functions are being developed based on a structure that separates mobility management and session management functions to improve scalability in terms of functional / implementation complexity and signaling load of the core entity responsible for the control plane.

[0029] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Furthermore, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined in light of their functions within the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0030] 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 may be assigned the same reference number.

[0031] The advantages and features of the technical ideas according to the present disclosure, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below 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 present disclosure is complete and to fully inform those skilled in the art of the disclosure of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals may refer to like elements throughout the specification.

[0032] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of an eNode B, a Node B, a BS (Base Station), a RAN (Radio Access Network), an AN (Access Network), a RAN node, 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 the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station.

[0033] In addition, although one or more embodiments of the present disclosure may be described below using LTE (Long Term Evolution), LTE-A (LTE-Advanced), or 5G (5th-generation) systems as examples, one or more embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which the embodiments of the present disclosure may be applied, and 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0034] It will be appreciated that each block of the flowchart drawings and combinations of the flowchart drawings 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, such that the instructions, when executed by the processor of the computer or other programmable data processing equipment, create a means for performing the functions described in the flowchart 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 perform the functions in a specific manner, such that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flowchart 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).

[0035] 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.

[0036] The term '~ unit' used in the embodiments of the present disclosure means a software or hardware component such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), and the '~ unit' can perform 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 play 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, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0037] For metaverse and XR applications, terminals must transmit and receive large amounts of traffic. Therefore, effectively handling this traffic presents a significant technical challenge, unlike traditional applications. While previous research has primarily focused on effectively transmitting application server traffic to terminals, metaverse / XR traffic presents a new challenge: effectively handling large volumes of traffic and service flows with diverse characteristics.

[0038] In the case of metaverse and XR applications, a large amount of data must be transmitted, and a method to reduce network congestion can be applied for effective scheduling. To this end, in XRM (Extended Reality and Media service), a method for data forwarding and processing in units of PDU (protocol data units) was introduced in consideration of the characteristics within the flow for efficient scheduling in addition to the existing simple 5-tuple-based flow-based data forwarding concept in the UPF (user plane function). In the application layer, data forwarding and processing in units of PDUs with similar characteristics can be distinguished into logical units called PDU sets.

[0039] In one embodiment of the present disclosure, when the characteristics of data traffic within a service floor transmitted from an application server or a terminal change according to a network situation and a request, information on the changed characteristics can be provided on a control plane or included in RTP (Real-time Transport Protocol) header extension (HE) information, etc., thereby providing the time point and related information on when the data characteristics change during real-time data transmission of the service floor, and a method for accurate processing can be proposed when processing data in units of PDUs in UPF.

[0040] According to one embodiment of the present disclosure, when traffic characteristics (data rate, codec type, etc.) within a service floor change due to congestion within a network, the UPF can be informed of the change in characteristics within the service floor through information on the control plane or in-band signaling to recognize information about the time of change, etc. In this way, when the UPF processes data in units of PDUs (PDU sets) considering the characteristics of the application layer, information for processing a bundle of PDUs with the same characteristics is transmitted, thereby providing an efficient service even when traffic characteristics change depending on the network situation. In addition, when separate in-band signaling is not provided due to operator policy, etc., the change in traffic characteristics and related information can be informed to the PCF (policy control function) through AF, so that the UPF can be informed of packet detection rules that take traffic changes into account.

[0041] FIG. 1 is a diagram illustrating an example of a network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0042] A network entity included in the network structure of the 5G system of Fig. 1 may include a network function (NF) depending on the system implementation.

[0043] Referring to FIG. 1, the network architecture of a 5G system may include various network entities. For example, the 5G system may include an authentication server function (AUSF), an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), an application function (AF), a unified data management (UDM), a data network (DN), a network exposure function (NEF), an edge application service domain repository (EDR), an edge application server (EAS), an EAS discovery function (EASDF), a user plane function (UPF), a (radio) access network (R)AN, and a terminal, i.e., a user equipment (UE).

[0044] Each NF in a 5G system can support the following functions:

[0045] AUSF can process and store data for UE authentication.

[0046] AMF provides functions for access and mobility management on a per-UE basis, and one UE can be connected to one AMF by default. Specifically, AMF can support signaling between Core Network (CN) nodes for mobility between 3GPP access networks, termination of Radio Access Network (RAN) Control Plane (CP) interface (i.e., N2 interface), termination (N1) of Non Access Stratum (NAS) signaling, NAS signaling security (NAS ciphering and integrity protection), Access Stratum (AS) security control, registration management (registration area management), connection management, idle mode UE reachability (including control and performance of paging retransmission), mobility management control (subscription and policy), intra-system mobility and inter-system mobility support, network slicing support, and SMF selection. Additionally, the AMF may support functions such as Lawful Intercept (LI) (for AMF events and interfaces to the LI system), providing forwarding of Session Management (SM) messages between the UE and the SMSF, acting as a transparent proxy for routing SM messages, access authentication, access authorization including roaming authorization checks, providing forwarding of SMS messages between the UE and the SMSF, Security Anchor Function (SAF) and / or Security Context Management (SCM). Some or all of the functions of the AMF may be supported within a single instance of the AMF.

[0047] A DN may represent, for example, an operator service, an Internet connection, or a third-party service. A DN may transmit a downlink protocol data unit (PDU) to a UPF or receive a PDU transmitted from a UE from the UPF.

[0048] PCF can receive information about packet flows from application servers and provide functions to determine policies such as mobility management and session management. Specifically, PCF can support functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane functions (e.g., AMF, SMF, etc.) can enforce the policy rules, and implementing a front end for accessing relevant subscription information for policy decision-making within the User Data Repository (UDR).

[0049] The SMF provides session management functions, and when a UE has multiple sessions, each session can be managed by a different SMF. Specifically, the SMF can support session management (e.g., session establishment, modification, and termination, including tunnel maintenance between the UPF and (R)AN nodes), UE IP address allocation and management (optionally including authentication), selection and control of UP functions, traffic steering configuration to route traffic from the UPF to the appropriate destination, termination of interfaces to policy control functions, enforcement of the control portion of policies and Quality of Service (QoS), and lawful intercept (for SM events and interfaces to the LI system). The SMF can also support functions such as termination of the SM portion of NAS messages, downlink data notification, initiation of AN-specific SM information (forwarded to the (R)AN via N2 via the AMF), determination of the SSC mode of a session, and roaming functions. Some or all of the features of an SMF may be supported within a single instance of an SMF.

[0050] The UDM stores user subscription data, policy data, and more. It can include two parts: the application front end (FE) and the user data repository (UDR).

[0051] The FE may include a UDM FE, which is responsible for location management, subscription management, and credential processing, and a PCF, which is responsible for policy control. The UDR may store data required for the functions provided by the UDM-FE and policy profiles required by the PCF. The data stored in the UDR may include user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. The UDM-FE may access subscription information stored in the UDR and support functions such as authentication credential processing, user identification handling, access authentication, registration / mobility management, subscription management, and SMS management.

[0052] The UPF can forward downlink PDUs received from the DN to the UE via the (R)AN, and forward uplink PDUs received from the UE via the (R)AN to the DN. Specifically, the UPF can support an anchor point for intra / inter RAT mobility, an external PDU session point for interconnection to a data network, a user plane part of packet routing and forwarding, packet inspection and policy rule enforcement, and an uplink classifier to support lawful intercept, traffic usage reporting, and routing of traffic flows to the data network. Additionally, UPF may support functions such as branching points to support multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement), uplink traffic validation (Service Data Flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering, and downlink data notification triggering. Some or all of the functions of UPF may be supported within a single instance of a UPF.

[0053] AF can interact with the 3GPP core network to provide services (e.g., support for application influence on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control).

[0054] (R)AN can be a general term for a new radio access network that supports both evolved E-UTRA, an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB).

[0055] The gNB may support functions for radio resource management (e.g., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to the UE in uplink / downlink (i.e., scheduling), IP (internet protocol) header compression, encryption and integrity protection of user data streams, selection of an AMF upon UE attachment if routing to the AMF is not determined from information provided to the UE, routing of user plane data to UPF(s), routing of control plane information to the AMF, connection setup and teardown. Additionally, the gNB may support functions such as scheduling and forwarding of paging messages (originating from AMF), scheduling and forwarding of system broadcast information (originating from AMF or Operating and Maintenance (O&M)), measurement and measurement reporting setup for mobility and scheduling, transport level packet marking in uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in inactive mode, distribution of NAS messages, NAS node selection, sharing of radio access networks, dual connectivity, and tight interworking between NR and E-UTRA.

[0056] UE can refer to a user equipment. A user equipment may be referred to by terms such as terminal, mobile equipment (ME), or mobile station (MS). Furthermore, a user equipment may be a portable device, such as a laptop, mobile phone, personal digital assistant (PDA), smartphone, or multimedia device, or a non-portable device, such as a personal computer (PC) or vehicle-mounted device.

[0057] The NEF may provide a means to securely expose services and capabilities provided by 3GPP network functions, such as third-party, internal exposure / re-exposure, application functions, and edge computing. The NEF may receive information from other NF(s) (based on the exposed capability(s) of other NF(s)). The NEF may store the received information as structured data using a standardized interface to a data storage network function. The stored information may be re-exposed by the NEF to other NF(s) and AF(s) and used for other purposes, such as analysis.

[0058] EASDF can be an NF that can add an ECS (EDNS (Extension Mechanisms for DNS) Client Subnet) option, which can be expressed as the address of a DNS server to forward the DNS (Domain Name System) request of the terminal for each FQDN (Fully Qualified Domain Name) and the IP subnet address to be added when forwarding the DNS request of the terminal. EASDF can receive EAS domain configuration information from EDR and process the DNS request message received from the terminal according to the received information.

[0059] In addition, the EASDF may be an NF that receives a terminal IP address and location information of the terminal within 3GPP from the SMF, and DNS message processing rules and DNS message reporting rules, processes a DNS query message received from the terminal, a DNS response message received from a DNS server, and transmits information in a DNS message and statistical information processed therefrom to the SMF according to the DNS message reporting rules.

[0060] All NFs shown in Fig. 1 can interact with NRF as needed.

[0061] NRF can support service discovery. It can receive NF discovery requests from NF instances and provide information about discovered NF instances to the NF instances. Furthermore, NRF can maintain a list of available NF instances and the services they support.

[0062] Meanwhile, for convenience of explanation, FIG. 1 illustrates a reference model for a case where a UE accesses one DN using one PDU session, but the present disclosure is not limited thereto.

[0063] A UE can access two (i.e., local and central) data networks simultaneously using multiple PDU sessions. Two SMFs can be selected for different PDU sessions. However, each SMF can have the ability to control both the local UPF and the central UPF within the PDU session.

[0064] Additionally, the UE may simultaneously access two (i.e., local and central) data networks provided within a single PDU session.

[0065] In the 3GPP system, a conceptual link connecting NFs within a 5G system can be defined as a reference point. For example, the reference point(s) included in the 5G system of Figure 1 are as follows.

[0066] - N1: Reference point between UE and AMF

[0067] - N2: Reference point between (R)AN and AMF

[0068] - N3: Reference point between (R)AN and UPF

[0069] - N4: Reference point between SMF and UPF

[0070] - N5: Reference point between PCF and AF

[0071] - N6: Reference point between UPF and DN

[0072] - N7: Reference point between SMF and PCF

[0073] - N8: Reference point between UDM and AMF

[0074] - N9: Reference point between two core UPFs

[0075] - N10: Reference point between UDM and SMF

[0076] - N11: Reference point between AMF and SMF

[0077] - N12: Reference point between AMF and AUSF

[0078] - N13: Reference points between UDM and AUSF

[0079] - N14: Reference point between two AMFs

[0080] - N15: Reference point between PCF and AMF in non-roaming scenario, reference point between PCF and AMF in visited network in roaming scenario.

[0081] - Nx: Reference point between SMF and EASDF

[0082] - Ny: Reference point between NEF (EDF) and EASDF

[0083] FIG. 2 is a diagram illustrating an example of transmitting information related to changes in intra-floor traffic characteristics to a control plane via a 5G system, according to one embodiment of the present disclosure. FIG. 2 is a diagram illustrating an example of transmitting information on requirements for detecting changes in intra-floor traffic characteristics and information on intra-floor traffic characteristics to a control plane via a 5G system, according to one embodiment of the present disclosure.

[0084] In existing 5G systems, a QoS floor within a PDU session can be a way to express the smallest unit of QoS difference. 5G QoS characteristics can be determined by a 5QI (QoS identifier). Through a 5G system, a large amount of traffic may temporarily be transmitted within a floor on the control plane depending on the temporary requirements of the terminal. For example, when a user's viewpoint or time movement is selected based on a service user's choice while using a network rendering-based VR service or VoD service, a new image or video may be required to be transmitted to the terminal within the user's recognized time point according to service requirements, etc., in order to play the video at that time. To support changes in temporary traffic characteristics such as the above, in addition to the existing QoS floor profile (e.g., Base QoS profile), a QoS profile (e.g., Dynamic QoS profile) that considers the characteristics of the traffic that will be temporarily changed can be additionally created. In addition, the characteristics of the QoS floor being serviced (e.g., Maximum Data Burst Volume, MDBV) can be changed only for a specific period of time.

[0085] AF can transmit to PCF, information on traffic characteristics within the floor (basic traffic characteristics and traffic characteristics to be changed), including information on the maximum data burst volume that it supports according to service requirements and / or at least one of the type, resolution, data rate, frame rate, and data burst size of the content.

[0086] The PCF can generate information to support a service that supports temporary traffic characteristic changes based on traffic characteristic change detection information (e.g., dynamic traffic characteristic detection information), traffic characteristic information (e.g., dynamic traffic characteristic requirement), and service support indicators that support temporary traffic characteristic changes (e.g., dynamic traffic characteristic change support indication) received from the AF. The PCF can generate a PCC (Policy and Charging Control) rule that includes traffic characteristic change detection information, Base QoS profile, Dynamic QoS profile, Data Burst Size, and dynamic traffic characteristic change support indication, and forward it to the SMF.

[0087] Based on the PCC rule information received from the PCF, the SMF can transmit information to the UPF and RAN to support services that support temporary traffic characteristic changes. Based on the dynamic traffic characteristic change support indication information and traffic characteristic change detection information (e.g., dynamic traffic characteristic detection information), the SMF can generate an N4 rule to request the UPF to generate information for detecting traffic characteristic changes within the service data floor and transmitting traffic characteristic change information to the RAN. In addition, the SMF can transmit the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc. to the RAN.

[0088] The RAN, which has received information such as the Base QoS profile, Dynamic QoS profile, and Data Burst Size from the SMF, can process the corresponding QoS floor based on the Base QoS profile until a separate instruction or traffic change notification information is transmitted. If traffic change notification information is transmitted through the UPF or SMF, the RAN can process traffic within the corresponding QoS floor based on information such as the Dynamic QoS profile and Data Burst Size received from the SMF.

[0089] After receiving an N4 rule from the SMF, which includes requirements such as detecting changes in traffic characteristics within the service data floor and generating traffic characteristic change notification information, the UPF can perform monitoring operations on traffic transmitted in the corresponding service data floor. The data traffic monitoring operation can be performed based on traffic characteristic change detection information (e.g., dynamic traffic characteristic detection information) transmitted from the AF. For example, if the AS (Application Server) explicitly notifies that the characteristics of a specific packet have changed, such as through the dynamic traffic characteristic change flag transmitted through the RTP HE (header) field, the AF can transmit information that it can detect the change in the traffic characteristics through information within the header information within the specific header or protocol. Alternatively, if the AS cannot explicitly transmit packet characteristic change information through the header field within the specific header or protocol, the AF can transmit relevant information that can measure the implicit packet characteristic change.

[0090] For example, by measuring the average data rate between packets or monitoring the interval between packets (based on frame rate) or packet delivery pattern (based on GOP (Group Of Pictures) information), if there is a change in the interval between packets or the pattern of packets, the UPF can recognize that the characteristics of the traffic received from the AS through the service data flow have changed. The UPF, which recognizes that the traffic characteristics have changed, can generate traffic characteristics change notification information to request that QoS profile information considering the changed traffic characteristics information be applied to the QoS floor.

[0091] The traffic characteristic change notification information generated by the UPF can be directly transmitted to the RAN on the user plane or can be transmitted to the RAN through the SMF on the control plane. For example, the UPF can mark the traffic characteristic change notification information in the form of a Dynamic Traffic Characteristic Change Indication (DCI) or a Dynamic Traffic Characteristic Change Flag in the GTP-U (GPRS (General Packet Radio Service) Tunneling Protocol-User plane) extension header and directly transmit it to the RAN on the user plane. Alternatively, the UPF can transmit the Dynamic Traffic Characteristic Change Indication (DCI) to the SMF through an event reporting message generated by the UPF, and the SMF can then transmit the traffic characteristic change notification information to the RAN through the AMF.

[0092] Afterwards, when notification information related to a traffic change event detected through the UPF is transmitted through the UPF or SMF, the RAN can process traffic within the corresponding QoS floor based on information such as the Dynamic QoS profile and Data Burst Size received from the SMF. If there is a requirement to support temporary traffic characteristic changes in uplink data, the SMF can transmit the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc. to the UE through the N1 SM Container. If the AS requests a traffic characteristic change for uplink data, the SMF or UPF can support the temporary traffic characteristic change transmitted by the UE by transmitting the traffic characteristic change notification information detected by the UPF to the UE through the RAN.

[0093] FIG. 3A is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a radio access network (RAN) to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure. FIG. 3B is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a RAN to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure. For example, FIG. 3B may illustrate one or more operations subsequent to FIG. 3A.

[0094] In step 1, the AF can determine a service request considering changes in traffic characteristics of the service floor currently being serviced at the discretion of the AS or the AF.

[0095] In step 2, the AF may transmit an AF session service operation create / update request message (AFsessionWithQoS Create / Update request) to the NEF, which includes a QoS requirement including an indicator requesting support for a dynamic traffic characteristic change service (Dynamic Traffic Characteristic Change Support Indication), traffic characteristic change detection information (Dynamic Traffic Characteristic Detection Information), and traffic characteristic information (Dynamic Traffic Characteristic Requirement). The traffic characteristic information (Dynamic Traffic Characteristic Requirement) transmitted from the AF may include floor traffic characteristic information (basic traffic characteristics and traffic characteristics to be changed) including Maximum Data Burst Volume information and / or at least one of the Type, Resolution, Data Rate, Frame Rate, and Data Burst Size of the content. Dynamic traffic characteristic detection information transmitted from AF includes information on traffic characteristic changes in packets, such as dynamic traffic characteristic change indication, dynamic traffic characteristic change flag, start time of data burst, end of data burst, etc., which are explicitly transmitted through RTP HE fields, etc., and information implicitly transmitted that can measure location information or packet characteristic changes (e.g. average data rate between packets or data rate threshold of basic QoS profile (e.g.It can compare traffic changes between packets based on a threshold for base QoS profile, or can include at least one piece of information such as intervals between packets (based on frame rate), packet delivery patterns (based on GOP information), periodicity information, etc.

[0096] In step 3, service QoS requirement information including an indicator requesting support for dynamic traffic characteristic change service (Dynamic Traffic characteristic change support indication), traffic characteristic change detection information (Dynamic traffic characteristic detection information), and traffic characteristic information (Dynamic traffic characteristic requirement) can be authorized by NEF, and then transmitted to PCF via a PolicyAuthorization create / update request message.

[0097] In step 4, if the PCF determines to support the dynamic traffic characteristic change service based on the dynamic traffic characteristic change support indication, dynamic traffic characteristic detection information, and dynamic traffic characteristic requirement received through the AF, the PCC rule may be updated to support the service. In the updated PCC rule, in addition to the profile of the existing QoS floor (e.g., Base QoS profile), a QoS profile that considers the characteristics of the traffic to be temporarily changed (e.g., Dynamic QoS profile) may be additionally created to support temporary traffic characteristic changes, and the RAN may use the dynamic QoS profile to change the characteristics of the QoS floor being serviced (e.g., MDBV, Maximum Data Burst Volume) only for a specific period of time. In addition, the PCC rule may include information for supporting a traffic characteristic change detection operation in the data floor in the UPF and a traffic characteristic change notification information generation operation.

[0098] In steps 5 and 6, the PCF may convey to the AF whether it accepts or rejects the request for support of dynamic traffic characteristic change service requested by the AF via the PolicyAuthorization_Create / update response and AFsessionWithQoS Create / update response messages. For example, the PCF may convey the PolicyAuthorization_Create / update response message to the NEF, and the NEF may convey the AFsessionWithQoS Create / update response message to the AF.

[0099] In step 7, the PCF in step 4 may determine a policy update based on the dynamic traffic characteristic change service information received from the AF and transmit the updated PCC rule based on the policy update to the SMF. The updated PCC rule may include at least one of: dynamic traffic characteristic detection information for supporting traffic characteristic change detection operation within the data floor; QoS floor-related information to be transmitted to the RAN and / or UE, such as a Base QoS Profile, a Dynamic QoS profile, and a Data Burst Size; dynamic traffic characteristic change support indication for indicating a dynamic traffic characteristic change service support and a transmission operation of service-related information; and information on whether to apply the changed traffic characteristic change information (dynamic QoS profile) for a certain period of time (dynamic traffic characteristic change timer).

[0100] Based on the PCC rule information received from the PCF, the SMF can decide to transmit information to the UPF and RAN to support a service that supports temporary traffic characteristic changes. Based on the dynamic traffic characteristic change support indication information and the dynamic traffic characteristic detection information, the SMF can perform an N4 rule generation operation to request a traffic characteristic change detection operation within the service data floor in the UPF and an information generation operation to transmit the traffic characteristic change information to the RAN. In addition, the SMF can decide to transmit the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc. to the RAN.

[0101] In steps 8 and 9, the SMF may transmit to the UPF an SDF template that includes information on the operation for detecting traffic characteristic changes in the service data floor and the operation for generating information for transmitting traffic characteristic change information to the RAN through the N4 session creation / modification process. After receiving an N4 rule from the SMF that includes requirements for detecting traffic characteristic changes in the service data floor and generating traffic characteristic change notification information, the UPF may perform a monitoring operation on the traffic transmitted in the corresponding service data floor. The data traffic monitoring operation may be performed based on the traffic characteristic change detection information (Dynamic traffic characteristic detection information) transmitted from the AF. For example, if the AS explicitly notifies that the characteristics of a specific packet have changed, such as through the Dynamic traffic characteristic change flag transmitted through the RTP HE field, information indicating that the traffic characteristic change can be detected through information in the header information within a specific header or protocol may be transmitted. Alternatively, if the AS cannot explicitly transmit packet characteristic change information through a specific header or header field within the protocol, relevant information that can measure an implicit packet characteristic change may be transmitted.

[0102] For example, by measuring the average data rate between packets or monitoring the interval between packets (based on frame rate) or packet delivery pattern (based on GOP information), if there is a change between packets or in the pattern of packets, the UPF can recognize that the characteristics of the traffic received from the AS through the service data flow have changed. The UPF, which recognizes that the traffic characteristics have changed, can generate traffic characteristics change notification information to request that QoS profile information considering the changed traffic characteristics information be applied to the QoS floor.

[0103] Traffic characteristic change notification information generated by the UPF can be directly transmitted to the RAN on the user plane or can be transmitted to the RAN through the SMF on the control plane. For example, the UPF can mark the traffic characteristic change notification information in the form of a Dynamic Traffic Characteristic Change Indication (DCI) or a Dynamic Traffic Characteristic Change Flag within the GTP-U extension header and directly transmit it to the RAN on the user plane. Alternatively, the UPF can transmit the Dynamic Traffic Characteristic Change Indication (DCI) to the SMF through an event reporting message generated by the UPF, and the SMF can then transmit the traffic characteristic change notification information to the RAN through the AMF.

[0104] In step 10, the PCF may transmit to the AMF, the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc., which are generated or updated based on the request information for the dynamic traffic characteristic change support service of the AF in step 4. The N1N2 message transmitted to the AMF may include N2 SM information including the Base QoS profile, Dynamic QoS profile, and Data Burst Size transmitted to the RAN, and an N1 SM container including the Base QoS profile, Dynamic QoS profile, and Data Burst Size information for supporting the dynamic traffic characteristic change support service of uplink traffic. The Base QoS profile, Dynamic QoS profile, and Data Burst Size information in the N2 SM information transmitted to the RAN and the Base QoS profile, Dynamic QoS profile, and Data Burst Size information in the N1 SM container transmitted to the UE may be the same or different depending on the settings of the service provider, etc.

[0105] In step 11, the AMF may transmit N2 SM information and N1 SM container including at least one of Base QoS profile, Dynamic QoS profile, and Data Burst Size information to the RAN through an N2 message to support dynamic traffic characteristic changes from the SMF.

[0106] In step 12, the RAN can transmit to the UE an N1 SM container including Base QoS profile, Dynamic QoS profile, and Data Burst Size information to support a service supporting dynamic traffic characteristic changes in uplink traffic to the UE.

[0107] From step 13 to step 14, the UE and RAN may forward response messages of the N2 message, etc. to the SMF. For example, the RAN may send an N2 message response message to the AMF, and the AMF may send an Nsmf_PDUSession_UpdateSMContext Request message to the SMF.

[0108] At step 15, SMF may send an Nsmf_PDUSession_UpdateSMContext Response message to AMF.

[0109] In step 16, the UPF, which recognizes that the traffic characteristic has changed, may generate traffic characteristic change notification information to request application of QoS profile information (Dynamic QoS profile) that takes into account the changed traffic characteristic information to the QoS floor. The traffic characteristic change notification information generated by the UPF may be directly transmitted to the RAN on the user plane or may be transmitted to the RAN through the SMF on the control plane. For example, the UPF may mark the traffic characteristic change notification information in the form of a Dynamic Traffic characteristic change indication (DCI) or a Dynamic Traffic characteristic change Flag in the GTP-U extension header and directly transmit it to the RAN on the user plane. Alternatively, the UPF may transmit the Dynamic Traffic characteristic change indication (DCI) to the SMF through an event reporting message generated by the UPF, and the SMF may transmit the traffic characteristic change notification information to the RAN through the AMF.

[0110] Afterwards, when notification information related to a traffic change event detected through the UPF is transmitted through the UPF or SMF, the RAN can process traffic within the corresponding QoS floor based on information such as the Dynamic QoS profile and Data Burst Size received from the SMF. If there is a requirement to support temporary traffic characteristic changes in uplink data, the SMF can transmit the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc. to the UE through the N1 SM Container. If the AS requests a traffic characteristic change for uplink data, the UPF or SMF can support the temporary traffic characteristic change transmitted by the UE by transmitting the traffic characteristic change notification information detected by the UPF to the UE through the RAN.

[0111] In step 17, the UE may perform uplink traffic transmission operation with the Dynamic QoS profile applied based on traffic characteristic change notification information transmitted from the RAN as a Dynamic Traffic characteristic change indication (DCI) or a Dynamic Traffic characteristic change Flag in the SDAP header. In step 16, if a Dynamic Traffic characteristic change indication (DCI) or a Dynamic Traffic characteristic change Flag is transmitted to the UE, the RAN may perform application of the Dynamic QoS profile to the uplink traffic transmitted from the UE. In addition, if a Burst Data size or a Dynamic Traffic characteristic change Timer is transmitted to the RAN and the UE through the SMF, the RAN and the UE may perform processing operation of the uplink traffic with the Dynamic QoS profile applied during the corresponding time. If an additional Dynamic Traffic characteristic change indication (DCI) or Dynamic Traffic characteristic change Flag is transmitted within the Burst Data size or the Dynamic Traffic characteristic change Timer, the time of the Burst Data size or the Dynamic Traffic characteristic change Timer is extended, and the RAN and the UE may perform processing operation of the uplink traffic with the Dynamic QoS profile applied by additionally considering the extended time.

[0112] FIG. 4A is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a radio access network (RAN) to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure. FIG. 4B is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a RAN to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure. For example, FIG. 4B may illustrate one or more operations subsequent to FIG. 4A.

[0113] The UPF according to an embodiment of the present invention can utilize RQI (Reflective QoS Indicator) information as a means of transmitting dynamic traffic characteristic change information of a downlink. In this case, the AF can instruct the performance of a dynamic traffic characteristic change occurrence information generation operation to transmit dynamic traffic characteristic change occurrence information using RQI if the corresponding PDU Session and terminal support Reflective QoS within the requirements for generating dynamic traffic characteristic change occurrence information. In addition, if Reflective QoS can be applied, when information of RQI is received, the RAN and UE can be configured to perform application of a dynamic QoS profile based on the corresponding indicator information.

[0114] In step 1, the AF can determine a service request considering changes in traffic characteristics of the service floor currently being serviced at the discretion of the AS or the AF.

[0115] In step 2, the AF may transmit an AF session service operation create / update request message (AFsessionWithQoS Create / Update request) to the NEF, which includes an indicator requesting support for a dynamic traffic characteristic change service (Dynamic Traffic Characteristic Change Support Indication), traffic characteristic change detection information (Dynamic Traffic Characteristic Detection Information), traffic characteristic information (Dynamic Traffic Characteristic Requirement), and QoS requirements including a requirement for generating dynamic traffic characteristic change occurrence information. The traffic characteristic information (Dynamic Traffic Characteristic Requirement) transmitted from the AF may include floor traffic characteristic information (basic traffic characteristics and traffic characteristics to be changed) including Maximum Data Burst Volume information and / or at least one of the Type, Resolution, Data rate, Frame rate, and Data Burst Size of the content. Dynamic traffic characteristic detection information transmitted from AF includes information on traffic characteristic changes in packets, such as dynamic traffic characteristic change indication, dynamic traffic characteristic change flag, start time of data burst, end of data burst, etc., which are explicitly transmitted through RTP HE fields, etc., and information implicitly transmitted that can measure location information or packet characteristic changes (e.g. average data rate between packets or data rate threshold of basic QoS profile (e.g.It can compare traffic changes between packets based on a threshold for base QoS profile, or can include at least one piece of information such as intervals between packets (based on frame rate), packet delivery patterns (based on GOP information), periodcity information, etc.

[0116] In step 3, service QoS requirement information including an indicator requesting support for dynamic traffic characteristic change service (Dynamic Traffic characteristic change support indication), traffic characteristic change detection information (Dynamic traffic characteristic detection information), and traffic characteristic information (Dynamic traffic characteristic requirement) can be authorized by NEF, and then transmitted to PCF via a PolicyAuthorization create / update request message.

[0117] In step 4, if the PCF determines to support the dynamic traffic characteristic change service based on the dynamic traffic characteristic change support indication, dynamic traffic characteristic detection information, dynamic traffic characteristic requirement, and dynamic traffic characteristic change occurrence information generation requirement received through the AF, the PCC rule update may be performed to support the service. In the updated PCC rule, in addition to the profile of the existing QoS floor (e.g., Base QoS profile), a QoS profile that considers the characteristics of the traffic to be temporarily changed (e.g., Dynamic QoS profile) may be additionally created to support temporary traffic characteristic changes, and the RAN may use the dynamic QoS profile to change the characteristics of the QoS floor being serviced (e.g., MDBV, Maximum Data Burst Volume) only for a specific period of time. In addition, the PCC rule may include information for supporting a traffic characteristic change detection operation in the data floor in the UPF and a traffic characteristic change notification information generation operation.

[0118] In steps 5 and 6, the PCF may convey to the AF whether it accepts or rejects the request for support of dynamic traffic characteristic change service requested by the AF via the PolicyAuthorization_Create / update response and AFsessionWithQoS Create / update response messages. For example, the PCF may convey the PolicyAuthorization_Create / update response message to the NEF, and the NEF may convey the AFsessionWithQoS Create / update response message to the AF.

[0119] In step 7, the PCF in step 4 may determine a policy update based on the dynamic traffic characteristic change service information received from the AF and transmit the updated PCC rule based on the policy update to the SMF. The updated PCC rule may include at least one piece of information from among: dynamic traffic characteristic detection information for supporting traffic characteristic change detection operation within the data floor; QoS floor-related information to be transmitted to the RAN and / or UE, such as a Base QoS Profile, a Dynamic QoS profile, and a Data Burst Size; dynamic traffic characteristic change support indication for indicating a dynamic traffic characteristic change service support and a transmission operation of service-related information; information on whether to apply the changed traffic characteristic change information (dynamic QoS profile) for a certain period of time (dynamic traffic characteristic change timer); and dynamic traffic characteristic change occurrence information generation requirements.

[0120] The SMF may determine to transmit information to the UPF and RAN to support services that support temporary traffic characteristic changes based on the PCC rule information received from the PCF. The SMF may perform an N4 rule generation operation to request a traffic characteristic change detection operation within the service data floor in the UPF and an operation to generate information to transmit traffic characteristic change information to the RAN based on dynamic traffic characteristic change support indication information and dynamic traffic characteristic detection information. In addition, the SMF may determine an operation to transmit the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc. to the RAN. In addition, the SMF may determine to use RQI information to notify the RAN and UE of the occurrence of a dynamic traffic characteristic change based on reflective QoS support request information transmitted from the UE through the PDU session establishment or change operation process if the corresponding service data floor supports reflective QoS. To this end, the SMF may additionally include an operation to mark the RQI within the GTP-U HE when a traffic characteristic change occurs in the N4 rule.

[0121] In steps 8 and 9, the SMF may transmit to the UPF an SDF template that includes information on operations for detecting traffic characteristic changes in the service data floor and generating information for transmitting traffic characteristic change information to the RAN through the N4 session creation / modification process. After receiving an N4 rule from the SMF that includes requirements for detecting traffic characteristic changes in the service data floor and generating traffic characteristic change notification information, the UPF may perform monitoring operations for traffic transmitted in the corresponding service data floor. The data traffic monitoring operation may be performed based on dynamic traffic characteristic detection information transmitted from the AF. For example, if the AS explicitly notifies that the characteristics of a specific packet have changed, such as through a dynamic traffic characteristic change flag transmitted through an RTP HE field, information indicating that the traffic characteristic change can be detected through information in the header information within a specific header or protocol may be transmitted. Alternatively, if the AS cannot explicitly transmit packet characteristic change information through a specific header or header field within a protocol, relevant information for measuring implicit packet characteristic changes may be transmitted.

[0122] For example, by measuring the average data rate between packets or monitoring the interval between packets (based on frame rate) or the packet delivery pattern (based on GOP information), if there is a change between packets or in the pattern of packets, the UPF can recognize that the characteristics of the traffic received from the AS through the service data flow have changed. The UPF, which recognizes that the traffic characteristics have changed, can generate traffic characteristics change notification information to request that QoS profile information considering the changed traffic characteristics information be applied to the QoS floor. The traffic characteristics change notification information generated by the UPF can be directly transmitted to the RAN by marking the RQI in the GTP-U extension field.

[0123] In step 10, the PCF may transmit to the AMF, the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc., which are generated or updated based on the request information for the dynamic traffic characteristic change support service of the AF in step 4. The N1N2 message transmitted to the AMF may include N2 SM information including the Base QoS profile, Dynamic QoS profile, and Data Burst Size transmitted to the RAN, and an N1 SM container including the Base QoS profile, Dynamic QoS profile, and Data Burst Size information for supporting the dynamic traffic characteristic change support service of uplink traffic. The Base QoS profile, Dynamic QoS profile, and Data Burst Size information in the N2 SM information transmitted to the RAN and the Base QoS profile, Dynamic QoS profile, and Data Burst Size information in the N1 SM container transmitted to the UE may be the same or different depending on the settings of the service provider, etc.

[0124] In step 11, the AMF may transmit N2 SM information and N1 SM container including at least one of Base QoS profile, Dynamic QoS profile, and Data Burst Size information to the RAN through an N2 message to support dynamic traffic characteristic changes from the SMF.

[0125] In step 12, the RAN can transmit to the UE an N1 SM container including Base QoS profile, Dynamic QoS profile, and Data Burst Size information to support a service supporting dynamic traffic characteristic changes in uplink traffic to the UE.

[0126] From step 13 to step 14, the UE and RAN may forward response messages of the N2 message, etc. to the SMF. For example, the RAN may send an N2 message response message to the AMF, and the AMF may send an Nsmf_PDUSession_UpdateSMContext Request message to the SMF.

[0127] At step 15, SMF may send an Nsmf_PDUSession_UpdateSMContext Response message to AMF.

[0128] In step 16, the UPF, which recognizes that the traffic characteristic has changed, may generate traffic characteristic change notification information to request application of QoS profile information (Dynamic QoS profile) that takes into account the changed traffic characteristic information to the QoS floor. The traffic characteristic change notification information generated by the UPF may be directly transmitted to the RAN on the user plane or may be transmitted to the RAN through the SMF on the control plane. For example, the UPF may mark the traffic characteristic change notification information in the form of a Dynamic Traffic characteristic change indication (DCI) or a Dynamic Traffic characteristic change Flag in the GTP-U extension header and directly transmit it to the RAN on the user plane. Alternatively, the UPF may transmit the Dynamic Traffic characteristic change indication (DCI) to the SMF through an event reporting message generated by the UPF, and the SMF may transmit the traffic characteristic change notification information to the RAN through the AMF.

[0129] Afterwards, when notification information related to a traffic change event detected through the UPF is transmitted through the UPF or SMF, the RAN can process traffic within the corresponding QoS floor based on information such as the Dynamic QoS profile and Data Burst Size received from the SMF. If there is a requirement to support temporary traffic characteristic changes in uplink data, the SMF can transmit the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc. to the UE through the N1 SM Container. If the AS requests a traffic characteristic change for uplink data, the UPF or SMF can support the temporary traffic characteristic change transmitted by the UE by transmitting the traffic characteristic change notification information detected by the UPF to the UE through the RAN.

[0130] In step 17, the UE can perform an uplink traffic transmission operation with a Dynamic QoS profile applied based on the RQI information in the SDAP header to the RAN. It can be known that the RAN, which has received the RQI from the UPF through step 16, should simultaneously apply the Dynamic QoS profile to the uplink traffic transmitted from the UE while transmitting the RQI information to the UE. In addition, based on information such as the Burst Data size or the Dynamic Traffic characteristic change Timer transmitted through the SMF, the RAN and the UE can perform an operation to process the uplink traffic with the Dynamic QoS profile applied during a specified time (Burst Data size or Dynamic Traffic characteristic change Timer) transmitted through the SMF. If an additional RQI is transmitted within the Burst Data size or the Dynamic Traffic characteristic change Timer, the time of the Burst Data size or the Dynamic Traffic characteristic change Timer is extended, and the RAN and the UE can perform an operation to process the uplink traffic with the Dynamic QoS profile by additionally considering the extended time.

[0131] FIG. 5A is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a radio access network (RAN) to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure. FIG. 5B is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a RAN to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure. FIG. 5C is a diagram illustrating an example of a method for detecting a change in traffic characteristics within a service floor and transmitting the detected information to a RAN to support temporary traffic changes within the service floor, according to one embodiment of the present disclosure. For example, FIG. 5B may illustrate one or more operations subsequent to FIG. 5A. For example, FIG. 5C may illustrate one or more operations subsequent to FIG. 5B.

[0132] The UPF according to an embodiment of the present invention can utilize RQI (Reflective QoS Indicator) information as a means of transmitting dynamic traffic characteristic change information of a downlink. In this case, the AF can instruct the performance of a dynamic traffic characteristic change occurrence information generation operation to transmit dynamic traffic characteristic change occurrence information using RQI if the corresponding PDU Session and terminal support Reflective QoS within the requirements for generating dynamic traffic characteristic change occurrence information. In addition, if Reflective QoS can be applied, upon receiving RQI information, the RAN / UPF and UE can be configured to perform traffic transmission using a QoS flow to which a Dynamic QoS profile is applied based on the corresponding indicator information.

[0133] In step 1, the AF can determine a service request considering changes in traffic characteristics of the service floor currently being serviced at the discretion of the AS or the AF.

[0134] In step 2, the AF may transmit an AF session service operation create / update request message (AFsessionWithQoS Create / Update request) to the NEF, which includes an indicator requesting support for a dynamic traffic characteristic change service (Dynamic Traffic Characteristic Change Support Indication), traffic characteristic change detection information (Dynamic Traffic Characteristic Detection Information), traffic characteristic information (Dynamic Traffic Characteristic Requirement), and QoS requirements including a requirement for generating dynamic traffic characteristic change occurrence information. The traffic characteristic information (Dynamic Traffic Characteristic Requirement) transmitted from the AF may include traffic characteristic information (basic traffic characteristics and traffic characteristics to be changed) within the floor, which includes Maximum Data Burst Volume information and / or at least one of the Type, Resolution, Data rate, Frame rate, and Data Burst Size of the content. Dynamic traffic characteristic detection information transmitted from AF includes information on traffic characteristic changes in packets, such as dynamic traffic characteristic change indication, dynamic traffic characteristic change flag, start time of data burst, end of data burst, etc., which are explicitly transmitted through RTP HE fields, etc., and information implicitly transmitted that can measure location information or packet characteristic changes (e.g. average data rate between packets or data rate threshold of basic QoS profile (e.g.It can compare traffic changes between packets based on a threshold for base QoS profile, or can include at least one piece of information such as intervals between packets (based on frame rate), packet delivery patterns (based on GOP information), periodcity information, etc.

[0135] In step 3, service QoS requirement information including an indicator requesting support for dynamic traffic characteristic change service (Dynamic Traffic characteristic change support indication), traffic characteristic change detection information (Dynamic traffic characteristic detection information), and traffic characteristic information (Dynamic traffic characteristic requirement) can be authorized by NEF, and then transmitted to PCF via a PolicyAuthorization create / update request message.

[0136] In step 4, if the PCF determines to support the dynamic traffic characteristic change service based on the dynamic traffic characteristic change support indication, dynamic traffic characteristic detection information, dynamic traffic characteristic requirement, and dynamic traffic characteristic change occurrence information generation requirement received through the AF, it can update the PCC rules to support the service. In the updated PCC rules, in addition to the profile of the existing QoS floor (e.g., Base QoS profile), a QoS profile that considers the characteristics of the traffic to be temporarily changed (e.g., Dynamic QoS profile) can be additionally created to support temporary traffic characteristic changes, and the RAN can use the dynamic QoS profile to change the characteristics of the QoS floor being serviced only for a specific period of time (e.g., MDBV, Maximum Data Burst Volume). Depending on the settings of the service provider or network provider, the dynamic QoS profile may be applied within the same QoS floor, or a QoS floor with a separate dynamic QoS profile applied may be used. According to an embodiment of the present invention, when using a QoS floor to which a separate Dynamic QoS profile is applied, PCC rule information including QFI (QoS Flow Identifier) ​​information to which a Base QoS profile is applied and QFI to which a Dynamic QoS profile is applied can be generated.Additionally, the PCC rule may include information for supporting operations such as detecting changes in traffic characteristics within a data floor in UPF and generating traffic characteristic change notification information.

[0137] In steps 5 and 6, the PCF may convey to the AF whether it accepts or rejects the request for support of dynamic traffic characteristic change service requested by the AF via the PolicyAuthorization_Create / update response and AFsessionWithQoS Create / update response messages. For example, the PCF may convey the PolicyAuthorization_Create / update response message to the NEF, and the NEF may convey the AFsessionWithQoS Create / update response message to the AF.

[0138] In step 7, the PCF in step 4 may determine a policy update based on the dynamic traffic characteristic change service information received from the AF and transmit the updated PCC rule based on the policy update to the SMF. The updated PCC rule may include at least one of: dynamic traffic characteristic detection information for supporting a traffic characteristic change detection operation within the data floor; QoS floor-related information to be transmitted to the RAN and / or UE, such as a Base QoS Profile and / or Base QFI, a Dynamic QoS profile and / or Dynamic QFI, and a Data Burst Size; a dynamic traffic characteristic change support indication for indicating a dynamic traffic characteristic change service support and a transmission operation of service-related information; information on whether to apply the changed traffic characteristic change information (dynamic QoS profile) for a certain period of time (dynamic traffic characteristic change timer); and a dynamic traffic characteristic change occurrence information generation requirement.

[0139] The SMF may determine to transmit information to the UPF and RAN to support services that support temporary traffic characteristic changes based on the PCC rule information received from the PCF. The SMF may perform an N4 rule generation operation to request a traffic characteristic change detection operation within the service data floor in the UPF and an operation to generate information to transmit traffic characteristic change information to the RAN based on dynamic traffic characteristic change support indication information and dynamic traffic characteristic detection information. In addition, the SMF may determine an operation to transmit the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc. to the RAN. In addition, the SMF may determine to use RQI information to notify the RAN and UE of the occurrence of a dynamic traffic characteristic change based on reflective QoS support request information transmitted from the UE through the PDU session establishment or change operation process if the corresponding service data floor supports reflective QoS. To this end, the SMF may additionally include an operation to mark the RQI within the GTP-U HE when a traffic characteristic change occurs in the N4 rule. According to one embodiment of the present invention, a Dynamic QoS profile can be applied using a separate QoS floor according to the settings of a service provider or a network provider.When using a QoS floor (Dynamic QoS flow) with a Dynamic QoS profile applied separately from a QoS floor (Base QoS flow) with a Base QoS profile applied as described above, FAR (Forwarding Action Rule) information including QFI information with a Base QoS profile applied and QFI information with a Dynamic QoS profile applied may be included in the N4 rule. In addition, the FAR information may also include timer information (e.g., Dynamic traffic characteristic change timer) for maintaining the corresponding QoS floor.

[0140] In steps 8 and 9, the SMF may transmit to the UPF an SDF template that includes information on operations for detecting traffic characteristic changes in the service data floor and generating information for transmitting traffic characteristic change information to the RAN through the N4 session creation / modification process. After receiving an N4 rule from the SMF that includes requirements for detecting traffic characteristic changes in the service data floor and generating traffic characteristic change notification information, the UPF may perform monitoring operations for traffic transmitted in the corresponding service data floor. The data traffic monitoring operation may be performed based on dynamic traffic characteristic detection information transmitted from the AF. For example, if the AS explicitly notifies that the characteristics of a specific packet have changed, such as through a dynamic traffic characteristic change flag transmitted through an RTP HE field, information indicating that the traffic characteristic change can be detected through information in the header information within a specific header or protocol may be transmitted. Alternatively, if the AS cannot explicitly transmit packet characteristic change information through a specific header or header field within a protocol, relevant information for measuring implicit packet characteristic changes may be transmitted.

[0141] For example, by measuring the average data rate between packets or monitoring the interval between packets (based on frame rate) or the packet delivery pattern (based on GOP information), if there is a change in the interval between packets or the pattern of packets, the UPF can recognize that the characteristics of the traffic received from the AS through the service data flow have changed. The UPF, which recognizes that the traffic characteristics have changed, can generate traffic characteristic change notification information to request that QoS profile information considering the changed traffic characteristic information be applied to the corresponding QoS floor. The traffic characteristic change notification information generated by the UPF can be directly transmitted to the RAN by marking the RQI in the GTP-U extension field. According to one embodiment of the present invention, when a dynamic QoS profile is applied using a separate QoS floor according to the settings of a service provider or a network provider, if the UPF detects a traffic change based on the explicit or implicit information included in the N4 rule received from the SMF, the UPF can perform a forwarding operation to a separate QoS floor. In addition, if the above N4 rule includes timer information (e.g. Dynamic traffic characteristic change timer) for maintaining the changed QoS floor (e.g. Dynamic QoS flow), the UPF can perform the traffic characteristic change indicator (e.g. RQI) marking operation and forwarding operation to Dynamic QoS flow within the GTP-U extended header field only within the timer.

[0142] In step 10, the PCF may transmit to the AMF, the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc., which are generated or updated based on the request information for the dynamic traffic characteristic change support service of the AF in step 4. The N1N2 message transmitted to the AMF may include N2 SM information including the Base QoS profile, Dynamic QoS profile, and Data Burst Size transmitted to the RAN, and an N1 SM container including the Base QoS profile, Dynamic QoS profile, and Data Burst Size information for supporting the dynamic traffic characteristic change support service of uplink traffic. The Base QoS profile, Dynamic QoS profile, and Data Burst Size information in the N2 SM information transmitted to the RAN and the Base QoS profile, Dynamic QoS profile, and Data Burst Size information in the N1 SM container transmitted to the UE may be the same or different depending on the settings of the service provider, etc.

[0143] In step 11, the AMF may transmit N2 SM information and N1 SM container including at least one of Base QoS profile and / or Base QFI, Dynamic QoS profile and / or Dynamic QFI, and Data Burst Size information to the RAN via an N2 message to support dynamic traffic characteristic changes from the SMF.

[0144] In step 12, the RAN may transmit to the UE an N1 SM container including Base QoS profile and / or Base QFI, Dynamic QoS profile and / or Dynamic QFI, and Data Burst Size information to support a service supporting dynamic traffic characteristic change of uplink traffic to the UE.

[0145] From step 13 to step 14, the UE and RAN may forward response messages of the N2 message, etc. to the SMF. For example, the RAN may send an N2 message response message to the AMF, and the AMF may send an Nsmf_PDUSession_UpdateSMContext Request message to the SMF.

[0146] At step 15, SMF may send an Nsmf_PDUSession_UpdateSMContext Response message to AMF.

[0147] In step 16a, the UPF, which recognizes that the traffic characteristic has changed, may generate traffic characteristic change notification information to request that QoS profile information (Dynamic QoS profile) considering the changed traffic characteristic information be applied to the QoS floor. The traffic characteristic change notification information generated by the UPF may be directly transmitted to the RAN on the user plane or may be transmitted to the RAN through the SMF on the control plane. For example, the UPF may mark the traffic characteristic change notification information in the form of a Dynamic Traffic characteristic change indication (DCI) or a Dynamic Traffic characteristic change Flag in the GTP-U extension header and directly transmit it to the RAN on the user plane. Alternatively, the UPF may transmit the Dynamic Traffic characteristic change indication (DCI) to the SMF through an event reporting message generated by the UPF, and the SMF may transmit the traffic characteristic change notification information to the RAN through the AMF.

[0148] Afterwards, when notification information related to a traffic change event detected through the UPF is transmitted through the UPF or SMF, the RAN can process traffic within the corresponding QoS floor based on information such as the Dynamic QoS profile and Data Burst Size received from the SMF. If there is a requirement to support temporary traffic characteristic changes in uplink data, the SMF can transmit the Base QoS profile, Dynamic QoS profile, Data Burst Size, etc. to the UE through the N1 SM Container. If the AS requests a traffic characteristic change for uplink data, the UPF or SMF can support the temporary traffic characteristic change transmitted by the UE by transmitting the traffic characteristic change notification information detected by the UPF to the UE through the RAN.

[0149] In step 16b, if the UPF decides to support temporary traffic characteristic changes using a separate QoS floor according to the policy of the service provider or network operator, the changed traffic characteristics can be forwarded to the Dynamic QoS floor based on the FAR containing the Base QFI and Dynamic QFI information received through the N4 rule. If a separate Dynamic QoS floor is applied, in step 16a, the UPF can additionally mark the changed Dynamic QFI information in addition to the RQI marking operation in the GTP-U extension header and forward it to the RAN.

[0150] In step 17, the UE can perform an uplink traffic transmission operation applying a Dynamic QoS profile and / or Dynamic QFI based on the RQI information in the SDAP header to the RAN. It can be known that the RAN, which has received the RQI from the UPF through step 16, should perform application of the Dynamic QoS profile to the uplink traffic transmitted from the UE while transmitting the RQI information to the UE. If it is decided to support temporary traffic characteristic changes using a separate QoS floor according to the policy of the service provider or network operator, the UE, which has received the Dynamic QFI value and RQI from the UPF and RAN through the SDAP header, can determine uplink traffic transmission using the Dynamic QoS floor for the uplink traffic transmitted from the UE.

[0151] RAN / UPF and UE can perform processing operation of uplink traffic with applied Dynamic QoS profile during the designated time (Burst Data size or Dynamic Traffic characteristic change Timer) transmitted through SMF based on information such as Burst Data size or Dynamic Traffic characteristic change Timer transmitted through SMF. If additional RQI is transmitted within Burst Data size or Dynamic Traffic characteristic change Timer, the time of Burst Data size or Dynamic Traffic characteristic change Timer is extended, and RAN and UE can perform processing operation of uplink traffic with applied Dynamic QoS profile by additionally considering the extended time.

[0152] In step 18a, the UPF may perform a change in operation to support a change in traffic characteristic based on explicit or implicit information from the AS. For example, the UPF, upon detecting a change in traffic characteristic change indicator information including a Dynamic Traffic Characteristic Change Indication (DCI) or an Expedite Indication from the AS, may determine to change the traffic forwarding operation from the Dynamic QoS floor to the Base QoS floor. When detecting a change in traffic characteristic using explicit information, the UPF may determine the presence or absence of the corresponding traffic characteristic change indicator. Alternatively, the UPF may determine to change the traffic forwarding operation from the Dynamic QoS floor to the Base QoS floor based on a Dynamic Traffic Characteristic Change Timer received from the AF, etc.

[0153] In step 18b, the UPF that detects a change in the traffic characteristic change indicator information in step 18a may stop marking operation within the GTP-U extended header field of RQI information and Dynamic QFI information, and then perform a forwarding operation to the Base QoS floor.

[0154] In step 19, a UE that receives a packet from RAN that does not include separate RQI and Dynamic QFI information can perform processing of uplink traffic using the existing configured Base QoS floor.

[0155] FIG. 6 is a drawing showing an example of a configuration of a terminal according to one embodiment of the present disclosure.

[0156] A terminal according to one embodiment of the present disclosure may include a processor (620) that controls the overall operation of the terminal, a transceiver (600) including a transmitter and a receiver, and a memory (610). Of course, the terminal is not limited to the above example, and the terminal may include more or fewer components than those illustrated in FIG. 6.

[0157] According to one embodiment of the present disclosure, the transceiver (600) 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 (600) can receive signals via a wireless channel, output them to the processor (620), and transmit the signals output from the processor (620) via the wireless channel.

[0158] According to one embodiment of the present disclosure, the processor (620) can control the terminal to perform any one of the operations described above. Meanwhile, the processor (620), the memory (610), and the transceiver (600) 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 (620) and the transceiver (600) can be electrically connected. In addition, the processor (620) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0159] According to one embodiment of the present disclosure, the memory (610) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (610) provides the stored data upon request of the processor (620). The memory (610) 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 (610). In addition, the processor (620) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (610).

[0160] FIG. 7 is a diagram illustrating an example of a configuration of a base station or network entity according to one embodiment of the present disclosure.

[0161] A base station or network entity according to one embodiment of the present disclosure may include a processor (720) that controls the overall operation of the base station or network entity, a transceiver (700) including a transmitter and a receiver, and a memory (710). Of course, the present invention is not limited to the above example, and the base station or network entity may include more or fewer components than those illustrated in FIG. 7.

[0162] According to one embodiment of the present disclosure, the transceiver (700) 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.

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

[0164] According to one embodiment of the present disclosure, the memory (710) can store data such as basic programs, application programs, and setting information for the operation of a base station or network entity. In particular, the memory (710) provides the stored data upon request of the processor (720). The memory (710) 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 (710). In addition, the processor (720) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (710).

[0165] In one embodiment of the present disclosure, a Policy Control Function (PCF) entity in a wireless communication system may include a transceiver and at least one processor connected to the transceiver. In one embodiment of the present disclosure, the at least one processor may receive a request message associated with a traffic characteristic in a target service flow. In one embodiment of the present disclosure, the at least one processor may generate first Policy and Charging Control (PCC) rule information for a first traffic characteristic of the target service flow and second PCC rule information for a second traffic characteristic of the target service flow based on the request message. In one embodiment of the present disclosure, the at least one processor may transmit the first PCC rule information and the second PCC rule information to a Session Management Function (SMF) entity.

[0166] In one embodiment of the present disclosure, the request message may include a Quality of Service (QoS) requirement for a first traffic characteristic and a QoS requirement for a second traffic characteristic.

[0167] In one embodiment of the present disclosure, at least one processor may generate first PCC rule information based on QoS requirements for a first traffic characteristic. In one embodiment of the present disclosure, at least one processor may generate second PCC rule information based on QoS requirements for a second traffic characteristic.

[0168] In one embodiment of the present disclosure, the first PCC rule information may be used to generate the first N4 rule information for the first traffic characteristic. In one embodiment of the present disclosure, the second PCC rule information may be used to generate the second N4 rule information for the second traffic characteristic.

[0169] In one embodiment of the present disclosure, the request message may include information about traffic characteristic detection.

[0170] In one embodiment of the present disclosure, information for traffic characteristic detection may include information indicating that traffic characteristic information is included in a Real-time Transport Protocol (RTP) Header Extension (HE) in a target service flow.

[0171] In one embodiment of the present disclosure, a rule associated with a second traffic characteristic may include information indicating a Reflective QoS indication (RQI) marking of a User Plane Function (UPF) entity.

[0172] In one embodiment of the present disclosure, a Session Management Function (SMF) entity in a wireless communication system may include a transceiver and at least one processor connected to the transceiver. In one embodiment of the present disclosure, the at least one processor may receive first Policy and Charging Control (PCC) rule information for a first traffic characteristic of a target service flow and second PCC rule information for a second traffic characteristic of the target service flow from a Policy Control Function (PCF) entity. In one embodiment of the present disclosure, the at least one processor may generate first N4 rule information for the first traffic characteristic and second N4 rule information for the second traffic characteristic based on the first PCC rule information and the second PCC rule information. In one embodiment of the present disclosure, the at least one processor may transmit the first N4 rule information and the second N4 rule information to a User Plane Function (UPF) entity.

[0173] In one embodiment of the present disclosure, the first PCC rule information and the second PCC rule information may be generated by the PCF entity based on a request message associated with traffic characteristics in a target service flow received by the PCF entity.

[0174] In one embodiment of the present disclosure, the request message may include a Quality of Service (QoS) requirement for a first traffic characteristic and a QoS requirement for a second traffic characteristic. In one embodiment of the present disclosure, the first PCC rule information may be generated based on the QoS requirement for the first traffic characteristic. In one embodiment of the present disclosure, the second PCC rule information may be generated based on the QoS requirement for the second traffic characteristic.

[0175] In one embodiment of the present disclosure, the request message may include information about traffic characteristic detection indicating that traffic characteristic information is included in a Real-time Transport Protocol (RTP) Header Extension (HE) in the target service flow.

[0176] In one embodiment of the present disclosure, a UPF entity can detect traffic characteristics of packets in an RTP HE in a target service flow based on information about traffic characteristic detection.

[0177] In one embodiment of the present disclosure, a rule associated with a second traffic characteristic may include information indicating a Reflective QoS indication (RQI) marking of a UPF entity.

[0178] FIG. 8 is a diagram illustrating an example of a method performed by a network entity in one embodiment of the present disclosure.

[0179] Referring to FIG. 8, the method (800) includes, but is not limited to, steps 810 to 830. For example, the method (800) may further include other steps. For example, the method (800) may omit at least some of steps 810 to 830. In one embodiment of the present disclosure, the network entity performing the method (800) may be, but is not limited to, a PCF.

[0180] In step 810, the network entity may receive a request message associated with a traffic characteristic in the target service flow. In one embodiment of the present disclosure, the request message may include a QoS requirement for a first traffic characteristic and a QoS requirement for a second traffic characteristic. In one embodiment of the present disclosure, the request message may include information regarding traffic characteristic detection. In one embodiment of the present disclosure, the information regarding traffic characteristic detection may include information indicating that traffic characteristic information is included in a Real-time Transport Protocol (RTP) Header Extension (HE) in the target service flow.

[0181] In step 820, the network entity may generate first PCC rule information for the first traffic characteristic of the target service flow and second PCC rule information for the second traffic characteristic of the target service flow based on the request message. In one embodiment of the present disclosure, the network entity may generate the first PCC rule information based on QoS requirements for the first traffic characteristic. In one embodiment of the present disclosure, the network entity may generate the second PCC rule information based on QoS requirements for the second traffic characteristic.

[0182] At step 830, the network entity may transmit the first PCC rule information and the second PCC rule information to the SMF entity. In one embodiment of the present disclosure, the first PCC rule information may be used to generate the first N4 rule information for the first traffic characteristic. In one embodiment of the present disclosure, the second PCC rule information may be used to generate the second N4 rule information for the second traffic characteristic.

[0183] In one embodiment of the present disclosure, a rule associated with a second traffic characteristic may include information indicating a Reflective QoS indication (RQI) marking of a UPF entity.

[0184] FIG. 9 is a diagram illustrating an example of a method performed by a network entity in one embodiment of the present disclosure.

[0185] Referring to FIG. 9, the method (900) includes, but is not limited to, steps 910 to 930. For example, the method (900) may further include other steps. For example, the method (900) may omit at least some of steps 910 to 930. In one embodiment of the present disclosure, the network entity performing the method (900) may be, but is not limited to, an SMF.

[0186] In step 910, the network entity may receive first PCC rule information for a first traffic characteristic of a target service flow and second PCC rule information for a second traffic characteristic of the target service flow from the PCF entity. In one embodiment of the present disclosure, the first PCC rule information and the second PCC rule information may be generated by the PCF entity based on a request message associated with the traffic characteristic in the target service flow received by the PCF entity. In one embodiment of the present disclosure, the request message may include a QoS requirement for the first traffic characteristic and a QoS requirement for the second traffic characteristic. In one embodiment of the present disclosure, the first PCC rule information may be generated based on the QoS requirement for the first traffic characteristic. In one embodiment of the present disclosure, the second PCC rule information may be generated based on the QoS requirement for the second traffic characteristic. In one embodiment of the present disclosure, the request message may include information about traffic characteristic detection indicating that traffic characteristic information is included in the RTP HE in the target service flow.

[0187] At step 920, the network entity can generate first N4 rule information for the first traffic characteristic and second N4 rule information for the second traffic characteristic based on the first PCC rule information and the second PCC rule information.

[0188] In step 930, the network entity may transmit the first N4 rule information and the second N4 rule information to the UPF entity. In one embodiment of the present disclosure, the UPF entity may detect the traffic characteristics of packets in the RTP HE in the target service flow based on the information regarding the traffic characteristic detection.

[0189] In one embodiment of the present disclosure, a rule associated with a second traffic characteristic may include information indicating a Reflective QoS indication (RQI) marking of a UPF entity.

[0190] According to one embodiment of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system may include the steps of receiving, from an application function (AF) entity, a service support indicator for temporarily changing traffic characteristics and information for detecting a change in traffic characteristics and traffic characteristic information, a step of generating a base QoS profile to be applied to a basic service flow and a dynamic QoS profile to be applied in consideration of a traffic characteristic to be temporarily changed in order to support a change in traffic characteristics in a service flow based on the information, and a step of transmitting the base QoS profile and the dynamic QoS profile and information for detecting a change in traffic characteristics to a session management function (SMF).

[0191] According to one embodiment of the present disclosure, a method performed by a session management function (SMF) entity in a wireless communication system may include a step of receiving a PCC rule including related information for supporting a service supporting a temporary change in traffic characteristics from a policy control function (PCF) entity, a step of transmitting N4 rule information to a UPF including an operation of generating a Packet Detection Rule (PDR) based on information for detecting a change in traffic characteristics and generating information for transmitting the detected traffic characteristic change information to a RAN, and a step of transmitting base QoS profile information and Dynamic QoS profile information to the RAN.

[0192] According to one embodiment of the present disclosure, a method performed by a user plane function (UPF) entity in a wireless communication system may include a step of receiving N4 rule information from an SMF, including an operation of generating a Packet Detection Rule (PDR) based on information for detecting a change in traffic characteristics and generating information for transmitting the detected traffic characteristic change information to a RAN, a step of detecting a traffic characteristic based on a Packet Detection Rule (PDR) based on information for detecting a change in traffic characteristics, a step of generating information for transmitting the detected traffic characteristic change information to a RAN, and a step of transmitting the detected traffic characteristic change information to the RAN.

[0193] In one embodiment of the present disclosure, a method performed by a user plane function (UPF) entity in a wireless communication system may include the steps of: obtaining information associated with detection of a change in traffic characteristics; monitoring data traffic based on the information associated with detection of the change in traffic characteristics; and transmitting traffic characteristic change notification information to a base station based on identifying that the traffic characteristics have changed.

[0194] In one embodiment of the present disclosure, a device and method for effectively providing services in a wireless communication system may be provided. The technical challenges addressed by the present disclosure are not limited to the technical challenges mentioned above, and other technical challenges not mentioned herein will be readily apparent to those skilled in the art.

[0195] In one embodiment of the present disclosure, a device and method for effectively providing services in a mobile communication system may be provided. The technical effects of one embodiment of the present disclosure are not limited to those described in the present disclosure, and other effects not described in the present disclosure will be readily apparent to those skilled in the art from the detailed description of the present disclosure.

[0196] 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 operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made without detracting 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.

[0197] 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).

[0198] The various components and modules of the entity, base station or terminal device described in the present disclosure 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.

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

[0200] 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 the embodiments described in the claims or specification of the present disclosure.

[0201] These programs (software modules, software) may be stored in a random access memory, a non-volatile memory including a flash memory, a read only memory (ROM), an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc ROM (CD-ROM), a digital versatile disc (DVD) or other forms of optical storage, a magnetic cassette, or a memory formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0202] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide LAN (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.

[0203] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, 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 the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0204] 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 a PCF (Policy Control Function) entity in a wireless communication system, A step of receiving a request message associated with traffic characteristics in a target service flow; A step of generating first PCC (Policy and Charging Control) rule information for the first traffic characteristic of the target service flow and second PCC rule information for the second traffic characteristic of the target service flow based on the request message; and A method comprising the step of transmitting the first PCC rule information and the second PCC rule information to a SMF (Session Management Function) entity.

2. In paragraph 1, A method wherein the request message includes a QoS (Quality of Service) requirement for the first traffic characteristic and a QoS requirement for the second traffic characteristic.

3. In paragraph 2, The above generating steps are: A step of generating the first PCC rule information based on the QoS requirements for the first traffic characteristic; and A method comprising the step of generating the second PCC rule information based on the QoS requirements for the second traffic characteristics.

4. In paragraph 1, The above first PCC rule information is used to generate the first N4 rule information for the first traffic characteristic, A method wherein the second PCC rule information is used to generate second N4 rule information for the second traffic characteristic.

5. In paragraph 1, A method wherein the above request message includes information for detecting traffic characteristics.

6. In paragraph 5, A method in which the information for detecting the above traffic characteristics includes information indicating that traffic characteristic information is included in the RTP (Real-time Transport Protocol) HE (Header Extension) in the target service flow.

7. In paragraph 1, A method wherein the rule associated with the second traffic characteristic includes information indicating RQI (Reflective QoS indication) marking of a UPF (User Plane Function) entity.

8. In a method performed by an SMF (Session Management Function) entity in a wireless communication system, A step of receiving first PCC (Policy and Charging Control) rule information for a first traffic characteristic of a target service flow and second PCC rule information for a second traffic characteristic of the target service flow from a PCF (Policy Control Function) entity; A step of generating first N4 rule information for the first traffic characteristic and second N4 rule information for the second traffic characteristic based on the first PCC rule information and the second PCC rule information; and A method comprising the step of transmitting the first N4 rule information and the second N4 rule information to a UPF (User Plane Function) entity.

9. In paragraph 8, A method wherein the first PCC rule information and the second PCC rule information are generated by the PCF entity based on a request message associated with traffic characteristics in the target service flow received by the PCF entity.

10. In paragraph 9, The request message includes a QoS (Quality of Service) requirement for the first traffic characteristic and a QoS requirement for the second traffic characteristic, The above first PCC rule information is generated based on the QoS requirements for the first traffic characteristic, A method in which the second PCC rule information is generated based on QoS requirements for the second traffic characteristics.

11. In paragraph 9, A method wherein the request message includes information for traffic characteristic detection indicating that traffic characteristic information is included in the RTP (Real-time Transport Protocol) HE (Header Extension) in the target service flow.

12. In paragraph 11, A method in which the UPF entity detects traffic characteristics of packets in RTP HE in the target service flow based on information about the detection of the traffic characteristics.

13. In paragraph 8, A method wherein the rule associated with the second traffic characteristic includes information indicating RQI (Reflective QoS indication) marking of the UPF entity.

14. In the PCF (Policy Control Function) entity in a wireless communication system, Transmitter and receiver; and At least one processor connected to the transceiver, At least one processor, Receive a request message associated with traffic characteristics in the target service flow, Based on the above request message, first PCC (Policy and Charging Control) rule information for the first traffic characteristic of the target service flow and second PCC rule information for the second traffic characteristic of the target service flow are generated, A PCF entity that transmits the first PCC rule information and the second PCC rule information to a SMF (Session Management Function) entity.

15. In the SMF (Session Management Function) entity in a wireless communication system, Transmitter and receiver; and At least one processor connected to the transceiver, At least one processor, Receive first PCC (Policy and Charging Control) rule information for the first traffic characteristic of the target service flow and second PCC rule information for the second traffic characteristic of the target service flow from a PCF (Policy Control Function) entity, Generate first N4 rule information for the first traffic characteristic and second N4 rule for the second traffic characteristic based on the first PCC rule information and the second PCC rule information, An SMF entity that transmits the first N4 rule information and the second N4 rule information to a UPF (User Plane Function) entity.

Images