IMS based P2P streaming and download services

• US 9,398,498 B2
• Filed: 09/30/2013
• Issued: 07/19/2016
• Est. Priority Date: 09/28/2012
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: Ozgur, Oyman
• Primary Examiner(s): Cho, Un C
• Assistant Examiner(s): Roudani, Oussama
• Application Number:
  US14/041,363
• Publication Number:
  US 20140095730A1
• Time in Patent Office: 1,023 Days
• Field of Search: 370/312, 370/252, 709/231, 709/203, 709/229
• US Class Current: 1/1
• CPC Class Codes: H04B 17/318 Received signal strength
• CPC Class Codes: H04J 11/00 Orthogonal multiplex systems, e.g. using WALSH codesH04J13/00 takes precedence
• CPC Class Codes: H04J 11/0086 Search parameters, e.g. search strategy, accumulation length, range of search, thresholds code acquisition in DSSS H04B1/7075
• CPC Class Codes: H04J 3/1694 Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers Passive Optical Networks H04Q11/0062
• CPC Class Codes: H04L 1/1812 Hybrid protocols; Hybrid automatic repeat request [HARQ]
• CPC Class Codes: H04L 1/1861 Physical mapping arrangements for ACK signaling see also H04L5/0053
• CPC Class Codes: H04L 1/1864 ARQ related signaling H04L1/1607 takes precedence
• CPC Class Codes: H04L 1/1893 Physical mapping arrangements physical resource mapping in general H04L5/00
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 41/5032 Generating service level reports
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 5/001 the frequencies being arranged in component carriers
• CPC Class Codes: H04L 5/0035 Resource allocation in a cooperative multipoint environment
• CPC Class Codes: H04L 5/0055 Physical resource allocation for ACK/NACK for physical mapping arrangements in ARQ protocols H04L1/1861
• CPC Class Codes: H04L 5/0057 Physical resource allocation for CQI
• CPC Class Codes: H04L 5/0073 Allocation arrangements that take into account other cell interferences for intercell interference mitigation or co-ordination in orthogonal multiplex systems H04J11/005
• CPC Class Codes: H04L 5/0091 Signaling for the administration of the divided path
• CPC Class Codes: H04L 5/14 Two-way operation using the same type of signal, i.e. duplex
• CPC Class Codes: H04L 65/60 Network streaming of media packets
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 65/65 : Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04W 24/02 : Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/08 : Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 24/10 : Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 28/0205 : at the air interface dynamic wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/0215 : based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 28/0221 : power availability or consumption
• CPC Class Codes: H04W 28/0252 : per individual bearer or channel dynamic wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/0268 : using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] negotiating SLA or negotiating QoS H04W28/24
• CPC Class Codes: H04W 28/16 : Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
• CPC Class Codes: H04W 36/0061 : of neighbour cell information
• CPC Class Codes: H04W 36/0066 : of control information between different types of networks in order to establish a new radio link in the target network
• CPC Class Codes: H04W 36/0083 : Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
• CPC Class Codes: H04W 36/0085 : Hand-off measurements
• CPC Class Codes: H04W 36/0088 : Scheduling hand-off measurements
• CPC Class Codes: H04W 36/22 : for handling the traffic
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 40/005 : Routing actions in the presence of nodes in sleep or doze mode
• CPC Class Codes: H04W 40/246 : Connectivity information discovery
• CPC Class Codes: H04W 48/14 : using user query or user detection
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 48/20 : Selecting an access point
• CPC Class Codes: H04W 52/0209 : in terminal devices terminal devices per se H04W88/02
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/0225 : using monitoring of external events, e.g. the presence of a signal
• CPC Class Codes: H04W 52/0235 : where the received signal is a power saving command
• CPC Class Codes: H04W 52/0258 : controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
• CPC Class Codes: H04W 52/0261 : managing power supply demand, e.g. depending on battery level
• CPC Class Codes: H04W 52/04 : TPC
• CPC Class Codes: H04W 52/14 : Separate analysis of uplink or downlink
• CPC Class Codes: H04W 72/02 : Selection of wireless resources by user or terminal
• CPC Class Codes: H04W 72/044 : based on the type of the allocated resource
• CPC Class Codes: H04W 72/0453 : Resources in frequency domain, e.g. a carrier in FDMA
• CPC Class Codes: H04W 72/20 : Control channels or signalling for resource management
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/30 : Resource management for broadcast services
• CPC Class Codes: H04W 72/52 : based on load
• CPC Class Codes: H04W 72/541 : using the level of interference
• CPC Class Codes: H04W 74/002 : Transmission of channel access control information
• CPC Class Codes: H04W 74/004 : in the uplink, i.e. towards network
• CPC Class Codes: H04W 76/12 : Setup of transport tunnels
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections
• CPC Class Codes: H04W 76/16 : Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
• CPC Class Codes: H04W 76/23 : Manipulation of direct-mode connections
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 76/30 : Connection release
• CPC Class Codes: H04W 8/08 : Mobility data transfer
• CPC Class Codes: H04W 80/10 : adapted for application session management, e.g. SIP [Session Initiation Protocol] connection management H04W76/00; arrangements for session management H04L67/14
• CPC Class Codes: H04W 84/042 : Public Land Mobile systems, e.g. cellular systems
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: H04W 88/12 : Access point controller devices
• CPC Class Codes: H04W 88/14 : Backbone network devices
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 88/18 : Service support devices; Network management devices
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Technology to provide P2P switching between HTTP based delivery of DASH formatted content to an MBMS download is disclosed. In an example, a host UE can include computer circuitry configured to: receive a session initiation protocol (SIP) termination message, from a service control function (SCF) module to terminate an SIP session for delivery of DASH based content to a mobile device; send a SIP acknowledgement message to the SCF to be forwarded to the mobile device; and establish a FLUTE protocol based MBMS download session between the mobile device and a BMSC.UPF module operating on the host mobile device for the MBMS download. Technology is also disclosed for P2P MBMS download via BMSC and file repair via an HTTP server using the switching.

