KR20240060282A - Method and apparatus to provide adaptive split rendering in communication system - Google Patents

Abstract

This disclosure relates to 5G or pre-5G communication systems to support higher data rates after 4G communication systems such as LTE.
The present disclosure provides a method of operating a terminal in a communication system, and the operating method includes, from an application provider (AP) device, an adaptive split rendering policy (ASR policy) applied by the AP device. An operation of receiving, based on the ASR policy, an operation of transmitting a SAI request requesting service access information (SAI) to an application function (AF) device, in response to the SAI request, An operation of receiving, from an AF device, an MPE uniform resource locator (MPE URL) response including a media play entry (MPE), based on the MPE URL response, an adaptive split rendering signaling server. : An operation of transmitting an MPE request requesting the MPE to an ASRSS), and in response to the MPE request, a media presentation description for Web Real-Time Communication (WebRTC) from the ASRSS. : MPD) and adaptive split rendering media play entry (ASRMPE) including session description protocol (SDP) for 5th generation media streaming (5GMS) communication. Includes receiving operations.

Description

Method and apparatus for providing adaptive split rendering in a communication system {METHOD AND APPARATUS TO PROVIDE ADAPTIVE SPLIT RENDERING IN COMMUNICATION SYSTEM}

This disclosure relates to a method and apparatus for providing adaptive split rendering in a communication system.

In order to meet the increasing demand for wireless data traffic following the commercialization of the 4G (4th generation) communication system, efforts are being made to develop an improved 5G (5th generation) communication system or pre-5G communication system. For this reason, the 5G communication system or pre-5G communication system is called a Beyond 4G Network communication system or a Post LTE (Long Term Evolution) system.

To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (such as the 60 GHz band). In order to alleviate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, the 5G communication system uses beamforming, massive array multiple input/output (massive MIMO), and full dimension multiple input/output (FD-MIMO). ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, to improve the network of the system, the 5G communication system uses evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), and ultra-dense networks. , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation. Technology development is underway.

In addition, the 5G system uses FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding), which are advanced coding modulation (ACM) methods, and FBMC (Filter Bank Multi Carrier), which is an advanced access technology. ), NOMA (Non Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access) are being developed.

Meanwhile, the Internet is evolving from a human-centered network where humans create and consume information to an IoT (Internet of Things) network that exchanges and processes information between distributed components such as objects. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection to cloud servers, etc., is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, sensor networks for connection between objects and machine to machine communication have been developed. , M2M), and MTC (Machine Type Communication) technologies are being researched. In the IoT environment, intelligent IT (Internet Technology) services can be provided that create new value in human life by collecting and analyzing data generated from connected objects. IoT is used in fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart home appliances, and advanced medical services through the convergence and combination of existing IT (Information Technology) technologies and various industries. It can be applied to .

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, 5G communications such as sensor network, Machine to Machine (M2M), and Machine Type Communication (MTC) are being implemented by techniques such as beam forming, MIMO, and array antenna. The application of cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of the convergence of 5G technology and IoT technology.

In the split rendering method, another device, for example a server, performs the rendering process to be performed on the terminal (or user equipment (UE)) on behalf of the terminal, and the rendered results according to the rendering process are sent to the terminal. In the split rendering method, in order for the server to perform the rendering process, not only information about the content on which the rendering process is to be performed, but also viewpoint information transmitted from the terminal (e.g., pose). Content before the rendering process is performed has non-real-time characteristics that can be used by an unspecified number of users at any time, such as educational materials. However, since the rendered result after the rendering process is performed is only valid in a specific spatial location (e.g., a specific spatial location of the terminal), a one-to-one relationship is established between the terminal and the server, and as one-time content, it can be distributed to the terminal and other terminals. It is not reused and may have the characteristic of being created and delivered in real time so that it can be delivered and consumed within a few to tens of ms.

In a communication system, in order to enable a terminal to use a split rendering service, there is a need for a method of controlling the processing load between the terminal and the server.

According to one aspect of the present disclosure, a method and apparatus for providing adaptive split rendering in a communication system may be provided.

According to another aspect of the present disclosure, a method and device for sharing information related to data between a terminal and a server for adaptive split rendering in a communication system may be provided.

According to one aspect of the present disclosure, a method and device for controlling processing load between a terminal and a server for adaptive split rendering in a communication system may be provided.

According to one aspect of the present disclosure, a method of operating a terminal in a communication system is provided, and the operating method includes, from an application provider (AP) device, an adaptive split rendering policy applied by the AP device. An operation of receiving an ASR policy), an operation of transmitting a SAI request requesting service access information (SAI) to an application function (AF) device based on the ASR policy, the SAI request In response to, an operation of receiving, from the AF device, an MPE uniform resource locator (MPE URL) response including a media play entry (MPE), based on the MPE URL response, an adaptive split rendering signaling server ( Transmitting an MPE request requesting the MPE to an adaptive split rendering signaling server (ASSRSS), and in response to the MPE request, media presentation for Web Real-Time Communication (WebRTC) from the ASRSS Adaptive split rendering media play entry including media presentation description (MPD) and session description protocol (SDP) for 5th generation media streaming (5GMS) communication. Includes an operation to receive entry: ASRMPE).

According to one aspect of the present disclosure, a terminal is provided in a communication system, the terminal includes a transceiver, and a processing unit connected to the transceiver, and the processing unit, through the transceiver, provides an application provider: Receives, from an AP) device, an adaptive split rendering policy (ASR policy) applied by the AP device, and based on the ASR policy, through the transceiver, an application function (AF) device Transmits a SAI request requesting service access information (SAI), and in response to the SAI request, includes a media play entry (MPE) from the AF device through the transceiver. Receives an MPE URL (uniform resource locator) response, and based on the MPE URL response, transmits an MPE request for requesting the MPE to an adaptive split rendering signaling server (ASSRSS) through the transceiver. And, in response to the MPE request, a media presentation description (MPD) for Web Real-Time Communication (WebRTC) and 5th generation media streaming ( It is configured to receive an adaptive split rendering media play entry (ASRMPE) including a session description protocol (SDP) for 5th generation media streaming (5GMS) communication.

1 is a diagram illustrating a communication system according to an embodiment of the present disclosure.
Figure 2 is a diagram schematically showing the structure of a communication system according to an embodiment of the present disclosure.
Figure 3 is a signal flow diagram schematically showing a service provisioning operation performed between an AF entity and an AP entity in a communication system according to an embodiment of the present disclosure.
Figure 4 is a diagram schematically showing an SRM profile list according to an embodiment of the present disclosure.
FIG. 5 is a signal flow diagram schematically illustrating an operation of providing content based on adaptive split rendering in a communication system according to an embodiment of the present disclosure.
FIG. 6 is a diagram schematically showing an example of the structure of a network entity according to an embodiment of the present disclosure.
Figure 7 is a diagram schematically showing an example of the structure of a terminal according to an embodiment of the present disclosure.
Figure 8 is a block diagram schematically showing another example of the structure of a terminal according to an embodiment of the present disclosure.
FIG. 9 is a block diagram schematically showing another example of the structure of a network entity according to an embodiment of the present disclosure.

Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings.

In describing the present disclosure, description of technical content that is well known in the technical field to which the present disclosure belongs and that is not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanation. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically shown. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and the present embodiments are merely intended to ensure that the disclosure is complete and are within the scope of common knowledge in the technical field to which the present disclosure pertains. It is provided to fully inform those who have the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification. Additionally, when describing the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, a base station (BS) is an entity that performs resource allocation for a terminal, such as gNode B, eNode B, Node B, (or xNode B (where x is an alphabet including g and e)), a wireless access unit. , it may be at least one of a base station controller, a satellite, an airborn, or a node on a network. Terminal (user equipment: UE) may include a MS (Mobile Station), vehicle, satellite, airborn, cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. You can. In this disclosure, downlink (DL) refers to the wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. Additionally, a sidelink (SL), which refers to a wireless transmission path of a signal transmitted from a terminal to another terminal, may exist.

In addition, although the LTE, LTE-A or 5G system may be described below as an example, embodiments of the present disclosure can also be applied to other communication systems with similar technical background or channel type. For example, this may include 5G-Advance or NR-Advance or the 6th generation mobile communication technology (6G) developed after 5G mobile communication technology (or new radio, NR), and 5G hereinafter refers to existing LTE, LTE- It may be a concept that includes A and other similar services. In addition, this disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person with skilled technical knowledge.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory The instructions stored in may also produce manufactured items containing instruction means that perform the functions described in the flow diagram block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially simultaneously, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' performs certain roles. do. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in an embodiment, '~ part' may include one or more processors.

Wireless communication systems have moved away from providing early voice-oriented services to, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), and LTE-Advanced. Broadband wireless that provides high-speed, high-quality packet data services such as communication standards such as (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e. It is evolving into a communication system.

As a representative example of the broadband wireless communication system, the LTE system adopts Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL), and Single Carrier Frequency Division Multiplexing (SC-FDMA) in the uplink (UL). Access) method is adopted. Uplink refers to a wireless link through which a terminal transmits data or control signals to a base station, and downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above multiple access method usually distinguishes each user's data or control information by allocating and operating the time-frequency resources to carry data or control information for each user so that they do not overlap, that is, orthogonality is established. You can.

