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

Abstract

A method for providing media streaming in a wireless communication system may comprise the steps of: calling, by an application, an initialize method to generate an instance of a media player; calling, by the instance of the media player, an attach method to set a source URL to a media presentation description (MPD) file; calling, by the instance of the media player, a preload method for starting streaming of media set by the attach method; and calling, by the instance of the media player, a play method for starting playback of the media set by the attach method. The method for providing media streaming in a wireless communication system may comprise the steps of: transmitting a media presentation description (MPD) to an apparatus for providing media streaming in a wireless communication system; transmitting media to the apparatus for providing media streaming; and receiving notification information from the apparatus for providing media streaming in the wireless communication system.

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] Multimedia streaming technology has continuously advanced to efficiently provide media content of various qualities, depending on network environment constraints and the performance of user terminals. In particular, 3GPP TS 26.512, standardized by 3GPP, defines methods to provide users with a stable and seamless streaming experience by specifying that media players must support different media formats. This specification presents technical requirements for media players to handle various video and audio codecs, adaptive bitrate streaming methods, and segment-based transmission structures.

[0003] One of the key elements of a streaming system is the Media Presentation Description (MPD) file. An MPD is a technical description file that outlines the structure and metadata of media content, containing the information necessary for a media player to determine which content to download and play, when, at what quality, and which segments to download. For example, an MPD describes metadata such as the content's playback time structure, segment information by adaptive quality, available bandwidth conditions, and codec format; based on this, the player establishes a streaming strategy tailored to network conditions.

[0004] However, there are several technical limitations to the operation of conventional media players. The pause function of existing media players is configured to operate only after the internal buffer is filled to a certain level, which causes delays in service environments requiring immediate playback or transmission control. Even when media data is provided in a broadcast format, the design operates under the premise of buffer loading; consequently, unnecessary buffering delays may occur in broadcast-based streaming services where real-time performance is critical.

[0005] Conventional technology is designed to maintain a buffer-based loading structure even when a User Equipment (UE) enters low-power mode, which presents a problem in that efficient control to reduce power consumption in low-power states is difficult. This structure of conventional technology causes issues such as increased battery consumption, reduced immediacy in broadcast-based services, and a lack of adaptability to changes in network conditions, thereby increasing the need for improved media playback control technology.

[0006] The method according to the embodiments goes beyond a method of providing a streaming service in which a media player interprets MPDs to control the transmission and playback of content, and further includes a more sophisticated and flexible control method due to network variability, various terminal environments, and user-customized playback requirements.

[0007] The method according to the embodiments aims to provide a new media playback control method that improves the Media Player model defined in 3GPP TS 26.512 and does not use or minimizes the existing buffer-based operation structure.

[0008] Accordingly, the technical objective according to the embodiments is to provide a structure that enables a media player to perform playback control without a buffering procedure, and to propose a media buffer-less or low-buffer-less media player model that improves immediacy in broadcast-based streaming environments and allows for efficient operation even in low-power operating environments. Through this, the objective is to provide an enhanced media playback structure that operates flexibly according to network status and power conditions.

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

[0010] A method for providing media streaming in a wireless communication system may include: a step of calling an initialize method to create an instance of a media player by an application; a step of calling an attach method by the instance of the media player to set a source URL to a Media Presentation Description (MPD) file; a step of calling a preload method by the instance of the media player to start streaming the media set by the attach method; and a step of calling a play method by the instance of the media player to start playback of the media set by the attach method. A method for providing media streaming in a wireless communication system may include: a step of transmitting a Media Presentation Description (MPD) to a device providing media streaming in a wireless communication system; a step of transmitting media to a device providing media streaming; and a step of receiving notification information from a device providing media streaming in a wireless communication system.

[0011] The method and apparatus according to the embodiments have the effect of solving the problems in the prior art where delays occur in the pause, play, and transmission control processes due to dependence on the buffer charge state, real-time performance is degraded by performing the same buffer loading operation even in broadcast-based media, and unnecessary power consumption occurs because the buffer usage structure is maintained even when the UE enters a low-power mode.

[0012] The method and apparatus according to the embodiments can efficiently support low-power operation for media playback.

[0013] Due to the method and apparatus according to the embodiments, the UE can significantly reduce power consumption related to unnecessary wireless interface activation, decoding operations, buffer management, etc.

[0014] Due to the method and apparatus according to the embodiments, the energy efficiency of the media consumption process in a wireless communication environment is significantly improved, and battery consumption can be minimized even in situations of long-term media streaming.

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

[0016] FIG. 1 shows a structure diagram of an interface and an API (Application Programming Interface) for downlink media streaming according to embodiments.

[0017] FIG. 2 shows the architecture of a DASH-based 5GMSd client according to embodiments.

[0018] FIG. 3 shows a media player model according to embodiments.

[0019] FIG. 4 shows the input parameters of Downloadandstore according to the embodiments.

[0020] FIG. 5 shows a change in the media player state according to the embodiments.

[0021] FIGS. 6A, FIGS. 6B, and FIGS. 6C illustrate media player notification events according to embodiments.

[0022] FIG. 7 illustrates a method for providing media streaming in a wireless communication system according to embodiments.

[0023] FIG. 8 shows a device that provides media streaming in a wireless communication system according to embodiments.

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

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

[0026] A method for providing media streaming in a wireless communication system according to embodiments and a device for providing media streaming in a wireless communication system are referred to hereinafter, for short, as the method and device according to embodiments.

[0027] The method according to the embodiments includes an efficient receiver operation method for processing media data in 5G media streaming. The wireless communication according to the embodiments is described as 5G by way of example, but is not limited to 5G and is interpreted as a term including all wireless communication technologies such as 5G-Advanced, 6G, etc.

[0028] The method according to the embodiments includes a method for improving the efficiency of the operation of a media player in 5G media streaming.

[0029] FIG. 1 shows a structure diagram of an interface and an API (Application Programming Interface) for downlink media streaming according to embodiments.

