Satellite telephony

• US 8,655,352 B2
• Filed: 03/08/2011
• Issued: 02/18/2014
• Est. Priority Date: 09/10/2003
• Status: Active Grant

• Current Assignee: Gilat Satellite Networks Limited
• Original Assignee: Gilat Satellite Networks Limited
• Inventors: Marinov, Izhar, Beniamini, Gil, Meiri, Tzvika
• Primary Examiner(s): FARAGALLA, MICHAEL A
• Application Number:
  US13/042,812
• Publication Number:
  US 20110158158A1
• Time in Patent Office: 1,078 Days
• Field of Search: 455/12.1, 375/240.01
• US Class Current: 455/427
• CPC Class Codes: H04B 7/18582 Arrangements for data linking, i.e. for data framing, for error recovery, for multiple access
• CPC Class Codes: H04H 40/90 specially adapted for satellite broadcast receiving
• CPC Class Codes: H04L 2012/6421 Medium of transmission, e.g. fibre, cable, radio, satellite
• CPC Class Codes: H04L 2012/644 Star
• CPC Class Codes: H04L 2012/6481 Speech, voice
• CPC Class Codes: H04L 2012/6483 Video, e.g. MPEG
• CPC Class Codes: H04M 7/1215 where a cable TV network is used as an access to the PSTN/ISDN
• CPC Class Codes: H04N 21/235 Processing of additional data, e.g. scrambling of additional data or processing content descriptors
• CPC Class Codes: H04N 21/23614 Multiplexing of additional data and video streams arrangements for simultaneous broadcast of plural pieces of information H04H20/28
• CPC Class Codes: H04N 21/434 Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream demultiplexing of data packets for data networks, e.g. RTP/UDP H04L65/00
• CPC Class Codes: H04N 21/4348 Demultiplexing of additional data and video streams
• CPC Class Codes: H04N 21/435 Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
• CPC Class Codes: H04N 21/6143 involving transmission via a satellite
• CPC Class Codes: H04N 21/8106 involving special audio data, e.g. different tracks for different languages

Abstract

Embodiments of the present invention relate generally to packetization techniques for satellite transmission of data, such as telephony data. Some embodiments use the MPEG2 standard in connection with the ETSI DVB data piping profile for arranging the data. Embodiments also relate to method for receiving, demultiplexing and managing incoming telephony data to support a variety of telephony applications including voice, facsimile, Internet and other data.

Claims

1. A method of receiving telephone information, comprising the steps of:

receiving a packet from a satellite at a receiver, said packet including a packet header and a payload;

determining whether said received packet contains telephone data by reviewing a payload unit start bit in the packet header and a telephone code contained in the payload of said packet;

based on a determination that the received packet contains telephone data, extracting a first frame of telephone data from said packet, wherein said packet does not contain data belonging to an Internet Protocol packet; and

forwarding said first frame of telephone data to a first telephone device communicatively connected to said receiver.

2. The method of claim 1, further comprising the steps of:

reviewing data contained in said packet to determine whether said packet contains telephone data intended for said receiver;

extracting a second frame of telephone data from said packet; and

forwarding said second frame of telephone data to a second telephone device communicatively connected to said receiver.

3. The method of claim 2, wherein said packet includes at least two VSAT identifiers.

4. The method of claim 2, wherein said packet includes a pointer to a location of said second frame, said location being within said packet.

5. The method of claim 1, further comprising the step of reviewing a frame counter contained within the payload of said packet to determine a number of frames of telephone data contained in said packet.

6. The method of claim 1, wherein said step of determining whether said received packet contains telephone data by reviewing the payload unit start bit in the packet header and the telephone code contained in the payload of said packet further comprises:

reviewing said packet header to determine whether said payload unit start bit is set;

if said payload unit start bit is set, reviewing a first byte of the payload of said packet to determine whether said first byte points to a location within said payload of said packet; and

determining that said packet contains telephone data if said first byte does not point to a location within the payload of said packet.

