Method and apparatus for processing multiplexed service data flow

Abstract

Provided are a method and apparatus by which a session management function (SMF) entity: receives information about whether or not a filter for processing a multiplexed service data flow of a UE is supported; transmits, to a policy control function (PCF), the received information about whether or not the filter for processing the multiplexed service data flow is supported; receives, from the PCF, a policy and charging control (PCC) rule generated on the basis of whether or not the filter for processing the multiplexed service data flow is supported; and provides the UE with a quality of service (QoS) rule based on the PCC rule.

Description

Method and device for processing multiplexed service data flows

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for managing traffic based on multiplexed service data flows 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 satisfy 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] The disclosed embodiment is intended to provide a device and method capable of effectively providing a service in a wireless communication system.

[0009] A method according to one embodiment of the present disclosure is characterized by including the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0010] The disclosed embodiment provides a device and method capable of effectively providing a service in a wireless communication system.

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

[0012] FIG. 2 illustrates an example of a traffic detection method considering traffic-specific characteristics and a QoS flow mapping method considering service characteristics of the traffic according to one embodiment of the present disclosure.

[0013] FIG. 3 illustrates an example of generating uplink packet filter information of a terminal in an SMF and transmitting the generated packet filter information to a UPF and a terminal depending on whether the terminal supports additional packets according to one embodiment of the present disclosure.

[0014] FIG. 4 illustrates an example of generating uplink packet filter and downlink packet filter information of a terminal in an SMF according to whether the terminal supports additional packet packets and whether the terminal supports Reflective QoS, and transmitting the generated packet filter information to the terminal and UPF according to one embodiment of the present disclosure.

[0015] FIG. 5 illustrates components of a user equipment (UE) in a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 6 illustrates components of a network entity in a wireless communication system according to one embodiment of the present disclosure.

[0017] According to one embodiment of the present disclosure, a method performed by a session management function (SMF) entity may include: receiving information on whether a terminal supports a filter for processing a multiplexed service data flow; transmitting information on whether the terminal supports a filter for processing the received multiplexed service data flow to a policy control function (PCF); receiving, from the PCF, a policy and charging control (PCC) rule generated based on whether the terminal supports a filter for processing the multiplexed service data flow; and providing, to the terminal, a quality of service (QoS) rule based on the PCC rule.

[0018] If the terminal supports a filter for processing multiplexed service data flows, the QoS rule may include information for identifying traffic within the flow of multiplexed service data.

[0019] Information for identifying the above traffic may include at least one of payload type information, media identification information, and SSRC (synchronization source) information.

[0020] If the terminal supports the identification function of multiplexed service data flows, the PCC rule may include QoS parameters for each traffic flow within the multiplexed service data flow.

[0021] The step of transmitting information about whether the terminal supports the identification function of the multiplexed service data flow to the PCF may be transmitting an Npcf_SMPolicyControl_Create message or an Npcf_SMPolicyControl_update message that includes information about whether the terminal supports the identification function of the multiplexed service data flow.

[0022] Information on whether the terminal supports the identification function of the multiplexed service data flow may be provided from the terminal in a PDU (protocol data unit) session establishment procedure.

[0023] The above method may further include a step of transmitting a QoS profile based on the PCC rule to a user plane function (UPF) entity.

[0024] According to one embodiment of the present disclosure, a method performed by a policy control function (PCF) entity may include: receiving information from a session management function (SMF) regarding whether a filter for processing multiplexed service data flows of a terminal is supported; generating a policy and charging control (PCC) rule based on the information regarding whether a filter for processing multiplexed service data flows of the terminal is supported; and transmitting the generated PCC rule to the SMF.

[0025] If the terminal supports the identification function of multiplexed service data flows, the PCC rule may include QoS parameters for each traffic flow within the multiplexed service data flow.

[0026] The step of receiving information on whether the terminal supports a filter for processing multiplexed service data flows from the above SMF may be receiving an Npcf_SMPolicyControl_Create message or an Npcf_SMPolicyControl_update message including information on whether the terminal supports an identification function of multiplexed service data flows.

[0027] According to one embodiment of the present disclosure, a session management function (SMF) entity comprises: at least one processor; and at least one memory communicatively coupled to the at least one processor and storing instructions,

[0028] The above commands can be executed individually or in any combination by the at least one processor so that the SMF: receives information on whether the terminal supports a filter for processing a multiplexed service data flow, transmits information on whether the terminal supports a filter for processing the received multiplexed service data flow to a policy control function (PCF), receives from the PCF a policy and charging control (PCC) rule generated based on whether the terminal supports a filter for processing the multiplexed service data flow, and provides the terminal with a quality of service (QoS) rule based on the PCC rule.

[0029] If the terminal supports a filter for processing multiplexed service data flows, the QoS rule may include information for identifying traffic within the flow of multiplexed service data.

[0030] Information for identifying the above traffic may include at least one of payload type information, media identification information, and SSRC (synchronization source) information.

[0031] If the terminal supports the identification function of multiplexed service data flows, the PCC rule may include QoS parameters for each traffic flow within the multiplexed service data flow.

[0032] According to one embodiment of the present disclosure, a policy control function (PCF) entity comprises: at least one processor; and at least one memory communicatively coupled to the at least one processor and storing instructions, wherein the instructions are individually or in any combination executed by the at least one processor, such that the PCF: receives information from a session management function (SMF) as to whether a filter for processing a multiplexed service data flow of a terminal is supported, generates a policy and charging control (PCC) rule based on the information as to whether the filter for processing the multiplexed service data flow of the terminal is supported, and transmits the generated PCC rule to the SMF.

[0033] 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:

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

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

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

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

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

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

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

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

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

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

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

[0045] For metaverse and XR (eXtended Reality) 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.

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

[0047] In one embodiment of the present disclosure, when data traffic within a multiplexed service flow transmitted from an application server or a terminal is scheduled in the RAN according to the characteristics of the traffic based on network conditions and requests, the AF provides information on requirements related to the characteristics of the data traffic within the multiplexed service flow on the control plane, thereby supporting quality of service (QoS) processing according to the characteristics of each data traffic. In addition, by including related information in the RTP (Real-time Transport Protocol) header to support processing of data traffic and QoS processing according to the characteristics of the data traffic, information on the time point and related information when the data characteristics within the multiplexed service flow change during real-time data transmission of the multiplexed service flow can be provided, and a method for accurate processing when data is processed in the UPF can be proposed.

[0048] According to one embodiment of the present disclosure, when a QoS processing method for each traffic characteristic is changed considering traffic characteristics (media type, SSRC, etc.) in a multiplexed service flow due to congestion occurring in a network, etc., the SMF can notify the AF (application function) through the PCF (policy control function) that the QoS processing method of the corresponding session has changed based on event notification information from the RAN (radio access network) to the SMF (session management function) according to the QoS processing method (e.g., Alternative QoS profile). In addition, at the same time, the UPF can receive information on updated Packet Detection Rule (PDR), Forwarding Action Rule (FAR), and QoS Enforcement Rule (QER) through the PCC (policy and charging control) rule, or perform an N4 update operation based on information in the previously transmitted PCC rule.