As a future communication system after LTE, that is, the 5G communication system must be able to freely reflect the various requirements of users and service providers, so services that simultaneously satisfy various requirements must be supported. Services considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC). There is.

eMBB aims to provide more improved data transmission speeds than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink from the perspective of one base station. In addition, the 5G communication system must provide the maximum transmission rate and at the same time provide increased user perceived data rate. In order to meet these requirements, improvements in various transmission and reception technologies are required, including more advanced multi-antenna (Multi Input Multi Output, MIMO) transmission technology. In addition, while LTE transmits signals using a maximum of 20MHz transmission bandwidth in the 2GHz band, the 5G communication system uses a frequency bandwidth wider than 20MHz in the 3~6GHz or above 6GHz frequency band to transmit the data required by the 5G communication system. Transmission speed can be satisfied.

mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. In order to efficiently provide the Internet of Things, mMTC requires support for access to a large number of terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal costs. Since the Internet of Things provides communication functions by attaching various sensors and various devices, it must be able to support a large number of terminals (for example, 1,000,000 terminals/km ² ) within a cell. Due to the nature of the service, terminals that support mMTC are likely to be located in shaded areas that cannot be covered by cells, such as the basement of a building, so they may require wider coverage than other services provided by the 5G communication system. Terminals that support mMTC must be composed of low-cost terminals, and since it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.

URLLC is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency situations. Services used for emergency alerts, etc. can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service that supports URLLC must satisfy an air interface latency of less than 0.5 milliseconds and has a packet error rate of less than 10 ^-5 . Therefore, for services that support URLLC, the 5G system must provide a smaller Transmit Time Interval (TTI) than other services, and at the same time, a design that requires allocating wide resources in the frequency band to ensure the reliability of the communication link. Specifications may be required.

The three services of 5G, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. At this time, different transmission/reception techniques and transmission/reception parameters can be used between services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

1 is a diagram illustrating a communication system according to an embodiment of the present disclosure.

Figure 1 illustrates a base station 110, a terminal 120, and a terminal 130 as some of the nodes that use a wireless channel in a communication system. 1 exemplarily shows only one base station, but other base stations identical or similar to the base station 110 may be further included.

Referring to FIG. 1, the base station 110 may be a network infrastructure that provides wireless access to terminals 120 and 130. The base station 110 has coverage defined as a certain geographic area based on the range over which it can transmit wireless signals. The base station 110 includes 'access point (AP)', 'eNodeB (eNB)', 'gNodeB (gNB)', '5G node (5th generation node)', 'wireless point', ' It may be referred to as a ‘transmission/reception point (TRP)’ or another term with equivalent technical meaning.

Each of the terminal 120 and terminal 130 is a device that can be used by a user and can communicate with the base station 110 through a wireless channel. In some cases, at least one of the terminal 120 and the terminal 130 may be operated without user involvement. That is, at least one of the terminal 120 and the terminal 130 is a device that performs machine type communication (MTC) and may not be carried by the user. The terminal 120 and the terminal 130 each include a 'user equipment (UE)', a 'mobile station', a 'subscriber station', a 'remote terminal', and a 'wireless terminal. It may be referred to as ‘wireless terminal’, ‘user device’, or other terms with equivalent technical meaning.

One embodiment of the present disclosure may provide a method and device for providing adaptive split rendering in a communication system.

An embodiment of the present disclosure uses an architecture for 5th generation media streaming (5GMS) communication and Web real-time communication (WebRTC) to provide adaptive split rendering in a communication system. A method and device for providing an architecture and an interface based on the architecture can be provided.

In an embodiment of the present disclosure, in order to provide adaptive split rendering in a communication system, a service provider may provide content to be provided by the service provider itself, a type of split rendering to be applied to the content, or a terminal. A method and device for providing ARS service information including information related to the load of each server and 5GMS application function (AF) entity can be provided.

An embodiment of the present disclosure provides a method and device for providing a service by considering the 5GMS protocol and the WebRTC protocol together based on service information received by AF from a service provider in order to provide adaptive split rendering in a communication system. can be provided.

In an embodiment of the present disclosure, in order to provide adaptive split rendering in a communication system, AF provides a plurality of protocols and a plurality of adaptive split rendering profiles to a 5G terminal based on service information received from a service provider. A method and apparatus for generating and providing an adaptive split rendering media play entry (ASRMPE) including split rendering profiles may be provided.

In one embodiment of the present disclosure, in a communication system, to provide adaptive split rendering, an adaptive split rendering signaling server (ASSRSS) performs WebRTC re-negotiation in a WebRTC re-negotiation process. A method and device can be provided that provide seamless switching between media before the process is performed and media after the WebRTC re-negotiation process is performed.

First, the architecture that provides an adaptive split rendering method in a communication system and provides split-rendered media is described as follows. According to one embodiment, the architecture of a communication system that provides an adaptive split rendering method may be based on an architecture for 5GMS communication and an architecture for WebRTC, and may provide an interface for providing an adaptive split rendering method. .

Figure 2 is a diagram schematically showing the structure of a communication system according to an embodiment of the present disclosure.

Referring to FIG. 2, the communication system may be based on an architecture for 5GMS communication. The communication system may include an architecture for 5GMS communication as well as other protocols, or architectures to support communications based on other protocols. The communication system may provide the functionality of 5GMS communication using existing protocols supported by 5GMS communication (e.g., dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) and/or HTTP) as well as other protocols.

