RULES

TECHNICAL FIELD

The present invention relates generally to wireless communication networks, and in particular to a UE’s handling of an established security context upon Access and Mobility Management Function (AMF) reallocation.

BACKGROUND

Wireless communication networks provide voice and data communication between a network of fixed nodes and a large number of mobile, wireless devices, such as mobile telephones, smartphones, laptop and tablet computers, wearable devices, vehicles, and the like. Successive generations of technical specifications and protocols for wireless cellular communication networks are established, maintained, and promulgated by the Third Generation Partnership Project (3GPP). At a very high level, wireless cellular communication networks standardized by 3GPP can be characterized as comprising a (large number of) user equipment (UE), a radio access network (RAN), and core network (CN). See the block diagram of Figure 1. The UE is a stationary or mobile device which wirelessly accesses the network. Although denominated“user” equipment, UE more broadly includes machine type communications (MTC) devices which are embedded in equipment, vehicles, and the like, and which have no“user” or even user interface. The RAN comprises base stations (BSs), also known as eNB or gNB, which provide wireless radio communication service to the UEs and connect the UEs to the core network. The CN comprises several types of core network functions which are responsible for various functions such as handling the mobility of the UE, e.g. the AMF (Access and Mobility Management Function), interconnecting to other data networks such as the Internet, packet routing and forwarding, paging, authentication, billing, and many other responsibilities.

Wireless cellular communication networks, also referred to herein as mobile networks, are operated by the so-called mobile network operators (MNOs). To use a particular mobile network offered by a particular MNO, users are required to have a contractual relationship with that MNO, that relationship being generally called the subscription.

In simple terms, the business model works as follows. The MNOs provide services to the users with valid subscriptions. These users use the services, e.g., send and receive Short Message System (SMS) messages (commonly called“texting”), make and receive phone calls, access the Internet, and the like. The MNOs charge these users for the services they have used through the MNOs' billing or charging systems. The users pay according to the billed amount.

This business model is supported by several security features built into the mobile networks. For example, the network can authenticate the users and determine if they have valid subscriptions. The traffic belonging to services such as SMS, phone calls, internet data, etc., are transported in a secure way so that the users are billed correctly according to their usage of the traffic.

Network traffic may be classified into two general types - control plane (CP) and user plane (UP). The control plane traffic, used for management of traffic in the network, is also referred to as overhead. User plane traffic carries the actual data which is delivered to users. The secure transport of the traffic is achieved by confidentiality/ciphering and integrity protection. Confidentiality/ciphering in this context means encryption of messages, which makes it infeasible for unauthorized parties to decrypt and read the original messages. Integrity protection in this context means the sender adding a security token or a message authentication code (MAC) to a message that the receiver can verify, which makes it infeasible for

unauthorized parties to tamper with the original message without the receiver detecting the tampering.

A UE is typically connected to a single base station in order to use the mobile network services such phone calls, messaging, and data transmissions. When a UE does not have any data to send, its connection is idle.

For the UE to join a network, a registration procedure takes place as a first step. The detailed registration procedure is outlined in 3GPP Technical Standard (TS) 23.502, v.16.0.2, § 4.2.2.2.2“General Registration.” Figure 4.2.2.2.2-1 ,“Registration procedure,” from that section is reproduced for convenience in Figure 2. The registration is to the above-mentioned core network function known as the Access and Mobility Management Function (AMF).

A feature of 5G mobile networks is network slicing. Network slicing is an important capability to bring network resource utilization efficiency, deployment flexibility, and support fast growing over the top (OTT) applications and services. A network slice is viewed as a logical end-to-end network that can be dynamically created. A given UE may access multiple slices over the same RAN. Each slice may serve a particular service type with agreed upon Service- level Agreement (SLA). A Network Slice is defined within a Public Land Mobile Network (PLMN) and includes the Core Network Control Plane and User Plane Network Functions as well as the 5G Access Network (AN).

In some cases, for example due to slicing requirements, or AMF set deployment constraints, a UE cannot continue to be served by the Initial AMF with which it registered. This is covered in said TS 23.502, in § 4.2.2.2.3“Registration with AMF re-allocation.” Figure 4.2.2.2.3-1 :“Registration with AMF re-allocation procedure” from that section is reproduced for convenience in Figure 3.

The AMF re-allocation procedure outlined in Figure 3 results in the UE and Initial AMF sharing a security context after step 2 in Figure 3 or after step 9 in Figure 2. Therefore, encryption and integrity protection keys that could be used for the secure communication between the UE and the Initial AMF remain valid. The last part of step 9 in Figure 2 is the Non- Access Stratum (NAS) Security Mode Command (SMC) that takes the security context into use between the UE and the Initial AMF. After the NAS SMC procedure, the Initial AMF receives the initial registration request which may have slicing information, such a Network Slice Selection Assistance Information (NSSAI). Based on this slicing information, the Initial AMF may determine that it is not the proper AMF to serve the UE, and so it performs a look-up for an appropriate AMF (steps 6a, 6b in Figure 3).