[0049] In addition, AF / AS can notify UPF of changes in characteristics within a service flow based on the changed QoS processing method through information on the control plane or in-band signaling to recognize information such as the timing of traffic changes considering the QoS processing method. This allows UPF to provide efficient services depending on the network situation by transmitting information for processing PDU units with the same characteristics considering the characteristics of the application layer. In addition, if AF / AS does not provide separate in-band signaling due to operator policy, etc., it can notify PCF (policy control function) of changes in traffic characteristics and related information through AF, thereby informing UPF of packet detection rules considering traffic changes.

[0050] 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, from a terminal, an indicator indicating whether an uplink packet filter in the terminal supports an additional packet filter for distinguishing multiplexed packets (additional Packet Filter support indication or Application level packet filter support indication); receiving, from a PCF, PCC rule information including a multiplexing support request indicator and multiplexed packet characteristic information; generating downlink and uplink packet filter information based on the PCC rule information including the multiplexing support request indicator and the multiplexed packet characteristic information and information on whether additional packet filter is supported (additional Packet Filter support indication or Application level packet filter support indication) from the PCF; transmitting, to a UPF via an N4 rule, a PDR including the downlink packet filter information; and transmitting, to a UE via an AMF and a RAN, a QoS rule including the uplink packet filter information. Additionally, when an SMF receives indication information indicating whether a terminal supports Reflective QoS during a PDU session establishment procedure from a terminal, the SMF may forward an N4 rule including additional UPF operations to the UPF, including an indication for mapping packets within a multiplexed service data flow to a separate QoS flow by considering the characteristics of each packet within the downlink packet filter information and information on QoS flows mapped to packets within the multiplexed service data flow.

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

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

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

[0054] Each NF in a 5G system can support the following functions. Of course, the examples below are not limited, and each NF may support additional functions beyond those described below.

[0055] According to one embodiment of the present disclosure, the AUSF can process and store data for authentication of the UE.

[0056] According to one embodiment of the present disclosure, the 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, the AMF can support signaling between Core Network (CN) nodes for mobility between 3GPP access networks, termination of a 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.

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

[0058] According to one embodiment of the present disclosure, a DN may mean, for example, an operator service, an Internet connection, or a third-party service. The DN may transmit a downlink protocol data unit (PDU) to the UPF, or receive a PDU transmitted from a UE from the UPF.

[0059] According to one embodiment of the present disclosure, the PCF may provide a function to determine policies such as mobility management and session management by receiving information about packet flows from an application server. Specifically, the PCF may 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 determination within a User Data Repository (UDR).

[0060] According to one embodiment of the present disclosure, 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 toward 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). In addition, the SMF can 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 the session, and roaming functions. Some or all of the features of an SMF may be supported within a single instance of an SMF.

[0061] According to one embodiment of the present disclosure, the UDM stores user subscription data, policy data, etc. The UDM may include two parts: an application front end (FE) and a user data repository (UDR).

[0062] According to one embodiment of the present disclosure, the FE may include a UDM FE responsible for location management, subscription management, credential processing, etc., and a PCF responsible for policy control. The UDR may store data required for 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.

[0063] According to one embodiment of the present disclosure, the UPF may forward downlink PDUs received from a DN to a UE via an (R)AN, and forward uplink PDUs received from the UE via the (R)AN to the DN. Specifically, the UPF may support an anchor point for intra / inter RAT mobility, an external PDU session point of 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 a 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.

[0064] According to one embodiment of the present disclosure, the AF can interact with the 3GPP core network to provide services (e.g., support functions such as application impact on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control).

[0065] According to one embodiment of the present disclosure, (R)AN may collectively refer to a new radio access network that supports both evolved E-UTRA, which is an evolved version of 4G radio access technology, and new radio (NR) technology (e.g., gNB).

[0066] According to one embodiment of the present disclosure, the gNB can support functions for radio resource management (e.g., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UE in uplink / downlink (i.e., scheduling), internet protocol (IP) header compression, encryption and integrity protection of user data streams, selection of AMF upon attachment of UE when routing to AMF is not determined from information provided to UE, routing of user plane data to UPF(s), routing of control plane information to AMF, connection setup and termination. 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.

[0067] According to one embodiment of the present disclosure, a UE may refer to a user equipment. A user equipment may be referred to by terms such as a 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.

[0068] According to one embodiment of the present disclosure, a NEF may provide a means for securely exposing 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 the 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 utilized for other purposes, such as analysis.

[0069] According to one embodiment of the present disclosure, the EASDF may be an NF that can add an ECS (EDNS Client Subnet) option, which can be expressed as the address of a DNS server to which a DNS (Domain Name System) request of a terminal will be forwarded, and an IP subnet address to be added when forwarding the DNS request of the terminal, for each FQDN (Fully Qualified Domain Name). The EASDF can receive EAS domain configuration information from the EDR and, based on the received information, process a DNS request message received from the terminal.

[0070] 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, 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 the DNS message and processed statistical information to the SMF according to the DNS message reporting rules. The NRF may support a service discovery function. The NRF may receive an NF discovery request from an NF instance and provide information on a discovered NF instance to the NF instance. In addition, the NRF may maintain available NF instances and the services they support.

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

[0072] According to one embodiment of the present disclosure, a UE can access two (i.e., local and central) data networks simultaneously using multiple PDU sessions. In this case, 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.

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

[0074] 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. Of course, the following examples are not limited to this example.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] - N14: Reference point between two AMFs

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

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

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

[0092] FIG. 2 illustrates an example of traffic detection considering traffic-specific characteristics and QoS flow mapping support considering service characteristics of the traffic according to one embodiment of the present disclosure.

[0093] Referring to FIG. 2, related information for supporting mapping of QoS flows considering traffic characteristics within multiplexed service data flows on the control plane through a 5G system may be transmitted. Specifically, requirement information for detecting packets considering traffic characteristics within multiplexed service data flows on the control plane of the 5G system from the AF and information related to generating QoS flows for QoS processing considering traffic characteristics may be transmitted. In addition, the terminal may transmit to the 5G system whether or not to support an additional packet filter capable of processing the multiplexed service data flow when requesting PDU session establishment or modification. The terminal may transmit information on whether or not to support an additional packet filter to the 5G system through an additional packet filter support indication or an application level packet filter support indication.

[0094] According to one embodiment of the present disclosure, in a 5G system, a QoS flow within a PDU session may be the smallest unit that can express a QoS difference. For example, a 5G QoS characteristic may be determined by a 5QI (QoS identifier). The AF may transmit service requirement information (e.g., QoS parameter information) for processing a multiplexed service data flow composed of four different media types to the PCF. For example, the AF may transmit four pieces of service requirement information considering service characteristics for each of the four media types within individual QoS parameters. The service requirement information (e.g., QoS parameter information) for processing the multiplexed service data flow may be transmitted as included in the Protocol description or as separate service requirement information. The Protocol description transmitted from the AF may include relevant information (e.g., protocol type, SSRC, etc.) for distinguishing packets transmitted from the AS in the UPF. Additionally, AF can transmit to PCF together the service requirement information considering the media characteristics of each packet and the mapping information of related information for distinguishing / detecting the corresponding media characteristic packet. Based on the mapping information of the service requirement (QoS requirement) information considering the media characteristics of each packet and the related information for distinguishing / detecting the corresponding media characteristic packet, a packet filter that additionally considers related information (e.g., protocol type, SSRC, etc.) for distinguishing packets within the same 5-Tuple service data flow considering the media characteristics can be created in SMF in the existing 5-Tuple-based packet filter.

