Split rendered media delivery based on IP multimedia subsystem (IMS) data channel

Abstract

A method performed by a client on a user equipment is provided. The method includes sending, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media. The method includes receiving the information for the DC media, wherein the information indicates the DC media is capable of being split rendered. And the method includes initiating, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

Description

SPLIT RENDERED MEDIA DELIVERY BASED ON IP MULTIMEDIA SUBSYSTEM (IMS) DATA CHANNEL TECHNOLOGICAL FIELD

[0001] The present disclosure relates generally to telecommunications and, in particular, to split graphics rendering across a telecommunications system. BACKGROUND

[0002] A telecommunications system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations and / or other nodes by providing carriers between the various entities involved in the communications path. A telecommunications system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, video, electronic mail (email), text message, multimedia and / or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.

[0003] In a wireless telecommunications system at least a part of a communication session between at least two stations occurs over a wireless link. Examples of wireless systems comprise public land mobile networks (PLMN), satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN). Some wireless systems can be divided into cells, and are therefore often referred to as cellular systems.

[0004] A user can access the telecommunications system by means of an appropriate communication device or terminal. A communication device of a user may be referred to as user equipment (UE) or user device. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by a station, for example a base station of a cell, and transmit and / or receive communications on the carrier.

[0005] The telecommunications system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and / or parameters which shall be used for the connection are also typically defined. One example of a telecommunications system is the Universal Mobile Telecommunications System (UMTS). Other examples of telecommunications systems are Long-Term Evolution (LTE), LTE Advanced and the so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP).BRIEF SUMMARY

[0006] Example implementations of the present disclosure are directed to telecommunications and, in particular, to split graphics rendering across a telecommunications system. The present disclosure includes, without limitation, the following example implementations for illustrative purposes.

[0007] Some example implementations provide an apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause a client to at least: send, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media; receive the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and initiate, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0008] Some example implementations provide an apparatus implemented by a user equipment including a client, the apparatus comprising: means for sending, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media; means for receiving the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and means for initiating, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0009] Some example implementations provide a method performed by a client on a user equipment, the method comprising: sending, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media; receiving the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and initiating, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0010] Some example implementations provide a computer-readable storage medium that is non-transitory and has instructions stored therein that, in response to execution by at least one processing circuitry, causes a client to at least: send, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media; receive the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and initiate, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0011] Some example implementations provide an apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause an Internet Protocol (IP) multimedia subsystem (IMS) applicationserver (AS) to at least: receive, from a client on a user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session; sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session; and create or modify an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function.

[0012] Some example implementations provide an apparatus implemented by a network device including an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS), the apparatus comprising: means for receiving, from a client on an user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session; means for sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session; and means for creating or modifying an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function.

[0013] Some example implementations provide a method performed by a network device including an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS), the method comprising: receiving, from a client on a user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session; sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session; and creating or modifying an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function.

[0014] Some example implementations provide a computer-readable storage medium that is non-transitory and has instructions stored therein that, in response to execution by at least one processing circuitry, causes an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS) to at least: receive, from a client on a user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session; sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session; and create or modify an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function.

[0015] Some example implementations provide an apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS) to at least: receive a request for information for data channel (DC) media from a client on a user equipment; send the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; create or modify a split rendering session over a standalone IMS DCsession; allocate a media resource for the split rendering session; and send, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session.

[0016] Some example implementations provide an apparatus implemented by a network device including a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS), the apparatus comprising: means for receiving a request for information for data channel (DC) media from a client on an user equipment; means for sending the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; means for creating or modifying a split rendering session over a standalone IMS DC session; means for allocating a media resource for the split rendering session; and means for sending, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session.

[0017] Some example implementations provide a method performed by a network device including a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS), the method comprising: receiving a request for information for data channel (DC) media from a client on a user equipment; sending the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; creating or modifying a split rendering session over a standalone IMS DC session; allocating a media resource for the split rendering session; and sending, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session.

[0018] Some example implementations provide a computer-readable storage medium that is non-transitory and has instructions stored therein that, in response to execution by at least one processing circuitry, causes a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS) to at least: receive a request for information for data channel (DC) media from a client on a user equipment; send the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; create or modify a split rendering session over a standalone IMS DC session; allocate a media resource for the split rendering session; and send, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session.

[0019] These and other features, aspects, and advantages of the present disclosure will be apparent from a reading of the following detailed description together with the accompanying figures, which are briefly described below. The present disclosure includes any combination of two, three, four or more features or elements set forth in this disclosure, regardless of whether such features or elements are expressly combined or otherwise recited in a specific example implementation described herein. This disclosure is intended to be read holistically such that any separable features or elements of the disclosure, in any of its aspects and example implementations, should be viewed as combinable unless the context of the disclosure clearly dictates otherwise.

[0020] It will therefore be appreciated that this Brief Summary is provided merely for purposes of summarizing some example implementations so as to provide a basic understanding of some aspects of the disclosure. Accordingly, it will be appreciated that the above described example implementations are merely examples and should not be construed to narrow the scope or spirit of the disclosure in any way. Other example implementations, aspects and advantages will become apparent from the following detailed description taken in conjunction with the accompanying figures which illustrate, by way of example, the principles of some described example implementations. BRIEF DESCRIPTION OF THE FIGURE(S)

[0021] Having thus described example implementations of the disclosure in general terms, reference will now be made to the accompanying figures, which are not necessarily drawn to scale, and wherein:

[0022] FIG.1 illustrates a telecommunications system that includes one or more public land mobile networks (PLMNs) coupled to one or more external data networks, according to some example implementations of the present disclosure;

[0023] FIG.2 illustrates a 5G deployment of a PLMN, referred to at times as the 5G system (5GS), according to some example implementations;

[0024] FIG.3 more particularly depicts aspects of the 5GS of FIG.2, according to some example implementations;

[0025] FIG.4 illustrates an IP multimedia subsystem (IMS) architecture supporting data channel services, according to some example implementations;

[0026] FIGS.5A and 5B illustrate a signaling chart of procedures for establishment of a split rendering session over a standalone IMS DC session, according to some example implementations;

[0027] FIGS.6A and 6B illustrate a signaling chart of procedures for modification of a split rendering session over a standalone IMS DC session, according to some example implementations;

[0028] FIGS.7A, 7B, 7C and 7D are flowcharts illustrating various steps in a method performed by a client on a user equipment (UE), according to various example implementations;

[0029] FIGS.8A and 8B are flowcharts illustrating various steps in a method performed by a network device including an IMS application server (AS), according to various example implementations;

[0030] FIG.9 is a flowchart illustrating various steps in a method performed by a network device including a media function (MF) of an IMS, according to various example implementations; and

[0031] FIG.10 illustrates an apparatus according to some example implementations. DETAILED DESCRIPTION

[0032] Some implementations of the present disclosure will now be described more fully hereinafter with reference to the accompanying figures, in which some, but not all implementations of the disclosure are shown. Indeed, various implementations of the disclosure may be embodied in many different forms andshould not be construed as limited to the implementations set forth herein; rather, these example implementations are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Like reference numerals refer to like elements throughout.

[0033] Unless specified otherwise or clear from context, references to first, second or the like should not be construed to imply a particular order. A feature described as being above another feature (unless specified otherwise or clear from context) may instead be below, and vice versa; and similarly, features described as being to the left of another feature else may instead be to the right, and vice versa. Also, while reference may be made herein to quantitative measures, values, geometric relationships or the like, unless otherwise stated, any one or more if not all of these may be absolute or approximate to account for acceptable variations that may occur, such as those due to engineering tolerances or the like.

[0034] As used herein, unless specified otherwise or clear from context, the “or” of a set of operands is the “inclusive or” and thereby true if and only if one or more of the operands is true, as opposed to the “exclusive or” which is false when all of the operands are true. Thus, for example, “[A] or [B]” is true if [A] is true, or if [B] is true, or if both [A] and [B] are true. Further, the articles “a” and “an” mean “one or more,” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, it should be understood that unless otherwise specified, the terms “data,” “content,” “digital content,” “information,” and similar terms may be at times used interchangeably. The term “network” may refer to a group of interconnected computers including clients and servers; and within a network, these computers may be interconnected directly or indirectly by various means including via one or more switches, routers, gateways, access points or the like.

