Method and apparatus for dynamic policy application in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a terminal in a wireless communication system comprises the steps of: acquiring, from a first entity, service access information for providing a media service; transmitting, to the first entity, a message for requesting a policy template, wherein the message comprises identification information of the terminal based on the service access information; and receiving, from the first entity, information about the policy template based on the identification information, wherein the first entity comprises a service application provider entity or a media application function (AF) entity, and the information about the policy template comprises at least one of a quality of service (QoS) specification or a charging specification.

Description

Method and device for dynamic policy application in wireless communication systems

[0001] The present disclosure relates to a method and apparatus for dynamically applying a packet processing policy of a media service in a mobile (or wireless) communication system.

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

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

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

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

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

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

[0008] The present disclosure provides a method and device for dynamic network resource allocation and network policy application for media service support in a mobile (or wireless) communication system.

[0009] According to one embodiment of the present disclosure, a method of a service control device for transmitting a media service in a mobile (or wireless) communication system may include: a step of receiving media service configuration information from an application service provider; a step of receiving QoS requirements for each packet flow for a media service from a user terminal or a server; and a step of providing network configuration information for the media service to a network.

[0010] One embodiment of the present invention provides a device and method capable of effectively providing a service in a wireless communication system.

[0011] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0012] FIG. 1 is a conceptual diagram illustrating a 5G system structure (5G system, 5GS) for media services in a wireless communication system according to one embodiment of the present disclosure.

[0013] FIG. 2 is a conceptual diagram illustrating a conceptualized media transmission structure for providing media services in a wireless communication system according to one embodiment of the present disclosure.

[0014] FIG. 3 is a diagram illustrating an example of a method for providing an adaptive media streaming service in a wireless communication system according to one embodiment of the present disclosure.

[0015] FIG. 4 is a diagram illustrating an example of a media service provision procedure in a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 5 illustrates a configuration of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 6 illustrates a configuration of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 7 illustrates a configuration of a network entity in a wireless communication system according to one embodiment of the present disclosure.

[0019] In describing the present invention below, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description will be omitted.

[0020] For the same reason, some components in the attached drawings are exaggerated, omitted or schematically illustrated.

[0021] The operating principles of the present disclosure are described in detail with reference to the attached drawings. The terms described below are defined based on the functions described in the present disclosure. Since the terms described in the present disclosure may vary depending on the intent or custom of the user or operator, their definitions should be determined based on the overall content of the present disclosure.

[0022] The terms used in this disclosure to refer to network entities or network functions, terms used to refer to messages, terms used to refer to identification information, and the like are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms used to refer to objects with equivalent technical meanings may be used.

[0023] For convenience, the present invention uses terms and names defined in the 5G system standards, but is not limited by the terms and names, and can be equally applied to systems conforming to other standards.

[0024] The operating principle of the present invention is described in detail with reference to the attached drawings below.

[0025] In describing embodiments of the present disclosure, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure may be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.

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

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

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

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

[0030] Here, the term '~ unit' used in this embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to regenerate one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, 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 '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in the embodiment, '~bu' may include one or more processors.

[0031] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0032] For convenience of explanation, this disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) LTE (3rd Generation Partnership Project Long Term Evolution) standards and the 3GPP 5G standards. However, the present invention is not limited by these terms and names and can be equally applied to systems conforming to other standards.

[0033] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, the attached drawings of the present disclosure are provided to aid understanding of the present disclosure, and it should be noted that the present invention is not limited to the forms or arrangements illustrated in the drawings.

[0034] According to one embodiment, a method of a service control device for supporting media streaming in a mobile communication system may include a step of receiving media streaming service configuration information from an application service provider, a step of receiving detailed information on packet flow for a media streaming service from a user terminal or a media streaming server, and a step of providing network configuration information for the media streaming service to a network.

[0035] It can be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce an article of manufacture that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions can also be installed on a computer or other programmable data processing device, a series of operations are performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the operations for performing the functions described in the flowchart block(s) can also provide operations for performing the functions described in the flowchart block(s).

[0036] Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for performing a specific logical function(s). It should also be noted that the functions described in the blocks of the embodiments may occur out of order. For example, two blocks depicted in succession may actually be executed substantially simultaneously (e.g., in parallel), or the blocks may sometimes be executed in reverse order, depending on the corresponding function.

[0037] In the present disclosure, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Although 5G (NR (new radio)) or a 5G (NR) system may be described below as an example, embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. In addition, the present disclosure may also be applied to other communication systems (e.g., LTE (long term evolution) system, 3G system) through some modifications without significantly departing from the scope of the present disclosure at the judgment of a person having skilled technical knowledge.

[0038] Hereinafter, embodiments of the present invention will be described in detail with the attached drawings.

[0039] The present disclosure relates to a method and device for allocating network resources and applying packet processing policies for media data transmission in a mobile (or wireless) communication system. For example, the present disclosure relates to a method and device for dynamically selecting network QoS (Quality of Service) parameters that satisfy media transmission characteristics and transmitting the same to a network control device to perform resource allocation and packet processing policy setting for a user plane network device located along a media transmission path.