A problematic situation is case (B) in Figure 3, when the Target AMF (the AMF that was discovered to fulfil the requirements to serve the UE with respect to slicing) cannot be contacted by the Initial AMF, in order to transfer the security context shared between the UE and the Initial AMF. As a result, step 8 in Figure 3 will be followed, which implies that the Target AMF will attempt to authenticate the UE again by issuing an unprotected NAS message, i.e. an

AUTHENTICATION REQUEST (AUTHRQ). According to the rules in TS 24.501 , v.16.0.2,

§ 4.4.4.2“Integrity checking of NAS signaling messages in the UE” this unprotected AUTHRQ message will be dropped by the UE, since it already has a security context with the network (although it is with the Initial AMF, not the Target AMF).

Note that in the case (A) in Figure 3, there is no problem since the security context is transferred from the Initial AMF to the Target AMF. Therefore, the Target AMF - whether or not it decides to re-authenticate the UE - has the security context with which it could protect the AUTHRQ message.

This problem has been recognized and is documented in the contribution 3GPP TDoc S3-19141 1. One solution has been proposed in contribution 3GPP TDoc S3-191413. The problem with solution S3-191413 is that it introduces a new message,“AMF reallocation notification message,” which causes the UE to delete the security context shared between itself and the Initial AMF. This solution is not ideal since the UE removes a working security context before the next security context is established.

The Background section of this document is provided to place embodiments of the present invention in technological and operational context, to assist those of skill in the art in understanding their scope and utility. Approaches described in the Background section could be pursued but are not necessarily approaches that have been previously conceived or pursued. Unless explicitly identified as such, no statement herein is admitted to be prior art merely by its inclusion in the Background section.

SUMMARY

The following presents a simplified summary of the disclosure in order to provide a basic understanding to those of skill in the art. This summary is not an extensive overview of the disclosure and is not intended to identify key/critical elements of embodiments of the invention or to delineate the scope of the invention. The sole purpose of this summary is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later.

According to various embodiments of the present invention disclosed and claimed herein, a UE having a security context with an Initial Access and Mobility Management Function (AMF) is able to accept an unprotected NAS message, AUTHRQ, under certain circumstances, for a limited time. In one embodiment, a UE considers a security context between the Initial AMF and the UE to be temporary, which invokes rules or exceptions different than a permanent security context, such as the acceptance of an unprotected AUTHRQ from a Target AMF. The network may indicate to the UE the temporary status, or the UE may assume it. Alternatively, the UE may not mark the security context as temporary but may have exceptions to the defined rules associated with it. In another embodiment, the UE receives a plurality of partial registration acceptance messages, each indicating a specific task or aspect of the overall registration has been completed. The UE may mark its security context temporary, or enable exceptions to the rules associated with it, until a partial registration acceptance messages indicates AMF reallocation is complete or is not required. In another embodiment, the UE accepts unprotected authentication messages from the network until the Registration procedure is completed, enabling a Target AMF to successfully send it an unprotected AUTHRQ.

One embodiment relates to a method, performed by a wireless device, of registering with a wireless communication network. A registration request message is sent to the network. A first security context is established with a first network Access and Mobility Management Function (AMF). A cryptographically unprotected authentication request message is received from a second AMF. The unprotected authentication request message is processed.

Another embodiment relates to a wireless device operative in a wireless communication network. The wireless device includes communication circuitry and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to send a registration request message to the network; establish a first security context with a first network Access and Mobility Management Function (AMF); receive a cryptographically unprotected authentication request message from a second AMF; and process the unprotected authentication request message.

Yet another embodiment relates to a method, performed by a base station operative in a wireless communication system, of performing registration and AMF re-allocation for a wireless device. A registration request message is received from the wireless device. A first security context is established between the wireless device and a first network Access and Mobility Management Function (AMF). A cryptographically unprotected authentication request message is sent to the wireless device from a second AMF. Messages sent by the wireless device pursuant to processing the unprotected authentication request message are received.

Still another embodiment relates to a base station operative in a wireless communication system. The base station includes communication circuitry and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to receive from the wireless device a registration request message; establish a first security context between the wireless device and a first network Access and Mobility Management Function (AMF); send to the wireless device a cryptographically unprotected authentication request message from a second AMF; and receive messages sent by the wireless device pursuant to processing the unprotected authentication request message.

Still another embodiment relates to a method, performed by a core network node operative in a wireless communication network and implementing network Access and Mobility Management Function (AMF). An AMF reallocation indication for a wireless device already allocated to an Initial AMF is received. In response to failure to communicate with the Initial AMF, a cryptographically unprotected authentication request message is sent to the wireless device. In response to the wireless device not discarding the cryptographically unprotected authentication request message, a message is received from the wireless device. In response to the message from the wireless device, a security context is established with the wireless device.