The architecture for 5GMS communication is an architecture being discussed in the 3rd Generation Partnership Project (3GPP) SA4 related to 5GMS communication, and the architecture for 5GMS communication is an architecture that provides media services (e.g. media trimming service). am. Hereinafter, for convenience of explanation, it should be noted that the term “media” may be used interchangeably with the term “content.” HTTP and DASH, which are protocols available in 5GMS communication, can support a one-to-many relationship and therefore support streaming of reusable media for an unspecified plurality of terminals.

In DASH, media variations of various qualities for one original media are created in advance, and a manifest (e.g. media presentation) is information that the terminal uses to access these media variations. A description (media presentation description: MPD) can be created and provided. However, in the split rendering method, one-time media is created and generated at the request of the terminal under a one-to-one relationship between the terminal and the server. In addition, in 5GMS communication, downlink streaming and/or uplink streaming may be supported, but it is related to the media that is the target of downlink streaming. Since uplink transmission of control information related to media that is the target of downlink streaming is not supported, 5GMS communication is based on real-time communication to the terminal. It may not be possible to create or change content.

In addition, WebRTC is a protocol for interactive services between terminals. It enables data transmission and reception between terminals in real time. However, in order to transmit and receive data between terminals again, the data connection must be re-established after the data connection is terminated. It has to be set. In other words, in WebRTC, disconnections may occur due to resetting the data connection. In addition, in WebRTC, a standard network interface for connection to edge processing provided by the communication system is not defined, and only communication between terminals is considered, so load and/or provision waiting time for each data to be transmitted are determined. The same control information is not provided.

Therefore, in the present disclosure, in order to support creating or changing content based on real-time communication to the terminal, an architecture based on an architecture for 5GMS communication and an architecture for WebRTC (e.g., an architecture for 5GMS communication and an architecture for WebRTC) The architecture of a communication system (based on a combination of architectures) can be provided.

The present disclosure may provide a method for controlling the processing load between a terminal and a server in a communication system to enable the terminal to use a split rendering service. In the present disclosure, when the performance of the terminal decreases after the service start time, the level of rendering load requested by the terminal at the start time is compared to the level of rendering load on the server side at the time of re-negotiation. A change request can be made so that the load level is higher, and in this case, seamless switching can be provided between the content that the terminal was receiving and the content that the terminal will receive after renegotiation.

As shown in FIG. 2, the communication system may include entities related to 5GMS communication, entities related to WebRTC, and entities related to an edge application (EdgeApp).

According to one embodiment, entities related to 5GMS communication include a UE 200 (e.g., UE 120 or UE 130 in FIG. 1), an application function (AF) entity 230, and/or It may include an application server (AS) 270.

According to one embodiment, entities related to WebRTC include WebRTC framework (201), ASRSS (271), adaptive split rendering application server (ASRAS) half render (273) ), and/or ASRAS full render (275).

According to one embodiment, entities related to EdgeApp include an edge enabler server (EES) 231, an edge application server (EAS) instance 277, and an EAS instance 279. , and/or may include an EAS instance 281.

In 5GMS communication, entities related to EdgeApp may be included in the architecture of the communication system, and therefore, when the EES 231 is shown in the AF entity 230, the AF 230 entity has the functions of the EES 231. It may mean that you can perform your role. In one embodiment, the AF 230 entity and the EES 231 can share information with each other without having a separate interface. Similarly, when EAS is shown in the AS (270), the AS (270) can perform the functions and roles of EAS, and thus EAS instances (e.g., EAS instance 277, EAS instance 279 ), and/or it may mean that an EAS instance 281) can be created.

According to one embodiment, each of WebRTC signaling servers and WebRTC endpoints, which are entities related to WebRTC, can be created, initialized, and executed as an EAS instance. In Figure 2, a WebRTC signaling server can be created as an EAS instance 277, and WebRTC endpoints can be created as an EAS instance 279 and EAS instance 281.

According to one embodiment, from a WebRTC perspective, peer devices participating in peer-to-peer communication and signaling servers associated with the peer devices run a split rendering process (UE) operating as an EAS instance, respectively. split rendering processes), and a WebRTC signaling server operating as an EAS instance.

According to one embodiment, the interface (e.g., interface for control communication) between the WebRTC framework 201 and the ASRSS 271 included in the terminal (or UE) 200 in the communication system is adapted. It may be adaptive split rendering signaling interface #5 (ASR-S5), and the interface between ASRSS 271 and ASRAS 273 (e.g., the interface for control communication is adaptive split rendering signaling interface It may be #3 (ASR-S3: adaptive split rendering signaling interface #3), and the media player and/or media access function entity 203 and ASRAS 275 of the terminal 200 The interface (e.g., an interface for media data communication) may be adaptive split rendering media interface #4 (ASR-M4).

According to one embodiment, the terminal 200 may include a WebRTC framework 201, which is an entity for WebRTC, along with a media session handler (MSH) 205, which is an entity for 5GMS communication. . The media player and/or media access function entity 203 of 5GMS communications may be extended to support the WebRTC protocol. As an example, if the protocol used to receive content (or media) is the 5GMS protocol, the media player and/or media access function entity 203 requests media data from the AS 270 using the 5GMS protocol. , media data may be received from the AS 270 in response to the request. As an example, if the protocol used to receive content (or media) is the WebRTC protocol, the media player and/or media access function entity 203 performs a WebRTC re-negotiation procedure with the ASRSS 271, Based on the results of performing the WebRTC re-negotiation procedure, data related to the terminal 200, such as pose, can be transmitted to the ASRASs 273 and 275, and the ASRASs 273 and 275 ), the rendered result media data can be received from.

In one embodiment of the present disclosure, the service provider provides service information including information related to the content (or media) the service provider intends to provide, the type of split rendering to be applied to the content, or the load of each terminal and server. It can be provided as an AF entity (230). This can be explained in detail as follows.

The service provider may also be called a service provider or an application provider (AP). In FIG. 2 , the AP entity 250 may create content and provide the generated content to the terminal 200 . According to one embodiment, the AP entity 250 may provide content that can be played in terminals included in the communication system, or content that may not be playable in the terminals. The AP entity 250 selects terminals that are capable of playing content provided by the AP entity 250 among terminals included in the communication system and terminals that are unable to play content provided by the AP entity 250. Split rendering service can be provided considering terminals. The AP entity 250 may determine the acceptable quality of split rendered media (SRM), which is content to which the split rendering method is applied. In this way, a split rendering service is provided in consideration of terminals that can play content provided by the AP entity 250 and terminals that cannot play content provided by the AP entity 250, and the SRM is allowed. To determine the possible quality, the AP entity 250 establishes an adaptive split rendering policy (ASR policy) through an interface with the AF entity 230, i.e., an adaptive split rendering policy (ASR policy) that the AP entity 250 wishes to provide. The process of delivering information related to the service and information related to the content that the AP entity 250 wishes to provide will be referred to as the ASR service provision process. In the ASR service provisioning process, the AP entity 250 may specify a provisioning session type for the provisioning session that the AP entity 250 wishes to provide. At this time, the AP entity 250 may determine the direction of transmission as “both” considering the characteristics of split rendering. In one embodiment, the direction of transmission may include downlink, uplink, and bidirectional. In one embodiment, the indicator indicating the direction of transmission may be implemented with, for example, 2 bits, with the downlink being a first value (e.g., 00) (downlink=00), and the uplink being a second value (e.g., 01). (uplink=01), bidirectional can be set to a third value (e.g., 10) (both =10). In the ASR service provisioning process, information related to the service included in the ASR policy is provided to the AP. It may include an SRM profile list that is the result of the split rendering process that the entity 250 allows to provide. In Figure 2, the ASR policy is the service content that the AP entity 250 wants to provide. It may include whether or not the split rendering process, which is a process for reprocessing the service content that the AP entity 250 wants to provide, is permitted, and a profile list of each SRM specified when the split rendering process is permitted. In an example, the SRM profile list may include at least one SRM profile, and each SRM profile may specify the intensity or level of load of the rendering process required by the terminal or server (e.g., AS, ASRSS, ASRAS), and a codec. , resolution, etc., may include attribute information of the media to be delivered to the terminal.