[0035] Reference may be made herein to terms specific to a particular system, architecture or the like, but it should be understood that example implementations of the present disclosure may be equally applicable to any of a number of systems, architectures and the like. For example, reference may be made to 3GPP technologies such as Global System for Mobile Communications (GSM), UMTS, LTE, LTE Advanced, 5G NR, 5G Advanced and 6G; however, it should be understood that example implementations of the present disclosure may be equally applicable to non-3GPP technologies such as IEEE 802, Bluetooth and Bluetooth Low Energy.

[0036] Further, as used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); or (c) hardware circuit(s) and / or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s),that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0037] The above definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0038] FIG.1 illustrates a telecommunications system 100 according to various example implementations of the present disclosure. The telecommunications system generally includes one or more telecommunications networks. As shown, for example, the system includes one or more public land mobile networks (PLMNs) 102 coupled to one or more other external data networks 104 – notably including a wide area network (WAN) such as the Internet. Each of the PLMNs includes a core network (CN) 106 backbone such as the Evolved Packet Core (EPC) of LTE, the 5G core network (5GC) or the like; and each of the core networks and the Internet are coupled to one or more radio access networks (RANs) 108, air interfaces or the like that implement one or more radio access technologies (RATs). As used herein, a “network device” refers to any suitable device at a network side of a telecommunications network. Examples of suitable network devices are described in greater detail below.

[0039] In addition, the system includes one or more radio units that may be varyingly known as user equipment (UE) 110, terminal device, terminal equipment, mobile station or the like. The UE is generally a device configured to communicate with a network device or a further UE in a telecommunication network. The UE may be a portable computer (e.g., laptop, notebook, tablet computer), mobile phone (e.g., cell phone, smartphone), wearable computer (e.g., smartwatch), or the like. In other examples, the UE may be an Internet of Things (IoT) device, an industrial IoT (IIoT device), a vehicle equipped with a vehicle-to- everything (V2X) communication technology, or the like. In some examples, as referenced by 3GPP, the UE may be a narrowband IoT (NB-IoT) device, an enhanced machine-type communication (eMTC) device, a reduced capability (RedCap) device, an ambient IoT device, or the like.

[0040] In operation, these UEs may be configured to connect to one or more of the RANs 108 according to their particular radio access technologies to thereby access a particular CN 106 of a PLMN 102, or to access one or more of the external data networks 104 (e.g., the Internet). The external data network may be configured to provide Internet access, operator services, 3rd party services, etc. For example, the International Telecommunication Union (ITU) has classified 5G mobile network services into three categories: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine type communications (mMTC) or massive internet of things (MIoT).

[0041] Examples of radio access technologies include 3GPP radio access technologies such as GSM, UMTS, LTE, LTE Advanced, 5G NR, 5G Advanced, and 6G. Other examples of radio access technologies include IEEE 802 technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.15 (including 802.15.1 (WPAN / Bluetooth), 802.15.4 (Zigbee) and 802.15.6 (WBAN)), Bluetooth, Bluetooth Low Energy (BLE), ultra wideband (UWB), and the like. Generally, a radio access technology may refer to any 2G, 3G, 4G, 5G, 6G or higher generation mobile communication technology and their different versions, as well as to any other wireless radio access technology that may be arranged to interwork with such a mobile communication technology to provide access to the CN 106 of a mobile network operator (MNO).

[0042] In various examples, a RAN 108 may be configured as one or more macrocells, microcells, picocells, femtocells or the like. The RAN may generally include one or more radio access nodes that are configured to interact with UEs 110. In various examples, a radio access node may be referred to as a base station (BS), access point (AP), base transceiver station (BTS), Node B (NB), evolved NB (eNB), macro BS, NB (MNB) or eNB (MeNB), home BS, NB (HNB) or eNB (HeNB), next generation NB (gNB), enhanced gNB (en-gNB), next generation eNB (ng-eNB), or the like. The RAN may include some type of network controlling / governing entity responsible for control of the radio access nodes. The network controlling / governing entity and radio access node may be separate or integrated into a single apparatus. The network controlling / governing entity may include processing circuity configured to carry out various management functions, etc. The processing circuity may be associated with a memory, computer-readable storage medium or database for maintaining information required in the management functions.

[0043] A RAN 108 may be centralized or distributed. In various examples, components of a RAN may be interconnected by Ethernet, Gigabit Ethernet, Asynchronous Transfer Mode (ATM), optical fiber, dark fiber, passive wavelength division multiplexing (WDM), WDM passive optical network (WDM-PON), optical transport network (OTN), time sensitive networking (TSN) and / or any other data link layer network, possibly including radio links. The RAN may be connected to a CN 106 through one or more gateways, network functions or the like.

[0044] As will be appreciated, a PLMN 102 may be deployed in a number of different manners. In a 4G LTE deployment, the EPC is the CN 106, and the evolved UMTS terrestrial radio access network (E- UTRAN) is the RAN 108; and the E-UTRAN includes one or more eNBs (radio access nodes) configured to connect UEs 110 to the E-UTRAN to thereby access the EPC. FIG.2 illustrates a deployment 200, referred to at times as the 5G system (5GS). As shown, the 5GC 202 is the CN, and the next generation (NG) radio access network (NG-RAN) 204 is the RAN; and the NG-RAN includes one or more gNBs 206 (radio access nodes) configured to connect UEs 208 to the NG-RAN to thereby access the 5GC. The term ‘gNB’ in 5G may correspond to the eNB in 4G LTE.

[0045] Some 4G LTE and 5G deployments are considered standalone (SA) deployments. Other deployments combine 4G LTE and 5G technologies, and are referred to as non-standalone (NSA)deployments. In some deployments, the E-UTRAN includes one or more ng-eNBs that are configured to communicate with the 5GC, and that may also be configured to communicate with one or more gNBs. Similarly, in another deployment, the NG-RAN mayinclude one or more ng-eNBs that are configured to communicate with the EPC, and that may also be configured to communicate with one or more eNBs. In various instances, a single UE 110, a dual-mode or multimode UE, may support multiple (two or more) RANs—thereby being configured to connect to multiple RANs, such as 4G LTE and 5G.

[0046] FIG.3 more particularly depicts aspects of the 5GS deployment 200 for a MNO, according to some example implementations. As shown, the deployment includes the 5GC 202, and NG-RAN 204 with one or more gNBs 206 configured to connect UEs 208 to the NG-RAN to thereby access the 5GC. The 5GC may include a number of network functions (NFs) divided between the control plane and the user plane. In particular, the 5GC may include, for example, an access and mobility management function (AMF) 302, a session management function (SMF) 304, a user plane function (UPF) 306, a policy and charging function (PCF) 308, a network exposure function (NEF) 310, and / or an application function (AF) 312. Other examples of suitable NFs include a network repository function (NRF), a network slice selection function (NSSF), a unified data management (UDM), or the like. Also shown is a server hosting an application, referred to as application server (AS) 314.

[0047] In the control plane, the AMF 302 is configured to provide UE-based authentication, authorization, mobility management, etc. The PCF 308 may be responsible for policy enforcement and management, controlling Quality of Service (QoS), charging, and resource allocation for subscribers. The PCF may facilitate efficient resource utilization, optimizing network performance, and delivering a quality user experience.

[0048] The SMF 304 is configured to provide various functionality including session management (SM), UE Internet Protocol (IP) address allocation and management, selection and control of UPF(s) 306, control part of policy application and QoS, lawful intercept, termination of SM parts of NAS messages, Downlink Data Notification (DNN), roaming functionality, handle local enforcement to apply QoS for Service Level Agreements (SLAs), charging data collection and charging interface, etc. If the UE 208 has multiple sessions, different SMFs may be allocated to each session to manage them individually and possibly provide different functionalities per session.

