Method for providing media streaming in wireless communication system and apparatus for providing media streaming in wireless communication system

Abstract

A method according to embodiments may comprise the steps of: collecting metrics by a media session handler of an apparatus for providing media streaming in a wireless communication system; collecting consumption information; and reporting the metrics and the consumption information to a data collection application function (AF). A method according to embodiments may comprise the steps of: receiving metric information and consumption information collected by a media session handler of an apparatus for providing media streaming in a wireless communication system; and switching a content delivery network (CDN) on the basis of the metric information and the consumption information.

Description

Method for providing media streaming in a wireless communication system and device for providing media streaming in a wireless communication system

[0001] The embodiments relate to a method for providing media streaming in a wireless communication system and a device for providing media streaming in a wireless communication system.

[0002] Recently, in mobile communication network environments, technologies have been proposed to utilize the status of User Equipment (UE) or network conditions at the server level to improve the quality of media streaming services. For example, 3rd Generation Partnership Project (3GPP) TS 26.501 defines a procedure in which a UE transmits a UE data report to a data server in a media streaming environment, and the server performs network assistance functions, such as network resource control, transmission path selection, or quality control, based on the reported UE information. Through this structure, the server side can collect the UE's network status, bandwidth, latency, or location information in real time to adaptively adjust streaming quality. However, existing technologies have limitations in responding quickly to dynamic changes in the UE's status or performing granular network control because the UE reporting cycle and reporting items are restricted.

[0003] With the advancement of 5th generation mobile communication (5G) technology, the transmission speed and service quality of mobile networks have significantly improved, leading users to expect to use various multimedia content, such as high-definition video and real-time streaming, more quickly and reliably. To meet these demands, the role of Content Delivery Networks (CDNs) is becoming increasingly important, and Multi-CDN switching technology, which combines the resources of multiple CDN operators to provide an optimal transmission path, is receiving particular attention. However, the current 5G Media Streaming (5GMS) framework defined in standards such as 3GPP TS 26.501 lacks clear definitions regarding switching procedures or algorithms that consider a multi-CDN environment on the 5GMS client side of the UE (User Terminal).

[0004] The method and apparatus according to the embodiments are intended to provide various multimedia content, such as high-definition video and real-time streaming, more quickly and stably depending on the transmission speed and service quality of the mobile network.

[0005] The method and apparatus according to the embodiments provide a configuration that selects the most suitable content transmission path for a terminal in real time by comprehensively considering various factors such as network quality, bandwidth, latency, user location, and content type between each CDN based on Multi-CDN switching.

[0006] The method and apparatus according to the embodiments provide a technology for collecting and analyzing data metric information that changes dynamically according to the connection status between each CDN (external CDN or inter-CDN) in order to efficiently perform such switching in a 5GMS environment.

[0007] The method and apparatus according to the embodiments solve the problem in which data metrics that can be utilized for such switching decisions are absent in current UE-server structures, and provide a configuration that effectively performs the process of a UE selecting or switching to an optimal CDN in a multi-CDN environment.

[0008] However, the scope of rights of the embodiments is not limited to the technical problems described above, and may be extended to other technical problems that a person skilled in the art can infer based on the entire content described.

[0009] A method according to the embodiments may include: collecting a metric by a media session handler of a device providing media streaming in a wireless communication system; collecting consumption information; and reporting the metric and consumption information to a data collection Application Function (AF). A method according to the embodiments may include: receiving metric information and consumption information collected by a media session handler of a device providing media streaming in a wireless communication system; and switching a Content Delivery Network (CDN) based on the metric information and consumption information.

[0010] The method and device according to the embodiments provide various multimedia content, such as high-definition video and real-time streaming, more quickly and stably depending on the transmission speed and service quality of the mobile network.

[0011] The method and apparatus according to the embodiments provide the effect of selecting the most suitable content transmission path for a terminal in real time by comprehensively considering various factors such as network quality, bandwidth, latency, user location, and content type between each CDN based on Multi-CDN switching.

[0012] The method and apparatus according to the embodiments provide the effect of collecting and analyzing data metric information that changes dynamically according to the connection status between each CDN (external CDN or inter-CDN) in order to efficiently perform such switching in a 5GMS environment.

[0013] The method and apparatus according to the embodiments solve the problem in which data metrics that can be utilized for such switching decisions are absent in the current UE-server structure, and provide the effect of effectively performing the process of a UE selecting or switching to an optimal CDN in a multi-CDN environment.

[0014] Drawings are included to further understand the embodiments, and the drawings illustrate the embodiments along with descriptions related to the embodiments. For a better understanding of the various embodiments described below, one must refer to the description of the embodiments below in relation to the following drawings, which include parts corresponding to similar reference numerals throughout the drawings.

[0015] FIG. 1 shows a 5G media streaming architecture within a 5G system according to embodiments.

[0016] FIG. 2 shows a media application function (Media AF) according to embodiments.

[0017] FIG. 3 shows a system design diagram for a UE using multiple CDNs according to embodiments.

[0018] FIG. 4 shows a multi-CDN media transmission structure in 5G and non-5G systems according to embodiments.

[0019] FIG. 5 shows a 5G media streaming architecture according to embodiments.

[0020] FIGS. 6a and FIGS. 6b illustrate a configuration that performs metric collection and reporting functions according to embodiments.

[0021] FIGS. 7a and FIGS. 7b illustrate consumption reporting according to the embodiments.

[0022] FIG. 8 illustrates Downlink Network Assistance according to embodiments.

[0023] FIG. 9 illustrates procedures for downlink media streaming data collection, reporting and exposure according to embodiments.

[0024] FIG. 10 illustrates procedures for downlink media streaming data collection, reporting and exposure according to embodiments.

[0025] FIG. 11 shows a 5G media streaming architecture according to embodiments.

[0026] FIGS. 12a, FIGS. 12b, and FIGS. 12c show reporting parameters according to the embodiments.

[0027] FIGS. 13a and 13b illustrate metric collection and reporting via R2' (CDN switching) through the R2' interface according to the embodiments.

[0028] FIG. 14 illustrates a method according to embodiments.

[0029] FIG. 15 illustrates a method according to embodiments.

[0030] Preferred embodiments of the embodiments are described in detail, and examples thereof are shown in the accompanying drawings. The following detailed description, with reference to the accompanying drawings, is intended to describe preferred embodiments of the embodiments rather than merely embodiments that may be implemented according to the embodiments. The following detailed description includes details to provide a thorough understanding of the embodiments. However, it is obvious to those skilled in the art that the embodiments may be practiced without these details.

[0031] Most terms used in the embodiments are selected from those commonly used in the field, but some terms are chosen at the applicant's discretion, and their meanings are described in detail in the following description as necessary. Accordingly, the embodiments should be understood based on the intended meaning of the terms, rather than their mere names or meanings.

[0032] FIG. 1 shows a 5G media streaming architecture within a 5G system according to embodiments.

[0033] The method and apparatus according to the embodiments include and can perform a client-side CDN switching assistance in multi-CDN scenarios.

[0034] The embodiments relate to a method for a client (e.g., UE) to define data metrics, report metrics, and receive metrics for switching CDNs in a multi-CDN environment.

[0035] 3GPP 26.501 contains a section where, in a media streaming environment, a UE reports UE data to a data server, and the server utilizes the UE's information to provide network assistance.

[0036] Among the technologies currently under discussion, there is a lack of discussion regarding multi-CDN (Content Delivery Network) switching methods in 5GMS (5G Mobile Services) clients of UE (User Terminals).

[0037] With the advancement of 5G technology, mobile data transmission speeds and service quality have significantly improved, leading to an increased demand for various multimedia content. Users desire a faster and more stable streaming experience, and the role of CDNs has become crucial for this. However, research and implementation regarding switching methods for 5GMS clients to operate efficiently in a multi-CDN environment are currently lacking.

[0038] Multi-CDN switching aims to provide users with the optimal content delivery path by utilizing the resources of various CDN providers. However, in a 5GMS environment, there are technical challenges required to effectively manage switching between CDNs and to select the appropriate CDN in real time to meet the needs of user terminals. Various factors must be considered during this switching process, including network latency, bandwidth, user location, and the type of content.

[0039] However, in current UEs and servers, there is a lack of data metrics to consider for switching based on external CDNs and internal CDNs.

