Session Management for Aviation Systems

Abstract

The mobility management function receives a registration request message for the wireless device from the wireless device. The mobility management function determines an authentication and / or authorization (AA) for air services for the wireless device. The mobility management function receives a request for session establishment for air services from the wireless device. The mobility management function sends an indication of the AA for air services for the wireless device to a session management function (SMF) based on the request for session establishment.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 086,572, filed October 1, 2020, which is incorporated by reference in its entirety. Summary of the Invention [Means for solving the problem]

[0002] Exemplary embodiments of the present invention enable the implementation of enhanced features and functions in 4G / 5G systems. Embodiments of the technology disclosed herein may be used in the technical fields of 4G / 5G systems and network slicing for communication systems. More specifically, embodiments of the technology disclosed herein may relate to 5G core networks and 5G systems for network slicing in communication systems. Throughout this disclosure, UE, wireless device, terminal, and mobile device are used interchangeably. Throughout this disclosure, base station, (radio) access network ((R)AN), next generation radio access network (NG-RAN), new radio node B (gNB), next generation eNodeB (ng-eNB) are used interchangeably. Throughout this disclosure, base station, radio access network (RAN), and eNodeB are used interchangeably. The present invention provides, for example, the following: (Item 1) receiving, by a mobility management function, a registration request message for a wireless device from the wireless device, the registration request message including an aircraft identifier for the wireless device; determining, by the mobility management function, an authentication and / or authorization (AA) for air services of the wireless device by performing an AA procedure, the AA procedure comprising: transmitting, by the mobility management function, to an AA server, an AA request including the aircraft identifier; receiving, by the mobility management function, an AA response from the AA server, the AA response including a result of the AA procedure; receiving, by the mobility management function, from the wireless device, a request to establish a session associated with the airline services; and sending, by the mobility management function, an indication of the AA of the airline services of the wireless device to a session management entity based on the request to establish the session and the result of the AA procedure. (Item 2) 2. The method of claim 1, further comprising determining that the AA of the airline service is required based on subscription information of the wireless device indicating that the airline service is authorized for the wireless device. (Item 3) 3. The method of claim 2, wherein performing the AA procedure is based on determining that the AA of the air service is required. (Item 4) 4. The method of claim 2 or 3, further comprising: based on determining that the AA of the air service is required, sending to the wireless device a registration approval message indicating that the AA of the air service is pending. (Item 5) receiving, by a mobility management function, from a wireless device, a registration request message for the wireless device; determining, by the mobility management function, an authentication and / or authorization (AA) for air services of the wireless device by performing an AA procedure, the AA procedure comprising: sending an AA request to an AA server by the mobility management function; receiving, by the mobility management function, an AA response from the AA server, the AA response including a result of the AA procedure; receiving, by the mobility management function, from the wireless device, a request to establish a session associated with the airline services; and sending, by the mobility management function, an indication of the AA of the airline services of the wireless device to a session management entity based on the request to establish the session and the result of the AA procedure. (Item 6) 6. The method of claim 5, wherein the registration request message includes an aircraft identifier of the wireless device. (Item 7) 7. The method of claim 6, wherein the AA request includes the aircraft identifier of the wireless device. (Item 8) The method of any one of items 5 to 7, further comprising determining that the AA of the airline service is required based on subscription information of the wireless device indicating that the airline service is authorized for the wireless device. (Item 9) 9. The method of claim 8, wherein performing the AA procedure is based on determining that the AA of the air service is required. (Item 10) 10. The method of claim 8 or 9, further comprising: based on determining that the AA of the air service is required, sending to the wireless device a registration approval message indicating that the AA of the air service is pending. (Item 11) receiving, by a mobility management function, from a wireless device, a registration request message for the wireless device; determining, by the mobility management function, an authorization and / or approval (AA) for air services for the wireless device; receiving, by the mobility management function, from the wireless device, a request to establish a session associated with the airline services; and sending, by the mobility management function, an indication of the AA of the airline service of the wireless device to a session management entity based on the request to establish the session. (Item 12) 12. The method of claim 11, further comprising receiving from the session management entity an indication of whether to approve the request to establish the session. (Item 13) 13. The method of claim 12, further comprising: determining, by the mobility management function and based on the indication of whether to approve the request to establish the session, whether to approve or reject the request to establish the session. (Item 14) 14. The method according to claim 11, further comprising: determining, by the mobility management function, whether to approve or reject the request to establish the session. (Item 15) 15. The method of claim 14, further comprising sending to the wireless device a response to the request to establish the session indicating approval or denial of the request. (Item 16) Item 16. The method of item 15, wherein the response is a packet data unit session establishment response message. (Item 17) 17. The method according to claim 15 or 16, wherein based on determining to reject the request to establish the session, the response indicates a rejection of the request to establish the session. (Item 18) 20. The method of claim 17, wherein the response includes a cause value associated with the rejection. (Item 19) 20. The method of claim 18, wherein the cause value indicates a cancellation of one or more of the AAs of the air service. (Item 20) 20. The method of claim 19, wherein the cause value indicates a failure of the AA of the air service. (Item 21) 21. The method according to any one of claims 15 to 20, wherein the response is a packet data unit session establishment rejection message. (Item 22) 17. The method according to claim 15 or 16, wherein, based on determining to approve the request to establish the session, the response indicates approval of the request to establish the session. (Item 23) 23. The method of claim 22, wherein the response is a packet data unit session establishment acknowledgement message. (Item 24) 24. The method according to one of items 12 to 23, wherein the indication of whether to approve the request to establish the session is received from the session management entity in a create session management context response message. (Item 25) 25. The method of claim 24, wherein the create session management context response message includes a cause value indicating cancellation of the AA of the airline service. (Item 26) 26. The method of claim 25, wherein the cause value indicates a cancellation of the AA of the air service. (Item 27) 27. The method according to claim 25 or 26, wherein the cause value indicates a failure of the AA of the air service. (Item 28) A method according to any one of items 11 to 27, wherein the indication of the AA of the airline service is sent to the session management entity in a create session management context request message. (Item 29) A method according to any one of items 11 to 28, wherein the session is for communicating with a service supplier of the air service. (Item 30) 30. The method according to any one of items 11 to 29, wherein the session is for command and control (C2) communication of the air service. (Item 31) The C2 communication: Direct C2 communications, Network support C2 communications, and 31. The method of claim 30, including at least one of air service traffic management C2 communications. (Item 32) 32. The method according to one of claims 11 to 31, wherein the request to establish the session is a packet data unit session establishment request message. (Item 33) 33. The method according to any one of claims 11 to 32, wherein the request to establish the session includes a wireless device capability indicating an air service capability. (Item 34) 34. The method according to one of items 11 to 33, wherein the request to establish the session includes a wireless device identifier of the wireless device. (Item 35) 35. The method according to one of claims 11 to 34, wherein the request to establish the session includes a packet data unit (PDU) session identifier. (Item 36) 36. The method according to any one of claims 11 to 35, wherein the request to establish the session includes a data network name (DNN) associated with the airline service. (Item 37) 37. The method according to one of items 11 to 36, wherein the request to establish the session includes single network slice selection assistance information (S-NSSAI). (Item 38) Item 38. The method according to any one of items 11 to 37, wherein the request to establish the session includes an aircraft identifier. (Item 39) Item 39. The method according to any one of items 11 to 38, wherein determining the AA of the air service of the wireless device includes determining an AA status of the wireless device. (Item 40) 40. The method according to any one of claims 11 to 39, wherein determining the AA of the air service of the wireless device performs an AA procedure. (Item 41) Item 41. The method according to item 40, wherein the AA procedure includes transmitting an AA request to an AA server by the mobility management function. (Item 42) Item 42. The method of item 41, wherein the AA request includes an aircraft identifier for the wireless device. (Item 43) 43. The method of claim 41 or 42, wherein the AA request includes a Universal Public Subscription Identifier (GPSI) of the wireless device. (Item 44) 44. A method according to any one of items 40 to 43, wherein the AA procedure includes receiving, by the mobility management function, an AA response from the AA server. (Item 45) Item 45. The method of item 44, wherein the AA response indicates an AA status of the wireless device. (Item 46) 46. ​​The method of claim 44 or 45, wherein the AA response comprises the result of the AA procedure. (Item 47) 44. The method according to any one of items 40 to 43, wherein said performing said AA procedure is performed with an air service supplier. (Item 48) A method according to any one of items 40 to 47, wherein the indication of the AA of the airline services is sent to the session management entity based on the AA procedure indicating that the airline services of the wireless device are authenticated and / or authorized. (Item 49) The method according to any one of items 40 to 48, further comprising transmitting to the wireless device a configuration result indicating that the air services of the wireless device are authenticated and / or authorized based on the AA procedure. (Item 50) 50. A method according to any one of items 40 to 49, wherein the indication of the AA of the air service is transmitted to the session management entity based on performing the AA procedure. (Item 51) 51. The method according to one of items 40 to 50, wherein performing the AA procedure is based on a determination that the AA of the air service is required. (Item 52) 52. The method of claim 51, wherein determining that the AA of the airline service is required includes sending, by the mobility management function, a context request message for the wireless device to a subscription server. (Item 53) 53. The method of claim 52, wherein the context request message includes a wireless device capability indicating an air service capability. (Item 54) 54. The method of claim 52 or 53, wherein the context request message includes a Subscriber Permanent Identifier (SUPI) of the wireless device. (Item 55) A method according to any one of items 51 to 54, wherein determining that the AA of the airline service is required includes receiving a context response message of the wireless device from the subscription server. (Item 56) Item 56. The method of item 55, wherein the context response message includes subscription information for the wireless device. (Item 57) 57. The method of claim 56, wherein determining that the AA of the airline service is required is based on the subscription information including a parameter indicating that the airline service is authorized for the wireless device. (Item 58) The method of any one of items 51 to 57, further comprising, based on determining that the AA of the air service is required, sending to the wireless device a registration approval message indicating that the AA of the air service is pending. (Item 59) 59. The method of any one of items 11 to 58, further comprising sending to the wireless device a registration approval message indicating that an AA for the air service is pending. (Item 60) 60. A method according to any one of items 11 to 59, wherein the registration request message for the wireless device includes an aircraft identifier for the wireless device. (Item 61) The aircraft identifier: an aircraft identifier associated with a civil aviation authority; Unmanned Aerial Vehicle Identifier, and 61. The method of any one of claims 38, 42, and 60, including one or more of the unmanned aircraft identifiers. (Item 62) 62. The method according to any one of items 11 to 61, wherein the AA of the air service includes an authorization for the air service. (Item 63) 63. The method according to one of items 11 to 62, wherein the AA of the air service includes an authorization for the air service. (Item 64) The wireless device, aircraft, unmanned aircraft, unmanned aircraft, Aircraft controller, An unmanned aerial vehicle controller, and The method according to any one of items 11 to 63, including at least one of the crewless aircraft controllers. (Item 65) 65. The method according to any one of items 11 to 64, wherein the aerial service is an unmanned aerial service. (Item 66) 66. The method according to one of items 11 to 65, wherein the air service is a crewless air service. (Item 67) 67. The method according to one of items 11 to 66, wherein the mobility management function is a mobility management entity (MME). (Item 68) Item 67. The method according to one of items 11 to 66, wherein the mobility management function is an access and mobility management function (AMF). (Item 69) A mobility management function comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the mobility management function to implement a method according to any one of items 1 to 68. (Item 70) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of items 1 to 68. (Item 71) receiving, by a session management entity, an indication of authentication and / or authorization (AA) for air services of the wireless device from a mobility management function; determining, by the session management entity and based on the indication of the AA of the air service, whether to approve the request to establish the session. (Item 72) 72. The method of claim 71, further comprising receiving an indication from the mobility management function whether to approve the request to establish the session. (Item 73) 73. The method of claim 72, wherein the indication of whether to approve the request to establish the session is received from the session management entity in a create session management context response message. (Item 74) Item 74. The method of item 73, wherein the create session management context response message includes a cause value indicating cancellation of the AA of the airline service. (Item 75) Item 75. The method of item 74, wherein the cause value indicates a cancellation of the AA of the air service. (Item 76) 76. The method according to claim 74 or 75, wherein the cause value indicates a failure of the AA of the air service. (Item 77) A method according to any one of items 71 to 76, wherein the indication of the AA of the airline service is sent to the session management entity in a create session management context request message. (Item 78) A method according to any one of items 71 to 77, wherein the session is for communicating with a service supplier of the air service. (Item 79) A method according to any one of items 71 to 78, wherein the session is for command and control communication of the air service. (Item 80) The command and control communication: Direct command and control communications; Network support command and control communications; and 80. The method of claim 79, including at least one of air service traffic management command and control communications. (Item 81) 81. A method according to one of items 71 to 80, wherein the request to establish the session is a packet data unit session establishment request message. (Item 82) 82. The method according to any one of items 71 to 81, wherein the AA of the air service includes an authorization for the air service. (Item 83) 83. The method according to any one of items 71 to 82, wherein the AA of the air service includes an authorization for the air service. (Item 84) 84. The method according to any one of items 71 to 83, wherein the aerial service includes an unmanned aerial service. (Item 85) 85. The method according to any one of items 71 to 84, wherein the air service comprises a crewless air service. (Item 86) 86. A method according to one of items 71 to 85, wherein the session management entity is a serving gateway (S-GW). (Item 87) A method according to one of items 71 to 86, wherein the session management entity is a serving gateway controller (S-GW-C). (Item 88) The method according to any one of items 71 to 85, wherein the session management entity is a session management function (SMF). (Item 89) A session management entity comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the session management entity to perform a method according to any one of items 71 to 88. (Item 90) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 71-88. (Item 91) 1. A method comprising: sending, by a wireless device, a registration request message for the wireless device to a mobility management function; sending, by the wireless device, to the mobility management function, a request to establish a session associated with an airline service of the wireless device; and receiving, by the wireless device, a response to the request to establish the session, the response comprising: denial of said request; and indicating a cause value indicative of a revocation and / or failure of the air service certification and / or authorization (AA). (Item 92) Item 92. The method of item 91, wherein the response is a packet data unit session establishment response message. (Item 93) Item 94. The method according to any one of items 91 to 93, wherein the response is a packet data unit session establishment rejection message. (Item 94) The method according to one of items 91 to 93, wherein the cause value indicates a cancellation of one or more of the AAs of the air service. (Item 95) The method according to any one of items 91 to 94, wherein the cause value indicates a failure of the AA of the air service. (Item 96) A method according to any one of items 91 to 95, wherein the session is for communicating with a service supplier of the air service. (Item 97) A method according to any one of items 91 to 96, wherein the session is for command and control (C2) communication of the air service. (Item 98) The C2 communication: Direct C2 communications, Network support C2 communications, and Item 98. The method of item 97, including at least one of air service traffic management C2 communications. (Item 99) Item 99. A method according to one of items 91 to 98, wherein the request to establish the session is a packet data unit session establishment request message. (Item 100) 99. The method of claim 91, wherein the request to establish the session includes a wireless device capability indicating an air service capability. (Item 101) Item 91. A method according to any one of items 91 to 100, wherein the request to establish the session includes a wireless device identifier of the wireless device. (Item 102) 102. The method according to one of claims 91 to 101, wherein the request to establish the session includes a packet data unit (PDU) session identifier. (Item 103) 103. The method according to any one of items 91 to 102, wherein the request to establish the session includes a data network name (DNN) associated with the airline service. (Item 104) A method according to one of items 91 to 103, wherein the request to establish the session includes single network slice selection assistance information (S-NSSAI). (Item 105) A method according to one of items 91 to 104, wherein the request to establish the session includes an aircraft identifier. (Item 106) A method according to any one of items 91 to 105, wherein the registration request message for the wireless device includes an aircraft identifier for the wireless device. (Item 107) The aircraft identifier: an aircraft identifier associated with a civil aviation authority; Unmanned Aerial Vehicle Identifier, and 107. The method of claim 105 or 106, further comprising one or more of the no occupant identifiers. (Item 108) A wireless device comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to implement a method according to any one of items 71 to 107. (Item 109) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 71 to 107. (Item 110) 1. A system comprising: 1. A wireless device, comprising: one or more processors; and when executed by the one or more processors, the wireless device: causing a mobility management function to send a registration request message for the wireless device; and a memory storing instructions for causing the mobility management function to transmit a request to establish a session associated with an airline service; and The mobility management function, when executed by one or more processors, comprising: receiving the registration request message from the wireless device; causing the mobility management function to determine an authentication and / or authorization (AA) for air services for the wireless device; receiving, from the wireless device, the request to establish the session associated with the airline service; and and a memory storing instructions for causing a session management entity to transmit, based on the request to establish the session, an indication of the AA of the air service of the wireless device. The session management entity, when executed by one or more processors, comprising: receiving from the mobility management function the indication of the AA of the air service of the wireless device; and A system comprising: the session management entity; and a memory storing instructions for determining whether to approve the request to establish the session based on the indication of the AA of the airline service. (Item 111) receiving an indication by a session management entity that authentication and / or authorization (AA) for air services of the wireless device has been revoked and / or failed; by the session management entity to the wireless device; Terminating, releasing, and / or rejecting establishment of a session of said wireless device; and transmitting a message indicating that the AA of the air service of the wireless device has been canceled and / or failed. (Item 112) Item 112. The method of item 111, wherein the session of the wireless device is associated with the airline service of the wireless device. (Item 113) Item 113. The method according to item 111 or 112, wherein the message is a session release command message indicating the termination and / or release of the session. (Item 114) A method according to one of items 111 to 113, further comprising receiving, by the session management entity from the wireless device, a confirmation message indicating completion of the termination and / or the release. (Item 115) A method according to one of items 111 to 114, wherein the message indicates that the command and control (C2) of the AA of the air service of the wireless device has been cancelled and / or failed. (Item 116) A method according to one of items 111 to 115, wherein the indication of the AA of the air service is received from a mobility management function. (Item 117) A method according to one of items 111 to 116, wherein the indication of the AA of the air service is included in a session creation message. (Item 118) The session creation message: A Subscriber Permanent Identifier (SUPI) of said wireless device; A Permanent Equipment Identifier (PEI) of said wireless device; Data Network Name (DNN), an identifier of said mobility management function; A session identifier for said session; Session management container, An indication that the AA for the air service has been cancelled; and Item 118. The method of item 117, including at least one of an indication that the AA for the air service has failed. (Item 119) Item 119. The method of item 118, wherein the session management container includes a session establishment request message. (Item 120) A method according to one of items 111 to 116, wherein the indication of the AA of the air service is included in a session update message. (Item 121) The session update message: Session Management (SM) Context Identity, User equipment (UE) location information; An indication that the AA for the UAS has been revoked; and Item 121. The method of item 120, further comprising at least one of an indication that the AA for the UAS has failed. (Item 122) The method according to any one of items 111 to 121, further comprising receiving, by the mobility management function, a message from the wireless device requesting to establish the session for the airline service. (Item 123) Item 123. The method of item 122, wherein the message requesting to establish the session is a non-access stratum message requesting to establish the session. (Item 124) Item 124. The method of item 122 or 123, wherein the message requesting to establish the session is a packet data unit session establishment request message. (Item 125) A method according to one of items 122 to 124, wherein the message requesting to establish the session is a packet data network connection request message. (Item 126) Item 126. The method of item 125, wherein an attach request message includes the packet data network connection request message. (Item 127) The message requesting to establish the session comprises: a wireless device capability indication associated with said air service; a packet data name associated with said airline service; Civil Aviation Authority (CAA) Uncrewed Aircraft (UAV) Identifier; Civil Aviation Authority (CAA) Unmanned Aerial Vehicle (UAV) Identifiers; a session identity for the session for the air service; A Subscriber Permanent Identifier (SUPI) of said wireless device; A Permanent Equipment Identifier (PEI) of said wireless device; Data Network Name (DNN), and A method according to one of items 122 to 126, including at least one of single network slice selection assistance information. (Item 128) A method according to one of items 122 to 127, further comprising sending, by the mobility management function to the wireless device in response to the message requesting to establish the session, a message approving the establishment of the session for the airline service. (Item 129) A method according to any one of items 122 to 127, further comprising sending a message by the mobility management function to the wireless device in response to the message requesting to establish the session based on the indication that the AA of the airline service of the wireless device has been cancelled and / or failed, the message rejecting the establishment of the session for the airline service. (Item 130) Item 130. The method of item 129, wherein the message refusing establishment comprises a packet data network connection refusal message. (Item 131) The packet data network connection rejection message comprises: User authentication failed, the AA of the air service on the wireless device has been cancelled and / or failed; and Item 131. The method of item 130, including an indication that command and control of the AA of the air service of the wireless device has been cancelled and / or has failed. (Item 132) Item 132. The method according to item 130 or 131, wherein the message rejecting the establishment comprises a leave request message. (Item 133) The method according to any one of items 111 to 132, wherein the indication of the AA of the air service is received from an AA server associated with the air service. (Item 134) A method according to any one of items 111 to 133, wherein the indication of the AA of the air service is received from an unmanned / crewed air system traffic management (UTM) server associated with the air service. (Item 135) The method of any one of items 111 to 134, wherein the indication of the AA of the air service is received from an unmanned / crewed air system service supplier (USS) server associated with the air service. (Item 136) A method according to one of items 111 to 135, wherein the indication of the AA of the air service is included in an AA cancellation request message. (Item 137) Item 137. The method of item 136, wherein the AA revocation request message includes a cause value for the AA revocation request message. (Item 138) Item 138. The method of item 136 or 137, wherein the AA cancellation request message includes an indication that the AA of the air service of the wireless device has been canceled. (Item 139) The method of any one of items 136 to 138, wherein the AA cancellation request message includes an indication that the AA of the air service of the wireless device has failed. (Item 140) A method according to one of items 136 to 139, wherein the AA revocation request message indicates that the AA for command and control (C2) of the wireless device has been revoked. (Item 141) A method according to one of items 136 to 140, wherein the AA cancellation request message indicates that the AA for command and control (C2) of the wireless device has failed. (Item 142) The method according to any one of items 111 to 141, wherein the AA of the air service includes an authorization for the air service. (Item 143) The method according to any one of items 111 to 142, wherein the AA of the air service includes an authorization for the air service. (Item 144) The method according to any one of items 111 to 143, wherein the aerial service includes an unmanned aerial service. (Item 145) The method according to any one of items 111 to 144, wherein the air service comprises a crewless air service. (Item 146) A method according to one of items 111 to 145, wherein the session management entity is a serving gateway (S-GW). (Item 147) A method according to one of items 111 to 146, wherein the session management entity is a serving gateway controller (S-GW-C). (Item 148) The method according to one of items 111 to 145, wherein the session management entity is a session management function (SMF). (Item 149) A session management entity comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the session management entity to perform a method according to any one of items 111 to 148. (Item 150) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 111 to 148. (Item 151) by the wireless device from the session management entity; Terminating, releasing, and / or rejecting establishment of a session of said wireless device; The method includes receiving a message indicating that authentication and / or authorization (AA) for air services of the wireless device has been revoked and / or failed. (Item 152) Item 152. The method of item 151, wherein the session of the wireless device is associated with the airline service of the wireless device. (Item 153) Item 153. The method according to item 151 or 152, wherein the message is a session release command message indicating the termination and / or release of the session. (Item 154) A method according to one of items 151 to 153, wherein the message is a session modification command message indicating the termination and / or release of the session. (Item 155) A method according to one of items 151 to 154, further comprising sending, by the wireless device, a confirmation message to the session management entity indicating completion of the termination and / or the release. (Item 156) A method according to one of items 151 to 155, wherein the message indicates that the command and control (C2) of the AA of the air service of the wireless device has been cancelled and / or failed. (Item 157) Item 157. The method of item 156, further comprising determining, by the wireless device, not to request establishment of a second session associated with the C2 of the air service based on the indication that the C2 of the AA of the air service of the wireless device has been canceled and / or failed. (Item 158) The method of any one of items 156 and 157, wherein the message that the C2 of the AA of the air service of the wireless device has been cancelled and / or failed is based on a cause parameter indicating that the C2 of the AA of the air service of the wireless device has been cancelled and / or failed. (Item 159) The method of any one of items 151 to 158, further comprising determining, based on the indication that the AA of the airline service of the wireless device has been canceled and / or failed, not to request establishment of a third session associated with the airline service by the wireless device. (Item 160) A method according to any one of items 151 to 159, wherein the message indicating that the AA of the air service of the wireless device has been cancelled and / or failed is based on a cause parameter indicating that the AA of the air service of the wireless device has been cancelled and / or failed. (Item 161) The method of any one of items 151 to 160, further comprising updating, by the wireless device, an AA status of the air service based on the indication that the AA of the air service of the wireless device has been canceled and / or failed. (Item 162) The method according to any one of items 151 to 161, wherein the AA of the air service includes an authorization for the air service. (Item 163) The method according to any one of items 151 to 162, wherein the AA of the air service includes an authorization for the air service. (Item 164) The method according to any one of items 151 to 163, wherein the aerial service includes an unmanned aerial service. (Item 165) The method according to any one of items 151 to 164, wherein the air service comprises a crewless air service. (Item 166) The wireless device, aircraft, Unmanned aerial vehicles, and The method according to any one of items 151 to 165, including at least one of the crewless aircraft. (Item 167) The wireless device, Aircraft controller, An unmanned aerial vehicle controller, and The method of any one of items 151 to 166, including at least one of the crewless aircraft controllers. (Item 168) A wireless device comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to implement a method according to any one of items 151 to 167. (Item 169) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 151 to 167. (Item 170) 1. A session management entity, comprising: one or more processors; and when executed by the one or more processors, the session management entity having: receiving an indication that an air service certification and / or authorization (AA) for the wireless device has been revoked and / or failed; The wireless device, Terminating, releasing, and / or rejecting establishment of a session of said wireless device; and transmitting a message indicating that the AA of the air service of the wireless device has been canceled and / or failed. The wireless device, comprising: one or more processors; and a programmable logic unit (PLC) that, when executed by the one or more processors, causes the wireless device to: from the session management entity, terminating, releasing, and / or rejecting establishment of the session of the wireless device; and a wireless device configured to receive a message indicating that the AA of the air service of the wireless device has been canceled and / or failed. (Item 171) receiving, by a mobility management entity (MME) from a serving gateway (S-GW) and / or a serving gateway controller (S-GW-C), a message requesting release of bearers for a wireless device, the message including an indication that authentication and / or authorization (AA) for air services of the wireless device has been revoked and / or has failed; and sending, by the MME to the wireless device, a leave request message requesting leave of the wireless device based on the indication that the AA of the air service of the wireless device has been canceled and / or failed. (Item 172) Item 172. The method of item 171, wherein the message requesting the release of the bearer is a delete bearer request message. (Item 173) the message requesting the release of the bearer, A Linked Evolved Packet System (EPS) Bearer Identifier (LBI), and 173. The method of claim 171 or 172, including at least one of the one or more EPS bearer identities. (Item 174) the message requesting the release of the bearer, a cause parameter indicating that the AA of the air service of the wireless device has been cancelled and / or failed; a cause parameter indicating that command and control of the AA of the air service of the wireless device has been cancelled and / or failed; and The method according to one of items 171 to 173, comprising at least one of the cause parameters indicating a change in radio access technology (RAT) from 3rd Generation Partnership Project (3GPP®) to non-3GPP®. (Item 175) The method according to one of items 171 to 174, further comprising determining, by the MME, that the first message causes a release of a last packet data network connection of the wireless device based on the wireless device not supporting an attach without a packet data network connection. (Item 176) determining, by the MME, that the message does not result in the release of the last packet data network connection of the wireless device; The method of any one of items 171 to 175, further comprising: based on the determination, sending to the wireless device a deactivate bearer request message requesting deactivation of the bearer and including a cause parameter indicating that the AA of the air service of the wireless device has been cancelled and / or failed. (Item 177) determining, by the MME, that the wireless device and the MME support an attach without a packet data network connection; The method of any one of items 171 to 176, further comprising: based on the determination, sending to the wireless device a deactivate bearer request message requesting deactivation of the bearer and including a cause parameter indicating that the AA of the air service of the wireless device has been cancelled and / or failed. (Item 178) The method according to any one of items 171 to 177, further comprising receiving a leave request acknowledgement message from the radio. (Item 179) A mobility management entity (MME), comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the MME to perform a method according to any one of items 171 to 178. (Item 180) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 171-178. (Item 181) receiving, by a mobility management entity (MME) from a serving gateway (S-GW) and / or a serving gateway controller (S-GW-C), a message requesting release of bearers for a wireless device, the message including an indication that authentication and / or authorization (AA) for air services of the wireless device has been revoked and / or has failed; and sending, by the MME to the wireless device, a leave request message requesting leave of the wireless device based on the indication that the AA of the air service of the wireless device has been canceled and / or failed. (Item 182) Item 182. The method of item 181, wherein the message requesting the release of the bearer is a delete bearer request message. (Item 183) the message requesting the release of the bearer, A Linked Evolved Packet System (EPS) Bearer Identifier (LBI), and 3. The method of claim 181 or 182, including at least one of the one or more EPS bearer identities. (Item 184) the message requesting the release of the bearer, a cause parameter indicating that the AA of the air service of the wireless device has been cancelled and / or failed; a cause parameter indicating that command and control of the AA of the air service of the wireless device has been cancelled and / or failed; and The method according to one of items 181 to 183, comprising at least one of the cause parameters indicating a change in radio access technology (RAT) from 3rd Generation Partnership Project (3GPP®) to non-3GPP®. (Item 185) A method according to one of items 181 to 184, further comprising receiving a delete bearer request message from the MME by the wireless device, the delete bearer request message including a cause parameter requesting deletion of the bearer and indicating that the AA of the air service of the wireless device has been cancelled and / or failed. (Item 186) The method according to one of items 181 to 185, further comprising receiving a deactivation request message from the MME by the wireless device, the deactivation request message including a cause parameter requesting deactivation of the bearer and indicating that the AA of the air service of the wireless device has been cancelled and / or failed. (Item 187) The method according to any one of items 181 to 186, further comprising receiving a leave request acknowledgement message from the radio. (Item 188) A mobility management entity (MME), comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the MME to perform a method according to any of items 181 to 187. (Item 189) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in any of items 181 to 187. (Item 190) A mobility management entity (MME), comprising: one or more processors; and when executed by the one or more processors, the MME is provided with: receiving a message from a Serving Gateway (S-GW) and / or a Serving Gateway Controller (S-GW-C) requesting release of a bearer for a wireless device, the message including an indication that authentication and / or authorization (AA) for air services of the wireless device has been revoked and / or has failed; and a memory storing instructions to cause the wireless device to send a disassociation request message to request disassociation of the wireless device based on the indication that the AA of the air service of the wireless device has been canceled and / or failed. A system comprising: a wireless device, the wireless device including one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to receive a leave request message requesting leave of the wireless device. [Brief description of the drawings]