[0049] The UPF 306 supports various user plane operations and functionalities, such as packet routing and forwarding, traffic handling (e.g., applying QoS policies), an anchor point for intra-RAT / inter-RAT mobility (when applicable), packet inspection and policy rule application, lawful intercept (UP collection), traffic accounting and reporting, etc. The UPF is the point of interconnect between the 5GC and at least one external data network (DN) 316 (i.e., point of ingress or egress for a DN), and routes packets to and from the DN. The DN may be configured to provide Internet access, operator services, 3rd party services, etc.

[0050] The AF 312 may interact with the 5GC 202 to enable the deployment of specific services and applications. The AF communicates with other NFs to request and manage network resources, ensuring that the network adapts to the requirements of different applications and services. The NEF 310 allows authorized third-party applications and services to access specific NFs and services in a controlled manner. The NEF enables the exposure of network capabilities to external entities, fostering innovation and the development of new services.

[0051] In some deployments, such as deployment 200, operations of the gNB 206 or other radio access node may be carried out, at least partly, in a central / centralized unit (CU), such as a server, host or node, operationally coupled to a distributed unit (DU), such as a radio head / node. It is also possible that node operations may be distributed among a plurality of servers, hosts or nodes. It should also be understood that the distribution of work between 5GC 202 (or other CN) operations and gNB (or other radio access node) operations may vary depending on implementation.

[0052] A 5G network architecture may be based on a so-called CU-DU split. One gNB-CU (central node) may control one or more gNB-DUs. The gNB-CU may control a plurality of spatially separated gNB-DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some example implementations, however, the gNB- DUs (also called DU) may include, for example, a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the gNB-CU (also called a CU) may include the layers above the RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC), and an IP layer. Other functional splits are also possible. It is considered that a skilled person is familiar with the open systems interconnection (OSI) model and the functionalities within each layer.

[0053] In some example implementations, the server or CU may generate a virtual network through which the server communicates with the radio node. In general, virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software- based administrative entity, a virtual network. Such virtual network may provide flexible distribution of operations between the server and the radio head / node. In practice, any digital signal processing task may be performed in either the CU or the DU, and the boundary where the responsibility is shifted between the CU and the DU may be selected according to implementation.

[0054] In 3GPP, the IP multimedia subsystem (IMS) is a standardized architectural framework designed for delivering IP multimedia services, including video, audio and messaging. The IMS also includes enhancements to support data channel services. FIG.4 illustrates an IMS architecture 400 supporting data channel services. The architecture includes a DC multimedia telephony service for IMS (DC-MTSI) client 402 and an IMS 404 which includes, for example, an interrogating / serving / proxy call session control function (I / S / P-CSCF) 406, an IMS AS 408, a media function (MF) 410 (or a media resource function (MRF)), and a data channel signaling function (DCSF) 412.

[0055] The DC-MTSI client 402 resides in a UE 208. The DC-MTSI client is a data channel capable MTSI client that supports DC media (data and applications transferred via DC). The MF 410 is a NF that interacts with the IMS AS 408 via the service-based interface DC2, and provides media capabilities in support of IMS DC. A DC application server 414 may be responsible for service control, including session media control and media capability negotiation with the UE via the MF.

[0056] In support of data channel services, the DCSF 412 is a signaling control function that provides data channel control logic. The DCSF may receive event reports from the IMS AS 408 via the service-based interface DC1, and decide whether a DC service is allowed to be provided during an IMS session. The DCSF may support HTTP web server functionality to download DC media including data and applications (e.g., IMS-aware application 416) via the MF 410 to the UE 208 based on UE subscription. The DCSF may download DC media from a DC application repository 418. The DCSF may interact with the DC application server 414 for DC resource control via DC4 / DC3, and for traffic forwarding via MDC3 / MDC2.

[0057] The IMS may also support negotiation of a standalone IMS DC session that includes a data channel without dedicated audio, video or messaging components. This support may include the ability to add audio / video / messaging media to an established standalone IMS data channel. It may also include the ability to remove audio / video / messaging media from an established IMS DC session.

[0058] A number of scenarios for IMS session with standalone bootstrap DC, or a combination of standalone bootstrap DC and application DC may be supported. For example, an IMS session with only standalone bootstrap DC may be used for downloading an application list and applications from the DCSF 412. In another example, a UE 208 may initiate an IMS session to another UE with only standalone bootstrap DC and further update the session with application DC. In yet another example, an IMS session with a combination of standalone bootstrap DC and application DC may be used to establish application DC for a downloaded application to a remote UE, which allows the remote UE to download the application if not yet downloaded after accepting the bootstrap DC, and update the session to use the application in the same session. In these and other similar scenarios, the session description protocol (SDP) offer / answer procedure may be used to change an IMS session with audio / video / DC media components to a standalone IMS DC session, and add audio / video media components to an established standalone IMS DC session.

[0059] When an IP multimedia application includes audio / video, split rendering (SR) may be used to leverage rendering resources in a NF or server, as well as rendering resources in the UE 208 to provide a better experience to the user. This may be the case, in particular, for interactive media services such as eXtended reality (XR), which encompasses virtual reality (VR), augmented reality (AR), and mixed reality (MR). These and a number of other media services involve graphics rendering, which can have compute, render and power intensive requirements to provide high quality graphics for a reasonable quality of experience (QoE). Resource constrained devices like smartphones and head-mounted displays may nothave the capacity to provide high quality XR experiences due to limitations of compute, render and energy resources.

[0060] In the split rendering paradigm, the rendering workload is divided between two or more rendering entities, for example, a split rendering client (SRC) and a split rendering server (SRS). Split rendering is envisioned to be available in 5G networks. One example of a proposed split rendering architecture is the IP multimedia subsystem (IMS) based conversational services (IBACS) split rendering architecture, which was developed specifically for conversational AR calls. In the IBACS split rendering architecture the DC-MTSI client 402 may provide SRC functionality (the DC-MTSI client referred to in this context as a SR DC-MTSI client), and the MF 410 (or MRF) may provide SRS functionality. In this regard, the DC-MTSI may be responsible for acquiring the UE media capabilities and interacting with the SRS during a split-rendering session over an IMS session. The MF may in turn be responsible for interacting with the DC-MTSI during split-rendering session, monitoring resource usage, and managing / running the split rendering session.

[0061] In order to enable the split rendering over a standalone IMS DC session, a number of problems need to be solved. When a typical IMS session with audio / video / DC media components is changed to a standalone IMS DC session, for example, the split-rendering should apply to the DC media. Also, when a standalone IMS DC session is established, the DC media needs to be split-rendered media.

[0062] Current standards and technical reports that address split rendering do not apply to DC media (data and applications), which could include a mix of audio, video, images, text, etc. The basic MTSI currently defined specifies media codecs for speech, video, still images and text. Data channels, however, currently do not require use of any codec, but allow for real-time interaction in parallel to the conversational media. Some potential solutions to support standalone IMS data channel have been proposed, but these solutions include general procedures without considering split rendering. Moreover, solutions and procedures are not provided to modify other IMS session procedures, such as to add audio / video / messaging media to an established standalone IMS data channel session, or remove audio / video / messaging media from an IMS session that also contains IMS DC media.

[0063] In view of the foregoing, example implementations of the present disclosure provide a solution to resolve the above problems, and enable split rendering over a standalone IMS DC session, namely, an IMS DC session without dedicated audio, video or messaging components. Some example implementations may involve or presume that the user plane protocol stack for the DC MTSI client includes media codecs for DC medial. And according to media characteristics of the DC media, example implementations of the present disclosure provide an information (e.g., an identifier) for DC media that indicates whether the DC media is capable of split rendering.

[0064] When a DC-MTIS client 402 on a UE 208 establishes a standalone IMS DC session to download a dedicated application 416, the DC-MTIS client may initiate session establishment request(s) to specifically request the information (e.g., value of the identifier) for DC media, such as a requested application (orapplication list). Similarly, when a DC-MTIS client on a UE requests modification of an established IMS session into a standalone IMS DC session to download an application 416, the DC-MTIS client may initiate session modification request(s) specifically to request the information for a requested application (or application list).

