Abstract: A method performed for handling an ongoing communication session with a remote party in a communication network is provided. A user is associated with a set of User Equipments, UEs, in a single user subscription. The set of UEs includes at least a first UE and a second UE. The ongoing communication session with the remote party involves the first UE. For each respective UE out of the set of UEs, information is obtained. The information is related to the respective UE's name recognizable by the user, communication capabilities, and communication session status. A user indication is obtained. The user indication is based on the received information. The indication indicates to transfer the ongoing communication session with the remote party. According to the indication, a network node is requested to transfer the ongoing communication session from the first UE to the second UE.

Abstract: There is provided mechanisms for providing a message service center address. The method is performed by a core network node. The method comprises providing, to a terminal device and as part of performing a registration procedure between a local serving network and the terminal device, a message service center address to terminal device address to a public safety answering point (PSAP) of the local sewing network for an advanced mobile location (AML) service.

Abstract: A Mission-Critical Push-To-Talk (MCPTT) node is connected to a group of user equipments (UEs) served by the MCPTT node. The MCPTT node generates a Multimedia Broadcast and Multicast Service (MBMS) Subchannel Control Key (MSCCK), sends first messages to the UEs in unicast, wherein the first messages include the generated MSCCK, generates at least one MBMS subchannel control message, applies integrity protection and/or confidentiality protection to the at least one MBMS subchannel control message with the MSCCK, and sends the at least one MBMS subchannel control message in multicast.

Abstract: A Mission-Critical Push-To-Talk (MCPTT) node is connected to a group of user equipments (UEs) served by the MCPTT node. The MCPTT node generates a Multimedia Broadcast and Multicast Service (MBMS) Subchannel Control Key (MSCCK), sends first messages to the UEs in unicast, wherein the first messages include the generated MSCCK, generates at least one MBMS subchannel control message, applies integrity protection and/or confidentiality protection to the at least one MBMS subchannel control message with the MSCCK, and sends the at least one MBMS subchannel control message in multicast.

Abstract: A Mission-Critical Push-To-Talk (MCPTT) node is connected to a group of user equipments (UEs) served by the MCPTT node. The MCPTT node generates a Multimedia Broadcast and Multicast Service (MBMS) Subchannel Control Key (MSCCK), sends first messages to the UEs in unicast, wherein the first messages include the generated MSCCK, generates at least one MBMS subchannel control message, applies integrity protection and/or confidentiality protection to the at least one MBMS subchannel control message with the MSCCK, and sends the at least one MBMS subchannel control message in multicast.

Abstract: A Mission-Critical Push-To-Talk (MCPTT) node is connected to a group of user equipments (UEs) served by the MCPTT node. The MCPTT node generates a Multimedia Broadcast and Multicast Service (MBMS) Subchannel Control Key (MSCCK), sends first messages to the UEs in unicast, wherein the first messages include the generated MSCCK, generates at least one MBMS subchannel control message, applies integrity protection and/or confidentiality protection to the at least one MBMS subchannel control message with the MSCCK, and sends the at least one MBMS subchannel control message in multicast.

Abstract: A Mission-Critical Push-To-Talk (MCPTT) node is connected to a group of user equipments (UEs) served by the MCPTT node. The MCPTT node generates a Multimedia Broadcast and Multicast Service (MBMS) Subchannel Control Key (MSCCK), sends first messages to the UEs in unicast, wherein the first messages include the generated MSCCK, generates at least one MBMS subchannel control message, applies integrity protection and/or confidentiality protection to the at least one MBMS subchannel control message with the MSCCK, and sends the at least one MBMS subchannel control message in multicast.

Abstract: A method of determining whether to apply a media specific action to communications in an Internet Protocol Multimedia Subsystem enabled network is disclosed, the method comprising at an application server receiving (33) an instruction comprising a rule, wherein the rule comprises conditions for implementing the media specific action, wherein the conditions comprise a first condition specifying (34) a set of one or more media types and a second condition specifying (35) that no media types other than the types in the set are present. On receipt of a protocol message (36) setting up or modifying a communication the method further comprises determining if the protocol message meets the first condition and the second condition, and only if both conditions are met (37), applying the media specific action to the communication.

Abstract: A method of authenticating a request to change IMS supplementary service data stored at an application server within an IMS network. The method comprises sending from a user equipment to the application server a request for current IMS supplementary service data, on receipt by the user equipment of a response containing the IMS supplementary data in an XML configuration document, and an indication that an access code is required to change the supplementary service data. The method further comprises constructing an amended XML configuration document, incorporating the amended XML document into an Extensible Mark-up Language, XML, Configuration Access Protocol, XCAP, message, incorporating an access code into the XCAP message at a location external to the XML document, and transmitting the XCAP message from the user equipment to the application server.