[0040] In one embodiment, a media service may include various media components, each of which may have different transmission requirements. For example, a real-time communication service may require a bit rate of tens of kbps for voice data, which is acceptable across most networks, but requires a packet delay of less than 100 ms for smooth service provision. For another example, a high-resolution video service may require a bit rate of tens of Mbps, but considering the size of the playback buffer, a packet delay of approximately 300 ms may be acceptable. Furthermore, to adapt to changing network conditions, a media service provider may provide the same content in multiple representations by changing parameters such as resolution. Service consumers can select a representation appropriate for the current network conditions and consume the content. Furthermore, a media service provider may support network usage fees that media service consumers must pay for specific content, depending on the media service provider's policies or the media service consumer's subscription terms.

[0041] A user terminal consuming a service can predict network conditions based on the functions provided by a content transmission protocol or the results of buffer management for content playback, and select an optimal phenotype based on this. However, in cases where network conditions are variable, frequent changes in phenotypes may deteriorate the user experience, and changing to a phenotype requiring a higher bit rate may not be easy. Therefore, the present disclosure provides a media service control technology that can request QoS support appropriate to the phenotype of the content being consumed from the network. More specifically, the present disclosure describes procedures for provisioning a transmission session for media data transmission, establishing a transmission session, and dynamic QoS requests, as well as the signaling for these procedures.

[0042] The devices and methods according to various embodiments of the present disclosure described below enable a media service provider to provide QoS that takes into account the characteristics of media data when providing a media service through a user terminal connected to a mobile communication system.

[0043] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0044] Additionally, for convenience, the following description uses terms and names defined in the 5G system standards. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0045] A wireless communication system according to various embodiments of the present disclosure may be, for example, a 5G system (5GS). The 5G system may be composed of a 5G radio access network (NG-RAN) and a 5G core network (5GC). 5GS interworks with existing LTE and may also be connected to non-3GPP radio access technologies such as Wi-Fi. 5GC is located between the NG-RAN and an external packet data network (PDN: Public Data Network) and may provide various types of data services, including voice, to users. Control plane components of 5GC may be regarded as (identified or determined) virtualized network functions (VNFs), and communication between VNFs may be regarded as (identified or determined) consuming services by other VNFs through an application programming interface (API) supported by a VNF providing a service. The API-based communication interface between VNFs is called a Service Based Interface (SBI).

[0046] FIG. 1 is a conceptual diagram illustrating a 5G system structure (5G system, 5GS) for media services in a wireless communication system according to the present disclosure.

[0047] Referring to FIG. 1, 5GS according to one embodiment includes a user equipment (UE) (101), an NG-RAN (102) including a base station, a user plane function (UPF) device (or entity) (103), an access and mobility management function (AMF) device (111), a session management function (SMF) device (112), a policy control function (PCF) device (113), a network exposure function (NEF) device (114), an NF repository function (NRF) device (115), an authentication server function (AUSF) device (116), a unified data management (UDM) device (117), a media application function (Media AF) device (121), and / or a media application server (Media AS) device. (122) may be included. Of course, the entities or devices included in 5GS are not limited to the examples, and 5GS may include fewer or more configurations than those illustrated in FIG. 1. In addition, each device may be referred to as a network entity, a network function, or a network function apparatus.

[0048] In one embodiment, each network function (NF) of the 5GS is described as a “network entity” or “network function” itself. However, those skilled in the art will appreciate that a network function (NF) and / or an NF device may be implemented in one or more specific servers, or two or more NFs performing the same operation may be implemented in a single server.

[0049] In one embodiment, one NF or two or more NFs may be implemented as a network slice, depending on the case. A network slice may be created based on a specific purpose. For example, a network slice may be configured for a group of subscribers to provide the same type of service to the specific group of subscribers, for example, based on a maximum transmission rate and data usage, and / or a guaranteed minimum transmission rate. In addition, a network slice may be implemented for various purposes. Since network slices are obvious to those skilled in the art, a description thereof may be omitted.

[0050] According to one embodiment, FIG. 1 illustrates interfaces between each node. A Uu interface may be used between a UE (101) and an NG-RAN (102), an N2 interface may be used between an NG-RAN (102) and an AMF (111), an N3 interface may be used between an NG-RAN (102) and an UPF (103), an N4 interface may be used between an SMF (112) and an UPF (103), and an N6 interface may be used between the UPF (103) and a Media AF (121) and a Media AS (122) located in a DN (Data Network). Since the above-described interfaces are defined in the 3GPP standard, further description is omitted. The interfaces between the Media AF (121) and the Media AS (122) and the UE are described in the media architecture described below.

[0051] FIG. 2 is a conceptual diagram illustrating a conceptualized media transmission structure for providing media services in a wireless communication system according to the present disclosure.

[0052] Referring to Figure 2, the main functional elements of the conceptualized media transmission architecture are as follows:

[0053] - Media AF (121): Application Function for providing media services

[0054] - Media AS (122): Application Server for media transmission

[0055] - Media Client (210): UE internal function for media transmission. The media client (210) may include the following sub-functions as logical functions.

[0056] -- Media Session Handler (211): Internal function of UE (200) that communicates with Media AF (121) to establish and control media transmission session.

