Method and device for managing multiplexed service data flow

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. According to various embodiments of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system may comprise the steps of: receiving, from an application function (AF) entity, information about a service data flow including one or more media flows; determining quality of service (QoS) flows for each of the one or more media flows; identifying, on the basis of the information about the service data flow, the one or more media flows supporting a multi-modal service; generating policy and charging control (PCC) rules including a QoS monitoring policy for the QoS flows; and transmitting the PCC rules to a session management function (SMF) entity, wherein the information about the service data flow may include a QoS monitoring requirement for each of the one or more media flows.

Description

Method and apparatus for managing multiplexed service data flows

[0001] The present disclosure relates to a wireless communication system, and more specifically, the present disclosure relates to a method and apparatus for managing a multiplexed service data flow 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 frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands ('above 6 GHz'), known as millimeter wave (mmWave), such as 28 GHz and 39 GHz. In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz (THz) band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies included beamforming and massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands; support for various numerologies (such as operating multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources; initial access technologies to support multi-beam transmission and broadband; definition and operation of Band-Width Parts (BWPs); Low Density Parity Check (LDPC) codes for high-volume data transmission; new channel coding methods such as polar codes for the reliable transmission of control information; and L2 pre-processing. Standardization has been carried out for network slicing, which provides a dedicated network specialized for specific services.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands that meets various regulatory requirements; NR terminal low power consumption technology (UE power saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides 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 RACH for NR which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., service-based architecture, service-based interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems will serve as a foundation for the development of technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication, multi-antenna transmission technologies like Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, metamaterial-based lenses and antennas to improve terahertz band signal coverage, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication, AI-based communication technology that realizes system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology that realizes services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It will be possible.

[0008] In particular, when providing multimedia services, service provider servers can generally multiplex service data flows with different media characteristics transmitted from the multimedia service provider server to the 5G mobile communication system by service or subscriber into a single service data flow in order to save resources, and thus a method to effectively provide these services is required.

[0009] Based on the discussion set forth above, the present disclosure aims to provide a method and apparatus for managing service data flow in a wireless communication system.

[0010] The technical problems to be solved by the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

[0011] According to various embodiments of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system may include: receiving information about a service data flow including one or more media flows from an application function (AF) entity; determining quality of service (QoS) flows for each of the one or more media flows; identifying the one or more media flows that support multi-modal services based on the information about the service data flow; generating policy and charging control (PCC) rules including a QoS monitoring policy for the QoS flows; and transmitting the PCC rules to a session management function (SMF) entity, wherein the information about the service data flow may include QoS monitoring requirements for each of the one or more media flows.

[0012] According to various embodiments of the present disclosure, in a policy control function (PCF) entity in a wireless communication system, at least one processor; and may include at least one memory that is communiquently coupled to the at least one processor and stores instructions, and the instructions may be executed by the at least one processor individually or in any combination, so that the PCF entity: receives information about a service data flow including one or more media flows from an application function (AF) entity, determines quality of service (QoS) flows for each of the one or more media flows, identifies the one or more media flows that support multi-modal services based on the information about the service data flow, generates policy and charging control (PCC) rules including a QoS monitoring policy for the QoS flows, and transmits the PCC rules to the session management function (SMF) entity, and the information about the service data flow may include QoS monitoring requirements for each of the one or more media flows.

[0013] According to an embodiment of the present disclosure, an apparatus and a method capable of effectively providing services in a wireless communication system may be provided.

[0014] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0015] FIG. 1 illustrates an example of a network structure and interface of a 5G system according to embodiments of the present disclosure.

[0016] FIG. 2 illustrates a process for determining whether a multiplexed service data flow supports multimodal services according to embodiments of the present disclosure.

[0017] FIGS. 3a and 3b illustrate a flow of signals for determining whether a multiplexed service data flow supports multimodal services and for transmitting related information, according to embodiments of the present disclosure.

[0018] FIGS. 4a and 4b illustrate a flow of another signal for determining whether a multiplexed service data flow supports multimodal services and for conveying related information, according to embodiments of the present disclosure.

[0019] FIG. 5 illustrates an example of the configuration of a base station in a wireless communication system according to embodiments of the present disclosure.

[0020] FIG. 6 illustrates an example of the configuration of a network entity in a wireless communication system according to embodiments of the present disclosure.

[0021] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit the scope of other embodiments. A singular expression may include a plural expression unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as generally understood by those skilled in the art described in this disclosure. Terms used in this disclosure that are defined in a general dictionary may be interpreted as having the same or similar meaning as they have in the context of the relevant technology, and are not to be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure. In some cases, even terms defined in this disclosure are not to be interpreted to exclude the embodiments of this disclosure.

[0022] In the various embodiments of the present disclosure described below, a hardware-based approach is described as an example. However, since the various embodiments of the present disclosure include techniques using both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0023] Terms referring to components of the device (control unit, processor) and terms referring to data (signal, feedback, report, reporting, information, parameter, value, bit, codeword, etc.) used in the following description are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms having similar or equivalent technical meanings may be used.

[0024] Additionally, the present disclosure describes various embodiments using terms used in some communication standards (e.g., 3GPP (3rd Generation Partnership Project)), but this is merely illustrative. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0025] 3GPP, which is responsible for cellular mobile communication standards, is proceeding with standardization of a new core network structure named 5G core (5GC) to facilitate the evolution from 4G LTE systems to 5G systems. 5GC can support the differentiated features described below compared to the Evolved Packet Core (EPC), which is the network core for 4G.

[0026] Network slicing capabilities are introduced in 5GC. As a requirement for 5G, 5GC must support various types of terminals and services. For example, services such as enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLC), and Massive Machine Type Communications (mMTC) can be supported. Each of these terminals or services may require different conditions from the core network. For instance, eMBB services may require high data rates, while URLLC services may require high stability and low latency. Network slicing technology has been proposed to satisfy these diverse service requirements.

[0027] According to various embodiments, network slicing may refer to a method of virtualizing a single physical network to create multiple logical networks (e.g., network slices). An active network slice may be referred to as a network slice instance (NSI), and each network slice instance may have different characteristics. A mobile operator can satisfy various service requirements for terminals or services by configuring a network function (NF) suitable for the characteristics of each NSI. For example, a mobile operator can efficiently support multiple 5G services (e.g., eMBB, URLLC, or mMTC) by assigning an NSI suitable for the characteristics of the service required by each terminal.

[0028] 5GC facilitates support for the network virtualization paradigm by separating mobility management functions and 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 functions. In 5G, as the number of terminals (e.g., including MTC terminals) increases explosively and the mobility and traffic / session characteristics that must be supported vary depending on the terminal type, if a single entity (e.g., MME) supports all functions, scalability—which requires adding entities for specific functions—inevitably suffers. Therefore, to improve scalability in terms of the functional / implementation complexity and signaling load of the core entity responsible for the control plane, various functions are being developed based on a structure that separates mobility management functions and session management functions.

[0029] Embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. Furthermore, in describing the present disclosure, specific descriptions of related known functions or configurations are omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Additionally, terms used below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0030] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing may be assigned the same reference number.

[0031] The advantages and features of the technical concept according to the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to make the present disclosure complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals may refer to the same components.

[0032] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of an eNode B, Node B, BS (Base Station), RAN (Radio Access Network), AN (Access Network), RAN node, wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) refers to the wireless transmission path of a signal transmitted by the base station to the terminal, and the uplink (UL) refers to the wireless transmission path of a signal transmitted by the terminal to the base station.