Abstract: A Mission-Critical Push-To-Talk (MCPTT) node is connected to a group of user equipments (UEs) served by the MCPTT node. The MCPTT node generates a Multimedia Broadcast and Multicast Service (MBMS) Subchannel Control Key (MSCCK), sends first messages to the UEs in unicast, wherein the first messages include the generated MSCCK, generates at least one MBMS subchannel control message, applies integrity protection and/or confidentiality protection to the at least one MBMS subchannel control message with the MSCCK, and sends the at least one MBMS subchannel control message in multicast.

Abstract: A method and apparatus for managing a HOLD announcement in a communication network. At an Application Server, AS, a message is received from a user terminal, the message comprises of an indicator, specifying whether the AS should provide a HOLD announcement in the event of a change in direction of a media stream between the user terminal and a further node during a session. The AS stores the indicator in a memory. Upon determination that a change in direction of the media stream has occurred, the AS determines, from the indicator, whether or not to provide the HOLD announcement to the further node.

Abstract: A method of authenticating a request to change IMS supplementary service data stored at an application server within an IMS network. The method comprises sending from a user equipment to the application server a request for current IMS supplementary service data, on receipt by the user equipment of a response containing the IMS supplementary data in an XML configuration document, and an indication that an access code is required to change the supplementary service data. The method further comprises constructing an amended XML configuration document, incorporating the amended XML document into an Extensible Mark-up Language, XML, Configuration Access Protocol, XCAP, message, incorporating an access code into the XCAP message at a location external to the XML document, and transmitting the XCAP message from the user equipment to the application server.

Abstract: According to a first aspect of the present invention there is provided a method of facilitating the end-to-end transfer of a URI between a plurality of SIP entities. The method comprising generating a SIP message and including the URI to be transferred in a Contact header of the message and including in the Contact header a parameter indicating to a back-to-back user agent that this URI is not to be changed or replaced.

Abstract: A method and apparatus for managing a HOLD announcement in a communication network. At an Application Server, AS, a message is received from a user terminal, the message comprises of an indicator, specifying whether the AS should provide a HOLD announcement in the event of a change in direction of a media stream between the user terminal and a further node during a session. The AS stores the indicator in a memory. Upon determination that a change in direction of the media stream has occurred, the AS determines, from the indicator, whether or not to provide the HOLD announcement to the further node.

Abstract: A method and apparatus for indicating to a node in an IMS network a transfer between two endpoints. A node in a first network determines that a communication session is to be transferred from a first endpoint to a second endpoint. The node includes an indication of at least one of the endpoints, and an explicit communication transfer indicator, in a message. The message is then sent towards the node in the IMS network. This allows the node in the IMS network to determine that a transfer has taken place and, if necessary, take further action.

Abstract: According to a first aspect of the present invention there is provided a method of facilitating the end-to-end transfer of a URI between a plurality of SIP entities. The method comprising generating a SIP message and including the URI to be transferred in a Contact header of the message and including in the Contact header a parameter indicating to a back-to-back user agent that this URI is not to be changed or replaced.

Abstract: According to a first aspect of the present invention there is provided a method of facilitating the end-to-end transfer of a URI between a plurality of SIP entities. The method comprising generating a SIP message and including the URI to be transferred in a Contact header of the message and including in the Contact header a parameter indicating to a back-to-back user agent that this URI is not to be changed or replaced.

Abstract: An application server invocated terminating service is enabled in an IMS based communication network. A request-to-establish message is received by an application server in a terminating part of the network, initiated by a calling party associated to an originating part of the network. The request-to-establish message is supplemented with information that the terminating service is desired to a called party associated to the terminating part, before being transmitted to an access node to which the called party is associated. A called terminal used by the called party is then notified that the terminating service is applicable by the access node, before the application server is confirmed that the called terminal has been notified. Supplementing the request-to-establish message in this way, enables parties communicating over an IMS based network to use the terminating service, regardless of whether they are directly associated to the network or via a non-IMS based communications network.

Abstract: A method and apparatus for indicating to a node in an IMS network a transfer between two endpoints. A node in a first network determines that a communication session is to be transferred from a first endpoint to a second endpoint. The node includes an indication of at least one of the endpoints, and an explicit communication transfer indicator, in a message. The message is then sent towards the node in the IMS network. This allows the node in the IMS network to determine that a transfer has taken place and, if necessary, take further action.

Abstract: According to a first aspect of the present invention there is provided a method of facilitating the end-to-end transfer of a URI between a plurality of SIP entities. The method comprising generating a SIP message and including the URI to be transferred in a Contact header of the message and including in the Contact header a parameter indicating to a back-to-back user agent that this URI is not to be changed or replaced.