[0003] Some examples of various embodiments of the present invention are described herein with reference to the drawings.

[0004] [Figure 1] FIG. 1 is a diagram of an example 5G system architecture, in accordance with aspects of an embodiment of the present disclosure. [Diagram 2] FIG. 1 is a diagram of an example 5G system architecture, in accordance with aspects of an embodiment of the present disclosure. [Diagram 3] FIG. 1 is a system diagram of an exemplary wireless device and network node in a 5G system in accordance with an aspect of an embodiment of the present disclosure. [Figure 4] 1 is a system diagram of an exemplary wireless device in accordance with aspects of an embodiment of the present disclosure. [Figure 5A] 1 illustrates two registration management state models in a UE 100 and an AMF 155 according to an aspect of an embodiment of the present disclosure. [Figure 5B] 1 illustrates two registration management state models in a UE 100 and an AMF 155 according to an aspect of an embodiment of the present disclosure. [Figure 6A] 1 illustrates two connection management state models in a UE 100 and an AMF 155 according to an aspect of an embodiment of the present disclosure. [Figure 6B] 1 illustrates two connection management state models in a UE 100 and an AMF 155 according to an aspect of an embodiment of the present disclosure. [Figure 7] FIG. 1 is a diagram of classification and marking traffic according to an aspect of an embodiment of the present disclosure. [Figure 8] 1 is an exemplary call flow in accordance with aspects of an embodiment of the present disclosure; [Figure 9] 1 is an exemplary call flow in accordance with aspects of an embodiment of the present disclosure; [Figure 10] 1 is an exemplary call flow in accordance with aspects of an embodiment of the present disclosure; [Figure 11] 1 is an exemplary call flow in accordance with aspects of an embodiment of the present disclosure; [Figure 12] 1 is an exemplary call flow in accordance with aspects of an embodiment of the present disclosure; [Figure 13] 1 is an exemplary call flow in accordance with aspects of an embodiment of the present disclosure; [Figure 14] 1 illustrates an exemplary mobile communication network in accordance with an aspect of an embodiment of the present disclosure; [Figure 15] A service-based architecture for 5G networks is shown with respect to interactions between the control plane (CP) and the user plane (UP). [Figure 16] 1 illustrates an example architecture of a UAS, according to an embodiment of the present disclosure. [Figure 17] 1 illustrates an example scenario of how a UAV interacts with a base station with respect to interference according to an embodiment of the present disclosure. [Figure 18] 1 illustrates an example architecture of a UAS with respect to an interface according to an embodiment of the present disclosure. [Figure 19] 1 illustrates an example registration procedure for authentication and / or authorization (AA) for air services, according to an embodiment of the present disclosure. [Figure 20]1 illustrates an exemplary service-specific AA procedure, according to an embodiment of the present disclosure.1 illustrates an exemplary procedure for handling impending communication failure by a base station having a wireless device and a control server, according to an embodiment of the present disclosure. [Figure 21] 1 illustrates an example session processing procedure for a 5G network according to an embodiment of the present disclosure. [Figure 22] 1 illustrates an example session processing procedure for a 5G network according to an embodiment of the present disclosure. [Diagram 23] 1 illustrates an example session modification procedure for a 5G network according to an embodiment of the present disclosure. [Figure 24] 1 illustrates a 4G system including an access network and a 4G core network (eg, an Evolved Packet system) according to an embodiment of the present disclosure. [Diagram 25] 1 illustrates an example session processing procedure for a 4G network according to an embodiment of the present disclosure. [Figure 26] 1 illustrates an example session processing procedure for a 4G network according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] Throughout this disclosure, FNF, SNF, CHF, AMF, SMF, UPF, PCF, UDM, OAM, AF are exemplary network functions that may be implemented either as network elements on (dedicated) hardware and / or network nodes as shown in FIG. 4, or as software instances running on (dedicated) hardware and / or shared hardware, or as virtualized functions instantiated on a suitable platform.

[0006] The following acronyms are used throughout this disclosure: 3GPP(registered trademark) 3rd Generation Partnership Project 5G Fifth Generation Mobile Network 5GC 5G Core Network 5G-GUTI 5G Global Unique Temporary Identifier 5GS 5G System 5G-AN 5G Access Network 5QI 5G QoS Indicator ACK Acknowledgement AF Application Features A-GNSS Assisted GNSS AMBR Total Maximum Bitrate AMF Access and Mobility Management Functions AN Access Network ANDSP Access Network Discovery and Selection Policy APN Access Point Name ARP Allocation and Retention Priority BD Billing Domain BPS Barometric Pressure Sensor CCNF Common Control Network Functions CDR Billing Data Records CHF billing function CIoT Cellular IoT CN Core Network CP Control Plane C-V2X Cellular Vehicle-To-Everything DAB Digital Audio Broadcast DDN Downlink Data Notification DDoS Distributed Denial of Service DL Downlink DN Data Network DN-AAA Data Network Authentication, Authorization and Accounting DNN Data Network Name DRX Intermittent reception DTMB Digital Terrestrial Multimedia Broadcasting ECGI E-UTRAN Cell Global Identifier ECID Enhanced Cell Identity eNodeB Evolutionary Node B EPS Evolution Packet System E-UTRAN Evolved Universal Terrestrial Radio Access Network FDD Frequency Division Duplex FNF Fast Network Function FQDN Fully Qualified Domain Name F-TEID Fully qualified TEID GAD Geographic Area Description GMLC Gateway Mobile Location Center gNB Next Generation Node B gNB-CU-CP gNB Central Unit Control Plane GNSS Global Navigation Satellite System GPSI Universal Public Subscription Identifier GTP GPRS Tunneling Protocol GUTI Global Unique Temporary Identifier GW Gateway HGMLC HomeGMLC HPLMN Home Public Land Mobile Network HSS Home Subscriber Server HTC Holographic Type Communication HTTP Hypertext Transfer Protocol ID Identifier IMEI International Mobile Equipment Identity IMEI DB IMEI Database IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IP Internet Protocol IP-CAN IP Connectivity Access Network L2 Layer 2 (Data Link Layer) L3 Layer 3 (Network Layer) LAN Local Area Network LADN Local Area Data Network LCS Location Service LI Lawful Intercept LMC Location Management Component LMF Location Management Function LPP LTE Positioning Protocol LRF location search function MAC Media Access Control MEI Mobile Equipment Identifier MICO Mobile Initiated Connection Only MME Mobility Management Entity MO Mobile call MO-LR Mobile Departure Location Request MSIS DN Mobile Subscriber ISDN MT Mobile Terminal MT-LR Mobile Termination Location Request N3IWF Non-3GPP (registered trademark) Interworking Function NAI Network Access Identifier NAS non-access layer NAS-MM Non-Access Stratum Mobility Management NAS-SM Non-Access Layer Session Management NAT Network Address Translation NB-IoT Narrowband IoT NCGI NR Cell Global Identity NEF Network Exposure Function NF Network Function NGAP Next Generation Application Protocol ng-eNB Next generation eNB NG-RAN NR Radio Access Network NI-LR Network Guided Location Request NR new radio NRF Network Repository Function NRPPa New Radio Positioning Protocol A NSI Network Slice Instance NSSAI Network Slice Selection Support Information NSSF Network Slice Selection Function NWDAF network data analysis function OAM Operation, Administration and Maintenance OCS Online Billing System OFCS Offline Billing System OTDOA Observation Time Difference of Arrival PCC Policy and Charging Control PCF Policy Control Function PCRF Policy and charging rules function PDN Packet Data Network PDU Packet / Protocol Data Unit PEI Persistent Equipment Identifier PGW PDN Gateway PLMN Public Land Mobile Network PRACH Physical Random Access Channel PLMN Public Land Mobile Network ProSe Proximity Service PSA PDU Session Anchor RAN Radio Access Network QFI QoS Flow Identification Information QoS Quality of Service RM Registration Management RA Random Access RAN Radio Access Network RAT Radio Access Technology RRC Radio Resource Control RM Registration Management S1-AP S1 Application Protocol SBA Service-Based Architecture SEA Security Anchor Function SCM Security Context Management SEA Security Anchor Function SET SUPL enabled device SGW Serving Gateway SI System Information SIB System Information Block SLP SUPL Location Platform SM Session Management SMF Session Management Facility SMSF SMS function S-NSSAI Single Network Slice Selection Assistance Information SS Sync Signal SSC Session and Service Continuity SUCI Served User Correlation ID SUPI Subscriber Persistent Identifier SUPL Secure User Plane Location TA Tracking Area TAI Tracking Area Identification TBS Ground Beacon System TCP Transmission Control Protocol TEID Tunnel Endpoint Identifier TMSI Temporary Mobile Subscriber Identity TNAN Trusted Non-3GPP Access Network TNGF Trusted Non-3GPP Gateway TRP Sending and Receiving Point UAS Unmanned Aerial System, Unmanned Aerial System UAV unmanned aerial vehicle, unmanned aircraft UAVC UAV Controller UDM Unified Data Management UDP User Datagram Protocol UDR User Data Repository UE User Equipment UL Uplink UL CL Uplink Classifier UPF User Plane Function USS UAS Service Supplier UTM UAS Traffic Management UPF User Plane Function V2X Vehicle-To-Everything VPLMN Visited Public Land Mobile Network WLAN Wireless Local Area Network XML Extensible Markup Language

[0007] Exemplary Figures 1 and 2 illustrate a 5G system including an access network and a 5G core network. The exemplary 5G access network may include an access network that connects to a 5G core network. The access network may include an NG-RAN 105 and / or a non-3GPP AN 165. The exemplary 5G core network may connect to one or more 5G access networks 5G-AN and / or NG-RAN. The 5G core network may include functional elements or network functions as in exemplary Figures 1 and 2, and interfaces may be used for communication between functional elements and / or network elements.

[0008] In an embodiment, a network function may be a processing function within a network, which may have a functional behavior and / or interface. The network functions may be implemented as network elements on dedicated hardware and / or network nodes as illustrated in Figures 3 and 4, or as software instances running on dedicated and / or shared hardware, or as virtualized functions instantiated on a suitable platform.

[0009] In one example, the Access and Mobility Management Function (AMF) 155 may include the following functions (some of the functions of the AMF 155 may be supported in a single instance of the AMF 155): termination of the RAN 105 CP interface (N2), termination of the NAS (N1), NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF 155 events and interface to the LI system), providing transport for session management (SM) messages between the UE 100 and the SMF 160, a transparent proxy for routing SM messages, access authentication, access authorization, providing transport for SMS messages between the UE 100 and the SMSF, a Security Anchor Function (SEA), interacting with the AUSF 150 and the UE 100, receiving intermediate keys established as a result of the UE 100 authentication process, a Security Context Management (SCM) for receiving keys from the SEA for use in deriving access network specific keys, etc.

[0010] In one example, the AMF 155 may support non-3GPP® access networks through an N2 interface with the N3IWF 170, NAS signaling with the UE 100 on the N3IWF 170, authentication of UEs connected on the N3IWF 170, mobility management, authentication, and separate security context state for the UE 100 connected via a non-3GPP® access 165 or simultaneously connected via a 3GPP® access 105 and a non-3GPP® access 165, support for coordinated RM contexts valid for the 3GPP® access 105 and the non-3GPP® access 165, support for a CM management context for the UE 100 for connectivity over a non-3GPP® access, etc.

[0011] In an embodiment, an AMF 155 region may include one or more AMF 155 sets. An AMF 155 set may include several AMFs 155 that provide a given area and / or network slice. In an embodiment, multiple AMF 155 sets may be per AMF 155 region and / or network slice. The application identifier may be an identifier that may be mapped to a specific application traffic detection rule. The configured NSSAI may be an NSSAI that may be provisioned at the UE 100. For a DNN, the DN 115 access identifier (DNAI) may be an identifier of a user plane access to the DN 115. The initial registration may relate to a registration of the UE 100 in the RM deregistration 500, 520 state. The N2AP UE 100 association may be logical per UE 100 association between a 5G AN node and the AMF 155. The N2AP UE-TNLA binding may be a binding between an N2AP UE 100 association and a specific transport network layer, TNL, association for a given UE 100.

[0012] In one example, the Session Management Function (SMF) 160 may include one or more of the following functions (one or more of the SMF 160 functions may be supported in a single instance of the SMF 160): session management (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF 110 and the AN 105 nodes), UE 100 IP address allocation and management (including optional authentication), UP function selection and control, configuration of traffic manipulation in the UPF 110 to route traffic to the appropriate destination, termination of interface to policy control function, control section for policy enforcement and QoS, Lawful Intercept (SM Events and Interface to LI System), termination of SM portion of NAS message, downlink data notification, initiation of AN specific SM information, transmission over N2 to the (R)AN 105 via the AMF 155, determination of SSC mode for the session, roaming functionality, handling of local enforcement to apply QoS SLA (VPLMN), charging data collection and charging interface (VPLMN), Lawful Intercept (SM Events and Interface to LI System), in the VPLMN for the interface to the System), support for interaction with external DN115 for transport of signalling for PDU session authorization / authentication by external DN115, etc.

