HK1170860A - Inter-device session duplication - Google Patents

Description

Inter-device session replication

Cross Reference to Related Applications

This application claims the benefit of U.S. provisional application No.61/261,421 filed on day 11, 16 of 2009, the contents of which are incorporated herein by reference.

Background

A wireless transmit/receive unit (WTRU) may participate in a communication session with a remote unit via an access network, such as a radio access network, e.g., a Universal Mobile Telecommunications System (UMTS) terrestrial wireless access network (UTRAN), a Long Term Evolution (LTE) network, a worldwide interoperability for microwave access (WiMax) network, or a Wireless Local Area Network (WLAN) network. Accordingly, this facilitates the WTRU to replicate (duplicate) the communication session on the second WTRU.

Disclosure of Invention

A method and apparatus for performing session duplication are provided. A communication session between a first wireless transmit/receive unit (WTRU) and a remote device may be duplicated to add a second WTRU to the communication session without disruption to the communication session on the first WTRU or the remote device. The communication session may be replicated by the network element in response to a policy or a communication session replication request. The first WTRU or the second WTRU may initiate session duplication by transmitting a communication session duplication request. Session duplication may include duplication of one or more media streams associated with a communication session. Session duplication may include transferring or sharing control of a communication session.

Drawings

The invention will be understood in more detail from the following description, given by way of example and understood in conjunction with the accompanying drawings, in which:

FIG. 1A is a system diagram of an example communication system in which one or more disclosed embodiments may be implemented;

figure 1B is a system diagram of an example wireless transmit/receive unit (WTRU) that may be used within the communication system shown in figure 1A;

fig. 1C is an example radio access network and an example core network that may be used within the communication system shown in fig. 1A;

figure 2 shows an example illustration of an internet protocol multimedia subsystem;

FIG. 3 shows an example illustration of a communication session using third party call control;

FIG. 4 shows an example illustration of a communication session using first party call control;

FIG. 5 shows an example illustration of a session duplication method using third party call control;

FIG. 6 is an exemplary illustration of a session duplication method using first party call control;

FIG. 7 shows an example illustration of a replicated communication session using third party call control;

fig. 8 shows an example illustration of a replicated communication session using first party call control.

Detailed Description

Fig. 1A is an illustration of an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messaging, broadcast, etc., to a plurality of wireless users. Communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, communication system 100 may use one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), orthogonal FDMA (ofdma), single carrier FDMA (SC-FDMA), and so forth.

As shown in fig. 1A, the communication system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a Radio Access Network (RAN) 104, a core network 106, a Public Switched Telephone Network (PSTN) 108, the internet 110, and other networks 112, it being understood that any number of WTRUs, base stations, networks, and/or network elements are contemplated by the disclosed embodiments. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. For example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include User Equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a Personal Digital Assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and the like.

The communication system 100 may also include a base station 114a and a base station 114b, each of the base stations 114a, 114b may be any type of device configured to wirelessly interact with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the core network 106, the internet 110, and/or the network 112. For example, the base stations 114a, 114B may be Base Transceiver Stations (BTSs), node B, e node bs, home enodeb, site controllers, Access Points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 104, which RAN 104 may also include other base stations and/or network elements (not shown) such as site controllers (BSCs), Radio Network Controllers (RNCs), relay nodes, and the like. Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic area, which may be referred to as a cell (not shown). A cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, one for each sector of the cell. In another embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology and thus may use multiple transceivers for each sector of the cell.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which air interface 116 may be any suitable wireless communication link (e.g., Radio Frequency (RF), microwave, Infrared (IR), Ultraviolet (UV), visible light, etc.). Air interface 116 may be established using any suitable Radio Access Technology (RAT).

More specifically, as previously described, communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) terrestrial radio access (UTRA), which may establish the air interface 116 using wideband cdma (wcdma). WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or evolved HSPA (HSPA +). HSPA may include High Speed Downlink Packet Access (HSDPA) and/or High Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as evolved UMTS terrestrial radio access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-advanced (LTE-a).

In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001x, CDMA2000EV-DO, Interim standard 2000 (IS-2000), Interim standard 95 (IS-95), Interim standard 856 (IS-856), Global System for Mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE (GERAN).