[0040] The method according to the embodiments includes a method for efficiently downloading streaming between multiple CDNs.

[0041] The embodiments include architectural changes to the UE for multi-CDN switching during media streaming downlink in a 5G system.

[0042] The method according to the embodiments includes a procedure including a UE data report of a media player in a Multi-CDN scenario.

[0043] The embodiments include reporting parameters among UE data reports in a downlink environment.

[0044] The embodiments add mean network round-trip time, network round-trip variance, and transport congestion window size to the reporting parameters in the UE data report, thereby reducing the burden of switching CDNs during data collection of the Application function (AF) and enabling CDN switching based on parameters at the end user level.

[0045] The embodiments can obtain network congestion information on the UE (End-user) side and perform CDN switching to select the best effort CDN for download streaming.

[0046] The embodiments can reduce the overall network load by selecting the CDN with the best efficient environment in the UE.

[0047] Below, a 5G media streaming architecture according to embodiments is described. The following is an explanation of the 5G media streaming structure and abbreviations.

[0048] General service architecture

[0049] Referring to Fig. 1, a 5G media streaming architecture within a 5G system is described.

[0050] In the 5G media streaming structure within a 5G system, 5GMS (5G Media Streaming: the areas where media is transmitted (e.g., 5GMS Client, 5GMS, 5GMS AF, 5GMS AS) belong to the stage 3 specification. The functions (Dp: of 5G system boxes (UE, 5G SYSTEM, RAN, UPF, NEF, PCF, Trusted DN)) are defined in the 5G system specification. External boxes (5GMS Application Provider, External DN) are not included in the specification scope of 5G media streaming or the 5G system. The following shows the architecture from the 5GMS-Aware Application to the 5GMS Application Provider.

[0051] DN: Data Network, Media Delivery: The area where media is transmitted (e.g., 5GMS Client, 5GMS, 5GMS AF, 5GMS AS), External: The area provided by the server, Media Client: A UE internal function dedicated to Media Delivery comprising: Media AF: Application Function for media transmission, Media AS: Application Server for media transmission, Media Application Provider: Role of providing multimedia content in a 5G network, 5GMS AF: Application Function for 5G media streaming, 5GMS AS: Application Server for 5G media streaming that hosts 5G media functions. For example, 5GMS AS can be implemented differently, such as distributing 5GMS AS functions between different physical hosts like a Content Delivery Network (CDN), 5GMS Client: An internal UE function dedicated to 5G media streaming; the 5GMS Client is a logical function, and depending on the implementation choice, sub-functions may be included within the UE. 5GMS AF and 5GMS AS are functions of the Data Network that communicate with the UE via the UPF and use the N6 reference point. A trusted DN is a trusted DN in the operator network, and the AF of a trusted DN can communicate directly with 5G core functions. The 5GMSd AF of an external DN can communicate with 5G core functions only through the NEF using the N33 reference point. N6 is a reference point between the UPF and the Data Network; the 5GMS AF and 5GMS AS are functions of the Data Network (DN) and communicate with the UE through N6.UPF: Processes user traffic in the data plane and supports multicast / broadcast services. It interacts with the SMF to receive multicast data from the MB-UPF for the 5GC individual MBS traffic delivery method. It delivers multicast data to UEs via PDU sessions for the 5GC individual MBS traffic delivery method. MBS: Multicast / Broadcast Service. RAN: Delivers MBS data packets to multiple UEs using PTM (Point-to-Multipoint) or PTP (Point-to-Point). It receives MBS data packets from the 5GC via shared MBS traffic delivery. PCF: Policy Control Function; supports an integrated policy framework for managing network operations. It provides policy rules to control plane functions for enforcement and implements a front end to access subscriber information necessary for policy decisions from the User Data Repository (UDR). Media Session Handler: A UE function capable of communicating with the 5GMSD AF to establish and control media session delivery, and performing functions such as consumption and QoE metric collection and reporting. The media session handler can expose APIs available for use by 5GMSD Aware Applications. Media player: A UE function that communicates with the 5GMSD AS to stream media content in real-time or download media content. 5GMS Aware Application: The 5GMS Client is controlled by external media applications, such as apps that implement specific logic for external applications or content service providers and establish media sessions. Although 5GMS Aware Applications are not defined in the 5G media streaming specification, they utilize network functions that use 5GMD clients, 5GMS interfaces, and APIs.

[0052] FIG. 2 shows a media application function (Media AF) according to embodiments.

[0053] Figure 2 shows the media application functions in more detail on the structure of Figure 1.

[0054] The description of the reference points in Fig. 2 is as follows.

[0055] M1: A reference point for providing media delivery between the Media Application Provider and the Media AF. M2: A reference point for ingesting media into the Media AS or egesting media from the Media AS between the Media Application Provider and the Media AS. M3: A reference point for media session processing related to Media AS configuration and / or media delivery between the Media AF and the Media AS. M4: A reference point for downlink media transfer ("Content Distribution") from the Media AS to the Media Access Function of the UE or uplink media transfer ("Content Contribution") from the Media Access Function to the Media AS. M5: A reference point for media session processing related to media delivery between the Media AF and the Media Client's Media Session Handler. M6: A reference point for configuring the Media Session Handler between the Media Aware Application and the Media Session Handler. M7: A reference point for media access control between the Media Aware Application and the Media Access Function. M8: A reference point between the Media Aware Application and the Media Application Provider. (Outside the scope of standardization). M9: A reference point between one Media AF instance and another instance for Media AF instance chaining. (Outside 5GMS scope). M10: A reference point between one Media AS instance and another instance for distributed service chaining. (Outside 5GMS scope). M11: A reference point for media session handler configuration and / or media access control between a media session handler and a media access function (both within the media client). M12: A reference point between one media access function and another function for peer-to-peer media transmission between other media clients, provided the 5G system allows it.

[0056] FIG. 3 shows a system design diagram for a UE using multiple CDNs according to embodiments.

[0057] With reference to FIG. 3, a multi-CDN media transmission structure within 5G and non-5G systems is described. FIG. 3 can be viewed as an example of a network structure for multicast / broadcast services based on a 5G core network for MBS.

[0058] FIG. 4 shows a multi-CDN media transmission structure in 5G and non-5G systems according to embodiments.

[0059] UE (User Equipment): A user terminal device that includes a 5GMSd Client. It is responsible for receiving and playing media content (video, audio, hybrid media, etc.). The UE can connect to the 5GMSd Application Server (AS) via the M4 interface. Data can be accessed via 3GPP access networks (e.g., 5G NR, LTE) or non-3GPP access networks (e.g., Wi-Fi). In other words, the terminal can access the streaming server not only through 5G networks but also through non-3GPP paths such as Wi-Fi.

[0060] Access Network (3GPP / Non-3GPP Access): 3GPP Access is an authorized mobile path that connects to the Data Network (DN) via the 5G Core. Non-3GPP Access is an unauthorized access method based on Wi-Fi, Ethernet, or a public network. Both access methods can connect to the 5GMSd AS via the M4 interface. These access networks serve as the foundation for multi-access streaming or CDN switching.

[0061] A 5GMSd AS (5G Media Streaming Application Server) is a media streaming server that serves as an entity providing actual media data to terminals. It can be distributed across multiple locations and reside in either a trusted or external data network. Trusted DN: This refers to a CDN / AS within a trusted network directly operated by a mobile carrier. External DN: This refers to a third-party CDN provider or a cloud-based content server. A 5GMSd AS can be either a carrier-managed CDN (Trusted DN) or an external CDN (External DN).

[0062] A 5GMSd Application Provider is a service provider or content provider. It controls or manages one or more 5GMSd ASs and configures streaming session information for terminals to connect to. It controls and configures (provisions) ASs through the M2 interface.

[0063] Below, the data collection, report, and exposure architecture for 5GMS is described.

[0064] FIG. 5 shows a 5G media streaming architecture according to embodiments.

[0065] Instantiating the 5G media streaming architecture results in Figure 5.

[0066] The 5GMS Application Provider in the architecture operates as an application service provider. The Data collection AF for 5G media streaming is implemented in the 5GMS AF. The Direct Data Collection Client for 5G media streaming is implemented in the Media Session Handler. The Media Session Handler is responsible for UE data collection activities of sub-functions such as metic collection and reporting, consumption collection, and reporting, and reports to the 5GMS AF via reference point M5. It also plays a role in logging ANBR-based network assistance calls by network assistance sub-functions and reporting them to the Data collection AF implemented in the 5GMS AF via reference point R2. The provisioning AF of the application service provider is not implemented in the 5GMS architecture. Data collection and reporting are configured using the procedures defined in this document. The role of the AS data collection client is performed in the 5GMS AS and can be deployed as a trusted AS within the 5G system or to an external AS. The Event Consumer AF is instantiated in the 5GMS Application Provider as a consumer of 5G media streaming events from the Data Collection AF.

[0067] The function of the reference point in the structure of Fig. 5 is as follows.

[0068] M1: The Data Collection AF performs the provisioning of data collection and reporting functions. R2: Direct data collection clients report ANBR-based network assistance calls directly to the Data Collection AF. To perform the provisioning of QoE metrics and consumption reports, R2 logically executes this using a combination of three internal interfaces and reference point M5. Internal interfaces between direct data reporting clients, including metric collection and reporting and consumption reporting sub-functions. Internal interfaces between the media session handler and its subordinate direct data collection client functions. Internal interfaces between the 5GMS AF and its subordinate data collection AF functions. M5: Direct data collection clients report data directly to the Data Collection AF via the media session handler and the 5GMS AF. R4: The 5GMS AS reports media streaming access to the Data Collection AF. R5: The Data Collection AF exposes events to subscribed NWDAF instances. R6: The Data Collection AF exposes events to subscribed event consumer AF instances within the 5GMS application provider. M6: Configures 5GMS-related data reporting by 5GMS-aware applications.

[0069] FIGS. 6a and FIGS. 6b illustrate a configuration that performs metric collection and reporting functions according to embodiments.

[0070] The procedure for the metric collection and reporting function of the method according to the embodiments performed on the structures of FIGS. 1 to 5 is described.

[0071] The following is 5GMS Downlink UE Data Reporting:

[0072] The following UE data reporting procedure is included in the scope of instantiation of the abstract data collection and reporting architecture in the downlink 5GMS architecture.

[0073] The procedure described below in the 'Metrics collection and reporting' step is used for a direct data collection client instantiated in a media session handler to report QoE metrics of downlink media streaming to a data collection AF instantiated in a 5GMSd AF.

[0074] The procedure described below in the 'Consumption reporting' step is used for a direct data collection client instantiated in a media session handler to report the consumption of downlink media streaming to a data collection AF instantiated in a 5GMSd AF.

[0075] The call to the downlink dynamic policy procedure is recorded by the 5GMSd AF and reported to its subordinate data collection AF.

[0076] In the 'Downlink Network Assistance' step below, the call to the AF-based downlink network assistance procedure described later is recorded by the 5GMSd AF and reported to its subordinate data collection AF during the active AF-based network assistance session.

[0077] The procedure described below in the 'Procedures for downlink media streaming data collection, reporting and exposure' step is used by the 5GMSd AS to report downlink media streaming access activities to the data collection AF instantiated in the 5GMSd AF via reference point R4. In this case, the UE data report includes the parameters defined in the reporting parameters used at reference point R2, which are described below in the procedures for downlink media streaming data collection, reporting and exposure.

[0078] The procedure defined in 'Consumption reporting parameters' below is used for a direct data collection client instantiated in a media session handler to report a call to an ANBR-based downlink network support procedure to a data collection AF instantiated in a 5GMSd AF via reference point R2. In this case, the UE data report includes the parameters defined in '2.3.6. Procedures for downlink media streaming data collection, reporting and exposure'.

[0079] Metrics collection and reporting step according to the embodiments:

[0080] Metrics collection and reporting can be performed in various ways depending on the relationship between the application provider and the 5GMS system operator. The following is a simple signal example.

[0081] 1: The overall metric configuration is performed at the network level. For example, it defines the geographic regions to enable metric collection, and defines the metrics to be collected and the method for reporting them. If slice-based metric collection and reporting are supported, the metric configuration may include slice scopes, which represent specific slice instances for metric collection and reporting. 2: The metric configuration is transmitted from the OAM to the RAN, and at this stage, it is not passed to the UE.

[0082] 3: As time passes, assume that the UE moves during this period.

[0083] 4: A UE enters an area (cell, location area, etc.) within geographical constraints. This is detected by the RAN, and the RAN must now enable metric collection and reporting for the UE.

[0084] 5: The actual metric configuration is transmitted from the RAN to the media session handler via the control plane.

[0085] 6: After additional time passes, the UE has the metric configuration but the streaming session does not start.

[0086] 7: The streaming session starts.

[0087] 8: Session setup is performed along with signal trading. (Not shown here)

[0088] 8a: If the metric configuration set includes a slice range, the media session handler must identify the running slice currently performing media streaming (e.g., via AT Command +CGDCONT

[0024] or specific traffic mapping via URSP [4]). If the running slice is within the slice range, metric collection and reporting must be performed. Additionally, the running slice must also be included in the metric report.

[0089] 9: A new metric collection task is created in the media player.

[0090] 10: A reference to the new metric collection task is returned.

[0091] 11: The configuration of the metric collection task (i.e., the metric to be measured) and the measurement resolution interval are sent to the media player. The metric reporting interval timer is activated in the media session handler.

[0092] 12: Media is delivered and rendered.

[0093] 13: More media is delivered.

[0094] 14: After the configured metric reporting interval has elapsed, the media session handler requests the metrics collected from the media player.

[0095] 15: The media player returns the collected metrics.

[0096] 16: Metrics are reported through the control plane.

[0097] 17: The session continues.

[0098] 18: More media is delivered, and the session ends.

[0099] 19: The media session handler requests the final collected metrics.

[0100] 20: The media player returns the final collected metrics.

[0101] 21: Metrics are reported to the OAM through the control plane.

[0102] 21a: OAM can determine QoE metrics per slice based on metric reports and slice ranges.

[0103] 22: The metric collection job is deleted.

[0104] 23: Time passes, and the UE moves.

[0105] 24: The UE leaves the geographic area specified in the metric configuration.

[0106] 25: The RAN sends the metric (non)configuration to the UE to stop future metric collection.

[0107] Referring to FIG. 6, the procedure for collecting and reporting metrics in a downlink media streaming service according to embodiments is described as follows.

[0108] The network establishes a network-level metrics configuration including geographical constraints for the terminal (UE) (Step 1), and the configuration information is transmitted to the terminal (Step 2). After a certain period of time has elapsed (Step 3), when the terminal enters a geographical area where metric collection and reporting are to be performed (Step 4), the network provides reporting configuration information to the terminal through the 5G control plane (Step 5).

[0109] The terminal starts a streaming session (step 7), and a metric job is created during the session setup process (step 8) (steps 9 and 10). Along with this, the terminal sets up a metric collection configuration for the streaming session (step 11), and subsequently, media content is transmitted to the terminal (steps 12 and 13).

[0110] During the streaming session, the terminal periodically acquires collected metrics (steps 14 and 15) and reports them to the network via the 5G control plane (step 16). During this time, media content continues to be transmitted (steps 17 and 18). During the session or at the end of the session, the terminal acquires additional metrics (steps 19 and 20) and performs a final metric report for them (step 21). Afterward, the terminal deletes the generated metric task to terminate the reporting procedure (step 22).

[0111] When the terminal leaves the geographic area after a period of time (step 24), the network terminates the reporting configuration for the terminal by performing a metrics (de)configuration procedure through the 5G control plane (step 25).

[0112] Metric collection and reporting are dynamically controlled based on the terminal's geographical location or session status, enabling efficient management of quality indicators (QoE / QoS) at the network level.

[0113] Metrics reporting configuration parameters according to the embodiments used in the aforementioned procedure are defined as follows.

[0114]

[0115] FIGS. 7a and FIGS. 7b illustrate consumption reporting according to the embodiments.

[0116] In addition to FIGS. 1 to 6a and FIG. 6b, the collection and reporting procedure of the method according to the embodiments is described with reference to FIG. 7a and FIG. 7b.

[0117] 1: The 5GMSd recognition application starts.

[0118] 2: The media content item is selected.

[0119] 3: A 5GMSd-aware application triggers a media session handler to start content playback. A media player item is provided.

[0120] 4: 5GMSd AF initializes the parameters of the consumption report configuration (e.g., frequency).

[0121] 5: The media session handler triggers a consumption report.

[0122] 6: The media session handler starts the media player with the media player item.

[0123] The second step is media playback, and user preferences can be changed.

[0124] 7: The 5GMSd recognition application selects / changes user environment settings.

[0125] 8: The media player sends the consumption report user preference settings to the media session handler.

[0126] When media is playing, consumption report parameters can be updated.

[0127] 9: 5GMSd AF updates consumption reporting parameters.

[0128] When media is playing:

[0129] 10: The media player regularly accesses media content.

[0130] 11: If there are changes to the consumed media properties, the media player sends the changes to the media session handler.

[0131] 12: The media session handler periodically sends reports to 5GMSd AF.

[0132] The final step is to stop the media.

[0133] 13: The 5GMSd-aware application triggers the media session handler to stop content playback.

[0134] 14: The media session handler stops consumption reporting.

[0135] 15: The media session handler can send the final consumption report to 5GMSd AF.

[0136] 17: The media session handler stops the media player.

[0137] With reference to FIGS. 7a and FIGS. 7b, a content consumption reporting procedure according to an embodiment of the present invention will be described.

[0138] The 5GMSd-Aware Application starts (Step 1), and the user selects media content to play (Step 2). Accordingly, the Media Session Handler initiates content playback (Step 3) and initializes the consumption reporting function for the session (Step 4). After initialization, the Media Session Handler starts consumption reporting (Step 5), and the Media Player starts playing the actual content (Step 6).

[0139] While content is playing, the user can select user preferences, such as language settings (step 7), and this user preference information is transmitted to the media session handler (step 8). The media session handler updates consumption reporting parameters according to the transmitted user preferences (step 9). At the same time, the media player requests and receives content corresponding to the selected settings from the 5GMSd AF (step 10).

[0140] While content playback is in progress, the media session handler transmits changes to consumed media properties to the 5GMSd AF (step 11) and transmits consumption report data periodically or on an event basis (step 12).

[0141] When the streaming session ends (step 13), the media session handler stops the consumption reporting function (step 14) and transmits the last consumption report data to the 5GMSd AF (step 15). Then, the media player ends content playback (step 16).

[0142] According to the embodiments, a media session handler within a user terminal dynamically adjusts consumption reporting parameters based on user preferences and session status, and reports the media consumption status to the 5GMSd AF in real time, thereby enabling the network to perform quality optimization and service adaptation based on user-specific media consumption characteristics.

[0143] The consumption reporting parameters used in the above procedure are as follows.

[0144]

[0145] Examples of parameters for consumption reporting according to embodiments are shown.

[0146] The consumption report parameters define the consumption information transmitted to the network by the terminal (UE) or media session handler, and each item included therein is as follows.

[0147] The Media Player Entry pointer is information used to identify the entry point of a media player, and in the case of DASH-based media player entry, it can be represented as the URL of the MPD (Manifest Presentation Description).

[0148] The Consumption reporting client ID indicates the identifier of the terminal consuming media data.

[0149] The location type is used only when the terminal's location reporting function is enabled, and is reported on the condition that the terminal shares its location within the network operator's trust domain. The location type can be expressed in the form of CGI, ECGI, or NCGI as defined in TS 23.003.

[0150] The Location parameter is used to identify the actual location of the terminal and applies only when the terminal's location reporting is enabled and sharing is allowed within the trusted area.

[0151] The Media consumed item identifies the media consumed by the user, and in the case of the DASH method, the AdaptationSet@id value can be used.

[0152] Start time indicates the point in time when content consumption begins, and Duration indicates the duration of consumption based on the start time.

[0153] The set of consumption reporting parameters according to the embodiments comprehensively defines the type of media consumed by the terminal, playback time, duration, location information, etc., thereby enabling the network to precisely analyze user consumption patterns and quality of excellence (QoE).

[0154] FIG. 8 illustrates Downlink Network Assistance according to embodiments.

[0155] In the conceptual design of FIGS. 1 to 7a and FIGS. 7b, the structure for supporting a downlink network can be configured as shown in FIG. 8.

[0156] The Network Assistance feature aims to improve the Quality of Experience (QoE) of streaming sessions when a UE performs downlink media streaming. The first feature is Bitrate Recommendation (Throughput Estimation). This allows the UE to initiate downlink streaming at the bitrate best suited to network conditions or receive recommendations from the server for networks where the media streaming session is valid. The recommended bitrate is based on an estimate or prediction of the network's available link bandwidth. The second feature is Delivery Boost. The 5GMSd client enables a temporary boost to the network, that is, a temporary increase in network throughput for the client. This prevents the risk of media playback being interrupted by buffer underruns.

[0157] Network assistance (NA) is broadly divided into the ANBR-based approach and the 5GMS AF-based approach.

[0158] 5GMSd AF-based approach:

[0159] Network Assistance (NA) functionality improves the QoE of media streaming sessions by enabling UEs to receive bitrate recommendations from the 5GMSd AF. The 5GMSd AF provides throughput estimates or bitrate recommendations, which are valid depending on network conditions. UEs use these to select the most suitable bitrate. The network allocates resources to meet these recommendations, but there is no guarantee regarding bandwidth estimation. 5GMSd clients can provide additional information to the 5GMSd AF, such as the required bitrate. The downlink network assistance procedure based on the 5GMSd AF is as follows.

[0160] NA Session Start: A 5GMSd client requests the 5GMSd AF to start an NA session. If the request satisfies preconditions such as policy and billing, the 5GMSd AF confirms that an NA session has been established.

[0161] NA Throughput Estimation: A 5GMSd client requests a throughput estimate for a downlink media session from the 5GMSd AF. If a set of available bitrates is provided with the request, the 5GMSd AF responds with a recommended bitrate based on the throughput estimate. If no set of bitrates is provided, it responds with only the throughput estimate.

[0162] NA Forwarding Boost: The 5GMSd client requests a downlink forwarding boost from AF.

[0163] NA Session Termination: A 5GMSd client requests NA session termination from the 5GMSd AF. The AF responds positively if session termination is possible, and negatively otherwise.

[0164] ANBR-based approach:

[0165] Bitrate recommendation messages and bitrate recommendation query messages are exchanged between the RAN and the UE. In this case, the network support functions of the 5GMSd client utilize the UE's internal functions to access the RAN modem driver, perform ANBR signaling operations, and receive corresponding responses from the network, operating outside the 5GMS architecture. Control plane interactions include the RAN sending downlink bitrate recommendations to the UE, which occur independently or in response to a boost request from the UE.

[0166] The operation of the method according to embodiments based on the Downlink Network Assistance architecture is as follows.

[0167] The user terminal (UE) includes a RAN Modem and a 5GMSd Client, and the 5GMSd Client includes a Media Session Handler and a Network Assistance Module.

[0168] The RAN Modem performs uplink and downlink data transmission of the terminal through a wireless interface with the wireless access network (RAN) and transmits and receives network status information using ANBR or ANBRQ messages.

[0169] The media session handler manages media streaming sessions and controls reporting and configuration procedures related to Quality of Experience (QoE) in 5G media streaming services (5GMS).

[0170] The Network Assistance module within this media session handler receives ANBR-based bitrate control and data collection configuration information provided by the network and reflects this in session management within the terminal.

[0171] An ANBR-based approach is applied between the RAN Modem and the media session handler, and real-time transmission status and channel quality information of the terminal are exchanged through this path.

[0172] Meanwhile, the media session handler is connected through the 5GMSd AF (5G Media Streaming Application Function) and M5d interface, which corresponds to the 5GMSd AF-based approach.

[0173] Through this interface, media session-related configuration information, QoE reports, consumption data, etc., are exchanged.

[0174] 5GMSd AF is a media application function at the upper layer of the network that collects consumption data and metrics reported from terminals and utilizes them for network quality analysis and service optimization.

[0175] The 5GMSd AF is also linked with the Network Exposure Function (NEF) and the Policy Control Function (PCF) through the N33 and N5 interfaces, respectively, to exchange policy control information and exposure data.

[0176] Through this, policy decisions, quality assurance (QoS management), and network-based media optimization for 5GMS services are performed.

[0177] The downlink network support architecture according to the embodiments provides the effect of improving transmission efficiency and user quality of experience (QoE) in 5G streaming sessions by integrating terminal-side ANBR-based control and network-side 5GMSd AF-based management procedures.

[0178] FIG. 9 illustrates procedures for downlink media streaming data collection, reporting and exposure according to embodiments.

[0179] Procedures for downlink media streaming data collection, reporting and exposure of the method according to the embodiments are as follows.

[0180] Data collection client configuration for downlink media streaming access reporting

[0181] This is a sequence diagram illustrating a data collection client configuration procedure for downlink media streaming access reporting according to an embodiment.

[0182] Referring to FIG. 9, the 5GMSd AF (510) includes a data collection application function (Data Collection AF) and performs the function of managing and controlling data reporting of terminals at the network level.

[0183] 5GMSd AS (520) is a 5G media streaming application server responsible for the transmission of media content and session management, and performs interactions to support data reporting configuration.

[0184] The data collection and reporting client is a 5GMSd client function within the terminal that periodically acquires parameters for downlink media streaming access reporting and performs the role of reporting to the network.

[0185] This client periodically requests client configuration and, in response, receives client configuration information from 5GMSd AF via Ndcaf_DataReporting messages.

[0186] This configuration information includes settings required for downlink streaming access reporting, such as data collection cycles, reporting trigger conditions, and QoE metric items.

[0187] The loop indication means that this procedure can be performed repeatedly at specific time intervals or according to network policies, thereby allowing the data collection client to be automatically reconfigured according to changes in the reporting policy of the 5GMS network.

[0188] The embodiments can efficiently configure and manage access reporting for downlink streaming services through the interoperability between 5GMSd AF and data collection clients, thereby allowing the network to optimize service quality by reflecting the consumption behavior and QoE information of user terminals in real time.

[0189] FIG. 10 illustrates procedures for downlink media streaming data collection, reporting and exposure according to embodiments.

[0190] This is a sequence diagram showing the configuration procedure of a Direct Data Collection Client for downlink media streaming access reporting according to one embodiment of the invention.

[0191] Referring to FIG. 6, the user terminal (UE) includes a media session handler (610), and a direct data collection client (611) is deployed inside the media session handler. This client performs the function of directly collecting media streaming-related data (e.g., QoE / QoS metrics, consumption metrics, etc.) within the terminal and reporting it to the network.

[0192] On the network side, there is a 5GMSd AF (620), and this 5GMSd AF includes a data collection application function (Data Collection AF, 621).

[0193] The data collection AF provides data reporting settings and policy information in response to a client configuration request from the terminal.

[0194] Communication is established between the terminal's direct data collection client and the 5GMSd AF through the R2 reference point.

[0195] The direct data collection client periodically sends an Acquire client configuration request, and this request is forwarded to the data collection AF via the R2 reference point.

[0196] The data collection AF sends client configuration information to the UE using the Ndcaf_DataReporting message.

[0197] This configuration information includes parameters necessary for data collection, such as reporting cycle, data type, reporting trigger conditions, and QoE metric items.

[0198] The direct data collection client sets its own reporting behavior based on the received configuration, and the same procedure is repeated (loop) at regular intervals to maintain the latest configuration.

[0199] The embodiments realize an independent and efficient reporting configuration with the network through a direct data collection client within the terminal's media session handler, thereby facilitating downlink quality monitoring and QoE-based control of 5G media streaming services.

[0200] The reporting parameters used at reference point R2, such as the structure and / or procedure in FIGS. 9 to 10, are as follows.

[0201]

[0202] The reporting parameters used at reference point R4, such as the structure and / or procedure in FIGS. 9 to 10, are as follows.

[0203] The parameters of Common baseline parameters for UE data reporting must be included in the UE data report sent by the data collection client to the Data Collection AF instantiated in the 5GMS AF, and the default parameters defined in 26.531 must also be included.

[0204] The UE data report for media streaming access activities must include the parameters specified in the table below as the UE data report for downlink media streaming access, and must also include the default parameters with a gray background defined in Common baseline parameters for UE data reporting.

[0205]

[0206] FIG. 11 shows a 5G media streaming architecture according to embodiments.

[0207] The method according to the embodiments relates to a media streaming method based on a wireless communication system (e.g., 5G, etc.) in multiple CDNs, and can be performed on a structure such as that of FIG. 11.

[0208] With reference to FIG. 11, a method for supporting downlink network and CDN switching in a 5G media streaming system according to embodiments is described.

[0209] The user terminal (UE) includes a 5GMS client, which consists of a Media Session Handler and a Media Stream Handler.

[0210] The media session handler includes multiple sub-functional blocks, among which are a Metrics Collection & Reporting block, a Consumption Collection & Reporting block, a Network Assistance block, and a CDN Switching Assistance block, which is a core component of the present invention.

[0211] The CDN switching support block performs control functions to dynamically switch CDNs based on media streaming quality of excellence (QoE) or network conditions in a multi-CDN (Content Delivery Network) environment.

[0212] The CDN switching support block controls the media session handler to change the CDN or select the optimal delivery path during the session by referring to Quality of Service (QoS) metrics and data collection results delivered from the network.

[0213] The Direct Data Collection Client directly collects various streaming-related data within the terminal and reports it to the 5GMS AF through the R2 interface.

[0214] Unlike the R2 or M5 interfaces defined in conventional 5GMS standards, the R2 interface provides a direct data reporting path between the terminal's direct data collection client and the 5GMS AF.

[0215] This allows the media session handler to directly transmit metrics or consumption data to the data collection application function (Data Collection AF) without going through the network.

[0216] 5GMS AF includes data collection application functions and interoperates with 5GMS AS and NWDAF through R4 and R5 interfaces.

[0217] The collected data is reflected in network analysis, policy control, and media quality optimization.

[0218] 5GMS AF also interacts with 5GMS application service providers that include Event Consumer AF through the M1 interface, thereby enabling external service providers to utilize QoE and QoS information in real time.

[0219] The embodiments combine the CDN switching support function within the terminal with the R2' interface, thereby enabling CDN switching control based on network quality or service policy changes at the terminal level, and enabling delay-free media quality control and adaptive streaming through direct data reporting.

[0220] The embodiments provide an extensible 5G media streaming architecture that integrates a 5GMS AF-based downlink network support procedure and a terminal-based CDN switching support function, thereby enabling simultaneous optimization of transmission paths between multiple CDNs, improvement of service quality, and efficiency of network resources.

[0221] FIGS. 12a, FIGS. 12b, and FIGS. 12c show reporting parameters according to the embodiments.

[0222] Reporting parameters used in Reference point R2:

[0223] Data metrics from R4 are adopted and used in R2'. This is intended to facilitate CDN selection by end-users and ensure smooth downlink media streaming when using various CDNs. By utilizing the extended R2', it is possible to determine not only the selection of a CDN but also which CDN to use to weight media data within the network. For example, when watching YouTube, the very beginning of the stream can be configured to download more media streaming data from a CDN with high QoS or a short Mean Network Round Trip Time, while a different CDN can be utilized for the middle and later parts of the stream to reduce the burden on the 5GMS AS server of the Trusted DN.

[0224] The definitions of the reporting parameters of the reference point R2' used in the structure of Fig. 11 are as follows.

[0225] The following shows the definitions of key parameters used in downlink media streaming data reporting.

[0226] The External Application Identifier is an identifier for the application performing UE data reporting, and is used to distinguish the source of the report in the network or 5GMSd AF.

[0227] The Expedite Directive is a parameter indicating whether to prioritize the processing of reported data, and is used when the Data Collection AF requires rapid data processing.

[0228] The Date-time parameter indicates the start time of downlink media streaming and is used for time synchronization and session history management.

[0229] The terminal identifier (UE Identity) is information for uniquely identifying the terminal at the M44 reference point with the 5GMSd AS, and may include, for example, GPS location, cell ID, or network level identifier.

[0230] The Media Delivery Session Identifier is an ID used to uniquely distinguish a session managed by a media session handler, and includes session information provided by 5GMSd AS during an HTTP-based session request.

[0231] The Data Network Name identifies the data network to which the downlink media streaming session is connected and may include slice information such as S-NSSAI (Single Network Slice Selection Assistance Information).

[0232] UE Location represents location information when a terminal downloads data from 5GMSd AS, and is used for location-based QoE analysis and transmission path optimization.

[0233] The 5GMSd AS Service Endpoint specifies the endpoint of the 5GMSd AS that the media player connects to, and includes IP address and port information.

[0234] HTTP request parameters are composed as follows.

[0235] The HTTP request method specifies the type of request (GET, POST, etc.), the HTTP request URL identifies the resource to be requested, and the HTTP request version indicates the HTTP protocol version used. The HTTP request range specifies the range in bytes for the HTTP request, and the HTTP request size expresses the total size of the request message in bytes.

[0236] An HTTP User Agent is string information that identifies a media player or client, and a User Identity is used for user authentication and session differentiation.

[0237] The Referrer URL indicates the origin URL from which the request originated and is used to track the content access path.

[0238] The Cache Status parameter indicates whether a request is in a cache hit or miss state when the media player requests content, and whether the validity period of the cache data has expired.

[0239] HTTP Response Parameters include the following.

[0240]

[0241] The Response Code represents the HTTP status code returned by the server, the Response Size represents the size of the entire received message in Bytes, and the Response Body Size represents the size of the actual content data.

[0242] The Response Content Type specifies the MIME type of the received data (e.g., video / mp4, image / jpeg, etc.).

[0243] Processing latency represents the total processing time from the time a media player sends a request until it receives a response from the 5GMSd AS, and is used to evaluate network congestion status and server response performance.

[0244] Mean Network Round-Trip Time and Network Round-Trip Time represent the round-trip delay for a single request and the average round-trip delay for multiple requests, respectively, and are used for session QoE analysis and network quality diagnosis.

[0245] The Transport Congestion Window Size represents the size of the congestion control window at the time of TCP or QUIC-based transmission and is used as an indicator to evaluate network load status.

[0246] Each of these parameters is used as key data to comprehensively evaluate media streaming quality, network efficiency, and user experience (QoE) within the 5GMS system, and can be dynamically configured and managed in the data collection and reporting procedure of the present invention.

[0247] FIGS. 13a and 13b illustrate metric collection and reporting via R2' (CDN switching) through the R2' interface according to the embodiments.

[0248] The method according to the embodiments further includes the step of performing switching of FIG. 13a and FIG. 13b based on parameters FIG. 12a, FIG. 12b and FIG. 12c in a structure such as FIG. 11.

[0249] 1: The overall metric configuration is performed at the network level. For example, it defines the geographic regions to enable metric collection, and defines the metrics to be collected and how to report them. If slice-based metric collection and reporting are supported, the metric configuration may include slice scopes, which represent specific slice instances for metric collection and reporting.

[0250] 2: The metric configuration is transmitted from the OAM to the RAN, and is not transmitted to the UE at this stage.

[0251] 3: As time passes, assume that the UE moves during this period.

[0252] 4: A UE enters an area (cell, location area, etc.) within geographical constraints. This is detected by the RAN, and the RAN must now enable metric collection and reporting for the UE.

[0253] 5: The actual metric configuration is transmitted from the RAN to the media session handler via the control plane.

[0254] 6: After additional time passes, the UE has the metric configuration but the streaming session does not start.

[0255] 7: The streaming session starts.

[0256] 8: Session setup is performed along with signal trading. (Not shown here)

[0257] 8a: If the metric configuration set includes a slice range, the media session handler must identify the running slice currently performing media streaming (e.g., via AT Command +CGDCONT

[0024] or specific traffic mapping via URSP [4]). If the running slice is within the slice range, metric collection and reporting must be performed. Additionally, the running slice must also be included in the metric report.

[0258] 9: A new metric collection task is created in the media player.

[0259] 10: A reference to the new metric collection task is returned.

[0260] 11: The configuration of the metric collection task (i.e., the metric to be measured) and the measurement resolution interval are sent to the media player. The metric reporting interval timer is activated in the media session handler.

[0261] 12: Media is delivered and rendered.

[0262] 13: More media is delivered.

[0263] 14: After the configured metric reporting interval has elapsed, the media session handler requests the metrics collected from the media player.

[0264] 15: The media player returns the collected metrics.

[0265] 16: Metrics are reported through the control plane.

[0266] 17: CDN switching occurs based on R2's metirc.

[0267] 18: The session continues.

[0268] 19: More media is delivered, and the session ends.

[0269] 20: The media session handler requests the final collected metrics.

[0270] 21: The media player returns the final collected metrics.

[0271] 22: Metrics are reported to the OAM through the control plane.

[0272] 22a: OAM can determine QoE metrics per slice based on metric reports and slice ranges.

[0273] 23: CDN switching occurs based on R2's metirc.

[0274] 24: The metric collection job is deleted.

[0275] 25: Time passes, and the UE moves.

[0276] 26: The UE leaves the geographic area specified in the metric configuration.

[0277] 27: The RAN sends the metric (non)configuration to the UE to stop future metric collection.

[0278] This is a sequence diagram illustrating the metric collection and reporting procedures and the CDN switching procedure in downlink media streaming.

[0279] The network establishes a network-level metrics configuration (Step 1), which may include geographical constraints or reporting policies. This configuration information is transmitted to the UE via the 5GMSd AS or Network Management Function (OAM) (Step 2). After a certain period of time has elapsed (Step 3), the terminal (UE) enters an area where metric collection and reporting are required (Step 4), at which time the metric configuration information is transmitted to the terminal via the 5G control plane (Step 5).

[0280] When the streaming session starts (step 7), the Media Session Handler sets up the streaming session (step 8) and then creates a metric job (steps 9 and 10). Subsequently, the terminal sets up the metric collection configuration (step 11), and then media content begins to be transmitted (steps 12 and 13).

[0281] The terminal periodically obtains collected metrics (Steps 14–15) and transmits them to a 5GMSd AS or network function in the form of a metric report via the 5G control plane (Step 16).

[0282] The CDN Switching function is performed (Step 17). Based on QoE / QoS information included in the reported metrics report—e.g., transmission delay, buffering rate, bitrate stability, network RTT, etc.—the CDN Switching Assistance Module within the media session handler is activated. If the quality of the currently used CDN falls below a standard, the CDN Switching Assistance Module selects the most suitable CDN from among pre-configured multiple CDN candidates and switches the streaming path in real time. This CDN switching is performed without service interruption, and the media player within the UE continues to play content from the new CDN within the same session context.

[0283] Even after the CDN transition, the terminal continuously collects metric data (steps 20–21) and transmits an updated metric report (step 22).

[0284] As a result, a second CDN switching procedure may be performed (Step 23), which may be readjusted based on network quality fluctuations or CDN server status reflected in the previous report.

[0285] The iterative CDN switching process maximizes transmission efficiency through metric-based adaptive control and provides a seamless user experience.

[0286] At the end of the session, the terminal deletes the generated metric task (step 24) and performs the metric deconfiguration procedure as it exits the area (step 27).

[0287] The embodiments provide a function to dynamically switch the CDN based on metric data collected and reported in real time by a terminal or 5GMS client, thereby enabling rapid response to network congestion, CDN server load, geographic latency variation, and user QoE degradation.

[0288] Unlike conventional single CDN-based streaming methods, the embodiments can significantly improve the stability and quality of media streaming by performing autonomous and intelligent CDN switching control using a metric feedback loop based on a 5GMS network.

[0289] Examples of the use of the CDN Switching Assistance module (or may be referred to as a control unit, processor, etc.) according to the embodiments are as follows.

[0290] Information such as Mean Processing latency, Mean network round-trip time, Network round-trip time variance, and Transport congestion window size for metrics added in R2' is collected from each CDN and reprocessed for use as follows to provide the necessary information for CDN switching.

[0291] a. Which CDN has the minimum average processing latency?

[0292] b. Which CDN has the minimum average network round-trip time?

[0293] c. Which CDN has the minimum network round-trip time variance?

[0294] d. Which CDN has the minimum transmission congestion window size?

[0295] Depending on each of a, b, c, and d, information on CDN Switching Assistance can be reported from the UE to the Data Collection AF.

[0296] FIG. 14 illustrates a method according to embodiments.

[0297] The method according to the embodiments may include the step of collecting metric information (S1400) by a media session handler of a device providing media streaming in a wireless communication system; the step of collecting consumption information (S1410); and / or the step of reporting the metric information and consumption information to a data collection application function (Application Function) (S1420); etc.

[0298] In a wireless communication system, the device providing media streaming can be a UE.

[0299] FIG. 15 illustrates a method according to embodiments.

[0300] The method according to the embodiments may include the step of receiving metric information and consumption information collected by a media session handler of a device providing media streaming in a wireless communication system (S1500); and / or the step of switching a Content Delivery Network (CDN) based on the metric information and consumption information (S1510); etc. The method of FIG. 15 may be performed by a server connected to the UE of FIG. 14.

[0301] The method of FIGS. 14 to 15 can be performed as follows.

[0302] Referring together with FIG. 11, the method may include the steps of: collecting a metric by a Media Session Handler of a device providing media streaming in a wireless communication system; collecting consumption information; and reporting the metric and consumption information to a Data Collection Application Function (AF).

[0303] Referring together with FIG. 11, in relation to steps 1 through 8 of FIG. 13a and FIG. 13b based on a 5G media streaming structure, metrics regarding the network are configured by a server, the configured metrics are transmitted to a Radio Access Network (RAN), and if the device is located in an area with geographical constraints, the metric configuration from the RAN is transmitted to the device's media session handler, and based on the streaming session, metric collection and reporting by the device can be performed.

[0304] In relation to steps 1 through 17 (CDN switching) of FIGS. 13a and 13b, media is received by the device, and based on downlink streaming for the media, metrics are collected by the device, the metrics are reported based on the control plane, and based on the metrics, the Contents Delivery Network (CDN) can be switched.

[0305] With respect to 'Date-time', 'UE identity', 'Media delivery session identifier', 'Data Network Name', 'Slice identification', and 'UE location' defined in the reporting parameters of 'Reference point R2' in FIG. 12a, 12b, and 12c, the metric is reported based on the reference point for reporting, and the metric includes reporting parameters for the selection of multiple CDNs and downlink media streaming, and the reporting parameters may include at least one of: access date and time regarding downlink media streaming ('Date-time'), unique identifier of the device accessing the server for downlink media streaming ('UE identity'), identifier regarding the session for downlink media streaming ('Media delivery session identifier'), data network name regarding the session for downlink media streaming ('Data Network Name'), identifier identifying the network slice regarding the session for downlink media streaming ('Slice identification'), or the location of the device when the media for downlink media streaming is downloaded ('UE location').

[0306] With respect to the reporting parameters of 'Reference point R2' in Figs. 12a, 12b, and 12c: '5GMSd AS service endpoint', 'HTTP request method', 'HTTP request URL', 'HTTP request version', 'HTTP request range', 'HTTP request size', 'HTTP User Agent', 'User identity', the metrics include reporting parameters for the selection of multiple CDNs and downlink media streaming, and the reporting parameters are: the server's service endpoint for accessing downlink media streaming ('5GMSd AS service endpoint'), the protocol request method for accessing downlink media streaming ('HTTP request method'), the protocol request URL by the media player for accessing downlink media streaming ('HTTP request URL'), the protocol version by the media player for accessing downlink media streaming ('HTTP request version'), the protocol request range for accessing downlink media streaming ('HTTP request range'), the protocol request size by the media player for accessing downlink media streaming ('HTTP request size'), and the downlink media streaming' It may include at least one of a string (HTTP User Agent) describing the media player that allowed access, or a string (User identity) identifying the user who performed access to the downlink media streaming.

[0307] Regarding the reporting parameters of 'Reference point R2' in FIG. 12a, 12b, and 12c: 'Referrer URL', 'Cache status', 'HTTP response code', 'HTTP response size', and 'HTTP response content type', the metric includes reporting parameters for the selection of multiple CDNs and downlink media streaming, and the reporting parameters may include at least one of: a reference URL reported by the media player, a cache status of the server for accessing downlink media streaming, a protocol response code of the server for accessing downlink media streaming, a protocol response size of the server for accessing downlink media streaming, or a protocol response content type of the server for accessing downlink media streaming.

[0308] Regarding the reporting parameters of 'Reference point R2' in FIG. 12a, FIG. 12b, and FIG. 12c: 'Processing latency', 'Mean network round-trip time', 'Network round-trip time variance', and 'Transport congestion window size', the metric includes reporting parameters for the selection of multiple CDNs and downlink media streaming, and the reporting parameters may include at least one of: the response time of the server for downlink media streaming to a request from a media player (Processing latency), the mean network round-trip time of protocol sessions received in access to downlink media streaming (Mean network round-trip time), the network round-trip time variance of protocol sessions received in access to downlink media streaming (Network round-trip time variance), or the congestion window size of protocol sessions received in access to downlink media streaming (Transport congestion window size).

[0309] In relation to the proposed metric-based CDN switching assistance, information on multiple CDNs is collected based on reporting parameters, and switching can be performed from a first CDN to a second CDN among multiple CDNs based on at least one of the response time, average network round-trip time, network round-trip time variance, or congestion window size for multiple CDNs.

[0310] The device according to the embodiments may include a memory and at least one processor connected to the memory. The at least one processor may be configured to collect metrics; collect consumption information; and report the metrics and consumption information to a data collection Application Function (AF) by a Media Session Handler of a device providing media streaming in a wireless communication system.

[0311] The device according to the embodiments may include a memory and at least one processor connected to the memory. The at least one processor may be configured to receive metric information and consumption information collected by a media session handler of a device providing media streaming in a wireless communication system; and to switch a Content Delivery Network (CDN) based on the metric information and consumption information.

[0312] The method and apparatus according to the embodiments provide the following technical effects.

[0313] The embodiments add mean network round-trip time, network round-trip variance, and transport congestion window size to the reporting parameters in the UE data report, thereby reducing the burden of switching CDNs during data collection of the Application function (AF) and enabling CDN switching based on parameters at the end user level.

[0314] The embodiments can obtain network congestion information on the UE (End-user) side and perform CDN switching to select the best effort CDN for download streaming.

[0315] The embodiments can reduce the overall network load by selecting the CDN with the best efficient environment in the UE.

[0316] The embodiments have been described in terms of methods and / or devices, and the description of the methods and the description of the devices may be applied complementarily.

[0317] Although the drawings have been described separately for the convenience of explanation, it is also possible to design a new embodiment by combining the embodiments described in each drawing. Furthermore, designing a computer-readable recording medium containing a program for executing the previously described embodiments, as required by a person skilled in the art, falls within the scope of the claims of the embodiments. The apparatus and method according to the embodiments are not limited to the configuration and method of the embodiments described above; rather, the embodiments may be configured by selectively combining all or part of each embodiment to allow for various modifications. Although preferred embodiments have been illustrated and described, the embodiments are not limited to the specific embodiments described above. It is not only possible for a person skilled in the art to make various modifications without departing from the essence of the embodiments claimed in the claims, but such modifications should not be understood individually from the technical concept or perspective of the embodiments.

[0318] Various components of the device of the embodiments may be implemented by hardware, software, firmware, or a combination thereof. Various components of the embodiments may be implemented as a single chip, for example, a single hardware circuit. Depending on the embodiments, the components according to the embodiments may each be implemented as separate chips. Depending on the embodiments, at least one of the components of the device according to the embodiments may be composed of one or more processors capable of executing one or more programs, and one or more programs may include instructions for performing or executing any one or more of the operations / methods according to the embodiments. Executable instructions for performing the methods / operations of the device according to the embodiments may be stored in non-transient CRMs or other computer program products configured to be executed by one or more processors, or may be stored in transient CRMs or other computer program products configured to be executed by one or more processors. Additionally, memory according to the embodiments may be used as a concept that includes not only volatile memory (e.g., RAM, etc.) but also non-volatile memory, flash memory, PROM, etc. In addition, it may also include implementation in the form of carrier waves, such as transmission over the Internet. Furthermore, processor-readable recording media are distributed across networked computer systems, allowing processor-readable code to be stored and executed in a distributed manner.

[0319] In this document, “ / ” and “,” are interpreted as “and / or.” For example, “A / B” is interpreted as “A and / or B,” and “A, B” is interpreted as “A and / or B.” Additionally, “A / B / C” means “at least one of A, B and / or C.” Also, “A, B, C” means “at least one of A, B and / or C.” Additionally, in this document, “or” is interpreted as “and / or.” For example, “A or B” may mean 1) “A” alone, 2) “B” alone, or 3) “A and B.” In other words, “or” in this document may mean “additionally or alternatively.”