[0057] -- Media Access Function (212): An internal function of the UE (200) that communicates with the Media AS (122) for access to and transmission of media content. The Media Access Function may have detailed functions such as, for example, a media transmission protocol, a media codec, and / or a metadata processor.

[0058] According to one embodiment, the media session handler (211) and the media access function (212) are shown to provide APIs to each other through the M11 interface and to the media-aware application (220) through the M6 ​​and M7 interfaces, respectively, but this is only an example. For example, depending on the implementation choice, the functions of the above-described element functions may be provided by the media-aware application (220) or other components of the UE (200), in which case the M11, M6, and M7 interfaces may not exist.

[0059] - Media-aware Application (220): An application running on a UE (200) that can utilize at least one of the APIs (Application Program Interfaces) provided by a media session handler (211) or a media access function (212) for media transmission. For example, a media-aware application may be replaced with the term application for identifying media, application related to media, or application for media.

[0060] According to one embodiment, components of the conceptualized media transmission structure described above may communicate with each other using at least one of the following interfaces, but are not limited to the following examples.

[0061] - M1: An interface between a media application provider (280) and Media AF (121) that can be used for provisioning media transmission service configuration.

[0062] - M2: An interface between a media application provider (280) and Media AS (122) that can be used to provide media data to or receive media data from Media AS (122).

[0063] - M3: An interface between Media AF (121) and Media AS (122), which can be used for configuration of Media AS (121) or media session processing related to media transmission.

[0064] - M4: An interface between the media access function (212) of the UE and the Media AS (122), which can be used for the media access function (212) to receive media data from the Media AS (122) or to transmit media data to the Media AS (122).

[0065] - M5: An interface between the UE's media session handler (211) and Media AF (121) that can be used for media session processing related to media transmission.

[0066] - M6: An interface between a media awareness application (220) and a media session handler (211) that can be used to set up the media session handler (211).

[0067] - M7: An interface between a media recognition application (220) and a media access function (212) that can be used to control the media access function (212).

[0068] - M8: Can be used to control media application service logic as an interface between UE's media awareness application (220) and media application provider (280).

[0069] - M9: An interface between the first and second instances of Media AF (121), which can be used for linking between Media AF instances.

[0070] - M10: An interface between the first and second instances of Media AS (122), which can be used for media relay and processing between Media AS instances.

[0071] - M11: An interface between a media session handler (211) and a media access function (212), which can be used to set up a media session handler (211) or a media access function (212).

[0072] According to one embodiment, the above-described Media AF (121) and Media AS (122) are functions located in the data network (250) and can communicate with the UE (200) through the N6 interface defined in 5GS. A function located in an operator's external network (External DN) (for example, Media AF (121)) can communicate with a 5G network function through the NEF (114) using the N33 interface, and a function located in an operator's trusted network (Trusted DN) (for example, Media AF (121)) can communicate directly with a 5G network function. According to one embodiment, the Media AF (121) located in the operator's trusted network can communicate with the PCF (113) using the N5 interface. The communication between the Media AF (121) and the NEF (114) or PCF (113) may be a network service consumption process using an API provided by the NEF (114) or PCF (113). For example, the Media AF (121) may request traffic processing policy settings including QoS parameters for a media transmission session between the media access function (212) of the UE (200) and the Media AS (122) using the Nnef_AFSessionWithQoS service provided by the NEF (114) or the Npcf_PolicyAuthoriztion service provided by the PCF (113). For example, the Media AF (121) may subscribe to a network event notification service and be notified or informed that a network event has occurred when a related situation occurs in the network. For example, an event notification may be delivered directly to Media AF (121) from a network function associated with the event (e.g., PCF (113) or UPF (103)) or may be delivered via NEF (114).

[0073] Media services according to various embodiments of the present disclosure may include at least one of the following three main scenarios, although the examples below are not limited thereto.

[0074] - Downlink Streaming: The network provides media and the UE performs the role of consuming the media (e.g., the UE performs the role of outputting the received media content (or information associated with the media)).

[0075] - Uplink Streaming: The UE provides media and the network performs the role of consuming the media (e.g., the network collects media content (or information associated with the media) and transmits it to other devices (e.g., other UEs, network entities, base stations)).

[0076] Real-Time Communication (RTC): Media is exchanged between RTC endpoints. An RTC endpoint can be a UE or a network (for example, a network located in the media transmission path between a first UE and a second UE can collect media content (or information associated with the media) and process it (e.g., codec conversion) before delivering it.)

[0077] The functions and interfaces of the conceptualized media transmission structure illustrated in FIG. 2 may provide different functions depending on the scenario described above. For example, the M4 interface described above may be used to transmit and / or receive media data between a UE (200) and a Media AS (122) in downlink streaming and uplink streaming services. In addition, the M4 interface described above may be used to transmit and / or receive media data between a UE (200) and an RTC AS (122) or between a UE (200) and a second UE (not shown) in an RTC service.

[0078] Adaptive media services according to the present disclosure can modify transmission and / or playback requirements of media data even while the service is being provided, taking into account the network and / or media consumption device conditions. For example, the adaptive media service may be an adaptive media streaming service in which a client downloads and plays media data stored on a server, or an adaptive real-time communication service in which service participants (devices) exchange media data generated in real time.