In one embodiment, the AP entity 250 may perform a service provisioning operation for the AF entity 230. Hereinafter, for convenience of explanation, the service provision operation performed by the AP entity 250 for the AF entity 230 will be referred to as an ASR service provision operation. In one embodiment, ASR service provision. may be M1 provisioning. In general, the provisioning application programming interface (API) for the AP entity 250 to provide services to the AF entity 230 is a provisioning session type, either a downlink type or an uplink type. Only supported. The provisioning session type indicates the direction of transmission (e.g., transmission type), and the indicator indicating the provisioning session type may be provisioningSessionType. However, as described above, according to one embodiment, the AP entity 250 may determine the direction of transmission as “both” in consideration of the characteristics of split rendering. In one embodiment, the direction of transmission may include downlink, uplink, and bidirectional. In one embodiment, the provisioningSessionType, which is an indicator indicating the direction of transmission, may be implemented with, for example, 2 bits, with the downlink having a first value (e.g., 00) (downlink=00), and the uplink having a second value ( Example: 01 (uplink=01). Bidirectional may be set to a third value (e.g., 10) (both=10). According to one embodiment, the AP entity 250 may be set to a third value (both=10). ), receives data such as a pose or user action, creates content in real time based on the data received from the terminal 200, and transmits it to the terminal 200. there is.

The provisioningSessionType may be based on the definition of ServiceAccessInformation resource as shown in Table 1 below.

<Table 1>

In Table 1 above, provisioningSessionType can be expressed as Table 2 below.

<Table 2>

Meanwhile, in order for the AP entity 250 to specify content control (content protocol) and content distribution to the AS (270) through the AF entity 230, media ingest and publish : M2) Protocol and media streaming (M4) protocol can be changed as follows. This is like an extension of M2 provisioning and M4 provisioning.

According to one embodiment, the protocol used to distribute (or provide) content in the communication system may further include DASH and HTTP as well as the WebRTC protocol. Accordingly, the AP entity 250 may include WebRTC distribution indicating the WebRTC protocol in the content distribution protocol information and distribution configuration provided to the AF entity 230. This can be expressed as Table 3 below.

<Table 3>

Table 3 may represent a set of content protocols supported by 5GMS AS, that is, the AS 270. As shown in Table 3, the AS 270 can support HTTP, DASH, and WebRTC protocols.

In Table 3, Clause 8.2 and Clasue 8.3 may be as shown in Tables 4 and 5 below.

<Table 4>

<Table 5>

Figure 3 is a signal flow diagram schematically showing a service provisioning operation performed between an AF entity and an AP entity in a communication system according to an embodiment of the present disclosure.

Referring to FIG. 3, the provisioning API for the AP entity 250 (e.g., the AP entity 250 in FIG. 2) to provide a service to the AF entity 230 (e.g., the AF entity 230 in FIG. 2) is As a provisioning session type, only downlink type or uplink type was supported.

However, according to an embodiment of the present disclosure, the AP entity 250 may determine the direction of transmission as “both” in consideration of the characteristics of split rendering. In one embodiment, the direction of transmission may include downlink, uplink, and bidirectional. In one embodiment, the provisioningSessionType, which is an indicator indicating the direction of transmission, may be implemented with, for example, 2 bits, with the downlink having a first value (e.g., 00) (downlink=00), and the uplink having a second value ( Example: 01 (uplink=01), and bidirectional may be set to a third value (eg, 10) (both=10). Therefore, the AP entity 250 performs the ASR service provisioning operation in operation 311. The direction can be set, and since this is similar to what is described in Table 1 and Table 2, detailed description thereof will be omitted here.

The AF entity 230, which has received a direction of transmission through an ASR service provisioning operation from the AP entity 250, uses ASRSS 271 (e.g., ASRSS 271 in FIG. 2) in operations 317, 319, and 321. )), ASRAS 313, and DASH AS 315 can be requested to perform an instantiation operation based on M3, an internal (M3) protocol, respectively.

The AP entity 250, which has performed an ASR service provisioning operation for the AF entity 230, may transmit an Ingest/Dist Configuration to the DASH AS 315 in operation 323. . In operation 325, the AP entity 250 sends an ingestion/distribution configuration (Ingest/ Dist Configuration) can be transmitted. As described in Table 3, according to one embodiment, the AS may support not only HTTP and DASH but also WebRTC protocols.

According to an embodiment of the present disclosure, the AP entity provides ASR service information to the AF entity, and the AF entity provides services by simultaneously considering the 5GMS protocol and WebRTC protocol based on the ASR service information provided by the AP entity. can do. The ASR service information may include information related to the content to be provided by the AF entity, the type of split rendering to be applied to the content, or the load of each terminal and server.

According to an embodiment of the present disclosure, the AF entity may create an EAS instance to perform the ASRSS role and an EAS instance for each SRM profile depending on whether the AP entity allows the ASR service. The EAS instance for the SRM profile plays the role of ASRAS, and the EAS instance playing the role of ASRAS is a WebRTC endpoint (e.g. ASRAS in Figure 2) where the process for creating the SRM corresponding to the SRM profile runs. It may be half render (273), and/or ASRAS full render (275).

Referring again to Figure 2, ASR policy (SRM profile list) 251, service content (3D content) 253, SRM profile list 261, non-SR (original) Content 283, half SR & half original content 285, and/or full SR content 287 may represent data.

The Non-SR content 283 may be content (eg, media data) provided by the AP entity 250 when the content is provided as is without going through a split rendering process.

The Half SR & Half Original content 285 may be content in which a split rendering process is applied to some of the content provided by the AP entity 250, and the split rendering process is not applied to the remaining portions. there is.

The Full SR content 287 may be content provided after the split rendering process is applied to all content provided by the AP entity 250.

As described above, the Half SR & Half Original content 285 may be content created when a split rendering process is applied to only some of the content provided by the AP entity 250. The range to which the split rendering process is applied among the content provided by the AP entity 250 and the processing level of the split rendering process may be implemented in many different forms, and therefore, the split among the content provided by the AP entity 250 A plurality of Half SR & Half Original contents 285 may be created based on the scope to which the rendering process is applied and the processing level of the split rendering process.

In Figure 2, SRM Profile A is used to transmit the service content (3D content) 253 of the AP entity 250 to the 5GMS of the AS 270, assuming that the terminal 200 performs split rendering processing perfectly. It can be delivered using a media streaming function, so a separate edge process is not used, and the transmission protocol used for content transmission may be 5GMS.