For example, the base station 114B in fig. 1A may be a wireless router, a home nodeb, a home enodeb, or an access point, and may use any suitable RAT for facilitating wireless connectivity in a local area, such as a business, residence, vehicle, campus, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE802.11 to establish a Wireless Local Area Network (WLAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may use a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE-a, etc.) to establish a pico cell (picocell) and a femto cell (femtocell). As shown in fig. 1A, the base station 114b may have a direct connection to the internet 110. Thus, the base station 114b does not have to access the internet 110 via the core network 106.

The RAN 104 may communicate with a core network 106, which may be any type of network configured to provide voice, data, application, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102 d. For example, the core network 106 may provide call control, billing services, mobile location-based services, prepaid calling, internetworking, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in fig. 1A, it should be understood that the RAN 104 and/or the core network 106 may communicate directly or indirectly with other RANs that employ the same RAT as the RAT 104 or a different RAT. For example, in addition to connecting to the RAN 104, which may employ E-UTRA radio technology, the core network 106 may also communicate with other RANs (not shown) that employ GSM radio technology.

The core network 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the internet 110, and/or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides Plain Old Telephone Service (POTS). The internet 110 may include a system of globally interconnected computer network devices that utilize common communication protocols, such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the TCP/IP internet protocol cluster. The network 112 may include wired or wireless communication networks owned and/or operated by other service providers. For example, the network 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU102c shown in fig. 1A may be configured to communicate with a base station 114a using a cellular-based radio technology and to communicate with a base station 114b using an IEEE802 radio technology.

Figure 1B is a system diagram of an example WTRU 102. As shown in fig. 1B, the WTRU102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 106, removable memory 132, a power source 134, a Global Positioning System (GPS) chipset 136, and other peripherals 138. It is to be appreciated that the WTRU102 may include any subcombination of the above elements while remaining consistent with an embodiment.

The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a Digital Signal Processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of Integrated Circuit (IC), a state machine, or the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functions that enable the WTRU102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which transceiver 120 may be coupled to a transmit/receive element 122. Although processor 118 and transceiver 120 are depicted in fig. 1B as separate components, it will be appreciated that processor 118 and transceiver 120 may be integrated together into an electronic package or chip.

Transmit/receive element 122 may be configured to transmit signals to a base station (e.g., base station 114 a) or receive signals from a base station (e.g., base station 114 a) over air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and receive both RF and optical signals. It should be appreciated that transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

Furthermore, although transmit/receive element 122 is depicted in fig. 1B as a single element, WTRU102 may include any number of transmit/receive elements 122. More particularly, the WTRU102 may use MIMO technology. Thus, in one embodiment, the WTRU102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

Transceiver 120 may be configured to modulate signals to be transmitted by transmit/receive element 122 and to demodulate signals received by transmit/receive element 122. As described above, the WTRU102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.

The processor 118 of the WTRU102 may be coupled to and may receive user input data from a speaker/microphone 124, a keyboard 126, and/or a display/touchpad 128, such as a Liquid Crystal Display (LCD) display unit or an Organic Light Emitting Diode (OLED) display unit. The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. Further, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 106 and/or the removable memory 132. The non-removable memory 106 may include Random Access Memory (RAM), Read Only Memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a Subscriber Identity Module (SIM) card, a memory stick, a Secure Digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located in the WTRU102, such as in a server or a home computer (not shown).

The processor 118 may receive power from the power source 134 and may be configured to distribute power to and/or control power to other components in the WTRU 102. The power source 134 may be any device suitable for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (nickel cadmium (NiCd), nickel zinc (NiZn), nickel metal hydride (NiMH), lithium ion (Li-ion), etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to a GPS chipset 136, which the GPS chipset 136 may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114 b) and/or determine its location based on the timing of signals received from two or more neighboring base stations. It is to be appreciated that the WTRU102 may acquire location information by any suitable location determination method while being consistent with an embodiment.