[0095] As described above, in order to process packets within a multiplexed service data flow according to the characteristics of each packet in a 5G system according to the policy or requirements of the service provider, the 5G system may request transmission of the multiplexed service data flow through one or more QoS flows. To this end, the AF may transmit to the PCF through an AFsessionWithQoS Create / Update request message at least one of the following information: a multiplexed traffic flows handling indication, service requirements for handling multiplexed traffic flows with different QoS requirements (e.g., mapping table between media type and QoS Flow) related to packets in the multiplexed service data flow, packet classification information in the multiplexed service data flow, and service requirements for creating a single QoS flow by considering the characteristics of the multiplexed service data flow in case the terminal does not support an additional packet filter.

[0096] According to one embodiment of the present disclosure, the AFsessionwithQoS message may include service requirements for each QoS flow (e.g., Guaranteed Flow Bit Rate, Packet Delay Budget, Packet Error Rate, etc.) and the type of media mapped to the corresponding QoS flow in the protocol description and transmit them. In addition, the AFsessionwithQoS message transmitted to the PCF may include characteristic information of the PDU packet, such as the protocol description.

[0097] According to one embodiment of the present disclosure, the PCF receives, as relevant information for processing multiplexed service data flows, service requirements for each QoS flow (e.g., Guaranteed Flow Bit Rate, Packet Delay Budget, Packet Error Rate, etc.) and media classification information mapped to the corresponding QoS flow, transmitted from the AF, and based on this, can generate QoS profiles for processing the multiplexed service data flows in consideration of policies of network operators and service providers.

[0098] According to one embodiment of the present disclosure, the PCF may additionally receive service requirement information for processing multiplexed service flows, such as a multiplexed traffic flows handling indication, from the AF. The PCF may generate a PCC rule including QoS-related information for processing multiplexed service flows based on at least one of the following service requirement information: multiplexed traffic flows handling indication, service requirements for each QoS flow (e.g., Guaranteed Flow Bit Rate, Packet Delay Budget, Packet Error Rate, etc.), and one or more characteristics mapped to the corresponding QoS flow, information on packets, information for detecting the corresponding packets (e.g., media type, SSRC, Payload type, RTP-M field, etc.), and service requirement information for generating a single QoS flow by considering the characteristics of the multiplexed service data flow in case the terminal does not support an additional packet filter (Service Requirements for multiplexed traffic flows).

[0099] In addition, based on the information on whether the terminal supports additional packet filters received from the SMF, such as the additional packet filter support indication or the application-level packet filter support indication, the PCF can generate one or more uplink QFIs so that the terminal can generate QoS flows that take different media characteristics into account based on the information in the protocol description (e.g., payload type, SSRC, etc.). That is, based on the information on whether the terminal supports the application-level packet filter received from the terminal and the information for distinguishing application-level packets received from the AF, the PCF can determine the mapping operation and the generation of operation-related information for multiplexed packets with different media characteristics into a QoS flow that suits the media characteristics of each packet. In addition, the PCF can instruct the generation of a packet filter that additionally supports application-level distinction information by using application-level packet filter information (e.g., SSRC, payload type, media type, etc.) in addition to the existing IP 5-tuple-based packet filter information, or can transfer related information to the SMF. If the terminal does not support additional packet filters, the PCF may generate downlink 5QI(s) consisting of one or more QFIs and uplink-related 5QI(s) consisting of one QFI considering the characteristics of one multiplexed service flow.

[0100] PCF can determine uplink-related QoS information (5QI) based on the network operator's configuration information or receive service requirements of a separate multiplexed service data flow transmitted from AF to determine a single QFI considering the characteristics of the multiplexed service flow.

[0101] An SMF that receives a PCC rule including information for processing a multiplexed service flow from a PCF as an individual QoS flow can generate a QoS profile and QoS rule for each QoS flow to forward the multiplexed service flow to an appropriate QoS flow by considering individual media characteristics.

[0102] An SMF that receives a PCC rule including information for processing a multiplexed service flow from a PCF as an individual QoS flow can create or update an N4 rule including a packet detection rule using an application-level filter in addition to the existing 5-tuple-based packet detection rule to map the multiplexed service flow to an appropriate QoS flow considering individual media characteristics. The packet detection rule using an application-level filter can be delivered to the SMF from the AF through the PCF via a protocol description, and the SMF can include a packet detection rule including classification information considering the media characteristics of the multiplexed packets (e.g., Media type or payload type, SSRC, RTP-M field, etc.) in the N4 rule and deliver it to the UPF. An N4 rule may include at least one rule among a Packet Detection Rule (PDR) including an application-level filter including media type or SSRC (synchronization source) information for detecting packets in a multiplexed service data flow, a Protocol description including information for mapping detected packets in a multiplexed service data flow based on a PDU set to one or more media types per QoS flow according to the service requirements of an AF or a Forwarding Action Rule (FAR) including Mapping information between a separate QFI and a Media type, and a QoS Enforcement Rule (QER) including information for indicating a PDU set information marking operation in a GTU-HE.

[0103] If the terminal transmits information on whether the terminal supports additional packet filters and whether it supports Reflective QoS to the SMF and PCF during the PDU session establishment procedure, the SMF can include information for performing the marking operation of the Reflective QoS indicator in the QER (QoS Enforcement Rule).

[0104] If the terminal does not support additional packet filters but supports Reflective QoS, the SMF may include information in the QER to perform the marking operation of the Reflective QoS indicator on one or more QoS flows, and additionally provide information to support the marking operation of the Reflective QoS indicator. For example, if packets with video or audio characteristics are multiplexed and transmitted as a single service data flow, the PCF may determine the mapping of each packet to two QoS flows based on the service requirements for processing the multiplexed service data flow of the AF.

[0105] At this time, if the terminal is a legacy terminal that does not support additional packet filters that utilize application-level information and supports Reflective QoS, the terminal must process uplink data using a single QoS flow. However, considering the characteristics of Reflective QoS, it can create two uplink QoS flows by following the settings of the downlink QoS flow. In this case, problems may occur because the terminal does not have the function to distinguish and map multiplexed packets to each QoS flow using an additional packet filter.

[0106] Therefore, SMF does not support additional packet filtering that utilizes application-level information for the terminal, but if the terminal supports Reflective QoS, it can transmit marking support information of the Reflective QoS indicator to the UPF, RAN, and UE to support selection of one QoS flow. The marking support information of the Reflective QoS indicator can include priority QFI information (Priority QFI info for UL), etc. Alternatively, SMF can include the marking support information of the Reflective QoS indicator in the QER to instruct the UPF to perform an operation of marking RQI (Reflective QoS indicator) information only for priority QoS flows when marking the Reflective QoS indicator.

[0107] FIG. 3 illustrates an example of generating uplink packet filter information of a terminal in an SMF according to whether the terminal supports additional packet packets, and transmitting the generated packet filter information to a UPF and the terminal, according to an embodiment of the present disclosure. Referring to FIG. 3, a process is illustrated in which traffic is detected by considering characteristics (e.g., media type) of each traffic within a multiplexed service flow, and the detected traffic is mapped to a QoS flow by considering the service characteristics of the traffic. Referring to FIG. 3, a downlink packet filter and an uplink packet filter can be separately generated depending on whether the terminal supports additional packet packets.

