Systems, Methods, and Devices for Signaling for Power Saving
US-2021259044-A1 · Aug 19, 2021 · US
US12262425B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12262425-B2 |
| Application number | US-202217895576-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 25, 2022 |
| Priority date | Aug 26, 2021 |
| Publication date | Mar 25, 2025 |
| Grant date | Mar 25, 2025 |
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 for controlling an execution (signalling) of a non-3rd generation partnership project (3GPP) interworking function (N3IWF) is provided. The method includes splitting a signalling of a N3IWF into a control plane signalling and a user plane signalling, where the control plane signalling is handled by an N3IWF-C device and the user plane signalling is handled by an N3IWF-U device. Further, the method includes adding the E10 interface between the N3IWF-C device and the N3IWF-U device. Further, the method includes monitoring the E10 interface, whereas the E10 interface includes an E10AP. The N3IWF-C device and the N3IWF-U device enables a plurality of services between the N3IWF-C device and the N3IWF-U device. The plurality of services includes an interface management service, a bear management service, a trace management service, and a load management service.
Opening claim text (preview).
What is claimed is: 1. A method for controlling an execution of a non-3 rd generation partnership project (3GPP) interworking function (N3IWF), the method comprising: splitting a signalling of the N3IWF into a control plane signalling and a user plane signalling, wherein the control plane signalling is handled by a N3IWF control plane (N3IWF-C) and the user plane signalling is handled by a N3IWF user plane (N3IWF-U); adding an E10 interface between the N3IWF-C and the N3IWF-U; and monitoring the E10 interface, wherein the E10 interface comprises an E10 application protocol (E10AP). 2. The method of claim 1 , wherein the monitoring, by the N3IWF-C and the N3IWF-U, of the E10 interface comprises: enabling, by the N3IWF-C and the N3IWF-U, a plurality of services between the N3IWF-C and the N3IWF-U, wherein the plurality of services comprises at least one of an interface management service, a bear management service, a trace management service, or a load management service. 3. The method of claim 1 , wherein the E10AP runs on a stream control transmission protocol (SCTP) of a transport layer. 4. The method of claim 1 , wherein the E10AP comprises user equipment (UE) associated services and non-UE-associated services. 5. The method of claim 1 , wherein the E10 interface enables the N3IWF-U to handle Internet protocol security (IPSec) user plane traffic. 6. The method of claim 1 , wherein the N3IWF-C selects one of the N3IWF-U from a plurality of the N3IWF-U during a protocol data unit (PDU) session establishment based on a local selection mechanism. 7. The method of claim 1 , wherein the N3IWF-C is capable of moving UE context from one N3IWF-U to another N3IWF-U during failure scenarios. 8. The method of claim 2 , wherein the interface management service comprises at least one of a reset service, an error indication service, an N3IWF-U E10 setup service, an N3IWF-U E10 setup response, an N3IWF-U E10 setup failure, an N3IWF-C E10 setup service, an N3IWF-C E10 setup response, an N3IWF-C E10 setup failure, an N3IWF-U configuration update service, an N3IWF-U configuration update acknowledge, an N3IWF-U configuration update failure, an N3IWF-C configuration update service, an N3IWF-C configuration update acknowledge, an N3IWF-C configuration update failure, an N3IWF-C configuration service, an E10 release service, or an N3IWF-U status indication service. 9. The method of claim 2 , wherein the bear management service comprises at least one of a bearer context setup service, a bearer context release request for the N3IWF-C, a bearer context release request for the N3IWF-U, a bearer context modification for the N3IWF-U, a bearer context modification for the N3IWF-C, a bearer context inactivity notification service, or a data usage report service. 10. The method of claim 2 , wherein the trace management service comprises at least one of a trace start service or a deactivate trace service. 11. The method of claim 2 , wherein the load management service comprises at least one of a resource status reporting initiation service or a resource status reporting service. 12. A non-3 rd generation partnership project (3GPP) interworking function control plane (N3IWF-C) for controlling an execution of a N3IWF, the N3IWF-C comprising: a memory; at least one processor; and an interface controller, operably connected to the memory and the at least one processor, configured to: split a signalling of the N3IWF into a control plane signalling, wherein the control plane signalling is handled by the N3IWF-C, add an E10 interface between the N3IWF-C and a N3IWF-U, and monitor the E10 interface, wherein the E10 interface comprises an E10 application protocol (E10AP). 13. A non-3 rd generation partnership project (3GPP) interworking function user plane (N3IWF-U) for controlling an execution of a N3IWF, the N3IWF-U comprising: a memory; at least one processor; and an interface controller, operably connected to the memory and the at least one processor, configured to: split a signalling of the N3IWF into a user plane signalling, wherein the user plane signalling is handled by the N3IWF-U, add an E10 interface between an N3IWF-C and the N3IWF-U, and monitor the E10 interface, wherein the E10 interface comprises an E10 application protocol (E10AP). 14. The N3IWF-U of claim 13 , wherein the at least one processor is further configured to: enable, by the N3IWF-C and the N3IWF-U, a plurality of services between the N3IWF-C and the N3IWF-U, wherein the plurality of services comprises at least one of an interface management service, a bear management service, a trace management service, or a load management service. 15. The N3IWF-U of claim 13 , wherein the E10AP runs on a stream control transmission protocol (SCTP) of a transport layer. 16. The N3IWF-U of claim 13 , wherein the E10AP comprises user equipment (UE) associated services and non-UE-associated services. 17. The N3IWF-U of claim 13 , wherein the E10 interface enables the N3IWF-U device to handle Internet protocol security (IPSec) user plane traffic. 18. The N3IWF-U of claim 13 , wherein the N3IWF-C selects one of the N3IWF-U from a plurality of the N3IWF-U during a protocol data unit (PDU) session establishment based on a local selection mechanism. 19. The N3IWF-U of claim 13 , wherein the N3IWF-C is capable of moving UE context from one N3IWF-U to another N3IWF-U during failure scenarios.
Related publications grouped by family.
Answers are generated from the same data shown on this page.