System and methods for session management
US-10462840-B2 · Oct 29, 2019 · US
US10820368B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10820368-B2 |
| Application number | US-201916571714-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 16, 2019 |
| Priority date | Jan 9, 2017 |
| Publication date | Oct 27, 2020 |
| Grant date | Oct 27, 2020 |
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 network architecture and methods of managing packet data unit (PDU) sessions in a network are provided. The methods include PDU session establishment procedures, PDU session modification procedures, PDU session state transfer procedures, PDU session release procedures, and user equipment (UE) handover procedures.
Opening claim text (preview).
We claim: 1. A method comprising: initiating, by a session management function (SMF), a release of a PDU session; if a user equipment (UE) associated with the PDU session is unreachable, notifying, by the SMF, an access and mobility management function (AM F) that the PDU session is released; and upon being notified, removing, by the AMF, a context associated with the PDU session, wherein a communication associated with a release of a resource is skipped, the resource being associated with the PDU session. 2. The method as claimed in claim 1 , wherein the AMF removes the context without the communication associated with the release of the resource. 3. The method as claimed in claim 1 , wherein skipping the communication associated with the release of the resource comprises that the AMF does not receive, from the SMF, N1 SM information including a PDU session release command. 4. The method as claimed in claim 3 , wherein skipping the communication associated with the release of the resource comprises that the AMF does not initiate, a service request procedure to transmit the N1 SM information to the UE which is in a CM-IDLE state. 5. The method as claimed in claim 3 , wherein skipping the communication associated with the release of the resource further comprises that the AMF does not receive an N2 SM resource release request from the SMF. 6. The method as claimed in claim 5 , wherein skipping the communication associated with the release of the resource further comprises that the AMF does not transmit the N2 SM resource release request and the N1 SM information to an access network (AN) node. 7. The method as claimed in claim 6 , wherein skipping the communication associated with the release of the resource further comprises that the AMF does not receive an acknowledgement of the N2 SM resource release request from the AN node. 8. The method as claimed in claim 7 , wherein skipping the communication associated with the release of the resource further comprises that the AMF does not forward the acknowledgement of the N2 SM resource release request to the SMF. 9. The method as claimed in claim 6 , wherein skipping the communication associated with the release of the resource further comprises that the AN node does not signal to the UE to release an AN resource associated with the PDU session. 10. The method as claimed in claim 1 , wherein the SMF initiates the release of the PDU session by deciding to release the PDU session based on at least one of a trigger from a data network (DN), a trigger from a unified data management (UDM) function, and a locally configured policy. 11. The method as claimed in claim 1 , wherein the SMF notifies the AMF that the PDU session is released by invoking an operation including information associated with the PDU session. 12. The method as claimed in claim 1 , wherein the context is associated with at least one event subscription by the SMF on the AMF. 13. The method as claimed in claim 1 , wherein the method further comprises: removing, by the SMF, a context associated with the PDU session, wherein the communication associated with the release of the resource is skipped. 14. A communication system comprising a session management function (SMF) and an access and mobility management function (AMF), wherein: the SMF is configured to: initiate a release of a PDU session; and if a user equipment (UE) associated with the PDU session is unreachable, notify the AMF that the PDU session is released; the AMF is configured to: upon being notified, remove a context associated with the PDU session, wherein a communication associated with a release of a resource is skipped, the resource being associated with the PDU session. 15. The communication system as claimed in claim 14 , wherein the AMF is configured to remove the context without the communication associated with the release of the resource associated with the PDU session. 16. The communication system as claimed in claim 14 , wherein the AMF is further configured to remove the context without waiting for receiving, from the SMF, N1 SM information including a PDU session release command if being notified from the SMF that the PDU session is released. 17. The communication system as claimed in claim 16 , wherein the AMF is further configured to remove the context without initiating a service request procedure to transmit the N1 SM information to the UE which is in a CM-IDLE state if being notified from the SMF that the PDU session is released. 18. The communication system as claimed in claim 16 , wherein the AMF is further configured to remove the context without waiting for receiving an N2 SM resource release request from the SMF if being notified from the SMF that the PDU session is released. 19. The communication system as claimed in claim 18 , wherein the AMF is further configured to remove the context without transmitting the N2 SM resource release request and the N1 SM information to an access network (AN) node if being notified from the SMF that the PDU session is released. 20. The communication system as claimed in claim 14 , wherein the SMF is configured to initiate the release of the PDU session by deciding to release the PDU session based on at least one of a trigger from a data network (DN), a trigger from a unified data management (UDM) function, and a locally configured policy. 21. The communication system as claimed in claim 14 , wherein the SMF is configured to notify the AMF that the PDU session is released by invoking an operation including information associated with the PDU session. 22. The communication system as claimed in claim 14 , wherein the context is associated with at least one event subscription by the SMF on the AMF. 23. The communication system as claimed in claim 14 , wherein the SMF is further configured to remove a context associated with the PDU session, wherein the communication associated with the release of the resource is skipped.
Policy-based network configuration management · CPC title
Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title
using virtualisation of network functions or resources, e.g. SDN or NFV entities · CPC title
between virtual entities, e.g. orchestrators, SDN or NFV entities · CPC title
Connection release · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.