[0033] In addition, while 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, 5th-generation mobile communication technology (5G) developed after LTE-A (e.g., new radio, NR) may be included in a system to which the embodiments of the present disclosure can be applied, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0034] It will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a specialized computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in such computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0035] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order.

[0036] As used in the embodiments of the present disclosure, the term “part” refers to a software or hardware component, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), and the “part” may perform certain roles. However, the “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0037] According to various embodiments of the present disclosure, in the case of metaverse and XR (eXtended reality) applications, since terminals need to transmit and receive a large amount of traffic, effectively processing traffic must solve significant technical problems, unlike in conventional applications. While existing research has primarily focused on effectively transmitting traffic from application servers to terminals, there is a need to further explore new methods to effectively process large amounts of traffic and service flows with various characteristics for metaverse / XR traffic.

[0038] According to various embodiments, for metaverse and XR applications, a large amount of data must be transmitted, and to effectively schedule this, a method to reduce network congestion can be applied.

[0039] FIG. 1 illustrates an example of a network structure and interface of a 5G system according to embodiments of the present disclosure. A network entity included in the network structure of the 5G system of FIG. 1 may include various network functions (NF) depending on the system implementation.

[0040] Referring to FIG. 1, the network structure 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), 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 (e.g., user equipment (UE)).

[0041] Each NF of a 5G system can support the following functions.

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

[0043] The AMF provides functions for connectivity and mobility management at the UE level, and can be connected to one AMF per UE by default. Specifically, the AMF can support signaling between Core Network (CN) nodes for mobility between 3GPP access networks, termination of Radio Access Network (RAN) Control Plane (CP) interfaces (e.g., N2 interfaces), termination of Non Access Stratum (NAS) signaling (e.g., N1 interfaces), NAS signaling security (NAS ciphering and integrity protection), Access Stratum (AS) security control, registration management (e.g., registration area management), connectivity management, idle mode UE reachability (e.g., including control and execution of paging retransmission), mobility management control (e.g., subscription and policy), support for intra-system mobility and inter-system mobility, support for network slicing, and SMF selection. In addition, the AMF can support functions such as Lawful Intercept (LI) (e.g., lawful interception of AMF events and interfaces to LI systems), provision of Session Management (SM) message delivery between the UE and the SMF, transparent proxy for SM message routing, access authentication, access authorization including roaming authorization checks, provision of SMS message delivery between the UE and the SMSF (short message service function), Security Anchor Function (SAF) and / or Security Context Management (SCM).Some or all of the functions of an AMF can be supported within a single instance of an AMF.

[0044] DN may mean, for example, operator services, internet access, or third-party services. DN may transmit downlink protocol data units (PDUs) to UPF or receive PDUs transmitted from UE from UPF.

[0045] The PCF can provide the functionality to determine policies, such as mobility management and session management, by receiving information about packet flows from the application server. Specifically, the PCF can support functions such as supporting a unified policy framework to control network behavior, providing policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce policy rules, and implementing a front end to access relevant subscription information within the User Data Repository (UDR) for policy decisions.

[0046] The SMF provides session management functions, and if 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 maintaining a tunnel between the UPF and the (R)AN node), UE IP address allocation and management (optional, including authentication), selection and control of UP functions, configuration of traffic steering to route traffic from the UPF to an appropriate destination, termination of interfaces toward policy control functions, enforcement of policy and Quality of Service (QoS) control parts, and lawful interception (e.g., SM events and lawful interception of interfaces to LI systems). Additionally, the SMF can support functions such as termination of the SM part of NAS messages, downlink data notification, initiation of AN-specific SM information (e.g., delivery to the (R)AN via the N2 interface through the AMF), determination of the session's SSC mode, and roaming functions. Some or all of the functions of an SMF can be supported within a single instance of an SMF.

[0047] UDM stores user sign-up data, policy data, etc. UDM may include two parts, for example, an application front end (FE) and a user data repository (UDR).

[0048] The FE (front end) may include a UDM FE responsible for location management, subscription management, and credential processing, and a PCF responsible for policy control. The UDR may store data required for the functions provided by the UDM-FE and policy profiles required by the PCF. The data stored in the UDR may include user subscription data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data, as well as policy 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, enrollment / mobility management, subscription management, and SMS management.

[0049] The UPF can forward downlink PDUs received from the DN to the UE via the (R)AN, and forward uplink PDUs received from the UE to the DN via the (R)AN. Specifically, the UPF can support anchor points for intra / inter RAT mobility, external PDU session points for interconnects to the data network, packet routing and forwarding, the user plane portion of packet inspection and policy rule enforcement, lawful intercept, traffic usage reporting, and uplink classifiers to support routing of traffic flows to the data network. Additionally, UPF can support features 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 verification (e.g., SDF mapping between Service Data Flows (SDF) and QoS flows), transport-level packet marking within uplink and downlink, downlink packet buffering, and downlink data notification triggering. Some or all of the functions of UPF can be supported within a single instance of UPF.

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

[0051] (R)AN can be a collective term for 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) (e.g., gNB).