[0030] The method according to the embodiments can be performed based on the interface and API (Application Programming Interface) structure for downlink media streaming of FIG. 1.

[0031] For the structural diagram of Fig. 1, refer to Figure 3A.2.1-1 of the standard document TS 26.511.

[0032] A media playback platform according to the embodiments is initialized by an access client and configured to create a streaming session for downlink media streaming. The access client handles the download of media content divided into segments via the interface M4d, and this specification is based on a virtual playback model for playing segment-based media content transmitted via 5G media streaming (5GMS) on a UE. Accordingly, a 5GMSd Aware Application and a Media Access Client can play CMAF-based streaming content delivered via downlink. Additionally, the requirements for CMAF content are to comply with the specifications defined in the CTA WAVE Device Playback Specification.

[0033] A media player according to the embodiments includes the following functions and components.

[0034] The media player must support the minimum codec metric defined by reference to CTA-5003, and MIME type and codec parameter information according to RFC 6381 must be provided.

[0035] The media player performs codec-based player platform initialization by providing appropriate initialization information, and initializes the decoder using at least the CMAF header. If the content is encrypted, the initialization procedure may vary depending on the requirements of the applied DRM system.

[0036] In addition, the media player adds data to the source buffer and track buffer, and performs playback control functions including operations such as seek, trick play, and random access.

[0037] In addition, the media player provides a function to query the state of the player platform to check the size of the media buffer, buffer duration, current playback position, etc. Through the interface M7d, the player platform state can be received using the relevant API exposed by the 5GMSd Client, and notifications and events occurring in situations such as non-conformant content and buffer underruns can be reported.

[0038] Referring to FIG. 1, a method according to the embodiments is performed based on an interface and functional components for performing downlink media streaming between a terminal (UE) and a 5GMSd application provider according to the embodiments. The terminal includes a 5GMSd-Aware Application and a 5GMSd Client, wherein the 5GMSd Client is composed of a Media Session Handler, a Media Player, and an Access Client. The 5GMSd-Aware Application exchanges control signals with the 5GMSd application provider through an interface M8d.

[0039] The media session handler interacts with the media player and access client through interface M6d, and exchanges session control and policy information with the 5GMSd AF through interface M5d. The media player includes a Media Playback and Content Decryption Platform (TS 26.511) that performs media playback and content decryption, and exchanges capability information, playback control, status information, subscriptions and notifications, etc. with the access client through interface M7d.

[0040] Meanwhile, the 5GMSd application server (5GMSd AS) includes a Manifest Server and a CMAF Segment Server, and provides segmented media content and related metadata to access clients through interface M4d. Additionally, the 5GMSd AF communicates with application providers through interface M1d, and the 5GMSd AS exchanges unique control signals through interface M2d.

[0041] Accordingly, FIG. 1 systematically illustrates the functional relationships and interface flows between internal terminal components and external 5GMSd application providers in a Downlink media streaming environment.

[0042] With this configuration, the Media Player can provide stable and interoperable playback functions in a 5G-based Downlink media streaming environment and effectively support adaptive streaming under various network conditions.

[0043] FIG. 2 shows the architecture of a DASH-based 5GMSd client according to embodiments.

[0044] FIG. 2 is a diagram showing the architecture and functional structure of a DASH-based 5GMSd client according to embodiments. The DASH-based 5GMSd client shown in FIG. 2 consists of a 5GMSd-Aware Application, a Media Player, an Access Client, Media Playback Management and Protection Controller, Media Playback and Content Decryption Platform, etc., each of which is interconnected for the efficient download, processing, and playback of 5G media streaming services.

[0045] The 5GMSd-Aware Application is an application that plays DASH media through a DASH-based media player, and performs configuration information, control information, event notifications, and internal status queries of the media presentation through the M7d interface. The Media Player is a module that performs the playback and decryption of media content, and provides a content playback platform and decryption functions.

[0046] The Access Client is part of the DASH player and performs the role of downloading resources for media access and providing the downloaded resources to the media playback platform and content decryption function.

[0047] Management includes management functions that control communication between all internal processes and 5GMSd-Aware Applications, and performs control operations such as service description and processing of operation points.

[0048] The MPR Processing function parses and processes MPR (MPD) to extract necessary service information and metadata.

[0049] The Adaptation Set Selection function selects an appropriate Adaptation Set based on user characteristics, application requirements, or terminal functions, and information provided through the M7d interface can be referenced.

[0050] The ABR Controller and Dynamic Switching function executes a bitrate adaptation algorithm and triggers stream switching based on network conditions and application requirements, and control information transmitted through the M7d can be used in this process.

[0051] The Throughput Estimation function estimates the throughput of the 5GMSd application server and operates to recommend an appropriate bitrate to the 5GMS AF based on this.

[0052] The Metric Logging feature logs low-level media-related metrics and provides metric aggregation and reporting capabilities for the Media Session Handler.

[0053] The Media Playback Management and Protection Controller delivers downloaded media information to the playback platform and manages DRM-related protection and access control.

[0054] The Media Playback and Content Decryption Platform plays CMAF-based media content by satisfying the playback requirements defined in 3GPP TS 26.511 and provides status information to the 5GMSd-Aware Application through the M7d interface.

[0055] The Event Processing function processes DASH events and transmits event information related to 5GMSd-Aware Applications as defined in 3GPP TS 26.247.

[0056] Meanwhile, the Media Stream Handler operates based on the M7 and M11 interfaces.

[0057] The 5GMS Aware Application of Reference Point M7 or the Media Session Handler of Reference Point M11 defines a set of APIs and methods for communicating with the Media Stream Handler. The APIs are independent of the language and runtime environment and can be implemented in various forms depending on the runtime environment supported by the terminal.

[0058] It is assumed that the DASH-based media player follows the structure shown in Fig. 2 and downloads, processes, and displays DASH media presentations under M7d control via the 5GMSd-Aware Application or M11d control via the Media Session Handler.

[0059] The 5GMSd-Aware Application configures additional media presentations, receives event notifications, or queries the internal state of the DASH Player through the M7d reference point. Generally, additional features such as various functions of the DASH Access Client required to process DASH media presentations may be provided.