[0065] The MF 420 may respond to a request from the DC-MTIS client 402 with an application parameter or application list that include the information that indicates whether the application (DC media) is capable split rendering. In some examples, if the information (e.g., value of the identifier), indicates the format of the application does not support split rendering, the DC-MTSI client may release a current session and request the application in the near future, such as when network conditions or time schedule are better. In other examples in which the format of the application does not support split rendering, the DC-MTSI client may stay with the same IMS session and withdraw the request for the standalone DC session, and further request to the split rendering session for video / audio transferring. If the format of the application does support split rendering, the DC-MTSI client may request a new MF 410 for a new split rendering process.

[0066] Some example implementations therefore provide a DT-MTSI client 402 (or other client) on a UE 208 that may send a request for information for DC media from an IMS 404. The DT-MTSI client may receive the information for the DC media, where the information indicates the DC media is capable of split rendering. The DT-MTSI client may then initiate, based on the information that indicates the DC media is capable of split rendering, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0067] An IMS AS 408 may receive, from the DT-MTSI client 402 on the UE 208, a request to create or modify a split rendering session over a standalone IMS DC session. The IMS AS may request a MF 410 in the IMS 404 to create or modify the split rendering session, and allocate a media resource for the split rendering session. The IMS AS may create or modify an IP transport connection for the split rendering session, and notify the DT-MTSI client that the split rendering session over the standalone IMS DC session has been created or modified.

[0068] The MF 410 may receive the request for information for the DC media from the DT-MTSI client 402 on the UE 208. The MF may send the information for the DC media to the DT-MTSI client. The MF may (with the IMS AS 408) create or modify the split rendering session over the standalone IMS DC session (including a data channel). The MF may allocate a media resource for the split rendering session. And the MF may send, over the data channel to the DT-MTSI client, split-rendered media associated with the DC media during the split rendering session.

[0069] FIGS.5A and 5B illustrate a signaling chart 500 of procedures for establishment of a split rendering session over a standalone IMS DC session, according to some example implementations. The signaling chart provides procedures for a scenario during an established IMS session in which a UE 208 desires to download a dedicated application, and provides negotiation for a split rendering session. As shown, a SRDC-MTSI client 410A (including SRC functionality) of a first UE (UE1) at step 501 initiates a session and sends a session initiation protocol (SIP) INVITE request with an initial session description protocol (SDP) to request a standalone IMS DC session, and request split rendering capabilities from network. The request is forwarded to the IMS AS 408.

[0070] The IMS AS 408 at step 502 proceeds with a DC routing decision and DCSF 412 discovery. The DCSF at step 503 decides whether DC is provided and creates origination-side DC media information, and the IMS AS at step 504 receives DC control instructions from DCSF. The IMS AS at step 505 proceeds with MF discovery, and the IMS AS at step 506 requests the discovered MF (including SRS functionality) to allocate a DC resource. Then, as shown at step 507, the standalone IMS DC session is established, and created for the SR DC-MTSI client 410A of the UE1.

[0071] As shown in FIG.5B for a session modification, the SR DC-MTSI client 410A of UE1 at step 508 sends a request message to the MF 410 to request a DC application or an application list if multiple DC applications are available. In the case in which multiple DC applications are available, the MF at step 509 sends a response to the SR DC-MTSI client of UE1 (via the DCSF 412) with the application list. The application list identifies multiple DC applications, and for a dedicated application 416, includes an identifier indicating whether the application is capable of being split rendered. If the format of the application does not support split rendering, the SR DC-MTSI client of UE1 may at step 510 release the current standalone IMS DC session and request the application in the near future (e.g., better network conditions, better time schedule).

[0072] If the format of the application 416 supports split rendering, the SR DC-MTSI client 410A of UE1 at step 511 requests a split rendering session leveraging the network resources based on the application list received from the MF 410 and UE1’s own capabilities, for the dedicated application. The IMS AS at step 512 forwards the split rendering request to the MF. The MF at steps 513, 514, 515 sends a description of the split rendering session, and exchanges a media resource allocation with the IMS AS. A transport connection is created between the SR DC-MTSI client of UE1 and the IMS AS at step 516. The split rendering session between the SR DC-MTSI client and the MF is established for application download at step 517. And as shown at step 518, a similar session also can be established between the SR DC-MTSI client of UE1, and a SR DC-MTSI client 410B of a second UE (UE2), for the remote UE2 to download applications.

[0073] In another scenario, during an established split rendering session over a standalone IMS DC session, the SR DC-MTSI client 410 of a UE 208 desires to download a dedicated application via the standalone IMS DC session, with no need for other components (e.g., audio, video, messaging components). For this scenario, FIGS.6A and 6B illustrate a signaling chart 600 of procedures for modification of a split rendering session over a standalone IMS DC session, according to some example implementations.

[0074] As shown in FIG.6A, a standalone IMS DC session is setup at step 601, such as in a manner similar to steps 501-507 above. A split rendering session is then setup over the standalone IMS DC session at steps 602-610 (including steps 602, 603, 604, 605, 606, 607, 608, 609 and 610, such as in a manner similar to steps 508-518, and also including establishment of the split rendering session between UE2 and the MF at step 609.

[0075] As shown in FIG.6B, when the SR DC-MTSI client 410A of UE1 discovers that its media capabilities cannot meet the related media rendering requirements, the SR DC-MTSI client of UE1 decides to modify the existing split rendering call flow. The SR DC-MTSI client of UE1 at step 611 sends a request to modify the split rendering session to the IMS AS 408. In this regard, UE1 initiates a session modification request with an SDP offer to request a standalone IMS DC session, and request split rendering capabilities from network. In some examples, as indicated above, the reason for session modification may be that UE1 desires to download a dedicated application via the standalone IMS DC session, with no need for other components (e.g., audio, video, messaging components).

[0076] The IMS AS 408 at step 612 interacts with the DCSF 412 via DC1 to send updated event notification(s) to modify the split. The DCSF at step 613 receives event report(s) from the IMS AS and decides whether the requested data channel service is allowed to be provided during the standalone IMS DC session. The IMS AS at step 614 receives the updated data channel control instructions from the DCSF and accordingly interacts with the MF 410.

[0077] In some cases, the IMS AS 408 at step 615 discovers a new MF 410. The SR DC-MTSI client 410A of UE1 at step 616 sends a request message to the new MF 410 to request a DC application or an application list if multiple DC applications are available. In the case in which multiple DC applications are available, the MF at step 617 sends a response to the SR DC-MTSI client of UE1 (via the DCSF 412) with the application list. As before, the application list identifies multiple DC applications, and for a dedicated application 416, includes an identifier indicating whether the application is capable of being split rendered.

[0078] Assuming the format of the application 416 supports split rendering, the IMS AS 408 at step 618 requests modification of the split rendering session. The request may include information of media objects of the dedicated application to be rendered in the IMS 404. The MF next sends a description of the split rendering session modification, and exchanges a media resource allocation with the IMS AS. In particular, the MF at step 619 sends a description of split rendering output to the IMS AS. The IMS AS at step 620 sends a media resource allocation request to the MF (via the DCSF 412), such as to reserve a XR media rendering resource for the SR DC-MTSI client 410A of UE1. When the media resource is successfully allocated, the MF at step 621 (again via the DCSF) returns a media resource allocation response to the IMS AS.

[0079] The transport connection between the SR DC-MTSI client 410A of UE1 and the IMS AS 408 is modified at step 622. The split rendering session between the SR DC-MTSI client and the MF 410 isestablished for application download at step 623. And as shown at step 624, a similar session also can be established between the SR DC-MTSI client of UE1 and the SR DC-MTSI client 410B of UE2 for the remote UE2 to download applications.

[0080] FIGS.7A – 7D are flowcharts illustrating various steps in a method 700 performed by a client on a user equipment, according to various example implementations. The method includes sending, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media, as shown at block 702 of FIG.7A. The method includes receiving the information for the DC media, In some of these examples, the information indicates the DC media is capable of being split rendered, as shown at block 704. And the method includes initiating, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session, as shown at block 706.

[0081] In some examples, the method 700 further includes receiving, via an IMS data channel for the standalone IMS DC session, split-rendered media associated with the DC media during the split rendering session, as shown at block 708 of FIG.7B.

[0082] In some examples, the sending the request comprises sending the request by the client engaged in an established standalone IMS DC session. In some of these examples, the established standalone IMS DC session is the standalone IMS DC session. Also in some of these examples, the initiating the one or more operations comprises initiating the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0083] In some examples, the method 700 further includes determining, based on the information for the DC media, that the DC media is capable of being split rendered. In some of these examples, the initiating the one or more operations comprises initiating, based on the determining that the DC media is capable of being split rendered, the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0084] In some examples, the method 700 further includes determining, based on the DC media, to modify the split rendering session, as shown at block 710 of FIG.7C. In some of these examples, the method also includes initiating, based on the determining to modify the split rendering session, one or more operations of a procedure to modify the split rendering session over the standalone IMS DC session, as shown at block 712.