Still another embodiment relates to a network node implementing network Access and Mobility Management Function (AMF) in a wireless communication network. The network node includes communication circuitry and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to receive an AMF reallocation indication for a wireless device already allocated to an Initial AMF; in response to failure to communicate with the Initial AMF, send to the wireless device a cryptographically unprotected authentication request message; in response to the wireless device not discarding the cryptographically unprotected authentication request message, receive a message from the wireless device; and in response to the message from the wireless device, establish a security context with the wireless device.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. However, this invention should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

Figure 1 is a block diagram of a wireless communication network.

Figure 2 is Fig. 4.2.2.2.2-1 from 3GPP TS 23.502, v.16.0.2.

Figure 3 is Fig. 4.2.2.2.3-1 from 3GPP TS 23.502, v.16.0.2.

Figure 4 is a signaling diagram showing a security context being considered temporary or having exceptions to rules associated with it. Figure 5 is a signaling diagram showing partial registration accept messages.

Figure 6 is a signaling diagram showing a UE accepting unprotected authentication messages throughout AMF reallocation.

Figure 7 is a flow diagram of steps in a method of registering with a wireless communication network.

Figure 8 is a flow diagram of steps in a method of performing registration and AMF re allocation for a wireless device.

Figure 9 is a hardware block diagram of a wireless device.

Figure 10 is a functional block diagram of a wireless device.

Figure 1 1 is a hardware block diagram of a network node.

Figure 12 is a functional block diagram of a network node.

Figure 13 is a diagram of a wireless network.

Figure 14 is a block diagram of a UE.

Figure 15 is a schematic block diagram illustrating a virtualization environment.

Figure 16 illustrates a telecommunication network connected via an intermediate network to a host computer.

Figure 17 illustrates host computer communicating via a base station with a user equipment over a partially wireless connection.

Figure 18 is a flowchart illustrating a method implemented in a communication system. Figure 19 is a flowchart illustrating another method implemented in a communication system.

Figure 20 is a flowchart illustrating yet another method implemented in a communication system.

Figure 21 is a flowchart illustrating still another method implemented in a communication system.

DETAILED DESCRIPTION

For simplicity and illustrative purposes, the present invention is described by referring mainly to exemplary embodiments thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be readily apparent to one of ordinary skill in the art that the present invention may be practiced without limitation to these specific details. In this description, well known methods and structures have not been described in detail so as not to unnecessarily obscure the present invention.

Several embodiments of the present invention will now be described. At least some of these embodiments may be described as applicable in certain contexts and/or wireless network types for illustrative purposes, but the embodiments are similarly applicable in other contexts and/or wireless network types not explicitly described. Temporary Security Context or Exceptions Enabled Throughout Registration

One embodiment of the present invention is based on the observation that the main cause of the problem is that the UE and the network already share security context but the network function which holds the context (Initial AMF) cannot transfer it to the Target AMF.

Figure 4 depicts an embodiment in which the network notifies the UE that the security context produced between the Initial AMF and the UE is temporary, until any potential AMF re allocation issues are resolved.

This may be achieved by the Security Mode Command (step 9 in Figure 2 and steps 2a and 2b in Figure 4) carrying an indication that the security context has a state of“temporary.” In one embodiment, the UE uses this security context to contact the network securely, but it does not use the existence of this temporary security context as a criterion to drop unprotected AUTHRQ message that may originate from another AMF in the network, in this case the Target AMF.

A generalized version of this embodiment is that the UE enables exceptions to the rules of 3GPP TS 24.501 § 4.4.4.2“Integrity checking of NAS signaling messages in the UE” due to potential pending AMF re-allocation, one example exception being the acceptance of unprotected AUTHRQ. The UE actions when receiving such an indication are more general than those known in the prior art (i.e. deleting the context). By marking the context as temporary, the UE can use it, but still be able to update it with a new AUTHRQ procedure.

When the UE actually receives a RegistrationAccept message (step 21 , Figure 2), or new special message for that purpose, with a special indication to the UE, it removes the exceptions, and invalidates or delete the temporary security context (Step 10, Figure 4), since by this time the AMF re-allocation is performed and there is a new security context between the Target AMF and the UE (case (B). In case (A) in Figure 4, the old security context is

successfully transferred to the Target AMF so in Step 10, Figure 4 the UE maintains the context as is, making it current).