[0320] Terms such as "first," "second," etc., may be used to describe various components of the embodiments. However, the interpretation of the various components according to the embodiments should not be limited by these terms. These terms are merely used to distinguish one component from another. For example, the first user input signal may be referred to as the second user input signal. Similarly, the second user input signal may be referred to as the first user input signal. The use of these terms should be interpreted as not departing from the scope of the various embodiments. Although the first user input signal and the second user input signal are both user input signals, they do not imply the same user input signals unless clearly indicated in the context.

[0321] The terms used to describe the embodiments are intended for the purpose of describing specific embodiments and are not intended to limit the embodiments. As used in the description of the embodiments and in the claims, the singular is intended to include the plural unless explicitly indicated in the context. Expressions of and / or are used to mean including all possible combinations between the terms. Expressions of include describe the presence of features, numbers, steps, elements, and / or components and do not imply the exclusion of additional features, numbers, steps, elements, and / or components. Conditional expressions such as "if" or "when" used to describe the embodiments are not limited to being optional. It is intended to be interpreted as "when a specific condition is satisfied," "when a related action is performed in response to a specific condition," or "when a related definition is interpreted."

[0322] Additionally, operations according to the embodiments described herein may be performed by a transmitting and receiving device including memory and / or a processor, depending on the embodiments. The memory may store programs for processing / controlling operations according to the embodiments, and the processor may control various operations described in this document. The processor may be referred to as a controller, etc. Operations in the embodiments may be performed by firmware, software, and / or a combination thereof, and the firmware, software, and / or a combination thereof may be stored in the processor or in memory.