[0013] In one example, the User Plane Function (UPF) 110 may include one or more of the following functions (some of the UPF 110 functions may be supported in a single instance of UPF 110): anchor point for intra / inter-RAT mobility (when applicable), external PDU session point for interconnection to DN 115, packet routing and forwarding, packet inspection and user plane part of policy rule enforcement, lawful interception (UP collection), traffic usage reporting, uplink classifier supporting routing of traffic flows to the data network, branching point supporting multi-homed PDU sessions, QoS handling for the user plane, uplink traffic validation (SDF to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering, downlink data notification triggers, etc.

[0014] In one example, IP address management of the UE 100 may include allocation and release of an IP address of the UE 100 and / or updating of an assigned IP address. The UE 100 may set the requested PDU type during a PDU session establishment procedure based on its IP stack capabilities and / or configuration. In an embodiment, the SMF 160 may select a PDU type for the PDU session. In an embodiment, if the SMF 160 receives a request with a PDU type set to IP, the SMF 160 may select a PDU type IPv4 or IPv6 based on a DNN configuration and / or operator policy. In an embodiment, the SMF 160 may provide a cause value to the UE 100 to indicate whether other IP versions are supported on the DNN. In one example, if the SMF 160 receives a request for a PDU type IPv4 or IPv6 and the requested IP version is supported by the DNN, the SMF 160 may select the requested PDU type.

[0015] In an example embodiment, the 5GC element and the UE 100 may support the following mechanisms: During the PDU session establishment procedure, the SMF 160 may send an IP address to the UE 100 via SM NAS signaling. IPv4 address allocation and / or IPv4 parameter configuration via DHCPv4 may be used once the PDU session is established. If IPv6 is supported, IPv6 prefix allocation may be supported via IPv6 stateless autoconfiguration. In one example, the 5GC network element may support IPv6 parameter configuration via stateless DHCPv6.

[0016] 5GC may support allocation of static IPv4 addresses and / or static IPv6 prefixes based on subscription information in UDM140 and / or based on configuration on a per-subscriber, per-DNN basis.

[0017] The User Plane Function (UPF 110) may handle the user plane path of the PDU session. The UPF 110, which provides an interface to the data network, may support the function of a PDU session anchor.

[0018] In an embodiment, a Policy Control Function (PCF) 135 may support a unified policy framework for governing network behavior, provide policy rules to a control plane function for enforcement of the policy rules, implement a front end to access subscription information relevant to policy decisions in a User Data Repository (UDR), etc.

[0019] The Network Exposure Function (NEF) 125 may provide means for securely exposing services and capabilities offered by 3GPP network functions, for translating between information exchanged with the AF 145 and information exchanged with internal network functions, for receiving information from other network functions, etc.

[0020] In an embodiment, the network repository function NRF130 may support service discovery functionality, which may receive NF discovery requests from NF instances, provide NF instances with information about discovered NF instances, maintain information about available NF instances and their supported services, etc.

[0021] In one example, the NSSF 120 may select a set of network slice instances serving the UE 100 and may determine an allowed NSSAI. In one example, the NSSF 120 may determine a set of AMFs 155 used to serve the UE 100 and / or may determine a list of candidate AMFs 155(s) by querying the NRF 130 based on a configuration.

[0022] In one example, the data stored in the UDR may include at least user subscription data, including at least a subscription identifier, security credentials, access and mobility related subscription data, session related subscription data, policy data, and the like.

[0023] In one example, the AUSF 150 may support an authentication server function (AUSF 150).

[0024] In one example, an application function (AF) AF 145 may interact with a 3GPP® core network to provide services. In one example, based on an operator deployment, application functions may be trusted by the operator to interact directly with associated network functions. Application functions that are not authorized by the operator to directly access network functions may use an external exposure framework (e.g., via NEF 125) to interact with associated network functions.

[0025] In an embodiment, the control plane interface between the (R)AN 105 and the 5G Core may support the connection of multiple different types of ANs (e.g., 3GPP® RAN 105, N3IWF 170 for untrusted access 165) to the 5GC via a control plane protocol. In an embodiment, the N2 AP protocol may be used for both 3GPP® access 105 and non-3GPP® access 165. In an embodiment, the control plane interface between the (R)AN 105 and the 5G Core may support separation between the AMF 155 and other functions such as the SMF 160 that may be required to control services supported by the AN (e.g., control of UP resources in the AN 105 for PDU sessions).

[0026] In an embodiment, the 5GC may provide policy information from the PCF 135 to the UE 100. In one example, the policy information may include an access network discovery and selection policy, a UE 100 route selection policy (URSP), an SSC mode selection policy (SSCMSP), a network slice selection policy (NSSP), a DNN selection policy, a non-seamless offload policy, and the like.

[0027] In one example, as illustrated in exemplary Figures 5A and 5B, registration management RM may be used to register or deregister a UE / user 100 with the network and establish a user context within the network. Connection management may be used to establish and release a signaling connection between the UE 100 and the AMF 155.

[0028] In an embodiment, the UE 100 may register with the network to receive services that require registration. In one example, the UE 100 may periodically update its registration with the network to remain reachable (periodic registration update), or upon mobility (e.g., mobility registration update), or to update its capabilities, or to renegotiate protocol parameters.

[0029] In an embodiment, the initial registration procedure illustrated in exemplary Figures 8 and 9 may involve the performance of network access control functions (e.g., user authentication and access authorization based on a subscription profile of UDM 140). Exemplary Figure 9 is a continuation of the initial registration procedure illustrated in Figure 8. As a result of the initial registration procedure, an identity of serving AMF 155 may be registered with UDM 140.

[0030] In an embodiment, the registration management (RM) procedures may be applicable over both 3GPP™ access 105 and non-3GPP™ access 165 .

[0031] Exemplary FIG. 5A may illustrate the RM states of the UE 100 as observed by the UE 100 and the AMF 155. In an exemplary embodiment, two RM states, RM-DELETED 500 and RM-REGISTERED 510, may be used by the UE 100 and the AMF 155 to reflect the registration state of the UE 100 in a selected PLMN. In an example, in the RM-DELETED state 500, the UE 100 may not be registered with the network. The UE 100 context in the AMF 155 may not hold valid location or routing information for the UE 100, so the UE 100 may not be reachable by the AMF 155. In an example, the UE 100 context may be stored in the UE 100 and the AMF 155. In an example, in the RM-REGISTERED state 510, the UE 100 may be registered with the network. In the RM-REGISTERED 510 state, the UE 100 may receive services that may require registration with the network.

[0032] In an exemplary embodiment, two RM states, RM DEREGISTRATION 520 and RM REGISTERED 530, may be used in the AMF 155 for the UE 100 and may reflect the registration state of the UE 100 in a selected PLMN.

[0033] As illustrated in the exemplary Figures 6A and 6B, connection management (CM) may include establishing and releasing a signaling connection between the UE 100 and the AMF 155 over an N1 interface. The signaling connection may be used to enable NAS signaling exchange between the UE 100 and the core network. The signaling connection between the UE 100 and the AMF 155 may include both an AN signaling connection between the UE 100 and the (R)AN 105 (e.g., an RRC connection over a 3GPP access) and an N2 connection for the UE 100 between the AN and the AMF 155. In one embodiment, the signaling connection may be an N1 signaling connection. In one embodiment, the signaling connection may be an N1 NAS signaling connection.

[0034] As illustrated in the exemplary FIG. 6A and FIG. 6B, two CM states may be used for the UE 100's NAS signaling connection with the AMF 155, CM Idle 600, 620, and CM Connected 610, 630. The UE 100 in the CM Idle 600 state may be in the RM Registered 510 state and may not have an established NAS signaling connection with the AMF 155 over N1. The UE 100 in the CM Idle 600 state may be in the RRC Idle state. The UE 100 may perform cell selection, cell reselection, PLMN selection, etc. The UE 100 in the CM Connected 610 state may have an NAS signaling connection with the AMF 155 over N1. In one embodiment, the UE 100 in the CM Connected 610 state may be in the RRC Connected state. The UE 100 in the CM Connected 610 state may be in the RRC Inactive state. In one example, the CM state of the AMF and the CM state of the UE may be different. This may be the case where a local state change occurs without an explicit signaling procedure between the UE and the AMF (e.g., a UE context release procedure). In one example, the RRC state of the UE (e.g., a wireless device) and the RRC state of the base station (e.g., a gNB, an eNB) may be different. This may be the case where a local state change occurs without an explicit signaling procedure between the UE and the base station (e.g., an RRC release procedure).

[0035] In an exemplary embodiment, two CM states may be used for a UE 100 in the AMF 155: CM idle 620 and CM connected 630.

[0036] In an embodiment, the RRC inactive state may apply to the NG-RAN (e.g., NR and E-UTRA connected to a 5G CN). The AMF 155 may provide assistance information to the NG RAN 105 based on a network configuration to assist the NG RAN 105 in determining whether the UE 100 may be sent to the RRC inactive state. When the UE 100 is CM connected 610 with an RRC inactive state, the UE 100 may resume the RRC connection due to pending uplink data, mobile initiated signaling procedures, in response to a RAN 105 paging to inform the network that it remains in the RAN 105 notification area.

[0037] In one example, NAS signaling connection management may include establishing and releasing a NAS signaling connection. A NAS signaling connection establishment function may be provided by the UE 100 and the AMF 155 to establish a NAS signaling connection for the UE 100 in the CM idle 600 state. The procedure to release the NAS signaling connection may be initiated by the 5G(R)AN 105 node or the AMF 155.

[0038] In an embodiment, the reachability management of the UE 100 may detect whether the UE 100 is reachable and provide the location (e.g., access node) of the UE 100 to the network to reach the UE 100. The reachability management may be performed by paging the UE 100 and location tracking of the UE 100. The location tracking of the UE 100 may include both registration area tracking of the UE 100 and reachability tracking of the UE 100. The UE 100 and the AMF 155 may negotiate the reachability characteristics of the UE 100 in the CM-IDLE 600, 620 state during registration and registration update procedures.

[0039] In one example, the following two UE 100 reachability categories may be negotiated between the UE 100 and the AMF 155 for CM idle 600, 620: State 1) UE 100 reachability allows data termination at the mobile device while the UE 100 is in CM idle 600; Mode 2) Mobile Initiated Connection Only (MICO) mode. 5GC may support a PDU connection service that provides for exchange of PDUs between the UE 100 and a data network identified by the DNN. The PDU connection service may be supported via a PDU session that is established upon request from the UE 100.

[0040] In an embodiment, the PDU session may support one or more PDU session types. The PDU session may be established (e.g., at the request of the UE 100), modified (e.g., at the request of the UE 100 and the 5GC), and / or released (e.g., at the request of the UE 100 and the 5GC) using NAS SM signaling exchanged over N1 between the UE 100 and the SMF 160. In response to a request from an application server, the 5GC may trigger a specific application in the UE 100. Upon receiving the trigger, the UE 100 may send it to the identified application in the UE 100. The identified application in the UE 100 may establish a PDU session for a specific DNN.

[0041] In an embodiment, the 5G QoS model may support a QoS flow-based framework as illustrated in the exemplary FIG. 7. The 5G QoS model may support both QoS flows that require a guaranteed flow bit rate and QoS flows that may not require a guaranteed flow bit rate. In an embodiment, the 5G QoS model may support reflective QoS. The QoS model may include flow mapping or packet marking in the UPF 110 (CN_UP) 110, the AN 105, and / or the UE 100. In one example, packets may arrive from and / or be directed to the application / service layer 730 of the UE 100, the UPF 110 (CN_UP) 110, and / or the AF 145.

[0042] In an embodiment, the QoS flow may be the granularity of QoS differentiation in a PDU session. A QoS flow ID, QFI, may be used to identify QoS flows in a 5G system. In an embodiment, user plane traffic with the same QFI in a PDU session may receive the same traffic forwarding treatment. The QFI may be carried in the encapsulation header on N3 and / or N9 (e.g., without any changes to the end-to-end packet header). In an embodiment, the QFI may be applied to PDUs with different types of payloads. The QFI may be unique within a PDU session.

[0043] In an embodiment, the QoS parameters of the QoS flow may be provided to the (R)AN 105 as a QoS profile at the PDU session establishment, at the QoS flow establishment, or whenever the user plane is activated, via N2 when NG-RAN is used. In an embodiment, a default QoS rule may be required per PDU session. The SMF 160 may assign a QFI for the QoS flow and may derive the QoS parameters from information provided by the PCF 135. In one example, the SMF 160 may provide the QFI to the (R)AN 105 along with a QoS profile that includes the QoS parameters of the QoS flow.

[0044] In an embodiment, a 5G QoS flow may be the granularity of QoS forwarding treatment in a 5G system. Traffic mapped to the same 5G QoS flow may receive the same forwarding treatment (e.g., scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). In one example, providing different QoS forwarding treatment may require separate 5G QoS flows.

[0045] In an embodiment, the 5G QoS indicator may be a scalar that may be used as a reference for a particular QoS forwarding behavior (e.g., packet loss rate, packet delay budget) provided to a 5G QoS flow. In an embodiment, the 5G QoS indicator may be implemented in the access network by a 5QI that references node-specific parameters (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configurations, etc.) that may control the QoS forwarding process.

[0046] In one embodiment, edge computing can provide computational and storage resources with adequate connectivity close to the devices that generate traffic.

[0047] In an embodiment, 5GC may support edge computing and may enable operator and third party services to be hosted close to the UE's access point of attachment. The 5G core network may select a UPF 110 close to the UE 100 and perform traffic steering from the UPF 110 to the local data network via the N6 interface. In an embodiment, the selection and traffic steering may be based on the UE 100's subscription data, the UE 100's location, information from the application function AF 145, policies, other relevant traffic rules, etc. In one example, the 5G core network may expose network information and capabilities to the edge computing application function. Functional support for edge computing may include local routing, where the 5G core network may select the UPF 110 to route user traffic to the local data network; traffic manipulation, where the 5G core network may select traffic and route it to an application in the local data network; enabling session and service continuity enabling UE 100 and application mobility; user plane selection and reselection, for example, based on input from an application function; network capability exposure, where the 5G core network and application functions may provide information to each other via the NEF 125; QoS and charging, where the PCF 135 may provide rules for QoS control and charging for traffic routed to the local data network; and support for local area data networks, where the 5G core network may provide support for connecting to a LADN in a particular area where an application is deployed.

[0048] An exemplary 5G system may be a 3GPP system, such as one that includes a 5G access network 105, a 5G core network, and a UE 100. The allowed NSSAI may be an NSSAI provided by a serving PLMN, for example, during a registration procedure, and indicates an NSSAI allowed by the network for the UE 100 in the serving PLMN for the current registration area.

[0049] In an embodiment, the PDU connection service may provide an exchange of PDUs between the UE 100 and a data network. A PDU session may be an association between the UE 100 and a data network (DN) 115, which may provide the PDU connection service. The type of association may be IP, Ethernet, and / or unstructured.

[0050] Establishing a user plane connection to a data network via a network slice instance may include performing an RM procedure to select an AMF155 that supports the required network slice, and establishing one or more PDU sessions to the required data network via the network slice instance.

[0051] In an embodiment, the set of network slices for the UE 100 may change at any time while the UE 100 is registered in the network and may be initialized by the network or the UE 100.

[0052] In an embodiment, the periodic registration update may be a re-registration of the UE 100 upon expiration of a periodic registration timer. The requested NSSAI may be an NSSAI that the UE 100 may provide to the network.

[0053] In an embodiment, a service-based interface may represent how a set of services may be provided / exposed by a given NF.

[0054] In an embodiment, service continuity may be an uninterrupted user experience of service, including cases where IP addresses and / or anchor points may change. In an embodiment, session continuity may refer to PDU session continuity. For IP type session continuity PDU sessions, it may imply that IP addresses are preserved for the life of the PDU session. Uplink classifier may be a UPF 110 function aimed at directing uplink traffic to the data network DN 115 based on filter rules provided by the SMF 160.

[0055] In an embodiment, the 5G system architecture may support data connectivity and services that allow deployment using technologies such as network function virtualization and / or software defined networking. The 5G system architecture may leverage service-based interactions between control plane (CP) network functions, if identified. Separation of user plane (UP) functions from control plane functions may be considered in the 5G system architecture. The 5G system may allow network functions to interact directly with other NFs, if desired.

[0056] In an embodiment, a 5G system may reduce dependencies between an access network (AN) and a core network (CN). The architecture may include an integrated access independent core network with a common AN-CN interface that may integrate different 3GPP and non-3GPP access types.

[0057] In an embodiment, the 5G system may support a unified authentication framework, stateless NFs where computational resources are separated from storage resources, performance exposure, and simultaneous access to local and centralized services. To support low latency services and access to local data networks, UP functions may be deployed close to the access network.

[0058] In an embodiment, the 5G system may support roaming with home routed traffic and / or local breakout traffic in visited PLMNs. The exemplary 5G architecture may be service-based, and interactions between network functions may be represented in two ways: (1) a service-based representation (illustrated in exemplary FIG. 1 ), where network functions in the control plane may enable other authorized network functions to access their services. This representation may also include point-to-point reference points, as appropriate. (2) a reference point representation, showing interactions between NF services in network functions described by a point-to-point reference point (e.g., N11) between any two network functions.

[0059] In an embodiment, a network slice may include core network control plane and user plane network functions, 5G radio access networks, NN3 IWF functions for non-3GPP access networks, etc. Network slices may vary in the implementation of supported functions and network functions. An operator may deploy multiple network slice instances delivering the same features for different UE groups, e.g., to provide different committed services and / or may be customer-specific. The NSSF 120 may store mapping information between slice instance IDs and NF IDs (or NF addresses).

[0060] In an embodiment, the UE 100 may be served by one or more network slice instances simultaneously via a 5G-AN. In an embodiment, the UE 100 may be served by k network slices at a time (e.g., k=8, 16, etc.). An AMF 155 instance logically serving the UE 100 may belong to the network slice instance serving the UE 100.

[0061] In an embodiment, a PDU session may belong to one specific network slice instance per PLMN. In an embodiment, different network slice instances may not share PDU sessions. Different slices may use the same DNN and have slice-specific PDU sessions.

[0062] The S-NSSAI (Single Network Slice Selection Assistance Information) may identify the network slice. The S-NSSAI may include a slice / service type (SST), which may indicate expected network slice behavior in terms of features and services, and / or a slice differentiator (SD). The slice differentiator may be optional information that may complement the slice / service type to allow further differentiation for selecting a network slice instance from potentially multiple network slice instances that match the indicated slice / service type. In an embodiment, the same network slice instance may be selected using different S-NSSAI. The CN part of the network slice instance serving the UE 100 may be selected by the CN.

[0063] In one example, the subscription data may include an S-NSSAI of a network slice to which the UE 100 subscribes. One or more S-NSSAIs may be marked as default S-NSSAIs. In an example, k S-NSSAIs may be marked as default S-NSSAIs (e.g., k=8, 16, etc.). In one example, the UE 100 may subscribe to more than eight S-NSSAIs.

[0064] In one example, the UE 100 may be configured by the HPLMN with a configured NSSAI for each PLMN. Upon successful completion of the UE registration procedure, the UE 100 may obtain from the AMF 155 an allowed NSSAI for this PLMN, which may include one or more S-NSSAIs.

[0065] In one example, the allowed NSSAI may take precedence over a configured NSSAI for a PLMN. The UE 100 may use the S-NSSAI in the allowed NSSAI corresponding to the network slice for procedures related to subsequent network slice selection in the serving PLMN.

[0066] In an embodiment, establishing a user plane connection to a data network via a network slice instance may include performing an RM procedure to select an AMF155 that can support the required network slice, establishing one or more PDU sessions to the required data network via the network slice instance, etc.

[0067] In an embodiment, when UE 100 registers to a PLMN, if UE 100 has a configured or permitted NSSAI for the PLMN, UE 100 may provide to the RRC and NAS layer network a requested NSSAI including an S-NSSAI corresponding to the slice for which UE 100 attempts to register, a temporary user ID if assigned to the UE, etc. The requested NSSAI may be a configured NSSAI, a permitted NSSAI, etc.

[0068] In an embodiment, when the UE 100 registers to a PLMN, the RAN 105 may route NAS signaling from / to the UE 100 to / from the default AMF 155 if the UE 100 does not have a configured or allowed NSSAI for the PLMN.

[0069] In an embodiment, based on local policy, subscription changes, and / or UE 100 mobility, the network may change the set of allowed network slices in which UE 100 is registered. In an embodiment, the network may implement the change during the registration procedure or trigger a notification to UE 100 of the change in supported network slices using an RM procedure (which may trigger the registration procedure). The network may provide UE 100 with a new allowed NSSAI and tracking area list.

[0070] In an embodiment, during the registration procedure of the PLMN, if the network determines that the UE 100 should be served by a different AMF 155 based on a network slicing aspect, the AMF 155 that initially received the registration request may redirect the registration request to another AMF 155 via the RAN 105 or via direct signaling between the initial AMF 155 and the target AMF 155.

[0071] In an embodiment, a network operator may provision a network slice selection policy (NSSP) to the UE 100. The NSSP may include one or more NSSP rules.

[0072] In one example, if the UE 100 has one or more PDU sessions established corresponding to a particular S-NSSAI, the UE 100 may route user data of the application to one of the PDU sessions unless other conditions of the UE 100 may prohibit the use of the PDU session. If the application provides a DNN, the UE 100 may consider the DNN to determine which PDU session to use. In an embodiment, if the UE 100 does not have an established PDU session with a particular S-NSSAI, the UE 100 may request a new PDU session corresponding to the S-NSSAI with a DNN that may be provided by the application. In one example, the RAN 105 may recognize the network slice used by the UE 100 in order for the RAN 105 to select appropriate resources to support network slicing within the RAN 105.

[0073] In an embodiment, the AMF 155 may select an SMF 160 in a network slice instance based on the S-NSSAI, the DNN, and / or other information, such as the subscription of the UE 100 and a local operator policy, when the UE 100 triggers the establishment of a PDU session. The selected SMF 160 may establish a PDU session based on the S-NSSAI and the DNN.

[0074] In one example, when UE100 is aware or configured that privacy considerations may apply to the NSSAI to support network-controlled privacy of slice information for slices that UE100 may have access to, UE100 may not include the NSSAI in NAS signaling unless UE100 has a NAS security context, and UE100 may not include the NSSAI in unprotected RRC signaling.

[0075] In one example, for a roaming scenario, network slice-specific network functions in the VPLMN and HPLMN may be selected based on the S-NSSAI provided by the UE 100 during PDU connection establishment. If a standardized S-NSSAI is used, the selection of a slice-specific NF instance may be made by each PLMN based on the provided S-NSSAI. In an embodiment, the VPLMN may map the S-NSSAI of the HPLMN to the S-NSSAI of the VPLMN based on a roaming agreement (e.g., including a mapping to a default S-NSSAI of the VPLMN). In an embodiment, the selection of a slice-specific NF instance in the VPLMN may be made based on the S-NSSAI of the VPLMN. In one example, the selection of any slice-specific NF instance in the HPLMN may be made based on the S-NSSAI of the HPLMN.

[0076] As illustrated in the examples of Figures 8 and 9, a registration procedure may be performed by the UE 100 to obtain authorization to receive services, enable mobility tracking, enable reachability, etc.