In contrast, the ASRAS half render (273) can be an edge process that generates SRM according to SRM profile B, and the ASRAS full render (275) can be an edge process that generates SRM according to SRM profile C. . In this case, the protocol used for content transmission may be the WebRTC protocol, and therefore the SRM Profile B and SRM Profile C may be transmitted using the WebRTC protocol.

According to one embodiment, based on ASR service information, the AF entity provides a terminal (5G terminal or UE) with an adaptive split rendering media play entry including a plurality of protocols and a plurality of ASR profiles. ASRMPE) can be provided.

Figure 4 is a diagram schematically showing an SRM profile list according to an embodiment of the present disclosure.

Referring to FIG. 4, depending on the operation of ASRAS and ASRSS, the SRM profile list may include SRM profiles, and each SRM profile may provide attribute information of SRM. The attribute information of the SRM may include attribute information related to media, attribute information related to time, attribute information related to performance, and/or attribute information related to terminal component requirements.

As shown in FIG. 4, the AP ASR policy may include content and an SRM profile list. Content may include a content component, and the content component may include content component access information.

The SRM profile list may include an SRM profile, and the SRM profile may include SRM. SRM may include media profile, time, device load, and type. The media profile may include codec, resolution, type, projection, and viewpoint. Types included in the media profile may include 2D, depth, occupancy, texture, and scene description. The time may include initial startup delay, max presentation delay, and MTP delay. Device load includes render requirements, and render requirements can include none, vertexShader, primitiveGeneration, raserization, framentShader, testingBlender, and finalRender. Types included in SRM may include projection, viewpoint, and attribute.

The SRM profile list may include a plurality of SRM profiles. Each SRM profile can provide attribute information of SRM. The attribute information of the SRM includes attribute information related to media (e.g., media profile), attribute information related to time (e.g., time), and attribute information related to performance (e.g., device load). load)), and/or may include attribute information (e.g. type) related to terminal component requirements.

As shown in FIG. 4, the AS may include an EAS instance, and the EAS instance may include ASRSS and ASRAS. ASRSS may include a WebRTC signaling server, and ASRAS may include a WebRTC endpoint and a split renderer. Split renderer may include performance, performance may include time, and time may include initial startup delay, max presentation delay, MTP delay ( MTP delay) may be included.

According to one embodiment, in a communication system, the AF entity and the AS may support the 5GMS protocol and the WebRTC protocol simultaneously. Therefore, the process of searching for content that the terminal wants to receive starts based on the 5GMS protocol, but the terminal receives the split rendering service that can be requested depending on its performance or the SRM that is the result of the split rendering service using the 5GMS protocol or WebRTC protocol. It can be provided through .

FIG. 5 is a signal flow diagram schematically illustrating an operation of providing content based on adaptive split rendering in a communication system according to an embodiment of the present disclosure.

Referring to FIG. 5, the communication system includes a UE (or terminal) 200 (e.g., UE 200 in FIG. 2), an AF entity 230 (e.g., AF entity 230 in FIG. 2 or 3), ASRSS 271 (e.g., ASRSS 271 in Figure 2 or 3), ASRAS 313 (e.g., ASRAS 313 in Figure 3), DASH AS 315 (e.g., DASH AS 315 in Figure 3 )), may include an AP entity 250 (e.g., AP entity 250 in Figure 2 or Figure 3). In operation 511, an ASR service provisioning process is performed through a service discovery procedure. It can be. After the ASR service provisioning process is performed, the AF entity 230 may create ASRSS 271 and ASRAS 313 based on the SRM profile list. ASRSS 271 may add or update the time attribute in the SRM profile list through performance measurement of the created EAS instances. The AF entity 230 may receive a list of currently serviceable SRM profiles from the ASRSS 271 and create an ASRMPE based on the received SRM profile list.

The UE 200 may transmit a SAI request requesting service access information (SAI) to the AF entity 230 according to the 5GMS protocol in operation 513. In operation 515, the AF entity 230, which has received the SAI request from the UE 200, selects a uniform resource locator (MPE URL) including a media play entry (MPE) among the parameters included in the SAI. ) A response may be sent to the .UE 200.

The UE 200, which has received the MPE URL response from the AF entity 230, may transmit an MPE request requesting the MPE to the URL included in the received MPE URL response in operation 517. The ASRSS (271), which has received the MPE request from the UE (200), generates an ASRMPE in operation 519, and then sends the generated ASRMPE to the UE (200) through an MPD + SDP offer. ) can be sent. Parameters related to the MPE included in the SAI may provide separate signaling as to whether ASR service is possible.

In one embodiment, the ASRMPE may be composed of a combination of an HTTP URL or DASH MPD for the 5GMS protocol and a session description protocol (SDP) for the WebRTC protocol. The SDP can be expanded to describe the SRM profile included in the ASR policy, and the method of expanding the SRM profile can be as follows.

First, the SDP extension is explained as follows.

SDP can specify media using the “m:” line and provide attribute information about the media in the m line using the “a:” line, which will be described later.

Additional attribute information of a line proposed in this disclosure may include the following.

(1) time/startupDelay: This may mean the first reception time from a request (e.g., a media request from a terminal), that is, the initial start up delay time.

(2) time/presentationDelay: This may refer to the maximum delay that needs to be expected until the first frame is output when changing to the channel being provided (the maximum delay to show the first or dedicated frame after switching). Various parameters such as GoP, coding order, decoder buffer size, etc. can affect time/presentationDelay.

(3) time/mtpDelay: This may refer to the time from when the terminal transmits a pose to when the photon is output on the display of the terminal (MTP delay time between sending a pose and receiving a photon).

Additional attribute information as described above can be used as an example, as shown in Table 6 below.

<Table 6>

Additional attribute information proposed in this disclosure may further include the following.

(1) type/projection: May refer to the projection type of SRM. In one embodiment, the projection type may include various projection types such as 2D, cube, 360, etc.

(2) type/viewport: This may refer to the field of view displayed by SRM.

(3) type/attribute: May refer to the content or information format of SRM. In one embodiment, the content or information format of SRM may include Image, depth, occupancy, alpha, etc.

(4) type/render: This may refer to the renderer pipeline required by the terminal. type/render can include none, vertexShader, primitiveGeneration, rasterization, fragmentShader, testingBlender, and finalRender. When a terminal that does not support the pipeline receives the SRM, it may not be able to play the received SRM or its performance may be reduced.

Additional attribute information as described above can be used as an example, as shown in Table 7 below.

<Table 7>

According to one embodiment, the detailed syntax of the ASRMPE may be as follows.

In one embodiment, ASRMPE in HTTP URL format may be provided in the form of a list of URLs, and is a reception path of original content that can be received from AS (e.g., AS 270 in FIG. 2) using the 5GMS protocol. It may include information related to and information related to the SDP offer reception path for communication with the ASRSS 271. The UE 200 receives the ASRMPE from the ASRSS 271 through the MPD + SDP offer, then performs a negotiation operation with the ASRSS 271, and negotiates the ASRAS based on the result of the negotiation operation. You can receive SRM of specified quality from (271). After receiving the ASRMPE from the ASRSS 271 through the MPD + SDP offer, the UE 200 may transmit a DASH segment request to the DASH AS 315 in operation 521. The DASH AS 315, which has received the DASH segment request from the UE 200, may transmit a DASH segment to the UE 200 in response to the DASH segment request in operation 523. In one embodiment, the DASH segment request in operation 521 and the DASH segment transmission in operation 523 may be based on HTTP. In one embodiment, the DASH segment request transmission in operation 521 and the DASH segment transmission in operation 523 may be content provision operations based on the 5GMS protocol.