[0323] Meanwhile, the operation according to the embodiments described above may be performed by a transmitting device and / or a receiving device according to the embodiments. The transmitting and receiving device may include a transmitting and receiving unit for transmitting and receiving media data, a memory for storing instructions (program code, algorithm, flowchart and / or data) for a process according to the embodiments, and a processor for controlling the operations of the transmitting and receiving devices.

[0324] The processor may be referred to as a controller, etc., and may correspond, for example, to hardware, software, and / or a combination thereof. The operation according to the embodiments described above may be performed by the processor. Additionally, the processor may be implemented as an encoder / decoder, etc., for the operation of the embodiments described above.

[0325] As described above, the relevant details have been explained in the best mode for carrying out the embodiments.

[0326] As described above, the embodiments may be applied wholly or partially to a method for providing media streaming in a wireless communication system, a device for providing media streaming in a wireless communication system, and a system.

Claims

1. A step of collecting a metric by a Media Session Handler of a device providing media streaming in a wireless communication system; Step of collecting consumption information; A step of reporting the above metric and the above consumption information to a data collection AF (Application Function); method.

2. In Paragraph 1, Network metrics are configured by a server, and the configured metrics are transmitted to the RAN (Radio Access Network), and If the above device is located in a geographically restricted area, a metric configuration from the RAN is transmitted to the media session handler of the above device, and Metric collection and reporting by the device are performed based on a streaming session, method.

