Provisional Patent Application No. In some configurations, UE may refer to a mobile, wireless device. The terms may also refer to devices that have similar capabilities but that are not readily transportable, such as desktop computers, set-top boxes, TV, IPTV or network nodes. When a UA is a network node, the network node could act on behalf of another function such as a UA or a fixed line device and simulate or emulate the UA or fixed line device. In other words, some functions that were traditionally carried out by a UA can be distributed in the form of a remote UA, where the remote UA represents the UA in the network.
|Published (Last):||10 September 2013|
|PDF File Size:||14.66 Mb|
|ePub File Size:||4.20 Mb|
|Price:||Free* [*Free Regsitration Required]|
Provisional Patent Application No. In some configurations, UE may refer to a mobile, wireless device. The terms may also refer to devices that have similar capabilities but that are not readily transportable, such as desktop computers, set-top boxes, TV, IPTV or network nodes. When a UA is a network node, the network node could act on behalf of another function such as a UA or a fixed line device and simulate or emulate the UA or fixed line device.
In other words, some functions that were traditionally carried out by a UA can be distributed in the form of a remote UA, where the remote UA represents the UA in the network. The term "UA" can also refer to any hardware or software component that can terminate a communication session that could include, but is not limited to, a SIP session.
Also, the terms "user agent," "UA," "user equipment, "UE," and "node" might be used synonymously herein. Those skilled in the art will appreciate that these terms can be used interchangeably within the application. Some UEs may be capable of multimode operation where they can operate on more than one access network technology either on a single access network at a time or in some devices using multiple access technologies simultaneously.
The network is often classified as a 2. High-speed data applications, such as video and other multimedia services, benefit from EGPRS' increased data capacity. A UE may also operate in other wireless technologies such as but not limited to Wimax, Wifi, etc. For example, Session Initiation Protocol SIP and other related internet based communication technologies support registering of multiple devices with a network, each device sharing the same user identity for example, a SIP or TeI Uniform Resource Identifier URI , or a group of overlapping or identical identities.
In keeping with the evolution of communication networks, SIP is also capable of support of various media types including but not limited to text, data for applications, audio and video, etc within the same session established between a network and a UE. In some cases, the controller function may be transferred from a controller UE to another UE which has the capability of providing controller functionality.
In some cases multiple UEs may act as controller. In some cases, a UE has multiple User Agents, one per access network. Similarly, a administrator or controller UA may be configured to manage the operation of various features or parameters made available via one or more other UAs. An administrator or controller UA can also be an administrator or controller UE.
In the following, the terms UE and UA are often used interchangeably, unless it is clear from the context. The consistent public user identities also allow a user to be reachable at whichever UE the user happens to be currently using. This flexibility minimizes the necessity of maintaining a large list of device oriented contacts to identify each user in an address book and having to decide which device is best when attempting to establish a communication - each user and all their associated cell phone, home phones, computers, etc.
Furthermore, when a UE is already involved in a session that uses one or more media types and the UE receives an invitation to add or modify one or more media types to the session, a controller UE should be identified so that the user can request to transfer the new media type to a different UE that can support and process or render the new media type. For example, if a user is engaged in an audio session on the user's mobile phone and the user wishes to accept added video steaming media on another device, the controller UE provides the user with the ability to select another device, such as a Laptop PC, for receiving and displaying the added video streaming media based on such as device capability and user preference.
For example, a user may accept the session or one or more media components of the session on his mobile phone outside in the garden but then move inside the house and transfer both the audio and video components to his desktop computer and since the user wishes now to control the session from his desktop computer he also transfers control of the session from his mobile phone to his desktop computer. Finally, controller status functionality should only be transferred between certain member UEs capable of being the controller devices e.
Accordingly, it is important to provide a secure mechanism to distribute and process transfer requests for the session, media, and controller functionality among a set of UEs that can potentially be used by different subscribers e.
The first UE is initially assigned controller function for the session. The method includes receiving a request from the first UE to transfer at least a subset of controller function for the session to the second UE, and determining a capability of the second UE to implement a controller function.
When the second UE has the capability to operate as a controller, the method includes assigning the at least a subset of controller function for the session to the second UE, and responding to the request to transfer at least a subset of controller function for the session to notify the first UE to release the session.
The first UE is initially assigned controller function for the session and the first UE includes an interface. The method includes receiving a request via the first UE interface to transfer controller function for the session to the second UE, transmitting a session controller function transfer request to an application server, and receiving a transfer response from the application server.
When the transfer response indicates that the first UE should release session controller function, the method includes releasing session controller function. When the second UE has the capability to receive the session for communicating media content, the method includes transferring the session for communicating media content to the second UE, and responding to the request to transfer the session for communicating media content to the second UE to notify the first UE to release the session.
It should be understood, however, that the drawings and detailed description relating thereto are not intended to limit the claimed subject matter to the particular form disclosed. Rather, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the claimed subject matter.
By way of illustration, both an application running on a computer and the computer can be a component. Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.
The term "article of manufacture" or alternatively, "computer program product" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer readable media can include but are not limited to magnetic storage devices for example, hard disk, floppy disk, magnetic strips, and the like , optical disks for example, compact disk CD , digital versatile disk DVD , and the like , smart cards, and flash memory devices for example, card, stick, and the like.
Additionally, it should be appreciated that a carrier wave can be employed to carry computer-readable electronic data such as those used in transmitting and receiving electronic mail or in accessing a network such as the Internet or a local area network LAN. Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.
The system may be implemented in various communication networks wherein UEs are configured to be assigned a single shared identification e. Within the network, each UE may initiate various communication sessions, each session involving the communication of data that may include multiple media types such as but not limited to data for applications media type application , voice, text, video including various encoding schemes and audio. The controller function may be moved from a first controller UE to another UE depending upon but not limited to network rules, operator policies, user preferences, or other system requirements.
In some cases, the UEs that have controller or controllee function may be provided via a network wherein the controllee UEs are configured in a similar manner as the controller UEs having similar functional capabilities and system designs. When a UE among UEs is first registered with a network, the first UE supporting controller functionality registered with the wireless server may be automatically designated as the administrator or controller UE.
In some cases, when a network receives an initial transfer request for collaborative sessions sent by a UE supporting the controller functionality, the UE may be automatically designated as the administrator or controller UE. However, other algorithms may be employed to determine the preliminary controller UE amongst a collection of UEs.
After connecting to the network, a user may optionally change the controller designation from the first registered UE to one of the other registered UEs under control by the user or by other associated users. After receiving the invitation, the network transfers, forwards, or sends the session invitation e. If the user is already involved in a session using various media types and an offer e.
This second clarification may cover the possibility that requests arrive out of the order in which they were sent. While maintaining an on-going collaborative session, each controller UE may transfer media flows of the collaborative session to a target UE.
Furthermore, each controller UE may be configured to transfer all or some of the available one or more media flows to a target UE with or without establishing a collaborative session.
If transferring all media flows to a target UE, the existing session on the controller UE may be released. For example, for enablement and execution of IUT, the SCC AS may first analyze the information required for Inter-UE Transfer as described below and decide which access networks should be executed based on operator policy and user preferences. Below are examples of two possible embodiments for such a media feature tag. This string could contain the same identifier value as in the "reg-id" parameter e.
The UE could allow the user to define human understandable labels for the string used in the media feature tag since the user may need to use these labels to indicate to which access leg they wish to transfer a media type to when performing a media transfer e. Values appropriate for use with this feature-tag string with an equality relationship. The feature-tag is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms This feature-tag is most useful in a communications application, for describing the capabilities of a device, such as a phone or PDA.
Table 2  In another example shown in Table 3, the existing g. Summary of the media feature indicated by this tag. This feature-tag when used is a none.
Examples of typical use Indicating that a mobile phone principal can support or wants to use ICS or that a network node server wants to invoke ICS functionality and Indicating the registration flow that the device is using.
Using these mechanisms the SCC AS can obtain the access-type and, if present, access-class values from the P-Access-Network- lnfo header and the value of the g. Note that the P-CSCF can also include additional access types or access class values in the P-Access-Network-lnfo header containing the access class and access type as verified by the network and indicated as such by the inclusion of the "np" network provided parameter. As a result, the request is routed to the UE using the desired access leg using the mechanism described in RFC and correspondingly if the request is accepted the media to also be established using that access leg.
By indicating "shall", the operator mandates the UE to start session transfer according to the home operator's list of preferred access networks as soon as possible. By indicating "should", the operator recommends the UE to start session transfer according to the home operator's list of preferred access networks, if session transfer is possible and desirable after having taken into account the Local Operating Environment Information.
By indicating "may", the operator leaves the UE free to decide whether or not to start session transfer in accordance with user preferences when configured , if session transfer is possible and desirable after having taken into account the Local Operating Environment Information. Whenever user preferences are not configured, the UE may take into account the home operator's list of preferred access networks.
The operator policy may also indicate whether to keep or drop non transferable media flow s in the case of partial session transfer. Generally, the operator policy for ession transfer is consistent with operator policy for T-ADS.
The Local Operating Environment Information can be implementation specific and may comprise of such items as radio environment information, quality of IP connection jitter, delay and packet loss , application specific requirements, memory considerations, power considerations, etc.
Generally, user preferences for Access Transfer are not transferred to the network. The UE could have previously allowed the user to define human understandable labels for the string used in the media feature tag so that the user can use these labels to indicate which access leg they which to transfer a media type when performing a media transfer e. Alternatively, the device, when registering over an access type, provides a mapping between human readable access types that the user can read and the access types that the device supports.
Example embodiments are below but those skilled in the art will appreciate that the mapping could be more or less constrained where the idea is that a human readable alphanumeric string is mapped against a number of possible P-.
To do this the UE includes in the request used to request the media transfer e. When the SCC AS or another network node receives the media transfer request it then includes the Accept-Contact header along with its values from the media transfer request in the request sent to the UE the media is to be transferred to.
This causes the request to be routed to the UE using the desired access leg using the mechanism described in RFC and, correspondingly, if the request is accepted, the media to also be established using that access leg. Note that the UE the media is to be transferred to could, in some cases such as the example above , be the same UE acting as the controller UE sending the media transfer request. The flow allows for transferring service control of a session containing two media components from a first controller UE UE-1 to a second controllee UE UE In this example, UE UE-1 initially facilitates collaborative session control.
As illustrated, in step , UE-1 initiates the process of transferring the collaborative session control and media type media-A to UE-2 by communicating or sending a transfer request to the SCC AS. The transfer request indicates that the collaborative session control and media type Media-A are to be transferred to UE Alternatively, the media type may be indicated by signalling the appropriate feature tags etc.
The SCC AS would then ensure that the feature tags in the accept contact header and the explicit and required parameters are set to choose an alternative contact to that of the one performing the request. Alternatively, SDP is included that contains the media type to be transferred. As this point UE-2 becomes the controller UE based upon receiving the media feature tag that indicates the IUT controller function for the collaborative sessions. In other implementations, however, UE-1 may send a transfer request including the Media to be transferred, while keeping the collaborative session control on the UE-1 In this case the transfer request doesn't include the indication, identifier, token, flag, or media feature tag of the collaborative session control IUT Controller function.
At this point, the system may optionally update the remote leg between the SCC AS and the remote party in accordance with the establishment of the new session with UE For example, the remote leg may be updated to implement a video codec adjustment or change e. After receiving the transfer response, the prior session carrying media-A on UE-1 may be released and the collaborative session control is released in step Media type Media-A is communicated between UE-2 and the remote party and media type Media-B continues to be communicated between UE-1 and the remote party.
A Warning may be included in the response indicating the reason for the failure.
US9001835B2 - Method and system for establishing emergency call - Google Patents
Specification : General Versions Responsibility Related. Reference: Action date Action Author.
Where is the use of SIP defined in 3GPP?