[0052] gNB (e.g., may be used interchangeably with (R)AN below) can support functions for radio resource management (e.g., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources (i.e., scheduling) to UEs in uplink / downlink), IP (internet protocol) header compression, encryption and integrity protection of user data streams, selection of AMF at UE attachment 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. In addition, the gNB can support functions such as scheduling and transmission of paging messages (generated from AMF), scheduling and transmission of system broadcast information (generated from AMF or Operating and Maintenance (O&M), measurement and measurement reporting settings for mobility and scheduling, transport level packet marking on the uplink, session management, support for network slicing, QoS flow management and mapping to data wireless bearers, support for UEs in inactive mode, distribution of NAS messages, NAS node selection, wireless access network sharing, dual connectivity, and tight interworking between NR and E-UTRA.

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

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

[0055] NRF can support service discovery features. NRF can receive NF discovery requests from NF instances and provide information about discovered NF instances to the NF instances. Additionally, NRF can maintain available NF instances and the services they support.

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

[0057] A UE can simultaneously access two data networks (e.g., local and central) using multiple PDU sessions. In this case, two SMFs may be selected for different PDU sessions. However, each SMF may have the capability to control both the local UPF and the central UPF within the PDU session.

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

[0059] In 3GPP systems, conceptual links connecting NFs within a 5G system can be defined as reference points. For example, reference point(s) defined in a 5G system include the reference point(s) illustrated in FIG. 1 and are as follows.

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

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

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

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

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

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

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

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

[0068] - N9: Reference point between 2 core UPFs

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

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

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

[0072] - N13: Reference point between UDM and AUSF

[0073] - N14: Reference point between 2 AMFs

[0074] - N15: Reference point between PCF and AMF in non-roaming scenarios, reference point between PCF and AMF within the visited network in roaming scenarios

[0075] FIG. 2 illustrates a process for determining whether a multiplexed service data flow supports multimodal services according to embodiments of the present disclosure. More specifically, FIG. 2 shows an example of determining whether a multiplexed service data flow supports multimodal services based on service requirements and operator policies related to the multiplexed service data flow received by the PCF from the AF.

[0076] Referring to FIG. 2, a request for a multimodal service to be appropriately processed by considering characteristic information of the media flow in the 5GC and RAN according to the multimodal service requirements per media flow that constitute a service data flow multiplexed on the control plane through a 5G system can be determined by the AF. Alternatively, the PCF can determine multimodal service-based processing for media flows within the multiplexed service data flow according to operator policy.

[0077] A service provider according to one embodiment of the present invention may consider the association between media flows constituting the same service. Accordingly, the service provider may generate one or more appropriate QoS flows based on characteristic information of the media constituting each media data flow, and request processing that considers multimodal service characteristics between media flows within a multiplexed service flow composed of the one or more QoS flows.

[0078] For example, in the case of a multiplexed service data flow composed of three media types (e.g., flows), such as audio, video, and haptics, the AS may transmit each media flow to the UPF through a single data service flow. In this case, the AF may transmit the service requirements of each media flow constituting the multiplexed service data flow and, accordingly, request the PCF to create one or more QoS flows for processing the media flow considering the media characteristics. Based on network conditions and network operator policy information, if the multiplexed service data flow requested by the AF can be processed according to one or more QoS flows, the PCF may determine whether to support QoS flow processing using multimodal service characteristics between one or more QoS flows. Whether to support multiplexed service data flows using multimodal service characteristics may be determined based on multimodal service-related information between media flows transmitted from the AF (e.g., MMS (multi-modality service) ID or MMS support indication for multiplexed service data flow). Alternatively, without separate multimodal service-related information from AF, PCF may determine media service support that considers the multimodal service characteristics between QoS flows constituting the media flows within the multiplexed service data flow, when a multiplexed service data flow is serviced through one or more QoS flows considering the characteristics of each media flow according to the operator's policy.

[0079] According to one embodiment, when one or more QoS flows are generated based on the requirements of a media flow generated in a PCF, in determining whether to apply multimodal service characteristics between the QoS flows, the number of QoS flows that ultimately support multimodal service characteristics can also be determined based on multimodal service-related information transmitted from an AF and QoS flow information determined in the PCF. For example, even when a multiplexed service data flow consists of video, audio, haptic, and control information (e.g., RTCP (Real Time Transport Protocol)), the PCF can determine the generation of QoS flows for each of the video and audio media flows, and can determine the generation of three QoS flows by mapping the haptic and control information into a single QoS flow. In such cases, the PCF can identify a single QoS flow mapped to a media flow having one of the media characteristics among the media flows constituting the multiplexed service data flow, and can decide to consider multimodal service characteristics only for these QoS flows.

[0080] According to one embodiment, the PCF may determine QoS flows for considering multimodal service characteristics among the QoS flows generated to ultimately consider different media characteristics, based on service provider policies, etc. Subsequently, for QoS monitoring of the QoS flows for considering multimodal service characteristics, the PCF may generate QoS monitoring policy information for the QoS flows to which multimodal service characteristics are to be applied, by utilizing QoS monitoring requirement information per media flow separately transmitted from the AF or based on information pre-configured through the service provider. Additionally, while a QoS monitoring policy is being created according to the requirements of the service provider or the configuration of the network provider, if a Threshold of Delay Difference between Media Flows is transmitted from the AF to the PCF, or if QoS monitoring using the required Delay Difference between Media Flows is determined based on pre-configured information within the PCF, binding-related information between the media flows (e.g., Threshold of Delay Difference between Media Flows per binding id, binding information (e.g., id) between the media (QoS) flows) may be generated. Alternatively, the PCF may generate mapping information between QoS flows to support multimodal services based on the binding-related information between media flows received from the AF. The mapping information between QoS flows may be generated by considering only QoS flows where one media flow is mapped to one QoS flow (e.g., QoS flows where one media flow is mapped) based on the binding information between media flows.Subsequently, the PCF may transmit media flow information supporting multi-modal services at the PCF (e.g., a list of accepted media flow for supporting multi-modal service) to the AF via the NEF. Alternatively, if the PCF independently decides to support multi-modal services based on the operator's policy, etc., without generating separate multi-modal service support request information from the AF (e.g., Multi-modal Service ID and / or Multi-modal service support indication for multiplexed service flow), the PCF may transmit a result related to the multi-modal service request (Result of the MMS for multiplexed service data flow) to the AF via the NEF, which includes at least one of the following: a multi-modal service ID (e.g., when the PCF generates a multi-modal service ID) or a multi-modal service ID request message (e.g., when providing multi-modal services using a multi-modal service ID generated by the AF).

[0081] According to one embodiment, the PCF may create or update a PCC rule containing binding information between QoS flows and a QoS monitoring policy and transmit it to the SMF. Upon receiving the PCC rule containing binding information between QoS flows and a QoS monitoring policy from the PCF, the SMF may transmit the binding information between QoS flows and the QoS monitoring policy information to the UPF or RAN to request QoS monitoring. The SMF may include the binding information between QoS flows and the QoS monitoring policy information within an N4 rule to request QoS monitoring between QoS flows to support multimodal service characteristics. The SMF may transmit the N4 rule to the UPF. Based on the QoS monitoring parameters within the QoS monitoring policy, if the difference in transmission delay times between media flows constituting a specific QoS flow exceeds a certain threshold (e.g., exceed the threshold of delay difference between Media (QoS) Flows), the UPF may perform a QoS monitoring reporting operation including whether the event occurred and related information. The QoS monitoring reporting message may include at least one of the following: binding information between QoS flows (e.g., binding id) and QoS monitoring results. The SMF may transmit the QoS monitoring reporting information received from the UPF to the PCF. Based on the QoS monitoring reporting information received from the SMF, the PCF may modify the QoS parameter information configuring the QoS flows so that the difference in transmission delay time between the media / QoS flows does not exceed a certain threshold value.For example, if the delay between QoS flows transmitting video and audio media increases to 50ms or more, the PCF may reduce the value of the delay difference between QoS flows by applying alternative QoS requirements to reduce the delay between the QoS flows or by performing QoS parameter updates, thereby controlling the delay within the delay threshold or synchronization thresholds. The PCF may transmit an updated PCC rule, including the changed QoS parameter information, to the SMF so that the difference in transmission delay time between media / QoS flows does not exceed a certain threshold. Based on the changed QoS parameter information, the SMF may generate an updated QoS profile and transmit the updated QoS profile information to the UPF and RAN.

[0082] According to one embodiment, the SMF may determine whether to request QoS monitoring from the RAN based on NG RAN QoS monitoring capability parameters received from the AMF while performing PDU session establishment / modification procedures, service requests, and UE mobility procedures. Additionally, the SMF may determine whether to request NG RAN scheduling based on multimodal services from the RAN based on NG RAN Multi-Modal service capability parameters received from the AMF while performing PDU session establishment / modification procedures, service requests, and UE mobility procedures. If the NG-RAN supports both QoS monitoring considering multimodal service characteristics and NG RAN scheduling considering multimodal service characteristics, the SMF may select one of them according to the network operator's policy. If the NG RAN does not support both QoS monitoring considering multimodal service characteristics and NG RAN scheduling considering multimodal service characteristics, the SMF may not transmit binding information between QoS flows and QoS monitoring-related information (e.g., QoS Monitoring indication, QoS Monitoring reporting frequency, QoS monitoring parameter) to the NG-RAN to support multimodal services. Regarding whether to request QoS monitoring from the UPF and / or NG-RAN, depending on the network operator's policy, QoS monitoring may be requested from both network entities, or one network entity may be selected and QoS monitoring may be requested from that network entity.

[0083] According to one embodiment, if AF does not generate separate multimodal service support request information (e.g., Multi-modal Service ID and / or Multi-modal service support indication for multiplexed service flow) and PCF independently decides to support multimodal services based on the operator's policy, etc., a result of the multimodal service request (Result of the MMS for multiplexed service data flow) including at least one of the following information (e.g., when PCF generates a Multi-modal service ID) and a multimodal service ID request message (e.g., when providing multimodal services using a Multi-modal service ID generated by AF) may be transmitted to AF via NEF.

[0084] According to one embodiment, if the result information related to a multimodal service request received from the PCF includes a multimodal service ID request message, the AF may update service requirement information related to a media flow determined to support a multimodal service by including a multimodal service ID within the multiplexed service data flow. The AF may transmit the service requirement information including the updated media flow-related multimodal service ID to the PCF.

[0085] FIGS. 3a and 3b illustrate a signal flow for determining whether a multiplexed service data flow supports multimodal services and for transmitting related information, according to embodiments of the present disclosure. More specifically, FIGS. 3a and 3b illustrate an example for determining whether a multiplexed service data flow supports multimodal services and for transmitting related information based on service requirements related to the multiplexed service data flow received from AF.

[0086] In Step 1, the Service Provider may generate one or more appropriate QoS flows based on characteristic information of the media constituting each media data flow, taking into account the association between media flows constituting the same service. The Service Provider may determine the processing of media flows by taking into account the multimodal service characteristics between media flows within a service flow (e.g., multiplexed) composed of the generated one or more QoS flows. For example, in the case of a service data flow multiplexed into three media types (e.g., flows), such as audio, video, and haptics, the AS may transmit each media flow to the UPF through a single data service flow.

[0087] In Step 2, the AF may transmit service requirements for each media flow constituting the multiplexed service data flow to the NEF. The AF may transmit service requirements for each media flow and multimodal service-related information to the NEF. Here, the service requirements for each media flow may be requirements for creating one or more QoS flows for processing media flow based on media characteristics. The multimodal service-related information may include at least one of the following: MMSID (multimodality service id), MMS support indication for multiplexed service data flow, QoS monitoring requirements per media flow, Threshold of Delay Difference between Media Flows, and binding information (e.g., binding id) between media flows.

[0088] In Step 3, the NEF may perform authorization regarding whether the AF can provide service requirements for each media flow constituting the multiplexed service data flow and multimodal service-related information. If the authorization is successful, the NEF may transmit service requirements for each media flow constituting the multiplexed service data flow and multimodal service-related information to the PCF.

[0089] In step 4, PCF can determine whether multimodal service is supported between media flows constituting the multiplexed service data flow based on service requirements per media flow and information related to multimodal service.

[0090] In step 4a, PCF can check (or determine) whether the multiplexed service data flow requested by AF can be processed into one or more QoS flows based on network status, network operator policy information, and service requirements per media flow.

[0091] In step 4b, the PCF can check whether separate multimodal service IDs or multimodal service support indicator information has been transmitted from the AF. If a multimodal service ID per media flow or a multimodal service support indicator is transmitted together within the multiplexed service data flow, the PCF can determine whether to support multimodal services based on the multimodal service ID transmitted from the AF. The PCF may also determine whether to support multimodal services based on the network operator's policy or network status information. If a separate multimodal service ID is not transmitted and a multimodal service support indicator is transmitted via a protocol description, etc., the PCF can generate a separate multimodal service ID according to the network operator's policy or request it from the AF to perform actions for multimodal service support per media flow within the multiplexed service data flow. Through step 4a, the PCF can generate one or more QoS flows per media flow. A PCF that has received multimodal-related information from an AF (e.g., a multimodal service ID per media flow or a multimodal service support indicator) can determine the processing of a multiplexed service data flow that supports multimodal services.

[0092] In step 4c, the PCF can check whether the multimodal service ID per media flow received from the AF is applicable. For example, even if the multiplexed service data flow consists of video, audio, haptic, and control information (e.g., RTCP), the PCF can determine the creation of a total of three QoS flows by determining the creation of QoS flows for each of the video and audio media flows, and determining the creation of a single QoS flow by mapping the haptic and control information into a single QoS flow. In this case, the PCF can decide to consider only the multimodal service characteristics for the single QoS flows to which a media flow having one of the media characteristics among the media flows constituting the multiplexed service data flow is mapped. As described above, the PCF can determine the QoS flows to consider multimodal service characteristics among the QoS flows created to consider different media characteristics, based on service provider policies, etc. Through the steps described above, the PCF can determine acceptable media flows based on the multimodal service application request information per media flow received from the AF.

[0093] In step 4d, the PCF can generate a QoS monitoring policy to perform a QoS monitoring operation based on media flow information capable of accepting multimodal service support requests determined in step 4c. Requirement information for QoS monitoring per media flow can be transmitted from the AF through steps 2 and 3. According to one embodiment, the PCF can generate a QoS monitoring policy based on the requirements of the service provider or the configuration of the network operator, and determine whether to perform a QoS monitoring operation using the required delay time threshold between media flows based on the required delay time threshold between media flows transmitted from the AF or pre-configured information within the PCF. If PCF determines this, it may additionally generate binding-related information between the media flows (e.g., Threshold of Delay Difference between Media Flows per binding id, binding information (e.g., id) between the media (QoS) flows), or generate mapping information between QoS flows that support multimodal services based on binding-related information between media flows received from AF. PCF may generate mapping information between QoS flows by considering only QoS flows that are mapped one-to-one to a single media flow based on binding information between media flows. PCF may include information regarding the delay difference between the media flows and binding / mapping information between media flows (e.g., Binding ID between media flows), etc., within the QoS monitoring policy.

[0094] In step 4e, the PCF can create or update a PCC rule containing a QoS monitoring policy and authorized QoS information for processing a multiplexed service data flow that supports the multimodal service created in step 4d.

[0095] In steps 5 and 6, the PCF may transmit to the AF via the NEF a result of the multimodal service request (Result of the MMS for multiplexed service data flow) that includes at least one of the following: media flow information supporting multimodal service at the PCF (e.g., list of accepted media flow for supporting Multi-modal service) and / or, if the PCF independently decides to support multimodal service according to the operator's policy, etc., without generating or transmitting information on a separate multimodal service support request from the AF (e.g., Multi-modal Service ID and / or Multi-modal service support indication for multiplexed service flow), a multimodal service ID (if the PCF generates a Multi-modal service ID) and a multimodal service ID request message (e.g., if the multimodal service is provided using a Multi-modal service ID generated by the AF).

[0096] In Step 7, the PCF may create or update a PCC rule containing authorized QoS-related information and a QoS monitoring policy to support multimodal services, and transmit it to the SMF. The QoS monitoring policy to support multimodal services may include requirements for QoS monitoring actions performed to support multimodal services (e.g., Threshold of Delay Difference between Media Flows per binding id, binding information (e.g., id) between the media (QoS) flows).

[0097] In step 8, the SMF, having received a PCC rule from the PCF that includes binding information between QoS flows and a QoS monitoring policy, may request QoS monitoring by transmitting the information regarding the binding information between QoS flows and the QoS monitoring policy to the UPF or RAN. The SMF may include the binding information between QoS flows and the QoS monitoring policy information in an N4 rule to request QoS monitoring between QoS flows to support multimodal service characteristics, and may transmit the N4 rule to the UPF.

[0098] In step 9, the UPF can perform QoS monitoring reporting including whether the event occurred and related information when the difference in transmission delay time between media flows constituting a specific QoS flow exceeds a certain threshold value based on QoS monitoring parameters within the QoS monitoring policy (e.g., exceed the threshold of delay difference between Media (QoS) Flows).

[0099] In step 10, the UPF can transmit the event information that occurred in step 9 to the SMF through a QoS monitoring reporting message. The QoS monitoring reporting message may include at least one of the binding information between QoS flows (e.g., binding id) and QoS monitoring results.

[0100] In step 11, SMF can transmit QoS monitoring reporting information received from UPF to PCF.

[0101] In Step 12, the PCF may modify the QoS parameter information constituting the QoS flows based on the QoS monitoring reporting information received from the SMF, so that the difference in transmission delay time between media / QoS flows does not exceed a certain threshold. For example, if the delay between QoS flows transmitting video and audio media increases to 50ms or more, the PCF may apply alternative QoS requirements or update QoS parameters to reduce the delay between the QoS flows, thereby reducing the value of the delay difference between each QoS flow and controlling the delay to within the range of the delay threshold or synchronization thresholds. The PCF may transmit an updated PCC rule containing the modified QoS parameter information to the SMF so that the difference in transmission delay time between media / QoS flows does not exceed a certain threshold. Based on the modified QoS parameter information, the SMF may generate an updated QoS profile and transmit the updated QoS profile information to the UPF and RAN.

[0102] At Step 13, the SMF may request the RAN to perform QoS monitoring from the SMF to the RAN. Whether to perform the QoS monitoring request operation from the SMF to the RAN may be determined based on the NG RAN QoS monitoring capability parameter received from the AMF during the PDU session establishment / modification procedure, service request, and UE mobility procedure. Additionally, whether to perform the NG RAN scheduling operation request based on multimodal service from the SMF to the RAN may be determined based on the NG RAN Multi-Modal service capability parameter received from the AMF during the PDU session establishment / modification procedure, service request, and UE mobility procedure. If the NG-RAN supports both QoS monitoring operations considering multimodal service characteristics and NG RAN scheduling operations considering multimodal service characteristics, the SMF may select one of these according to the network operator's policy. If the NG RAN does not support both QoS monitoring operations considering multimodal service characteristics and NG RAN scheduling operations considering multimodal service characteristics, the SMF may not transmit binding information between QoS flows and QoS monitoring-related information (e.g., QoS Monitoring indication, QoS Monitoring reporting frequency, QoS monitoring parameter) to the NG-RAN to support multimodal services. Depending on the network operator's policy, the request to perform QoS monitoring to the UPF and / or NG-RAN may be made to two network entities, or one network entity may be selected and the request made to that network entity.Based on the information and network operator's policy described above, the SMF can generate appropriate N2 SM information depending on whether QoS monitoring considering multimodal service characteristics or NG RAN scheduling based on multimodal services is performed in the NG-RAN, and can transmit said information to the AMF via the Namf_Communication_N1N2MessageTransfer message. The N2 SM information may include a QoS monitoring policy that includes requirements for performing QoS monitoring to support multimodal services (e.g., Threshold of Delay Difference between Media Flows per binding id, binding information (e.g., id) between the media (QoS) flows) when QoS monitoring operation considering multimodal service characteristics is supported according to the NG-RAN support function information. If only multimodal service-based NG RAN scheduling operations are supported according to the NG-RAN support function information, the N2 SM information may include at least one of the following: a multimodal service ID, a Threshold of Delay Difference between QoS Flows per binding ID, and binding information (e.g., ID) between the QoS flows.

[0103] In step 14, the AMF can transmit N2 SM information, which includes information related to a multiplexed service data flow supporting a multimodal service received from the SMF, to the NG RAN via an N2 message.

[0104] In step 15, the NG RAN can perform QoS monitoring to support multimodal services related to multiplexed service data flows supporting multimodal services or NG RAN scheduling based on multimodal services, based on N2 SM information transmitted based on information selected according to the status of the NG RAN and the network operator's policy and support function information. QoS monitoring to support multimodal services may include an operation to calculate and report the delay time difference between QoS flows (e.g., media flows) based on requirements for performing QoS monitoring to support multimodal services (e.g., Threshold of Delay Difference between QoS Flows per binding id, binding information (e.g., id) between the QoS flows). In addition, multimodal service-based NG RAN scheduling may include, based on the Threshold of Delay Difference between QoS Flows per binding id and binding information (e.g., id) between the QoS flow bound to the multimodal service, an operation to adjust an appropriate buffer delay or an operation to drop packets within the relevant QoS flow when congestion occurs.

[0105] FIGS. 4a and 4b illustrate another signal flow for determining whether a multiplexed service data flow supports multimodal services and for transmitting related information, according to embodiments of the present disclosure. More specifically, FIGS. 4a and 4b illustrate an example for determining whether a multiplexed service data flow supports multimodal services and for transmitting related information based on service requirements and operator policies related to the multiplexed service data flow received from AF.

[0106] In Step 1, the Service Provider may generate one or more appropriate QoS flows based on characteristic information of the media constituting each media data flow, taking into account the association between media flows constituting the same service. The Service Provider may determine the processing of media flows by taking into account the multimodal service characteristics between media flows within a service flow (e.g., multiplexed) composed of the generated one or more QoS flows. For example, in the case of a multiplexed service data flow composed of three media types (e.g., flows), such as audio, video, and haptics, the AS may transmit each media flow to the UPF through a single data service data flow.

[0107] In Step 2, AF may transmit service requirements for each media flow constituting the multiplexed service data flow to NEF. AF may transmit service requirements for each media flow and multimodal service-related information to NEF. Here, the service requirements for each media flow may be requirements for creating one or more QoS flows for processing media flow based on media characteristics. Multimodal service-related information may include at least one of the following: MMS support indication for multiplexed service data flow, QoS monitoring requirements per media flow, Threshold of Delay Difference between Media Flows, and binding information (e.g., binding id) between media flows.

[0108] In Step 3, the NEF may perform authorization regarding whether the AF can provide service requirements for each media flow constituting the multiplexed service data flow and multimodal service-related information. If the authorization is successful, the NEF may transmit service requirements for each media flow constituting the multiplexed service data flow and multimodal service-related information to the PCF.

[0109] In Step 4, the PCF can determine whether multimodal services are supported between media flows constituting the multiplexed service data flow based on service requirements per media flow and information related to multimodal services. The PCF can check (or determine) whether the multiplexed service data flow requested by the AF can be processed as one or more QoS flows based on network conditions, network operator policy information, and service requirements per media flow.

[0110] In step 5a, the PCF can check whether separate multimodal service support indicator information has been transmitted from the AF. If multimodal service support indicators have been transmitted from the AF, the PCF can determine whether to support multimodal services based on the network operator's policy or network status information. If a separate multimodal service ID is not transmitted and the multimodal service support indicator is transmitted via a protocol description, etc., the PCF can generate a separate multimodal service ID according to the network operator's policy or request it from the AF to perform actions for multimodal service support for each media flow within the corresponding multiplexed service data flow.

[0111] In step 5b, the PCF may generate one or more QoS flows per media flow, and if it receives multimodal-related information (e.g., a multimodal service support indicator) from the AF, the PCF may determine the processing of a multiplexed service data flow that supports multimodal services. According to one embodiment of the present invention, in step 5a, the PCF may determine multimodal service support between media flows within a multiplexed service data flow according to network operator policies or settings, even if separate multimodal service support indicator information is not transmitted from the AF. For example, if the PCF can generate one or more QoS flows per media flow through step 4, it may determine multimodal service support between media flows within a multiplexed service data flow according to network operator policies or settings.

[0112] In Step 6, if the PCF determines multimodal service support between media flows within the multiplexed service data flow in Step 5b, it may determine QoS flows (e.g., media flows) to support multimodal services. For example, even if the multiplexed service data flow consists of video, audio, haptic, and control information (e.g., RTCP), the PCF may determine the creation of three QoS flows by determining the creation of separate QoS flows for the video and audio media flows, and determining the creation of haptic and control information by mapping them into a single QoS flow. In the above case, the PCF may determine to consider multimodal service characteristics only for QoS flows that are mapped one-to-one to a media flow having one of the media characteristics among the media flows constituting the multiplexed service data flow. As described above, the PCF can determine QoS flows for considering multimodal service characteristics among the QoS flows generated to ultimately consider different media characteristics, based on service provider policies, etc. Through the steps described above, the PCF can determine acceptable media flows based on the multimodal service application request information for each media flow received from the AF.

[0113] In step 7, if a separate multimodal service ID is not transmitted from AF, PCF may decide to request the multimodal service ID from AF or to generate a multimodal service ID. If, according to the network operator's policy, PCF can generate a separate multimodal service ID, PCF does not perform the action of requesting the multimodal service ID from AF, and may transmit the multimodal service ID generated by PCF and related information (e.g., media flow information constituting the multimodal service).

[0114] In steps 8 and 9, the PCF may transmit to the AF via the NEF a result of the MMS for multiplexed service data flow, which includes at least one of the following: media flow information supporting the multimodal service determined through steps 5 through 7 (e.g., list of accepted media flow for supporting Multi-modal service) and, according to the result of step 7, a multimodal service ID request (e.g., Multi-modal Service ID Request indication), a multimodal service ID generated by the PCF, or information related to the multimodal service ID (e.g., media flow information constituting the multimodal service).

[0115] In steps 10 and 11, if the AF receives multi-modal service ID request information (e.g., Multi-modal Service ID Request indication) from the PCF in steps 8 and 9, it can generate a multi-modal service ID based on media flow information supporting multi-modal service (e.g., list of accepted media flow for supporting multi-modal service) and transmit the information to the PCF through the NEF.

[0116] In Step 12, the PCF can generate a QoS monitoring policy to perform QoS monitoring based on the information received and determined in the above-described step. The requirement information for QoS monitoring per media flow described above may be transmitted from the AF, or additionally selected according to the requirements of the service provider or the settings of the network operator. When a PCF is generating a QoS monitoring policy, if a threshold of delay difference between media flows required from an AF is transmitted to the PCF, or if it is determined to perform QoS monitoring using the threshold of delay difference between media flows based on pre-configured information within the PCF, the PCF may generate binding-related information between the media flows (e.g., Threshold of Delay Difference between Media Flows per binding id, binding information (e.g., id) between the media (QoS) flows), or generate mapping information between QoS flows that support multimodal services based on the binding-related information between media flows received from the AF. According to one embodiment of the present invention, the mapping information between QoS flows may be generated by considering only QoS flows to which a single media flow is mapped one-to-one based on the binding information between media flows. PCF can include information on latency differences between media flows and binding / mapping information between media flows (e.g., Binding ID between media flows) within the QoS monitoring policy.

[0117] In step 13, the PCF can create or update a PCC rule containing a QoS monitoring policy and authorized QoS information for processing a multiplexed service data flow supporting a multimodal service created in step 12.

[0118] At Step 14, the PCF may create or update a PCC rule containing authorized QoS-related information and a QoS monitoring policy to support multimodal services, and transmit it to the SMF. The QoS monitoring policy to support multimodal services may include requirements for performing QoS monitoring to support multimodal services (e.g., Threshold of Delay Difference between Media Flows per binding id, binding information (e.g., id) between the media (QoS) flows).

[0119] In step 15, the SMF, having received a PCC rule from the PCF that includes binding information between QoS flows and a QoS monitoring policy, may request QoS monitoring by transmitting the information regarding the binding information between QoS flows and the QoS monitoring policy to the UPF or RAN. The SMF may include the binding information between QoS flows and the QoS monitoring policy information in the N4 rule to request QoS monitoring between QoS flows to support multimodal service characteristics, and may transmit the N4 rule to the UPF.

[0120] In step 16, the UPF can perform QoS monitoring reporting including whether the event occurred and related information when the difference in transmission delay time between media flows constituting a specific QoS flow exceeds a certain threshold value based on QoS monitoring parameters within the QoS monitoring policy (e.g., exceed the threshold of delay difference between Media (QoS) Flows).

[0121] In step 17, the UPF can transmit the event information that occurred in step 9 to the SMF through a QoS monitoring reporting message. The QoS monitoring reporting message may include at least one of the binding information between QoS flows (e.g., binding id) and QoS monitoring results.

[0122] In step 18, SMF can transmit QoS monitoring reporting information received from UPF to PCF.

[0123] In Step 19, the PCF may modify the QoS parameter information configuring the QoS flows based on the QoS monitoring reporting information received from the SMF, so that the difference in transmission delay time between media / QoS flows does not exceed a certain threshold. For example, if the delay between QoS flows transmitting video and audio media increases to 50ms or more, the PCF may apply alternative QoS requirements or update QoS parameters to reduce the delay between the QoS flows, thereby reducing the value of the delay difference between each QoS flow and controlling the delay to within the range of the delay threshold or synchronization thresholds. The PCF may transmit an updated PCC rule containing the modified QoS parameter information to the SMF so that the difference in transmission delay time between media / QoS flows does not exceed a certain threshold. Based on the modified QoS parameter information, the SMF may generate an updated QoS profile and transmit the updated QoS profile information to the UPF and RAN.

[0124] At step 20, the SMF may request the RAN to perform QoS monitoring from the SMF to the RAN. Whether to perform the operation to request QoS monitoring from the SMF to the RAN may be determined based on the NG RAN QoS monitoring capability parameter received from the AMF during the PDU session establishment / modification procedure, service request, and UE mobility procedure. Additionally, whether to perform the operation to request multimodal service-based NG RAN scheduling from the SMF to the RAN may be determined based on the NG RAN Multi-Modal service capability parameter received from the AMF during the PDU session establishment / modification procedure, service request, and UE mobility procedure. If the NG-RAN supports both QoS monitoring operation considering multimodal service characteristics and NG RAN scheduling operation considering multimodal service characteristics, the SMF may select one of these according to the network operator's policy. If the NG RAN does not support both QoS monitoring operations considering multimodal service characteristics and NG RAN scheduling operations considering multimodal service characteristics, the SMF may not transmit binding information between QoS flows and QoS monitoring-related information (e.g., QoS Monitoring indication, QoS Monitoring reporting frequency, QoS monitoring parameter) to the NG-RAN to support multimodal services. Depending on the network operator's policy, the request to perform QoS monitoring to the UPF and / or NG-RAN may be made to two network entities, or one network entity may be selected and the request made to that network entity.Based on the information and network operator's policy described above, the SMF can generate appropriate N2 SM information depending on whether QoS monitoring considering multimodal service characteristics or NG RAN scheduling based on multimodal services is performed in the NG-RAN, and can transmit said information to the AMF via the Namf_Communication_N1N2MessageTransfer message. The N2 SM information may include a QoS monitoring policy that includes requirements for performing QoS monitoring to support multimodal services (e.g., Threshold of Delay Difference between Media Flows per binding id, binding information (e.g., id) between the media (QoS) flows) when QoS monitoring operation considering multimodal service characteristics is supported according to the NG-RAN support function information. If only multimodal service-based NG RAN scheduling operations are supported according to the NG-RAN support function information, the N2 SM information may include at least one of the following: a multimodal service ID, a Threshold of Delay Difference between QoS Flows per binding ID, and binding information (e.g., ID) between the QoS flows.

[0125] In step 21, the AMF can transmit N2 SM information, which includes information related to a multiplexed service data flow supporting a multimodal service received from the SMF, to the NG RAN via an N2 message.

[0126] In step 22, the NG RAN can perform QoS monitoring to support multimodal services or NG RAN scheduling based on multimodal services related to multiplexed service data flows that support multimodal services, based on N2 SM information transmitted based on information selected according to the status of the NG RAN and the network operator's policy and support function information. QoS monitoring to support multimodal services may include an operation to calculate and report the delay time difference between QoS flows (e.g., media flows) based on requirements for performing QoS monitoring to support multimodal services (e.g., Threshold of Delay Difference between QoS Flows per binding id, binding information (e.g., id) between the QoS flows). In addition, multimodal service-based NG RAN scheduling may include, based on the Threshold of Delay Difference between QoS Flows per binding id and binding information (e.g., id) between the QoS flow bound to the multimodal service, an operation to adjust an appropriate buffer delay or an operation to drop packets within the relevant QoS flow when congestion occurs.

[0127] FIG. 5 illustrates an example of the configuration of a base station in a wireless communication system according to embodiments of the present disclosure. According to various embodiments of the present disclosure, the base station may be referred to as a network or a radio access network (RAN) for convenience. The configuration exemplified in FIG. 5 can be understood as the configuration of a base station. Terms such as '...unit', '...unit' used below refer to a unit that processes at least one function or operation, which may be implemented in hardware or software, or a combination of hardware and software.

[0128] Referring to FIG. 5, the base station may include a wireless communication unit (510), a backhaul communication unit (520), a storage unit (530), and a control unit (540).

[0129] The wireless communication unit (510) performs functions for transmitting and receiving signals through a wireless channel. For example, the wireless communication unit (510) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the wireless communication unit (510) generates complex symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the wireless communication unit (510) restores the received bit sequence by demodulating and decoding the baseband signal. Additionally, the wireless communication unit (510) upconverts the baseband signal into an RF (radio frequency) band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal.

[0130] To this end, the wireless communication unit (510) may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Additionally, the wireless communication unit (510) may include a plurality of transmitting and receiving paths. Furthermore, the wireless communication unit (510) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the wireless communication unit (510) may be composed of a digital unit and an analog unit, and the analog unit may be composed of a plurality of sub-units according to operating power, operating frequency, etc.

[0131] The wireless communication unit (510) can transmit and receive signals. To this end, the wireless communication unit (510) may include at least one transceiver. For example, the wireless communication unit (510) can transmit a synchronization signal, a reference signal, system information, a message, control information, or data. Additionally, the wireless communication unit (510) can perform beamforming.

[0132] The wireless communication unit (510) transmits and receives signals as described above. Accordingly, all or part of the wireless communication unit (510) may be referred to as a 'transmitter', 'receiver', or 'transmitter / receiver'. Furthermore, in the following description, transmission and reception performed through a wireless channel are used to mean that processing as described above is performed by the wireless communication unit (510).

[0133] The backhaul communication unit (520) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (520) converts a bit sequence transmitted from a base station to another node, e.g., another connection node, another base station, an upper node, a core network, etc., into a physical signal, and converts a physical signal received from another node into a bit sequence.

[0134] The storage unit (530) stores data such as basic programs, application programs, and configuration information for the operation of the base station. The storage unit (530) may include memory. The storage unit (530) may be composed of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. Additionally, the storage unit (530) provides the stored data upon the request of the control unit (540).

[0135] The control unit (or controller) (540) controls the overall operations of the base station. For example, the control unit (540) transmits and receives signals through the wireless communication unit (510) or through the backhaul communication unit (520). Additionally, the control unit (540) writes and reads data to and from the storage unit (530). Furthermore, the control unit (540) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (540) may include at least one processor.

[0136] The configuration of the base station shown in FIG. 5 is merely one example of a base station, and the examples of base stations for performing various embodiments of the present disclosure are not limited to the configuration shown in FIG. 5. That is, depending on various embodiments, some configurations may be added, deleted, or changed.

[0137] In FIG. 5, the base station is described as a single entity, but the present disclosure is not limited thereto. A base station according to various embodiments of the present disclosure may be implemented to form an access network having a distributed deployment as well as an integrated deployment. According to one embodiment, the base station may be distinguished into a central unit (CU) and a digital unit (DU), wherein the CU is implemented to perform upper layer functions (e.g., radio link control (RLC), packet data convergence protocol (PDCP), and radio resource control (RRC)), and the DU is implemented to perform lower layer functions (e.g., medium access control (MAC), physical (PHY)). The DU of the base station may form beam coverage on a radio channel.

[0138] FIG. 6 illustrates an example of the configuration of a network entity in a wireless communication system according to embodiments of the present disclosure. The network entity exemplified in FIG. 6 can be understood as a configuration thereof when the network entity is configured as hardware. Here, the network entity may include an AMF, UPF, SMF, PCF, NEF, or AF, etc., according to various embodiments of the present disclosure. Terms such as '...part', '...unit', etc. used below refer to a unit that processes at least one function or operation, and may be implemented in hardware or software, or a combination of hardware and software.

[0139] Referring to FIG. 6, the network entity may include a communication unit (610), a storage unit (620), and a control unit (630).

[0140] The communication unit (610) performs functions for transmitting and receiving signals through a wireless channel. More specifically, the communication unit (610) can transmit and receive signals. To this end, the communication unit (610) may include at least one transceiver. Accordingly, all or part of the communication unit (610) may be referred to as a 'transmitter', a 'receiver', or a 'transmitter / receiver'. Furthermore, in the following description, transmission and reception performed through a wireless channel are used to mean that processing as described above is performed by the communication unit (610).

[0141] The storage unit (620) stores data such as basic programs, application programs, and configuration information for the operation of network entities. The storage unit (620) may be composed of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. Additionally, the storage unit (620) provides the stored data upon request from the control unit (630).

[0142] The control unit (or controller) (630) controls the overall operations of the network entity. For example, the control unit (630) transmits and receives signals through the communication unit (610). Additionally, the control unit (630) writes and reads data to and from the storage unit (620). Furthermore, the control unit (630) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (630) may include at least one processor. The control unit (630) may include at least one processor or microprocessor, or may be part of a processor. The control unit (630) may include various modules for performing communication. According to various embodiments, the control unit (630) may control the network entity to perform operations according to various embodiments.

[0143] The configuration of the network entity illustrated in FIG. 6 is merely an example, and the examples of terminals performing various embodiments of the present disclosure are not limited to the configuration illustrated in FIG. 6. That is, depending on various embodiments, some configurations may be added, deleted, or changed.

[0144] In one embodiment of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system comprises: receiving at least one information related to a multiplexed service data flow, such as a Multi-Modal Service ID (MMSID) transmitted from an AF, a Multi-Modal Service Support Indication for multiplexed service data flow, service requirement information per media flow, and / or QoS monitoring requirements per media flow; determining service support for media flows having different media characteristics within the multiplexed service data flow through one or more QoS flows based on the service requirement information per media flow received from the AF and the network operator's policy, network status information, etc.; determining whether to support multi-modal service when providing a service using one or more QoS flows for the multiplexed service data flow based on separate Multi-Modal Service ID or Multi-Modal Service Support Indication information per media flow and the network operator's policy, network status information, etc.; and checking whether each QoS flow for the media flow that requested the multi-modal service has been created to provide the multi-modal service A step of determining supported QoS flows, a step of creating a QoS monitoring policy to request the execution of monitoring operations for QoS flows per media flow that requested multimodal service,If, during the operation to create a QoS monitoring policy, the Threshold of Delay Difference between Media Flows required between Media Flows is transmitted from the AF to the PCF, or if it is decided to perform a QoS monitoring operation utilizing the Threshold of Delay Difference between Media Flows based on pre-configured information within the PCF, a step of generating binding-related information between the media flows (e.g., Threshold of Delay Difference between Media Flows per binding id, binding information (e.g., id) between the media (QoS) flows); a step of performing an operation to create / update a PCC rule containing a QoS monitoring policy and binding information between media flows to support multimodal services considering multiplexed service data flows; and, in the PCF, media flow information supporting multimodal services (list of accepted media flows for supporting multi-modal service) and / or, if the AF does not generate separate multimodal service support request information (e.g., Multi-modal Service ID and / or Multi-modal service support indication for multiplexed service flow), the PCF independently [manages] according to the operator's policy, etc. If modal service support is decided, the multi-modal service ID (when generating a multi-modal service ID in PCF),The method may include a step of transmitting a result related to a multimodal service request (Result of the MMS for multiplexed service data flow) to the AF via the NEF, which includes at least one piece of information from a multimodal service ID request message (when providing a multimodal service using a multimodal service ID generated by the AF).

[0145] In one embodiment of the present disclosure, a method performed by a Session Management Function (SMF) entity in a wireless communication system comprises: receiving a PCC rule including binding information between a QoS monitoring policy and a media flow for supporting a multimodal service considering multiplexed service data flows from a PCF; generating a QoS monitoring policy within a UPF based on the binding information between the QoS monitoring policy and the media flow received from the PCF; transmitting an N4 rule including the generated QoS monitoring policy for each media flow within the UPF to the UPF; receiving a report from the UPF regarding whether an event (e.g., exceed the threshold of delay difference between Media Flows) has occurred and related information when a reporting condition within the QoS monitoring policy for each media flow considering a multiplexed service data flows is satisfied; transmitting the QoS monitoring report information received from the UPF to the PCF; receiving a PCC rule updated based on the QoS monitoring report information from the PCF; and requesting a QoS monitoring operation within the RAN to the RAN and / or supporting a scheduling operation considering a multimodal service. It may include a step of transmitting N2 SM information including at least one of binding information between media flows and QoS monitoring policies per media flow.

[0146] In one embodiment of the present disclosure, an apparatus and a method capable of effectively providing services in a wireless communication system may be provided. The technical problems to be solved by the present disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood from the present disclosure by those skilled in the art to which the present disclosure pertains.

[0147] In one embodiment of the present disclosure, an apparatus and a method capable of effectively providing services in a mobile communication system may be provided. The technical effects according to one embodiment of the present disclosure are not limited to the effects described in the present disclosure, and other effects not described in the present disclosure will be clearly understood by those skilled in the art from the detailed description of the present disclosure.

[0148] It should be noted that the aforementioned configuration diagrams, exemplary diagrams of control / data signal transmission methods, exemplary diagrams of operation procedures, and configuration diagrams are not intended to limit the scope of the rights of the present disclosure. That is, all components, entities, or steps of operation described in the embodiments of the present disclosure should not be interpreted as essential components for the implementation of the disclosure, and may be implemented within a scope that does not impair 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.

[0149] 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 the program code stored in the memory device using a processor or CPU (Central Processing Unit) and executing it.

[0150] Various components of entities, base stations, or terminal devices and modules described in this disclosure may be operated using hardware circuits, such as, for example, complementary metal oxide semiconductor-based logic circuits, firmware, software, and / or a combination of 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.

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

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

[0153] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (read-only memory), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

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

[0155] In the specific embodiments of the present disclosure described above, the components included in the disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0156] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. A method performed by a PCF (policy control function) entity in a wireless communication system, A step of receiving information about a service data flow including one or more media flows from an AF (application function) entity; A step of determining QoS (quality of service) flows for each of the above one or more media flows; A step of identifying one or more media flows that support a multi-modal service based on information regarding the above service data flow; A step of generating PCC (policy and charging control) rules including a QoS monitoring policy for the above QoS flows; and The method includes the step of transmitting the above PCC rules to an SMF (session management function) entity, and Information regarding the above service data flow includes a method comprising QoS monitoring requirements for each of the one or more media flows.

