Mobile-terminated packet transmission

Abstract

Methods, apparatus circuitry, and storage media are described for mobile-terminated packet transmissions. In one embodiment, an apparatus of a control plane device configured to operate within an evolved packet network core identifies a first service flow event trigger associated with a first packet data unit (PDU) session and processes a path reselection for a first PDU session in response to the first service flow event trigger, wherein the path reselection determines a new gateway for the first PDU session resulting from the path reselection. Transmission of a change notification to an application server controller associated with the first PDU session is initiated in response to the path reselection. Transmission of a routing update to the new gateway in response to the path reselection is also initiated. In various embodiments, the trigger may be a mobility event, a load balancing event, or operations in association with an application server controller.

1 - 23 . (canceled) 
     
     
         24 . An apparatus, comprising:
 a memory; and   processing circuitry in communication with the memory, wherein the apparatus is comprised in a control plane device configured to operate within a packet network core connected to a user equipment (UE) via a radio access network, and wherein the processing circuitry is arranged to:
 configure a routing policy on one or more data gateways for a service flow of a service for the UE; and 
 perform a notification procedure towards one or more application functions via a Service interworking function in response to the configuration of the routing policy, wherein the notification procedure is based on a previous notification request from the one or more application functions via the Service interworking function requesting notification of changes. 
   
     
     
         25 . The apparatus of  claim 24 ,
 wherein the memory is configured to store an identifier associated with the service flow; and   wherein the previous notification request is related to a load balancing event.   
     
     
         26 . The apparatus of  claim 24 ,
 wherein the previous notification request is related to a user equipment mobility event.   
     
     
         27 . The apparatus of  claim 24 ,
 wherein the previous notification request is related to receipt of a path reselection request from an Application Server (AS) controller.   
     
     
         28 . The apparatus of  claim 24 ,
 wherein the processing circuitry is further arranged to:
 process a packet data unit (PDU) session establishment request from the UE; and 
 initiate establishment of a first PDU session using a first gateway in response to the PDU session establishment request prior to receipt of a first service flow event trigger. 
   
     
     
         29 . The apparatus of  claim 28 ,
 wherein the processing circuitry is further arranged to initiate establishment of a second PDU session for the UE.   
     
     
         30 . The apparatus of  claim 29 ,
 wherein the processing circuitry further manages internet protocol (IP) address assignments for the UE as part of path reselection.   
     
     
         31 . The apparatus of  claim 27 ,
 wherein the processing circuitry is further arranged to:
 process a change notification from the AS controller indicating reallocation of a first packet data unit (PDU) session from a first application server to a second application server. 
   
     
     
         32 . The apparatus of  claim 24 ,
 wherein the previous notification request is related to a gateway failure event.   
     
     
         33 . The apparatus of  claim 24 ,
 wherein the previous notification request is related to a quality of service latency trigger associated with a mission-critical latency threshold.   
     
     
         34 . The apparatus of  claim 24 , further comprising:
 an antenna; and   radio frequency (RF) circuitry coupling the processing circuitry to the antenna, wherein the processing circuitry is configured as part of baseband circuitry of the apparatus.   
     
     
         35 . A method, comprising:
 while a packet network core is connected to a user equipment (UE) via a radio access network:
 configuring a routing policy on one or more data gateways for a service flow of a service for the UE; and 
 performing a notification procedure towards one or more application functions via a Service interworking function in response to the configuration of the routing policy, wherein the notification procedure is based on a previous notification request from the one or more application functions via the Service interworking function requesting notification of changes. 
   
     
     
         36 . The method of  claim 35 , further comprising:
 storing an identifier associated with the service flow, wherein the previous notification request is related to a load balancing event.   
     
     
         37 . The method of  claim 35 ,
 wherein the previous notification request is related to a user equipment mobility event.   
     
     
         38 . The method of  claim 35 ,
 wherein the previous notification request is related to receipt of a path reselection request from an Application Server (AS) controller.   
     
     
         39 . The method of  claim 35 ,
 wherein the previous notification request is related to a gateway failure event.   
     
     
         40 . A non-transitory computer readable memory medium, comprising:
 program instructions configured to cause a control plane device operating within a packet network core connected to a user equipment (UE) via a radio access network to:
 configure a routing policy on one or more data gateways for a service flow of a service for the UE; and 
 perform a notification procedure towards one or more application functions via a Service interworking function in response to the configuration of the routing policy, wherein the notification procedure is based on a previous notification request from the one or more application functions via the Service interworking function requesting notification of changes. 
   
     
     
         41 . The non-transitory computer readable memory medium of  claim 40 ,
 wherein the previous notification request is related to a quality of service latency trigger associated with a mission-critical latency threshold.   
     
     
         42 . The non-transitory computer readable memory medium of  claim 40 ,
 wherein the previous notification request is related to a user equipment mobility event.   
     
     
         43 . The non-transitory computer readable memory medium of  claim 40 ,
 wherein the previous notification request is related to receipt of a path reselection request from an Application Server (AS) controller.