In another embodiment, the NAS Security Mode Command (SMC) does not carry any indication, but the UE marks the security context as temporary after the NAS SMC in any case. The UE having a temporary security context changes its behavior by adding a few more rules, at least with respect to the handling unprotected AUTHRQ. In one embodiment, the change in the behavior is to accept an unprotected AUTHRQ. Of course, other rules and exceptions are also possible for the UE to add when a security context is temporary. The exception for a UE to accept an unprotected AUTHRQ may be used“as is,” or upon conditions. For example, in one embodiment the UE always considers the security context after NAS SMC as temporary (with all the implications on exceptions that this situation may have). In another embodiment, it only marks the security context as temporary in the case that it expects that an AMF re-allocation is expected due to slicing. In another embodiment, if the UE indicates slicing information in the Registration Request, it knows an AMF re-allocation is possible, so the UE considers the security context temporary upon NAS SMC, and accepts unprotected AUTHRQ. In any other case, the UE considers the security context upon NAS SMC as current.

In any case, when the security context is considered temporary in any stage of the Registration procedure, any exceptions will be removed and the security context shared with the Initial AMF will be transitioned to another state (e.g., current), or invalidated/deleted, when the RegistrationAccept message is received, or upon another new message carrying an appropriate indication. The RegistrationAccept or new message could indicate that the Initial AMF security context should be invalidated or deleted, or left as is (if it has been transferred to the New AMF). Alternatively, the RegistrationAccept or new message could indicate that exceptions introduced in an earlier stage (e.g., that the UE process an unprotected AUTHRQ) should be removed.

This new message could be a completely newly defined message, or an existing message (e.g. UE Configuration Update command) with the appropriate parameters could be used for such purposes.

According to embodiments of the present invention, the UE is provided exceptions to the normal handling of NAS messages when the UE shares some existing security context with the network. In various embodiments, two mechanisms are employed to achieve this goal - marking the existing security context (e.g., as temporary), and defining/enabling exceptions to the UE’s behavior with respect to handling security-related tasks. Which mechanism will be deployed in any particular situation may depend e.g. on the standardization procedures and other factors. However, both are disclosed and explained below.

Temporary context marking: The current security context shared between the UE and the Initial AMF is marked as temporary (or by some other label). This marking implies that this type of security context has special rules, or exceptions to rules, regarding the handling of received NAS messages from the network. For example, the main rules are defined in 3GPP TS 24.501 , § 4.4.4.2“Integrity checking of NAS signalling messages in the UE.” Exceptions to these rules, which are deployed by a UE whose security context has been marked temporary, are determined either by hardcoded rules in a specification, or exceptions explicitly sent by the network. One particularly relevant example of such an exception is allowing received, unprotected AUTHRQ messages to be processed by the UE. Other exceptions are also possible.

Exceptions only: The UE may leave the current security context state as is, but when it receives a NAS message from the network, aside from referencing the standardized rules (e.g., 3GPP TS 24.501 , § 4.4.4.2) the UE checks a list of exceptions to those rules that the network has provided. In contexts outside the scope of the present disclosure, such exception check may still be implemented, but the list of exceptions is empty.

Accordingly, there are two options for the UE when instructed by the network. First, the UE may mark the security context as temporary. In this case, the UE may use configured or hardcoded exceptions to defined/standardized rules when the context is marked as temporary, or alternatively, it may use exceptions provided by the network via an explicit mechanism, such as dedicated signaling. Second, the UE may enable exceptions to the defined/standardized rules - essentially defining new, or exception, rules. These exception rules may be hardcoded or pre-configured in the UE, or alternatively they may be provided by the network via an explicit mechanism, such as dedicated signaling.

Partial Registration Accept Messages

Another embodiment of the present invention is based on the observation that the registration reguest message (in step 1 of Figure 2) includes a lot of other sub-reguests apart from the security establishment reguest, e.g., slicing (which may cause AMF re-allocation), PDU session management, etc.

Figure 5 depicts an embodiment in which a new general message called, e.g., partialRegistrationAccept is sent by the network to the UE, to notify the UE about which of these sub-reguests have succeeded/completed so far, and which are pending. In one embodiment, the UE maintains a general state machine for handling its state based on which reguests are completed. An example of this general message is a partialRegistrationAccept message sent after the authentication completion, to indicate that the authentication is complete (step 2a, Figure 5). Another example (not shown in Fig. 5) is that the partialRegistrationAccept message is sent after the Security Mode Command, indicating that the security context is established. Yet another example is the partialRegistrationAccept message being sent after the AMF re allocation to indicate that the AMF re-allocation is complete (step 7c, Figure 5). One example of this is case (A) in Figure 5, in which the security context is transferred from the Initial AMF to the Target AMF. This message may also indicate the outcome of the AMF re-allocation, e.g., if there was no re-allocation (e.g. step 7c, Figure 5) or there was a re-allocation to a new AMF.

The UE decides the appropriate actions to take in each case.

In one embodiment, when a partialRegistrationAccept() message is received which indicates that the Security Mode Command is complete and the AMF re-allocation is pending, that the UE marks its security context as temporary, and adds exceptions to the rules of 3GPP TS 24.501 § 4.4.4.2“Integrity checking of NAS signalling messages in the UE”. This behavior is as described above with respect to Embodiment 1.