3. In Paragraph 1, Media is received by the above device, and Based on downlink streaming for the above media, the metric is collected by the device, and The above metric is reported based on the control plane, and Based on the above metric, the Contents Delivery Network (CDN) is switched, method.

4. In Paragraph 2, The above metrics are reported based on reference points for reporting, and The above metrics include reporting parameters for the selection of multiple CDNs and downlink media streaming, and The above reporting parameters are: Access date and time regarding the above-mentioned downlink media streaming, A unique identifier of a device accessing the server for the above-mentioned downlink media streaming, Identifier regarding the session for the above-mentioned downlink media streaming, Data network name regarding the session of the above-mentioned downlink media streaming, An identifier identifying a network slice regarding a session of the above-mentioned downlink media streaming, or At least one of the location of the device when the media for the above-mentioned downlink media streaming is downloaded, method.

5. In Paragraph 2, The above metrics include reporting parameters for the selection of multiple CDNs and downlink media streaming, and The above reporting parameters are: The server's service endpoint for accessing the above-mentioned downlink media streaming, A protocol request method for accessing the above-mentioned downlink media streaming, Protocol request URL by the media player for accessing the above-mentioned downlink media streaming, Protocol version by a media player for accessing the above-mentioned downlink media streaming, Protocol request range for accessing the above-mentioned downlink media streaming, Protocol request size by the media player for accessing the above-mentioned downlink media streaming, A string describing a media player that has allowed access to the above-mentioned downlink media streaming, or including at least one of a string identifying a user who accessed the above-mentioned downlink media streaming, method.