[0060] Furthermore, the 5G media streaming system distinguishes the functional roles between components through various reference points. M1 is a reference point for providing media delivery between the media application provider and the media AF, and M2 is a reference point for ingesting into or extruding from the media AS. M3 is a reference point for configuration and session processing between the media AF and the media AS, and M4 is used for downlink or uplink media transmission between the media AS and the terminal's media access function. M5 is a reference point between the media AF and the media client's Media Session Handler, and M6 is a reference point for configuration between the media awareness application and the Media Session Handler. M7 is a reference point for media access control between the media awareness application and the media access function, and M8 is a reference point between the media awareness application and the media application provider. Additionally, M11 serves as a reference point for session configuration and access control between the media session handler and the media access function, performing control procedures and policy delivery within the terminal. M12 is a reference point between one media access function and another function for peer-to-peer media transmission between different media clients, if allowed by the 5G system.

[0061] The 5GMSd client and reference point structure according to these embodiments provides cooperative operation between components to maximize the adaptability, efficiency, and quality of service of DASH-based media streaming, and has the technical advantage of being able to flexibly respond to network conditions and user requirements.

[0062] FIG. 2 is a diagram illustrating the architecture of a DASH-based 5GMSd (5G Media Streaming downlink) client according to embodiments. As shown in FIG. 2, the 5GMSd client includes a structure composed of a 5GMSd-Aware application, a media session handler, a 5GMSd AF (Application Function), and a media player.

[0063] The 5GMSd-Aware application provides the media player with settings and configurations, method calls, status information, notifications, and error information related to the overall operation of the 5GMSd client through the M7d interface. Additionally, the application interacts with the 5GMSd application provider through the M8d interface.

[0064] The media session handler interacts with the 5GMSd AF through the M5d interface and performs session control and metric reporting functions. The media session handler communicates with the media player through the M11d interface and controls session-related procedures such as session creation, termination, and policy delivery.

[0065] The media player consists of an access client, a media playback management and protection controller, and a media playback and content decoding platform defined in TS 26.511. The media playback management and protection controller manages the media player's capability information, playback information, status, subscriptions, and notifications, and performs content protection and access control functions.

[0066] The access client includes a management module and a download module, and supports the efficient transmission and playback of DASH-based streaming by performing functions such as MPD processing, adaptation set selection, Adaptive Bitrate (ABR) control and dynamic switching, request scheduling, throughput estimation, event processing, client metadata management, and metric collection.

[0067] In addition, the media player obtains DASH segments from the 5GMSd AS, which includes the CMAF segment server and the MPD server, through the M4d interface and performs content playback.

[0068] Accordingly, the DASH-based 5GMSd client architecture according to the embodiments illustrated in FIG. 2 provides a multi-layered structure, session-based control, adaptive streaming control, and metric-based optimization functions to improve media streaming quality in a 5G environment.

[0069] FIG. 3 shows a media player model according to embodiments.

[0070] The state of the media player model according to the embodiments is as follows.

[0071] IDLE: The media player is not connected to any application.

[0072] INITIALIZED: The initialized media player is connected to the application, and M7d API communication is established.

[0073] READY: The media player has loaded the MPD and can play media in this media presentation. It also updates the MPD according to the MPD update mechanism.

[0074] Preloaded: The media player preloads all media information to start playback immediately. It also updates the MPD according to the MPD update mechanism.

[0075] PLAYING: The media player is playing a media presentation and continuously updates the MPD according to the MPD update mechanism.

[0076] DOWNLOADING: The media player downloads the media presentation and saves it to the media player so that it can be played later.

[0077] Paused: Playback of the media presentation is paused. Additionally, the MPD is updated according to the MPD update mechanism.

[0078] FIG. 3 illustrates a state transition model of a media player according to embodiments, based on the Media Player State Machine defined in TS 26.512. As shown in FIG. 3, the media player performs transitions between the INITIALIZED state, READY state, DOWNLOADING state, PRELOADED state, PLAYING state, PAUSED state, and IDLE state, each state corresponding to various operations related to media playback, preloading, downloading, pausing, recovery, and destruction. The INITIALIZED state is the state in which the player is initially initialized or re-initialized, and can be transitioned to the READY state or PRELOADED state by the attach(MPD) or preload(MPD) command, and can be maintained in the same state by the reset() command. The READY state refers to a state where the MPD is attached and basic playback preparation is complete, and it can transition to the DOWNLOADING, PRELOADED, PLAYING states through operations such as seek(MPD, time), preload(), play(), and downloadAndStore(). The DOWNLOADING state is the stage of downloading media segments from the network, entered by the downloadAndStore() operation, and can return to the READY or PRELOADED state after the download is complete, or transition to the IDLE state by the destroy() operation.

[0079] The PRELOADED state is a state where the initial segment of the media is preloaded; it transitions to the PLAYING state via the play() or seek(time) operation, and the same state can be updated by the preload(MPD) command. The PLAYING state is the state where the media is playing; it transitions to the PAUSED state via the pause() operation, restarts from the same state via the seek(time) command, or moves to the IDLE state via the destroy() command. The PAUSED state is a state where playback is paused; it returns to the PLAYING state via the play() command, allows seeking via the seek(time) command, and transitions to the IDLE state via the destroy() operation. The IDLE state signifies a state where the player has terminated or playback resources have been destroyed; it can re-enter the INITIALIZED state via the initialize() command.

[0080] The state transition model according to FIG. 3 is designed to allow the media player to respond flexibly to network conditions, user input, and session management commands (including M7 / M11 APIs), minimizes streaming latency through a continuous path of DOWNLOADING-PRELOADED-PLAYING, and ensures the continuity and adaptability of playback operations based on commands such as pause(), seek(), and preload(). In addition, it supports stable recovery in the event of an error state through state cleanup and recovery procedures represented by destroy(), reset(), and initialize(). This state model is linked with components included in the DASH-based playback engine and the 5GMSd client architecture (Fig. 2), and interacts with media access functions, session management functions, and event processing functions to enable efficient playback control and QoE improvement.