[0077] In one example, the UE 100 may send a message 805 (including AN parameters, RM-NAS registration request (registration type, SUCI or SUPI or 5G-GUTI, last visited TAI (if available), security parameters, requested NSSAI, mapping of requested NSSAI, 5GC capability of the UE 100, PDU session state, PDU session to be reactivated, follow-on request, MICO mode preference, etc.) to the (R)AN 105. In one example, in the case of NG-RAN, the AN parameters may include, for example, the SUCI or SUPI or 5G-GUTI, selected PLMN ID, and requested NSSAI, etc. In one example, the AN parameters may include an establishment cause. The establishment cause may provide a reason for requesting establishment of an RRC connection. In one example, the registration type may indicate whether the UE 100 wishes to perform an initial registration (e.g., the UE 100 is in an RM-DEREGISTERED state), a mobility registration update (e.g., the UE 100 is in an RM-REGISTERED state and initiates a registration procedure due to mobility), a periodic registration update (e.g., the UE 100 is in an RM-REGISTERED state and may initiate a registration procedure due to expiration of a periodic registration update timer), or an emergency registration (e.g., the UE 100 is in a limited service state). In one example, if the UE 100 performs an initial registration (e.g., the UE 100 is in an RM-DEREGISTERED state) to a PLMN for which the UE 100 does not yet have a 5G-GUTI, the UE 100 may include its SUCI or SUPI in the registration request. The SUCI may be included if the home network has prepared a public key to protect the SUPI in the UE. If the UE 100 receives a UE 100 configuration update command indicating that the UE 100 needs to re-register and the 5G-GUTI is invalid, the UE 100 may perform an initial registration and may include a SUPI in the registration request message. For emergency registration, a SUPI may be included if the UE 100 does not have a valid 5G-GUTI available, and a PET may be included when the UE 100 does not have a SUPI and does not have a valid 5G-GUTI. In other cases, a 5G-GUTI may be included and may indicate the last serving AMF 155.If the UE 100 is already registered via a non-3GPP® access in a PLMN different from the new PLMN of the 3GPP® access (e.g., not the registered PLMN or an equivalent PLMN of the registered PLMN), the UE 100 may not provide the 5G-GUTI allocated by the AMF 155 via the 3GPP® access during the registration procedure via the non-3GPP® access. If the UE 100 is already registered via a non-3GPP® access in a PLMN different from the new PLMN of the non-3GPP® access (e.g., not the registered PLMN or an equivalent PLMN of the registered PLMN), the UE 100 may not provide the 5G-GUTI allocated by the AMF 155 via the non-3GPP® access during the registration procedure via the non-3GPP® access. The UE 100 may provide the UE's usage settings based on its configuration. In case of initial registration or mobility registration update, the UE 100 may include a mapping of the requested NSSAI, which may be a mapping of each S-NSSAI of the requested NSSAI of the S-NSSAI of the configured NSSAI to the HPLMN to ensure that the network can verify whether the S-NSSAI in the requested NSSAI is allowed based on the registered S-NSSAI. If available, the last visited TAI may be included to help the AMF 155 generate a registration area for the UE. In an embodiment, security parameters may be used for authentication and integrity protection. The requested NSSAI may indicate network slice selection assistance information. The PDU session status may indicate a previously established PDU session in the UE. When the UE 100 is connected to two AMFs 155 belonging to different PLMNs via 3GPP® access and non-3GPP® access, then the PDU session status may indicate an established PDU session of the current PLMN in the UE. The PDU session to be reactivated may be included to indicate the PDU session for which UE 100 may intend to activate a UP connection.The PDU session corresponding to the LADN may not be included in the PDU session that is reactivated when the UE 100 is outside the available area of ​​the LADN. The follow-on request may be included when the UE 100 may have pending uplink signaling and the UE 100 may not have a PDU session that is reactivated, or when the registration type may indicate that the UE 100 may want to perform an emergency registration.

[0078] In one example, if the SUPI is included or the 5G-GUTI does not indicate a valid AMF 155, the (R)AT 105 may select an AMF 155 based on the (R)AT and the requested NSSAI, if available (808). If the UE 100 is in a CM-connected state, the (R)AN 105 may forward the registration request message to the AMF 155 based on the UE's N2 connection. If the (R)AN 105 may not select an appropriate AMF 155, the registration request may be forwarded to the AMF 155 configured in the (R)AN 105 to perform the AMF 155 selection 808.

[0079] In one example, the (R)AT 105 may send an N2 message 810 (including N2 parameters, RM-NAS registration request (registration type, SUPI or 5G-GUTI, last visited TAI (if available), security parameters, requested NSSAI, mapping of requested NSSAI, 5GC capability of UE 100, PDU session state, PDU session to be reactivated, follow-on request, and MICO mode preference), etc.) to the new AMF 155. In one example, when NG-RAN is used, the N2 parameters may include a selected PLMN ID, location information, cell identity, and RAT type associated with the cell on which the UE 100 is camped. In one example, when NG-RAN is used, the N2 parameters may include an establishment cause.

[0080] In one example, the new AMF 155 may send Namf_Communication_UEContextTransfer (complete registration request) 815 to the previous AMF 155. In one example, if the UE's 5G-GUTI is included in the registration request and the serving AMF 155 has changed since the last registration procedure, the new AMF 155 may invoke a Namf_Communication_UEContextTransfer service operation 815 to the previous AMF 155 including a complete registration request IE, which may be integrity protected, to request the UE's SUPI and MM context. The previous AMF 155 may use the integrity protected complete registration request IE to verify whether the context transfer service operation call corresponds to the requested UE 100. In an embodiment, the previous AMF 155 may forward event subscription information by each NF consumer for the UE to the new AMF 155. In one example, if the UE 100 identifies itself using a PEI, the SUPI request may be skipped.

[0081] In one example, the previous AMF 155 may send a response 815 to Namf_Communication_UEContextTransfer(SUPI, MM context, SMF 160 information, PCF ID) to the new AMF 155. In one example, the previous AMF 155 may respond to the new AMF 155 for the Namf_Communication_UEContextTransfer call by including the SUPI and MM context of the UE. In one example, if the previous AMF 155 holds information about an established PDU session, the previous AMF 155 may include SMF 160 information including the S-NSSAI, SMF 160 identification information, and PDU session ID. In one example, if the previous AMF 155 holds information about an active NGAP UE-TNLA binding belonging to an N3IWF, the previous AMF 155 may include information about the NGAP UE-TNLA binding.

[0082] In one example, if the SUPI is not provided by the UE 100 and is not obtained from a previous AMF 155, the identification request procedure 820 may be initiated by the AMF 155 sending an identity information request message to the UE 100 requesting the SUCI.

[0083] In one example, the UE 100 may respond with an identity response message 820 that includes the SUCI. The UE 100 may derive the SUCI using a provisioned public key of the HPLMN.

[0084] In one example, the AMF 155 may decide to initiate authentication 825 of the UE 100 by invoking the AUSF 150. The AMF 155 may select the AUSF 150 based on the SUPI or SUCI. In one example, if the AMF 155 is configured to support emergency registration for an unauthenticated SUPI and the UE 100 indicates a registration type emergency registration, the AMF 155 may skip the authentication and security setup, or the AMF 155 may accept that the authentication may fail and may continue with the registration procedure.

[0085] In one example, authentication 830 may be performed by a Nudm_UEAuthenticate_Get operation. AUSF 150 may discover UDM 140. If AMF 155 provided SUCI to AUSF 150, AUSF 150 may return SUPI to AMF 155 after authentication is successful. In an embodiment, if network slicing is used, AMF 155 may determine whether the registration request needs to be rerouted where initial AMF 155 points to AMF 155. In an embodiment, AMF 155 may initiate NAS security function. In an embodiment, upon completion of NAS security function setup, AMF 155 may initiate NGAP procedure to enable 5G-AN to use NGAP procedure for security procedure with UE. In an embodiment, 5G-AN may store security context and acknowledge to AMF 155. 5G-AN may use security context to protect messages exchanged with UE.

[0086] In one example, the new AMF 155 may send Namf_Communication_RegistrationCompleteNotify 835 to the previous AMF 155. If the AMF 155 has changed, the new AMF 155 may notify the previous AMF 155 that the registration of the UE 100 in the new AMF 155 may be completed by invoking a Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security procedure fails, the registration may be rejected and the new AMF 155 may invoke a Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code to the previous AMF 155. The previous AMF 155 may continue as if the UE 100 context transfer service operation was never received. If one or more of the S-NSSAIs used in the previous registration area may not be served in the target registration area, the new AMF 155 may determine which PDU sessions may be supported in the new registration area. The new AMF 155 may invoke a Namf_Communication_RegistrationCompleteNotify service operation to the previous AMF 155 including the rejected PDU session ID and the reason for the rejection (e.g., S-NSSAI is no longer available). The new AMF 155 may modify the PDU session state accordingly. The previous AMF 155 may notify the corresponding SMF 160 to locally release the UE's SM context by invoking the Nsmf_PDUSession_ReleaseSMContext service operation.

[0087] In one example, the new AMF 155 may send an identity request / response 840 (e.g., a PEI) to the UE 100. If the PEI is not provided by the UE 100 and is not obtained from the previous AMF 155, an identity request procedure may be initiated by the AMF 155 sending an identity request message to the UE 100 to obtain the PEI. The PEI may be transferred encrypted, except when the UE 100 performs an emergency registration and may not be authenticated. For emergency registration, the UE 100 may have included the PEI in the registration request.

[0088] In one example, the new AMF 155 may initiate the ME identity check 845 by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation 845.

[0089] In one example, the new AMF 155 may select a UDM 140 based on the SUPI (905). The UDM 140 may select a UDR instance. In one example, the AMF 155 may select a UDM 140.

[0090] In one example, if the AMF 155 has changed since the last registration procedure, or if the UE 100 provides a SUPI that may not reference a valid context of the AMF 155, or if the UE 100 registers with the same AMF 155 already registered in a non-3GPP® access (the UE 100 may be registered via a non-3GPP® access and initiate a registration procedure to add a 3GPP® access), the new AMF 155 may register with the UDM 140 using Nudm_UECM_Registration 910 and register to be notified when the UDM 140 may deregister the AMF 155. The UDM 140 may store the identification information of the AMF 155 associated with the access type and may not remove the identification information of the AMF 155 associated with other access types. The UDM 140 may store the information provided at the time of registration of the UDR by Nudr_UDM_Update. In one example, the AMF 155 may obtain the access and mobility subscription data and the SMF 160 selection subscription data using Nudm_SDM_Get 915. The UDM 140 may obtain this information from the UDR by Nudr_UDM_Query (access and mobility subscription data). After a successful response is received, the AMF 155 may register to be notified using Nudm_SDM_Subscribe 920 when the requested data may be modified. The UDM 140 may subscribe to the UDR by Nudr_UDM_Subscribe. The GPSI may be provided to the AMF 155 in the subscription data from the UDM 140 if the GPSI is available in the subscription data of the UE 100. In an embodiment, the new AMF 155 may provide the UDM 140 with the access type to serve for the UE 100, and the access type may be set to 3GPP access. The UDM 140 may store the associated access type in the UDR with the serving AMF 155 via Nudr_UDM_Update. The new AMF 155 may create an MM context for the UE 100 after obtaining the mobility subscription data from the UDM 140.In one example, when UDM 140 stores the associated access type with serving AMF 155, UDM 140 may initiate Nudm_UECM_DeregistrationNotification 921 to previous AMF 155 corresponding to 3GPP access. Previous AMF 155 may remove the MM context of the UE. If the reason for serving NF removal indicated by UDM 140 is initial registration, previous AMF 155 may invoke Namf_EventExposure_Notify service operation to all associated SMFs 160 of UE 100 to notify that UE 100 has been deregistered from previous AMF 155. SMF 160 may release the PDU session upon obtaining this notification. In one example, previous AMF 155 may unsubscribe with UDM 140 for subscription data using Nudm_SDM_unsubscribe 922.

[0091] In one example, when the AMF 155 decides to initiate PCF 135 communication, for example, the AMF 155 has not yet obtained an access and mobility policy for the UE 100 or the access and mobility policy of the AMF 155 is no longer valid, the AMF 155 may select a PCF 135 (925). If the new AMF 155 receives a PCF ID from the old AMF 155 and successfully contacts the PCF 135 identified by the PCF ID, the AMF 155 may select the (V-)PCF identified by the PCF ID. If the PCF 135 identified by the PCF ID is not used (e.g., there is no response from the PCF 135) or if there is no PCF ID received from the old AMF 155, the AMF 155 can select 925 the PCF 135.

[0092] In one example, the new AMF 155 may perform policy association establishment 930 during the registration procedure. When the new AMF 155 contacts the PCF 135 identified by the (V-)PCF ID received during the mobility of the AMF 155, the new AMF 155 may include the PCF-ID in the Npcf_AMPolicyControl Get operation. When the AMF 155 informs the PCF 135 of mobility constraints (e.g., location of the UE 100) for adjustment or when the PCF 135 updates the mobility constraints itself due to some condition (e.g., application in use, time and date), the PCF 135 may provide the updated mobility constraints to the AMF 155.

[0093] In one example, the PCF 135 may invoke the Namf_EventExposure_Subscribe service operation 935 for the UE 100 event subscription.

[0094] In one example, the AMF 155 may send Nsmf_PDUSession_UpdateSMContext 936 to the SMF 160. In one example, the AMF 155 may call Nsmf_PDUSession_UpdateSMContext if the PDU session to be reactivated is included in the registration request. The AMF 155 may send a Nsmf_PDUSession_UpdateSMContext request to the SMF 160 associated with the PDU session to activate the user plane connection of the PDU session. The SMF 160 may decide to trigger, for example, an insertion, removal, or change of an intermediate UPF 110 of the PSA. If the insertion, removal, or relocation of the intermediate UPF 110 is performed for a PDU session that is not included in the PDU session to be reactivated, the procedure may be performed without N11 and N2 interaction to update the N3 user plane between the (R)AN 105 and the 5GC. The AMF 155 may invoke the Nsmf_PDUSession_ReleaseSMContext service operation to the SMF 160 if any PDU session state indicates released at the UE 100. The AMF 155 may invoke the Nsmf_PDUSession_ReleaseSMContext service operation to the SMF 160 to release any network resources associated with the PDU session.

[0095] In one example, the new AMF 155 may send an N2 AMF 155 mobility request 940 to the N3IWF. If the AMF 155 has changed, the new AMF 155 may create an association of the NGAP UE 100 to the N3IWF to which the UE 100 is connected. In one example, the N3IWF may respond to the new AMF 155 with an N2 AMF 155 mobility response 940.

[0096] In one example, the new AMF 155 may send a registration accept 955 (including 5G-GUTI, registration area, mobility constraint, PDU session state, allowed NSSAI, [map of allowed NSSAI], periodic registration update timer, LADN information and steered MICO mode, IMS voice over PS session support indication, emergency service support indicator, etc.) to the UE 100. In one example, the AMF 155 may send a registration accept message to the UE 100 indicating that the registration request is accepted. The 5G-GUTI may be included if the AMF 155 assigns a new 5G-GUTI. If the AMF 155 assigns a new registration area, it may send the registration area to the UE 100 via the registration accept message 955. If the registration area is not included in the registration accept message, the UE 100 may consider the previous registration area valid. In an embodiment, the mobility constraint may be included if the mobility constraint may apply to the UE 100 and the registration type may not be emergency registration. The AMF 155 may indicate the established PDU sessions to the UE 100 in the PDU session state. The UE 100 may locally remove any internal resources related to the PDU sessions that are not marked as established in the received PDU session state. In an embodiment, when the UE 100 is connected to two AMFs 155 that belong to different PLMNs via 3GPP® access and non-3GPP® access, then the UE 100 may locally remove any internal resources related to the PDU sessions of the current PLMN that are not marked as established in the received PDU session state. If the PDU session state information was in the registration request, the AMF 155 may indicate the PDU session state to the UE. The mapping of the allowed NSSAIs may be a mapping of each S-NSSAI of the allowed NSSAI to the S-NSSAI of the configured NSSAI for the HPLMN. The AMF 155 may include in the registration accept message 955 the LADN information for the LADNs that are available in the registration area determined by the AMF 155 of the UE. If the UE 100 includes the MICO mode in the request, the AMF 155 may respond whether the MICO mode can be used.The AMF 155 may set the IMS voice-over PS session support indication. In an embodiment, to set the IMS voice-over PS session support indication, the AMF 155 may perform a UE / RAN radio information and compatibility request procedure to check the compatibility of the UE 100 and the RAN radio capabilities related to the IMS voice-over PS. In an embodiment, the emergency service support indicator may inform the UE 100 that emergency services are supported, e.g., the UE 100 may request a PDU session for the emergency service. In one example, the handover restriction list and the UE-AMBR may be provided by the AMF 155 to the NG-RAN.

[0097] In one example, the UE 100 may send a registration complete 960 message to the new AMF 155. In one example, the UE 100 may send a registration complete message 960 to the AMF 155 to acknowledge that a new 5G-GUTI may be assigned. In one example, if information about the PDU session to be reactivated is not included in the registration request, the AMF 155 may release the signaling connection with the UE 100. In an embodiment, when a follow-on request is included in the registration request, the AMF 155 may not release the signaling connection after the completion of the registration procedure. In one example, if the AMF 155 recognizes that some signaling is pending in the AMF 155 or between the UE 100 and the 5GC, the AMF 155 may not release the signaling connection after the completion of the registration procedure.

[0098] As illustrated in exemplary Figures 10 and 11, a service request procedure, e.g., a UE 100 triggered service request procedure, may be used by the UE 100 in CM idle state to request establishment of a secure connection to the AMF 155. Figure 11 is a continuation of Figure 10 illustrating the service request procedure. The service request procedure may be used to activate a user plane connection for established PDU sessions. The service request procedure may be triggered by the UE 100 or the 5GC and may be used when the UE 100 is in CM idle and / or CM connected, and may allow selective activation of a user plane connection for some of the established PDU sessions.

[0099] In one example, the UE 100 in the CM IDLE state may initiate a service request procedure to send an uplink signaling message, user data, etc., in response to a network paging request, etc. In one example, after receiving the service request message, the AMF 155 may perform authentication. In one example, after establishing a signaling connection to the AMF 155, the UE 100 or the network may send a signaling message, e.g., PDU session establishment, from the UE 100 to the SMF 160 via the AMF 155.

[0100] In one example, for any service request, the AMF 155 may respond with a service accept message to synchronize the PDU session state between the UE 100 and the network. If the service request may not be accepted by the network, the AMF 155 may respond with a service reject message to the UE 100. The service reject message may include an indication or trigger code that requests the UE 100 to perform a registration update procedure. In one example, for a service request due to user data, the network may take further action if the user plane connection activation may not be successful. In the exemplary FIG. 10 and FIG. 11, more than one UPF may be involved, for example, the old UPF 110-2 and the PDU session anchor PSA UPF 110-3.

[0101] In one example, the UE 100 may send a message to the (R)AN 105 including AN parameters, a mobility management (MM) NAS service request 1005 (e.g., a list of PDU sessions to be activated, a list of allowed PDU sessions, security parameters, PDU session state, etc.). In one example, the UE 100 may provide a list of PDU sessions to be activated when the UE 100 may reactivate a PDU session. The list of allowed PDU sessions may be provided by the UE 100 when the service request may be a response to paging or a NAS notification, and may identify PDU sessions that may be forwarded or associated to an access to which the service request may be sent. In one example, for NG-RAN, the AN parameters may include a selected PLMN ID and an establishment cause. The establishment cause may provide a reason for requesting establishment of an RRC connection. The UE 100 may send a NAS service request message to the RAN 105 for the AMF 155 encapsulated within an RRC message.

[0102] In one example, if the service request may be triggered for user data, the UE 100 may identify the PDU sessions for which the UP connection is to be activated in the NAS service request message using the list of activated PDU sessions. If the service request may be triggered for signaling, the UE 100 may not identify any PDU sessions. If the procedure may be triggered for a paging response and / or the UE 100 may have user data to be transferred at the same time, the UE 100 may identify the PDU sessions for which the UP connection is to be activated in the MM NAS service request message by the list of activated PDU sessions.

[0103] In one example, if a service request over a 3GPP® access may be triggered in response to paging indicating a non-3GPP® access, the NAS service request message may identify, in a list of allowed PDU sessions, a list of PDU sessions associated with the non-3GPP® access that may be reactivated over 3GPP®. In one example, the PDU session status may indicate PDU sessions available to the UE 100. In one example, the UE 100 may not trigger a service request procedure for a PDU session corresponding to an LADn when the UE 100 may be outside the area of ​​availability of the LADn. The UE 100 may not identify such a PDU session in a list of PDU sessions to be activated if a service request may be triggered for other reasons.

[0104] In one example, the (R)AN 105 may send an N2 message 1010 (e.g., a service request) to the AMF 155, including N2 parameters, a MM NAS service request, and the like. The AMF 155 may reject the N2 message if it may not be able to process the service request. In one example, if NG-RAN may be used, the N2 parameters may include a 5G-GUTI, a selected PLMN ID, location information, a RAT type, an establishment cause, and the like. In one example, the 5G-GUTI may be obtained in an RRC procedure, and the (R)AN 105 may select the AMF 155 according to the 5G-GUTI. In one example, the location information and the RAT type may relate to a cell in which the UE 100 may camp. In one example, based on the PDU session status, the AMF 155 may initiate a PDU session release procedure in the network for a PDU session whose PDU session ID may be indicated as unavailable by the UE 100.

[0105] In one example, if the service request was not sent integrity protected or the integrity protection verification failed, the AMF 155 may initiate a NAS authentication / security procedure 1015.

[0106] In one embodiment, if the UE 100 triggers a service request to establish a signaling connection, upon successful establishment of the signaling connection, the UE 100 and the network may exchange NAS signaling.

[0107] In one example, the AMF 155 may send a PDU session update context request 1020, such as an Nsmf_PDUSession_UpdateSMContext request, to the SMF 160, including a PDU session ID, a cause, location information of the UE 100, an access type, etc.

[0108] In one example, the Nsmf_PDUSession_UpdateSMContext request may be invoked by the AMF 155 if the UE 100 may identify a PDU session to be activated in a NAS service request message. In one example, the Nsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160 and the PDU session identified by the UE 100 may correlate with other PDU session IDs than the one triggering the procedure. In one example, the Nsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160 and the current UE 100 location may be outside the area of ​​validity for the N2 information provided by the SMF 160 during the network-triggered service request procedure. The AMF 155 may not send the N2 information provided by the SMF 160 during the network-triggered service request procedure.

[0109] In one example, the AMF 155 may determine the PDU session to be activated and may send an Nsmf_PDUSession_UpdateSMContext request to the SMF 160 associated with the PDU session with a cause set to indicate establishment of user plane resources for the PDU session.

[0110] In one example, if the procedure may be triggered in response to paging indicating non-3GPP access and the list of allowed PDU sessions provided by the UE 100 may not include the PDU session for which the UE 100 was paged, the AMF 155 may inform the SMF 160 that the user plane for the PDU session may not be reactivated. The service request procedure may succeed without reactivating the user plane of any PDU session, and the AMF 155 may inform the UE 100.

[0111] In one example, if the PDU session ID corresponds to the LADn and the SMF 160 may determine based on the UE 100 location report from the AMF 155 that the UE 100 may be outside the area of ​​availability of the LADn, the SMF 160 may decide to maintain the PDU session (based on local policy) and may reject activation of the user plane connection for the PDU session and may inform the AMF 155. In one example, if the procedure may be triggered by a network-triggered service request, the SMF 160 may inform the UPF 110 that initiated the data notification to discard downlink data for the PDU session and / or not provide further data notification messages. The SMF 160 may respond to the AMF 155 with an appropriate rejection cause and the user plane activation for the PDU session may be stopped.

[0112] In one example, if the PDU session ID corresponds to an LADN and the SMF 160 may determine, based on the UE 100 location report from the AMF 155, that the UE 100 may be outside the area of ​​availability of the LADN, the SMF 160 may decide to release the PDU session (based on local policy). The SMF 160 may locally release the PDU session and may notify the AMF 155 that the PDU session may be released. The SMF 160 may respond with an appropriate rejection cause to the AMF 155, and user plane activation of the PDU session may be stopped.

[0113] In one embodiment, if UP activation of a PDU session may be granted by SMF 160, based on the location information received from AMF 155, SMF 160 may check the criteria for UPF 110 selection 1025 (e.g., slice separation requirements, slice coexistence requirements, dynamic load of UPF 110, relative static capacity of UPF 110 among UPFs supporting the same DNN, location of UPF 110 available to SMF 160, location information of UE 100, capabilities of UPF 110, and functionality required for a particular UE 100 session). In one example, the appropriate UPF 110 may be selected by matching the capabilities and features required by the UE 100, the DNN, the PDU session type (e.g., IPv4, IPv6, Ethernet type or unstructured type) and, if applicable, the static IP address / prefix, the SSC mode selected for the PDU session, the UE 100 subscription profile in the UDM 140, the DNAI included in the PCC rules, local operator policies, the S-NSSAI, the access technology used by the UE 100, the logical topology of the UPF 110, etc., to the current UPF. The UE 100 may decide to perform one or more of the following: continue to use the UPF 110 that was already connected to the (R)AN 105; if the UE 100 has moved out of the service area of ​​the UPF 110 that was already connected to the (R)AN 105, select a new intermediate UPF 110 (or add / remove an intermediate UPF 110) but maintain the UPF acting as a PDU session anchor; trigger re-establishment of the PDU session to perform reallocation / reallocation of the UPF 110 acting as a PDU session anchor, for example, if the UE 100 has moved out of the service area of ​​the anchor UPF 110 connected to the RAN 105.

[0114] In one example, the SMF 160 may send an N4 session establishment request 1030 to the UPF 110 (e.g., new intermediate UPF 110). In one example, if the SMF 160 may select a new UPF 110 to act as an intermediate UPF 110-2 for a PDU session, or if the SMF 160 may select to insert an intermediate UPF 110 for a PDU session that may not have an intermediate UPF 110-2, the N4 session establishment request 1030 message may be sent to the new UPF 110 to provide packet detection, data forwarding, enforcement, and reporting rules to be installed in the new intermediate UPF. PDU session anchor addressing information (over N9) for this PDU session may be provided to the intermediate UPF 110-2.

[0115] In one example, when a new UPF 110 is selected by the SMF 160 to replace the previous (intermediate) UPF 110-2, the SMF 160 may include a data forwarding indication. The data forwarding indication may indicate to the UPF 110 that a second tunnel endpoint may be reserved for buffered DL data from the previous I-UPF.

[0116] In one example, the new UPF 110 (intermediate) may send an N4 session establishment response message 1030 to the SMF 160. If the UPF 110 may allocate CN tunnel information, the UPF 110 may provide the SMF 160 with DL CN tunnel information and UL CN tunnel information (e.g., CN N3 tunnel information) for the UPF 110 acting as a PDU session anchor. If a data forwarding indication may be received, the new (intermediate) UPF 110 acting as an N3 termination point may send DL CN tunnel information for the previous (intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer to release resources of the previous intermediate UPF 110-2.

[0117] In one example, if the SMF 160 may select a new intermediate UPF 110 for the PDU session or remove the previous I-UPF 110-2, the SMF 160 may send an N4 session modification request message 1035 to the PDU session anchor, PSA UPF 110-3, providing a data forwarding indication and DL tunnel information from the new intermediate UPF 110.

[0118] In one example, if a new intermediate UPF 110 may be added to the PDU session, the (PSA)UPF 110-3 may start sending DL data to the new I-UPF 110 as indicated in the DL tunnel information.

[0119] In one example, if a service request may be triggered by the network and the SMF 160 may remove the previous I-UPF 110-2 and not replace the previous I-UPF 110-2 with the new I-UPF 110, the SMF 160 may include a data forwarding indication in the request. The data forwarding indication may indicate to the (PSA) UPF 110-3 that a second tunnel endpoint may be reserved for buffered DL data from the previous I-UPF 110-2. In this case, the PSA UPF 110-3 may start buffering DL data that may be received simultaneously from the N6 interface.

[0120] In one example, the PSA UPF 110-3 (PSA) may send an N4 session modification response 1035 to the SMF 160. In one example, if a data forwarding indication may be received, the PSA UPF 110-3 may become the N3 termination point and send DL CN tunnel information for the previous (intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer to release resources of the previous intermediate UPF 110-2, if one exists.

[0121] In one example, the SMF 160 may send an N4 session modification request 1045 to the previous UPF 110-2 (e.g., may include the new UPF 110 address, the DL tunnel ID of the new UPF 110, etc.). In one example, if a service request may be triggered by the network and / or if the SMF 160 may remove the previous (intermediate) UPF 110-2, the SMF 160 may send an N4 session modification request message to the previous (intermediate) UPF 110-2 and may provide DL tunnel information for the buffered DL data. If the SMF 160 may allocate a new I-UPF 110, the DL tunnel information may be from the new (intermediate) UPF 110 and act as the N3 termination point. If the SMF 160 may not allocate a new I-UPF 110, the DL tunnel information may be from the new (intermediate) UPF 110 (PSA) 110-3 acting as the N3 termination point. The SMF 160 may start a timer to monitor the forwarding tunnel. In one example, the previous (intermediate) UPF 110-2 may send an N4 session modification response message to the SMF 160.

[0122] In one example, if the I-UPF 110-2 may be relocated and a forwarding tunnel may be established to the new I-UPF 110, the previous (intermediate) UPF 110-2 may forward its buffered data to the new (intermediate) UPF 110 acting as an N3 termination point. In one example, if the previous I-UPF 110-2 may be removed and the new I-UPF 110 may not be assigned to a PDU session and a forwarding tunnel may be established to UPF 110 (PSA) 110-3, the previous (intermediate) UPF 110-2 may forward its buffered data to UPF 110 (PSA) 110-3 acting as an N3 termination point.

[0123] In one example, the SMF 160 may send an N11 message 1060, e.g., Nsmf_PDUSession_UpdateSMContext response (N1 SM container (PDU Session ID, PDU Session Re-establishment Indication), N2 SM information (PDU Session ID, QoS Profile, CN N3 Tunnel Information, S-NSSAI), Cause) to the AMF 155 upon receipt of a Nsmf_PDUSession_UpdateSMContext request including a cause including, for example, establishment of user plane resources. The SMF 160 may determine whether UPF 110 relocation may be performed based on the UE 100 location information, the UPF 110 service area, and an operator policy. In one example, for a PDU session that the SMF 160 may determine to be served by the current UPF 110, e.g., the PDU session anchor or intermediate UPF, the SMF 160 may generate N2 SM information and send the Nsmf_PDUSession_UpdateSMContext response 1060 to the AMF 155 to establish the user plane. The N2 SM information may include information that the AMF 155 may provide to the RAN 105. In one example, for a PDU session that the SMF 160 may determine requires relocation of the UPF 110 for the PDU session anchor UPF, the SMF 160 may reject activation of the UP for the PDU session by sending an Nsmf_PDUSession_UpdateSMContext response, which may include an N1 SM container, to the UE 100 via the AMF 155. The N1 SM container may include a corresponding PDU session ID and a PDU session re-establishment indication.

[0124] Upon receipt of a Namf_EventExposure_Notify from AMF 155 to SMF 160, including an indication that UE 100 is reachable, if SMF 160 has pending DL data, SMF 160 may invoke a Namf_Communication_N1N2MessageTransfer service operation towards AMF 155 to establish a user plane for the PDU session. In one example, SMF 160 may resume sending DL data notifications to AMF 155 in the case of DL data.

[0125] In one example, SMF 160 may send a message to AMF 155 to reject the activation of the UP of the PDU session by including a cause in the Nsmf_PDUSession_UpdateSMContext response if the PDU session may correspond to an LADN and UE 100 may be outside the availability area of ​​the LADN, or if AMF 155 may inform SMF 160 that UE 100 may be reachable for a barred prioritized service and the PDU session to be activated may not be for a barred prioritized service, or if SMF 160 may decide to perform a PSA UPF 110-3 relocation for the requested PDU session.

[0126] In one example, the AMF 155 may send an N2 request message 1065 (e.g., N2 SM information received from the SMF 160, security context, AMF 155 signaling connection ID, handover restriction list, MM NAS service accept, list of recommended cell / TA / NG-RAN node identifiers) to the (R)AN 105. In one example, the RAN 105 may store the security context, the AMF 155 signaling connection ID, QoS information for QoS flows of the PDU session that may be activated, and the N3 tunnel ID in the RAN 105 context of the UE 100. In one example, the MM NAS service accept may include the PDU session state in the AMF 155. If the UP activation of the PDU session may be rejected by the SMF 160, the MM NAS service may include the PDU session ID and the reason why the user plane resources may not be activated (e.g., LADN is not available). The local PDU session release during the session request procedure may be indicated to the UE 100 via the session state.

[0127] In one example, if there are multiple PDU sessions that may involve multiple SMFs 160, the AMF 155 may not wait for responses from all SMFs 160 before it can send the N2 SM information to the UE 100. The AMF 155 may wait for all responses from the SMFs 160 before it can send the MM NAS service accept message to the UE 100.

[0128] In one example, the AMF 155 may include at least one N2 SM information from the SMF 160 if a procedure may be triggered for PDU session user plane activation. The AMF 155 may send additional N2 SM information from the SMF 160 in a separate N2 message (e.g., N2 tunnel setup request), if present. Alternatively, if multiple SMFs 160 may be involved, the AMF 155 may send one N2 request message to the (R)AN 105 after all Nsmf_PDUSession_UpdateSMContext response service operations from all SMFs 160 associated with the UE 100 may be received. In such a case, the N2 request message may include the N2 SM information received in each of the Nsmf_PDUSession_UpdateSMContext responses and a PDU session ID to enable the AMF 155 to associate the response with the relevant SMF 160.

[0129] In one example, if the RAN 105 (e.g., NG RAN) node may provide a list of preferred cell / TA / NG-RAN node identifiers during the AN release procedure, the AMF 155 may include information from the list in the N2 request. The RAN 105 may use this information to allocate a RAN 105 notification area when the RAN 105 may decide to enable an RRC inactive state for the UE 100.

[0130] During a PDU session establishment procedure in which the UE 100 may be using a PDU session related to a delay-sensitive service, the AMF 155 may receive an indication from the SMF 160 for any of the PDU sessions established for the UE 100, and if the AMF 155 receives an indication from the UE 100 that may support a CM connection in an RRC inactive state, the AMF 155 may include the RRC inactive support information of the UE. In one example, the AMF 155 based on the network configuration may include the RRC inactive support information of the UE.

[0131] In one example, the (R)AN 105 may send a message to the UE 100 to perform an RRC connection reconfiguration 1070 with the UE 100 depending on the QoS information for all QoS flows of the PDU session for which the UP connection may be activated, and the data radio bearers. In one example, user plane security may be established.

[0132] In one example, if the N2 request may include an MM NAS service accept message, the RAN 105 may forward the MM NAS service accept to the UE 100. The UE 100 may locally delete the context of the PDU session that may not be available in 5GC.

[0133] In one example, if N1 SM information is transmitted to UE 100 and may indicate that some PDU session(s) may be re-established, UE 100 may initiate PDU session re-establishment for the PDU session(s) that may be re-established after the service request procedure may be completed.

[0134] In one example, after user plane radio resources may be configured, uplink data from the UE 100 may be forwarded to the RAN 105. The RAN 105 (e.g., NG-RAN) may send the uplink data to the provided UPF 110 address and tunnel ID.

[0135] In one example, the (R)AN 105 may send an N2 Request Ack 1105 (e.g., N2 SM information (AN tunnel information, list of accepted QoS flows for the PDU session for which the UP connection is activated, list of rejected QoS flows for the PDU session for which the UP connection is activated)) to the AMF 155. In one example, the N2 Request message may include the N2 SM information, e.g., AN tunnel information. The RAN 105 may respond with the N2 SM information including a separate N2 message (e.g., N2 Tunnel Setup Response). In one example, if multiple N2 SM information is included in the N2 Request message, the N2 Request Ack may include multiple N2 SM information and information to enable the AMF 155 to associate the response with the relevant SMF 160.

[0136] In one example, the AMF 155 may send a Nsmf_PDUSession_UpdateSMContext request 1110 (N2 SM information (AN tunnel information), RAT type) to the SMF 160 for each PDU session. If the AMF 155 may receive N2 SM information(s) from the RAN 105, the AMF 155 may forward the N2 SM information to the associated SMF 160. If the time zone of the UE 100 may change compared to the last reported time zone of the UE 100, the AMF 155 may include the time zone of the UE 100 IE in the Nsmf_PDUSession_UpdateSMContext request message.

[0137] In one example, when a dynamic PCC is deployed, the SMF 160 may initiate a notification to the PCF 135 (if registered) about the new location information by invoking an event exposure notification operation (e.g., Nsmf_EventExposure_Notify service operation). The PCF 135 may provide the updated policy by invoking a policy control update notification message 1115 (e.g., Npcf_SMPolicyControl_UpdateNotify operation).

[0138] In one example, if the SMF 160 may select a new UPF 110 to act as an intermediate UPF 110 for the PDU session, the SMF 160 may initiate an N4 session modification procedure 1120 to the new I-UPF 110 and provide the AN tunnel information. Downlink data from the new I-UPF 110 may be forwarded to the RAN 105 and the UE 100. In one example, the UPF 110 may send an N4 session modification response 1120 to the SMF 160. In one example, the SMF 160 may send an Nsmf_PDUSession_UpdateSMContext response 1140 to the AMF 155.

[0139] In one example, if a forwarding tunnel may be established to the new I-UPF 110 and if the timer SMF 160 configured for the forwarding tunnel may expire, the SMF 160 may send an N4 session modification request 1145 to the new (intermediate) UPF 110 acting as the N3 termination point to release the forwarding tunnel. In one example, the new (intermediate) UPF 110 may send an N4 session modification response 1145 to the SMF 160. In one example, the SMF 160 may send an N4 session modification request 1150, or an N4 session release request, to the PSA UPF 110-3. In one example, if the SMF 160 may continue to use the previous UPF 110-2, the SMF 160 may send an N4 session modification request 1155, providing the AN tunnel information. In one example, if the SMF 160 may select a new UPF 110 to act as the intermediate UPF 110 and the previous UPF 110-2 may not be a PSA UPF 110-3, the SMF 160 may initiate resource release after timer expiration by sending an N4 session release request (release cause) to the previous intermediate UPF 110-2.

[0140] In one example, the previous (intermediate) UPF 110-2 may send an N4 Session Modify Response or N4 Session Release Response 1155 to the SMF 160. The previous UPF 110-2 may acknowledge with an N4 Session Modify Response or N4 Session Release Response message to confirm the modification or release of resources. The AMF 155 may invoke the Namf_EventExposure_Notify service operation to notify the mobility related event towards NFs that may have registered for the event after this procedure may be completed. In one example, AMF 155 may call Namf_EventExposure_Notify towards SMF 160 if SMF 160 has subscribed for UE 100 moving within or out of the coverage area and the UE's current location may indicate that the UE is moving within or out of the registered area of ​​interest, or if SMF 160 has registered an LADN DNN and UE 100 may be moving within or out of an area where the LADN is available, or UE 100 may be in MICO mode and AMF 155 has notified SMF 160 of UE 100 that it is unreachable, which SMF 160 may not have sent a DL data notification to AMF 155 and AMF 155 may inform SMF 160 that UE 100 is reachable, or if SMF 160 has registered the reachability state of UE 100, then AMF 155 may notify UE 100 of its reachability.

[0141] An exemplary PDU session establishment procedure illustrated in Figures 12 and 13. In an exemplary embodiment, when a PDU session establishment procedure may be employed, the UE 100 may send a NAS message 1205 (or a SM NAS message) to the AMF 155, including an NSSAI, an S-NSSAI (e.g., a requested S-NSSAI, an allowed S-NSSAI, a registered S-NSSAI, etc.), a DNN, a PDU session ID, a request type, a previous PDU session ID, an N1 SM container (PDU session establishment request), etc. In one example, the UE 100 may generate a new PDU session ID to establish a new PDU session. In one example, if emergency services may be required and an emergency PDU session may not yet be established, the UE 100 may initiate a UE 100 requested PDU session establishment procedure with a request type indicating an emergency request. In one example, the UE 100 may initiate the requested PDU session establishment procedure of the UE 100 by sending a NAS message including a PDU session establishment request in an N1 SM container. The PDU session establishment request may include a PDU type, an SSC mode, a protocol configuration option, etc. In one example, the request type may indicate an initial request if the PDU session establishment is a request to establish a new PDU session, or an existing PDU session if the request refers to an existing PDU session between a 3GPP® access and a non-3GPP® access or an existing PDN connection in the EPC. In one example, the request type may indicate an emergency request if the PDU session establishment may be a request to establish a PDU session for an emergency service. The request type may indicate an existing emergency PDU session if the request refers to an existing PDU session for an emergency service between a 3GPP® access and a non-3GPP® access. In one example, the NAS message sent by the UE 100 may be encapsulated by the AN in an N2 message toward the AMF 155, which may include user location information and access technology type information. In one example, the PDU session establishment request message may include an SM PDU DN request container containing information for PDU session authorization by an external DN.In one example, if the procedure may be triggered for SSC mode 3 operation, the UE 100 may include a previous PDU session ID in the NAS message that may indicate the PDU session ID of the ongoing PDU session to be released. The previous PDU session ID may be an optional parameter that may be included in this case. In one example, the AMF 155 may receive a NAS message (e.g., a NAS SM message) from the AN along with user location information (e.g., a cell ID in case of the RAN 105). In one example, the UE 100 may not trigger a PDU session establishment for a PDU session corresponding to an LADN when the UE 100 is outside the area of ​​availability of the LADN.

[0142] In one example, the AMF 155 may determine that the NAS message or the SM NAS message may correspond to a request for a new PDU session based on the request type indicating an initial request and the PDU session ID may not be used for any existing PDU session of the UE 100. If the NAS message does not include an S-NSSAI, the AMF 155 may determine a default S-NSSAI for the requested PDU session according to the subscription of the UE 100 or based on an operator policy in the case where only one default S-NSSAI may be included. In one example, the AMF 155 may perform SMF 160 selection 1210 and select the SMF 160. If the request type may indicate an initial request or the request may result from a handover from an EPS, the AMF 155 may store an association of the S-NSSAI, the PDU session ID, and the ID of the SMF 160. In one example, if the request type is an initial request and a previous PDU session ID indicating an existing PDU session may be included in the message, AMF 155 may select an SMF 160 and store the association of the new PDU session ID and the ID of the selected SMF 160.

[0143] In one example, the AMF 155 may send an N11 message 1215 to the SMF 160, such as an Nsmf_PDUSession_CreateSMContext request (including SUPI or PEI, DNN, S-NSSAI, PDU session ID, ID of AMF 155, request type, N1 SM container (PDU session establishment request), user location information, access type, PEI, GPSI) or an Nsmf_PDUSession_UpdateSMContext request (including SUPI, DNN, S-NSSAI, PDU session ID, ID of AMF 155, request type, N1 SM container (PDU session establishment request), user location information, access type, RAT type, PEI). In one example, if the AMF 155 may not have an association with the SMF 160 for the PDU session ID provided by the UE 100 (e.g., when the request type indicates an initial request), the AMF 155 may invoke the Nsmf_PDUSession_CreateSMContext request, but if the AMF 155 already has an association with the SMF 160 for the PDU session ID provided by the UE 100 (e.g., when the request type indicates an existing PDU session), the AMF 155 may invoke the Nsmf_PDUSession_UpdateSMContext request. In one example, the ID of the AMF 155 may be the UE's GUAMI, which uniquely identifies the AMF 155 serving the UE 100. The AMF 155 may forward the PDU session ID together with the N1 SM container containing the PDU session establishment request received from the UE 100. When the UE 100 registered for emergency services without providing a SUPI, the AMF 155 may provide a PEI instead of a SUPI. If the UE 100 is registered with emergency services but is not authenticated, the AMF 155 may indicate that the SUPI is not authenticated.

[0144] In one example, if the request type may not indicate an emergency request or an existing emergency PDU session, and if the SMF 160 is not yet registered and subscription data may not be available, the SMF 160 may register with the UDM 140, obtain subscription data 1225, and subscribe to be notified when the subscription data may be modified. In one example, if the request type may indicate an existing PDU session or an existing emergency PDU session, the SMF 160 may determine whether the request may be due to a handover between 3GPP access and non-3GPP access, or due to a handover from an EPS. The SMF 160 may identify an existing PDU session based on a PDU session ID. The SMF 160 may not create a new SM context, but instead may update the existing SM context and provide a representation of the updated SM context to the AMF 155 in the response. If the request type may be an initial request and if a previous PDU session ID may be included in the Nsmf_PDUSession_CreateSMContext request, SMF 160 may identify an existing PDU session to be released based on the previous PDU session ID.

[0145] In one example, the SMF 160 may send an N11 message response 1220 to the AMF 155, such as a PDU session create / update response, an Nsmf_PDUSession_CreateSMContext response 1220 (cause, SM context ID or N1 SM container (PDU session rejected (cause))), or an Nsmf_PDUSession_UpdateSMContext response.

[0146] In one example, if the SMF 160 may perform secondary authorization / authentication 1230 during PDU session establishment with the DN-AAA server, the SMF 160 may select the UPF 110 and trigger the PDU session establishment authentication / authorization.

[0147] In one example, if the request type may indicate an initial request, the SMF 160 may select the SSC mode for the PDU session. The SMF 160 may select one or more UPFs as needed. For PDU type IPv4 or IPv6, the SMF 160 may assign an IP address / prefix for the PDU session. For PDU type IPv6, the SMF 160 may assign an interface identifier to the UE 100 to construct its link-local address. For unstructured PDU types, the SMF 160 may assign an IPv6 for the PDU session and N6 point-to-point tunneling (based on UDP / IPv6).

[0148] In one example, if a dynamic PCC is deployed, the SMF 160 may perform selection 1235 of a PCF 135. If the request type indicates an existing PDU session or an existing emergency PDU session, the SMF 160 may use the already selected PCF 135 for the PDU session. If a dynamic PCC is not deployed, the SMF 160 may apply a local policy.

[0149] In one example, the SMF 160 may perform a session management policy establishment procedure 1240 to establish a PDU session with the PCF 135 and obtain default PCC rules for the PDU session. GPSI may be included if available in the SMF 160. If the request type of 1215 indicates an existing PDU session, the SMF 160 may notify the event already registered by the PCF 135 by the session management policy modification procedure, and the PCF 135 may update the policy information in the SMF 160. The PCF 135 may provide the SMF 160 with the authorized session AMBR and the authorized 5QI and ARP. The PCF 135 may register the IP allocation / release event in the SMF 160 (and may register other events).

[0150] In one example, the PCF 135 may set the ARP of the PCC rule based on the emergency DNN to a value that may be reserved for emergency services.

[0151] In one example, if the request type in 1215 indicates an initial request, the SMF 160 may select the SSC mode for the PDU session. The SMF 160 may select one or more UPFs as needed (1245). For PDU type IPv4 or IPv6, the SMF 160 may assign an IP address / prefix for the PDU session. For PDU type IPv6, the SMF 160 may assign an interface identifier to the UE 100 to construct its link-local address. For unstructured PDU types, the SMF 160 may assign an IPv6 for the PDU session and N6 point-to-point tunneling (e.g., based on UDP / IPv6). In one example, for an Ethernet PDU type PDU session, neither a MAC nor an IP address may be assigned by the SMF 160 to the UE 100 for this PDU session.

[0152] In one example, if the request type at 1215 is an existing PDU session, the SMF 160 may maintain the same IP address / prefix that may be assigned to the UE 100 in the source network.

[0153] In one example, if the request type in 1215 indicates an existing PDU session that references an existing PDU session that has been moved between 3GPP® access and non-3GPP® access, the SMF 160 may maintain the SSC mode of the PDU session, e.g., the current PDU session anchor and IP address. In one example, the SMF 160 may, for example, trigger the insertion of a new intermediate UPF 110 or the allocation of a new UPF 110. In one example, if the request type indicates an emergency request, the SMF 160 may select (1245) the UPF 110 and may select SSC mode 1.

[0154] In one example, the SMF 160 may perform a Session Management Policy Modification 1250 procedure to report some events to a previously registered PCF 135. If the request type is an initial request, a dynamic PCC is deployed, and the PDU type is IPv4 or IPv6, the SMF 160 may notify the PCF 135 (previously registered) with the assigned IP address / prefix of the UE 100.

[0155] In one example, the PCF 135 may provide the updated policy to the SMF 160. The PCF 135 may provide the authorized session AMBR and the authorized 5QI and ARP to the SMF 160.

[0156] In one example, if the request type indicates an initial request, the SMF 160 may initiate an N4 session establishment procedure 1255 with the selected UPF 110. The SMF 160 may initiate an N4 session modification procedure with the selected UPF 110. In one example, the SMF 160 may send an N4 session establishment / modification request 1255 to the UPF 110 and may provide packet detection, enforcement, reporting rules, etc. to be installed on the UPF 110 for this PDU session. If CN tunnel information is assigned by the SMF 160, the CN tunnel information may be provided to the UPF 110. If selective user plane deactivation is required for this PDU session, the SMF 160 may determine an inactivity timer and provide it to the UPF 110. In one example, the UPF 110 may acknowledge by sending an N4 session establishment / modification response 1255. If CN tunnel information is assigned by the UPF, the CN tunnel information may be provided to the SMF 160. In one example, if multiple UPFs are selected for a PDU session, the SMF 160 may initiate an N4 session establishment / modification procedure 1255 with each UPF 110 of the PDU session.

[0157] In one example, the SMF 160 may send a Namf_Communication_N1N2MessageTransfer 1305 message (including PDU Session ID, Access Type, N2 SM information (PDU Session ID, QFI, QoS Profile, CN Tunnel Information, S-NSSAI, Session AMBR, PDU Session Type, etc.), and N1 SM Container (PDU Session Establishment Accept (QoS Rule, Selected SSC Mode, S-NSSAI, Assigned IPv4 Address, Interface Identifier, Session AMBR, Selected PDU Session Type, etc.)) to the AMF 155. If multiple UPFs are used for the PDU session, the CN Tunnel Information may include tunnel information associated with the UPF 110 terminating N3. In one example, the N2 SM information may carry information that the AMF 155 may forward to the (R)AN 105 (e.g., CN tunnel information corresponding to a core network address of an N3 tunnel corresponding to a PDU session, one or more QoS profiles and corresponding QFIs may be provided to the (R)AN 105, a PDU session ID may be used by AN signaling with the UE 100 to indicate to the UE 100 an association between AN resources and a PDU session for the UE 100, etc.). In one example, the PDU session may be associated with an S-NSSAI and a DNN. In one example, the N1 SM container may include a PDU session establishment agreement that the AMF 155 may provide to the UE 100. In one example, multiple QoS rules and QoS profiles may be included in the PDU session establishment agreement in the N1 SM and in the N2 SM information. In one example, Namf_Communication_N1N2MessageTransfer 1305 may further include a PDU session ID and information that allows AMF 155 to know which access to use towards UE 100.

[0158] In one example, the AMF 155 may send an N2 PDU session request 1310 (including N2 SM information, NAS message (PDU session ID, N1 SM container (PDU session establishment accept, etc.))) to the (R)AN 105. In one example, the AMF 155 may send a NAS message 1310, which may include a PDU session ID and a PDU session establishment accept targeted to the UE 100, and the N2 SM information received from the SMF 160 in the N2 PDU session request 1310 to the (R)AN 105.

[0159] In one example, the (R)AN 105 may issue an AN-specific signaling exchange 1315 with the UE 100, which may relate to the information received from the SMF 160. In one example, in the case of a 3GPP® RAN 105, an RRC connection reconfiguration procedure may be performed with the UE 100 to establish the necessary RAN 105 resources related to the QoS rules for the PDU session request 1310. In one example, the (R)AN 105 may assign the (R)AN 105's N3 tunnel information for the PDU session. In the case of dual connectivity, the master RAN 105 node may assign some (zero or more) QFIs to be configured in the master RAN 105 node and others to the secondary RAN 105 nodes. The AN tunnel information may include tunnel endpoints for each participating RAN 105 node and QFIs assigned to each tunnel endpoint. The QFIs may be assigned to either the master RAN 105 node or the secondary RAN 105 node. In one example, the (R)AN 105 may forward a NAS message 1310 (PDU Session ID, N1 SM Container (PDU Session Establishment Accept)) to the UE 100. The (R)AN 105 may provide the NAS message to the UE 100 if the required RAN 105 resources have been established and the allocation of the (R)AN 105 tunnel information has been successful.

[0160] In one example, the N2 PDU session response 1320 may include a PDU session ID, a cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs), etc. In one example, the AN tunnel information may correspond to an access network address of an N3 tunnel corresponding to the PDU session.

[0161] In one example, the AMF 155 may forward the N2 SM information received from the (R)AN 105 to the SMF 160 via an Nsmf_PDUSession_UpdateSMContext request 1330 (including N2 SM information, request type, etc.). In one example, if a list of rejected QFIs is not included in the N2 SM information, the SMF 160 may release the rejected QFI-related QoS profiles.

[0162] In one example, the SMF 160 may initiate an N4 session modification procedure 1335 with the UPF 110. The SMF 160 may provide the AN tunnel information to the UPF 110 as well as the corresponding forwarding rules. In one example, the UPF 110 may provide an N4 session modification response 1335 to the SMF 160 160.

[0163] In one example, the SMF 160 may send a Nsmf_PDUSession_UpdateSMContext response 1340 (cause) to the AMF 155. In one example, the SMF 160 may register for UE 100 mobility event notifications (e.g., location reports, UE 100 moving into or out of the area of ​​interest) from the AMF 155 after this step by invoking a Namf_EventExposure_Subscribe service operation. For LADN, the SMF 160 may register for event notifications of UE 100 moving into or out of the LADN service area by providing the LADN DNN as an indicator for the area of ​​interest. The AMF 155 may forward the related events registered by the SMF 160.

[0164] In one example, SMF 160 may send Nsmf_PDUSession_SMContextStatusNotify(release) 1345 to AMF 155. In one example, whenever the PDU session establishment is not successful during the procedure, SMF 160 may notify AMF 155 by calling Nsmf_PDUSession_SMContextStatusNotify(release) 1345. SMF 160 may release any N4 sessions created, any PDU session addresses (e.g., IP addresses) if assigned, and may release the association with PCF 135.

[0165] In one example, for PDU type IPv6, the SMF 160 may generate an IPv6 Router Advertisement 1350 and send it to the UE 100 via N4 and the UPF 110.

[0166] In one example, if a PDU session may not be established, the SMF 160 may unsubscribe (1360) the modification of the session management subscription data for the corresponding (SUPI, DNN, S-NSSAI) using Nudm_SDM_Unsubscribe(SUPI, DNN, S-NSSAI) if the SMF 160 will not process any more PDU sessions for the UE 100 for this (DNN, S-NSSAI). In one example, if a PDU session may not be established, the SMF 160 may deregister (1360) for a given PDU session using Nudm_UECM_Deregistration(SUPI, DNN, PDU Session ID).

[0167] Figure 14 illustrates an example of a mobile communication network in which an embodiment of the present disclosure may be implemented. The mobile communication network depicted in Figure 14 includes a wireless device 1410, a base station 1420, a physical core network deployment of one or more network functions 1430 (hereinafter "CN deployment 1430"), and a physical core network deployment of one or more network functions 1440 (hereinafter "CN deployment 1440"). Deployment 1430 and deployment 1440 may be elements of a core network.

[0168] The wireless device 1410 may communicate with the base station 1420 over the air interface 1470. The direction of communication from the wireless device 1410 to the base station 1420 over the air interface is known as the uplink, and the direction of communication from the base station 1420 to the wireless device 1410 over the air interface 1470 is known as the downlink. The downlink transmission may be separated from the uplink transmission using FDD, TDD, and / or some combination of the two duplexing techniques. Although FIG. 14 shows a single wireless device 1410 and a single base station 1420, it will be understood that the wireless device 1410 may communicate with any number of base stations or other access network components over the air interface 1470, and the base station 1420 may communicate with any number of wireless devices over the air interface 1470.

[0169] The wireless device 1410 may include a processing system 1411 and a memory 1412. The memory 1412 may include one or more computer readable media, e.g., one or more non-transitory computer readable media. The memory 1412 may include instructions 1413. The processing system 1411 may process and / or execute the instructions 1413. The processing and / or execution of the instructions 1413 may cause the processing system 1411 to perform one or more functions or activities. The memory 1412 may include data (not shown). One of the functions or activities performed by the processing system 1411 may be to store data in the memory 1412 and / or to retrieve previously stored data from the memory 1412. In one example, downlink data received from a base station 1420 may be stored in the memory 1412, and uplink data for transmission to the base station 1420 may be retrieved from the memory 1412. The wireless device 1410 may communicate with a base station 1420 using a transmit processing system 1414 and a receive processing system 1415. The wireless device 1410 may include one or more antennas 1416 for accessing an air interface 1470. Although not shown in FIG. 14 , the transmit processing system 1414 and / or the receive processing system 1415 may be coupled to dedicated memory similar to but separate from the memory 1412 and may include instructions that can be processed and / or executed to perform one or more of their respective functions.

[0170] The wireless device 1410 may include one or more other elements 1419. The one or more other elements 1419 may include software and / or hardware that provide features and / or functionality. For example, a speaker, a microphone, a keypad, a display, a touchpad, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for an automobile), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, a global positioning sensor (GPS), etc.). The wireless device 1410 may receive user input data from the one or more other elements 1419 and / or provide user output data to the one or more other elements 1419. The one or more other elements 1419 may include a power source. The wireless device 1410 may be configured to receive power from the power source and distribute the power to other components within the wireless device 1410. The power source may include one or more power sources, for example, a battery, a solar cell, a fuel cell, or any combination thereof.

[0171] The wireless device 1410 may transmit data to the base station 1420 over the air interface 1470. To perform the transmission, the processing system 1411 may implement layer 3 and layer 2 Open System Interconnection (OSI) functions to process the data for uplink transmission. Layer 3 may include a radio resource control layer (RRC). Layer 14 may include a service data application protocol layer (SDAP), a packet data convergence protocol layer (PDCP), a radio link control layer (RLC), and a media access control layer (MAC). The data may be provided to a transmit processing system 1414 that may implement layer 1 OSI functions. Layer 1 may include a physical layer (PHY). The wireless device 1410 may transmit data over the air interface 1470 using one or more antennas 1416. For scenarios in which the one or more antennas 1416 include multiple antennas, the multiple antennas may be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple-input multiple-output (MIMO) or multi-user MIMO), transmit / receive diversity, and / or beamforming.