[0108] In step 300a, AF can determine a service request considering the media characteristics of the multiplexed service flow according to the service provider's policy, etc.

[0109] In step 300b, the AF may transmit an AF session service operation create / update request (AFsessionWithQoS Create / Update request) message to the NEF, which includes a multiplexed traffic flows handling indication, service requirement information related to packets in the multiplexed service data flow (Service Requirements for handling multiplexed traffic flows with different QoS requirements (e.g., mapping table between media type and QoS Flow)), packet classification information in the multiplexed service data flow, and service requirement information for creating a single QoS flow (Service Requirements for multiplexed traffic flows) considering the characteristics of the multiplexed service data flow in a case where the terminal does not support an additional packet filter, in order to process packets in the 5G system through one or more QoS flows considering the characteristics of each packet.

[0110] In step 300c, in order to process packets in a multiplexed service data flow through one or more QoS flows in a 5G system by considering the characteristics of each packet, service QoS requirement information including a multiplexed traffic flows handling indication of a multiplexed service data flow or traffic flow, service requirement information related to packets in a multiplexed service data flow (Service Requirements for handling multiplexed traffic flows with different QoS requirements (e.g., mapping table between media type and QoS Flow)), packet classification information in a multiplexed service data flow, and service requirement information for creating a single QoS flow by considering the characteristics of a multiplexed service data flow in a case where the terminal does not support an additional packet filter, may be authorized by the NEF, and may then be transmitted to the PCF through a PolicyAuthorization create / update request message.

[0111] In steps 300c and 300d, the PCF may convey to the AF whether to accept or reject the request for QoS support considering the media characteristics of the multiplexed service data flow 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.

[0112] In step 301, the terminal may include in a message a request for establishing or modifying a PDU session whether it supports additional packet filters capable of processing multiplexed service data flows and transmit this information to the AMF. Information on whether it supports additional packet filters may include an additional packet filter support indication or an application level packet filter support indication.

[0113] If the terminal is a legacy terminal with a basic packet filter that supports 5-tuple-based packet detection and does not support additional packet filters, information on whether the terminal supports additional packet filters at the application level (e.g., additional Packet Filter support indication or Application level packet filter support indication) may not be included in the message when requesting PDU session establishment or modification.

[0114] In step 302, the AMF may forward an Nsmf_PDUSession_CreateSMContext Request message to the SMF, which may include an additional packet filter support indication or an application level packet filter support indication. Through this, the SMF may determine whether the terminal supports additional packet filters capable of processing multiplexed service data flows.

[0115] In step 303, the SMF may forward an Npcf_SMPolicyControl_Create / Update request message to the PCF, including an additional Packet Filter support indication or an Application level packet filter support indication.

[0116] In step 304, the PCF may determine to create or update a policy based on service information for QoS support considering the media characteristics of the multiplexed service data flow received from the AF, and may transmit the created or updated PCC rule based on the policy to the SMF. The created or updated PCC rule may include at least one of related 5QI for QoS support considering the characteristics of the multiplexed service data flow and the capability of the terminal, a protocol description providing packet classification information at the application level, and / or QoS mapping information of packets by media type or SSRC (e.g., mapping information between media type and Qos Flow).

[0117] In step 304a, the PCF can determine whether the terminal supports additional packet filters based on the additional packet filter support indication or application level packet filter support indication information received from the SMF.

[0118] In step 304b, the PCF may perform a generation or update operation of a PCC rule based on the service requirements received from the AF if the terminal supports an additional packet filter for detection and processing of multiplexed service data based on the information received from the SMF in step 304a. The service requirements received from the AF may include at least one piece of information among multiplexed traffic flows handling indication, service requirements for each QoS flow (e.g., Guaranteed Flow Bit Rate, Packet Delay Budget, Packet Error Rate, etc.), and one or more characteristics mapped to the corresponding QoS flow, information for detecting the corresponding packet (e.g., media type, SSRC, Payload type, RTP-M field, etc.), and service requirement information for generating a single QoS flow by considering the characteristics of the multiplexed service data flow if the terminal does not support an additional packet filter (Service Requirements for multiplexed traffic flows). PCF can generate PCC rules including one or more 5QIs to process multiplexed service flows based on service requirements received from AF and additional packet filter support information of the terminal.

[0119] In step 304c, if the PCF determines that the terminal does not support an additional packet filter for detection and processing of multiplexed service data based on the information received from the SMF in step 304a, the PCF may generate a PCC rule including related information for mapping multiplexed packets with different characteristics for processing downlink data to one or more QoS flows (e.g., multiple 5QI considering the service characteristics of each flow / packet or multiplexed traffic flows with different QoS for DL) and related information for mapping multiplexed packets with different characteristics for processing uplink data to a single QoS flow (e.g., Single 5QI considering the service characteristics of multiplexed flow / packet or multiplexed traffic flows with single QoS for UL) based on the service requirements received from the AF.

[0120] PCF can receive service requirement information related to multiplexing service data flow from AF through steps 300a to 300c. AF can support the creation of packet filters for downlink and uplink data processing by transmitting to PCF together information for packet detection and generation of separate QoS flows considering packet characteristics, such as multiplexed traffic flows handling indication, service requirement information related to packets in multiplexed service data flows (Service Requirements for handling multiplexed traffic flows with different QoS requirements (e.g., mapping table between media type and QoS Flow)), packet classification information in multiplexed service data flows, and service requirement information for multiplexed traffic flows for generation of a single QoS flow considering the characteristics of multiplexed service data flows when a terminal that supports a conventional 5-tuple-based packet filter does not support an additional packet filter. Service requirement information related to multiplexing service data flow can be included in the protocol description and delivered to PCF or included separately in the AF session QoS related requirements (AFsessionWithQoS) message.

[0121] In step 305, the PCF may transmit to the SMF, via the Npcf_SMPolicyControl_Create / Npcf_SMPolicyControl_Update message, PCC rules (updated PCC rules for supporting multiplexed traffic flows with different QoS) including QoS information (e.g., 5QI) that takes into account the media characteristics of the multiplexed service data flow generated based on the service requirements related to the multiplexed service data flow received from the AF and the information on whether the terminal supports additional packet filters received from the terminal.

[0122] Based on the PCC rule information received from the PCF, the SMF can decide to transmit QoS profile, QoS rule, and packet filter information for processing downlink and uplink data to the UPF and RAN / UE for QoS support considering the media characteristics of the multiplexed service data flow. Based on the information for distinguishing packets within the multiplexed service data flow based on application-level information such as media type or SSRC when mapping the QoS flow of the multiplexed service flow and the related information for mapping the distinguished packets to appropriate QoS flows (e.g., mapping information between media type and QoS Flow), the SMF can perform an N4 rule generation operation to request a packet detection operation within the multiplexed service flow in the UPF and an operation for mapping detected packets by media type or SSRC to QoS flows.

[0123] Additionally, the SMF may generate uplink packet filter information to determine whether to transmit uplink data to the RAN through one QoS flow of multiplexed service data flows or through one or more QoS flows of multiplexed service data flows, depending on whether the terminal supports additional packet filters, and transmit QoS flow-related information (e.g., QoS profile and its related QoS id, QoS rule) to the RAN and / or UE.