In one embodiment, ASRMPE in the DASH MPD format can be provided in a form that extends the functionality of the MPD by including an SDP in the MPD. As an example, use uri indicating an extension for WebRTC communication of 3GPP's 5GMS as the value of the schemeIdUri attribute of @supplementalProperty (e.g., urn:3gpp:contentProtocol:webrtc-distribution), and use it in the following XML (extensible markup language) content. SDP may be included. After receiving the ASRMPE from the ASRSS 271 through the MPD + SDP offer, the UE 200 receives original content of various qualities through DASH, or receives the ASRSS using the SDP included in the extension field. A negotiation operation may be performed with 271, and an SRM of a specified quality may be received from the ASRAS 271 based on the result of the negotiation operation.

According to one embodiment, MPD expansion may be described as follows.

ASRMPE in DASH MPD format can be provided in a form that extends the functionality of MPD by including SDP in MPD. As an example, use uri indicating an extension for WebRTC communication of 3GPP's 5GMS as the value of the schemeIdUri attribute of @supplementalProperty (e.g., urn:3gpp:contentProtocol:webrtc-distribution), and add the extended SDP to the following XML content. ASRMPE in DASH MPD format can be provided in the form of inclusion.

After receiving the ASRMPE from the ASRSS 271 through the MPD + SDP offer, the UE 200 may transmit an SDP response to the ASRSS 271 in operation 525. The ASRSS 271, which has received the SDP response from the UE 200, may transmit an instance request to the ASRAS 313 in response to the SDP response in operation 527. Additionally, the UE 200 may transmit a pose to the ASRAS 313 in operation 529. In one embodiment, pose may be data related to the UE (200). The ASRAS (313), which has received an instance request from the ASRSS (271) and a pose from the UE (200), transmits RTC streaming to the UE (200) in operation 531. You can. In one embodiment, the SDP response transmission in operation 525, the instantiation request transmission in operation 527, the pause transmission in operation 529, and the RTC streaming transmission in operation 531 may be content providing operations based on the WebRTC protocol.

According to an embodiment of the present disclosure, ASRSS can provide seamless switching between media before the WebRTC renegotiation process is performed and media after the WebRTC renegotiation process is performed. . This can be explained in detail as follows.

After creation and initialization, the ASRAS continuously processes (e.g., 360VR rendering, stereoscopic rendering, simplified scene description generation) depending on the performance targeted when requesting self-evaluation or edge resource allocation. The measured performance index can be calculated, and the measured performance index of the calculated process can be transmitted to ASRSS.

The measurement performance indicator may be an indicator that can vary depending on various parameters such as the performance of the server to which edge resources are allocated, the transmission speed of the cell to which the server belongs, the distance and mobility speed between the terminal and the base station, etc. AS may calculate the measurement performance index based on network status, process performance measurement, etc., and provide the calculated measurement performance index as attribute information of SRM included in ASRMPE.

The measurement performance index is the initial start up delay time, which is the time from the acquisition of the terminal's request and pose information to the time when the SRM as a result of the split rendering process is first transmitted, and the transmitted SRM is received and played from an arbitrary intermediate point. max presentation delay time, which is the maximum delay time for the first presentation from the decoded picture buffer, and motion to photon (MTP) delay that can be supported by methods such as motion estimation within the split rendering process, late stage reprojection (LSR), or time warp. May include time information, etc.

As an example, the operation of an AF entity creating an EAS instance for ASRAS determines which SRM to use as a result of a negotiation operation between the terminal (or UE) and the ASRSS, and uses EAS to provide the determined corresponding SRM(s). An operation to create an instance (hereinafter, for convenience of explanation, referred to as a “first EAS instance creation operation”), and/or an EAS instance for each of all SRMs in the process of the AF entity creating the ASRSS and ASRAS. It may include an operation to create (hereinafter, for convenience of explanation, it will be referred to as a “second EAS instance creation operation”). According to one embodiment, the initial start up delay time may be the time until the creation, initialization, and processing results of the EAS instance in the first EAS instance creation operation, and the pose in the process preparation state in the second EAS instance creation operation. It may be the time until the processing result is received after receiving.

The measurement performance indicator can be inserted as attribute information for each SRM included in the ASRMPE generated by the ASRSS, and is information that determines whether the terminal will select the corresponding SRM in WebRTC negotiation and renegotiation operations between the terminal and the ASRSS. It can be used as.

The terminal can determine whether to select the corresponding SRM as follows based on various time information (e.g., initial start up delay time, max presentation delay time, motion to photon delay time) as described above.

First, the terminal has a lower complexity (e.g., a complexity lower than the currently provided complexity, or a complexity below the critical complexity level) depending on the terminal's own state (e.g., a state in which it is expected to enter a low-power mode). It is possible to determine whether to receive SRM. If lower complexity is allowed in the terminal, it is common for the server to require higher complexity (e.g., higher complexity than the currently provided complexity, or complexity above the critical complexity level), and in this case, more complexity is required from the server's edge resources. Delays due to performing high-complexity processes, network state-based delays or shortening times for transmitting SRMs with higher or lower transmission volume, and MTP times of changed SRMs can be factors to consider when making changes.

Since a plurality of EAS instances are created for seamless switching between the SRM that the terminal is currently receiving (e.g., the first SRM) and the SRM that the terminal wants to receive (e.g., the second SRM), the terminal Select an EAS instance (second EAS instance) providing a suitable SRM in addition to the EAS instance (e.g., the first EAS instance) providing the SRM currently being received through communication, and during operation of the first EAS instance, the second EAS An instance may be prepared, and the first EAS instance may be stopped after the reception of the second EAS instance begins.

The time at which reception from the second EAS instance is initiated after the request for the second EAS instance, the max delay when switching between the first SRM and the second SRM after reception from the second EAS instance is initiated, and the Considering the MTP delay of the second SRM, which may be different from the first SRM, the terminal starts receiving the second SRM based on the time margin calculated back from the target SRM switching time, and the first SRM and the second SRM At the point when reception overlaps, the swap chain can be connected so that the target display time of each SRM is continuous, and reception of the first SRM can be terminated.