[0085] In some examples, the method 700 further includes determining, based on the DC media, to terminate the split rendering session, as shown at block 714 of FIG.7D. In some of these examples, the method also includes initiating one or more operations of a procedure to establish a new split rendering session over a standalone IMS DC session or over an IMS DC session, as shown at block 716.

[0086] In some examples, the initiating the one or more operations of the procedure to establish the new split rendering session is based on a determination that network conditions have improved or based on a specific request by the client.

[0087] FIGS.8A and 8B are flowcharts illustrating various steps in a method 800 performed by a network device including an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS), according to various example implementations. The method includes receiving, from a client on a user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session, as shown at block 802 of FIG.8A. The method includes sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session, as shown at block 804. And the method includes creating or modifying an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function, as shown at block 806.

[0088] In some examples, the method 800 further includes notifying the client that the split rendering session over the standalone IMS DC session has been created or modified.

[0089] In some examples, the receiving the request comprises receiving the request from the client that is engaged in an established standalone IMS DC session. In some of these examples, the established standalone IMS DC session is the standalone IMS DC session. In some of these examples, the request comprises a request to create the split rendering session over the established standalone IMS DC session.

[0090] In some examples, receiving the request comprises receiving the request from the client that is engaged in an established split rendering session over a standalone IMS DC session. In some of these examples, the established standalone IMS DC session is the standalone IMS DC session. Also in some of these examples, the request comprises a request to modify the established split rendering session.

[0091] In some examples, the method 800 further includes sending, to a data channel signaling function (DCSF), an event notification to modify the established split rendering session, as shown at block 808 of FIG.8B. In some of these examples, the method also includes receiving, from the DCSF in response to the event notification, data channel control instructions, as shown at block 810. Also in some of these examples, the sending the request to the media function at block 804 comprises sending, based on the data channel control instructions, to the MF, the request, and the request is a request to modify the established split rendering session.

[0092] FIG.9 is a flowchart illustrating various steps in a method 900 performed by a network device including a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS), according to various example implementations. The method includes receiving a request for information for data channel (DC) media from a client on a user equipment, as shown at block 902 of FIG.9A. The method includes sending the information for the DC media, In some of these examples, the information indicates the DC media is capable of being split rendered, as shown at block 904. The method includes creating or modifyinga split rendering session over a standalone IMS DC session, as shown at block 906. The method includes allocating a media resource for the split rendering session, as shown at block 908. And the method includes sending, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session, as shown at block 910.

[0093] In some examples, the receiving the request comprises receiving the request from the client that is engaged in an established standalone IMS DC session. In some of these examples, the established standalone IMS DC session is the standalone IMS DC session. Also in some of these examples, creating or modifying the split rendering session over the standalone IMS DC session comprises creating the split rendering session over the established standalone IMS DC session.

[0094] In some examples, receiving the request comprises receiving the request from the client that is engaged in an established split rendering session over a standalone IMS DC session. In some of these examples, the established standalone IMS DC session is the standalone IMS DC session. Also in some of these examples, creating or modifying the split rendering session over the standalone IMS DC session comprises modifying the established split rendering session.

[0095] According to example implementations of the present disclosure, a telecommunications system 100 or PLMN 102, and its components such as a UE 110, CN 106, RAN 108, 5GC 202, NG-RAN 204, gNB 206, UE 208, AF 312, AS 314, DC-MTSI client 402 (SR DC-MTSI client), IMS AS 408, MF 410, and / or DCSF 412, may be implemented by various means. Means for implementing the system and its components may include hardware, firmware, software, or combinations thereof. In some examples, one or more apparatuses may be configured to function as or otherwise implement the system and its components shown and described herein. In examples involving more than one apparatus, the respective apparatuses may be connected to or otherwise in communication with one another in a number of different manners, such as directly or indirectly via a wired or wireless network or the like.

[0096] According to some example implementations, at least some of the method 700 described with respect to FIGS.7A-7D may be carried out by an apparatus comprising means for performing functions corresponding steps of the method. Similarly, at least some of the method 800 described with respect to FIGS.8A and 8B may be carried out by an apparatus comprising means for performing functions corresponding steps of the method. And at least some of the method 900 described with respect to FIG.9 may be carried out by an apparatus comprising means for performing functions corresponding steps of the method. Examples of a suitable apparatus may include a network function, an application server, network function, media function, media resource function or any suitable apparatus, such as a server, host or node. Other examples of a suitable apparatus may include a user equipment, user device, user terminal or the like.

[0097] FIG.10 illustrates an apparatus 1000 in which means for performing various functions includes hardware, alone or under direction of one or more computer programs from a computer-readable storagemedium or other memory, such as computer memory, according to some example implementations of the present disclosure. Generally, an apparatus of example implementations of the present disclosure may comprise, include or be embodied in one or more fixed or portable electronic devices. Examples of suitable electronic devices include a wearable computer, mobile phone, portable computer, desktop computer, workstation computer, server (server computer) or the like. The apparatus may include one or more of each of a number of components such as, for example, processing circuitry 1002 connected to computer- readable storage medium or other memory 1004.

[0098] The processing circuitry 1002 may be composed of one or more processors alone or in combination with one or more computer-readable storage media. The processing circuitry is generally any piece of computer hardware that is capable of processing information such as, for example, data, computer programs and / or other suitable electronic information. The processing circuitry is composed of a collection of electronic circuits some of which may be packaged as an integrated circuit or multiple interconnected integrated circuits (an integrated circuit at times more commonly referred to as a “chip”). The processing circuitry may be configured to execute computer programs, which may be stored onboard the processing circuitry or otherwise stored in the memory 1004 (of the same or another apparatus).

[0099] The processing circuitry 1002 may be a number of processors, a multi-core processor or some other type of processor, depending on the particular implementation. Further, the processing circuitry may be implemented using a number of heterogeneous processor systems in which a main processor is present with one or more secondary processors on a single chip. As another illustrative example, the processing circuitry may be a symmetric multi-processor system containing multiple processors of the same type. In yet another example, the processing circuitry may be embodied as or otherwise include one or more ASICs, FPGAs or the like. Thus, although the processing circuitry may be capable of executing a computer program to perform one or more functions, the processing circuitry of various examples may be capable of performing one or more functions without the aid of a computer program. In either instance, the processing circuitry may be appropriately programmed to perform functions or operations according to example implementations of the present disclosure.

[0100] The memory 1004 is generally any piece of computer hardware that is capable of storing information such as, for example, data, computer programs, instructions 1006 (e.g., computer-readable program code) and / or other suitable information either on a temporary basis and / or a permanent basis. The memory may include volatile and / or non-volatile memory, and may be fixed or removable. Examples of suitable memory include recording media, random access memory (RAM), read-only memory (ROM), a hard drive, a flash memory, a thumb drive, a removable computer diskette, an optical disk or some combination thereof.

[0101] The memory 1004 is a non-transitory device capable of storing information. One example of a suitable memory is a computer-readable storage medium, which is distinguishable from a computer-readable transmission medium capable of carrying information from one location to another. Examples of suitable computer-readable transmission media comprise electronic carrier signals, telecommunications signals, software distribution packages, or some combination thereof. As used herein, the term “non- transitory” is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM versus ROM). A computer-readable medium as described herein generally refers to a computer-readable storage medium or computer-readable transmission medium. A computer- readable medium is any entity or device capable in which information, such as one or more computer programs or portions thereof, may be stored and carried.