[0124] In steps 306 and 307, the SMF may transmit to the UPF an SDF template containing downlink data packet filter information, such as information about packet detection operations within multiplexed service flows through the N4 session creation / modification process, and operations for mapping detected packets to QoS flows by media type or SSRC.

[0125] The UPF may receive an N4 rule from an SMF that includes requirements for packet detection by media type or media characteristic of traffic within a multiplexed service data flow, and then perform a detection operation on traffic transmitted in the multiplexed service data flow. The detection operation on traffic within the multiplexed service data flow may be performed based on media type information within the protocol description transmitted from the AF, or SSRC information and payload type or RTP-M field information within the header of the packet. In addition, a QoS flow mapping operation on packets detected may be performed based on QoS flow mapping information by media type information or SSRC information and payload type information within the protocol description transmitted from the AF, and QoS-related information (QoS flow ID (QFI)).

[0126] In step 308, the SMF may forward to the AMF, the N2 SM information including the QoS profile, QFI(s) information, and / or the N1 SM container including the Qos rule, which the PCF generated or updated in step 305 based on the QoS support service request information considering the media characteristics of the multiplexed service data flow of the AF. The N1N2 message forwarded to the AMF may forward QFI information for the uplink and downlink to the RAN, respectively, depending on whether the terminal supports additional packet filters. If the terminal supports additional packet filters at the application level according to the media characteristics of the multiplexed packets in step 301, the SMF may include one or more QFI information for the downlink and uplink. However, if the terminal does not support additional packet filters at the application level according to the media characteristics of the multiplexed packets in step 301, the downlink may include one or more QFI information, and the uplink data may forward the QoS profile and QFI information configured to be mapped to one QFI to the RAN through the N2 SM information. SMF can transmit to RAN together with N1 SM container including packet filter information (one or more QoS profiles and QFI) of uplink traffic depending on whether the terminal in the above N1N2 message supports additional packet filters.

[0127] In step 309, the AMF may transmit N2 SM information and N1 SM container including one or more QoS profiles and QFI information for uplink and downlink depending on whether the terminal supports additional packet filters and QoS support services considering the media characteristics of the multiplexed service data flow received from the SMF to the RAN through an N2 message.

[0128] In step 310, the RAN may transmit to the UE an N1 SM container including one or more QoS profiles and QFI information related to uplink data depending on whether the UE supports additional packet filters and a QoS support service considering the media characteristics of the multiplexed service data flow.

[0129] From step 311 to step 312, the UE and the 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. In step 313, the SMF may send an Nsmf_PDUSession_UpdateSMContext Response message to the AMF.

[0130] In step 314, based on the PDR, FAR and / or QER information within the N4 rule received through step 306, the UPF may perform an operation of detecting packets within the multiplexed service data flow and forwarding the detected packets to appropriate QoS flows based on media characteristics or media types.

[0131] In step 315, the terminal may receive one or more QoS profiles and QFI information related to appropriate uplink data through a QoS rule in step 310, depending on whether the terminal supports additional packet filters, and then perform an operation of forwarding the uplink data to an appropriate QoS flow based on the uplink packet filter information.

[0132] According to one embodiment of the present disclosure, some of the steps in FIG. 3 may be omitted or replaced, and the order of the steps in FIG. 3 may also be changed and performed. Furthermore, the description of each step is described without regard to the order for convenience of explanation.

[0133] FIG. 4 illustrates an example of generating uplink packet filter and downlink packet filter information of a terminal in an SMF according to whether the terminal supports additional packet packets and whether the terminal supports Reflective QoS, and transmitting the generated packet filter information to the terminal and UPF according to one embodiment of the present disclosure.

[0134] Referring to FIG. 4, the process of detecting traffic transmitted from AS based on packet classification information at the application level by considering traffic characteristics (e.g. media type, Payload type, SSRC, RTP-M field, etc.) within a multiplexed service flow in UPF and mapping the detected traffic to an appropriate QoS flow considering the service characteristics of the packet or traffic is illustrated. Referring to FIG. 4, the SMF can separately generate a downlink packet filter and an uplink packet filter depending on whether the terminal supports additional packet packets at the application level and whether it supports Reflective QoS.

[0135] In step 400a, AF can determine a service request considering the media characteristics of the multiplexed service flow according to the service provider's policy, etc.

[0136] In step 400b, the AF may transmit an AF session service operation create / update request (AFsessionWithQoS Create / Update request) message to the NEF, which includes a multiplexed traffic flows handling indication, service requirement information related to packets in the multiplexed service data flow (Service Requirements for handling multiplexed traffic flows with different QoS requirements (e.g., mapping table between media type and QoS Flow)), packet classification information in the multiplexed service data flow, and service requirement information for creating a single QoS flow considering the characteristics of the multiplexed service data flow in case the terminal does not support an additional packet filter.

[0137] In step 400c, in order to process packets in a multiplexed service data flow through one or more QoS flows in a 5G system by considering the characteristics of each packet, service QoS requirement information including a multiplexed traffic flows handling indication of a multiplexed service data flow or traffic flow, service requirement information related to packets in a multiplexed service data flow (Service Requirements for handling multiplexed traffic flows with different QoS requirements (e.g., mapping table between media type and QoS Flow)), packet classification information in a multiplexed service data flow, and service requirement information for creating a single QoS flow by considering the characteristics of a multiplexed service data flow in a case where the terminal does not support an additional packet filter, may be authorized by the NEF, and may then be transmitted to the PCF through a PolicyAuthorization create / update request message.

[0138] In steps 400c and 400d, the PCF may convey to the AF whether to accept or reject the request for QoS support considering the media characteristics of the multiplexed service data flow requested by the AF via the PolicyAuthorization_Create / update response and AFsessionWithQoS Create / update response messages. For example, the PCF may convey to the NEF the PolicyAuthorization_Create / update response message, and the NEF may convey to the AF the AFsessionWithQoS Create / update response message.

[0139] At step 400e, NEF may forward an AFsessionWithQoS Create response message to AF.

[0140] In step 401, the terminal may transmit to the AMF, in a message when requesting establishment or modification of a PDU session, whether or not the terminal supports additional packet filters capable of processing multiplexed service data flows and whether or not the terminal supports Reflective QoS. Information on whether or not the terminal supports additional packet filters may include an additional packet filter support indication or an application level packet filter support indication. If the terminal is a legacy terminal with a basic packet filter that supports 5-tuple based packet detection and does not support additional packet filters, information on whether or not the terminal supports additional packet filters that utilizes application level information (e.g., additional Packet Filter support indication or Application level packet filter support indication) may not be included in the message when requesting establishment or modification of a PDU session.

[0141] In step 402, the AMF may transmit to the SMF an Nsmf_PDUSession_CreateSMContext Request message, including information on whether the terminal supports additional packet filters capable of processing multiplexed service data flows, such as an additional packet filter support indication or an application level packet filter support indication, based on application level information received from the terminal, and information on whether the terminal supports Reflective QoS.