[0081] The function definition of the media player of FIG. 3 according to the embodiments is as follows.

[0082] Initialize()

[0083] This method is called to create a new media player instance. The Media Delivery Session identifier is assigned to the media delivery session by the media player and can be returned if the caller of the method does not provide a value. The input parameters are the ServiceId and the SessionId. The ServiceId is an external service identifier, and the media entry point URL received from the application provider to initiate media delivery can be provided as an input parameter. A Media Aware Application must assign a globally unique Media Delivery Session identifier to enable the media client to use subsequent interactions with the Media AF and Media AS. This identifier is the ServiceId. It attempts to obtain full service access information for the specified external service identifier from the Media AF, and if successful, returns the Media Delivery Session identifier to the caller of the API method. sessionId is the Media Delivery Session Identifier, and this parameter must be included when the method is called by the media session handler at reference point M6d, and omitted when the method is called by the 5GMSD Aware Application at reference point M7d.

[0084] The settings for media playback management, specifically the notification and error APIs and status information, are initialized to enable API-based communication via M7d or M11d. If the sessionId parameter is provided by the Media Session Handler at reference point M11d, the newly created media player instance must rely on the Media Session Handler assigning a media delivery session identifier as a side effect of calling the method specified in createMediaDeliverySession at reference point M11d. The media player then uses this value in subsequent interactions, specifically for the notification and error APIs and status information. The return value of Initialize() is the Media Delivery Session identifier, represented as a String.

[0085] Attach()

[0086] The Attach() method is entered only when the media player is in the INITIALIZED state.

[0087] The 5GMDS Aware Application calls attachMPD() on the media player instance to set the source URL to an MPD file or a previously downloaded and parsed MPD.

[0088] The expected behavior of the media player is as follows.

[0089] - Request Scheduling and Download functions are configured.

[0090] - If the input is a URL, the media player requests MPD from that URL via the reference point M4d.

[0091] - If the MPD cannot be found even after multiple retries, the error ERROR_MPD_NOT_FOUND is returned and the process terminates.

[0092] - The MPD processing function is configured, and the MPD is parsed.

[0093] - If the MPD is invalid, the error ERROR_MPD_NOT_VALID is returned and the process terminates.

[0094] - If the DASH player does not support the profile displayed in the MPD, the error ERROR_PROFILE_NOT_SUPPORTED is returned and the process terminates.

[0095] - Based on the type of MPD, available anchors, and wall-clock time—the actual operation time from the start to the end of a computer program—the media player selects the period of the content expected to be played next.

[0096] - Media Playback Management and Protection Controller are configured.

[0097] - The MPD is parsed for available service descriptions (including media subsets and adaptation sets). By using the functional mechanisms defined in TS 26.511 and other information (language settings, output functions, accessibility settings), the media player identifies an acceptable set of service descriptions, including media subsets and adaptation sets. If there is no playable adaptation set, the error ERROR_MEDIA_NOT_SUPPORTED is returned and the process terminates.

[0098] - The Service Description, including the Adaptation Set, is provided to the 5GMS Aware Application via reference point M7d.

[0099] - The application can select a Service Description instance and an Adaptation set.

[0100] - Additional service description parameters can be configured by the 5GMSd-Aware application through reference point M7d.

[0101] - The description of the service description parameter and adaptation set according to the embodiments is as follows.

[0102] 1) The Operation Point parameter is set.

[0103] 2) Media Playback Platform and Content Decryption is configured using the method defined in TS 26.511.

[0104] 3) The selected Adaptation Set is initialized by downloading the relevant initialization segment / CMAF header through the M4d of the media playback platform, such as TS 26.511, and sets the track buffer for each selected media type.

[0105] - One or more of the following functions may be set depending on MPD information and / or M7d configuration.

[0106] 1) Metrics logging and collection, 2) Event processing and notification, 3) Client metadata processing, 4) The media player switches to the READY state.

[0107] The application can use this method to load the MPD and prepare for playback. In the case of error notifications, it is up to the application to initiate appropriate action.

[0108] Pre-load()

[0109] The description of the Pre-load() method is as follows.

[0110] Preload() is entered when the media player is in the INITIALIZED or READY state. The Preload() method is called on the media player instance and starts media streaming as set to ready for playback by the attach() method.

[0111] The application can use this method to pre-load media into the player to minimize startup time.

[0112] The 5GMSd Aware Application calls preload() to start streaming in preparation for playing the media configured by the attach() method. The variable values ​​for Preload() are SessionId and urlOrMPD. SessionId is an identifier for the downlink media delivery session that does not contain data identifying the user, and it is represented in String format. The Access Client downloads this media by scheduling and generating a request for the relevant media segment based on ABR Controller information and throughput estimation (bit rate recommendation). The segment is downloaded from the corresponding URL via M4d, which is the fastest reference point at the time segment availability begins. The segment is appropriately added to the track buffer as configured by the Media Playback Platform and Content Decryption APIs, in accordance with the description of section 26.511 regarding playback requirements.

[0113] The expected media player behavior is as follows.

[0114] - If the state is INITIALIZED, the attach() method is called with the value of the urlOrMPD input parameter.

[0115] - The fastest media time range for preloading is identified based on the type of MPD, possible anchors, wall-clock time, and other MPD information.

[0116] - The Access Client schedules and generates requests for relevant media segments based on ABR Controller information and thru-out estimation, and downloads the media.

[0117] - The segment is downloaded from the corresponding URL via the reference point M4d prior to the segment's segment availability start time.

[0118] - The downloaded segment is appropriately added to the track buffer as set by the Media Playback Platform and Content Decryption API in accordance with the description of TS 26.511

[0035] for playback requirements.

[0119] - Configuration and service description parameters are taken into account. (e.g., content is continuously loaded to remain at the live edge based on latency requirements provided in the service description settings). Content not at the live edge is removed. For static services, content is loaded from the beginning until the appropriate buffer period (presumably as configured), and then the download is stopped.