[0102] In addition to the memory 1004 (e.g., computer-readable storage medium), the processing circuitry 1002 may also be connected to one or more interfaces for displaying, transmitting and / or receiving information. The interfaces may include a communications interface 1008 and / or one or more user interfaces. The communications interface may be configured to transmit and / or receive information, such as to and / or from other apparatus(es), network(s) or the like. The communications interface may be configured to transmit and / or receive information by physical (wired) and / or wireless communications links. Examples of suitable communication interfaces include a network interface controller (NIC), wireless NIC (WNIC) or the like.

[0103] The user interfaces may include a display 1010 and / or one or more user input interfaces 1012. The display may be configured to present or otherwise display information to a user, suitable examples of which include a liquid crystal display (LCD), light-emitting diode (LED) display, organic LED (OLED) display, active-matrix OLED (AMOLED) or the like. The user input interfaces may be wired or wireless, and may be configured to receive information from a user into the apparatus, such as for processing, storage and / or display. Suitable examples of user input interfaces include a microphone, image or video capture device, keyboard or keypad, joystick, touch-sensitive surface (separate from or integrated into a touchscreen), biometric sensor or the like. The user interfaces may further include one or more interfaces for communicating with peripherals such as printers, scanners or the like.

[0104] Execution of the instructions 1006 by the processing circuitry 1002, or storage of the instructions in the memory 1004, supports combinations of operations for implementing example implementations of the present disclosure. In this manner, an apparatus 1000 may comprise at least one processing circuitry and at least one memory coupled to the at least one processing circuitry, where the at least one processing circuitry is configured to execute instructions stored in the at least one memory. It will also be understood that one or more functions, and combinations of functions, may be implemented by special purpose hardware-based computer systems and / or processing circuitry which perform the specified functions, or combinations of special purpose hardware and program code instructions.

[0105] Some example implementations of the present disclosure may also be carried out in the form of a computer process defined by one or more computer programs or portions thereof. Exampleimplementations of the present disclosure may be carried out by executing at least one portion of a computer program comprising instructions. The computer program may be in source code form, object code form, or in some intermediate form. The computer program may be stored in a computer-readable medium that is readable by a computer, processing circuitry or other suitable apparatus. As indicated above, for example, the computer program may be stored in a memory, such as a computer-readable storage medium. Additionally or alternatively, for example, the computer program may be stored in a computer-readable transmission medium. The coding of software for carrying out example implementations of the present disclosure is well within the scope of a person of ordinary skill in the art.

[0106] As will be appreciated, any suitable instructions may be loaded onto a computer, a processing circuitry or other programmable apparatus from a memory or a computer-readable medium (e.g., computer- readable storage medium, computer-readable transmission medium) to produce a particular machine, such that the particular machine becomes a means for implementing the functions specified herein. The instructions may also be stored in a computer-readable medium that can direct a computer, a processing circuitry or other programmable apparatus to function in a particular manner to thereby generate a particular machine or particular article of manufacture. In some examples, the instructions stored in the computer-readable medium may produce an article of manufacture, where the article of manufacture becomes a means for implementing functions described herein. The instructions may be retrieved from a computer-readable medium and loaded into a computer, processing circuitry or other programmable apparatus to configure the computer, processing circuitry or other programmable apparatus to execute operations to be performed on or by the computer, processing circuitry or other programmable apparatus.

[0107] Retrieval, loading and execution of instructions comprising program code instructions may be performed sequentially such that one instruction is retrieved, loaded and executed at a time. In some example implementations, retrieval, loading and / or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and / or executed together. Execution of the program code instructions may produce a computer-implemented process such that the instructions executed by the computer, processing circuitry or other programmable apparatus provide operations for implementing functions described herein.

[0108] As explained above and reiterated below, the present disclosure includes, without limitation, the following example implementations.

[0109] Clause 1. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause a client to at least: send, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media; receive the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and initiate, based on the information for the DCmedia that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0110] Clause 2. The apparatus of clause 1, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further receive, via an IMS data channel for the standalone IMS DC session, split-rendered media associated with the DC media during the split rendering session.

[0111] Clause 3. The apparatus of clause 1 or clause 2, wherein the client caused to send the request comprises the client caused to send the request by the client engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the client caused to initiate the one or more operations comprises the client caused to initiate the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0112] Clause 4. The apparatus of clause 3, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further determine, based on the information for the DC media, that the DC media is capable of being split rendered, and wherein the client caused to initiate the one or more operations comprises the client caused to initiate, based on the determining that the DC media is capable of being split rendered, the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0113] Clause 5. The apparatus of any of clauses 1 to 4, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further at least: determine, based on the DC media, to modify the split rendering session; and initiate, based on the determining to modify the split rendering session, one or more operations of a procedure to modify the split rendering session over the standalone IMS DC session.

[0114] Clause 6. The apparatus of any of clauses 1 to 5, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further at least: determine, based on the DC media, to terminate the split rendering session; and initiate one or more operations of a procedure to establish a new split rendering session over a standalone IMS DC session or over an IMS DC session.

[0115] Clause 7. The apparatus of clause 6, wherein the client is caused to initiate the one or more operations of the procedure to establish the new split rendering session based on a determination that network conditions have improved or based on a specific request by the client.

[0116] Clause 8. An apparatus implemented by a user equipment including a client, the apparatus comprising: means for sending, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media; means for receiving the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and means for initiating, based onthe information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0117] Clause 9. The apparatus of clause 8 further comprising means for receiving, via an IMS data channel for the standalone IMS DC session, split-rendered media associated with the DC media during the split rendering session.

[0118] Clause 10. The apparatus of clause 8 or clause 9, wherein the means for sending the request comprises means for sending the request by the client engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the means for initiating the one or more operations comprises means for initiating the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0119] Clause 11. The apparatus of clause 10, wherein the apparatus further comprises means for determining, based on the information for the DC media, that the DC media is capable of being split rendered, and wherein the means for initiating the one or more operations comprises means for initiating, based on the determining that the DC media is capable of being split rendered, the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0120] Clause 12. The apparatus of any of clauses 8 to 11 further comprising: means for determining, based on the DC media, to modify the split rendering session; and means for initiating, based on the determining to modify the split rendering session, one or more operations of a procedure to modify the split rendering session over the standalone IMS DC session.

[0121] Clause 13. The apparatus of any of clauses 8 to 12 further comprising: means for determining, based on the DC media, to terminate the split rendering session; and means for initiating one or more operations of a procedure to establish a new split rendering session over a standalone IMS DC session or over an IMS DC session.

[0122] Clause 14. The apparatus of clause 13, wherein the means for initiating the one or more operations of the procedure to establish the new split rendering session is based on a determination that network conditions have improved or based on a specific request by the client.

[0123] Clause 15. A method performed by a client on a user equipment, the method comprising: sending, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media; receiving the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and initiating, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0124] Clause 16. The method of clause 15 further comprising receiving, via an IMS data channel for the standalone IMS DC session, split-rendered media associated with the DC media during the split rendering session.

[0125] Clause 17. The method of clause 15 or clause 16, wherein the sending the request comprises sending the request by the client engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the initiating the one or more operations comprises initiating the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0126] Clause 18. The method of clause 17, wherein the method further comprises determining, based on the information for the DC media, that the DC media is capable of being split rendered, and wherein the initiating the one or more operations comprises initiating, based on the determining that the DC media is capable of being split rendered, the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0127] Clause 19. The method of any of clauses 15 to 18 further comprising: determining, based on the DC media, to modify the split rendering session; and initiating, based on the determining to modify the split rendering session, one or more operations of a procedure to modify the split rendering session over the standalone IMS DC session.

[0128] Clause 20. The method of any of clauses 15 to 19 further comprising: determining, based on the DC media, to terminate the split rendering session; and initiating one or more operations of a procedure to establish a new split rendering session over a standalone IMS DC session or over an IMS DC session.

[0129] Clause 21. The method of clause 20, wherein the initiating the one or more operations of the procedure to establish the new split rendering session is based on a determination that network conditions have improved or based on a specific request by the client.

