Abstract: Aspects relating to data transmission are described herein. In an implementation, in a method for data transmission, a tunneling protocol header is appended to a payload to obtain an encapsulated data packet, and at least one field is modified in the tunneling protocol header to indicate at least one of an access network (108) and a core network (108) for transmitting the encapsulated data packet, and the access network (108) and the core network (110) belong to different communication networks (104). Further, based on the tunneling protocol header, the encapsulated data packet is delivered to a routing unit for transmission.
Claims:1. A method for data transmission, the method comprising:
appending a tunneling protocol header to a payload to obtain an encapsulated data packet;
modifying at least one field in the tunneling protocol header to indicate at least one of an access network (108) and a core network (110) for transmitting the encapsulated data packet, wherein the access network (108) and the core network (110) belong to different communication networks (104); and
delivering the encapsulated data packet to a routing unit (112) for transmission based on the tunneling protocol header.
2. The method as claimed in claim 1, wherein the delivering comprises:
selecting the routing unit (112) based on the tunneling protocol header; and
negotiating delivery of the encapsulated data packet with the selected routing unit (112).
3. The method as claimed in claim 1, wherein the tunneling protocol header is a generic routing encapsulation (GRE) header.
4. The method as claimed in claim 1, wherein the modifying comprises updating a delivery header of the tunneling protocol header to indicate an intercept unique identification address (UIA) of the routing unit (112).
5. A method of routing data, the method comprising:
intercepting an encapsulated data packet, the encapsulated data packet comprising a tunneling protocol header appended to a payload, the tunneling protocol header indicative of at least one of an access network (108) and a core network (110) for transmitting the encapsulated data packet, wherein the access network (108) and the core network (110) belong to different communication networks (104), and wherein the tunneling protocol header is used to determine a routing unit (112); and
transmitting, by the determined routing unit (112), the encapsulated data packet to a target terminal, based on the tunneling protocol header.
6. The method as claimed in claim 5, wherein the transmitting comprises determining the routing unit (112) based on the tunneling protocol header comprising a delivery header having an intercept unique identification address (UIA).
7. The method as claimed in claim 6, wherein the intercepting comprises determining an abstraction layer for intercepting the encapsulated data packet based on a protocol used for the intercept UIA.
8. A network terminal (102) comprising:
a processor (202);
a modification module (116), coupled to the processor (202), to,
append a tunneling protocol header to a payload to obtain an encapsulated data packet; and
modify at least one field in the tunneling protocol header to indicate at least one of an access network (108) and a core network (110) to transmit the encapsulated data packet, wherein the access network (108) and the core network (110) belong to different communication networks (104); and
a delivery module (212), coupled to the processor (202), to deliver the encapsulated data packet to a routing unit (112) for transmission based on the tunneling protocol header.
9. The network terminal (102) as claimed in claim 8, wherein the delivery module (212) is to:
select the routing unit (112) based on the tunneling protocol header; and
negotiate delivery of the encapsulated data packet with an access network controller (114) associated with the selected routing unit (112).
10. The network terminal (102) as claimed in claim 8, wherein the tunneling protocol header is a generic routing encapsulation (GRE) header.
11. The network terminal (102) as claimed in claim 8, wherein the delivery module (212) is to identify the routing unit (112) based on the tunneling protocol header comprising a delivery header indicating an intercept unique identification address (UIA) of the routing unit (112).
12. A routing unit (112) comprising:
a processor (302),
an interception module (118), coupled to the processor (302), to intercept an encapsulated data packet, the encapsulated data packet comprising a tunneling protocol header appended to a payload, the tunneling protocol header indicative of at least one of an access network (108) and a core network (110) for transmitting the encapsulated data packet, wherein the access network (108) and the core network (110) belong to different communication networks (104); and
a transmission module (212), coupled to the processor (302), to transmit the encapsulated data packet to a target terminal, based on the tunneling protocol header.
13. The routing unit (112) as claimed in claim 12, wherein the interception module (118) is to determine the routing unit (112) for transmitting the encapsulated data packet to the target terminal based on a delivery header having an intercept unique identification address (UIA).
14. The routing unit (112) as claimed in claim 13, wherein the transmission module (212) is to re-order the encapsulated data packet before delivery based on a sequence field in the tunneling protocol header.
15. A non-transitory computer-readable medium comprising instructions executable by a processing resource to:
append a tunneling protocol header to a payload to obtain an encapsulated data packet, the appending comprising modifying at least one field in the tunneling protocol header to indicate at least one of an access network (108) and a core network (110) for transmitting the encapsulated data packet, wherein the access network (108) and the core network (110) belong to different communication networks (104); and
deliver the encapsulated data packet to a routing unit (112) for transmission based on the tunneling protocol header.
, Description:As Attached
| Section | Controller | Decision Date |
|---|---|---|
| # | Name | Date |
|---|---|---|
| 1 | 201641005744-Correspondence to notify the Controller [12-11-2024(online)].pdf | 2024-11-12 |
| 1 | Power of Attorney [18-02-2016(online)].pdf | 2016-02-18 |
| 2 | 201641005744-Correspondence to notify the Controller [30-10-2024(online)].pdf | 2024-10-30 |
| 2 | Form 5 [18-02-2016(online)].pdf | 2016-02-18 |
| 3 | Form 3 [18-02-2016(online)].pdf | 2016-02-18 |
| 3 | 201641005744-US(14)-HearingNotice-(HearingDate-18-11-2024).pdf | 2024-10-30 |
| 4 | Drawing [18-02-2016(online)].pdf | 2016-02-18 |
| 4 | 201641005744-FER.pdf | 2021-10-17 |
| 5 | Description(Complete) [18-02-2016(online)].pdf | 2016-02-18 |
| 5 | 201641005744-CLAIMS [08-09-2021(online)].pdf | 2021-09-08 |
| 6 | abstract 201641005744.jpg | 2016-08-02 |
| 6 | 201641005744-COMPLETE SPECIFICATION [08-09-2021(online)].pdf | 2021-09-08 |
| 7 | Other Patent Document [03-08-2016(online)].pdf | 2016-08-03 |
| 7 | 201641005744-DRAWING [08-09-2021(online)].pdf | 2021-09-08 |
| 8 | 201641005744-Form 1-080816.pdf | 2016-08-18 |
| 8 | 201641005744-FER_SER_REPLY [08-09-2021(online)].pdf | 2021-09-08 |
| 9 | 201641005744-Correspondence-F1-080816.pdf | 2016-08-18 |
| 9 | 201641005744-OTHERS [08-09-2021(online)].pdf | 2021-09-08 |
| 10 | 201641005744-Information under section 8(2) [03-09-2021(online)].pdf | 2021-09-03 |
| 10 | REQUEST FOR CERTIFIED COPY [03-03-2017(online)].pdf | 2017-03-03 |
| 11 | 201641005744-FORM 3 [02-09-2021(online)].pdf | 2021-09-02 |
| 11 | Request For Certified Copy-Online.pdf_1.pdf | 2017-03-04 |
| 12 | 201641005744-FORM 18 [23-01-2020(online)].pdf | 2020-01-23 |
| 12 | Request For Certified Copy-Online.pdf | 2017-03-04 |
| 13 | 201641005744-FORM 3 [11-08-2017(online)].pdf | 2017-08-11 |
| 14 | 201641005744-FORM 18 [23-01-2020(online)].pdf | 2020-01-23 |
| 14 | Request For Certified Copy-Online.pdf | 2017-03-04 |
| 15 | 201641005744-FORM 3 [02-09-2021(online)].pdf | 2021-09-02 |
| 15 | Request For Certified Copy-Online.pdf_1.pdf | 2017-03-04 |
| 16 | 201641005744-Information under section 8(2) [03-09-2021(online)].pdf | 2021-09-03 |
| 16 | REQUEST FOR CERTIFIED COPY [03-03-2017(online)].pdf | 2017-03-03 |
| 17 | 201641005744-OTHERS [08-09-2021(online)].pdf | 2021-09-08 |
| 17 | 201641005744-Correspondence-F1-080816.pdf | 2016-08-18 |
| 18 | 201641005744-FER_SER_REPLY [08-09-2021(online)].pdf | 2021-09-08 |
| 18 | 201641005744-Form 1-080816.pdf | 2016-08-18 |
| 19 | Other Patent Document [03-08-2016(online)].pdf | 2016-08-03 |
| 19 | 201641005744-DRAWING [08-09-2021(online)].pdf | 2021-09-08 |
| 20 | abstract 201641005744.jpg | 2016-08-02 |
| 20 | 201641005744-COMPLETE SPECIFICATION [08-09-2021(online)].pdf | 2021-09-08 |
| 21 | Description(Complete) [18-02-2016(online)].pdf | 2016-02-18 |
| 21 | 201641005744-CLAIMS [08-09-2021(online)].pdf | 2021-09-08 |
| 22 | Drawing [18-02-2016(online)].pdf | 2016-02-18 |
| 22 | 201641005744-FER.pdf | 2021-10-17 |
| 23 | Form 3 [18-02-2016(online)].pdf | 2016-02-18 |
| 23 | 201641005744-US(14)-HearingNotice-(HearingDate-18-11-2024).pdf | 2024-10-30 |
| 24 | Form 5 [18-02-2016(online)].pdf | 2016-02-18 |
| 24 | 201641005744-Correspondence to notify the Controller [30-10-2024(online)].pdf | 2024-10-30 |
| 25 | 201641005744-Correspondence to notify the Controller [12-11-2024(online)].pdf | 2024-11-12 |
| 25 | Power of Attorney [18-02-2016(online)].pdf | 2016-02-18 |
| 1 | 2021-06-0912-40-04E_09-06-2021.pdf |