[0079] FIG. 3 is a diagram illustrating an example of a method for providing an adaptive media streaming service in a wireless communication system according to an embodiment of the present disclosure. In the adaptive media streaming service according to the present disclosure, media content may have a representation according to a requested bit rate, and media data for each representation may be divided into chunks of a certain unit and stored in a media server. A client consuming the adaptive media streaming service may determine the representation of the chunk to be requested next by considering the network conditions and the client's own circumstances, and may request the determined representation from the media server. For example, the network conditions may include at least one of the download speed of the chunk or the available bit rate. For example, the client's circumstances may include at least one of the client's video playback capability (e.g., the CPU (Central Processing Unit) / RAM (Random Access Memory) load status), the client's screen resolution, or the screen situation (e.g., whether it is in full-screen mode or in background playback).

[0080] In one embodiment, the media server (310) may generate three phenotypes for the same content to provide an adaptive media streaming service. For example, the resolution and required bit rate of each phenotype may be given as shown in [Table 1] below. Of course, the present invention is not limited to the following example.

[0081]

[0082] An adaptive media streaming service provider may provide a client with a service description that includes transmission and / or playback requirements for each phenotype, such as the resolution and required bit rate shown in Table 1, for example. The client may select a phenotype to which a chunk to be downloaded and played next belongs based on the transmission and / or playback requirements for each phenotype included in the service description, taking into account network and / or client conditions. In one embodiment, the client (320) may download and play six chunks belonging to phenotype A (311) at the time of service initiation, and then sequentially download and play six chunks each belonging to phenotype B (312) and phenotype C (313). If the download or playback of chunks belonging to phenotype C (313) is not smooth, the client may download and play chunks belonging to phenotype B (312) again.

[0083] In an adaptive real-time communication service according to the present disclosure, a service participant (device) that receives and plays media data may request a change in media generation parameters from a service participant (device) that generates and transmits media data, taking into account the circumstances of at least one of a network, a media reception device, or a media playback device. For example, the media generation parameters may include resolution and a required bit rate. In an adaptive real-time communication service according to the present disclosure, a service participant (device) that generates and transmits media data may change the media generation parameters, taking into account the circumstances of a network, a media generation or media transmission device, and a request from at least one of a media reception device or a media playback device. At this time, the changed media parameters may be notified (or announced) to the media reception and / or media playback devices. In addition, negotiation regarding the media parameters to be changed may be performed between real-time communication service participants (devices) before applying the actual change in media generation parameters. For example, the parameter request, notification, and / or negotiation may be performed using SDP (Session Description Protocol) exchange or RTCP (RTP (Real-Time Protocol) Control Protocol).

[0084] FIG. 4 is a diagram illustrating an example of a media service provision process in a wireless communication system according to one embodiment of the present disclosure. Referring to FIG. 4, media services can be provided to users through the following procedures. However, the following procedures are merely examples, and at least one of the following procedures may be omitted or other procedures may be added.

[0085] 1. Service Provisioning: The media application provider (280) and the Media AF (121) can establish a provisioning session and perform function configuration for a media service. The function for the media service may include a dynamic policy invocation, and the provisioning information for the dynamic policy request function configuration may include policy template information for the dynamic policy request. For example, a policy template according to an embodiment of the present disclosure may include a policy template resource identifier and an external reference that can be referenced in external metadata related to a media transmission session. For example, a policy template according to an embodiment of the present disclosure may further optionally include provisioning information related to at least one of a QoS specification for a media transmission session and a charging specification.

[0086] 2. Media AS setting: Media AF (121) can set Media AS (122) based on provisioning information. However, step 2 may be omitted.

[0087] 3. Service Announcement: A media application provider (280) may transmit service announcement information to a media-aware application (220) running on a user device. The service announcement information according to the present disclosure may include at least one of service access information or information regarding a path for obtaining service access information. The service access information may include at least one of an associated provisioning session identifier or configuration information for a dynamic policy request.

[0088] 4. Start Media Service: A media-aware application (220) can request media processing for a media service selected by a user from a media client (210). At this time, the service access information or a path for obtaining the service access information can be transmitted to the media client (210).

[0089] 5. Media Session Configuration: If the media client (210) knows a path through which service access information can be obtained, it can obtain service access information using the path through which service access information can be obtained.

[0090] 6. Establish Transport Session: The media client (210) can establish a media transport session for media transmission with the Media AS or RTC endpoint (122). In the adaptive streaming service according to the present disclosure, the process of establishing the media transport session may include a process of obtaining a service description. The service description may include at least one of transmission requirements, playback requirements, media data acquisition information (e.g., URL information), or associated policy template information for each expression type of media content. In the real-time communication service according to the present disclosure, the process of establishing the media transport session may include a process of negotiating connection information (e.g., an IP address and a port number) and media-related detailed parameters for exchanging media data between RTC endpoints (e.g., an SDP Offer / Answer process). In a real-time communication service according to the present disclosure, an RTC terminal can obtain associated policy template information for media-related detailed parameters from at least one of a media application provider during the service announcement acquisition process of step 3 described above, another RTC terminal during the media-related detailed parameter negotiation (e.g., SDP Offer / Answer process) step described above, or a signaling server. The associated policy template information according to the present disclosure can be one or a combination of two or more of a policy template resource identifier, an external reference, and a QoS specification identifier.