In one embodiment, the Initial AMF delays the transmission of the

partialRegistrationAccept until it verifies whether an AMF re-allocation is required or not. It then notifies the UE that the AMF re-allocation check is complete, with the result that no AMF re allocation should take place. In this case, the UE makes the temporary security context a permanent one, and removes any exceptions. In the case that the partialRegistrationAccept message indicates that an AMF re-allocation is required (similar to the prior art special message “AMF re-allocation message”), the UE keeps the exceptions active until a partialRegistrationAccept 0 message is received with the indication that AMF re-allocation is completed, or until the final RegistrationAccept message is received.

At the completion of the registration procedure, when the UE can be considered fully registered and all the sub-requests served, the network sends a RegistrationAccept message (step 9, Figure 5), which is equivalent to a partialRegistrationAccept indicating that all the subrequests have completed. The UE then invalidates or delete any temporary context, since there is already a new context between the UE and the Target AMF (case (B), Figure 5). In case (A) in Figure 5 the old security context is successfully transferred to the Target AMF so in Step 10, Figure 5 the UE maintains the context as is.

Unprotected Authentication Allowed Throughout Registration

Another embodiment of the present invention allows unprotected authentication messages from the network until the Registration procedure is completed. Figure 6 illustrates the actions undertaken by the UE in this embodiment.

First, the UE sends the Initial UE message as described in step 1 of Figure 6. In addition, the UE starts allowing unprotected authentication messages from the network. Note that steps 1a and 1 b of Figure 6 could be performed in a different order, but they should be related. In other words, if the UE performs step 1 b, it is because it has prepared an Initial UE Message in order to perform step 1 a.

Next, the steps 2-8 of the AMF reallocation procedure in Figure 6 take place, including the possibility that either case (A) or case (B) steps are performed.

Finally, the UE disallows unprotected authentication messages from the network.

The UE may track and control the timing and duration of allowing the reception of unprotected authentication messages from the network in a variety of ways. In one embodiment, upon the transmission of a Registration Request, the UE sets an internal flag in step 1 b, which is cleared upon the reception of the final message, i.e., a Registration Accept or a Registration Reject message in step 3.

Alternatively, a new state of the security context (e.g., temporary) is introduced as described in Embodiment 1 or Embodiment 2, and in which the UE allows unprotected authentication messages from the network. This state is entered in step 1 and exited in step 3.

Note that on the network side, in case (B), the target AMF does not have the security context. Accordingly, the network will process the authentication messages from the UE whether they are protected or not.

Methods and Apparatuses

Figure 7 depicts a method 100 in accordance with particular embodiments. The method, performed by a wireless device, is for registering with a wireless communication network. A registration request message is sent to the network (block 102). A first security context with a first network Access and Mobility Management Function (AMF) is established (block 104). A cryptographically unprotected authentication request message is received from a second AMF (block 106). The unprotected authentication request message is processed (block 108).

Figure 8 depicts a method 200 in accordance with other particular embodiments. The method, performed by a base station operative in a wireless communication system, is for performing registration and AMF re-allocation for a wireless device. A registration request message is received from the wireless device to the network (block 202). A first security context between the wireless device and a first network Access and Mobility Management Function (AMF) is established (block 204). A cryptographically unprotected authentication request message is sent to the wireless device (block 206). Messages sent by the wireless device pursuant to processing the unprotected authentication request message are received (block 208).

Note that apparatuses described herein may perform the methods 100, 200 herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