[0142] Through this, the SMF can determine whether the terminal supports additional packet filters to process multiplexed service data flows. In addition, when the SMF receives information on whether the terminal supports Reflective QoS, it can know that it transmits packets for uplink and downlink data using the same QoS information, and there is no need to transmit packet filter information for separate downlink data processing. In addition, when the SMF receives information on whether the terminal supports Reflective QoS, it can additionally include a request for an action to mark RQI information in the GTP-U extended header field when generating an N4 rule to be transmitted to the UPF to support Reflective QoS.

[0143] In step 403, the SMF may forward an Npcf_SMPolicyControl_Create / Update request message to the PCF, which includes additional packet filter support information, such as an additional packet filter support indication or an application level packet filter support indication, and UE support of reflective QoS.

[0144] In step 404, the PCF may determine to create or update a policy based on service information for QoS support considering the media characteristics of the multiplexed service data flow received from the AF, and may transmit the created or updated PCC rule based on the policy to the SMF. The created or updated PCC rule may include at least one of related QoS information (5QI) for QoS support considering the characteristics of the multiplexed service data flow and the capability of the terminal, and / or QoS mapping information of packets by media type or SSRC (e.g., mapping information between media type and Qos Flow), and protocol description including packet classification information at the application level.

[0145] In addition, the PCF can generate or update PCC rule information including information for performing Reflective QoS operation (Reflective QoS Control) and Priority QoS information (5QI) within the SDF based on information on whether additional packet filters are supported and whether Reflective QoS is supported by the terminal. The PCF supports Reflective QoS of the terminal and, if it does not support additional packet filters, can determine whether to allow a packet processing service request considering media characteristics of the multiplexed service data flow of the AF.

[0146] If the Reflective QoS service of a terminal is set as a priority service over the packet processing service that considers the media characteristics of the multiplexed service data flow according to the policy of the network operator or the policy of the service provider, the PCF may decide to service the packet filter of uplink and downlink data through a single QoS flow in order to support the Reflective QoS service. If the PCF decides to simultaneously service the Reflective QoS service and the packet processing service that considers the media characteristics of the multiplexed service data flow, the PCF may additionally include information for performing the Reflective QoS operation on a terminal that supports Reflective QoS but does not support an additional packet filter (Reflective QoS Control) and Priority QoS information (5QI) or information for performing the RQI operation on only a single QoS flow.

[0147] Based on the additional packet filter support indication or application level packet filter support indication information received from the SMF in step 404a and the reflective QoS support information of the terminal, it is possible to determine whether the terminal supports additional packet filters and whether the terminal supports reflective QoS services.

[0148] In step 404b, the PCF may perform a generation or update operation of a PCC rule based on the service requirements received from the AF if the terminal supports an additional packet filter for detection and processing of multiplexed service data based on the information received from the SMF in step 404a. The service requirements received from the AF may include at least one piece of information among multiplexed traffic flows handling indication, service requirements for each QoS flow (e.g., Guaranteed Flow Bit Rate, Packet Delay Budget, Packet Error Rate, etc.), and one or more characteristics mapped to the corresponding QoS flow, information for detecting the corresponding packet (e.g., media type, SSRC, Payload type, RTP-M field, etc.), and service requirement information for generating a single QoS flow by considering the characteristics of the multiplexed service data flow if the terminal does not support an additional packet filter (Service Requirements for multiplexed traffic flows).

[0149] The PCF can generate a PCC rule including one or more QoS information (5QI) for processing multiplexed service flows based on the service requirements received from the AF and the additional packet filter support information of the terminal. Additionally, the PCC rule can include information related to the operation of marking RQI information in the GTP-U extended header field based on the reflective QoS support information of the terminal.

[0150] In step 404c, if the PCF determines that the terminal does not support an additional packet filter for detection and processing of multiplexed service data based on the information received from the SMF in step 304a, the PCF may generate a PCC rule including related information for mapping multiplexed packets with different characteristics for processing downlink data to one or more QoS flows (e.g., multiple 5QI considering the service characteristics of each flow / packet or multiplexed traffic flows with different QoS for DL) and related information for mapping multiplexed packets with different characteristics for processing uplink data to a single QoS flow (e.g., Single 5QI considering the service characteristics of multiplexed flow / packet or multiplexed traffic flows with single QoS for UL) based on the service requirements received from the AF.

[0151] PCF can receive service requirement information related to multiplexing service data flow from AF through steps 400a to 400c. AF can support the creation of packet filters for downlink and uplink data processing by transmitting to PCF together information for packet detection and generation of separate QoS flows considering packet characteristics, such as multiplexed traffic flows handling indication, service requirement information related to packets in multiplexed service data flows (Service Requirements for handling multiplexed traffic flows with different QoS requirements (e.g., mapping table between media type and QoS Flow)), packet classification information in multiplexed service data flows, and service requirement information for multiplexed traffic flows for generation of a single QoS flow considering the characteristics of multiplexed service data flows in case the terminal does not support an additional packet filter at the application level that only supports the existing 5-tuple-based packet filter.

[0152] Service requirement information related to multiplexing service data flows can be transmitted as included in the protocol description or separately included in the AF session QoS related requirement (AFsessionWithQoS) message and transmitted to PCF. If PCF decides to simultaneously provide a Reflective QoS service and a packet processing service that considers media characteristics of multiplexed service data flows, it can additionally include information for performing Reflective QoS operation on a terminal that supports Reflective QoS but does not support an additional packet filter (Reflective QoS Control), Priority QFI information, or information for performing RQI operation on only one QoS flow.

[0153] For example, when audio and video packets are transmitted as a single multiplexed service data flow, PCF can determine service support through each different QoS flow considering the service characteristics of audio and video by utilizing additional packet filter information in UPF for downlink data. However, if the terminal is a legacy terminal that cannot utilize additional packet filter information, PCF can perform RQI marking operation only on the QoS flow transmitting video packets, or additionally include separate information (Priority 5QI information for multiple reflective QoS flows) indicating that the QoS flow transmitting video packets is a priority QoS flow in the PCC rule and transmit it to SMF.

[0154] In step 405, the PCF may transmit to the SMF, through the Npcf_SMPolicyControl_Create / Npcf_SMPolicyControl_Update message, PCC rules (updated PCC rules for supporting multiplexed traffic flows with different QoS) that include QoS information that takes into account the media characteristics of the multiplexed service data flow generated based on the service requirements related to the multiplexed service data flow received from the AF, information on whether the terminal supports additional packet filters received from the terminal, and information on whether Reflective QoS is supported.

[0155] The SMF can generate packet filter information and QoS profiles and Qos rules for processing downlink and uplink data to support QoS considering the media characteristics of multiplexed service data flows based on the PCC rule information received from the PCF, and can transfer the QoS-related information and packet filter information generated in the SMF to the UPF and RAN / UE. The SMF can perform packet detection using an application-level packet filter in the multiplexed service flow in the UPF based on information for distinguishing packets in the multiplexed service data flow based on information such as media type or SSRC when mapping QoS flows of the multiplexed service flows, and related information for mapping the distinguished packets to appropriate QoS flows (e.g. mapping information between media type and Qos Flow), an operation for mapping detected packets to QoS flows based on application-level information (by media type or SSRC), and an operation for generating N4 rules for requesting RQI marking.