[0091] 7. Dynamic policy invocation: The media client (210) may request the Media AF (121) to set a dynamic policy to be applied to a media transmission session. The dynamic policy setting request may include at least one of a provisioning session identifier, an application flow description, or a policy template identifier. The policy template identified by the policy template may be determined based on the associated policy template information acquired in step 6. For example, if the service description of an adaptive streaming service provides associated policy template information for each expression type of content, the media client may use the associated policy template information to determine the policy template to be used when requesting dynamic policy setting for the selected expression type. For example, if associated policy template information for a media parameter is given in an adaptive real-time communication service, similarly to the case of an adaptive streaming service, the media client (210) may use the associated policy template information to determine the policy template to be used when requesting dynamic policy setting for the selected media parameter. For example, when the media client (210) does not know the policy template information associated with the transmission and / or playback requirements of the media content, the media client (210) may perform a dynamic policy setting request by selecting a policy template that satisfies the transmission and / or playback requirements of the media content to be selected. The policy template details for selecting a policy template that satisfies the transmission and / or playback requirements of the content by the media client (210) according to the present disclosure may be obtained using information included in the service access information or provided as the service access information.

[0092] 8. Media traffic policy request: Media AF (121) can request a media transmission traffic processing policy to PCF (113) or NEF (114).

[0093] 9. Confirm QoS Allocation: The media client (210) can confirm the result of the dynamic policy setting requested to Media AF (121). The policy setting result confirmation message may include at least one of information about the dynamic policy setting status (e.g., Accepted, Rejected, etc.) or guidance about the dynamic policy (e.g., bit rate, whether QoS is supported by each media stream, etc.).

[0094] 10. Media Contents: The media client (210) can set internal parameters and initiate media transmission or reception according to the response of Media AF (121).

[0095] In the above-described embodiment, the media client (210) requested dynamic policy setting to the Media AF (121), but the Media AS (122) may request dynamic policy setting according to the policy of the mobile (or wireless) communication service provider or the request of the media application provider (280).

[0096] Adaptive media services according to the present disclosure can change the transmission and / or playback requirements of media data even while the service is being provided, taking into account the network and / or media consumption device conditions. In this case, the processes from steps 7 to 9 described above may be performed prior to transmitting and / or receiving media data with altered media content expression or media parameters.

[0097] The provisioning procedure for an adaptive media service according to the present disclosure may include creating, acquiring, and updating Provision Session resources using Rest APIs, etc. Table 2 below illustrates an example of a Provisioning Session resource according to an embodiment of the present disclosure. Of course, the present disclosure is not limited to the following example.

[0098]

[0099] A Provisioning Session resource according to an embodiment of the present disclosure may include resource identifiers associated with a Policy Template. The following [Table 3] illustrates an example of a Policy Template resource according to an embodiment of the present disclosure. However, the present disclosure is not limited to the following example.

[0100]

[0101] The qoSSpecification attribute of the Policy Template resource according to the present disclosure may be an array of objects having the M1QoSSpecification data format, and each object may have at least one of the following attributes, but is not limited to the following examples.

[0102] - componentReference: An identifier representing the associated QoS Specification.

[0103] - qosReference: An identifier representing QoS parameters agreed upon in advance between the service provider and the network.

[0104] - downlinkQosSpecification: QoS Specification for the downlink stream, which may include at least one of maximum bit rate, maximum authorized bit rate, minimum packet loss rate, maximum packet loss rate, maximum packet error rate, or packet delay.

[0105] - uplinkQosSpecification: QoS Specification for uplink stream, which may include at least one of maximum bit rate, maximum authorized bit rate, minimum packet loss rate, maximum packet loss rate, maximum packet error rate, or packet delay.

[0106] The chargingSpecification attribute of the Policy Template resource according to the present disclosure may provide information related to sponsored connectivity. Sponsored connectivity may, for example, allow a third party, referred to as a sponsor, to pay traffic charges for specific content consumed by a mobile communication subscriber. The chargingSpecification attribute of the Policy Template resource according to the present disclosure may follow the ChargingSpecification data format, and the ChargingSpecification data format may optionally include at least one of the following attributes. Of course, the present disclosure is not limited to the following examples.

[0107] - sponsorId: Identifier of the sponsor supporting sponsored connectivity.

[0108] - sponsoringStatus: A value indicating whether sponsored connectivity is enabled. For example, it can be an enumerated data type with one of the values ​​{SPONSOR_DISABLE, SPONSOR_ENABLED}. If omitted, sponsored connectivity is considered enabled (identified or determined).

[0109] - permittedUes: A list of users for whom sponsored connectivity is supported. If permittedUes exists, it may include at least one member. However, omitting permittedUes may mean that sponsored connectivity is supported for all users. The member may be given as information or a combination of information that can identify the user. For example, it may be one or a combination of two or more of the following: Generic Public Subscription Identifier (GPSI), Subscription Permanent Identifier (SUPI), Subscription Concealed Identifier (SUCI), Permanent Equipment Identifier (PEI), 5G Globally Unique Temporary Identifier (5G-GUTI), and third-parity user ID.