6. In Paragraph 2, The above metrics include reporting parameters for the selection of multiple CDNs and downlink media streaming, and The above reporting parameters are: Referring URL reported by the media player, The server's cache status for accessing the above-mentioned downlink media streaming, The server's protocol response code for accessing the above-mentioned downlink media streaming, The size of the server's protocol response for accessing the above-mentioned downlink media streaming, or A server protocol response content type for accessing the above-mentioned downlink media streaming, comprising at least one of method.

7. In Paragraph 2, The above metrics include reporting parameters for the selection of multiple CDNs and downlink media streaming, and The above reporting parameters are: The server's response time for the above-mentioned downlink media streaming in response to the media player's request, Average network round-trip time of protocol sessions received in access to the above downlink media streaming, Network round-trip time distribution of protocol sessions received in access to the above-mentioned downlink media streaming, or Comprising at least one of the congestion window size for a protocol session received in access to the above-mentioned downlink media streaming, method.

8. In Paragraph 7, Based on the above reporting parameters, information on multiple CDNs is collected, and Switching from a first CDN to a second CDN among the multiple CDNs based on at least one of the response time, average network round-trip time, network round-trip time variance, or congestion window size for the multiple CDNs, method.

9. A step of receiving metric information and consumption information collected by a Media Session Handler of a device providing media streaming in a wireless communication system; and A step of switching a Content Delivery Network (CDN) based on the above metric information and the above consumption information; comprising method.