[0120] - The media player switches to the PRELOADED state.

[0121] - Appropriate notifications and error messages are generated.

[0122] - Appropriate status information is generated.

[0123] Play()

[0124] The description of the Play() method is as follows.

[0125] The following prerequisites are required.

[0126] - The media player is in the INITIALIZED, READY, PRELOADED, or PAUSED state.

[0127] The play() method is called on the media player instance and starts media playback as set by the attach() method.

[0128] The expected media player actions are as follows.

[0129] - If the state is INITIALIZED, the attach() method is called internally to pass the value of the urlOrMPD input parameter.

[0130] - If in PAUSED state, the earliest media time becomes MEDIA_TIME; otherwise, the earliest media time for startup is identified based on the MPD type, available anchor, wall-clock time, and other MPD information.

[0131] The Access Client checks the available buffer status of the media on the media playback platform. Based on this, the Access Client schedules and generates a request for the relevant media segment based on ABR controller information and yield estimates, and downloads the media.

[0132] - Media segments are retrieved from the corresponding URL (via M4d or from local storage if already downloaded and saved) at the earliest of the segment availability start times.

[0133] - Media is appropriately added to the Media Playback Platform and Content Decryption API in accordance with the description of TS 26.511 regarding playback requirements.

[0134] - When the threshold value for sufficient buffering is reached, the media playback platform starts, i.e., playback begins, in accordance with the description of TS 26.511 regarding playback requirements.

[0135] - Content is continuously streamed, downloaded, and played.

[0136] - The media player switches to the PLAYING state.

[0137] - Appropriate notifications and error messages are generated.

[0138] - Appropriate status information is generated.

[0139] The application can use this method to start media playback.

[0140] Pause()

[0141] The description of the Pause() method is as follows.

[0142] The following prerequisites are required.

[0143] - The media player is playing.

[0144] The pause() method is called on the media player instance, and the media playback platform is paused.

[0145] The expected media player actions are as follows.

[0146] - Playback on the playback platform is paused and the media time is maintained at MEDIA_TIME.

[0147] The Access Client checks the available buffer status of the media on the media playback platform. Based on this, the Access Client generates reservations and requests for the relevant media segments based on ABR controller information and throughput estimates, and downloads the media.

[0148] - The media is downloaded first via reference point M4d at the start of the media segment availability at the corresponding URL.

[0149] - Media is appropriately added to the Media Playback Platform and Content Decryption API in accordance with the description of TS 26.511 regarding playback requirements.

[0150] - The client stops the download when the buffer is sufficiently filled.

[0151] - The media player switches to a paused state.

[0152] - Appropriate notifications and error messages are generated.

[0153] - Appropriate status information is generated.

[0154] The application can play media using this method.

[0155] Seek()

[0156] The description of the Seek() method is as follows.

[0157] The following prerequisites are required.

[0158] - The media player is in the INITIALIZED, READY, PRELOADED, or PAUSED state.

[0159] The seek() method is called on a media player instance to move to a specific media time.

[0160] The input parameters are sessionId, urlOrMPD, and mediaTime. Here, mediaTime is the media time for playback (in milliseconds).

[0161] - In the initial state, the attach() method is called internally to pass the value of the urlOrMPD input parameter.

[0162] - If mediaTime is inaccessible, the ERROR_MEDIA_TIME_NOT_ACCESSIBLE event is raised, and the following actions are not performed.

[0163] - The fastest media time is set to the value of the mediaTime input parameter.

[0164] - The media player switches to the PAUSED state.

[0165] - The play() method is called internally.

[0166] The application can start media playback using this method.

[0167] FIG. 4 shows the input parameters of Downloadandstore according to the embodiments.

[0168] Downloadandstore()

[0169] The description of the DownloadAndStore() method is as follows.

[0170] The following prerequisites are required.

[0171] - The media player is in the INITIALIZED or READY state.

[0172] DownloadAndStore() is called on the media player instance to download and save media according to the attach() method.

[0173] Reset()

[0174] The reset() method defines the function of initializing all information of the media player. The following prerequisites are required.

[0175] - The media player can be in any state.

[0176] When the 5GMSd-Aware Application calls reset(), all information related to the media and the media presentation described by the MPD (Media Presentation Description) is deleted.

[0177] - Playback ends on the playback platform.

[0178] - All open requests are canceled.

[0179] - All scheduled requests are deleted.

[0180] - The current MPD is removed.

[0181] - The media player is changed to remain in the INITIALIZED state.

[0182] Destroy()

[0183] The destroy() method defines the function of initializing all information related to the media player and network. The following prerequisites are required.

[0184] - The media player can be in any state.

[0185] When the 5GMSd-Aware Application calls destroy(), all information related to media and networks is reset.

[0186] - Playback ends on the playback platform.

[0187] - All open requests are canceled.

[0188] - All scheduled requests are deleted.

[0189] - The current MPD is removed.

[0190] - All network information records are erased.

[0191] FIG. 5 shows a change in the media player state according to the embodiments.

[0192] Change media player status

[0193] When transitioning from PLAYING to PASUED, the function that saves MPD information to the buffer in advance while in the paused state is called pause(). The added SLEEP mode refers to a state where, if the UE is detected to be in low-power mode after entering the paused state, the function of saving to the buffer is not performed. The conditions for entering SLEEP mode vary depending on the implementation; for example, it may be the case where the UE operates in battery-saving mode as in 1). Or, as in 2), there is the case of a media player that supports ultra-low power mode.

[0194] 1) The conditions for entering battery saver mode vary for each UE, and in most cases, follow one of the following scenarios.

[0195] i) When the UE operates at high temperatures, it forcibly lowers throughput due to throttling.

[0196] ii) If the antenna SAR (Specific Absorption Rate) backoff limit is exceeded, the UE automatically switches to low-power mode to reduce the SAR value. In this mode, the antenna output is limited or the device's communication method is changed to reduce the signal strength.