[0110] A user terminal according to the present disclosure may receive service access information directly included in service guidance information from an application service provider, or may obtain service access information from Media AF using a service access information acquisition path included in service guidance information provided by the application service provider. A user terminal according to the present disclosure may provide user terminal identification information when obtaining service access information from an application service provider and / or Media AF. For example, the user terminal identification information may be one or a combination of two or more of GPSI, SUPI, SUCI, PEI, 5G-GUTI, and a third-party user ID.

[0111] The application service provider and / or Media AF according to the present disclosure may use the user terminal identification information provided together with the service access information request to select a policy template that can be used by the corresponding terminal, and may include information about the selected policy template in the service access information and provide it to the user terminal. For example, the policy template that can be used by the corresponding terminal may be a policy template that does not include a chargingSpecification attribute, includes a chargingSpecification attribute that is allowed for all users (e.g., chargingSpecification that does not include the permittedUes attribute), or includes a chargingSpecification attribute that indicates that sponsored connectivity is supported for the corresponding user (e.g., chargingSpecification whose permittedUes attribute includes the corresponding user terminal information). If the format of the user terminal identification information provided when requesting service access information is different from the format of the user identification information included in the permittedUes attribute of chargingSpecification, the application service provider and / or Media AF may use information provided by the network service provider to convert the user identification information provided when requesting service access information into the format of the user identification information included in the permittedUes attribute of chargingSpecification, thereby performing a policy template selection procedure.

[0112] Service access information according to an embodiment of the present disclosure may include an associated provisioning session identifier and dynamic policy request configuration information. The dynamic policy request configuration information included in the service access information according to an embodiment of the present disclosure may include at least a portion of an associated policy template or may include a path for obtaining at least a portion of the associated policy template.

[0113] A user terminal according to the present disclosure may provide user terminal identification information when acquiring an associated policy template from a Media AF. The user terminal identification information may be, for example, a combination of one or more of GPSI, SUPI, SUCI, PEI, 5G-GUTI, and a third-party user ID. The Media AF according to the present disclosure may determine whether the corresponding terminal can use the requested policy template using the user terminal identification information provided together with the policy template acquisition request. In addition, the Media AF may provide the requested policy template, in whole or in part, to the user terminal, if available. For example, a policy template that the corresponding terminal can use may be a policy template that does not include a chargingSpecification attribute, includes a chargingSpecification attribute that is allowed for all users (for example, chargingSpecification that does not include the permittedUes attribute), or includes a chargingSpecification attribute that indicates that sponsored connectivity is supported for the corresponding user (for example, chargingSpecification whose permittedUes attribute includes the corresponding user terminal information). If the format of the user terminal identification information provided when requesting service access information is different from the format of the user identification information included in the permittedUes attribute of chargingSpecification, the application service provider and / or Media AF may use the information provided by the network service provider to convert the user identification information provided when requesting service access information into the format of the user identification information included in the permittedUes attribute of chargingSpecification to perform the policy template selection procedure.

[0114] The following [Table 4] is an example of a Service Access Information resource indicating service access information according to an embodiment of the present disclosure. Of course, the present disclosure is not limited to the following example.

[0115]

[0116] A user terminal according to an embodiment of the present disclosure may obtain service access information resources from an application service provider. At this time, the user terminal may provide user terminal identification information to the application service provider. The application service provider according to an embodiment of the present disclosure may use the user terminal identification information provided by the user terminal and / or the user terminal identification information obtained from a function provided by the application service to select a policy template to be included in dynamic policy request configuration information of the service access information (for example, a policy template to be included in the policyTemplateBinding attribute of dynamicPolicyInvocationConfiguration in [Table 4]). The selected policy template may be a policy template determined to be usable by the requesting terminal according to the above-described criteria. The dynamic policy request configuration information according to the present disclosure may include the qoSSpecification attribute and / or the chargingspecification attribute of the selected policy template. At this time, the permittedUes attribute of chargingspecification may be omitted. The dynamic policy request configuration information according to the present disclosure may provide a format of user identification information that the user terminal may include when requesting to obtain a policy template (for example, the ueIDFormat attribute in [Table 4]).

[0117] A user terminal according to an embodiment of the present disclosure can obtain service access information resources from a Media AF. At this time, the user terminal can provide user terminal identification information to the Media AF. The user terminal identification information can be transmitted to the Media AF by a query parameter of a request URL, an http header of an HTTP GET request, or a method defined by an application layer protocol. The Media AF according to an embodiment of the present disclosure can select a policy template to be included in dynamic policy request configuration information of service access information (for example, a policy template to be included in the policyTemplateBinding attribute of dynamicPolicyInvocationConfiguration in [Table 4]) using the user terminal identification information provided by the user terminal and / or the user terminal identification information obtained from a function provided by an application service. The selected policy template may be a policy template determined to be usable by the requesting terminal according to the above-described criteria. The dynamic policy request configuration information according to the present disclosure may include the qoSSpecification attribute and / or the chargingspecification attribute of the selected policy template. At this time, the permittedUes attribute of chargingspecification may be omitted. The dynamic policy request setting information according to the present disclosure can provide a format of user identification information that a user terminal can include when requesting to obtain a policy template (e.g., the ueIDFormat attribute of [Table 4]).