Figure 9 for example illustrates a wireless device 10, such as a UE, as implemented in accordance with one or more embodiments. As shown, the wireless device 10 includes processing circuitry 12 and communication circuitry 16. The communication circuitry 16 (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas 18 that are either internal or external to the wireless device 10. The processing circuitry 12 is configured to perform processing described above, such as by executing instructions stored in memory 14. The processing circuitry 12 in this regard may implement certain functional means, units, or modules. Figure 10 illustrates a schematic block diagram of a wireless device 20 in a wireless network according to still other embodiments (for example, the wireless network shown in Figure 13). As shown, the wireless device 20 implements various functional means, units, or modules, e.g., via the processing circuitry 12 in Figure 7 and/or via software code. These functional means, units, or modules, e.g., for implementing the method(s) herein, include for instance: registration request sending unit 22, security context establishing unit 24, AUTHRQ receiving unit 26, and AUTHRQ processing unit 28.

Registration request sending unit 22 is configured to send a registration request message to the network. Security context establishing unit 24 is configured to establish a first security context with a first network Access and Mobility Management Function (AMF).

AUTHRQ receiving unit 26 is configured to receive a cryptographically unprotected

authentication request message from a second AMF. AUTHRQ processing unit 26 is configured to process the unprotected authentication request message.

Figure 1 1 illustrates a network node 30, which may for example comprise a base station, as implemented in accordance with one or more embodiments. As shown, the network node 30 includes processing circuitry 32 and communication circuitry 36. The communication circuitry 36 is configured to transmit and/or receive information to and/or from one or more wireless devices 10 and/or other nodes, e.g., via any communication technology. The communication circuitry 36 may comprise Radio Frequency (RF) transceivers operative to communicate with wireless devices 10 or other network nodes via one or more antennas 38. As indicated by a broken line, the antennas 38 may be mounted remotely from the network node 30, such as on a tower or building. The processing circuitry 32 is configured to perform processing described above, such as by executing instructions stored in memory 34. The processing circuitry 32 in this regard may implement certain functional means, units, or modules.

Figure 12 illustrates a schematic block diagram of a core network node 40, which may comprise an AMF, in a wireless network according to still other embodiments (for example, the wireless network shown in Figure 13). As shown, the network node 40 implements various functional means, units, or modules, e.g., via the processing circuitry 32 in Figure 1 1 and/or via software code. These functional means, units, or modules, e.g., for implementing the method(s) herein, include for instance: registration request receiving unit 22, security context establishing unit 24, AUTHRQ sending unit 26, and message processing unit 28.

Registration request receiving unit 42 is configured to receive from the wireless device a registration request message. Security context establishing unit 44 is configured to establish a first security context between the wireless device and a first network Access and Mobility Management Function (AMF). AUTHRQ sending unit 46 is configured to send to the wireless device a cryptographically unprotected authentication request message from a second AMF. Message processing unit 48 is configured to receive messages sent by the wireless device pursuant to processing the unprotected authentication request message. Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 13. For simplicity, the wireless network of Figure 13 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ1 10, QQ1 10b, and QQ1 10c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ1 10 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-loT), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.1 1 standards; and/or any other appropriate wireless communication standard, such as the

Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks

(WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node QQ160 and WD QQ1 10 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In Figure 13, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of Figure 13 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example,

GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.

Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Processing circuitry QQ170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ1 10. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node QQ160 may include additional components beyond those shown in Figure 13 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device QQ1 10 includes antenna QQ1 1 1 , interface QQ1 14, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ1 10 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ1 10, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-loT, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ1 10.

Antenna QQ1 1 1 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ1 14. In certain alternative embodiments, antenna QQ1 1 1 may be separate from WD QQ1 10 and be connectable to WD QQ1 10 through an interface or port. Antenna QQ1 1 1 , interface QQ1 14, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ1 1 1 may be considered an interface.

As illustrated, interface QQ1 14 comprises radio front end circuitry QQ1 12 and antenna QQ1 1 1. Radio front end circuitry QQ1 12 comprise one or more filters QQ1 18 and amplifiers QQ1 16. Radio front end circuitry QQ1 14 is connected to antenna QQ1 1 1 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ1 1 1 and processing circuitry QQ120. Radio front end circuitry QQ1 12 may be coupled to or a part of antenna QQ1 1 1. In some embodiments, WD QQ1 10 may not include separate radio front end circuitry QQ1 12; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ1 1 1. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ1 14. Radio front end circuitry QQ1 12 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ1 12 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ1 18 and/or amplifiers QQ1 16. The radio signal may then be transmitted via antenna QQ1 1 1. Similarly, when receiving data, antenna QQ1 1 1 may collect radio signals which are then converted into digital data by radio front end circuitry QQ1 12. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ1 10 components, such as device readable medium QQ130, WD QQ1 10 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ1 10 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ1 14. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ1 10, but are enjoyed by WD QQ1 10 as a whole, and/or by end users and the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ1 10, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g. , a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some

embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated. User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ1 10. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ1 10. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ1 10. For example, if WD QQ1 10 is a smart phone, the interaction may be via a touch screen; if WD QQ1 10 is a smart meter, the interaction may be through a screen that provides usage (e.g. , the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ1 10, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ1 10, and to allow processing circuitry QQ120 to output information from WD QQ1 10. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ1 10 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ1 10 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ1 10 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ1 10 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ1 10 to which power is supplied.

Figure 14 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE QQ2200 may be any UE identified by the 3 ^rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in Figure 14, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 ^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 14 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 14, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ21 1 , memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof.

Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 14, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In Figure 14, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.)·, programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer. In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In Figure 14, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ21 1 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local- area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ21 1 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ21 1 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.

ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221 , which may comprise a device readable medium.

In Figure 14, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks.

Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any

combination of hardware, software or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

Figure 15 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g. , a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be

implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

As shown in Figure 15, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Figure 15.

In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.

Figure 16 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference to FIGURE 16, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ41 1 , such as a radio access network, and core network QQ414. Access network QQ41 1 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491 , QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.

Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420. Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).