[0197] iii) Battery saver mode is automatically turned on when the battery level drops to about 20% or less, and the user can adjust this threshold.

[0198] 2) Enter if the terminal is an NR-light or RedCAP UE.

[0199] NR-light refers to a device introduced in Release 17 that supports only reduced capability; it is an entry-level IoT UE that does not fully support NR. It has peak data rate limits of 150 Mbps for downlink and 50 Mbps for uplink. Because it has reduced capability, it is referred to by the abbreviation RedCAP UE.

[0200] 3) When the UE watches broadcast media, even if it is not downloaded to the buffer during pause, it does not affect the end user's media viewing when playback resumes after the pause is released.

[0201] In the case of broadcast media, after opening the MBMS initial bearer, the media player operates using the MBMS bearer. In this case as well, the sleep entry condition is satisfied.

[0202] SLEEP mode needs to be added because the current user scenario requires bandwidth capable of handling more than 30 8K frames per second when transmitting volumetric metadata in the future, and to prevent UE battery drain issues.

[0203] Sleep state according to the embodiments:

[0204] Sleep is a state for low-power streaming that calculates the minimum frame loading without interruption at a recommended bit rate through throughput estimation to minimize or not use the buffer.

[0205] The input parameter of the Sleep() method is the session ID (sessionId), and there is no return value.

[0206] Input parameters of the sleep() method

[0207] NameTypeDescriptionsessionIdString Media delivery session identifier of an initialized downlink media streaming session (as specified in Clause 7.3.2 of TS 26.510 and Clause 10.1A of this document).

[0208] The description of the Sleep() method is as follows.

[0209] The following prerequisites are required.

[0210] - The media player is playing or paused.

[0211] The sleep() method is called on the media player instance, causing the media playback platform to enter sleep mode.

[0212] The expected media player actions are as follows.

[0213] The transition between the sleep state and the pause state is as follows.

[0214] - If the sleep state condition is entered during a pause, the media time is saved as MEDIA_TIME. For example, to return to the pause and resume media playback, the time information I was watching needs to be saved.

[0215] - Stop the download.

[0216] FIGS. 6A, FIGS. 6B, and FIGS. 6C illustrate media player notification events according to embodiments.

[0217] The media player notification event according to the embodiments further includes notification and error events. The notification and error events can be notified to the server.

[0218] The media player notification event according to the embodiments may refer to the media player notification event of standard TS 26.512. The media player notification event according to the embodiments further includes a playback slip (PLAYBACK_SLEPT).

[0219] PLAYBACK_SLEPT: Status information transmitted when playback is paused, and includes a media transmission session identifier.

[0220] FAST_IN_FUTURE: An event indicating that playback is scheduled rather than starting immediately when the MPD's availabilityStartTime is a future point in time. The payload includes the Media delivery session identifier and the Time before playback will start.

[0221] AVAILABLE_MEDIA_CHANGED: An event triggered when the list of available media changes. As a payload, it includes a media delivery session identifier, and the media type includes, for example, video, audio, subtitles, etc.

[0222] BUFFER_EMPTY: Occurs when the buffer of the media playback platform is exhausted and playback cannot proceed. As a payload, it includes a media delivery session identifier and a media type.

[0223] BUFFER_LOADED: Occurs when the buffer is refilled and transitions to a state where normal playback is possible. As a payload, it includes a media delivery session identifier and a media type.

[0224] CAN_PLAY: Indicates that there is enough data to play media. As a payload, it includes a media delivery session identifier.

[0225] MANIFEST_LOADED: Occurs when the manifest file (Manifest) is successfully loaded. It contains the Media delivery session identifier as the payload.

[0226] METRIC_ADDED: Occurs whenever a new metric item is added. As a payload, it contains the media delivery session identifier.

[0227] METRIC_CHANGED: Triggered when the minimum bitrate of the ABR (Adaptive Bitrate) algorithm changes (NaN means no limit). As a payload, it includes a media delivery session identifier.

[0228] METRIC_UPDATED: Occurs when a DASH client is configured to continue downloading fragments in the background or when a metric is updated. As a payload, it contains a media delivery session identifier.

[0229] METRICS_CHANGED: An event that occurs when a change is detected among the total metric values. As a payload, it includes a media delivery session identifier.

[0230] OPERATION_POINT_CHANGED: Occurs when the selected operation point (such as a Quality of Service profile) changes. As a payload, it includes a media delivery session identifier and an external reference identifier of the currently selected service operation point.

[0231] PLAYBACK_ENDED: Transmitted when media playback has ended normally. As a payload, it includes a media delivery session identifier.

[0232] PLAYBACK_ERROR: An event transmitted when an error occurs during playback, containing error attribute information. As a payload, it includes a media delivery session identifier and error attributes.

[0233] PLAYBACK_PAUSED: Transmitted when playback is paused. As a payload, it includes a media delivery session identifier.

[0234] PLAYBACK_SLEEP(PLAYBACK_SLEPT): An event sent when playback enters a sleep state (inactive state). As a payload, it includes a media delivery session identifier.

[0235] PLAYBACK_PLAYING: Occurs when media is first played, plays after a pause, or resumes playback after a seek. As a payload, it includes a media delivery session identifier.

[0236] PLAYBACK_SEEKED: Transmitted when the seek operation is complete. As a payload, it includes a media delivery session identifier.

[0237] PLAYBACK_SEEKING: Occurs when a seek operation is in progress. As a payload, it contains a media delivery session identifier.

[0238] PLAYBACK_STALLED: Occurs when the playback platform is paused (stopped) due to reasons such as insufficient buffer. As a payload, it includes a media delivery session identifier.

[0239] PLAYBACK_STARTED: Occurs when playback starts. Includes resuming playback after pause. As a payload, it includes a media delivery session identifier.

[0240] PLAYBACK_WAITING: Occurs when playback is interrupted because the playback platform can no longer continue playback due to insufficient data or other reasons. As a payload, it includes a media delivery session identifier.