[0172] The wireless device 1410 may receive downlink data from the base station 1420 via the air interface 1470. The downlink data may be received via one or more antennas 1416. The receive processing system 1415 may implement layer 1 OSI functions on the received downlink data and provide the data to the processing system 1411. The processing system 1411 may implement layer 2 and layer 3 OSI functions to process the received downlink data. The base station 1420 may include elements similar to the elements of the wireless device 1410. The base station 1420 may include a processing system 1421 and a memory 1422. The memory 1422 may include one or more computer readable media, e.g., one or more non-transitory computer readable media. The memory 1422 may include instructions 1423. The processing system 1421 may process and / or execute the instructions 1423. Processing and / or execution of instructions 1423 may cause processing system 1421 to perform one or more functions or activities. Memory 1422 may include data (not shown). One of the functions or activities performed by processing system 1421 may be storing data in memory 1422 and / or retrieving previously stored data from memory 1422. Base station 1420 may communicate with wireless device 1410 using transmit processing system 1424 and receive processing system 1425. Base station 1420 may include one or more antennas 1426 for accessing air interface 1470. Processing system 1421 may implement layer 14 and layer 3 OSI functions. Transmit processing system 1424 and receive processing system 1425 may implement layer 1 OSI functions to perform transmission of downlink data and reception of uplink data, respectively.