7. A satellite receiver system, comprising:

at least one processor; and

at least one non-transitory computer-readable medium storing executable program code that, when executed by said at least one processor, causes said at least one processor to perform the following steps;

receiving a packet from a satellite, said packet including a packet header and a payload;

determining whether said received packet contains telephone data by reviewing a payload unit start bit in the packet header and a telephone code contained in the payload of said packet;

based on a determination that the received packet contains telephone data, extracting a first frame of telephone data from said packet, wherein said packet does not contain data belonging to an Internet Protocol packet; and

forwarding said first frame of telephone data to a first telephone device communicatively connected to said satellite receiver system.

8. The satellite receiver system of claim 7, the at least one computer-readable medium storing additional executable program code that, when executed by said at least one processor, causes said at least one processor to perform the following additional steps:

reviewing data contained in said packet to determine whether said packet contains telephone data intended for said satellite receiver system;

extracting a second frame of telephone data from said packet; and

forwarding said second frame of telephone data to a second telephone device communicatively connected to said satellite receiver system.

9. The satellite receiver system of claim 8, wherein said packet includes at least two VSAT identifiers.

10. The satellite receiver system of claim 8, wherein said packet includes a pointer to a location of said second frame, said location being within said packet.

11. The satellite receiver system of claim 7, the at least one computer-readable medium storing additional executable program code that, when executed by said at least one processor, causes said at least one processor to perform the following additional step:

reviewing a frame counter contained within the payload of said packet to determine a number of frames of telephone data contained in said packet.

12. The satellite receiver system of claim 7, wherein said step of determining whether said received packet contains telephone data by reviewing the payload unit start bit in the packet header and the telephone code contained in the payload of said packet further comprises:

reviewing said packet header to determine whether said payload unit start bit is set;

if said payload unit start bit is set, reviewing a first byte of the payload of said packet to determine whether said first byte points to a location within said payload of said packet; and

determining that said packet contains telephone data if said first byte does not point to a location within the payload of said packet.

13. A method of receiving telephone information, comprising the steps of:

receiving a packet from a satellite at a receiver, said packet having a packet header and a payload;

determining whether said payload contains telephone data of relevance to said receiver by identifying a pointer value in said packet payload, and determining whether said pointer value points to a location within said payload;

based on a determination that said payload contains telephone data of relevance to said receiver, extracting a plurality of frames of telephone data from said payload; and

forwarding said frames of telephone data to at least one device communicatively connected to said receiver.

14. The method of claim 13, further comprising assigning a telephone data type to payload pointers that point to locations outside of the payload.

15. The method of claim 13, wherein the payload of said received packet contains at least three frames of compressed voice data.

16. The method of claim 14, wherein the payload of said received packet contains at least three VSAT IDs, each said VSAT ID identifying a device communicatively connected to said receiver.

17. The method of claim 14, wherein the payload of said received packet includes additional header information identifying a number of frames of compressed voice data contained in said payload.

18. The method of claim 13, further comprising:

extracting a packet identifier from the payload of said received packet; and

determining whether said extracted packet identifier corresponds to a predefined packet identifier associated with the presence of telephone data in the received packet.

19. A communication method comprising the steps of:

packing a plurality of frames of telephone data into a payload portion of a single MPEG2 packet according to a DVB data piping profile and using a payload unit start bit in a header of said MPEG2 packet to indicate that the data in said payload is telephone data, wherein a first byte in the payload portion of the MPEG2 packet is a pointer that points to a location outside of the payload portion; and

transmitting said MPEG2 packet to a receiver via an extraterrestrial satellite.

20. The method of claim 19, further comprising the step of determining a number of frames to pack in said MPEG2 packet based on an acceptable delay time.

21. The method of claim 19, further comprising the step of determining a number of frames to pack in said MPEG2 packet based on a size of said frames.

22. The method of claim 19, wherein said payload portion does not contain Internet Protocol data.