[0241] SERVICE_DESCRIPTION_SELECTED: Occurs when a DASH client selects a new Service Operation Point. As a payload, it contains a media delivery session identifier.

[0242] SERVICE_DESCRIPTION_CHANGED: DASH is sent when the client changes the service description. As a payload, it includes a media delivery session identifier.

[0243] SERVICE_DESCRIPTION_VIOLATED: Provides a notification that the current service description parameter is not satisfied. As a payload, it includes a media transport session identifier and the unsatisfied service description parameter.

[0244] SOURCE_INITIALIZED: Occurs when a media source is initialized and ready. As a payload, it contains the media delivery session identifier.

[0245] FIG. 7 illustrates a method for providing media streaming in a wireless communication system according to embodiments.

[0246] A method according to the embodiments (e.g., a method by a UE (client)) may include the step of calling an initialize method to create an instance of a media player by an application (S700); the step of calling an attach method to set a source URL to a Media Presentation Description (MPD) file by the instance of the media player (S710); the step of calling a preload method to start streaming the media set by the attach method by the instance of the media player (S720); the step of calling a play method to start playback of the media set by the attach method by the instance of the media player (S730); etc.

[0247] S700, S710, S720 and / or S730, etc., may include the aforementioned operations to perform states and methods such as those in FIGS. 3 and FIGS. 5 on the structure of FIGS. 1 and FIGS. 2.

[0248] FIG. 8 shows a device that provides media streaming in a wireless communication system according to embodiments.

[0249] A method according to the embodiments (e.g., a method by a server) may include the step of transmitting a Media Presentation Description (MPD) to a device providing media streaming in a wireless communication system (S800); the step of transmitting media to the device providing media streaming (S810); the step of receiving notification information from the device providing media streaming in a wireless communication system (S820); and the like.

[0250] S800, S810 and / or S820, etc., may include the aforementioned operations to perform states and methods such as those in FIGS. 3 and FIGS. 5 on the structure of FIGS. 1 and FIGS. 2. The client method of FIGS. 7 and the server method of FIGS. 8 may correspond to each other in reverse processes.

[0251] With respect to the media player methods initialize, Attach, preload, Play, etc. of FIG. 7 and FIG. 3, the method according to the embodiments may include: a step of calling an initialize method to create an instance of the media player by an application; a step of calling an attach method to set a source URL to a Media Presentation Description (MPD) file by the instance of the media player; a step of calling a preload method to start streaming the media set by the attach method by the instance of the media player; and a step of calling a play method to start playback of the media set by the attach method by the instance of the media player.

[0252] With respect to the pause and seek methods of the media player in FIG. 7 and FIG. 3, the method according to the embodiments may further include the step of calling a pause method to pause the playback of the media playback platform by an instance of the media player; and the step of calling a seek method to move to a specific media time by an instance of the media player in a playing state for the playback of the media.

[0253] With respect to the media player methods Download and store, reset, and destroy in FIG. 7 and FIG. 3, the method according to the embodiments may further include the step of calling a Download and store method to download and store media by the Attach method in at least one of an initialized state by the Initialize method or a ready state by the Attach method; the step of calling a reset method to terminate media presentation by the MPD and reset all information related to the media; and the step of calling a destroy method to reset the network and all information related to the media.

[0254] FIG. 5. With respect to the sleep state during the change of the media player state, the method according to the embodiments further comprises the step of calling a sleep method to enter the sleep state of the media playback platform by an instance of the media player in at least one of the playing state of the media player by the Play method or the pause state by the Pause method; and when entering the sleep state from the pause state, the media time is saved and the media download is stopped.

[0255] With respect to the notification in FIGS. 6A, 6B, and 6C, the method according to the embodiments further comprises the step of transmitting notification information to a server; and the notification information may include at least one of: playback end information (PLAYBACK_ENDED) indicating the completion of playback; playback error information (PLAYBACK_ERROR) indicating the occurrence of an error; or playback pause information (PLAYBACK_PAUSED) indicating the pause of playback.

[0256] With respect to the notification in FIGS. 6A, FIGS. 6B, and FIGS. 6C, the notification information may further include at least one of: playback playing information (PLAYBACK_PLAYING) indicating the start time of media playback; playback seeking information (PLAYBACK_SEEKED) indicating the completion of an operation regarding a seek method; playback seeking information (PLAYBACK_SEEKING) indicating the start of an operation regarding a seek method; playback stall information (PLAYBACK_STALLED) indicating a stop of the media playback platform; playback start information (PLAYBACK_STARTED) indicating the start of media playback after a pause in playback; or playback waiting information (PLAYBACK_WAITING) indicating a stop of media playback due to a temporary lack of data.

[0257] In relation to 'PLAYBACK_SLEPT' in the notifications of FIGS. 6A, 6B, and 6C, the notification information may further include: playback sleep information (PLAYBACK_SLEPT) indicating the sleep state of the playback.

[0258] With respect to the media delivery session ID in the notification payload in FIGS. 6A, FIGS. 6B, and FIGS. 6C, the notification information payload may include a media delivery session ID.

[0259] A method for providing media streaming in a wireless communication system may be performed by a device that provides media streaming in a wireless communication system. The device includes memory; and at least one processor connected to the memory; and the at least one processor may be configured to: call an initialize method to create an instance of a media player by an application; call an attach method to set a source URL to an MPD file by an instance of the media player; call a preload method to start streaming of the media set by the attach method by an instance of the media player; and call a play method to start playback of the media set by the attach method by an instance of the media player.

[0260] Referring to FIG. 8, FIG. 6A, FIG. 6B, FIG. 6C, FIG. 2, etc., a method according to the embodiments may include the steps of: transmitting a Media Presentation Description (MPD) to a device providing media streaming in a wireless communication system; transmitting media to the device providing media streaming; and receiving notification information from the device providing media streaming in a wireless communication system. The method of FIG. 8 is performed by a device providing media streaming in a wireless communication system, and the device includes a memory; and at least one processor connected to the memory; and the at least one processor may be configured to: transmit a Media Presentation Description (MPD) to a device providing media streaming in a wireless communication system; transmit media to a device providing media streaming; and receive notification information from the device providing media streaming in a wireless communication system.