[0118] A user terminal according to the present disclosure can obtain a policy template resource from Media AF. At this time, the target URL of a request for obtaining the policy template resource may include all or part of the policyTemplateId attribute value included in the dynamic policy setting information of the service access information. A policy template resource request according to the present disclosure may include user terminal identification information. The user terminal identification information may be transmitted to Media AF by a query parameter of the request URL, an http header of an HTTP GET request, or a method defined by an application layer protocol. For example, the format of the user terminal identification information of the policy template request according to the present disclosure may be a format provided in the dynamic policy request setting information of the service access information (for example, the ueIDFormat attribute value of the associated policy template). A Media AF according to an embodiment of the present disclosure may determine whether the requested policy template is available to the requesting user terminal based on the above-described criteria, and if the policy template is available, provide all or part of the policy template resource (for example, the qoSSpecification attribute and / or the chargingSpecification attribute) to the requesting user terminal. If the chargingSpecification attribute is provided to the user terminal, the permittedUes attribute of the chargingSpecification attribute may be omitted.

[0119] An adaptive media service according to the present disclosure may include dynamic policy support information associated with each phenotype or media parameter. The dynamic support policy information according to the present disclosure may include at least one of externalReference, policyTemplateId, componentReference, or desiredBitrate information. A user terminal according to an embodiment of the present disclosure may select a policy template and / or QoS specification using the dynamic policy support information when selecting a phenotype or media parameter, and may perform a dynamic policy request based on the selected policy template and / or QoS specification.

[0120] A dynamic policy request according to the present disclosure may include a QoS request for media data transmission. For example, in the following embodiments, the minimum traffic unit for a QoS request may be set to at least one of an application flow, which is a packet flow identified by 5-tuple information consisting of a sending and / or receiving IP address, a sending and / or receiving port number, or a protocol identifier. However, if the application layer protocol used for an actual service can provide subflow identification information constituting the application flow, a QoS request may be made on a subflow basis.

[0121] A dynamic policy request according to an embodiment of the present disclosure may include an identifier of an associated dynamic policy resource and one or more application flow binding information to which the dynamic policy is to be applied. Each application flow binding information may include one or more application flow-related information, and optionally may include a QoS parameter to be applied to the application flow. If a QoS parameter to be applied to the application flow is omitted, Media AF may consider (identify or determine) that the dynamic policy request includes a QoS specification included in an associated policy template or policy template element (e.g., one of the QoS specifications provided as the qoSSpecification attribute of [Table 4]).

[0122] The dynamic policy request procedure for a media service according to the present disclosure may include the process of creating, obtaining, and updating a Dynamic Policy resource using a Rest API, etc. The following [Table 5] illustrates an example of a Dynamic Policy resource according to an embodiment of the present disclosure. Of course, the present disclosure is not limited to the following example.

[0123]

[0124] The applicationFlowBinding attribute of a Dynamic Policy resource according to the present disclosure may include QoS specification-related information. The following [Table 6] illustrates an example of the applicationFlowBinding attribute according to an embodiment of the present disclosure. Of course, the present disclosure is not limited to the following example.

[0125]

[0126] FIG. 5 illustrates a configuration of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0127] A terminal according to one embodiment of the present disclosure may include a processor (530) that controls the overall operation of the terminal, a transceiver (510) including a transmitter and a receiver, and a memory (520). Of course, the terminal is not limited to the above-described examples, and the terminal may include more or fewer components than those illustrated in FIG. 5.

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

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

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

[0131] FIG. 6 illustrates a configuration of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0132] The base station of FIG. 6 may refer to the RAN node or BS described in the embodiments described above.

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

[0134] According to one embodiment of the present disclosure, the transceiver (610) can transmit and receive signals with at least one of a terminal, another base station, or a network entity. The transmitted and received signals can include at least one of control information and data.

[0135] According to one embodiment of the present disclosure, the processor (630) can control the overall operation of the base station to perform any one of the operations described above. Meanwhile, the processor (630), the transceiver (610), and the memory (620) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (630) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (610) can include at least one communication interface for transmitting and receiving signals wired / wirelessly to and from a terminal, another base station, or a network entity.

[0136] According to one embodiment of the present disclosure, the memory (620) can store data such as basic programs, application programs, and setting information for the operation of the corresponding base station. In addition, the memory (620) provides the stored data upon request of the processor (630). The memory (620) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (620). In addition, the processor (630) can perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory (620).

[0137] FIG. 7 illustrates a configuration of a network entity in a wireless communication system according to one embodiment of the present disclosure.

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

[0139] According to one embodiment of the present disclosure, the transceiver (710) can transmit and receive signals with at least one of other network entities, a base station, or a terminal. The signals transmitted and received with at least one of the other network entities, a base station, or a terminal may include control information and data.

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

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