The processor 118 may also be coupled to other peripherals 138, which peripherals 138 may include one or more software and/or hardware modules that provide additional features, functionality, and/or wired or wireless connectivity. For example, the peripheral devices 138 may include accelerometers, electronic compasses (e-compass), satellite transceivers, digital cameras (for photos or video), Universal Serial Bus (USB) ports, vibrating devices, television transceivers, hands-free headsets, BluetoothA module, a Frequency Modulation (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, and so forth.

Fig. 1C is a system diagram of RAN 104 and core network 106 according to one embodiment. As previously described, the RAN 104 may use E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also communicate with a core network 106.

The RAN 104 may include enodebs 140a, 140B, 140c, although it is noted that the RAN 104 may include any number of enodebs while remaining consistent with an embodiment. The enodebs 140a, 140B, 140c may each include one or more transceivers for communicating with the WTRUs 102a, 102B, 102c, respectively, over the air interface 116. In one embodiment, the enode bs 140a, 140B, 140c may implement MIMO technology. Thus, the enodeb 140a may, for example, use multiple antennas to transmit wireless signals to the WTRU102a and receive wireless signals from the WTRU102 a.

each of the enodebs 140a, 140B, 140c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling, etc., in the uplink and/or downlink. As shown in fig. 1C, the enode bs 140a, 140B, 140C may communicate with each other via an X2 interface.

The core network 106 shown in fig. 1C may include a mobility management gateway (MME) 142, a serving gateway 144, and a Packet Data Network (PDN) gateway 146. Although each of the above elements are described as part of the core network 106, it is noted that any of these elements may be owned and/or operated by an entity other than the core network operator.

MME 142 may be connected to enodebs 142a, 142B, 142c in RAN 104 via an S1 interface and may serve as a control node. For example, the MME 142 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, and the like. MME 142 may also provide control plane functionality for handover between RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM or WCDMA.

The serving gateway 144 may be connected to each of the enodebs 140a, 140B, 140c in the RAN 104 via an S1 interface. The serving gateway 144 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102 c. The serving gateway 144 may also perform other functions such as anchoring the user plane during inter-enodeb handovers, triggering paging when downlink data is available to the WTRUs 102a, 102B, 102c, managing and storing the context of the WTRUs 102a, 102B, 102c, and the like.

The serving gateway 144 may also be connected to a PDN gateway 146, where the PDN gateway 146 may provide the WTRUs 102a, 102b, 102c with access to a packet-switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

The core network 106 may facilitate communication with other networks. For example, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and conventional landline communication devices. For example, the core network 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 106 and the PSTN 108. In addition, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to the network 112, where the network 112 may include other wired or wireless networks owned and/or operated by other service providers.

The wireless communication may include using an IP Multimedia (IM) Subsystem (IMs). For example, in LTE as shown in fig. 1C or in any other RAN/core network, the other network 112 may include IMS. A communication session using IMS may be transmitted or copied from one WTRU to another WTRU.

Fig. 2 is an exemplary illustration of an Internet Protocol (IP) IP multimedia core network (IM CN) including an IP Multimedia (IM) Subsystem (IMs) 200, an IM network 202, a Circuit Switched (CS) network 204, a legacy network 206 in communication with a wireless transmit/receive unit (WTRU) 210. IMS200 includes Core Network (CN) elements for providing IM services, such as voice, video, text, chat, or a combination thereof, delivered over a packet switched domain. AS shown, IMS200 includes a local subscriber server (HSS) 220, an Application Server (AS) 230, a Call Session Control Function (CSCF) 240, a Breakout Gateway Function (BGF) 250, a Media Gateway Function (MGF) 260, and a service centralization and continuity application server (SCC AS) 270. In addition to the logical entities and signal paths shown in fig. 2, the IMS may comprise any other configuration of logical entities, which may be located in one or more physical devices. Although not shown in the logical example, the WTRU may be a separate physical unit and may be connected into the IM CN via a base station, such as a node B or enhanced node B (enb).

The WTRU 210 may be any type of device configured to operate and/or communicate in a wired and/or wireless environment.

HSS 220 may maintain and provide relevant subscription information to support network entities handling IM sessions. For example, the HSS may include identification information, security information, location information, and profile information for IMS users.

The AS 230 may provide a value added IM service and may exist in a home network or a third location, wherein the AS 230 may be a SIP application server, an OSA application server, or a CAMELIM-SSF. The AS may be comprised in a network such AS a home network, a core network or a separate AS network. The AS may provide IM services. For example, the AS may perform functions of terminating a User Agent (UA), redirecting a server, initiating a UA, SIP proxy, or third party call control.

CSCF 240 may include a proxy CSCF (P-CSCF), a serving CSCF (S-CSCF), an emergency CSCF (E-CSCF), or an interrogating CSCF (I-CSCF). For example, the P-CSCF may provide a first point of contact for WTRUs within the IMS, the S-CSCF may handle session state, and the I-CSCF may provide a point of contact within the operator 'S network for IMS connections destined for subscribers of the network operator or roaming subscribers currently located within the network operator' S service area.

The BGF 250 may include an Interconnection Border Control Function (IBCF), an egress gateway control function (BGCF), or a transition gateway (TrGW). Although described as part of a BGF, the IBCF, BGCF, or TrGW may represent different logical entities and may be located in one or more physical entities, respectively.

The IBCF may provide application specific functionality in the SIP/SDP protocol layers to perform interworking between operator domains. For example, the IBCF may enable communication between SIP applications, network topology hiding, control transport plane functions, SIP signaling information screening, selection of appropriate signaling interconnections, and generation of accounting data records.

The BGCF may determine the route to IMS messages, such as SIP messages. The determination may be based on information received in a signaling protocol, management information, or database access. For example, for PSTN/CS domain termination, the BGCF may determine the network where PSTN/CS domain egress will occur and may select the MGCF.

The TrGW may be located on the media path and may be controlled by the IBCF and may provide network address and port translation as well as protocol translation.

MGF 260 may include a Media Gateway Control Function (MGCF), a Multimedia Resource Function Controller (MRFC), a Multimedia Resource Function Processor (MRFP), an IP multimedia subsystem-media gateway function (IMS-MGW), or a media resource Broker (Broker) (MRB). Although described as part of an MGF, an MGCF, MRFC, MRFP, IMS MGW, or MRB may represent different logical entities and may be located in one or more physical entities, respectively.

The MGCF may control call state connection control for media channels in the IMS; can communicate with CSCF, BGCF and circuit switching network entity; a route for incoming calls from the legacy network may be determined; protocol conversion between ISUP/TCAP and IM subsystem call control protocol can be executed; and out of band (out of band) information received in the MGCF may be forwarded to the CSCF/IMS-MGW.

MRFC and MRFP may control media stream resources. MRFC and MRFP may mix incoming media streams; sources of media streams (source media streams) may be sought, for example, for multimedia announcements; the media stream may be processed, such as by performing voice transcoding (transcoding) or media analysis; and may provide underlying (floor) control, such as by managing access rights to shared resources (e.g., in a conferencing environment).

IMS-MGWs can terminate bearer channels from switched circuit networks and media streams from packet networks, such as RTP streams in IP networks. IMS-MGWs may support media switching, bearer control, and payload processing, such as codecs, echo cancellers, or conference bridges. The IMS-MGW may interact with MGCF for resource control; managing resources such as echo cancellers; a codec may be included. The IMS-MGW may comprise resources for supporting UMTS/GSM transport media.

The MRB may support the sharing of heterogeneous MRF resource pools through multiple heterogeneous applications. The MRB may allocate or release certain MRF resources to calls requested by the consuming application based on, for example, certain MRF attributes. For example, when allocating MRF resources to an application, the MRB may evaluate specific characteristics of the media resources required for one or more calls; an identification of the application; rules for allocating MRF resources in different applications; per application or per subscriber SLA or QoS criteria; or a capacity model for a particular MRF resource.

The SCC AS 270 may provide communication session service continuity, such AS duplication, transfer, addition, or deletion of communication sessions, among the WTRUs in, for example, a subscription. The SCC AS may perform access transfer, session transfer or duplication, terminating access domain selection (T-ADS), and processing of multiple media streams. The SCC AS may merge or split media streams in one or more access networks. For example, when a WTRU requests to add a media flow through an additional access network during session establishment, or when a WTRU requests to add or delete a media flow to an existing session through one or more access networks, the media flow may be split or merged for session transfer, session termination.

The communication session may be performed between a WTRU (such as the WTRU shown in figure 1B) and a remote device using the communication system shown in figure 1A. A WTRU may access a communication system via a RAN (such as the RAN shown in figure 1C) or any other wired or wireless access network. The communication session may include services such as IP Multimedia (IM) services provided by the IMS as shown in fig. 2. Although described herein with reference to IMS, session duplication may be performed using any communication system or access network.

The WTRU, remote device, or network may control the communication session. Control of the communication session may include, for example, starting or stopping the media flow, adding or removing the media flow, transferring or replicating the media flow on another WTRU, adjusting the bit rate, or terminating the communication. For example, the WTRU may initiate a communication session with a remote device. The WTRU may first control the communication session. The WTRU may pass (pass) or share control of the communication session with the remote device.

Figure 3 shows an example illustration of a communication session 300 between a WTRU 310 and a remote device 320 using IMS. The communication session 300 may include a media flow 330 (media path) and control signaling 340 (control path) between the WTRU 310 and a remote device 320 via a network 350 (e.g., the IM CN shown in figure 2). IM CN 350 may include SCC AS 352, AS 354, CSCF356, and MGF 358.

The communication session 300 may be anchored in an SCC AS 352 associated with the WTRU 310. For example, SCC AS 352 may maintain information related to the communication session, such AS media stream identifiers and control device identifiers, and may provide call control (e.g., session replication) for communication session 300. For simplicity, the portion of the communication session between the WTRU 310 and the SCC AS 352 may be referred to AS an access leg (access leg), and the portion of the communication session between the SCC AS 352 and the remote device 320 may be referred to AS a remote leg (remote leg).

To establish the communication session 300 using IMS, the WTRU 310 may initiate a connection (access leg) via the IM CN 350. The WTRU 310 may receive the media flow 330 via the MGF358 and the control signaling 340 via the CSCF 356. The remote device 320 may participate in the communication session 300 (remote leg) via a remote network, such as via network 360.

Fig. 4 shows an example illustration of a point-to-point communication session 400 between a WTRU 410 and a remote unit 420 using IMS. The communication session 400 may include a media stream 430 and control signaling 440 established via a network, which may include an IM CN 450, such as the one shown in fig. 2. IM CN 450 may include CSCF 452 and MGF 458. The WTRU 410 may also receive control signals and media streams directly from a remote device without using an IM CN.

To establish a communication session 400 using IMS, a WTRU 410 may initiate a connection (access leg) via an IM CN 450. In the access leg, WTRU 410 may receive media flow 430 via MGF 458 and control signaling 440 via CSCF 452. The WTRU 410, the remote unit 420, or both may maintain communication for the communication session 400 and perform call control functions, such as session replication. The remote device 420 may participate in the communication session 400 (remote leg) via a remote network, such as via network 460.

Session duplication may be performed for communication sessions, such as the communication sessions shown in fig. 3 and 4. Session duplication may include adding one or more target WTRUs to an access leg of a communication session between a source WTRU and a remote device by duplicating the communication session or a portion of the communication session on the target WTRU without disrupting the communication session on the source WTRU or the remote device. For example, the first media stream may be replicated on a first target WTRU and the second media stream may be replicated on a second target WTRU. In another example, the first media stream may be replicated on the first target WTRU and the second WTRU. The target WTRU may be a separate physical unit (multi-unit session replication) or may be a separate physical interface in a single physical unit (multi-connection session replication).

The source WTRU and the target WTRU may be associated with each other via a collaborative session, which may be anchored in a third party such AS the SCC AS. The collaboration session may be established prior to session replication or during session replication.

The source WTRU, the target WTRU, or the network may initiate session duplication. For example, the source WTRU or the target WTRU may initiate session duplication in response to user input, context, or signal quality. In another example, a network device, such AS a SCC AS, may initiate session replication in response to a policy or service interruption. The source WTRU may first control the communication session or may share control with the remote device. The source WTRU may transfer control to the target WTRU or may share control with the target WTRU. Although figures 5 and 6 show source WTRU 502/602 initiated session replication for simplicity, target WTRU 504/604 initiated or network initiated session replication may be used.

Fig. 5 is an exemplary illustration of a session duplication method using IMS. At 510, the source WTRU502 may perform a communication session including media flow (media flow a) with the remote device 508 as shown in figure 3 via the access leg. For simplicity, only SCC AS506 is shown in fig. 5; however, the communication path may include the IM CN as shown in fig. 2 and 3 and/or other elements of the RAN as shown in fig. 1A and 1C. Although a single media stream and a single target WTRU 504 are shown, session duplication may include duplication of any number of communication sessions and media streams between any number of WTRUs.

At 520, the source WTRU502 may initiate session duplication by sending a communication session duplication request to the SCC AS 506. Session replication may be initiated based on, for example, information from the target WTRU 504 (such as information received during discovery) or in response to input from a user or subscriber of the source WTRU 502. The request may include an identification of the target media flow (media flow a), an identification of the target WTRU (WTRU-2) 504, and may indicate the use of the collaborative session.

At 530, the SCC AS506 may establish an access leg on the target WTRU 504, may replicate the media flow, and may send the replicated media flow to the target WTRU 504. At 540, the SCC AS506 may send a communication session duplication response to the source WTRU502, where the communication session duplication response may indicate that a duplication request was received and processed. The duplicate response may indicate that the duplicate request is accepted or rejected due to an unsupported server, lack of resources, or inability to establish an access leg with the target WTRU 504.

At 550, the source WTRU502 may maintain session control, such as in a collaborative session, and the target WTRU 504 may become the controlled party WTRU. Although fig. 5 shows session control maintained by the source WTRU502 for simplicity, the communication session may be controlled by the source WTRU502, the target WTRU 504, the network, or any combination thereof.

At 560, each of the source WTRU502 and the target WTRU 504 may continue the communication session by performing a media flow. Either the source WTRU502 or the target WTRU 504 may stop performing the media flow. The controlling WTRU may terminate or modify the communication session.

Fig. 6 is an example illustration of a session duplication method for a point-to-point communication session. At 610, the source WTRU 602 may perform a communication session including media flow (media flow a) with the remote device 608 via a network such as the IM CN shown in fig. 3. For simplicity, only CSCF 606 is shown; however, the communication path may include other elements of the IM CN as shown in fig. 2 and 3 and/or of the RAN as shown in fig. 1A and 1C. Further, although a single CSCF 606 is shown, the communication path may include multiple cfcfcfcfcfs, e.g., the source WTRU 602, the target WTRU 604, and the remote device 608 may each be associated with a different CFCF. Although a single media stream and a single target WTRU 604 are shown, session duplication may include any number of communication sessions and duplication of media streams among any number of WTRUs.

At 620, the source WTRU 602 may initiate session duplication by sending a communication session duplication request to the remote device 608 via the CSCF 606. Session replication may be initiated based on information from the target WTRU 604 (such as information received during a discovery period) or in response to input from a user or subscriber of the source WTRU 602. The request may include the identity of the target media stream (media stream a) and the identity of the target WTRU 604.

At 630, the remote device 608 may establish an access leg on the target WTRU 604, may replicate the media flow a and may send the replicated media flow to the target WTRU 604. At 640, the remote device 608 may send a communication session duplication response to the source WTRU 602 via the CSCF 606, where the communication session duplication response may indicate that a duplication request was received and processed. The duplicate response may indicate that the duplicate request is accepted or rejected due to an unsupported server, lack of resources, or inability to establish an access leg with the target WTRU 604.

Although not shown in fig. 6 for simplicity, session replication for a point-to-point communication session may include session control and collaboration sessions. The communication session may be controlled by the source WTRU502, the target WTRU 504, or both.

At 650, the source WTRU 602 and the target WTRU 604 may continue the communication session by performing media streaming, respectively. Either the source WTRU 602 or the target WTRU 604 may stop performing the media flow.

Fig. 7 shows an example illustration of a replicated communication session 700. The source WTRU 710 and the target WTRU 715 may participate in the replicated communication session 700 with the remote device 720 via a network 750, such as the IM CN shown in figure 2. IM CN 750 may include SCC AS 752, AS754, CSCF 756, and MGF 758.

The communication session 700 may be anchored in an SCC AS 752 associated with the WTRU 710. For simplicity, the portion of the communication session between WTRU 710/715 and SCC AS 752 may be referred to AS an access leg, and the portion of the communication session between SCC AS 752 and remote device 720 may be referred to AS a remote leg.

On the access leg, the source WTRU 710 and the target WTRU 715 may receive the replicated media flows 770A/770B via the MGF 758 and replicated control signaling 740A/740B via the SCC AS 752 and CSCF 756. The remote device 720 may participate in the communication session 700 via a remote network, such as the internet 760.

Fig. 8 shows an example illustration of a replicated point-to-point communication session 800. The source WTRU 810 and the target WTRU 815 may participate in the replicated point-to-point communication session 800 with the remote device 820 via a network 850, such as the IM CN shown in figure 2. The IM CN 850 may include CSCFs 856 and MGFs 858.

For simplicity, the portion of the communication session between WTRU 810/815 and CSCF856 may be referred to as an access leg, and the portion of the communication session between CSCF856 and remote device 820 may be referred to as a remote leg.

On the access leg, the source WTRU 810 and the target WTRU 815 may receive the replicated media flows 880A/880B via MGF 858 and replicated control signaling 840A/840B via CSCF 856. The remote device 820 may participate in the communication session 800 via a remote network, such as the internet 860. Although fig. 8 shows the media stream being replicated by MGF 858, the media stream may be replicated by remote device 820, such as using multiple transmitters.

Examples

1. A method for use in wireless communications, the method comprising:

the communication session is replicated.

2. The method of any preceding embodiment, wherein the replicating the communication session comprises performing the communication session via an access leg.

3. The method of any preceding embodiment, wherein replicating the communication session comprises replicating the communication session between the first WTRU and the remote device.

4. The method of any preceding embodiment, wherein the replicating the communication session includes adding a second WTRU to the communication session.

5. The method of any preceding embodiment, wherein replicating the communication session includes adding a second WTRU to an access leg.

6. The method of any preceding embodiment, wherein said replicating the communication session comprises transmitting a communication session replication request.

7. The method of any preceding embodiment, wherein the duplicate communication session is initiated by a first wireless transmit/receive unit (WTRU).

8. The method of any preceding embodiment, wherein the duplicate communication session is initiated by a second wireless transmit/receive unit (WTRU).

9. The method of any preceding embodiment, wherein the replication communication session is initiated by a network.

10. The method of any preceding embodiment, wherein said transmitting a communication session duplication request comprises transmitting the communication session duplication request into a network.

11. The method of any preceding embodiment, wherein said transmitting a communication session duplication request comprises transmitting the communication session duplication request into an IMS network.

12. The method of any preceding embodiment, wherein said transmitting a communication session duplication request comprises transmitting the communication session duplication request into an SCC AS.

13. The method of any preceding embodiment, wherein said replicating the communication session comprises anchoring the communication session in an SCC AS.

14. The method of any preceding embodiment, wherein the transmitting a communication session duplication request is performed by the first WTRU.

15. The method of any preceding embodiment, wherein the transmitting a communication session duplication request is performed by the second WTRU.

16. The method of any preceding embodiment, wherein the communication session duplication request indicates the communication session.

17. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session if the communication session is associated with the remote device.

18. The method of any preceding embodiment, wherein the duplicating the communication session comprises duplicating the communication session on a condition that the communication session is associated with the first WTRU.

19. The method of any preceding embodiment, wherein the duplicating the communication session comprises duplicating the communication session on a condition that the communication session is associated with a second WTRU.

20. The method of any preceding embodiment, wherein the replicating the communication session comprises receiving the communication session.

21. The method of any preceding embodiment, wherein the replicating the communication session comprises receiving the communication session at a first WTRU.

22. The method of any preceding embodiment, wherein the replicating the communication session comprises receiving the communication session at a second WTRU.

23. The method of any preceding embodiment, wherein the duplicating the communication session comprises duplicating the communication session if the second WTRU comprises a plurality of WTRUs.

24. The method of any preceding embodiment, wherein the replicating the communication session comprises replicating the communication session if the communication session replication request indicates a media stream.

25. The method of any preceding embodiment, wherein said receiving a communication session comprises receiving a media stream.

26. The method of any preceding embodiment, wherein said receiving a media stream comprises receiving a plurality of media streams.

27. The method of any preceding embodiment, wherein said transmitting a communication session duplication request comprises transmitting the communication session duplication request into the remote device.

28. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session if the communication session replication request indicates a collaborative session.

29. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session if the communication session replication request indicates transferred session control.

30. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session if the communication session replication request indicates shared session control.

31. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session if the communication session replication request indicates that session control is maintained.

32. The method of any preceding embodiment, wherein the replicating the communication session comprises replicating the communication session on a condition that a single device comprises a first WTRU and a second WTRU.

33. The method of any preceding embodiment, wherein the replicating the communication session comprises transmitting the communication session to the first WTRU.

34. The method of any preceding embodiment, wherein the replicating the communication session comprises transmitting the replicated communication session to the second WTRU.

35. The method of any preceding embodiment, wherein said replicating the communication session comprises receiving the communication session replication request.

36. The method of any preceding embodiment, wherein said replicating a communication session comprises discovering the communication session.

37. The method of any preceding embodiment, wherein the replicating the communication session includes discovering the first WTRU.

38. The method of any preceding embodiment, wherein the replicating the communication session includes discovering the second WTRU.

39. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session in response to user input.

40. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session in response to a policy.

41. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session in response to a service interruption.

42. The method of any preceding embodiment, wherein said replicating the communication session comprises replicating the communication session in response to a quality of service metric.

43. The method of any preceding embodiment, wherein the duplicating the communication session comprises duplicating the communication session in response to detecting a second WTRU.

44. The method of any preceding embodiment, wherein the duplicating a communication session comprises duplicating a communication session in response to detecting the communication session.

45. The method of any preceding embodiment, wherein the replicating the communication session comprises receiving an acknowledgement.

46. The method of any preceding embodiment, wherein the replicating the communication session comprises terminating the communication session.

47. The method of any preceding embodiment, wherein the replicating the communication session comprises terminating the communication session at the first WTRU without terminating the communication session at the second WTRU.

48. The method of any preceding embodiment, wherein the replicating the communication session comprises terminating the communication session at the second WTRU without terminating the communication session at the first WTRU.

49. A wireless transmit/receive unit (WTRU) configured to perform at least a portion of any of the preceding embodiments.

50. A base station configured to perform at least a part of any of the preceding embodiments.

51. An integrated circuit configured to perform at least a portion of any of the preceding embodiments.

Although the features and elements of the present invention are described above in particular combinations, it will be understood by those of ordinary skill in the art that each feature or element can be used alone without the other features and elements or in various combinations with other features and elements of the present invention. Furthermore, the methods provided by the present invention may be implemented in a computer program, software, or firmware executed by a computer or a processor, wherein the computer program, software, or firmware is embodied in a computer-readable storage medium. Examples of computer readable media include electronic signals (transmitted over a wired or wireless connection) and computer readable storage media. Examples of computer readable storage media include, but are not limited to, Read Only Memory (ROM), Random Access Memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and Digital Versatile Disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims (15)

1. A method for use in wireless communications, the method comprising:

transmitting a communication session duplication request from a first wireless transmit/receive unit (WTRU) to a first network, wherein the communication session duplication request indicates a communication session associated with a remote device; and

receiving the communication session at the first WTRU.

2. The method of claim 1, wherein the transmitting is performed on a condition that the communication session is associated with the first WTRU and the communication session duplication request indicates a second WTRU.

3. The method of claim 1, wherein the transmitting is performed on a condition that the communication session is associated with a second WTRU.

4. The method of claim 1, wherein the communication session duplication request indicates a media stream, and the receiving a communication session comprises receiving the media stream.

5. The method of claim 1, wherein the transmitting comprises transmitting the communication session duplication request to the remote device.

6. The method of claim 1, wherein the communication session duplication request indicates a request to transfer session control.

7. The method of claim 1, wherein a device comprises the first WTRU; the method further comprises the following steps:

receiving the communication session at a second WTRU, wherein the apparatus comprises the second WTRU.

8. An apparatus for use in wireless communications, the apparatus comprising:

a first wireless transmit/receive unit (WTRU) configured to:

transmitting a communication session duplication request to a first network, wherein the communication session duplication request indicates a communication session associated with a remote device; and

the communication session is received.

9. The apparatus of claim 8, wherein the first WTRU is configured to transmit on a condition that the communication session is associated with the first WTRU and the communication session duplication request indicates a second WTRU.

10. The apparatus of claim 8, wherein the first WTRU is configured to transmit on a condition that the communication session is associated with a second WTRU.

11. The apparatus of claim 8, wherein the communication session duplication request indicates a media flow and the first WTRU is configured to receive the media flow.

12. The apparatus of claim 8, wherein the first WTRU is configured to transmit the communication session duplication request to the remote device.

13. The apparatus of claim 8, wherein apparatus comprises the first WTRU; the device also includes:

receiving the communication session at a second WTRU, wherein the apparatus comprises the second WTRU.

14. A method for use in wireless communications, the method comprising:

receiving an associated communication session from a remote device;

transmitting the communication session to a first wireless transmit/receive unit (WTRU);

replicating the communication session; and

the replicated communication session is transmitted to a second WTRU.

15. The method of claim 14, further comprising:

a communication session duplication request is received indicating the communication session.