[0156] In addition, the SMF may generate uplink packet filter information to determine whether to transmit uplink data from multiplexed service data flows to the RAN as a single QoS flow or to transmit uplink data from multiplexed service data flows to the RAN as one or more QoS flows, depending on whether the terminal supports additional packet filters, and may decide to transmit QoS flow-related information (e.g., QoS profile and its related QoS id, QoS rule) to the RAN. If the terminal cannot utilize additional packet filter information but supports a Reflective QoS service, the SMF may generate priority QoS flow (Priority QFI) information based on information preset in the SMF and determine to transmit it to the RAN and UE when performing an RQI marking operation on one or more QoS flows to support the Reflective QoS service. Alternatively, if priority QoS information (Priority 5QI) is received through the PCC rule, the related information (Priority QFI and indication of RQI marking only for Priority QFI) can be transmitted to the UPF to perform RQI marking operation only on priority QoS flows when generating QER.

[0157] In steps 406 and 407, the SMF may transmit to the UPF an SDF template including downlink data packet filter information, such as packet detection operation based on application-level packet filter of packets in multiplexed service flows through N4 session creation / modification process, operation of mapping detected packets to QoS flows considering each media characteristic based on application-level media classification information (e.g. by media type or by SSRC), and information on RQI marking operation. The UPF may receive from the SMF an N4 rule including requirements for packet detection by media type or by media characteristic of traffic in the multiplexed service data flow, and then perform detection operation on traffic transmitted in the multiplexed service data flow.

[0158] The detection operation of traffic within a multiplexed service data flow can be performed based on one or more application-level packet classification information, such as media type information, SSRC information, payload type, or RTP-M field, transmitted through a protocol description transmitted from an AF. In addition, a QoS flow mapping operation of the detected packets can be performed based on mapping information to an appropriate QoS flow that takes into account the detected packets and the media characteristics of the packets through application-level packet classification information (media type information, SSRC information, and payload type) within the protocol description transmitted from an AF.

[0159] A UPF that has not received information about a separate RQI marking operation from the SMF can perform the RQI marking operation on the GTP-U HE of one or more QoS flows. If the UPF receives information from the SMF to perform the RQI marking operation only on the priority QoS flow or is requested to perform the RQI marking operation only on one QoS flow, the UPF can perform the RQI marking operation only on the GTP-U HE of the corresponding QoS flow.

[0160] In step 408, the SMF may forward to the AMF, the N2 SM information including the QoS profile, QFI(s) information, and / or the N1 SM container including the QoS rule, based on the QoS support service request information considering the media characteristics of the multiplexed service data flow of the AF generated or updated by the PCF in step 405. The N1N2 message forwarded to the AMF may forward to the RAN QFI information and additional QoS-related information (Priority QFI information) for the uplink depending on whether the terminal supports an additional packet filter and whether it supports Reflective QoS. If the terminal supports an additional packet filter in step 401, the SMF may not include QFI information for a separate downlink. However, if the terminal does not support an additional packet filter in step 401 but supports Reflective QoS, the downlink may include one or more QFI information, and the uplink-related Priority QFI information, which is configured to be mapped to one QFI, may be forwarded to the RAN through the N2 SM information.

[0161] The SMF may forward the N1 SM container including the Priority QFI information related to the packet filter of the uplink traffic to the RAN depending on whether the terminal in the N1N2 message supports an additional packet filter. If the terminal does not support the additional packet filter but supports Reflective QoS, the UPF may decide to mark the RQI on the GTP-U HE of one QoS flow or mark the RQI on the GTP-U HE of one or more QoS flows based on the decision of the PCF or SMF. In this case, the SMF may provide the RAN with decision information for allocating resources for appropriate uplink data transmission by forwarding the Priority QFI information to the RAN.

[0162] In step 409, the AMF may transmit to the RAN, via an N2 message, N2 SM information and N1 SM container including one or more QoS profiles and QFI information and Priority QFI information for downlink depending on whether the terminal supports additional packet filters and whether the terminal supports Reflective QoS, considering the media characteristics of the multiplexed service data flow received from the SMF.

[0163] In step 410, the RAN may transmit to the UE an N1 SM container including QFI-related information such as one or more QoS profiles and Priority QFI information related to uplink data depending on whether the terminal supports additional packet filters and Reflective QoS, and QoS-supported services considering media characteristics of multiplexed service data flows.

[0164] From step 411 to step 412, the UE and the RAN may forward the response message of the N2 message, etc. to the SMF. For example, the RAN may send the N2 message response message to the AMF, and the AMF may send the Nsmf_PDUSession_UpdateSMContext Request message to the SMF. In step 413, the SMF may send the Nsmf_PDUSession_UpdateSMContext Response message to the AMF.

[0165] In step 414, based on the PDR, FAR and / or QER information in the N4 rule received through step 406, the UPF may perform an operation of detecting packets in the multiplexed service data flow and forwarding the detected packets to appropriate QoS flows based on media characteristics or media types. In addition, the UPF may perform a separate RQI marking operation (RQI marking only on one QoS flow) or an RQI marking operation (RQI marking on all QoS flows) depending on whether the terminal supports an additional packet filter in order to support a Reflective QoS service.

[0166] In step 415a, if RQI information is marked and transmitted for only one QoS flow, the terminal may generate uplink packet filter information for generating and mapping QoS flow-related information for transmitting uplink data based on the information of the corresponding QoS flow. Thereafter, the terminal may perform an operation of forwarding the multiplexed uplink data to the selected QoS flow based on the uplink packet filter information.

[0167] In step 415b, if RQI information is marked and transmitted to one or more QoS flows, the terminal can select one QoS flow based on the Priority QFI information transmitted through the QoS rule. The terminal can generate uplink packet filter information including an operation for generating information related to one or more QoS flows based on information of a downlink QoS flow composed of one or more QoS flows and an operation for mapping to a specific QoS flow based on the Priority QFI information. Thereafter, the terminal can perform an operation for forwarding multiplexed uplink data to the selected QoS flow based on the uplink packet filter information.

[0168] According to one embodiment of the present disclosure, some of the steps in FIG. 4 may be omitted or replaced, and the order of the steps in FIG. 4 may also be changed and performed. Furthermore, the description of each step is described without regard to the order for convenience of explanation.

[0169] 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: receiving terminal-related function information (Additional packet filter support indicator and / or Reflective QoS support indicator); receiving information associated with a multiplexed service data flow; detecting and mapping packets transmitted in the multiplexed service data flow to QoS flows based on a PCC rule including the information associated with the received multiplexed service data flow; and generating an N4 rule requesting an RQI marking operation.

[0170] 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 the steps of: receiving, from a terminal, an indicator indicating whether an uplink packet filter in the terminal supports an additional packet filter for distinguishing multiplexed packets (additional Packet Filter support indication or Application level packet filter support indication); receiving, from a PCF, PCC rule information including a multiplexing support request indicator and multiplexed packet characteristic information; generating, from the PCF, downlink and uplink packet filter information based on the PCC rule information including the multiplexing support request indicator and the multiplexed packet characteristic information and information on whether additional packet filter is supported (additional Packet Filter support indication or Application level packet filter support indication); transmitting, to a UPF via an N4 rule, a PDR including the downlink packet filter information; and transmitting, to a UE via an AMF and a RAN, a QoS rule including the uplink packet filter information. Additionally, when an SMF receives indication information indicating whether a terminal supports Reflective QoS during a PDU session establishment procedure from a terminal, the SMF may forward an N4 rule including additional UPF operations to the UPF, including an indication for mapping packets within a multiplexed service data flow to a separate QoS flow by considering the characteristics of each packet within the downlink packet filter information and information on QoS flows mapped to packets within the multiplexed service data flow.