Next, the structure of a network entity according to an embodiment of the present disclosure will be described with reference to FIG. 6. A network entity (or network device (e.g., base station, AF entity, AP entity, AS) may be any one of various entities included in a communication system (e.g., mobile communication network).

FIG. 6 is a diagram schematically showing an example of the structure of a network entity according to an embodiment of the present disclosure.

The embodiment of the network entity shown in FIG. 6 is for illustrative purposes only, and therefore FIG. 6 does not limit the scope of the present disclosure to any particular implementation of the network entity.

As shown in FIG. 6, the network entity includes multiple antennas 605a-605n, multiple RF transceivers 610a-610n, transmit (TX) processing circuitry 615, and receive (receive: RX) includes a processing circuit 620. The network entity also includes a controller/processor 625, memory 630, and a backhaul or network interface 635.

The RF transceivers 610a-610n receive incoming RF signals, such as signals transmitted by terminals in the network, from the antennas 605a-605n. The RF transceivers (610a-610n) down-convert the input RF signals and generate IF or baseband signals. The IF or baseband signals are transmitted to the RX processing circuit 620, which filters, decodes, and/or digitizes the baseband or IF signals to generate processed baseband signals. . The RX processing circuit 620 transmits the processed baseband signals to the controller/processor 625 for further processing.

The TX processing circuit 615 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from the controller/processor 625. The TX processing circuit 615 encodes, multiplexes, and/or digitizes the output baseband data to generate processed baseband or IF signals. The RF transceivers 610a-610n receive the processed baseband or IF signals output from the TX processing circuit 615, and transmit the baseband or IF signals through the antennas 605a-605n. Up-converts to RF signals.

The controller/processor 625 may include one or more processors or other processing devices that control the overall operation of the network entity. As an example, the controller/processor 625 may control the reception of forward channel signals by the RF transceivers 610a-610n, the RX processing circuit 620, and the TX processing circuit 615 according to well-known principles. and transmission of reverse channel signals. The controller/processor 625 may support additional functions, such as more advanced wireless communication functions.

In various embodiments of the present disclosure, the controller/processor 625 performs overall operations related to adaptive split rendering.

Additionally, the controller/processor 625 may support beamforming or directional routing operations in which signals output from multiple antennas 605a-605n are weighted differently to efficiently steer the output signals in a desired direction. there is. Any of a variety of other functions may be supported by the controller/processor 625 at the network entity.

The controller/processor 625 may also execute programs and other processes residing in the memory 630, such as an operating system (OS). The controller/processor 625 may move data into or out of the memory 630 as needed by a running process.

The controller/processor 625 is also coupled to the backhaul or network interface 635. The backhaul or network interface 635 allows the network entity to communicate with other devices or systems through a backhaul connection or over a network. The interface 635 may support communications via any suitable wired or wireless connection(s). As an example, when the network entity is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G, LTE, or LTE-A), the interface 635 allows the network entity to establish a wired or wireless backhaul connection. Allows communication with other network entities. When the network entity is implemented as an access point, the interface 635 allows the network entity to connect to a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. Communication can be permitted. The interface 635 includes a suitable structure to support communications through a wired or wireless connection, such as Ethernet or an RF transceiver.

The memory 630 is coupled to the controller/processor 625. Part of the memory 630 may include RAM, and another part of the memory 630 may include flash memory or other ROM.

Although Figure 6 shows one example of a network entity, various changes could be made to Figure 6. As an example, the network entity may include any number of components shown in FIG. 6. As a specific example, an access point may include multiple interfaces 635 and the controller/processor 625 may support routing functions to route data between different network addresses. As another specific example, while shown as comprising a single instance of TX processing circuitry 615 and a single instance of RX processing circuitry 620, each of the network entities (one per RF transceiver and one per RF transceiver) may contain multiple instances of the same type. Additionally, various components in FIG. 6 may be combined, further divided, or omitted, and additional components may be added according to special needs.

Next, the structure of a terminal according to an embodiment of the present disclosure will be described with reference to FIG. 7.

Figure 7 is a diagram schematically showing an example of the structure of a terminal according to an embodiment of the present disclosure.

One embodiment of the terminal shown in FIG. 7 is for illustrative purposes only, and therefore FIG. 7 does not limit the scope of the present disclosure to any specific implementation of the terminal.

As shown in FIG. 7, the terminal includes an antenna 705, a radio frequency (RF) transceiver 710, a TX processing circuit 715, a microphone 720, and a receive (RX) ) includes a processing circuit 725. The terminal also includes a speaker 730, a processor 740, an input/output (I/O) interface (IF) 745, a touch screen 750, a display (display) 755, and Includes memory 760. The memory 760 includes an operating system (OS) 761 and one or more applications 762.

The RF transceiver 710 receives an incoming RF signal transmitted by a network entity of the network from the antenna 705. The RF transceiver 710 down-converts the input RF signal and generates an intermediate frequency (IF) or baseband signal. The IF or baseband signal is transmitted to the RX processing circuit 725, which filters, decodes, and/or digitizes the baseband or IF signal to generate a processed baseband signal. . The RX processing circuit 725 sends the processed baseband signal to the speaker 730 (such as for voice data) or to the processor 740 (such as for web browsing data) for additional processing. (as in).

The TX processing circuit 715 may receive analog or digital voice data from the microphone 720, or other output baseband data (web data, email, or interactive video game data) from the processor 740. (such as data) is received. The TX processing circuit 715 encodes, multiplexes, and/or digitizes the output baseband data to generate a processed baseband or IF signal. The RF transceiver 710 receives the processed baseband or IF signal output from the TX processing circuit 715, and upconverts the baseband or IF signal into an RF signal transmitted through the antenna 705. (up-convert).

The processor 740 may include one or more processors or other processing devices, and may execute the OS 761 stored in the memory 760 to control the overall operation of the terminal. As an example, the processor 740 receives downlink channel signals and uplink channel signals by the RF transceiver 710, the RX processing circuit 725, and the TX processing circuit 715 according to known principles. You can control their transmission. In one embodiment, the processor 740 includes at least one microprocessor or microcontroller.

In one embodiment of the present disclosure, the processor 740 performs overall operations related to adaptive split rendering.

The processor 740 may also execute other processes and programs resident in the memory 760, such as processes related to the adaptive split rendering. The processor 740 can move data into or out of the memory 760 when required by a running process. In one embodiment, the processor 740 is configured to execute the applications 762 based on the OS program 761 or in response to signals received from network entities or operators. Additionally, the processor 740 is connected to the I/O interface 745, and the I/O interface 745 provides the terminal with information about other devices such as laptop computers and handheld computers. Provides connectivity capabilities. The I/O interface 745 is a communication path between these accessories and the processor 740.

The processor 740 is also connected to the touch screen 750 and the display unit 755. The operator of the terminal can input data into the terminal using the touch screen 750. The display 755 may be a liquid crystal display, a light emitting diode display, or other display capable of rendering text and/or at least limited graphics, such as from web sites.

The memory 760 is connected to the processor 740. A portion of the memory 760 may include random access memory (RAM), and the remaining portion of the memory 760 may include flash memory or other read-only memory (ROM). can do.

Although Figure 7 shows an example of a terminal, various changes may be made to Figure 7. As an example, various components in FIG. 7 may be combined, further divided, or omitted, and other components may be added according to special needs. Additionally, as a specific example, the processor 740 may include multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). It can be divided. Additionally, although the terminal is configured as a mobile phone or a smart phone in FIG. 7, the terminal may be configured to operate as other types of mobile or stationary devices.

Then, another example of the structure of a terminal according to an embodiment of the present disclosure will be described with reference to FIG. 8.

Figure 8 is a block diagram schematically showing another example of the structure of a terminal according to an embodiment of the present disclosure.

As shown in FIG. 8, the terminal may include a receiving unit 800, a transmitting unit 804, and a processing unit 802. The receiving unit 800 and the transmitting unit 804 may be collectively referred to as a transmitting/receiving unit in an embodiment of the present disclosure. The transceiver can transmit and receive signals with a network entity. Here, the signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. Additionally, the transceiver may receive a signal through a wireless channel and output it to the processing unit 802, and transmit the signal output from the processing unit 802 through a wireless channel. The processing unit 802 can control a series of processes so that the terminal can operate according to the embodiment of the present disclosure described above.