2. The method of claim 1, wherein the information regarding the service data flow further includes a multi-modal service ID (identifier) ​​for one or more media flows.

3. In claim 1, the method is, Generate a multi-modal service ID for one or more of the above media flows; or The method includes the step of sending a message to the AF entity to request a multi-modal service ID for the one or more media flows, The above multi-modal service ID is a method included in the above PCC rules.

4. In claim 3, the method is, A step of determining multi-modal service support between one or more of the above media flows; and A method further comprising the step of determining the number of QoS flows for each of the one or more media flows.

5. The method of claim 1, wherein the QoS flows are determined based on the multi-modal service characteristics of the service data flow.

6. In claim 1, the method is, A step of receiving a message from the above SMF entity for a QoS monitoring report based on the above PCC rules; and A method further comprising the step of updating QoS parameter information for the QoS flows based on the message for the QoS monitoring report.

7. A method according to claim 1, wherein the PCC rules include at least one of threshold information for delay time between one or more media flows, binding information between one or more media flows, or mapping information for QoS flows.

8. In a PCF (policy control function) entity in a wireless communication system, At least one processor; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the PCF entity: Receive information about a service data flow including one or more media flows from an AF (application function) entity, and Determine QoS (quality of service) flows for each of the above one or more media flows, and Based on information regarding the above service data flow, identify one or more media flows that support a multi-modal service, and Create PCC (policy and charging control) rules including QoS monitoring policies for the above QoS flows, and Instruct the SMF (session management function) entity to transmit the above PCC rules, and Information regarding the above service data flow is a PCF entity including QoS monitoring requirements for each of the one or more media flows.

9. The information for the service data flow of claim 8, wherein the PCF entity further comprises a multi-modal service ID (identifier) ​​for one or more media flows.

10. In claim 8, the instructions are such that the PCF entity: Generate a multi-modal service ID for one or more of the above media flows; or Send a message to the above AF entity to request a multi-modal service ID for the one or more media flows, and The above multi-modal service ID is a PCF entity included in the above PCC rules.

11. In claim 10, the instructions are such that the PCF entity: Determining multi-modal service support between one or more of the above media flows, and A PCF entity that determines the number of QoS flows for each of the one or more media flows.

12. In claim 8, the QoS flows are PCF entities determined based on the multi-modal service characteristics of the service data flow.

13. In claim 8, the instructions are such that the PCF entity: Receive a message from the above SMF entity for a QoS monitoring report based on the above PCC rules, and A PCF entity that updates QoS parameter information for the QoS flows based on the message for the above QoS monitoring report.

14. The PCF entity of claim 8, wherein the PCC rules comprise at least one of threshold information for delay time between one or more media flows, binding information between one or more media flows, or mapping information for QoS flows.

Images