[0142] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission and reception methods, and examples of operational procedures are not intended to limit the scope of the embodiments of the present disclosure. That is, not all of the aforementioned components, entities, or operational steps should be construed as essential components for the implementation of the disclosure, and implementations may be made without detracting from the essence of the disclosure even if only some of the components are included.

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

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

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

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

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

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

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

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

[0151] Electronic devices that implement, operate, and perform various embodiments of the present disclosure may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of the present disclosure are not limited to the aforementioned devices.

[0152] The various embodiments of the present disclosure and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more items, unless the relevant context clearly indicates otherwise. In the present disclosure, each of the phrases "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among the phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0153] The term "module" used in various embodiments of the present disclosure may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be an integrally formed component or a minimum unit or part of a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0154] Various embodiments of the present disclosure may be implemented as software (e.g., a program) including one or more instructions stored in a storage medium (e.g., built-in memory or external memory) readable by a machine (e.g., an electronic device). For example, a processor (e.g., a processor) of the machine (e.g., an electronic device) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, "non-transitory" only means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily in the storage medium.

[0155] According to one embodiment, the method according to various embodiments of the present disclosure may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0156] According to various embodiments, each component (e.g., a module or a program) of the described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In a method performed by a terminal of a wireless communication system, A step of obtaining service access information for providing a media service from a first entity; A step of transmitting a message to the first entity to request a policy template, wherein the message includes identification information of the terminal based on the service access information; and A step of receiving information about a policy template based on the identification information from the first entity, The above first entity includes a service application provider entity or a media AF (application function) entity, and A method wherein the information regarding the above policy template includes at least one of a quality of service (QoS) specification or a charging specification.

2. In paragraph 1, A method wherein the service access information includes at least a portion of an associated policy template or a path for obtaining at least a portion of the associated policy template.

3. In paragraph 1, A method, wherein, if the policy template requested by the terminal is available for the terminal, the information about the policy template includes information about at least a part of the policy template requested by the terminal.

4. In paragraph 1, A method wherein the information about the policy template does not include an attribute of the charging specification, includes an attribute of a charging specification that is allowed for all terminals, or includes an attribute of a charging specification that indicates that sponsored connectivity is supported for the terminal.

5. A method performed by a first entity of a wireless communication system, A step of transmitting service access information for providing media services to a terminal; A step of receiving a message for requesting a policy template from the terminal, wherein the message includes identification information of the terminal based on the service access information; and A step of transmitting information about a policy template based on the identification information to the terminal, The above first entity includes a service application provider entity or a media AF (application function) entity, and A method wherein the information regarding the above policy template includes at least one of a quality of service (QoS) specification or a charging specification.

6. In paragraph 5, A method wherein the service access information includes at least a portion of an associated policy template or a path for obtaining at least a portion of the associated policy template.

7. In paragraph 5, A method, wherein, if the policy template requested by the terminal is available for the terminal, the information about the policy template includes information about at least a part of the policy template requested by the terminal.

8. In paragraph 5, A method wherein the information about the policy template does not include an attribute of the charging specification, includes an attribute of a charging specification that is allowed for all terminals, or includes an attribute of a charging specification that indicates that sponsored connectivity is supported for the terminal.

9. At the terminal: At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor, so that the terminal: Obtain service access information for providing media services from the first entity, A message is transmitted to the first entity to request a policy template, wherein the message includes identification information of the terminal based on the service access information, and To receive information about a policy template based on the identification information from the first entity; The above first entity includes a service application provider entity or a media AF (application function) entity, and A terminal, wherein the information regarding the above policy template includes at least one of a quality of service (QoS) specification or a charging specification.

10. In paragraph 9, A terminal, wherein the above service access information includes at least a portion of an associated policy template or a path for obtaining at least a portion of the associated policy template.

11. In paragraph 9, A terminal, wherein, if the policy template requested by the terminal is available for the terminal, information about the policy template includes information about at least a part of the policy template requested by the terminal.

12. In paragraph 9, A terminal wherein the information about the above policy template does not include an attribute of the above charging specification, includes an attribute of the charging specification that is allowed for all terminals, or includes an attribute of the charging specification that indicates that sponsored connectivity is supported for the terminal.

13. In the first entity: At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor, such that the first entity: Transmit service access information to provide media services to the terminal, Receive a message for requesting a policy template from the terminal, wherein the message includes identification information of the terminal based on the service access information, and To the above terminal, transmit information about a policy template based on the above identification information, The above first entity includes a service application provider entity or a media AF (application function) entity, and A first entity, wherein the information regarding the above policy template includes at least one of a quality of service (QoS) specification or a charging specification.

14. In paragraph 13, A first entity, wherein the service access information includes at least a portion of an associated policy template or a path for obtaining at least a portion of the associated policy template.

15. In paragraph 13, If the policy template requested by the terminal is available for the terminal, the information about the policy template includes information about at least a part of the policy template requested by the terminal, and A first entity, wherein the information about the above policy template does not include an attribute of the above charging specification, includes an attribute of the charging specification that is allowed for all terminals, or includes an attribute of the charging specification that indicates that sponsored connectivity is supported for the terminal.

Images