[0261] The method and apparatus according to the embodiments can efficiently support low-power operation of a 3GPP UE by adding a sleep status to the status information of a media player. For example, if the media player switches to a sleep status during periods when active media playback is not required, the terminal can significantly reduce power consumption related to unnecessary wireless interface activation, decoding operations, buffer management, etc. As a result, energy efficiency in the media consumption process in a wireless communication environment is significantly improved, and battery consumption can be minimized even during long-term media streaming. Furthermore, power saving by the terminal leads to a reduction in signaling load and improved efficiency of wireless resource utilization on the network side, providing benefits to both the user and the network. Therefore, the present invention has the effect of significantly improving technical performance for power optimization in UE-based media services.

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

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

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

[0265] 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.”

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

[0267] 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."

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

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

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

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

[0272] As described above, the embodiments may be applied wholly or partially to point cloud data transmission and reception devices and systems.

[0273] Those skilled in the art may make various changes or modifications to the embodiments within the scope of the embodiments.

[0274] The embodiments may include modifications / variations, and such modifications / variations do not exceed the scope of the claims and their equivalents.

Claims

1. A step of calling the initialize method to create an instance of the media player by the application; A step of calling an Attach method to set the source URL to an MPD (Media Presentation Description) file by the instance of the above media player; A step of calling a preload method to start streaming the media set by the attach method by the instance of the media player; and The step of calling a Play method to start playback of the media set by the Attach method by the instance of the media player; comprising A method for providing media streaming in a wireless communication system.

2. In paragraph 1, the above method is: A step of calling a pause method to pause playback of a media playback platform by an instance of the media player; and The method further comprises the step of calling a seek method to move to a specific media time by an instance of the media player in a playing state for the playback of the media. A method for providing media streaming in a wireless communication system.

3. In paragraph 2, the above method is: A step of calling a Download and Store method for downloading and storing media by the Attach method in at least one of the initialized state by the initialize method or the ready state by the Attach method; A step of terminating media presentation by MPD and calling a reset method to reset all information related to the media; and The method further comprises the step of calling a destroy method to reset all information related to the network and the media. A method for providing media streaming in a wireless communication system.

4. In paragraph 1, the above method is: The method further comprises the step of calling a sleep method to enter a sleep state of a media playback platform by an instance of the media player in at least one of the playing state of the media player by the Play method or the pause state by the Pause method. When entering the sleep state from the above pause state, the media time is saved and the media download is stopped. A method for providing media streaming in a wireless communication system.

5. In paragraph 4, the above method is: It further includes the step of transmitting notification information to a server, and The above notification information is: Playback end information (PLAYBACK_ENDED) indicating the completion of playback; Playback error information (PLAYBACK_ERROR) indicating the occurrence of an error; or at least one of playback pause information (PLAYBACK_PAUSED) indicating a pause in playback, A method for providing media streaming in a wireless communication system.

6. In Paragraph 5, The above notification information is: Playback Playing Information (PLAYBACK_PLAYING) representing the media's playback start time; Playback Seeked information (PLAYBACK_SEEKED) indicating the completion of an operation regarding the seek method; Playback Seeking Information (PLAYBACK_SEEKING) indicating the start of an operation regarding the seek method; Playback stall information (PLAYBACK_STALLED) indicating a stop of the media playback platform; Playback start information (PLAYBACK_STARTED) indicating the start of media playback after playback pause; or further comprising at least one of playback waiting information (PLAYBACK_WAITING) indicating a stop of media playback due to a temporary lack of data, A method for providing media streaming in a wireless communication system.

7. In Paragraph 5, The above notification information is: further including playback sleep information (PLAYBACK_SLEPT) indicating the sleep state of playback, A method for providing media streaming in a wireless communication system.

8. In Paragraph 5, The payload of the above notification information includes a media delivery session ID, A method for providing media streaming in a wireless communication system.

9. Memory; and At least one processor connected to the memory; comprising, wherein the at least one processor: Call the initialize method to create an instance of the media player by the application; Call the Attach method to set the source URL to an MPD file by the instance of the above media player; Calling a preload method to start streaming the media set by the attach method by the instance of the media player; and Configured to call a Play method to start playback of the media set by the Attach method by the instance of the media player, A device that provides media streaming in a wireless communication system.

10. A step of transmitting a Media Presentation Description (MPD) to a device providing media streaming in a wireless communication system; A step of transmitting media to a device providing the above media streaming; and A method comprising the step of receiving notification information from a device providing media streaming in a wireless communication system, A method for providing media streaming in a wireless communication system.

11. In paragraph 10, the above method is: The above notification information is: Playback end information (PLAYBACK_ENDED) indicating the completion of playback; Playback error information (PLAYBACK_ERROR) indicating the occurrence of an error; or at least one of playback pause information (PLAYBACK_PAUSED) indicating a pause in playback, A method for providing media streaming in a wireless communication system.

12. In Paragraph 11, The above notification information is: Playback Playing Information (PLAYBACK_PLAYING) representing the media's playback start time; Playback Seeked information (PLAYBACK_SEEKED) indicating the completion of an operation regarding the seek method; Playback Seeking Information (PLAYBACK_SEEKING) indicating the start of an operation regarding the seek method; Playback stall information (PLAYBACK_STALLED) indicating a stop of the media playback platform; Playback start information (PLAYBACK_STARTED) indicating the start of media playback after playback pause; or further comprising at least one of playback waiting information (PLAYBACK_WAITING) indicating a stop of media playback due to a temporary lack of data, A method for providing media streaming in a wireless communication system.

13. Memory; and At least one processor connected to the memory; comprising, wherein the at least one processor: Transmit MPD (Media Presentation Description) to a device providing media streaming in a wireless communication system; Transmitting media to a device providing the above media streaming; and Configured to receive notification information from a device providing media streaming in a wireless communication system, A device that provides media streaming in a wireless communication system.

Images