Next, another example of the structure of a network entity according to embodiments of the present disclosure will be described with reference to FIG. 9.

FIG. 9 is a block diagram schematically showing another example of the structure of a network entity according to an embodiment of the present disclosure.

As shown in FIG. 9, the network entity may include a receiving unit 901, a transmitting unit 905, and a processing unit 903. The receiving unit 901 and the transmitting unit 905 may be collectively referred to as a transmitting/receiving unit in the embodiment of the present disclosure. The transceiver can transmit and receive signals to and from the terminal. The signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. Additionally, the transceiver may receive a signal through a wireless channel and output it to the processing unit 903, and transmit the signal output from the processing unit 903 through a wireless channel. The processing unit 903 can control a series of processes so that the network entity can operate according to the above-described embodiments of the present disclosure.

Meanwhile, the embodiments of the present disclosure disclosed in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present disclosure and aid understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it is obvious to those skilled in the art that other modifications based on the technical idea of the present disclosure can be implemented. Additionally, each embodiment may be operated in combination with each other as needed. Although the present disclosure has been described with reference to example embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover changes and modifications that fall within the scope of the appended claims. Nothing in the detailed description of this application should be read to imply that any particular element, process, or function is an essential element that must be included within the scope of the claims. The scope of patentable subject matter is defined by the claims.

Claims (20)

In a method of operating a terminal in a communication system,
An operation of receiving, from an application provider (AP) device, an adaptive split rendering policy (ASR policy) applied by the AP device;
Based on the ASR policy, transmitting a SAI request requesting service access information (SAI) to an application function (AF) device;
In response to the SAI request, receiving, from the AF device, an MPE uniform resource locator (MPE) response including a media play entry (MPE);
Based on the MPE URL response, transmitting an MPE request requesting the MPE to an adaptive split rendering signaling server (ASSRSS); and
In response to the MPE request, from the ASRSS, media presentation description (MPD) for Web Real-Time Communication (WebRTC) and 5th generation media streaming (5GMS) communication The operating method comprising receiving an adaptive split rendering media play entry (ASRMPE) including a session description protocol (SDP) for.
According to paragraph 1,
Based on the ASRMPE, transmitting a DASH segment request to a DASH (dynamic adaptive streaming over hypertext transfer protocol (HTTP)) application server (AS); and
The method further comprising receiving a DASH segment from the DASH AS in response to the DASH segment request.
According to paragraph 1,
Based on the ASRMPE, transmitting an SDP response to the ASRSS;
Based on the ASRMPE, transmitting information related to the terminal to an adaptive split rendering application server (ASRAS); and
The operating method further includes receiving real-time communication (RTC) streaming from the ASRAS in response to information related to the terminal.
According to paragraph 3,
The operating method wherein the information related to the terminal includes at least one of pose information or field of view information.
According to paragraph 1,
The ASR policy includes first information related to a service provided by the AP device and second information related to content provided by the AP device, and
The ASR policy includes a provisioning session type for a provisioning session provided by the AP device.
According to clause 5,
The provisioning session type indicates a direction of transmission, and indicates one of downlink, uplink, or both supporting both downlink and uplink.
According to clause 5,
The ASR policy includes a profile list of split rendered media (SRM) that the AP device allows to provide.
In clause 7,
The SRM profile list includes at least one SRM profile,
Each of the at least one SRM profile includes attribute information of media to be delivered to the terminal, and
The attribute information of the media includes at least one of the intensity or level of load, codec, or resolution of the rendering process required by the terminal, the ASRSS, or the ASRAS. method. According to paragraph 1,
The SDP is:
time/startupDelay, which is the first reception time from the media request of the terminal, time/presentationDelay, which is the maximum delay time that needs to be expected until the first frame is output when changing to the channel being provided, or the terminal related to the terminal. The operating method including at least one of time/mtpDelay, which is the time from the time information is transmitted to the time Photon is output on the display of the terminal.
According to paragraph 1,
The SDP is:
type/projection, which is the projection type of split rendered media (SRM), type/viewport, which is the field of view displayed by the SRM, and type/attribute, which is the content or information format of the SRM. , or the operation method including at least one of type/render, which is a renderer pipeline required for the terminal.
In a terminal in a communication system,
Transmitter and receiver; and
It includes a processing unit connected to the transmitter and receiver,
The processing unit:
Receiving an adaptive split rendering policy (ASR policy) applied by the AP device from an application provider (AP) device through the transceiver,
Based on the ASR policy, a SAI request requesting service access information (SAI) is transmitted to an application function (AF) device through the transceiver,
In response to the SAI request, receive an MPE URL (uniform resource locator) response including a media play entry (MPE) from the AF device through the transceiver,
Based on the MPE URL response, transmitting an MPE request for requesting the MPE to an adaptive split rendering signaling server (ASSRSS) through the transceiver, and
In response to the MPE request, a media presentation description (MPD) for Web Real-Time Communication (WebRTC) and 5th generation media streaming are received from the ASRSS through the transceiver. The terminal configured to receive an adaptive split rendering media play entry (ASRMPE) including a session description protocol (SDP) for (streaming: 5GMS) communication.
According to clause 11,
The processing unit:
Based on the ASRMPE, a DASH segment request is transmitted to a DASH (dynamic adaptive streaming over hypertext transfer protocol (HTTP)) application server (AS) through the transceiver, and
The terminal further configured to receive a DASH segment from the DASH AS through the transceiver in response to the DASH segment request.
According to clause 11,
The processing unit:
Based on the ASRMPE, transmitting an SDP response to the ASRSS through the transceiver,
Based on the ASRMPE, information related to the terminal is transmitted to an adaptive split rendering application server (ASRAS) through the transceiver, and
The terminal further configured to receive real-time communication (RTC) streaming from the ASRAS through the transceiver in response to information related to the terminal.
According to clause 13,
The information related to the terminal includes at least one of pose information or field of view information.
According to clause 11,
The ASR policy includes first information related to a service provided by the AP device and second information related to content provided by the AP device, and
The ASR policy includes a provisioning session type for a provisioning session provided by the AP device.
According to clause 15,
The provisioning session type indicates a direction of transmission and indicates one of downlink, uplink, or both supporting both downlink and uplink.
According to clause 15,
The ASR policy includes a profile list (SRM profile list) of split rendered media (SRM) that the AP device allows to provide.
According to clause 17,
The SRM profile list includes at least one SRM profile,
Each of the at least one SRM profile includes attribute information of media to be delivered to the terminal, and
The attribute information of the media includes at least one of the intensity or level of load, codec, or resolution of the rendering process required by the terminal, the ASRSS, or the ASRAS. .
According to clause 11,
The SDP is:
time/startupDelay, which is the first reception time from the media request of the terminal, time/presentationDelay, which is the maximum delay time that needs to be expected until the first frame is output when changing to the channel being provided, or the terminal related to the terminal. The terminal including at least one of time/mtpDelay, which is the time from when information is transmitted to when Photon is output on the display of the terminal.
According to clause 11,
The SDP is:
type/projection, which is the projection type of split rendered media (SRM), type/viewport, which is the field of view displayed by the SRM, and type/attribute, which is the content or information format of the SRM. , or the terminal including at least one of type/render, which is a renderer pipeline required for the terminal.

Images