Claims

1. A service control function (SCF) module operable to switch from a multimedia broadcast multicast services (MBMS) download to a hypertext transfer protocol (HTTP) based delivery of dynamic adaptive streaming over HTTP (DASH) formatted content, the SCF having one or more processors and memory configured to:

receive a session initiation protocol (SIP) re-invitation at a service control function (SCF) module from a mobile device while the mobile device is receiving an MBMS download in a content delivery session that includes DASH formatted content from a broadcast multicast service center user plane sub-function (BM-SC.UPF) module operating on a host wireless mobile user device;

send a SIP invitation from the SCF module to an HTTP/SIP adapter operating on the host wireless mobile user device to select an HTTP server operating on the host wireless mobile user device for an HTTP-based delivery to the mobile device;

receive a SIP acknowledgement at the SCF module from the HTTP/SIP adapter indicating a selection of the HTTP server on the host wireless mobile user device for the content delivery session; and

forward the SIP acknowledgement to the mobile device indicating a switch to the HTTP server for the content delivery session.

2. The one or more processors and memory of claim 1, wherein the SIP re-invitation is received from the mobile device at an internet protocol (IP) multimedia subsystem (IMS) core network (IM CN) subsystem, and the IP CN subsystem is configured to forward the SIP re-invitation to the SCF.

3. The one or more processors and memory of claim 2, wherein the one or more processors and memory are further configured to send the SIP acknowledgment to the IM CN subsystem to enable a quality of service (QOS) reservation, and the IM CN subsystem forwards the SIP acknowledgement to the mobile device indicating the switch to the HTTP server for the content delivery session.

4. The one or more processors and memory of claim 1, wherein a session description protocol (SDP) offer and a request-URI are included in the SIP re-invite message.

5. The one or more processors and memory of claim 1, wherein the one or more processors and memory are further configured to determine if MBMS to HTTP switching is supported at the mobile device.

6. The one or more processors and memory of claim 1, wherein the one or more processors and memory are further configured to tear down the MBMS content delivery session between a broadcast multicast service center user plane sub-function (BMSC.UPF) module operating at the host wireless mobile user device and the mobile device when MBMS to HTTP switching is available at the mobile device.

7. The one or more processors and memory of claim 1, wherein the SIP re-invitation includes a SIP Re-INVITE message, the SIP invitation includes a SIP INVITE message, and the SIP acknowledgement includes a SIP 200 OK.

8. A service control function (SCF) module operable to switch from a multimedia broadcast multicast services (MBMS) download to a hypertext transfer protocol (HTTP) based delivery of content for file repair, the SCF having one or more processors and memory configured to:

receive a session initiation protocol (SIP) re-invitation at a service control function (SCF) module from a mobile device while the mobile device is receiving an MBMS download in a content delivery session that includes DASH formatted content from a broadcast multicast service center user plane sub-function (BM-SC.UPF) module operating on a host wireless mobile user device;

determine that the SIP re-invitation is for a file repair procedure;

send a SIP invitation from the SCF module to an HTTP/SIP adapter used for the file repair procedure, wherein the HTTP/SIP adapter is configured to operate on the host wireless mobile user device;

receive a SIP acknowledgement at the SCF module from the HTTP/SIP adapter indicating a selection of an HTTP server on the host wireless mobile user device for content delivery of a requested file repair content; and

forward the SIP acknowledgement to the mobile device indicating a switch to the HTTP server for the content delivery of the requested file repair content.

9. The one or more processors and memory of claim 8, wherein the SIP re-invitation is received from the mobile device at an internet protocol (IP) multimedia subsystem (IMS) core network (IM CN) subsystem, and the IP CN subsystem is configured to forward the SIP re-invitation to the SCF.

10. The one or more processors and memory of claim 8, wherein the SIP re-invitation includes:

a session description protocol (SDP) offer; and

a request-uniform resource identifier (URI), and the URI includes;

a content identifier; and

a repair server address URI.

11. The one or more processors and memory of claim 10, wherein the one or more processors and memory are further configured to check for user rights for content associated with the content identifier.

12. The one or more processors and memory of claim 10, wherein the SIP invitation includes a To header containing a same content identifier as in the SIP re-invitation.

13. The one or more processors and memory of claim 12, wherein the HTTP/SIP adapter is configured to:

examine the content identifier in the To header;

select the HTTP server according to the repair server address URI;

send an HTTP post message to the HTTP server that includes an internet protocol (IP)

address of the mobile device; and

determine whether to redirect the request URI to another HTTP/SIP adapter.

14. The one or more processors and memory of claim 13, wherein the HTTP server is configured to send the SIP acknowledgement to the HTTP/SIP adapter.

15. The one or more processors and memory of claim 8, wherein the SIP acknowledgement includes an SDP answer that describes an MBMS file repair session that includes a download URL of the requested file repair content.

16. The one or more processors and memory of claim 8, wherein the one or more processors and memory are further configured to determine if MBMS to HTTP switching is supported at the mobile device.

17. The one or more processors and memory of claim 8, wherein the one or more processors and memory are further configured to tear down the MBMS content delivery session between the broadcast multicast service center user plane sub-function (BMSC.UPF) module operating at the host wireless mobile user device and the mobile device when MBMS to HTTP switching is available at the mobile device.

18. The one or more processors and memory of claim 8, wherein the SIP re-invitation includes a SIP Re-INVITE message, the SIP invitation includes a SIP INVITE message, and the SIP acknowledgement includes a SIP 200 OK.