10. In Paragraph 9, Network metrics are configured by a server, and the configured metrics are transmitted to the RAN (Radio Access Network), and If the above device is located in a geographically restricted area, a metric configuration from the RAN is transmitted to the media session handler of the above device, and Metric collection and reporting by the device are performed based on a streaming session, method.

11. In Paragraph 10, Media is downlink streamed to the device by the above server, and Based on downlink streaming for the above media, the metric is collected by the device, and The above metric is reported based on the control plane, and Based on the above metric, the Contents Delivery Network (CDN) is switched, method.

12. In Paragraph 9, The above metrics include reporting parameters for the selection of multiple CDNs and downlink media streaming, and The above reporting parameters are: The server's service endpoint for accessing the above-mentioned downlink media streaming, A protocol request method for accessing the above-mentioned downlink media streaming, Protocol request URL by the media player for accessing the above-mentioned downlink media streaming, Protocol version by a media player for accessing the above-mentioned downlink media streaming, Protocol request range for accessing the above-mentioned downlink media streaming, Protocol request size by the media player for accessing the above-mentioned downlink media streaming, A string describing a media player that has allowed access to the above-mentioned downlink media streaming, or including at least one of a string identifying a user who accessed the above-mentioned downlink media streaming, method.

13. In Paragraph 9, The above metrics include reporting parameters for the selection of multiple CDNs and downlink media streaming, and The above reporting parameters are: Referring URL reported by the media player, The server's cache status for accessing the above-mentioned downlink media streaming, The server's protocol response code for accessing the above-mentioned downlink media streaming, The size of the server's protocol response for accessing the above-mentioned downlink media streaming, or A server protocol response content type for accessing the above-mentioned downlink media streaming, comprising at least one of method.

14. In Paragraph 9, The above metrics include reporting parameters for the selection of multiple CDNs and downlink media streaming, and The above reporting parameters are: The server's response time for the above-mentioned downlink media streaming in response to the media player's request, Average network round-trip time of protocol sessions received in access to the above downlink media streaming, Network round-trip time distribution of protocol sessions received in access to the above-mentioned downlink media streaming, or Comprising at least one of the congestion window size for a protocol session received in access to the above-mentioned downlink media streaming, method.

15. In Paragraph 14, Based on the above reporting parameters, information on multiple CDNs is collected, and Switching from a first CDN to a second CDN among the multiple CDNs based on at least one of the response time, average network round-trip time, network round-trip time variance, or congestion window size for the multiple CDNs, method.

Images