Method and apparatus for operating protocol layer of terminal in inactive mode in next-generation mobile communication system
US-12069573-B2 · Aug 20, 2024 · US
USRE47719E · US · E1
| Field | Value |
|---|---|
| Publication number | US-RE47719-E |
| Application number | US-201615208233-A |
| Country | US |
| Kind code | E1 |
| Filing date | Jul 12, 2016 |
| Priority date | Jan 10, 2001 |
| Publication date | Nov 5, 2019 |
| Grant date | Nov 5, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method of relocating the header compression context in a packet network which transmits packets having compressed headers. A connection is established between a mobile terminal and a first network entity and context information used with compression and decompression of the headers of the packets is stored at the mobile terminal and the first network entity. The context information updating is stopped in the mobile terminal and in the first network entity and after that, a snapshot of the compression and decompression context information is taken and stored in the first network entity. The connection between the first network entity and the mobile terminal is changed to a connection between the mobile terminal and a second network entity. The context information snapshot stored by the first network entity is transferred to the second network entity to be stored therein as the context information of the second network entity. The stored context information at the mobile terminal and the second network entity is then used for compression and decompression of the headers of the packets.
Opening claim text (preview).
The invention claimed is: 1. A method of relocating the header compression context in a packet network which transmits packets having compressed headers, said method comprising: establishing a connection between a mobile terminal and a first network entity including storing context information used with compression and decompression of the headers of the packets at the mobile terminal and the, first network entity; stopping the context information updating in the mobile terminal and in the first network entity; taking a snapshot of the compression and decompression context information in the first network entity including storing said context information snapshot in the first network entity; and changing the connection between the first network entity and the mobile terminal to a connection between the mobile terminal and a second network entity including transferring the context information snapshot stored by the first network entity to the second network entity which is stored by the second network entity as the context information of the second network entity and using the stored context information at the mobile terminal and the second network entity for compression and decompression of the headers of the packets. 2. A method in accordance with claim 1 wherein: said context information updating is stopped by disabling the mobile terminal and the first network entity decompressors from sending acknowledgements to the compressor of the opposite side. 3. A method in accordance with claim 1 wherein: said context information updating is stopped by stopping the mobile terminal to compress and transmit uplink data and stopping the first network entity to compress and transmit downlink data. 4. A method in accordance with claim 3 wherein: said taking a snapshot of the compression and decompression context information in the first network entity is delayed until said transmitted uplink data and downlink data has been received and decompressed. 5. A method in accordance with claim 1 wherein: said context information updating is stopped by discarding in the first network entity compression/decompression acknowledgements from the mobile terminal. 6. A method in accordance with claim 1 wherein: said context information updating is stopped by disabling in the first network entity to send compression/decompression acknowledgements to the mobile terminal. 7. A method in accordance with claim 5 wherein: sending a context update request from the first network entity to the second network entity, in response to a detection of a context update request sent by the mobile terminal in the first network entity; and sending the first packet from the second network entity to the mobile terminal as a packet containing said context update request. 8. A method in accordance with claim 5 wherein: sending a context update request from the first network entity to the second network entity, in response to a detection of out-of synchronism of the context information in the first network entity; and sending the first packet from the second network entity to the mobile terminal as a packet containing said context update request. 9. A method in accordance with claim 1 wherein: transferring the context information snapshot stored by the first network entity to the second network entity before changing the connection between the first network entity and the mobile terminal to a connection between the mobile terminal and a second network entity. 10. A method in accordance with claim 1 wherein: said method is used in accordance with Robust Header Compression (ROHC) implemented in a UMTS system. 11. A method in accordance with claim 10 wherein: performing said relocation overlapping with serving radio network subsystem (SRNS) relocation. 12. A packet network in which packets having compressed headers are transmitted between a mobile terminal and network entities, said network comprising: a connection is arranged to established between a mobile terminal and a first network entity; context information used with compression and decompression of the headers of the packets is arranged to be stored at the mobile terminal and the first network entity; the context information updating in the mobile terminal and in the first network entity is arranged to be stopped; a snapshot of the compression and decompression context information is arranged to be taken at and stored in the first network entity; the connection between the first network entity and the mobile terminal is arranged to be changed to a connection between the mobile terminal and a second network entity, whereby the context information snapshot stored by the first network entity is arranged to be transmitted to and stored in the second network entity as the context information of the second network entity; and the stored context information at the mobile terminal and the second network entity is arranged to be used for compression and decompression of the headers of the packets. 13. A packet network in accordance with claim 12 wherein: said context information updating is arranged to be stopped by disabling the mobile terminal and the first network entity decompressors from sending acknowledgements to the compressor of the opposite side. 14. A packet network in accordance with claim 12 wherein: said context information updating is arranged to be stopped by stopping the mobile terminal to compress and transmit uplink data and stopping the first network entity to compress and transmit downlink data. 15. A packet network in accordance with claim 14 wherein: said taking a snapshot of the compression and decompression context information in the first network entity is arranged to be delayed until said transmitted uplink data and downlink data has been received and decompressed. 16. A packet network in accordance with claim 12 wherein: said context information updating is arranged to be stopped by discarding in the first network entity compression/decompression acknowledgements from the mobile. 17. A packet network in accordance with claim 12 wherein: said context information updating is arranged to be stopped by disabling in the first network entity to send compression/decompression acknowledgements to the mobile terminal. 18. A packet network in accordance with claim 16 wherein: a context update request is arranged to be sent from the first network entity to the second network entity, in response to a detection of a context update request sent by the mobile terminal in the first network entity; the first packet is arranged to be sent from the second network entity to the mobile terminal as a packet containing said context update request. 19. A packet network in accordance with claim 16 wherein: a context update is arranged to be sent request from the first network entity to the second network entity, in response to a detection of out-of-synchronism of the context information in the first network entity; and the first packet is arranged to be sent from the second network entity to the mobile terminal as a packet containing said context update request. 20. A packet network in accordance with claim 12 wherein: the context information snapshot stored by the first network entity is arranged to be transferred to the second network entity before changing the connection between the first network entity and the mobile terminal to a connection between the mobile terminal and a second network entity. 21. A packet network in
with transfer of context information · CPC title
using assembly or disassembly of packets · CPC title
Conversion of a code where information is represented by a given sequence or number of digits to a code where the same {, similar or subset of} information is represented by a different sequence or number of digits · CPC title
Parsing or analysis of headers · CPC title
characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks] (wireless communication networks H04W {; arrangements for dividing the transmission path H04W40/00}) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.