[0173] The base station 1420 may include an interface system 1427. The interface system 1427 may communicate with one or more elements of the core network via an interface 1480. The interface 1480 may be wired and / or wireless, and the interface system 1427 may include one or more components suitable for communicating via the interface 1480. In FIG. 14, the interface 1480 connects the base station 1420 to a single CN deployment 1430, but it will be understood that the wireless device 1410 may communicate with any number of CN deployments over the interface 1480, and the CN deployment 1430 may communicate with any number of base stations over the interface 1480. The base station 1420 may include one or more other elements 1429 similar to one or more of the one or more other elements 1419.

[0174] The CN deployment 1430 may include one or more network functions (NFs). For example, the CN deployment 1430 may include an AMF and / or UPF similar to the AMF and UPF shown in FIG. 1. The CN deployment 1430 may include elements similar to the elements of the wireless device 1410 and the base station 1420, as described above. The CN deployment 1430 may include a processing system 1431 and a memory 1432. The memory 1432 may include one or more computer readable media, e.g., one or more non-transitory computer readable media. The memory 1432 may include instructions 1433. The processing system 1431 may process and / or execute the instructions 1433. The processing and / or execution of the instructions 1433 may cause the processing system 1431 to perform one or more functions or activities. The memory 1432 may include data (not shown). One of the functions or activities performed by processing system 1431 may be to store data in memory 1432 and / or retrieve previously stored data from memory 1432. CN deployment 1430 may access interface 1480 using interface system 1437. CN deployment 1430 may also use interface system 1437 to access interface 1490. CN deployment 1430 may use interface 1490 to communicate with one or more data networks (similar to the DN depicted in FIG. 1 and / or one or more other CN deployments, including CN deployment 1440 depicted in FIG. 14). CN deployment 1430 may include one or more other elements 1439.

[0175] CN deployment 1440 may include elements similar to those of CN deployment 1430, as described above. CN deployment 1440 may include a processing system 1441 and a memory 1442. Memory 1442 may include one or more computer readable media, e.g., one or more non-transitory computer readable media. Memory 1442 may include instructions 1443. Processing system 1441 may process and / or execute instructions 1443. The processing and / or execution of instructions 1443 may cause processing system 1441 to perform one or more functions or activities. Memory 1442 may include data (not shown). One of the functions or activities performed by processing system 1441 may be to store data in memory 1442 and / or retrieve previously stored data from memory 1442. CN deployment 1440 may access interface 1490 using interface system 1447. The CN expansion 1440 may include one or more other elements.

[0176] Processing system 1411, processing system 1421, processing system 1431, and / or processing system 1441 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. Processing system 1411, processing system 1421, processing system 1431, and / or processing system 1441 may perform signal coding / processing, data processing, power control, input / output processing, and / or any function that may enable wireless device 1410, base station 1420, CN deployment 1430, and / or CN deployment 1440 to operate in a mobile communication system.

[0177] Each CN deployment may include one or more network functions. Depending on the context in which the term is used, a network function (NF) may refer to a particular set of functions and / or one or more physical elements (e.g., a processing system and memory containing instructions that, when executed by the processing system, cause the processing system to perform the functions) configured to perform those functions. There are many different types of NFs, and each type of NF may be associated with a different set of functions. Different NFs may be flexibly deployed in different locations (e.g., different physical core network deployments) or in the same location (e.g., co-located in the same physical core network deployment). Furthermore, a physical CN deployment is not limited to the implementation of an NF. For example, a particular physical CN deployment may further include a base station or a portion thereof, and / or a data network or a portion thereof. Thus, one or more NFs implemented in a particular physical core network deployment may coexist with one or more non-core elements, including elements of an access network or a data network.

[0178] FIG. 15 illustrates a service-based architecture for 5G networks with respect to control plane (CP) and user plane (UP) interactions. This diagram may illustrate logical connections between nodes and functions, and the illustrated connections may not be interpreted as direct physical connections. A wireless device may form a radio access network connection with a base station connected to a user plane (UP) function (UPF) via a network interface that provides a defined interface, such as an N3 interface. The UPF may provide a logical connection to a data network (DN) via a network interface, such as an N6 interface. The radio access network connection between a wireless device and a base station may be referred to as a data radio bearer (DRB).

[0179] The DN may be a data network used to provide operator services, third party services such as Internet, IP Multimedia Subsystem (IMS), Augmented Reality (AR), Virtual Reality (VR), etc. In some embodiments, the DN may represent an edge computing network or resource, such as a Mobile Edge Computing (MEC) network.

[0180] The wireless device also connects to the AMF via a logical N1 connection. The AMF may be responsible for AA of access requests, as well as mobility management functions. The AMF may perform other roles and functions. In a service-based view, the AMF may communicate with other core network control plane functions via a service-based interface, denoted as Namf.

[0181] The SMF is a network function that may be responsible for allocating and managing IP addresses assigned to wireless devices, as well as selecting a UPF for traffic associated with a particular session of the wireless device. Typically, there are multiple SMFs in a network, each of which may be associated with a respective group of wireless devices, base stations, or UPFs. The SMF may communicate with other core network functions through service-based interfaces, denoted as Nsmf in a service-based view. The SMF may also connect to a UPF through a logical interface, such as the network interface N4.

[0182] An Authentication Server Function (AUSF) may provide authentication services to other network functions via a service-based Nausf interface. A Network Exposure Function (NEF) may be introduced within the network to allow servers, functions, and other entities, such as those outside the trusted domain (operator network), to be exposed to services and capabilities within the network. In one such embodiment, the NEF may act like a proxy between external application servers (AS) outside the illustrated network and network functions such as PCF, SMF, UDM, and AMF. The external AS may provide information that may be used in setting up parameters associated with a data session. The NEF may communicate with other network functions via a service-based Nnef network interface. The NEF may have an interface to non-3GPP functions.

[0183] A Network Repository Function (NRF) may provide network service discovery functionality. An NRF may be specific to a Public Land Mobility Network (PLMN) or the network operator with which it is associated. The service discovery function allows network functions and wireless devices connected to the network to determine where and how to access existing network functions.

[0184] The PCF may communicate with other network functions via a service-based Npcf interface and may be used to provide policies and rules to other network functions, including those in the control plane. The enforcement and application of policies and rules may not be the responsibility of the PCF. The responsibility for the function to which the PCF conveys policies may be the responsibility of the AMF or SMF. In one such example, the PCF may convey policies associated with session management to the SMF. This may be used to enable a unified policy framework within which network behavior can be managed.

[0185] The UDM may present a service-based Nudm interface for communicating with other network functions. The UDM may provide data storage facilities to other network functions. Unified data storage may enable a unified view of network information that may be used to make the most relevant information available to different network functions from a single resource. This may allow for easier implementation of other network functions as they may not need to determine where a particular type of data is stored within the network. The UDM may employ an interface such as Nudr to connect to the UDR. A PCF may be associated with the UDM.

[0186] The PCF may have a direct interface to the UDR or may connect to the UDR using a Nudr interface. The UDM may receive requests to retrieve content stored in the UDR or to store content in the UDR. The UDM may be responsible for functions such as authentication information processing, location information management, and subscription management. The UDR may also support authentication credential processing, user identity processing, access authentication, registration / mobility management, subscription management, and short message service (SMS) management. The UDR may be responsible for storing data provided by the UDM. The stored data is associated with policy profile information (which may be provided by the PCF) that governs access rights to the stored data. In some embodiments, the UDR may store policy data and user subscription data, which may include any or all of subscription identifiers, security credentials, access and mobility related subscription data, and session related data.

[0187] An Application Function (AF) may represent non-data plane (also called non-user plane) functions of applications deployed within a network operator domain and within a 3GPP-compliant network. An AF may reside within an internal Application Server (AS). An AF may interact with other core network functions via a service-based Naf interface to access network capability exposure information and provide application information for use in decisions such as traffic routing. An AF may also interact with functions such as PCFs to provide application-specific inputs to policy and policy enforcement decisions. In many cases, an AF may not provide network services to other network functions. An AF may often be considered a consumer or user of services provided by other network functions. Applications (application servers) outside the trusted domain (operator network) may use a NEF to perform many of the same functions as an AF.

[0188] A wireless device may communicate with network functions in the Core Network Control Plane (CN-UP) and Core Network User Plane (CN-CP). The UPF and Data Network (DN) are part of the CN-UP. The DN may be outside the core network domain (cellular network domain). In the diagram (Figure 15), the base station is located on the CP-UP side. The base station may provide connectivity for both the CN-CP and the CN-UP. The AMF, SMF, AUSF, NEF, NRF, PCF, and UDM may be functions that reside in the CN-CP and are often referred to as control plane functions. If the AF resides in a trusted domain, the AF may communicate with other functions in the CN-CP directly through the service-based Naf interface.

[0189] If the AF resides outside the trusted domain, the AM may communicate with other functions in the CN-CP indirectly via the NEF.

[0190] An unmanned aerial vehicle and / or crewless aerial vehicle (UAV) may be an aerial vehicle without a human pilot or crew on board (e.g., crewless) and / or without passengers on board (e.g., unmanned). An unmanned aerial vehicle and / or crewless aerial system (UAS) may be a system for operating a UAV. As shown in FIG. 16, a UAS may include a UAV, a ground control system (e.g., a UAV controller), a camera, a positioning system, and / or any other suitable device for operating the UAS. A wireless network (e.g., a cellular network, a 4G cellular network, a 5G cellular network) may enable a ground control system (e.g., a UAV controller, a UTM, a USS) to communicate with the UAV, which may be one of the components of the UAS.

[0191] In one embodiment, the wireless device may be a UAV. The wireless device may be an aerial wireless device. The wireless device may fly over the ground. As shown in FIG. 17, the wireless device may experience high line-of-sight (LOS) propagation probability. The wireless device may receive downlink (e.g., from a base station to the wireless device) interference from a larger number of cells than a typical terrestrial wireless device. In the downlink direction, the number of neighboring cells causing high levels of downlink interference at the wireless device may be more likely than for a terrestrial wireless device. In one embodiment, 16 cells causing high levels of downlink direction interference may be observed by a wireless device at a height of 50 m or more. In one embodiment, the antenna of the base station (e.g., eNB, gNB) may be tilted down to serve the terrestrial wireless device. The wireless device may be located above the height of the antenna of the base station. The wireless device may be served by the side lobe of the antenna of the base station. The wireless device may see stronger signals from a base station that is farther away than the one that is geographically closest. The wireless device may be served by a base station that is farther away instead of the closest one. The luminosity in the downlink direction and the luminosity in the uplink direction of an aviation wireless device may be different in some scenarios where reciprocity is not maintained (e.g., due to different side leaf orientations in the uplink and downlink, or different channel characteristics in a frequency domain division multiplexing (FDD) arrangement).

[0192] Base stations of the wireless network and wireless devices may employ Radio Access Network (RAN) functions for aviation communication services (e.g., UAS, UAV, UAV controller, etc.). The base stations and wireless devices may support Radio Access Network (RAN) functions for aviation communication services. The RAN functions for aviation communication services may be aviation user equipment (UE) communications. In one embodiment, the aviation communication services may be aviation UE communications. The aviation communication services may support UAS. The RAN functions for aviation communication services may include height-based measurement reports, interference detection for aviation UE communications, interference mitigation for aviation UE communications, flight path information reports, location reports for aviation UE communications, and / or the like.

[0193] In one embodiment, the base station may send an RRC message (e.g., an RRC configuration message, an RRC reconfiguration message) to the wireless device. The RRC message may include one or more measurement events related to height-based measurement reporting. The one or more measurement events may indicate to the wireless device a height threshold for height-based measurement reporting. The wireless device may receive the measurement event including the height threshold. The wireless device may send a height report if the altitude of the wireless device is above or below the height threshold. The height report may include the height of the wireless device, the location of the wireless device, and / or the like.

[0194] If the received signaling power (e.g., RSRP) of multiple neighboring cells exceeds a certain level to the wireless device, the wireless device may experience or introduce interference. For interference detection, the base station may configure a radio resource management (RRM) event that triggers a measurement report when the individual (per cell) RSRP values ​​of a configured number of cells (e.g., 8, 16) meet the configured event. The configured event may be for interference detection. The RRM event may be A3, A4, or A5. The wireless device may send the measurement report in response to determining that an RRM event occurs.

[0195] In one embodiment, for interference mitigation, the base station may configure with a wireless device specific alpha parameter for physical uplink shared channel (PUSCH) power control. The base station may transmit a radio resource control (RRC) message including the alpha parameter for PUSCH power control. If the wireless device receives a dedicated alpha parameter (e.g., alpha-UE) from the base station, the radio may apply the dedicated alpha parameter instead of the common alpha parameter.

[0196] In one embodiment, the base station may request the wireless device to report flight path information by sending a USER EQUIPMENT INFORMATION REQUEST message. The flight path information may include a number of waypoints defined as 3D positions. The USER EQUIPMENT INFORMATION message may indicate a maximum number of waypoints and / or whether the waypoints require timestamps. The wireless device may receive the USER EQUIPMENT INFORMATION message. If the wireless device is available to report the flight path, the wireless device may send a USER EQUIPMENT INFORMATION RESPONSE message to the base station. The USER EQUIPMENT RESPONSE message may include one or more waypoints and one or more timestamps associated with the one or more waypoints. The base station may use the flight path information for congestion prediction or resource handling to mitigate interference.

[0197] In one embodiment, for position reporting of air UE communications, the base station may request the wireless device to include the horizontal and vertical velocity of the wireless device in the position information report. The wireless device may transmit the position information to the base station. The position information report may include the horizontal velocity, the vertical velocity, and / or the like. The position information may further include the height of the wireless device.

[0198] Remote Identification (RID) may be a technique to avoid collisions between different UAVs or between manned aircraft and UAVs. To prevent collisions, the Federal Aviation Authority (FAA) may incorporate UAVs into the National Airspace System (NAS) by introducing RID. RID may be the capability of a UAS in flight to provide identification and tracking information that may be received by other parties and may serve to identify and ground unauthorized UAS in restricted areas. In one embodiment, UAVs over 0.55 pounds may be mandated to support RID. There may be two types of RID: standard RID and restricted RID. For standard RID, the UAV may support network publishing identification (ID) and direct broadcast ID. For restricted RID, the UAV may support network publishing ID. For restricted RID, the UAV may not support direct broadcast ID. Network publishing ID may be based on communication over the Internet from a RID server provider that interfaces with the UAV. A direct broadcast ID may be based on direct transmission of the RID by the UAV using its on-board direct transmission technology (e.g., Bluetooth, Wi-Fi module). UAVs that support limited RID (e.g., do not support direct broadcast ID) may not be permitted to fly above 400 feet. During flight, UAVs that support limited RID, network connectivity may be required. UASs that support standard RID may be permitted to fly above 400 feet and have no restrictions on network connectivity.