[0171] FIG. 5 illustrates components of a user equipment (UE) in a wireless communication system according to one embodiment of the present disclosure.

[0172] Referring to FIG. 5, a terminal according to one embodiment may include a transceiver (500), a memory (510), and a processor (520). The transceiver (500), memory (510), and processor (520) of the UE may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited thereto. For example, the terminal may include more or fewer components than those described above. In addition, the processor (520), transceiver (500), and memory (510) may be implemented as a single chip. In addition, the processor (520) may include at least one processor.

[0173] The transceiver (500) collectively refers to the UE receiver and the UE transmitter, and can transmit and receive signals with a base station or network entity. The signals transmitted and received with the base station or network entity may include control information and data. The transceiver (500) may include an RF transmitter for up-converting and amplifying the frequency of a transmission signal, and an RF receiver for low-noise amplification and down-converting the frequency of a reception signal. However, this is merely an example of the transceiver (500), and the components of the transceiver (500) are not limited to the RF transmitter and RF receiver.

[0174] In addition, the transceiver (500) can receive a signal through a wireless channel, output it to the processor (520), and transmit the signal output from the processor (520) through the wireless channel. The memory (510) can store programs and data necessary for the operation of the UE. In addition, the memory (510) can store control information or data included in a signal acquired by the UE. The memory (510) can be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0175] The processor (520) can control a series of processes to enable the terminal to operate. For example, the transceiver (500) can receive a data signal including a control signal transmitted by a base station or a network entity, and the processor (520) can determine the result of receiving the control signal and data signal transmitted by the base station or the network entity.

[0176] FIG. 6 illustrates components of a network entity in a wireless communication system according to one embodiment of the present disclosure.

[0177] Referring to FIG. 6, the configuration of a core network object in a wireless communication system can be illustrated. The configuration illustrated in FIG. 6 can be understood as a configuration of a device having at least one function among the network entities (e.g., AMF, UPF, SMF, PCF, NEF, NEF, RAN) described in FIG. 1, FIG. 2, FIG. 3, and / or FIG. 4. Terms such as "... unit" and "... device" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.

[0178] Referring to FIG. 6, a network entity may be configured to include a transceiver (600), a memory (610), and a processor (620).

[0179] The transceiver (600) may provide an interface for communicating with other devices within the network. That is, the transceiver (600) may convert a bit string transmitted from a network entity to another device into a physical signal, and may convert a physical signal received from another device into a bit string. That is, the transceiver (600) may transmit and receive signals. Accordingly, the transceiver (600) may be referred to as a modem, a transmitter, a receiver, or a transceiver. In this case, the transceiver (600) may enable the network entity to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via the network.

[0180] The memory (610) can store data such as basic programs, application programs, and configuration information for the operation of the network entity. The memory (610) can be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the memory (610) can provide stored data upon request from the processor (620).

[0181] The processor (620) can control the overall operations of the network entity. For example, the processor (620) can transmit and receive signals through the transceiver (600). Additionally, the processor (620) can write and read data to and from the memory (610). For this purpose, the processor (620) can include at least one processor. According to various embodiments of the present disclosure, the processor (620) can control synchronization using a wireless communication network. For example, the processor (620) can control the network entity to perform operations according to various embodiments.

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

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

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

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

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

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

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

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

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

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

[0192] 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. In the method of performing SMF (session management function) entity, A step of receiving information on whether the terminal supports a filter for processing multiplexed service data flow; A step of transmitting information on whether a filter for processing the received multiplexed service data flow is supported to a PCF (policy control function); A step of receiving a policy and charging control (PCC) rule generated based on whether the PCF supports a filter for processing the multiplexed service data flow; and A method comprising the step of providing a terminal with a quality of service (QoS) rule based on the PCC rule.

2. In paragraph 1, A method wherein, if the terminal supports a filter for processing multiplexed service data flows, the QoS rule includes information for identifying traffic within the flow of multiplexed service data.

3. In paragraph 2, A method in which information for identifying the above traffic includes at least one of payload type information, media identification information, and SSRC (synchronization source) information.

4. In paragraph 1, A method wherein, if the terminal supports the identification function of a multiplexed service data flow, the PCC rule includes QoS parameters for each traffic flow within the multiplexed service data flow.

5. In paragraph 1, The step of transmitting information to the PCF regarding whether the terminal supports the identification function of the multiplexed service data flow is as follows: A method for transmitting an Npcf_SMPolicyControl_Create message or an Npcf_SMPolicyControl_update message that includes information on whether the terminal supports the identification function of the multiplexed service data flow.

6. In paragraph 1, A method in which information on whether the terminal supports the identification function of the multiplexed service data flow is provided from the terminal in a PDU (protocol data unit) session establishment procedure.

7. In the first paragraph, the method, A method further comprising the step of transmitting a QoS profile based on the above PCC rule to a user plane function (UPF) entity.

8. In the method performed by the PCF (policy control function) entity, A step of receiving information from a session management function (SMF) on whether a filter for processing multiplexed service data flows of a terminal is supported; A step of generating a PCC (policy and charging control) rule based on information on whether the terminal supports a filter for processing multiplexed service data flows; and A method comprising the step of transmitting the generated PCC rule to the SMF.

9. In paragraph 8, A method wherein, when the terminal supports the identification function of a multiplexed service data flow, the PCC rule includes QoS parameters for each traffic flow within the multiplexed service data flow.

10. In paragraph 8, The step of receiving information on whether the terminal supports a filter for processing multiplexed service data flow from the above SMF is as follows: A method for receiving an Npcf_SMPolicyControl_Create message or an Npcf_SMPolicyControl_update message including information on whether the terminal supports the identification function of the multiplexed service data flow.

11. For SMF (session management function) entities: at least one processor; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor, so that the SMF: Receive information on whether the terminal supports a filter for processing multiplexed service data flows, Transmit information to the PCF (policy control function) about whether a filter for processing the received multiplexed service data flow is supported, Receive a policy and charging control (PCC) rule generated based on whether the PCF supports a filter for processing the multiplexed service data flow, SMF that provides terminals with QoS (quality of service) rules based on the above PCC rules.

12. In paragraph 11, If the terminal supports a filter for processing multiplexed service data flows, the QoS rule includes information for identifying traffic within the flow of multiplexed service data.

13. In paragraph 12, Information for identifying the above traffic is an SMF including at least one of payload type information, media identification information, and SSRC (synchronization source) information.

14. In paragraph 11, If the terminal supports the identification function of the multiplexed service data flow, the PCC rule includes QoS parameters for each traffic flow within the multiplexed service data flow.

15. For PCF (policy control function) entities: at least one processor; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor, so that the PCF: Receive information from the SMF (session management function) on whether the terminal supports a filter for processing multiplexed service data flows, Generates a PCC (policy and charging control) rule based on information about whether the terminal supports a filter for processing multiplexed service data flows. PCF, which transmits the above generated PCC rule to the SMF.

Images