The communication system of Figure 16 as a whole enables connectivity between the connected UEs QQ491 , QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491 , QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ41 1 , core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 17. Figure 17 illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510 further comprises software QQ51 1 , which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ51 1 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.

Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 17) served by base station QQ520.

Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in Figure 17) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531 , which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 17 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491 , QQ492 of Figure 16, respectively. This is to say, the inner workings of these entities may be as shown in Figure 17 and independently, the surrounding network topology may be that of Figure 16. In Figure 17, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the efficiency of AMF re-allocation, and thereby provide benefits such as reduced network overhead signaling, and concomitant reduced interference and power consumption.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ51 1 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ51 1 , QQ531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc. the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ51 1 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.

Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step QQ610, the host computer provides user data. In substep QQ61 1 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure 19 will be included in this section. In step QQ710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application.

In step QQ720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the

embodiments described throughout this disclosure. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

Figure 20 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure 20 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ81 1 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure 21 will be included in this section. In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Embodiments of the present invention present significant advantages over the prior art. During registration, when AMF reallocation is possible, a UE according to embodiments described herein may mark a security context temporary, invoke exceptions to rules associated with the security context, and/or accept unprotected authentication messages. This allows AMF reallocation to be successful where an Initial AMF cannot transfer a security context to a Target AMF. The embodiments described herein are flexible, and introduce a more general message than the one proposed in S3-191413.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data

communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more

embodiments of the present disclosure.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. As used herein, the term“configured to” means set up, organized, adapted, or arranged to operate in a particular way; the term is synonymous with “designed to.” As used herein, the term“substantially” encompasses and accounts for mechanical tolerances, measurement error, random variation, and similar sources of imprecision. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Some of the embodiments contemplated herein are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Example Embodiments

1. A method performed by a wireless device for registering with a wireless communication network, the method comprising:

sending a registration request message to the network;

establishing a first security context with a first network Access and Mobility Management Function (AMF);

receiving a cryptographically unprotected authentication request message from a second AMF; and

processing the unprotected authentication request message.

2. The method of embodiment 1 further comprising

receiving a registration resolution message; and

in response to the registration resolution message, discarding any further received

cryptographically unprotected authentication request message without processing it.

3. The method of embodiment 2 wherein the registration resolution message is a

Registration Accept message or a Registration Reject message.

4. The method of embodiment 1 further comprising marking the first security clearance as temporary, and wherein processing the unprotected authentication request message comprises processing the unprotected authentication request message in response to the first security clearance being marked as temporary.

5. The method of embodiment 4 wherein processing the unprotected authentication request message in response to the first security clearance being marked as temporary further comprises processing the unprotected authentication request message only if an AMF reallocation is expected.

6. The method of embodiment 5 wherein an AMF reallocation is expected if the wireless device included network slicing information in the registration request message.

7. The method of embodiment 4 further comprising, after establishing the first security context:

receiving from the network a first security mode command; and

wherein marking the first security clearance as temporary comprises marking the first security clearance as temporary in response to the security mode command.

8. The method of embodiment 7 wherein the first security mode command includes an indication that the first security context is temporary.

9. The method of embodiment 4 further comprising:

receiving from the network one of a registration resolution message and a second

message including an indication that the first security context is not temporary; and

in response to the registration resolution message or second message, marking the first security context as not temporary.

10. The method of embodiment 9 wherein the first network AMF transferred the first security context to a second network AMF and wherein, after being marked as not temporary, the first security context is between the wireless device and the second network AMF.

1 1. The method of embodiment 4 further comprising:

receiving from the network one of a registration resolution message and a second

message including an indication that the first security context is not temporary; and

in response to the registration resolution message or second message, invalidating or deleting the first security context.

12. The method of embodiment 4 further comprising:

receiving from the network a first partial registration acceptance message, the first partial registration acceptance message including separate indications of status of two or more network operations; and

wherein marking the first security clearance as temporary comprises marking the first security clearance as temporary in response to an indication in the first partial registration acceptance message that an AMF re-allocation is pending.

13. The method of embodiment 12 wherein the first partial registration acceptance message further includes an indication that an authentication procedure is complete.

14. The method of embodiment 12 wherein the first partial registration acceptance message further includes an indication that the first security context is established.

15. The method of embodiment 12 further comprising: receiving from the network a second partial registration acceptance message including an indication that an AMF re-allocation is complete; and

marking the first security clearance as not temporary in response to the second partial registration acceptance message.

16. The method of embodiment 1 further comprising:

receiving from the network a message including an indication that the wireless device should process certain security related tasks according to one or more exceptions to pre-programmed task processing rules;

accessing the one or more exceptions; and

wherein processing the unprotected authentication request message comprises

processing the unprotected authentication request message in response to an exception.

17. The method of embodiment 16 wherein the exceptions are provisioned in the wireless device.

18. The method of embodiment 16 wherein the exceptions are provided to the wireless device by the network in dedicated signaling.

AA. The method of any of the previous embodiments, further comprising:

providing user data; and

forwarding the user data to a host computer via the transmission to the base station.

1. A method, performed by a base station operative in a wireless communication system, for performing registration and AMF re-allocation for a wireless device, the method comprising: receiving from the wireless device a registration request message;