[0199] In one embodiment, the command and control communication can be a user plane link for delivering messages including command and control information for UAV operation from the UAV's controller or UTM to the UAV. The command and control communication can be C2 communication. C2 communication includes three types of communication: 1) direct C2 communication, 2) network-assisted C2 communication, and 3) UTM-navigated C2 communication. Direct C2 communication can use a direct communication link between the UAV and the UAV controller. Network-assisted C2 communication can use a cellular network (e.g., a public land mobile network) to communicate between the UAV and the UAV controller. If UTM-navigated C2 communication is available, the UTM can provide a pre-scheduled flight plan to the UAV, and the UTM can track and verify the latest restrictions or flight plans for the UAV.

[0200] FIG. 18 illustrates example interfaces (e.g., U2U, UAV3, UAV6, UAV8, UAV9) of a UAS with a wireless network (e.g., PLMN1, PLMN2). The interfaces may be communication connections. In one embodiment, the U2U interface may be a direct broadcast ID interface. The UAV8 interface may be an interface for direct C2 communication between the UAV and the UAV controller. The UAV3 interface may be an interface between the UAV and the UAV controller over a wireless network. In one embodiment, the UAV3 may be intra-PLMN or intra-PLMN. In one embodiment, for intra-PLMN, PLMN1 and PLMN2 may be the same PLMN. For intra-PLMN, PLMN1 and PLMN2 may be different PLMNs. In one embodiment, the UAV9 may be an interface between the UAV and the networked UAV controller and the USS / UTM for UAS management (e.g., authentication and / or authorization (AA), C2 forwarding, RID, and tracking of the UAV). In one embodiment, the UAV6 may be an interface between the PLMN (e.g., a 3GPP network) and the USS / UTM for exposing functionality, supporting identification and tracking, and authenticating and / or authorizing the UAV.

[0201] As shown in FIG. 19, the wireless device may move according to a moving path (e.g., a flight path) indicated by a dotted line. In one embodiment, the base station of "Cell A" may not function due to a power outage or malfunction. The wireless device may experience a communication failure while the wireless crosses the area of ​​"Cell A". The communication failure may be a short-term (e.g., 1 minute, 5 minutes) communication failure. The communication failure may be a communication outage. In one example, there is no available base station next to the coverage area of ​​"Cell B". The wireless device may experience a communication failure after the wireless device leaves the coverage area of ​​"Cell B" and moves to the right. The communication failure may be a long-term (e.g., 30 minutes, 1 hour) communication failure.

[0202] In one embodiment, the wireless device may send a registration request message to the AMF via the base station. The registration request message may include an identity of the wireless device, an aeronautical service capability (e.g., an aeronautical service capability, an aeronautical communication service capability, a UAS service capability), slice information, a UAV identifier (e.g., a Civil Aviation Authority (CAA) UAV identifier, etc.), and / or the like. In one embodiment, the aeronautical service capability may be whether the wireless device supports a RAN function for aeronautical services. In one embodiment, the aeronautical service capability may be whether the wireless device requires aeronautical services (e.g., acts as a UAV or a controller of a UAV). An aeronautical domain or a function of the aeronautical domain may assign a UAV identifier to the wireless device. In one embodiment, the aeronautical domain may be a UAS Traffic Management (UTM) or a UAS Service Supplier (USS). The UAV identifier may be a CAA-level UAV identifier. The UAV identifier may be used for RID and tracking of the wireless device. The wireless device identity may include at least one of a SUCI, a 5G-GUTI, an International Mobile Equipment Identity (IMEI), an IMEI Software Version (IMEISV), a shortened version of the 5G-GUTI, and / or the like.

[0203] In response to receiving the registration request message, the AMF may send a UE context request message to a subscription service (e.g., UDM, etc.). The UE context request message may include an identity of the wireless device, capabilities of the UAS, slice information, and / or the like. In one embodiment, the identity of the wireless device may be a permanent identifier (e.g., IMSI, SUPI) of the subscriber of the wireless device.

[0204] In one embodiment, the UDM may receive a UE context request message from the AMF. In response to receiving the UE context request message, the UDM may send a UE context response message to the AMF, including subscription information of the wireless device. The UDM may determine the subscription information based on the presence of a capability for aviation services and slice information. In one embodiment, if a capability for aviation services is present in the UE context request message, the UDM may include UAS subscription information in the subscription information. The subscription information may be subscription data. In one embodiment, the subscription information may indicate whether the wireless device can receive aviation services. In one embodiment, the subscription information may indicate whether the wireless device may or may not receive aviation services. The subscription information may further indicate whether authentication and / or authorization (AA) is required for the aviation services.

[0205] The AMF may receive a UE context response message including the subscription information. In response to receiving the UE context response message, the AMF may determine whether authentication and / or authorization (AA) is required for aviation services. The determination may be based on capabilities provided by the wireless device, subscription information provided by a subscription server, and / or the like. If the capabilities indicate that the wireless device does not support aviation services, the AMF may not allow the aviation services and may not perform AA for the services.

[0206] In one embodiment, the subscription information may indicate that the wireless device can receive aviation services. If aviation services are authorized for the wireless device, the AMF may check whether authentication and / or authorization (AA) is required for the wireless device. If AA is required for the service, the AMF may indicate to the wireless device that AA for the aviation services is pending. While AA for the wireless device's aviation services is pending, the AMF may suspend activation of base stations and RAN functions associated with the wireless device and the service.

[0207] If authentication and / or authorization (AA) for the aviation service is required based on the subscription information, the AMF may perform an AA procedure for the aviation service by sending an AA request message to an AA server. The AA server may be a UTM or a USS. The AMF may send the AA request message to the AA server via the NEF or a new network device for the aviation service. The AA request message may include the identity of the UAV, a GPSI, and / or the like. The AA server may use the identity of the UAV to identify the AA server or a wireless device in the aviation domain (e.g., UTM / USS). The 3GPP® network (e.g., a mobile operator) may assign the GPSI for the aviation service. The AA server may use the GPSI for communication with the 3GPP® network.

[0208] The AA request message may trigger the implementation of authentication and / or authorization procedures between the AA server and the wireless device. A detailed procedure of the service-specific AA procedure is described in FIG. 20. When the service-specific AA procedure is completed, the AA server may send an AA response message to the AMF. The AA response message may include an AA result, an authentication type, an authentication level, an authentication path, and / or the like. In one embodiment, the AA completion may mean that the service is ready for use at the application layer between the wireless device and the AA server.

[0209] In one embodiment, the AMF may receive an AA response message from an AA server. In response to receiving the AA response message, the AMF may send a configuration update message indicating an AA result (e.g., whether the wireless device is authenticated and / or authorized for aeronautical services). If the AA result indicates that aeronautical services are not authenticated / authorized for the wireless device (e.g., AA is unsuccessful), the wireless device may not request establishment of one or more PDU sessions associated with the aeronautical services. If the AA result indicates that aeronautical services are authenticated / authorized for the wireless device (e.g., AA is successful), the wireless device may request the SMF to establish one or more PDU sessions associated with the aeronautical services. In one embodiment, the AAA-S may be an AA server.

[0210] FIG. 20 illustrates an exemplary service-specific AA procedure. The AMF may trigger the initiation of a service-specific AA procedure for a service. The AMF may be an MME. The AMF may send an Extensible Authentication Protocol (EAP) Identity Request for the service to the wireless device in a NAS MM Transport message including the service name. The wireless device may provide an EAP Identity Response for the service with the service name in a NAS MM Transport message to the AMF. The AMF may send the EAP Identity Response to the AA server in an AA Request (EAP Identity Response, AAA-S Address, GPSI, Service Name) message. If an AAA-P exists (e.g., because the AAA-S belongs to a third party and the operator has deployed a proxy for the third party), the AA server forwards the EAP Identity Response message to the AAA-P. Otherwise, the AA server forwards the message directly to the AAA-S. The AA server may use AAA protocol messages for the AAA-P or AAA-S of the same protocol as supported by the AAA-S. The AAA-P can forward the EAP Identity message with the service and GPSI to the AAA-S addressable by the AAA-S address. The AAA-S may store the GPSI to create an association with the EAP Identity in the EAP Identity Response message, so that the AAA-S may later use the GPSI to revoke authorization or trigger re-authentication. EAP messages may be exchanged with the wireless device. One or more iterations of these steps may occur. Once the EAP authentication is completed, the AAA-S may store the service for which authorization was granted, so that the AAA-S may decide to trigger re-authentication and / or re-authorization based on its local policy. The EAP success / failure message may be delivered to the AAA-P (or directly to the AA server if the AAA-P does not exist) with the GPSI and the service name. If the AAA-P is used, the AAA-P may send an AAA protocol message including (EAP success / failure, service name, GPSI) to the AA server.The AA server may send an authentication response (EAP success / failure, service name, GPSI) to the AMF. The AMF may transmit a NAS MM transport message (EAP success / failure) to the wireless device. The AMF may store the EAP result for each service for which a service-specific AA procedure was performed. In one embodiment, the AAA-S may be the AA server.

[0211] In existing techniques, a wireless device (e.g., a UAS, a UAV, a UAV controller, etc.) may request establishment of one or more sessions (e.g., a PDU session, a PDN connection, etc.). The one or more sessions may be for an aviation service (e.g., an aviation system service, a UAS service, etc.). To establish the one or more sessions, the wireless device may send a request to a session management entity (SME, e.g., a session management function (SMF), a mobility management entity (MME), etc.). Authentication and / or authorization (AA) of the wireless device may need to be determined (e.g., required) (e.g., before a session can be established and / or before a request can be accepted by the SME). The AA may require one or more communications between the wireless device and / or the network and a traffic manager (e.g., a UAS traffic management (UTM) or a UAS service supplier (USS)). If the need for (e.g., request) AA for an aviation service is introduced, the existing techniques for session management (e.g., request, establishment, modification, acceptance, rejection, etc.) may result in delays, ambiguity, and / or signaling overhead. For example, a wireless device may request a session establishment associated with an airline service. At the time of the request, the AA may be incomplete and / or the outcome of the AA procedure may be unknown. As a result, the request may be rejected, retried and rejected again, accepted after a delay, etc. Additionally or alternatively, the request may be accepted without the necessary AA, resulting in an unauthorized and / or inoperable session.

[0212] According to an example embodiment of the present disclosure, a mobility management function (MMF) (e.g., an access and mobility management function (AMF), a mobility management entity (MME), etc.) may determine an AA for an air service of a wireless device. The determination may be based on, for example, a registration request message received from the wireless device, or any other suitable signal or information that prompts the MMF to determine an AA for the wireless device. In one example, the registration or other signal / information may indicate an air service (e.g., may include a UAS indicator, a UAV identifier of the wireless device, etc.). The MMF may send an indication of the AA for the air service of the wireless device to a session management entity (SME) (e.g., a serving gateway (S-GW), a serving gateway controller (S-GW-C), a session management function (SMF), etc.). The indication may enable the SME to manage the session of the wireless device without delay, ambiguity, or signaling overhead associated with existing techniques (e.g., more quickly, more accurately, etc. with less signaling overhead).

[0213] In existing technology, a wireless device (e.g., a UAS, a UAV, a UAV controller, etc.) may establish one or more sessions (e.g., PDU sessions, PDN connections) for an aviation service (e.g., an aviation system service, a UAS service, etc.). To establish the one or more sessions, the wireless device may obtain an authentication and / or authorization (AA) from a traffic manager (e.g., a UAS traffic management (UTM) or a UAS service supplier (USS)). The wireless device may request one or more sessions associated with the aviation service. The wireless device may be authorized to use the one or more sessions if the wireless device obtains the AA from the traffic manager.

[0214] In one embodiment, a problem may occur when AA fails for a wireless device. This problem may occur when a traffic manager cancels AA of a wireless device for a UAS. For example, the traffic manager may cancel AA if the wireless device is out of an authorized area or if the subscription of the wireless device expires. If AA of a wireless device for a UAS fails, one or more sessions associated with the UAS may be rejected. If AA of a wireless device for a UAS is canceled, one or more sessions associated with the UAS may be released. Existing session rejection or release procedures may increase ambiguity for the wireless device and increase signaling exchanges to handle the procedures. Therefore, enhanced session handling procedures for UAS failure or cancellation may be needed.

[0215] According to an example embodiment of the present disclosure, a network device (e.g., SMF, AMF) may terminate (e.g., release, reject PDU session establishment, deregister) one or more packet data unit (PDU) sessions associated with one or more airline services of a wireless device. The network function may terminate one or more PDU sessions associated with one or more airline services by sending an indication that AA for the services of the wireless device is cancelled or failed. The network device may terminate one or more PDU sessions of the wireless device by sending a message indicating that AA for the airline services of the wireless device is cancelled or failed. The network device may terminate one or more PDU sessions by sending a second message indicating that AA for command and control (C2) for the airline services of the wireless device is cancelled or failed. The network device may indicate a level, category, or type of AA cancellation or failure. Based on different levels of AA cancellation (e.g., per airline service, per C2 service), the wireless device may be able to process the sessions associated with the airline services without further signaling exchange.

[0216] According to an example embodiment of the present disclosure, a session management function (SMF) may receive a first message from a network device (e.g., AMF, traffic manager). The first message may indicate that an AA for an air service for the wireless device has been cancelled or failed. The SMF may determine to release one or more packet data unit (PDU) sessions based on the first message. The SMF may determine to reject establishment of a PDU session based on the first message. The one or more PDU sessions may be associated with the air service. The SMF may send a second message to the wireless device indicating the decision. The second message may include a cause parameter indicating that an AA for an air service for the wireless device has been cancelled or failed. Example embodiments may enable the SMF to determine that the PDU session release or rejection is associated with an AA for the air service. Example embodiments may enable the SMF to determine that the PDU session release or rejection is associated with an AA for the air service but not the network device. Therefore, the release or rejection can be decided dynamically and intelligently (e.g., if the PDU session has a higher priority, the SMF may decide not to release or reject the PDU session).

[0217] According to an example embodiment of the present disclosure, a wireless device may receive a message from an SMF requesting modification of a PDU session. The message may include a cause parameter indicating, for example, that an AA of C2 to a UAS has been revoked or failed. The message may indicate a QoS flow to be removed from the PDU session. In one example, the indicated QoS flow may be associated with C2. Example embodiments may reduce ambiguity for the wireless device by indicating a cause. In the absence of the cause parameter, the wireless device may request modification of the PDU session to request one or more QoS flows for C2. Based on the cause parameter, the wireless device may reduce delay and / or signaling overhead by avoiding wasteful and / or unnecessary modification requests. Based on the cause parameter, the wireless device may request an update of authentication information for the AA of C2 from an AA server (e.g., UTM / USS) before requesting modification.

[0218] According to an example embodiment of the present disclosure, a mobility management function (MME) may receive a first message from a wireless device requesting establishment of a packet data network (PDN) connection. The PDN connection may be associated with an aviation service. The MME may send a second message to a serving gateway (S-GW) requesting creation of the PDN connection. The MME may receive a third message indicating a cause parameter that AA for the aviation service of the wireless device has been cancelled or failed. The MME may send a fourth message indicating rejection of establishment of the PDN connection. The fourth message may include a cause. Example embodiments may reduce ambiguity for the wireless device by indicating a cause that AA for the aviation service of the wireless device has been cancelled or failed.

[0219] According to an example embodiment of the present disclosure, an MME may receive a first message from a serving gateway (S-GW) requesting release of bearers of a wireless device. The first message may include a cause parameter indicating that AA for an air service of the wireless device has been cancelled or failed. The MME may determine that the first message may cause release of a last packet data network (PDN) connection of the wireless device. Based on the determination, the MME may send a second message requesting disassociation of the wireless device. The second message may be a disassociation request message. The second message may include a cause parameter indicating that AA for an air service of the wireless device has been cancelled or failed. Based on the cause parameter, the wireless device may recognize that AA for the air service may be required in a UTM or USS. The example embodiment may reduce ambiguity of the MME by introducing a decision condition of disassociation of the wireless device regarding AA cancellation for the air service. The example embodiment may reduce signaling overload of the wireless device by indicating a disassociation cause of the wireless device. Based on the cause parameter that the AA for the air service was canceled or failed, the wireless device may not be able to send an attach request to the MME. Based on the cause parameter that the AA for the air service was canceled or failed, the wireless device may update the AA for the air service by the UTM / USS.

[0220] 21 and 22 show example session processing procedures for a 5G network and a wireless device regarding cancellation / failure of AA for an aviation service. In one embodiment, the wireless device may be registered to a 5G network. As shown in FIG. 19, the AMF may perform an AA procedure for an aviation service. The SMF may receive a first message indicating that an AA (AA) for an aviation service of the wireless device has been cancelled or failed from a network device. The first message may be a PDU session creation message. The first message may be a PDU session update message. The SMF may determine a rejection of one or more PDU session establishments. The SMF may determine a release of one or more PDU sessions of the wireless device. The one or more PDU sessions may be associated with the aviation service. The SMF may send a second message indicating the determination to the wireless device. The second message may include a cause parameter indicating that an AA for an aviation service of the wireless device has been cancelled or failed. The cause parameter may indicate that an AA for a command and control (C2) of the wireless device has been cancelled or failed. In one embodiment, the wireless device may be a UAV. The wireless device may be a UAV controller.

[0221] 21 illustrates a call flow in which the SMF notifies the wireless device of a rejection of an establishment request for one or more PDU sessions based on an AA (AA) status for an air service received from a network device. The network device may be an AMF.

[0222] The wireless device may send a PDU session establishment request message to the AMF to obtain an aviation service (e.g., to communicate with a UTM / USS, C2 session). The PDU session establishment request message may include a UAS capability (e.g., aviation service capability, UAS service capability, etc.), a PDU session identity, a UAV identifier, a DNN, an S-NSSAI, and / or the like. The DNN and / or the S-NSSAI may be associated with an aviation service. In one embodiment, the DNN may indicate an aviation service or a C2 service. The S-NSSAI may indicate an aviation service or a C2 service.

[0223] In response to receiving a PDU session establishment request associated with the aviation service, the AMF may invoke a create session management (SM) context request service with SMF service by sending a first message (e.g., a create SM context request message, Nsmf_PDUSession_CreateSMContext) to the SMF. The first message may be a create SM context request message. The create SM context request message may include an identifier of the wireless device, a DNN, an S-NSSAI, a UAS capability, a PDU session identity, a UAV identifier, a SM container including the PDU session establishment request message, and / or the like. In one embodiment, the create SM context request message may further include an AA (AA) state for the UAS of the wireless device. The AA state of the UAS may indicate whether the wireless device is authenticated and / or authorized for aviation services. The AA state for the aviation services of the wireless device may include a first parameter indicating whether the wireless device is authenticated and / or authorized for aviation services. The AA status of the wireless device for air services may include a second parameter indicating whether the wireless device is certified and / or authorized for C2 of the air services.

[0224] In one embodiment, the SMF may receive a create SM context request message from the AMF. In an embodiment, the SMF may determine whether to accept or reject the create SM context request based on the AA status for the aeronautical services. The SMF may decide to accept the create SM context request if the AA status indicates that the wireless device is authenticated and / or authorized for the aeronautical services. The SMF may decide to reject the create SM context request if the AA status indicates that the wireless device is not authenticated and / or authorized for the aeronautical services. In one embodiment, the PDU session may be a higher priority PDU session (e.g., an emergency PDU session). The SMF may decide to accept the create SM context request if the AA status indicates that the wireless device is not authenticated and / or authorized for the aeronautical services.

[0225] Based on the determination, the SMF may send a create SM context response message to the AMF. The SM context response message may include a PDU session accept message. The SMF context response message may include a PDU session reject message. The PDU session reject message may include a cause parameter indicating that AA for the UAS of the wireless device has been cancelled or failed. The PDU session reject message may include a cause parameter indicating that AA for C2 for air services has been cancelled or failed.

[0226] In response to receiving the create SM context response message, the AMF may send a PDU session rejection message to the wireless device. In response to receiving the PDU session rejection message, the wireless device may send a confirmation message. In response to receiving the cause parameter, the wireless device may update an AA status for the air services of the wireless device. The wireless device may not request establishment of a PDU session associated with the air services. The wireless device may not request establishment of a PDU session associated with the air services prior to the AMF indicating that the air services have been (re)authenticated and (re)authorized. This exemplary embodiment may reduce potential PDU session rejections by indicating an AA status for the air services to the wireless device.

[0227] FIG. 22 illustrates a case in which the SMF determines to release one or more PDU sessions regarding the cancellation or failure of the AA (AA) for the air service. In one embodiment, the wireless device may request the establishment of one or more PDU sessions associated with the air service. The SMF may establish and accept the one or more PDU sessions associated with the air service. The SMF may then receive a first message from the network device indicating that the AA for the air service of the wireless device is cancelled or failed. In response to receiving the first message, the SMF may determine to release the one or more PDU sessions associated with the air service. Based on the determination, the SMF may send a second message to the wireless device to indicate the release of the one or more PDU sessions. The second message may include a cause parameter indicating that the AA for the air service of the wireless device has been cancelled or failed. The cause parameter may further indicate that the C2 AA for the air service of the wireless device has been cancelled or failed.

[0228] In one embodiment, the network device may be an AMF. The first message may be an Update Session Management (SM) Context Request message (Nsmf_PDU Session_Update SM Context). The Update SM Context Request message may include an SM context identity, user equipment (UE) location information, an indication indicating that the AA for the UAS has been cancelled or failed. The SM context identity may identify one or more PDU sessions. The SMF may send an Update SM Context Response message to the AMF including the second message. The second message may be a PDU Session Release Command message. The PDU Session Release Command message may include one or more PDU session identities, a cause parameter indicating that the AA for the air service has been cancelled or failed, and / or the like. In response to receiving the Update SM Context Response message, the AMF may send a PDU Session Release message to the wireless device. In response to receiving the PDU Session Release Command message, the wireless device may delete information associated with the one or more PDU sessions.

[0229] In one embodiment, the network device may be an AA server (e.g., UTM, USS) for an air service. The first message may be an AA (AA) cancellation request message. The AA cancellation request message may include an indication indicating that an AA of the air service of the wireless device has been cancelled or failed. The AA cancellation request message may further indicate that an AA of the command and control (C2) for the air service of the wireless device has been cancelled or failed. The AA cancellation request message may include an indication indicating that an AA of the command and control (C2) for the air service of the wireless device has been cancelled or failed. In response to receiving the AA cancellation request message, the SMF may determine release of one or more PDU sessions. Based on the determination, the SMF may invoke message delivery to the AMF by sending an N1N2 message transfer message including the second message. In response to receiving the N1N2 message transfer message from the SMF, the AMF may send a second message (e.g., a PDU session release command) to the wireless device.

[0230] In response to receiving the PDU session release command message, the wireless device may send a PDU session release complete message to the SMF. Based on the cause parameter, the wireless device may update the AA status for the air service of the wireless device. The wireless device may not request establishment of a PDU session associated with the air service. The wireless device may not request establishment of a PDU session associated with the air service before the AMF indicates that the air service has been (re)authenticated and (re)authorized. This exemplary embodiment may reduce potential PDU session rejections by indicating the AA status for the air service to the wireless device.

[0231] FIG. 23 illustrates an example session modification procedure for a 5G network and a wireless device regarding cancellation / failure of AA for an aeronautical service. The wireless device may be a UAV or a UAV controller. The SMF may send a message to the wireless device requesting modification of a PDU session. The PDU session may be associated with the aeronautical service. The message may be a PDU Session Modify Command message. The message may include a PDU session identity indicating the PDU session, a cause parameter indicating that the AA (AA) of C2 for the aeronautical service has been cancelled or failed, and / or the like. The message may further include one or more QoS flows to remove from the PDU session. In one embodiment, the one or more QoS flows may be associated with C2. The wireless device may receive the message from the SMF. The wireless device may delete the one or more QoS flows based on the message. In response to receiving the message, the wireless device may send a response message (e.g., PDU Session Modify Complete) to indicate completion of the modification. Based on the cause parameter, the wireless device may update the state of the aeronautical service to AA, where the AA of C2 has been cancelled or failed. Based on the cause parameter, the wireless device may not send a PDU session modification request message to obtain the C2 service. Based on the cause parameter, the wireless device may request modification of the PDU session to not request one or more QoS flows for C2. Example embodiments may reduce signaling exchanges by indicating the revocation / failure of AA of C2 to the wireless device during the modification procedure.