[0130] Clause 22. A computer-readable storage medium that is non-transitory and has instructions stored therein that, in response to execution by at least one processing circuitry, causes a client to at least: send, to an Internet Protocol (IP) multimedia subsystem (IMS), a request for information for data channel (DC) media; receive the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and initiate, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session over a standalone IMS DC session.

[0131] Clause 23. The computer-readable storage medium of clause 22, wherein the computer-readable storage medium has further instructions stored therein that, in response to execution by the at least one processing circuitry, causes the client to further receive, via an IMS data channel for the standalone IMS DC session, split-rendered media associated with the DC media during the split rendering session.

[0132] Clause 24. The computer-readable storage medium of clause 22 or clause 23, wherein the client caused to send the request comprises the client caused to send the request by the client engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the client caused to initiate the one or more operations comprises the client caused to initiate the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0133] Clause 25. The computer-readable storage medium of clause 24, wherein the computer-readable storage medium has further instructions stored therein that, in response to execution by the at least one processing circuitry, causes the client to further determine, based on the information for the DC media, that the DC media is capable of being split rendered, and wherein the client caused to initiate the one or more operations comprises the client caused to initiate, based on the determining that the DC media is capable of being split rendered, the one or more operations to establish the split rendering session over the established standalone IMS DC session.

[0134] Clause 26. The computer-readable storage medium of any of clauses 22 to 25, wherein the computer-readable storage medium has further instructions stored therein that, in response to execution by the at least one processing circuitry, causes the client to further at least: determine, based on the DC media, to modify the split rendering session; and initiate, based on the determining to modify the split rendering session, one or more operations of a procedure to modify the split rendering session over the standalone IMS DC session.

[0135] Clause 27. The computer-readable storage medium of any of clauses 22 to 26, wherein the computer-readable storage medium has further instructions stored therein that, in response to execution by the at least one processing circuitry, causes the client to further at least: determine, based on the DC media, to terminate the split rendering session; and initiate one or more operations of a procedure to establish a new split rendering session over a standalone IMS DC session or over an IMS DC session.

[0136] Clause 28. The computer-readable storage medium of clause 27, wherein the client is caused to initiate the one or more operations of the procedure to establish the new split rendering session based on a determination that network conditions have improved or based on a specific request by the client.

[0137] Clause 29. An apparatus comprising means for performing the method of any of clauses 15 to 21.

[0138] Clause 30. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 15 to 21.

[0139] Clause 31. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 15 to 21.

[0140] Clause 32. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 15 to 21.

[0141] Clause 33. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS) to at least: receive, from a client on a user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session; sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session; and create or modify an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function.

[0142] Clause 34. The apparatus of clause 33, wherein the at least one processing circuitry is configured to execute the instructions to cause the IMS AS to further notify the client that the split rendering session over the standalone IMS DC session has been created or modified.

[0143] Clause 35. The apparatus of clause 33 or clause 34, wherein the receiving the request comprises receiving the request from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the request comprises a request to create the split rendering session over the established standalone IMS DC session.

[0144] Clause 36. The apparatus of any of clauses 33 to 35, wherein receiving the request comprises receiving the request from the client that is engaged in an established split rendering session over a standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the request comprises a request to modify the established split rendering session.

[0145] Clause 37. The apparatus of clause 36, wherein the at least one processing circuitry is configured to execute the instructions to cause the IMS AS to further at least: send, to a data channel signaling function (DCSF), an event notification to modify the established split rendering session; and receive, from the DCSF in response to the event notification, data channel control instructions, and wherein the IMS AS caused to send the request to the media function includes the IMS AS caused to send, based on the data channel control instructions, to the MF, the request, wherein the request is a request to modify the established split rendering session.

[0146] Clause 38. An apparatus implemented by a network device including an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS), the apparatus comprising: means for receiving, from a client on an user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session; means for sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session; and means for creating or modifying an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function.

[0147] Clause 39. The apparatus of clause 38 further comprising means for notifying the client that the split rendering session over the standalone IMS DC session has been created or modified.

[0148] Clause 40. The apparatus of clause 38 or clause 39, wherein the means for receiving the request comprises means for receiving the request from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the request comprises a request to create the split rendering session over the established standalone IMS DC session.

[0149] Clause 41. The apparatus of any of clauses 38 to 40, wherein the means for receiving the request comprises means for receiving the request from the client that is engaged in an established split rendering session over a standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the request comprises a request to modify the established split rendering session.

[0150] Clause 42. The apparatus of clause 41, wherein the apparatus further comprises: means for sending, to a data channel signaling function (DCSF), an event notification to modify the established split rendering session; and means for receiving, from the DCSF in response to the event notification, data channel control instructions, and wherein the means for sending the request to the media function comprises means for sending, based on the data channel control instructions, to the MF, the request, wherein the request is a request to modify the established split rendering session.

[0151] Clause 43. A method performed by a network device including an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS), the method comprising: receiving, from a client on a user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session; sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session; and creating or modifying an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function.

[0152] Clause 44. The method of clause 43 further comprising notifying the client that the split rendering session over the standalone IMS DC session has been created or modified.

[0153] Clause 45. The method of clause 43 or clause 44, wherein the receiving the request comprises receiving the request from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the request comprises a request to create the split rendering session over the established standalone IMS DC session.

[0154] Clause 46. The method of any of clauses 43 to 45, wherein receiving the request comprises receiving the request from the client that is engaged in an established split rendering session over a standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMSDC session, and wherein the request comprises a request to modify the established split rendering session.

[0155] Clause 47. The method of clause 46, wherein the method further comprises: sending, to a data channel signaling function (DCSF), an event notification to modify the established split rendering session; and receiving, from the DCSF in response to the event notification, data channel control instructions, and wherein the sending the request to the media function comprises sending, based on the data channel control instructions, to the MF, the request, wherein the request is a request to modify the established split rendering session.

[0156] Clause 48. A computer-readable storage medium that is non-transitory and has instructions stored therein that, in response to execution by at least one processing circuitry, causes an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS) to at least: receive, from a client on a user equipment, a request to create or modify a split rendering session over a standalone IMS data channel (DC) session; sending, to a media function in the IMS, a request to create or modify the split rendering session and to allocate a media resource for the split rendering session; and create or modify an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the media function.

[0157] Clause 49. The computer-readable storage medium of clause 48, wherein the at least one processing circuitry is configured to execute the instructions to cause the IMS AS to further notify the client that the split rendering session over the standalone IMS DC session has been created or modified.

[0158] Clause 50. The computer-readable storage medium of clause 48 or clause 49, wherein the receiving the request comprises receiving the request from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the request comprises a request to create the split rendering session over the established standalone IMS DC session.

[0159] Clause 51. The computer-readable storage medium of any of clauses 48 to 50, wherein receiving the request comprises receiving the request from the client that is engaged in an established split rendering session over a standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the request comprises a request to modify the established split rendering session.

[0160] Clause 52. The computer-readable storage medium of clause 51, wherein the at least one processing circuitry is configured to execute the instructions to cause the IMS AS to further at least: send, to a data channel signaling function (DCSF), an event notification to modify the established split rendering session; and receive, from the DCSF in response to the event notification, data channel control instructions, and wherein the IMS AS caused to send the request to the media function includes the IMSAS caused to send, based on the data channel control instructions, to the MF, the request, wherein the request is a request to modify the established split rendering session.

[0161] Clause 53. An apparatus comprising means for performing the method of any of clauses 43 to 47.

[0162] Clause 54. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 43 to 47.

[0163] Clause 55. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 43 to 47.

[0164] Clause 56. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 43 to 47.

[0165] Clause 57. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS) to at least: receive a request for information for data channel (DC) media from a client on a user equipment; send the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; create or modify a split rendering session over a standalone IMS DC session; allocate a media resource for the split rendering session; and send, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session.

[0166] Clause 58. The apparatus of clause 57, wherein the MF caused to receive the request comprises the MF caused to receive the request from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the MF caused to create or modify the split rendering session over the standalone IMS DC session comprises the MF caused to create the split rendering session over the established standalone IMS DC session.