establishing a first security context between the wireless device and a first network Access and Mobility Management Function (AMF);

sending to the wireless device a cryptographically unprotected authentication request message from a second AMF; and

receiving messages sent by the wireless device pursuant to processing the unprotected authentication request message.

2. The method of embodiment 1 further comprising

sending to the wireless device a registration resolution message; and

wherein, in response to the registration resolution message, the wireless device discards any further received cryptographically unprotected authentication request message without processing it.

3. The method of embodiment 2 wherein the registration resolution message is a

Registration Accept message or a Registration Reject message. 4. The method of embodiment 1 further comprising the wireless device marking the first security clearance as temporary, and wherein the wireless device processing the unprotected authentication request message comprises the wireless device processing the unprotected authentication request message in response to the first security clearance being marked as temporary.

5. The method of embodiment 4 wherein the wireless device processing the unprotected authentication request message in response to the first security clearance being marked as temporary further comprises the wireless device processing the unprotected authentication request message only if an AMF reallocation is expected.

6. The method of embodiment 5 wherein an AMF reallocation is expected if the wireless device included network slicing information in the registration request message.

7. The method of embodiment 4 further comprising, after establishing the first security context:

sending to the wireless device a first security mode command; and

wherein the wireless device marking the first security clearance as temporary comprises the wireless device marking the first security clearance as temporary in response to the security mode command.

8. The method of embodiment 7 wherein the first security mode command includes an indication that the first security context is temporary.

9. The method of embodiment 4 further comprising:

sending to the wireless device one of a registration resolution message and a second message including an indication that the first security context is not temporary; and

in response to the registration resolution message or second message, the wireless device marking the first security context as not temporary.

10. The method of embodiment 9 wherein the first network AMF transferred the first security context to a second network AMF and wherein, after being marked as not temporary, the first security context is between the wireless device and the second network AMF.

1 1. The method of embodiment 4 further comprising:

sending to the wireless device one of a registration resolution message and a second message including an indication that the first security context is not temporary; and

in response to the registration resolution message or second message, the wireless device invalidating or deleting the first security context.

12. The method of embodiment 4 further comprising: sending to the wireless device a first partial registration acceptance message, the first partial registration acceptance message including separate indications of status of two or more network operations; and

wherein the wireless device marking the first security clearance as temporary comprises the wireless device marking the first security clearance as temporary in response to an indication in the first partial registration acceptance message that an AMF re-allocation is pending.

13. The method of embodiment 12 wherein the first partial registration acceptance message further includes an indication that an authentication procedure is complete.

14. The method of embodiment 12 wherein the first partial registration acceptance message further includes an indication that the first security context is established.

15. The method of embodiment 12 further comprising:

sending to the wireless device a second partial registration acceptance message

including an indication that an AMF re-allocation is complete; and the wireless device marking the first security clearance as not temporary in response to the second partial registration acceptance message.

16. The method of embodiment 1 further comprising:

sending to the wireless device a message including an indication that the wireless

device should process certain security related tasks according to one or more exceptions to pre-programmed task processing rules;

the wireless device accessing the one or more exceptions; and

wherein the wireless device processing the unprotected authentication request message comprises the wireless device processing the unprotected authentication request message in response to an exception.

17. The method of embodiment 16 wherein the exceptions are provisioned in the wireless device.

18. The method of embodiment 16 further comprising sending the exceptions to the wireless device in dedicated signaling.

BB. The method of any of the previous embodiments, further comprising:

obtaining user data; and

forwarding the user data to a host computer or a wireless device.

Group C Embodiments

C1. A wireless device configured to perform any of the steps of any of the Group A embodiments.

C2. A wireless device comprising:

processing circuitry configured to perform any of the steps of any of the Group A

embodiments; and

power supply circuitry configured to supply power to the wireless device. C3. A wireless device comprising:

processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the wireless device is configured to perform any of the steps of any of the Group A embodiments.

C4. A user equipment (UE) comprising:

an antenna configured to send and receive wireless signals;

radio front-end circuitry connected to the antenna and to processing circuitry, and

configured to condition signals communicated between the antenna and the processing circuitry;

the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;

an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output

information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

C5. A computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to carry out the steps of any of the Group A embodiments.

C6. A carrier containing the computer program of embodiment C5, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

C7. A base station configured to perform any of the steps of any of the Group B

embodiments.

C8. A base station comprising:

processing circuitry configured to perform any of the steps of any of the Group B

embodiments;

power supply circuitry configured to supply power to the wireless device.

C9. A base station comprising:

processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the base station is configured to perform any of the steps of any of the Group B embodiments.

C10. A computer program comprising instructions which, when executed by at least one processor of a base station, causes the base station to carry out the steps of any of the Group B embodiments.

C1 1. A carrier containing the computer program of embodiment C10, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.