[0232] FIG. 24 illustrates a 4G system including an access network and a 4G core network (e.g., an evolved packet system). An exemplary 4G access network may include an access network that connects to a 5G core network. The access network may include a RAN. An exemplary 4G core network may connect to one or more 4G access networks. The 4G core network may include an MME, an HSS, a gateway (e.g., S-GW, PDN-GW), and / or the like. The MME may be a node responsible for the AMF and SMF functions of the 5G system. The gateway may be a node responsible for the UPF functions. The HSS may be a node responsible for the UDM functions. In one embodiment, a wireless device (e.g., UE) may attach to an MME by sending an attach request message to obtain a service from a 4G system. The wireless device may send a PDN connection request message to the MME to conduct a session with a data network (DN) via a gateway (e.g., S-GW, PDN-GW).

[0233] 25 illustrates an example session processing procedure for a 4G network and a wireless device for an AA failure for airline services. In one embodiment, the wireless device may perform the attach procedure by sending an attach request message to the MME. The MME may send an attach accept message to the wireless device in response to receiving the attach request message.

[0234] The wireless device may be a UAV. The wireless device may be a UAV controller. The wireless device may transmit a first message requesting establishment of a packet data network (PDN) connection associated with the aviation service. The first message may be a PDN connection request message for obtaining the aviation service (e.g., UTM / USS, communicating with C2 session / C2 service). The first message may include a UAS capability, a UAV identifier, and / or the like. The MME may receive the first message. In response to receiving the first message, the MME may send a second message to a PDN Gateway (P-GW) via a Serving Gateway (S-GW) requesting creation of a PDN connection. The second message may be a create session request message. The second message may include a protocol configuration option (PCO), an APN, a UAS capability, an AA state for the aviation service. In one embodiment, the protocol configuration option (PCO) may include information of the AA for the aviation service. The APN may be associated with the aviation service. In one embodiment, the P-GW may perform AA for the aviation service by sending an AA request message to an AA server (e.g., UTM / USS). The AA request message may include a UAV identifier, a PCO, and / or the like. The P-GW may receive an AA response message to the AA request. The AA response message may include a result for the AA request. The P-GW may decide whether to accept or reject the creation of the PDN connection. The decision may be based on the result. In one embodiment, if the result indicates that the AA for the aviation service has failed, the P-GW may decide to reject the creation of the PDN connection. Based on the decision, the P-GW may send a third message to the MME via the S-GW. The third message may be a create session response message. The third message may include the PCO, a result that the AA for the UAS has failed, and / or the like. In response to receiving the third message, the MME may send a fourth message indicating the rejection of the creation of the PDN connection.The fourth message may be based on the third message. The fourth message may be a PDN connection reject message. The fourth message may include a cause parameter indicating that the AA for the air service failed.

[0235] In an example implementation, the first message may be a PDN connection for the C2 service (e.g., a C2 session). The first message may include a second PCO including AA information for the C2 service. The APN of the first message may be associated with the C2 service. The P-GW may perform AA (AA) for the C2 service by sending an AA request message to an AA server. The AA request message may include a UAV identifier, a second PCO, a UAV identifier of a pairing UAV device, and / or the like. In one embodiment, the wireless device may be a UAV. If the wireless device is a UAV, the UAV identifier of the pairing UAV device may be a UAV identifier of a UAV controller of the wireless device. In one embodiment, the wireless device may be a UAV controller. If the wireless device is a UAV controller, the UAV identifier of the pairing UAV device may be a UAV identifier of a UAV of the wireless device. The P-GW may receive an AA response message for the AA request message. The AA response message may include a result for the AA request. The P-GW may decide whether to accept or reject the creation of the PDN connection. The decision may be based on the result. In one embodiment, if the result indicates that the AA for C2 has failed, the P-GW may decide to reject the creation of the PDN connection associated with the C2 service. Based on the decision, the P-GW may send a third message to the MME via the S-GW. The third message may be a create session response message. The third message may include a PCO, a result indicating that the AA for C2 has failed, and / or the like. In response to receiving the third message, the MME may send a fourth message indicating the rejection of the creation of the PDN connection. The fourth message may be based on the third message. The fourth message may be a PDN connection reject message. The fourth message may include a cause parameter. The cause parameter may be based on the result. The cause parameter may indicate that the AA for C2 has failed.

[0236] In an example implementation, the PDN connection associated with the aviation service may be a default PDN connection of the wireless device. If the PDN connection associated with the aviation service is a default PDN connection, the procedure shown in FIG. 25 may be performed as part of the attach procedure. The attach request message may include a first message (e.g., PDN connection request). AA for the aviation service may have failed. If the AA for the UAS has failed, the P-GW may reject the creation of the PDN connection. In response to receiving the third message indicating that the creation of the PDN connection has been rejected, the MME may send an attach rejection message to the wireless device. The attach rejection message may include a PDN connection rejection message, a cause value, and / or the like. The cause value may indicate that AA for the aviation service has failed.

[0237] FIG. 26 illustrates an example session processing procedure for a 4G network and a wireless device for cancellation of an AA for an aviation service and a C2 service. The wireless device may have one or more PDN connections associated with the aviation service or the C2 service. In one embodiment, the P-GW may detect the AA for the aviation service, or the AA for the C2 service may be cancelled or failed. In response to the detection, the P-GW may trigger a bearer deactivation procedure by sending a first message to the MME via the S-GW. The first message may be a delete bearer request message. The first message may include a cause parameter indicating that the AA for the aviation service or the AA for the C2 service is cancelled or failed. In response to receiving the first message, the MME may determine that the first message causes release of the last PDN connection of the wireless device. If the first message causes release of the last PDN connection, the MME may send a second message to the wireless device requesting disassociation of the wireless device. The second message may be a disassociation request message. The second message may include a cause parameter indicating that the AA for the aviation service has been cancelled or failed. The second message may include a cause parameter indicating that the AA for the C2 service has been cancelled or failed. In one embodiment, the wireless device or MME cannot support attach without a PDN connection. The first message may include a linked evolved packet system (EPS) bearer identifier (LBI), one or more EPS bearer identities, a cause parameter, and / or the like. In one embodiment, the cause parameter may further include a change in radio access technology (RAT) from 3rd Generation Partnership Project (3GPP) to non-3GPP. In one embodiment, the wireless device may receive a detach request message indicating that the AA for the aviation service has been cancelled or failed. The wireless device may send a second attach request message requesting reauthentication and reauthorization for the aviation service.Sending the second attach request message may be based on an indication (eg, that the AA for the air service is cancelled or fails).

[0238] In an example implementation, the MME may determine that the first message may not cause a release of the wireless device's last PDN connection. Based on the determination, the MME may send a third message requesting deactivation of the bearer. The fourth message may include a cause parameter. The third message may be a deactivate EPS bearer context request message.

[0239] In an example implementation, the MME and the wireless device may support an attach without a PDN connection. Based on the determination, the MME may send a fourth message requesting deactivation of the bearer. The fourth message may include a cause parameter. The fourth message may be a deactivate PES bearer context request message. The wireless device may send a deactivate PES bearer context acknowledge message to the MME in response to receiving the fourth message.

[0240] In one embodiment, a session management function (SMF) may receive a first message from a network device indicating that an AA (AA) for air services of the wireless device has been cancelled or failed. The SMF may decide to release one or more packet data unit (PDU) sessions. The SMF may decide to reject establishment of one or more PDU sessions. The decision may be based on the first message. The SMF may send a second message to the wireless device indicating the decision. The second message may include a cause parameter indicating that an AA for air services of the wireless device has been cancelled or failed.

[0241] According to an example embodiment, one or more PDU sessions may be associated with an air service.

[0242] According to an example embodiment, the network device may be an Access and Mobility Management Function (AMF). The first message may be a PDU Session Creation message. The first message may include a Subscriber Permanent Identifier (SUPI) or Permanent Equipment Identifier (PEI), a Data Network Name (DNN), an identifier of the AMF, a PDU Session Identity, a Session Management Container, an indication that the AA for the UAS has been revoked or failed, and / or the like. The Session Management Container may include a PDU Session Establishment Request message.

[0243] According to an example embodiment, the network device may be an Access and Mobility Management Function (AMF). The first message may be a PDU Session Update message. The first message may include a Session Management (SM) context identity, a User Equipment (UE) location information, an indication that the AA for the UAS has been revoked or failed, and / or the like.

[0244] According to an example embodiment, the SMF may receive a first Non-Access Stratum (NAS) message from the wireless device requesting establishment of a PDU session for an aeronautical service. The SMF may send a second NAS message to the wireless device accepting establishment of a PDU session for an aeronautical service. The first NAS message may include a Civil Aviation Authority (CAA) Unmanned Aerial Vehicle (UAV) identifier, a PDU session identity, a Subscriber Permanent Identifier (SUPI) or Permanent Equipment Identifier (PEI), a Data Network Name (DNN), single network slice selection assistance information, and / or the like.

[0245] According to an example embodiment, the network device may be an AA server for an air service. The network device may be a UAS Traffic Management (UTM) server. The network device may be an air service supplier (USS) server. The first message may be an AA cancellation request message. The AA cancellation request message may include an indication indicating that the AA for the air service of the wireless device has been cancelled or has failed. The indication may further indicate that the AA for the command and control (C2) of the wireless device has been cancelled or has failed.

[0246] According to an example embodiment, the wireless device may be an unmanned aerial vehicle (AAV).The wireless device may be an unmanned aerial vehicle (AAV) controller.

[0247] In one embodiment, the wireless device may receive from a session management function (SMF) a message requesting termination of a packet data unit (PDU) session. The message may include a cause parameter. The cause parameter may indicate that AA for air services (AA) of the wireless device has been canceled or failed. The cause parameter may indicate that AA for command and control (C2) of the wireless device has been canceled or failed. The wireless device may transmit a confirmation message indicating completion of the termination based on the message.

[0248] According to an example embodiment, the termination may be the release of an established PDU session, the message being a PDU session release command message.

[0249] According to an example embodiment, the wireless device may send a first Non-Access Stratum (NAS) message to the SMF requesting establishment of a PDU session for the aeronautical service. The wireless device may receive a second NAS message from the SMF accepting establishment of the PDU session for the aeronautical service.

[0250] According to an example embodiment, the termination may be a refusal to establish a PDU session.

[0251] In an example embodiment, the message may be a PDU session rejection message.

[0252] According to an example embodiment, the wireless device may update the AA status of the UAS and may be based on the cause parameters. The AA status of the UAS may include at least one of a first parameter indicating whether the wireless device is certified and / or authorized for aeronautical services and a second parameter indicating whether the wireless device is certified and / or authorized for C2 for aeronautical services.

[0253] In one embodiment, the wireless device may receive from a session management function (SMF) a message requesting release of a first packet data unit (PDU) session. The message may include a cause parameter indicating that an AA for air services (AA) has been cancelled or an AA for command and control (C2) for air services has been cancelled. Based on the message, the wireless device may transmit a confirmation message indicating completion of the release.

[0254] According to an example embodiment, the wireless device may determine, in response to a cause parameter indicating that an AA for the air service has been cancelled, without requesting establishment of a PDU session associated with the air service. The wireless device may determine, in response to a cause parameter indicating that an AA of C2 for the air service has been cancelled, without requesting establishment of a PDU session associated with the air service.

[0255] In one embodiment, the wireless device may send a registration request message including air service capabilities to an access and mobility management function (AMF). The wireless device may receive a registration reject message from the AMF indicating that the AA for air services (AA) has been cancelled or failed. The AA for air services may further include that the AA for air services (AA) has been cancelled or that the AA for command and control (C2) for air services has been cancelled.

[0256] In one embodiment, the wireless device may receive from a session management function (SMF) a message requesting modification of a packet data unit (PDU) session. The message may include a cause parameter indicating that an AA (AA) for command and control (C2) of the wireless device has been canceled or failed. The wireless device may transmit a confirmation message indicating completion of the termination based on the message.

[0257] According to an example embodiment, the cause parameter may further indicate that the AA (AA) for the air service has been cancelled.

[0258] In one example, a mobility management entity (MME) may receive a first message from a wireless device requesting establishment of a packet data network (PDN) connection associated with aviation services. The MME may send a second message to a serving gateway (S-GW) requesting creation of the PDN connection. The MME may receive a third message from the S-GW indicating a cause parameter that AA for the aviation services of the wireless device has been cancelled or failed. The MME may send a fourth message to the wireless device indicating rejection of establishment of the PDN connection. The fourth message may include the cause.

[0259] In one embodiment, the wireless device may send a first message to a mobility management entity (MME) requesting establishment of a packet data network (PDN) connection associated with an aviation service. The wireless device may receive a second message from the MME indicating a rejection of the request for establishment. The second message may include a cause parameter indicating that an AA for the aviation service of the wireless device has been cancelled or failed. The first message may be a PDN connection request message. The PDN connection request message may include a capability indication for the aviation service, a civil aviation authority (CAA) unmanned aerial vehicle (UAV) identifier, a packet data name (APN) associated with the aviation service, and / or the like. In one embodiment, the attach request message may include a PDN connection request message. The fourth message may be a PDN connection reject message. The PDN connection reject message may include a second cause parameter including a user authentication failed, an AA for the UAS failed or cancelled, an AA for command and control (C2) if failed or cancelled.

[0260] In one embodiment, the second message may be a leave request message. The PDN connection may be the last PDN connection of the wireless device.

[0261] In one embodiment, a mobility management entity (MME) may receive a first message from a serving gateway (S-GW) requesting release of bearers of a wireless device. The first message may include a cause parameter indicating that an AA (AA) for air services of the wireless device has been cancelled or failed. The MME may determine that the first message causes release of a last packet data network (PDN) connection of the wireless device. Based on the determination, the MME may send a second message to the wireless device requesting detachment of the wireless device, the second message including the cause parameter. The wireless device of the MME cannot support an attach without a PDN connection. The first message may be a delete bearer request message. The delete bearer request message may include a linked evolved packet system (EPS) bearer identifier (LBI), one or more EPS bearer identities, a cause parameter, and / or the like. The cause parameters may include an indication that AA for air services has been canceled or failed, an indication that AA for command and control (C2) has been canceled or failed, or an indication that the radio access technology (RAT) is changing from 3rd Generation Partnership Project (3GPP®) to non-3GPP®.

[0262] In one embodiment, the MME may determine that the first message may not result in release of a last packet data network (PDN) connection of the wireless device. Based on the determination, the MME may send a third message to the wireless device requesting deactivation of the bearer, the third message including a cause parameter.

[0263] In one embodiment, the MME may determine that the wireless device and the MME support an attach without a PDN connection. Based on the determination, the MME may send a fourth message to the wireless device requesting deactivation of the bearer, the fourth message including a cause parameter.

[0264] In one embodiment, the wireless device may receive a Leave Request message from a mobility management entity (MME) including a cause value indicating that AA of air services for the wireless device has been cancelled or failed. Based on the cause value, the wireless device may send an Attach Request message to the MME requesting re-authentication and re-authorization for air services. The wireless device may send a Leave Request Acknowledge message to the MME, the Leave Request Acknowledge message being responsive to receipt.

[0265] The disclosure may refer to possible combinations of the listed elements. For the sake of brevity and readability, the disclosure does not explicitly describe each and every variation that may be obtained by selecting from a set of optional features. The disclosure should be construed as explicitly disclosing all such variations. For example, the seven possible combinations of the listed elements A, B, and C consist of (1) "A", (2) "B", (3) "C", (4) "A and B", (5) "A and C", (6) "B and C", and (7) "A, B, and C". For the sake of brevity and readability, these seven possible combinations may be described using any of the following interchangeable formulations: "at least one of A, B, and C", "at least one of A, B, or C", "one or more of A, B, and C", "one or more of A, B, or C", "A, B, and / or C". It will be understood that impossible combinations are excluded. For example, "X and / or not X" should be interpreted as "X or not X." Furthermore, it will be appreciated that these formulations may describe overlapping and / or synonymous concepts, e.g., alternative expressions of "identifier, identification, and / or ID number."

[0266] In this specification, "a" and "an" and similar terms are interpreted as "at least one" and "one or more". In this specification, the term "may" is interpreted as "may, for example." In other words, the term "may" indicates that the term following the term "may" is one example of multiple suitable possibilities, which may or may not be used for one or more of the various embodiments. If A and B are sets, and all elements of A are also elements of B, then A is said to be a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the possible subsets of B={cell1, cell2} are {cell1}, {cell2}, and {cell1, cell2}. In this specification, a parameter (information element: IE) is composed of one or more objects, each of which is composed of one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element) J, then for example, N includes K and N includes J. In an exemplary embodiment, when one or more messages include multiple parameters, it means that a parameter of the multiple parameters is included in at least one of the one or more messages, but need not be included in each of the one or more messages. Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined herein as a separable element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e., hardware with biological elements), or a combination thereof, which may be behaviorally equivalent. For example, a module may be implemented in a software routine written in a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a computer language configured to run on Simulink, Stateflow, GNU Octave, or LabVIEW MathScript.Additionally, it may be possible to implement modules using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages ​​(HDLs) such as VHSIC Hardware Description Language (VHDL) or Verilog that configure connections between less functional internal hardware modules of the programmable device. Finally, it should be emphasized that the above techniques are often used in combination to achieve functional modular results. Exemplary embodiments of the present invention may be implemented using a variety of physical and / or virtual network elements, software defined networking, and virtual network functions. The disclosure of this patent document incorporates material that is subject to copyright protection. The copyright owner has no objection to anyone facsimile reproduction of the patent document or patent disclosure as it appears in the patent or trademark office patent file or records, for the limited purposes required by law, but otherwise reserves all and any copyrights. Although various embodiments have been described above, it should be understood that they are presented by way of example and not limitation. It will be apparent to one skilled in the relevant art(s) that various changes in form and details can be made without departing from the concept and scope. Indeed, after reading the above specification, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiment should not be limited by any of the exemplary embodiments described above. In particular, it should be noted that for illustrative purposes, the above description focuses on an example using a 5G AN.However, those skilled in the art will recognize that embodiments of the present invention may also be implemented in one or more legacy systems or systems including LTE. The disclosed methods and systems may be implemented in wireless or wired systems. Features of the various embodiments presented in this disclosure may be combined. One or many features (methods or systems) of one embodiment may be implemented in other embodiments. A limited number of example combinations are shown to show those skilled in the art the possibility of features that may be combined in various embodiments to create enhanced transmission and reception systems and methods. Furthermore, it should be understood that any diagrams that highlight features and advantages are presented for illustrative purposes. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, the actions listed in any flowchart may be rearranged or used in some embodiments. Furthermore, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the general public, particularly scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or jargon, to quickly determine the nature and substance of the technical disclosure of the present application at a glance. The Abstract of the Disclosure is not intended to be limiting in any way. Finally, it is Applicant's intention that only those claims which expressly include the words "means for" or "step for" be construed under 35 U.S.C. 112. Any claim which does not expressly include the phrase "means for" or "step for" is not to be construed under 35 U.S.C. 112.

Claims

1. 1. A method comprising: A wireless device transmits a registration request message for the wireless device to an Access and Mobility Management Function (AMF); The wireless device transmits a protocol data unit (PDU) session establishment request to the AMF to establish a PDU session associated with an aviation service, the transmitting being after an authentication and / or authorization procedure for the aviation service of the wireless device is confirmed; and receiving, from the AMF, first information indicating an acceptance or rejection of the PDU session establishment request, the rejection or acceptance of the PDU session establishment request being based on second information indicating whether the air services of the wireless device are certified and / or authorized by a crewless air system service supplier (USS); The method includes:

2. 2. The method of claim 1, wherein the first information is received in a PDU session rejection message.

3. The method of claim 2, further comprising marking an uncrewed air system (UAS) certification and / or authorization (AA) status as revoked or failed based on the first information when the first information is received and the first information indicates a rejection.

4. 2. The method of claim 1, wherein the PDU session is for communicating with a service supplier that provides the air service, or the PDU session is for command and control (C2) communication of the air service.

5. 2. The method of claim 1, wherein the air services of the wireless device are authenticated and / or authorized using a procedure that includes the AMF sending an authentication and / or authorization request to the USS.

6. The method of claim 5 , wherein the authentication and / or authorization request includes an aircraft identifier for the wireless device.

7. The method of claim 5 , wherein the authentication and / or authorization request includes a Universal Public Subscription Identifier (GPSI) of the wireless device.

8. 2. The method of claim 1, wherein the first information is received in a PDU session release message.

9. The method of claim 8, further comprising: sending a PDU session release complete message to a session management function (SMF) in response to the first information.

10. The method of claim 8, further comprising marking an uncrewed air system (UAS) certification and / or authorization (AA) status as revoked or failed based on the first information when the first information is received and the first information indicates a rejection.

11. 1. A wireless device, comprising: The wireless device comprises one or more processors and a memory for storing instructions; The instructions, when executed by the one or more processors, transmitting a registration request message for the wireless device to an Access and Mobility Management Function (AMF); transmitting a protocol data unit (PDU) session establishment request to the AMF to establish a PDU session associated with an aviation service, the transmitting being after an authentication and / or authorization procedure for the aviation service of the wireless device is confirmed; and receiving, from the AMF, first information indicating an acceptance or rejection of the PDU session establishment request, the rejection or acceptance of the PDU session establishment request being based on second information indicating whether the air services of the wireless device are certified and / or authorized by a crewless air system service supplier (USS); The wireless device is caused to perform the above.

12. 12. The wireless device of claim 11, wherein the first information is received in a PDU session reject message.

13. 13. The wireless device of claim 12, wherein the instructions further cause the wireless device to mark a crewless air system (UAS) authentication and / or authorization (AA) status as revoked or failed based on the first information if the first information is received and the first information indicates a denial.

14. The wireless device of claim 11, wherein the PDU session is for communicating with a service supplier that provides the aviation service, or the PDU session is for command and control (C2) communication of the aviation service.

15. 12. The wireless device of claim 11, wherein the air services of the wireless device are authenticated and / or authorized using a procedure that includes the AMF sending an authentication and / or authorization request to the USS.

16. The wireless device of claim 15 , wherein the authentication and / or authorization request includes an aircraft identifier for the wireless device.

17. The wireless device of claim 15 , wherein the authentication and / or authorization request includes a Universal Public Subscription Identifier (GPSI) of the wireless device.

18. The wireless device of claim 11 , wherein the first information is received in a PDU session release message.

19. 20. The wireless device of claim 18, wherein the instructions further cause the wireless device to mark a crewless air system (UAS) authentication and / or authorization (AA) status as revoked or failed based on the first information if the first information is received and the first information indicates a denial.

20. A non-transitory computer-readable medium containing instructions that, when executed by one or more processors of a wireless device, transmitting a registration request message for the wireless device to an Access and Mobility Management Function (AMF); transmitting a protocol data unit (PDU) session establishment request to the AMF to establish a PDU session associated with an aviation service, the transmitting being after an authentication and / or authorization procedure for the aviation service of the wireless device is confirmed; and receiving, from the AMF, first information indicating an acceptance or rejection of the PDU session establishment request, the rejection or acceptance of the PDU session establishment request being based on second information indicating whether the air services of the wireless device are certified and / or authorized by a crewless air system service supplier (USS); A non-transitory computer-readable medium that causes the wireless device to

Images