[0167] Clause 59. The apparatus of clause 57 or clause 58, wherein the MF caused to receive the request comprises the MF caused to receive the request from the client that is engaged in an established split rendering session over a standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the MF caused to create or modify the split rendering session over the standalone IMS DC session comprises the MF caused to modify the established split rendering session.

[0168] Clause 60. An apparatus implemented by a network device including a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS), the apparatus comprising: means for receiving a request for information for data channel (DC) media from a client on an user equipment; means for sending the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; means for creating or modifying a split rendering session over a standalone IMS DC session;means for allocating a media resource for the split rendering session; and means for sending, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session.

[0169] Clause 61. The apparatus of clause 60, wherein the means for receiving the request comprises means for receiving the request from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the means for creating or modifying the split rendering session over the standalone IMS DC session comprises means for creating the split rendering session over the established standalone IMS DC session.

[0170] Clause 62. The apparatus of clause 60 or clause 61, wherein the means for receiving the request comprises means for receiving the request from the client that is engaged in an established split rendering session over a standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the means for creating or modifying the split rendering session over the standalone IMS DC session comprises means for modifying the established split rendering session.

[0171] Clause 63. A method performed by a network device including a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS), the method comprising: receiving a request for information for data channel (DC) media from a client on a user equipment; sending the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; creating or modifying a split rendering session over a standalone IMS DC session; allocating a media resource for the split rendering session; and sending, via a data channel for the standalone IMS DC session, to the client, split- rendered media associated with the DC media during the split rendering session.

[0172] Clause 64. The method of clause 63, wherein the receiving the request comprises receiving the request from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein creating or modifying the split rendering session over the standalone IMS DC session comprises creating the split rendering session over the established standalone IMS DC session.

[0173] Clause 65. The method of clause 63 or clause 64, wherein receiving the request comprises receiving the request from the client that is engaged in an established split rendering session over a standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein creating or modifying the split rendering session over the standalone IMS DC session comprises modifying the established split rendering session.

[0174] Clause 66. A computer-readable storage medium that is non-transitory and has instructions stored therein that, in response to execution by at least one processing circuitry, causes a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS) to at least: receive a request for information for datachannel (DC) media from a client on a user equipment; send the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; create or modify a split rendering session over a standalone IMS DC session; allocate a media resource for the split rendering session; and send, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session.

[0175] Clause 67. The computer-readable storage medium of clause 66, wherein the MF caused to receive the request comprises the MF caused to receive the request from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the MF caused to create or modify the split rendering session over the standalone IMS DC session comprises the MF caused to create the split rendering session over the established standalone IMS DC session.

[0176] Clause 68. The computer-readable storage medium of clause 66 or clause 67, wherein the MF caused to receive the request comprises the MF caused to receive the request from the client that is engaged in an established split rendering session over a standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the MF caused to create or modify the split rendering session over the standalone IMS DC session comprises the MF caused to modify the established split rendering session.

[0177] Clause 69. An apparatus comprising means for performing the method of any of clauses 63 to 65.

[0178] Clause 70. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 63 to 65.

[0179] Clause 71. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 63 to 65.

[0180] Clause 72. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 63 to 65.

[0181] Many modifications and other implementations of the disclosure set forth herein will come to mind to one skilled in the art to which the disclosure pertains having the benefit of the teachings presented in the foregoing description and the associated figures. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Moreover, although the foregoing description and the associated figures describe example implementations in the context of certain example combinations of elements and / or functions, it should be appreciated that different combinations of elements and / or functions may be provided by alternative implementations without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those explicitly described above are also contemplated as may be set forth in some of the appendedclaims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

WHAT IS CLAIMED IS:

1. A method performed by a client on a user equipment, the method comprising: sending, to an Internet Protocol, IP, multimedia subsystem, IMS, a request to modify an established split rendering session with a media function, MF, of the IMS over a standalone IMS data channel, DC, session; sending, to the IMS, a request for information for data channel, DC media; receiving, from the IMS, the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; and initiating, based on the information for the DC media that indicates the DC media is capable of being split rendered, one or more operations of a procedure to establish a split rendering session with a new MF of the IMS over the standalone IMS DC session.

2. The method as claimed in claim 1 further comprising receiving, via an IMS data channel for the standalone IMS DC session, split-rendered media associated with the DC media during the split rendering session.

3. The method as claimed in claim 1 or claim 2, wherein the sending the request comprises sending the request by the client engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session, and wherein the initiating the one or more operations comprises initiating the one or more operations to establish the split rendering session over the established standalone IMS DC session.

4. The method as claimed in claim 3, wherein the sending the request for the information for the media to the IMS comprises sending the request for the information for the DC media to the new MF of the IMS; wherein the receiving the information for the DC media from the IMS comprises receiving the information for the DC media from the new MF of the IMS, wherein the method further comprises determining, based on the information for the DC media, that the DC media is capable of being split rendered, and wherein the initiating the one or more operations to establish the split rendering session over the established standalone IMS DC session is based on the determining that the DC media is capable of being split rendered.

5. The method as claimed in any of claims 1 to 4 further comprising: determining, based on the DC media, to modify the split rendering session; andinitiating, based on the determining to modify the split rendering session, one or more operations of a procedure to modify the split rendering session over the standalone IMS DC session.

6. The method as claimed in any of claims 1 to 5 further comprising: determining, based on the DC media, to terminate the split rendering session; and initiating one or more operations of a procedure to establish a new split rendering session over a standalone IMS DC session or over an IMS DC session.

7. The method as claimed in claim 6, wherein the initiating the one or more operations of the procedure to establish the new split rendering session is based on a determination that network conditions have improved or based on a specific request by the client.

8. The method as claimed in any of claims 1 to 7, wherein the sending of the request to modify the established split rendering session is based on determining, by the client, media capabilities of the client in the established split rendering session cannot meet the related rendering requirements.

9. The method as claimed in any of claims 1 to 8, wherein the split rendering session is established between the client and the new MF via an IMS data channel for application download.

10. The method as claimed in claim 9, wherein the split rendering session is further established between the client on the user equipment and a client in another user equipment via the new MF.

11. An apparatus comprising means for performing the method as claimed in any of claims 1 to 10.

12. A method performed by a network device including an Internet Protocol (IP) multimedia subsystem (IMS) application server (AS), the method comprising: receiving, from a client on a user equipment, a request to modify an established split rendering session with a media function, MF, of the IMS over a standalone IMS data channel (DC) session; sending, to a data channel signaling function (DCSF) of the IMS, an event notification to modify the established split rendering session; receiving, from the DCSF in response to the event notification, data channel control instructions, discovering a new media function, MF, of the IMS, wherein the new MF is different from the MF; and sending, to the new MF , a request to allocate a media resource for a split rendering session; andcreating or modifying an IP transport connection for the split rendering session to enable the client to establish the split rendering session over the standalone IMS DC session with the new media function.

13. The method as claimed in claim 12 further comprising notifying the client that the split rendering session over the standalone IMS DC session has been created or modified.

14. An apparatus comprising means for performing the method as claimed in any of claims 12 to 13.

15. A method performed by a network device including a media function (MF) of an Internet Protocol (IP) multimedia subsystem (IMS), the method comprising: receiving a request for information for data channel (DC) media from a client on a user equipment that is engaged in an established split rendering session with another MF of the IMS over a standalone IMS DC session; sending, to the client, the information for the DC media, wherein the information indicates the DC media is capable of being split rendered; receiving, from an application server, AS, of the IMS, a request to allocate a media resource for a split rendering session of the DC media over a standalone IMS DC session; allocating the media resource for the split rendering session; sending, to the AS, a response indicating the media resource is allocated for the split rendering session; and sending, via a data channel for the standalone IMS DC session, to the client, split-rendered media associated with the DC media during the split rendering session.

16. The method as claimed in claim 15, wherein the receiving the request for the information comprises receiving the request for the information from the client that is engaged in an established standalone IMS DC session, wherein the established standalone IMS DC session is the standalone IMS DC session.

17. An apparatus comprising means for performing the method as claimed in any of claims 15 to 16.

Images